There is a priori no such thing as an intermediate XJDF file that is maintained during production. An implementation may choose to do so but there is no requirement for an XJDF FILE to exist except as the interface to and from a device and that need not / should not be a file but rather a network transaction.
QueueSubmissionParams/@ReturnJMF specifies the address where the completed XJDF with audits should be returned to.
That makes sense after the job completes. However, how should we obtain the XJDF file before it completes?
Powered by a free Atlassian Confluence Open Source Project License granted to CIP4. Evaluate Confluence today.