Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

This page provides a page by summary of all errata that unfortunately made it into XJDF 2.0.

A copy of the XJDF 2.0 specification showing the location of these errata as pdf comment annotations can be found here XJDF Specification 2.0-Final-Errata.pdf.

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

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


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 XJDF. Add 20 to the printed page number in order to navigate to an indexed page, e.g. in Acrobat.

Table of Contents

Quick Links:



Chapter 3


3.1 XJDF

Table 3.1: XJDF (Sheet 2 of 2)

Page 20

XJDF should contain the @Version attribute.

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The new line in the table reads

NAMEDATA TYPEDESCRIPTION
Version ?enumeration

@Version SHALL define the version of the XJDF document. The value of @Version SHALL be "2.0" for documents that comply to this specification.

Allowed values are:
2.0 - This version.


Chapter 4


4.1.1 Product

Table 4.1: Product Element

Page 31

The description of @IsRoot has been amended to clarify that it SHOULD be specified in all root products.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The amended line in the table reads

NAMEDATA TYPEDESCRIPTION
IsRoot ?booleanIf true, this Product is a self-contained product. If false, this Product is a product part of another Product, such as a cover or insert. Multiple Product elements with @IsRoot=”true” may be specified, for instance in a gang job. If the parent ProductList element contains multiple Product elements, @IsRoot SHOULD be specified in all root products.

4.3 BindingIntent

Table 4.9: BindingIntent Element (Sheet 1 of 2)

Page 36

The description of @ChildRefs has been amended to clarify that at least two products should be referenced, and that it shall not be specified for a single bound product.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The amended line in the table reads

NAMEDATA TYPEDESCRIPTION
ChildRefs ?IDREFS@ChildRefs contains references to two or more child products each identified by Product/@ID (e.g., cover and body of a book) that SHALL be bound together. @ChildRefs SHALL NOT be specified if a single Product is bound.


4.7 FoldingIntent

Introduction

Page 45

The introduction incorrectly omitted a clarifying statement intended to prevent adding a FoldingIntent that duplicated folds implied by the binding specified in BindingIntent.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The amended introduction to FoldingIntent reads

This Product Intent specifies the straight line folding, creasing and perforating of a product. Folds that are implied by binding such as "F4-1" of a saddle stitched booklet SHALL NOT be specified. See Section 4.3 BindingIntent for additional details.

Chapter 5


5.4.1 Bending

Table 5.12: Bending – Input Resources

Page 58

The cardinality of the input "ExposedMedia" resource was incorrectly set to optional; this has been corrected to be mandatory.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The amended line in the table reads

NAMEDESCRIPTION
ExposedMedia

The ExposedMedia resource to be bent/punched. Dummy forms are also described as ExposedMedia even though they NEED NOT be imaged.


5.4.7 ImageSetting

Table 5.24: ImageSetting – Input Resources

Page 61

The cardinality of the 'RunList' input resource was incorrectly set to optional; this has been corrected to be mandatory.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The amended line in the table reads

NAMEDESCRIPTION
RunListIdentifies the set of bitmaps to image. The RunList MAY contain bytemaps or images.


Chapter 6


6.19 Contact

Table 6.37: Contact Resource

Page 135

The DataType of @ContactTypeDetails was incorrectly set to string; it should be NMTOKENS.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The amended line in the table reads

NAMEDATA TYPEDESCRIPTION
ContactTypeDetails ?NMTOKENS

@ContactTypeDetails specifies the details of the contact's role or roles.
If Part/@ContactType="Employee", then @ContactTypeDetails SHALL define the list of roles that the employee fills.

Values include:
Apprentice – Employee that is in training (“Auszubildender” / “Auszubildende”/ “Stift” in German).
Assistant – Assistant operator.
Craftsman – Trained employee (“Geselle” / “Facharbeiter” in German).
CSR – Customer Service Representative.
Manager – Manager.
Master – Highly trained employee (“Meister” in German).
Operator – Operator.
ShiftLeader – The leader of the shift.
StandBy – Employee who is allocated to a specific task on demand.


6.62.5 PSCreationDetails

Table 6.137: PSCreationDetails Element (Sheet 2 of 2)

