<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="/transform"?>
<!--<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">-->
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
  <head>
    <title>Dynamic Faceted Taxonomies for Organizing Web Resources</title>
    <base href="http://doriantaylor.com/"/>
    <link rel="meta" type="application/rdf+xml" title="FOAF" href="person/dorian-taylor?type=application/rdf+xml"/>
    <link rel="alternate index" title="This Site" href="this-site"/>
    <link rel="alternate bookmark" title="Elsewhere" href="elsewhere"/>
    <link rel="up" rev="section" href="policy/uris-resources-and-representations" title="URIs, Resources and Representations" />
    <link rel="next" rev="prev" href="policy/distinguishing-persistence-from-publication" title="Distinguishing Persistence from Publication" />
    <link rel="prev" rev="next" href="policy/the-uri-naming-conundrum" title="The URI Naming Conundrum" />
  </head>
  <body>
    <p>To a <abbr title="World-Wide Web">Web</abbr> server, at least initially, a request-<a href="lexicon/uniform-resource-identifier" title="Uniform Resource Identifier">URI</a> &#x2014; the concatenation of the <a rel="external" href="http://tools.ietf.org/html/rfc3986#section-3.3" title="Path &#x2014; Uniform Resource Identifier (URI): Generic Syntax">path</a> and <a rel="external" href="http://tools.ietf.org/html/rfc3986#section-3.4" title="Query &#x2014; Uniform Resource Identifier (URI): Generic Syntax">query</a> components &#x2014; is treated as an <a href="lexicon/semantic-opacity" title="Semantic Opacity">opaque</a> string. What to <em>do</em> with a requested <acronym title="Uniform Resource Identifier">URI</acronym>, however, must be defined by an implementation-specific resolution mechanism. By far the most common of these is a direct mapping to a region on the server's <a href="lexicon/file" title="File">file</a> system.</p>
    <p>As the <abbr title="World-Wide Web">Web</abbr> matures, however, we discover that a fixed hierarchical taxonomy, such as that offered by and modeled after conventional file systems, suffers many shortcomings for organizing information:</p>
    <ul>
      <li>Hierarchies require copious curatorial effort to design and maintain;</li>
      <li>Each category of resources must <em>completely contain</em> sub-categories;</li>
      <li>The addition of new resources can elicit a restructuring of the taxonomy, as resources can often <em>straddle</em> categories in unforeseen ways;</li>
      <li>To <em>not</em> restructure at such a point introduces a <q>taxonomical rot</q> which has a subtle and detrimental effect on an organization's information resources;</li>
      <li>There exist various cognitive and cultural biases that inhibit individuals from correctly inferring the membership of resources to categories; and</li>
      <li>On the <abbr title="World-Wide Web">Web</abbr>, where <a href="policy/the-uri-naming-conundrum" title="The URI Naming Conundrum">it pays to keep resources perpetually reachable</a>, the expense of a restructuring can be exacerbated by more effort required to maintain the original paths, or more so by doing nothing.</li>
    </ul>
    <p>It is likely because of this that significant attention within the information architecture community has turned toward non-hierarchical, or <em>faceted</em> taxonomies. Moreover, the flexibility of computers and the <abbr title="World-Wide Web">Web</abbr> affords a great deal of automated assistance in this arena. Therefore:</p>
    <blockquote><a href="projects/dynamic-faceted-taxonomy" title="">Define a mechanism</a> for producing and maintaining a <strong>dynamically-generated</strong>, <strong>self-arranging</strong>, <strong>faceted</strong> taxonomy for organizing on-line resources, that <em>grows</em> and <em>adapts</em> as an organization appends to its knowledge base.</blockquote>
  </body>
</html>
