IPP Mail Archive: RE: IPP> MOD> printer-state-reasons

IPP Mail Archive: RE: IPP> MOD> printer-state-reasons

RE: IPP> MOD> printer-state-reasons

Manros, Carl-Uno B (cmanros@cp10.es.xerox.com)
Fri, 17 Sep 1999 09:56:35 -0700

Ira,

I agree, it seems like this is one fix we should try to make before the
IPP/1.1 RFCs are published.

Carl-Uno

> -----Original Message-----
> From: Ira Mcdonald [mailto:imcdonal@sdsp.mc.xerox.com]
> Sent: Friday, September 17, 1999 7:52 AM
> To: ipp@pwg.org; kugler@us.ibm.com
> Subject: Re: IPP> MOD> printer-state-reasons
>
>
>
> Hi Carl and Tom, Friday (17
> September 1999)
>
> This suffix nonsense on 'printer-state-reasons' keywords was
> a mistake.
> And the MUST interpretation of 'error' when a suffix is not present is
> EXACTLY wrong. There are important printer state reasons that do NOT
> indicate warning or error events - sub-states like 'moving-to-paused',
> 'paused', 'shutdown', 'connecting-to-device'.
>
> And as Carl observed (below) 'none-error' is obviously broken.
>
> It's never an error for a printer to be 'paused'. It's a
> neutral report
> of a condition. No program error or resource problem has
> occurred. The
> printer is in a sub-state at the request of an authorized
> human user or
> operator.
>
> MOD should be corrected to say that a missing suffix SHALL mean that
> the specified state reason is of '-report' severity (or better yet,
> abandon suffixes entirely, but prior art won't really let us do that).
>
> Cheers,
> - Ira McDonald
> High North Inc
> 906-494-2697/2434
>
> >
> ----------------------------------------------------------------------
> > From: kugler@us.ibm.com
> > To: ipp@pwg.org
> > Date: Thu, 16 Sep 1999 14:00:13 -0600
> > Subject: IPP> MOD> printer-state-reasons
> >
> > MOD says:
> >
> > Each keyword value MAY have a suffix to indicate its
> level of severity.
> > The three levels are: report (least severe), warning,
> and error (most
> > severe).
> >
> > ...
> >
> > - '-error': This suffix indicates that the reason is
> an "error". An
> > implementation MUST include all errors. If this
> attribute contains
> > one or more errors, printer MUST be in the stopped state.
> >
> > If the implementation does not add any one of the three
> suffixes, all
> > parties MUST assume that the reason is an "error".
> >
> > Does this mean to say that the REQUIRED
> "printer-state-reasons" attribute
> > value must always have a -report or -warning suffix unless
> the printer is
> > in the 'stopped' state? For example, if the printer is idle, MUST I
> > have "printer-state" = 'idle' and "printer-state-reasons" =
> 'none-report'?
> > (Can't have "printer-state-reasons" = 'none' since that would be
> > semantically equivalent to "printer-state-reasons" =
> 'none-error' which
> > implies that the printer MUST be in the stopped state, not
> the idle state.)
> >
> > - Carl
> >
> >
> ----------------------------------------------------------------------
>
>