We are working on Solution for the Print Industry and we need to import info from JDF (Job Definition Format) or CiP4 format to eWorks (which is our solution based on FM13ADV).
Can anyone assist us where to get such API or import scripts. We are willing to work with such organization.
Please let me know
a brief intro to JDF and CIP4
Job Definition Format (JDF) is a technical standard being developed by the graphic arts industry to facilitate cross-vendor workflow implementations of the application domain. It is an XMLformat about job ticket, message description, and message interchange. JDF is presently managed by CIP4, the International Cooperation for the Integration of Processes in Prepress, Press and Postpress Organization. JDF was initiated by Adobe Systems, Agfa, Heidelberg and MAN Roland in 1999 but handed over to CIP3 at Drupa 2000. CIP3 then renamed itself to CIP4.
The initial focus was on sheetfed offset and digital print workflow, but has been expanded to web(roll)-fed systems, newspaper workflows and packaging and label workflows.
The JDF standard is currently at revision 1.4a. The process of defining and promulgating JDF began circa 1999. The standard is in a fairly mature state; and a number of vendors have implemented or are in the process of implementing it. JDF PARC, a multivendor JDF interoperability demonstration, was a major event at the 2004 Drupa print industry show, and featured 21 vendors demonstrating, or attempting to demonstrate interoperability between a total of about forty pairs of products.
JDF is an extensible format. It defines both JDF files and JMF, a job messaging format based on XML over HTTP. In practice, JDF-enabled products can communicate with each other either by exchanging JDF files, typically via "hot folders," or the net or by exchanging JMF messages over the net.
Acrobat 7 includes a menu item to create a JDF file linked to a PDF file. This starts with the 'intent' for the job. More JDF detail is added later in various steps of the production workflow.
As is typical of workflow systems, the JDF message contains information that enables each "node" to determine what files it needs as input and where they are found, and what processes it should perform. It then modifies the JDF job ticket to describe what it has done, and examines the JDF ticket to determine where the message and accompanying files should be sent next.
The goal of CIP4 and the JDF format is to encompass the whole life cycle of a print and cross-media job, including device automation, management data collection and job-floor mechanical production process, including even such things as bindery, assembly of finished products on pallets.
Before JDF can be completely realized, more vendors need to accept the standard. Therefore few users have been able to completely utilize the benefits of the JDF system. In finishing and binding, and printing there is a tradition of automation and few large enough dominating companies that can steer the development of JDF system. But it is still necessary for the manufacturers of business systems to fully support JDF. The same progress has not been made here probably because many of these companies are small specialty companies who haven't the resource to manage such development and who don't specialize on graphic production.