Page 206

The cardinality of the @SuppressRotate attribute was set to mandatory and should be optional.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The amended line in the table reads

NAMEDATA TYPEDESCRIPTION

SuppressRotate ?

boolean

If "true", pages with dimensions that are better suited to landscape orientation SHALL NOT be automatically rotated. More specifically, the application that generates the PostScript compares the dimensions of the page. If the width is greater than the height, then pages are SHALL NOT be rotated if @SuppressRotate="true". On the other hand, if @SuppressRotate="false", the orientation of each source page (e.g., as set by the PDF Rotate key) is honored, regardless of the dimensions of the pages (as defined by the MediaBox attribute).


Chapter 7


3.1 XJMF

Table 7.1: XJMF

Page 243

XJMF should contain the @Version attribute.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The new line in the table reads

NAMEDATA TYPEDESCRIPTION
Version ?enumeration

@Version SHALL define the version of the XJMF document. The value of @Version SHALL be "2.0" for documents that comply to this specification.

Allowed values are:
2.0 - This version.


7.14.1.1 ResourceQuParams

Table 7.49: ResourceQuParams Element

Page 261

The cardinality of the @Scope attribute was set to mandatory and should be optional.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The amended line in the table reads

NAMEDATA TYPEDESCRIPTION

Scope ?

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


Appendix D Media Size

D.4 International B Paper Sizes

Table D.4 International B Paper Sizes

Page 380

The Japanese and International B paper sizes were both mapped to the Japanese B paper sizes, and a single set of NMTOKEN values used, i.e. 'B0'-'B10'.

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.

New NMTOKEN values introduced

The original NMTOKEN values of 'B0' to 'B10' have been completely replaced by these two new tables.

See: Unable to locate Jira server for this macro. It may be due to Application Link configuration.


The section 'D4 International B Paper Sizes' now reads...

D.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 √2m2 whereas the JISB0 sheet has an area of 1.5m2. The aspect ratio of both is identical.

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

D.4.1 International B Paper Sizes

Table D.4: International B Paper Sizes

MEDIA SIZESIZE IN POINTS           SIZE IN
MILLIMETERS		SIZE IN INCHES

ISOB0

2834 x 40081000 x 141439.4 x 55.7

ISOB1

2004 x 2834707 x 100027.8 x 39.4

ISOB2

1417 x 2004500 x 70719.7 x 27.8

ISOB3

1001 x 1417353 x 50013.9 x 19.7

ISOB4

709 x 1001250 x 3539.8 x 13.9

ISOB5

499 x 709176 x 2506.9 x 9.8

ISOB6

354 x 499125 x 1764.9 x 6.9

ISOB7

249 x 35488 x 1253.5 x 4.9

ISOB8

176 x 24962 x 882.4 x 3.5

ISOB9

125 x 17644 x 621.7 x 2.4
ISOB1088 x 12531 x 441.2 x 1.7

D.4.2 Japanese (JIS) B Paper Sizes

Table D.5: Japanese (JIS) B Paper Sizes

MEDIA SIZESIZE IN POINTSSIZE IN
MILLIMETERS		SIZE IN INCHES

JISB0

2920 x 41271030 x 145640.55 x 57.32

JISB1

2064 x 2920728 x 103028.66 x 40.55

JISB2 

1460 x 2064515 x 72820.28 x 28.66

JISB3

1032 x 1460364 x 51514.33 x 20.28

JISB4

729 x 1032257 x 36410.12 x 14.33

JISB5

516 x 729182 x 2577.17 x 10.12

JISB6

363 x 516128 x 1825.04 x 7.17

JISB7

258 x 36391 x 1283.58 x 5.04

JISB8

181 x 25864 x 912.52 x 3.58

JISB9

127 x 18145 x 641.77 x 2.52
JISB1091 x 12732 x 451.26 x 1.77


Appendix F Pagination Catalog

F.1.4.1 Signature with Horizontal Final Folds

Table F.2: Signatures with horizontal final folds

Page 386

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

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

The updated illustration is now


XJDF Schema Errata Issues

The following is a list of all Schema Bugs.


  • No labels