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;">Ira,<div><br><div><div>On Jun 20, 2014, at 2:59 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr"><div><div><div><div><div><div>Hi Mike,<br><br></div>I like this "printer-finisher" proposal for exposing the Finisher MIB info.<br><br></div>A few comments:<br><br>(1) TYPO - Section 6.15.3 in title and second example says "printer-input-tray"<br></div></div></div></div></div></blockquote><div><br></div>Oops, will fix that on the next pass... :/</div><div><br><blockquote type="cite"><div dir="ltr"><div><div><div>(2) TECHNICAL - Section 16.5 should also reference finDeviceAttributeTable<br></div>and later sections should reference a (flattened) "finisher-detail" member that<br>is a simple key/value mapping for all defined finisher-specific attributes, e.g.,<br>
</div><br>- general: deviceModel, finReferenceEdge, numberOfPositions, etc.<br>- subunit types: stitching (staple,stitch,saddle,dual), folding, binding, etc.<br></div><div>- subunit details for stitching and punching<br>
</div></div></blockquote><br></div><div>I'd actually like to defer these - the finishing intent attributes (finishings-supported, finishings-col-database/ready, etc.) already expose most of this information in a way that can be used by the Client. The only information we didn't have a way to get via IPP was the capacity of the finisher subunits - how many sheets can be stapled, etc.</div><div><br></div><div>Longer term (probably in System Control) we can expose things like deviceModel for use by management applications. But anything regarding capabilities should already be exposed by the new finishings-col stuff (and if not then we should add it there and not using the octetString key/value syntax).</div><div><br></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>