Syntax
XPath:
/JDF[@Type="Combined"]
/JDF[@Category="DigitalPrinting"]
/JDF[contains(@Types=<see table below>)]
The JDF root node is a "Combined Process" node, which specifies the attributes @Type, @Category and @Types.
The ticket must contain only one JDF node.
The supported processes which can be listed in the attribute @Types are:
|
Supported processes |
Mandatory or optional |
|---|---|
|
LayoutPreparation |
mandatory |
|
Imposition |
mandatory |
|
Interpreting |
mandatory |
|
Rendering |
mandatory |
|
ColorCorrection |
optional |
|
ColorSpaceConversion |
optional |
|
Screening |
optional |
|
DigitalPrinting |
mandatory |
|
oce:Mailbox |
optional |
|
HoleMaking |
optional |
|
Folding |
optional |
|
Stitching |
optional |
|
Trimming |
optional |
|
Gathering |
optional |
|
CoverApplication |
optional |
|
Creasing |
optional |
When a process is present in @Types, its parameter resources and the input and output resources must be specified in the /JDF/ResourceLinkPool element. Intermediate resources do not need to be specified, see JDF 1.3. For example, LayoutPreparation implies the presence of LayoutPreparationParams.
ColorCorrection, HoleMaking, Creasing, Folding, Stitching, oce:Mailbox and CoverApplication:
Do not specify these processes more than once.
When you use CoverApplication for perfect binding jobs:
Do not specify: HoleMaking, Creasing, Folding, Stitching and Gathering.
It is allowed to specify Trimming.
Gathering is the only process allowed to be specified more than once.
Remark
A Process node is not allowed to have a JDF child node, see [ICS-IDP].
LayoutPreparation, Imposition, Interpreting, Rendering, and DigitalPrinting must always be specified once, even if these are not used. For example:
<JDF Type="Combined" Category="DigitalPrinting" Types="LayoutPreparation Imposition Interpreting Rendering DigitalPrinting"/>