On Nov 25, 2013, at 1:37 AM, Martin J. Dürst wrote:
>
>
> On 2013/11/23 1:54, Allen Wirfs-Brock wrote:
>>
>>>
>>
>> You should say it that it is not an actual issue of the JSON format whose
>> grammar clearly defines the handling of the 0xfeff code point. Rather it is
>> an upstream data interchange issue that should be dealt with in exactly the
>> same way as with any other data interchange on a similar channel. Say
>> whatever you think is appropriate about BOMs in the transmission of data
>> conforming to the "application/json" MIME type. Just be clear that whatever
>> you decide has nothing to do with the abstract, grammar-based interpretation
>> of the actual JSON payload.
>
> That works for ECMA-404. It does not work for the IETF draft, because it is
> extremely relevant for application/json, which is part of that draft.
>
> Regards, Martin.
It still seems pretty clear. Anything feed as input into an actual parser for
the JSON grammar as standardized by ECMA-404 must not contain any U+feff code
points other than as part of JSON string values. If the application/json wire
format chooses to to use BOMs, then they must be removed before processing by a
standard JSON parser. From a JSON parser prospect, I think that's pretty much
all you need to say.
allen
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
