attachment
<div dir="ltr"><div><div><div><div><div><div>Hi Smith,<br><br></div>I agree with Mike's much simpler definitions.<br><br></div>I don't like this explicit ordering from "top" to "bottom" bin, because<br>
</div>it's hardware architecture specific and doesn't even mean anything<br></div>if the only two bins are side by side (they sometimes are).<br><br></div>Cheers,<br></div>- Ira<br><br></div><div class="gmail_extra">
<br clear="all"><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div>
<div></div><div></div><div></div><div></div></div></div>
<br><br><div class="gmail_quote">On Wed, Jul 9, 2014 at 5:20 PM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">I'm still not sure about the explicit ordering (top to bottom); let's see if others have a problem with it...<div><br></div><div>(also, "or copy job" doesn't make sense since we have no copy service in IPP...)</div>
<div><div class="h5"><div><br></div><div><br><div><div>On Jul 9, 2014, at 5:01 PM, Kennedy, Smith (Wireless Architect) <<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>> wrote:</div><br>
<blockquote type="cite"><div style="word-wrap:break-word">Fair enough. :) How about this:<div><br></div><div><div style="font-family:ArialMT">‘job-separator’</div><div style="font-family:ArialMT">Jobs are delivered to an available (empty) output bin, starting from the top bin and continuing to the bottom bin. If no bins are empty, a job is delivered first to the top bin and, if the top bin is full, then to subsequent bins, continuing to the bottom bin.</div>
<div style="font-family:ArialMT"><br></div><div style="font-family:ArialMT">’collator’</div><div style="font-family:ArialMT">Each copy of a single print or copy job is delivered to a separate output bin, starting with the top bin and continuing to the bottom bin. When a copy is delivered to the lowest bin, the next copy is delivered to the top bin and the delivery process is repeated.</div>
<div><br></div><div><br></div><div><br><div><div>
Smith<br><br><br>
</div>
<br><div><div>On 2014-07-09, at 2:40 PM, Michael Sweet <<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>> wrote:</div><br><blockquote type="cite"><div style="word-wrap:break-word">No objections here, although the descriptions could be made simpler and less tied to a particular implementation, e.g.:<div>
<br></div><div> 'job-separator'; All of the output for the job is placed in an empty output tray. If no trays are empty, the Printer chooses an output tray in an implementation-defined manner.</div><div><br></div>
<div> 'collator'; Each copy is placed in an empty output tray. If all trays are full, the Printer cycles through each of the trays in an implementation-defined manner.</div><div><br></div><div>Since you can only specify one "output-bin" value, I don't think you need the "When this mode is selected" user manual verbiage.</div>
<div><br></div><div><br><div><div>On Jul 8, 2014, at 1:19 PM, Kennedy, Smith (Wireless Architect) <<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>> wrote:</div><br><blockquote type="cite">
<div style="word-wrap:break-word">Greetings,<div><br></div><div>Hewlett-Packard would like to request that 2 new keywords be defined for the “output-bin” attribute defined in PWG 5100.2: ‘job-separator’ and ‘collator’. Each of them are described below.</div>
<div><br></div><div>‘job-separator’</div><div>Jobs are delivered to an available (empty) output bin (a job can include the original and its copies), starting from the top bin and continuing to the bottom bin. If no bins are empty, a job is delivered first to the top bin and, if the top bin is full, then to subsequent bins, continuing to the bottom bin. The bin that the job is sent to is considered the destination bin. When the Job Separator mode is selected, you cannot select which bin to send your job to.</div>
<div><br></div><div>’collator’</div><div>Each copy of a single print or copy job is delivered to a separate output bin, starting with the top bin and continuing to the bottom bin. When a copy is delivered to the lowest bin, the next copy is delivered to the top bin and the delivery process is repeated. When this mode is selected, you cannot select which bin to send your job to.</div>
<div><br></div><div>Please reply with any comments or questions. We can discuss these briefly in the next IPP WG con call,</div><div><br></div><div>Cheers,</div><div><div>
<div style="font-family:Arial;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
Smith<br><br>/**<br> Smith Kennedy<br> Hewlett-Packard Co.<br>*/</div>
</div>
<br></div></div>_______________________________________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br><a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></div><br><div>
<span style="border-collapse:separate;font-family:'Andale Mono';border-spacing:0px"><span style="border-collapse:separate;font-family:'Andale Mono';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;border-spacing:0px"><div style="word-wrap:break-word">
_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></div></blockquote></div><br></div></div></div></div></blockquote></div><br><div>
<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;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><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;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="word-wrap:break-word">
_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></div></div></div><br>_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
<br></blockquote></div><br></div>