In message <EMEW3|b88ea541556c1ff93cb7842c018e2d08l681Q702hg|ecs.soton.ac.uk|C21D%hg
@ecs.soton.ac.uk>, Hugh Glaser <h...@ecs.soton.ac.uk> writes

Hash URIs are very valuable in linked data, precisely *because* they
can't be directly requested from a server - they allow us to bypass
the whole HTTP 303 issue.
Mind you, it does mean that you should make sure that you don't put too many
LD URIs in one document.
If dbpedia decided to represent all the RDF in one document, and then use
hash URIs, it would be somewhat problematic.

One aspect of this that puzzles me is how you do the "deliver a human-readable or machine-processible version depending on the Accept header" trick when the actual resource is a single RDF document containing hash-referenced assertions.

Richard
--
Richard Light

Reply via email to