2006/3/9, James Tauber <[EMAIL PROTECTED]>: > > Something that has been niggling at me for a while... > > I've long assumed that the collection feeds used by APP will > generally NOT be the feeds the public subscribes to (at least in the > common scenario of a blog). > > The mental model I've been assuming in developing Demokritos is that > the collection feeds are just for use by APP clients and each Atom > server will have some separate mechanism for configuring what feeds > are published more generally. > > So, for example, a collection feed for a blog might only be visible > to me and might contain summaries and out-of-line content for use > only by my APP client. Quite separate from this, I can configure a > publicly available full-content feed, summary-only feed, categories > feeds, author-specific feeds, etc. > > Is this what other people are thinking as the common practice for APP- > powered blogs?
As soon as the implementation supports the notion of "drafts" (or other "private" or "protected" data/metadata), yes. Otherwise, if both feeds would have the same content (except probably the atom:[EMAIL PROTECTED]"edit"]), then an implementation could give APP clients the same feed as "subscribers" (subscribers would have an atom:[EMAIL PROTECTED]"edit"] they couldn't use without the appropriate credentials). But I think that many implementations will use separate resources. -- Thomas Broyer
