Lists Home |
Date Index |
> 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?
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