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=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@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:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 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;}
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.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;}
/* List Definitions */
@list l0
{mso-list-id:966737983;
mso-list-type:hybrid;
mso-list-template-ids:-1085269756 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:38.7pt;
text-indent:-.25in;
font-family:Symbol;}
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-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Kelly, <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>There was a great deal of discussion, and the consensus was that the PWG very much appreciated Google’s intent to retain compliance with the PWG Semantic Model and willingness to work with the PWG members. We understand that specifics of the transport and aspects of the format need to be compatible with other Google requirements; but we believe that the actual imaging semantics can be a proper subset of the PWG Semantic Model. As others have written, this would be beneficial to manufacturers since devices already use PWG semantics; it would be beneficial to Google and client providers since it is fairly consistently implemented (avoiding the need for extensive device- or manufacturer-specific handing); and it would be beneficial to the end users because a reasonable subset will provide access to the features that they would like to use.<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'>I have attached a applicable sections of the minutes below. Some of the more significant aspects are:<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:38.7pt;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Providing the current PWG Job Ticket and Capabilities document to Google (immediately)<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:38.7pt;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Identify a reasonable subset of the elements in that document commensurate with our understanding of the level and requirements of the users Google is anticipating (very soon, and we would appreciate Google’s input)<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:38.7pt;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Extend the Job Ticket from just Print service to all multifunction services (concentrating initially on Scan and Resource/storage services) <o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:38.7pt;text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:Symbol;color:#17365D'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Provide a </span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif";color:#17365D'>JSON/protobuf mapping/binding of PWG PJT</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17365D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17365D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17365D'>Please let us know if you see alternate or additional things we can do to facilitate this coordination.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17365D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17365D'>I know you understand the difficulty of getting manufacturers to assign their engineers to work on public standards, but we believe that, in this case, imaging manufactures understand that it is in their best interests. There are usually problems in achieving consensus, but in this case, the work largely involves things that have already been agreed to. We have high hopes that the PWG and Google can work together effectively on this. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> Many thanks,<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'>Bill Wagner, Cloud WG Vice Chair<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 style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>Google Cloud Print CDD<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>a. See emails posted to the Cloud mailing list<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>b. Q: Do we send PWG PJT to Google?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"MS Gothic"'>⁃</span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'> A: Yes<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"MS Gothic"'>⁃</span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'> Action: Mike to send Google a copy of PWG PJT<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>c. Q: Do we ask Semantic Model WG to take on storage capabilities WRT resource service<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"MS Gothic"'>⁃</span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'> A: Yes<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>d. CDD seems to expose implementation details, not sure why they have been defined differently<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>from the Semantic Model<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>e. Important to work with Google to resolve these discrepancies, they seem to be open to this<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>f. CDD also seems to expose vendor-specific extensions, unsure how that maps?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>g. What elements of the PWG PJT should be exposed in CDD?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"MS Gothic"'>⁃</span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'> No objection to compatible/proper subset of PWG PJT mapped to JSON/protobuf<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"MS Gothic"'>⁃</span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'> Glen will look into feasibility of writing something up<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"MS Gothic"'>⁃</span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'> Action: Glen to find out if he can spend time making a proper subset of PWG PJT for GCP/CDD<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>h. Another significant source of information would be the mapping document (even the current<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>version, since PPD is in decent shape)<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"MS Gothic"'>⁃</span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'> Still need more work on MSPS<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"MS Gothic"'>⁃</span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'> Send drafts to Google as well<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'>i. "Tiger team" for GCP:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"MS Gothic"'>⁃</span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'> Do we make a JSON/protobuf mapping/binding of PWG PJT?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"MS Gothic"'>⁃</span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'> Pete Zehler has a JSON version of Semantic Model - maybe we can get it and subset it?<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.5pt;font-family:"MS Gothic"'>⁃</span><span style='font-size:9.5pt;font-family:"Helvetica","sans-serif"'> Action: Mike to send email to Pete requesting copy of JSON files for PWG PJT<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 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>kdLucas<br><b>Sent:</b> Tuesday, February 12, 2013 1:03 PM<br><b>To:</b> cloud@pwg.org<br><b>Subject:</b> [Cloud] CDD Feedback<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I was curious if there was any new feedback on Google's Cloud Device Description (Semantic CAPS) at the Feb 6-7 Face-to-Face meeting. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Our developers are currently in the design phase so it's the right time to impact this effort.<o:p></o:p></p></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><p class=MsoNormal>Kelly<o:p></o:p></p></div><p class=MsoNormal>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>