[Cosmo-dev] Sharing format questions

[Brian Moseley]

On 7/19/06, Katie Capps Parlante <capps at osafoundation.org> wrote:

> These tangles are part of the motivation for going with the "item soup"
> way of looking at things in the original chandler repository. Similarly,
> the user's model of these items is not that they reside in a master
> hierarchical folder/filesystem. This doesn't mean that there will never
> be ways to navigate the space using hierarchical views, but that there
> isn't one master hierarchy that is used to both determine how
> information is viewed as well as encode semantics about the items.

i'm definitely coming more around to this way of thinking. a practical
example for cosmo is similar to the one morgen used earlier: events in
different calendars refer to the same organizer. what happens when
that organizer's contact info changes? it would be ideal to have one
organizer item in the server repository to receive updates rather than
two copies "inlined" with each event. whether or not the contact item
itself is directly exposed as part of an address book collection, or a
generic webdav collection, or not at all, is irrelevant - it's
implicitly exposed by the events related to it.