Bill de hÓra wrote:
Thomas Broyer wrote:
If this is not core, at least let implementations the possibility to order
collection membership listing by something different from atom:updated.
protocol-06 reads “The entries in the returned Feed MUST be ordered by
their 'atom:updated' property” which prevents any app:modified-style
extension.
Don't take this as an objection to your idea, but I don't understand how
allowing a variety of sort-bys relates to a client syncing with a server?
Client syncing with a server is related to syncing “significant” vs.
“insignificant” changes (use cases: offline editing, wikis and group
blog “ex post facto” moderation).
“Significant” vs. “insignificant” is related to atom:updated vs.
app:modified (or call it as you want).
Eric proposed examples showing the problem having atom:updated-sorted
lists and syncing “insignificant” changes.
That's how I relate allowing sorting by app:modified rather than
atom:updated and a client syncing with a server.
--
Thomas Broyer
