- From: Eric Jain <Eric.Jain@isb-sib.ch>
- Date: Tue, 17 Feb 2004 16:18:26 +0100
- To: "rdf-interest" <www-rdf-interest@w3.org>
> <http://example.com/foo#bar> can denote an entirely
> different resource than <http://example.com/foo>
From http://www.ietf.org/rfc/rfc2396.txt: "[...] the optional fragment
identifier, separated from the URI by a crosshatch ("#") character,
consists of additional reference information *to be interpreted by the
user agent* after the retrieval action has been successfully completed."
(emphasis mine).
This would seem to imply that user agents have no obligation of passing
on fragment identifiers, and servers no business of making use of them.
On the other hand this does of course not imply that there isn't a lot
of existing software that assumes otherwise...
Yet another option may be to use URNs as resource identifiers, e.g.
rdf:about="urn:test:123". One question in this context: Is it correct to
say that the previously mentioned resource is '123' in the 'urn:test:'
(or 'urn:test'?) namespace?
Received on Tuesday, 17 February 2004 10:18:29 UTC