In table 3.12 ProofApprovalResponse Element, the following row is found:
|ProofResponse *||element||Human-readable text for individual proof response.|
Although this was the description in PrintTalk 1.5, the description is clearly wrong, since ProofResponse is an element with an attribute and two subelements so can't be "human-readable text".
If a Print Provider wants a Print Buyer to approve a soft or hard copy order, the Print Provider SHALL send to the Print Buyer
a ProofApprovalRequest whose @BusinessRefID references the order’s PurchaseOrder.
Note: xjdf:ContentCheckIntent allows the Print Buyer to define the desired proofing and preflighting workflow for a specific print job.
Note: Multiple ProofApprovalRequests need to be sent if multiple proofs need to be approved.
<rename ProofRequest to ProofApprovalRequest and delete original ProofApprovalRequest>
Table 3.11: ProofRequest Element
|xjdf:ProofItem *||...||Details of the items to be proofed. xjdf:ProofItem/@ProofTarget SHALL be
used to reference the proof that is requested.
|JobIDRef ?||string NMTOKEN||Reference to the @JobID this proof corresponds to. If not specified, the
ProofRequest refers to the job that was ordered by the PurchaseOrder that is
referenced by @BusinessRefID.
Table 3.12: ProofApprovalResponse
<rename ProofResponse to ProofApprovalResponse and delete original ProofApprovalResponse>
Table 3.13: ProofResponse Element
|xjdf:ProofItem ?||...||Details of the items that haveitem that has been proofed. xjdf:ProofItem/@ProofTarget SHALL be used to reference the proof that was requested.|