Subject: Re: [SG16-Unicode] BOM in JSON (was: Re: SG16 meeting summary for July 31st, 2019)
From: Tom Honermann (tom_at_[hidden])
Date: 2019-08-18 19:06:45
Thank you, Henri! This is very helpful!
Ben, the context here is whether weâre ok with producers of the dependency format you specified producing a UTF-8 BOM. It looks like we should be ok to allow them to (optionally) do so given that both of the specs below allow consumers to remove one.
> On Aug 15, 2019, at 2:12 PM, Henri Sivonen <hsivonen_at_[hidden]> wrote:
>> On Thu, Aug 15, 2019 at 5:16 AM Tom Honermann <tom_at_[hidden]> wrote:
>> - Are we ok with allowing a BOM (JSON doesn't permit one)?
> Consuming JSON from a byte source in the Web Platform only supports
> UTF-8 but removes the BOM if there is one. There is no corresponding
> authoring conformance requirement in the Infra Standard, but the
> practical effect is that the BOM does not fail to parse but doesn't
> signal anything.
> The IETF wording requires producers to use UTF-8 without a BOM but
> allows consumers to remove the BOM if it's there, so the Infra
> Standard language and the IETF RFC are compatible on this point.
> (Apologies if this distinction between producer and consumer
> conformance requirements was already made in the meeting.)
> Henri Sivonen
> SG16 Unicode mailing list
SG16 list run by firstname.lastname@example.org