Becker, Matthew R a écrit :
This approach sounds good. Thanks.
There is, however, nothing to stop you from linking other, non-
collection feeds (ie. with a different `rel` value) from the
service document. You'd just need to specify in an extension how
clients can know the ordering of these feeds so they can request
the one they'd like.
Can anyone elaborate some more on why draft 15 is changing the standard
ordering to be based on app:edited instead of atom:updated? Wouldn't feed
readers be triggering off of atom:updated? Leaving that as the default sort
order would allow for optimization in determining significantly changed content
as opposed to ordering on app:edited where changes may or may not have been
significant.
If you search for the discussion you'll find a *very* long one so let's
not start it again. Basically:
* the WG felt collections needed at least one default sorting element
* app:edited is the best one for a collection feed which takes place in
the context of the AtomPub service itself
In other words, you should not consider the collection feed as the
"public" feed to which you would like the public to subscribe to a feed.
Instead consider the collection feed to the limited set of users that
are interested in editing entries. If you need a "public" feed, create a
distinct atom feed where you can sort the entries as you please. That
feed would not be the collection feed, but a simple feed meaningless for
an APP aware peer.
- Sylvain
