Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt

[Carsten Bormann <[e-mail]>]

On Jul 21, 2017, at 17:35, Peter Saint-Andre - Filament <[e-mail]> wrote:
> 
> Improvements over my suggested text are welcome. Or do you think that
> the text in -04 is good enough? I find it somewhat ambiguous.

Hi Peter,

>>> When an entity transmits JSON text over a network,
>>> e.g. as the payload of an application protocol, it MUST encode
>>> that text using UTF-8 [RFC3629].

… seems close enough for me.

It clearly has a nitpicking opportunity, but other attempts to improve the original text so far have made it worse.
I was mainly trying to point out that the mere fact that one can willfully pretend to misunderstand this (or the previous) text does not mean that it actually is ambiguous to a cooperating reader — the previous version is just a bit hard to read (and shouts out that we had trouble wordsmithing it).  I was then trying to point out what the essence of the statement is: The term JSON when used in a context that implies interchange (as opposed to representing the concept of JSON within a program or single system) also includes its encoding in UTF-8.  But I’m not trying to wordsmith here, I’ll leave that to the native speakers.

Grüße, Carsten