mapping cip4 jdf to pwg print job ticket v1.0 (jdfmap)the printer working group 17 may 2015 working...

The Printer Working Group

17 May 2015 Working Draft

of 50

1 2 3 4 5 6 7 8

9

Mapping CIP4 JDF to PWG Print Job Ticket v1.0 (JDFMAP) 10

11

Status: Prototype 12

13

Abstract: For interoperability between job ticket-based printing systems, this document 14 defines a normative mapping from XML objects and attributes in the CIP4 Job Definition 15 Format [CIP4JDF] to XML elements in the PWG Print Job Ticket and Associated 16 Capabilities [PWG5108.7]. 17

This document is a PWG Working Draft. For a definition of a "PWG Working Draft", see: 18

http://ftp.pwg.org/pub/pwg/general/pwg-process30.pdf 19

This document is available electronically at: 20

http://ftp.pwg.org/pub/pwg/sm3/wd/wd-smjdfmap10-2015517.pdf 21

Deleted: Interim22

Formatted: Indent: Left: 0"

Deleted: 2015042423

http://ftp.pwg.org/pub/pwg/general/pwg-process30.pdf

Working Draft – Mapping CIP4 JDF to PWG PJT (JDFMAP) 17 May 2015

of 50 Copyright © 2011-2015 The Printer Working Group. All rights reserved.

Copyright © 2011-2015 The Printer Working Group. All rights reserved. 24

This document may be copied and furnished to others, and derivative works that comment 25 on, or otherwise explain it or assist in its implementation may be prepared, copied, 26 published and distributed, in whole or in part, without restriction of any kind, provided that 27 the above copyright notice, this paragraph and the title of the Document as referenced 28 below are included on all such copies and derivative works. However, this document itself 29 may not be modified in any way, such as by removing the copyright notice or references to 30 the IEEE-ISTO and the Printer Working Group, a program of the IEEE-ISTO. 31

Title: Mapping CIP4 JDF to PWG Print Job Ticket v1.0 (JDFMAP) 32

The IEEE-ISTO and the Printer Working Group DISCLAIM ANY AND ALL WARRANTIES, 33 WHETHER EXPRESS OR IMPLIED INCLUDING (WITHOUT LIMITATION) ANY IMPLIED 34 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 35

The Printer Working Group, a program of the IEEE-ISTO, reserves the right to make 36 changes to the document without further notice. The document may be updated, replaced 37 or made obsolete by other documents at any time. 38

The IEEE-ISTO takes no position regarding the validity or scope of any intellectual 39 property or other rights that might be claimed to pertain to the implementation or use of the 40 technology described in this document or the extent to which any license under such rights 41 might or might not be available; neither does it represent that it has made any effort to 42 identify any such rights. 43

The IEEE-ISTO invites any interested party to bring to its attention any copyrights, patents, 44 or patent applications, or other proprietary rights which may cover technology that may be 45 required to implement the contents of this document. The IEEE-ISTO and its programs 46 shall not be responsible for identifying patents for which a license may be required by a 47 document and/or IEEE-ISTO Industry Group Standard or for conducting inquiries into the 48 legal validity or scope of those patents that are brought to its attention. Inquiries may be 49 submitted to the IEEE-ISTO by e-mail at: [email protected]. 50

The Printer Working Group acknowledges that the IEEE-ISTO (acting itself or through its 51 designees) is, and shall at all times, be the sole entity that may authorize the use of 52 certification marks, trademarks, or other special designations to indicate compliance with 53 these materials. 54

Use of this document is wholly voluntary. The existence of this document does not imply 55 that there are no other ways to produce, test, measure, purchase, market, or provide other 56 goods and services related to its scope. 57

58



About the IEEE-ISTO 59

The IEEE-ISTO is a not-for-profit corporation offering industry groups an innovative and 60 flexible operational forum and support services. The IEEE-ISTO provides a forum not only 61 to develop standards, but also to facilitate activities that support the implementation and 62 acceptance of standards in the marketplace. The organization is affiliated with the IEEE 63 (http://www.ieee.org/) and the IEEE Standards Association (http://standards.ieee.org/). 64

For additional information regarding the IEEE-ISTO and its industry programs visit: 65

http://www.ieee-isto.org 66

About the IEEE-ISTO PWG 67

The Printer Working Group (or PWG) is a Program of the IEEE Industry Standards and 68 Technology Organization (ISTO) with member organizations including printer 69 manufacturers, print server developers, operating system providers, network operating 70 systems providers, network connectivity vendors, and print management application 71 developers. The group is chartered to make printers and the applications and operating 72 systems supporting them work together better. All references to the PWG in this 73 document implicitly mean “The Printer Working Group, a Program of the IEEE ISTO.” In 74 order to meet this objective, the PWG will document the results of their work as open 75 standards that define print related protocols, interfaces, procedures and conventions. 76 Printer manufacturers and vendors of printer related software will benefit from the 77 interoperability provided by voluntary conformance to these standards. 78

In general, a PWG standard is a specification that is stable, well understood, and is 79 technically competent, has multiple, independent and interoperable implementations with 80 substantial operational experience, and enjoys significant public support. 81

For additional information regarding the Printer Working Group visit: 82

http://www.pwg.org 83

Contact information: 84

The Printer Working Group 85 c/o The IEEE Industry Standards and Technology Organization 86 445 Hoes Lane 87 Piscataway, NJ 08854 88 USA 89

90

http://www.ieee.org/

http://standards.ieee.org/)

http://www.ieee-isto.org/



About the Semantic Model Work Group 91

The Semantic Model Work Group is responsible for the modeling of the services - Print, 92 Copy, Scan, Fax, Resource, System Control, and Transform hosted on Multifunction 93 Devices . Standardization of the Multifunction Device (MFD) model and semantics will 94 support interoperability of devices and services in local and enterprise networks enabling 95 improved job submission, job management, remote administration, and support. The goal 96 of the project is to define a unified semantic model and set of abstract operations for the 97 most common and essential service and device features of the Multifunction Device. For 98 additional information regarding SM visit: 99

http://www.pwg.org/sm 100

Implementers of this specification are encouraged to join the SM mailing list in order to 101 participate in any discussions of the specification. Suggested additions, changes, or 102 clarification to this specification, should be sent to the SM mailing list for consideration. 103 104

http://www.pwg.org/sm



105

Table of Contents 106

1. Introduction ...................................................................................................................... 8 107 2. Terminology ..................................................................................................................... 8 108

2.1 Conformance Terminology ......................................................................................... 8 109 2.2 Printing Terminology................................................................................................... 8 110 2.3 Other Terminology ...................................................................................................... 8 111 2.4 Acronyms and Organizations ..................................................................................... 9 112

3. Requirements ................................................................................................................. 10 113 3.1 Rationale for Mapping of JDF to PJT........................................................................ 10 114 3.2 Use Cases for Mapping of JDF to PJT ..................................................................... 11 115

3.2.1 Print Service Designer ....................................................................................... 11 116 3.2.2 Print Device Designer ........................................................................................ 11 117

3.3 Out-of-Scope for Mapping of JDF to PJT ................................................................. 11 118 3.4 Design Requirements for Mapping of JDF to PJT .................................................... 12 119

4. Mapping of CIP4 Job Definition Format (JDF) ............................................................... 13 120 4.1 Mapping JDF Attributes to PWG Print Job Ticket Elements ..................................... 13 121

4.1.1 Binding ............................................................................................................... 19 122 4.1.2 BindingType ....................................................................................................... 19 123 4.1.3 CompressionSupplied ........................................................................................ 19 124 4.1.4 DocumentCharsetSupplied ................................................................................ 19 125 4.1.5 DocumentFormat ............................................................................................... 20 126 4.1.6 Document Format (w/ Charset) .......................................................................... 20 127 4.1.7 DocumentFormatDetailsSupplied ...................................................................... 20 128 4.1.8 DocumentNumbers ............................................................................................ 20 129 4.1.9 DocumentPages ................................................................................................ 21 130 4.1.10 DocumentPassword ......................................................................................... 21 131 4.1.11 Finishings and FinishingsCol ........................................................................... 21 132 4.1.12 ImpositionTemplate .......................................................................................... 22 133 4.1.13 InsertSheet ...................................................................................................... 22 134 4.1.14 JobFinishings and JobFinishingsCol ................................................................ 22 135 4.1.15 JobPriority ........................................................................................................ 22 136 4.1.16 JobRecipientName ........................................................................................... 22 137 4.1.17 JobUuid ............................................................................................................ 23 138 4.1.18 Media and MediaCol ........................................................................................ 23 139 4.1.19 MediaPreprinted............................................................................................... 23 140 4.1.20 MediaRecycled ................................................................................................ 23 141 4.1.21 MediaSize ........................................................................................................ 24 142 4.1.22 MediaSizeName............................................................................................... 24 143 4.1.23 Number Up....................................................................................................... 24 144 4.1.24 Overrides ......................................................................................................... 24 145 4.1.25 OverridingElements ......................................................................................... 24 146 4.1.26 PageRanges .................................................................................................... 25 147 4.1.27 PresentationDirectionNumberUp ..................................................................... 25 148 4.1.28 PrintColorMode ................................................................................................ 25 149 4.1.29 PrintRenderingIntent ........................................................................................ 26 150



4.1.30 ProofPrint ......................................................................................................... 26 151 4.1.31 TemplateInfo .................................................................................................... 27 152 4.1.32 TemplateName ................................................................................................ 27 153 4.1.33 Trimming .......................................................................................................... 27 154 4.1.34 TrimmingType .................................................................................................. 27 155 4.1.35 XImage Layout ................................................................................................. 28 156 4.1.36 YImage Layout ................................................................................................. 29 157

4.2 Mappings of JDF to PJT Binding Types ................................................................... 30 158 4.3 JDF RunList Resources ............................................................................................ 33 159 4.4 JDF Partitioning Resources ...................................................................................... 33 160 4.5 Mapping JDF Job State Model to PWG Job State Model ......................................... 34 161

5. Conformance Requirements .......................................................................................... 36 162 5.1 Print Server Conformance ........................................................................................ 36 163 5.2 Print Device Conformance ........................................................................................ 36 164

6. Internationalization Considerations ................................................................................ 37 165 7. Security Considerations ................................................................................................. 38 166 8. IANA and PWG Considerations ..................................................................................... 38 167 9. References ..................................................................................................................... 39 168

9.1 Normative References .............................................................................................. 39 169 9.2 Informative References ............................................................................................ 41 170

10. Authors’ Addresses ...................................................................................................... 42 171 11. Change History ............................................................................................................ 43 172

11.1 17 May 2015 – JDFMAP update by SM WG and Rainer Prosi ............................... 43 173 11.2 24 April 2015 – JDFMAP update by SM WG and Rainer Prosi .............................. 44 174 11.3 28 March 2015 – JDFMAP update by SM WG and Rainer Prosi ........................... 44 175 11.4 9 March 2015 – JDFMAP update by SM WG and Rainer Prosi ............................. 44 176 11.5 15 February 2015 – JDFMAP update by SM WG and Rainer Prosi ....................... 45 177 11.6 19 January 2015 – JDFMAP update by SM WG and Rainer Prosi ......................... 45 178 11.7 12 January 2015 – JDFMAP update by SM WG and Rainer Prosi ......................... 45 179 11.8 15 December 2014 – JDFMAP update by SM WG and Rainer Prosi ..................... 46 180 11.9 8 December 2014 – JDFMAP update by SM WG and Rainer Prosi ....................... 46 181 11.10 7 December 2014 – JDFMAP update by SM WG and Rainer Prosi ..................... 46 182 11.11 31 October 2014 – JDFMAP update by SM WG and Rainer Prosi ....................... 47 183 11.12 5 October 2014 – JDFMAP update by SM WG and Rainer Prosi ......................... 47 184 11.13 16 September 2014 – JDFMAP update by SM WG and Rainer Prosi .................. 47 185 11.14 8 September 2014 – JDFMAP update by SM WG and Rainer Prosi .................... 47 186 11.15 28 August 2014 – JDFMAP update by SM WG and Rainer Prosi ........................ 48 187 11.16 29 July 2014 – JDFMAP update by SM WG and Rainer Prosi ............................. 48 188 11.17 21 July 2014 – JDFMAP update by SM WG and Rainer Prosi ............................. 49 189 11.18 4 June 2014 – JDF update by Rick Yardumian and Rainer Prosi ......................... 49 190 11.19 30 April 2014 – JDF update by Rick Yardumian ................................................... 49 191 11.20 6 April 2014 .......................................................................................................... 49 192 11.21 5 October 2011 to 24 October 2013 ..................................................................... 50 193

194



List of Tables 195

Table 1 – Mapping of CIP4 JDF to PWG PJT Elements .................................................... 13 196 Table 2 – Mapping of CIP4 JDF to PWG PJT for Rendering Intent ................................... 26 197 Table 3 – Mapping of CIP4 JDF Postpress Binding Class to PWG PJT BindingType ....... 31 198 Table 4 – Mapping of CIP4 JDF BindingIntent/@BindingType to PWG PJT BindingType . 32 199 Table 5 – Mapping of CIP4 JDF Node Status to PWG SM Job States .............................. 35 200 201

202



1. Introduction 203

For interoperability between job ticket-based printing systems, this document defines a 204 normative mapping from XML objects and attributes defined in the CIP4 Job Definition 205 Format [CIP4JDF] to XML elements defined in the PWG Print Job Ticket and Associated 206 Capabilities [PWG5108.07],. 207

208

2. Terminology 209

2.1 Conformance Terminology 210

Capitalized terms, such as MUST, MUST NOT, RECOMMENDED, REQUIRED, SHOULD, 211 SHOULD NOT, MAY, and OPTIONAL, have special meaning relating to conformance as 212 defined in Key words for use in RFCs to Indicate Requirement Levels [RFC2119]. 213

The term CONDITIONALLY REQUIRED is additionally defined for a conformance 214 requirement that applies to a particular capability or feature. 215

2.2 Printing Terminology 216

Normative definitions and semantics of printing terms are imported from the Printer MIB v2 217 [RFC3805], Printer Finishings MIB [RFC3806], and Internet Printing Protocol/1.1: Model 218 and Semantics [RFC2911]. 219

This document also defines the following protocol roles in order to specify unambiguous 220 conformance requirements: 221

Client: Initiator of outgoing IPP session requests and sender of outgoing IPP operation 222 requests. 223

Printer: Listener for incoming IPP session requests and receiver of incoming IPP operation 224 requests that represents one or more Physical Devices or a single Logical Device. 225

Proxy: A Client that sends configuration and status information to and retrieves and 226 manages Jobs and Documents from a shared Logical Device on behalf of one or more 227 Output Devices. 228

2.3 Other Terminology 229

Document: An object created and managed by a Printer that contains the description, 230 processing, and status information. A Document object may have attached data and is 231 bound to a single Job. 232



Job: An object created and managed by a Printer that contains description, processing, 233 and status information. The Job also contains zero or more Document objects. 234

Logical Device: a print server, software service, or gateway that processes jobs and either 235 forwards or stores the processed job or uses one or more Physical Devices to render 236 output. 237

Output Device: a single Logical or Physical Device. 238

Physical Device: a hardware implementation of an print device (that includes a marking 239 engine). 240

2.4 Acronyms and Organizations 241

CIP4: International Cooperation for the Integration of Processes in Prepress, Press, and 242 Postpress Organization, http://www.cip4.org/ 243

IANA: Internet Assigned Numbers Authority, http://www.iana.org/ 244

IEEE: Institute of Electrical and Electronics Engineers, http://www.ieee.org/ 245

IETF: Internet Engineering Task Force, http://www.ietf.org/ 246

JDF: CIP4 Job Definition Format, http://www.cip4.org/ 247

ISO: International Organization for Standardization, http://www.iso.org/ 248

NEA: IETF Network Endpoint Assessment WG, http://datatracker.ietf.org/wg/nea/charter/ 249

PJT: PWG Print Job Ticket, http://www.pwg.org/ 250

PWG: IEEE-ISTO Printer Working Group, http://www.pwg.org/ 251

http://www.cip4.org/

http://www.iana.org/

http://www.ieee.org/

http://www.ietf.org/


http://www.iso.org/

http://datatracker.ietf.org/wg/nea/charter/

http://www.pwg.org/

http://www.pwg.org/



3. Requirements 252

3.1 Rationale for Mapping of JDF to PJT 253

Originally, in order to print a document from a mainframe, desktop, or mobile computer, it 254 was necessary to understand the characteristics and capabilities and configured defaults 255 of the target printer: accessibility, supported document formats, color capability, duplex 256 capability, etc. When submitting a print job, it has traditionally been necessary to specify 257 (or accept default) values for each of these capabilities. Originally, when the printer 258 supported only unidirectional or simple print protocols, printer capabilities were statically 259 defined in specific drivers, Adobe PostScript Printer Description (PPD) files, and/or user-260 entered configuration information. Originally, the capabilities to be used for a given job 261 were also embedded in the document description format such as Adobe Postscript and HP 262 Printer Control Language (PCL). Later, as printers and print protocols evolved, capabilities 263 and job information were exchanged via separate commands using Adobe PostScript, HP 264 Printer Job Language (PJL). Finally, as open print standards evolved, CIP4 JDF 265 [CIPJDF4] and IETF/PWG Internet Printing Protocol (IPP) [RFC2911] [PWG5100.12] 266 [PWG5100.14] became widespread in production printers and digital network printers, 267 respectively. 268

Creating, managing, storing, and accessing printer-specific drivers and PPDs was always 269 time-consuming, storage-intensive, and error-prone and had high implementation costs for 270 printer and operating system manufacturers. 271

It is not feasible to determine printer capabilities when there are a large number of 272 potential targets, when the target printers are remote, and/or when there is no direct 273 communication possible with each printer. 274

To address the limitations of traditional print protocols, two types of data elements have 275 evolved in CIP4 and PWG standards: 276

1) A set of elements with value ranges defining printer capabilities (printer capabilities); 277

