Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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  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.

                                                                                Logo_JDF_rgb_preview.jpg

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.

Info
titleYou 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.

  1. The order of the errata duplicates the order of the JDF 1.6 specification.
  2. Chapter headings are included for convenience only (to allow for an entry in the Table of Contents on this page).
  3. Each errata item is bounded by horizontal rule lines.
  4. 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.
  5. Each errata item is comprised of left and right columns where
    1. The left column contains the details, explanation, location and JIRA reference.
    2. The right column contains the revised content.
  6. Each errata will have a link to the JIRA entry that describes the issue in detail.


Warning
titleJIRA 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.


Info
titleRevised content format

The revised content is NOT formatted in the same manner as the specification due to editing restrictions of this wiki.


Info
titleRevised 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.


Info
titleLocation 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.




Panel
titleTable of contents

Table of Contents
maxLevel2




Chapter 3



3.8.4.7.2 Location

Table 3.25 Location Element

Page 67

The data type of the Address element was incorrectly specified as 'element' - this has been corrected to 'refelement'.

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdca24a432-b2d2-34e1-b9dc-79179cf2f6d4
keyJDF-1121

The new line in the table reads

NAMEDATA TYPEDESCRIPTION
Addressrefelement

Address of the storage facility. For more information, see Section 9.1 Address.




Chapter 8



8.26 Contact

Table 8.45 Contact Resource

Page 383

The data type of the Address, ComChannel and Person elements were incorrectly specified as 'element' - these have been corrected to 'refelement'.


The new lines in the table read

NAMEDATA TYPEDESCRIPTION
Address ?refelementElement describing the address.

ComChannel *

Modified in JDF 1.2

refelement

Communication channels such as phone number or email of the contact. These elements define communication channels that MAY be assigned to multiple persons, for instance the communication channel of a reception area.

Person ?refelementName of the contact person.



8.52 Employee

Table 8.82 Employee Resource

Page 419

The data type of the Person element was incorrectly specified as 'element' - this has been corrected to 'refelement'.

The new line in the table reads

NAMEDATA TYPEDESCRIPTION
Person ?refelement

Describes the employee. If no Person resource is specified, the Employee resource represents any employee who fulfills the selection criteria




Chapter 9



9.41 Person

Table 9.49 Person Element

Page 655

The data type of the Address and ComChannel elements were incorrectly specified as 'element' - these have been corrected to 'refelement'.

The new lines in the table read

NAMEDATA TYPEDESCRIPTION

Address ?

New in JDF 1.2

refelementAddress of the Person.

ComChannel *

refelement

Communication channels to the Person.