<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="0.92" xml:base="http://uncorked.wachob.com">
<channel>
 <title>Gabe Wachob Uncorked - XRI</title>
 <link>http://uncorked.wachob.com/taxonomy/term/2/0</link>
 <description>The Extensible Resource Identifier</description>
 <language>en</language>
<item>
 <title>Link Technorati Tags Using XRIs instead of Technorati URL?</title>
 <link>http://uncorked.wachob.com/node/38</link>
 <description>&lt;p&gt;Tags: &lt;a href="http://technorati.com/tag/xri" rel="tag"&gt;xri&lt;/a&gt;, &lt;a href="http://technorati.com/tag/technorati" rel="tag"&gt;technorati&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Kevin Burton and a few other folks make a good point in talking about &lt;a href="http://www.peerfear.org/rss/permalink/2005/01/18/TechnoratiTagAPIIsBroken/"&gt;problems with the new Technorati tagging system&lt;/a&gt;. One thing that bugs me in particular is that it's basically a technorati-only solution that is a metadata standard based on a site-specific URL pattern. This seems brittle and more than a little hackish. I mean, great start, don't stop, but lets come up with a better solution.&lt;/p&gt;
</description>
 <pubDate>Tue, 30 Aug 2005 01:10:15 -0400</pubDate>
</item>
<item>
 <title>Technorati Tags and XRI</title>
 <link>http://uncorked.wachob.com/node/34</link>
 <description>&lt;p&gt;Tags: &lt;a href="http://technorati.com/tag/xri" rel="tag"&gt;xri&lt;/a&gt;, &lt;a href="http://technorati.com/tag/technorati" rel="tag"&gt;technorati&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;Seems like using XRIs with Technorati tags might be an interesting fit, especially with the "+" XRI namespace reserved for "concepts". For example, xri://+love xri://+war xri://+vanilla - things that aren't really meant to be "resolved" but are either used "as-is" (ie to refer to the thing everyone commonly knows the identifier to be - ie "love", "war", or "vanilla"), or used in the context of something else xri://=GabeWachob*(+father).&lt;/p&gt;
&lt;p&gt;OK, so now I get to try to put in my first technorati tag(s). Lets see if this works. &lt;/p&gt;
</description>
 <pubDate>Sun, 23 Jan 2005 17:17:11 -0500</pubDate>
</item>
<item>
 <title>Radically simplified XRI resolution</title>
 <link>http://uncorked.wachob.com/node/15</link>
 <description>&lt;p&gt;I proposed a &lt;a href="http://lists.oasis-open.org/archives/xri/200309/msg00000.html"&gt;radically simplified XRI resolution mechanism&lt;/a&gt; that relies only on HTTP, leveraging caching for efficiency, and providing a clear path for using a &lt;a href="http://internet.conveyor.com/RESTwiki/moin.cgi/FrontPage"&gt;REST&lt;/a&gt; architecture to use XRIs. In other words, this resolution is RESTful, and could be used in a RESTful application.&lt;/p&gt;
&lt;p&gt;I've gotten fairly positive feedback about it so far and I'm hoping its now within the comprehension of mere mortals. While I was really jazzed about DNS and especially DDDS, its become clear to me that the newness of using DNS for generic identifier resolution is proving to be an impediment to any serious review of the XRI resolution document. &lt;/p&gt;
</description>
 <pubDate>Sun, 07 Sep 2003 03:24:04 -0400</pubDate>
</item>
<item>
 <title>XRI TC Looking for Input on Draft Specification</title>
 <link>http://uncorked.wachob.com/node/3</link>
 <description>&lt;p&gt;As, co-chair of the XRI TC, I'm really glad to announce that we've finally reached a point with the Extensible Resource Identifier specification that we want public input. See the &lt;a href="http://lists.oasis-open.org/archives/xri/200307/msg00060.html"&gt;announcement&lt;/a&gt;.&lt;/p&gt;
</description>
 <pubDate>Thu, 31 Jul 2003 12:48:24 -0400</pubDate>
</item>
</channel>
</rss>

