3 ms·
" Where things really went completely awry is XML Schema." I think XML worked out OK for its intended purpose because there was a lot of experience with SGML,
by jamesbritt 17y ago
" Where things really went completely awry is XML Schema."
I think XML worked out OK for its intended purpose because there was a lot of experience with SGML, HTML, and ad-hoc attempts at "re-purposing" HTML. Folks could say, well, we tried this and that, and this works and that is painful. And since it was not assured to be a success, there were fewer major vendors clamoring to get their fingerprints all over it.
But after XML caught on there was interest from tool vendors to beef things up, largely with abstractions that had yet to see real-world testing, and with things that just so happened to require massive IDE support.
The worst may have been the schema stuff, but there's a lot of competition.
BTW, this page http://www.w3.org/TR/REC-xml/ http://www.w3.org/TR/REC-xml/ gives me 40 pages of print preview. A good chunk consists of appendices, but the main part runs more than 11 pages. I don't recall where I got that number from.
I'll just blame Tim Bray, for lack of a real excuse. :)
- fauigerzigerk 17y agoWhat really surprises me in XML Schema is not so much all the half baked stuff they put in and not even the crazy nesting of complex types for instance. What surprises me is what XML Schema cannot do. One thing it cannot do is probably the most frequently used structure in all structured documents I have seen. It is to specify that a particular set of quantified elements can occur in any order. The reason they gave for not supporting this is that validators would have to be more than contextless state machines. That's insane. They have created a schema language that doesn't support the most important schema constraint of them all for performance reasons.