Re: [Json] Strings

If keys are unicode strings, the proper languagee is:

“For purpose of establishing key equality, comparisons MUST be conducted,
after all escaping is done, on a character-by-character basis by comparing
numeric character codepoints. There is to be no modification of any kind to
the characters in keys, including case-changing or combining-form
normalization.”

On Thu, Jun 6, 2013 at 9:43 AM, Matt Miller (mamille2)
<mamille2@cisco.com>wrote:

>
> On Jun 6, 2013, at 8:59 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>
> > On Jun 5, 2013, at 8:35 PM, Joe Hildebrand (jhildebr) <
> jhildebr@cisco.com> wrote:
> >
> >> On 6/5/13 6:14 PM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:
> >>
> >>> Proposed wording: just before the ABNF at the end of section 2.5, add:
> >>>
> >>> When comparing strings, escaped characters SHOULD compare the same as
> >>> their unescaped counterparts. For example, the following three strings
> >>> SHOULD be considered equivalent for comparisons:
> >>
> >>
> >> Are you sure you want to open pandora's box of comparing strings?
> >
> > Yes. String comparison is used for object keys, which is a hot topic in
> another thread.
> >
> > { "a": 1, "\u0061": 2 }
> >
>
> To (probably vainly) help keep a lid on the box, do we need to note there
> is no expectation of normalization?
>
>
> - m&m
>
> Matt Miller < mamille2@cisco.com >
> Cisco Systems, Inc.
>
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>
>