<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Lee Iverson</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/" />
    <link rel="self" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/weblog/atom.xml" />
   <id>tag:www.ece.ubc.ca,2006:/~leei/weblog/1</id>
    <link rel="service.post" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1" title="Lee Iverson" />
    <updated>2006-03-29T19:34:49Z</updated>
    <subtitle>Dr. Lee Iverson is an Assistant Professor in the Department of Electrical and Computer Engineering at the University of British Columbia. He is in the Software Engineering Program, the HCT Lab and heads the UCL Lab. This site is for sharing his thoughts and observations with his collaborators and any others who might be interested.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2</generator>
 
<entry>
    <title>Thomas Vander Wal on Folksonomy</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2006/03/thomas_vander_wal_on_folksonom.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=56" title="Thomas Vander Wal on Folksonomy" />
    <id>tag:www.ece.ubc.ca,2006:/~leei/weblog//1.56</id>
    
    <published>2006-03-29T18:43:44Z</published>
    <updated>2006-03-29T19:34:49Z</updated>
    
    <summary>In Online Information Folksonomy Presentation Posted :: Personal InfoCloud Thomas Vander Wal writes about tagging, folksonomy and taxonomy and rightly points out that they are not necessarily opposed or incompatible concepts. I&apos;d go further than him though to suggest that...</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Ontology" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[<p>In <a title="Online Information Folksonomy Presentation Posted :: Personal InfoCloud" href="http://www.personalinfocloud.com/2006/01/online_informat.html">Online Information Folksonomy Presentation Posted :: Personal InfoCloud</a> Thomas Vander Wal writes about tagging, folksonomy and taxonomy and rightly points out that they are not necessarily opposed or incompatible concepts.  I'd go further than him though to suggest that they are, in fact, quite compatible.</p>]]>
        <![CDATA[<p>So let's start out by reiterating Vander Wal's terminology.  He seems to be making the distinction between "tagging" and "folksonomy" by pointing out that tagging has been going on for a long time and that folksonomy is new, moreover that old style tagging "provided no certainty as to the vocabulary being correct in the perspective of all trying to use it."  The distinction he seems to be making is between "creator-driven keywords" (tags) and something new represented by del.icio.us.

<p>The something new is the triple: person, tag name, object.  Anyone with a database background and a few minutes on del.icio.us realizes that what is going on is that there's a table for identities, one for tags and one for URLs and in the middle is an association table.
<img alt="tag-descr.gif" align="right" src="http://www.ece.ubc.ca/~leei/weblog/images/tag-descr.gif" width="464" height="320" />
The significant thing about this architecture (and the thing that seems to get Thomas to say "folksonomy") is the "tags" association table at the middle of this and its consequences. For one, whenever an individual tags an object, an entry in the association table is made for every one of the "tags" used (e.g. if user "leei" tags "<a href="http://www.ece.ubc.ca/~leei">http://www.ece.ubc.ca/~leei</a>" with the words "me" and "leei", we'll get two entries of the form (leei,"me",URL) and (leei,"leei",URL) in the "tags" table. A user can add as many tags as he wants to, but all of them will be referenced to his user table entry.  Similarly, an entry will be added to the "user_urls" table with the user's title and description of every URL he uses.

<p>One of the primary consequences of the relational model and the database backend here is that queries can be made from any side of this association:
<ul>
<li>From a user, I can see all tag names and urls;</li>
<li>From a URL, I can see all users and tag_names;</li>
<li>From a tag name, I can see all users and URLs;</li>
<li>From a user and tag name, I can see all URLS;</li>
<li>From a user and URL, I can see all tag names; and</li>
<li>From a tag name and URL, I can see all users.</li>
</ul>
And, of course, I can obtain counts of the size of all of these sets and use those statistics to generate things like tag clouds etc.  It is this <i>attributed tagging</i> in a public space that Thomas Vander Wal seems to prefer the term "folksonomy" for (hopefully, he'll correct me if I've got this wrong).

<p>Now, that said, what is the relationship between this and taxonomy.  Here I disagree with Vander Wal.   Taxonomy is a way of managing an organizational system as a hierarchy (and he rightly points out that many taxonomies may exist within the same domain), whereas the tagging or "folksonomy" models now in place seem to completely ignore the issue of hierarchy.  This is clearly a deliberate choice (see <a href="http://www.shirky.com/writings/ontology_overrated.html">Clay Shirky</a> for example) but is it a necessary one? I'd suggest that it is not.  The fundamental nature of folksonomy is a personal organization of objects of interest using simple markers (tag names).  I do not believe that this necessarily implies that there can be no expressed relations between those markers.  Some of the markers may express categories in the user's mind and there may be relationships between those categories (e.g. sub- or super-category relations or mutual exclusion).  As with all technologies, it is important to distinguish between the manifestations of a technology and its fundamental nature.

<p>So, I agree that taxonomy and folksonomy are not incompatible.  In fact, I believe that taxonomy can be a part of folksonomy if the user finds it useful. The oppositions here are clear, they are between authoritative or prescribed vocabularies and personal or socially constructed vocabularies and between structured, categorical organization systems and flat or unstructured organizational systems. The table below shows these two axes with representative examples of the kinds identified by these properties.  Of course, these axes are by no means binary, but more or less continuous.  For example, one can be completely structured as in closed database schemas or semi-structured as in various RDF models that respect certain categorical relationships but leave definitions open and relationships largely unspecified such as <a href="http://dublincore.org">Dublin Core</a>.

<table border="1" align="center">
<caption>Axes of organizational vocabularies. </caption>
<tr> <td></td> <th>Structured</th> <th>Unstructured</th> </tr>
<tr> <th>Authoritative</th> <td> Domain Taxonomy</td> <td> Glossary</td></tr>
<tr> <th>Personal/Opportunistic</th> <td>Hierarchical Filesystem</td> <td> Folksonomy </td></tr>
</table>

<p>Of course, the above is just a starting point, a sketch.  This is really much more multi-dimensional than that.  There is the personal/social axis, the private/public axis, the authoritative/opportunistic axis,  and a few others. I think this is ripe for exploitation.  I just don't think personal, tag-driven, opportunistic  organizational systems are necessarily unstructured.]]>
    </content>
</entry>
<entry>
    <title></title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2006/03/post.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=54" title="" />
    <id>tag:www.ece.ubc.ca,2006:/~leei/weblog//1.54</id>
    
    <published>2006-03-17T00:09:27Z</published>
    <updated>2006-03-17T00:09:27Z</updated>
    
    <summary>In Lowering Barriers to Participation, Bradley Horowitz points out how tagging lowers the barriers to participation and thus allows ordinary users to create useful metadata. I think he&apos;s right on here. Especially on a system such as del.icio.us, the ease...</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Musings" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[<p>In <a title="Elatable | Bradley Horowitz ï¿½ Lowering Barriers to Participation" href="http://www.elatable.com/blog/?p=11">Lowering Barriers to Participation</a>, <a href="">Bradley Horowitz</a> points out how tagging lowers the barriers to participation and thus allows ordinary users to create useful metadata. I think he's right on here.  Especially on a system such as <a href="http://del.icio.us">del.icio.us</a>, the ease of use and triviality of creating tags allows pretty much anyone to create "personally useful" metadata.  As an aide memoire, that is exactly what it should allow.</p>

<p>Is it authoritative?  Is it useful for others? That's for someone else to decide.  It's easy and useful for me, and if there are natural concordances with others, I can take advantage of those.  That should be enough, and is.]]>
        
    </content>
</entry>
<entry>
    <title>My Favourite Cafe: The Beanery</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2006/03/my_favourite_cafe_the_beanery_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=53" title="My Favourite Cafe: The Beanery" />
    <id>tag:www.ece.ubc.ca,2006:/~leei/weblog//1.53</id>
    
    <published>2006-03-16T06:01:21Z</published>
    <updated>2006-03-16T07:04:24Z</updated>
    
    <summary>My favourite little cafe is a place called &quot;The Beanery&quot; on the UBC campus in the middle of the Fairview residences. Sonny and Sonya, who run the place, are two wonderful friendly hosts, the atmosphere is great, and UBC wireless...</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Musings" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[<p>My favourite little cafe is a place called "The Beanery" on the <a href="http://www.ubc.ca">UBC</a> campus in the middle of the Fairview residences.  Sonny and Sonya, who run the place, are two wonderful friendly hosts, the atmosphere is great, and <a href="http://www.ubc.ca">UBC</a> wireless is usually available.  It's my second office.</p>

<p>It's located inside the Fairview residences.  The entrance to the residences is at the intersection of Fairview Ave. and Western Parkway.  There's a sign there for the Beanery, but it is actually all the way in the back of the residence complex, near Pearkes Lane.

<div class="GMapEZ GSmallMapControl" style="width: 480px; height: 480px;">
  <a href="http://maps.google.com/?ll=49.263506,-123.239028&spn=0.007856,0.012596">
    EXTENT
  </a>
  <a href="http://maps.google.com/?ll=49.26373,-123.23935&spn=0.007856,0.012596">
  </a>
</div>]]>
        
    </content>
