Syntax Independent Components
Implementation Related Components
Implementation Related Components
|
|
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Identifier : RODGEN - - (Données communes objets de risque / Algemene gegevens risico-object) - ( UN/Edifact MIG : Fr / Nl ) |
Version : 3 Status : 3 |
| n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
XML-tag |
UN/EDIFACT representation (including comments) |
||
Indicator |
Identifier |
Version |
||||||
u |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
Generic- possibly completed with one of (ROD001.v2 / ROD002.v2 / ROD01x.v3 / ROD030.v2 / ROD04x.v1 / ROD05x.v1 / ROD060.v1 / ROD090.v2 / ROD149.v2)
|
InsuranceObject
|
ROD+xxx
|
u |
Garantie
|
No
|
-
|
-
|
Mand.
|
Completed with ICDGEN.v3
|
Guarantee
|
ICD+xxx
|
Sous-objet de risque
|
No
|
-
|
-
|
Option.
|
InsuranceObject withSubObject isObject
|
SRO+xxx
|
||
(*) 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.