Anne van Kesteren wrote:
Quoting James Holderness <[EMAIL PROTECTED]>:
I think the issue of neutral link bookmarking is unlikely to be a
problem for Atom aggregators though. Server bugs are another thing,
but I think most feeds will be broken without an explicit xml:base
anyway, so maybe that's not worth worrying about. I'm not sure though.
Should the WG recommend ignoring Content-Location as a base URI, or
should aggregators follow the RFC exactly as specified?
If `Content-Location` is not usable or can't be used consistent on a
website
(for example, using it for both Atom and HTML content) I suggest we specify
something that is consistent with what browsers do. And perhaps try to
obsolete
the relevant header if possible...
The problem is not with Content-Location, but with RFC 3986. It says
that same-document references must be resolved with respect to the base
URI. It adds that when those references are resolved, they should not
result in a new retrieval action, but that does not help with things
like bookmarking (as James pointed out), and is almost impossible to
implement.
--
Sjoerd Visscher
http://w3future.com/weblog/
