JDF permits adding of generic key-value pairs in a specific structure in the JDF ticket:
<JDF ID="NodeIDRoot" Type="ProcessGroup" Types="... DigitalPrinting ..."xmlns="http://www.CIP4.org/JDFSchema_1_1" Status="Waiting"xmlns:oce="http://www.oce.com/JDF_Extension/1_00" >
<oce:KeyValuePair Key="Key1">Value 1</oce:KeyValuePair>
<oce:KeyValuePair Key="Key2">Hello, World!</oce:KeyValuePair>...</JDF>
This is not a modification of the mapping file but a possible generic extension of the JDF ticket to support custom user defined ticket fields.
After mapping all the items defined in the mapping table, the system performs an additional step. It searches for all the oce:KeyValuePair nodes in the JDF ticket. The Key attribute specifies the name of the item in the PD ticket and the inner content of the node becomes the value for this item.
Example:
The default ticket definition contains a series of items related to user profile information ( eg: FirstName, LastName, Department, Location, TelephoneNumber, EmailAddress, etc).
Suppose the PrintShop where PRISMAdirect is installed wants to stay connected to its customers via a social network (facebook, google+). The customer wants to extend the user information with the FaceBook account. For this he will add a new item in the PD ticket called FacebookAccount from JTE.
Additionally, the JDF tickets that are sent to the JDF/JMF interface of PRISMAdirect must contain a new node:
<oce:KeyValuePair Key="FacebookAccount">John.Doe</oce:KeyValuePair>
The job ticket in PRISMAdirect will have the FacebookAccount field set with the value “John.Doe”.