[Cosmo-dev] morse code and dav sharing mix
Brian Moseley
bcm at osafoundation.org
Mon Apr 30 11:55:14 PDT 2007
On 4/30/07, Morgen Sagen <morgen at osafoundation.org> wrote:
> Once we have removed support for dual-fork ICS/XML shares from
> Chandler, from that point on handing Chandler a CalDAV URL (i.e., a
> DAV collection of type "calendar") will cause Chandler to subscribe
> as a CalDAV client, as I don't think there is a way for the client to
> know that a given CalDAV collection *also* has a morsecode interface
> to it, and what the URL would be without some intelligent "guessing"
> on the client's part. If we need different behavior, this needs to
> be spec'd out.
we could use the DAV:resourcetype property to signal this.
the value of DAV:resourcetype for a typical published collection looks like:
<D:resourcetype xmlns:D="DAV:"><C:calendar
xmlns:C="urn:ietf:params:xml:ns:caldav"/><D:collection/></D:resourcetype>
we could add a cosmo-specific resource type element like so:
<D:resourcetype xmlns:D="DAV:"><C:calendar
xmlns:C="urn:ietf:params:xml:ns:caldav"/><D:collection/><cosmo:morsecode
xmlns:cosmo="http://osafoundation.org/cosmo/DAV"/></D:resourcetype>
we could also add a cosmo specific property like so:
<cosmo:morsecode-URL
xmlns:cosmo="http://osafoundation.org/cosmo/DAV"><href>http://localhost:8080/cosmo/mc/collection/f18754d3-9c4a-4ce6-a462-aca324ad3a04</href></cosmo:morsecode-URL>
More information about the cosmo-dev
mailing list