http://norman.walsh.name/2007/02/18/bigBang 10 14 2007-02-18T19:04:57-05:00 $Date: 2007-02-20 07:37:57 -0500 (Tue, 20 Feb 2007) $ Norman Walsh 2007 Norman Walsh Hacking httpRange-14. Hubert H. Humphrey In real life, unlike in Shakespeare, the sweetness of the rose depends upon the name it bears. Things are not only what they are. They are, in very important respects, what they seem to be. Semantic web enthusiasts among my readers will have encountered the “hash vs. slash” debate, perhaps most famously in the TAG's attempt to resolve the range of HTTP: URIs. When I first started this weblog, I knew it was going to be built on top of a semantic web framework, not out of any fervent belief that it's the future, but out of the conviction that I won't be able to say whether or not I think it's the future if I don't try it out. I also knew about the hash vs. slash debate. While I was never entirely convinced by the arguments of the “anti-slash” camp, I decided to simply avoid the issue by using a hash. There's never been any argument about hashed URIs, only slashed ones. As a result, the identifier for me, my physical person, became: http://norman.walsh.name/knows/who#norman-walsh As time passed, this had a practical consequence. If you dereferenced that URI, the server would send you the whole “who” file that contained all the metadata about everyone. That file got to be big. I ignored this problem as long as I could, simply living with the inconvenience, but when I decided to support “link groups” I faced a real hurdle. The obvious URI for the “link group” about me is the URI that identifies me. But linking to the hashed URI made following the link way too expensive to be of practical value. I could have cooked up an alternate URI for the link group, but that would effectively have been an alias. Aliases: bad. Unable to come up with a workaround I liked, I decided it was time for a big bang: I decided to change a whole lot of URIs. Instead of using a hashed URI to identify me (and everyone and everything else), I'd use a slashed one: http://norman.walsh.name/knows/who/norman-walsh In order to do this, I felt I needed to implement the TAG resolution on httpRange-14. Which I've done: A GET on http://norman.walsh.name/knows/who/norman-walsh returns a 303 redirect to http://norman.walsh.name/knows/who/norman-walsh.html. The HTML at http://norman.walsh.name/knows/who/norman-walsh.html includes a link to the metadata: <link rel="alternate" type="application/rdf+xml" title="Metadata" href="norman-walsh.rdf" /> which I hope helps semantic web software find the underlying metadata. That metadata in turn contains <owl:sameAs rdf:resource="http://norman.walsh.name/knows/who#norman-walsh"/> which tells the semantic web agent that this URI is entirely equivalent to the former hashed URI. Hopefully this all “just works” in every meaningful way.