Re: A request for formal registration of "ucode" as URN

Ted Hardie <ted.ietf@gmail.com> Fri, 13 January 2012 17:07 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6276021F85F1 for <urn-nid@ietfa.amsl.com>; Fri, 13 Jan 2012 09:07:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.402
X-Spam-Level:
X-Spam-Status: No, score=-4.402 tagged_above=-999 required=5 tests=[AWL=1.197, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jllAnCL1-QSn for <urn-nid@ietfa.amsl.com>; Fri, 13 Jan 2012 09:07:46 -0800 (PST)
Received: from mail-yw0-f49.google.com (mail-yw0-f49.google.com [209.85.213.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9CE2721F858F for <urn-nid@apps.ietf.org>; Fri, 13 Jan 2012 09:07:46 -0800 (PST)
Received: by yhjj72 with SMTP id j72so441129yhj.22 for <urn-nid@apps.ietf.org>; Fri, 13 Jan 2012 09:07:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=r/rAFU5SACtCPWMZB79/LUa4TSE41bB9YCKanwhrtKk=; b=JMQUT0G8Mws7dT4VLaZwx+/ob3lTGcyX/vUOVbUeTGDihq8jRnz1qWUfI7rG9pOPkX idVsyBzU7GYVh6AQYaCKA63+SoqBAf3UxfE/hsQi45bCYF2sgtmgXtRBDQLG7+gsJ95s Bso1ifyNscsDok+x1XVsRZtn8eQrVDCLqAdI8=
MIME-Version: 1.0
Received: by 10.236.121.168 with SMTP id r28mr3156532yhh.51.1326474465087; Fri, 13 Jan 2012 09:07:45 -0800 (PST)
Received: by 10.236.116.165 with HTTP; Fri, 13 Jan 2012 09:07:45 -0800 (PST)
In-Reply-To: <4F0FE671.6070709@ubin.jp>
References: <4EF2C203.4010205@ubin.jp> <4EF30BB5.90002@ubin.jp> <4EF7E1B0.8000504@ubin.jp> <4F0D14F7.9000506@ubin.jp> <CA+9kkMBLRXETpE5P-AKVj+TkvS-zib6FGo0hsbyWWJPfmtmS_g@mail.gmail.com> <4F0E0CBA.1020806@stpeter.im> <CA+9kkMB5jy-VbCvO0BCc0a0Wwzz5EctxBN6BB5zp9BVLBMSJDw@mail.gmail.com> <4F0FE671.6070709@ubin.jp>
Date: Fri, 13 Jan 2012 09:07:45 -0800
Message-ID: <CA+9kkMDjGRt3f-EAXsYO_Yfmpr2uvffYiLzYZqcBbBUS9k860g@mail.gmail.com>
Subject: Re: A request for formal registration of "ucode" as URN
From: Ted Hardie <ted.ietf@gmail.com>
To: ishikawa <chiaki.ishikawa@ubin.jp>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: urn-nid@apps.ietf.org
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn-nid>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jan 2012 17:07:47 -0000

Dear Ishikawa-san,

Thank you for your careful consideration of the message.  With this
data, I believe that this registration is ready to proceed.

regards,

Ted

2012/1/13 ishikawa <chiaki.ishikawa@ubin.jp>:
> Dear Ted and Peter,
>
> This is Chiaki Ishikawa.
>
> Thank you for your comments.
>
> I take the suggestion from TED seriously, and
> I checked with the original developer of the specification for the
> intention behind the "case-sensitive" nature.
>
> It turns out that the hexadecimal string that represents ucode in urn
> would be directly translated into XML tags in some of
> the intended applications. (Some of them anyway.)
>
> XML tags are case-sensitive and that is why the capital letters only are
> allowed for hexadecimal "A", "B", "C", "D", "E" and "F" for keeping the
> uniqueness issue of XML tag names under control.
>
> (So I take that conversion to numeric value is less of an issue
> for this particular class of applications. XML is processed in character
> string space more or less.)
>
> So because of the nature of some planned applications (and some of them are
> large-scale deployment), this case-sensitivity dictating the use of  capital
> letters only for hexadecimal string must be there. That is the comment from
> the ucode designers and ucode application developers.
>
> Thank you for your valuable time.
>
> Sincerely,
> Chiaki Ishikawa
>
> On (2012年01月12日 07:32), Ted Hardie wrote:
>> On Wed, Jan 11, 2012 at 2:27 PM, Peter Saint-Andre<stpeter@stpeter.im>  wrote:
>>>
>>>> I would suggest that it permit the use of lower case la-f as well,
>>>> even if the preferred presentation format of the name uses the upper
>>>> case.  There are many hexadecimal representations which do not
>>>> distinguish between the two, so I believe it would be better practice
>>>> to permit them.
>>>
>>> Hi Ted,
>>>
>>> That would be inconsistent with this sentence in Section 2 of
>>> draft-ishikawa-yrpunl-ucode-urn:
>>>
>>>    The entire UCODE-URN is case-sensitive.
>>>
>>
>> I understand.  From a registration perspective, this is clear.  But
>> from a practice perspective, it is my personal advice that this will
>> likely lead to problems, because many hexadecimal parsers would treat
>> a and A as equivalent.  The authors are, of course, free to discard
>> this suggestion if the constraints on their system are such that this
>> will not arise.
>>
>> Ted
>>
>>
>>> Peter
>>>
>>> --
>>> Peter Saint-Andre
>>> http://stpeter.im/
>>
>
>