</entry>
<entry>
    <title>How to Write a Proposal</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2006/02/how_to_write_a_proposal.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=51" title="How to Write a Proposal" />
    <id>tag:www.ece.ubc.ca,2006:/~leei/weblog//1.51</id>
    
    <published>2006-02-25T00:01:42Z</published>
    <updated>2006-02-25T00:02:22Z</updated>
    
    <summary>I&apos;ve been asked repeatedly by students and others for advice on writing a proposal document. As with all documents, I believe that the best way to go about this is to concentrate on two things: the audience and the goal...</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Essays" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[<p>I've been asked repeatedly by students and others for advice on writing a proposal document.  As with all documents, I believe that the best way to go about this is to concentrate on two things: the audience and the goal of the document. In general, a proposal is written to someone who has the ability to allow you to do something (i.e. money, resources, supervision) and your goal is to convince them to enable or allow you to do it.  With that in mind, we can come up with a few guidelines.</p>]]>
        <![CDATA[<p>In essence, you are trying to provide a good answer to a simple question (from the point of view of your audience): should I commit my resources to helping this person accomplish their goal? Your goal is to get them to answer "Yes!"</p>

<p>One approach that I really like is to concentrate on the <a href="http://www.destinationkm.com/articles/default.asp?ArticleID=397">NABC</a>'s of your problem: the <b>need</b>, <b>approach</b>, <b>benefits</b> and <b>competition</b>.  If you can present an argument that accomplishes the goals described by these principles, then you're well on your way to convincing your audience.</p>

<p>Well, clearly you start out with some problem you are planning to solve - that has to frame everything. So So , how do these NABC's relate to the problem, and how do they answer the question for your audience?  Well, I find it useful to again, think about what questions you are answering for each topic.
<ul>
<li><b>Need:</b> Why do I need to solve the problem?  Who has the problem? How important is it to them? How much do they need it?
</li>
<li><b>Approach:</b>How am I going to solve the problem? How does this approach relate to the need and the people who need it? Why will this approach solve it?
</li>
<li><b>Benefits:</b>What will the benefits of this specific approach be to the users? How will it change what they are doing? How will the specifics of the approach affect these users? What are possible downsides and how can they be mitigated?
</li>
<li><b>Competition:</b>Who else has tried to solve the problem?  How did they do it and how successful were they?  How does your solution compare to theirs in terms of benefits and drawbacks?
</li>
</ul>
In general, if you get this far, then you are well on your way to making a case.  If you can't answer all of these questions, then you have more work to do.
Now, that said, there are definite differences in style and specifics with different audiences.</p>

<p>For academic research the order is usually a bit different: NCAB.  You need to further justify the need and make the transition to your approach by doing a review of the work that has already been done that: makes the case for your need, either directly informs or relates to your approach, and provides a baseline to compare yourself against.</p>

<p>For business proposals (and the NABC is sometimes referred to as a mini-business plan), the reason you end with a description of the competition is that that also helps to answer the money questions.  How big is the market for this?  What impact will it have on an organization in terms of cost-savings, market expansion, or increased productivity?  How is the competition selling themselves and how does that relate?</p>

<p>Now, as to writing style and length, that's up to you.  You have to make the case.  But you should be able to make it at some level in one page, and also be able to produce a more detailed proposal in 20-30 pages.  In the ECE department, we limit our Ph.D. proposals to a maximum of 30 pages. If you're having trouble with actually writing the case up, I recommend an approach that I call "Structured Argumentation" that I'll write about soon (and link back to here).</p>]]>
    </content>
</entry>
<entry>
    <title>Trying out Elgg</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2006/02/trying_out_elgg.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=50" title="Trying out Elgg" />
    <id>tag:www.ece.ubc.ca,2006:/~leei/weblog//1.50</id>
    
    <published>2006-02-24T22:46:35Z</published>
    <updated>2006-02-25T18:33:02Z</updated>
    
    <summary>Lee Iverson :: Blog is my new blog on http://elgg.net, an ePortfolio system. I&apos;m using it for my CSCW course EECE 519. I chose it because of the combination of blogging, tagging, selective sharing, and community definition and maintenance. I...</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Weblogs" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[<p><a title="Lee Iverson :: Blog" href="http://elgg.net/leei/weblog/">Lee Iverson :: Blog</a> is my new blog on <a href="http://elgg.net">http://elgg.net</a>, an ePortfolio system.  I'm using it for my CSCW course <a href="http://www.ece.ubc.ca/~leei/519">EECE 519</a>. I chose it because of the combination of blogging, tagging, selective sharing, and community definition and maintenance.  I also have a student studying information sharing behaviours in a community of Elgg users.  Let you know how I like it.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Tagging and Attribution</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2006/02/tagging_and_attribution.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=49" title="Tagging and Attribution" />
    <id>tag:www.ece.ubc.ca,2006:/~leei/weblog//1.49</id>
    
    <published>2006-02-06T19:32:25Z</published>
    <updated>2006-02-23T23:42:42Z</updated>
    
    <summary>A simple, but important point about tagging. If a social tag is unattributed, then it is next to useless. Think of &quot;I tag Obj with tag&quot; as an assertion that Obj &quot;means&quot; tag to me (whatever tag means to me)....</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Ontology" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[A simple, but important point about tagging.  If a social tag is unattributed, then it is next to useless. Think of "I tag <i>Obj</i> with <i>tag</i>" as an assertion that <i>Obj</i> "means" <i>tag</i> to me (whatever <i>tag</i> means to me). If this is done in a social environment, then without attribution and some ability to assess the meaning or trustworthiness of my tags (from your own perspective), the information that <i>Obj</i> has been tagged is problematic.]]>
        <![CDATA[At <a href="http://tagcamp.org">TagCamp</a>, I gave a presentation on "Why tagging works" in which I suggested some reasons for tagging's success where previous attempts at social information organization have largely failed.  Now, someone added a tag facility to the Wiki for the meeting, a good idea. But it was unattributed, and showed up in the sidebar when you visited a page.  Sometime shortly after the meeting someone tagged my personal page with the word "blabbermouth".

<p>Now, I don't mind a negative tag, but this was anonymous and thus kind of cowardly.  And as far as I could tell it was inaccurate.   A "blabbermouth" is someone who talks out of turn or reveals information they shouldn't.  I don't do that.  I may be a "bore" or a "loudmouth" (I happen to think best with my mouth open), but never a "blabbermouth".

<p>But I also found cheated out of the opportunity to engage in a conversation with the tagger.  What were they bothered by?  Did I offend you or prevent you from speaking?  I'm left hanging (and branded) without any possibility of correcting an unintended offence...

<p>Now, not all anonymous tagging is of this character, but it certainly does leave me hanging.]]>
    </content>
</entry>
<entry>
    <title>Del.icio.us vs Google</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2006/02/delicious_vs_google.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=48" title="Del.icio.us vs Google" />
    <id>tag:www.ece.ubc.ca,2006:/~leei/weblog//1.48</id>
    
    <published>2006-02-06T19:06:50Z</published>
    <updated>2006-02-23T23:43:05Z</updated>
    
    <summary>In A social analysis of tagging, Rashmi Sinha makes a few interesting points about the transition from solitary to social with the tagging experience. I tend to agree with this, but I would like to point out a few things...</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Ontology" />
            <category term="Weblogs" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[In <a title="A social analysis of tagging" href="http://www.rashmisinha.com/archives/06_01/social-tagging.html">A social analysis of tagging</a>, Rashmi Sinha makes a few interesting points about the transition from solitary to social with the tagging experience. I tend to agree with this, but I would like to point out a few things I think deserve more consideration.]]>
        <![CDATA[One of the main reasons that social tagging systems work is that they emulate Google's page rank algorithm in an open, browseable way.  What do I mean by this, well bear with me.

<p>One there are a hundred or thousand responses to a search engine query the primary distinguishing feature of one search engine from another (besides speed) is the ordering of the responses. The main reason Google worked so much better than their competitors initially was the <a href="http://www.google.com/technology/">PageRank</a> algorithm.  What Sergey Brin and Larry Page figured out was that how many people are talking about you and what they are saying is more important than what you say about yourself. In essence, all the search engines that preceded Google did textual and structural analysis <i>of the web page itself</i> and created match values with key words on the page in order to calculate the strength of match with each query keyword.  Brin and Page figured out that a link is primarily used as an attestation of authority and that the description of a page near its link location is more precise and significant than the page content itself. In other words it uses the "wisdom of crowds" to select pages that best match key words.

<p>Tagging (in the <a href="http://del.icio.us">del.icio.us</i> style) has exactly this property.  The primary differences are 1) that tags are open and attributed, and 2) that tagging is easier and more dynamic than building a web page.  In essence tag systems mirror the pagerank structure of Google's system, but make the internal structures browsable and viewable directly. The consequence of this, and the primary strength of tagging systems, is that tagged structures are more trustable and harder to spoof or spam than search engines.

<p>That said, they need to get better. I need to be able to express who I trust and especially who I don't. I need to express what information I trust from these sources and again what I don't (I may completely agree with a person's perspective on technology but abhor their politics). There's so much more that can and should be done with these systems...

<p>Technorati Tags: <a href="http://technorati.com/tag/del.icio.us" rel="tag">del.icio.us</a>, <a href="http://technorati.com/tag/tagging" rel="tag">tagging</a>, <a href="http://technorati.com/tag/google" rel="tag">google</a>.]]>
    </content>
