[Cosmo-dev] Cosmo 0.6 sharing

[Brian Moseley]

On 10/23/06, Randy Letness <randy at osafoundation.org> wrote:
> I've started a Wiki page containing a bunch of notes (and a lot of
> questions) on sharing for Cosmo 0.6.

a few comments:

* you're right in thinking that cosmo should be able to store data
types defined by parcels and regurgitate them back to chandler without
any server code changes. ideally the cosmo ui would be able to present
these items and allow basic item crud functions even without any
semantic understanding.

* according to my understanding of EIM, a "contentitem" record
explicitly doesn't carry any stronger typing information. this sort of
record could apply to an item of any type. this implies to me a mixin
typing system for cosmo like jcr's. when processing the record stream
for an item, we could first create it as a ContentItem from the first
record, then mix in the Note type when we hit the note record.

* pje had discussed the notion of a "metadata record" that would tell
the processor what data items to expect in following records. i don't
think we've hammered out the details, but imagine it's sort of like
the header line that you often put into a csv file. i imagine this
will allow us to unambiguously determine what record element describes
the uuid of the associated item.

* i believe that all item data will be communicated through EIM. in
other words, no icalendar.

* re cosmo AttributeSets, i like the idea. the api could be something
like Item.getAttribute(namespace, name) or even
Item.getAttribute(QName) where a QName is simply a namespace/localname
pair, just like xml and jcr. i'm not sure how an item would have two
distinct sets of attributes in the same namespace - this implies that
chandler sent two separate Note records for the same item, for
instance, which would be redundant.