On 5/23/05, Graham <[EMAIL PROTECTED]> wrote: > On 23 May 2005, at 12:15 pm, Robert Sayre wrote: > > > -1 to this part. Why would you bar it? There is no right answer, so > > just let it be looser. > > Because we have to have this line: > > > Within the atom:author and atom:contributor elements an atom:entry > > contains, any single Person SHOULD NOT be mentioned more than once.
That's what I'm -1 on. > Anything looser makes it very hard to interpret the intended meaning > of a set of atom:author and atom:contributor elements > programmatically. What is the interop problem you are trying to avoid? You don't just throw in a SHOULD NOT and say "otherwise it would be hard". > Please describe a suitable algorithm if you wish to > remove this constraint. You get N authors and N contributors. The "Person" rule is terrible overspecification. Robert Sayre
