70 likes | 201 Views
Modeling of ABIEs and message assembly. Martin Forsberg Single Face To Industry, Sweden. The CII-way. Billing_ Period. Details Billing Line_ Monetary Summation. Details Billing_ Monetary Summation. Details Billing_ Currency Exchange. Details Invoice_ Trade Line Item. Details Used in CII
E N D
Modeling of ABIEs and message assembly Martin Forsberg Single Face To Industry, Sweden
The CII-way • Billing_ Period. Details • Billing Line_ Monetary Summation. Details • Billing_ Monetary Summation. Details • Billing_ Currency Exchange. Details • Invoice_ Trade Line Item. Details • Used in CII • Not reusable outside CII • Very specific and self describing ABIEs • No involuntary reuse • XSD schema close to the actual message model • XML - Unique namespace for each message, root element that reflects the message type
The TBG6-way • Tendering_ Period. Details • Tendering_ Communication. Details • Tendering_ Location. Details • Used in tendering messages • Reuse of ABIEs within a suit of messages/process • XML - Unique namespaces and root elements for each message type • Possibly some involuntary reuse?
The TBG2-way • Cross-Border_ Contact. Details • Cross-Border_ Party. Details • Cross-Border_ Location. Details • Cross-Border_ Period. Details • Cross-Border_ Communication. Details • Used in UNEdocs • ABIEs reused within the TBG2 context • Not very specific and self describing ABIEs • Involuntary reuse • On message (namespace, root element) for each process (Buy/Ship/Material Management/Transport Operation)
The new TBG1-way • Supply Chain_ Party. Details • Supply Chain_ Contact. Details • Supply Chain_ Trade Line Item. Details • Grouping of ASBIEs in: • Agreement, Delivery, Settlement (Used on both header and line level) • Used in the new submission from TBG1 • ABIEs reused within the supply chain context • ABIEs reused on line and header level • One message (Namespace and root element) for each message) • All messages reuses the same structure • Involuntary reuse • Not very specific and self describing ABIEs
Schemas • We want to have one schema for each message • The definition of the schema (namespace) must be retained when further contextualization is done (as long as it is restrictions)