Comments on the proposed resolution to the IPP/1.1 issue concerning the
semantics of the Printer object's "printer-state" and
"printer-state-reasons" attributes had been raised on the mailing list as WG
Last Call comments. At the IPP WG meeting on 5/26-27 we agreed to the
following resolution to these comments.
The editors will be updating the IPP/1.1 Model and Semantics document and
the Encoding and Transport document to reflect these agreements. Any
comments should be send to the mailing list by Thursday, June 10, 1999.
Then the resulting documents will be sent as Internet-Drafts on Friday, June
11, 1999 for review by the IESG as proposed standards.
ISSUE 31: How indicate a ripped job that is waiting for the marker?
Simplified "printer-state" descriptions that preserves IPP/1.0
compatibility, including fan-out, while allowing multiple rips with a
4.4.14 printer-state (type1 enum)
This REQUIRED Printer attribute identifies the current state of the device.
The "printer-state reasons" attribute augments the "printer-state" attribute
to give more detailed information about the Printer in the given printer
A Printer object need only update this attribute before responding to an
operation which requests the attribute; the Printer object NEED NOT update
this attribute continually, since asynchronous event notification is not
part of IPP/1.1. A Printer NEED NOT implement all values if they are not
applicable to a given implementation.
The following standard enum values are defined:
Value Symbolic Name and Description
'3' 'idle': Indicates that new jobs can start processing
'4' 'processing': Indicates that jobs are processing; new jobs
will wait before processing.
'5' 'stopped': Indicates that no jobs
can be processed and intervention is required.
Values of "job-state-reasons", such as [new] 'queue-full' and
'stopped-partly', MAY be used to provide further information.
Put the above deleted definitions for simple, multi-rip, and fan-out
configurations into the IIG. This deleted text appeared in the May
Internet-Drafts. Also discuss the difficulty of the simple IPP/1.1 Printer
object abstraction to represent a set of devices that have widely differing
capabilities, i.e., a color and a black and white printer.