2) A set of element values specifying the capabilities values to be used for a specific 278 job (print job ticket). 279

To enable interoperability, the CIP4 JDF [CIP4JDF] data elements should be mapped to 280 the corresponding data elements in the PWG Print Job Ticket and Associated Capabilities 281 [PWG5108.07]. 282

283

Formatted: Numbered + Level: 1 +Numbering Style: 1, 2, 3, … + Start at: 1 +Alignment: Left + Aligned at: 0.25" + Indentat: 0.5"



3.2 Use Cases for Mapping of JDF to PJT 284

This document does not define any new elements, structure or protocol; it correlates 285 different sets of elements defined elsewhere. Therefore, end-user scenarios are not 286 applicable. Rather, users of this information will be print service designers and clients that 287 interface with print services seeking to better provide and use the Printer Capabilities and 288 Submitted Job Ticket information. 289

3.2.1 Print Service Designer 290

A print service designer is responsible for interfacing printer devices from multiple vendors 291 with several remote print services requiring Printer Capabilities and submitting Print Job 292 Tickets using various standard but differing representations. All of the target printers 293 support IPP [RFC2911] [PWG5100.12], and as such can be considered to offer interfaces 294 fully compliant with the PWG Print Job Ticket [PWG5108.07]. The print service designer 295 needs a consistent guide in mapping the capabilities elements accessible from the printers 296 via IPP to the Printer Capabilities structures needed by JDF model [CIP4JDF]. Similarly, 297 the print service designer needs a consistent guide in translating the job ticket information 298 provided in JDF job tickets into IPP attributes. 299

3.2.2 Print Device Designer 300

A print device designer has a new, improved product that the marketing group wants to 301 advertise as out-of-the box compatible with systems using various representations for 302 Printer Capabilities and Print Job Tickets. This new printer supports IPP [RFC2911] 303 [PWG5100.12], and the print device designer wants to be able to support IPP and the data 304 structures supplied in JDF Job Tickets [CIP4JDF] using a common internal mapping 305 database. 306

3.3 Out-of-Scope for Mapping of JDF to PJT 307

The following are out of scope for this specification: 308

1) Creation of any new element not in either the PWG model or the method to which it 309 is being cross mapped. 310

2) Definition of a specific structure of how the Printer Characteristics and/or Job Ticket 311 elements are to be presented. 312

313



3.4 Design Requirements for Mapping of JDF to PJT 314

This specification should: 315

1) Follow the naming conventions in PWG Print Job Ticket [PWG5108.07]. 316

2) Conform to the normative specifications for each of the Printer Characteristic and 317 each of the Print Ticket elements in [CIP4JDF] and [PWG5108.07]. 318

3) Map elements from [CIP4JDF] to [PWG5108.07] in a one-to-one manner, whenever 319 possible. 320

4) Whenever a one-to-one element mapping is not possible, define the best practice 321 for complex mapping between elements and groups of elements. 322

5) Define conformance requirements for implementations of Print Servers and Print 323 Devices. 324

325



4. Mapping of CIP4 Job Definition Format (JDF) 326

4.1 Mapping JDF Attributes to PWG Print Job Ticket Elements 327

JDF attributes are encoded as XML attributes in XML schema instances – instead of as 328 XML elements as in the PWG Print Job Ticket (PJT) – this complicates JDF/PJT mapping 329 implementations. JDF attributes are defined in the CIP4 JDF Specification Release 1.5 330 [CIP4JDF] and profiled for various printing environments in a series of CIP4 ICS 331 (Interoperability Conformance Specification) documents, in particular the CIP4 Integrated 332 Digital Printing (IDP) ICS v1.3 [CIP4IDP]. The reader is also directed to the section 333 “Mapping of parameters into JDF elements and attributes” on pages 167-173 of Adobe 334 PDF Creation Settings [ADOBECREATE] for information on the extent of JDF support and 335 mapping choices in Adobe Acrobat 9.0. 336

Notes: 337

1) JDF uses 0-based ranges. The PWG PJT and IPP use 1-based ranges. 338 Implementations of mappings defined in Table 1 need to convert ranges 339 accordingly. 340

2) JDF object/attribute and PWG element pairs listed in Table 1 in bold have 341 corresponding complex mapping discussion sections below Table 1, based on the 342 PWG element name. 343

3) In PWG Web Service and IPP protocol bindings, certain elements (attributes) are 344 sent as operation parameters (“invisible” because not saved to the corresponding 345 Job/Document objects). XxxSupplied elements in the PWG JobTicket and 346 JobReceipt (and corresponding IPP objects) record these elements (attributes) for 347 each Job/Document. 348

4) In the future, CIP4 may deprecate the usage of the LayoutPreparation process and 349 replace it with the Stripping process which is more general. 350

5) In the future, PWG may define a Compression attribute that applies to individual 351 Documents. 352

Table 1 – Mapping of CIP4 JDF to PWG PJT Elements 353 354

CIP4 JDF Object or Attribute PWG Print Job Ticket Element

FileSpec/@Compression CompressionSupplied (note 3) (note5)

[Output] ComponentLink/@Amount Copies

<none> CoverBack CoverType

Media

MediaCol

Formatted Table




<none> CoverFront

CoverType Media

MediaCol

FileSpec/@Encoding DocumentCharsetSupplied (note 3)

FileSpec/@CheckSum DocumentDigitalSignatureSupplied (note 3)

FileSpec/@MimeType DocumentFormat

FileSpec

/@Application

/@AppVersion

/@AppOS /@OSVersion

/@MimeType

/@FileTargetDeviceModel <none>

/@DocumentNaturalLang

DocumentFormatDetailsSupplied (note 3)

DocumentSourceApplicationName

DocumentSourceApplicationVersion

DocumentSourceOsName DocumentSourceOsVersion

DocumentFormat

DocumentFormatDeviceId DocumentFormatVersion

DocumentNaturalLanguage

<none> DocumentMessageSupplied (note 3)

FileSpec/@UserFileName DocumentName

FileSpec/@Password DocumentPassword

FileSpec/@DocumentNaturalLang ElementsNaturalLanguage

[Input] ComponentLink/@Orientation FeedOrientation

Finishings Finishings

Finishings

Wrapping/WrappingParams

/@WrappingKind <none>

XxxBinding (class) or BindingIntent/

/XxxParams/HoleMakingParams/ @HoleReferenceEdge

