> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : ROD009 - - (Données engin aérien / Gegevens luctvaartuig) - Approved , and is part of release 201801
- ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info )
Sender :
Receiver :
Status : 2 - Version : 1
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2 UN/EDIFACT representation
Indicator
Identifier
Version
10  
Riskobject, type
No
-
-
Mand.
 
ROD+009 
20  
Marque et modèle
No
-
-
Mand.
 
NME+005+x--x:x--x 
30  
Marques d'identification
No
-
-
Cond.
pour tout engin immatriculé 
NME+006+x--x 
40  
Numéro de série de fabrication (n° chassis)
No
-
-
Mand.
 
RFF+011:x--x:001 
50  
Type d'engin aérien
Yes
1
Mand.
 
ATT+5900+x--x 
60  
Classe d'utilisation du drone
Yes
1
Cond.
IF ATT+5900 = 06 Drone 
ATT+5910+x--x 
70  
Masse maximale de décollage en kg
No
-
-
Mand.
 
QTY+154:x--x:2:003 

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