Peter Keane wrote:
Here's the link:
http://tools.ietf.org/id/draft-nottingham-http-link-header-03.txt
thanks a lot for the link!
http://tools.ietf.org/id/draft-nottingham-http-link-header-04.txt is the
latest version, btw, and i have updated my atom landscape overview to
also include a link to that draft, which i hope will become an RFC.
http://dret.typepad.com/dretblog/atom-landscape.html
it seems to me that this draft and HTML5 are currently out of sync when
it comes to linking to feeds. HTML5 explicitly defines a "feed" relation
(http://dev.w3.org/html5/spec/Overview.html#link-type-feed), whereas the
draft only has "alternate" and thus probably is based on current
practice. is HTML5 expected to maybe add "feed" (and whatever else new
link relations it may introduce) to the registry, or wouldn't it be
easier to include this in the registry from the very beginning, so that
HTML5 can count on it?
but then again, if "feed" would be defined by that draft, its semantics
would also have to be defined by it, because there currently is no
stable document defining it. which in a way brings me back to my initial
question of where those semantics are currently defined anywhere...
thanks and cheers,
dret.