This page provides a page by page summary of all errata that unfortunately made it into JDF 1.8

.

A copy of the JDF 1.8 specification showing the location of these errata as pdf comment annotations can be found here

 

:

View file
name JDF Specification 1.

6-Final-

8 Errata.pdf

.

Note: To properly view the annotations, this pdf should be downloaded to viewed in Acrobat Reader, rather than a web browser.

                                                                                Image Removed

Panel
title Table of contents
Table of Contents maxLevel 2

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

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

Priority ?

Modified in JDF 1.6

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.

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

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

Describes the controls selected for the manipulation of images.

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

Table 6.86: Stripping – Input Resources

Page 255

An input resource 'BinderySignature' was incorrectly added and has now been removed.

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

The amended line in the output resources table reads

Page 330

The introduction paragraph to this Intent incorrectly referred to @ProductionResources. This should have been ProductionIntent/Resource.

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

Named orientation of the BundleItem respective to the Bundle coordinate system.
For details, see 4Table 2.4 Matrices and Orientation values for describing the orientation of a Component.
At most one of @Orientation or @Transformation shall be specified.
Allowed value is from: Orientation.

Orientation of the BundleItem respective to the Bundle coordinate system.
At most one of @Orientation or @Transformation shall be specified.

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

CoverBoardWidth ?

New in JDF 1.5

Width of the cover board.

Note: Height and total case dimensions are specified in the Component(BookCase) of the CasingIn process.

For details of @CoverBoardWidth, see also Figure 8-10: CaseMakingParams (in this figure @CoverBoardWidth is referred to as @CoverWidth).

SpineBoardWidth ?

New in JDF 1.5

Width of the spine board.

Note: Height and total case dimensions are specified in the Component(BookCase) of the CasingIn process.

For details of @SpineBoardWidth, see also Figure 8-10: CaseMakingParams (in this figure @SpineBoardWidth is referred to as @SpineWidth).

Table 8.41: ColorCorrectionParams Resource

Page 379

The first FileSpec refelement in the table is missing the resource usage identifier that is intended to show that this FileSpec is for the final target device only.

The '(FinalTargetDevice)' specification has been added.

The amended line in the table reads

FileSpec
(FinalTargetDevice) ?

Table 8.69: Device Resource (Sheet 2 of 3)

Page 407

The @JDFVersions attribute had an invalid data type and was incorrectly specifed and formatted. This has been corrected and a link to the table of versions enumeration added.

The modified line in the table now reads

JDFVersions ?

New in JDF 1.1

Whitespace separated list of supported JDF versions that this device supports (e.g., "1.0 1.1" specifies that both the 1.0 and 1.1 versions are supported).

Allowed values are from: JDFJMFVersion.

Table 8.72: Module Element (Sheet 1 of 2)

Page 409

The data type of the @ModuleID attribute was incorrectly changed to 'NMTOKEN', it has been restored to be 'string'.

The modified line in the table reads

Identifier of the module. This is a unique identifier within the workflow. @ModuleID SHALL be the same over time for a specific Module instance (i.e., SHALL survive reboots). At least one of @ModuleID or @ModuleIndex SHALL be specified. If multiple logical devices share a physical Module, @ModuleID SHALL be identical. @ModuleID SHOULD be used to specify machines that comprise a Device.

Table 8.81: ElementColorParams Resource

Page 421

The data type of the 'ColorantAlias' child of the resource was incorrectly set to be 'element'; it has been corrected to be 'refelement'.

The modified line in the table reads

Each resource instance specifies a replacement colorant name string to be used instead of one or more named colorant strings found in the Layout resource referenced element.
Multiple ColorantAlias elements with identical values of ColorantAlias/@ReplacementColorantName SHALL NOT be specified in the same ElementColorParams resource context.

Table 8.102: GluingParams Resource

Page 438

The 'GlueLine' child element of the GluingParams resource has been corrected to be a 'Glue' child element and the description updated.

The modified line in the table reads

