News for hackers. Stuff that matters.
Re:Best Practices for Designing a Pragmatic RESTful API by ams6110 on Monday October 28, 2013 @07:56AM (#6626387)
The strength of xml is xsl. The ability to declaratively transform the content into another form. I'm not aware of any way to do this with json other than by hand-rolling code.
Re:Best Practices for Designing a Pragmatic RESTful API by e12e on Monday October 28, 2013 @08:01AM (#6626402)
I'm not entirely certain that is a plus... Is writing a compiler/translator in xsl really more pleasant/easier to maintain than writing it in a "proper" language?

That said, I really enjoyed: http://www.amazon.com/Program-Generators-Java-Craig-Cleavela...

edit: for example: you could transform an ant build.xml file -- but should you?

Re:Best Practices for Designing a Pragmatic RESTful API by arethuza on Monday October 28, 2013 @09:12AM (#6626645)
I would say that the strength of XML is XPath - forget the rest of XSL (XSLT and XSL-FO) - and I would still avoid it unless there was a real requirement for "document like" content.