A standard for building APIs in JSON
I would say there is no need for this.<p>JSON/REST are beloved because it's simple and just works. Originally XML itself was simple too with just DTD as "Schema".<p>BUT then all the additional standards like XMLSchema, XSLT, XML-RPC/SOAP turned it in an ugly duck.<p><pre><code>  JSON API is extracted from the JSON transport implicitly 
  defined by Ember Data's REST adapter. 
  http://jsonapi.org/about/
</code></pre>
As JSON-API comes from the Ember.js camp, I remember the Ember vs. Angular discussions on HN 1-2 years ago. Google Trends shows Ember.js has gone nowhere. <a href="https://www.google.com/trends/explore#q=AngularJS%2C%20Ember.js&cmpt=q&tz=" rel="nofollow">https://www.google.com/trends/explore#q=AngularJS%2C%20Ember...</a> (and now there is also React). So I guess the "Ember.js way" to do things failed. At some point we should learn from history, and not turn JSON into SOAP/WSDL - <a href="https://xkcd.com/927/" rel="nofollow">https://xkcd.com/927/</a> .<p>XML-RPC/SOAP and/or many other remote procedure call transport techniques failed in in the long term and are a big pile of legacy mess (CORBA, DCOM, RMI, SAP RFC, .NET Remoting, XML-RPC, etc.):  <a href="http://en.wikipedia.org/wiki/Remote_procedure_call" rel="nofollow">http://en.wikipedia.org/wiki/Remote_procedure_call</a>