Section 6.1 Send-Hardcopy-Document Operation
This is a CONDITIONALLY REQUIRED Operation. The condition is that Printers with one or more scanning accessories MUST support this operation. At the same time, it requires that a client (SHOULD) check if the Printer supports the operation by querying the "operation-supported" Printer Description, and clients discover the available input sources by querying "input-source-supported" Printer Description. Is it the case that the *client* (MUST or SHOULD ?) specify that the job input comes from a hard copy via the scan input device? This requirement makes sense for small devices which are driven from a client driver on their PC but doesn't make sense for an enterprise or work group device which is shared by many users. Enterprise or work group devices have a local user interface which allow the user to program and submit jobs.
Section 7.1 - These are all new attributes which go along with the new operation defined in section 6. As such they should be exempt (SHOULD as opposed to REQUIRED) if supplied by the user at client station.
Section 7.2.2 - This attribute is specified as being "CONDITIONALLY REQUIRED". Does the REQUIRED apply to each of the member attributes? There are a number of member attributes in this section which are not supposed to be overridden by the user or client (reference to section 6 about clients gives the impression that the user supplies the values that override values from system), and some which can be optionally supplied.
* 7.2.2.1 date-time - this is not able to be overridden by the submitting user. The system defines the submission time.
* 7.2.2.2 from-name - this is filled in with the submitting user name (job-originating-user-name) for the job.
* 7.2.2.3 logo - This should be optional.
* 7.2.2.4 message - This should be optional.
* 7.2.2.5 organization-name - This should be optional.
* 7.2.2.6 subject
* 7.2.2.7 to-name - This should be optional.
Section 7.2.4 - 7.2.6 all three of these are CONDITIONALLY REQUIRED for spooling devices. The number-of-retries, retry-interval, and retry-time-out are all system level attributes that belong to the fax card and are not adjustable on a job per job basis. Are we suggesting that the settings for these attributes be exposed at a job level?
Section 7.3.1 The destination-status for each recipient is contained completely within the fax card and is only made available to the user through the confirmation sheet. The job level status reported to the UI's and job history only give the overall status of the entire job. This attribute should be changed to SHOULD.
Sections 7.4.23 - 7.4.25 (printer-fax-modem-info, printer-fax-modem-name, printer-fax-modem-number) Wish that these were SHOULD as opposed to REQUIRED as this will require the gathering of the information and make it available to IPP (also privacy issues ...) - but otherwise ok.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.