[MFD] Technical Interface Consulting has reviewed the Print Job Ticket and Associated Capabilities specification and has comments

[MFD] Technical Interface Consulting has reviewed the Print Job Ticket and Associated Capabilities specification and has comments

[MFD] Technical Interface Consulting has reviewed the Print Job Ticket and Associated Capabilities specification and has comments

William Wagner wamwagner at comcast.net
Fri Feb 24 19:31:10 UTC 2012


Minor editorial comments:

Table 3 - meaning of "implicit" is unclear

Line 707 - Information should be initial caps. Also should appendix be
labeled Normative?

Line 708 - space after Table 4

Table 4 - some field values have unfortunate break (e.g. entries under
DocumentDigitalSignatureSupplied, JobHoldUntilTime). Also, it would be
better to avoid page breaks splitting up element properties

Table 4 - Units element name is not bold

Line 731 - Should appendix be labeled Normative?

Section 16 - Although the necessary information in provided between Section
15 and 16,  and it is understood that capabilities elements mirror job
ticket elements except for syntax, it is a little disconcerting to see Print
Service Capabilities as just a listing of data types. I would suggest
section 16  be ordered by element, giving the different syntax and perhaps
constrant. Full replication of the other fields from Section 15  probably
would not be necessary. (I realize this would be time consuming and, if the
consensus is that this is desirable, I would be willing to help create this
alternate table)

Section 17 - should appendix be labeled Informative?

Line 769 -  Should be new page, Appendix D (already have a Appendix C) and
labeled Informative. Note subsequent appendixes need to be renumbered

Line 770 - space after "Table 7"

Line 777 - Should be Appendix E. It is confusing have two sections with the
same title.  Also, since  Print Service Capabilities is one of the subjects
of the paper (although the title evades this by referring to associated
capabilities, with the distinction unclear), why is this section not in the
main body of the specification.

Line 783 - is table 3 the intended reference? If so, might be better to
repeat the table without the compliance information.

Line 791-794 excess lines

Line 860 - Suggest new page, correct appendix letter, informative?, 

 

 

 

 


-- 
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/mfd/attachments/20120224/291c1c98/attachment-0002.html>


More information about the mfd mailing list