[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Registered Namespace prefixes

• To: Jeff Lowery <Jeff.Lowery@c...>
• Subject: Re: Registered Namespace prefixes
• From: "Chiusano Joseph" <chiusano_joseph@b...>
• Date: Wed, 05 Mar 2003 13:19:37 -0500
• Cc: "'Gavin Thomas Nicol'" <gtn@r...>, XML Dev <xml-dev@l...>
• Organization: BAH
• References: <4827EC373E03DB44AC2AB3900430896B02661B@w...>

This seems like a case of Thread Deja Vu...

I believe this progressed to the point where some felt that a prefix
registry would not necessarily be useful, but a namespace identifier
registry would potentially be useful. 

[Not trying to jump-start thread, just clarifying!]

Jeff Lowery wrote:
> 
> > -----Original Message-----
> > From: Gavin Thomas Nicol [mailto:gtn@r...]
> 
> > On Wednesday 26 February 2003 12:54 pm, Jeff Lowery wrote:
> > > My opinion is that the answer lies in a prefix registry
> 
> > Why do you need one? If you register foo: as a prefix, so you
> > can then do
> > foo:bar, why not simply register foo:bar instead?
> 
> That would address a different use case: to guarantee the uniqueness (and
> associations of) each universal name (I won't call it expanded name, since
> there's nothing to expand).
> 
> The prefix registry is NO MORE THAN a short-string repository. THE ONLY
> SEMANTIC is that ownership is designated as belonging to a registree.  WHILE
> IT IS POSSIBLE to store association information (such as internet domain,
> local names, RDDL documents, etc.), those extensions should not be "core".
> 
> > FWIW. I
> > can't see the value
> > in either... neither guarantees any kind of interpretation.
> 
> Precisely, that IS its value: there's very little interpretation to be made
> about the information stored.  Any interpretations one cares to add are
> outside the scope of the registry.  This makes the registry simple and
> economical to maintain.  It need be no more complex than web site registries
> that are around today.  The one possible exception is that it may be very
> desirable to query the registry FOR THE SOLE REASON of establishing whether
> a candidate prefix is already registered, and to know who registered it.
> 
> [Sorry 'bout the caps, but people seem to be missing the point of the
> original proposal.  Since I'm unable to articulate it better, I'll just
> articulate it louder.]
> 
> -- Jeff
> 
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> 
> The list archives are at http://lists.xml.org/archives/xml-dev/
> 
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>

begin:vcard 
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@b...
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard

• References:
  • RE: Registered Namespace prefixes
    • From: Jeff Lowery <Jeff.Lowery@c...>

• Prev by Date: RE: Registered Namespace prefixes
• Next by Date: Life as an SGML Neanderthal (WAS RE: The subsetting has begun)
• Previous by thread: RE: Registered Namespace prefixes
• Next by thread: Re: Registered Namespace prefixes
• Index(es):
  • Date
  • Thread