SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : EROD020 - Echange contextuel, données terrain - (Données terrain / Gegevens terrein)
- Approved
, and is part of release 202101 - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender : Any
Receiver : Any
Status : 2 - Version : 1
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 5 |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
ObjectInsuredTerrain
|
||
| 10 |
Adresse optimisée sur base de
|
Yes
|
1
|
Option.
|
info: a better alternative is to use X099 in segment ADR
|
AddressOptimisedBasedUponProcesscode
|
||
| 20 |
Adresse - rue
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail StreetName
|
||
| 30 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail HouseNumber
|
||
| 40 |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail BoxNumber
|
||
| 50 |
Adresse - extension
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail AddressExtension
|
||
| 60 |
Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail AddressIdentifier
|
||
| 70 |
Adresse - code postal
|
No
|
-
|
-
|
Option.
|
OfficialAddress PostalCode
|
||
| 80 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
OfficialAddress CityName
|
||
| 90 |
Adresse - code pays
|
No
|
-
|
-
|
Option.
|
OfficialAddress CountryCoded
|
||
| 100 |
Surface
|
No
|
-
|
-
|
Option.
|
SurfaceAreaQuantity
|
||
| 110 |
Longueur
|
No
|
-
|
-
|
Option.
|
LengthQuantity
|
||
| 120 |
Largeur
|
No
|
-
|
-
|
Option.
|
WidthQuantity
|
||
| 130 |
Usage
|
Yes
|
0
|
Option.
|
||||
| 140 |
Type de plantation
|
Yes
|
0
|
Option.
|
||||
| 150 |
Localisation
|
No
|
-
|
-
|
Option.
|
LocationText
|
||
(*) 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.