ItemMessageHeader: Difference between revisions
From imde.io
Line 46: | Line 46: | ||
Header is a mandatary for every message and defines the type of message and all related parties: | Header is a mandatary for every message and defines the type of message and all related parties: | ||
==Dictionary== | ==Dictionary== |
Revision as of 13:11, 9 January 2023
Every message starts with a message header where the type of message can be found and all parties related to the message. The ItemMesssage contains one or more items. And per item you can have one or more DataTopics. Background Presentation
<IMDEMessage xmlns="https://imde.io/schema/imdemessage"> <Header DataContainerType="Material"> <DataSender> <Identifiers> <Identifier Type="GLN">8719328024200</Identifier> </Identifiers> </DataSender> <DataReceiver> <Identifiers> <Identifier Type="GLN">8719328024262</Identifier> <Identifier Type="DataReceiverID">23235</Identifier> </Identifiers> </DataReceiver> <DataProvider> <Identifiers> <Identifier Type="GLN">8719328024279</Identifier> </Identifiers> <Name>SyncForce</Name> </DataProvider> <MessageIdentifier>a1a1140b-1859-4fe5-b4f4-0cd843f9e1c3</MessageIdentifier> <CreationDateTime>2022-05-30T09:30:10-06:00</CreationDateTime> </Header> <Items> <Item> <DataTopics> <DataTopic Topic="KeyInfo" Format="Azlon" Version="1.0"> ... </DataTopic> </DataTopics> </Item> </Items> </IMDEMessage>
Downloads
Header is a mandatary for every message and defines the type of message and all related parties:
Dictionary
Data element | Definition |
---|---|
DataSender | The legal entity or system sending the data. In this example Wonka is the chocolate manufacturer sending data |
DataReceiver | The legal entity or target system receiving the data. In this example Acme is the retailer receiving data |
DataProvider | The solution provider / system that has distributed the data. In this example Virtucon is the Solution Provider sending the data. |
MessageIdentifier | UUID based, uniquely identifies the data message |