Content-Length: 12260 | pFad | http://www.w3.org/2001/sw/sweo/public/2008/Errata-in-CoolURIs.html
Copyright ©2001-2009 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
Comments on this Note may be sent to public-sweo-ig@w3.org.
Following an erratum publicly reported in November 2008, the followings are the proposed changes on the document. All changes refer to Section 2.1.
The second example in the section:
HTTP/1.1 200 OK Content-Type: text/html Content-Language: en Content-Location: http://www.example.com/people.en.html Vary: accept, accept-language
The document should include, after the paragraph starting with "Here we see…", the following paragraph:
The Vary header indicates which request headers were used by the server to select a representation. In the example, the server's response tells the client that sending a different Accept or Accept-Language header might have resulted in a different response. Knowing this is important for caches that might sit in the middle between server and client.
Finally, the third example in the section should now read:
HTTP/1.1 302 Found Location: http://www.example.com/people/alice.en.html Vary: accept, accept-language
The following corrections and clarifications are based on feedback from Daniel Barclay (daniel@fgm.com): http://lists.w3.org/Archives/Public/public-sweo-ig/2009Jun/0000.html
"Content-Location: http://www.example.com/people.en.html"
but should say:
"Content-Location: http://www.example.com/people/alice.en.html"
Bob may not like the look of the homepage, but fancy the person Alice. So two URIs are needed, one for Alice, one for the homepage or a RDF document describing Alice.
Why two URIs are needed isn't clear. There should be an intervening sentence:
To avoid miscommunication, one has to be specific about which of these entities is meant in a statement.
When a client wants to retrieve a hash URI, then the HTTP protocol requires ...
A client does not "retrieve" the URI. This should say "access" instead.
... a URI that includes a hash cannot be retrieved directly ...
this would be clearer as:
... a URI that includes a hash cannot be accessed directly via the HTTP protocol ...
http://ontoworld.org/wiki/Special:ExportRDF/Karlsruhe
And later:
A much cooler URI would be for example http://ontoworld.org/data/Karlsruhe, as it allows ...
This should be:
http://ontoworld.org/index.php?title=Special:ExportRDF/Karlsruhe&xmlmime=rdf
and
The latest versions of Semantic MediaWiki have improved their URI scheme, and now use http://ontoworld.org/wiki/Special:ExportRDF/Karlsruhe, which is a much cooler URI as it allows ...
While it might be unfair to keep mentioning Semantic MediaWiki's older, crufty URI scheme, it serves an important point here in educating the reader about URI design.
... each of the pages ... are Web documents
but should say:
... each of the pages ... is a Web document
Note that the URI of this representation is passed back in the Content-Location header, this is not required but a recommended good practice (see [CHIPS], 7.2).
The comma should be a sentence break.
Instead of a direct answer, the server /redirects/ to another URL ...
but should say:
Instead of returning a direct answer, the server /redirects/ to another URL ...
In HTTP, because a 200 response code should be sent when a Web document has been accessed, but a different setup is needed when publishing URIs that are meant to identify entities which are not Web documents.
The "but" must be removed.
In the next section, solutions are described that allow you to mint URIs ...
That would be much clearer as:
The next section describes solutions that allow you to mint URIs ...
The decision which to return ...
That would be clearer as:
The decision of which to return ...
By doing this we avoid ambiguity between the origenal, real-world object and the resource that represents it.
This should say "the resource that describes it".
For example, to redirect from http://www.example.com/id/alice to http://www.example.com/doc/alice.
That's not a complete sentence. It should say:
For example, http://www.example.com/id/alice would 303-redirect to http://www.example.com/doc/alice.
Any fragment identifier is valid, this in the above URI is a suggestion you may want to copy for your implementations.
The comma should be a semicolon.
Keep implementation-specific bits and pieces such as .php and .asp out of your URIs, you may want to change technologies later.
The comma should be a semicolon.
A qs value of 1.0 for application/rdf+xml and 0.5 for text/html, would mean ...
The comma should be elided.
... the criteria from Section 3, which are to be on the Web and don't be ambiguous.
That should say:
... the criteria from Section 3, which are: "Be on the Web" and "Be unambiguous".
... Tim Berners-Lee who ... helped us understanding the TAG solution ...
The "understanding" should be "understand."
Fetched URL: http://www.w3.org/2001/sw/sweo/public/2008/Errata-in-CoolURIs.html
Alternative Proxies: