Crossref and DataCite support content negotiated DOIs via http://data.crossref.org and http://data.datacite.org. See http://crosscite.org/cn/ for details.
Examples using curl:
curl -D - -L -H "Accept: application/rdf+xml" "https://doi.org/10.1126/science.1157784"
curl -D - -L -H "Accept: text/turtle" "https://doi.org/10.1126/science.1157784"
curl -D - -L -H "Accept: application/atom+xml" "https://doi.org/10.1126/science.1157784"
The Crossref-specific 'unixref' format can be used as well:
curl -D - -L -H "Accept: application/unixref+xml" "https://doi.org/10.1126/science.1157784"
Here are some behind-the-scenes details that most people don't need to know:
All prefixes assigned by Crossref have had their default content negotiation set within in Handle to use Crossref's content negotiation proxy. This is done by assigning an HS_NAMESPACE property on the prefix's record in Handle (automatically done by the Handle system whenever Crossref creates a new prefix on behalf of a member).
20 | HS_NAMESPACE | Wed Feb 23 2011 17:17:15 EST | <HS_NAMESPACE> <DOI.RA>0.SERV/10.crossref</DOI.RA> <locs>0.SERV/10.crossref</locs> </HS_NAMESPACE> |
This points to the Handle record 0.SERV/10.crossref where location properties are set (see The DOI Handbook). In that record there is a property that specifies that for http role "content negotiation" the DOI proxy should redirect to data.crossref.org.
4 | 10320/loc | Tue Mar 15 2011 12:54:15 EDT | <locations> <location weight="0" http_role="conneg" href_template="http://data.crossref.org/{hdl}" /> <xlocation weight="0" role="metadata" href_template="http://metadata.labs.crossref.org/?dois={hdl}&format=unixref" /> </locations> |
If a Crossref member would instead like to perform their own content negotiation for their DOIs they should ask that Crossref modify the Handle record for their prefix.
Example, for Wiley's prefix 10.1002 we would change the HS_NAMESPACE value on 0.NA/10.1002 to:
20 | HS_NAMESPACE | Wed Feb 23 2011 17:17:15 EST | <HS_NAMESPACE> <DOI.RA>0.SERV/10.crossref</DOI.RA> <locs>0.NA/10.1002</locs> </HS_NAMESPACE> |
and add:
4 | 10320/loc | Tue Mar 15 2011 12:54:15 EDT | <locations> <location weight="0" http_role="conneg" href_template="http://cnproxy.wiley.com/{hdl}" /> </locations> |
Comments
0 comments
Please sign in to leave a comment.