Re:Intro to RAML 1.0
by tannhaeuser on Tuesday December 27, 2016 @06:14AM
(#13262530)
It's being used in large-scale projects because it can be used in tenders. Do you want government shell out your tax money for the latest JS fad instead? Imagine the outcry something goes south in such a project.
I agree though that XML is overkill for describing payloads in most RPC scenarios. XML is for describing semistructured data rather than co-inductive data structures (arrays, records, etc.). JSON shines here precisely because it doesn't need a schema to be useful.
However, once you have a need to communicate your API to others, or to develop in a large project/waterfall model, schemaless doesn't cut it. JSON Schema is doing it wrong IMHO. I think that since JSON is basically the object literal syntax of JavaScript, an RPC mechanism could use a JavaScript subset as IDL, in the style of "Logic Programs as Types of Logic Programs" ([1]).
Note that WSDL can describe REST-like and other HTTP-based protocols, not just SOAP.
I agree though that XML is overkill for describing payloads in most RPC scenarios. XML is for describing semistructured data rather than co-inductive data structures (arrays, records, etc.). JSON shines here precisely because it doesn't need a schema to be useful.
However, once you have a need to communicate your API to others, or to develop in a large project/waterfall model, schemaless doesn't cut it. JSON Schema is doing it wrong IMHO. I think that since JSON is basically the object literal syntax of JavaScript, an RPC mechanism could use a JavaScript subset as IDL, in the style of "Logic Programs as Types of Logic Programs" ([1]).
Note that WSDL can describe REST-like and other HTTP-based protocols, not just SOAP.
[1]: http://www.informatik.uni-ulm.de/pm/fileadmin/pm/home/fruehw...