<?xml version="1.0"?>
<?xml-stylesheet href="/transform" type="text/xsl"?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:bibo="http://purl.org/ontology/bibo/" xmlns:bs="http://purl.org/ontology/bibo/status/" xmlns:ci="https://vocab.methodandstructure.com/content-inventory#" xmlns:dct="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xhv="http://www.w3.org/1999/xhtml/vocab#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" lang="en" prefix="bibo: http://purl.org/ontology/bibo/ bs: http://purl.org/ontology/bibo/status/ ci: https://vocab.methodandstructure.com/content-inventory# dct: http://purl.org/dc/terms/ foaf: http://xmlns.com/foaf/0.1/ rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# xhv: http://www.w3.org/1999/xhtml/vocab# xsd: http://www.w3.org/2001/XMLSchema#" vocab="http://www.w3.org/1999/xhtml/vocab#" xml:lang="en">
  <head>
    <title property="dct:title">The URI Naming Conundrum</title>
    <base href="https://doriantaylor.com/policy/the-uri-naming-conundrum"/>
    <link href="../document-stats#EJyxZbkR_jJgODjxaaZWmL" rev="ci:document"/>
    <link href="../elsewhere" rel="alternate bookmark" title="Elsewhere"/>
    <link href="../this-site" rel="alternate index" title="This Site"/>
    <link href="http://purl.org/ontology/bibo/status/published" rel="bibo:status"/>
    <link href="" rel="ci:canonical" title="The URI Naming Conundrum"/>
    <link href="../lexicon/#EzqXIsriaILFcWjXdS7FbI" rel="dct:audience" title="Software Developer"/>
    <link href="../person/dorian-taylor#me" rel="dct:creator" title="Dorian Taylor"/>
    <link href="dynamic-faceted-taxonomies-for-organizing-web-resources" rel="dct:references next" title="Dynamic Faceted Taxonomies for Organizing Web Resources"/>
    <link href="distinguishing-resources-from-files" rel="dct:references prev" title="Distinguishing Resources from Files"/>
    <link href="uris-resources-and-representations" rel="dct:references up" title="URIs, Resources and Representations"/>
    <link href="../lexicon/#EnewYu-MeZVXNc97q_-jAI" rel="dct:subject" title="Web Development"/>
    <link href="../person/dorian-taylor" rel="meta" title="Who I Am"/>
    <link about="../" href="../3f36c30c-6096-454a-8a22-c062100ae41f" rel="alternate" type="application/atom+xml"/>
    <link about="../" href="../f07f5044-01bc-472d-9079-9b07771b731c" rel="alternate" type="application/atom+xml"/>
    <link about="../" href="../this-site" rel="alternate"/>
    <link about="../" href="../elsewhere" rel="alternate"/>
    <link about="../" href="../e341ca62-0387-4cea-b69a-cdabc7656871" rel="alternate" type="application/atom+xml"/>
    <link about="../verso/" href="../3f36c30c-6096-454a-8a22-c062100ae41f" rel="alternate" type="application/atom+xml"/>
    <link about="../verso/" href="../this-site" rel="alternate"/>
    <link about="../verso/" href="../elsewhere" rel="alternate"/>
    <meta content="the-uri-naming-conundrum" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="Making the case for a mechanism for preserving URI history to track renames and deletions." name="description" property="dct:abstract"/>
    <meta content="2008-09-01T04:29:32+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="the-uri-naming-conundrum" property="dct:identifier"/>
    <meta content="2008-09-02T13:58:53+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2008-09-15T19:58:52+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2008-09-15T21:22:59+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2008-09-15T21:28:15+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2008-09-16T07:49:31+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2008-09-16T07:50:01+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2008-09-16T08:11:07+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2008-09-20T03:23:49+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2008-10-09T02:02:01+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-03-04T00:43:00+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2022-05-31T04:18:52+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2022-05-31T15:10:50+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta about="../person/dorian-taylor#me" content="Dorian Taylor" name="author" property="foaf:name"/>
    <meta content="summary" name="twitter:card"/>
    <meta content="@doriantaylor" name="twitter:site"/>
    <meta content="The URI Naming Conundrum" name="twitter:title"/>
    <meta content="Making the case for a mechanism for preserving URI history to track renames and deletions." name="twitter:description"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="../colophon" rev="dct:references" typeof="bibo:Note">
              <span property="dct:title">Colophon</span>
            </a>
          </li>
          <li>
            <a href="../defining-feeds" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">Defining Feeds</span>
            </a>
          </li>
          <li>
            <a href="distinguishing-resources-from-files" rev="dct:references" typeof="bibo:Report">
              <span property="dct:title">Distinguishing Resources from Files</span>
            </a>
          </li>
          <li>
            <a href="dynamic-faceted-taxonomies-for-organizing-web-resources" rev="dct:references" typeof="bibo:Report">
              <span property="dct:title">Dynamic Faceted Taxonomies for Organizing Web Resources</span>
            </a>
          </li>
          <li>
            <a href="uris-resources-and-representations" rev="dct:references" typeof="bibo:Report">
              <span property="dct:title">URIs, Resources and Representations</span>
            </a>
          </li>
          <li>
            <a href="../working-titles-get-random-cryptonyms" rev="dct:references" typeof="bibo:Article">
              <span property="dct:title">Working Titles get Random Cryptonyms</span>
            </a>
          </li>
          <li>
            <a href="../document-stats#EJyxZbkR_jJgODjxaaZWmL" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:272c596e-447f-48c9-b80e-0e3c5a6995a6</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="E0IgkTcKaN_ZEm5AJfEQ_K" typeof="bibo:Report">
    <p><a href="../lexicon/file" title="File" rel="dct:references">Files</a> are probably the most widely-recognized metaphor for persisting digital information: an opaque container with <em>whatever</em> inside, to which an arbitrary label is attached. The <a href="../lexicon/uniform-resource-identifier" title="Uniform Resource Identifier" rel="dct:references">URI</a>, taking cues from the naming schemes of hierarchical file systems, extends this metaphor &#x2014; with all its benefits and shortcomings &#x2014; to the <abbr title="World-Wide Web">Web</abbr>.</p>
    <p>The first problem in this space is that <a href="http://www.useit.com/papers/filedeath.html" title="Death of File Systems &#x2014; Jakob Nielsen" rel="dct:references">people are <em>really</em> bad at naming things</a>, a condition to which anyone with an <samp>Untitled-1</samp> on their system can attest. Moreover, a computer's latent threat of discarding your hard work unless you choose a name <em>right now</em> does little to inspire creativity in this arena.</p>
    <p>This problem is exacerbated by a second: you have <span class="parenthesis" title="For the armchair attorneys out there, this is notwithstanding legal action, but try to argue how effective that is anyway.">no control over who or what links to you</span>. Once you mint a <acronym title="Uniform Resource Identifier">URI</acronym>, advertise its existence and <span class="parenthesis" title="nit-pickers: i mean an external request.">reply to a request</span> for it, that's it: it's <q>out there</q> for good. Of course, <a href="http://www.w3.org/Provider/Style/URI" title="Cool URIs don't change." rel="dct:references">the courteous thing to do</a> is to <a href="http://www.w3.org/TR/cooluris/" title="Cool URIs for the Semantic Web" rel="dct:references">keep your <acronym title="Uniform Resource Identifier">URI</acronym>s the same</a> &#x2014; forever. This promise isn't so easy to keep when you can rename or delete resources on a whim.</p>
    <aside role="note" id="E90iw0lfaaD3_QmY6u9O3K">This lack of control over inbound links is <a href="http://www.cs.brown.edu/memex/ACM_HypertextTestbed/papers/64.html" title="ACM Computing Surveys: The Unfinished Revolution and Xanadu" rel="dct:references">one of the central criticisms of the <abbr title="World-Wide Web">Web</abbr></a> held by Professor <a href="http://xanadu.com/" title="Project Xanadu&#xAE;" rel="dct:references">Ted Nelson</a>, the progenitor of <a href="http://en.wikipedia.org/wiki/Hypertext" title="Hypertext &#x2014; Wikipedia" rel="dct:references">hypertext</a>. His alternative, in essence, is to <span class="parenthesis" title="or fragments thereof">tether documents together</span> with permanent, bidirectional links that enforce citation, copyright and compensation for the author. It is also worth noting that implementing this model would almost certainly require a common carrier to control these links &#x2014; a fact which <a href="http://www.wired.com/wired/archive/3.06/xanadu.html" title="The Curse of Xanadu &#x2014; Wired" rel="dct:references">essentially describes</a> Nelson's original business plan.</aside>
    <p>However, our problem goes beyond mere courtesy and into the realm of <em title="Oh come on, I had to.">serious business</em>. In the mid-1990s, <a href="http://www.google.com/" title="Google" rel="dct:references">some guys made a bet</a> that every link to a resource <a href="http://www.google.com/corporate/tech.html" title="Corporate Information &#x2014; Technology Overview &#x2014; Google" rel="dct:references">is a vote for its fitness</a>. By proxy, this bet gave birth to an entire industry known as <acronym title="Search Engine Optimization">SEO</acronym>. The net effect is this: if your <a href="../lexicon/resource" title="Resource" rel="dct:references">resource</a> got hastily named, giving it a better one without compensating for the original <span class="parenthesis" title="assuming you're trying to be found.">will likely do more harm than good</span>. A final complication is that more pithy names &#x2014; aside from being more helpful to <em>people</em> &#x2014; are also found to contribute to this fitness rating, driving incentive to do so. Therefore:</p>
    <ul>
      <li>Provide a mechanism to <span>track renames, deletions and collisions</span> of <acronym title="Uniform Resource Identifier">URI</acronym>s;</li>
      <li>Provide an intermediate naming scheme for <a rel="dct:references xhv:section" href="distinguishing-persistence-from-publication" title="Distinguishing Persistence from Publication">unpublished work</a>; and</li>
      <li><a rel="dct:references xhv:section" href="uri-syntax-constraints" title="URI Syntax Constraints">Constrain</a> the <a rel="dct:references xhv:section" href="uri-path-and-query-parameter-semantics" title="URI Path and Query Parameter Semantics">options for naming</a> <acronym title="Uniform Resource Identifier">URI</acronym>s.</li>
    </ul>
  </body>
</html>
