>I disagree, as I've said before. The only literal interpretation is >that you can't serve the same entry twice with the same id. We know it >doesn't mean that, but the spec just doesn't define in which axis >"unique" is meant to apply.
I think that the problem is that the term 'entry' is used to refer to two different concepts. An entry id is identifying the underlying entry resource. But something like an entry title, I would think of as a property of the 'entry instance'. Currently we don't distinguish between entries and entry instances, and I think that this creates a lot of ambiguity. Although we could keep the model we have (let's call it the 'mutable entries' model), it isn’t clear on a number of issues. Eg, if an old version of an entry has some property that isn’t present in a newer version, does that property still apply to the new instance? The answer is presumably 'no' but it isn't obvious from the spec. Under a 'multiple instances' model, it would be implicit. -- Dave
