On 07 Jan 2014, at 10:31, Anders Rundgren <[email protected]> wrote:
>> That’s not JSON.
>> ("Parsing Restrictions:” "• The original property order must be preserved.”)
>
> It is a correct but [somewhat] restricted JSON syntax.
The syntax conformance is not the point.
In my version of a “somewhat restricted JSON syntax", a double newline in front
of a string means that the string is a binary string in base64url decoding.
Fully conforming. And, I’m expecting all of your implementations to heed this
and automatically decode those binaries, of course. Oh, and decode strings
starting with \u003a as a symbol, while continuing to decode strings starting
with an unescaped colon as a string.
That’s just not the way JSON works.
If you need a special parser for a syntax, it’s no longer JSON.
Grüße, Carsten
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