Table 8.107: IdentificationField Resource (Sheet 1 of 2)

Page 442

An attribute was incorrectly spelt as @EncodingDetals; this has been amended to @EncodingDetails.

The modified line in the table reads

Details about the encoding type. An example is the bar code scheme.
Values include those from: Table 8.108 EncodingDetails Attribute Values.

Table 8.126: ImageSetterParams Resource (Sheet 3 of 3)

Page 456

The Media refelement was omitted and has been reinstated.

The new line in the table reads

Media ?
New in JDF 1.1

Describes the media to be used. Different Media MAY be specified in different partition leaves to enable content driven Media selection.

Table 8.135: PDFInterpretingParams Element (Sheet 2 of 2)

Page 462

The data type of @OCGProcess was incorrectly left as 'enumeration'; it has been amended to 'NMTOKEN'. This is necessary to allow for additional values from the referenced ISO document.

The modified line in the table reads

OCGProcess ?
New in JDF 1.3
Modified in JDF 1.6

If @OCGDefault="FromPDF", then the value of @OCGProcess sets the purpose for which the Interpreting process is being performed. This, in turn, sets which value from a relevant optional content usage dictionary shall be used to determine whether each OCG is included in the InterpretedPDLData.

Allowed values are:
Export – PDF ExportState in the export subdictionary.
Print – PDF PrintState in the print subdictionary.
View – PDF ViewState in the view subdictionary.

Additional values are defined in 4[ISO19593-1:2016] or MAY be site specific.
Modification Note: The data type was changed from enumeration to NMTOKEN in JDF 1.6 to allow support for [ISO19593-1:2016].

Table 8.140: Layout Resource (Sheet 2 of 4)

Page 466

The attributes 'NonPrintableMarginBottom', 'NonPrintableMarginLeft', 'NonPrintableMarginRight' and 'NonPrintableMarginTop' were inadvertently added to the Layout resource and have been removed.

Table 8.140: Layout Resource (Sheet 4 of 4)

Page 468

A constraint regarding the usage of SheetCondition with Layout was omitted. The description has been updated to restore the constraint.

The amended line in the table reads

Specifies the conditions under which the optional sheet defined by this Layout SHALL be produced. SheetCondition SHALL only be present when Layout/@Automated="true", and SHALL be contained within a Layout branch partitioned by @SheetName.

Table 8.174: TabDimensions Element

Page 512

The data type of @TabSetCollationOrder was incorrectly specified as an enumeration. This has been corrected to NMTOKEN.

The amended line in the table reads

Collation order of media provided in sets. Applicable to sets of pre-cut tabs. See Figure 8-38: Diagram of a single bank of tabs. Although @TabSetCollationOrder is of type NMTOKEN, values other than those in Table 8.175 TabSetCollationOrder Attribute Values are NOT RECOMMENDED.

Values include those from: Table 8.175 TabSetCollationOrder Attribute Values.

Table 8.240 RunList Resource (Sheet 2 of 5)

Page 561

The data type of the @Docs attribute was incorrectly specified as NameRangeList. This has been corrected with the value of 'IntegerRangeList'.

The amended line in the table reads

Zero-based list of document indices in a multi-document file specified by the LayoutElement resource If not present, all documents SHALL be selected.

Table 8.240: RunList Resource (Sheet 5 of 5)

Page 564

The data type of 'InsertSheet' was incorrectly set to 'element'; this has now reverted to 'refelement'.

The amended line in the table reads

Describes how sheets and surfaces are to be completed and OPTIONAL media which MAY be inserted at the beginning or end of this RunList resource.

Figure 8-56: Definition of margins in StripCellParams

Page 592

The labels in the JDF figure reflected the values for XJDF. This errata updates the labels to reflect JDF:

TrimSpine has been updated to Spine and missing labels have been added.

The new figure:

Image Removed

Introductory paragraph and throughout chapter

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: false

Resource candidate: true

Resource candidate: false

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: false

Resource candidate: false

Resource candidate: true

