Re: [Json] Kicking Off JSONbis

[Barry Leiba <[e-mail]>]

> I must admit that I am puzzled as to how ECMA-404 can be a normative
> reference for any document that is a minor change from rfc7159.  What in
> ECMA-404 is needed to understand or implement what is in rfc7159?

Rob has it nailed in his message:
"To me, it seems like a political or diplomatic gesture that helps the
Internet to move forward.

"Framing it in technical or standards-wonk terms seems counterproductive.
I don't think there are substantive issues in those areas that would be
resolved by objecting to the plan in the charter."

That really is the point: tying the two documents together more tight,
to make people more comfortable that they are not likely (certainly
not intended) to diverge later.

> As has been stated, rfc7159 already references ECMA-404.  A conservative way
> to make a closer connection from rfc7159 to ECMA-404 would be to state that
> ECMA-404 has an alternative description of JSON that is extremely close to
> the definition in rfc7159.

Such a statement would, indeed, be an excellent one to put into 7159bis.

Barry, responsible AD