Digital object identifier - Revision history

Tom: /* Problems */

2025-03-07T18:56:34Z

‎Problems

Tom: /* Standardization */

2019-12-20T18:14:46Z

‎Standardization

Tom: /* External links */

2019-12-20T18:12:57Z

‎External links

Tom: /* Display */

2019-12-20T18:11:14Z

‎Display

Tom: /* Nomenclature and syntax */

2019-12-20T18:10:02Z

‎Nomenclature and syntax

Tom: /* Nomenclature and syntax */

2019-12-20T18:08:26Z

‎Nomenclature and syntax

Tom: /* Notes */

2019-12-20T18:07:06Z

‎Notes

Tom: /* External links */

2019-12-20T18:06:34Z

‎External links

Tom: /* External links */

2019-12-20T18:06:19Z

‎External links

Tom: /* Problems */

2019-12-20T18:05:11Z

‎Problems

@@ Line 24: / Line 24: @@
 The IDF designed the DOI system to provide a form of [[Persistent identifier|persistent identification]], in which each DOI name permanently and unambiguously identifies the object to which it is associated. It also associates [[metadata]] with objects, allowing it to provide users with relevant pieces of information about the objects and their relationships. Included as part of this metadata are network actions that allow DOI names to be resolved to web locations where the objects they describe can be found. To achieve its goals, the DOI system combines the [[Handle System]] and the [[indecs Content Model]] with a social infrastructure.
-The Handle System ensures that the DOI name for an object is not based on any changeable attributes of the object such as its physical location or ownership, that the attributes of the object are encoded in its metadata rather than in its DOI name, and that no two objects are assigned the same DOI name. Because DOI names are short character strings, they are human-readable, may be copied and pasted as text, and fit into the [[Uniform Resource Identifier|URI]] specification. The DOI name-resolution mechanism acts behind the scenes, so that users communicate with it in the same way as with any other web service; it is built on [[open architecture]]s, incorporates [[Computational trust|trust mechanisms]], and is engineered to operate reliably and flexibly so that it can be adapted to changing demands and new applications of the DOI system.<ref>https://arstechnica.com/science/2010/03/dois-and-their-discontents-1/|title= DOIs and their discontents|last= Timmer|first= John|date= 6 March 2010|work= [[Ars Technica]]|accessdate= 5 March 2013}}</ref> DOI name-resolution may be used with [[OpenURL]] to select the most appropriate among multiple locations for a given object, according to the location of the user making the request.<ref>Susanne DeRisi,  Rebecca|last2= Kennison|first3= Nick|last3= Twyman|title= Editorial: The what and whys of DOIs|journal= [[PLoS Biology]]|volume= 1|issue= 2|page= e57|date= 2003|doi= 10.1371/journal.pbio.0000057|pmid= 14624257|pmc= 261894}} {{open access}}</ref> However, despite this ability, the DOI system has drawn criticism from librarians for directing users to non-free copies of documents that would have been available for no additional fee from alternative locations.<ref>Open access to scientific and technical information: the state of the art|first= Jack|last= Franklin|title= Open access to scientific and technical information: state of the art and future trends|editor1-first= Herbert|editor1-last= Grüttemeier|editor2-first= Barry|editor2-last= Mahon|publisher= IOS Press|date= 2003 https://books.google.com/?id=2X3gW1lUvN4C&pg=PA74#v=onepage&q|isbn= 978-1-58603-377-4}}</ref>
+The Handle System ensures that the DOI name for an object is not based on any changeable attributes of the object such as its [[Physical Location]] or ownership, that the attributes of the object are encoded in its metadata rather than in its DOI name, and that no two objects are assigned the same DOI name. Because DOI names are short character strings, they are human-readable, may be copied and pasted as text, and fit into the [[Uniform Resource Identifier|URI]] specification. The DOI name-resolution mechanism acts behind the scenes, so that users communicate with it in the same way as with any other web service; it is built on [[open architecture]]s, incorporates [[Computational trust|trust mechanisms]], and is engineered to operate reliably and flexibly so that it can be adapted to changing demands and new applications of the DOI system.<ref>https://arstechnica.com/science/2010/03/dois-and-their-discontents-1/|title= DOIs and their discontents|last= Timmer|first= John|date= 6 March 2010|work= [[Ars Technica]]|accessdate= 5 March 2013}}</ref> DOI name-resolution may be used with [[OpenURL]] to select the most appropriate among multiple locations for a given object, according to the location of the user making the request.<ref>Susanne DeRisi,  Rebecca|last2= Kennison|first3= Nick|last3= Twyman|title= Editorial: The what and whys of DOIs|journal= [[PLoS Biology]]|volume= 1|issue= 2|page= e57|date= 2003|doi= 10.1371/journal.pbio.0000057|pmid= 14624257|pmc= 261894}} {{open access}}</ref> However, despite this ability, the DOI system has drawn criticism from librarians for directing users to non-free copies of documents that would have been available for no additional fee from alternative locations.<ref>Open access to scientific and technical information: the state of the art|first= Jack|last= Franklin|title= Open access to scientific and technical information: state of the art and future trends|editor1-first= Herbert|editor1-last= Grüttemeier|editor2-first= Barry|editor2-last= Mahon|publisher= IOS Press|date= 2003 https://books.google.com/?id=2X3gW1lUvN4C&pg=PA74#v=onepage&q|isbn= 978-1-58603-377-4}}</ref>
 The [[indecs Content Model]] as used within the DOI system associates metadata with objects. A small kernel of common metadata is shared by all DOI names and can be optionally extended with other relevant data, which may be public or restricted. Registrants may update the metadata for their DOI names at any time, such as when publication information changes or when an object moves to a different URL.

