ItemMessageHeader

From imde.io

Revision as of 13:25, 19 December 2022 by HansdG (talk | contribs)

Background Presentation


Open Question: create just one message/datacontainer standard and define type of message in <header> or make specific messages where type is not part of header?

<Header Version="1.0">
  <DataContainerType="Item">
  <DataSender>
    <Identifier Type=GLN 8719328024200>
  <DataReceiver>
    <Identifyer Type=GLN 8719328024262>
    <DataReceiverID= 23235>
  <DataProvider>
    <Identifyer Type=GLN 8719328024279>
    <Name "SyncForce">
  <MessageIdentifier>a1a1140b-1859-4fe5-b4f4-0cd843f9e1c3
  <Creation DateTime 2021-12-17 11:26:25.578441510 +0530
</ItemHeader>

Header is a mandatary for every message and defines the type of message and all related parties:

  • DataSender: The legal entity or target system sending the data
  • DataReceiver: The legal entity or target system receiving the data
  • DataProvider: The solution provider / system that has distributed the data (e.g. PIM systems like InRiver, SyncForce, Akeneo, et cetera)