Master Data
Vessel Name
The vessel name should correspond to the vessel's IMO. It should be specified in the master data like so:
JSON-LD Example: "cbvmda:vesselName": "BING Ship",
Vessel Flag
The vessel flag should be represented by its 2-digit ISO Country Code:
JSON-LD Example: "cbvmda:vesselFlagState": "US",
Vessel ID
So that the vessel ID would not have to be repeated each time in the Vessel Catch Information, it's possible to just specify it in the master data like so:
JSON-LD Example: "cbvmda:vesselID": "ID123456789",
IMO Number
IMO number is a required attribute for GDST. It is expected that the IMO number will be recorded in the master data for the vessel.
JSON-LD Example: "gdst:imoNumber": "IMO.1234567890",
Vessel Public Registry
The vessel public registry is a required attribute for GDST. It is expected that the Vessel Public Registry will be recorded in the master data for the vessel.
JSON-LD Example: "gdst:vesselPublicRegistry": "https://www.register-my-vessel.fake.com",
Satellite Tracking Authority
Satellite tracking authority is a required attribute for GDST. It is expected that the Satellite Tracking Authority will be recorded in the master data for the vessel.
JSON-LD Example: "gdst:satelliteTrackingAuthority" : "https://vessel_tracking.com/vessel/1233213"
Notes on EPCIS Conformance
The CBV 1.2 documentation states that:
https://www.gs1.org/sites/default/files/docs/epc/CBV-Standard-1-2-2-r-2017-10-12.pdf
The key word here is SHOULD NOT which means that is recommended that this is not practiced. However, at the time of defining the Vessel Flag, Vessel ID, and Vessel Name, it was not expected that the Fishing, Transshipment, and Landing events would be recorded. So they defined these KDEs in the ILMD section so that the first transformation event could record this vessel information. Now that we are recording the Fishing, Transshipment, and Landing events, it makes no sense to record these KDEs in the ILMD section, when they rarely change. It is much easier to record them in the master data associated with the GLN of the vessel/port.Master Data Elements in the Basic Universal List of Key Data Elements
As these attributes are static among event-level data, they are intended to be represented in the master data header. These attributes are included in GS1's Addition of Attributes for Fish Traceability
Vessel Name
The vessel name should correspond to the vessel's IMO. It should be specified in the master data like so:
JSON-LD Example: "cbvmda:vesselName": "BING Ship",
Vessel Flag
The vessel flag should be represented by its 2-digit ISO Country Code:
JSON-LD Example: "cbvmda:vesselFlagState": "US",
Vessel ID
So that the vessel ID would not have to be repeated each time in the Vessel Catch Information, it's possible to just specify it in the master data like so:
JSON-LD Example: "cbvmda:vesselID": "ID123456789",
IMO Number
IMO number is a required attribute for GDST. It is expected that the IMO number will be recorded in the master data for the vessel.
JSON-LD Example: "gdst:imoNumber": "IMO.1234567890",
Vessel Public Registry
The vessel public registry is a required attribute for GDST. It is expected that the Vessel Public Registry will be recorded in the master data for the vessel.
JSON-LD Example: "gdst:vesselPublicRegistry": "https://www.register-my-vessel.fake.com",
Satellite Tracking Authority
Satellite tracking authority is a required attribute for GDST. It is expected that the Satellite Tracking Authority will be recorded in the master data for the vessel.
JSON-LD Example: "gdst:satelliteTrackingAuthority" : "https://vessel_tracking.com/vessel/1233213"
Notes on EPCIS Conformance
The CBV 1.2 documentation states that:
https://www.gs1.org/sites/default/files/docs/epc/CBV-Standard-1-2-2-r-2017-10-12.pdf
The key word here is SHOULD NOT which means that is recommended that this is not practiced. However, at the time of defining the Vessel Flag, Vessel ID, and Vessel Name, it was not expected that the Fishing, Transshipment, and Landing events would be recorded. So they defined these KDEs in the ILMD section so that the first transformation event could record this vessel information. Now that we are recording the Fishing, Transshipment, and Landing events, it makes no sense to record these KDEs in the ILMD section, when they rarely change. It is much easier to record them in the master data associated with the GLN of the vessel/port.
