> Syntax independent - MCIs - Messages > Details > Representations

SYNTAX INDEPENDENT COMPONENTS

Implementation Related Components


Message Content Inventory Identifier : DPTDAM003 - - (Claimant - Damage - données dommage financier ou moral ou non spécifié) - Approved , and is part of release 202201
- ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info )
Sender :
Receiver :
Status : 2 - Version : 2
Seq. n° n
u
d
(*)
Data element
Code list
Usage
Mandatory
Conditional
Optional (**)
Condition(s)
TB2 UN/EDIFACT representation
Indicator
Identifier
Version
10  
Claimant - Damage - type of damage : financial or moral damage
No
-
-
Mand.
 
DAM+003/004/998 
20 u 
Claimant - Dommage financier/moral - Objet endommagé
No
-
-
Option.
Multiple presencies possible. Extendible with one of : (DPTDAMDODGEN.v5) 
DAM+003/004/998 - DOD+xxx 
30  
Claimant - Dommage financier/moral - Objet endommagé - object type
No
-
-
Mand.
 
DAM+003/004/998 - DOD+xxx 
40  
Claimant - Dommage financier/moral - Objet endommagé - object instance identifier
No
-
-
Option.
 
DAM+003/004/998 - DOD+xxx+x--x:002/003 
50  
Claimant - Dommage financier/moral - Objet endommagé - object instance name
No
-
-
Option.
 
DAM+003/004/998 - DOD+xxx+:::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.