Re: A request for formal registration of "ucode" as URN
ishikawa <chiaki.ishikawa@ubin.jp> Wed, 25 January 2012 10:41 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 505B721F8646 for <urn-nid@ietfa.amsl.com>; Wed, 25 Jan 2012 02:41:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.392
X-Spam-Level: *
X-Spam-Status: No, score=1.392 tagged_above=-999 required=5 tests=[AWL=0.282, BAYES_50=0.001, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_53=0.6]
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 i6nmQWO5FWk9 for <urn-nid@ietfa.amsl.com>; Wed, 25 Jan 2012 02:41:21 -0800 (PST)
Received: from post.ubin.jp (post.ubin.jp [202.32.0.84]) by ietfa.amsl.com (Postfix) with ESMTP id 3156021F864D for <urn-nid@apps.ietf.org>; Wed, 25 Jan 2012 02:41:21 -0800 (PST)
Received: from post.ubin.jp (post [127.0.0.1]) by localhost.ubin.jp (Postfix) with ESMTP id 97B9529AC38; Wed, 25 Jan 2012 19:41:10 +0900 (JST)
Received: from home.intra.ubin.jp (home.intra.ubin.jp [10.129.1.1]) by post.ubin.jp (Postfix) with ESMTP id 8175829AB26; Wed, 25 Jan 2012 19:41:10 +0900 (JST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by home.intra.ubin.jp (Postfix) with ESMTP id E50CB426597; Wed, 25 Jan 2012 19:41:19 +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 8L8RONxFtAZv; Wed, 25 Jan 2012 19:41:18 +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 4CCAF426150; Wed, 25 Jan 2012 19:41:18 +0900 (JST)
Message-ID: <4F1FDC5B.50802@ubin.jp>
Date: Wed, 25 Jan 2012 19:41:31 +0900
From: ishikawa <chiaki.ishikawa@ubin.jp>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: urn-nid@apps.ietf.org
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> <4F0FE671.6070709@ubin.jp> <CA+9kkMDjGRt3f-EAXsYO_Yfmpr2uvffYiLzYZqcBbBUS9k860g@mail.gmail.com> <4F1065E1.7080208@stpeter.im> <4F14FE53.5000807@ubin.jp> <4F15ADE6.3070101@stpeter.im>
In-Reply-To: <4F15ADE6.3070101@stpeter.im>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
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: Wed, 25 Jan 2012 10:41:22 -0000
Dear all, I have uploaded a very minor change to draft-ishikawa-yrpunl-ucode-urn-01.txt The change is that the use of "<" and ">" was not deleted in a couple of places. The two usages in main text part were missed when the usage was removed in ABNF description. E.g. <ucode-number> vs ucode-number I noticed them and deleted the usage and now uploaded the "-02" version. (I am not sure if it is customary to update the submission and expiration date on the document, presumably it is, so I did.) The document is available at http://datatracker.ietf.org/doc/draft-ishikawa-yrpunl-ucode-urn/history/ Thank you in advance for your attention. Regards, Chiaki Ishikawa On (2012年01月18日 02:20), Peter Saint-Andre wrote: > Thank you, Ishikawa-san. I have requested an IETF Last Call. > > Peter > > On 1/16/12 9:51 PM, ishikawa wrote: >> Dear Peter,Ted, and readers of the mailing list, >> >> I have uploaded a revised version of "draft-ishikawa-yrpunl-ucode-urn" >> to correct the mention of outdated >> RFC for URI syntax (from RFC 2396 to RFC 3986), and >> removed the use of "<",">" from the non-terminal symbols >> in ABNF description of ucode urn name. This makes it easier to read the >> ABNF. (Per Peter's suggestion.) >> >> The newly submitted modified document is available at the following. >> >> https://datatracker.ietf.org/doc/draft-ishikawa-yrpunl-ucode-urn/ >> >> Thank you in advance for your attention. >> >> Sincerely, >> Chiaki Ishikawa >> >> On (2012年01月14日 02:12), Peter Saint-Andre wrote: >>> Yes, I agree. >>> >>> I shall initiate IETF Last Call on this specification, so that the IESG >>> can consider it before the end of my term at IETF 83. >>> >>> On 1/13/12 10:07 AM, Ted Hardie wrote: >>>> 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/ >
- A request for formal registration of "ucode" as U… ishikawa
- Re: A request for formal registration of "ucode" … ishikawa
- Re: A request for formal registration of "ucode" … ishikawa
- Re: A request for formal registration of "ucode" … ishikawa
- Re: A request for formal registration of "ucode" … Ted Hardie
- Re: A request for formal registration of "ucode" … Peter Saint-Andre
- Re: A request for formal registration of "ucode" … Ted Hardie
- Re: A request for formal registration of "ucode" … ishikawa
- Re: A request for formal registration of "ucode" … Ted Hardie
- Re: A request for formal registration of "ucode" … Peter Saint-Andre
- Re: A request for formal registration of "ucode" … ishikawa
- Re: A request for formal registration of "ucode" … Peter Saint-Andre
- Re: A request for formal registration of "ucode" … ishikawa