</entry>
<entry>
    <title>del.icio.us and Recommended Tags</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2005/11/delicious_and_recommended_tags.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=47" title="del.icio.us and Recommended Tags" />
    <id>tag:www.ece.ubc.ca,2005:/~leei/weblog//1.47</id>
    
    <published>2005-11-02T22:55:04Z</published>
    <updated>2006-02-23T23:43:34Z</updated>
    
    <summary>On the weekend at TagCamp, I made a few points about the possibilities of del.icio.us and Flock for bootstrapping the development of rich, personal ontological models. In that framework, I made some unfounded criticisms of current del.icio.us practice that I...</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Ontology" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[On the weekend at <a href="http://tagcamp.org">TagCamp</a>, I made a few points about the possibilities of <a href="http://del.icio.us">del.icio.us</a> and <a href="http://flock.com/">Flock</a> for bootstrapping the development of rich, personal ontological models.  In that framework, I made some unfounded criticisms of current del.icio.us practice that I should correct publically.]]>
        <![CDATA[<p>One of my main hopes for this stuff is that we are on our way towards allowing individuals to create <i>contextualized</i> information structures and then create systems that can mine these in social environments for community formation, <i>grounded</i> community ontological modelling, etc. In this context, as I see it, it is fundamentally important to allow and encourage individualized and potentially idiosyncratic tagging (or categorization) behaviour.

<p>In that light, I was criticizing del.icio.us' "Recommended Tags" feature for its seeming push towards harmonization or homogenization of tagging behaviour.  I was concerned that "recommending" tags based on how others had tagged an item would actively encourage decontextualization of the tagging activity.

<p>Well, I was wrong.  The "Recommended Tags" are derived from an intersection of tags others have used and your own tagset.  In other words, you are encouraged to reuse your own tags when those have already been used to identify the resource by others.  This seems to be much more about simply <i>recognizing</i> a natural concordance of your tagging choices with those of others.  In other words, exactly the kind of "mining" of the social environment that I advocate.  Mea culpa.  Sorry for badmouthing you inappropriately Josh.

<p>
<i>Technorati Tags</i>:
<a href="http://technorati.com/tag/folksonomy" rel="tag">folksonomy</a>,
<a href="http://technorati.com/tag/tagcamp" rel="tag">tagcamp</a>,
<a href="http://technorati.com/tag/del.icio.us" rel="tag">del.icio.us</a>,
<a href="http://technorati.com/tag/tagging" rel="tag">tagging</a>.]]>
    </content>
