The Job Definition Format (JDF) is an industry standard designed to simplify information exchange between different applications and systems in and around the graphic arts industry. To that end, JDF builds on and extends beyond pre-existing partial solutions, such as CIP3's Print Production Format (PPF) and Adobe Systems' Portable Job Ticket Format (PJTF). It also enables the integration of commercial and planning applications into the technical workflow. JDF joins the growing number of standards based on XML, ensuring maximum possible portability between different platforms and ready interaction with Internet-based systems. The JDF Specification defines the entire print production process as well as the print product life cycle in a very detailed manner. The JDF specification is the master document for system integration and product description.
JDF is a comprehensive XML-based file format and proposed industry standard for end-to-end job ticket specifications combined with a message description standard and message interchange protocol.
The most prominent features of JDF are:
You are missing functionality in the JDF Specification or you have a suggestion how to clarify or improve our Spec? Become part of the CIP4 Community! Please don't hesitate to tell us by creating a new JIRA issue. We would love to discuss your ideas! If you don't have any account yet, feel free to create one here: Visitor Registration. |
Description | Link | Remarks |
---|---|---|
JDF 1.7 final published version | ||
JDF schema (lax) | https://schema.cip4.org/jdfschema_1_7/JDF.xsd | The official version of the jdf schema is available at schema.cip4.org |
There is also an archive of all former JDF versions on JDF Archive.
|
The concept of Interoperability Conformance Specification of “ICS” documents is introduced. No single device (i.e., printer, press, imagesetter, etc.) is likely to implement all that the JDF specification provides for. For instance, if you are in the digital printing business, you might not care to facilitate data used for case binding. A RIP is not a requirement for facilitating JDF preflighting. A Stitcher probably doesn't need to handle image rendering data. To specify exactly what individual classes of devices need to do with JDF, CIP4 members are developing ICS document that will provide the minimum expectations for individual classes of devices.