On 2/1/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: > > * David Powell <[EMAIL PROTECTED]> [2006-02-01 17:10]: > >On the contrary, I have a problem with preventing multiple > >revisions from having the same atom:updated value. > > But then you have no idea which revision will be picked by > clients that try to show the latest one, which to me sounds like > it fulfills the criteria for a potential interop problem, which > is exactly what "SHOULD" is about, so I think this was the right > choice.
It's not straightforward, this came up pretty quickly in the Atom/OWL efforts. As Bill said, it's a composite key. In RDF/OWL that has so far demanded a rule* - somewhat less convenient than having a single URI as id. The question is, from what is the composite key formed? id certainly, updated too - but is same id+updated enough? What if other parts of the entry differ? Different xml:lang even...same entry or different? *see also : http://esw.w3.org/topic/CIFP Cheers, Danny. -- http://dannyayers.com
