I've been working on the FaxIn spec per August F2F review.
In section 6.6, I need FaxLogUri, but it's *still* missing in SM v1.147
(it's present only in FaxOut spec and the FaxOutService schema).
So here's my opinion about the equivalent FaxOutServiceDescription
service-specific elements for FaxIn:
Compression[Default/Supported] - No
DefaultFaxModem - No
DocumentFormat[Default/Supported/DetailsXxx] - No*
FaxLogUri - Yes (REQUIRED)
MultipleDocumentJobsSupported - Yes (OPTIONAL)
MultipleOperation[Timeout/TimeoutXxx] - No
ServiceChargeInfoUri - Yes
ServiceOrganizations - Yes
*DocumentFormat belongs in FaxInDocumentProcessing[Capabilities],
so that documents sent to the DestinationUris get the right format, right?
Similar conceptually to ScanService? I think all analagous Scan elements
should be available for processing FaxIn documents in order to be able
to send reasonably to a variety of destinations.
NOTE - There's an error in PWG 5108.5 (FaxOut) where FaxLogUri is
optional in the schema, according to my reading of the spec.
I think we've made a mistake making the FaxInDocument single-valued
in the schema, because we're keeping the text saying that support for
multiple document jobs is optional (per our August F2F review).
I did add the various notes about PSTN FaxIn being inherently single
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
mailto:blueroofmusic at gmail.com
Winter 579 Park Place Saline, MI 48176 734-944-0094
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
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...