Loading

Partitioning for subset/page programming

Partitioning of the document

Syntax

XPath: //<Element>/@PartIDKeys

Type

Enumeration

Supported range

@PartIDKeys

Description

RunIndex

The element is partitioned with RunIndex. A RunIndex defines a set of logical pages from the RunList.

Run

The element is partitioned with Run. A Run defines an name for an individual RunList partition.

BundleItemIndex

The element is partitioned with BundleItemIndex. A BundleItemIndex defines a set of indexed bundle of physical sheets called BundleItem.

Description

The following elements can be partitioned:

Element

Allowed partition type

Use for

/JDF/ResourcePool/RunList

Run

Force to front/back

/JDF/ResourcePool/LayoutPreparationParams

RunIndex

Image shift, plexity, inserts (media, jog, stapling)

/JDF/ResourcePool/DigitalPrintingParams

RunIndex

Media

/JDF/ResourcePool/GatheringParams

RunIndex

BundleItemIndex

Offset stacking

/JDF/ResourcePool/StitchingParams

RunIndex

BundleItemIndex

Stapling

/JDF/ResourcePool/Folding

RunIndex

BundleItemIndex

Folding

/JDF/ResourcePool/HoleMakingParams

RunIndex

BundleItemIndex

Punching

/JDF/ResourcePool/CreasingParams

RunIndex

Creasing

/JDF/ResourceLinkPool/ComponentLink/AmountPool/PartAmount/Part/

RunIndex

BundleItemIndex

Page programming for finishing

According to the type of partition used, the sub-nodes must specify the attribute @RunIndex, or @Run with @Pages, or @BundleItemIndex

RunIndex partitioning

Syntax

XPath: //<Element>[@PartIDKeys="RunIndex"]/<Element>/@RunIndex

Type

Range list

Supported values

@RunIndex

Description

Range list

Selects a set of logical pages from the RunList.

A Range List is an array of mixed Ranges and individual indices separated by whitespace. A Range consists in two indices connected with a tilde (~).

Description

NOTE

All resources, except RunList, are allowed to be partitioned with RunIndex.

Indices are the logical reference to the zero-based page number of the RunList. For example, 0 is the first page of the document and 9 is the tenth page of the document.

Negative numbers reference pages from the back of a file. For example, -1 is the last page of the document, and -2 is the before-last page of the document.

Example

  • Individual indices: “0”, “2 5”, “50 100 -1”

  • Ranges: “0 ~2”, “5 ~ 22 50 ~ 100”, “0 ~ 1 2 ~ -3 -2 ~ -1”

  • Mixed: “0 1 ~ 3 5 22 100 ~ -1”

If partitioned, GatheringParams, StitchingParams, and FoldingParams must have the same RunIndex partition values.

When different resource are used, GatheringParams, StitchingParams, and FoldingParams are allowed to have different RunIndex partition values.

Within the same resource, the values for RunIndex are not allowed to overlap or be repeated. So the following is not correct:

<DigitalPrintingParams PartIDKeys=”RunIndex”>

<DigitalPrintingParams RunIndex=” 0 ~ 3” …/>

<DigitalPrintingParams RunIndex=” 3 ~ 4” …/> => WRONG

<DigitalPrintingParams RunIndex=” 5 ~ -1” …/>

<DigitalPrintingParams>

Remark

For ranges with negative values, only one range of the kind [n ~ m] is supported, where n>0 and m>0.

All page rages with positive values are supported.

Run partitioning

Syntax

XPath: //RunList[@PartIDKeys="Run"]/RunList/@Run

Type

String

Syntax

XPath: //RunList[@PartIDKeys="Run"]/RunList/@Pages

Type

Integer range list

Supported values

@Run

Description

String

A string that uniquely identifies an individual RunList partition.

@Pages

Description

Range list

Select a set of logical pages from the RunList.

A Range List is an array of mixed Ranges and individual indices separated by whitespace. A Range consists in two indices connected with a tilde (~).

NOTE

Only RunList is allowed to be partitioned with Run partition.

BundleItemIndex partitioning

Syntax

XPath: //<Element>[@PartIDKeys="BundleItemIndex"]/<Element>/@BundleItemIndex

Type

Integer range list

Supported values

@BundleItemIndex

Description

Range list

Select a set of zero-based numbered BundleItems.

A Range List is an array of mixed Ranges and individual indices separated by whitespace. A Range consists in two indices connected with a tilde (~).

Syntax

XPath: //RunList[@PartIDKeys="Run"]/RunList/@EndOfBundleItem

Type

Boolean

Supported values

@EndOfBundleItem

Description

False

Pages from this RunList partition will be part of the same BundleItem of the next RunList partition.

Default value for all but last RunList partitions.

InsertSheet with @IncludeInBundleItem="New" or "Before" MUST NOT be specified after this RunList partition.

True

The last page in the RunList partition is the last page of a BundleItem.

Default value for the last RunList partition.

An InsertSheet with @IncludeInBundleItem="New" MAY be specified after this RunList partition.

