More nice-to -aves..

scheduled publishing of push

Ideally, allow the REST API to work with normal permissions

If workflow is implemented then we need to update our listing on cmsmatrix to reflect this.
Ditto once we are happy with our extendable 'meta data' support.

I am verging on throwing away the core XML syndication idea, and changing it to the virtual filesystem in #218. This way we are representing content within interchange formats. These can be hand-edited, directly managed in normal tools (e.g. video editors, photoshop), managed from git (which is a nicer workflow than juggling with complex structured XML) and interfaced with by other systems that don't want to be Composr-specific.

I like the idea of separating out the content into two:
- Core content (documents, videos, etc)
- Social aspects (view counts, comments, etc)

You have little or no desire to syndicate the social aspects (except using replication on redundant networks) - in fact you probably don't want it. The social stuff does not fit with the interchange formats either. However, the core content can syndicate great with webdav and git, using interchange formats.

New revision control strategy will focus around WebDav, Commandr, and Git.

Content syndication can be done with MySQL replication. http://dev.mysql.com/doc/refman/5.0/en/replication-options-master.html