Require that atom:id is a NewsML URN. Proposed by: [BobWyman]
Withdrawn by Author 7-Sep-2004
Much aggregator and processor experience indicates that not providing strong guidance on the proper formation of atom:id's results in great difficulties for the processors of atom feeds. See: mailing list discussion.
Change sections 4.2.6 and 5.5 of the format specification to read:
4.2.6 "atom:id" Element
The "atom:id" element's content conveys a permanent, globally unique identifier for the feed. It MUST NOT change over time, even if the feed is relocated. atom:head elements MAY contain an atom:id element, but MUST NOT contain more than one. The content of this element, when present, MUST be a NewsML URN.
5.5 "atom:id" Element
The "atom:id" element's content conveys a permanent, globally unique identifier for the entry. It MUST NOT change over time, even if other representations of the entry (such as a web representation pointed to by the entry's atom:link element) are relocated.
For a given entry, the atom:id element's content MUST be stable across all Atom Documents published by the same entity.
atom:entry MUST contain exactly one atom:id element. The content of this element MUST be a NewsML URN.
Slightly increases complexity of generating atom feeds and entries since an identifier other than permalink must be created for each feed and entry.
Significantly increases the ability of feed aggregators and other atom processors to detect and manage new atom entries and feeds.
See also: PaceRecommendIdScheme
See: RFC 3085 http://ietf.org/rfc/rfc3085.txt
The following are valid, and distinct, NewsML URNs: