W3C home > Mailing lists > Public > public-identity@w3.org > December 2011

JSON Description Language

From: Anders Rundgren <anders.rundgren@telia.com>
Date: Tue, 06 Dec 2011 03:51:13 +0100
Message-ID: <4EDD8321.8080707@telia.com>
To: "public-identity@w3.org" <public-identity@w3.org>
The following is related to DOMCrypt and similar...


Having a strong background in XML schema authoring I'm slightly
puzzled by the enthusiasm of using "secure" objects that (seem) to
have no notion of explicit (built-in) name-spaces or a description

Lets say that you have a system that accepts a certain set of
different objects.  How can you tell the difference between
them without writing some kind of "content sniffer"?

How can you deal with JSON objects in Java?  It seems that you
only get an "Object" and then have to explicitly cast that
based on knowledge of the data structure.

If I were into the JOSE stuff, I would consider adding a mandatory
name-space to all container objects which would open the door
to automatic generation of proxy objects and data validation.
There's no imminent need to agree on a JSON DL at this stage.

Received on Tuesday, 6 December 2011 02:51:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:09:06 UTC