<?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/"
		>
<channel>
	<title>Comments on: Should We Embrace the Short URL?</title>
	<atom:link href="http://activehistory.ca/2010/05/should-we-embrace-the-short-url/feed/" rel="self" type="application/rss+xml" />
	<link>http://activehistory.ca/2010/05/should-we-embrace-the-short-url/</link>
	<description>History Matters</description>
	<lastBuildDate>Mon, 21 May 2012 15:10:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: A.J. Rowley</title>
		<link>http://activehistory.ca/2010/05/should-we-embrace-the-short-url/comment-page-1/#comment-4115</link>
		<dc:creator>A.J. Rowley</dc:creator>
		<pubDate>Tue, 11 May 2010 10:33:14 +0000</pubDate>
		<guid isPermaLink="false">http://activehistory.ca/?p=1434#comment-4115</guid>
		<description>Thanks @Michael, wise words.</description>
		<content:encoded><![CDATA[<p>Thanks @Michael, wise words.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Eamon</title>
		<link>http://activehistory.ca/2010/05/should-we-embrace-the-short-url/comment-page-1/#comment-4111</link>
		<dc:creator>Michael Eamon</dc:creator>
		<pubDate>Mon, 10 May 2010 14:09:59 +0000</pubDate>
		<guid isPermaLink="false">http://activehistory.ca/?p=1434#comment-4111</guid>
		<description>A great topic for debate.  As with any citation we should make it as easy as possible for the reader to find the source.    As a former reference archivist I spent an inordinate amount of time trying to decipher for researchers abbreviations made by historians before the Internet Age.  I think trying to find the path of least resistance always bites you in the end.   Mix in stable vs unstable URLs and it becomes an even more difficult situation.  Citing the most complete, stable URL is probably the best practice for now.</description>
		<content:encoded><![CDATA[<p>A great topic for debate.  As with any citation we should make it as easy as possible for the reader to find the source.    As a former reference archivist I spent an inordinate amount of time trying to decipher for researchers abbreviations made by historians before the Internet Age.  I think trying to find the path of least resistance always bites you in the end.   Mix in stable vs unstable URLs and it becomes an even more difficult situation.  Citing the most complete, stable URL is probably the best practice for now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A.J. Rowley</title>
		<link>http://activehistory.ca/2010/05/should-we-embrace-the-short-url/comment-page-1/#comment-4095</link>
		<dc:creator>A.J. Rowley</dc:creator>
		<pubDate>Wed, 05 May 2010 22:28:51 +0000</pubDate>
		<guid isPermaLink="false">http://activehistory.ca/?p=1434#comment-4095</guid>
		<description>@Brenton I agree.

Users need some sort of guarantee that the service is going to stick around before they move to adopt it.  Government could be a means to that end by helping to provide or even fund a dedicated archive either for general use or very specific databases / user groups.

For now, I think there&#039;s some urgency to the matter since short URLs seem poised to become something of a normalized fad.  It may be more difficult in future to  question their use.  All the more reason to &quot;co-opt&quot; them, so to speak.


@Ian Thanks!

I wonder if the US Library of Congress has enough space in their archive to copy the full link and even the page it leads to -- after all, the price of digital storage has fallen significantly in recent years.

On the other hand, bit.ly (and other popular stand-alone services) are likely to be purchased and absorbed into broader platforms (maybe even Twitter itself).  That might raise ownership problems and hinder the LOC&#039;s archival efforts.</description>
		<content:encoded><![CDATA[<p>@Brenton I agree.</p>
<p>Users need some sort of guarantee that the service is going to stick around before they move to adopt it.  Government could be a means to that end by helping to provide or even fund a dedicated archive either for general use or very specific databases / user groups.</p>
<p>For now, I think there&#8217;s some urgency to the matter since short URLs seem poised to become something of a normalized fad.  It may be more difficult in future to  question their use.  All the more reason to &#8220;co-opt&#8221; them, so to speak.</p>
<p>@Ian Thanks!</p>
<p>I wonder if the US Library of Congress has enough space in their archive to copy the full link and even the page it leads to &#8212; after all, the price of digital storage has fallen significantly in recent years.</p>
<p>On the other hand, bit.ly (and other popular stand-alone services) are likely to be purchased and absorbed into broader platforms (maybe even Twitter itself).  That might raise ownership problems and hinder the LOC&#8217;s archival efforts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Milligan</title>
		<link>http://activehistory.ca/2010/05/should-we-embrace-the-short-url/comment-page-1/#comment-4094</link>
		<dc:creator>Ian Milligan</dc:creator>
		<pubDate>Wed, 05 May 2010 19:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://activehistory.ca/?p=1434#comment-4094</guid>
		<description>This is a really fascinating blog post and an interesting, pertinent discussion.

Brenton&#039;s comment made me think of the recent announcement that the American Library of Congress is archiving Twitter tweets - and what a neat source that&#039;ll be for a future historian. Of course, everybody uses URL shortening services for Twitter... and if bit.ly fails, the utility of the archive could be considerably diminished. I guess you&#039;d have to preserve the long URL and hope that you could cross-reference it with the Internet Archive.</description>
		<content:encoded><![CDATA[<p>This is a really fascinating blog post and an interesting, pertinent discussion.</p>
<p>Brenton&#8217;s comment made me think of the recent announcement that the American Library of Congress is archiving Twitter tweets &#8211; and what a neat source that&#8217;ll be for a future historian. Of course, everybody uses URL shortening services for Twitter&#8230; and if bit.ly fails, the utility of the archive could be considerably diminished. I guess you&#8217;d have to preserve the long URL and hope that you could cross-reference it with the Internet Archive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brenton</title>
		<link>http://activehistory.ca/2010/05/should-we-embrace-the-short-url/comment-page-1/#comment-4093</link>
		<dc:creator>Brenton</dc:creator>
		<pubDate>Wed, 05 May 2010 18:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://activehistory.ca/?p=1434#comment-4093</guid>
		<description>One problem with shortening URLs is that the service is not centrally controlled or regulated. If tons of groups started using Tiny URLs&#039;s service, what would happen if the service was discontinued for some reason (company folds, perhaps). I think there&#039;s an argument for a government-regulated body that would guarantee the shortened link.</description>
		<content:encoded><![CDATA[<p>One problem with shortening URLs is that the service is not centrally controlled or regulated. If tons of groups started using Tiny URLs&#8217;s service, what would happen if the service was discontinued for some reason (company folds, perhaps). I think there&#8217;s an argument for a government-regulated body that would guarantee the shortened link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Blog Archive &#187; Now Blogging for ActiveHistory.ca</title>
		<link>http://activehistory.ca/2010/05/should-we-embrace-the-short-url/comment-page-1/#comment-4091</link>
		<dc:creator>&#187; Blog Archive &#187; Now Blogging for ActiveHistory.ca</dc:creator>
		<pubDate>Wed, 05 May 2010 12:35:34 +0000</pubDate>
		<guid isPermaLink="false">http://activehistory.ca/?p=1434#comment-4091</guid>
		<description>[...] first post, for example, explores how short URLs could potentially rein in run-away links in things like course materials, endnotes/footnotes, and finding aides both online and [...]</description>
		<content:encoded><![CDATA[<p>[...] first post, for example, explores how short URLs could potentially rein in run-away links in things like course materials, endnotes/footnotes, and finding aides both online and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A.J. Rowley</title>
		<link>http://activehistory.ca/2010/05/should-we-embrace-the-short-url/comment-page-1/#comment-4090</link>
		<dc:creator>A.J. Rowley</dc:creator>
		<pubDate>Wed, 05 May 2010 12:15:25 +0000</pubDate>
		<guid isPermaLink="false">http://activehistory.ca/?p=1434#comment-4090</guid>
		<description>@Alun Thanks for sharing!  

You know, I suspected there were others out there with similar views on this.  And I had no idea that &lt;em&gt;British Archaeology&lt;/em&gt; was already printing tinyurl.com links.  That&#039;s a bit disconcerting.  I wonder why they didn&#039;t just launch their own service... (not very archaeological of them!).</description>
		<content:encoded><![CDATA[<p>@Alun Thanks for sharing!  </p>
<p>You know, I suspected there were others out there with similar views on this.  And I had no idea that <em>British Archaeology</em> was already printing tinyurl.com links.  That&#8217;s a bit disconcerting.  I wonder why they didn&#8217;t just launch their own service&#8230; (not very archaeological of them!).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alun</title>
		<link>http://activehistory.ca/2010/05/should-we-embrace-the-short-url/comment-page-1/#comment-4088</link>
		<dc:creator>Alun</dc:creator>
		<pubDate>Wed, 05 May 2010 11:56:14 +0000</pubDate>
		<guid isPermaLink="false">http://activehistory.ca/?p=1434#comment-4088</guid>
		<description>You might be interested in the archaeologist Tom Goskar&#039;s thoughts on the subject: http://tom.goskar.com/2009/04/16/why-im-creating-my-own-url-shortening-service/

Is this a service that scholarly societies could usefully provide?</description>
		<content:encoded><![CDATA[<p>You might be interested in the archaeologist Tom Goskar&#8217;s thoughts on the subject: <a href="http://tom.goskar.com/2009/04/16/why-im-creating-my-own-url-shortening-service/" rel="nofollow">http://tom.goskar.com/2009/04/16/why-im-creating-my-own-url-shortening-service/</a></p>
<p>Is this a service that scholarly societies could usefully provide?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

