> Of course, what's happening is that the JSON crowd is re-inventing SOAP, but, whatever.
SOAP uses schemas and the like, they just keep reinventing the same RPC as ever, except can't actually bring themselves to use the word. At least JSON-RPC is honest there, and ticks all of TFAA's box:
* uses whatever's under as a trivial transport (covers 1, 3 and 6)
* all data and metadata are part of the higher protocol (covers 2, 4 and 5)
Hence also reinventing CORBA IIOP, DCE, Apollo NCS, Xerox Courier...
Actual innovation in this area seems to be limited to JS background data sync libs. Ironically, reference-capable protocols like CORBA anticipated this whereas flattening it all REST-style was a step backwards.
SOAP uses schemas and the like, they just keep reinventing the same RPC as ever, except can't actually bring themselves to use the word. At least JSON-RPC is honest there, and ticks all of TFAA's box:
* uses whatever's under as a trivial transport (covers 1, 3 and 6)
* all data and metadata are part of the higher protocol (covers 2, 4 and 5)
* is JSON (covers the entire essay)