The following glossary is NOT a CIP4 standard and some of the terms defined below are done so in a manner that is as much educational as it is definitive. If there are discrepancies between the following definitions and definitions contained with in the JDF specification, the JDF specification shall take precedence as it is the standard.

French Translation

Term	Definition
Agent	The component of a JDF-based workflow that writes JDF or JMF.
Attribute	An XML construct that is used to describe a characteristic of an XML element. For instance, the JDF resource element "Color" may have an attribute called "Lab", and that "Lab" attribute provides the L a* b* value of a specified colorant at 100% tint value. Another example: The JDF resource element "DigitalDelivery" allows you to specify digital file delivery via email, ISDN software, a web server, instant messaging and so on with the "Method" attribute.
CIP3	International Cooperation for Prepess, Press, and Postpress a consortium that is the predecessor of CIP4 and the source of the Print Production Format
CIP4	The International Cooperation for the Integration of Processes in Prepress, Press and Postpress organization, a not-for-profit global associated found in Zurich, Switzerland in 2001, whose purpose it is to encourage computer-based integration of all processes that have to be considered in the graphic arts industry, in particular the specification of standards.
Controller	The component of a JDF-based workflow that selects devices for jobs (within its area of workflow responsibility), receives JDF from an agent and routes JDF, and communicates status information.
Device	The component of a JDF workflow part that interprets JDF and executes the instructions. A Device can be software that controls a machine, which it does in a manner that is proprietary to the product vendor, or it can be software such as a RIP that executes the JDF instructions directly.
Element	An XML-based syntactic construct describing structured data in JDF. In it most simple description, JDF is structured metadata about a print job and the basic XML building block is an "element." The top level element in JDF is the "JDF Element" and you can break down a print job into multiple JDF elements that are nested into each other. Each nested JDF element is called a "node" and these nodes can be processes nodes such as Imposition, ColorCorrection, FilmToPlateCopying, Screening, CoverApplication, BoxPacking ... all the process elements of a job that you have come to expect.
IFRAtrack	IFRA�s job tracking and information messaging standard, which uses and is a complement to JDF.
IMF	IFRA Messaging Format, a component of IFRAtrack.
Instance	You'll hear the terms "JDF Instance" or "XML Instance" all the time. Although JDF data can be bound to content files with MIME encoding, the JDF data exists separately from your content files. So what is the JDF file called? If we called it a "document" it would become unnecessarily confused with the content file: when a printer or customer refers to their document, they don't mean the JDF. This is also a common issue with other applications of XML, so the convention is to refer to the XML, or in our case the JDF, as the "Instance."
JDF	Job Definition Format. The overall name of CIP4's primary process automation specification. There is also a JDF element, which is a top-level element within JDF that encompasses a node (see "Node" below.) JDF's basic functions are to provide metadata that can be used to describe the entire lifecycle of a print job, provide a method for automating flexible workflows, enable workflow or MIS systems to query new devices to determine their JDF capabilities, and to provide a command and control language that allows workflow or MIS systems to direct devices on the shop floor.
JDF Consumer	A Device, Controller, Process, Queue, or Agent that consumes (e.g., reads and makes use of) JDF instances.
JMF	Job Messaging Format. A communication format with multi-level capabilities -- the command and control language that is an integral part of JDF. Like JDF, there is also the JMF element, which is a top-level element within JDF. JMF is specified within the JDF Specification ... it is not a separate CIP4 standard.
Job	In JDF a Job consists of one or more nodes that are structured in hierarchical tree and also describes the output that is desired by a customer. For instance �job� may either refer to a pile of printed sheets or to the printed sheets themselves. �Job� also refers to varying levels of granularity of a complete order. The printer will refer to the pile of sheets produced in one press run, while the binder may refer to a complete book that is composed of multiple sheets and a cover whereas the end customer may refer to all books that are produced in one contract.
Job part	One or more nodes which comprise the smallest level of control of interest to a JDF-enabled MIS, workflow or production management system.
Machine	Either a software application or hardware equipment that does not use JDF. A Machine is controlled by a JDF Device to which it is connected in a proprietary manner.
Manager	The software that implements the Manager Interface, the interface that sends JDF Instances, JMF Messages and other data (possibly via the network) to a Worker in a Device or Controller in the hierarchy below (see [JDF1.3] Figure 2.1) and may receive information back (possibly via the network) from a Worker in a Device or Controller.
MIS	The functional part of a JDF workflow that oversees all processes and communication between system components and system control. In JDF this is used as an umbrella term that may include workflow, production management and pressroom management systems, as well as print MIS systems, and should not be confused with the broader usage of MIS or Management Information Systems. The JDF usage of "MIS" does NOT require management reporting, financial systems, accounting, or other functions implied by the broader general usage of MIS.
Node	The JDF element type detailing the resources and process specification required to produce a final or intermediate product or resource.
Partition	In JDF the individual physical and logical parts of a job are identified by "partitions." In JDF code partitions are specified by the PartIDKeys attribute of the Resource element.
PDL	Page Description Language. A generic term for any language that describes pages which may be printed. Examples are PDF®, PostScript® or PCL®.
PJTF	Adobe Systems� Portable Job Ticket Format, which is directly mapped to JDF in the JDF Specification
PPF	CIP3's Print Production Format specification, which is widely used in ink key presetting systems and is maintained by CIP4.
Process	An individual step in the production workflow.
Queue	Entity that accepts and manages job entries for a Device via a JMF messaging system.
Resource	A physical or logical entity that is modified or used by a JDF node. Every process has inputs and outputs. The output of one process in JDF becomes the input to the next process, so collectively inputs and outputs are called "Resources." Examples include paper, images, or process parameters.
Tag	A XML construct that marks the start or end of an XML element.
Work center	An organizational unit such as a department or a subcontracting company that can accomplish a task.
Worker	The software that implements the Worker Interface, the interface that receives JDF Instances, JMF Messages and other data (possibly via the network) from a Manager in a Controller or MIS in the hierarchy above (see [JDF1.3] Figure 2.1) and may send information back (possibly via the network) to a Manager in a Controller or MIS.

