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 14 (filtered medium)"><style><!--
/* Font Definitions */
@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: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.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.EmailStyle20
{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'>Only question I have is the licensing requirements. Otherwise it’s a format to start with, seems would be quick to define “required items” and extensions.<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'>Larry Upthegrove<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'>Licensing (from the WIKI). Also if you go to Microsoft to get the documentation referenced by Google, there is a licensing step.<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'>In order to encourage wide use of the format, Microsoft has released XPS under a royalty-free patent license called the Community Promise for XPS,[36][37] allowing users to create implementations of the specification that read, write and render XPS files as long as they include a notice within the source that technologies implemented may be encumbered by patents held by Microsoft. Microsoft also requires that organizations "engaged in the business of developing (i) scanners that output XPS Documents; (ii) printers that consume XPS Documents to produce hard-copy output; or (iii) print driver or raster image software products or components thereof that convert XPS Documents for the purpose of producing hard-copy output, [...] will not sue Microsoft or any of its licensees under the XML Paper Specification or customers for infringement of any XML Paper Specification Derived Patents (as defined below) on account of any manufacture, use, sale, offer for sale, importation or other disposition or promotion of any XML Paper Specification implementations." The specification itself is released under a royalty-free copyright license, allowing its free distribution.[38]<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"'> cloud-bounces@pwg.org [mailto:cloud-bounces@pwg.org] <b>On Behalf Of </b>William Wagner<br><b>Sent:</b> Monday, July 11, 2011 8:53 AM<br><b>To:</b> cloud@pwg.org<br><b>Subject:</b> [Cloud] low lying fruit<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><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><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>