> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Archived, and was part of release 201301 :
Identifier : RODGEN - - (Données communes objets de risque / Algemene gegevens risico-object) - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info )
Sender :
Receiver :
Status : 3 - Version : 8
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2 UN/EDIFACT representation
Indicator
Identifier
Version
10 u 
Riskobject, type
No
-
-
Mand.
Generic- possibly completed with one of (ROD001.v5 / ROD002.v4 / ROD003.v2 / ROD01x.v6 / ROD030.v3 / ROD04x.v3 / ROD05x.v2 / ROD060.v2 / ROD090.v2 / ROD149.v2) 
ROD+xxx 
20 n 
Pour tout objet possible, nom
No
-
-
Option.
 
NME+001+x--x 
30 n 
Pour tout objet possible, situation du risque
No
-
-
Option.
Ideally- mandatory for objects- non-moving and mentionned at such address. 
ADR+001+x--x:x--x:x--x::x--x:x--x:x--x+x--x+x--x+x--x+x--x 
40 n 
Pour tout objet possible, capital
No
-
-
Option.
 
MOA+004:x--x:EUR:2:001+x--x:x--x:2 
50 n 
Pour tout objet possible, description
No
-
-
Option.
 
FTX+019+x--x:x--x:x--x:x--x:x--x 
60 n 
Geo Coordinates, position
No
-
-
Option.
 
GEC+001 
70 n 
Geo Coord., position - System
Yes
1
Mand.
 
GEC+001 - ATT+A10M+1 
80 n 
Geo Coord., position - Latitude
No
-
-
Option.
 
GEC+001 - QTY+148:-dddDmmMssssS:2:026 
90 n 
Geo Coord., position - Longitude
No
-
-
Option.
 
GEC+001 - QTY+149:-dddDmmMssssS:2:026 
100 n 
Geo Coord., position - Altitude
No
-
-
Option.
 
GEC+001 - QTY+147:-mmmm:2:008 
110 n 
Geo Coord., position - Description
No
-
-
Option.
 
GEC+001 - FTX+051+GPS ddd° mm?' ss,ss?'?' Sud ddd° mm?' ss,ss?'?' Ouest -mm,mm Mètres 
120 u 
Garantie
No
-
-
Mand.
0..n presencies / Completed with ICDGEN.v7 
ICD+xxx 
130  
Sous-objet de risque
No
-
-
Option.
0..n presencies 
SRO+xxx 

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