Resource candidate: false

Resource candidate: false

Resource candidate: false

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: false

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: false

Resource candidate: false

Resource candidate: false

Resource candidate: true

Resource candidate: true

Resource candidate: false

Resource candidate: false

Resource candidate: true

Resource candidate: true

Resource candidate: true

Resource candidate: false

Resource candidate: true

Resource candidate: false

Table 9.13: ChannelTypeDetails Attribute – predefined values for certain ChannelType values

Page 620

Some values for the ChannelTypeDetails attribute that had been deprecated in JDF 1.5 were incorrectly omitted and have now been restored.

The new composite row in the table reads

CHANNELTYPEDETAILS

VALUE

ISDN  

LandLine

Deprecated in JDF 1.5 

Land line telephone number.

Deprecation note: The combination of @ChannelType="Phone" and @ChannelTypeDetails="LandLine" has been replaced with @ChannelType="Phone" without @ChannelTypeDetails.

Mobile

Deprecated in JDF 1.5

Mobile/Cellular telephone number.

Deprecation note: The combination of @ChannelType="Phone" and @ChannelTypeDetails="Mobile" has been replaced with @ChannelType="Mobile".

Secure  

Secure phone line.

Table 10.8: Loc Element

Page 659

The 'Value' entry in the table was incorrectly omitted and has now been restored.

The new row in the table reads

Table 10.10: Abstract State Element

Page 663

The @Required attribute was incorrectly deprecated. This has been corrected.

The amended line in Table 10.10 reads

Required ?

New in JDF 1.2

If "true", then the attribute or span element described by this State element is REQUIRED to be present in a JDF or JMF (as appropriate) submitted to the device.

Note This does not override the cardinality specified by the JDF specification where the specification requires the element to be specified.

Example A.19: IntegerRange

Page 729

The examples for @Pages were incorrectly formatted. These have now been corrected.

The new examples are

<RunList ID="RL1" class="Parameter" Status="Available" Pages="-3 ~ -5"/>

<RunList ID="RL2" class="Parameter" Status="Available" Pages="-1 ~ -5"/>

Table A.9: BindingType Enumeration Values

Page 740

Binding type values have been migrated from an inline table in the BindingIntent Resource of version JDF 1.5 to this appendix. During this process an inadvertent addition of 'ThreadSewing' was added to the table.

The entire 'ThreadSewing' row has been removed.

A.3.xx Face

Page 745

The table for 'Face' enumeration was not included and has now been added. (Note the use of 'xx' for auto-numbering placeholders).

The new entry in the enumeration section of the appendix is as follows

A.3.xx Face

Face specifies the location on a three dimensional object, e.g. Component.

Table A.xx: Face Enumeration Values

Back side of a sheet or product.

Front side of a sheet or product.

Left side of a product, e.g. the spine of a left bound book.

Right side of a product, e.g. the spine of a right bound book.

Top of a product.

Table A.58: SurplusHandling Enumeration Values

Page 759

The fifth row of the table incorrectly defined the enumeration value to be 'ReturnWithProof'; this has been corrected to be 'ReturnWithProduct'.

The row in the table reads

Table A.65: Contact Types

Page 763

The value 'Pickup' was incorrectly omitted and has now been restored.

The new row in the table reads

Table A.98: Status Details Mapping for Generic Devices

Pages 787-789

Several values in the DEVICESTATUS column were incorrectly set (to those translated to XJDF 2.0). These values have been corrected to align with JDF 1.5.

The affected rows in the table read (note: unaffected rows have been omitted for clarity)

Breakdown of the device, repair needed.

The Device is calibrating, either manually or automatically.

ControlDeferred

Modified in JDF 1.4

The Machine is not accessible by the Device.

Note:JDF/@Status is unknown if the device is not accessible.

Modification note: starting with JDF 1.4, the @DeviceStatus value changed from "Stopped" to

"Unknown".

Good

counter is on, waste copy counter is off.

Idling

consumed. Good and waste copy counters are off.

