SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : EROD006 - Echange contextuel, données véhicule non automoteur - (Données véhicule non automoteur / Gegevens niet-gemotoriseerd voertuig)
- Approved
, and is part of release 202001 - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Any
Receiver : Any
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+006
|
||
| 20 |
Marque
|
No
|
-
|
-
|
Mand.
|
NME+005+x--x
|
||
| 30 |
Modèle
|
No
|
-
|
-
|
Mand.
|
NME+005+:x--x
|
||
| 40 |
Type
|
No
|
-
|
-
|
Option.
|
NME+005+::x--x
|
||
| 50 |
Date du première usage
|
No
|
-
|
-
|
Option.
|
DTM+013:x--x:001
|
||
| 60 |
Date d'achat
|
No
|
-
|
-
|
Option.
|
DTM+061:x--x:001
|
||
| 70 |
Numéro de châssis
|
No
|
-
|
-
|
Option.
|
RFF+011:x--x
|
||
(*) 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.