Re: [Json] Using a non-whitespace separator (Re: Working Group Last Call on draft-ietf-json-text-sequence)

And, editing my own abnf, the two alternatives are:

JSON-sequence = JSON-text *( %1e JSON-text )
JSON-sequence = ws *( %1e JSON-text )

I see no utility in saying anything about linefeeds whatsoever.

On Wed, Jun 4, 2014 at 10:54 AM, Tim Bray <tbray@textuality.com> wrote:

> Hah, I hadn’t realized that RS (U+001E, INFORMATION SEPARATOR TWO) was
> excluded.   OK, so the abnf for JSON-sequence becomes one of these two:
>
> JSON-sequence = JSON-text *( %1e JSON-text )
> JSON-sequence = *( ws %1e JSON-text )
>
> Depending on whether you see the RS as an initiator or a separator.  I
> think I very slightly prefer the second.
>
>
> On Wed, Jun 4, 2014 at 10:43 AM, Paul Hoffman <paul.hoffman@vpnc.org>
> wrote:
>
>> <no hat>
>>
>> On Jun 4, 2014, at 9:12 AM, Nico Williams <nico@cryptonector.com> wrote:
>>
>> > Alright.  Two proposals:
>> >
>> > 1) Writers MUST precede texts with RS, and SHOULD follow texts with LF.
>> >
>> > (RS must precede at least so as to make any complete text parseable
>> > even if the preceding one was written incompletely.  LF is needed so
>> > as to make line-oriented tooling happy.)
>> >
>> > 2) Writers of logfiles (or any case where incomplete writes are a
>> > problem) MUST do the same as in (1).  Other writers need only emit
>> > (MUST emit) an LF after each text.  Symmetrically, parsers MUST be
>> > able to parse either form.
>>
>> (1) seems much cleaner than (2).
>>
>> --Paul Hoffman
>>
>> _______________________________________________
>> json mailing list
>> json@ietf.org
>> https://www.ietf.org/mailman/listinfo/json
>>
>
>
>
> --
> - Tim Bray (If you’d like to send me a private message, see
> https://keybase.io/timbray)
>

-- 
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)