Re: RDF & fragment ids; what breaks?

Mark Baker wrote,
> If an HTTP client is told that "http://example.org/foo#bar"
> identifies a resource of interest to it, and attempts to dereference
> that URIref, "#bar" isn't part of that HTTP GET message that gets
> sent.  By *definition*, other HTTP components have less visibility
> into the meaning of the message than the client.

I agree, but I don't see how this is relevant to my original comment. I 
wasn't talking about URI refs.

Cheers,


Miles