> Syntax independent - MCIs - Messages > Details
SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
|
> Syntax independent - MCIs - Messages > Details
|
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : DPTDAM00x - - (Claimant - Damage - données dommage financier ou moral) - Approved , and is part of release 202201 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info ) |
Version : 2 Status : 2 |
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2-UN/EDIFACT representation (including comments) |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Claimant - Damage - type of damage : financial or moral damage
|
No
|
-
|
-
|
Mand.
|
DAM+003/004
|
||
| 20 | u |
Claimant - Dommage financier/moral - Objet endommagé
|
No
|
-
|
-
|
Option.
|
Multiple presencies possible. Extendible with one of : (DPTDAMDODGEN.v5)
|
DAM+003/004 - DOD+xxx
|
| 30 |
Claimant - Dommage financier/moral - Objet endommagé - object type
|
No
|
-
|
-
|
Mand.
|
DAM+003/004 - DOD+xxx
|
||
| 40 |
Claimant - Dommage financier/moral - Objet endommagé - object instance identifier
|
No
|
-
|
-
|
Option.
|
DAM+003/004 - DOD+xxx+x--x:002/003
|
||
| 50 |
Claimant - Dommage financier/moral - Objet endommagé - object instance name
|
No
|
-
|
-
|
Option.
|
DAM+003/004 - DOD+xxx+:::x--x
|
||
(*) n u d : new / updated / deleted since previous version.
(*bis) u : updated : this can be a codelist-version incrementing.
Note that in many, not to say all such cases, the user-community does not await such next release to implement/activate such new codelist-values.
The reasoning is that such added value does not affect the current data-structures and hence is considered easely implementable.
Such reasoning tends to forget how given new codelist-values might not simply affect the data, but also affect the process, which might be more of a problem...
(**) 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.