SYNTAX INDEPENDENT
COMPONENTS
Implementation Related Components
SYNTAX INDEPENDENT
COMPONENTS |
|
| Message Content Inventory |
Identifier : EROD003 - Echange contextuel, données engin nautique - (Données engin nautique)
- 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 : 3
|
| Seq. n° | n u d (*) |
Data element | Code list |
Usage Mandatory Conditional Optional (**) |
Condition(s) |
TB2 XML and JSON representation (***) |
||
Indicator |
Identifier |
Version |
||||||
| 10 |
Contrat
|
No
|
-
|
-
|
Mand.
|
|||
| 20 |
Riskobject, type
|
No
|
-
|
-
|
Mand.
|
ObjectInsuredVessel
|
||
| 30 |
Bateau, nom
|
No
|
-
|
-
|
Mand.
|
OfficialName NameDetail LastName
|
||
| 40 |
Bateau, marque
|
No
|
-
|
-
|
Option.
|
MakeModelTypeName NameDetail LastName
|
||
| 50 |
Bateau, marque et modèle
|
No
|
-
|
-
|
Option.
|
MakeModelTypeName NameDetail LastName FirstName
|
||
| 60 |
Bateau, pays de construction (code et nom)
|
No
|
-
|
-
|
Option.
|
ConstructionAddress CountryCoded CountryName
|
||
| 70 |
Bateau, année de construction
|
No
|
-
|
-
|
Option.
|
ProductionYear
|
||
| 80 |
Bateau, numéro d'identification de la coque
|
No
|
-
|
-
|
Option.
|
HullidentificationReference
|
||
| 90 |
Bateau, lettre de pavillon - code
|
No
|
-
|
-
|
Option.
|
CertificateOfColoursCodeReference
|
||
| 100 |
Bateau, lettre de pavillon - numéro
|
No
|
-
|
-
|
Option.
|
CertificateOfColoursNumberReference
|
||
| 110 |
Bateau, plaque d'immatriculation numéro
|
No
|
-
|
-
|
Option.
|
RegistrationPlateReference
|
||
| 120 |
Bateau, utilisation
|
Yes
|
1
|
Mand.
|
VesselUsageCode
|
|||
| 130 |
Bateau, type
|
Yes
|
1
|
Option.
|
VesselCode
|
|||
| 140 |
Bateau, gréement
|
Yes
|
1
|
Option.
|
RiggingCode
|
|||
| 150 |
Bateau, matériaux de construction principal
|
Yes
|
1
|
Option.
|
VesselConstructionmaterialsCode
|
|||
| 151 | n |
Bateau, a cabine
|
No
|
-
|
-
|
Option.
|
WithCabinBinary
|
|
| 160 |
Bateau, longueur hors tout en mètres
|
No
|
-
|
-
|
Option.
|
ShipTotalLenghtQuantity
|
||
| 170 |
Bateau, longueur de la coque en mètres
|
No
|
-
|
-
|
Option.
|
LengthQuantity
|
||
| 180 |
Bateau, largeur de la coque en mètres
|
No
|
-
|
-
|
Option.
|
WidthQuantity
|
||
| 190 |
Bateau, tirant d'eau en mètres
|
No
|
-
|
-
|
Option.
|
DraughtQuantity
|
||
| 200 |
Bateau - Certificat de navigation, nom
|
No
|
-
|
-
|
Option.
|
Multiple documents are a possibility
|
DocumentCertificateOfNavigability
|
|
| 210 |
Bateau - Certificat de navigation, date de début de validité
|
No
|
-
|
-
|
Option.
|
ValidityStartDate
|
||
| 220 |
Bateau - Certificat de navigation, date de fin de validité
|
No
|
-
|
-
|
Option.
|
ExpirationDate
|
||
| 230 |
Bateau - Certificat de navigation, mediafile
|
No
|
-
|
-
|
Option.
|
...Datafile MultimediaDetail MultimediafileName MIMElikeContentTransferEncoding DatastringLength Datastring
|
||
| 240 |
Bateau - Port d'attache, nom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail LastName
|
||
| 250 |
Bateau - Chantier de construction, nom
|
No
|
-
|
-
|
Option.
|
OfficialName NameDetail LastName
|
||
| 260 |
Garantie
|
No
|
-
|
-
|
Option.
|
0..n presencies
|
Guarantee...
|
|
| 270 |
Bateau - Moteur, marque
|
No
|
-
|
-
|
Option.
|
0..n presencies - Multiple engines are a possibility
|
MakeModelTypeName NameDetail LastName
|
|
| 280 |
Bateau - Moteur, marque et type
|
No
|
-
|
-
|
Option.
|
MakeModelTypeName NameDetail LastName FirstName
|
||
| 290 |
Bateau - Moteur, année de construction
|
No
|
-
|
-
|
Option.
|
ProductionYear
|
||
| 300 |
Bateau - Moteur, numéro de série
|
No
|
-
|
-
|
Option.
|
SerialNumberReference
|
||
| 310 |
Bateau - Moteur, installation
|
Yes
|
1
|
Option.
|
BoatMotorPlacementCode
|
|||
| 320 |
Bateau - Moteur, carburant
|
Yes
|
1
|
Option.
|
BoatMotorFueltypeCode
|
|||
| 330 |
Bateau - Moteur, description
|
No
|
-
|
-
|
Option.
|
DescriptionText
|
||
(*) 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.