</entry>
<entry>
    <title>Yahoo 360 and Lucasfilms&apos; Habitat</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2005/04/yahoo_360_and_lucasfilms_habit.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=46" title="Yahoo 360 and Lucasfilms' Habitat" />
    <id>tag:www.ece.ubc.ca,2005:/~leei/weblog//1.46</id>
    
    <published>2005-04-05T22:15:14Z</published>
    <updated>2006-02-24T21:20:33Z</updated>
    
    <summary>Reading Yahoo! 360 through &quot;The Lessons of Lucasfilm&apos;s Habitat&quot;. A great little article with another great little article in a link. Well worth the read....</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Musings" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[<a title="Reading Yahoo! 360 through "The Lessons of Lucasfilm's Habitat"" href="http://www.oreillynet.com/pub/wlg/6771">Reading Yahoo! 360 through "The Lessons of Lucasfilm's Habitat"</a>.  A great little article with another great little article in a link.  Well worth the read.]]>
        
    </content>
</entry>
<entry>
    <title>Intermediation, REST &amp; Bookmarking</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2005/04/intermediation_rest_bookmarkin.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=45" title="Intermediation, REST &amp; Bookmarking" />
    <id>tag:www.ece.ubc.ca,2005:/~leei/weblog//1.45</id>
    
    <published>2005-04-01T18:54:11Z</published>
    <updated>2006-02-23T23:35:04Z</updated>
    
    <summary>In The architecture of intermediation, Jon Udell suggests that there might not have been the need to &quot;clone&quot; del.icio.us (see de.lirio.us) in order to be able to experiment with the structure and services. He suggests instead the with the proper...</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Musings" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[In <a title="Jon Udell: The architecture of intermediation" href="http://weblog.infoworld.com/udell/2005/03/30.html#a1205">The architecture of intermediation</a>,
