SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : M9101 - Description d'un courtier opérationnel, envoi / Beschrijving operationele makelaar, zending - (As in Community MIG's - Divers : Courtier opérationnel / Diversen : Operationeel makelaar)
- Approved
, and is part of release 2005pre - (UN/Edifact & XML/JSON : added info ) |
Sender : Portima
Receiver : Insurer
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 |
||||||
| 10 |
Description d'un intervenant
|
No
|
-
|
-
|
Mand.
|
|||
| 20 |
Nom officiel
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail LastName
|
||
| 30 |
Adresse - rue
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail StreetName
|
||
| 40 |
Adresse - numéro de maison
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail HouseNumber
|
||
| 50 |
Adresse - numéro de boîte
|
No
|
-
|
-
|
Option.
|
OfficialAddress AddressDetail BoxNumber
|
||
| 60 |
Adresse - code postal
|
No
|
-
|
-
|
Option.
|
OfficialAddress PostalCode
|
||
| 70 |
Adresse - localité
|
No
|
-
|
-
|
Option.
|
OfficialAddress CityName
|
||
| 80 |
Adresse - code pays
|
No
|
-
|
-
|
Option.
|
OfficialAddress CountryCoded
|
||
| 90 |
Date de désaffiliation AS/1
|
No
|
-
|
-
|
Option.
|
As1UnsubscriptionDate
|
||
| 100 |
Date de formation AS/1
|
No
|
-
|
-
|
Option.
|
As1CourseFollowedDate
|
||
| 110 |
Date d'affiliation AS/2
|
No
|
-
|
-
|
Option.
|
As2SubscriptionDate
|
||
| 120 |
Date opérationnelle AS/2
|
No
|
-
|
-
|
Option.
|
As2OperationalDate
|
||
| 130 |
Date de désaffiliation AS/2
|
No
|
-
|
-
|
Option.
|
As2UnsubscriptionDate
|
||
| 140 |
Numéro d'affiliation Assurnet
|
No
|
-
|
-
|
Option.
|
RegistrationNumberAssurnetReference
|
||
| 150 |
Numéro de téléphone privé
|
No
|
-
|
-
|
Option.
|
PrivateTelephoneCommID CommunicationChannelNumber
|
||
| 160 |
Langue de communication
|
Yes
|
3
|
Option.
|
LanguageCode
|
|||
| 170 |
Texte de communication
|
No
|
-
|
-
|
Option.
|
CommunicationText
|
||
| 180 |
Correspondant
|
No
|
-
|
-
|
Option.
|
RelatedCorrespondentOrManager
|
||
| 190 |
Correspondant - Nom officiel
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail LastName
|
||
| 200 |
Description d'un intervenant
|
No
|
-
|
-
|
Mand.
|
|||
(*) 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.