<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:html="http://www.w3.org/1999/html" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>Ross Burton</title><link>http://www.burtonini.com/blog</link><description>A potted account of Ross' life</description><language>en</language><ttl>60</ttl><dc:creator>Ross Burton</dc:creator><admin:generatorAgent rdf:resource="http://pyblosxom.sourceforge.net/"/><admin:errorReportsTo rdf:resource="mailto:ross@burtonini.com"/><item><title>URIs Considered Harmful...</title><guid isPermaLink="false">computers/uuid-20031103</guid><link>http://www.burtonini.com/blog/computers/uuid-20031103</link><description>Many people, specifically the Nautilus maintainers, but including me, consider the use of URIs in GNOME something which should be ...</description><content:encoded><![CDATA[  <p>
    Many people, specifically the Nautilus maintainers, but including me,
    consider the use of <abbr title="Uniform Resource Identifiers">URIs</abbr>
    in GNOME something which should be hidden from the user.
  </p>
  <p>
    For example, to access the CD burning tools in Nautilus, you can navigate to
    <tt>burn:///</tt>. This is ugly and has zero discoverability, i.e. the user
    has to be told that it exists. The same for <tt>network:///</tt>,
    <tt>fonts:///</tt> and <tt>applications:///</tt>. These are all magic URIs,
    once the user knows they exist, they should be able to remember them, but
    the point is that shouldn't have to.  A good example of this is the
    integration of magicdev with nautilus-cd-burner, instead of having to go to
    <tt>burn:///</tt> (or selecting "CD Creator" in GNOME 2.4) to open the
    correct location, magicdev will open it automatically when a blank CD is
    inserted on the assumption that you are likey to want to burn something to
    it.  Joe User can just use it, and Lee T. Hacker remembers the URI.
  </p>
  <p>
    Thats all well and good, and often-covered material.  However, URIs have one
    thing going for them: at least they are not <abbr title="Universal Unique
    Identifiers">UUIDs</abbr>.  I found this gem in the Windows 2000 Resource
    Kit:
  </p>
  <blockquote>
    <p>
      To open a new Explorer window which displays My Documents, use this as the
      command line:
    </p>
    <pre>%SystemRoot%\explorer.exe /e,::{450D8FBA-AD25-11D0-98A8-0800361B1103}</pre>
  </blockquote>
  <p>
    Check out that snappy UUID...
  </p>
]]></content:encoded><category domain="http://www.burtonini.com">/computers</category><dc:date>2003-11-03T19:19:45Z</dc:date></item></channel></rss>