IMHO, JSON can be seen as the simplified, fat-free child, non Enterprise-Edition of XML; where features are created out of popular demand -as opposed to being c

IMHO, JSON can be seen as the simplified, fat-free child, non Enterprise-Edition of XML; where features are created out of popular demand -as opposed to being created by committee decision-. So far, we have: XML -> JSON BaseX, eXistdb -> MongoDB, RethinkDB XSD, DTD -> JSON Schema WSDL -> HATEOAS XML-RPC -> JSON-RPC XPath -> JSONPath xmlns -> JSON-LD SAX -> clarinet -------------------- Would we have: XSLT -> Baobab ?