Syntax

XPath: //LayoutPreparationParams/InsertSheet/@IncludeInBundleItem

Type

Enumeration

Supported values

@IncludeInBundleItem

Description

None (default)

This InsertSheet is not included in a new BundleItem. It is part of the same BundleItem of the RunList partition to which it is associated, even if @EndOfBundleItem=”true”.

New

A new BundleItem is created. Unless it is an InsertSheet before the first page, A RunList partition with @EndOfBundleItem=”true” MUST be specified before it.

Before

This InsertSheet is included in the BundleItem that occurs before this InsertSheet. An InsertSheet with attribute @IncludeInBundleItem=”New” MUST be specified before it.

Description

Only GatheringParams, StitchingParams and FoldingParams can be partitioned either with RunIndex or with BundleItemIndex.

NOTE

BundleItemIndex must not be used when RunIndex partition is possible. The BundleItemIndex must only be used when InsertSheets must be finished independently from the RunList pages.

RunList/@EndOfBundleItem is used to define BundleItem for logical pages of the document defined by RunList.

InsertSheet/@IncludeInBundleItem is used to define BundleItem for the physical extra sheets defined by InsertSheets

BundleItems are numbered starting at 0. BundleItemIndex is a range list referring to BundleItems numbers and NOT to logical pages or sheets. Negative values are NOT allowed for BundleItemIndex.

A new Bundeltem is defined with BundleItemIndex values increased by 1 when one or both of the following occurs:

  • RunList/@EndOfBundleItem=”true”,

  • InsertSheet/@IncludeInBundleItem="New".

InsertSheets with @IncludeInBundleItem=”None” are considered as part of the same BundleItem to the associated RunList partition, even if @EndOfBundleItem=”true”. So, if @EndOfBundleItem=”true” is defined in a RunList partition, Trailing InsertSheets after it will NOT be separated in a new BundleItem if @IncludeInBundleItem=”None”. The new BundleItem will be created just after these InsertSheets.

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.

Subset stapling

Syntax

XPath: /JDF/ResourcePool/StitchingParams[@PartIDKeys="RunIndex"]/StitchingParams[@RunIndex="<value>"]

Syntax for staple positions

XPath: /JDF/ResourceLinkPool/ComponentLink[@Usage="Input"]/AmountPool/PartAmount[@Orientation]/Part[@RunIndex="<value>"]

Where @RunIndex="<value>" defines the same range as for StitchingParams.

Description

The stapling position is specified using partitioning of the ComponentLink as described above.

For stapling of several subsets, each orientation must be defined in:

  • Separate PartAmount partitions

  • The same AmountPartPool

Example: the ResourceLinkPool for a landscape stapling orientation from page 1 to 4 and from page 9 to 12

<ResourceLinkPool>

<ComponentLink Usage="Input" rRef="res_ref" CombinedProccessIndex=”7”>

<AmountPool>

<PartAmount Orientation="Flip0">

<Part RunIndex=”0 ~ 3"/>

</PartAmount>

<PartAmount Orientation=" Flip0">

<Part RunIndex="8 ~ 11"/>

</PartAmount>

</AmountPool>

</ComponentLink>

<ComponentLink Usage="Output" rRef="res_ref" CombinedProccessIndex=”7”>

<AmountPool>

<PartAmount Orientation="Flip0">

<Part RunIndex=”0 ~ 3"/>

</PartAmount>

<PartAmount Orientation=" Flip0">

<Part RunIndex="8 ~ 11"/>

</PartAmount>

</AmountPool>

</ComponentLink>

</ResourceLinkPool>

The stapling at job level is not supported if a stapling at subset level is specified. This means that the attributes of the following element are ignored when this element contains one or more other StitchingParams elements: /JDF/ResourcePool/StitchingParams

Insert

Syntax

XPath: JDF/ResourcePool/LayoutPreparationParams[@PartIDKeys="RunIndex"]/LayoutPreparationParams[@RunIndex="<value>"]/InsertSheet[@SheetFormat="Blank" and @SheetType="InsertSheet" and @SheetUsage="<value>"]

@SheetUsage

Description

Header

The insert sheet must be inserted before the subset defined by @RunIndex="<value>".

Trailer

The insert sheet must be inserted after the subset defined by @RunIndex="<value>".

A media for the insert can be specified with //InsertSheet/Layout/MediaRef.

By default, the jogging and the stapling defined for a subset in GatheringParams and StitchingParams are applied to the inserted sheets attached to this subset.

It is allowed to override this behaviour with attribute @IncludeInBundleItem.

Supported values for @IncludeInBundleItem are:

  • “None” (default)

  • “New”: A new bundle item is created

  • “Before”: Insert sheet is member of the previous bundle

All following Inserts with @IncludeInBundleItem ="before" must be part of this bundleItem.

Jogging and Stapling can be specified explicitly for Inserts using Gathering and StichingParams partition with BundleItemIndex.

NOTE

BundleItemIndex must not be used when the RunIndex partition is possible.