<a href="http://weblog.infoworld.com/udell/">Jon Udell</a> suggests that there might not have been the need to "clone" <a href="http://del.icio.us">del.icio.us</a> (see <a href="http://de.lirio.us/">de.lirio.us</a>) in order to be able to experiment with the structure and services.  He suggests instead the with the proper "intermediation" in terms of proxies etc.  there should be ways to do things with del.icio.us that the designers haven't anticipated.]]>
        <![CDATA[<p>In a certain sense, I agree. The RESTful architecture of del.icio.us should make it really easy to do some interesting things with smart proxies and other kinds of services.  In essence, the real hope an promise of the RESTful web services model (over SOA-like models) is the potential ease of aggregating services and really doing web services "right" with little cost.

<p>The danger with this approach is the dissolution of services into a morass of intermediated  systems.  In essence, if the really useful information and services are all managed by these intermediated services then the benefits of "mining" the information are lost.  In essence, a big part of the benefit of what I'm calling "object-out interaction" is potentially lost if the object reference information isn't somehow centralized.  By that I mean, the opportunity to discover like-minded people and communities from the objects out to the people.  I'm writing a paper on this at the moment, so more on this in the future.

<p>Now, the "somehow" up there was also deliberate.  Another nice thing about RESTful systems is the ways in which notification and update can be managed.  It should be possible to have these intermediating services notify the central system in various ways to maintain the advantages of centralization.  It is not clear how easy that is to do at the moment.

<p>Finally, I do see a significant problem in this whole approach.  Because of the need to mix representation (read data models) with presentation (read user-interface) in these RESTful services, it can be really quite difficult to provide a completely different UI as a front-end via such intermediated web services.  Ideally, the real strengths of del.icio.us, which are in its data models, would be more or less directly accessible in a way that would allow for wide experimentation in user interface and service aggregation, without comprising the integrity of the original service.  Hmmm...  Definitely more on this later.]]>
    </content>
