[Design] annotations in Chandler
mimi at osafoundation.org
Mon Nov 14 09:05:12 PST 2005
Good point. For Chandler to be viable as a 1.0 email client, we would
need to support versioning some kind of crude versioning so that user-
edits never corrupt the "original mail" and users always have access
to the original mail.
(Could we, for example, store the original mail as an attribute of
the content item? subsequent edits may not be versioned, but the
original mail is always maintained in some form, even if just raw
text? it would mostly be hidden from the user unless they did
something explicit to see it...the same way you can tell your client
to expose the raw mail headers to you, but they're hidden out of the
However prior to being a viable 1.0 email client, I think there is
room to study how people mark-up and edit their content while
Chandler is more of experimental wrt email..more of a task and
calendar app that has email functionality and less of an email client.
On Nov 14, 2005, at 6:36 AM, Steven Healey wrote:
>> It's really a question of philosophy, I'm proposing that we take the
>> 2nd approach and let users do what they want with their data, even if
>> it means corrupting the original content...until we are able to
>> provide more robust annotation functionality. We can probably learn
>> a lot about how to do annotations correctly, by studying how
>> people "annotate" their content on their own.
> There was a discussion on this list about 18 months ago concerning
> the legal
> consequences of editing received e-mail. That might be a good
> thing to
> review at this point.
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "Design" mailing list
More information about the Design