Sorry, I just took the first sentence here (second one added to the confusion, not clarified it, but this is probably just me): A JSON text is a sequence of tokens. The set of tokens includes six structural characters, strings, numbers, and three literal names. A JSON text is a serialized object or array. Anyway, this is good. It means that the RFC has no problem, it's just me :-) But the conclusion that the RFC does not allow BOM is independent, and I think it stands. Mihai On Mon, Nov 18, 2013 at 9:50 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote: > * mnita@google.com wrote: > >The first four bytes are: > > > > 00 00 00 22 UTF-32BE > > 00 22 E5 65 UTF-16BE > > 22 00 00 00 UTF-32LE > > 22 00 65 E5 UTF-16LE > > 22 E6 97 A5 UTF-8 > > > >The UTF-16 bytes don't match the patterns in RFC, so UTF-16 streams would > >(wrongly) be detected as UTF-8, if one strictly follows the RFC. > > RFC 4627 does not allow string literals at the top level. > -- > Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de > Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de > 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ >
Received on Tuesday, 19 November 2013 08:00:51 UTC