<?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: Is the web sticky enough?</title>
	<atom:link href="http://masonlee.org/2009/08/21/is-the-web-sticky-enough/feed/" rel="self" type="application/rss+xml" />
	<link>http://masonlee.org/2009/08/21/is-the-web-sticky-enough/</link>
	<description>home page and weblog</description>
	<lastBuildDate>Sat, 14 Jan 2012 18:34:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Mason Lee</title>
		<link>http://masonlee.org/2009/08/21/is-the-web-sticky-enough/#comment-245</link>
		<dc:creator><![CDATA[Mason Lee]]></dc:creator>
		<pubDate>Mon, 23 Nov 2009 23:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://masonlee.wordpress.com/?p=91#comment-245</guid>
		<description><![CDATA[The Tag URI scheme (RFC4151) looks like a nice method for minting URIs that are globally unique across time.  They aren&#039;t network resolvable by nature, though.
http://www.ietf.org/rfc/rfc4151.txt]]></description>
		<content:encoded><![CDATA[<p>The Tag URI scheme (RFC4151) looks like a nice method for minting URIs that are globally unique across time.  They aren&#8217;t network resolvable by nature, though.<br />
<a href="http://www.ietf.org/rfc/rfc4151.txt" rel="nofollow">http://www.ietf.org/rfc/rfc4151.txt</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mason Lee</title>
		<link>http://masonlee.org/2009/08/21/is-the-web-sticky-enough/#comment-226</link>
		<dc:creator><![CDATA[Mason Lee]]></dc:creator>
		<pubDate>Wed, 07 Oct 2009 00:56:16 +0000</pubDate>
		<guid isPermaLink="false">http://masonlee.wordpress.com/?p=91#comment-226</guid>
		<description><![CDATA[Just found this briefing paper on the same topic:
http://www.digitalpreservationeurope.eu/publications/briefs/persistent_identifiers.pdf]]></description>
		<content:encoded><![CDATA[<p>Just found this briefing paper on the same topic:<br />
<a href="http://www.digitalpreservationeurope.eu/publications/briefs/persistent_identifiers.pdf" rel="nofollow">http://www.digitalpreservationeurope.eu/publications/briefs/persistent_identifiers.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mason Lee</title>
		<link>http://masonlee.org/2009/08/21/is-the-web-sticky-enough/#comment-204</link>
		<dc:creator><![CDATA[Mason Lee]]></dc:creator>
		<pubDate>Tue, 25 Aug 2009 09:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://masonlee.wordpress.com/?p=91#comment-204</guid>
		<description><![CDATA[Textbook examples of Atom feed elements use GUIDs as IDs.  The nice thing about these is you don&#039;t need a central authority to generate them, they are just probably unique.  Here is a scheme for generating them and for representing them as URIs:  

http://www.ietf.org/rfc/rfc4122.txt

RFC 4122 uses 128 bit IDs.  Using 256-bits would get you almost enough IDs to assign one to every atom in the universe (Est. 10^80).  (Did God use 256-bit IDs and run out of space?)

How resource IDs fit in with versioning is an interesting question...]]></description>
		<content:encoded><![CDATA[<p>Textbook examples of Atom feed elements use GUIDs as IDs.  The nice thing about these is you don&#8217;t need a central authority to generate them, they are just probably unique.  Here is a scheme for generating them and for representing them as URIs:  </p>
<p><a href="http://www.ietf.org/rfc/rfc4122.txt" rel="nofollow">http://www.ietf.org/rfc/rfc4122.txt</a></p>
<p>RFC 4122 uses 128 bit IDs.  Using 256-bits would get you almost enough IDs to assign one to every atom in the universe (Est. 10^80).  (Did God use 256-bit IDs and run out of space?)</p>
<p>How resource IDs fit in with versioning is an interesting question&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mason Lee</title>
		<link>http://masonlee.org/2009/08/21/is-the-web-sticky-enough/#comment-203</link>
		<dc:creator><![CDATA[Mason Lee]]></dc:creator>
		<pubDate>Tue, 25 Aug 2009 09:05:20 +0000</pubDate>
		<guid isPermaLink="false">http://masonlee.wordpress.com/?p=91#comment-203</guid>
		<description><![CDATA[@plaggypig Thanks.  I agree, the re-assignability of memorable names is important for some systems.  An audit trail maintained at the DNS level wouldn&#039;t be able to tell you if path-named resources were reassigned.  Can you explain more your thinking?]]></description>
		<content:encoded><![CDATA[<p>@plaggypig Thanks.  I agree, the re-assignability of memorable names is important for some systems.  An audit trail maintained at the DNS level wouldn&#8217;t be able to tell you if path-named resources were reassigned.  Can you explain more your thinking?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: @plaggypig</title>
		<link>http://masonlee.org/2009/08/21/is-the-web-sticky-enough/#comment-202</link>
		<dc:creator><![CDATA[@plaggypig]]></dc:creator>
		<pubDate>Sat, 22 Aug 2009 04:50:02 +0000</pubDate>
		<guid isPermaLink="false">http://masonlee.wordpress.com/?p=91#comment-202</guid>
		<description><![CDATA[Individuals and businesses need to trade names that fit their particular interests and markets. A namespace that didn&#039;t cater for this demand would be a pretty unattractive one.

I dare say if identifiers weren&#039;t reassignable then the process of registration would probably have to be qualified with checks that applicants are eligible to own any particular name, thereby raising the cost and reducing participation.

But anyway, couldn&#039;t the problem be mitigated with an audit trail? The governing authority (TLD registry) could log a timestamp whenever a domain is transferred between registrants, and provide a list of these historical changes (via whois).

I&#039;m loving your blog Mason, this is a great discussion.]]></description>
		<content:encoded><![CDATA[<p>Individuals and businesses need to trade names that fit their particular interests and markets. A namespace that didn&#8217;t cater for this demand would be a pretty unattractive one.</p>
<p>I dare say if identifiers weren&#8217;t reassignable then the process of registration would probably have to be qualified with checks that applicants are eligible to own any particular name, thereby raising the cost and reducing participation.</p>
<p>But anyway, couldn&#8217;t the problem be mitigated with an audit trail? The governing authority (TLD registry) could log a timestamp whenever a domain is transferred between registrants, and provide a list of these historical changes (via whois).</p>
<p>I&#8217;m loving your blog Mason, this is a great discussion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

