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:Impact;
panose-1:2 11 8 6 3 9 2 5 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
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.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{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:1056122146;
mso-list-type:hybrid;
mso-list-template-ids:-826884792 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 l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
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='color:#1F497D'>Pete,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Yes, the samples in Appendixes F &G should be helpful. By my understanding, the Google specification presents the format for the ticket and capabilities, but does not define a full set of elements and element values to be supported. What Glen was working on was a subset (and he came up with two) of the compete SM elements/values that represents our idea of what support might be appropriate in, for example, an enterprise situation (and a set somewhat less daunting than the full SM model).<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Kelly, it would help a lot if you could indicate the most effective format for your people in using our information to have the Google Capabilities Format use semantics for capabilities and values compatible with the industry semantic model.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Many Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Bill Wagner<o:p></o:p></span></p><p class=MsoNormal><span style='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"'> Zehler, Peter [mailto:Peter.Zehler@xerox.com] <br><b>Sent:</b> Tuesday, February 19, 2013 3:32 PM<br><b>To:</b> William A Wagner; cloud@pwg.org<br><b>Cc:</b> mfd@pwg.org<br><b>Subject:</b> RE: [MFD] Call for action and Minutes of 18 Feb Cloud WG call<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Bill,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Perhaps you can mention appendices F & G to Google since they contain a JSON mapping of a simple ticket and capability. Another approach would be to create an XML document instance containing just the features that Google mentioned in their specification. XML SPY can generate that easily. The XML file can then be edited to be a bit more realistic. Then XML SPY can create a JSON document from the XML document. I don’t know if there is a tool around to convert JSON to Protobuf but I suspect there is one around. Another alternative would be to edit the document to provide the Protobuf encoding of the PWG semantics for the feature in the specification.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Pete<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-family:"Impact","sans-serif";color:navy'>Peter Zehler</span><span style='color:#1F497D'><br><br></span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy'>Xerox Research Center Webster<br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Email: <a href="mailto:Peter.Zehler@Xerox.com">Peter.Zehler@Xerox.com</a></span><span style='color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Voice: (585) 265-8755</span><span style='color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>FAX: (585) 265-7441</span><span style='color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>US Mail: Peter Zehler</span><span style='color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Xerox Corp.</span><span style='color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>800 Phillips Rd.</span><span style='color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>M/S 128-25E</span><span style='color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Webster NY, 14580-9701</span><span style='color:#1F497D'> </span><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='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"'> <a href="mailto:mfd-bounces@pwg.org">mfd-bounces@pwg.org</a> [<a href="mailto:mfd-bounces@pwg.org">mailto:mfd-bounces@pwg.org</a>] <b>On Behalf Of </b>William A Wagner<br><b>Sent:</b> Tuesday, February 19, 2013 12:58 PM<br><b>To:</b> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br><b>Cc:</b> <a href="mailto:mfd@pwg.org">mfd@pwg.org</a><br><b>Subject:</b> [MFD] Call for action and Minutes of 18 Feb Cloud WG call<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The minutes of the 18 February Cloud WG conference call are posted at:<o:p></o:p></p><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20130218.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20130218.pdf</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Note that there were some important and time critical items discussed, particularly relating to PWG response to the two Cloud Imaging Service specifications provided by Google. Google has given the PWG the opportunity to comment on and potentially contribute to these specifications in a way that may allow us to both make optimum use of the established imaging semantics and to provide our customers with consistent imaging capabilities appropriate to their needs. It is strongly suggested that we should take full advantage of this opportunity.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The Google draft specifications are posted at:<o:p></o:p></p><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/GCP20_CapabilitiesFormat.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/white/GCP20_CapabilitiesFormat.pdf</a> <o:p></o:p></p><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/PrivetCloudDeviceLocalDiscoveryAPIProtocol-0001.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/white/PrivetCloudDeviceLocalDiscoveryAPIProtocol-0001.pdf</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Comments on these specifications, best presented to this mail list, are encouraged. In addition:<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>The PWG Job Ticket and Printer Capabilities standard will be sent to Google with a request that this be accepted as an alternate to the PPD and MSPS (XPS) structures<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Recognizing that the PWG Job Ticket and Printer Capabilities standard is extremely broad in scope, at our request Glen Petrie has generated a table identifying the elements and element value sets appropriate for three levels of Users. This is posted at <a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/pwg.pjt.level.config.for.PWG.h">ftp://ftp.pwg.org/pub/pwg/cloud/white/pwg.pjt.level.config.for.PWG.h</a> (an MS Word version may be available shortly).<o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Since most of these elements/values are optional, it is understood that these three subsets are suggested sets that should be understood by Cloud Print Services in accepting capabilities information from printers and providing that information to Clients, and should be accepted in Print Job Tickets. Cloud Print Services may, of course, recognize a larger, smaller, or different subset. <o:p></o:p></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>The membership is requested to review this table and voice any strong criticisms, objections or preferences promptly, because it is our intent to pass this information on to Google promptly.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It is also requested that the Feb 18 minutes be reviewed and comments sent to this list because several questions arose, particularly with the issue of Print-by-reference, that have a bearing the current work in progress.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Many thanks,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bill Wagner, PWG Cloud WG vice-chair.<o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><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></span></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>