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=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@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:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 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.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-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.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:48454344;
mso-list-type:hybrid;
mso-list-template-ids:-1977352046 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-tab-stop:1.0in;
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>In the February Cloud Imaging face-to-face, we asked Glen to find out if he could spend time making a proper subset of PWG PJT for GCP/CDD. He did and he could and he provided his suggestions in a nice draft. But on discussing this, it was unclear that we had a consistent notion of what we wanted to do with what turned out to be two subsets. I think we all see some value in Glen’s contribution; buy we need agree on what this is. I offer the following thoughts and questions. Corrections and contradictions are welcomed.<o:p></o:p></p><p class=MsoNormal><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 motivation to define the proper subset was the belief that the size of the full PJT set and the perceived lack of need for some of the elements in the typical cloud application would make the set appear unduly complex and inappropriate to Google and other Cloud Print Service suppliers.<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]>As Mike indicated that “Supported elements are the intersection of the client, cloud, and printer capabilities”. <span style='font-family:"MS Gothic"'>⁃</span>He also wrote “Defining levels are nice, but clients still need to discover what elements are supported by the printer” and that limiting to elements in support level “ prevents adoption of useful higher-level elements.” <o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>It is my , perhaps incorrect, understanding that the print job ticket elements in a job request did not need to specify values for all of the elements in the reported printer capabilities. Indeed, a job request could be sent without the client even querying printer capabilities. Therefore, although it may be desirable for a Client to support (which is to say, provide values for) a set of elements commensurate with the anticipated needs of the User, it is unnecessary to require clients to support some defined subset of elements or values. I therefore would moderate the contention that clients need to discover what elements are supported by the printer, to say that client would need to determine whether the printer support those elements and value that are of interest to the User. Therefore, element subsets may be at most useful suggestions to what different clients should support.<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>4.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>The Printer (and Cloud Print Manager) will support those few elements that are required and whatever additional elements are necessary to expose the service capabilities. There appears no reason that they should support elements for capabilities that do not exist. So the subsets are not applicable to them beyond perhaps being suggestions as to what features might be provided.<o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>5.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]>If these contentions are valid, the Cloud Server must communicate subset of printer capabilities determined by the printer and a subset of desired job elements determined by the Client. If Cloud servers have essentially infinite capacity, they should handle the full set of elements and values. But practically, if the Cloud Print Service is intended for an identifiable User base, it is probably justified to support both for capabilities and job requests, a subset of the full PJT elements and values. That is, a Cloud Print Service need support just an element subset which is the intersection of the client job requests and printer capabilities. I think that our proper subset was to be our suggestion of what might be in that intersection. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bill Wagner<o:p></o:p></p><p class=MsoNormal style='margin-left:.25in'><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>