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 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;}
@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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.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;}
--></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">All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have posted v1.182 of the semantic model and the links are available from the PWG Semantic Model page <<a href="http://www.pwg.org/mfd">http://www.pwg.org/mfd</a>>. (Note: please check the version number for the Semantic Model v2 Schema
links. If it is not v1.182 dated October 30<sup>th</sup>, refresh the page to clear the mysterious faulty cache we seem to have.) The easies view of the operations is from <<a href="http://www.pwg.org/mfd/navigate/PwgSmRev1-182_ServiceOperations.html#LinkFF5">http://www.pwg.org/mfd/navigate/PwgSmRev1-182_ServiceOperations.html#LinkFF5</a>>.
The Cloud Print manager and Cloud Print Service specific operations are shown in their own sequence at the bottom of the diagram of the currently defined Print Service operations.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The new operations are:<o:p></o:p></p>
<p class="MsoNormal"><b>GetAvailableJobs</b>: <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Returns the list of jobs ready to be fetched for each of the Printers requested. In the simple case the number of Printers will be one. Higher end “Output Managers” can front end a number of Printers. The API
also accommodates job scheduling at either the Cloud Print Service or the Cloud Print Manager. When the Cloud Print Service is handling job scheduling the list of jobs returned will always contain a single Job for a Printer. The current definition returns
a list of JobUuids. To properly enable Cloud Print Manager job scheduling a job summary element group (i.e., job summary collection in IPP) should be returned. Included in the summary will be the job identifier as well as some minimal set of information
useful for scheduling (e.g., Finishings, Media, PrintColorModeType, Sides)<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal"><b>FetchJob, ReplyToJob: <o:p></o:p></b></p>
<p class="MsoNormal" style="margin-left:.5in">This set of operations are similar to the IPP CreatePrintJob operation. The FetchJob response is analogous to the request portion of CreatePrintJob. This is where the operational attributes (e.g., RequestingUserName,
JobPassword) are passed as well as the Job’s PrintJobTicket. The ReplyToJob request is analogous to the CreatePrintJob response. This is where the newly created Job’s JobUuid is returned along with any UnsupportedElements. As an optimization some appropriate
state information is included.<o:p></o:p></p>
<p class="MsoNormal"><b>FetchDocument, ReplyToDocument:<o:p></o:p></b></p>
<p class="MsoNormal" style="margin-left:.5in">This set of operations are similar to the IPP SendPrintDocument/SendPrintUri operations. . The FetchDocument response is analogous to the request portion of SendPrintDocument/SendPrintUri. This is where the operational
attributes (e.g., RequestingUserName, JobPassword) are passed as well as the Document’s content (i.e., data itself or a reference to it). For implementations that support it a DocumentTicket can also be passed. The ReplyToDocument request is analogous to
the SendPrintDocument/SendPrintUri response. This is where the newly created Document’s DocumentUuid is returned along with any UnsupportedElements if applicable. As an optimization some appropriate state information is included.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal"><b>UpdatePrinterState, UpdateJobState, UpdateDocumentState:<o:p></o:p></b></p>
<p class="MsoNormal" style="margin-left:.5in">This set of operations is used by the Cloud Print Manager to inform the Cloud Print Service of its changes in state. Each of the operations sends sparsely populated object of the appropriate type. For example
if the configuration of a Printer changes then the UpdatePrinterState request would contain only the relevant portions of the Printer’s PrintServiceConfiguration. If media was added, removed or changed in an input tray the InputTrays element group would be
returned. Another example is if the Printer completes a Job. The UpdateJobState request would contain the elements in PrintJobStatus that have been changed and a final version of the PrintJobReceipt.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">I looked at separating out operations for config changes vs. status changes but from a wire representation I did not see much difference. From an implementation point of view not only was the dispatch logic simplified
but also it allows for combining of multiple operations into a single request. For example a configuration change (e.g., change media in a tray) can affect capabilities.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<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"><span style="color:blue">Peter.Zehler@Xerox.com</span></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"><o:p> </o:p></p>
<p class="MsoNormal"><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>