attachment
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Andale Mono";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoToc3, li.MsoToc3, div.MsoToc3
{mso-style-priority:39;
mso-style-link:"TOC 3 Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:#1F497D;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.TOC3Char
{mso-style-name:"TOC 3 Char";
mso-style-priority:39;
mso-style-link:"TOC 3";
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Michael,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoToc3>Actually, I believe at your suggestion, we did add <a href="#_Toc397612068"><span style='color:windowtext;text-decoration:none'> Cloud Service Management Operations<span style='display:none'>. </span></span><span style='color:windowtext;display:none;text-decoration:none'>46</span></a> to the Model, including the SetServiceElements operation that (I suggest) defines incomming facsimile handling. However, I do get the sense that there is no interest in including FaxIn so unless someone suggestst that it is desirable, I will eliminate it. We are, of course, rethinking things we had settled some time ago. Any other Services we should drop? What about CloudFaxOut? CloudScan?<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bill Wagner<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cloud-bounces@pwg.org [mailto:cloud-bounces@pwg.org] <b>On Behalf Of </b>Michael Sweet<br><b>Sent:</b> Wednesday, September 17, 2014 11:44 AM<br><b>To:</b> Ira McDonald<br><b>Cc:</b> cloud@pwg.org; Semantic Model 3.0 Workgroup discussion list<br><b>Subject:</b> Re: [Cloud] [SM3] Cloud FaxIn Service<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>My $0.02 CAD - Cloud FaxIn is out-of-scope, not only because of prototyping but because remote management is out of scope already (as Bill points out) and any local-to-Cloud push of incoming faxes sure looks a lot like a regular client-to-Cloud interaction that we don't need to be involved in...<o:p></o:p></p><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Sep 16, 2014, at 4:19 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Hi Bill,<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>We *did* define in complete detail how a set of available job tickets are<br>configured on a FaxIn service and how they are selected - and all of <br>this is in SM schema and the most recent FaxIn draft.<o:p></o:p></p></div><p class=MsoNormal>BUT - I strongly urge that we *not* put FaxIn into Cloud Model, because<br>the IPP WG has decided (and written into their charter a year ago) that<o:p></o:p></p></div><p class=MsoNormal>they will *not* do an IPP FaxIn service - no protocol binding to satisfy the<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>PWG prototype requirement.<o:p></o:p></p></div><p class=MsoNormal>Cheers,<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>- Ira<o:p></o:p></p></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<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 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Tue, Sep 16, 2014 at 4:07 PM, William A Wagner <<a href="mailto:wamwagner@comcast.net" target="_blank">wamwagner@comcast.net</a>> wrote:<o:p></o:p></p><p class=MsoNormal>In working on the Cloud spec, we decided that Resource, Transform, and Copy<br>Services were not to be considered. EmailIn and Email Out services we to be<br>dropped from the Semantic Model entirely. That left Print, Scan, FaxOut and<br>FaxIn Cloud services that might involve connection to a 'local' service.<br><br><br><br>FaxIn remains an unusual service in that it does not involve an explicit<br>CreateJob or, indeed, any specific Job-related communication with a User. It<br>may involve creation of a user-specific FaxInAvailableJobTicket, which<br>defines how an incoming Fax is to be handled. In the MFD Model, I don't<br>think we ever defined how a FaxInAvailableJobTicket was provided to a FaxIn<br>Service. Conceptually, it could be either be via some out of band<br>management operation, or possible a SetFaxInJobElements or a<br>SetFaxInServiceElements operation. Presumably SetFaxInServiceElements makes<br>the most sense, understanding that there will typically be multiple<br>FaxInAvailableJobTickets with different Imaging Metrics.<br><br><br><br>The interface to a FaxIn Service is therefore most reasonably an<br>administrative operation.<br><br><br><br>The rationale for a Cloud FaxIn service is shaky but probably as valid as<br>for a Cloud FaxOut service: Fax Modems could be in the Cloud or 'Local";<br>incoming fax destinations can be local or in the cloud. Therefore, although<br>the User Client to Cloud Service connection would just be administrative,<br>incoming facsimile messages to a Cloud FaxIn Service may require creating a<br>Job that is sent to a local FaxIn Service (although it could be just a<br>print Service or a storage service). Incoming facsimile messages to a Local<br>FaxIn Service could require both notification and upload of the facsimile<br>message to a Cloud FaxIn Service, although such transfers could be out of<br>band from the model. Presently, we have not provided any mechanism for the<br>Proxy to create a job in the Cloud Service (do we want to?)<br><br><br><br>So.long story short, should we:<br><br>1. Drop FaxIn from the Cloud Model<br><br>2. Allow a Cloud FaxIn Service to create a Job from an incoming Fax,<br>and then relay the fax data to a Local FaxIn Service for printing and/or<br>local storage<br><br>3. Also allow a LocalFaxIn Service to create a Job from an incoming<br>Fax and relay the fax data to a Cloud FaxIn service for storage?<br><br><br><br>There are also some parallel questions for FaxOut. Should the Cloud<br>Model consider:<br><br>A. Just configurations where the Fax Modem is 'Local' (fax transmitted<br>and locally generated from locally scanned hardcopy and/or Digital Data<br>obtained by the local FaxOut (or Proxy) Service or Digital Data pulled from<br>the Cloud FaxOut Service.)<br><br>B. Also configurations where the Fax Modem is in the Cloud (fax<br>generated from uploaded locally scanned hardcopy and/or uploaded Digital<br>Data obtained by the local FaxOut or Proxy, or Digital Data otherwise<br>accessed by the Cloud FaxOut Service.<br><br><br><br>It might be noted that whatever we decide, FaxIn should be addressed in the<br>SM3 specification.<br><br><br><br>Many thanks for your consideration.<br><br><br><br><br><br><br><br>_______________________________________________<br>sm3 mailing list<br><a href="mailto:sm3@pwg.org">sm3@pwg.org</a><br><a href="https://www.pwg.org/mailman/listinfo/sm3" target="_blank">https://www.pwg.org/mailman/listinfo/sm3</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>_______________________________________________<br>cloud mailing list<br><a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><a href="https://www.pwg.org/mailman/listinfo/cloud">https://www.pwg.org/mailman/listinfo/cloud</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal><span style='font-family:"Andale Mono","serif";color:black'>_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>