[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: michaelm@netsol.com
Cc: George Belotsky <george@register.com>, "Hollenbeck, Scott" <shollenbeck@verisign.com>, ietf-provreg@cafax.se
From: Martin Oldfield <m@mail.tc>
Date: Thu, 15 Mar 2001 16:40:33 +0000 (GMT)
In-Reply-To: <20010315105315.G12359@bailey.dscga.com>
Sender: owner-ietf-provreg@cafax.se
Subject: Re: Unique handle generation

>>>>> "Michael" == Michael Mealling <michael@bailey.dscga.com> writes:

--> snip <--

    Michael> My recommendation is this: use the
    Michael> <registry-handle>-<local-handle> syntax where
    Michael> registry-handle is registered with the IANA and
    Michael> local-handle is a unique identifier assigned however the

Rather than having an IANA registered registry-handle, can't one
simply use a URI ? This idea is used by XML namespaces [2], and
similar to Rick Wesson's idea [3]. 

From the handle perspective I don't think it's necessary that the URI
actually points at anything, though of course this could happen in
future---this actually mirrors the XML situation (see
e.g. [4]). Following the XML example, the registry handle URI would be
a natural place to store things like a specification of the registry,
its policies and so forth.

Are there lessons to be learned from XML namespaces ? I've done little
more than browse the FAQs [5] but I'm sure there are people here much
more knowledgable.

    Michael> registry sees fit. Then, to handle equivalence between
    Michael> registries, the base schema of all objects (if that has a
    Michael> concept here, I haven't looked yet) allow for a way for
    Michael> one object to say two things: "Hey, I'm also known as
    Michael> FOO-BAR, BAZ-BAR, and HOMER-DONUTS." as well as "I was
    Michael> also known as PREHISTORIC-CAVEMAN at sometime in the
    Michael> past". The one thing this fixes is that equivalence may

Presumably this implies that the local-parts can't be reused ?

    Michael> be a pre-registry concept. I.e. while Bill may consider
    Michael> WM110-ARIN and WM35-RADB the same, the registries
    Michael> involved may have some policy where they're not allowed
    Michael> to either know or publish that information.

    Michael> -MM

    Michael> [1]
    Michael> http://www.cafax.se/ietf-provreg/maillist/2001-03/msg00128.html

[2] http://www.w3.org/TR/REC-xml-names/
[3] http://www.cafax.se/ietf-provreg/maillist/2001-03/msg00059.html
[4] http://www.xmlhack.com/read.php?item=974
[5] http://www.rpbourret.com/xml/NamespacesFAQ.htm

Cheers,
-- 
Martin Oldfield,
AdamsNames Ltd.


Home | Date list | Subject list