Good catch. Tom Hastings and I also found that some "text"
attributes (like xxx-state-message) were being erroneously
conveyed in strict US-ASCII while we were working through
issues around the simplifications for localization that you
(Bob) proposed during Wednesday afternoon's IPP telecon.
I agree that we should either remove the Event Notification
content from the spec OR fix it to use IPP standard encoding
format. Note however, that doing reverse HTTP (from a
server TO a client) for notification is not a trivial
burden for clients to absorb.
We certainly have to fix it or remove it from IPP/1.0.
- Ira McDonald (outside consultant at Xerox)
------------------------ Bob's note -------------------------
Return-Path: <ipp-owner at pwg.org>
Received: from zombi (zombi.eso.mc.xerox.com) by snorkel.eso.mc.xerox.com (4.1/XeroxClient-1.1)
id AA20235; Thu, 16 Oct 97 21:46:40 EDT
Received: from alpha.xerox.com by zombi (4.1/SMI-4.1)
id AA01984; Thu, 16 Oct 97 21:42:22 EDT
Received: from lists.underscore.com ([220.127.116.11]) by alpha.xerox.com with SMTP id <53179(1)>; Thu, 16 Oct 1997 18:42:25 PDT
Received: from localhost (daemon at localhost) by lists.underscore.com (8.7.5/8.7.3) with SMTP id VAA00516 for <imcdonal at eso.mc.xerox.com>; Thu, 16 Oct 1997 21:38:56 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Thu, 16 Oct 1997 21:36:11 -0400
Received: (from daemon at localhost) by lists.underscore.com (8.7.5/8.7.3) id VAA00154 for ipp-outgoing; Thu, 16 Oct 1997 21:25:53 -0400 (EDT)
Date: Thu, 16 Oct 1997 18:23:34 PDT
From: Robert.Herriot at Eng.Sun.COM (Robert Herriot)
Message-Id: <199710170123.SAA03809 at woden.eng.sun.com>
To: ipp at pwg.org
Subject: IPP>MOD Concern about Event Notification Content
Sender: ipp-owner at pwg.org
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.