Walter Underwood wrote:
Hmm, I wasn't clear. While we are working on the protocol, will we learn things that need to be applied to the format? The protocol is an application of Atom. There will be lots of others, but this one is core, by definition. Previous feed formats have not had an editing aspect, so it wouldn't be a complete surprise to find something missing in Atom.
One of the demonstrated problems in syndication[0] and editing APIs is representation of collections with collections.
-------------------------------
Disclaimer: The following paragraph is not an edorsement of WebDAV's requirements, syntax, or extension of HTTP.
-------------------------------
One thing WebDAV does get right to some extent is representation of sub-collections. This approach is provably effective. Some example applications based on this approach:
* Outlook Web Access is based entirely on XSL-transformed DAV XML, and Javascript's XMLHttpRequest.
* Outlook Express's Hotmail accounts use this protocol as well.
The problems facing a server storing blog entries are not much different (whether or not the entries are exposed to APP). The implementation requirements of those protocols far excede anything we can expect, but some aspects of the model would be extremely valuable to the format and protocol, IMHO.
Robert Sayre
[0] http://www.25hoursaday.com/weblog/PermaLink.aspx?guid=a257ba40-b9fd-4cba-959a-2bba6ae917f0
