|
> What if it's > <quantity value="999999999/> or something even wacky-er. This would be flagged as an invalid XML stream by a parser (the parser would fail checking the stream is 'well formed' and wouldn't get to the validating stage to check the stream against the DTD, if there is one), because of the missing " before the /> There are at least some basic check is done by a parser... > We never even see standards on XML docs from the same comanpany. > One XML form may have ShipAddress as a tag, and then another on > may have ShipToAddress Ah, the old homonyms and symonyms issue. There are DTD/Schema standards out there, for most of the vertical markets, granted, they are not well publisised, check out places like www.dtd.com, lists.xml.org, etc. You still need to decide which DTD fits your useage, but it's better than creating your own DTD. Of if you feel your DTD/Schema suits you vertical market, you can register your DTD/Schema with these places for other companies in your arena to use a the 'standard' The suggestion that the W3 should take of creating DTD/Schema for all uses is silly, they haven't the resources or market skills to do so. It's down to XML users/developers to move away from working with blinkers on and re-inventing the wheel yet again. There are normally peolpe who have already worked out a usable DTD/schema, you just need to take the time to go find it, just like you would say, find the time to go search out the best price for a new car... --phil +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.