Harry,
I agree with you that JDF job tickets can be quite suitable for enterprise
printing such as PSI. And if there happen to be any deficiencies, a "psi"
namespace could be used to add functionality to it. I'm sure the CIP4
would also entertain changing the JDF spec to better suit the PSI needs,
too. Like you mentioned, though, the JDF spec is quite large and can be
daunting to absorb, even though we'd only be interested in a fraction of it
for enterprise printing.
At 02:05 PM 6/14/2002 -0600, Harry Lewis wrote:
>Peter recently posted a PWG Job Ticket proposal derived from IPP
>attributes. While I wholeheartedly support establishing and leveraging the
>PWG Semantic Model (and deriving it largely from IPP)... I want to bring
>to the attention of PWG members that there is already a robust XML Job
>Ticket defined by the CIP4 JDF working group.
><http://www.cip4.org/>http://www.cip4.org/>>JDF has it's roots in Graphic Arts and Workflow and , in it's full
>definition, the JDF JT is not as simple as what Peter is proposing. The
>JDF JT incorporates aspects of the Adobe Portable Job Ticket Format and
>addresses things like order of operations, has longevity and facilitates
>job tracking and accounting. Nonetheless, the JDF Job Ticket can be
>reduced and simplified.
>>Because the JDF job ticket is already gaining acceptance in some industry
>segments and overlaps with our goals to a degree, I suggest we consider
>either basing our Job Ticket definition on JDF (see link to simple
>example, below) or, at least, assure a simple mechanical XSLT mapping
>between the two.
>><ftp://ftp.pwg.org/pub/pwg/semantic_model/simple_jdf_jt.xml>ftp://ftp.pwg.org/pub/pwg/Semantic_model/Simple_JDF_JT.xml>----------------------------------------------
>Harry Lewis
>IBM Printing Systems
>----------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/ps/attachments/20020617/1f613167/attachment-0001.html