<?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 - Technology</title>
 <link>http://uncorked.wachob.com/taxonomy/term/3/0</link>
 <description></description>
 <language>en</language>
<item>
 <title>Barcamp</title>
 <link>http://uncorked.wachob.com/node/43</link>
 <description>&lt;p&gt;Tags: &lt;a rel="tag" href="http://technorati.com/tag/barcamp"&gt;Barcamp&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Last Sunday, I had the opportunity to attend &lt;a href="http://barcamp.org"&gt;Barcamp&lt;/a&gt;, a great technology grassroots get-together. Kudos to all the folks who brought it together - the best 6 hours I've spent geeking out in a long time... &lt;/p&gt;
</description>
 <pubDate>Tue, 30 Aug 2005 01:03:58 -0400</pubDate>
</item>
<item>
 <title>My new IRC Channel - #GabeW</title>
 <link>http://uncorked.wachob.com/node/41</link>
 <description>&lt;p&gt;In blatant imitation of &lt;a href="irc://irc.freenode.net/#joiito"&gt;#joiito&lt;/a&gt;, I hereby announce my own IRC channel, &lt;a href="irc://irc.freenode.net/#GabeW"&gt;#GabeW&lt;/a&gt;. This is on the freenode network (irc.freenode.net).&lt;/p&gt;
&lt;p&gt;If you don't know what IRC is, or how to connect (try clicking on the link above first - it may just work depending on software you have installed), go see the &lt;a href="http://joiwiki.ito.com/joiwiki/index.cgi?ircchannel&amp;#038;login=user79204"&gt;#joiito intro to IRC&lt;/a&gt; wiki page. &lt;/p&gt;
</description>
 <pubDate>Wed, 10 Aug 2005 02:16:17 -0400</pubDate>
</item>
<item>
 <title>California SB 682 - The Identity Information Protection Act of 2005</title>
 <link>http://uncorked.wachob.com/node/40</link>
 <description>&lt;p&gt;My state senator, &lt;a href="http://democrats.sen.ca.gov/senator/simitian/"&gt; Joe Simitian&lt;/a&gt; has authored a &lt;a href="http://www.leginfo.ca.gov/cgi-bin/postquery?bill_number=sb_682&amp;#038;sess=CUR&amp;#038;house=B&amp;#038;author=simitian"&gt;bill&lt;/a&gt; which is intended to keep the state or any local government entity from using or issuing identity cards with contactless communication facilities that don't meet strict security standards. It also outlaws completely the use of contactless data communications for certain types of identity documents (e.g. drivers licenses) for a period of 3 years.&lt;/p&gt;
&lt;p&gt;The bill has the support of EFF, ACLU, and a number of other organizations. It also has my support. Please visit EFF's &lt;a href="https://secure.eff.org/site/Advocacy?id=125"&gt;Action Alert&lt;/a&gt; for SB 682. And if you are a fellow consituent of Joe Simitian, please do &lt;a href="http://democrats.sen.ca.gov/senator/simitian/email.htm"&gt;contact&lt;/a&gt; his office and express your appreciation! &lt;/p&gt;
</description>
 <pubDate>Sat, 06 Aug 2005 01:14:00 -0400</pubDate>
</item>
<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>Upgraded to Drupal 4.4</title>
 <link>http://uncorked.wachob.com/node/24</link>
 <description>&lt;p&gt;Well, I upgraded to Drupal 4.4 &lt;/p&gt;
&lt;p&gt;I don't see any new features, maybe there'll be some speed or bug fixes... I'll have to get some modules and play around with them. &lt;/p&gt;
&lt;p&gt;Time for me to go to sleep. &lt;/p&gt;
</description>
 <pubDate>Mon, 26 Jul 2004 02:11:53 -0400</pubDate>
</item>
<item>
 <title>ATOM feeds, fission and fusion</title>
 <link>http://uncorked.wachob.com/node/18</link>
 <description>&lt;p&gt;&lt;a href="http://diveintomark.org/archives/2003/08/05/atom02"&gt;ATOM&lt;/a&gt;  is the specification for syndicated content feeds.&lt;/p&gt;
&lt;p&gt;One could say that creating a feed is the "splitting" of the original content from the blog, hence &lt;b&gt;FISSION&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;Putting the feeds together in an aggregator is therefore &lt;b&gt;FUSION&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;Hows that for slick wordsmithing.&lt;/p&gt;
</description>
 <pubDate>Mon, 06 Oct 2003 00:34:04 -0400</pubDate>
</item>
<item>
 <title>Dean forms Internet Advisory Network</title>
 <link>http://uncorked.wachob.com/node/17</link>
 <description>&lt;p&gt;Wow!&lt;/p&gt;