@BindingType

VarnishingParams

@Side (Front, Back, empty) Ink/@SpecialInk

<none>

Folding/Fold

/@To

/@Travel /@From

LaminatingParams

/@Side

Media/@FrontCoatings HoleMaking/HoleMakingParams

/@Hole

/@Center ComponentLink/@Orientation

StitchingParams

FinishingsCol

FinishingTemplate

Bailing

BailingType BailingWhen

Binding

BindingReferenceEdge

BindingType

Coating

CoatingSides

CoatingType

Covering

CoveringName Folding

FoldingDirection

FoldingOffset FoldingReferenceEdge

Laminating

LaminatingSides

LaminatingType Punching

PunchingLocations

PunchingOffset PunchingReferenceEdge

Stitching

Formatted Table




/@StitchPositions

/@Offset ComponentLink/@Orientation

CuttingParams/Cut or

PerforatingParams/Perforate or

CreasingParams/Crease

/@StartPosition

/@WorkingPath

<implicit>

<none>

StitchingLocations

StitchingOffset StitchingReferenceEdge

Trimming

TrimmingOffset

TrimmingReferenceEdge

TrimmingType TrimmingWhen

FontPolicy/@PreferredFont FontNameRequested

<none> FontSizeRequested

LayoutPreparationParams/InsertSheet/ @SheetUsage=”FillForceFront” (and)

@SheetType=”FillSheet”

ForceFrontSide (note 4)

LayoutPreparationParams/

ExternalImpositionTemplate/FileSpec/ @UserFileName

ImpositionTemplate (note 4)

RunList/@Page (divided by)

LayoutPreparationParams/NumberUp

Impressions

RunList/InsertSheet

<complex mapping>

<none> Layout/Media

Layout/Media

InsertSheet

ISheet

InsertAfterPage

InsertCount Media

MediaCol

CustomerInfo/@BillingCode JobAccountingID

InsertSheet @SheetType= ”AccountingSheet”

<none>

Layout/Media Layout/Media

<none>

JobAccountingSheets

JobAccountingSheetsType

Media MediaCol

JobAccountingOutputBin

CustomerInfo/@CustomerID JobAccountingUserID

[Output] ComponentLink/@Amount JobCopies

<none> JobCoverBack

CoverType

Media

MediaCol

<none>

JobCoverFront

CoverType

Media MediaCol

<none> JobDelayOutputUntil

NodeInfo/@FirstStart JobDelayOutputUntilTime

Formatted Table

Deleted: <355

Deleted: >356




InsertSheet

@SheetType=”ErrorSheet” <none>

<none>

Layout/Media

Layout/Media

JobErrorSheet

JobErrorSheetType

JobErrorSheetWhen

Media MediaCol

Finishings JobFinishings

Finishings JobFinishingsCol

<none> JobHoldUntil

NodeInfo/@FirstStart JobHoldUntilTime

@SettingsPolicy=”MustHonor” (generic JDF element attribute)

JobMandatoryElements

JDF/Comment[@Name=”OperatorText”] JobMessageFromOperator

JDF/Comment[@Name=”Instruction”] JobMessageToOperator

<none> JobMoreInfo

CustomerInfo/@CustomerJobName JobName

Contact/@UserID JobOriginatingUserName

<none> JobOriginatingUserUri

<none> JobPassword

<none> JobPasswordEncryption

CustomerInfo/Contact/ComChannel/@Locator JobPhoneNumber

NodeInfo/@Priority JobPriority

CustomerInfo/Contact/Person JobRecipientName

<none> JobSaveDisposition

SaveDisposition SaveInfo

SaveDocumentFormat

SaveLocation SaveName

<none> JobSheetMessage

InsertSheet/@SheetType=”JobSheet” JobSheets

InsertSheet @SheetType=”JobSheet”

@SheetUsage

Layout/Media

Layout/Media

JobSheetsCol

JobSheets

Media

MediaCol

QueueEntryId JobUuid

<none> KOctets

Media Media

Formatted Table




Media

Media/@BackCoatings Media/@MediaColorName

Media/@FrontCoatings

Media/@GrainDirection Media/@HoleType & Media/HoleList

Media/Comment/@Name=

“Description”

Media/GeneralID Media/@MediaSetCount

Media/@PrePrinted

Media/@RecycledPercentage

Media/@Dimension

(see Media/@Dimension)

(see Media/@Dimension) <none>

Media/@Thickness

Media/@Texture

Media/@MediaTypeDetails Media/@Weight

DigitalPrintingParams/@NonPrintableMarg

inBottom DigitalPrintingParams/@NonPrintableMarg

inLeft

DigitalPrintingParams/@NonPrintableMarginRight

DigitalPrintingParams/@NonPrintableMarg

inTop

Media/@Location (input tray name)

MediaCol

MediaBackCoating MediaColor

MediaFrontCoating

MediaGrain MediaHoleCount

MediaInfo

MediaKey MediaOrderCount

MediaPreprinted

MediaRecycled

MediaSize

XDimension

YDimension

MediaSizeName

MediaThickness

MediaTooth

MediaType MediaWeightMetric

MediaBottomMargin

MediaLeftMargin

MediaRightMargin

MediaTopMargin

MediaSource

<none> MediaInputTrayCheck

[Input] MediaLink/@Amount MediaSheets

<none> MultipleDocumentsHandling

LayoutPreparationParams/@NumberUp NumberUp

LayoutPreparationParams/@Rotate OrientationRequested

DigitalPrintingParams/@OutputBin OutputBin

<none> OutputDevice

Formatted Table




RunListLink/Part or other Link/Part

@DocRunIndex

@DocIndex

@DocCopies

<other JDF attribute>

Overrides

Override Pages

PageRange

Lowerbound Upperbound

DocumentNumbers

NumberRange

Lowerbound Upperbound

DocumentCopies

PCopiesRange Lowerbound

Upperbound

OverridingElements

DigitalPrintingParams/@PageDelivery PageDelivery

FileSpec/@PageOrder PageOrderReceived

RunList/@Pages

<none> (see Overrides)

(see Overrides)

PageRanges

PageRange Lowerbound

Upperbound

<none>

PagesPerSubset

Pages

<none>

PdlInitFiles

PdlInitFile PdlInitFileLocation

PdlInitFileName

PdlInitFileEntry

LayoutPreparationParams/

@PresentationDirection

PresentationDirectionNumberUp

ColorantControl/@ProcessColorModel PrintColorMode

<none> PrintContentOptimize

ColorSpaceConversionParams/

ColorSpaceConversionOp/@RenderingIntent

PrintRenderingIntent

<none>

DigitalPrintingParams/

@DirectProofAmount <none>

<none>

ProofPrint

Copies

Media

MediaCol

InterpretingParams/@PrintQuality Quality

RenderingParams/ObjectResolution/@Resolution Resolution

InsertSheet

@SheetType=”SeparatorSheet”

@SheetUsage Layout/Media

Layout/Media

SeparatorSheets

SeparatorSheetsType Media

MediaCol

DigitalPrintingParams/@Collate SheetCollate

DigitalPrintingParams/@Sides Sides

<none> TemplateCreatorUserName

Formatted Table

Comment [i1]: 08/25/14 – Rainer says this is sort of upside down to the way JDF does it – we

have to map JDF Partioning to PWG Overrides – Rainer suggests that you could take a JDF Job Ticket and create *only* Overrides in a

PWG PJT – will need examples. Rainer thinks we could use, for example RunListLink/Part/@DocRunIndex (page ranges)

or RunListLink/Part/@DocCopies (document copies) or

RunListLink/Part/@DocIndex (document numbers). Mention JDF zero-based vs PWG one-based.

- 01/12/15 – Partitioning resource is key here e.g., Media/Media/@RunIndex = ‘5~-1’ - mapping paragraph needed for Overrides

about Partitioning resource and for OverridingElements for examples of N-up, media, etc.




<none> TemplateId

JDF/@TemplateVersion TemplateInfo

JDF/@TemplateID TemplateName

<none> TemplateType

LayoutPreparationParams/ImageShift/

@PositionX

XImagePosition


@ShiftFront

XImageShift


@ShiftFront

XSide1ImageShift


@ShiftBack

XSide2ImageShift


@PositionY

YImagePosition


@ShiftFront

YImageShift


@ShiftFront

YSide1ImageShift


@ShiftBack

YSide2ImageShift

357

4.1.1 Binding 358

PWG PJT Mapping: Binding 359

See detailed mappings for various JDF binding classes and attributes in section 4.2 below. 360

4.1.2 BindingType 361

PWG PJT Mapping: BindingType 362

See detailed mappings for various JDF binding classes and attributes in section 4.2 below. 363

4.1.3 CompressionSupplied 364

PWG PJT Mapping: CompressionSupplied (see note 3 and note 5 above) 365

JDF defines the FileSpec element in section 8.57 “FileSpec” of [CIP4JDF], which contains 366 the Compression attribute, whose keyword values map directly to values of the PWG PJT 367 CompressionSupplied element. 368

Note: The JDF Compression attribute only applies to the FileSpec element that it is 369 attached to – but the PWG CompressionSupplied element applies to the entire Job. 370

4.1.4 DocumentCharsetSupplied 371

PWG PJT Mapping: DocumentCharsetSupplied (see note 3 above) 372

Formatted Table



JDF defines the FileSpec element in section 8.57 “FileSpec” of [CIP4JDF], which contains 373 the Encoding attribute. PWG and JDF both use the IANA Charset Registry [IANACHAR]. 374

4.1.5 DocumentFormat 375

PWG PJT Mapping: DocumentFormat 376

JDF defines the FileSpec element in section 8.57 “FileSpec” of [CIP4JDF], which contains 377 the MimeType attribute which maps directly to the PWG PJT DocumentFormat element. 378 PWG and JDF both use the IANA Mime Media Types Registry [IANAMIME]. 379

4.1.6 Document Format (w/ Charset) 380

PWG PJT Mapping: Document Format, DocumentCharsetSupplied (see note 3 above) 381

JDF defines the FileSpec element in section 8.57 “FileSpec” of [CIP4JDF], which contains 382 the MimeType attribute which maps directly to the PWG PJT DocumentFormat element. 383 PWG and JDF both use the IANA Mime Media Types Registry [IANAMIME]. 384

Note: When a “charset” parameter is appended to the JDF MimeType attribute, the JDF 385 MimeType can be mapped to the PWG PJT DocumentFormat and PWG PJT 386 DocumentCharsetSupplied elements. 387

4.1.7 DocumentFormatDetailsSupplied 388

PWG PJT Mapping: DocumentFormatDetailsSupplied (see note 3 above) 389

JDF defines the FileSpec element in section 8.57 “FileSpec” of [CIP4JDF] and the PWG 390 PJT DocumentFormatDetailsSupplied element has similar content. Therefore, each PWG 391 PJT DcumentFormatDetailsSupplied member element MUST be mapped directly from the 392 corresponding JDF FileSpec element – see details in Table 1 above. 393

4.1.8 DocumentNumbers 394

PWG PJT Mapping: DocumentNumbers 395

JDF defines the RunList resource in section 8.125 “RunList” of [CIP4JDF], which contains 396 the Docs attribute. 397

Note: The JDF Docs attribute is a zero-based list of document indices in a multi-document 398 file specified by the LayoutElement Resource – but the PWG PJT DocumentNumbers 399 element is a single range of ‘1..MAX’. Therefore, only an approximate mapping is possible 400 from the JDF Docs attribute to the PJT Document element. Also, every JDF Docs value 401 MUST be incremented by one to map to the corresponding PJT DocumentNumbers value. 402 All negative JDF Docs values MUST be calculated from the known actual range of Docs 403 values for the given Job. For example, a JDF Docs value of ‘0 ~ -1’ specifies the first 404 document through the last document in the RunList. 405

Deleted: element 406



4.1.9 DocumentPages 407

PWG PJT Mapping: DocumentPages 408

JDF defines the RunList resource in section 8.125 “RunList” of [CIP4JDF], which contains 409 the Pages attribute. 410

