[IPP] Apple has reviewed the IPP FaxOut specification and has comments

[IPP] Apple has reviewed the IPP FaxOut specification and has comments

[IPP] Apple has reviewed the IPP FaxOut specification and has comments

Michael Sweet msweet at apple.com
Fri Jun 28 13:04:06 UTC 2013


Still more:

Section 7.4.3: The required list of cover-sheet-info member attributes was not updated to use the new names "from-name" and "to-name".


On Jun 28, 2013, at 8:47 AM, Michael Sweet <msweet at apple.com> wrote:

> Additional comments after review of the latest SM 2.0 document:
> 
> Section 7.1.1: Add the following paragraph:
> 
>     "Note: The Semantic Model defines a single InputSource element, which does not capture all of the necessary input intent. IPP FaxOut instead maps elements from the CopyInTicket group to do so." [I wanted to add something about SM 2.0 adopting this approach, but we usually avoid prognostication in our specs...]
> 
> Section 7.3: Add input-attributes-actual (1setOf collection), with reference to 7.1.1 for the member attributes. This provides a receipt of hardcopy input-attributes values. CONDITIONALLY REQUIRED for printers with scan capabilities.
> 
> Section 7: Add new 7.x Document Description Attributes, 7.x.1 with input-attributes-actual (collection), with reference to 7.1.1 for the member attributes. This provides a per-document receipt of hardcopy input-attributes values. CONDITIONALLY REQUIRED for printers with scan capabilities and support for the document object.
> 
> Section 9.2: Add input-attributes-actual job description attribute to list for scan-capable printers, add a new scan + document object paragraph for input-attributes-actual document description attribute.
> 
> Section 12.1: Add input-attributes-actual job description and document description attributes.
> 
> Section 13.1: Add reference to 5100.5 (document object) and 5108.04 (copy service)
> 
> 
> On Jun 27, 2013, at 8:12 AM, Michael Sweet <msweet at apple.com> wrote:
> 
>> Follow-up comments based on the feedback we have gotten so far:
>> 
>> Section 8.2 does not mention that the 'fax-modem-xxx' keywords are defined in PWG 5107.3.
>> 
>> Section 8.2 does not define the equivalent of the 'connecting-to-defice' value from "printer-state-reasons". Should we define keyword(s) to describe this and/or the following intermediate states: Dialing, Answered, Training, and Connected?
>> 
>> Section 12.2 should not re-register PWG 5107.3 keyword values for "job-state-reasons".
>> 
>> Section 13.1 is missing a reference to PWG 5107.3.
>> 
>> _________________________________________________________
>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>> 
>> 
>> -- 
>> This message has been scanned for viruses and 
>> dangerous content by MailScanner, and is 
>> believed to be clean.
>> _______________________________________________
>> ipp mailing list
>> ipp at pwg.org
>> https://www.pwg.org/mailman/listinfo/ipp
> 
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
> 
> 
> -- 
> This message has been scanned for viruses and 
> dangerous content by MailScanner, and is 
> believed to be clean.
> _______________________________________________
> ipp mailing list
> ipp at pwg.org
> https://www.pwg.org/mailman/listinfo/ipp

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


-- 
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/ipp/attachments/20130628/15bce9fd/attachment-0001.html>


More information about the ipp mailing list