* Matt Miller (mamille2) wrote: >There does not appear to be any consensus on explicitly allowing or >disallowing of a Byte Order Mark (BOM). Neither RFC4627 nor the current >draft mention BOM anywhere, and the modus operandi of the JSON Working >Group has been to leave text unchanged unless there was wide support. To be clear, that means application/json entities that start with a byte sequence that matches U+FEFF encoded in UTF-8/16/32 is malformed because the ABNF does not allow a U+FEFF at that position (and interpreting such a sequence as anything other than ordinary character data requires explicit specification). I do think an informational note saying as much could be useful. -- Björn Höhrmann · mailto:bjoern@xxxxxxxxxxxx · 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/