attachment-0001
<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;}
/* 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;}
code
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
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='color:#1F497D'> We have been having meetings on Cloud printing for a year now, and we have not gotten past settling on use cases. Meanwhile, the reality has continued to progress. One of our main concerns expressed when we start looking at this was not that the PWG wanted to specify the entire process, but that we wanted to encourage those who did develop the standards to use the elements for the PWG semantic model to specify printer characteristics and job tickets.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I have belatedly read through the public Google interface standards and see that they have selected a “j</span>ob ticket that can be in XPS (<a href="http://en.wikipedia.org/wiki/Open_XML_Paper_Specification">XML Paper Specification</a>) or PPD (<a href="http://en.wikipedia.org/wiki/PostScript_Printer_Description">Postscript Printer Description</a>) format. In the future, other job ticket formats may be supported.” Furthermore, “The <code><span style='font-size:10.0pt'>capabilities</span></code> and <code><span style='font-size:10.0pt'>defaults</span></code> parameters[of the printer] can be in XPS (<a href="http://en.wikipedia.org/wiki/Open_XML_Paper_Specification">XML Paper Specification</a>) or PPD (<a href="http://en.wikipedia.org/wiki/PostScript_Printer_Description">Postscript Printer Description</a>) formats. Additional formats may be supported in the future to describe the printer capabilities and defaults.”<o:p></o:p></p><p class=MsoNormal>I suggest that defining a job ticket and a printer description following the semantic model (in a new or in PPD and/or XPS format) would achieve one of our primary purposes, would best utilize the PWG expertise, and could be done relatively quickly. Pete has a job ticket schema posted. (<a href="ftp://ftp.pwg.org/pub/pwg/mfd/schemas/PwgPrintJobTicket_v1.129.zip">ftp://ftp.pwg.org/pub/pwg/mfd/schemas/PwgPrintJobTicket_v1.129.zip</a> )<span style='color:#1F497D'> This would be applicable to Google Cloud Print as well as other Cloud Imaging approaches, including one the PWG may wish to define.<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></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>