&lt;p&gt;The Dean campaign &lt;a href="http://www.deanforamerica.com/site/News2?page=NewsArticle&amp;#038;id=9432&amp;#038;JServSessionIdr001=pb1lrky7p1.app195a&amp;#038;security=1&amp;#038;news_iv_ctrl=1301"&gt;announced&lt;/a&gt; the formation of an advisory panel for policy issues surrounding the Internet. And the list of members is impressive: Joi Ito, Larry Lessig, Dewayne Hendricks to name a few. &lt;/p&gt;
&lt;p&gt;Its about time these issues got addressed seriously at the presidential level. I'm waiting for other campaigns now (of course, they'll have to pick from the rest of the experts - Dean's got many of the best already!). &lt;/p&gt;
</description>
 <pubDate>Mon, 29 Sep 2003 17:57:23 -0400</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>HTTP: Its good for a lot more than you may think</title>
 <link>http://uncorked.wachob.com/node/14</link>
 <description>&lt;p&gt;Did you know that RFC 2616 (HTTP/1.1) defines the HTTP protocol to operate on &lt;a href="http://www.zvon.org/tmRFC/RFC2616/Output/chapter3.html#sub2"&gt;any type of URI&lt;/a&gt;? This opens a lot of possiblities how different identifier schemes can be used.
&lt;p&gt;
In my role as co-chair of the &lt;a href="http://www.oasis-open.org/committees/xri"&gt;XRI&lt;/a&gt; effort, I do a lot of research into existing specifications. I want to reuse them. Specifically, I want to reuse HTTP since its probably the most widely implemented specification out there (except maybe TCP/IP).&lt;br /&gt;
&lt;P&gt;&lt;br /&gt;
&lt;b&gt;The Realization&lt;/b&gt;
&lt;p&gt;
According to my reading of RFC 2616, the on-the-wire protocol can use any URI. For example, this is legal according to 2616:&lt;/p&gt;
</description>
 <pubDate>Wed, 27 Aug 2003 19:17:10 -0400</pubDate>
</item>
<item>
 <title>RDF as universal cross-application context</title>
 <link>http://uncorked.wachob.com/node/12</link>
 <description>&lt;p&gt;In a modern GUI (lets take Windows), you should be able to right click on any window and be able to grab some rdf from any app (like an mp3 player and the rdf would be what song it is playing)and be able to paste that rdf into another app. What that "other app" does is independent of where you got the RDF - though of course, presumably some of that RDF that is recognized by the receiving application. Unrecognized RDF assertions would just be ignored. &lt;/p&gt;
&lt;p&gt;And then maybe even the apps can let you configure how to map application-specific state into RDF (and back to application-specific state or functionality). &lt;/p&gt;
</description>
 <pubDate>Mon, 25 Aug 2003 21:36:50 -0400</pubDate>
</item>
<item>
 <title>A good simple XML-Schema validating XML Editor</title>
 <link>http://uncorked.wachob.com/node/10</link>
 <description>&lt;p&gt;I don't think I have unreasonable requirements. I want an XML editor that does validation as I edit, that validates against XML Schema, and validates documents with elements and attributes from multiple namespaces. It should run on Windows. &lt;/p&gt;
&lt;p&gt;I'm doing this for producing a document with SOAP 1.2 messages and various extension headers. I've had all sorts of problems with what used to be my favorite tool - XMLSpy. I just can't get it to reliably validate documents across mutiple schema.&lt;/p&gt;
&lt;p&gt;Today, I found &lt;a href="http://architag.com/xray/"&gt;XRay2&lt;/a&gt; from Architag. A free download (with registration). I'm still trying it out, but it does just what I need in an intuitive way. Load all the schema in the validator, and it builds a catalog from the declarations in the schema, and you can then build an XML document using all the namespaces defined in that catalog. Simple, intuitive, and just what I need. &lt;/p&gt;
</description>
 <pubDate>Mon, 18 Aug 2003 16:16:30 -0400</pubDate>
</item>
<item>
 <title>Using WikiWords to make topics more findable</title>
 <link>http://uncorked.wachob.com/node/7</link>
 <description>&lt;p&gt;Kevin Marks suggests using &lt;a href="http://prosua.blogspot.com/2002_08_01_prosua_archive.html#85386541"&gt;BlogTags&lt;/a&gt; to make topics "emerge" from the wild wild-web. The idea is neat. Simply insert a WikiWord (that is unlikely to get confused with a normal word, because it is at least two words smushed together) into your blog entry, or web content. &lt;/p&gt;
&lt;p&gt;Then, when others want to find links on this topic, they use the same WikiWord in their favorite search engine. The search will have both high recall and high precision! Great idea! &lt;/p&gt;
</description>
 <pubDate>Fri, 08 Aug 2003 19:47:24 -0400</pubDate>
</item>
<item>
 <title>New Blog</title>
 <link>http://uncorked.wachob.com/node/1</link>
 <description>&lt;p&gt;I've decided that this blogging thing is something I should really try out. &lt;/p&gt;
&lt;p&gt;Since I've decided to actively support the &lt;a href="http://www.deanforamerica.com"&gt;Dean 2004&lt;/a&gt; campaign, and specifically the &lt;a href="http://www.hack4dean.org"&gt;Hack4Dean&lt;/a&gt; effort, which uses &lt;a href="http://www.drupal.org"&gt;Drupal&lt;/a&gt;, I'm trying out this Drupal thing. &lt;/p&gt;
&lt;p&gt;We'll see how it goes!&lt;/p&gt;
</description>
 <pubDate>Thu, 31 Jul 2003 03:14:37 -0400</pubDate>
</item>
</channel>
</rss>
