JSON-RPC vs. YASMIN. Was: A Critical Analysis of REST APIs for "Transaction Systems"

Here is the intended YASMIN RPC mapping system:
https://cyberphone.github.io/doc/web/yasmin.html#apimapping

It doesn't seem to benefit by adding "jsonrpc" or "params" properties since all core characteristics (platform/audience/transport/security/etc) of YASMIN messages is supposed to be (implicitly) provided by the "@context" URI.

How you can add signature support to an "API" (in a practical way) is still not addressed...
In message-oriented YASMIN-powered applications this is trivial: you create the message and then sign it.

Anders

Received on Monday, 30 January 2017 06:09:40 UTC