Re: What to do about namespace derived URI refs... (long)

> 2) You cannot wish away (by virture of some definiton
> which is out of channel) the fact that
> http://robustai.net/~seth/index.htm#Truth returns some
> sting of bits and that the URL identifies that string of bits.

Well we are dealing with RDF here... so what about if that document
was an RDF document instead, which RDF Schemata usually are? What
then? Does the FragID still reference the bundle of bits?

Think about it carefully... what do you get when you put that URI
Reference into a browser when the thing is an HTML page? Assuming that
there is an <a id="Truth"> tag in there somewhere, these things
happen:-

1) You browser dereferences http://robustai.net/~seth/index.htm
2) Your browser parses the representation of the resource returned
3) According to the MIME type of whatever it is that's been retured
(let's assume text/html) it figures out what do do with the "#Truth"
bit. That is something which is coded into the browser. Usually, it
will go to that particular reference in the page.

Now go through the same process, but where an RDF document is
returned... nothing happens, unless you have re-coded your browser to
do something. RDF defines that #Truth as being anything you want it to
be - any instance of rdf:Resource. That's how any RDF conformant
process will recognize it (should recognize it) as being; a
rdf:Resource. RDF M&S clearly states that that can be *anything* that
has identity.

--
Kindest Regards,
Sean B. Palmer
@prefix : <http://webns.net/roughterms/> .
:Sean :hasHomepage <http://purl.org/net/sbp/> .

Received on Wednesday, 6 June 2001 16:53:14 UTC