9051 2010-02-17 13:41:34 +0000 feed autodiscovery for main feed on posts 2010-10-04 14:48:53 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Linux RESOLVED FIXED P3 normal --- 1 annevk ian geoffers+w3cbugs ian mark mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 32273 0 annevk 2010-02-17 13:41:34 +0000 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. 32578 1 ian 2010-02-23 11:47:52 +0000 I asked Mark to comment on this. 32579 2 geoffers+w3cbugs 2010-02-23 11:56:30 +0000 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. 32591 3 mark 2010-02-23 18:27:57 +0000 I agree with Geoffrey; the definition of rel=alternate should be changed to match existing web content. 34274 4 ian 2010-03-31 21:24:04 +0000 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? 34275 5 annevk 2010-03-31 21:29:02 +0000 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. 34280 6 mark 2010-03-31 21:40:03 +0000 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. 34487 7 ian 2010-04-04 06:59:25 +0000 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. 34488 8 contributor 2010-04-04 07:03:19 +0000 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