permanent URIs for media

 "permanence" is a desirable characteristic for many things: data,
names, URIs, etc.

However, it's difficult to think how to "add" permanence. 


We are doing task A, and we have a pretty good way of doing it, but it

characteristic X, how do we add X?


I think "permanence" fits in with "security", "reliability",
"performance", "usable":

characteristics that are best approached from the negative: remove
things that

are "not X".  To make something secure, you discover all of the

and mitigate them. To make something fast, you discover the
bottlenecks and

optimize them.  To make something "permanent", you discover all of the
ways in

which might interrupt continuity and eliminate those.


Permanent IDs in XMP (eXtensible Metadata Platform) and in particular, page 19 of



XMP uses GUID-based URIs for referencing content. It is assumed that
there is

a system/index which can be used to discover content if all you have
is the



Each asset has at least two such identifiers: 

one which changes every time any edit is made by any tool (the
"instance ID"),

 and one of which does not change but refers to the entire version

(the "document ID").  (There is a complex bit of infrastructure for

relationships between versions using History, Ingredients, and other

of relationship metadata.)


The URI scheme "xmp.iid:" is a bit reflexive. 




is a URI which identifies the file that has the following

pair in its metadata:


         xmpMM:InstanceId = "xmp.iid:b9db20421f30bb3fe10e5f90"


(xmpMM is the XML namespace prefix used by the XMP media management

 of metadata properties.)







is a URI which identifies any/all/the most recent file that has the

attribute/value pair in its metadata:


         xmpMM:DocumentId = "xmp.did:b9db20421f30bb3fe10e5f90"


xmp.iid and xmp.did URIs are used only for files that have XMP

stored in the file, not in sidecar files. Files that do not have

XMP still have InstanceID and DocumentID, but not in this form. Some

documents that do have embedded XMP might still have a DocumentID

that does not use xmp.did, because the document started out as a file

without XMP but with some other kind of unique document identifier.


These are URIs (that is, they uniformly identify resources), but they

are only useful as URLs (Uniform Resource Locators) if there is an

of files with XMP indexed by the IDs found within them. In the case

of xmp.did:, it might be necessary to examine modification dates

and history to determine which is the latest of multiple instances

with the same document ID.

Received on Sunday, 6 June 2010 17:57:20 UTC