IterationPaused
New in JDF 1.4

At least one iteration cycle has completed but additional iteration cycles MAY still occur.

JobCanceledByOperator
New in JDF 1.3

The job was canceled by the device operator using AbortQueueEntry, or means local to the device.

New in JDF 1.3

The job was canceled by the owner of the job using AbortQueueEntry

JobCompletedSuccessfully
New in JDF 1.3

The job completed successfully.

JobCompletedWithErrors
New in JDF 1.3

The job completed with errors (and possibly warnings too).

JobCompletedWithWarnings
New in JDF 1.3

JobHeld
New in JDF 1.3

The device held the job that had been waiting (by performing a HoldQueueEntry request on a waiting QueueEntry).

JobHeldOnCreate
New in JDF 1.3

The job was submitted to the queue with the Queue/@Status = "Held", the job's QueueSubmissionParams/@Held = "true", or JDF/@Activation = "Held".

JobIncoming
New in JDF 1.3

The device is retrieving/accepting document data.

JobResuming
New in JDF 1.3

The device is in the process of moving the job from a suspended condition to a candidate for processing (ResumeQueueEntry).

JobScheduling
New in JDF 1.3

The device is scheduling the job for processing.

JobStreaming
New in JDF 1.3

Same as "JobIncoming" with the specialization that the device is processing the document data as it is being received (that is, the job data is not being spooled, but rather is being processed in chunks by the output device and is being imaged during reception).

JobSuspended
New in JDF 1.3

The device suspended the job that had been processing (e.g., by performing a SuspendQueueEntry request on a running QueueEntry) and other jobs can be processed by the device.

JobSuspending
New in JDF 1.3

InProgress

The device is in the process of moving the job from a processing condition to a suspended condition where other jobs can be processed.

MovingToPaused
New in JDF 1.3

InProgress

taking an appreciable time to stop.

ProcessingToStopPoint
New in JDF 1.3

InProgress

The requester has issued an AbortQueueEntry request or the device has aborted the job, but is still performing some actions on the job until a specified stop point occurs or job termination/cleanup is completed.

Machine stopped (can be switched off), restart requires a run up.

WarmingUp

mode wake-up.

Waste

InProgress

Production of products in progress, good copy counter is off, waste copy counter is on.

Table A.98: Status Details Mapping for Generic Devices

Page 789

The value in the DEVICESTATUS column was incorrectly set to 'Offline' and has been corrrected to 'Stopped'.

The affected rows in the table now reads

StandBy

New in JDF 1.6

The device has been switched into power saving mode and cannot process jobs without prior intervention such as Command[@Type="WakeUp"].

Table A.99: Status Details Mapping for Printing Devices

Pages 789-799

Several values in the DEVICESTATUS column were incorrectly set (to those translated to XJDF 2.0). These values have been corrected to align with JDF 1.5.

The affected rows in the table read (note: unaffected rows have been omitted for clarity)

BlanketWash

CleaningInkFountain

CylinderWash

DampeningRollerWash

 "WashUp".

FormChange

imaging printing, imaging or re-imaging of plates.

InkRollerWash

"WashUp".

Processing
New in JDF 1.4

Other productive processing (RIP, etc.) is taking place but no final output is being produced. All input data has arrived (not "JobStreaming"/"InProgress" nor "JobIncoming"/"Waiting").

WaitingForMarker
New in JDF 1.4

Suspended or Ready

The @Status is "Suspended" if the printing device models any module prior to the marker module, otherwise, the @Status is "Ready".
Processing is automatically suspended by the worker because it is waiting behind other jobs for the marker module and the worker will resume processing when a marker module becomes available.

WaitingForReferencedDataCollector
New in JDF 1.4

The @Status is "Suspended" if the printing device models any module prior to the referenced data collector module, otherwise, the @Status is "Ready".
Processing is automatically suspended by the worker because it is waiting behind other jobs for the referenced data collector module and the worker will resume processing when a referenced data collector module becomes available.

