attachment
<div dir="ltr">For soft-proof-icc-profile, would this be obviated by the proof operations in Enterprise Print Extensions?<div><br></div><div>Regarding UI suggestions, it would seem to make sense to include these recommendations in a separate document as they don't pertain specifically to the proposed attributes.</div><div><br></div><div>I'm concerned that adding vendor extensions to print-color-mode will significantly complicate client applications attempting to render previews of content as the behavior is predictable now. I would prefer to add a standard value for printer-color-mode that indicates we defer to an advanced setting for color.</div><div><br></div><div>Sean</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 18, 2019 at 7:32 AM Ira McDonald via ipp <<a href="mailto:ipp@pwg.org">ipp@pwg.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi Smith,</div><div><br></div><div>Bit or arcana,</div><div><br></div><div>In Printer MIB and many other IETF MIBs, enum '1' is 'other' and '2' is 'unknown',</div><div>so we avoid them for compatibility in IPP as a rule.</div><div><br></div><div>Cheers,</div><div>- Ira</div><div><br></div><div><div><div dir="ltr" class="gmail-m_1526932805105548713gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG</div><div>Co-Chair - TCG Metadata Access Protocol SG<br></div><div dir="ltr">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>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></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 17, 2019 at 9:41 PM Kennedy, Smith (Wireless & Standards Architect) via ipp <<a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br>
<div><br><blockquote type="cite"><div>On Apr 17, 2019, at 5:40 PM, Michael Sweet <<a href="mailto:msweet@msweet.org" target="_blank">msweet@msweet.org</a>> wrote:</div><br class="gmail-m_1526932805105548713gmail-m_5020134672147159841Apple-interchange-newline"><div><span style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">Some quick comments:</span><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><br></div><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">1. The tooltip stuff in strings files should be a separate Best Practice. Yes it will be mostly boilerplate... :(</div></div></blockquote><div><br></div>OK. Can reference that from this doc.</div><div><br><blockquote type="cite"><div><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><br></div><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">2. print-color-mode-default: Drop</div></div></blockquote><div><br></div>I'm interpreting this to mean to remove it from this document, since it is already defined in 5100.13?</div><div><br></div><div><blockquote type="cite"><div><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><br></div><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">3. print-color-mode-supported: Should be print-color-mode</div></div></blockquote><div><br></div>I'm interpreting this to mean just relabel the sub-section to be "print-color-mode"?</div><div><br></div><div>FWIW, I've been struggling with a related stylistic concern. If one is defining an attribute, say that specifies a keyword type syntax, and there are standard keywords defined as well, should those standard keyword definitions be made in the "xxx-supported" or "xxx" subsection?</div><div><br><blockquote type="cite"><div><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><br></div><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">4. print-quality enum extensions: enums are not supposed to use values 1 and 2... :( </div></div></blockquote><div><br></div><div>Hum - I always puzzled over that. Why is that? Whatever the reason, we need to capture the reason for that in our as-yet-to-be-started IPP Design Patterns document...</div><br><blockquote type="cite"><div><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">Maybe we could look at a "print-quality-col (collection)" attribute with more details? Or define a separate range (10-19?) representing 10 different vendor-specific qualities?</div></div></blockquote><div><br></div><div>I'd probably tend toward the latter since that attribute is already widely supported, and I don't know what other fields a "print-quality-col" might provide. Let's see if others have thoughts on that.</div><br><blockquote type="cite"><div><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><br></div><div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><br><div><br><blockquote type="cite"><div>On Apr 17, 2019, at 2:10 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp <<a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a>> wrote:</div><br class="gmail-m_1526932805105548713gmail-m_5020134672147159841Apple-interchange-newline"><div><div>Greetings,<div><br></div><div>I just posted a first draft of a "IPP Custom Print Quality and Intent Extensions</div>(CUSTOMPQI)" white paper that proposes some additions to IPP that relate to supporting print quality hint and settings additions.<br><div><br></div><div> <span class="gmail-m_1526932805105548713gmail-m_5020134672147159841Apple-converted-space"> </span><a href="https://protect-us.mimecast.com/s/W969CG6xjxhMD2MKTK84n2?domain=ftp.pwg.org" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/whitepaper/white-hp-ipp-custompqi-20190412.pdf</a> <br> <span class="gmail-m_1526932805105548713gmail-m_5020134672147159841Apple-converted-space"> </span><a href="https://protect-us.mimecast.com/s/iQcRCJ6AmAhY6gY3hGy9KW?domain=ftp.pwg.org" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/whitepaper/white-hp-ipp-custompqi-20190412.docx</a> </div><div><br></div><div>We won't likely have time to review it at our April 2019 F2F in a session, but I encourage those at the F2F to take a look at it so we can discuss after hours, etc. if you have an interest in what it proposes.</div><div><br></div><div>Cheers,</div><div><div>Smith<br><br>/**<br> Smith Kennedy<br> HP Inc.<br>*/</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://protect-us.mimecast.com/s/CCdKCKrBnBFnXZnzc3PXr6?domain=pwg.org" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br></div></blockquote></div><br><div><span class="gmail-m_1526932805105548713gmail-m_5020134672147159841Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;border-spacing:0px"><div><div>_____________<br>Michael Sweet</div></div></span></div></div></div></blockquote></div><br></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" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></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" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Sean Kau</div></div>