We have considered how we could align our OMG Printing Facility model
with your comments on 5.5.5 printer-state. You might know that our
model and attributes are also strongly affected by DPA, so your DPA
oriented approach is easy to accept to our model.
> Comments:
>
> 2. "idle" should not indicate whether the Printer is accepting jobs or not,
> that is what the enabled attribute is for. So change the definition of
> idle to:
>
> idle The Printer is not processing any jobs.
>
> 3. Change the name of the "printing" state to "processing", so that
> the state may be used by Printers when interpreting, and by non-Printer
> output devices, like CD-ROM writers and fax-out. So change the definition
> to:
>
> processing The Printer is currently processing a job.
>
> 4. "needs-attention" may now need special training, since needs-attention
> is for any reason that the Printer needs human attention. Also the operator
> may have paused the printer or the job may contain instructions to stop
> the printer and wait for human interaction. So change the definition of
> needs-attention to:
>
> needs-attention The Printer needs human attention. This state typically
> includes adding paper, clearing a jam, changing the medium, etc. It also
> includes when a system operator has paused the printer or the job contains
> special instructions to stop the printer at a particular point in the job
> to wait for operator or end-user interaction, such as installing special
> forms or entering a password. The printer-state-reasons and
> printer-state-message printer attributes give further information about why
> the output device needs attentions.
>
> 5. I also believe that we need the ISO DPA "shutdown" state, which indicates
> that the Printer has been shutdown. It seems too surprising to end-users
> to indicate a shutdown condition as a printer-state-reason when the printer
> is in the needs-attention or idle states. So bring back "shutdown":
>
> shutdown The Printer has been taken out of service, (for a long time),
> whether for repairs or others reasons. The Printer's printer-state message
> attribute may be used to record a reason and estimated time for return to
> service.
Most of the differences between our previous state model and your's are
on the name descriptions.
Tom's States Ricoh's States Comments
============================================================================
shutdown power-off Same meaning
processing executing Same meaning
needs-attention error needs-attention and needs-key-operator included
unknown unknown Same meaning
idle idle Same meaning
Assuming IPP may be one of the candidates for implementation of
OMG Printing Facility, we slightly changed our Device STD to be
a superset of IPP printer states as follows,
/----------\ /----------\
| shutdown | | unknown |
\----------/ \----------/
| ^
| |
/------+------------- active -------------------\
| | |
| V |
| /------------\ /-- needs-attention --\ |
| | initialize |<-+ | | |
| \------------/ | | /-- error --------\| |
| | +--+->| || |
| | | | (needs-key-op) || |
| /----+-----------\ | | || |
| | V | | | (connect-to-p) || |
| | /----------\ |<--+->| || |
| | | idle | | | | (timeout) || |
| | \----------/ | | | || |
| | | ^ | | \-----------------/| |
| | | | | | | |
| | V | | | | |
| | /------------\ | | /----------\ | |
| | | processing | |<--+->| paused | | |
| | \------------/ | | \----------/ | |
| | | | | |
| \--operational---/ \---------------------/ |
| |
\-----------------------------------------------/
Device State Transition Diagram
(in OMG Printing Facility submission by Ricoh)
Although we know the 'initialize' state is not defined by DPA, we added
it because print client might select other 'operational' device and start
printing quickly. Today's almost available printers have some warm-up time.
I suppose the 'initialize' could be included in 'idle' state in IPP
model, right?
> By the way, the OMG Print Facility standards project is on the same
> schedule as IPP and is trying to align with IPP, so this above discussion
> on printer states relates to work they are currently doing. So I hope we
> can get closure on these printer attributes soon in order to keep the two
> developing standards aligned.
We would be so happy to make liaison with IPP Working Group. I hope our
new Device STD is well aligned to IPP printer-state attributes.
Thanks,
-- Tetsuya Morita Ricoh Company Ltd. Printer Business Center