[MFD] Re: FaxLogUri *still* missing in FaxInServiceDescription SM schema

[MFD] Re: FaxLogUri *still* missing in FaxInServiceDescription SM schema

[MFD] Re: FaxLogUri *still* missing in FaxInServiceDescription SM schema

Ira McDonald blueroofmusic at gmail.com
Mon Oct 31 16:06:20 UTC 2011


Hi Pete,

I didn't make myself clear about DocumentFormat.

IMHO, *all*  MFD services need DocumentFormat.

FaxIn doesn't have it (search the schema), including
in the FaxInJobTicket.

Which I think breaks the model that FaxIn receives
images and processes them in a manner conceptually
similar to Scan and then sends the document to one
or more destinations.

In the FaxInJob life cycle (which I'm writing up) there
are several important steps:

0) Incoming Fax call and negotiated connection (PSTN
    or Internet Fax email transport)

1) Implicit CreateFaxInJob by System (as JobOwner)
    - FaxInService searches AvailableFaxInJobTickets

2) Implicit AddFaxInDocument by System
    - FaxInService stores images (streaming or as a block)

3) Implicit CloseFaxInJob by System
    - FaxInService processes document;
      sends to one or more destinations; and
      logs Job metadata to FaxLogUri

Certainly by the time of Job/Document creation, it
seems that any MFD job must have DocumentFormat?

Cheers,
- Ira


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
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
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



On Mon, Oct 31, 2011 at 8:22 AM, Zehler, Peter <Peter.Zehler at xerox.com>wrote:

> Comments inline below.****
>
> ** **
>
> ** **
>
> Peter Zehler
>
> Xerox Research Center Webster
> Email: Peter.Zehler at Xerox.com
> Voice: (585) 265-8755
> FAX: (585) 265-7441
> US Mail: Peter Zehler
> Xerox Corp.
> 800 Phillips Rd.
> M/S 128-25E
> Webster NY, 14580-9701 ****
>
> ** **
>
> *From:* Ira McDonald [mailto:blueroofmusic at gmail.com]
> *Sent:* Sunday, October 30, 2011 8:14 PM
> *To:* Zehler, Peter; Ira McDonald
> *Cc:* mfd at pwg.org
> *Subject:* FaxLogUri *still* missing in FaxInServiceDescription SM schema*
> ***
>
> ** **
>
> Hi Pete,
>
>
> 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).****
>
> <PZ>Added in v1.149</PZ>****
>
>
>
> 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****
>
> <PZ>Everything in v1.149 except MultipleDocumentJobsSupported which is in
> v 1.150</PZ>****
>
>
>
> *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.****
>
> <PZ>I don’t quite agree.  I think that capabilities and defaults are
> applicable to the FaxInService.  However, I think that the capabilities are
> used by a FaxInService user to determine the allowed values when creating
> an entry in AvailableFaxInJobTicket.  FaxInJobs are initiated/created by an
> inbound FAX protocol initiation.  A FaxInService user configures what
> happens when an inbound FAX is received.  If none of the configured
> FaxInMetrics match, then the FaxIn ServiceDefaults would be used.  I expect
> the operations (as of yet undefined) would focus on FaxInService
> configuration including the setting of job routing and handling (i.e.
> AvailableFaxInJobTickets.</PZ>****
>
>
>
> NOTE - There's an error in PWG 5108.5 (FaxOut) where FaxLogUri is
> optional in the schema, according to my reading of the spec.****
>
> <PZ>Corrected in v 1.149.</PZ>****
>
>
>
> 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).****
>
> <PZ>Corrected in v 1.149.</PZ>****
>
>
>
> I did add the various notes about PSTN FaxIn being inherently single
> document jobs.
>
> Cheers,
> - Ira
>
>
> 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
> http://sites.google.com/site/blueroofmusic
> http://sites.google.com/site/highnorthinc
> 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...
URL: <http://www.pwg.org/pipermail/mfd/attachments/20111031/9284a63f/attachment-0001.html>


More information about the mfd mailing list