WaitingForRIP
New in JDF 1.4

The @Status is "Suspended" if the printing device models any module prior to the RIP module, otherwise, the @Status is "Ready".
Processing is automatically suspended by the worker because it is waiting behind other jobs for a RIP module (process slot) and the worker will resume processing when a RIP module becomes available.

WashUp

Machine is washed before, during or after production."WashUp" has specialized subcategories: "BlanketWash", "CleaningInkFountain", "CylinderWash", "DampeningRollerWash", "InkRollerWash", or "PlateWash". "WashUp" is the default that is assumed if @StatusDetails is not specified.

Page 806

The Japanese and International B paper sizes were both mapped to the Japanese B paper sizes.

This section has been amended to contain more clarification text. The original single table has been replaced by two tables, one for each of the International and Japanese B paper sizes each with new NMTOKEN values; the original table has been deprecated.

To ensure backward compatibility a note has been added to clarify the use of the deprecated values to allow systems that receive them to continue to behave in a system defined 'localized' manner.

The section 'F4 International B Paper Sizes' reads

F.4 International and Japanese B Paper Sizes

These sizes are defined by ISO standards, including [ISO216:2007] and by JIS standards [JIS P0138].

Note: Equivalent International and Japanese B paper sizes, i.e. ISOB0/JISB0, ISOB1/JISB1 etc, differ in area and size. To illustrate this point the ISOB0 sheet has an area of √2m² whereas the JISB0 sheet has an area of 1.5m². The aspect ratio of both is identical.

Implementations SHOULD NOT calculate values and SHOULD use the values from the respective tables below.

F.4.1 International B Paper Sizes

New in JDF 1.6

Note: Prior to JDF 1.6 values for ISO and JIS B paper sizes were incorrectly conflated.  See B Paper Sizes.

Table F.4: International B Paper Sizes

ISOB0

ISOB1

ISOB2

ISOB3

ISOB4

ISOB5

ISOB6

ISOB7

ISOB8

ISOB9

F.4.2 Japanese B Paper Sizes

New in JDF 1.6

Note: Prior to JDF 1.6 values for ISO and JIS B paper sizes were incorrectly conflated.  See B Paper Sizes.

Table F.5: Japanese B Paper Sizes

JISB0

JISB1

JISB2 

JISB3

JISB4

JISB5

JISB6

JISB7

JISB8

JISB9

F.4.2 B Paper Sizes

Deprecated in JDF 1.6

Prior to JDF 1.6 only values B0-B10 were available. These did not allow for the difference between the ISO and JIS values. New media size tokens have been introduced to clearly distinguish between these two sets of values as shown in International (ISO) B Paper Sizes and Japanese (JIS) B Paper Sizes above.

Note: The actual size for these values matched the JIS values.

Deprecation Note: Implementing systems should replace a deprecated value of B0-B10 with the appropriate localized value.

Table F.5: B Paper Sizes

B0

B1

B2 

B3

B4

B5

B6

B7

B8

B9

Table I.1: Scheme Names for Binding Orientations

Page 821

Underlining to show the default values in the column Header and Footer were missed. These have been added.

The header now reads

SCHEME NAME (FOR @BindingOrientation SETTING SHOWN IN HEADER)

(FOR SINGLE-ROW SIGNATURES: USE COLUMN FOOTERS

ROTATE0

FLIP0

ROTATE90

FLIP90

ROTATE180

FLIP180

ROTATE270

FLIP270

The footer now reads

FLIP0

ROTATE0

FLIP270

ROTATE270

FLIP180

ROTATE180

FLIP90

ROTATE90

Table I.4: Horizontal Binding Edges

Page 823

The illustration for the Rotate90 Scheme Name was incorrect for pages 7&8. This has now been corrected.

The updated illustration is now

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

The amended line in the FlushResources Query table reads

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

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

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

Scope ?

New in JDF 1.4

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.
Allowed value is from: Scope.

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

DeviceOperationMode ?

New in JDF 1.2