[IPP] media-input-tray-check-default

[IPP] media-input-tray-check-default

[IPP] media-input-tray-check-default

Ira McDonald blueroofmusic at gmail.com
Tue Jan 24 17:45:07 UTC 2012


Hi Mike,

Thanks - I agree w/ Pete about the advantages of
option 2 - and this is a more backward compatible
solution than actually deleting a previously registered
(and apparently implemented) IPP attribute.

The 'no-value' approach to special "xxx-default"
attributes is elegant.

Cheers,
- Ira



Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com
Winter  579 Park Place  Saline, MI  48176  734-944-0094
Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434



On Tue, Jan 24, 2012 at 11:52 AM, Michael Sweet <msweet at apple.com> wrote:

> OK, I'm convinced.  I'll add "no-value" to this one and any others like it
> where it would not always make sense to force a default value.
>
>
> On Jan 24, 2012, at 4:33 AM, Zehler, Peter wrote:
>
> Mike,****
> I prefer option #2.  One of my reason is that it allows the operator to
> set policy for underspecified jobs on the printer.  (If the client is not
> being careful, then the printer will.)  It is a very handy feature in
> production printing.****
> Pete****
> ** **
> Peter Zehler
>
> Xerox Research Center Webster
> Email: Peter.Zehler at Xerox.com
> Voice: (585) 265-8755
> FAX: (585) 265-7441
> US Mail: Peter Zehler
> Xerox Corp.
> 800 Phillips Rd.
> M/S 128-25E
> Webster NY, 14580-9701****
> ** **
> *From:* ipp-bounces at pwg.org [mailto:ipp-bounces at pwg.org] *On Behalf Of *Paul
> Tykodi
> *Sent:* Tuesday, January 24, 2012 6:11 AM
> *To:* ipp at pwg.org
> *Subject:* RE: [IPP] media-input-tray-check-default****
> ** **
> Hi Mike,****
> ** **
> For production printing, I have found during my career that it is critical
> to have automatic checks and balances within the job submission workflow so
> that a very large job (with a significant cost of production) is not
> released such that it will be printed on incorrect media and thus be a
> total loss (i.e. must be destroyed and cannot be distributed – job must be
> run again). The AFP Consortium has the same type of intelligence in their
> Intelligent Printer Data Stream specification as we have in IPP.****
> ** **
> I think it is possible that some vendors may have interpreted the
> description in the specification to mean that the default value should
> refer to the function being enabled or disabled. If it is enabled, it then
> interacts with the media in the job ticket I therefore prefer option #2 to
> resolve this issue.****
> ** **
> Best Regards,****
> ** **
> /Paul****
> --****
> Paul Tykodi
> Principal Consultant
> TCS - Tykodi Consulting Services LLC
>
> Tel/Fax: 603-343-1820
> Mobile:  603-866-0712
> E-mail:  ptykodi at tykodi.com
> WWW:  http://www.tykodi.com****
> *From:* ipp-bounces at pwg.org [mailto:ipp-bounces at pwg.org] *On Behalf Of *Michael
> Sweet
> *Sent:* Monday, January 23, 2012 6:14 PM
> *To:* ipp at pwg.org
> *Subject:* [IPP] media-input-tray-check-default****
> ** **
> All,****
> ** **
> I am going through yet another round of updates to the IANA registry (this
> time for sure! :), and noticed that I still have the
> media-input-tray-check-default attribute tagged as "under review". I would
> like to resolve this before we submit our next round of updates to the
> registry.****
> ** **
> BACKGROUND****
> ** **
> PWG 5100.3 (Production Printing Set 1) defines the media-input-tray-check
> Job Template attribute thusly:****
> ** **
>
> The “media-input-tray-check” Job Template attribute indicates that the
> Printer MUST check that the characteristics of the media in the identified
> input tray are the same as characteristics of the media identified by the
> Job's "media" Job Template attribute or matched (see section 3.13) by the
> Job's "media- col" Job Template attribute. The keyword values are the same
> input tray keyword values as are defined for the "media" Job Template
> attribute (see section 6.3 in this document and [RFC2911] Appendix C),
> i.e., 'top', 'middle', 'bottom', etc.****
> ** **
> Independent of the "ipp-attributes-fidelity" operation attribute supplied
> by the client, if the characteristics differ, the Printer adds the
> ‘resources-are-not-ready’ value (see section 6.1) to the job's
> "job-state-reasons" attribute and MAY either (1) put the job into the
> ‘pending-held’ state or (2) start to process the job normally, but
> immediately stop the job (“job-state” = ‘processing-stopped’) and the
> Printer (“printer-state” = ‘stopped’). In either implementation, the
> operator can change the media in the input tray to agree with the job or
> can modify the job’s “media” or “media-col” attributes to agree with the
> input tray, depending on policy.****
>
> ** **
> Table 1 (at the beginning of section 3) defines
> media-input-tray-check-default and -supported.****
> ** **
> The issue is that there should not be a default media-input-tray-check
> value; like some other Job Template attributes (e.g. overrides), it does
> not make sense to have a default value for this particular attribute since
> it interacts with the media in the job ticket.****
> ** **
> There are two ways to resolve this issue:****
> ** **
> 1. Drop media-input-tray-check-default from the registry and post an
> errata for 5100.3 removing the media-input-tray-check-default attribute
> from Table 1.****
> ** **
> 2. Update the definition of media-input-tray-check-default to include the
> "no-value" out-of-band value.****
> ** **
> I prefer option #1.****
> ** **
> Comments?****
>  ****
> ________________________________________________________________________**
> **
> Michael Sweet, Senior Printing System Engineer, PWG Chair****
> ** **
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.****
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.****
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean. _______________________________________________
> ipp mailing list
> ipp at pwg.org
> https://www.pwg.org/mailman/listinfo/ipp
>
>
> __________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>
> _______________________________________________
> ipp mailing list
> ipp at pwg.org
> https://www.pwg.org/mailman/listinfo/ipp
>
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20120124/4017e3ad/attachment-0001.html>


More information about the ipp mailing list