Cart
[Home] [By Thread] [By Date] [Recent Entries]
Hi Tim, I agree, that avoiding a Schema (both not designing at all, and not using at run time with each XML instance) improves performance of XML processing. XML Schema processing is certainly a processing overhead for processing XML documents/messages. But to my opinion, Schemas add tremendous value to XML processing, when validation constraints need to be imposed. I think, this is a basic notion of data integrity and a very fundamental need for any kind of data processing. On Mon, Nov 16, 2009 at 4:02 AM, Tim Bray <Tim.Bray@s...> wrote: > The textual flaw isn't that it doesn't mention XSD or RNG, the textual flaw is that it mentions *any* schema language. Â A very high proportion of real-world XML processing is entirely free of anything schema-related. Â The vast majority of the XML value proposition is delivered by schema-free well-formed XML. Â Even in those apps that use a schema in their specification, the vast majority of run-time processing is schema-free. Â One of the costliest common mistakes of XML app/language designers is putting too much importance on schemas. Â The XML specification shouldn't be encouraging that mistake. > > My own vision of what XML.next ought to look like may be found at http://www.textuality.com/xml/xmlSW.html -- Regards, Mukul Gandhi
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