</entry>
<entry>
    <title>What is a Facet?</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2005/03/what_is_a_facet.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=43" title="What is a Facet?" />
    <id>tag:www.ece.ubc.ca,2005:/~leei/weblog//1.43</id>
    
    <published>2005-03-18T19:38:52Z</published>
    <updated>2006-02-23T23:41:43Z</updated>
    
    <summary>Nils Soren Peterson in Semantic Tagging, an extension to a Group&apos;s Thesaurus asks &quot;what is a facet?&quot; in the context of an experiment being by Haiko Hebig with his del.icio.us tags....</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Ontology" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[<a href="http://pbj.ctlt.wsu.edu/nils_peterson/">Nils Soren Peterson</a> in <a title="Semantic Tagging, an extension to a Group's Thesaurus" href="http://pbj.ctlt.wsu.edu/nils_peterson/archive/0001/01/01/1498.aspx">Semantic Tagging, an extension to a Group's Thesaurus</a> asks "what is a facet?" in the context of an experiment being by Haiko Hebig with his <a href="http://del.icio.us/haikohebig">del.icio.us</a> tags.]]>
        <![CDATA[<p>He speculates that facets are like groups, but misses the point a bit.  Facets are essentially like typed links, not groups.  The best way to understand it is to think about the relation that a tag represents.  Most tags have the meaning "resource X is about Y", where X is the tagged item and Y is the tag.  In that sense we have an implicit "about:" or "subject:" facet.  But we could have "kind:" facets representing the class of object or even facets tracking other metadata for an item "date-published:" or "site:".

<p>In its simplest form a facet thus an aspect of the resource in question.  For more, it is worth checking out the <a href="http://www.iawiki.net/FacetedClassification">IAWiki: FacetedClassification</a>.]]>
    </content>
</entry>
<entry>
    <title>Controlled Vocabularies Cut Off the Long Tail</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2005/03/controlled_vocabularies_cut_of.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=42" title="Controlled Vocabularies Cut Off the Long Tail" />
    <id>tag:www.ece.ubc.ca,2005:/~leei/weblog//1.42</id>
    
    <published>2005-03-17T19:12:51Z</published>
    <updated>2006-03-16T19:49:37Z</updated>
    
    <summary>Bokardo ï¿½ Controlled Vocabularies Cut Off the Long Tail makes a couple of important observations relating folksonomy to controlled vocabularies (e.g. domain ontologies). In particular he contrasts: Discovery vs. Finding, or what I would term browsing vs. search. Tracking vs....</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Ontology" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[<a title="Bokardo ï¿½ Controlled Vocabularies Cut Off the Long Tail" href="http://bokardo.com/archives/controlled_vocabularies_long_tail/">Bokardo ï¿½ Controlled Vocabularies Cut Off the Long Tail</a> makes a couple of important observations relating folksonomy to controlled vocabularies (e.g. domain ontologies).  In particular he contrasts:
