Tim, can I ask about your thinking regarding the use of atom:updated in PaceDuplicateIDs. What if someone (either the publisher or someone downstream) wants to store a history of every revision in an archive feed? atom:updates forces one to choose only one version per "significant" change. The mechanism it affords (being able to automatically display the newest version) is vital, but it doesn't seem like the best way to do it.
Graham
