The examples are currently incomplete and / or incorrect
The section needs a major review
Table 1.1: Glossary
|PrintTalk Project||The <Glos>Business Transactions</Glos> that apply to one set of <Glos>Items</Glos> that are negotiated between <Glos>Print Buyer</Glos> and <Glos>Print Provider</Glos> .|
<remove entire B Usage of PrintTalk IDs>
6.2 Identifiers in PrintTalk
This section summarizes the usage of the various IDs that are defined in PrintTalk in typical workflow scenarios.
Every PrintTalk element SHOULD be uniquely identified by specifying ##refPrintTalk/@payloadID.
Every BusinessObject SHALL be uniquely identified by specifying ##refRequest/@BusinessID in the parent Request. The value of ##refRequest/@BusinessID SHALL NOT be identical for two Requests if ##refPrintTalk/@payloadID of the parent PrintTalk element is not identical.
Request/@BusinessRefID references a Business Object that identifies the <Glossary> PrintTalk Project</Glssary>. See ##ref Table Table 6.1: Business Object References for a summary of the Request/@BusinessID values that SHALL be referenced by Request/@BusinessRefID of the various business objects.
@CustomerProjectID is the ID of the entire order, which contains one or more jobs or individual
products in the context of the Print Buyer’s MIS or ERP system. Once specified, @CustomerProjectID SHALL remain constant for all business objects of a <glos>PrintTalk Exchange</glos>. If present, xjdf:CustomerInfo/@CustomerProjectID SHALL match Request/@CustomerProjectID.
<copy B.3 xjdf:XJDF/@JobID, B.4 xjdf:CustomerInfo/@CustomerOrderID>