Note: The JDF Pages attribute is a zero-based list of indices in the documents in the 411 LayoutElement resource – but the PWG PJT DocumentPages element has a range of 412 ‘1..MAX’ and specifies the total number of pages in the Document. Therefore, only an 413 approximate mapping is possible from the JDF Pages attribute to the PJT DocumentPages 414 element. Also, every JDF Pages value MUST be incremented by one to map to the 415 corresponding PJT DocumentPages value. All negative JDF Pages values MUST be 416 calculated from the known actual range of DocumentPages values for the given 417 Document. 418

4.1.10 DocumentPassword 419

PWG PJT Mapping: DocumentPassword 420

JDF defines the FileSpec element in section 8.57 “FileSpec” of [CIP4JDF], which contains 421 the Password attribute. 422

Note: The JDF Password attribute contains either: (a) a cleartext password; or (b) the 423 decryption key needed to read the document file contents – but the PWG PJT 424 DocumentPassword operation parameter always contains a cleartext password supplied 425 by the IPP Client over a secure Job submission channel. 426

4.1.11 Finishings and FinishingsCol 427

PWG PJT Mapping: Finishings, FinishingsCol 428

JDF does not define a single Finishings object – instead, section 6.4 “Postpress 429 Processes” of [CIP4JDF] defines over 50 finishing processes including: ChannelBinding, 430 CoilBinding, Cutting, Folding, HoleMaking, PlasticCombBinding, RingBinding, 431 SaddleStitching, Stitching, StripBinding, Trimming, and WireCombBinding. 432

JDF section 7 “Intents” of [CIP4JDF] defines Intent Resource elements that closely 433 correspond to the PWG Print Job Ticket including: section 7.5 “BindingIntent” (which 434 includes stitching), section 7.9 “FoldingIntent”, section 7.10 “HoleMakingIntent”, and 435 section 7.13 “LayoutIntent”. 436

JDF section 8 “Parameters” of [CIP4JDF] defines further Resource elements that closely 437 correspond to the PWG Print Job Ticket including: section 8.17 “CoilBindingParams”, 438 section 8.36 “CuttingParams”, section 8.58 “FoldingParams”, section 8.66 “HoleList”, 439 section 8.67 “HoleMakingParams”, section 8.103 “PlasticCombBindingParams”, section 440 8.124“RingBindingParams”, section 8.126 “SaddleStitchingParams”, section 8.143 441




“StitchingParams”, section 8.145 “StripBindingParams”, section 8.157 “TrimmingParams”, 443 and section 8.162 “WireCombBindingParams”. 444

4.1.12 ImpositionTemplate 445

PWG PJT Mapping: ImpositionTemplate 446

JDF defines the ExternalImpositionTemplate in section 8.55 of [CIP4JDF], which contains 447 the FileSpec element, which contains the UserFileName attribute (user-friendly file name), 448 which can be mapped to the PJT ImpositionTemplate element (keyword of ‘None’ or 449 ‘Signature’ or site-specific name) defined in [PWG5100.3]. The PJT ImpositionTemplate 450 element interacts in an implementation-specific manner with the PJT NumberUp element 451 and PJT XImage and YImage layout elements. 452

4.1.13 InsertSheet 453

PWG PJT Mapping: InsertSheet, InsertAfterPage, InsertCount 454

JDF defines the RunList resource in section 8.125 “RunList” of [CIP4JDF], which contains 455 the InsertSheet element defined in section 8.77 “InsertSheet” of [CIP4JDF]. The position 456 of the InsertSheet can be inferred from the location of the InsertSheet element in the 457 RunList for the mapping to the PWG PJT InsertPageAfter element. The chosen mapping 458 for PWG PJT InsertCount is <none> because JDF normally has a separate InsertSheet for 459 each inserted page. 460

4.1.14 JobFinishings and JobFinishingsCol 461

PWG PJT: JobFinishings and JobFinishingsCol 462

See section 4.1.11 Finishings and FinishingsCol above. 463

4.1.15 JobPriority 464

PWG PJT Mapping: JobPriority 465

JDF defines the NodeInfo element in section 8.91 “NodeInfo” of [CIP4JDF], which contains 466 the JobPriority attribute. 467

Note: The JDF JobPriority attribute has a range of ‘0’ (lowest) to ‘100’ (highest) – but the 468 PWG PJT JobPriority element has a range from ‘1’ (lowest) to ‘100’ (highest). Therefore, a 469 JDF JobPriority value of ‘0’ MUST be mapped to a PJT JobPriority value of ‘1’ and all other 470 JDF values MUST be mapped directly to the identical PJT values. 471

4.1.16 JobRecipientName 472

PWG PJT Mapping: JobRecipientName 473

JDF defines the CustomerInfo element in section 8.3 “CustomerInfo” of [CIP4JDF], which 474 contains the Contact element defined in section 8.27 “Contact” of [CIP4JDF], which 475




contains the Person dlement defined in section 10.29 “Person” of [CIP4JDF], which 477 contains the FirstName, FamilyName, JobTitle, NamePrefix, and NameSuffix attributes (all 478 of which SHOULD be included in the value of PWG PJT JobRecipientName). 479

4.1.17 JobUuid 480

PWG PJT Mapping: JobUuid 481

JDF defines the JobPhase element in section 5.9.9.3 “JobPhase”, the QueueEntry element 482 in section 5.14.2 “QueueEntry”, and various other elements of [CIP4JDF], all of which 483 contain the QueueEntryID attribute, a string which could contain a UUID of a Job. 484

Note: PJT JobUuid contains a UUID in the form of a URN that conforms to [RFC4122]. 485 JDF QueueEntryID is assigned by the PrintService at Job creation time. PJT JobUuid is 486 assigned by the Print Service at Job creation time and therefore can only appear in a PWG 487 JobReceipt and NOT in a PWG JobTicket (before Job submission). A JDF system that 488 plans to forwards a Job to a PWG Print Service SHOULD assign a QueueEntryID value in 489 the form of a URN that conforms to [RFC4122]. 490

4.1.18 Media and MediaCol 491

PWG PJT Mapping: Media, MediaCol 492

JDF defines the Media element in section 9.7 “Media” of [CIP4JDF]. Most of the PWG PJT 493 MediaCol member elements MUST be mapped directly from the corresponding JDF Media 494 attributes – see details in Table 1 above. 495

4.1.19 MediaPreprinted 496

PWG PJT Mapping: MediaPreprinted 497

JDF defines the Media element in section 9.7 “Media” of [CIP4JDF] which contains the 498 PrePrinted attribute which is a boolean – but the PJT MediaPrePrinted element is a 499 keyword (Blank, PrePrinted, LetterHead are currently defined). Therefore, only a partial 500 mapping is possible from the JDF PrePrinted attribute to the PJT MediaPrePrinted 501 element. 502

4.1.20 MediaRecycled 503

PWG PJT Mapping: MediaRecycled 504

JDF defines the Media element in section 9.7 “Media” of [CIP4JDF], which contains the 505 RecycledPercentage attribute. 506

Note: The JDF RecycledPercentage attribute is an integer (0 to 100) and SHOULD be 507 mapped to the PJT MediaRecycled element, by converting a JDF value of 51 percent to a 508 PJT keyword of “Standard” for best fidelity. 509



4.1.21 MediaSize 510

PWG PJT Mapping: MediaSize 511

JDF defines the Media element in section 9.7 “Media” of [CIP4JDF], which contains the 512 Dimension attribute. 513

Note: The JDF Dimension attribute is a pair of integers (X and Y dimensions in points) and 514 has a direct mapping to the XDimension and YDimension members (in hundredths of 515 millimeters) of the PJT MediaSize element [PWG5100.3]. When converting from a JDF 516 Dimension attribute to a PJT MediaSize element, an approximate mapping with a 517 tolerance of 1-2 percent SHOULD be used, in order to select the correct media actually 518 intended by the Job Owner. 519

4.1.22 MediaSizeName 520

PWG PJT Mapping: MediaSizeName 521

JDF defines the Media element in section 9.7 “Media” of [CIP4JDF], which contains the 522 Dimension attribute. 523

Note: The JDF Dimension attribute is a pair of integers (X and Y dimensions in points) and 524 has no direct mapping to a PJT MediaSizeName element [PWG5101.1], since the class 525 (“na”, “iso”, etc.) cannot be reliably inferred. 526

4.1.23 Number Up 527

PWG PJT Mapping: NumberUp 528

JDF defines the LayoutPreparationParams element in section 8.86 529 “LayoutPreparationParams” of [CIP4JDF], which contains the NumberUp attribute. 530

Note: The JDF NumberUp attribute is a pair of integers (the number of columns and 531 number of rows) – but the PWG PJT NumberUp element is a single integer (1, 4, 6, 9, etc.) 532 that does NOT constrain the column/row layout implementation choices. Therefore, only 533 an approximate mapping is possible from the JDF NumberUp attribute to the PJT 534 NumberUp element. 535

4.1.24 Overrides 536

PWG PJT Mapping: Overrides 537

JDF defines the RunList resource in section 8.125 “RunList” of [CIP4JDF] (a Process 538 resource). See section 4.3 JDF RunList Resources below for more details. 539

4.1.25 OverridingElements 540

PWG PJT Mapping: OverridingElements 541

Comment [i2]: 11/10/14 – revise this section

after discussing Overrides mappings in table.




JDF defines Partitioned resources in section 3.11.5 “Description of Partitioned Resources” 543 of [CIP4JDF]. See section 4.4 JDF Partitioning Resources below for more details. 544

4.1.26 PageRanges 545

PWG PJT Mapping: InsertAfterPage, PageRanges 546

JDF defines the RunList resource in section 8.125 “RunList” of [CIP4JDF], which contains 547 the Pages attribute. 548

Note: The JDF Pages attribute is a list of zero-based integer ranges – but the PWG PJT 549 PageRanges element is a single range of integer (1..MAX). Therefore, only an 550 approximate mapping is possible from the JDF Pages attribute to the PJT PageRanges 551 element. Also, every JDF Pages value MUST be incremented by one to map to the 552 corresponding PJT PageRanges value. All negative JDF Pages values MUST be 553 calculated from the known actual range of PJT PageRanges values for the given 554 Document. 555

4.1.27 PresentationDirectionNumberUp 556

PWG PJT Mapping: PresentationDirectionNumberUp 557

JDF defines the LayoutPreparationParams element in section 8.86 558 “LayoutPreparationParams” of [CIP4JDF], which contains the PresentationDirection 559 attribute. 560

Note: The JDF PresentationDirection attribute is a keyword (either ‘FoldCatalog’ or 561 permutations of ‘XYZ’, each letter in uppercase or lowercase to specify the order in which 562 finished pages are flowed along each axis with respect to the coordinate system of the 563 front side of the Sheet – but the PJT PresentationDirectionNumberUp element is a 564 keyword (e.g., TorightTobottom, TobottomToright, ToleftTotop). Therefore, only an 565 approximate mapping is possible from the JDF PresentationDirection attribute to the PJT 566 PresentationDirectionNumberUp element. 567

4.1.28 PrintColorMode 568

PWG PJT Mapping: PrintColorMode 569

JDF defines the ColorantControl element in section 8.21 “ColorantControl” of [CIP4JDF], 570 which contains the ProcessColorModel attribute. 571

Note: The JDF ProcessColorModel attribute is a keyword (DeviceCMY, DeviceCMYK, 572 DeviceGray, DeviceN, DeviceRGB, or None) – but the PJT PrintColorMode attribute is a 573 keyword (Auto, BiLevel, Color, Highlight, Monochrome, ProcessBiLevel, 574 ProcessMonochrome). Therefore, only an approximate mapping is possible from the JDF 575 ProcessColorModel attribute to the PJT PrintColorMode element. 576

577

Deleted: ISSUE: More details on JDF 578 Partioning resource.¶579




4.1.29 PrintRenderingIntent 581

PWG PJT Mapping: PrintRenderingIntent 582

JDF defines the ColorSpaceConversionParams element in section 8.25 of [CIP4JDF], 583 which contains the ColorSpaceConversionOp element defined in section 10.7 of 584 [CIP4JDF], which contains the RenderingIntent attribute. 585

Note: The JDF RenderingIntent attribute is an enumeration (AbsoluteColorimetric, 586 Perceptual, RelativeColorimetric, Saturation, or ColorSpaceDependent (i.e., 587 implementation-defined)) – but the PJT PrintRenderingIntent element is a keyword 588 (Absolute, Auto, Perceptual, Relative, RelativeBPC, or Saturation). 589

Notes: 590

1) JDF RelativeColorimetric and equivalent PWG PJT Relative specify “white point 591 compensation” – defined in section 5.2.4 of [PWG5100.13] as “Clip out-of-gamut 592 colors to preserve in-gamut accuracy, adjusting the white point as necessary.” 593

