Require upwards-compatibility with WebDAV.
The Publishing Protocol overlaps with WebDAV in several areas. By ensuring that the protocol is compatible with WebDAV, we can reduce the surface area of the spec, decrease the need to reinvent WebDAV functionality in the future, and perhaps even punt on complex problems (e.g. renaming images, ACLs) in favor of WebDAV.
Adjust the charter as follows:
The editing protocol must enable:
creating, editing, and deleting feed entries
upward-compatibility with WebDAV
multiple authors for a feed
multiple subjects or categories in a feed
adding, editing, and deleting users
setting and getting user preferences
creating, getting and setting related resources such as
comments, templates, etc.
Despite appearances, it would not change current implementations a whole lot.
One thing this *does not* rule out is the current approach using feed listings and prev/next. WebDAV does not define responses to GET on a collection, so that approach would be acceptable.