> On Mar 17, 2016, at 5:19 PM, Kennedy, Smith (Wireless Architect) <smith.kennedy at hp.com> wrote:
>> Would rejecting the operation with "client-error-conflicting-attributes" be an appropriate response?
Possibly, although that status code is usually reserved for Job Template attribute conflicts...
>>>> On 2016-03-17, at 3:09 PM, Michael Sweet <msweet at apple.com<mailto:msweet at apple.com>> wrote:
>> On Mar 17, 2016, at 5:00 PM, Kennedy, Smith (Wireless Architect) <smith.kennedy at hp.com<mailto:smith.kennedy at hp.com>> wrote:
>> PWG 5100.7 defined the "document-format-details" attribute, and one of its children is "document-format". There is also a "document-format" attribute, which is essential to the proper operation of IPP in general (filtering printer description attributes and so forth). But the definition of "document-format-details" is ambiguous in situations where "document-format" is not a "packaging" format.
>> If "document-format" is not a packaging format, but is rather a conventional format such as "application/pdf" or "image/pwg-raster", and "document-format-details" is provided by the Client, but the "document-format" child of "document-format-details" doesn't match "document-format", what should the Printer do?
>> Given the lack of firm conformance requirements, the Printer is free to return client-error-attributes-or-values-not-supported or successful-ok-ignored-or-substituted-attributes, or to ignore the value completely and just return successful-ok. (any of those is allowed by 2911)
> Michael Sweet, Senior Printing System Engineer
Michael Sweet, Senior Printing System Engineer