All,
PrintDocumentTicket is only applicable when a Document object is supported by an implementation. A proper Document object was added about 4 years after IPP was published. Originally IPP would allow multiple documents but all the documents were processed the same. A couple years later overrides were introduced that allowed "exception" processing for documents and pages. A couple of years after that the Document object appeared.
In the current model the PrintDocumentProcessing element in the PrintJobTicket can be thought of as the defaults for all the Documents in the Job. A PrintJobTicket is an attribute of the Job object. A PrintDocumentTicket on the other hand is an attribute of a Document object. Note that even if multiple Document are in a Job there is no requirement that each Document has a PrintDocumentTicket. It is not true that a PrintDocumentTicket "Generally applies to multiple document print jobs; but allowed to use for a single document print job". PrintDocumentTickets only apply to Documents regardless of how many Documents are in a Job.
See PWG 5108.01-2011 section 2.6
Pete
Peter Zehler
Xerox Research Center Webster
Email: Peter.Zehler at Xerox.com<mailto:Peter.Zehler at Xerox.com>
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
From: mfd-bounces at pwg.org [mailto:mfd-bounces at pwg.org] On Behalf Of Petrie, Glen
Sent: Tuesday, February 05, 2013 5:30 PM
To: mfd at pwg.org
Subject: [MFD] Help understanding PrintDocumentTicket
All,
Can some clarify, confirm or correct my understand how to use PrintDocumentTicket.
1. Generally applies to multiple document print jobs; but allowed to use for a single document print job.
The PrintDocumentTicket is not contained in a higher collection but I believe it should be in the PrintJobTicket collections. Further, I believe there are '0 - infinity' (really, '0 - Number of Documents) of PrintDocumentTickets since a PrintDocumentTicket applies only to a single document. Thus, a fully described PrintJobTicket would be
+ . . . . . . . . . . . . . . . . . . . . . . . . . +
. PrintJobTicketType .
. .
. + - - - - - - - - - - - - + .
. + - | PrintDocumentProcessing |+ .
. ! + - - - - - - - - - - - - + .
. ! .
+----------------+ . /---------\ ! + - - - - - - - - - - + .
| PrintJobTicket |--.--| -o-o-o- |-- + - | PrintJobDescription |+ .
+----------------+ . \---------/ ! + - - - - - - - - - - + .
. ! .
. ! + - - - - - - - - - - + .
. + - | PrintJobProcessing |+ .
. ! + - - - - - - - - - - + .
. ! .
. ! + - - - - - - - - - - - + .
. + - | PrintDocumentTickets |+ .
. ! + - - - - - - - - - - - + .
. ! 0..infinite .
. ! .
. ! / - - - - - - -\ .
. + - | any ##other | .
. \ - - - - - - -/ .
. 0..infinite .
. .
+ . . . . . . . . . . . . . . . . . . . . . . . . . +
1. Is the above collection definition correct?
Glen
--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
--
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/20130206/e86575bf/attachment-0002.html>