Luke Arno wrote:
There are feeds and some of the members of some of them are editable. The concept that "public feeds" are a separate animal from APP "collections" is meaningless. Public to who?
s/public feed/“subscribable” feed/ (or feed meant to be subscribed to?)
It might be possible to drop the distinction between feeds and collections but this might a bit too early as it might have impacts on other things in the protocol (e.g. ordering collection List feed documents using app:modified instead of atom:updated, list-template without “GET on the collection URI” –where collection URI = app:collection/@href in protocol-06–, etc.)
My opinion however is too keep a distinction between feeds (as things that subscribe to, having RSS or Atom Feed Document representations) and collections (as things you sync' AtomPP clients with –using an Atom Feed Document representation or another format along the line of protocol-04 Collection Document– and HTTP POST resource representations to). Using an Atom Feed Document representation for both uses is not enough to call them the same. Moreover, this distinction doesn't necessarily prevent using the same Atom Feed Document representation at the same URI for both uses (i.e. the collection URI is also the feed URI readers will subscribe to).
-- Thomas Broyer
