An Acknowledge Message is a JMF Message that is delayed response to a Command Message or Query Message.
The component of a JDF-based workflow that writes JDF or JMF.
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.
The portion of a PrintTalk document that describes a Business Transaction. For example, a PurchaseOrder Business Object describes a purchase order Business Transaction.
When a Print Buyer sends a PrintTalk document to a Print Provider, or a Print Provider sends a PrintTalk document to a Print Buyer, the Business Object within the PrintTalk document describes a business transaction between the Print Buyer and Print Provider.
International Cooperation for Prepress, Press, and Postpress a consortium that is the predecessor of CIP4 and the source of the Print Production Format
The CIP4 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.
A Command Message is a JMF/XJMF Message that requests its recipient to change its state.
The component of a JDF/XJDF-based workflow that selects devices for jobs (within its area of workflow responsibility), receives JDF/XJDF from an agent and routes JDF/XJDF, and communicates status information.
The component of a JDF/XJDF workflow part that interprets JDF/XJDF 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/XJDF instructions directly.
An XML-based syntactic construct describing structured data in JDF/XJDF. In it most simple description, JDF/XJDF 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. A XJDF Node, however, has no XJDF sub-nodes.
Placing pages/signatures from unrelated customers on a print sheet.
A Gray Box specifies a loose combination of several Processes with a specific goal. Examples include proofing, plate making or book making. A Gray Box does not specify all Processes or all Resources – except for Output Resources.
ICS - Interoperability Conformance Specification
Each ICS defines a set of conformance requirements that a conforming JDF-enabled Product shall meet in order to achieve interoperability with other conforming JDF-enabled Products.
You'll hear the terms "JDF Instance", "XJDF 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."
A Resource that is an input to a Process.
An Intent Resource defines the details of products to be produced without defining the process to produce them.
Interoperability Conformance Specification (ICS)
A set of specifications developed by CIP4. ICS documents specify the interface requirements. JDF/XJDF modules (e.g. MIS, Prepress controllers or Press controllers and devices) should interoperate if they comply to the same ICS.
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.
A Device, Controller, Process, Queue, or Agent that consumes (e.g., reads and makes use of) JDF/XJDF instances.
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.
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, a “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.
One or more nodes which comprise the smallest level of control of interest to a JDF-enabled MIS, workflow or production management system.
A job ticket is a metadata container (e.g. a file) that is used by one or more applications (e.g. MIS, WMS, controller, devices) for information exchange concerning the production of a print job.
Either a software application or hardware equipment that does not use JDF or XJDF. A Machine is controlled by a JDF/XJDF Device to which it is connected in a proprietary manner.
The software that implements the Manager Interface, the interface that sends JDF/XJDF Instances, JMF(XJMF Messages and other data (possibly via the network) to a Worker in a Device or Controller in the hierarchy below (see [JDF1.7] Figure 2.1) and may receive information back (possibly via the network) from a Worker in a Device or Controller.
Information/data concerning content data (text, images, graphics, pages) or about print production. JDF and XJDF are the most dominant metadata for print production.
The functional part of a JDF/XJDF 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/XJDF usage of "MIS" does NOT require management reporting, financial systems, accounting, or other functions implied by the broader general usage of MIS.
The JDF/XJDF element type detailing the resources and process specification required to produce a final or intermediate product or resource.
A Resource that is an output from a Process.
In JDF/XJDF the individual physical and logical parts of a job are identified by "partitions." In JDF, code partitions can be specified by the PartIDKeys attribute of the Resource element.
Page Description Language. A generic term for any language that describes pages which may be printed. Examples are PDF®, PostScript® or PCL®.
A Phase is a distinct part of a work step such as setup, production or cleanup.
Adobe Systems’ Portable Job Ticket Format, which is directly mapped to JDF in the JDF Specification.
CIP3's Print Production Format specification, which is widely used in ink key presetting systems and is maintained by CIP4.
An emergent concept for print manufacturing, encompassing mass customizations, highly flexible and nearly autonomous production, extensive integration between print providers to customers and business partners and linking of production with high-quality services. The basis for this are technical standards for communication between persons to machine and machine to machine. Print 4.0 is derived from the term "Industry 4.0" - an initiative for the entire industry.
The customer that is buying a Print Product.
The printed matter produced by the Print Provider according to the specifications from the Print Buyer.
The producer of the Print Product.
PrintTalk is an open XML standard used to communicate business information. It provides JDF and XJDF with capabilities for Pricing, Web-to-Print, RFQ/Quote, Invoicing, Order Status, Sub-contracting and more. The CIP4 consortium has maintained PrintTalk as integral to JDF development since 2005.
Description of the result that a customer is requesting.
An individual step in the production workflow, that is, a singular activity with a specific objective that can be planned and executed independently.
A Query element is a JMF/XJMF message that retrieves information from a receiver without changing the state of that receiver.
Entity that accepts and manages job entries for a Device via a JMF messaging system.
A physical or logical entity that is modified or used by a JDF/XJDF 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.
A Response element is used to reply to a Query or a Command message.
A XML construct that marks the start or end of an XML element.
An organizational unit such as a department or a subcontracting company that can accomplish a task.
The software that implements the Worker Interface, the interface that receives JDF/XJDF Instances, JMF/XJMF Messages and other data (possibly via the network) from a Manager in a Controller or MIS in the hierarchy above (see [JDF1.7] Figure 2.1) and may send information back (possibly via the network) to a Manager in a Controller or MIS.
A Workflow is a sequence of defined work steps (processes), whereby the activities are triggered, controlled and terminated by events.
Workflow Automation is the concept of sharing electronic data between agents, controller and devices to make sure that processes get all the information/resources that they require for an automatic execution, at least in part.
Workflow Management System (WMS)
A WMS is a software system for defining (modeling), executing, controlling and simulating workflows. Normally, a WMS has a common User Interface for all processes, that it handles.
XJDF is an extensible, XML-based data interchange format built upon more than 15 years of experience with JDF. The major conceptual change is that XJDF no longer attempts to model the entire job as one large “job ticket” but rather specifies an interchange format between two applications that are assumed to have an internal data model that is not necessarily based on XJDF. Thus, each XJDF ticket specifies a single transaction between two parties.
Exchange Job Messaging Format. A communication format with multi-level capabilities -- the command and control language that is an integral part of XJDF. XJMF is specified within the XJDF Specification ... it is not a separate CIP4 standard.