On Tue, 03 May 2005 18:52:59 +0200, Tim Bray <[EMAIL PROTECTED]> wrote:
http://diveintomark.org/rfc/draft-ietf-atompub-autodiscovery-01.txt http://diveintomark.org/rfc/draft-ietf-atompub-autodiscovery-01.html http://diveintomark.org/rfc/draft-ietf-atompub-autodiscovery-01.xml
Although Mark's not subscribed, I've agreed to relay any changes that have WG consensus back to him for update; although if they're minor, I guess one of us could just rejigger the XML ourselves.
First, I am not too fond of making an autodiscovery protocol "Atom-only" - we will have to live with other feed formats for a few years still, so I think we should embrace legacy feed formats. These are my suggestions
1) Change the attribute value for the rel from "alternate" to "feed", or some similar wording. A feed is not always an alternate of the HTML document in which it occurs. Suggested replacement text:
# 4.1 rel attribute
# The rel attribute MUST be present in an Atom autodiscovery element. As defined
# in section 6.12 of HTML 4 [W3C.REC-html401-19991224], the value of the rel
# attribute is a space-separated list of keywords. The list of keywords MUST
# include the keyword "feed" in uppercase, lowercase, or mixed case.
2) I am not too fond of requiring a type attribute, since feeds may be served in multiple formats from a single URL. I have previously performed a survey about how aggregators handle content negotiation, <URL:http://virtuelvis.com/archives/2005/01/feed-survey>, and with sensible q-values set, aggregators currently in development may be served feeds in a format they're able to understand. In line with this, I suggeest that section 4.2 is removed, and that a new section 5.1 is added:
# 5.1 type attribute
# The type attribute MAY be present in an Atom autodiscovery element. As defined
# in section 12.3 of HTML 4 [W3C.REC-html401-19991224], the value of the type
# attribute of any link element MUST be a registered Internet media type [RFC2045].
-- Arve Bersvendsen
