All,
I have not had the cycles to review the IPP-FaxOut specification until
now and was greatly surprised at the some of the requirements and
specification.
For example "IPP FaxOut Jobs MUST be retained for a minimum of 300
seconds", "Printers [IPP FaxOut Service???] MUST support scaling and
color space conversion of document data to match the negotiated
facsimile image format at the job processing time", and "Imaging Devices
[IPP FaxOut Services???] that can only stream print jobs to a single
destination URI MUST support retransmission of the current page".
There are many of these types of requirements that appear to be Client
and/or the Imaging Devices "product/implementation design
specifications" and not what I expected to be API interfaces capability
and job submission specifications.
For instance, the IPP FaxOut Service should be provide capability on
"Job Retention times supported", "Fax Scaling Supported", "Color Spaces
Conversion Supported" and "Retransmission Supported" versus this
specification setting device and client design and implementation
requirements for these capabilities.
An example of the simplest fax out would be something like "no-cover,
single-sheet, one-recipient, (jpeg) image - to - fax binary CCITT
Encoding, no-retry, no-job-hold-after". Anything beyond that should be
based on the capability of the specific IPP FaxOut Service
implementation and/or the Client implementation but independent of a
"MUST" requirement of the PWG / IPP FaxOut Service specification.
However, the PWG / IPP FaxOut Service specification must define how
capability information is specified.
Glen
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20130530/be96d528/attachment-0001.html>