Using an XML native NoSQL database is a game changer when consuming XML and producing XML HTTP APIs. A good XQuery engine makes many of the problems people are listing about XML simply go away.
I like @mnot's point about providing "excellent client bindings" in common languages.
What DB do you like for storing and querying XML? I've been using eXistDB lately, but I'd be curious to hear if people are finding something else to be better.
Re:JSON or XML: Just Decide
by rollypolly on Thursday April 12, 2012 @09:56PM
(#3835052)
Yeah, the XML ecosystem is priceless. XPath, for example, is the one reason a project I'm working on can't switch to JSON.
I was about to ask if JSON had an equivalent to XPath / XQuery, but it looks like the answer is "yes." http://stackoverflow.com/questions/8481380/is-there-a-json-e...
That's cool to know, and I might just give it a look. But my perception is still that the supporting ecosystem around XML is more mature and comprehensive, at least for some use-cases.
Re:JSON or XML: Just Decide
by rollypolly on Thursday April 12, 2012 @10:54PM
(#3835209)
Interesting. All these solutions are javascript-based tho. We need a C-based solution (like libxml2).
Re:JSON or XML: Just Decide
by BerislavLopac on Friday April 13, 2012 @05:19AM
(#3835969)
Have you followed the link? Dead. :-(
Sure, you could get there from here with JSON as well, but it sure seems more natural using XML.