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]

 



Manger, James scripsit:

> How about:
> 
>   "A JSON text sequence consists of any number of JSON texts,
>    each prefixed by a Record Separator (U+001E) character, and
>    each suffixed by an End of Line (U+000A) character. It is
>    UTF-8 encoded."
> 
> Say "Information Separator Two (U+001E)" if you really want to be pure.

The trouble with that is that U+001E has no official Unicode name or
function; those come from ISO 6429, which is incorporated (in relevant
part) into US-ASCII, which is described in RFC 20.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan@xxxxxxxx
To say that Bilbo's breath was taken away is no description at all.  There are
no words left to express his staggerment, since Men changed the language that
they learned of elves in the days when all the world was wonderful. --The Hobbit





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