Description changed to 'From http://dev.w3.org/html5/spec/Overview.html#atom:
"9...
Otherwise
Let id be a user-agent-defined undereferenceable yet globally unique valid absolute URL. The same absolute URL should be generated for each run of this algorithm when given the same input. Let has-alternate be false."
But RFC 4287 states:
"When an Atom Document is relocated, migrated, syndicated, republished, exported, or imported, the content of its atom:id element MUST NOT change." -- http://greenbytes.de/tech/webdav/rfc4287.html#rfc.section.4.2.6
So it appears that HTML5 tries to relax that requirement.
Suggested fix: either just reference the requirement in the base spec, or make it a "must".
Furthermore, HTML5 requires "undereferenceable", while RFC 4287 does not.
See http://www.w3.org/Bugs/Public/show_bug.cgi?id=7806.
HTML5-SPEC-SECTIONS [atom]'/html/wg/tracker/issues/86#2010-02-16T13:22:46Z2010-02-16T13:22:46ZJulian Reschke

Otherwise
Let id be a user-agent-defined undereferenceable yet globally unique valid absolute URL. The same absolute URL should be generated for each run of this algorithm when given the same input. Let has-alternate be false."

Description changed to 'From http://dev.w3.org/html5/spec/Overview.html#atom:
"9...
Otherwise
Let id be a user-agent-defined undereferenceable yet globally unique valid absolute URL. The same absolute URL should be generated for each run of this algorithm when given the same input. Let has-alternate be false."
But RFC 4287 states:
"When an Atom Document is relocated, migrated, syndicated, republished, exported, or imported, the content of its atom:id element MUST NOT change." -- http://greenbytes.de/tech/webdav/rfc4287.html#rfc.section.4.2.6
So it appears that HTML5 tries to relax that requirement.
Suggested fix: either just reference the requirement in the base spec, or make it a "must".
Furthermore, HTML5 requires "undereferenceable", while RFC 4287 does not.
See http://www.w3.org/Bugs/Public/show_bug.cgi?id=7806.
'/html/wg/tracker/issues/86#2009-10-23T16:28:19Z2009-10-23T16:28:19ZJulian Reschke

Otherwise
Let id be a user-agent-defined undereferenceable yet globally unique valid absolute URL. The same absolute URL should be generated for each run of this algorithm when given the same input. Let has-alternate be false."

Created issue 'HTML5 relaxes Atom requirement on atom:id stability' nickname atom-id-stability owned by Julian Reschke on product HTML 5 spec, description 'From http://dev.w3.org/html5/spec/Overview.html#atom:
"9...
Otherwise
Let id be a user-agent-defined undereferenceable yet globally unique valid absolute URL. The same absolute URL should be generated for each run of this algorithm when given the same input. Let has-alternate be false."
But RFC 4287 states:
"When an Atom Document is relocated, migrated, syndicated, republished, exported, or imported, the content of its atom:id element MUST NOT change." -- http://greenbytes.de/tech/webdav/rfc4287.html#rfc.section.4.2.6
So it appears that HTML5 tries to relax that requirement.
Suggested fix: either just reference the requirement in the base spec, or make it a "must".
See http://www.w3.org/Bugs/Public/show_bug.cgi?id=7806,
' non-public/html/wg/tracker/issues/86#2009-10-23T16:25:31Z2009-10-23T16:25:31ZJulian Reschke

Otherwise
Let id be a user-agent-defined undereferenceable yet globally unique valid absolute URL. The same absolute URL should be generated for each run of this algorithm when given the same input. Let has-alternate be false."