Bob and others that have responded to Bob's message,
My view is that it would be highly undesirable to just take out the whole
concept of notifications, about which we have had general agreement right
from the start of the project. Also, trying to leave out the format
specification while keeping the attributes etc., I do not think is going to
fly when the IESG reviews the document. Looking at the actual text that we
are discussing, it seems that there are about 30 lines of text starting
with line number 1752 (from the PDF version of Scott's latest draft).
Reading through that, I think that we have most of the right semantics in
there already, except for an inconsistent statement about the use of ASCII.
We should not throw out the baby with the bath water!
My suggestion is to rewrite the text in these 30 lines and instead create
an additional MIME type called "application/ipp-notification", which
contains the right language and encoding for I18N in the right places,
building on what we currently have. This MIME type could be carried in
SMTP, over HTTP, or other protocols.
This does not seem such a major job. I do not think it would be a problem
to work out the details within a week.
Comments? Volonteers?
Carl-Uno
Carl-Uno Manros
Principal Engineer - Advanced Printing Standards - Xerox Corporation
701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231
Phone +1-310-333 8273, Fax +1-310-333 5514
Email: manros@cp10.es.xerox.com