2) PWG PJT Relative specifies “black point compensation” – defined in section 5.2.4 594 of [PWG5100.13] as “Clip out-of-gamut colors to preserve in-gamut accuracy, 595 adjusting both the white and black points as necessary.” 596

Table 2 – Mapping of CIP4 JDF to PWG PJT for Rendering Intent 597

JDF RenderingIntent PJT PrintRenderingIntent

AbsoluteColorimetric Absolute

ColorSpaceDependent Auto

Perceptual Perceptual

RelativeColorimetric Relative (note 1)

<none> RelativeBPC (note 2)

Saturation Saturation

598

4.1.30 ProofPrint 599

PWG PJT Mapping: ProofPrint 600

There is no JDF support for specifying specific media for ProofPrint. Use standard Media 601 or MediaCol from PrintJob for ProofPrint. 602

Formatted: Numbered + Level: 1 +Numbering Style: 1, 2, 3, … + Start at: 1 +Alignment: Left + Aligned at: 0.29" + Indentat: 0.54"

Deleted: 603

Deleted: ¶604

Formatted Table



605

4.1.31 TemplateInfo 606

PWG PJT Mapping: TemplateInfo 607

JDF defines the JDF Node in section 3.2 of [CIP4JDF], which contains the 608 TemplateVersion attribute. 609

610

4.1.32 TemplateName 611

PWG PJT Mapping: TemplateName 612

JDF defines the JDF Node in section 3.2 of [CIP4JDF], which contains the TemplateID 613 attribute. 614

615

4.1.33 Trimming 616

PWG PJT Mapping: Trimming 617

JDF defines the CuttingParams element in section 8.36 “CuttingParams” of [CIP4JDF], 618 which contains the Cut element defined in section 10.12 “Cut” of [CIP4JDF], which 619 contains details of the requested cutting. 620

JDF defines the PerforatingParams element in section 8.101 “PerforatingParams” of 621 [CIP4JDF], which contains the Perforate element defined in section 10.28 “Perforate” of 622 [CIP4JDF], which contains the details of the requested perforating. 623

JDF defines the CreasingParams element in section 8.32 “CreasingParams” of [CIP4JDF], 624 which contains the Crease element defined in section 10.11 “Crease” of [CIP4JDF], which 625 contains the details of the requested creasing (i.e., scoring). 626

JDF defines the Trimming element in section 6.4.49 “Trimming” of [CIP4JDF], which 627 contains the TrimmingParams element defined in section 8.1.57 “TrimmingParams” of 628 [CIP4JDF], which contains the TrimmingType attribute (deprecated in JDF 1.2) with values 629 of ‘Detailed’ (use Height, Width, and TrimmingOffset values) and ‘SystemSpecified’ 630 (specified by System, but not exposed). 631

Note: Since the deprecated JDF TrimmingType attribute is not useful for determining the 632 equivalent value of PJT TrimmingType, the JDF Trimming element is not used in this 633 mapping specification. 634

4.1.34 TrimmingType 635

PWG PJT Mapping: TrimmingType 636



The value of the PJT TrimmingType element [PWG5100.1] can be inferred from the use of 637 the JDF Cutting, Perforating, or Creasing element and the details in the respective Cut, 638 Perforate, or Crease elements. The PJT TrimmingType element contains a keyword value 639 (Full, Partial, Perforate, Score, or Tab). The JDF Cut element maps to PJT TrimmingType 640 value of Full. The JDF Perforate element maps to PJT TrimmingType value of Perforate. 641 The JDF Crease element maps to PJT TrimmingType value of Score. There is no 642 reasonable mapping to PJT TrimmingType values of Partial or Tab. 643

4.1.35 XImage Layout 644

PWG PJT Mapping: XImagePosition, XImageShift, XSide1ImageShift, XSide2ImageShift 645

JDF defines the LayoutPreparationParams resource (from JDF/1.1) in section 8.86 of 646 [CIP4JDF], which contains the ImageShift element, which contains the PositionX, 647 ShiftFront, and ShiftBack attributes with simple mappings to the equivalent PJT XImage 648 layout elements – in this version of this JDFMAP, this is the recommended mapping for 649 XImage layout elements. If only JDF ShiftFront is used without a ShiftBack, then JDF 650 ShiftBack is calculated from ShiftFront so that the content remains aligned. To explicitly do 651 JDF ShiftBack of zero, you have to specify JDF ShiftBack. 652

Note: In the future, CIP4 may deprecate LayoutPreparationParams, in favor of the newer 653 and more general StrippingParams resource (from JDF/1.2) defined in section 8.146 of 654 [CIP4JDF], which contains the Position and BinderySignature elements. 655

Note: PWG image shift units are Integer 1/2540th inch (1/100 of a millimetre). JDF image 656 shift units are DoubleFloat 1/72 inch (points). Also JDF ShiftFront and ShiftBack are pair 657 of both X and Y values. 658

The JDF PositionX attribute is a keyword (None, Center, Left, Right, or Spline), while the 659 equivalent PJT XImagePosition element is a keyword (None, Center, Left, or Right), so 660 there is no mapping for the JDF ‘Spline’ value. 661

The JDF LayoutPreparationParams resource (from JDF/1.1) in section 8.86 of [CIP4JDF] 662 also contains the ExternalImpositionTemplate element, which contains the FileSpec 663 element, which contains the UserFileName attribute (user-friendly file name), which can be 664 mapped to the PJT ImpositionTemplate element (keyword of ‘None’ or ‘Signature’ or site-665 specific name) defined in [PWG5100.3]. The PJT ImpositionTemplate element interacts in 666 an implementation-specific manner with the PJT NumberUp element and PJT XImage and 667 YImage layout elements. 668

669

The JDF Position element contains the MarginBottom, MarginLeft, MarginRight, and 670 MarginTop attributes (margins in points outside of the BinderySignature) and the 671 AbsoluteBox attribute (absolute position in points of the BinderySignature display area). 672

JDF defines the BinderySignature element (a conceptual folding dummy) in section 8.7 of 673 [CIP4JDF], which contains the TrimBottom, TrimLeft, TrimRight, and TrimTop attributes 674

Moved (insertion) [1]

Moved up [1]: Note: In the future, CIP4 may 675 deprecate LayoutPreparationParams, in favor of 676 the newer and more general StrippingParams 677 resource (from JDF/1.2) defined in section 678 8.146 of [CIP4JDF], which contains the Position 679 and BinderySignature elements. ¶680



(cutoff margin widths around the sides of the BinderySignature – the remainder contains 681 the Strips). 682 The JDF BinderySignature element also contains the NumberUp attribute (pair of integers, 683 columns and rows) that interacts with the PJT NumberUp element (single integer product 684 of columns and rows). See the discussion of JDF and PJT page layout in the section 685 4.1.23 NumberUp above. 686

4.1.36 YImage Layout 687

PWG PJT Mapping: YImagePosition, YImageShift, YSide1ImageShift, YSide2ImageShift 688

JDF defines the LayoutPreparationParams resource (from JDF/1.1) in section 8.86 of 689 [CIP4JDF], which contains the ImageShift element, which contains the PositionY, 690 ShiftFront, and ShiftBack attributes with simple mappings to the equivalent PJT YImage 691 layout elements – in this version of this JDFMAP, this is the recommended mapping for 692 YImage layout elements. If only JDF ShiftFront is used without a ShiftBack, then JDF 693 ShiftBack is calculated from ShiftFront so that the content remains aligned. To explicitly do 694 JDF ShiftBack of zero, you have to specify JDF ShiftBack. 695

Note: In the future, CIP4 may deprecate LayoutPreparationParams, in favor of the newer 696 and more general StrippingParams resource (from JDF/1.2) defined in section 8.146 of 697 [CIP4JDF], which contains the Position and BinderySignature elements. See the 698 discussion of the StrippingParams resource and Position and BinderySignature elements 699 in section 4.1.35 XImage Layout above. 700

Note: PWG image shift units are Integer 1/2540th inch (1/100 of a millimetre). JDF image 701 shift units are DoubleFloat 1/72 inch (points). Also JDF ShiftFront and ShiftBack are pair 702 of both X and Y values. 703

The JDF PositionY attribute is a keyword (None, Center, Left, Right, or Spline), while the 704 equivalent PJT YImagePosition element is a keyword (None, Center, Left, or Right), so 705 there is no mapping for the JDF ‘Spline’ value. 706

707

708

Deleted: s709

Deleted: section710

Deleted: The JDF BinderySignature element 711 also contains the NumberUp attribute¶712

Moved (insertion) [2]

Deleted: the713

Deleted: section714

Moved up [2]: Note: In the future, CIP4 may 715 deprecate LayoutPreparationParams, in favor of 716 the newer and more general StrippingParams 717 resource (from JDF/1.2) defined in section 718 8.146 of [CIP4JDF], which contains the Position 719 and BinderySignature elements. See the 720 discussion of the StrippingParams resource and 721 Position and BinderySignature elements in the 722 XImage Layout section above.¶723



4.2 Mappings of JDF to PJT Binding Types 724

JDF defines various binding classes in section 6.4 Postpress Binding and of [CIP4JDF] 725 and also defines the binding resource in section 7.5 “BindingIntent” of [CIP4JDF]. 726

Notes for Table 3 and Table 4: 727

1) JDF Postpress WireCombBinding and JDF BindingIntent/@BindingType value of 728 WireComb can be mapped to the *new* PWG PJT value of WireComb, while JDF 729 Postpress PlasticCombBinding and and JDF BindingIntent/@BindingType value of 730 can be mapped to PWG PJT value of Comb, because the PWG PJT value Comb is 731 defined as specifically plastic comb binding. 732

2) JDF BindingIntent/@BindingType value of Adhesive is deprecated in JDF 1.1 – use 733 JDF SoftCover or HardCover instead – JDF BindingIntent/@BindingType value of 734 SoftCover includes Perfect binding – JDF PWG PJT mapping is still Adhesive??? 735

3) JDF BindingIntent/@BindingType values of CornerStitch, SaddleStitch, Sewn 736 (deprecated in JDF/1.4), SideSewn (deprecated in JDF/1.4), and SideStitch 737 SHOULD be mapped to PWG PJT Stitch. 738

4) JDF BindingIntent/@BindingType value of ThreadSealing (deprecated in JDF/1.4) 739 of sewing signatures at the spine and also well as Sewn (deprecated in JDF/1.4), 740 SideSewn SideSewn (deprecated in JDF/1.4), and SideStitch SHOULD be mapped 741 to PWG PJT Stitch. 742

5) JDF Postpress EndSheetGlueing applies to hard cover binding and differs from 743 PWG PJT value Adhesive (which only applies the glue but does not apply the hard 744 cover). 745

6) JDF BindingIntent/@BindingType value of None can be mapped to PWG PJT by 746 explicitly omitting the PJT BindingType element 747

7) JDF PostPress RingBinding and JDF BindingIntent/@BindingType value of Ring 748 define both the punching of holes for a 2/3-ring binder and the application of the 749 actual 2/3-ring binder – use PJT Punching to punch the appropriate holes, but PJT 750 does not support applying the actual 2/3-ring binder. 751

752

Deleted: Mappings753

Deleted: ’t754

Deleted: JDF 755

Deleted: 756

Deleted: has no PWG PJT mapping757



Table 3 – Mapping of CIP4 JDF Postpress Binding Class to PWG PJT BindingType 758

CIP4 JDF Postpress Binding Class PWG PJT BindingType

AdhesiveBinding Adhesive (note 5)

ChannelBinding <none>

CoilBinding Spiral

EndSheetGlueing <none> (note 5)

LongitudinalRibbonOperations <none>

PlasticCombBinding Comb (note 1)

RingBinding <none> (note 7)

SpineTaping Tape

StripBinding Velo

