66
Page 55
Page 55
Table 3-13 Additional contents of the abstract parameter Resource elements
Name
Data Type
Description
NoOp ?
New in JDF 1.1
boolean
Indicates whether a resource or resource partition should be treated as if it
did not exist, e.g., to switch off a complete process step for the process that
requires the given parameter resource or partition as input. Default = false,
i.e., the Resource is operational and should be honored.
3.7.1.2 Intent Resources
Intent resources define the details of products to be produced without defining the process to produce them. In
addition, they provide structures to define sets of allowable options and to match these selections with prices. The
details of all intent resources are described in Section 7.1 Intent Resources. The abstract Intent resource element
contains no attributes or elements besides those contained in the abstract Resource element.
3.7.1.3 Implementation Resources
Implementation resources define the devices and operators that execute a given node. Only two implementation
resource types are defined: Employee (see Section 7.2.51) and Device, each of which is described in greater detail
in the Chapter 7.
Implementation resources can only be used as input resources and may be linked to any process. The abstract
Implementation resource element contains no attributes or elements besides those contained in the abstract
Resource element. An example demonstrating how to use implementation resources is provided in Section 3.8.2
Links to Implementation Resources.
Note that it is not recommended to specify the capabilities of a Device that is linked to a process to specify that
it should execute the given process.
3.7.1.4 Physical Resources (Consumable, Quantity, Handling)
Any resource whose Class is Consumable, Quantity, or Handling is considered a physical resource. They are
defined as follows:
• Consumable resources are resources that are
consumed during a process. Examples include Ink
and Media. They are the unmodified inputs in a
process chain.
• Quantity resources are resources that have been
created by a process from either a Consumable
resource or an earlier Quantity resource. For
example, printed sheets are cut and a pile of cut
blocks is created. Component resources are an
example of Quantity resources.
• A Handling resource is used during a process, but is
not destroyed by that process. ExposedMedia and
Tool are examples of such a resource, although it does describe various kinds of items such as film and
plates. A Handling resource may be created from a Consumable resource.
Table 3-14 Additional contents of the abstract physical Resource elements defines the additional attributes and
elements that may be defined for physical resources. The processes that consume physical resources—any kind of
physical resource—have the option of using these attributes and elements to determine in what way the resources
should be consumed. Table 3-14 Additional contents of the abstract physical Resource elements then describes the
contents of the Location subelement of physical resource elements.
Table 3-14 Additional contents of the abstract physical Resource elements
Name
Data Type
Description
AlternateBrand ?
string
Information, such as the manufacturer or type, about a resource compatible
to that specified by the Brand attribute, which is described below.
JDF’s handling of physical resources provides
a bridge between your JDF enabled systems
and inventory management, ordering and
replenishing systems. This opens the door to
just-in-time inventory management driven by
real-time scheduling and consumption data.
Automating Inventory
Management
Online Remove password from protected PDF file If we need a password from you, it will not be read or stored. To hlep protect your PDF document in C# project, XDoc.PDF provides some PDF security settings.
create secure pdf online; change security on pdf
86
Page 56
Page 56
Name
Data Type
Description
Amount ?
number
Actual amount of the resource that is available.
Note that the amount of consumption and production of a node is specified
in the corresponding resource links.
AmountProduced ? number
Total amount of the resource that has been produced by all nodes that
reference this resource as output. This corresponds to the sum of all
CumulativeAmount values of output resource links of leaf JDF Nodes with
Status=”Completed” that reference this resource.
[RP101]
AmountRequired ? number
Total amount of the resource that is referenced by all nodes that will
consume this resource. This corresponds to the sum of all Amount values
of input resource links that reference this resource.
BatchID ?
string
ID of a specific batch of the physical resource
Brand ?
string
Information, such as the manufacturer or type, about the resource being
used.
PipePause ?
New in JDF 1.2
number
Parameter for controlling the pausing of a process if the resource amount in
the pipe buffer passes the specified value. For details on using PipePause,
see Section 4.3.2.
PipeResume ?
New in JDF 1.2
number
Parameter for controlling the resumption of a process if the resource amount
in the pipe buffer passes the specified value. For details on using
PipeResume, see Section 4.3.2.
RemotePipeEndPa
use ?
New in JDF 1.2
number
Parameter for controlling the pausing of a process at the other end of the
pipe if the resource amount in the pipe buffer passes the specified value. For
details on using RemotePipeEndPause, see Section 4.3.2.
RemotePipeEndRe
sume ?
New in JDF 1.2
number
Parameter for controlling the resumption of a process at the other end of the
pipe if the resource amount in the pipe buffer passes the specified value. For
details on using RemotePipeEndResume, see Section 4.3.2.
ResourceWeight ?
New in JDF 1.1
double
Weight of a single component of the resource in grams.
Unit ?
NMTOKEN Unit of measurement for the values of Amount and AmountRequired.
Note that it is strongly discouraged to specify units other than those that are
defined in Units
Weight ?
Illegal in 1.1
double
Weight of a single component of the resource in grams. This parameter
collides with Media::Weight and is therefore illegal and has been replaced
with ResourceWeight in version 1.1 and beyond.
Contact ?
refelement
If this element is specified, it describes the owner of the resource.
IdentificationField
*
New in JDF 1.1
refelement
If this element is specified, a bar code or label is associated with this
physical resource.
Location ?
refelement
Description of details of the resource location.
Note, in order to describe multiple locations, resources may be partitioned
by the Location-key as described in Section 3.9.2 Description of
Partitionable Resources.
QualityResult *
refElement
Results of quality measurements which were performed during or after the
production of this resource.
C# HTML5 Viewer: Deployment on AzureCloudService RasterEdge.XDoc.PDF.HTML5Editor.dll. system.webServer> <validation validateIntegratedModeConfiguration="false"/> <security> <requestFiltering
add security to pdf document; decrypt pdf with password C# HTML5 Viewer: Deployment on ASP.NET MVC RasterEdge.XDoc.PDF.HTML5Editor.dll. system.webServer> <validation validateIntegratedModeConfiguration="false"/> <security> <requestFiltering
create pdf security; create secure pdf
56
Page 57
Page 57
Structure of Location Subelement
Table 3-15 Contents of the Location element
Name
Data Type
Description
LocationName ?
New in JDF 1.1
string
Name of the location, e.g., for example in MIS. This part key allows to
describe distributed resources.
LocID ?
string
Location identifier, e.g., within a warehouse system.
Address ?
refelement
Address of the storage facility. For more information, see Section 7.2.2.
3.7.1.5 PlaceHolder Resources
PlaceHolder resources, unlike physical resources, do not describe any logical or physical entity. Rather, they define
process linking and help to define process ordering when the exact nature of interchange resources is still unknown.
In essence, they serve as placeholders that stand in for defined resources. Using PlaceHolder resources, a
processing skeleton can be constructed that gives a basic shape to a job. The appropriate resources can be
substituted for PlaceHolder resources when they become known.
This kind of resource should only be used to link nodes of Type = ProcessGroup, since process leaf nodes have
well defined resources that should be used in preference. The only resource whose Class = PlaceHolder is called
PlaceHolderResource.
Like Parameter and Implementation resources, PlaceHolder resources contain no attributes besides those
contained in the abstract Resource element.
3.7.1.6 Selector Resources
Removed in JDF 1.1
Resources of class Selector have been removed in JDF version 1.1 and higher. Note that they are not only
deprecated but actually removed from the format including the schema and must not be supported by a JDF 1.1
conforming agent
3.7.2 Position of Resources within JDF Nodes
Resources may exist in any JDF node, but JDF nodes may only reference local or global resources. In other words,
JDF nodes may only reference resources in the two kinds of locations: in the node’s own ResourcePool element
or in JDF nodes that are hierarchically closer to the JDF root. An exception to this rule, however, occurs if two
independent jobs are merged for a process step and are to be separated afterwards, as is the case when two
independent jobs are printed on the same web-fed press. For further details on independent job merging, see Section
4.4.5 Case 5: Spawning and Merging of Independent Jobs.
It is good practice to put resources into the highest-level node that references the resource. For example, the
RenderingParams resource should be located in the Rendering node, unless it is used by multiple Rendering
processes, in which case it should be located in the ProcessGroup node that contains the Rendering process
nodes. Resources that link more than one node should be placed in the parent node of the siblings that are linked by
the resource.
A process that needs additional detailed process information specifying the creation of a resource must infer this
information by explicitly linking to the appropriate parameter resource.
3.7.3 Pipe Resources
A Pipe describes the resource dependency in which a process begins to consume a resource while it is being
produced by another process. For example, stacking components while they are being printed, or consuming a data
stream while it is being written by an upstream process. Note that defining a Pipe resource does not automatically
set up communication between processes. The Controllers/Agents that execute the process must still implement the
protocol that defines the Pipe.
Using dynamic pipe control, a downstream process may control the total quantity produced by an upstream
process, and/or the quantity buffered by an inter-process transport device (i.e. Conveyor belt.) Additional description
110
Page 58
Page 58
of pipes and process communication via pipes is provided in Section 4.3.2 Partial Processing of Nodes with
Partitioned Resources
JDF nodes themselves may not be partitioned, although the input and output resources may. If the input and output
ResourceLinks reference one or more individual partitions, the Node executes using only the referenced
Resources.
If multiple input resources are input to a process, the resource with the highest granularity defines the partitioning.
For instance, a ConventionalPrinting process may consume a non-partitioned ConventionalPrintingParams, and a set
of Ink and ExposedMedia(Plate) resources that are partitioned by Separation. The partition granularity will be
defined by the Ink and ExposedMedia(Plate) resources to be Separation. The Separation partition set is defined by
the superset of all defined partition key values. If the Separation key values of Ink were Black and Varnish, and the
the Separation key values of ExposedMedia(Plate) were Black, the resulting set is Black and Varnish.
The partition keys of both input and output restrict the process. If the partition keys are not identical, both must be
applied to restrict the node. If the partition keys are non-overlapping, e.g. in an Imposition node, where a RunList
based input partition is mapped to a sheet based output partition, the application must explicitily calculate the result.
The following examples illustrate the restriction algorithms:
Input Partition 1
Input Partition 2
Output Partition
Node Partition
Description
SheetName=
”S1”
-
-
SheetName=
”S1”
If only the input is
partitioned, the node
partition is defined by
the input.
SheetName=
”S1”
Separation=
”Cyan”
-
-
SheetName=
”S1”
Separation=
”Cyan”
If only the input is
partitioned, the node
partition is defined by
the input.
SheetName=
”S1”
Separation=
”Cyan”
Separation=
”Cyan” +
Separation=
”Black”
(PartUsage=
“Implicit”)
-
SheetName=
”S1”
Separation=
Cyan”
+
SheetName=
”S1”
Separation=
”Black”
The first input is
partitioned by
SheetName and
Separation which
defines the partition
key granularity. The
second input is
partitioned by
Separation only but
has an implied
SheetName and has a
larger but overlapping
set of separation
values. The separation
value set is therefore
defined by the second
key.
SheetName=
”S1”
-
SheetName=
”S1”
Separation=
”Cyan”
SheetName=
”S1”
Separation=
”Cyan”
The input and output
base partitions are
identical. The output
further restricts the
partition.
SheetName=
”S1”
-
SheetName=
”S2”
Separation=
”Cyan”
error
Input and output are
not overlapping. This
specifies the null set.
78
Page 59
Page 59
SheetName=
”S1”
Separation=
”Magenta”
Separation=
”Cyan” +
Separation=
”Black”
-
error
This is an error and
defines the null set.
The first input is
partitioned by
SheetName and
Separation which
defines the partition
key granularity. The
second input is
partitioned by
Separation only and
has a larger but non-
overlapping set of
separation values. The
separation value set is
therefore the null set.
SheetName=
”S1”
Separation=
”Cyan”
Separation=
”Cyan” +
Separation=
”Black”
(PartUsage=
“Explicit”)
-
error
The first input is
partitioned by
SheetName and
Separation which
defines the partition
key granularity. The
second input is
partitioned by
Separation only but has
no implied SheetName
and therefore has a
non-overlapping set of
partition keys. The
separation value set is
therefore defined by
the second key.
RunIndex=”0~7” -
SheetName=
”s2”
special
This specifies sheet s2,
with all PlacedObject
elements with an Ord
in the range of 0 to 7.
This special case is
important when
RunList entries occur
multiply on different
imposition sheets.
Overlapping Processing Using Pipes.
Resources may contain a string attribute called PipeID that declares the resource to be a pipe, and identifies it in
a dynamic-pipe messaging environment. A pipe that is also controlled by JMF pipe messages is called dynamic
pipe. For more information about dynamic pipes, see Section 4.3.2.2 Dynamic Pipes.
3.7.4 ResourceUpdate Elements
New in JDF 1.1
ResourceUpdate elements are an abstract element class that optionally contains any of the attributes and elements
valid for the Resource that they reside in. Required attributes and elements of resources are optional in the
respective ResourceUpdate. In addition, a ResourceUpdate defined within a Resource must contain a unique
61
Page 60
Page 60
UpdateID of type NMTOKEN. Only devices that process the resource as input can reference the UpdateID of a
ResourceUpdate. Such references to ResourceUpdate elements must update the current state of the device.
When a ResourceUpdate is referenced from a device, e.g., from a PPML TicketRef element, said device will
update ONLY those elements that are explicitly specified within the ResourceUpdate. No attributes are inherited
from the Resource that contains the ResourceUpdate.
ResourceUpdate elements are useful for process input resources only and must not be applied to product
intent resources.
Table 3-16 Contents of the abstract ResourceUpdate Element
Name
Data Type
Description
UpdateID
New in JDF 1.1
NMTOKEN
Unique ID that identifies the ResourceUpdate. Note that only
one Resource, Resource partition or ResourceUpdate with
a given value of UpdateID may occur per JDF document, even
though the scope of the ResourceUpdate is local to the
resource that it is defined in.
Example:
The following example shows ResourceUpdate elements in highlight.
<JDF
xmlns=”http://www.CIP4.org/JDFSchema_1_1”
ID="MyCombinedProcessNode" Status="Ready"
Type="Combined"
Types="Interpreting Rendering DigitalPrinting" Version="1.1">
<ResourceLinkPool>
<InterpretingParamsLink rRef=”PDFIParams” Usage=”Input” CombinedProcessIndex=”0”/>
<RenderingParamsLink rRef=”RParams” Usage=”Input” CombinedProcessIndex=”1”/>
<DigitalPrintingParamsLink rRef=”DPParams” Usage=”Input” CombinedProcessIndex=”2"/>
. . .
</ResourceLinkPool>
<ResourcePool>
<Media ID="White" … />
<InterpretingParams ID="PDFIParams" Class="Parameter" Status="Available" PrintQuality="High"
Polarity="Positive" EmitPDFTransfers="false" UpdateID="SetPrintQualityDefault"/>
<InterpretingParamsUpdate UpdateID=”SetNegativePolarity” Polarity=”Negative”/>
<InterpretingParamsUpdate UpdateID=”SetPositivePolarity” Polarity=”Positive”/>
<InterpretingParamsUpdate UpdateID=”SetPrintQualityDraft” PrintQuality=”Draft”/>
<InterpretingParamsUpdate UpdateID=”SetPrintQualityNormal” PrintQuality=”Normal”/>
<InterpretingParamsUpdate UpdateID=”SetPrintQualityHigh” PrintQuality=”High”/>
</PDFInterpretingParams>
<RenderingParams ID="RParams" Class="Parameter" Status="Available">
<AutomatedOverprintParams OverPrintBlackText="true" OverPrintBlackLineArt="true"/>
</RenderingParams>
<DigitalPrintingParams ID="DPParams" Class="Parameter" Status="Available" PrintingType="Sheet">
<MediaRef rRef="White" MediaLocation=”WhiteTray” UpdateID=”SetMediaDefault”/>
<DigitalPrintingParamsUpdate UpdateID=”SetMediaYellow”/>
<Media ID="Yellow" MediaLocation=”YellowTray” />
</DigitalPrintingParamsUpdate>
</DigitalPrintingParams>
. . .
</ResourcePool>
</JDF>
3.8 Resource Links
ResourceLinks describe what resources a node uses, and how it uses them. They also allow node dependencies to be
calculated. The following diagram summarizes resource linking within a JDF node. In this example there are two
resources, A and B, which are placed in the node’s ResourcePool. To reference the resources, the node has two
resource links, ALink and BLink, in the ResourceLinkPool. The resource links are named by appending “Link” to
63
Page 61
Page 61
the type of resource referenced. Resource B also contains a reference to resource A, called ARef. References to
resources from within resources are named by appending “Ref” to the type of resource referenced.
Figure 3.5 Resource Links and ResourceRefs
The previous section described resources used by the node in which it resides. This section describes how resources
may serve as links between nodes. As was described in Section 2.2 JDF Workflow , any resource that is the output
of one process will very likely serve as an input of a subsequent resource. Furthermore, some resources are shared
between ancestor nodes and their child nodes.
Each JDF node contains a ResourceLinkPool element that in turn contains all of the ResourceLink elements
that link the node to the resources it uses. They also define whether the resources are inputs or outputs. These
inputs and outputs provide conceptual links between the execution elements of JDF nodes. Outputs of one node
may in turn become inputs in another node, and a given node must not be executed before all required input
resources are available.
6
Figure 3.6 shows two processes that are linked by a resource. The resource represents the
output of Node 1, which in turn becomes an input for Node 2.
6
The availability of a resource that is consumed as a whole is given by the Resource attribute
Status = Available. In the case of pipe resources, the availability depends on the individual parameter defining the
dynamics of a pipe (for details see Section 4.3.2 Partial Processing of Nodes with Partitioned Resources
JDF nodes themselves may not be partitioned, although the input and output resources may. If the input and output
ResourceLinks reference one or more individual partitions, the Node executes using only the referenced
Resources.
If multiple input resources are input to a process, the resource with the highest granularity defines the partitioning.
For instance, a ConventionalPrinting process may consume a non-partitioned ConventionalPrintingParams, and a set
of Ink and ExposedMedia(Plate) resources that are partitioned by Separation. The partition granularity will be
defined by the Ink and ExposedMedia(Plate) resources to be Separation. The Separation partition set is defined by
the superset of all defined partition key values. If the Separation key values of Ink were Black and Varnish, and the
the Separation key values of ExposedMedia(Plate) were Black, the resulting set is Black and Varnish.
The partition keys of both input and output restrict the process. If the partition keys are not identical, both must be
applied to restrict the node. If the partition keys are non-overlapping, e.g. in an Imposition node, where a RunList
based input partition is mapped to a sheet based output partition, the application must explicitily calculate the result.
The following examples illustrate the restriction algorithms:
Input Partition 1
Input Partition 2
Output Partition
Node Partition
Description
SheetName=
”S1”
-
-
SheetName=
”S1”
If only the input is
partitioned, the node
partition is defined by
the input.
SheetName=
”S1”
Separation=
”Cyan”
-
-
SheetName=
”S1”
Separation=
”Cyan”
If only the input is
partitioned, the node
partition is defined by
the input.
92
Page 62
Page 62
SheetName=
”S1”
Separation=
”Cyan”
Separation=
”Cyan” +
Separation=
”Black”
(PartUsage=
“Implicit”)
-
SheetName=
”S1”
Separation=
Cyan”
+
SheetName=
”S1”
Separation=
”Black”
The first input is
partitioned by
SheetName and
Separation which
defines the partition
key granularity. The
second input is
partitioned by
Separation only but
has an implied
SheetName and has a
larger but overlapping
set of separation
values. The separation
value set is therefore
defined by the second
key.
SheetName=
”S1”
-
SheetName=
”S1”
Separation=
”Cyan”
SheetName=
”S1”
Separation=
”Cyan”
The input and output
base partitions are
identical. The output
further restricts the
partition.
SheetName=
”S1”
-
SheetName=
”S2”
Separation=
”Cyan”
error
Input and output are
not overlapping. This
specifies the null set.
SheetName=
”S1”
Separation=
”Magenta”
Separation=
”Cyan” +
Separation=
”Black”
-
error
This is an error and
defines the null set.
The first input is
partitioned by
SheetName and
Separation which
defines the partition
key granularity. The
second input is
partitioned by
Separation only and
has a larger but non-
overlapping set of
separation values. The
separation value set is
therefore the null set.
Documents you may be interested
Documents you may be interested
