On Wed, Feb 25, 2009 at 10:53:29AM -0500, Joe Hourcle wrote:
> The only problem that I have with URIs is when they don't resolve so that
> we can get information about what it means. (and well, that one doesn't,
> as lcsh.info had to shut down). Without resolution, URIs are less useful
> than strings.
The mechanics for resolving URIs to useful information -- and
in accordance with current principles of Web architecture --
have been worked out as described in [1] and [2].
If an Apache Web server is configured accordingly, a
property URI such as
http://www.w3.org/2008/05/skos#broader
will resolve either to a Web page (if you are a human clicking on
the URI in a browser):
http://www.w3.org/TR/2008/WD-skos-reference-20080829/skos.html#broader
or to a machine-processable RDF schema (if you are requesting
the information via an RDF application):
http://www.w3.org/TR/2008/WD-skos-reference-20080829/skos.rdf
The redirects happen automatically. If you have access to
a computer running the command-line utility "curl", you can
examine the intermediate steps, as attached below.
Tom
[1] http://www.w3.org/TR/cooluris/
[2] http://www.w3.org/TR/swbp-vocab-pub/
----
curl --header "Accept: application/rdf+xml" http://www.w3.org/2008/05/skos#broader
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>303 See Other</title>
</head><body>
<h1>See Other</h1>
<p>The answer to your request is located
<a href="http://www.w3.org/TR/2008/WD-skos-reference-20080829/skos.rdf">here</a>.</p>
</body></html>
curl --header "Accept: text/html" http://www.w3.org/2008/05/skos#broader
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>303 See Other</title>
</head><body>
<h1>See Other</h1>
<p>The answer to your request is located
<a href="http://www.w3.org/TR/2008/WD-skos-reference-20080829/skos.html">here</a>.</p>
</body></html>
--
Thomas Baker <[log in to unmask]>
|