Building on your idea...
How about making your first part (vendor proprietary) be a mail attachment
in whatever media type the vendor wants or defines?
Make your second part be the text/plain body of the mail message
and be human readable in any format (hopefully in the language of the
user, but in a charset that the transport system can handle).
When the PWG agrees (soon after IPP V1.0) to a media type for notification
purposes, the Printer vendor can include that as an attachment as well.
If he had a proprietary media type, he can attach both as separate
Then we have a good migration path as you urge, correct?
At 09:52 10/21/1997 PDT, Larry Masinter wrote:
>If event notifications are supplied in a multipart/alternative,
>with, for example, the first part being the vendor's proprietary notification
>format, and the second in text/plain, then
>there will be a cleaner migration path than if only a single
>part is expected by recipients of notifications.