Tags: xri, technorati

Kevin Burton and a few other folks make a good point in talking about problems with the new Technorati tagging system. 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.

Tags: xri, technorati

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).

OK, so now I get to try to put in my first technorati tag(s). Lets see if this works.

I proposed a radically simplified XRI resolution mechanism that relies only on HTTP, leveraging caching for efficiency, and providing a clear path for using a REST architecture to use XRIs. In other words, this resolution is RESTful, and could be used in a RESTful application.

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.

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 announcement.