attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Barry,<div><br></div><div>Thanks for your feedback. Response below.</div><div><br><div><div>On Sep 13, 2013, at 9:13 AM, Barry Cavill <<a href="mailto:bcavill@lexmark.com">bcavill@lexmark.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr">"The actual methods of measurement and limit enforcement" are considered
out-of-scope for the specification, which is fine. However, perhaps
there should be a job-state-reason to indicate that the user's job is
rejected for a measurement other than limit enforcement... for example,
the user isn't authorized for color printing, or for printing on photo
paper, or some similar scenario. <br clear="all"></div></blockquote><div><br></div><div>In general, such things would be detected when the job is submitted, however since we *do* define "job-state-reasons" keywords for many of the client-error-xxx status codes, how about the following additions?</div></div><div><br></div><div> Status Code "job-state-reasons" Keyword</div><div> ----------------------------------------------- ----------------------------------</div><div> client-error-attributes-or-values-not-supported 'unsupported-attributes-or-values'</div><div> client-error-conflicting-attributes 'conflicting-attributes'</div><div><br></div><div>Unfortunately, we don't have a place to store the actual unsupported attributes and values after the response, but at least the client would know there was a problem and the "job-state-message" attribute could provide a localized reason with specifics...</div><div><br></div><div><span style="orphans: 2; text-align: -webkit-auto; widows: 2;">_________________________________________________________</span></div><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 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; ">Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></body></html>