Re: [Json] Proposed minimal change for duplicate names in objects

[Eliot Lear <[e-mail]>]

On 7/3/13 9:48 PM, Pete Resnick wrote:
> Speaking strictly as a participant, and just to give guidance, not
> insist on an outcome.

Same.

>
> Let's remember the meaning of these capitalized words in IETF
> parlance. We use them "where it is actually required for
> interoperation or to limit behavior which has potential for causing
> harm." So a MUST would mean that not doing so would prevent
> interoperation or cause harm. RECOMMENDED (like SHOULD) would also
> mean that not doing so would prevent interoperation or cause harm, but
> "that there may exist valid reasons in particular circumstances to
> ignore a particular item, but the full implications must be understood
> and carefully weighed before choosing a different course."

I have to say that ambiguity of a language implies an introduction to
interoperability problems.  But MUST we use MUST in those cases?   I
would prefer the catch the problem when we have the opportunity.  If the
WG feels differently, Meh.  As Nico said, deal with it at a higher layer.

Eliot