JDF ticket data structure

The JDF ticket must concatenate these elements in the following order:

1. UTF-8 BOM

2. UTF-8 JDF ticket without any XML comment after the ending tag “</JDF>”

Multiple nested JDF nodes are allowed.

Exactly one JDF node with an executable process DigitalPrinting must be present in the ticket. Only this JDF node is executed in the JDF/JMF workflow:

• //JDF[@types] contains DigitalPrinting, and

• //JDF[@status] is either “Waiting”, “Ready” or “Spawned”.

If the JDF ticket does not comply to the above conditions, error 3 (XML parser error) will be sent in response to the JMF message SubmitQueueEntry.

Example

Example of a nested JDF ticket:

<?xml version="1.0" encoding="UTF-8"?>

<JDF>

<!-- Ticket content removed -->

<JDF Types=”DigitalPrinting” Status=”Waiting”>

<!-- Ticket content removed -->

...

</JDF>

</JDF>

Remark

The JDF ticket data applies to all incoming tickets.