Blog

photo credit Summary You can use a new Crossref API to query all sorts of interesting things about who funded the research behind the content Crossref members publish. Background Back in May 2013 we launched Crossref’s FundRef service. It can be summarized like this: Crossref keeps and manages a canonical list of Funder Names (ephemeral) and associated identifiers (persistent). We encourage our members (or anybody, really- the list is available under A CC-Zero license waiver) to use this list for collecting information on who funded the research behind the content that our members publish.

The South Park movie , “Bigger, Longer & Uncut” has a DOI: a) http://0-dx-doi-org.libus.csd.mu.edu/10.5240/B1FA-0EEC-C316-3316-3A73-L So does the pornographic movie, “Young Sex Crazed Nurses”: b) http://0-dx-doi-org.libus.csd.mu.edu/10.5240/4CF3-57AB-2481-651D-D53D-Q And the following DOI points to a fake article on a “Google-Based Alien Detector”: c) http://0-dx-doi-org.libus.csd.mu.edu/10.6084/m9.figshare.93964 And the following DOI refers to an infamous fake article on literary theory: d) http://0-dx-doi-org.libus.csd.mu.edu/10.2307/466856 This scholarly article discusses the entirely fictitious Australian “Drop Bear”: e) http://0-dx-doi-org.libus.csd.mu.edu/10.1080/00049182.2012.731307 The following two DOIs point to the same article- the first DOI points to the final author version, and the second DOI points to the final published version:

In April In April for its DOIs. At the time I cheekily called-out DataCite to start supporting content negotiation as well. Edward Zukowski (DataCite’s resident propellor-head) took up the challenge with gusto and, as of September 22nd DataCite has also been supporting content negotiation for its DOIs. This means that one million more DOIs are now linked-data friendly. Congratulations to Ed and the rest of the team at DataCite. We hope this is a trend.

So does anybody remember the posting DOIs and Linked Data: Some Concrete Proposals? Well, we went with option “D.” From now on, DOIs, expressed as HTTP URIs, can be used with content-negotiation. 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://0-dx-doi-org.libus.csd.mu.edu/10.1126/science.1157784” curl -D - -L -H “Accept: text/turtle” “http://0-dx-doi-org.libus.csd.mu.edu/10.1126/science.1157784”

Just a quick heads-up to say that we’ve had a go at incorporating InChIs and ontology terms into our PDFs with XMP. There isn’t a lot of room in an XMP packet so we’ve had to be a bit particular about what we include. InChIs: the bigger the molecule the longer the InChI, so we’ve standardized on the fixed-length InChIKey. This doesn’t mean anything on its own, so we’ve gone the Semantic Web route of including an InChI resolver HTTP URI.

Since last month’s threads (here, here, here and here) talking about the issues involved in making the DOI a first-class identifier for linked data applications, I’ve had the chance to actually sit down with some of the thread’s participants (Tony Hammond, Leigh Dodds, Norman Paskin) and we’ve been able sketch-out some possible scenarios for migrating the DOI into a linked data world. I think that several of us were struck by how little actually needs to be done in order to fully address virtually all of the concerns that the linked data community has expressed about DOIs.

Tony’s recent thread on making DOIs play nicely in a linked data world has raised an issue I’ve meant to discuss here for some time- a lot of the thread is predicated on the idea that Crossref DOIs are applied at the abstract “work” level. Indeed, that it what it currently says in our guidelines. Unfortunately, this is a case where theory, practice and documentation all diverge. When the Crossref linking system was developed it was focused primarily on facilitating persistent linking amongst journals and conference proceedings.

Was outraged (outraged, I tell you) that one of my favorite online comics, PhD, didn’t include DOIs in their recent bibliography of Christmas-related citations.. So I’ve compiled them below. We care about these things so that you don’t have to. Bet you will sleep better at night knowing this. Or perhaps not… A Christmas Reading List… with DOIs. Citation: Biggs, R, Douglas, A, Macfarlane, R, Dacie, J, Pitney, W, Merskey, C & O’Brien, J, 1952, ‘Christmas Disease’, BMJ, vol.

I was happy to read David Shotton’s recent Learned Publishing article, Semantic Publishing: The Coming Revolution in scientific journal publishing, and see that he and his team have drafted a Citation Typing Ontology.* Anybody who has seen me speak at conferences knows that I often like to proselytize about the concept of the “typed link”, a notion that hypertext pioneer, Randy Trigg, discussed extensively in his 1983 Ph.D. thesis.. Basically, Trigg points out something that should be fairly obvious- a citation (i.

Over the past few months there seems to have been a sharp upturn in general interest around implementing an “author identifier” system for the scholarly community. This, in turn, has meant that more people have been getting in touch with us about our nascent “Contributor ID” project. The other day, after seeing my comments in the above thread, Martin Fenner asked if he could interview me about the issue of author identifiers for his blog on Nature Networks, Gobbledygook.