SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Archived, and was part of release 200701 : Identifier : PTY003GRP - - (Données preneur d'assurance - Groupement de personnes / Gegevens verzekeringsnemer - Groepering van personen) - ( 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 |
||||||
| 4 |
Party, type
|
No
|
-
|
-
|
Mand.
|
PartyMainPolicyHolder
|
||
| 5 |
Nom officiel - Nom
|
No
|
-
|
-
|
Mand.
|
OfficialName
|
||
| 9 |
Nom officiel - Extension du nom
|
No
|
-
|
-
|
Option.
|
OfficialName
|
||
| 10 |
Code titre
|
Yes
|
0
|
Option.
|
OfficialName
|
|||
| 20 |
Adresse - rue
|
No
|
-
|
-
|
Mand.
|
AddressDetail StreetName
|
||
| 21 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Mand.
|
AddressDetail HouseNumber
|
||
| 22 |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
AddressDetail BoxNumber
|
||
| 23 |
Adresse - extension
|
No
|
-
|
-
|
Option.
|
AddressDetail AddressExtension
|
||
| 24 |
Adresse - identifiant
|
No
|
-
|
-
|
Option.
|
AddressDetail AddressIdentifier
|
||
| 25 |
Adresse - code postal
|
No
|
-
|
-
|
Mand.
|
PostalCode
|
||
| 26 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
CityName
|
||
| 27 |
Adresse - code pays
|
No
|
-
|
-
|
Option.
|
CountryCoded
|
||
| 55 |
Numéro du compte financier
|
No
|
-
|
-
|
Option.
|
AccountReference
|
||
| 60 |
Numéro IBAN
|
No
|
-
|
-
|
Option.
|
InternationalBankAccountNumberReference
|
||
| 75 |
Numéro de téléphone privé
|
No
|
-
|
-
|
Option.
|
PrivateTelephoneCommID
|
||
| 80 |
Numéro de fax
|
No
|
-
|
-
|
Option.
|
FaxCommID
|
||
| 85 |
Adresse boîte postale électronique
|
No
|
-
|
-
|
Option.
|
EmailAddressCommID
|
||
| 95 |
Personne physique ou morale
|
Yes
|
2
|
Mand.
|
NaturalOrLegalPersonCode
|
|||
| 105 |
Langue de communication
|
Yes
|
3
|
Mand.
|
LanguageCode
|
|||
| 110 |
Nationalité
|
Yes
|
6
|
Option.
|
NationalityCode
|
|||
| 125 | u |
Statut juridique
|
Yes
|
5
|
Option.
|
LegalFormCode
|
||
| 130 |
Statut social
|
Yes
|
5
|
Option.
|
SocialStatusCode
|
|||
| 135 |
Code commerce (NACEBEL)
|
Yes
|
1
|
Option.
|
BusinessCodeNacebelCode
|
|||
| 150 |
Instructions en cours
|
No
|
-
|
-
|
Option.
|
DeclarationInvestigationPending ResponseCoded
|
||
| 165 |
Assurance refusée, résiliée ou prolongée sous conditions
|
No
|
-
|
-
|
Option.
|
DeclarationInsuranceRefusedOrEndedOrExtendedUnderCircumstances ResponseCoded
|
||
| 175 |
Assurance refusée, résiliée ou prolongée sous conditions - Type de difficulté
|
Yes
|
1
|
Option.
|
ResponseTypeOfDifficulty ResponseDetail ResponseDetailValueCoded
|
|||
(*) 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.