> Syntax independent - MCIs - Messages > Details
SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
|
> Syntax independent - MCIs - Messages > Details
|
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : DPTDAMDOD010 - - (Claimant - Damage - Damaged object - données bâtiment) - Approved , and is part of release 201501 - ( TB2-UN/Edifact MIG : Fr / Nl ) - ( TB2-XML : added info ) |
Version : 1 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 - Damaged construction
|
No
|
-
|
-
|
Mand.
|
DOD+010
|
||
| 20 |
Claimant - Damage - Damaged construction - object instance identifier
|
No
|
-
|
-
|
Option.
|
DOD+010+x--x:002/003
|
||
| 30 |
Claimant - Damage - Damaged construction - object instance name
|
No
|
-
|
-
|
Option.
|
DOD+010+:::x--x
|
||
| 40 |
Claimant - Damage - Damaged construction - Montant règle proportionnelle
|
No
|
-
|
-
|
Option.
|
DOD+010 - MOA+073:9--9:EUR:2:001+x--x:9--9:2+9--9:2
|
||
| 50 |
Claimant - Damage - Damaged construction - Montant vétusté
|
No
|
-
|
-
|
Option.
|
DOD+010 - MOA+074:9--9:EUR:2:001+x--x:9--9:2+9--9:2
|
||
| 60 |
Claimant - Damage - Damaged construction - Lieu de visite
|
No
|
-
|
-
|
Option.
|
DOD+010 - FTX+027+x--x:x--x:x--x:x--x: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.