The reference to the PDL data. The JDF ticket must contain one or more HTTP URLs where the PDF data must be retrieved. The PDL type must be PDF. The URL must be of type HTTP. The PDL file(s) must be available for download throughout the lifetime of the job.
Combining the PDF data with ticket in a MIME package is not supported (e.g. URL=”cid:sometag”).
In case of multiple PDF files, the PDF files are merged:
In the order in which the files are listed.
Duplicate references to the same PDF file are discarded.
The JDF ticket must contain the following FileSpec element: //LayoutElement/FileSpec/@URL.
The LayoutElement must be referenced in the RunList element.
The PRISMAsync Print Server no longer needs the files after sending the JMF message ReturnQueueEntry.
Syntax
XPath:
/JDF/ResourcePool/LayoutElement[@ID="..."]/FileSpec/@URL=”http://...”
/JDF/ResourcePool/RunList/LayoutElementRef/@rRef="..."
Example - Reference to PDL data in the JDF ticket
<JDF>
<ResourcePool>
<RunList>
<LayoutElementRef rRef="file_1"/>
</RunList>
<LayoutElement ID="file_1">
<FileSpec URL="http://somewhere/file.pdf"/>
</LayoutElement>
</ResourcePool>
</JDF>
Remark
Agfa :Apogee version 8 requires the merging of PDF files. The merging of the PDF files does not respect the Runlist index. Selecting specific pages or ordering is not supported.
The PDL type is not checked. A PDL type different than PDF results in a RIP error from the PDF RIP.
When specified, the @MimeType indicates the PDL type of job data. The PDL type must be PDF for the JMF communication.
If the MimeType is not PDF, the corresponding URL is ignored.
Syntax
XPath: /JDF/ResourcePool/LayoutElement/FileSpec/@MimeType
Type
String
Supported range
application/pdf
When specified, @MimeType defines the type of PDL data that is used for processing. The type of PDL data can be PostScript or PDF.
Syntax
XPath: /JDF/ResourcePool/LayoutElement/FileSpec/@MimeType
Type
String
Supported range
application/pdf
application/postscript
application/vnd.hp-PCL