attachment-0001

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII"> <META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD> <BODY> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>My comments on whether to call the attribute that the submitter supplies in the proposed FSG OpenPrinting WG papiPrinterQuery argument, "job-template" or "job-context" or "processing":</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>There is one very important attribute, in fact the most important attribute, that a papiPrinterQuery needs to be able to submit and that is "document-format=xxx" in his query.  It is the only attribute that IPP allows the submitter to supply for its Get-Printer-Attributes operation in order to constrain the supported results that the Printer returns.  In IPP, the "document-format" attribute is NOT a Job Template attribute, it is an Operation attribute.  The reason is that it is not subject to "ipp-attribute-fidelity".  The Printer MUST reject a job if the "document-format" isn't a supported one, even if "ipp-attribute-fidelity" is 'false'.  Otherwise, the Printer prints garbage for an unsupported document format.</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>I see three options for papiPrinterQuery:</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>1. Add "document-format" as an additional input parameter to papiPrinterQuery.  Then rename "job-context-attrs" to "job-template-attrs", since only Job Template attributes would be supplied there.  </FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>2. Rename "job-context-attrs" to "processing-attrs".  The PWG Semantic Model current version does include DocumentFormat as one of the Processing attributes.</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>[Note:  The PWG Semantic Model spells attribute names, but not keyword values, as mixed case, hence DocumentFormat as opposed to IPP's document-format.]</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>[Comment on the PWG Semantic Model: indicate in both the AttributeFidelity and DocumentFormat Processing attributes in section 4.3 Document Attributes, that AttributeFidelity does NOT apply to DocumentFormat.]</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>3. Leave "job-context-attrs" as it is and clarify that it includes any of the IPP Job Template attributes and the IPP "document-format" Operation attribute.</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>Currently, the PAPI spec is using the IPP terminology and attribute name spelling, not the PWG terminology and attribute name spelling which is fine and is as the PWG Semantic Model intends.  So I prefer 1 or 3.  Lets not mix the terminology in PAPI between IPP and PWG Semantic Model.  Also when the PWG Semantic Model invents something new, such as the Document object, it is the intent to write a detailed IPP extension specification to pickup the semantics with IPP terminology and IPP attribute/operation spelling.</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>ISSUE for PWG Semantic Model and FSG PAPI spec:</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>When the Document object is added, do we need a separate context attribute list to be supplied in the papiPrinterQuery function call, or can any Document Template attributes be included in the same list?</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>Presumably there should be two IPP Printer Description attributes that contain the names of the Job Template versus Document Template attributes: "job-template-attributes-supported" and "document-template-attributes-supported" since the lists are not the same.  For example, "job-priority" is only a Job Template attribute. </FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>[PWG spelling and terminology would be: JobProcessingAttributesSupported and DocumentProcessingAttributesSupported).  Note: that this is one case where the attribute names between IPP and PWG Semantic Model will differ in more than spelling because of differing terminology.]</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff size=2>Tom</FONT></SPAN></DIV> <DIV><SPAN class=080125216-26082002></SPAN><FONT face=Tahoma><FONT size=2><SPAN class=080125216-26082002><FONT face=Arial color=#0000ff> </FONT></SPAN></FONT></FONT></DIV> <DIV><FONT face=Tahoma><FONT size=2><SPAN class=080125216-26082002></SPAN></FONT></FONT> </DIV> <DIV><FONT face=Tahoma><FONT size=2><SPAN class=080125216-26082002> </SPAN>-----Original Message-----<BR><B>From:</B> Alan Hlava [mailto:hlava@us.ibm.com]<BR><B>Sent:</B> Thursday, August 22, 2002 10:03<BR><B>To:</B> printing-cap@freestandards.org<BR><B>Subject:</B> Re: [printing-cap] (no subject) [Capability Query addition to PAP I]<BR><BR></DIV></FONT></FONT> <BLOCKQUOTE><BR><FONT face=sans-serif size=2>On Thursday, 08/22/2002 at 12:55 AST, Michael Sweet <mike@easysw.com> wrote:<BR>> We could use "job-context" instead of "job-template" as the prefix;<BR>> I chose "job-template" just because that is the nomenclature that<BR>> IPP uses...<BR>Should PAPI then use the "job-template" terminology for the new papiPrinterQuery argument?  </FONT> <BR><BR><FONT face=sans-serif size=2>Regards,</FONT> <BR><BR><FONT face=sans-serif size=2>Alan Hlava<BR>IBM Printing Systems Division<BR>hlava@us.ibm.com</FONT></BLOCKQUOTE></BODY></HTML>