[MFD] RE: Help understanding PrintDocumentTicket

[MFD] RE: Help understanding PrintDocumentTicket

[MFD] RE: Help understanding PrintDocumentTicket

Petrie, Glen glen.petrie at eitc.epson.com
Wed Feb 6 16:23:12 UTC 2013


Peter,

 

Thanks for the history but I still don't understand where Document Ticket fits in.  Maybe I found it, please correct my diagram below if I am wrong.

 

A PrintDocumentTicket(s) is not part of the a PrintJobTicket but is part of a PrintJob ????

 

PrintJob --+----PrintJobTicket

                  |----PrintDocumentTicket(s)

                  |----Document (is content in PrintJob; i.e. not by ref)             

                  |----??????

 

 

glen

 

 

 

Below is just reference for 2108.1

 

Document Ticket  

A data object that contains a User‟s <service>Intent for Document processing and descriptive properties of a Document in a Job. Any Document processing properties in the Document Ticket for a particular Job will override the values specified in the Job Ticket‟s Document processing  properties. The content of a Document Ticket is configured by a User through a <service> Client.

 

Job Ticket   

A data object that contains a User's Job-level Intent for Document processing, Job processing and descriptive Job properties of a Job, sent to an MFD Service. Job Elements apply to the entire Job. Document processing Elements apply to all Documents within the Job unless overridden at the Document level (See Document Ticket). The content of a Job Ticket is configured by a User through a Client.

 

 

*	A Job Ticket relates to the Job and all Documents in the Job, except those for which a Document Ticket is created.
*	A  Document  Ticket  relates to a specific  Document  and any property specified in a  Document Ticket overrides the value of that property that may be specified in the Job Ticket.

 

________________________________

From: Zehler, Peter [mailto:Peter.Zehler at xerox.com] 
Sent: Wednesday, February 06, 2013 4:15 AM
To: Petrie, Glen; mfd at pwg.org
Subject: RE: Help understanding PrintDocumentTicket

 

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
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                .                                

                     .                                                   .                                

                     + . . . . . . . . . . . . . . . . . . . . . . . . . +                                

                                                                                                          

 

2.	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/be3c0b6a/attachment-0002.html>


More information about the mfd mailing list