- From: Xiaoshu Wang <wangxiao@musc.edu>
- Date: Mon, 7 Aug 2006 09:36:49 -0400
- To: "'Richard Newman'" <r.newman@reading.ac.uk>
- Cc: "'Semantic Web'" <semantic-web@w3.org>
--Richard, > >> And then to look up http://rdf.insee.fr/geo#code_commune , > a consumer > >> just GETs http://rdf.insee.fr/geo as usual; then when they want to > >> look up another term such as http://rdf.insee.fr/geo#subdivision, > >> they can save a round trip because they already have it. > >> > >> Using a / namespace has a higher cost for the producer > >> (redirects) and for the consumer (one GET per term rather than one > >> GET for the ontology). > > > > I actually disagree this a little bit. To save a roundtrip > requires > > caching on the consumer's side. The same can/should also > be done with > > the slash URI. > > No, it can't. > > Retrieving > > http://example.com/ont#one > http://example.com/ont#two > http://example.com/ont#three > > makes three requests for "http://example.com/ont", which is > the resource. This is very very likely to be cached in at > least one place along the line; hopefully within the tool > itself, for one. > > Retrieving > > http://example.com/ont/one > http://example.com/ont/two > http://example.com/ont/three > > requires three separate requests for three separate > resources, and an HTTP client *does not know* that it should > -- *perhaps* -- retrieve "http://example.com/ont" to get a > description of those three terms. > > The web architecture does not support retrieval of terms from > the entire hierarchy. Why can't it be cached? For instance, http://purl.org/dc/elements/1.1/contributor and http://purl.org/dc/elements/1.1/title, would get back the same document. If there is a rule says: all http://purl.org/dc/elements/1.1/* would return the same document, why can't it be cached? The rest of your message seemed have missed the intension of my question. Of course, everything in RDF is processed as a full URI. But knowing the relationship between namespace URI and the resource URIs that are under the namespace will help the client side processing. The relationship between the # namespace URI and its governed URIs is clearly defined in URI spec. But that for slash namespace URI is not (at least from my limited knowledge). Xiaoshu
Received on Monday, 7 August 2006 13:37:39 UTC