Océ imagePRESS C7010VPS series, Техническое руководство

Страница: 274 / 362

GatheringParams, StitchingParams or FoldingParams share the same BundleItemIndex paritions
numbering. If one of these resources is partitioned using BundleItemIndex, then ALL of these
three resource MUST be partitioned using BundleItemIndex.
Force to front / Force to back
Syntax
XPath: /JDF/ResourcePool/RunList[@PartIDKeys="Run"]/RunList[@Run="<value>" and
@Pages="<value>"]/InsertSheet[@IsWaste="false" and @SheetFormat="Blank" and
@SheetType="FillSheet" ]/@SheetUsage
Type
Enumeration
Supported range
@SheetUsage Description
FillForceFront Force to front
FillForceBack Force to back
Description
Attribute @SheetUsage specifies that the first pages of each range indicated by
@Pages="<value>" are either forced to front or back.
@Run="<value>" is an arbitrary ID for the RunList Partition.
Subset Jogging
Syntax
XPath: /JDF/ResourcePool/GatheringParams[@PartIDKeys="RunIndex”]/
GatheringParams[@RunIndex="…"]/Disjointing/@OffsetDirection
Type
Enumeration
Supported range
@OffsetDirection Description
None No jogging
Alternate Each copy of the job is jogged
Description
Subset jogging must not be defined in DigitalPrinting (as at job level), but in the Gathering
process.
“Gathering” process must be present at the end of the list of processes in @Types in the JDF
node.
The jog occurs at the start of the ranges specified by @RunIndex.
If the run index range contains the page “0”, the jogging is not decoded for this range. The job
level value will be applied.
In case of jogging with Inserts, Gathering partition is allowed to be defined with BundleItemIndex
instead of RunIndex.
Partitioning for subset/page programming
274 Chapter 10 - JDF interface specification
imagePRESS C7010VPS series v2.2