So does anybody remember the posting DOIs and Linked Data: Some Concrete Proposals?
Well, we went with option “D.”
Let’s get straight to the point. If you have curl installed, you can start playing with content-negotiation and CrossRef DOIs right away:
curl -D – -L -H “Accept: application/rdf+xml” “http://dx.doi.org/10.1126/science.1157784”
curl -D – -L -H “Accept: text/turtle” “http://dx.doi.org/10.1126/science.1157784”
curl -D – -L -H “Accept: application/atom+xml” “http://dx.doi.org/10.1126/science.1157784”
Or if you are already using CrossRef’s “unixref” format:
curl -D – -L -H “Accept: application/unixref+xml” “http://dx.doi.org/10.1126/science.1157784”
This will work with over 46 million CrossRef DOIs as of today, but the beauty of the setup is that from now on, any DOI registration agency can enable content negotiation for their constituencies as well. DataCite– we’re looking at you 😉 .
It also means that, as registration agency members (CrossRef publishers, for instance) start providing more complete and richer representations of their content, we can simply redirect content-negotiated requests directly to them.
We expect that that this development will round-out CrossRef’s efforts to support standard APIs including OpenURL and OAI_PMH and we look forward to seeing DOIs increasingly used in linked data applications.
Latest posts by gbilder (see all)
- Members will soon be able to assign CrossrefDOIs to preprints - May 5, 2016
- Community responses to our proposal for early content registration - March 1, 2016
- Rehashing PIDs without stabbing myself in the eyeball - June 11, 2015