This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I'd like to make use of feed autodiscovery on pages such as http://annevankesteren.nl/2010/02/sabotage While I can understand that rel=feed is not really needed when it was removed the definition of rel=alternate in conjunction with type=application/atom+xml was not changed to indicate that using it on such pages is acceptable. It would be nice if that was fixed.
I asked Mark to comment on this.
This seems really bad, as it means the spec is incompatible with the majority of deployed usage of autodiscovery, as WordPress, MT, and other widely used blogging packages include autodiscovery on all pages.
I agree with Geoffrey; the definition of rel=alternate should be changed to match existing web content.
So to clarify, the request here is to make rel=alternate have a different meaning when the type="" attribute explicitly specifies an Atom or RSS type than when it does not? Even if it points to the same document?
Yeah. Probably also add a note of caution that people who want something similar introduce a specific rel value instead rather than building on top of this model.
The original proposal for rel=alternate for RSS feeds was all about home pages (and other landing pages that might reasonably have their own "alternate" forms, like a page that had full or partial content from all the blog posts in a specific category and linked to a category-specific feed that mirrored that landing page in a specific feed format). The RFC I wrote for rel=alternate for Atom feeds (long since expired) was all about home pages and other landing pages. It intentionally did NOT mention the case of individual blog post pointing to a "main" feed for the site that might not even contain the blog post in question (if it was too old and/or the feed was too short). In the meantime, the world decided to put rel=alternate links on every single fracking web page, ever. I don't particularly care how you phrase it, but the HTML5 spec needs to acknowledge this fact. It will be the first attempt to ever do so. Good luck with that.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r4964. Check-in comment: Define rel=alternate for feeds as something conforming. http://html5.org/tools/web-apps-tracker?from=4963&to=4964