It is the circle of life: XML is a fine format for structured text, but some people decided it should be used for everyhing - tabular data, key-value sets, prog

It is the circle of life: XML is a fine format for structured text, but some people decided it should be used for everyhing - tabular data, key-value sets, programming code what have you. Then somebody figures out an alternative (JSON) is much simpler and concise for some particular use cases. And then some people decides that JSON should be used for everything. It wont be long before someone propose JHTML - HTML in JSON-notation. And of course JCSS. We programmers love simplicity. The selling point of JSON was that it was really simple compared to the pile of specs which XML had become. But after a while it turns out people actually needed the features the XML standards provided: validation, querying etc. And a similar set of specs grow around JSON. My guess for the next revolution: Some people figure out it is really annoying to have to quote keys in JSON and that JSON does not express expressions or DSL's very well. So s-expressions comes into fashion. And we get sexpr-schema, sexpr-query, and at some point someone will propose sexprs as a standard for structured hypertext.