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; line-break: after-white-space;" class=""><br class="">
<div><br class=""><blockquote type="cite" class=""><div class="">On Apr 17, 2019, at 5:40 PM, Michael Sweet <<a href="mailto:msweet@msweet.org" class="">msweet@msweet.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Some quick comments:</span><div class="" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 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 class=""></div>OK. Can reference that from this doc.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;">2. print-color-mode-default: Drop</div></div></blockquote><div><br class=""></div>I'm interpreting this to mean to remove it from this document, since it is already defined in 5100.13?</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;">3. print-color-mode-supported: Should be print-color-mode</div></div></blockquote><div><br class=""></div>I'm interpreting this to mean just relabel the sub-section to be "print-color-mode"?</div><div><br class=""></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 class=""><blockquote type="cite" class=""><div class=""><div class="" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;">4. print-quality enum extensions: enums are not supposed to use values 1 and 2... :( </div></div></blockquote><div><br class=""></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 class=""><blockquote type="cite" class=""><div class=""><div class="" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 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 class=""></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 class=""><blockquote type="cite" class=""><div class=""><div class="" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); 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; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Apr 17, 2019, at 2:10 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp <<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Greetings,<div class=""><br class=""></div><div class="">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 class=""><div class=""><br class=""></div><div class=""> <span class="Apple-converted-space"> </span><a href="https://protect-us.mimecast.com/s/W969CG6xjxhMD2MKTK84n2?domain=ftp.pwg.org" class="">https://ftp.pwg.org/pub/pwg/ipp/whitepaper/white-hp-ipp-custompqi-20190412.pdf</a> <br class=""> <span class="Apple-converted-space"> </span><a href="https://protect-us.mimecast.com/s/iQcRCJ6AmAhY6gY3hGy9KW?domain=ftp.pwg.org" class="">https://ftp.pwg.org/pub/pwg/ipp/whitepaper/white-hp-ipp-custompqi-20190412.docx</a> </div><div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">Cheers,</div><div class=""><div class="">Smith<br class=""><br class="">/**<br class=""> Smith Kennedy<br class=""> HP Inc.<br class="">*/</div><br class=""></div></div>_______________________________________________<br class="">ipp mailing list<br class=""><a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class=""><a href="https://protect-us.mimecast.com/s/CCdKCKrBnBFnXZnzc3PXr6?domain=pwg.org" class="">https://www.pwg.org/mailman/listinfo/ipp</a><br class=""></div></blockquote></div><br class=""><div class=""><span class="Apple-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-variant-position: 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; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div class="">_____________<br class="">Michael Sweet</div></div></span></div></div></div></blockquote></div><br class=""></body></html>