W3C home > Mailing lists > Public > public-interledger@w3.org > January 2017

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

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Mon, 30 Jan 2017 07:08:56 +0100
To: Interledger Community Group <public-interledger@w3.org>
Message-ID: <8024952c-878d-791e-3a13-8cb3144a445e@gmail.com>
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

This archive was generated by hypermail 2.3.1 : Monday, 30 January 2017 06:09:41 UTC