> Syntax independent - MCIs - Messages > Details > Representations
Syntax Independent Components
Dictionary
Models
Code lists

Implementation Related Components
Filters
Doc. Filter
MPB Filter
MCIs
Message Content Inventory Identifier : AMEME - - (A Message Envelope - holding Message(s) being Exchanged) - Approved , and is part of release 202701
 - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info )
Sender :
Receiver :
Status : 2 - Version : 7
Seq. n° n
u
d
(*)		 Data element
Code list
 Usage
 Mandatory
Conditional
Optional (**)
Condition(s)
TB2 UN/EDIFACT representation
Indicator
Identifier
Version
10  
Message Envelope - Syntax version number
No
-
-
Mand.
 
XGH+1' 
20  
Envelope Sender Domain Address
No
-
-
Mand.
 
XGH+1+x--x' 
30  
Envelope Sender User Address
No
-
-
Option.
 
XGH+1+x--x:x--x' 
40  
Envelope Sender Type Coded
No
-
-
Option.
 
XGH+1+x--x:x--x:x--x' 
50  
Envelope Recipient Domain Address
No
-
-
Mand.
 
XGH+1+x--x:x--x:x--x+x--x' 
60  
Envelope Recipient User Address
No
-
-
Option.
 
XGH+1+x--x:x--x:x--x+x--x:x--x' 
70  
Envelope Recipient Type Coded
No
-
-
Option.
 
XGH+1+x--x:x--x:x--x+x--x:x--x:x--x' 
80  
Envelope Content Group Type
No
-
-
Option.
 
XGH+1+x--x:x--x:x--x+x--x:x--x:x--x+x--x' 
90 u 
Envelope Content - Message = Exchange Unit
No
-
-
Mand.
1..n occurrences - each one of (M0101v23 / M0103v23 / M0104ANNv7 / M0104MODv23 / M0104REMv23 / M0104RESv7 / M0104REXv23 / M0104SUSv6 / M0104TFTv23 / M0104TFTRv19 / M0105v7 / M0108v6 / M0109v17 / M0114v23 / M0118v23 / M0119v21 / M0121v19 / M0122v19 / M0123v19 / M0124v18 / M0125v11 / M0126v16 / M0130v9 / M0131v10 / M0140v3 / M0147v6 / M0151v2 / M0202v16 / M0203v9 / M0204v15 / M0205v16 / M0206v16 / M0207v7 / M0210v16 / M0211v16 / M0214v7 / M0215v6 / M0216v5 / M0302v6 / M0303v4 / M0304v15 / M0306v6 / M0307v4 / M0308v5 / M0410v15 / M0421v1 / M0603v3 / M0701v6 / M0901v1 / M0902v1 / M9101v2 / M9103v9 / M9120v4 / M9130v1 / M9730v6)  
XEH … XET 
100  
Message Envelope - Syntax version number
No
-
-
Mand.
 
XGT+1' 

(*) 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.