attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Greetings,<div class=""><br class=""></div><div class="">In the process of doing final evaluation of FIN2 leading up to voting, some questions have arisen about the “finishings-col-default” attribute that I wanted to discuss on the reflector.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">1. How would “finishings-col-default” provide an equivalent to “finishings” == ‘none’? PWG 5100.3 makes no restriction on what can be in “finishings-col-default”, so from a 5100.3 perspective this would be legitimate:</div><div class=""><br class=""></div><div class="">finishings-col-default = { finishing-template = ’none’ }</div><div class=""><br class=""></div><div class="">FIN2 section 6.9 doesn’t seem to disallow including an entry in “finishings-col-database” like the one above, but for some reason ’none’ not included in the following statement in 6.9 lines 1079-1081:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">Printers SHOULD report "finishings-col-database" values for each "finishings-supported" value other than 'none', and MAY report multiple instances with the same "finishing- template" value but different "media-size" or "media-size-name" values.</div></blockquote><div class=""><br class=""></div><div class="">I don’t get why “other than ‘none’” was included here. Presumably a Client would never need to even consult such an entry since the meaning of ‘none’ should be well-understood by a client that properly implements 5100.3 and FIN2, that knows to start with finishings-XXX and then go to finishings-col-XXX if more details are needed? If so that should be called out more clearly (maybe in the IPP Implementor’s Guide v2 but better if it is in the FIN2 spec itself).</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">2. I don’t quite understand why “finishings-col-default” would ever be needed or need to have sub-attributes other than “finishing-template”? I guess it is conceivable that the default may be custom settings not described in any entry in “finishings-col-database”, but is that kind of flexibility really a good thing? It adds complexity to a Client for that corner case.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">3. There seems to be no requirement that “finishings-default” and “finishings-col-default” need to be synchronized - is this an oversight?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">4. Related to #3, it may be that “finishings-col-default” has its “finishing-template” value set to a “name(MAX) value, which isn’t allowable in “finishings-default”. In this case, what should the value be set to in “finishings-default”?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Thoughts?</div><div class=""><br class=""></div><div class=""><div class="">
<div style="color: rgb(0, 0, 0); font-family: Arial; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class="">Smith<br class=""><br class="">/**<br class=""> Smith Kennedy<br class=""> Hewlett-Packard Co.<br class="">*/</div>
</div>
<br class=""></div></body></html>