...jay
Robert Herriot wrote:
>
> I just noticed that the IPP model document now has an Event Notification
> Content attribute whose format is US-ASCII even though it is intended
> for machine consumption.
>
> I am concerned about freezing this format into the standard because
> I think that it is a mistake.
>
> I suggest that the format of this message should be in the IPP protocol
> format so that the notification content can represent whatever the
> protocol can represent. Text in different languages is one thing
> that comes to mind.
>
> This means that for HTTP, the content would go as an application/ipp
> entity in an HTTP request and we need a new IPP operation called "notify".
>
> For email, it could go as a Multipart/alternative with one part
> text/plain whose content is specified but whose format is unspecified
> and with another part which is application/ipp. Alternatively, we
> could have two variants of email, one for human consumption and one
> for machine consumption.
>
> Although we may be too late in the process to solve this problem as I
> have suggested, it is not too late to remove the specification of the
> Event Notification Content so that we don't freeze a mistake.
>
> Bob Herriot