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)"><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;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{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;}
--></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'>Hi Mike,<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'>The </span>MFD Model and Common Semantics does not define Output Device (it should) and some may take it to mean something like a dumb printer. I believe that SM assiduously avoids any reference to the interface between the Service and the Output Device. Rather, it deals with the Client-<service>Service interface, and that can be extended to a Service-Service interface in the case of a superior (pr Primary) Service feeding other <service>Services (as you 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. I also question the first sentence. I suggest:,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><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.<br><br>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><p class=MsoNormal style='margin-bottom:12.0pt'>Thanks,<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Bill Wagner<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><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'><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> Sunday, March 17, 2013 4:17 PM<br><b>To:</b> cloud@pwg.org<br><b>Subject:</b> [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><div><p class=MsoNormal>All,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Here is my proposed introductory text for the Cloud Print Requirements and Model. I chose to stick with Semantic Model terminology for the introduction since the corresponding Cloud Print terms are not yet introduced...<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 style='margin-bottom:12.0pt'>The PWG Semantic Model supports Output Devices that operate separately from the corresponding Service. The MFD Model and Common Semantics [PWG5108.01] defines the outward-facing semantics of this interface to ensure conformance to the model. However, it does not define the interface between the Service and the Output Device. When the Output Device is network accessible to the Service, the existing Semantic Model interface can be used with the primary Service acting as a Client to the Output Device's Service. However, when the Output Device is not network accessible to the Service, a new interface is required that allows the Output Device to retrieve and update Jobs and Documents, as well as provide current status and configuration of the Output Device to the Service.<br><br>This specification defines a new printing interface between a Semantic Model Output Device and Service to support situations where the Output Device 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 Output Device 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><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><br><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. <o:p></o:p></p></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>