On 8 Oct 2013, at 23:39, "Mark S. Miller" <erig...@google.com> 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.
By that logic, it should have referred to either Unicode v5.0.0 or v4.1.0 because that were the latest available versions back in July 2006 as per http://www.unicode.org/history/publicationdates.html. On 8 Oct 2013, at 23:51, Allen Wirfs-Brock <al...@wirfs-brock.com> wrote: > 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? Not as far as I can tell. On 8 Oct 2013, at 23:51, Allen Wirfs-Brock <al...@wirfs-brock.com> wrote: > I suspect the version specificity could be removed in the future. Yay! _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
