Message Content Inventory |
Identifier : ICD4xx - - (Données spécifiques des garanties Responsabilité - Exploitation ou autres)
- Approved
, and is part of release 201501 |
Sender :
Receiver :
Status : 2 - Version : 1
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 UN/EDIFACT representation |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
|||||||
10 |
Garantie, type
|
No
|
-
|
-
|
Mand.
|
ICD+4xx
|
Guarantee...
|
||
20 |
Responsabilité dommages corporels
|
No
|
-
|
-
|
Option.
|
MOA+192:amount:EUR:2:001+X024:X025:X030
|
BodilyInjuryLiabilityAmount
|
||
30 |
Responsabilité dommages matériels
|
No
|
-
|
-
|
Option.
|
MOA+193:amount:EUR:2:001+X024:X025:X030
|
MaterialDamagesLiabilityAmount
|
||
40 |
Responsabilité dommages confondus C/M
|
No
|
-
|
-
|
Option.
|
MOA+194:amount:EUR:2:001+X024:X025:X030
|
OverallDamagesLiabilityCorporalAndMaterialAmount
|
||
50 |
Responsabilité dommages immatériels
|
No
|
-
|
-
|
Option.
|
MOA+195:amount:EUR:2:001+X024:X025:X030
|
ImmaterialDamagesLiabilityAmount
|
||
60 |
Responsabilité dommages confondus C/M/I
|
No
|
-
|
-
|
Option.
|
MOA+197:amount:EUR:2:001+X024:X025:X030
|
OverallDamagesLiabilityCorpAndMatAndImmaterialAmount
|
||
70 |
Responsabilité dommages immatériels consécutifs
|
No
|
-
|
-
|
Option.
|
MOA+198:amount:EUR:2:001+X024:X025:X030
|
ConsecutiveImmaterialDamagesLiabilityAmount
|
||
80 |
Objets confiés
|
No
|
-
|
-
|
Option.
|
MOA+196:amount:EUR:2:001+X024:X025:X030
|
EntrustedObjectsAmount
|
(*) 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.