SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : DPTDAMDOD001 - - (Claimant - Damage - Damaged object - données véhicule)
- Approved
, and is part of release 202201 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender :
Receiver :
Status : 2 - Version : 4
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Claimant - Damage - Damaged vehicle
|
No
|
-
|
-
|
Mand.
|
ObjectDamagedTractorVehicle
|
||
| 20 |
Claimant - Damage - Damaged vehicle - object instance identifier
|
No
|
-
|
-
|
Option.
|
RiskObjectDetail ObjectIdentifier CodeListIdentifier
|
||
| 30 |
Claimant - Damage - Damaged vehicle - object instance name
|
No
|
-
|
-
|
Option.
|
RiskObjectDetail ObjectName
|
||
| 40 |
Claimant - Damage - Damaged vehicle - Marque / Modèle / Type
|
No
|
-
|
-
|
Option.
|
MakeModelTypeName NameDetail LastName FirstName
|
||
| 50 |
Claimant - Damage - Damaged vehicle - Numéro plaque d'immatriculation
|
No
|
-
|
-
|
Option.
|
RegistrationPlateReference
|
||
| 60 |
Claimant - Damage - Damaged vehicle - Véhicule immobilisé
|
Yes
|
1
|
Option.
|
TheVehicleIsOutOfServiceCode
|
|||
| 61 | n |
Véhicule - Type de transmission
|
Yes
|
2
|
Option.
|
TransmissionCode
|
||
| 62 | n |
Claimant - Damage - Damaged vehicle - Véhicule A ou B sur constat européen
|
Yes
|
1
|
Option.
|
VehicleAsOnFormCode
|
||
| 70 |
Claimant - Damage - Damaged vehicle - Driver
|
No
|
-
|
-
|
Option.
|
PartyDriver
|
||
| 80 |
Claimant - Damage - Damaged vehicle - Driver - Nom officiel - Nom de famille
|
No
|
-
|
-
|
Cond.
|
Mandatory
|
OfficialName NameDetail LastName
|
|
| 90 |
Claimant - Damage - Damaged vehicle - Driver - Nom officiel - 1er prénom
|
No
|
-
|
-
|
Cond.
|
Mandatory
|
OfficialName NameDetail FirstName
|
|
| 100 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - rue
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail StreetName
|
||
| 110 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail HouseNumber
|
||
| 120 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail BoxNumber
|
||
| 130 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - extension
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail AddressExtension
|
||
| 140 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail AddressIdentifier
|
||
| 150 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - Adresse optimisée suivant fournisseur, code
|
No
|
-
|
-
|
Option.
|
OfficialAddress
|
||
| 160 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - code postal
|
No
|
-
|
-
|
Option.
|
OfficialAddress PostalCode
|
||
| 170 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - localité
|
No
|
-
|
-
|
Option.
|
OfficialAddress CityName
|
||
| 180 |
Claimant - Damage - Damaged vehicle - Driver - Adresse - code pays
|
No
|
-
|
-
|
Option.
|
OfficialAddress CountryCoded
|
||
| 190 |
Claimant - Damage - Damaged vehicle - Driver - Date de naissance
|
No
|
-
|
-
|
Option.
|
BirthDate
|
||
| 200 |
Claimant - Damage - Damaged vehicle - Driver - Numéro de téléphone privé
|
No
|
-
|
-
|
Option.
|
PrivateTelephoneCommID CommunicationChannelNumber
|
||
| 210 |
Claimant - Damage - Damaged vehicle - Driver - Numéro de fax
|
No
|
-
|
-
|
Option.
|
FaxCommID CommunicationChannelNumber
|
||
| 220 |
Claimant - Damage - Damaged vehicle - Driver - Adresse boîte postale électronique
|
No
|
-
|
-
|
Option.
|
EmailAddressCommID CommunicationChannelNumber
|
||
| 230 | n |
Claimant - Damage - Damaged vehicle - Driver - Qualité de l'adresse eMail
|
Yes
|
1
|
Cond.
|
Possibly IF COM+003 NOT Null
|
EMailQualityCode
|
|
(*) 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.