@@ Line 67: / Line 67: @@
 The maintainers of the DOI system have deliberately not registered a DOI namespace for URNs, stating that:
-{{quotation|URN architecture assumes a DNS-based Resolution Discovery Service (RDS) to find the service appropriate to the given URN scheme. However no such widely deployed RDS schemes currently exist.... DOI is not registered as a URN namespace, despite fulfilling all the functional requirements, since URN registration appears to offer no advantage to the DOI System. It requires an additional layer of administration for defining DOI as a URN namespace (the string {{code|urn:doi:10.1000/1}} rather than the simpler {{code|doi:10.1000/1}}) and an additional step of unnecessary redirection to access the resolution service, already achieved through either http proxy or native resolution. If RDS mechanisms supporting URN specifications become widely available, DOI will be registered as a URN.|International DOI Foundation|Factsheet: DOI System and Internet Identifier Specifications{{sfnp|International DOI Foundation|2012|}}}}
+<blockquote>URN architecture assumes a DNS-based Resolution Discovery Service (RDS) to find the service appropriate to the given URN scheme. However no such widely deployed RDS schemes currently exist.... DOI is not registered as a URN namespace, despite fulfilling all the functional requirements, since URN registration appears to offer no advantage to the DOI System. It requires an additional layer of administration for defining DOI as a URN namespace (the string {{code|urn:doi:10.1000/1}} rather than the simpler {{code|doi:10.1000/1}}) and an additional step of unnecessary redirection to access the resolution service, already achieved through either http proxy or native resolution. If RDS mechanisms supporting URN specifications become widely available, DOI will be registered as a URN.|International DOI Foundation|Factsheet: DOI System and Internet Identifier Specifications{{sfnp|International DOI Foundation|2012|</blockquote>
 ==References==

@@ Line 75: / Line 75: @@
 [[Category:Identifier]]
-==External links==
+===External links===
 * [https://doi.org/  Official Web site]
 * [http://shortdoi.org Short DOI] – DOI Foundation service for converting long DOIs to shorter equivalents

@@ Line 17: / Line 17: @@
 ===Display===
-The official ''DOI Handbook'' explicitly states that DOIs should display on screens and in print in the format <code>doi:10.1000/182</code>.<ref name="C4WDefault-2811140">https://doi.org/doi_handbook/2_Numbering.html#2.6.1 |title=DOI Handbook – Numbering |date=13 February 2014 |accessdate=30 June 2014 |work=doi.org |author1=<!--Staff writer(s); no by-line.--> |archiveurl=https://web.archive.org/web/20140630181440/http://www.doi.org/doi_handbook/2_Numbering.html |archivedate=30 June 2014 |deadurl=no |at=Section 2.6.1 Screen and print presentation}}</ref>
+* The official ''DOI Handbook'' explicitly states that DOIs should display on screens and in print in the format <code>doi:10.1000/182</code>.<ref name="C4WDefault-2811140">https://doi.org/doi_handbook/2_Numbering.html#2.6.1 |title=DOI Handbook – Numbering |date=13 February 2014 |accessdate=30 June 2014 |work=doi.org |author1=<!--Staff writer(s); no by-line.--> |archiveurl=https://web.archive.org/web/20140630181440/http://www.doi.org/doi_handbook/2_Numbering.html |archivedate=30 June 2014 |deadurl=no |at=Section 2.6.1 Screen and print presentation}}</ref>
+* Contrary to the ''DOI Handbook'', a major DOI registration agency, recommends displaying a URL (for example, <code><nowiki>https://doi.org/10.1000/182</nowiki></code>) instead of the officially specified format (for example, <code>[https://doi.org/10.1000/182 doi:10.1000/182]</code>)<ref>DOI Display Guidelines|url=http://www.crossref.org/02publishers/doi_display_guidelines.html}}</ref><ref>New Crossref DOI display guidelines are on the way|url=http://blog.crossref.org/2016/09/new-crossref-doi-display-guidelines.html}}</ref> This URL is persistent (there is a contract that ensures persistence in the DOI.ORG domain), so it is a [[Persistent uniform resource locator|PURL]] &mdash; providing the location of an [[HTTP proxy]] server which will redirect web accesses to the correct online location of the linked item.<ref name="dd"/><ref>first=Andy |last=Powell |title=Resolving DOI Based URNs Using Squid: An Experimental System at UKOLN |journal = D-Lib Magazine|date=June 1998|url=http://www.dlib.org/dlib/june98/06powell.html| issn=1082-9873}}</ref>
-Contrary to the ''DOI Handbook'', [[CrossRef]], a major DOI registration agency, recommends displaying a URL (for example, <code><nowiki>https://doi.org/10.1000/182</nowiki></code>) instead of the officially specified format (for example, <code>[https://doi.org/10.1000/182 doi:10.1000/182]</code>)<ref>DOI Display Guidelines|url=http://www.crossref.org/02publishers/doi_display_guidelines.html}}</ref><ref>New Crossref DOI display guidelines are on the way|url=http://blog.crossref.org/2016/09/new-crossref-doi-display-guidelines.html}}</ref> This URL is persistent (there is a contract that ensures persistence in the DOI.ORG domain), so it is a [[Persistent uniform resource locator|PURL]] &mdash; providing the location of an [[HTTP proxy]] server which will redirect web accesses to the correct online location of the linked item.<ref name="dd"/><ref>first=Andy |last=Powell |title=Resolving DOI Based URNs Using Squid: An Experimental System at UKOLN |journal = D-Lib Magazine|date=June 1998|url=http://www.dlib.org/dlib/june98/06powell.html| issn=1082-9873}}</ref>
+* The CrossRef recommendation is primarily based on the assumption that the DOI is being displayed without being hyper-linked to its appropriate URL – the argument being that without the hyperlink it is not as easy to copy-and-paste the full URL to actually bring up the page for the DOI, thus the entire URL should be displayed, allowing people viewing the page containing the DOI to copy-and-paste the URL, by hand, into a new window/tab in their [[Web browser|browser]] in order to go to the appropriate page for the document the DOI represents.<ref>https://www.crossref.org/news/2011-08-02-crossref-revises-doi-display-guidelines/</ref>
 ==Problems==

@@ Line 8: / Line 8: @@
 ===Nomenclature and syntax===
-* A DOI is a type of Handle System handle, which takes the form of a [[character string]] divided into two parts, a prefix and a suffix, separated by a slash.
+* A DOI is a type of Handle System handle, which takes the form of a character string divided into two parts, a prefix and a suffix, separated by a slash.
 <code>prefix/suffix</code>
-* The prefix identifies the registrant of the identifier, and the suffix is chosen by the registrant and identifies the specific object associated with that DOI. Most legal [[Unicode]] characters are allowed in these strings, which are interpreted in a [[case-insensitive]] manner. The prefix usually takes the form <code>10.NNNN</code>, where <code>NNNN</code> is a series of at least 4 numbers greater than or equal to <code>1000</code>, whose limit depends only on the total number of registrants.<ref name="CrossRefDOI">http://www.crossref.org/01company/15doi_info.html |archive-url=https://web.archive.org/web/20021021021703/http://www.crossref.org/01company/15doi_info.html |dead-url=yes |archive-date=2002-10-21 |access-date=10 June 2016 |title=doi info & guidelines |website=CrossRef.org |publisher=Publishers International Linking Association, Inc. |date=2013 |quote=All DOI prefixes begin with "10" to distinguish the DOI from other implementations of the Handle System followed by a four-digit number or string (the prefix can be longer if necessary). }}</ref><ref name="DOIKeyFacts">https://doi.org/factsheets/DOIKeyFacts.html |access-date=10 June 2016 |title=Factsheet—Key Facts on Digital Object Identifier System |website=doi.org |publisher=International DOI Foundation |date=June 6, 2016 |quote=Over 18,000 DOI name prefixes within the DOI System}}</ref> The prefix may be further subdivided with periods, like <code>10.NNNN.N</code>.<ref name="2.2.2">https://doi.org/doi_handbook/2_Numbering.html#2.2.2 |access-date=10 June 2016 |title=DOI Handbook—2 Numbering |website=doi.org |publisher=International DOI Foundation |date=February 1, 2016 |quote=The registrant code may be further divided into sub-elements for administrative convenience if desired. Each sub-element of the registrant code shall be preceded by a full stop.}}</ref>
+* The prefix identifies the registrant of the identifier, and the suffix is chosen by the registrant and identifies the specific object associated with that DOI. Most legal [[Unicode]] characters are allowed in these strings, which are interpreted in a [[case-insensitive]] manner. The prefix usually takes the form <code>10.NNNN</code>, where <code>NNNN</code> is a series of at least 4 numbers greater than or equal to <code>1000</code>, whose limit depends only on the total number of registrants.<ref name="CrossRefDOI">http://www.crossref.org/01company/15doi_info.html https://web.archive.org/web/20021021021703/http://www.crossref.org/01company/15doi_info.html |dead-url=yes |archive-date=2002-10-21 |access-date=10 June 2016 |title=doi info & guidelines |website=CrossRef.org |publisher=Publishers International Linking Association, Inc. |date=2013 |quote=All DOI prefixes begin with "10" to distinguish the DOI from other implementations of the Handle System followed by a four-digit number or string (the prefix can be longer if necessary). }}</ref><ref name="DOIKeyFacts">https://doi.org/factsheets/DOIKeyFacts.html |access-date=10 June 2016 |title=Factsheet—Key Facts on Digital Object Identifier System |website=doi.org |publisher=International DOI Foundation |date=June 6, 2016 |quote=Over 18,000 DOI name prefixes within the DOI System}}</ref> The prefix may be further subdivided with periods, like <code>10.NNNN.N</code>.<ref name="2.2.2">https://doi.org/doi_handbook/2_Numbering.html#2.2.2 |access-date=10 June 2016 |title=DOI Handbook—2 Numbering |website=doi.org |publisher=International DOI Foundation |date=February 1, 2016 |quote=The registrant code may be further divided into sub-elements for administrative convenience if desired. Each sub-element of the registrant code shall be preceded by a full stop.}}</ref>
 * For example, in the DOI name <code>10.1000/182</code>, the prefix is <code>10.1000</code> and the suffix is <code>182</code>. The "10." part of the prefix distinguishes the handle as part of the DOI namespace, as opposed to some other Handle System namespace,{{efn-ua|Other registries are identified by other strings at the start of the prefix. Handle names that begin with "100." are also in use, as for example in the following citation: {{cite journal|hdl=100.2/ADA013939 |url=http://handle.dtic.mil/100.2/ADA013939 |title=Development of a Transmission Error Model and an Error Control Model l |journal=<!-- --> |volume=<!-- --> | date=May 1975 |last1=Hammond |first1=Joseph L., Jr. |last2=Brown |first2=James E. |last3=Liu |first3=Shyan-Shiang S. |bibcode=1975STIN...7615344H|publisher=Rome Air Development Center|series=Technical Report RADC-TR-75-138}}}} and the characters <code>1000</code> in the prefix identify the registrant; in this case the registrant is the International DOI Foundation itself. <code>182</code> is the suffix, or item ID, identifying a single object (in this case, the latest version of the ''DOI Handbook'').
 * DOI names can identify creative works (such as texts, images, audio or video items, and software) in both electronic and physical forms, [[performance]]s, and abstract works<ref name=doifaq2>https://doi.org/faq.html#1 |title=Frequently asked questions about the DOI system: 2. What can be identified by a DOI name? | accessdate = 23 April 2010 | date = 17 February 2010|origyear=update of earlier version |publisher=International DOI Foundation}}

@@ Line 87: / Line 87: @@
 ==External links==
 {{Wikidata property|P356}}
-* {{official website|https://doi.org/}}
+* [https://doi.org/  Official Web site]
 * [http://shortdoi.org Short DOI] – DOI Foundation service for converting long DOIs to shorter equivalents
 * [https://doi.org/factsheets/DOIIdentifierSpecs.html Factsheet: DOI System and Internet Identifier Specifications]