Abstract
Require atom:id, atom:title, atom:updated, atom:author. That's it.
Status
Open
Rationale
The spec delivers value when it can make an element mandatory.
A number of use cases (e.g., subversion change logs and email attachments) have been defined in which there is no alternate html representation.
A number of use cases (e.g., linkblogs and HTTPLR) have been defined in which there is no summary or content.
Proposal
In atompub-format-07, change two bullets in section 4.1.1.
Before:
-
atom:feed elements MUST NOT contain more than one atom:id element.
After:
-
atom:feed elements MUST contain exactly one atom:id element.
Before:
-
atom:feed elements MUST contain at least one atom:link element with a relation of "alternate".
After:
-
atom:feed elements SHOULD contain at least one atom:link element with a relation of "alternate".
In atompub-format-07, change two bullets in section 4.1.2.
Before:
atom:entry elements MUST contain an atom:summary element in any of the following cases:
-
the atom:entry element contains no atom:content element.
-
the atom:entry contains an atom:content that has a "src" attribute (and is thus empty).
-
the atom:entry contains content that is encoded in Base64; i.e. the "type" attribute of atom:content is a MIME media type [RFC2045] and does not begin with "text/" nor end with "+xml".
After:
atom:entry elements MUST contain an atom:summary element in any of the following cases:
-
the atom:entry contains an atom:content that has a "src" attribute (and is thus empty).
-
the atom:entry contains content that is encoded in Base64; i.e. the "type" attribute of atom:content is a MIME media type [RFC2045] and does not begin with "text/" nor end with "+xml".
Impacts
Tools which expect feed level links (such as Bloglines) will need to be prepared for the absense of this information. Current tools are prepared to deal with content that contains no <summary> or <content>.
Notes
see also: PaceCoConstraintsAreBad