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

Re: WebSocket + YASMIN = Viable REST Replacement

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Fri, 27 Jan 2017 11:38:35 +0100
To: Timothy Holborn <timothy.holborn@gmail.com>, W3C Credentials Community Group <public-credentials@w3.org>
Message-ID: <6e463070-da5c-7e6c-df3f-9c44fe6ff877@gmail.com>
On 2017-01-27 11:17, Timothy Holborn wrote:

> Nb: if you find a priority date prior to Manu / Dave, that would be v.interesting.

I did not invent JSON
I did not invent JSON-LD
I did not invent Name spaces
I did not invent HTTP
I did not invent WebSocket
I did not invent Digital signatures
I did not invent A single cryptographic method
I did not invent "@context"


So what's the [possible] contribution then?

It is a collection of [what I consider] useful stuff.
Most "inventions" are of that kind.

However, signed JavaScript objects (which is a part of the underpinnings of YASMIN), using the built-in JSON parser/serializer for normalizing, in my opinion qualifies as a "real" invention:
https://cyberphone.github.io/doc/security/jcs.html#ECMAScript_Compatibility_Mode

Note: I have no IPR claims at all.  My worst fear is that some other party may have such.

Anders



> I wish some priority dates of my own work were earlier.  Genius is unique ;)
>
> On Fri., 27 Jan. 2017, 9:11 pm Timothy Holborn, <timothy.holborn@gmail.com <mailto:timothy.holborn@gmail.com>> wrote:
>
>     I respect your opinions and contributions; yet in this case my view is, meh.  Not well though out. It may develop well, but that wouldn't be progress imho.
>
>
>     On Fri., 27 Jan. 2017, 9:09 pm Anders Rundgren, <anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>> wrote:
>
>         On 2017-01-27 10:58, Timothy Holborn wrote:
>         > The @context makes it RDF as far as I'm aware?
>
>         I indeed borrowed the actual name "@context" from JSON-LD but it is in turn a concept already existing in XML (name space).
>         I would have got the same result if I have called it "@ns" since on the JSON level it is just a property.
>
>
>         > Non quantum restistant crypto is either stupid or intentional.  Given how society finds things, who knows.
>
>         I'm not a cryptographer so I only use what these guys have made available for general usage and is supported by languages and platforms.
>         There are folks working with next generation schemes and I (and most other people) have to rely on these developments.
>
>         Note that the posting was about REST, or more correct, a replacement for REST.
>
>         Anders
>
>         >
>         >
>         > On Fri., 27 Jan. 2017, 8:52 pm Anders Rundgren, <anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com> <mailto:anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>>> wrote:
>         >
>         >     On 2017-01-27 10:12, Timothy Holborn wrote:
>         >     > Alongside stupid: https://en.m.wikipedia.org/wiki/Elliptic_curve_cryptography#Quantum_computing_attacks
>         >
>         >     You claim that this is a [very?] bad idea and/or that it is already done, right?
>         >
>         >     Well...
>         >
>         >     Elliptic curves is the current NIST standard for asymmetric cryptography.  It will (in due time) be replaced by something else which hopefully be a simple upgrade of existing systems including YASMIN.
>         >
>         >     YASMIN is not JSON-LD but it could host JSON-LD including signed JSON-LD.
>         >
>         >     WebSocket has nothing to do with RDF or JSON, it is this context primarily a challenger to REST and HTTP.
>         >
>         >     Anders
>         >
>         >     >
>         >     >
>         >     > On Fri., 27 Jan. 2017, 8:08 pm Timothy Holborn, <timothy.holborn@gmail.com <mailto:timothy.holborn@gmail.com> <mailto:timothy.holborn@gmail.com <mailto:timothy.holborn@gmail.com>> <mailto:timothy.holborn@gmail.com <mailto:timothy.holborn@gmail.com> <mailto:timothy.holborn@gmail.com <mailto:timothy.holborn@gmail.com>>>> wrote:
>         >     >
>         >     >     Looks like RDF[4] dressed up to look like a new opportunity.
>         >     >
>         >     >     [4] https://en.m.wikipedia.org/wiki/JSON-LD
>         >     >
>         >     >
>         >     >     On Fri., 27 Jan. 2017, 7:44 pm Anders Rundgren, <anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com> <mailto:anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>> <mailto:anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com> <mailto:anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>>>> wrote:
>         >     >
>         >     >         WebSocket [1] is claimed to be the most efficient communication method for interactive Web applications.
>         >     >
>         >     >         REST [2] is essentially incompatible with WebSocket although some people try to merge them.
>         >     >         That's IMO fairly pointless, since they are building on different concepts.
>         >     >
>         >     >         YASMIN [3], OTOH was *designed from scratch* to support both event-based communication like WebSocket and postMessage(), as well as traditional request/response schemes.
>         >     >
>         >     >         Anders
>         >     >
>         >     >         1] https://tools.ietf.org/rfc/rfc6455.txt
>         >     >
>         >     >         2] https://en.wikipedia.org/wiki/Representational_state_transfer
>         >     >              https://cyberphone.github.io/doc/web/REST-in-peace.html
>         >     >
>         >     >         3] https://cyberphone.github.io/doc/web/yasmin.html
>         >     >
>         >     >
>         >     >
>         >
>
Received on Friday, 27 January 2017 10:39:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 July 2018 21:19:34 UTC