Re: [Json] Gen-ART and OPS-Dir review of draft-ietf-json-text-sequence-10

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Paul Hoffman scripsit:

> >   JSON text sequences MUST use UTF-8 encoding; other encodings of JSON
> >   (i.e., UTF-16 and UTF-32) MUST NOT be used.
> > 
> 
> That seems like a good clarifying addition as well.

I continue to think this is a bad idea.  In particular, you cannot claim
that because a text sequence entity body is not valid UTF-8, that it is
not a valid JSON text sequence; as I explained before, the JSON texts
may be truncated or otherwise damaged such that they contain only part
of a UTF-8-encoded character.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan@xxxxxxxx
Deshil Holles eamus.  Deshil Holles eamus.  Deshil Holles eamus.
Send us, bright one, light one, Horhorn, quickening, and wombfruit. (3x)
Hoopsa, boyaboy, hoopsa!  Hoopsa, boyaboy, hoopsa!  Hoopsa, boyaboy, hoopsa!
  --Joyce, Ulysses, "Oxen of the Sun"





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]