Larry Masinter wrote:
You might also want to scan your email for "event invitations from my
boss",
and you can't solve that problem with specialized MIME media types. So the
question is: are there any realistic cases where having a "text/calendar"
distinction in the email header actually helps substantially in deciding
which email bodies to retrieve?
Actually, the current MIME content type definition for "text/calendar"
provides for MIME header parameter that CUAs are using to scan the inbox for
the "new invitations". This is what gave me concern when I read the content
type definition for text/xml and application/xml. It doesn't allow an
application to detect what kind of XML object is in the email. For our
application area, it is disfunctional. It is imparing the use of XML for
representing iCalendar objects (and certainly other application objects
too).
- - Frank