Re: [URN] Agenda for Washington Meeting -- Questions on URN

"Sam Sun" <ssun@CNRI.Reston.VA.US> Thu, 04 December 1997 14:36 UTC

Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id JAA29058 for urn-ietf-out; Thu, 4 Dec 1997 09:36:30 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id JAA29053 for <urn-ietf@services.bunyip.com>; Thu, 4 Dec 1997 09:36:27 -0500 (EST)
Received: from ns.cnri.reston.va.us (ns.CNRI.Reston.VA.US [132.151.1.1]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id JAA16982 for <urn-ietf@Bunyip.Com>; Thu, 4 Dec 1997 09:36:24 -0500 (EST)
Received: from newcnri.CNRI.Reston.Va.US (newcnri [132.151.1.84]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with SMTP id JAA16494; Thu, 4 Dec 1997 09:39:16 -0500 (EST)
Received: from ssun by newcnri.CNRI.Reston.Va.US (SMI-8.6/SMI-SVR4) id JAA03602; Thu, 4 Dec 1997 09:36:03 -0500
From: Sam Sun <ssun@CNRI.Reston.VA.US>
To: "Rebecca S. Guenther" <rgue@loc.gov>
Cc: "Ron Daniel Jr." <rdaniel@lanl.gov>, urn-ietf@bunyip.com
Subject: Re: [URN] Agenda for Washington Meeting -- Questions on URN
Date: Thu, 04 Dec 1997 09:41:16 -0500
Message-ID: <01bd00c2$ad3db600$29019784@ssun.CNRI.Reston.Va.US>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Sam Sun <ssun@CNRI.Reston.VA.US>
Errors-To: owner-urn-ietf@Bunyip.Com

This is exactly the point I want to make clear. That is:

URN specification SHOULD allow for various schemes using whatever syntax
they define, and that the handle scheme (hdl:) is a particular type of URN
scheme.

It is my believe that a Handle is a URN, and can be presented in syntax of
either "hdl:" or "urn:hdl:". When used under "urn:hdl:" syntax, it is
subject to the syntax rules defined by the URN Syntax draft
(ftp://ds.internic.net/internet-drafts/draft-ietf-urn-syntax-05.txt). And
when presented using "hdl:" syntax, it follows the syntax defined by the
Handle Syntax draft
(ftp://ds.internic.net/internet-drafts/draft-sun-handle-system-00.txt).

Sam
ssun@cnri.reston.va.us


-----Original Message-----
From: Rebecca S. Guenther <rgue@loc.gov>
To: Sam X. Sun <ssun@CNRI.Reston.Va.US>
Cc: Ron Daniel Jr. <rdaniel@lanl.gov>; urn-ietf@Bunyip.Com
<urn-ietf@Bunyip.Com>
Date: Thursday, December 04, 1997 9:15 AM
Subject: Re: [URN] Agenda for Washington Meeting -- Questions on URN


>On Thu, 4 Dec 1997, Sam X. Sun wrote:
>
>>
>> First of all, what I meant by implementation should really be "Syntax
>> definition". It's true that we may never be able to address all possible
>> syntax definitions that ever come up. But limiting URN to one particular
>> syntax definition has the effect of rejecting other URN syntax based on
>> other URL/URI schemes. While "urn:" scheme has its nice feature of easy
>> input from standard English Keyboard, "hdl:" (handle system) scheme has
its
>> advantage of requiring less reserved/excluded characters and allowing
>> native characters to be used without hex encoding, and the "pdi:"
>> (persistent document identifier) scheme has been used for document
>> identification for years.
>
>.....stuff deleted....
>
>> In summary, my point is that "urn:" syntax, as it defined now, serves
well
>> as one URN "syntax definition", or one URN name space. But URN as a
general
>> concept for persistent naming scheme, may not necessarily be restricted
to
>> one URI/URL scheme. Besides "urn:", we now have seen "hdl:" and "pdi:"
>> claiming to be under the URN framework. And there could very well be
other
>> URI/URL schemes to be proposed to serve the same purpose, but with
>> different syntaxes, and with their own set of implementations.
>>
>>
>> Thanks much for your response...
>> Sam
>> ssun@cnri.reston.va.us
>
>I've been trying to follow these discussions and am feeling confused. I
>always thought that the URN specification allows for various schemes using
>whatever syntax they define, and that the handle scheme (hdl:) was a
>particular type of URN scheme. That is how we represented it to the MARC
>world when we requested the addition of a data element to accommodate a
>URN.  Although the particular need was for a handle in a MARC record, our
>intention was to accommodate URNs in general.  This message implies that
>you have a URN or you have a handle, and a handle is not a URN. Please
>clarify.
>
>Rebecca
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>^^  Rebecca S. Guenther                                   ^^
>^^  Senior MARC Standards Specialist                      ^^
>^^  Network Development and MARC Standards Office         ^^
>^^  Library of Congress                                   ^^
>^^  Washington, DC 20540-4020                             ^^
>^^  (202) 707-5092 (voice)    (202) 707-0115 (FAX)        ^^
>^^  rgue@loc.gov                                          ^^
>^^                                                        ^^
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>
>