SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : DPTDAM002 - - (Claimant - Damage - données dommage corporel)
- 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 : physical damage
|
No
|
-
|
-
|
Mand.
|
DAM+002
|
||
| 20 | u |
Claimant - Dommage corporel - Objet endommagé
|
No
|
-
|
-
|
Option.
|
Multiple presencies possible. Extendible with one of : (DPTDAMDODGEN.v5)
|
DAM+002 - DOD+xxx
|
| 30 |
Claimant - Dommage corporel - Objet endommagé - object type : personne (individu)
|
No
|
-
|
-
|
Mand.
|
DAM+002 - DOD+030
|
||
| 40 |
Claimant - Dommage corporel - Personne (individu) - instance identifier
|
No
|
-
|
-
|
Option.
|
DAM+002 - DOD+030+x--x:002/003
|
||
| 50 |
Claimant - Dommage corporel - Personne (individu) - instance name
|
No
|
-
|
-
|
Option.
|
DAM+002 - DOD+030+:::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.