If you look at the actual dependencies, it hardly matter as they are upon
things that is very hard to image ever changing.
The dependencies are:
1)The definition of "code point"
http://www.unicode.org/versions/Unicode6.2.0/ch03.pdf#G2212
2) the actual code point to abstract character associations for the "ASCII
characters" mentioned in the spec.
3) the UTF-16 encoding algorithm used for non-BMP code points
4) ?? is there anything else?
I suspect the version specificity could be removed in the future.
Allen
On Oct 8, 2013, at 2:39 PM, Mark S. Miller wrote:
> JSON must not change. If it refers to "the latest Unicode, whatever that is",
> then it is potentially subject to disruption by (admittedly unlikely) future
> changes to Unicode.
>
>
> On Tue, Oct 8, 2013 at 1:44 PM, Mathias Bynens <[email protected]> wrote:
> On 8 Oct 2013, at 22:19, Rick Waldron <[email protected]> wrote:
> > On Tue, Oct 8, 2013 at 4:10 PM, Mathias Bynens <[email protected]> wrote:
> > > As for Unicode, it explicitly refers to Unicode 6.2.0, even though
> > > version 6.3.0 was released last week.
> >
> > The document was written in July, which was before last week.
>
> No need to get snarky.
>
> Why not just refer to http://www.unicode.org/versions/latest/, i.e. the
> latest available Unicode version? The version number doesn’t really matter
> for JSON as all it cares about is the concept of “code points”, the range of
> which is fixed.
>
> Sorry for not raising this earlier, I must’ve missed the call for feedback
> in/before July.
> _______________________________________________
> es-discuss mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/es-discuss
>
>
>
> --
> Cheers,
> --MarkM
> _______________________________________________
> es-discuss mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
