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;">All,<div><br></div><div>Something I've been thinking about for IPP Finishings 2.0 is the notion of "presets" for finishings-col - there is already a "template-name" member attribute, but what about combining multiple finishings for standard post-processing (e.g., booklet + cover + saddlestitch + bale)?</div><div><br></div><div>There is also the question of default values - right now we don't have a "finishings-col-database" attribute that provides the defaults for each template-name. But there is a finishings-col-ready attribute. Should we add a finishings-col-database attribute to list all of the defaults for each template-name? Or is finishings-col-ready sufficient?</div><div><br></div><div>I think we should make it clear that the presence of the corresponding member attribute is what activates a particular finisher and not the use of a specific template-name - that will make it clear that vendor, user, or site-defined template-name values can apply one or more finishing options just by setting the corresponding member attributes (stitching, punching, folding, etc.) And by having finishings-col-ready/database there with all of the details, it will be possible for Client UI to visually simulate the results of finishing instructions in addition to the usual selection-by-name.</div><div><br></div><div>Thoughts?</div><div><br></div><div><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>