attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Daniel,<div><br></div><div>Thank you for your comments. My initial responses are inline below...</div><div><br><div><div><div>On Aug 30, 2013, at 1:27 AM, Manchala, Daniel <<a href="mailto:Daniel.Manchala@xerox.com">Daniel.Manchala@xerox.com</a>> wrote:</div><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
<div ocsi="0" fpstyle="1">
<div style="direction: ltr; font-family: Tahoma; font-size: 10pt;"><font size="2" face="Helvetica">Xerox has reviewed the IPP Transaction-Based Printing Extensions specification and has the following comments.<br>
<br>
Xerox would like to add a new "job-state-reason" to <span style="font-size: 11pt; color: rgb(31, 73, 125);">
section 8.1 “job-state-reasons (1setOf type2 keyword)”: “incompatible account-information”. This account (“job-account-id”) is not associated with the user (“job-accounting-user-id”).</span><i><span style="font-size: 11pt; color: rgb(31, 73, 125);"></span></i><span style="font-size: 11pt; color: rgb(31, 73, 125);">
<br></span></font></div></div></blockquote><div><br></div>No objection, although we need a proper keyword value. 'account-info-conflicting'?</div><div><br></div><div><blockquote type="cite" dir="auto"><div ocsi="0" fpstyle="1"><div style="direction: ltr; font-family: Tahoma; font-size: 10pt;"><font size="2" face="Helvetica"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Likewise, add a new associated status-code to section 8.2 "client-error-account-information-incompatible" (or something of that nature).<br></span></font></div></div></blockquote><div><br></div>In this case I'd prefer to keep using client-error-conflicting-attributes and have the printer return the job-account-id and job-accounting-user-id attributes in the unsupported attributes group.</div><div><br><blockquote type="cite" dir="auto"><div ocsi="0" fpstyle="1"><div style="direction: ltr; font-family: Tahoma; font-size: 10pt;"><font size="2" face="Helvetica"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Add an attribute: “job-account-type (type2 keyword | name(MAX))<Job Template>” along with “job-account-type-supported(1setOf type2 keyword | 1setOf name(MAX))<Printer>” and “job-account-type-default(type2
keyword | name(MAX))<Printer>”. The keywords initially can start with ‘none’, ‘general’, ‘group’ or ‘visa-card’, ‘master-card’, ‘paypal’,’bit-coin’, ‘micro-mint’, ‘cash’, ‘credit-account’, etc., . The preference is to use keywords as it aids in the internationalization.
<br></span></font></div></div></blockquote><div><br></div>We've very specifically avoided currency or payment identifiers since a) many members, including Xerox, have indicated that payment processing is done separately from the printer and b) we have no facility in IPP to express currency values or other complex, fractional types.</div><div><br></div><div>What would be the purpose of adding this when the printer-charge-info and printer-charge-info-uri values provide localized resources that can be displayed by the Client? Since the Client never has to have knowledge of how transactions are processed (just whether the printer needs transactional information), and since job-account-id will not (or at least SHOULD NOT) be a credit card number or other direct payment identifier, I don't see the point in telling the Client anything other than "I need a job-account-id from the user."</div><div><br><blockquote type="cite" dir="auto"><div ocsi="0" fpstyle="1"><div style="direction: ltr; font-family: Tahoma; font-size: 10pt;"><font size="2" face="Helvetica"><span style="font-size: 11pt; color: rgb(31, 73, 125);">
</span></font><font size="2" face="Helvetica"><span style="font-size: 11pt; color: rgb(31, 73, 125);">
Add the conformance requirement </span><span style="font-size: 11pt; color: rgb(31, 73, 125);"><span style="font-size: 11pt; color: rgb(31, 73, 125);">in IPP: Transaction Based Printing,
</span>as an addendum to PWG 5100.3-2001 IPP:Production Printing Attributes – Set 1, Section 7 as follows:</span></font><font size="2" face="Helvetica">
</font><div><font size="2" face="Helvetica"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></font><br class="webkit-block-placeholder"></div>
<font size="2" face="Helvetica"></font><p class="MsoNormal"><font size="2" face="Helvetica"><span style="font-size: 11pt; color: rgb(31, 73, 125);">If the Printer supports “job-accounting-user-id” then the Printer MUST support “job-account-id”.</span></font></p></div></div></blockquote><div><br></div>No objection to adding this.</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></div></body></html>