> Syntax independent - MCIs - Messages > Details

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components

Message Content Inventory Identifier : EROD003 - Echange contextuel, données engin nautique - (Données engin nautique)- - Approved , and is part of release 202101
- ( UN/Edifact : added info ) - (UN/Edifact MIG : Fr / Nl ) - (XML/JSON : added info )
Sender : Any
Receiver : Any
Status : 2 - Version : 3
Seq. n° n
u
d
(*)		 Data element
Code list
 Usage
 Mandatory
Conditional
Optional (**)
Condition(s)
Indicator
Identifier
Version
10  
Contrat
No
-
-
Mand.
 
20  
Riskobject, type
No
-
-
Mand.
 
30  
Bateau, nom
No
-
-
Mand.
 
40  
Bateau, marque
No
-
-
Option.
 
50  
Bateau, marque et modèle
No
-
-
Option.
 
60  
Bateau, pays de construction (code et nom)
No
-
-
Option.
 
70  
Bateau, année de construction
No
-
-
Option.
 
80  
Bateau, numéro d'identification de la coque
No
-
-
Option.
 
90  
Bateau, lettre de pavillon - code
No
-
-
Option.
 
100  
Bateau, lettre de pavillon - numéro
No
-
-
Option.
 
110  
Bateau, plaque d'immatriculation numéro
No
-
-
Option.
 
120  
Bateau, utilisation
Yes
1
Mand.
 
130  
Bateau, type
Yes
1
Option.
 
140  
Bateau, gréement
Yes
1
Option.
 
150  
Bateau, matériaux de construction principal
Yes
1
Option.
 
151 n 
Bateau, a cabine
No
-
-
Option.
 
160  
Bateau, longueur hors tout en mètres
No
-
-
Option.
 
170  
Bateau, longueur de la coque en mètres
No
-
-
Option.
 
180  
Bateau, largeur de la coque en mètres
No
-
-
Option.
 
190  
Bateau, tirant d'eau en mètres
No
-
-
Option.
 
200  
Bateau - Certificat de navigation, nom
No
-
-
Option.
Multiple documents are a possibility 
210  
Bateau - Certificat de navigation, date de début de validité
No
-
-
Option.
 
220  
Bateau - Certificat de navigation, date de fin de validité
No
-
-
Option.
 
230  
Bateau - Certificat de navigation, mediafile
No
-
-
Option.
 
240  
Bateau - Port d'attache, nom
No
-
-
Option.
 
250  
Bateau - Chantier de construction, nom
No
-
-
Option.
 
260  
Garantie
No
-
-
Option.
0..n presencies 
270  
Bateau - Moteur, marque
No
-
-
Option.
0..n presencies - Multiple engines are a possibility 
280  
Bateau - Moteur, marque et type
No
-
-
Option.
 
290  
Bateau - Moteur, année de construction
No
-
-
Option.
 
300  
Bateau - Moteur, numéro de série
No
-
-
Option.
 
310  
Bateau - Moteur, installation
Yes
1
Option.
 
320  
Bateau - Moteur, carburant
Yes
1
Option.
 
330  
Bateau - Moteur, description
No
-
-
Option.
 

(*) n u d : new / updated / deleted since previous version.

(*bis) u : updated : this can be a codelist-version incrementing.
  Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
  The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
  Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...

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