Never mind!!! Because the PJT will be in xml format, the header will
define type, etc. I was looking at a C-Code implementation and will
have to add a header for this info.
glen
________________________________
From: mfd-bounces at pwg.org [mailto:mfd-bounces at pwg.org] On Behalf Of
Petrie, Glen
Sent: Friday, January 13, 2012 8:23 AM
To: mfd at pwg.org
Subject: [MFD] How to identify a PWG Job Ticket
Pete (All),
How do you identify that the PJT of the PJ is a PWG:PJT and not a
JDF:PJT or Special:PJT or My:PJT. In general, the world will never
100% use just PWG:PJT and even the version of the PWG:PJT may change
over time. And, like IPP, I suspect it will not be long before we
officially define different levels of support (min requirements) of PJT
for differing environments.
[I am not quite sure if the current PWG:PJT is not really a PWG:PJ;
that is a PJ = PJT + Doc(uri)!!???]
Maybe I missed it but in case I didn't.
I think we need to define a general Print Job object with
Print Job {
Print Job Ticket Format
Print Job Ticket Level
Print Job Ticket Version
Document URI
}
Example:
PJ {
PJTF = PWG:PJT
PJTL = MOBILE
PJTV = 1.00
DURI = //here/doc
}
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/20120113/974e0d07/attachment-0002.html>