[Cosmo-dev] Sharing format questions
bcm at osafoundation.org
Thu Jul 27 10:00:28 PDT 2006
On 7/26/06, Morgen Sagen <morgen at osafoundation.org> wrote:
> 1) There are no "core" attributes -- everything is an annotation. If
> I say an item's title is "Foo" and you say it's "Bar" then Cosmo
> stores both of those values along with their attributions. It's up
> to the client to decide whose to pay attention to -- or possibly
> render both values to the user to decide.
this has too much potential to break down when we have to share the
items with non-osaf products.
> 2) Certain attributes are simply fundamental and have only a single
> value stored on the server -- core attributes like "title" and "start
> time". These attributes are never filtered out when the item is
> shared. Other attributes are considered annotations and may be
> filtered out either by publisher or subscriber.
seems more reasonable.
> Also, I've updated the list below to take into account people's
> comments from the past day:
> - On Cosmo, Items are in a soup, identified by UUID
> - We define the term "Principal" which represents a Ticket, an
> Account, or a Group (where a Group can contain Accounts or other Groups)
> - There are two types of Permissions: Read-only and Read-write
what about the free-busy permission that we have today?
> - The attributes of an Item fall into two categories: those that are
> "core" to that Item, and those that are "annotations"; core
> attributes live in the body of the item's resource, while annotations
> live in the resource's DAV properties (This depends on how people
> answer the core/annotation choice I posed at the top of this message).
not necessarily a perfect distinction. dav clients and servers can
choose to add their own properties to resources that aren't understood
by our server or client, and we should/must store and re-transmit
those. they aren't user-generated annotations, and they aren't core
attributes of our own schema. what are they?
More information about the cosmo-dev