JDF 1.6 Errata
This page provides a page by page summary of all errata that unfortunately made it into JDF 1.6.
A copy of the JDF 1.6 specification showing the location of these errata as pdf comment annotations can be found here JDF Specification 1.6-Final-Errata.pdf.
Note: To properly view the annotations, this pdf should be viewed in Acrobat Reader rather than a web browser.
Table of Contents
- 1 Chapter 1
- 2 Chapter 2
- 3 Chapter 3
- 4 Chapter 5
- 5 Chapter 6
- 6 Chapter 7
- 7 Chapter 8
- 7.1 8.12.1 BundleItem
- 7.2 8.16 CasingInParams
- 7.3 8.22 ColorCorrectionParams
- 7.4 8.44 Device
- 7.5 8.44.3 Module
- 7.6 8.51 ElementColorParams
- 7.7 8.65 GluingParams
- 7.8 8.69 IdentificationField
- 7.9 8.74
- 7.10 8.80.2 PDFInterpretingParams
- 7.11 8.84 Layout
- 7.12 8.84 Layout
- 7.13 8.91.1 TabDimensions
- 7.14 8.130 RunList
- 7.15 8.130 RunList
- 7.16 8.152.2 StripCellParams
- 8 Chapter 9
- 9 Chapter 10 Device Capabilities
- 10 Appendix
- 11 Appendix A Data Types and Values
- 12 A.4.22.1 Status Details for Generic Devices
- 13 Appendix F Media Size
- 14 Appendix I Pagination Catalog
- 15 Appendix N Release Notes
- 15.1 N Release Notes
Only issues that affect interoperability will be updated here. Minor typos and similar issues will be tracked in JIRA for the next version but will not be tracked here.
You have found a new issue?
If you have found an Error in the JDF Specification, please don't hesitate to create a new Bug-Ticket in the JDF Project here: https://jira.cip4.org/projects/JDF.
How to use this errata.
The order of the errata duplicates the order of the JDF 1.6 specification.
Chapter headings are included for convenience only (to allow for an entry in the Table of Contents on this page).
Each errata item is bounded by horizontal rule lines.
If an errata affects multiple pages then it will be ordered by the first page it affects and all the revisions for the errata will be kept together in a single section.
Each errata item is comprised of left and right columns where
The left column contains the details, explanation, location and JIRA reference.
The right column contains the revised content.
Each errata will have a link to the JIRA entry that describes the issue in detail.
JIRA status value
The JIRA link is 'live'! It contains the current status of the issue.
If this entry has a value of IMPLEMENTED then it is complete and will be incorporated into the next version of the specification.
All other values, such as TSC VERIFY or SPECIFICATION mean that the entry is still in the process of being constructed and MAY change before being finally implemented.
Revised content format
The revised content is NOT formatted in the same manner as the specification due to editing restrictions of this wiki.
Revised content instructions
Text written in Bold Blue Underlined in the revised content column is for information and clarification only - it does NOT form part of the new/revised content.
Location page numbering
Page numbers refer to the printed page number in JDF 1.6. Add 32 to the printed page number in order to navigate to an indexed page, e.g. in Acrobat.
Chapter 1
Table 1.6: JDF Data Types (Sheet 3 of 3)
Page 15
The sRGBColor data type was incorrectly left out of the JDF Data Types table. It has now been replaced.
The new line in the table reads
DATA TYPE | DESCRIPTION |
|---|---|
sRGBColor | Represents an sRGB color specification. |
Chapter 2
Figure 2-3: Example of a hierarchical tree structure of JDF nodes
Page 23
An incorrect figure was used and has been replaced with the correct figure.
The new figure:
Chapter 3
Table 3.22: PartIDKey Attribute Values
Page 82
One of the PartIDKey values was misspelled as 'PrintConditon', this has been corrected to 'PrintCondition'.
The PartIDKey Attribute Values table simply lists acceptable enumerations as used by a number of attributes.
The modified entry in the table is not shown here as there is no related context other than the spelling change.
Table 3.23 Part Element (Sheet 5 of 7)
Page 87
The JDF 1.5 Errata added the value "None" to the Part @Separation attribute to allow for separations to be skipped. This value was incorrectly removed in JDF 1.6.
The value "None" was changed to "none" in JDF 1.6 so that it matches the predefined separation "none" in PDF.
Note: As part of this edit the order of the values have also been sorted.
The @Separation row of the Part element reads
NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
Separation ? Modified in JDF 1.6 | string | Identifies the separation name. Values include: Note: Other values include any separation name defined in the @Name attribute of a Color element in the ColorPool. |
Chapter 5
Table 5.35 FlushResources Command
5.21.2 FlushResources Query
Table 5.36 FlushResources Query
Page 168
The ResponseTypeObj for both the FlushResources Command and Query have a place holder element. Both should reference an element that was incorrectly omitted. This omitted element (section and table) has been restored and references to it from the Command and Query table restored as well.
The amended line in the FlushResources Command table reads
OBJECT TYPE | ELEMENT NAME | DESCRIPTION |
|---|---|---|
ResponseTypeObj | FlushedResources ? | This element is a placeholder for future use. |
The amended line in the FlushResources Query table reads
OBJECT TYPE | ELEMENT NAME | DESCRIPTION |
|---|---|---|
ResponseTypeObj | FlushedResources ? | This element is a placeholder for future use. |
Shown below is the restored section for the placeholder FlushedResources element, referred to in the above table rows
5.21.x.x FlushedResources
Table 5.xx FlushedResources Element
NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
Table 5.53: SubscriptionFilter Element
Page 175
The data type of the @DeviceID attribute was incorrectly changed to NMTOKEN. It has been reset to string.
The amended line in the table reads
NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
DeviceID ? | string | Only subscriptions from devices or controllers with a matching @DeviceID attribute are queried. |
Table 5.82: ResourceQuParams Element (Sheet 2 of 2)
Page 190
The cardinality of the @Scope attribute was set to mandatory and should be optional.
The amended line in the table reads
NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
Scope ? New in JDF 1.4 | enumeration | Specifies whether the Response or Signal SHALL return a complete list of all known resources, or the currently loaded resources or the resources related to a specific job. |
Table 5.103: DeviceInfo Element (Sheet 1 of 2)
Page 206
The @DeviceOperationMode attribute from the DeviceInfo resource was incorrectly removed. The attribute has been reinstated.
The new line in the table reads
NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
DeviceOperationMode ? New in JDF 1.2 | enumeration | @DeviceOperationMode shows the operation mode that the Device is in. It is used to show if the production of a Device is aimed at producing good products or not. The latter case applies when a Device is used to produce a job for testing, calibration, etc., without the intention to produce good output. |
Table 5.107: StopPersChParams Element
Page 211
The data type of the @DeviceID attribute was incorrectly changed to 'NMTOKEN', it has been restored to be 'string'.
The amended line in the table reads
NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
DeviceID ? | string | Only messages from devices or controllers with a matching @DeviceID attribute are suppressed. |
Table 5.111 QueueSubmissionParams Element (Sheet 2 of 2)
Page 214
QueueSubmissionParams/@Priority had a default value of "1" and yet it states that :
"Exactly one of NextQueueEntryID, @PrevQueueEntryID or
@Priority SHALL be specified."
Since having a default is equivalent to always specifying the value either manually or 'automatically' with the default value, this effectively outlaws NextQueueEntryID and PrevQueueEntryID as Priority is always specified.
The default has been removed and a modification note added.
The Priority attribute entry in the QueueSubmissionParams Element table reads
NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
Priority ? Modified in JDF 1.6 | integer | Number from 0 to 100, where "0" is the lowest priority and "100" is the maximum priority. At most one of @NextQueueEntryID, @PrevQueueEntryID or @Priority SHALL be specified. Note that QueueSubmissionParams/@Priority is not the same as NodeInfo/@Priority. QueueSubmissionParams/@Priority specifies the priority in the context of the device queue whereas NodeInfo/@Priority specifies the priority of the task in general. QueueSubmissionParams/@Priority MAY be modified due to additional scheduling information (e.g., NodeInfo/@FirstStart). The priority from QueueSubmissionParams/@Priority and QueueEntryPriParams/@Priority takes precedence over NodeInfo/@JobPriority. Modification Note: Prior to JDF 1.6, @Priority had a default value of "1". This default is erroneous and has been removed because it conflicts with the default of NodeInfo/@JobPriority="50" and because @NextQueueEntryID and @PrevQueueEntryID could never be specified without violating the restriction that @Priority is not specified. |
Chapter 6
Table 6.22: Bending – Input Resources (Sheet 2 of 2)
Page227
The cardinality of the input resource "ExposedMedia" was set to mandatory, this has been corrected to be optional.
The amended line in the table reads
NAME | DESCRIPTION |
|---|---|
ExposedMedia ? | The ExposedMedia resource to be bent/punched. |
Table 6.42: ImageReplacement – Input Resources
Page 233
The cardinality of the 'ImageReplacementParams' and 'RunList' input resources were incorrectly set to optional; these have been amended to be mandatory.
The amended line in the table reads
NAME | DESCRIPTION |
|---|---|
ImageReplacementParams | Describes the controls selected for the manipulation of images. |
RunList | List of page contents on which to perform the selected operation. |
Table 6.44: ImageSetting – Input Resources
Page 234
The cardinality of the 'RunList' input resource was incorrectly set to optional; it has been amended to be mandatory.
The amended lines in the table reads
NAME | DESCRIPTION |
|---|---|
RunList | Identifies the set of bitmaps to image. MAY contain bytemaps or images. |
Table 6.86: Stripping – Input Resources
Page 255
An input resource 'BinderySignature' was incorrectly added and has now been removed.
As the row has been removed, there is no revised content
Table 6.154: PrintRolling – input resources
Table 6.155: PrintRolling – output resources
Page 276
Both the input and output 'Component' resources were incorrectly set to optional; they have been amended to be mandatory.
The amended line in the input resources table reads
NAME | DESCRIPTION |
|---|---|
Component | Component to be rolled. |
The amended line in the output resources table reads
NAME | DESCRIPTION |
|---|---|
Component | The print roll. |
Chapter 7
Page 330
The introduction paragraph to this Intent incorrectly referred to @ProductionResources. This should have been ProductionIntent/Resource.
The revised introduction reads
This resource specifies the manufacturing intent and considerations for a JDF job using information that identifies the desired result or specified manufacturing path. If specific details of print quality, such as color quality, need to be specified, ProductionIntent/Resource SHOULD reference a QualityControlParams resource.
Chapter 8
Table 8.20: BundleItem Element
Page 358
Several attributes incorrectly referred to 'Bundle'; this has been corrected so that they refer to 'BundleItem'. In addition the 'Bundle' element has been corrected to be a 'Component' element.
The amended lines in the table read
NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
Orientation ? | enumeration | Named orientation of the BundleItem respective to the Bundle coordinate system. |
Transformation ? | matrix | Orientation of the BundleItem respective to the Bundle coordinate system. |
Component | refelement | Reference to a Component that is part of this BundleItem. |
Table 8.26 CasingInParams Resource
Page 364
As part of the migration to XJDF the attributes @CoverBoardWidth and @SpineBoardWidth were renamed to @CoverWidth and @SpineWidth. This change should not have been made to the JDF version and has been reversed.
The amended lines in the table read
NAME | DATA TYPE | DESCRIPTION |
|---|---|---|
CoverBoardWidth ? New in JDF 1.5 | double | Width of the cover board. |