Son – A minimal subset of JSON for machine-to-machine communication

Re:Son – A minimal subset of JSON for machine-to-machine com... by dsp1234 on Tuesday March 14, 2017 @05:35PM (#13871666)

"Object keys must be unique.""

How should the following be serialized (if at all)?

{"a":0,"\u0073\u0323\u0307":1,"\u1E69":2,"Z":3}

Note that I'm using the \u forms even though they aren't allowed via the specification because, HN doesn't show unicode combining properly sometimes, and so that's it's clear to see that it's a different byte pattern.

[ Parent | on HN ]

Re:Son – A minimal subset of JSON for machine-to-machine com... by seagreen on Tuesday March 14, 2017 @06:51PM (#13872232)

The plan is to go codepoint by codepoint in ascending order:

`{"Z":3,"a":0,"\u0073\u0323\u0307":1,"\u1E69":2}`

See this issue for the discussion: https://github.com/seagreen/Son/issues/1

My current understanding is that RFC 7159 doesn't require Unicode normalization to be performed, if it does we're in trouble: https://tools.ietf.org/html/rfc7159

[ Parent | on HN ]