Pages, Sheets, Forms and Folios: Old Definitions in a Modern Context

The term �page� is very common in everyday conversations regarding printing, but in context of a technical specification for graphic arts it can be misleading. Is page �1� of a document the same as the first page or page one of an imposition or the first page numbered one? The Terminology section of the JDF Specification includes more specific definitions, but, in general, a �reader page� is as the reader sees it in the final product, and a �finished page� is one side of the final cut, folded, and bound product.

�Recto� and �verso� finished pages describe the forward-facing and away-facing pages of a �leaf,� meaning both recto and verso finished pages of one a piece of paper with �leaves� being the plural of leaf.

A �form� is an imposed (ordered) collection of finished pages set for printing on a �sheet� which is the printer�s roll of paper or paper cut for press size. Sheets may also have �recto� and �verso� forms for identification of orientation through the press (facing up vs. facing down at the feeder or off the roll.) And finally, a �signature� is the printed (folded or yet to be folded) sheet and a �surface� is a single side of either a sheet or a signature.

Finished pages are not all necessarily numbered. A 72-page book may have 68 pages that are numbered, which are referred to as either �folio pages� or �folios.� It is also a common convention that the page count for a book does not include the cover pages. Hence, a book may be described as a �72-page book, plus four cover pages� or just �plus cover.� Cover pages may be referenced as �cover 1� (front cover), �cover 2� (inside of front cover), �cover 3� (inside of back cover), and �cover 4� (back cover).

Special arrangements, such as over-covers, wraps, and glue on pages applied to covers are treated as inserts and other furnished material that is bound, but not printed, (e.g., treated as separate job parts until bindery). Where the word �page� is used in the JDF Specification (as opposed to finished page or reader page), it should be interpreted as �finished page.�

For comments or questions about this page please send an email to webmaster@cip4.org
CIP4 and JDF are registered trademarks of the CIP4 Association.