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

ishikawa <chiaki.ishikawa@ubin.jp> Fri, 13 January 2012 08:08 UTC

Return-Path: <chiaki.ishikawa@ubin.jp>
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 1938C21F85CF for <urn-nid@ietfa.amsl.com>; Fri, 13 Jan 2012 00:08:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.265
X-Spam-Level: *
X-Spam-Status: No, score=1.265 tagged_above=-999 required=5 tests=[AWL=0.755, BAYES_50=0.001, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 ffsyqXl80CV9 for <urn-nid@ietfa.amsl.com>; Fri, 13 Jan 2012 00:08:25 -0800 (PST)
Received: from post.ubin.jp (post.ubin.jp [202.32.0.84]) by ietfa.amsl.com (Postfix) with ESMTP id 11A6321F85CD for <urn-nid@apps.ietf.org>; Fri, 13 Jan 2012 00:08:24 -0800 (PST)
Received: from localhost (post [127.0.0.1]) by localhost.ubin.jp (Postfix) with SMTP id 906D329AC35; Fri, 13 Jan 2012 17:08:11 +0900 (JST)
Received: from home.intra.ubin.jp (home.intra.ubin.jp [10.129.1.1]) by post.ubin.jp (Postfix) with ESMTP id A41FF29AC35; Fri, 13 Jan 2012 17:08:08 +0900 (JST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by home.intra.ubin.jp (Postfix) with ESMTP id BCCC542699F; Fri, 13 Jan 2012 17:08:17 +0900 (JST)
X-Virus-Scanned: amavisd-new at ubin.jp
Received: from home.intra.ubin.jp ([127.0.0.1]) by localhost (home.intra.ubin.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J1MnHwRIsk6a; Fri, 13 Jan 2012 17:08:16 +0900 (JST)
Received: from [10.254.225.253] (debian-vbox-ci.ddns.intra.ubin.jp [10.254.225.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by home.intra.ubin.jp (Postfix) with ESMTP id 1072B426157; Fri, 13 Jan 2012 17:08:16 +0900 (JST)
Message-ID: <4F0FE671.6070709@ubin.jp>
Date: Fri, 13 Jan 2012 17:08:17 +0900
From: ishikawa <chiaki.ishikawa@ubin.jp>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: A request for formal registration of "ucode" as URN
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>
In-Reply-To: <CA+9kkMB5jy-VbCvO0BCc0a0Wwzz5EctxBN6BB5zp9BVLBMSJDw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
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 08:08:26 -0000

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/
>