- From: Booth, David (HP Software - Boston) <dbooth@hp.com>
- Date: Wed, 9 Aug 2006 11:54:07 -0400
- To: "Schleiff, Marty" <marty.schleiff@boeing.com>, <www-tag@w3.org>
Hi Marty, > From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] > On Behalf Of Schleiff, Marty > . . . > Not all identifiers are intended to persist indefinitely. Some > identifiers (e.g., DDNS IP addresses) actually are intended to be > re-issued as needed. . . . > > It think that one-time pseudonymns (like those used in assertions to > avoid profiling and protect privacy) are also somehow relevant to the > topic of persistence. Ineresting use case! Transient URIs can also be handled using specialized HTTP prefix URIs, as described in http://dbooth.org/2006/urn2http/ . I've just added this to the FAQ: http://dbooth.org/2006/urn2http/#FAQ . > . . . > I agree that persistent identifiers is a management issue and not a > technology issue, and that it's up to the identifier minters > to enforce > the degree of persistence they choose. However, there is value to a > consistent syntactic method for the minters to manifest their > intentions > with respect to persistence and convey those intentions to another > party. A company such as mine has literally thousands of customer, > supplier, and partner companies -- it would pretty difficult for me to > keep track of the variety of approaches each partner might use to > indicate persistence. Good point. This can also be done using specialized http prefix URIs. I've just added this to the FAQ also: http://dbooth.org/2006/urn2http/#FAQ . Here are the techniques mentioned: [[ - The owner of the specialized HTTP prefix can use the rest of the URI to delegate minting authority to other URI owners, such as: http://xyzpurl.org?xyzscheme:foo.com/fum http://xyzpurl.org?xyzscheme:bar.com/boo - In effect, a class of specialized HTTP prefixes can be defined, and individually owned prefixes can declare themselves to be members of that class. For example, if the term http://xyzconsortium.org/terms/xyzprefix is defined to indicate that something is a specialized xyz HTTP prefix, then metadata served (indirectly) via http://foo.com?fum can indicate that "http://foo.com?" is a http://xyzconsortium.org/terms/xyzprefix , and metadata served (indirectly) via http://bar.com?bee can also indicate that "http://bar.com?" is a http://xyzconsortium.org/terms/xyzprefix . ]] David Booth, Ph.D. HP Software dbooth@hp.com Phone: +1 617 629 8881
Received on Wednesday, 9 August 2006 16:03:01 UTC