Re: [Json] Two Documents

On Thu, Jun 13, 2013 at 6:42 PM, R S <sayrer@gmail.com> wrote:

> This dual-document proposal seems aimed at avoiding impractical character
> encoding requirements. I am sympathetic to that. I would prefer two
> documents over a single document with prescriptive and therefore incorrect
> encoding directives.
>

I think it’s pretty clear that 4627bis can’t retroactively rule out things
that are already in JSON like naked surrogates. So with luck we’re good
with a single JSON spec that says so, then another best-Internet-practices
one that says “don’t”. -T

>
> - Rob
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>
>