Lists Home |
Date Index |
- From: Ron Daniel <RDaniel@DATAFUSION.net>
- To: Jerome McDonough <email@example.com>, Kent Sievers <firstname.lastname@example.org>, email@example.com
- Date: Tue, 8 Jun 1999 16:46:15 -0700
Just to clarify a point or two in Jerry's message:
> Most of the URN crowd has been reluctant to put URN resolution on to
[Ron Daniel] Very true. Cowards that we are, none of us
would like to be fingered as the person responsible for
breaking the global Domain Name System.
> My take on looking over the URN Working
> Group's documents is that the default assumption by the IETF
> is that client software will first turn to DNS and ask where it can
> find a
> for a particular URN namespace (DNS will use NAPTR records to identify
> for particular URN name spaces) and then go to the resolver identified
> by DNS
> to resolve particular URNs.
[Ron Daniel] A couple of clarifications. The main point
is that the DNS itself is not used for looking up individual
documents, instead it is used for locating 'resolvers' which
hold databases of lots of document IDs and locations.
Also, we want people to use this method LAST, not first. Use
local resolvers first. (For example, to resolve UUID URNs
someone might write some code that first looked into the
client machine's registry. Catalogs could also be used
for local resolution info). If that fails, try a workgroup
or enterprise resolver. (For example, at Los Alamos we used to
have a demo resolver which was a proxy server that trapped URNs,
looked to see if they were from a namespace our library knew a
lot about, and sent them to the library's resolver if they were.
Only if that failed or if they were from another namespace did
we try using the NAPTR-based resolution.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)