[Cosmo-dev] chandler/cosmo sharing format -- requirements proposal

[Brian Moseley]

On 5/6/06, Kervin L. Pierre <kervin at adevsoft.com> wrote:

> Is this format proposal tackling the CalDAV
> client/server synchronization also?  Or is
> it only dealing with representing further
> resource information on the CalDAV server?

the latter. remember the discussion about mixed content i started on
the caldav list a while back? that was in service of the same goal -
to find a way for chandler to share arbitrary mixed content to cosmo
and to provide caldav access to only the calendar part of that
content.

cosmo has never been intended as "just" a caldav server. caldav is one
way to get data in and out of cosmo, but there can certainly be
others. for instance, we're talking about ways to use atom (like
google's gdata api). we're also trying to find more efficient ways for
chandler and cosmo to sync collections of mixed content.

> What does "share" versus "publish" mean?

it's chandler terminology for publishing and subscribing :)