This is an annotated simple annotated ConventionalPrinting job to illustrate the differences and similarities of JDF and XJDF.
The XJDF was created automatically using the CIP4 JDF editor, which in turn uses utility classes which are available in the CIP4 open source Java Library - see: JDFLibJ.
- Rainer Prosi add Product definition to this example
The root tag, version information and schema are obviously different.
Whereas JDF allows for multiple JDF nodes, XJDF requires exactly one.
Audits have remained mostly unchanged.
ResourceLinkPool and ResourcePool have been removed. The ResourceSet elements reside directly in the only XJDF.
ColorantControlLink and ColorantControl have been merged into one ResourceSet.
Separations are referred to by attribute lists rather than SepaationSpec elements.
ColorPool is a "standard" partitioned Color ResourceSet rather than a specific animal.
The name is a token that SHOULD be matched to an ActualColorName that is a string may contain blanks and other special characters.
This allows separations to be referenced as NMTOKENS lists rather than requiring expilcit SeparationSpec elements.
ConventionalPrintingParams + Link
In JDF, a resource is only applicable to the JDF that contains a matching ResourceLink. In XJDF the two concepts have been combined into a "Set" entry that is always applicable. Thus you need no longer search for the matching resource to a ResourceLink.
Generic attributes such as Usage are defined in explicit elements which are the parent elements of the specific resources such as ConventionalPrintingParams.
Thus each table in the specification is self contained and does not require an implementor to follow the tree of inheritence in the specification.
Partitioned NodeInfo ParameterSet
Partitioning always is written as a linear list with Part elements rather than a hierarchical structure.
The SignatureName partition key has been removed.
References, if used at all, are simple ID-IDRef pairs rather than
that may even contain additional partitioning data, requiring specific lookup functions.
Paper Media excluding consumption reporting
Paper Media including consumption reporting
JDF allowes Amount definitions both in the resource and the ResourceLink. XJDF has only one container object, in our case it is the <Resource> that contains an AmountPool.
All planned amounts are defined in:
All actual amounts are defined in:
Waste has been made a specific attribute, thus removing the reqirement for Part/@Condition.
End of File
End of File