SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 201001 : Identifier : RODGEN - - (Données communes objets de risque / Algemene gegevens risico-object) - ( TB2-UN/Edifact MIG : Fr / Nl ) - (UN/Edifact & XML/JSON : added info ) |
Sender :
Receiver :
Status : 3 - Version : 5
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 UN/EDIFACT representation |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
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)
|
ROD+xxx
|
|
| 20 | u |
Garantie
|
No
|
-
|
-
|
Mand.
|
Completed with ICDGEN.v4
|
ICD+xxx
|
| 30 |
Sous-objet de risque
|
No
|
-
|
-
|
Option.
|
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.