SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : AMECE - - (A Message Envelope - holding Contextally Exchanged Information)
- Approved
, and is part of release 202401 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender :
Receiver :
Status : 2 - Version : 4
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Message Envelope - Syntax version number
|
No
|
-
|
-
|
Mand.
|
GroupHeader
|
||
| 20 |
Envelope Sender Domain Address
|
No
|
-
|
-
|
Mand.
|
SenderIdentificationDetail SenderDomainAddress
|
||
| 30 |
Envelope Sender User Address
|
No
|
-
|
-
|
Option.
|
SenderIdentificationDetail SenderUserAddress
|
||
| 40 |
Envelope Sender Type Coded
|
No
|
-
|
-
|
Option.
|
SenderIdentificationDetail SenderTypeCoded
|
||
| 50 |
Envelope Recipient Domain Address
|
No
|
-
|
-
|
Mand.
|
RecipientIdentificationDetail RecipientDomainAddress
|
||
| 60 |
Envelope Recipient User Address
|
No
|
-
|
-
|
Option.
|
RecipientIdentificationDetail RecipientUserAddress
|
||
| 70 |
Envelope Recipient Type Coded
|
No
|
-
|
-
|
Option.
|
RecipientIdentificationDetail RecipientTypeCoded
|
||
| 80 |
Envelope Content Group Type
|
No
|
-
|
-
|
Option.
|
GroupType
|
||
| 90 | u |
Envelope Content - Contextual Question or Response
|
No
|
-
|
-
|
Mand.
|
1 question or 1..n response - each of (EPTY002v2 / EPTY003v15 / ERODGENv11 / ECNTRCTv1 / ECLAFILNv1 / EDOCxxxv2 / ECNTRCTv2 / EPRENOTIDv1 / EPRENOTDETv1)
|
|
| 100 |
Message Envelope - Syntax version number
|
No
|
-
|
-
|
Mand.
|
|||
(*) n u d : new / updated / deleted since previous version.
(**) Usage: The indications Mandatory / Conditional / Optional are to be understood in respect of the actual level of the Data element:
example given; some party data-set as a whole can be optional, while, if present, the party's name within that party data-set can be mandatory.
Remark: in UN/Edifact, "Mandatory / Conditional" are notions used within the standard. And within edi-guides (a refinement of a standard) the "Conditional" can become "Required / Optional / Dependent / Advised / Not used". Ideally we should implement the same ideas.
(***) Remark: In 2020 things evolved into another "approach A" and then yet another "approach B" - It is that "appoach B" which you see here - That "approach B" is the basis of the EDIMERX development.
In TB2-XML "Namespace 2018" (as well as in eEG7-UN/CEFACT), things were/are structurally different.
EDIMERX is supporting the transition from Edifact (messages) to JSON (API's).
The so-called "Business API's" are what comes next / after such transition-phase - and there things will be structurally differrent again.