<?xml version="1.0" encoding="UTF-8"?>
<essay xml:lang="en" version="pto" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:gal="http://norman.walsh.name/rdf/gallery#">
<info>
    
    
    
    
    
    
    
    
    
<title>Tagback: Joining the Folksonomy Fray</title><biblioid class="uri">http://norman.walsh.name/2005/02/20/tagback</biblioid>
<volumenum>8</volumenum>
<issuenum>26</issuenum>
<pubdate>2005-02-20T12:47:20-05:00</pubdate>
<date>$Date: 2005-09-11 10:27:02 -0400 (Sun, 11 Sep 2005) $</date>
<author>
      <personname>
<firstname>Norman</firstname>
	<surname>Walsh</surname>
</personname>
    </author>
<copyright>
      <year>2005</year>
      <holder>Norman Walsh</holder>
    </copyright>
<abstract>
<para>I've added provisions for folksonomy tags and plan to
adopt them as a replacement for threads.</para>
</abstract>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#RDF"/>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#SelfReference"/>
</info>

<para xml:id="p1">The web has been buzzing with discussion about
ontologies recently, and especially about
<link xlink:href="http://en.wikipedia.org/wiki/Folksonomy">folksonomies</link>.
Since the
very beginning
of this blog, I've been
<link xlink:href="/2003/05/14/how">keeping track of metadata</link>
about each entry,
including how each post fits into my own personal taxonomy.</para>

<para xml:id="p2">A personal taxonomy
(<abbrev>aka<alt>Also Known As</alt></abbrev> folksonomy) is all well
and good. You can use it, for example, to see the
<link xlink:href="/topics">topics index</link> on this site. But
<emphasis>real</emphasis> value is only going to come from it if other
people start to use it. Realistically, the chances of other folks
using my ontology for their posts is remote at best.</para>

<para xml:id="p3">But with
<link xlink:href="http://www.technorati.com/">Technorati</link> now
building tag-based indexes of blogs,
<link xlink:href="http://www.flickr.com/">Flickr</link> photographs, and
<link xlink:href="http://del.icio.us/">del.icio.us</link> and
<link xlink:href="http://www.furl.net/">furl</link> bookmarks, the
possibility of hooking into a shared ontology seems much greater.
</para>

<para xml:id="p4">To that end, I've reworked the taxonomy of these pages
to support tags, per the Technorati
<link xlink:href="http://developers.technorati.com/wiki/RelTag">specification</link>. I haven't removed my own taxonomy, just provided an
additional mechanism for public tagging.
</para>

<para xml:id="p5">Following <personname>
      <firstname>Shelley</firstname>
<surname>Powers</surname>
    </personname>’
<link xlink:href="http://weblog.burningbird.net/archives/2005/02/07/introducing-tag-back/">lead</link>, I'm also using adding unique “tagback” tags for
specific threads of discussion. This will (very quickly, I think) replace
the poorly maintained
<link xlink:href="/2003/06/26/threads">threading</link> system that
I have been using.</para>

<para xml:id="p6">The biggest problem with the threading system is that
only I can update the threads. With the folksonomy tags, anyone can
add their own essay to the thread or use 
<link xlink:href="http://del.icio.us/">del.icio.us</link> or
<link xlink:href="http://www.furl.net/">furl</link> to add someone else's.
Only time will tell how well this system stands up to use and abuse.
</para>

<section xml:id="semweb">
<title>On The Benefits of the Semantic Web</title>

<para xml:id="p7">As regular readers may have already guessed, I've
abandoned my Palm device in favor of my new
<link xlink:href="/2005/01/11/sidekick">Sidekick</link>. The hardest
part of this transition (beyond some of the irksome shortcomings of
the device) is rebuilding all of the server-side tools that I used to
use to
<link xlink:href="http://nwalsh.com/docs/articles/extreme2002/">manage
my personal information</link>.</para>

<para xml:id="p8">One of the aspects I'm struggling with is the whole
RDF thing. I'm strongly tempted to just use Plain Old XML. Frankly,
it'd be faster and somewhat easier to do it that way.</para>

<para xml:id="p9">At least <emphasis>at first</emphasis>. It's much
less clear that <acronym>POX<alt>Plain Old XML</alt></acronym> would
be the best <emphasis>long term</emphasis> answer for this particular
application.</para>

<para xml:id="p10">That point was driven home dramatically when I set out
to update this site to use tags. I accomplished the entire task by
adding a few new bits of metadata in the
<link xlink:href="/knows/taxonomy.n3">taxonomy</link> and the
<link xlink:href="/knows/topics.n3">topics</link> files, by adding
<emphasis>a single rule</emphasis> to the set of inferences used by
<command>cwm</command> to build the metadata for this site, and by updating
<emphasis>one template</emphasis> in the stylesheet that builds the HTML.</para>

<para xml:id="p11">It's hard to imagine that it would have been just
that easy if I'd only used <acronym>POX<alt>Plain Old XML</alt></acronym>
and custom scripts to build this site. RDF's ability to aggregate disparate
sources of information and to be extended by inference shows promise
once again.</para>

<para xml:id="p12">(In case you go looking for that rule, you won't
find it anymore. After I had it all working, I decided to do it a little
bit differently, changing the way topics and tags are processed so that
they're generated dynamically by the server instead of being baked into
the HTML. That required moving things around a little bit and made the
inference unnecessary. But the RDF is still used to build the
runtime <link xlink:href="/index.tax">taxonomy</link> file and it's still
just a simple matter of adding a few new RDF statements to build new
tags and new taxonomies.)</para>

</section>
</essay>

