- From: Peter Mika <pmika@cs.vu.nl>
- Date: Fri, 16 Dec 2005 09:50:28 +0100
- To: <mark@few.vu.nl>
- Cc: "'Mark van Assem'" <mark@cs.vu.nl>, "'Jacco van Ossenbruggen'" <Jacco.van.Ossenbruggen@cwi.nl>, "'Jeremy Carroll'" <jjc@hpl.hp.com>, "'Aldo Gangemi'" <aldo.gangemi@istc.cnr.it>, <public-swbp-wg@w3.org>, <schreiber@cs.vu.nl>, <Benjamin.Nguyen@inria.fr>
Hi Mark, > > Two alternatives may be: > > > > 1. All statements with this resource as subject, predicate or object. > > 2. The concise bounded description of the resource [1] > > These are options only for the slash-case, right? > Yes. I don't know if this came up before in the discussion (sorry if I repeat something), but the problem with hash URIs is that the fragment identifier (the part after the hash) is not passed on to the server. So something like http://wordnet.princeton.edu/rdf#entity will be seen by the Princeton server as http://wordnet.princeton.edu/rdf So the only thing the server can do is to return the entire WordNet. Patrick Stickler's workaround is to pass on the full URI as an HTTP header [1]. But again, I couldn't say this is best practice. Cheers, Peter [1] http://sw.nokia.com/uriqa/URIQA.html
Received on Friday, 16 December 2005 08:50:34 UTC