[Chandler-dev] Sharing API type system meeting

[Brian Kirsch]

It may be the case that EIM is not the right solution for converting 
items to mail.

Basically I want the ability for an item to serialize itself in such as 
way that various services ie. mail, sharing, rss, etc could leverage the 
same information.

As stated before putting the burden on items to know how to convert 
themselves to RFC 2882 messages seems like the wrong approach.

-Brian



Grant Baillie wrote:
>
> On 13 Sep, 2006, at 14:41, Morgen Sagen wrote:
>
>>
>> On Sep 13, 2006, at 2:21 PM, Brian Kirsch wrote:
>>> I am trying to figure out if there is some way to leverage your 
>>> Sharing format for mail.
>>> [...]
>>> 2. Use a common serialization format which the Mail Service layer 
>>> can use to determine how to convert the Item. This would be the 
>>> preferred method.
>>
>> Yes, it makes sense to transport External Information Model (EIM) 
>> records over email, just as we're going to be doing over DAV, etc.
>
> Er, that doesn't sound so interoperable. Are we just talking about the 
> "Chandler"-specific parts of the message?
>
> --Grant
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev

-- 
Brian Kirsch 
Internationalization Architect / Mail Service Engineer
Open Source Applications Foundation
543 Howard Street 5th Floor
San Francisco, CA 94105
http://www.osafoundation.org