MIME type for distribution lists
joon at radleys.co.za
Thu Jun 2 11:48:42 CEST 2005
I understand your reasoning on a folder basis, but this is a completely
different object to the contact object. Maybe we could sub type it to
Radley Network Technologies CC
Cell: +27 (0)83 368 8557
Fax: +27 (0)12 998 4346
E-mail: joon at radleys.co.za
> -----Original Message-----
> From: kolab-format-bounces at kolab.org
> [mailto:kolab-format-bounces at kolab.org] On Behalf Of David Faure
> Sent: Thursday, June 02, 2005 11:30 AM
> To: kolab-format at kolab.org
> Subject: Re: MIME type for distribution lists
> 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
> Kolab-format mailing list
> Kolab-format at kolab.org
More information about the format