On 2015-10-29 12:47, Jim Schaad wrote:
Is there any reason to believe that other JSON libraries are going to
implement the ES6 standard? For example, what should one expect either a
hand rolled version or a C# version do?
I can only speak for myself. I'm currently upgrading my Java-tools
to support ES6 number serialization. The rest already supports a
superset of ES6 (with respect to JSON processing NB).
Anyway, since JavaScript is the mother of JSON, it seems logical that
the off-springs adapt as well :-)
Anders
-----Original Message-----
From: jose [mailto:[email protected]] On Behalf Of Anders Rundgren
Sent: Wednesday, October 28, 2015 11:40 PM
To: [email protected]
Subject: [jose] At a glance: JWS vs "in-object" ES6/JSON signatures
ES6-compliant in-object JS/JSON signature:
var inObjectSignedData =
{
// Object data expressed as JS properties
"device": "Pump2",
"value": 1e-18,
// Object signature
"signature": {
...Protected headers + Signature value expressed as JS
properties...
}
};
JavaScript's JSON.parse() and JSON.stringify() suffice for
"canonicalization"
purposes.
Converting the above to JWS JSON Serialization you would get:
var signedData =
{
// Object data in a coded format
"payload":"<payload contents>",
// Protected headers wrapped in Base64URL
"protected":"<integrity-protected header contents>",
// Signature in a unique format
"signature":"<signature contents>"
}
ES6 was released in June 2015 so this opportunity is actually quite new.
Cheers,
Anders
http://webpki.org/ietf/draft-rundgren-predictable-serialization-for-json-too
ls-
00.html#rfc.section.3.3
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
