*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
-
Created by
Brian D. Caruso, last updated by user-f44b9 on Nov 06, 2008
1 minute read
This document is intended to contain examples possible of persistent identifier strings and their pros and cons.
Issues
Components of the URI
An example showing different paths to the same resource as an alternative to content negotiation
Jon: why is it necessary to have multiple paths (commons/record, commons/html, and commons/xml)? There seems to be concern that content negotiation is the equivalent of polysemy (one name, many meanings), but this partitions every identifier into yet another segment
From URI-based Naming Systems for Science
http://purl.org/commons/record/ncbi_gene/24866
denotes an Entrez Gene record "without commitment as to representation" - that is, the record's declarative content independent of whether the record is rendered as XML, ASN, or RDF. The information in the record may change over time as annotations are added and corrections are made, but it will always be about the same "gene" (a term that unfortunately is not defined).
http://purl.org/commons/xml/ncbi_gene/24866
denotes the XML version of the record.
http://purl.org/commons/html/ncbi_gene/24866
denotes a web page presenting information from the record in human-readable form.