1. Welcome to the Heidelberg JDF Tutorial

2. Why ICS ? JDF A ICS JDF B Product AProduct B Interoperability Conformance Specifications

3. Define a set of Interoperability Conformance Specifications – ICS –The term “JDF Compliant” does not immediately imply that two arbitrary applications will communicate. Sending RIP instructions to a Folding Machine is not useful… –Two applications that comply with a given ICS will communicate in a meaningful way. –Product Certification will be based on ICS Compliance Avoid multiple, incompatible JDF Dialects

4. Comparison of Spec and ICS Spec Specifies –syntax of JDF Cardinality of Parameters in a JDF ticket –Optional (?,*) –Required (“ “, +) –Number of elements (?,*,+,” “) –Job Ticket view only ICS Specifies –Requirements for Applications Read + Write requirements –May, Must Read (R?, R) –May, Must Write (W?, W) –Must be capable of writing (W  ) –Manager and Worker Role

5. Read, Write Conformance JDF Specification: Specifies only cardinality requirements within a JDF Ticket ICS: Specifies conformance requirements for an Application: –W: Must Write. JDF is invalid unless feature is set. –W?: May Write. No conformance requirement –W  : Conditional Must Write. There are Conditions where a JDF must contain a feature –!W: MUST NOT Write. JDF is invalid if feature is set. –R: Must Read. The information in the JDF must be read and appropriately processed –R?: May Read. No conformance requirement.

6. ICS Document Structure Base ICS JDF Specification Prepress to Conv. Printing ICS MIS Base ICS MIS Sheet ConvPrint ICS MIS Prepress ICS MIS Binding ICS TBD MIS DOMAIN ICS MIS Integ. DigiPrint ICS

7. Base ICS Conformance requirements that are common to all other ICS documents includes the conformance requirements for –Hot Folders, –string Attribute Lengths, –specific generic JDF Elements –specific generic JMF Messages Job Submission

8. MIS ICS Interoperability requirements related to the communication between MIS and production equipment. Generic requirements for all stages of the production process –pre-press –Press –post-press Focus on the main JDF structure –JDF submission from an MIS to a Device –Device communication back to the MIS

9. MIS-Prepress Defines the Interface between the MIS and Prepress focused on Conventional Printing. Processes for a Prepress Workflow System that produces: –Proofs –Plates –Previews.

10. MIS-Sheetfed-Offset This ICS defines the interoperability requirements for JDF Sheet-Fed Offset Printing

11. Prepress - Sheetfed offset Describes the interface between a Prepress Workflow System and a Conventional Sheet Fed Printing Press Controller. Defines how a Prepress Workflow System dynamically communicates with a Press Controller in order to deliver –previews used for evaluating ink zone settings –information about plates.

12. MIS-Binding Defines the conformance requirements for: –Saddle Stitching –Soft-cover and –Hardcover Binding devices. Specifies –JDF Instances, –JDF Messages –JDF Processes

13. MIS-Digital Print Specifies the Conformance Requirements for Integrated Digital Printing Devices. –integrated digital printing systems with in-line finishing capabilities. black and white and limited color –Encompasses production printing IPP semantics.

14. CIP4 Interoperability Event Status CIP4 hosted Interoperability first test event in May 2003 Regular 3-4 month interval Next April 2005 Previous One was January in Heidelberg, Germany –Goals are: Integration of products from various vendors Pinpoint ambiguous areas in the specification Deine and Test Drupa Interoperability –More than 60 Participants from >15 Companies Next Event: Tomorrow, here in Pittsburgh Events are closed door –Goal is to enhance the standard and enable interoperability –NOT to find scapegoats / heroes

15. JDF Interoperability JDF Content JDF Transport JDF Conformance F(t)

16. JDF Conformance Interoperability Levels 1.None (Fax, Phone, Job Sheet) 2.JDF wrapper with many custom extensions 3.Customized JDF in Prototype Applications 4.1-1 Customized JDF in hand-selected customer sites (beta or customer Project) 5.ICS-Based Standard JDF in hand-selected customer sites 6.Out of the box applications using ICS-based Standard JDF

17. JDF Transport Interoperability Levels 1.None (Fax, Phone, Job Sheet) 2.JDF File written to hard coded folder. (one way) 3.Two way JDF File exchange to hard coded folders (inbox, outbox) 4.JDF sent to File or HTTP URL as specified in the JDF 5.JDF + JMF Signaling from Device to Controller 6.JDF + Dynamic, bidirectional JMF exchange

18. JDF Content Interoperability Levels 1.None (Fax, Phone, Job Sheet) 2.Customer Name, Time, Date 3.2. + rough description of workflow steps 4.2. + Vendor-specific subsets of ICS including vendor-specific misinterpretations 5.Complete ICS Functionality 6.Complete description of the workflow