Blog

 4 minute read.

New Crossref DOI display guidelines are on the way

TL;DR

Crossref will be updating its DOI Display Guidelines within the next couple of weeks.  This is a big deal.  We last made a change in 2011 so it’s not something that happens often or that we take lightly.  In short, the changes are to drop “dx” from DOI links and to use “https:” rather than “http:”.  An example of the new best practice in displaying a Crossref DOI link is: https://0-doi-org.lib.rivier.edu/10.1629/22161

Hey Ho, “doi:” and “dx” have got to go

The updated Crossref DOI Display guidelines recommend that https://0-doi-org.lib.rivier.edu/ be used and not http://0-dx-doi-org.lib.rivier.edu/ in DOI links.  Originally the “dx” separated the DOI resolver from the International DOI Foundation (IDF) website but this has changed and the IDF has already updated its recommendations so we are bringing ours in line with theirs.

We are also recommending the use of HTTPS because it makes for more secure browsing.  When you use an HTTPS link, the connection between the person who clicks the DOI and the DOI resolver is secure.  This means it can’t be tampered with or eavesdropped on.  The DOI resolver will redirect to both HTTP and HTTPS URLs.

Timing and backwards compatibility

We are requesting all Crossref member publishers and anyone using Crossref DOIs to start following the updated guidelines as soon as possible.  But realistically we are setting a goal of six months for implementation; we realize that updating systems and websites can take time.  We at Crossref will also be updating our systems within six months - we already use HTTPS for some of our services and our new website (coming very soon!) will use HTTPS.

An important point about backwards compatibility is that “http://0-dx-doi-org.lib.rivier.edu/” and “http://0-doi-org.lib.rivier.edu/” are valid and will continue to work forever-or as long as Crossref DOIs continue to work-and we plan to be around a long time.

We need to do better

Reflecting on the 2011 update to the display guidelines it’s fair to say that we have been disappointed.  It is still much too common to see unlinked DOIs in the form doi:10.1063/1.3599050 or DOI: 10.1629/22161 or even unlinked in this form: http://0-dx-doi-org.lib.rivier.edu/10.1002/poc.3551

What’s so wrong with this approach?  To demonstrate, please click on this DOI doi:10.1063/1.3599050 - oh, you can’t click on it?  How about I send you to a real example of a publisher page.  What I’d like you to do is click the following link and then copy the DOI you find there and come back - http://0-dx-doi-org.lib.rivier.edu/10.1002/poc.3551.

Are you back? I expect you had to carefully highlight the “10.1063/1.3599050” and then do “edit”, “copy”.  That wasn’t too bad but the next step is to put the DOI into an email and send it to someone.  But wait - what are they going to do with “10.1063/1.3599050”?  It’s useless.  If you want it to be useful you’ll have to add “http://doi.org” or https://0-doi-org.lib.rivier.edu/ in the front.

When publishers follow the guidelines it makes things easier - if you go to https://0-doi-org.lib.rivier.edu/10.1063/1.3599050 you’ll note that you can just right click on the full DOI link on the page and get a full menu of options of what to do with it.  One of which is to copy the link and then you can easily paste into an email or anywhere else.

However-putting a positive spin on the spotty adherence to the 2011 update to the DOI display guidelines-everyone has another chance with the latest set of updates to make all the changes at once!

More on HTTPS (future-proofing scholarly linking)

We take providing the central linking infrastructure for scholarly publishing seriously.  Because we form the link between publisher sites all over the web, it’s important that we do our bit to enable secure browsing from start to finish.  In addition, HTTPS is now a ranking signal for Google who gives sites using HTTPS a small ranking boost.

The process of enabling HTTPS on publisher sites will be a long one and, given the number of members we have, it may a while before everyone’s made the transition.  But by using HTTPS we are future-proofing scholarly linking on the web.

Some years ago we started the process of making our new services available exclusively over HTTPS.  The Crossref Metadata API is HTTPS enabled, and Crossmark and our Assets CDN use HTTPS exclusively. Last year we collaborated with Wikipedia to make all of their DOI links HTTPS.  We hope that we’ll start to see more of the scholarly publishing industry doing the same.

So-it’s simple-always make the DOI a full link - https://0-doi-org.lib.rivier.edu/10.1006/jmbi.1995.0238 - even when it’s on the abstract or full text page of the content that the DOI identifies - and use “https://0-doi-org.lib.rivier.edu/”.

Related pages and blog posts

Page owner: Ed Pentz   |   Last updated 2016-September-27
https://0-www-crossref-org.lib.rivier.edu/blog/new-crossref-doi-display-guidelines-are-on-the-way/
0-www-crossref-org.lib.rivier.edu
CC-MAIN-2024-26
45272
application/http; msgtype=response
sha1:GTLNSN35C2X2RRVWBVIQ5IBTBVTHEPXT
<urn:uuid:af3f796e-d9cd-42cf-8917-244221476bde>
2024-06-12T22:30:24Z
216.17.115.87
text/html
sha1:PTHS45IKKI2ZIFEUGACKVWVMOBHPKQUL
<urn:uuid:33f66ba8-7405-44dc-9d49-663f174a8b3f>
https://0-www-crossref-org.lib.rivier.edu/blog/new-crossref-doi-display-guidelines-are-on-the-way/
response
<urn:uuid:12bb6a95-cfd0-448a-91f6-c6dc80fe3f12>
isPartOf: CC-MAIN-2024-26
publisher: Common Crawl
description: Wide crawl of the web for June 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-225
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/