<ul>
<li>Discovery vs. Finding, or what I would term browsing vs. search.</li>
<li>Tracking vs. Prediction, although he doesn't quite abstract it in those terms.</li>
</ul>
In general, I agree with much of what he's pointed out, but I think he misses a few important aspects of the problem or generalizations of these observations.]]>
        <![CDATA[<p>In particular, there's a big issue around contextualized organization and decontextualized (or broadly contextualized) organization, and it's largely an issue of goals.  Folksonomy approaches start from the point-of-view that you give people simple tools for organizing the information that they use or have used and this may or may not be useful for others.  The controlled vocabulary approach assumes that a particular community has a common way of organizing the world and the vocabulary reflects that common scheme.  Folksonomies attempt to support categorization in an individual's own context while controlled vocabularies assume a community context and assume that will be useful for all of its members (and possibly non-members).

<p>The failures of the controlled vocabulary approach largely lie, in my mind, in this decontextualization of knowledge.  I often look back on Jonathan Grudin's "Work vs. Benefit" analysis in assessing whether or not community technologies have a chance of actually working, and in the case of categorization, it is often more work for an individual to conform to a community vocabulary than to simply build and use their own, especially if the tools for doing so are extremely simple (e.g. <a href="http://del.icio.us">del.icio.us</a> or <a href="http://flickr.com">Flickr</a>).  Moreover the benefit (to the individual) accrued from using the controlled vocabulary is minimal.  This is one of the two reasons that tagging is succeeding.

<p>The other is simply the collapse of the horribly poor metaphor for organizing digital information that is the "Folder".  And in this respect, it is not that it is an incapable metaphor or hard to grasp, just that it doesn't scale.  It doesn't scale to a large number of items, and it doesn't scale to mutiple users.  And unfortunately, I believe that the pure tagging approach to folksonomy development will fail for the same basic reason -- scaling.]]>
    </content>
</entry>
<entry>
    <title>Do Tags Work?</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2005/03/do_tags_work.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=41" title="Do Tags Work?" />
    <id>tag:www.ece.ubc.ca,2005:/~leei/weblog//1.41</id>
    
    <published>2005-03-07T22:02:22Z</published>
    <updated>2006-02-24T21:19:25Z</updated>
    
    <summary>In ongoing ï¿½ Do Tags Work?, Tim Bray asks whether tagging systems such as Technorati or del.icio.us work? He suggested a simple piece of research that might find out......</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Ontology" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[In <a title="ongoing ï¿½ Do Tags Work?" href="http://www.tbray.org/ongoing/When/200x/2005/03/04/DoTagsWork">ongoing ï¿½ Do Tags Work?</a>, Tim Bray asks whether tagging systems such as Technorati or del.icio.us work?  He suggested a simple piece of research that might find out...]]>
        <![CDATA[<p>I think there's something a little more going on here though.  It's not "do tags work?" it's more of a "how far can they go?"  In a simple sense it seems that keywords (i.e. author supplied tags) vs. tagging (i.e. community supplied tags) is really something that Google already proved.  What the community thinks of you is just a better way to assess how relevant or important you're information is than what you think of yourself.  And if you don't think that's what's behind Google's PageRank then go back and read the original papers again.

<p>The real question (and this should be the questin with every proposed information management tool) is "how does it scale?"  What happens when I go from 100 tags to 10,000?  What happens when we have synonymy?  How about conflicts?  The "<a href="http://www.google.com/search?hl=en&lr=&safe=off&c2coff=1&client=mozilla&rls=org.mozilla%3Aen-US%3Aunofficial&q=miserable+failure&btnG=Search">miserable failure</a>" manipulation even points out how something as global as Google's approach can be exploited.

<p>My answer?  I suspect that the way out of this is a combination of organization of tags (probably semi-automatic rather than fully automatic) and some real models of testimony (i.e. I believe X to be true because Y asserts that X is true).  In other words information management paired with social networking.

<p>How could this play out then?  First organiztion. Well, frankly I believe that RDF and ontological modelling are the right foundation for building and describing conceptual organization (and that is what tags are really about, named concepts).  The real question is how to make the formation of these conceptual models accessible to real users and useful for finding and organizing information.  I say that we should start from the bottom up: let me model my own knowledge and information resources efficiently and practically (i.e. find something to replace folders, desktops and simple taxonomies) and then find ways to coordinate these organizational systems with collaborators and friends and ultimately the communities we participate in.

<p>The next, and possibly more important thing though, is to take testimony seriously.  For example, I might want to know what the most popular sites tagged with "<a href="http://del.icio.us/popular/baseball+statistics">baseball statistics</a>" or <a href="http://del.icio.us/tag/baseball+statistics">the most recent</a>.  Strangely, del.icio.us actually screws this up, since what I'm really asking for is a different ordering and not a filter.  But, frankly, I'm much more interested in the opinions of a few people who I trust to suggest the best sources of information (e.g. Bill James).  So, what I <i>really</i> want is both...  I want to tell del.icio.us that "these are the people whose opinions (and bookmarks) I trust" and therefore give their tags greater weight in presenting things to me.  I may want to be slightly transitive on this too, giving some, but less, weight to those they trust.  And of course the opposite is useful too (e.g. "I don't trust doofus' tags") Del.icio.us does use this a teeny touch with the "ignore" feature, but that's a really broad broom and it prevents you from seeing stuff instead of merely downgrading it.

<p>Now of course, testimony is contextual too.  Frankly, it is very likely that I will agree with someone's technical recommendations and have a big problem with their politics, so that should be a consideration too...  It is easy to see how far this could go and not really too difficult to do either.  Anyone game?]]>
    </content>
</entry>
<entry>
    <title>Seb&apos;s Social Software Challenge</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2005/03/sebs_social_software_challenge.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=40" title="Seb's Social Software Challenge" />
    <id>tag:www.ece.ubc.ca,2005:/~leei/weblog//1.40</id>
    
    <published>2005-03-03T07:18:30Z</published>
    <updated>2006-02-24T21:37:44Z</updated>
    
    <summary>Seb&apos;s Open Research describes a &quot;Programming Challenge&quot; to count links in deli.cio.us topics. There&apos;s some hope there, but I think we need to go in a different direction....</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Ontology" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[<a title="Seb's Open Research" href="http://radio.weblogs.com/0110772/2005/01/18.html#a1686">Seb's Open Research</a> describes a "Programming Challenge" to count links in <a href="http://deli.cio.us">deli.cio.us</a> topics. There's some hope there, but I think we need to go in a different direction.]]>
        <![CDATA[<p>The problem with simple tagging systems like deli.cio.us and <a href="http://flickr.com">FlickR</a> are that they just don't scale well.  In essence, it's easy to organize things if you don't have that much to organize.  It's when you get a lot of stuff that life gets tough.  Think folders when you have 50,000 emails in your archive or a 500GB hard drive.  What worked a while ago doesn't any more.

<p>I'd suggest two things:
<ul>
<li>The addition of "testimony", a social component, to the tagging.  In essence, there are people whose tags I trust and those I don't.  Moreover, those I trust I probably only trust on some topics and not on others (e.g. I can agree with someone's software development practices without agreeing with their politics or religion).</li>
<li>Some way of organizing tags. It does seem bizarre to use the term "folksonomy" without having any of the characteristics of "taxonomy" (i.e. sub-categories).  The addition of very lightweight tagging with a model of the tags (and some ways of making it consensual) would just kill.</a>
</ul>]]>
    </content>
</entry>
<entry>
    <title>Hunter S Thompson and Qualitative Research</title>
    <link rel="alternate" type="text/html" href="http://www.ece.ubc.ca/~leei/weblog/2005/02/hunter_s_thompson_and_qualitat.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.ece.ubc.ca/~leei/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=39" title="Hunter S Thompson and Qualitative Research" />
    <id>tag:www.ece.ubc.ca,2005:/~leei/weblog//1.39</id>
    
    <published>2005-02-26T16:10:15Z</published>
    <updated>2006-02-23T22:56:38Z</updated>
    
    <summary>ongoing · HST is a good start on some Hunter S. Thompson reflections. I must admit, I have read little of his stuff and my clearest image of him is Doonesbury&apos;s Uncle Duke, but a few things that I heard...</summary>
    <author>
        <name>Lee Iverson</name>
        <uri>http://www.ece.ubc.ca/~leei/weblog</uri>
    </author>
            <category term="Musings" />
    
    <content type="html" xml:lang="en" xml:base="http://www.ece.ubc.ca/~leei/weblog/">
        <![CDATA[<a title="ongoing · HST" href="http://www.tbray.org/ongoing/When/200x/2005/02/21/HST">ongoing · HST</a> is a good start on some Hunter S. Thompson reflections.  I must admit, I have read little of his stuff and my clearest image of him is Doonesbury's Uncle Duke, but a few things that I heard people saying about him ran true, and I made an observation in my CSCW class on Tuesday that I'd like to share.]]>
        <![CDATA[<p>Someone being interviewed on CBC radio suggested that HST's greatest contribution to journalism was his very personal stance. He took the point-of-view that the things he was writing about were too important to try to adopt a dispassionate, "just-the-facts ma'am" reportage (i.e. a traditional journalistic style).  Instead he loudly reacted to events, told everyone who could read what his own opinions and biases were, and told people what he thought about what his subjects.  In essence, he personalized his writing in order to try to create an opportunity to personalize their own reactions and thoughts to his subjects.

<p>So, how is this related to qualitative research?  Well, traditional scientific epistemology is about adopting a depersonalized stance, a dependence on replicable evidence and theory and models based only on such evidence.  The kind of knowledge being developed is decontextualized and generalized and dispassionate (think traditional journalism).  Qualitative research takes the general stance that we also need contextualized and personalized knowledge (especially when we are studying people or the relationships between people and the world) and we need methods and standards for ensuring that such knowledge is useful. One of the foundations of qualitative methods is exposing the researcher biases, the context in which the evidence was gathered, and the methods used to achieve whatever generalization was possible.  The key is that a reader of a qualitative study, rather than just trusting the results on their face and using them as needed, has enough information about the context used to gather the evidence and make the claims that he/she can assess for themselves.  I'd suggest that these are exactly the characteristics that made HST's approach to reportage so different and engaging.

<p>So what lessons to be learned?  Does on need to get drunk to do qualitative research? Is a huge, all-encompassing sense of self and mission necessary?  No, just a relentless, self-critical honesty with yourself and your readers.  A complete openness in terms of the background and suppositions in your approach.  And finally, a sense that it is the reader of a qualitative study who has to be able to decide for themselves whether or not your work is relevant or useful to them.  Anything that you do in your approach to the work or description of it that inhibits this ability is reducing its potential impact and usefulness.

<p>May Hunter rest peacefully now that he's been delivered from his demons and sense of responsibility.]]>
    </content>
</entry>

</feed> 


