Message Content Inventory |
Archived, and was part of release 201201 : Identifier : RODGEN - - (Données communes objets de risque / Algemene gegevens risico-object) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender :
Receiver :
Status : 3 - Version : 7
|
Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
10 | u |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
Generic- possibly completed with one of (ROD001.v4 / ROD002.v4 / ROD01x.v5 / ROD030.v3 / ROD04x.v2 / ROD05x.v2 / ROD060.v2 / ROD090.v2 / ROD149.v2)
|
ObjectInsured...
|
20 | u |
Garantie
|
No
|
-
|
-
|
Mand.
|
0..n presencies / Completed with ICDGEN.v6
|
Guarantee...
|
30 |
Sous-objet de risque
|
No
|
-
|
-
|
Option.
|
0..n presencies
|
Subobject...
|
(*) 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.
(***) Remark: In 2020 things evolved into another "approach A" and then yet another "approach B" - It is that "appoach B" which you see here - That "approach B" is the basis of the EDIMERX development.
In TB2-XML "Namespace 2018" (as well as in eEG7-UN/CEFACT), things were/are structurally different.
EDIMERX is supporting the transition from Edifact (messages) to JSON (API's).
The so-called "Business API's" are what comes next / after such transition-phase - and there things will be structurally differrent again.