- From: Pat Hayes <phayes@ihmc.us>
- Date: Mon, 23 Jan 2006 17:12:29 -0600
- To: "Booth, David (HP Software - Boston)" <dbooth@hp.com>
- Cc: <public-swbp-wg@w3.org>
> >Thing-described-by.org provides one easy mechanism for avoiding this >kind of URI clash. For example, if you have a URI for a Web page >describing Mark Birbeck: > http://shutr.net/user/markb >by prepending "http://thing-described-by.org?" to the URI, you can >easily create a URI that you can use as an identifier for Mark Birbeck, >the person: > http://thing-described-by.org?http://shutr.net/user/markb >Dereferencing this latter URI will result in a 303-redirect to the >original Web page that describes him. Well, in this particular case it actually yields a 403 Forbidden error rather than a Web page, but I get the idea. And in any case it might even be true of Mark Birkbeck that I don't have permission to access him. Come to think of it, that is more likely than not. > Simple! No servers to configure, >nothing to do. > >And if thing-described-by.org is too long for your taste, you can use >t-d-b.org instead, such as: > http://t-d-b.org?http://shutr.net/user/markb > >For more information, see http://thing-described-by.org . > >Of course, this is not the only way this problem can be solved, but I >thought it would be relevant to mention it. My dear fellow, you are a genius. The whole idea of having to generate 303 indirects is utterly insane, but given that we have to do insane things from time to time, at least you have given us a way to do it relatively painlessly. My heartiest congratulations (and thanks). Pat Hayes -- --------------------------------------------------------------------- IHMC (850)434 8903 or (650)494 3973 home 40 South Alcaniz St. (850)202 4416 office Pensacola (850)202 4440 fax FL 32502 (850)291 0667 cell phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes
Received on Monday, 23 January 2006 23:12:36 UTC