SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : AMEME - - (A Message Envelope - holding Message(s) being Exchanged)
- 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 - Message = Exchange Unit
|
No
|
-
|
-
|
Mand.
|
1..n occurrences - each one of (M0101v20 / M0103v20 / M0104ANNv7 / M0104MODv20 / M0104REMv20 / M0104RESv7 / M0104REXv20 / M0104SUSv6 / M0104TFTv20 / M0104TFTRv16 / M0105v7 / M0108v6 / M0109v14 / M0114v20 / M0118v20 / M0119v18 / M0121v16 / M0122v16 / M0123v16 / M0124v15 / M0125v8 / M0126v13 / M0130v9 / M0131v8 / M0140v3 / M0147v5 / M0202v13 / M0203v8 / M0204v13 / M0205v13 / M0206v13 / M0207v7 / M0210v13 / M0211v13 / M0214v6 / M0215v4 / M0216v2 / M0302v4 / M0303v2 / M0304v13 / M0306v4 / M0307v2 / M0308v3 / M0401v2 / M0403v2 / M0405v2 / M0410v12 / M0603v3 / M0701v3 / M0901v1 / M0902v1 / M9101v2 / M9103v7 / M9120v3 / M9130v1 / M9730v6)
|
|
| 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.