Re: [Json] Proposal: JSON text sequence MIME type and Proposed Standard

["Markus Lanthaler" <[e-mail]>]

On Wednesday, March 12, 2014 6:03 AM, Nico Williams wrote:
On Tuesday, March 11, 2014, Tim Bray wrote:
> > I lean to \s+ because as soon as you see the first char, you’re
> > at the start of the next legal JSON text. 
>
> The separator can be whitespace.  It can be any whitespace recognized
> as such in the JSON ABNF.  It could be a subset of that.  It also
> could be any character or string of them that can't start a JSON value's
> encoding.  Since in practice existing apps use whitespace, we should use
> whitespace.  If other apps can be found using ", " or "," or whatever,
> we might be able to require parser support for all of them or else define
> multiple MIME types.

Given that "," is already used as separator in objects and arrays, I think it would make sense to at least include that as additional separator (and not just whitespace). Please let's not create multiple media types.


--
Markus Lanthaler
@markuslanthaler