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 May 23, 2014, at 11:21 AM, 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>Hi Smith,<br><br></div>Actually, the Printer doesn't have to bind values to "xxx-actual" until the Job<br>completes.<br><br></div>This reply is not about 'guaranteed'.<br>
<br></div>This reply is about the usability of 'attempted'.<br><br>An IPP Client could use Validate-Job with "document-format" and "pdl-override" and,<br>when it receives the response that says ignored or substituted, examine the values <br>
of "preferred-attributes" (from JPS3, PWG 5100.13-2012) to find out the extent to <br>which the Printer *could* and *could not* successfully 'attempt' to do the overrides.<br></div></div></div></blockquote><div><br></div>Well, if a Client sends "ipp-attribute-fidelity" (not "pdl-override"), then Validate-Job needs to respond just like Create-Job/Print-Job/Print-URI. So in that case "preferred-attributes" doesn't enter into the picture.</div><div><br></div><div>Instead, the Client would need to *omit* "ipp-attribute-fidelity" to see which overrides are supported. Then you'll get the unsupported attributes/values and potentially the ones that would be used instead.</div><div><br></div><div>Based on my own experience, I'm not sure how useful/reliable this method would be, but we can certainly document it.</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>