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;}
/* 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.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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;}
--></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'>Kelly, Thank you for sending this format specification.<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 style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>To the Cloud WG, I suggest that we spend some time next Wednesday considering this subject. I believe that, as a group, we concur with the observations below relative to the use of PPDs, and with much of what is in the introduction to the CDD document with respect to the use of PPDs and “XPS” for capabilities and job ticket communication. I am pleased to see that the Google specification seeks to address scan and storage as well as print functions. However, I think that we may be failing to communicate to Google that, with respect to semantics, the basic elements in the PWG Semantic Model are common to virtually all network printers and have been massaged over the years to address the capabilities and requirements of imaging devices being offered in the market. The model has been around long enough to allow fairly consistent interpretation among different manufacturers. To attempt to establish yet another method of capabilities and job ticket definition that does not follow this model will likely perpetuate the current problems of manufacturer-specific interpretations, inadequate coverage of capabilities and conditions, and general incompatibility. <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 PWG model (and the PWG Job Ticket and Capabilities) defines the semantics, not the protocols. I believe that the PWG would be happy to assist in bindings of the model to protocols other than IPP or Web Services, should some other set of protocols appear more appropriate in some applications. Alternatively, it would appear that we will have to cross map the semantic model to yet another method.<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'>Regardless, I think Google’s timely attention to multifunction imaging should encourage both the Cloud and SM working groups to get on with the Printing subset and initiate the Cloud multifunction efforts.<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><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>:</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>K.D. Lucas<br><b>Sent:</b> Monday, January 28, 2013 12:38 AM<br><b>To:</b> cloud@pwg.org<br><b>Subject:</b> [Cloud] Semantic Parsing of Capabilities: Cloud Device Description Capabilities<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hello Cloud Print Aficionados,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I wanted to inform you that the Google Cloud Print team is proposing a new capabilities format that will allow us to take advantage of semantic options, something we're calling <b><span style='font-family:"Arial","sans-serif";color:#222222'>Cloud Device Description </span></b><span style='font-family:"Arial","sans-serif";color:#222222'>(<i>CDD</i>) format, and can be used from printers to a host of other devices that may be used with our service. </span><o:p></o:p></p><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#222222'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#222222'>This is our rough draft of our proposal. We are proposing this capabilities format in order to provide a more uniform experience for our Cloud Print users, as correctly parsing various PPD files is challenging and ultimately not feasible.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#222222'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#222222'>Since I know this group has thought about Cloud Printing for quite some time, and has significant experience with the issues around Cloud Printing, we welcome any feedback or comments you might have. I've attached the specification as a PDF file.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#222222'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#222222'>I won't be around to make your next face-to-face meeting, but I've been reading some of the emails regarding this meeting.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#222222'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#222222'>Regards,<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#222222'><o:p> </o:p></span></p></div><div><p class=MsoNormal>Kelly<br>kdLucas<o:p></o:p></p></div></div><p class=MsoNormal><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>