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

Re: Are we ready for the namespace ID registry, yet? (was: Rel

• To: Jeff Lowery <Jeff.Lowery@c...>
• Subject: Re: Are we ready for the namespace ID registry, yet? (was: RelaxNG question)
• From: "Chiusano Joseph" <chiusano_joseph@b...>
• Date: Wed, 20 Aug 2003 08:36:10 -0400
• Cc: "'Norman Walsh'" <ndw@n...>, xml-dev@l...
• Organization: Booz Allen Hamilton
• References: <4827EC373E03DB44AC2AB3900430896B672359@c...>

<Quote>
A registry of very short string namespace authority identifiers would be
even simpler, since there are few authorities than namespaces, and it
offloads maintenance of namespace IDs to the authorities. 

I don't blame anyone if they think the idea [expletive deleted]. But criminy: how long
we gonna harp on about complexity of namespace handling in this mailing
list? Here I am, stuck in this permathread again, and what's worse, I
started it.</Quote>

Perhaps it may help if we scope this a bit else spin our wheels for
eternity. Are we speaking here of a registry model/standard that can be
implemented and used by public and private authorities alike, or a
single, centralized public registry that is under a single authority?

Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton


Jeff Lowery wrote:
> 
> > I'm sorry, I clearly misunderstood. What were you proposing a registry
> > for?
> 
> Namespace short-string identifier registry.  I did use the word "prefixes",
> but in the sense that these identifiers would be prepended to local names.
> They're not stubs for full namespace IDs, they are the IDs.
> 
> The reason they're short is so that they can be used for prefixing. Such ID
> prefixes would be mandatory, to eliminate scoping issues. They'd be used for
> both attribute and element names, and namespaces in content.
> 
> Perhaps I'm just stubborn or ignorant for thinking that namespace scoping
> issues are the fundamental processing problem for XML. Forcing namespaces in
> root, as you suggest, do simplify scoping considerably.  Still presents a
> problem for brain-dead cut & paste operations, though, which I'm thinking is
> done "manually" more often that is commonly thought.
> 
> Any registry is a hard pill to swallow.  I would only suggest it because (as
> I've said in a previous thread long ago) it's a pretty simple registry. A
> registry of very short string namespace authority identifiers would be even
> simpler, since there are few authorities than namespaces, and it offloads
> maintenance of namespace IDs to the authorities.
> 
> I don't blame anyone if they think the idea [expletive deleted]. But criminy: how long we
> gonna harp on about complexity of namespace handling in this mailing list?
> Here I am, stuck in this permathread again, and what's worse, I started it.
> 
> -----------------------------------------------------------------
> 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: Are we ready for the namespace ID registry, yet? (w as: RelaxNG question)
    • From: Jeff Lowery <Jeff.Lowery@c...>

• Prev by Date: Re: XSLT 2.0 Processor = XSLT Processor + W3 XML Schema Validator
• Next by Date: Re: A standard approach to glueing together reusableXML fragments in prose?
• Previous by thread: Re: Are we ready for the namespace ID registry, yet? (w as: RelaxNG question)
• Next by thread: RE: Are we ready for the namespace ID registry, yet? (w as: RelaxNG question)
• Index(es):
  • Date
  • Thread