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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:304503968;
mso-list-type:hybrid;
mso-list-template-ids:-2076654180 649889250 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l1
{mso-list-id:603853097;
mso-list-type:hybrid;
mso-list-template-ids:-1180259330 998309274 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l2
{mso-list-id:654527583;
mso-list-type:hybrid;
mso-list-template-ids:-1093622660 67698709 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-number-format:alpha-upper;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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>In working on the Cloud spec, we decided that Resource, Transform, and Copy Services were not to be considered. EmailIn and Email Out services we to be dropped from the Semantic Model entirely. That left Print, Scan, FaxOut and FaxIn Cloud services that might involve connection to a ‘local’ service.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>FaxIn remains an unusual service in that it does not involve an explicit CreateJob or, indeed, any specific Job-related communication with a User. It may involve creation of a user-specific FaxInAvailableJobTicket, which defines how an incoming Fax is to be handled. In the MFD Model, I don’t think we ever defined how a FaxInAvailableJobTicket was provided to a FaxIn Service. Conceptually, it could be either be via some out of band management operation, or possible a SetFaxInJobElements or a SetFaxInServiceElements operation. Presumably SetFaxInServiceElements makes the most sense, understanding that there will typically be multiple FaxInAvailableJobTickets with different Imaging Metrics.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The interface to a FaxIn Service is therefore most reasonably an administrative operation.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The rationale for a Cloud FaxIn service is shaky but probably as valid as for a Cloud FaxOut service: Fax Modems could be in the Cloud or ‘Local”; incoming fax destinations can be local or in the cloud. Therefore, although the User Client to Cloud Service connection would just be administrative, incoming facsimile messages to a Cloud FaxIn Service may require creating a Job that is sent to a local FaxIn Service (although it could be just a print Service or a storage service). Incoming facsimile messages to a Local FaxIn Service could require both notification and upload of the facsimile message to a Cloud FaxIn Service, although such transfers could be out of band from the model. Presently, we have not provided any mechanism for the Proxy to create a job in the Cloud Service (do we want to?)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So…long story short, should we:<o:p></o:p></p><p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;mso-list:l1 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Drop FaxIn from the Cloud Model<o:p></o:p></p><p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;mso-list:l1 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Allow a Cloud FaxIn Service to create a Job from an incoming Fax, and then relay the fax data to a Local FaxIn Service for printing and/or local storage<o:p></o:p></p><p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;mso-list:l1 level1 lfo1'><![if !supportLists]><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Also allow a LocalFaxIn Service to create a Job from an incoming Fax and relay the fax data to a Cloud FaxIn service for storage?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There are also some parallel questions for FaxOut. Should the Cloud Model consider:<o:p></o:p></p><p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;mso-list:l0 level1 lfo3'><![if !supportLists]><span style='mso-list:Ignore'>A.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Just configurations where the Fax Modem is ‘Local’ (fax transmitted and locally generated from locally scanned hardcopy and/or Digital Data obtained by the local FaxOut (or Proxy) Service or Digital Data pulled from the Cloud FaxOut Service.)<o:p></o:p></p><p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in;mso-list:l0 level1 lfo3'><![if !supportLists]><span style='mso-list:Ignore'>B.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Also configurations where the Fax Modem is in the Cloud (fax generated from uploaded locally scanned hardcopy and/or uploaded Digital Data obtained by the local FaxOut or Proxy, or Digital Data otherwise accessed by the Cloud FaxOut Service.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It might be noted that whatever we decide, FaxIn should be addressed in the SM3 specification.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Many thanks for your consideration.<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>