Hi Pete,
While reviewing PWG Raster Format spec, I have two more comments for Print
Job Ticket and Associated Capabilities:
1. The attribute name: "PWGRasterDocumentBackside" in Table 3 (page 36),
Table 4 (page 57), Table 6 (page 73) should be changed to
"PWGRasterDocumentSheetBack" for being consistent with the Schema and PWG
Raster Format spec.
2. The document format "image/pwg-raster" should be in DocumentFormatWKV.
Regards,
-Nancy
----- Forwarded by Nancy Chen/OKIDATA/OKI_DATA_CORP/OKI_ELECTRIC/US on
02/29/2012 06:03 PM -----
Nancy Chen/OKIDATA/OKI_DATA_CORP/OKI_ELECTRIC/US
02/27/2012 12:44 PM
To
Peter.Zehler at xerox.com,
cc
mfd at pwg.org, cloud at pwg.org
Subject
Oki Data has reviewed the Print Job Ticket and Associated Capabilities
specification and has comments
Hi Pete,
I have no further comments for the version 20120117 in addition to those
posted already.
Here are the comments against the new updated version (20120227) today:
Line 373-376 - It's not clear "a protocol" here is what protocol. Readers
need to do a lot of guessing here. It's any printing protocol? Or only a
protocol for cloud printing?
Line 360 - Please also reference the section number in RFC291 here - much
easier for readers not familiar with IPP to find.
Line 413 - Figure 7 caption still labels this element as "InsertSheet
Datatype". Same problem with Figures 9 -12, and Figures 15, 17-23.
Line 521 - It's not clear "that element" here means the PageRanges
PrintJobTicket element or a vendor extension that controls this feature.
Please reword.
Thanks,
-Nancy
--------------------------------------------------------------------------------
Nancy Chen
Principal Engineer
Solutions and Technology
Services and Solution Business - US
Oki Data
2000 Bishops Gate Blvd.
Mt. Laurel, NJ 08054
Phone: (856)222-7006
Email: Nancy.Chen at okidata.com
--
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/20120229/d04a686c/attachment-0002.html>