attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Apple has prototyped all of the finishings enum values and the template, fold, staple, and punch functionality of the finishings-col attribute in the following prototype draft of IPP Finishings 2.0:<div><br></div><div> <a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfinishings20-20140509.pdf">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfinishings20-20140509.pdf</a></div><div><br></div><div>A few observations:</div><div><br></div><div>1. Designing UI for specific finishings-col finishing types is quite difficult due to the number of moving parts. We suspect any UI that provides direct control over the parameters will necessarily be for expert users only.</div><div><br></div><div>2. The extension of finishing-template to include keywords as well as names should allow for simpler UI that vends standard and "pre-composed" finishing operations created by vendors and/or local experts.</div><div><br></div><div>3. We should make it clear that finishings-col-ready is potentially READ-WRITE, and/or introduce a finishings-col-database that can store pre-composed finishing operations. The latter may be a better fit since the semantics of -ready imply that the finisher subunits are ready/available.</div><div><br></div><div>I will post a proposal for finishings-col-database for inclusion in the stable draft of IPP Finishings 2.0.</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; 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-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; 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-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></body></html>