WireCombBinding WireComb (note 1)

759

760

Deleted: ¶761

Formatted Table

Deleted: ?762

Deleted: (note 1)763

Deleted: <none>764



Table 4 – Mapping of CIP4 JDF BindingIntent/@BindingType to PWG PJT BindingType 765

CIP4 JDF BindingIntent/@BindingType PWG PJT BindingType

AdhesiveBinding Adhesive (note 2)

ChannelBinding <none>

CoilBinding Spiral

CornerStitch <none> (note 3)

EdgeGlueing Padding

HardCover <none> (note 2)

None <no BindingType element> (note 6)

PlasticComb Comb

Ring <none> (note 7)

SaddleStitch <none> (note 3)

Sewn <none> (note 3)

SideSewn <none> (note 3)

SideStitch <none> (note 3)

SoftCover Perfect (note 2)

StripBind Velo

Tape Tape

ThreadSealing <none> (note 4)

WireComb <none> (note 1)

766

Deleted: ¶767

Formatted Table




Deleted: Adhesive771

Deleted: ne772






Deleted: ?778





4.3 JDF RunList Resources 781

JDF defines the RunList resource in section 8.125 “RunList” of [CIP4JDF] (a Process 782 resource), which is the primary JDF means of controlling processing and finishing 783 execution and sequencing. 784

RunList resources describe an ordered set of LayoutElement or ByteMap elements. 785 Ordering and structure are defined using the generic Partitioning mechanisms as 786 described in JDF section 3.11.5 “Description of Partitioned Resources” [CIP4JDF]. 787

RunList resources are used whenever an ordered set of page descriptions elements are 788 specified. Depending on the Process usage of a RunList, only certain types of 789 LayoutElement MAY be valid. 790

In essence, a RunList is a virtual document or set of documents. It allows a document to 791 either be physically spread over multiple files, or multiple documents to be contained within 792 a single file (e.g., PPML, PDF/VT). It retains the same properties as the original 793 documents (e.g., the pages of a document that is described by a RunList are ordered). 794

ISSUE: Get Rainer’s help to write more about Partitioning Resources and tie back to PJT 795 Overrides. 796

4.4 JDF Partitioning Resources 797

JDF defines Partitioned resources in section 3.11.5 “Description of Partitioned Resources” 798 of [CIP4JDF]. 799

Printing workflows contain a number of Processes that are repeated over a potentially 800 large number of individual files, Sheets, surfaces or separations. In order to define a 801 Partitioned Resource in a concise manner without having to create a large number of 802 individual Nodes and Resources, a set of Resources might be Partitioned by factoring 803 them by one or more attributes. The common elements and defaults are placed in the 804 parent element while Partition-specific attributes and overrides are placed in the child 805 elements. This saves space. Also, by providing a single parent ID for the Resources, it 806 allows easy access to the entire Resource or iteration over each Part. 807

To reference part of a Resource, a ResourceLink references the parent Resource and 808 supplies a Part element that contains an actual value for a Partition. The result is all the 809 child Elements with matching Partition values, including common values and defaults from 810 the parent Resource. If @PartUsage = "Implicit", the parent Attributes are returned if there 811 is no matching Partition. 812

ISSUE: Get Rainer’s help to write more about Partitioning Resources and tie back to PJT 813 Overrides. 814



4.5 Mapping JDF Job State Model to PWG Job State Model 815

JDF defines the NodeInfo element in section 8.91 “NodeInfo” of [CIP4JDF], which contains 816 the NodeStatus attribute. PWG Semantic Model [REF] defines the JobState element. 817

This mapping of JDF Job states is actually for the JMF Job states (in progress jobs) and 818 the corresponding mapping of PWG Job states is actually for the PWG JobReceipt 819 (results, not submission states). The PWG Client does not control Job state – instead the 820 Spooler/Printer does so. 821

Notes: 822

1) JDF NodeStatus of Aborted may map to either PJT Aborted or Canceled (the 823 distinction is between system Abort and operator Cancel is not preserved in JDF). 824

2) JDF NodeStatus of Cleanup is ephemeral and SHOULD be mapped to PJT 825 Completed. 826

3) JDF NodeStatus of Setup (holding for Operator setup/load/preparation) SHOULD 827 be mapped to PJT PendingHeld. 828

4) JDF NodeStatus of Stopped and Suspended SHOULD be mapped to PJT 829 ProcessingStopped. 830

5) JDF NodeStatus of Waiting SHOULD be mapped to PJT Pending. 831 832

Deleted: about833

Deleted: c834



Table 5 – Mapping of CIP4 JDF Node Status to PWG SM Job States 835

JDF NodeStatus PWG JobState PWG JobStateReasons

Aborted Aborted or Canceled (note 1) AbortedBySystem, UnsupportedCompression, CompressionError, UnsupportedDocumentFormat, JobCanceledByUser, or JobCanceledByOperator and (ephemeral) ProcessingToStopPoint

Cleanup Completed (note 2)

Completed Completed JobCompletedSuccessfully, JobCompletedWithWarnings, or JobCompletedWithErrors, DocumentAccessError, QueuedInDevice

InProgress Processing JobQueued, JobInterpreting, JobTransforming, JobQueuedForMarker, JobPrinting

Ready Pending

Setup PendingHeld (note 3) JobHoldUntilSpecified, ResourcesAreNotReady, JobQueuedForMarker, ServiceOffline

Stopped ProcessingStopped PrinterStopped, PrinterStoppedPartly

Suspended ProcessingStopped (note 4)

Waiting Pending (note 5) JobDataInsufficient, JobIncoming

836

Deleted: ¶837

Formatted Table

Deleted: n838

Deleted: n839

Deleted: n840

Deleted: n841

Deleted: n842



5. Conformance Requirements 843

5.1 Print Server Conformance 844

Conforming Print Servers that implement this specification MUST: 845

1) Conform to the all of the element mappings defined in section 4.1 Mapping JDF 846 Attributes to PWG Print Job Ticket Elements; 847

2) Conform to all of the state mappings defined in section 4.2 Mapping JDF State 848 Model to PWG Printer State Model; 849

3) Conform to section 6 Internationalization Considerations; 850

4) Conform to section 7 Security Considerations. 851

5.2 Print Device Conformance 852

Conforming Print Devices that implement this specification MUST: 853

1) Conform to the all of the element mappings defined in section 4.1 Mapping JDF 854 Attributes to PWG Print Job Ticket Elements; 855

2) Conform to all of the state mappings defined in section 4.2 Mapping JDF State 856 Model to PWG Printer State Model; 857

3) Conform to section 6 Internationalization Considerations; 858

4) Conform to section 7 Security Considerations. 859

860



6. Internationalization Considerations 861

For interoperability and basic support for multiple languages, conforming implementations 862 MUST support the Universal Character Set (UCS) Transformation Format -- 8 bit (UTF-8) 863 [RFC3629] encoding of Unicode [UNICODE] [ISO10646] and the Unicode Format for 864 Network Interchange [RFC5198]. 865

When processing human names that are being concatenated from multiple CIP4 JDF 866 attributes (e.g., JDF “CustomerInfo/Contact/Person” object attributes such as FirstName, 867 FamilyName, JobTitle, NamePrefix, and NameSuffix) into a PWG PJT single human-868 readable string attribute (e.g., JobRecipientName), the correct layout order for these 869 components of human names is locale-dependent. 870

For more information on locale-dependent processing, see ICU User Guide/Software 871 Internationalization [ICU-SWI18N]. 872

Implementations of this specification SHOULD conform to the following standards on 873 processing of human-readable Unicode text strings, see: 874

Unicode Bidirectional Algorithm [UAX9] – left-to-right, right-to-left, and vertical 875

Unicode Line Breaking Algorithm [UAX14] – character classes and wrapping 876

Unicode Normalization Forms [UAX15] – especially NFC for [RFC 5198] 877

Unicode Text Segmentation [UAX29] – grapheme clusters, words, sentences 878

Unicode Identifier and Pattern Syntax [UAX31] – identifier use and normalization 879

Unicode Collation Algorithm [UTS10] – sorting 880

Unicode Locale Data Markup Language [UTS35] – locale databases 881

Implementations of this specification are advised to also review the following informational 882 documents on processing of human-readable Unicode text strings: 883

Unicode Character Encoding Model [UTR17] – multi-layer character model 884

Unicode in XML and other Markup Languages [UTR20] – XML usage 885

Unicode Character Property Model [UTR23] – character properties 886

Unicode Conformance Model [UTR33] – Unicode conformance basis 887

888

Deleted: +889



7. Security Considerations 890

Implementations of this specification MUST conform to all security requirements specified 891 in section 8 Security Considerations of IPP/1.1 Model and Semantics [RFC2911] and in 892 section 10 Security Considerations of IPP/2.0 Second Edition [PWG5100.12]. 893

Implementations of this specification SHOULD conform to the following standard on 894 processing of human-readable Unicode text strings, see: 895

Unicode Security Mechanisms [UTS39] – detecting and avoiding security attacks 896

Implementations of this specification are advised to also review the following informational 897 document on processing of human-readable Unicode text strings: 898

Unicode Security FAQ [UNISECFAQ] – common Unicode security issues 899

900

8. IANA and PWG Considerations 901

There are no IANA or PWG registration considerations for this document. 902

903



9. References 904

9.1 Normative References 905

[CIP4JDF] CIP4, "JDF Specification Release 1.5, December 2013, 906 http://www.cip4.org 907

[CIP4IDP] CIP4, "Integrated Digital Printing (IDP) ICS Version 1.3 Errata 908 Revision A”, February 2009, http://www.cip4.org 909

[ISO10646] ISO, "Information technology -- Universal Coded Character Set 910 (UCS)", ISO/IEC 10646:2012, 2012, 911 http://www.iso.org/iso/home/store/catalogue_ics.htm 912

[PWG5100.1] M. Sweet, “IPP Finishings 2.0 (FIN)”, PWG 5100.1, December 2014, 913 ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippfinishings20-20141219-914 5100.1.pdf 915

[PWG5100.3] T. Hastings, K. Ocke, “Internet Printing Protocol (IPP): Production 916 Printing Attributes – Set1”, PWG 5100.3, February 2001, 917 ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippprodprint10-20010212-918 5100.3.pdf 919

[PWG5100.12] R. Bergman, H. Lewis, I. McDonald, M. Sweet, "Internet Printing 920 Protocol Version 2.0 Second Edition (IPP/2.0 SE)", PWG 5100.12, 921 February 2011, 922 ftp://ftp.pwg.org/pub/pwg/candidates/cs-ipp20-20110214-5100.12.pdf 923

[PWG5100.13] I. McDonald, M. Sweet, P. Zehler, “IPP Job and Printer Extensions – 924 Set 3 (JPS3)”, July 2012, 925 ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext3v10-926 20120727-5100.13.pdf 927

[PWG5100.14] J. Hutchings, I. McDonald, A. Mitchell, M. Sweet, "IPP Everywhere", 928 PWG 5100.14, January 2013, 929 ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippeve10-20130128-930 5100.14.pdf 931

[PWG5101.1] R. Bergman, T. Hastings, M. Sweet, “PWG Media Standardized 932 Names 2.0 (MSN2)”, PWG 5101.1, March 2013, 933 ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn20-20130328-934 5101.1.pdf 935

[PWG5108.07] P. Zehler, “PWG Print Job Ticket and Associated Capabilities v1.0 936 (PJT)”, PWG 5108.7, 937 ftp://ftp.pwg.org/pub/pwg/candidates/cs-sm20-pjt10-20120801-938 5108.07.pdf 939

ftp://ftp.pwg.org/pub/pwg/candidates/cs-ipp20-20110214-5100.12.pdf


http://www.iso.org/iso/home/store/catalogue_ics.htm

ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippprodprint10-20010212-5100.3.pdf





ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext3v10-20120727-5100.13.pdf

ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext3v10-20120727-5100.13.pdf



ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn20-20130328-5101.1.pdf

ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn20-20130328-5101.1.pdf





