2 ms·
Requisite XKCD link: https://xkcd.com/927/ https://xkcd.com/927/ The problem with XML is that there are a lot of different programming models (streaming, pull,
by zdw 11y ago
Requisite XKCD link: https://xkcd.com/927/ https://xkcd.com/927/
The problem with XML is that there are a lot of different programming models (streaming, pull, DOM), many schema and validation formats (DTD, XSD, RELAX NG), to the point that most people didn't care and just manually generated some monstrosity surrounded <>'s using printf.
Personally, the way to get value out of using XML today is to find or make a schema in the most restrictive and expressive format possible that's supported by your development environment (RELAX NG or Schematron are the prime contenders), then use it as a safety belt every time you read or write data. The schema helps handle all the nastiness of parsing, which is the real enemy: https://www.usenix.org/system/files/login/articles/login_aug15_02_bratus.pdf https://www.usenix.org/system/files/login/articles/login_aug...
- agentgt 11y agoI agree but XML the language with out namespaces or schemas is still useful. Schema like technology are surprisingly hard to implement and very similar to writing a type checker. Most human readable formats do not support any sort of validation and just now we are starting to see the newer formats try to come up with schema specifications (http://json-schema.org/ http://json-schema.org/). I think the problem with XML has little to do with the language but the organizing ivory tower organizations that got carried away with extending it... but at least those extensions/enhancement were extensions and not modifications of the language itself (ie new versions). An anecdotal observation is newer specifications for languages seem to follow a more open and transparent ala OSS philosophy (ie spec is on github).