[
Lists Home |
Date Index |
Thread Index
]
> <Quote>
> 1)elements and attributes have unambiguous names;
> </Quote>
>
> How do you foresee a registy ensuring this?
The registry doesn't; the local authorities do (or should do). All the
registry does is say "Okay, this sequence of characters you asked for can be
prepended as part of any namespace ID you create and manage." It also says,
"Hey, out there! Only this guy can use this sequence of characters at the
start of his namespace identifiers."
Whatever comes after the authority ID begin sequence in the namespace ID
this person or entity creates (<AUTH_xxx:foo/>) is up to them to determine
and ensure the unambiguousness of. If they want to build a local registry
for that purpose they can, but they don't have to. It's not an absolute
requirement for XML document processing to look up anything in a registry.
For document creation, all you need to know is your personal namespace
authority ID start sequence, plus character sequence after that that's being
used in the local domain. It's a lot like URL, except the string IDs are
deliberately short in order to minimize the affect on XML verbosity and
readability, since these prefixes MUST appear in all qualified names (i.e.,
there are not xmlns:xxx="..." declarations.
I realize this would have HUGE impact on legacy XML, mostly of the
simplifying kind, but huge nonetheless. Chance of adoption: +-0%. But you
know, you gotta put up or shut up. This is what I'm puttin' up.
>
> Kind Regards,
> Joe Chiusano
> Booz | Allen | Hamilton
>
> Jeff Lowery wrote:
> >
> > > The question is, is it possible to design a means for the
> > > computer registries to coordinate registration without the
> > > need for a master list if every registry, where a registry
> > > would at it's own top level represents the local authority,
> > > either sends copies of its registry to other registrars or
> > > gets registrations? Does a namespace registration system
> > > require a single rooted authority?
> >
> > Two concerns:
> >
> > 1) authority ID collisions
> > 2) ID disputes
> >
> > For example, if I send out that I've registered "MSFT" as my namespace
> ID
> > authority prefix (e.g. <MSFT_ns1:blah MSFT_ns2:foo="bar"/> ), then I'm
> > likely to collide with Microsoft's preferred very short string authority
> ID,
> > since I imagine they'd want to use their stock index symbol. Assuming
> that
> > I'm correct, and a dispute arises, who resolves it? That's why I think
> you
> > need a central authority, or at least an arbitration board, which is
> more or
> > less the same thing.
> >
> > Now, if you're asking me if the authority registry needs to be
> centralized,
> > I guess it wouldn't. However, there's really no need to 'look-up'
> > authorities in normal metalanguage processing. All we're trying to do
> is
> > make sure that:
> > 1)elements and attributes have unambiguous names;
> > 2) companies and individuals have the means (through the proper use of
> > their authority ID string) to easily create such names.
> >
> > Good questions, Len. I'm forwarding this to the permathread. I hope you
> > won't mind.
> >
> > -----------------------------------------------------------------
> > 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>
|