[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate Requirement 940 Levels", RFC 2119/BCP 14, March 1997, 941 http://www.ietf.org/rfc/rfc2119.txt 942

[RFC2911] T. Hastings, R. Herriot, R. deBry, S. Isaacson, P. Powell, "Internet 943 Printing Protocol/1.1: Model and Semantics", RFC 2911, September 944 2000, 945 http://www.ietf.org/rfc/rfc2911.txt 946

[RFC3805] R. Bergman, H. Lewis, I. McDonald, "Printer MIB v2", RFC 3805, June 947 2004, 948 http://www.ietf.org/rfc/rfc3805.txt 949

[RFC3806] R. Bergman, H. Lewis, I. McDonald, "Printer Finishing MIB", RFC 950 3806, June 2004, 951 http://www.ietf.org/rfc/rfc3806.txt 952

[RFC4122] P. Leach, M. Mealling, R. Salz, “A Universally Unique IDentifier 953 (UUID) URN Namespace”, RFC 4122, July 2005, 954 http://www.ietf.org/rfc/rfc4122.txt 955

[RFC5646] A. Phillips, M. Davis, “Tags for Identifying Languages”, RFC 5646 / 956 BCP 47, September 2009, 957 http://www.ietf.org/rfc/rfc5646.txt 958

[STD63] F. Yergeau, "UTF-8, a transformation format of ISO 10646", RFC 959 3629/STD 63, November 2003, 960 http://www.ietf.org/rfc/rfc3629.txt 961

[UAX9] Unicode Consortium, “Unicode Bidirectional Algorithm”, UAX#9, June 962 2014, 963 http://www.unicode.org/reports/tr9/tr9-31.html 964

[UAX14] Unicode Consortium, “Unicode Line Breaking Algorithm”, UAX#14, 965 June 2014, 966 http://www.unicode.org/reports/tr14/tr14-33.html 967

[UAX15] Unicode Consortium, “Normalization Forms”, UAX#15, June 2014, 968 http://www.unicode.org/reports/tr15/tr15-41.html 969

[UAX29] Unicode Consortium, “Unicode Text Segmentation”, UAX#29, June 970 2014, 971 http://www.unicode.org/reports/tr29/tr29-25.html 972

[UAX31] Unicode Consortium, “Unicode Identifier and Pattern Syntax”, 973 UAX#31, June 2014, 974 http://www.unicode.org/reports/tr31/tr31-21.html 975

http://www.ietf.org/rfc/rfc2119.txt







http://www.unicode.org/reports/tr9/tr9-31.html







[UNICODE] Unicode Consortium, "Unicode Standard", Version 7.0.0, June 2014, 976 http://www.unicode.org/versions/Unicode7.0.0/ 977

[UTS10] Unicode Consortium, “Unicode Collation Algorithm”, UTS#10, June 978 2014, 979 http://www.unicode.org/reports/tr10/tr10-30.html, 980

[UTS35] Unicode Consortium, “Unicode Locale Data Markup Language”, 981 UTS#35, September 2014, 982 http://www.unicode.org/reports/tr35/tr35-37/tr35.html 983

[UTS39] Unicode Consortium, “Unicode Security Mechanisms”, UTS#39, 984 September 2014, 985 http://www.unicode.org/reports/tr39/tr39-9.html 986

987

9.2 Informative References 988

[RFC5226] T. Narten, H. Alvestrand, "Guidelines for Writing an IANA 989 Considerations Section in RFCs", RFC 5226 / BCP 26, May 2008, 990 http://www.ietf.org/rfc/rfc5226.txt 991

[UTR17] Unicode Consortium “Unicode Character Encoding Model”, UTR#17, 992 November 2008, 993 http://www.unicode.org/reports/tr17/tr17-7.html 994

[UTR20] Unicode Consortium “Unicode in XML and other Markup Languages”, 995 UTR#20, January 2013, 996 http://www.unicode.org/reports/tr20/tr20-9.html 997

[UTR23] Unicode Consortium “Unicode Character Property Model”, UTR#23, 998 November 2008, 999 http://www.unicode.org/reports/tr23/tr23-9.html 1000

[UTR33] Unicode Consortium “Unicode Conformance Model”, UTR#33, 1001 November 2008, 1002 http://www.unicode.org/reports/tr33/tr33-5.html 1003

[UNISECFAQ] Unicode Consortium “Unicode Security FAQ”, November 2013, 1004 http://www.unicode.org/faq/security.html 1005

1006

1007

http://www.unicode.org/versions/Unicode7.0.0/

http://www.unicode.org/reports/tr35/tr35-37/tr35.html







http://www.unicode.org/faq/security.html



10. Authors’ Addresses 1008

Ira McDonald 1009 High North 1010 PO Box 221 1011 Grand Marais, MI 49839 1012 906-494-2434 1013 [email protected] 1014

Rick Yardumian 1015 Canon Information & Imaging Solutions, Inc 1016 15975 Alton Parkway 1017 Irvine, CA 92618 1018 [email protected] 1019

The authors would especially like to thank Rainer Prosi (Heidelberg, CIP4 CTO) for his 1020 extensive and thorough contributions to this document. 1021

The authors would also like to thank the following individuals for their contributions to this 1022 document: 1023

Michael Sweet Apple 1024

Daniel Manchala Xerox 1025

Paul Tykodi TCS 1026

William Wagner TIC 1027

Pete Zehler Xerox 1028

mailto:[email protected]



11. Change History 1029

11.1 17 May 2015 – JDFMAP update by SM WG and Rainer Prosi 1030

* May 2015 – draft in SM WG – from 04/29/15 review in PWG F2F 1031 - Changed status to Prototype draft, per PWG F2F review 1032 - Global – added gray shading to all table headers for clarity 1033 - Revised section 3.1 Rationale, section 3.3 Out-of-Scope, section 3.4 Design 1034 Requirments, and section 4.1 Mapping JDF to correct formatting of numbered bullets 1035 - Revised Table 1 to add “or” between CuttingParams, PerforatingParams, and 1036 CreasingParams 1037 - Revised sections 4.1.1 and 4.1.2 to add missing “:” 1038 - Revised section 4.1.12 to add missing “an” 1039 - Revised section 4.1.24 to add forward reference to new section 4.3 JDF RunList 1040 Resources 1041 - Revised section 4.1.25 to add forward reference to new section 4.4 JDF Partioning 1042 Resources 1043 - Revised section 4.1.29 and Table 2 to add notes about white point compensation and 1044 black point compensation with reference to IPP JPS3 (PWG 5100.13) 1045 - Revised section 4.1.33 to break out last sentence of last paragraph into separate “Note:” 1046 paragraph as an implementor warning 1047 - Revised section 4.1.35 to reorder notes, change “cuttings margins” to “cutting margins”, 1048 add cross-reference to section 4.1.23 NumberUp, and delete dangling final partial 1049 sentence 1050 - Revised section 4.1.36 to reorder notes and add cross-reference to section 4.1.35 1051 XImage Layout 1052 - Revised section 4.2 Mappings of JDF to PJT Binding Types, Table 3, and Table 4 to 1053 move all notes to right column (PJT), expand note 4, add note 5, add note 6, add note 7, 1054 delete mapping of HardCover to Adhesive, accept mapping of StripBinding to Velo, and 1055 add mapping of WireCombBinding/WireComb to *new* PJT value of WireComb (to be 1056 added in IPP and SM 3.0) 1057 - Added new section 4.3 JDF RunList Resources – needs more content 1058 - Added new section 4.4 JDF Partioning Resources – needs more content 1059 - Revised section 4.5 Mapping JDF Job State to clarify that this mapping is wholly 1060 concerned with JMF (in progress jobs) and PWG JobReceipt (results) 1061 - Revised section 4.5 Mapping JDF Job State Table 5 to combine PJT rows for Aborted 1062 and Canceled rows, add column for JobStateReasons, and clarify in note 3 that JDF Setup 1063 is Operator hold for setup/load/preparation 1064 - Revised section 6 Internationalization Considerations to remove trailing “+” in list 1065 - Revised section 9.1 Normative References to add IPP JPS3 (PWG 5100.13) 1066 - TODO – Section 4.1.x miscellaneous cleanup 1067 - TODO – tie up looses ends for PJT Overrides and JDF RunList and Partitioning 1068 Resources 1069



11.2 24 April 2015 – JDFMAP update by SM WG and Rainer Prosi 1070

* April 2015 – draft in SM WG – from 03/30/15 review 1071 - Kept status as Interim draft 1072 - Reviewed and accepted all changes in mapping table and sections 4.1.x 1073 - Revised Binding and added BindingType in sections 4.1.x 1074 - Added ImpositionTemplate and OverridingElements in sections 4.1.x – open issues 1075 remain 1076 - Revised TemplateInfo and TemplateName in sections 4.1.x 1077 - Added XImage Layout and YImageLayout in sections 4.1.x with discussions of original 1078 LayoutPreparationParams and newer StrippingParams and BinderySignature mappings 1079 - Added section 4.2 with notes and two tables for JDF Postpress Process and JDF 1080 BindingIntent@BindingType mappings – open issues remain 1081 - Revised section 4.3 and added notes to state mapping 1082 - Revised sections 6 and 7 Internationalization and Security Considerations to correct for 1083 Informative (rather than Normative) Unicode UTR and FAQ documents 1084 - TODO – Section 4.1.x miscellaneous cleanup 1085 - TODO – Prototype draft for August 2015 PWG F2F 1086

11.3 28 March 2015 – JDFMAP update by SM WG and Rainer Prosi 1087

* March 2015 – draft in SM WG – from 03/09/15 review 1088 - Kept status as Interim draft 1089 - Reviewed and accepted all changes in mapping table 1090 - Revised MediaSizeName and Trimming in mapping table 1091 - Revised JobUuid, Trimming, and TrimmingType in sections 4.1.x 1092 - Updated section 9 References for several IETF and PWG specs 1093 - TODO – Section 4.1.x keyword mapping tables, Bindings, Layout, Conformance, Security 1094 Considerations, I18N Considerations, miscellaneous cleanup 1095 - TODO – Prototype draft for April/May 2015 PWG F2F 1096

11.4 9 March 2015 – JDFMAP update by SM WG and Rainer Prosi 1097

* March 2015 – draft in SM WG – from 02/04/15 F2F and 02/16/15 reviews 1098 - Kept status as Interim draft 1099 - Reviewed and accepted all changes in mapping table 1100 - Revised Trimming and Trimming Type in mapping table 1101 - Added JobUuid, PrintRenderingIntent, ProofPrint, MediaRecycled, MediaSize, 1102 MediaSizeName, Trimming, TrimmingType in sections 4.1.x 1103 - Updated section 9.1 Normative References for several PWG specs 1104 - TODO – Section 4.1.x keyword mapping tables, Bindings, Layout, Conformance, Security 1105 Considerations, I18N Considerations, miscellaneous cleanup 1106 - TODO – Prototype draft for April/May 2015 PWG F2F 1107



11.5 15 February 2015 – JDFMAP update by SM WG and Rainer Prosi 1108

* February 2015 – draft in SM WG – from 01/19/15 and 02/04/15 F2F reviews 1109 - Kept status as Interim draft 1110 - Reviewed and accepted all changes in mapping table 1111 - Updated section 6 Internationalization Considerations, section 7 Security Considerations, 1112 and section 9 References for Unicode 7.0, UAX#9, UAX#14, UAX#15, UAX#29, UAX#31, 1113 UTS#10, UTS#35, UTS#39, UTR#17, UTR#20, UTR#23, UTR#33, and Unicode Security 1114 FAQ 1115 - TODO – Section 4.1.x keyword mapping tables, Bindings, Layout, Conformance, Security 1116 Considerations, I18N Considerations, miscellaneous cleanup 1117 - TODO – Prototype draft for April/May 2015 PWG F2F 1118

11.6 19 January 2015 – JDFMAP update by SM WG and Rainer Prosi 1119

* January 2015 – draft in SM WG – from 01/19/15 review 1120 - Kept status as Interim draft 1121 - Reviewed and accepted all changes in mapping table 1122 - Reviewed and accepted ImageShift (although newer non-JDF/1.1 mappings needed) 1123 - Completed mapping table, except for Bindings and Trimming mappings 1124 - Added empty section 4.2 for Bindings mappings 1125 - Resume next review in sections 4.1.x 1126 - Confirmed dates for February special calls (02/09 & 02/16) 1127 - TODO – Section 4.1.x keyword mapping tables, Bindings, Layout, Conformance, Security 1128 Considerations, I18N Considerations, miscellaneous cleanup 1129 - TODO – Prototype draft for February 2015 PWG F2F and PWG Last Call for April/May 1130 PWG F2F 1131

11.7 12 January 2015 – JDFMAP update by SM WG and Rainer Prosi 1132

* January 2015 – draft in SM WG – from 01/12/15 review 1133 - Kept status as Interim draft 1134 - Reviewed and accepted all changes in mapping table 1135 - Deleted redundant PJT Feed (sub-element of PJT Resolution) from mapping table 1136 - Reviewed and specified PJT Overrides mapping – still need to add JDF and PJT 1137 equivalent examples for clarity) 1138 - Reviewed and accepted/revised all sections 4.1.x changes from December 2014 1139 - Discussed RenderingIntent in 4.1.x – still need to add keyword mapping table 1140 - Resume next review at ImageShift in mapping table and 4.1.x 1141 - Discussed dates for February special calls (02/09 & 02/16) 1142 TODO – Prototype draft for February 2015 PWG F2F and PWG Last Call for April/May 1143 PWG F2F 1144



