Closed gra-moore closed 12 years ago
Hmmmm. Is this a good thing? The flexibility to allow a fragment to represent several resources might be useful in some cases, even if nobody does it right now.
If conceptually the feed lists the resources that have changed rather than a update it then seems confusing / unclear that two or more resource uris are listed in the entry.
Well, yes, if you choose to make that conceptual change. But you don't have to do that. It could instead be a feed of the changes, at any granularity. I sort of liked the old ambiguity, but I agree that the fragment-per-resource approach is easier to explain. We might be able to add some verbiage to make this clear without tying ourselves down.
We allow multiple (with the conceptual implications that has), and explain the single-resource-per-fragment concept for ease of understanding.
We changed our minds: we're now tied to the single-resource-per-fragment concept, which means single resource.
The spec is now in line.
Now that conceptually each entry is related to the fact that a single resource has been updated I proposed we remove the option to mush together updates and disallow multiple ResourceUri properties in an entry.