@smallcircles If you control both ends of the pipeline, you don’t need any validation or interoperability. XML technologies are thus not needed anymore. The price you pay as a developer is a more and more heavy dependency on a HTML5-compliant web browser. The web as a whole pays an additional cost that the developer becomes the little tyrant of their corner of the web, and the browser ecosystem is collapsing into a monopoly. We can’t build anything useful on top of that.
Yes, thank you. It is a bit of everything. Where I worked in Print production at the time we used all the XML standards to max extent and got great benefit from doing so. It all crumbled down very quickly with the take-off of Web where #JSON mapped way better to JS than #XML did, esp. when also honoring the intricate web of (de-facto) standards that had emerged, and how the XML ecosystem got captured by corporations peddling expensive products, such Enterprise service buses and the like.
It would have been great if #XHTML had stuck around. In hindsight the shift to HTML5 may be seen as a move by the WHATWG to establish their dominance over the #browser market.
As for #JSONLD it must see to rewin hearts and minds, must inspire and convince people to take the bet of adopting it.