attachment-0001
Hi Pete,<br><br>I didn't make myself clear about DocumentFormat.<br><br>IMHO, *all* MFD services need DocumentFormat.<br><br>FaxIn doesn't have it (search the schema), including<br>in the FaxInJobTicket.<br><br>Which I think breaks the model that FaxIn receives <br>
images and processes them in a manner conceptually <br>similar to Scan and then sends the document to one<br>or more destinations.<br><br>In the FaxInJob life cycle (which I'm writing up) there<br>are several important steps:<br>
<br>0) Incoming Fax call and negotiated connection (PSTN<br> or Internet Fax email transport)<br><br>1) Implicit CreateFaxInJob by System (as JobOwner)<br> - FaxInService searches AvailableFaxInJobTickets<br><br>2) Implicit AddFaxInDocument by System<br>
- FaxInService stores images (streaming or as a block)<br><br>3) Implicit CloseFaxInJob by System<br> - FaxInService processes document;<br> sends to one or more destinations; and<br> logs Job metadata to FaxLogUri<br>
<br>Certainly by the time of Job/Document creation, it<br>seems that any MFD job must have DocumentFormat?<br><br>Cheers,<br>- Ira<br><br><br clear="all">Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>
Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a style="color:rgb(51, 51, 255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a style="color:rgb(102, 0, 204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div>
</div><div></div><div></div><br>
<br><br><div class="gmail_quote">On Mon, Oct 31, 2011 at 8:22 AM, Zehler, Peter <span dir="ltr"><<a href="mailto:Peter.Zehler@xerox.com">Peter.Zehler@xerox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Comments inline below.<u></u><u></u></span></p><div class="im"><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:navy">Peter Zehler</span><span style="font-size:11.0pt;color:#1F497D"><br>
<br></span><span style="font-size:10.0pt;color:navy">Xerox Research Center Webster<br></span><span style="font-size:10.0pt;color:navy">Email: <a href="mailto:Peter.Zehler@Xerox.com" target="_blank">Peter.Zehler@Xerox.com</a></span><span style="font-size:11.0pt;color:#1F497D"><br>
</span><span style="font-size:10.0pt;color:navy">Voice: <a href="tel:%28585%29%20265-8755" value="+15852658755" target="_blank">(585) 265-8755</a></span><span style="font-size:11.0pt;color:#1F497D"><br></span><span style="font-size:10.0pt;color:navy">FAX: <a href="tel:%28585%29%20265-7441" value="+15852657441" target="_blank">(585) 265-7441</a></span><span style="font-size:11.0pt;color:#1F497D"><br>
</span><span style="font-size:10.0pt;color:navy">US Mail: Peter Zehler</span><span style="font-size:11.0pt;color:#1F497D"><br></span><span style="font-size:10.0pt;color:navy">Xerox Corp.</span><span style="font-size:11.0pt;color:#1F497D"><br>
</span><span style="font-size:10.0pt;color:navy">800 Phillips Rd.</span><span style="font-size:11.0pt;color:#1F497D"><br></span><span style="font-size:10.0pt;color:navy">M/S 128-25E</span><span style="font-size:11.0pt;color:#1F497D"><br>
</span><span style="font-size:10.0pt;color:navy">Webster NY, 14580-9701</span><span style="font-size:11.0pt;color:#1F497D"> </span><span style="color:#1F497D"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> Ira McDonald [mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>] <br><b>Sent:</b> Sunday, October 30, 2011 8:14 PM<br>
<b>To:</b> Zehler, Peter; Ira McDonald<br><b>Cc:</b> <a href="mailto:mfd@pwg.org" target="_blank">mfd@pwg.org</a><br><b>Subject:</b> FaxLogUri *still* missing in FaxInServiceDescription SM schema<u></u><u></u></span></p><p class="MsoNormal">
<u></u> <u></u></p></div><p class="MsoNormal">Hi Pete,</p><div class="im"><br><br>I've been working on the FaxIn spec per August F2F review.<br><br>In section 6.6, I need FaxLogUri, but it's *still* missing in SM v1.147 <br>
(it's present only in FaxOut spec and the FaxOutService schema).<span style="color:#1F497D"><u></u><u></u></span></div><p></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><PZ>Added in v1.149</PZ><u></u><u></u></span></p>
<p class="MsoNormal"></p><div class="im"><br><br>So here's my opinion about the equivalent FaxOutServiceDescription<br>service-specific elements for FaxIn:<br><br>Compression[Default/Supported] - No<br>DefaultFaxModem - No<br>
DocumentFormat[Default/Supported/DetailsXxx] - No*<br>FaxLogUri - Yes (REQUIRED)<br>MultipleDocumentJobsSupported - Yes (OPTIONAL)<br>MultipleOperation[Timeout/TimeoutXxx] - No<br>ServiceChargeInfoUri - Yes<br></div>ServiceOrganizations <span style="color:#1F497D">–</span> Yes<span style="color:#1F497D"><u></u><u></u></span><p>
</p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><PZ>Everything in v1.149 except MultipleDocumentJobsSupported which is in v 1.150</PZ><u></u><u></u></span></p><div class="im"><p class="MsoNormal">
<br><br>*DocumentFormat belongs in FaxInDocumentProcessing[Capabilities],<br>so that documents sent to the DestinationUris get the right format, right?<br>Similar conceptually to ScanService? I think all analagous Scan elements<br>
should be available for processing FaxIn documents in order to be able<br>to send reasonably to a variety of destinations.<span style="color:#1F497D"><u></u><u></u></span></p></div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><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><u></u><u></u></span></p>
<div class="im"><p class="MsoNormal"><br><br>NOTE - There's an error in PWG 5108.5 (FaxOut) where FaxLogUri is<br>optional in the schema, according to my reading of the spec.<span style="color:#1F497D"><u></u><u></u></span></p>
</div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><PZ>Corrected in v 1.149.</PZ><u></u><u></u></span></p><div class="im"><p class="MsoNormal"><br><br>I think we've made a mistake making the FaxInDocument single-valued<br>
in the schema, because we're keeping the text saying that support for<br>multiple document jobs is optional (per our August F2F review).<span style="color:#1F497D"><u></u><u></u></span></p></div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><PZ>Corrected in v 1.149.</PZ><u></u><u></u></span></p>
<div class="im"><p class="MsoNormal"><br><br>I did add the various notes about PSTN FaxIn being inherently single<br>document jobs.<br><br>Cheers,<br>- Ira<br><br><br>Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>
Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a href="http://sites.google.com/site/blueroofmusic" target="_blank"><span style="color:#3333FF">http://sites.google.com/site/blueroofmusic</span></a><br>
<a href="http://sites.google.com/site/highnorthinc" target="_blank"><span style="color:#6600CC">http://sites.google.com/site/highnorthinc</span></a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 <a href="tel:734-944-0094" value="+17349440094" target="_blank">734-944-0094</a><br>Summer PO Box 221 Grand Marais, MI 49839 <a href="tel:906-494-2434" value="+19064942434" target="_blank">906-494-2434</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p></div></div></div></blockquote></div><br><style>#avg_ls_inline_popup{position:absolute;z-index:9999;padding:0px;margin:0px;overflow:hidden;wordWrap:break-word;color:black;font-size:10px;text-align:left;line-height:130%;}#avg_ls_inline_popup div{border-width:3px;border-style:solid;padding:3px;padding-left:8px;padding-right:8px;-moz-border-radius:5px;-webkit-border-radius:5px;}#avg_ls_inline_popup .red{border-color:#D20003;;background-color:#F5D4C1;;}#avg_ls_inline_popup .orange{border-color:#F57301;;background-color:#FFD3B0;;}#avg_ls_inline_popup .yellow{border-color:#EAA500;;background-color:#FEEFAE;;}#avg_ls_inline_popup .green{border-color:#00A120;;background-color:#C3E5CA;;}</style><div style="visibility: hidden; left: -5000px;" id="avg_ls_inline_popup">
</div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.