attachment-0002
<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)"><base href="x-msg://403/"><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";}
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:12.0pt;
font-family:"Times New Roman","serif";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle19
{mso-style-type:personal-reply;
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;}
/* List Definitions */
@list l0
{mso-list-id:190996339;
mso-list-type:hybrid;
mso-list-template-ids:927624258 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1494446530;
mso-list-type:hybrid;
mso-list-template-ids:-427648382 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{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><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Michael,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>I don’t want to drag this out, but I think we have a basic difference in our understanding of the terminology. By agreed to definition, the MFD “</span><span style='font-family:"Calibri","sans-serif"'>supports one or more Imaging Services”. I take ‘support’ to mean that the MFD contains the physical elements that execute the Service(s). It was noted that an MFD could in fact be distributed among several pieces of equipment. But the Semantic Model just deals with how an MFD exposes itself to an external entity and does not necessarily relate to the internal structure of the MFD. And the intent has always been to avoid dealing with any interfaces internal to an MFD.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>I therefore have difficulty with the circumstance where the “Imaging Service does not reside on the MFD”. It is my understanding that any networked physical printer (which is an MFD) MUST include, manifest, implement, or contain a Print Service. (Perhaps, a very dumb printer with a direct connection to an external computer, where the computer does Print Service functions such as job control and rasterization, is not a MFD, although the combination of the printer and the computer may be considered an MFD). Of course, as in fanout, a Print Service may interface with one or more subsequent Print Services. Therefore, in the Cloud Printing mode, the Cloud Print Service is interacting with a local Print Service, and it is the assumed inability of the Cloud Print Service to initiate connections with the local Print Service that presents the need for defining a new set of operations. <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>Therefore, after indicating that the specification defines a set of actors and their interactions for Cloud Printing, and that the target printer may be behind a firewall. you might want the intro to note that:<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span style='font-family:"Calibri","sans-serif"'><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-family:"Calibri","sans-serif"'>The MFD Model and Common Semantics [PWG5108.01] defines the semantics of the interface between an Imaging Service and either a Client or an ‘upstream” Imaging Service acting as a Client, where the communication is initiated on the Client side.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span style='font-family:"Calibri","sans-serif"'><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-family:"Calibri","sans-serif"'> In cases where Client side communication initiation is prevented, as by a firewall, there needs to be some way by which the Imaging Service that is the destination of the Imaging Job Request can initiate communication with the upstream Client or Imaging Service.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span style='font-family:"Calibri","sans-serif"'><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-family:"Calibri","sans-serif"'>This specification defines an additional interface allowing a destination Print Service to initiate this communication.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>I think we should also not later on that the actor we identify are conceptual, and that the Cloud Print Manager may very well be contained within the MFD (Printer).<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>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><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"'> Michael Sweet [mailto:msweet@apple.com] <br><b>Sent:</b> Monday, March 18, 2013 2:33 PM<br><b>To:</b> William A Wagner<br><b>Cc:</b> cloud@pwg.org<br><b>Subject:</b> Re: [Cloud] Proposed introduction text for Cloud Print Requirements and Model<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bill,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On 2013-03-18, at 1:50 PM, William A Wagner <<a href="mailto:wamwagner@comcast.net">wamwagner@comcast.net</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span style='color:black'>...</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The<span class=apple-converted-space> </span></span>MFD Model and Common Semantics does not define Output Device (it should)<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Hmm, it may not define it but OutputDevice is part of the SM schema, in PrintJobProcessingCapabilities and PrintJobProcessing. But in any case...<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><p class=MsoNormal>...<o:p></o:p></p></div></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal>indicate). I would suggest that Multifunction Device (MFD), which is defined as “A hardware entity that supports one or more Imaging Services, including the System.” Be used in place of Output Device.<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I have no objection.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><p class=MsoNormal>I also question the first sentence. I suggest:,<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>The MFD Model and Common Semantics [PWG5108.01] defines the semantics of the interface between a Client and an Imaging Service, including one contained in a Multifunction Device (MFD) such as a Printer. When a primary Service, acting as a Client to the service within an MFD, has network accessibly to the MFD, the existing Semantic Model interface applies. However, when the MFD is not network accessible to a primary Service, a new interface is required that allows the MFD to retrieve and update Jobs and Documents, as well as provide current status and configuration of the MFD to the Service.<o:p></o:p></p></div><p class=MsoNormal>This feels awkward to me. How about:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><blockquote style='margin-left:30.0pt;margin-right:0in'><div><div><p class=MsoNormal>The MFD Model and Common Semantics [PWG5108.01] defines the semantics of the interface between a Client and an Imaging Service representing a Multifunction Device (MFD) such as a Printer. When the Imaging Service does not reside on the MFD, an additional interface between them is required. When the MFD is network accessible to the Imaging Service, the existing Semantic Model interface can be used with the Imaging Service acting as a Client to the MFD's Service. However, when the MFD is not network accessible to the Imaging Service, a new interface is required that allows the MFD to retrieve and update Jobs and Documents, as well as provide current status and configuration of the MFD to the Imaging Service. <o:p></o:p></p></div></div></blockquote><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-bottom:12.0pt'>This specification defines a new printing interface between a Semantic Model MFD and a Service to support situations where the MFD is not network accessible to the Service. While the focus of this specification is on Cloud-based Services, the same interface can be used in any situation where the MFD is not network accessible to the Service, as is common in many secure and multi-homed network environments. For example, a gateway Service might use the printing interface defined by this specification to provide guest printing from an open Wi-Fi network to a secure corporate LAN.<o:p></o:p></p></div></blockquote><div><p class=MsoNormal>And a few minor changes here since this is the Cloud *Print* Requirements and Model:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div><blockquote style='margin-left:30.0pt;margin-right:0in'><div><div><div><p class=MsoNormal>This specification defines a new printing interface between a Semantic Model MFD and a Print Service to support situations where the MFD is not network accessible to the Service. While the focus of this specification is on Cloud-based Print Services, the same interface can be used in any situation where the MFD is not network accessible to the Service, as is common in many secure and multi-homed network environments. For example, a gateway Print Service might use the printing interface defined by this specification to provide guest printing from an open Wi-Fi network to a MFD on a secure corporate LAN.<o:p></o:p></p></div></div></div></blockquote><div><div><div><p class=MsoNormal><br>We can tweak the wording again when we do the multifunction version of the spec...<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks!<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><div><p class=MsoNormal><span style='font-size:13.5pt;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><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.
</body></html>