[Cloud] low lying fruit

[Cloud] low lying fruit

[Cloud] low lying fruit

larryupthegrove larryupthegrove at comcast.net
Mon Jul 11 16:33:09 UTC 2011

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


Larry Upthegrove


Licensing (from the WIKI).  Also if you go to Microsoft to get the
documentation referenced by Google, there is a licensing step.

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]


From: cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] On Behalf Of
William Wagner
Sent: Monday, July 11, 2011 8:53 AM
To: cloud at pwg.org
Subject: [Cloud] low lying fruit


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

I have belatedly read through the public Google interface standards and see
that they have selected a  "job ticket that can be in XPS (XML Paper
Specification <http://en.wikipedia.org/wiki/Open_XML_Paper_Specification> )
or PPD (Postscript Printer Description
<http://en.wikipedia.org/wiki/PostScript_Printer_Description> ) format. In
the future, other job ticket formats may be supported."  Furthermore, "The
capabilities and defaults parameters[of the printer] can be in XPS (XML
Paper Specification
<http://en.wikipedia.org/wiki/Open_XML_Paper_Specification> ) or PPD
(Postscript Printer Description
<http://en.wikipedia.org/wiki/PostScript_Printer_Description> ) formats.
Additional formats may be supported in the future to describe the printer
capabilities and defaults."

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.
(ftp://ftp.pwg.org/pub/pwg/mfd/schemas/PwgPrintJobTicket_v1.129.zip ) This
would be applicable to Google Cloud Print  as well as other Cloud Imaging
approaches, including one the PWG may wish to define.


Bill Wagner

This message has been scanned for viruses and 
dangerous content by  <http://www.mailscanner.info/> MailScanner, and is 
believed to be clean. 

This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/cloud/attachments/20110711/2f380c5f/attachment-0001.html>

More information about the cloud mailing list