<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Digital Object Identifiers (DOIs) for Electronic References</title>
	<atom:link href="http://blog.amamanualofstyle.com/2012/01/17/digital-object-identifiers-dois-for-electronic-references/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.amamanualofstyle.com/2012/01/17/digital-object-identifiers-dois-for-electronic-references/</link>
	<description>Official blog of the AMA Manual of Style</description>
	<lastBuildDate>Tue, 09 Apr 2013 06:05:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Otto</title>
		<link>http://blog.amamanualofstyle.com/2012/01/17/digital-object-identifiers-dois-for-electronic-references/#comment-430</link>
		<dc:creator><![CDATA[Otto]]></dc:creator>
		<pubDate>Fri, 10 Feb 2012 22:52:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amamanualofstyle.com/?p=356#comment-430</guid>
		<description><![CDATA[^ &quot;Gets in return,&quot; that is.]]></description>
		<content:encoded><![CDATA[<p>^ &#8220;Gets in return,&#8221; that is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://blog.amamanualofstyle.com/2012/01/17/digital-object-identifiers-dois-for-electronic-references/#comment-429</link>
		<dc:creator><![CDATA[Otto]]></dc:creator>
		<pubDate>Fri, 10 Feb 2012 22:49:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.amamanualofstyle.com/?p=356#comment-429</guid>
		<description><![CDATA[&quot;At the time of publication, DOI names are assigned to content objects themselves; in contrast, URLs are assigned to locations of objects. DOIs are permanent; once assigned, they cannot be changed.&quot;

Like the entire DOI system, this is a bit breezy. The missing qualification is that DOIs are not unique, and thus &quot;content object&quot; doesn&#039;t mean anything as operationally defined. Suppose one issues a commemorative issue of a journal consisting mainly of reprints, and recall that DOIs were originally touted as the solution to deep linking (something that never even came close to occurring). Does the reprinted version of Figure 1 of Article 1 have the same DOI as the original? Does Article 1 itself have the same DOI as the original? By necessity, no. The framework is just a label printer. As such, &quot;because of the DOI system’s technology, DOI links are persistent&quot; obscures the fact that there is *no new technology*--it&#039;s merely a subscriber-based contractual arrangement in which one pays $35,000 a year for the privilege of adding an extra step to solving the original problem, which is keeping track of where you&#039;ve put the data, and getting in return an uninformative user name and somebody else&#039;s branding.]]></description>
		<content:encoded><![CDATA[<p>&#8220;At the time of publication, DOI names are assigned to content objects themselves; in contrast, URLs are assigned to locations of objects. DOIs are permanent; once assigned, they cannot be changed.&#8221;</p>
<p>Like the entire DOI system, this is a bit breezy. The missing qualification is that DOIs are not unique, and thus &#8220;content object&#8221; doesn&#8217;t mean anything as operationally defined. Suppose one issues a commemorative issue of a journal consisting mainly of reprints, and recall that DOIs were originally touted as the solution to deep linking (something that never even came close to occurring). Does the reprinted version of Figure 1 of Article 1 have the same DOI as the original? Does Article 1 itself have the same DOI as the original? By necessity, no. The framework is just a label printer. As such, &#8220;because of the DOI system’s technology, DOI links are persistent&#8221; obscures the fact that there is *no new technology*&#8211;it&#8217;s merely a subscriber-based contractual arrangement in which one pays $35,000 a year for the privilege of adding an extra step to solving the original problem, which is keeping track of where you&#8217;ve put the data, and getting in return an uninformative user name and somebody else&#8217;s branding.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
