MIME type for distribution lists

David Faure dfaure at klaralvdalens-datakonsult.se
Thu Jun 2 11:29:49 CEST 2005

On Thursday 02 June 2005 07:05, Joon Radley wrote:
> Hi David,
> The whole idea of the content-type definition for the objects is to
> establish the object type before parsing it. Now two objects have the same
> content-type. Could we please keep to the model and give each object an
> unique MIME type.

Hmm, this breaks the current model of "one type of object per folder" though.
We currently know which type of attachment to look for, in a given mail, by looking
up "the" mimetype for this type of folder (which itself comes from the annotation).

To present this differently: the (first component of the) annotation directly maps to the mimetype:

Folder annotation -> Mimetype for objects found in this folder
"mail" -> "application/x-vnd.kolab.mail"
"event" -> "application/x-vnd.kolab.event"
"contact" -> "application/x-vnd.kolab.contact"
"note" -> "application/x-vnd.kolab.note"
"task" -> "application/x-vnd.kolab.task"
"journal" -> "application/x-vnd.kolab.journal"

Do we really want to break that model by having two kinds of objects in a "contact"-annotated folder?

David Faure -- faure at kde.org, dfaure at klaralvdalens-datakonsult.se
Qt/KDE/KOffice developer
Klarälvdalens Datakonsult AB, Platform-independent software solutions

More information about the format mailing list