4 ms·
W3C's XML (and also semantic web stuff) is an excellent example of what not to do as standardization body. XML may be important for enterprises, but what was a
by tannhaeuser 4y ago
W3C's XML (and also semantic web stuff) is an excellent example of what not to do as standardization body. XML may be important for enterprises, but what was achieved for the web except a decade-long meta discussing, resulting into HTML taken away (or back if you will) by browser vendors after years of stagnation?
There was zero need for XML; recall XML is just a proper subset of SGML by its original developers, which was used to specify HTML until version 4. And even today, SGML is the only game in town to parse HTML (including version 5, up to minor trivialities) based on an international standard, whereas Hickson's/WHATWG's procedural parsing spec has become unmaintainable and isn't covered by a test suite, precisely because it doesn't follow a formal model, but started from a prose description of what an SGML parser does but lost track. Not a great outcome for a markup language used daily by billions of people; especially since HTML the markup language hasn't really changed for a very long time, whereas everything around it (CSS, JS) had to change drastically to make up for HTML's stagnation and first W3C's, then WHATWG's fuckups.
- bawolff 4y agoXML may have failed as a syntax for HTML, but it was enormously succesful in its own right. W3C has lots of failures and bad standards. I don't think the base XML spec was one of them, even if i think JSON is better for most usecases.
- Kwpolska 4y agoIt was successful in the 2000s, but then everyone figure out it’s pointless, and all data exchange in software written in the past decade is in JSON or possibly protobuf.
- bawolff 4y agoAll things have a time. XML was succesful in its. That it was eventually taken over by competitors doesn't really detract from it being hugely succesful in its time.