Syntax Independent Components
Implementation Related Components
Implementation Related Components
Syntax Independent Components
Implementation Related Components |
| Message Content Inventory |
Archived, and was part of release 200701 : Identifier : ROD01x - - (Données bâtiment/contenu / Gegevens gebouw/inhoud) - ( TB2-XML/JSON MIG : Fr/Nl are under construction... ) - (UN/Edifact & XML/JSON : added info ) |
Sender :
Receiver :
Status : 3 - Version : 2
|
| 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.
|
ObjectInsured...
|
||
| 10 |
Situation du risque est adresse du preneur
|
Yes
|
1
|
Option.
|
LocationIsPolicyHolderAddressProcesscode
|
|||
| 15 |
Situation du risque - rue
|
No
|
-
|
-
|
Option.
|
RiskAddress AddressDetail StreetName
|
||
| 20 |
Situation du risque - numéro de maison
|
No
|
-
|
-
|
Option.
|
RiskAddress AddressDetail HouseNumber
|
||
| 25 |
Situation du risque - numéro de boîte
|
No
|
-
|
-
|
Option.
|
RiskAddress AddressDetail BoxNumber
|
||
| 26 | n |
Situation du risque - extension adresse
|
No
|
-
|
-
|
Option.
|
RiskAddress AddressDetail AddressExtension
|
|
| 27 | n |
Situation du risque - identifiant
|
No
|
-
|
-
|
Option.
|
RiskAddress AddressDetail AddressIdentifier
|
|
| 30 |
Situation du risque - code postal
|
No
|
-
|
-
|
Option.
|
RiskAddress PostalCode
|
||
| 35 |
Situation du risque - localité
|
No
|
-
|
-
|
Option.
|
RiskAddress CityName
|
||
| 40 |
Situation du risque - code pays
|
No
|
-
|
-
|
Option.
|
RiskAddress CountryCoded
|
||
| 45 |
Année de construction
|
No
|
-
|
-
|
Option.
|
ProductionYear
|
||
| 50 |
Date de livraison provisoire
|
No
|
-
|
-
|
Option.
|
TemporaryDeliveryDate
|
||
| 55 |
Usage de l'immeuble
|
Yes
|
3
|
Option.
|
BuildingUsageCode
|
|||
| 56 | n |
Affectation du bâtiment
|
Yes
|
1
|
Option.
|
ConstructionUsageCode
|
||
| 57 | n |
Genre du bâtiment
|
Yes
|
1
|
Option.
|
ConstructionNatureCode
|
||
| 60 |
Code commerce (NACEBEL)
|
Yes
|
1
|
Option.
|
BusinessCodeNacebelCode
|
|||
| 65 | u |
Qualité du preneur d'assurance
|
Yes
|
4
|
Mand.
|
pour le contenu la zone est optionnelle
|
PolicyHolderCategoryCode
|
|
| 70 |
Système d’évaluation
|
Yes
|
6
|
Option.
|
BuildingValuationSystemCode
|
|||
| 71 |
Type d'habitation
|
Yes
|
7
|
Option.
|
DwellingCode
|
|||
| 72 | u |
Type d'habitation - détail
|
Yes
|
2
|
Option.
|
DwellingDetailCode
|
||
| 73 |
Type de résidence
|
Yes
|
1
|
Option.
|
ResidenceCode
|
|||
| 74 |
Type de construction
|
Yes
|
2
|
Option.
|
ConstructionCode
|
|||
| 75 |
Type de préfabriqué
|
Yes
|
1
|
Option.
|
PrefabCode
|
|||
| 76 |
Type de toiture
|
Yes
|
3
|
Option.
|
RoofCode
|
|||
| 77 |
Type de toiture - détail
|
Yes
|
1
|
Option.
|
RoofDetailCode
|
|||
| 78 |
Contiguïté
|
Yes
|
5
|
Option.
|
ContiguityCode
|
|||
| 79 | u |
Type protection et prévention (Vol))
|
Yes
|
4
|
Option.
|
Occurs 6 times
|
RecognitionOfTheAlarmUPEACode
|
|
| 80 |
Degré d'occupation
|
Yes
|
4
|
Option.
|
DegreeOfOccupationCode
|
|||
| 81 | n |
Type d'abandon de recours
|
Yes
|
4
|
Option.
|
AppealDroppedCode
|
||
| 105 |
Bâtiment en construction
|
No
|
-
|
-
|
Option.
|
BuildingUnderConstructionBinary
|
||
| 115 |
Habitation préfabriquée
|
No
|
-
|
-
|
Option.
|
PrefabricatedDwellingBinary
|
||
| 125 |
Bâtiment équivalent à nouvelle construction
|
No
|
-
|
-
|
Option.
|
BuildingEquivalentToNewConstructionBinary
|
||
| 140 |
Bâtiment contigu
|
No
|
-
|
-
|
Option.
|
AdjacentBuildingBinary
|
||
| 155 |
Bâtiment à plusieurs appartements
|
No
|
-
|
-
|
Option.
|
BuildingWithSeveralApartmentsBinary
|
||
| 170 |
Présence d'une ensiegne
|
No
|
-
|
-
|
Option.
|
PresenceOfANeonLightBinary
|
||
| 185 |
Bâtiment en matériaux combustibles
|
No
|
-
|
-
|
Option.
|
BuildingWithCombustibleMaterialsBinary
|
||
| 195 |
Eléments portants en matériaux combustibles
|
No
|
-
|
-
|
Option.
|
ElementsWithCombustibleMaterialsBinary
|
||
| 200 |
Présence d'un système de protection vol
|
No
|
-
|
-
|
Option.
|
BuildingWithBurglaryProtectionSystemBinary
|
||
| 210 |
Présence d'un système de protection incendie
|
No
|
-
|
-
|
Option.
|
BuildingWithFireProtectionSystemBinary
|
||
| 220 |
Présence d'une antenne
|
No
|
-
|
-
|
Option.
|
BuildingWithAntennaBinary
|
||
| 225 |
Présence d'une plate-forme en matériaux combustibles
|
No
|
-
|
-
|
Option.
|
PlatformMadeOfCombustibleMaterialsBinary
|
||
| 230 |
Véhicule compris dans le risque
|
No
|
-
|
-
|
Option.
|
VehicleIncludedOrIncorporatedInRiskObjectBinary
|
||
| 235 |
Bâtiment avec concierge résident
|
No
|
-
|
-
|
Option.
|
BuildingWithResidentCaretakerBinary
|
||
| 236 | u |
Valeur enseigne lumineuse
|
No
|
-
|
-
|
Option.
|
NeonSignValueAmount
|
|
| 237 | u |
Valeur vitres
|
No
|
-
|
-
|
Option.
|
ValueOfWindowGlassAmount
|
|
| 238 | u |
Résultat grille
|
No
|
-
|
-
|
Option.
|
CalculationTableResultAmount
|
|
| 239 | u |
Capital
|
No
|
-
|
-
|
Option.
|
CapitalAmount
|
|
| 244 |
Nombre d'appartements
|
No
|
-
|
-
|
Option.
|
ApartmentsQuantity
|
||
| 245 |
Nombre d'étages
|
No
|
-
|
-
|
Option.
|
FloorsQuantity
|
||
| 250 |
Nombre de m2 d'enseignes
|
No
|
-
|
-
|
Option.
|
SquareMetresOfSignsQuantity
|
||
| 255 |
Nombre de pièces
|
No
|
-
|
-
|
Option.
|
PlacesQuantity
|
||
| 260 |
Nombre d'ascenseurs
|
No
|
-
|
-
|
Option.
|
LiftsQuantity
|
||
| 265 |
Nombre de monte-charge
|
No
|
-
|
-
|
Option.
|
HoistsQuantity
|
||
| 270 |
Surface toit vitré
|
No
|
-
|
-
|
Option.
|
GlassRoofQuantity
|
||
| 275 |
Superficie
|
No
|
-
|
-
|
Option.
|
SurfaceAreaQuantity
|
||
| 280 |
Distance entre bâtiments
|
No
|
-
|
-
|
Option.
|
DistanceBetweenBuildingsQuantity
|
||
| 285 | n |
Nombre de nuits d'absence maximum par an
|
No
|
-
|
-
|
Option.
|
MaximalAnnualNightsAbsentQuantity
|
|
| 290 | n |
Nombre de nuits d'absence consécutifs
|
No
|
-
|
-
|
Option.
|
SubsequentNightsUninhabitedQuantity
|
|
| 295 |
Pourcentage matériaux combustibles
|
No
|
-
|
-
|
Option.
|
CombustibleMaterialsPercentage
|
||
| 300 |
Créancier
|
No
|
-
|
-
|
Option.
|
PartyCreditor
|
||
| 305 |
Créancier - Nom officiel
|
No
|
-
|
-
|
Mand.
|
OfficialName
|
||
| 310 |
Créancier - Adresse - rue
|
No
|
-
|
-
|
Mand.
|
AddressDetail StreetName
|
||
| 315 |
Créancier - Adresse - numéro de maison
|
No
|
-
|
-
|
Mand.
|
AddressDetail HouseNumber
|
||
| 320 |
Créancier - Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
AddressDetail BoxNumber
|
||
| 325 |
Créancier - Adresse - extension
|
No
|
-
|
-
|
Option.
|
AddressDetail AddressExtension
|
||
| 330 |
Créancier - Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
AddressDetail AddressIdentifier
|
||
| 335 |
Créancier - Adresse - code postal
|
No
|
-
|
-
|
Mand.
|
PostalCode
|
||
| 340 |
Créancier - Adresse - localité
|
No
|
-
|
-
|
Option.
|
CityName
|
||
| 345 |
Créancier - Adresse - code pays
|
No
|
-
|
-
|
Option.
|
CountryCoded
|
||
| 350 |
Créancier - Numéro du dossier
|
No
|
-
|
-
|
Option.
|
FileReference
|
||
| 355 |
Créancier - Type de créancier
|
Yes
|
1
|
Option.
|
CreditorCode
|
|||
| 360 |
Garantie
|
No
|
-
|
-
|
Mand.
|
Guarantee...
|
||
| 365 |
Sous-objet de risque
|
No
|
-
|
-
|
Option.
|
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.