RE: [URN] WG last call: URN Namespace Definition Mechanisms
"Larry Masinter" <masinter@parc.xerox.com> Fri, 09 October 1998 18:34 UTC
Received: from services.bunyip.com (services.Bunyip.Com [192.77.55.2]) by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA04679 for <urn-archive@ietf.org>; Fri, 9 Oct 1998 14:34:34 -0400 (EDT)
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id NAA06461 for urn-ietf-out; Fri, 9 Oct 1998 13:53:47 -0400 (EDT)
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 NAA06450 for <urn-ietf@services.bunyip.com>; Fri, 9 Oct 1998 13:53:42 -0400 (EDT)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id NAA27483 for urn-ietf@services; Fri, 9 Oct 1998 13:53:44 -0400 (EDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by mocha.bunyip.com (8.8.5/8.8.5) with SMTP id NAA27478; Fri, 9 Oct 1998 13:53:39 -0400 (EDT)
Received: from casablanca.parc.xerox.com ([13.2.16.111]) by alpha.xerox.com with SMTP id <55536(5)>; Fri, 9 Oct 1998 10:53:36 PDT
Received: from copper-208.parc.xerox.com ([13.2.17.212]) by casablanca.parc.xerox.com with SMTP id <71820>; Fri, 9 Oct 1998 10:53:27 PDT
From: Larry Masinter <masinter@parc.xerox.com>
To: Patrik Fältström <paf@swip.net>, Leslie Daigle <leslie@Bunyip.Com>, urn-ietf@Bunyip.Com
Subject: RE: [URN] WG last call: URN Namespace Definition Mechanisms
Date: Fri, 09 Oct 1998 10:53:16 -0700
Message-ID: <001801bdf3ad$b15e9720$c93bb00d@copper-208.parc.xerox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26
Importance: Normal
In-Reply-To: <v04101a05b243a554144f@[192.71.220.146]>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-urn-ietf@Bunyip.Com
Precedence: bulk
Reply-To: Larry Masinter <masinter@parc.xerox.com>
Errors-To: owner-urn-ietf@Bunyip.Com
> >What was the source of the > >requirement for reserving two-letter NIDs for country codes? > > It was output from my discussions on namespaces held with the policy > oversight committee, when I was appointed by IAB there. > > I.e. from some countries (not few), there are "questions" whether the > 2-letter countrycode according to ISO can be allocated within each gTLD. > This was later expanded to the URN namespaces for for example social > security numbers and other series of names which are unique within each > country -- like car license plates in some countries. > > So, the input is from the gTLD debate, and the result solves some problems > on what to do with geopolitical bounded namespaces. I.e. each country have > to handle their namespaces the way they find it the easiest. But is the URN space hierarchical? It would seem that at least according to the proposed "URN Namespace Definition Mechanisms", that each namespace is expected to have consistent set features for the namespace. Are you imagining something like this? urn:us:ca:license:3URN101 California license plates urn:us:ssn:459-82-0101 social security numbers urn:us:tax:100-25-0717 taxpayer ID but each of these sub-namespaces have different 'communities' uniqueness considerations, persistence considerations, etc. The syntax in RFC 2141 suggests that a namespace is just first part. I would imagine that given the use of "-" as a possible delimiter for namespaces, that the syntax actually should be urn:us-ca-license:3URN101 urn:us-ssn:459-82-0101 urn:us-tax:100-25-0717 if a namespace is expected to have consistent values for the elements of the template in draft-ietf-urn-nid-req, or else you're actually defining hierarchical namespaces, where "us:ca:license" is a namespace designator. Am I misunderstanding something about the intention of having a registration form for namespaces? Do you want to reserve all namespaces that start with two letters and then a "-"? Larry -- http://www.parc.xerox.com/masinter
- [URN] WG last call: URN Namespace Definition Mech… Leslie Daigle
- RE: [URN] WG last call: URN Namespace Definition … Larry Masinter
- RE: [URN] WG last call: URN Namespace Definition … Patrik Fältström
- RE: [URN] WG last call: URN Namespace Definition … Leslie Daigle
- Re: New draft-ietf-urn-ietf-07.txt was RE: [URN] … Leslie Daigle
- New draft-ietf-urn-ietf-07.txt was RE: [URN] WG l… Ryan Moats
- RE: [URN] WG last call: URN Namespace Definition … Larry Masinter
- Re: [URN] WG last call: URN Namespace Definition … Claus André Färber
- Re: [URN] WG last call: URN Namespace Definition … Claus André Färber
- Re: New draft-ietf-urn-ietf-07.txt was RE: [URN] … Claus André Färber
- RE: [URN] WG last call: URN Namespace Definition … Larry Masinter
- RE: New draft-ietf-urn-ietf-07.txt was RE: [URN] … Ryan Moats
- RE: [URN] WG last call: URN Namespace Definition … Patrik Fältström
- Re: [URN] WG last call: URN Namespace Definition … Michael Mealling
- RE: [URN] WG last call: URN Namespace Definition … Yves Arrouye
- Re: [URN] WG last call: URN Namespace Definition … Patrik Fältström
- RE: [URN] WG last call: URN Namespace Definition … Ryan Moats
- Re: [URN] WG last call: URN Namespace Definition … Claus André Färber