GUID-OID-DOI-URN-URL.
I am really interested in the solution to this problem also. It would
seem that there is a confound of "what" and "where". An object ID is a
unique (or at least unambiguous) label. This is not inherently the same
as the location of something. How does one deal with the problem of
objects that exist in more than one place, for instance. This requires
a service akin to what I understand (albeit weakly) to the the Trader
Services of the OMG.
Can we un-confound the "what" and the "where"? Clearly the solution
must allow for persistence and scalability. It needs to be generated
locally, at least on a temporary basis. I breathlessly await the
solution.
--Tom Wason
[log in to unmask] wrote:
>
> Re reference to "globally-unique identifier" below: shouldn't it also be
> persistent/permanent? For example, a URL is a URI but it's not permanent.
> Should we specifically refer to URNs or PURLs instead? Or, to be non-Web
> specific, DOIs?
>
> Cliff Morgan
> Publishing Technologies Director
> John Wiley & Sons Ltd
> Chichester PO19 1UD
> UK
>
> I. Relation Semantics:
>
> The Relation element specifies the relationship between the present
> resource and a target resource, and can be thought of as two entities
> connected by an arc, the arc being a named relationship.
>
> The present resource is unambiguously identifiable as the resource with
> which the metadata is associated (identified in the Identifier element).
>
> The target resource should be unambiguously defined by a globally-unique
> identifier (one of any of several varieties in common usage: ISBN, URI,
> whatever).
--
--------------------------------------------
Thomas D. Wason, Ph.D.
Director of Research and Evaluation
Institute for Academic Technology
University of North Carolina at Chapel Hill
730 Airport Rd., Suite 100
Chapel Hill, North Carolina 27599
919.962.9286
919.962.4321 FAX
|