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;">Nancy,<div><br><div><div>On Mar 7, 2013, at 5:08 PM, Ying Chen <<a href="mailto:chen.nancy5@gmail.com">chen.nancy5@gmail.com</a>> wrote:</div><blockquote type="cite"><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"><div><font color="#000000">...</font></div><div>2.  In Mike's response to #5, regarding Get-Printer-Supported-Values -</div><div>From rfc3380 page 1,  "The Get-Printer-Supported-Values administrative operation returns values that the IPP Printer will accept for setting its "xxx-supported".  Notice that this operation does not return any "xxx-supported" values that cannot be set by an administrator.  Hence Mike is correct that "use Get-Printer-Supported-Values to get the full set of values that can be configured", but I did not see any semantic in rfc3380 that defines "Get-Printer-Supported-Values returns the original manufacturer xxx-supported values while Get-Printer-Attributes returns the values as configured by the administrator of the printer" as Mike said.</div></div></blockquote><div><br></div>RFC 3380 also defines Set-Printer-Attributes; from section 4.1:</div><div><br></div><div><div>   5. The Printer MUST support the value, according to the rules defined</div><div>      in Appendix A, i.e., each value of each supplied "xxx" attribute</div><div>      MUST be validated against the value of a corresponding "xxx-</div><div>      supported" Printer attribute.  One of those rules permits an</div><div>      administrator to set arbitrary 'name' values to those "xxx-</div><div>      supported" Printer attributes that include the 'name' attribute</div><div>      syntax if the implementation supports the 'admin-define' out-of-</div><div>      band value for that "xxx-supported" attribute (see section 8.3 and</div><div>      Appendix A).</div><div><br></div><div>Section 4.3 talks about the differences between Get-Printer-Attributes and Get-Printer-Supported-Values, including:</div><div><br></div><div><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always;"> 3. The Get-Printer-Attributes operation returns the current values of requested attributes, while the Get-Printer-Supported-Values operation returns the values that are inherently supported by the implementation code, i.e., the values that an administrative client can set in a Set-Printer-Attributes request. 4. The Get-Printer-Attributes operation returns the current values of requested "xxx-supported" attributes that the Printer is configured to accept in Job Creation operations, including additional values defined by the administrator, while the Get- Printer-Supported-Values operation returns only the values of "xxx-supported" attributes that are inherently supported by the implementation and does not return any additional values defined by the administrator, where the implementation supports the 'admin-define' out-of-band value. </pre></div><div><br></div><blockquote type="cite"><div style="orphans: auto; text-align: start; text-indent: 0px; widows: auto;"><div style="letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">...</div></div></blockquote><blockquote type="cite"><div style="orphans: auto; text-align: start; text-indent: 0px; widows: auto;"><div style="letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Therefore, Mike is correct that there is no element in MFD SM that defines "the original manufacturer xxx-supported values".  I think this set of values are very useful when there is a need to restore <service> attributes to the manufacturer's defaults.  But I don't see the IPP spec (rfc3380) has this set of attributes defined either.</div></div></blockquote><div><br></div>I'm interpreting "values inherently supported by the implementation" as the "manufacturer default values", but you are right technically the defaults might not include all values. Consider my wording changed accordingly to align with 3380's Get-Printer-Supported-Values terminology.  We still don't have a way to get the full set of supported values for read/write elements in the Semantic Model... :/</div><br><div> <span class="Apple-style-span" style="border-collapse: separate; font-family: 'Andale Mono'; border-spacing: 0px; font-size: medium;"><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; font-size: medium; "><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><br />-- <br />This message has been scanned for viruses and <br />dangerous content by <a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is <br />believed to be clean. </body></html>