Smith Kennedy 4 Days Ago

The tables in section 4 providing a column for normative requirements for the Proxy are difficult for many to understand, and should be refactored. Many are not reading the paragraph preceding the tables and are then at a loss as to the meaning of MUST for a Proxy - they are thinking that it means the Printer MUST implement the attributes. If one reads, for instance, the last sentence of the paragraph in section 4.7 preceding Table 7, which says: "For Proxies the conformance requirements are the capability to send the attribute in an Update-Output-Device-Attributes request if supported by the proxied Output Device." This means that all the MUST are really CONDITIONALLY MUST. But if one doesn't read the paragraph, the interpretation is quite different. It might be as well if we replaced all the "MUST" with a new "Note 5" that explains this / states the sentence from the paragraph? (The "Note" syntax should be normalized as well...) And how should an implementer of a Proxy or an implementer of a test system testing a Proxy decide on what action to take for a "SHOULD"?

Find a way to present the information in a way that is less difficult to understand.