11.8 15 December 2014 – JDFMAP update by SM WG and Rainer Prosi 1145

* December 2014 – draft in SM WG – from 12/15/14 review 1146 - Kept status as Interim draft 1147 - Reviewed and accepted/revised all sections 4.1.x through 4.1.21 Print RenderingIntent 1148 - Added notes to applicable sections 4.1.x about mapping of JDF negative range values 1149 - Reviewed and accepted/revised section 4.2 Job State mapping (though this only applies 1150 to JobReceipt (i.e., Job processing results) 1151 - Resume next review at Overrides in mapping table 1152 - Discussed dates for January special calls (01/12 & 01/19) 1153 - Discussed dates for milestones – Prototype draft for February 2015 PWG F2F and PWG 1154 Last Call for April/May PWG F2F 1155 - TODO – CLOSED –Abandoned plan for sections 4.1.x keyword mapping tables – they 1156 are either trivial or implementation-dependent 1157 - TODO – CLOSED –Abandoned plan for section 4.3 Printer State mapping table (out-of-1158 scope for JobTicket/JobReceipt) 1159


* December 2014 – draft in SM WG – from 12/08/14 review 1161 - Kept status as Interim draft 1162 - Restored bullets and numbering destroyed by MS Word in previous draft 1163 - Discussed sections to be reviewed for next week (12/15) 1164 - Discussed dates for January special calls (01/12 & 01/19) 1165 - Resume next review at Overrides in mapping table 1166 - TODO – add JDF to PWG keyword mapping tables in sections 4.1.x 1167 - TODO – add JDF to PWG Device/Printer state mapping table in section 4.2 1168


* December 2014 – draft in SM WG – from 11/10/14 review 1170 - Kept status as Interim draft 1171 - Continued review at section 4.1.x JobFinishings and JobFinishingsCol 1172 - Revised all JDF attributes in table to be in italics (per JDF typographic conventions) 1173 - Reviewed and accepted verified changes as appropriate 1174 - Reviewed and deleted comments as appropriate (when processed in mappings) 1175 - Added sections 4.1.x for all remaining bold PJT attributes 1176 - Added sections 4.1.x mappings for most remaining bold PJT attributes 1177 - Rechecked, corrected, and added JDF/1.5 section numbers throughout sections 4.1.x 1178 - Added Job state mapping table to section 4.2 1179 - Completed review through section 4.1.x PageRanges 1180 - Resume next review at Overrides in mapping table 1181 - TODO – add JDF to PWG keyword mapping tables in sections 4.1.x 1182 - TODO – add JDF to PWG Device/Printer state mapping table in section 4.2 1183



11.11 31 October 2014 – JDFMAP update by SM WG and Rainer Prosi 1184

* October 2014 – eleventh draft in SM WG – from 10/27/14 review 1185 - Kept status as Interim draft 1186 - Continued review at section 4.1 (detailed mappings) – stopped at InsertSheet 1187 - Reviewed and accepted verified changes as appropriate 1188 - Reviewed and deleted comments as appropriate (when processed in mappings) 1189 - Reviewed and deleted comments as appropriate (when moved to details) 1190 - Deleted weak JDF mapping for PWG [Job]CoverBack and [Job] CoverFront, which 1191 depended on JDF elements defined in JDF 1.0 and deprecated in JDF 1.1 1192 - Added and expanded some sections 4.1.x (detailed mappings) 1193 - Resume next review at section 4.1.x JobFinishings and JobFinishingsCol 1194

11.12 5 October 2014 – JDFMAP update by SM WG and Rainer Prosi 1195

* October 2014 – tenth draft in SM WG – from 09/22/14 review 1196 - Kept status as Interim draft 1197 - Changed font of Table 1 to TimesNewRoman (serif) per request of Rainer Prosi (sans 1198 serif fonts made some lowercase and uppercase letters ambiguous – breaking mapping) 1199 - Continued review of mapping table – completed first complete pass through table 1200 - Reviewed and accepted verified changes as appropriate 1201 - Reviewed and deleted comments as appropriate (when processed in mappings) 1202 - Reviewed and deleted comments as appropriate (when moved to details) 1203 - Added and expanded some sections 4.1.x (detailed mappings) 1204 - Resume next review at section 4.1 1205

11.13 16 September 2014 – JDFMAP update by SM WG and Rainer Prosi 1206

* September 2014 – ninth draft in SM WG 1207 - Kept status as Interim draft 1208 - Reviewed and accepted changes to Abstract and Introduction 1209 - Numbered section 3.3 Out-of-scope and section 3.4 Design Requirements lists 1210 - Continued review of mapping table – stopped at TemplateType 1211 - Reviewed and added comments to PresentationDirectionNumberUp, PrintColorMode, 1212 PrintContentOptimize, PrintRenderingIntent, ProofPrint.Media, and ProofPrint.MediaCol 1213 - Added updates and deleted old comments in sections 4.1.x (detailed mappings) 1214 - Resume next review at XImagePosition 1215

11.14 8 September 2014 – JDFMAP update by SM WG and Rainer Prosi 1216

* September 2014 – eighth draft in SM WG 1217 - Kept status as Interim draft 1218 - Continued review of mapping table – stopped at PdlInitFiles 1219 - Discussed and added comments to PageRanges, PagesPerSubset, and PdlInitFiles 1220 - Reviewed and accepted verified changes as appropriate 1221



- Resorted and accepted sections 4.1.x in PJT attribute order (right column of table) 1222 - Resume next review at PresentationDirectionNumberUp 1223

11.15 28 August 2014 – JDFMAP update by SM WG and Rainer Prosi 1224

* August 2014 – seventh draft in SM WG 1225 - Kept status as Interim draft 1226 - Revised Abstract and section 1 Introduction to correctly refer to XML objects and 1227 attributes in JDF being mapped to XML elements in PJT 1228 - Revised boilerplate to change “IDS” to “SM” and correct link to SM WG per Paul Tykodi 1229 - Revised section 3.2.1 to correct spelling of “Print Job” per Paul Tykodi 1230 - Revised section 4.1.1 title to refer to PJT CompressionSupplied 1231 - Revised section 4.1.2 title to refer to PJT CoverXxx 1232 - Revised section 4.1.4 title to refer to PJT DocumentNumbers 1233 - Revised section 4.1.5 title to refer to PJT DocumentFormatDetailsSupplied 1234 - Moved former section 4.1.8 on LayoutPreparationParams to Notes under table 1235 - Revised section 4.1.9 title to refer to PJT DocumentFormat 1236 - Revised section 4.1.10 title to refer to PJT DocumentFormat (w/ Charset) 1237 - Revised section 4.1.12 title to refer to PJT DocumentPassword 1238 - Revised section 4.1.13 title to refer to PJT Overrides 1239 - Revised section 4.1.14 title to refer to PJT InsertSheet 1240 - Revised section 4.1.15 title to refer to PJT PageRanges 1241 - Revised section 4.1.16 title to refer to PJT InsertCount 1242 - Continued review of mapping table – stopped at PageOrderReceived 1243 - Reviewed Finishings (needs work – especially multiple JDF Binding classes) 1244 - Discussed and added comments to Overrides (needs work) 1245 - Reviewed and deleted comments as appropriate (when processed in mappings) 1246 - Reviewed and accepted verified changes as appropriate 1247 - Resume next review at PageRanges 1248

11.16 29 July 2014 – JDFMAP update by SM WG and Rainer Prosi 1249

* July 2014 – sixth draft in SM WG 1250 - Kept status as Interim draft 1251 - Continued review of mapping table – stopped at OutputDevice 1252 - Reviewed and deleted comments as appropriate (when processed in mappings) 1253 - Reviewed and accepted all changes up to OutputDevice (except for Finishings – see 1254 below) 1255 - Skipped over review of FinishingsCol mappings (from Mike Sweet) with IPP WG review 1256 updates from 06/16/14 – to be reviewed with Rainer in the future 1257 - Resume next review at Overrides in mapping table 1258



11.17 21 July 2014 – JDFMAP update by SM WG and Rainer Prosi 1259

* July 2014 – fifth draft in SM WG 1260 - Kept status as Interim draft 1261 - Continued review of mapping table – stopped at JobSheetsCol 1262 - Reviewed and deleted comments as appropriate (when processed in mappings) 1263 - Capitalized and enclosed in square brackets “[Input]” and “[Output]” in mapping table per 1264 Rainer 1265 - Skipped over review of FinishingsCol mappings (from Mike Sweet) – to be reviewed with 1266 Rainer in the future 1267 - Added all FinishingsCol mappings (from Mike Sweet) – per IPP WG review on 06/16/14 1268 - Resume next review at Media in mapping table 1269

11.18 4 June 2014 – JDF update by Rick Yardumian and Rainer Prosi 1270

* June 2014 – fourth draft in SM WG 1271 - Kept status as Interim draft 1272 - Added all of Rainer Prosi’s PDF notes on 13 May 2014 as comments in this draft – Rick 1273 - Added all new mappings from PWG F2F on 14 May 2014 – Rick 1274 - Added all finishing types and member attributes from PWG Finishings 2.0 – Ira 1275 - Added ISSUE about XxxSupplied elements (which should NOT be in a Job Ticket, but 1276 only in a Job Receipt) before Table 1 and highlighted all affected PWG elements – Ira 1277 - Added Rick Yardumian as co-author and Rainer Prosi as major contributor – Ira 1278

11.19 30 April 2014 – JDF update by Rick Yardumian 1279

* April 2014 – third draft in SM WG 1280 - Kept status as Interim Draft 1281 - Added many mapping comments and questions to table and section 4.1 1282 - Added full Xpath for all JDF objects (favoring non-intent classes) 1283 - Accepted all font changes in table (for readability) 1284

11.20 6 April 2014 1285

* April 2014 – second draft in SM WG 1286 - Kept status as Interim Draft, consistent with previous reviews of JDF mapping content. 1287 - Converted spec to current PWG document template (copying each body section as 1288 plaintext to avoid format errors). 1289 - Corrected copyright dates and headers/footers. 1290 - Rewrote Abstract and section 1 to clarify single-mapping scope (JDF to PJT). 1291 - Added sections 2.1 to 2.4 on conformance, printer, and other terminology and acronyms. 1292 - Completely rewrote sections 3.1 to 3.4 on rationale, use cases, out-of-scope, and design 1293 requirements for consistency with other recent PWG specifications. 1294 - Added section 5 on conformance requirements. 1295



- Added sections 6 to 8 on internationalization, security, and IANA considerations. 1296 - Added or updated references in section 9. 1297

11.21 5 October 2011 to 24 October 2013 1298

* October 2013 – first draft in SM WG (w/ Adobe PPD and MSPS mappings included) by 1299 Paul Tykodi, with additions to especially MSPS mapping. 1300

* Five previous drafts – in Cloud WG and MFD WG. 1301 - Initial content from Mike Sweet, Justin Hutchings, Paul Tykodi, and Ira McDonald. 1302 - Partial mapping from JDF to PJT from Ira McDonald. 1303