Re: [Json] Consensus call: establishing name equality

[0]

On Sat, Jun 22, 2013 at 6:30 AM, Stefan Drees <stefan@drees.name> wrote:

> On 2013-06-21 18:42 +02:00, Paul Hoffman wrote:
>
>> There are four proposals for establishing name equality:
>>
>> 0) Leave the current draft as-is, not discussing name equality
>>
>> 1) In Section 2.5 ("Strings"), immediately before the ABNF add:
>>     For purpose of establishing name equality, comparisons MUST be
>> conducted, after all unescaping
>>     is done, by comparing numeric character code points. There is to be
>> no modification of any
>>     kind to the characters in names, including case-changing or
>> combining-form normalization.
>>     For example, the following four names MUST be considered equivalent:
>>      * "\u002F"
>>      * "\u002f"
>>      * "\/"
>>      * "/"
>>
>> 2) In Section 2.5 ("Strings"), immediately before the ABNF add:
>>     For purpose of establishing name equality, comparisons MUST be
>> conducted, after all unescaping
>>     is done, by comparing numeric character code points. There MUST NOT
>> be any modification of any
>>     kind to the characters in names, including change of case or change
>> between precomposed and
>>     decomposed forms.
>>     For example, the following four names MUST be considered equivalent:
>>      * "\u002F"
>>      * "\u002f"
>>      * "\/"
>>      * "/"
>>
>> 3) In Section 2.5 ("Strings"), immediately before the ABNF add:
>>     For purpose of establishing name equality, implementations MUST first
>> do all unescaping and
>>     then MUST compare numeric character code points. There is to be no
>> modification of any kind to
>>     the characters in names, including case-changing or combining-form
>> normalization.
>>     For example, the following four names MUST be considered equivalent:
>>      * "\u002F"
>>      * "\u002f"
>>      * "\/"
>>      * "/"
>>
>> Please respond to this message with a list of proposals you could
>> accept, ordered from highest to lowest. Do not list proposals you cannot
>> live with. If you cannot accept any of the proposals, please respond and
>> say why. ...
>>
>
> [3,2,1]
>
> plus: I am happily hopping on John's train, trying to leave "numeric
> character code points" town for some better place ...
>
> {"Stefan":true}
>
>
> ______________________________**_________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/**listinfo/json<https://www.ietf.org/mailman/listinfo/json>
>