SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : EVTROD001 - - (Evénement - objet de risque - données véhicule)
- Approved
, and is part of release 201501 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (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 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Risk object - type : véhicule automoteur
|
No
|
-
|
-
|
Mand.
|
ObjectInsuredTractorVehicle
|
||
| 20 |
Risk object véhicule - Instance ID at insurer
|
No
|
-
|
-
|
Option.
|
RiskObjectDetail ObjectIdentifier CodeListIdentifier
|
||
| 30 |
Risk object véhicule - Instance ID at intermediary
|
No
|
-
|
-
|
Option.
|
RiskObjectDetail ObjectIdentifier CodeListIdentifier
|
||
| 40 |
Risk object véhicule - Marque / modèle / type
|
No
|
-
|
-
|
Option.
|
MakeModelTypeName NameDetail LastName FirstName
|
||
| 50 |
Risk object véhicule - Numéro plaque d'immatriculation
|
No
|
-
|
-
|
Option.
|
RegistrationPlateReference
|
||
| 60 |
Risk object véhicule - Numéro de chassis
|
No
|
-
|
-
|
Option.
|
ChassisReference
|
||
| 70 |
Risk object véhicule - Type de véhicule codification DIV
|
Yes
|
6
|
Option.
|
VehicleCode
|
|||
| 80 |
Risk object véhicule - Usage du véhicule
|
Yes
|
6
|
Option.
|
VehicleUsageCode
|
|||
| 90 |
Risk object véhicule - Type de valeur couverte (véhicule)
|
Yes
|
5
|
Option.
|
ValueCoveredForMotorisedVehiclesCode
|
|||
| 100 |
Risk object véhicule - Financement
|
No
|
-
|
-
|
Option.
|
FinancingBinary
|
||
| 110 |
Risk object véhicule - Valeur catalogue hors TVA
|
No
|
-
|
-
|
Option.
|
ListValueVatExclusiveAmount
|
||
| 120 |
Risk object véhicule - Valeur assurée (compagnie)
|
No
|
-
|
-
|
Option.
|
InsuredValueInsurerAmount
|
||
| 130 |
Risk object véhicule - Conducteur
|
No
|
-
|
-
|
Option.
|
PartyDriver
|
||
| 140 |
Risk object véhicule - Conducteur - Identifiant chez l'assureur
|
No
|
-
|
-
|
Option.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 150 |
Risk object véhicule - Conducteur - Identifiant chez l'intermédiaire
|
No
|
-
|
-
|
Option.
|
PartyIdentificationDetail PartyIdentifier CodeListIdentifier
|
||
| 160 |
Risk object véhicule - Conducteur - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName FirstName
|
||
| 170 |
Risk object véhicule - Conducteur - Adresse
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail StreetName
|
||
| 180 |
Risk object véhicule - Conducteur - Date de naissance
|
No
|
-
|
-
|
Option.
|
BirthDate
|
||
| 190 |
Risk object véhicule - Conducteur - Alcootest effectué
|
No
|
-
|
-
|
Option.
|
BreathTestDriverBinary
|
||
| 200 |
Risk object véhicule - Guarantee
|
No
|
-
|
-
|
Mand.
|
Multiple presencies possible
|
Guarantee...
|
|
| 210 |
Risk object véhicule - Guarantee - Montant franchise
|
No
|
-
|
-
|
Option.
|
ExemptionAmount
|
||
| 220 |
Risk object véhicule - Guarantee - Cover
|
No
|
-
|
-
|
Option.
|
Multiple presencies possible
|
Cover...
|
|
(*) 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.
(***) Remark: In 2020 things evolved into another "approach A" and then yet another "approach B" - It is that "appoach B" which you see here - That "approach B" is the basis of the EDIMERX development.
In TB2-XML "Namespace 2018" (as well as in eEG7-UN/CEFACT), things were/are structurally different.
EDIMERX is supporting the transition from Edifact (messages) to JSON (API's).
The so-called "Business API's" are what comes next / after such transition-phase - and there things will be structurally differrent again.