EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
ANNEX B : EUCISE2020 Data Model
Annex B.1 SV-11 EUCISE2020 LOGICAL DATA MODEL………………………………….………………………..2
1. EUCISE2020 CORE DATA SPECIFICATIONS…………………………………………………………………………3
2. ENTITY CORE ENTITY………………………………………………………………………………………………………..4
3. ACTION CORE ENTITY…….………………………………………………………………………………………………..5
4. AGENT CORE ENTITY………………………………………………………………………………………………………..9
5. ANOMALY CORE ENTITY…………………………………………………………………………………………………16
6. CARGO CORE ENTITY……………………………………………………………………………………………………..18
7. DOCUMENT CORE ENTITY……………………………………………………………………………………………..32
8. EVENT CORE ENTITY………………………………………………………………………………………………………65
9. INCIDENT CORE ENTITY ………………………………………………………………………………………………..70
10. LOCATION CORE ENTITY ………………………………………………………………………………………………..90
11. METADATA CORE ENTITY ……………………………………………………………………………………………..102
12. MOVEMENT CORE ENTITY …………………………………………………………………………………………..106
13. OBJECT CORE ENTITY …………………………………………………………………………………………………..108
14. OPERATIONAL ASSET CORE ENTITY………………………………………………………………………………116
15. ORGANIZATION CORE ENTITY ……………………………………………………………………………………..122
16. PERIOD CORE ENTITY ………………………………………………………………………………………………….148
17. PERSON CORE ENTITY …………………………………………………………………………………………………151
18. RISK CORE ENTITY ……………………………………………………………………………………………………….157
19. UNIQUEIDENTIFIER CORE ENTITY ………………………………………………………………………………..161
20. VESSEL CORE ENTITY …………………………………………………………………………………………………..163
21. REFERENCES…………………………………………………………………………………………………………………174
Annex B.2 XML SCHEMAS FOR THE EUCISE2020 CORE DATA SPECIFICATIONS…………………..178
1. DOCUMENT METADATA……………………………………………………………………………………………….179
2. SCHEMAS..…………………………………………………………………………………………………………………..180
EUCISE2020
Page 1 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
ANNEX B.1
EUCISE2020
SV-11 EUCISE2020 LOGICAL DATA MODEL
Page 2 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
1. EUCISE2020 Core Data Specifications
The EUCISE2020 Data Model is based on the CISE Data Model version 1.0 which was defined
in the Cooperation Project.
The CISE Data Model designed in Coop Project identified seven core data entities (Agent,
Object, Location, Document, Event, Risk and Period) and eleven auxiliary ones (Vessel, Cargo,
OperationalAsset, Person, Organization, Movement, Incident, Anomaly, Action,
UniqueIdentifier and Metadata), which together represent the information exchanged in.
EUCISE2020 data model is based on the same data entities (7+11), but, in order to take into
account additional data sources (meteo-oceanographic), EUCISE2020 defined additional
attributes to some of the above mentioned data entities.
Consequently, EUCISE2020 :
 takes as reference the CISE data model defined in CoopProject ;
 does not enlarge the scope of such data model, maintaining the original data entities;
 adds attributes to selected data entities to ensure that EUCISE2020 services can be
implemented.
All the above improvements have been discussed in partnership with JRC.
Finally, the EUCISE2020 Data Model is licensed as Attribution-ShareAlike (CC BY-SA). This
license lets others remix, tweak, and build upon it even for commercial purposes, as long as
they credit the EUISE2020 Consortium and license their new creations under the identical
term.
For additional information please refer to : https://creativecommons.org/licenses/bysa/4.0/legalcode.
EUCISE2020
Page 3 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
2.
Entity Core Entity
2.1. UML models
2.2. Elements defined in the Core Vocabulary
2.2.1. Entity Class
Abtract class representing an entity of the CISE data model.
EUCISE2020
Page 4 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
3.
Action Core Entity
3.1. UML models
3.2. Elements defined in the Core Vocabulary
3.2.1. Action Class (subclass of Event)
It is a subclass of Event. The Action entity may be linked to Incident, Anomaly and can also be expressed taking
into account other entities as location, object, etc.
3.2.1.1. Attributes
UML Name
ActionStatus
Data type
ActionStatusType
ActionType
ActionType
Mission
MissionType
Priority
Identifier
ActionPriorityType
UniqueIdentifier
EUCISE2020
Description
Defines the current status of the
action. An action can be Canceled,
Completed, InProgress....
Many different action types can be
described
The mission associated with the
action.
Example
InProgress
The Action priority
Identifier of the event.
Each UniqueIdentifier can be
correlated with other
UniqueIdentifiers, either manually,
High
Rescue
MIL
Source
CWA
159311:2009
EUROSUR
CWA
159311:2009
Page 5 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Metadata
Metadata
NatureType
NatureType
Description
by operators, or automatically, by
systems, so that duplicate objects in
the network can be identified and
brought together for a better
understanding of the information
being shared.
see: Core Vocabularies Specification
for "Metadata"
Enumerated. Is used to define
nature of the event. An event can
be observed, declared, estimated or
simulated.
OccurrencePeriod Period
An Event occurs during a period of
time.
(*) Inherited attributes are coloured in grey.
Example
Source
see: Core
Vocabularies
Specification
for "Metadata"
for an
observed
event:
01
CISE
3.2.1.2. Association Roles
UML Name
Document
ImpliedRisk
InvolvedAgent
Data type
Document
Risk
Agent
Description
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class ObjectEvent.
InvolvedWith
Event
The association has additional attributes. Please check
association class EventEvent.
Location
Location
The association has additional attributes. Please check
association class EventLocation.
(*) Inherited association roles are coloured in grey.
Multiplicity
0..*
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
3.2.2. ActionPriorityType Enumeration
This enumeration presents the different priorities which can be assigned to an Action.
3.2.2.1. Enumeration Values
Value
01
02
03
98
99
Label
high
medium
low
other
non-specified
Description
Used to identify a high priority Action
Used to identify a medium priority Action
Used to identify a low priority Action
Action status not included above
Action status non-specified
Source
3.2.2.2. Enumeration Usage
The following attributes use this enumeration as data type:
 Priority (Action)
3.2.3. ActionStatusType Enumeration
In order to define the statuses associated to an action, we suggest reusing the work already done during the
"Tactical Situation Object" project. Among many artifacts, a list of action statuses has been defined. This
enumeration presents the possible statuses of an Action.
EUCISE2020
Page 6 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Source: CWA 15931-1:2009
3.2.3.1. Enumeration Values
Value
01
Label
aborted
Action aborted
Description
02
cancelled
Action canceled
03
completed
Action completed
04
in progress
05
not started
Action InProgress (2 additional digits - such as IPR50 - may provide
the percentage of completeness of the action)
Action is not started
06
paused
Action is paused
98
99
other
nonspecified
Action status not included above
Action status non-specified
Source
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
3.2.3.2. Enumeration Usage
The following attributes use this enumeration as data type:
 ActionStatus (Action)
3.2.4. ActionType Enumeration
This enumeration presents the possible types of Actions.
Source: EUROSUR
3.2.4.1. Enumeration Values
Value
01
02
03
04
Label
inspection
confirmation
rescue
deterrence
05
06
07
08
09
10
11
98
99
assistance
acknowledgment
exercise
search
detection
tracking
interception
other
non-specified
Description
A inspection action as defined in the EUROSUR system
A confirmation action
A rescue action as defined in the EUROSUR system
An action intended to dissuade an adversary from undertaking an
action not yet started
An assistance action.
An action resulting in an acknowledgement
An action defined as an exercise
A search action.
A detection action
A tracking action
An interception action
Action type not included above
Action type non-specified
Source
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
3.2.4.2. Enumeration Usage
The following attributes use this enumeration as data type:
 ActionType (Action)
3.2.5. MissionType Enumeration
EUCISE2020
Page 7 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
In order to define the type of mission associated to an action. We suggest reusing the work already done during
the "tactical situation object" project. Among many artifacts, a list of mission type has been defined.||During
the scope of the Cooperation project, we chose to limit the enumeration list to the first level defined by the
tactical situation object project. Sub-levels are also defined and their adoption could be considered in future
developments of the data model (see "Disaster and emergency management - Shared situation awareness Part 2: Codes for the message structure.").
Source: CWA 15931-1:2009
3.2.5.1. Enumeration Values
Value
Label
C2
CBRN
Description
Command & Control
FF
Activities related to chemical, bacteriological, radioactive and
nuclear substances
Fire Fighting missions
FSTT
Fire Services Technical Intervention
GEN
Generic activities
INT
Intelligence
MAC
Multi-agency Cooperation
MIL
Military activities
NET
Network and telecommunication activities
OPR
Use Operational Resources
POL
Police activities
REC
Reconstruction/rehabilitation activities
RSC
Rescue activities
SAV
Save and Rescue Endangered Life
SCS
Support Community Safety
SOC
Social and media/communication activities
Other
NonSpecified
other
nonspecified
Source
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
Mission type not included above
Mission type non-specified
3.2.5.2. Enumeration Usage
The following attributes use this enumeration as data type:
 Mission (Action)
EUCISE2020
Page 8 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
4.
Agent Core Entity
4.1. UML models
4.2. Elements defined in the Core Vocabulary
4.2.1. Agent Class (subclass of Entity)
The Agent is one of the core entities of the overall data model of the information sharing environment. By
definition, an Agent is an operative entity that plays a role in any Event, owns, handles or operates Objects such
as Cargo or Assets, creates and exploits Documents etc. It is an entity which holds information about individual
persons or organizations which are involved as actors or targets in the various events and activities. Agent can
have relationship with other agents, objects and locations. Agent can also be related to risks in different roles.
Agent is an abstract entity which has two sub-entities Person and Organization.
4.2.1.1. Attributes
UML Name
ContactInformation
EUCISE2020
Data type
String
Description
vCard [IETF RFC6350] is
a data format for
representing and
exchanging information
about individuals and
other entities. It is a
text-based format (as
opposed to a binary
format). xCard [IETF
RFC6351] is an XML
Example
Name of a person called Mr
John Brown, M.Sc.:
<fn><text>Mr John Brown,
M.Sc.</text></fn>
<n>
Source
IETF
RFC
6351
<surname>Brown</surname>
<given>John</given>
<additional/>
<prefix>Mr<prefix/>
Page 9 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Identifier
UniqueIdentifier
IsOfInterest
boolean
EUCISE2020
Description
representation for
vCard. All available
attributes are described
in the vCard document
[IETF RFC6350] and
listed bellow:
• General Properties
(BEGIN, END, SOURCE,
KIND, XML)
• Identification
Properties (FN, N,
NICKNAME, PHOTO,
BDAY, ANNIVERSARY,
GENDER)
• Delivery Addressing
Properties (ADR)
• Communications
Properties (TEL, EMAIL,
IMPP, LANG)
• Geographical
Properties (TZ, GEO)
• Organizational
Properties (TITLE, ROLE,
LOGO, ORG, MEMBER,
RELATED)
• Explanatory Properties
(CATEGORIES, NOTE,
PRODID, REV, SOUND,
UID, CLIENTPIDMAP,
URL, VERSION)
• Security Properties
(KEY)
• Calendar Properties
(FBURL, CALADRURI,
CALURI)
Identifier of the agent.
Each UniqueIdentifier
can be correlated with
other UniqueIdentifiers,
either manually, by
operators, or
automatically, by
systems, so that
duplicate objects in the
network can be
identified and brought
together for a better
understanding of the
information being
shared.
Attribute is flagging an
interest to follow more
closely any activities
Example
<suffix>M.Sc.<suffix/>
</n>
more examples found in: [IETF
RFC6351]
Source
0
Page 10 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
IsSuspect
boolean
Metadata
Metadata
Nationality
String
Description
related to the Agent.
Value of the attribute
can be either true or
false (true = 1 and false
= 0)
Attribute is flagging a
possible suspicion of
illegal activities related
to the Agent. Value of
the attribute can be
either true or false (true
= 1 and false = 0)
see: Core Vocabulary
Specification for
"Metadata"
Three-letter country
codes to represent
countries, dependent
territories, and special
areas of geographical
interest
Example
Source
There is some suspect related
to the agent:
1
DCMI
Portugal: PT
ISO
3166-1
(alpha2)
4.2.1.2. Association Roles
UML Name
Document
InvolvedEvent
Data type
Document
Event
InvolvedObject
Object
InvolvedRisk
Risk
InvolvedWith
Agent
Location
Location
Description
The association has additional attributes. Please check
association class AgentEvent.
The association has additional attributes. Please check
association class AgentObject.
The association has additional attributes. Please check
association class AgentRisk.
The association has additional attributes. Please check
association class AgentAgent.
The association has additional attributes. Please check
association class AgentLocation.
Multiplicity
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
4.2.2. AgentAgent Association Class
This class allows the association between two Agents (or one of their sub-classes: person, organization). It is not
mandatory to associate an Agent with another Agent but one Agent can be associated to multiple other Agents.
The association further describes the role of the Agent in relation to the other Agent. Crew members have also
a special relationship with the Organization inside the vessel company which is described by attribute Duty. This
attribute carries information about the responsibilities and position of the person in the vessel. The duration of
the relationship between the Agents is described by an association with class Period.
4.2.2.1. Attributes
UML Name
AgentRole
Data type
AgentRoleInAgentType
Duty
DutyType
EUCISE2020
Description
Enumerated - Describes the relationship
between Agents.
Person who leads an organization:
AgentRole
Attribute carries information about the
positions and responsibilities of
individual crew members.
Example
01
Source
31
NSW
Page 11 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
InvolvementPeriod
Data type
Period
Description
Defines the duration of the relationship
between the Agents.
Example
Source
4.2.3. AgentLocation Association Class
This class allows the association between Agent (or one of its sub-classes: person, organization) and Location. It
is not mandatory to associate an Agent with a Location but one Agent can be associated to multiple different
Locations. The association further describes the role of the Agent in relation to the Location. The duration of
the relationship between the Agent and the Location is described by an association with class Period.
4.2.3.1. Attributes
UML Name
AgentRole
Data type
AgentRoleInLocationType
InvolvementPeriod
Period
Description
Enumerated. Describes the
relationship between Agent and
Location; Place where the person was
born or
Defines the duration of the
relationship between the Agent and
the Location.
Example
04
Source
4.2.4. AgentObject Association Class
This class allows the association between Agent (or one of its sub-classes: person, organization) and Object (or
one of its sub-classes: Vehicle (Vessel, Aircraft, Landvehicle, CargoPackage). It is not mandatory to associate an
Agent with an Object but one Agent can be associated to multiple different Objects. The association further
describes the role of the Agent in relation to the Object. The special relationship between Passengers and Craft
is described by Boolean type attribute TransitPassanger which carries information about the status of the
passenger (Transit passenger or not) and by two associations with class Location. Crew members have also a
special relationship to Craft which is described by attribute Duty. This attribute carries information about the
responsibilities and position of the person in the vessel. The duration of the relationship between the Agent and
the Object is described by an association with class Period.
4.2.4.1. Attributes
UML Name
AgentRole
Data type
AgentRoleInObjectType
Duty
DutyType
InvolvementPeriod
TransitPassenger
Period
boolean
Description
Enumerated - Describes the
relationship between the Agent
and the Object.
Attribute carries information about
the positions and responsibilities of
individual crew members.
The period of involvement
Attribute is carrying information
about the voyage details of an
individual passenger. Is he/her a
transit passenger or not. Value of
the attribute can be either true or
false (true = 1 and false = 0)
Example
03
Source
31
NSW
In question
of a transit
passenger:
1
NSW
4.2.5. AgentRisk Association Class
This class allows the association between Agent (or one of its sub-classes) and Risk. It is not mandatory to
associate an Agent with a Risk but one Agent can be associated to multiple different Risks. The association
further describes the role of the Agent in relation to the Risk.
4.2.5.1. Attributes
EUCISE2020
Page 12 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
AgentRole
Data type
AgentRoleInRiskType
InvolvementPeriod
Period
Description
Enumerated - Describes the
relationship between Agent and
Risk.
The period of Involvement
Example
Person who is the
cause of the risk:
01
Source
4.2.6. AgentRoleInAgentType Enumeration
This enumeration presents the relationship between two Agents.
4.2.6.1. Enumeration Values
Value
01
02
03
04
05
98
99
Label
leads
works for
manages security CSO
encompasses
owns
other
non-specified
Description
Agent who leads the other Agent(s)
Agent who works for the other Agent(s)
Person who manages the security of an organization
Agent who encompasses the other Agent(s)
Person who owns the organization.
Any other role/relationship not mentioned above
Role not specified
Source
4.2.6.2. Enumeration Usage
The following attributes use this enumeration as data type:
 AgentRole (AgentAgent)
4.2.7. AgentRoleInLocationType Enumeration
This enumeration presents the relationship between Agent and Location.
4.2.7.1. Enumeration Values
Value
01
02
03
04
05
06
07
08
09
98
99
Label
owns
is located in
country of birth
place of birth
country of death
place of death
embarkation port
disembarkation port
country of residence
other
non-specified
Description
Owns the location
Is the (permanent) location of the agent
Is the country where the agent was birth
Is the place where the agent was birth
Is the country where the agent died
Is the place where the agent died
Port in which the agent embarked
Port in which the agent disembarked
The country in which the agent normally resides
Any other relationship not mentioned above
Relationship not specified
Source
4.2.7.2. Enumeration Usage
The following attributes use this enumeration as data type:
 AgentRole (AgentLocation)
4.2.8. AgentRoleInObjectType Enumeration
This enumeration presents the relationship between Agent and Object.
Source: NSW
4.2.8.1. Enumeration Values
EUCISE2020
Page 13 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
98
99
Label
owner
ship agent
passenger
crew member
captain master
ship operating company
company security officer
employee
vessel builder
vessel charterer
vessel registered owner
vessel company
shipping agent
declarant
carrier agent
shipping line
customs broker
DPG contact point
other
non-specified
Description
Owns the object
Is the agent of the object
Is a passenger of the object
Is a member of the crew of the object
Is the master of the object
Is the master of the object
Is the security officer of the company
Is an employee of the object
The Vessel Builder
The Vessel Charterer
The Vessel Registered Owner
The Vessel Company
Shipping agent of the goods
Declarant of the goods
Carrier agent of the goods
Shipping line for the goods
Customs broker of the goods
DGP (dangerous and polluting goods) contact point
Any other role not mentioned above
Role not specified
Source
NSW
NSW
NSW
WCO
WCO
WCO
WCO
WCO
NSW
4.2.8.2. Enumeration Usage
The following attributes use this enumeration as data type:
 AgentRole (AgentObject)
4.2.9. AgentRoleInRiskType Enumeration
This enumeration presents the role of Agent in relation to Risk.
4.2.9.1. Enumeration Values
Value
01
02
03
98
99
Label
cause
involved
reports
other
non-specified
Description
Agent is the cause of the risk
Agent is somehow involved in the risk
Agent is reporting of the risk
Any other relation not mentioned above
Relation not specified
Source
4.2.9.2. Enumeration Usage
The following attributes use this enumeration as data type:
 AgentRole (AgentRisk)
4.2.10.
DutyType Enumeration
This enumeration presents the role of Agent in relation to Risk.
Source: NSW
4.2.10.1. Enumeration Values
Value
001
002
003
004
EUCISE2020
Label
able seaman
agent
asst food bev mngr
bar manager
Description
Able Seaman
Agent
Assistant Food and Beverage Manager
Bar Manager
Source
NSW
NSW
NSW
NSW
Page 14 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
Label
Description
Source
005
bar service
Bar Service
NSW
WARNING: The current enumeration contains 105 values. The rest of the values can be found in the CISE Data
model.
4.2.10.2. Enumeration Usage
The following attributes use this enumeration as data type:
 Duty (AgentObject)

Duty (AgentAgent)
4.2.11.
ISO3166CountryCodeType Enumeration
contains the Codes Of Nationality according to ISO3166 Standard
Source: ISO 3166-1
4.2.11.1. Enumeration Values
Value
Label
Description
Source
AC
Ascension Island
ISO 3166-1
AD
Andorra
ISO 3166-1
AE
United Arab Emirates
ISO 3166-1
AF
Afghanistan
ISO 3166-1
AG
Antigua and Barbuda
ISO 3166-1
WARNING: The current enumeration contains 260 values. The rest of the values can be found in the CISE Data
model.
EUCISE2020
Page 15 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
5.
Anomaly Core Entity
5.1. UML models
5.2. Elements defined in the Core Vocabulary
5.2.1. Anomaly Class (subclass of Event)
The class Anomaly is a sub-class of the class Event. An anomaly is used to characterize an unusual event which
deserves to be noted or reported. Anomaly has the same associations and relationships than its parent-class
Event. Thus it can have relationship with Document, Risk, Event, Object, Period, Location, and Agent.
5.2.1.1. Attributes
UML Name
AnomalyType
Data type
AnomalyType
Description
The type of the reported anomaly
Identifier
UniqueIdentifier
Metadata
Metadata
Identifier of the event.
Each UniqueIdentifier can be correlated
with other UniqueIdentifiers, either
manually, by operators, or automatically,
by systems, so that duplicate objects in
the network can be identified and
brought together for a better
understanding of the information being
shared.
see: Core Vocabularies Specification for
"Metadata"
EUCISE2020
Example
Cargo leaking
Source
SSN
IRG
see: Core
Vocabularies
Specification for
"Metadata"
Page 16 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
NatureType
Data type
NatureType
Description
Enumerated. Is used to define nature of
the event. An event can be observed,
declared, estimated or simulated.
OccurrencePeriod Period
An Event occurs during a period of time.
(*) Inherited attributes are coloured in grey.
Example
for an observed
event:
01
Source
CISE
5.2.1.2. Association Roles
UML Name
Document
ImpliedRisk
InvolvedAgent
Data type
Document
Risk
Agent
Description
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class ObjectEvent.
InvolvedWith
Event
The association has additional attributes. Please check
association class EventEvent.
Location
Location
The association has additional attributes. Please check
association class EventLocation.
(*) Inherited association roles are coloured in grey.
Multiplicity
0..*
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
5.2.2. AnomalyType Enumeration
This enumeration presents the different types of anomalies.
Source: SSN IRG
5.2.2.1. Enumeration Values
Value
01
02
03
04
05
06
07
08
09
10
98
99
Label
unexpected movement
cargo leaking
shifting of cargo
vessel out of traffic lanes
vessel with erratic movements
stain of oil sighted
detecion of changes in AIS parameters
performing AIS spoofing
without AIS transmission
do not answer on VHF ch16
other
non-specified
Description
Unexpected movement
Cargo leaking
Shifting of cargo
Vessel out of traffic lanes
Vessel with erratic movements
Stain of oil sighted
Detection of changes in AIS parameters
Performing AIS spoofing
Without AIS transmission
Do not answer on VHF Ch 16
Any other anomaly type not mentioned above
Anomaly type not specified
Source
SSN IRG
5.2.2.2. Enumeration Usage
The following attributes use this enumeration as data type:
 AnomalyType (Anomaly)
EUCISE2020
Page 17 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
6.
Cargo Core Entity
6.1. UML models
6.2. Elements defined in the Core Vocabulary
6.2.1. Cargo Class (subclass of CargoUnit)
A Cargo refers to a set of goods transported by a ship between two ports.
6.2.1.1. Attributes
EUCISE2020
Page 18 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
CargoType
Data type
CargoType
Description
This enumeration is used to
described the type of cargo
associated with the entity
Colour
ColourType
Colour information about the
object
ExternalMarkings String
External markings of the object
Identifier
UniqueIdentifier Identifier of the object.
Each UniqueIdentifier can be
correlated with other
UniqueIdentifiers, either
manually, by operators, or
automatically, by systems, so that
duplicate objects in the network
can be identified and brought
together for a better
understanding of the information
being shared.
Metadata
Metadata
Metadata related to the object
Name
String
Name of the object
(*) Inherited attributes are coloured in grey.
Example
4
(Palletized)
Red
Source
UNECE
Recommendation
21 - annex II
EUROSUR
ABER
FLUX
ABERIII
NSW
6.2.1.2. Association Roles
UML Name
ContainedCargoUnit
Document
InvolvedAgent
Data type
CargoUnit
Document
Agent
InvolvedEvent
Event
InvolvedRisk
Location
Risk
Location
Description
The association has additional attributes. Please
check association class AgentObject.
The association has additional attributes. Please
check association class ObjectEvent.
The association has additional attributes. Please
check association class ObjectLocation.
(*) Inherited association roles are coloured in grey.
Multiplicity
0..*
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..*
0..* (allow
duplicates)
6.2.1.3. Constraints
Name
At least one
CargoUnit
OCL
Constraint
Description
There must be at least one CargoUnit or, alternatively, one type of
Catch to have a Cargo.
6.2.2. CargoUnit Class (subclass of Object)
CargoUnit is an entity which holds information about units of goods when transported by ships. The subclasses
of CargoUnit can represent either the whole cargo in a vehicle or a part of it.
6.2.2.1. Attributes
UML Name
Colour
ExternalMarkings
Identifier
EUCISE2020
Data type
ColourType
String
UniqueIdentifier
Description
Colour information about the object
External markings of the object
Identifier of the object.
Each UniqueIdentifier can be correlated with
other UniqueIdentifiers, either manually, by
operators, or automatically, by systems, so
Example
Red
ABER
Source
EUROSUR
FLUX
Page 19 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Description
that duplicate objects in the network can be
identified and brought together for a better
understanding of the information being
shared.
Metadata
Metadata
Metadata related to the object
Name
String
Name of the object
(*) Inherited attributes are coloured in grey.
Example
ABERIII
Source
NSW
6.2.2.2. Association Roles
UML Name
Document
InvolvedAgent
Data type
Document
Agent
InvolvedEvent
Event
InvolvedRisk
Location
Risk
Location
Description
The association has additional attributes. Please check
association class AgentObject.
The association has additional attributes. Please check
association class ObjectEvent.
The association has additional attributes. Please check
association class ObjectLocation.
(*) Inherited association roles are coloured in grey.
Multiplicity
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..*
0..* (allow
duplicates)
6.2.3. Catch Class (subclass of CargoUnit)
A Catch refers to a set of distinct species catch in the see/ocean by a fishing vessel. Catch has the same
associations and relationships than its parent-class Object. Thus it can have relationship with Document, Risk,
Event, Location, and Agent.
6.2.3.1. Attributes
UML Name
CatchWeight
Data type
double
FishNumber
int
NetHeld
double
QuantityHeld
double
SizeDeclaration
Species
double
SpeciesType
TotalNumber
TotalWeight
UniqueIdentifier
WeightMeans
int
double
UniqueIdentifier
WeightMeansType
Description
Depending on context this item to be
either
1. Total weight of fish (in kilograms) in
catch period
2. Total weight of fish (in kilograms) on
board (aggregate) or
3. Total weight of fish (in kilograms)
landed
4. Total weight of fish discarded or used
as a live bait
Number of fish (when catch have to be
registered in numbers of fish i.e.
salmon, tuna)
Estimate of number of live fish held in
nets i.e. not in hold
Estimate of quantity of live fish held in
nets i.e. not in hold
ERS/SizeDeclaration
This enumeration is used to specify the
type of species that were catch
see ERS::TotalNumber
see ERS::TotalWeight
Unique identifier for the catch
Means of weight measuring
Colour
ColourType
Colour information about the object
EUCISE2020
Example
Source
ERS
ERS
ERS
ERS
ERS
FLUX
ERS
ERS
EST
(estimation)
Red
ERS
EUROSUR
Page 20 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
ExternalMarkings
Identifier
Data type
String
UniqueIdentifier
Description
External markings of the object
Identifier of the object.
Each UniqueIdentifier can be correlated
with other UniqueIdentifiers, either
manually, by operators, or
automatically, by systems, so that
duplicate objects in the network can be
identified and brought together for a
better understanding of the information
being shared.
Metadata
Metadata
Metadata related to the object
Name
String
Name of the object
(*) Inherited attributes are coloured in grey.
Example
ABER
Source
FLUX
ABERIII
NSW
6.2.3.2. Association Roles
UML Name
Document
InvolvedAgent
Data type
Document
Agent
InvolvedEvent
Event
InvolvedRisk
Location
Risk
Location
Description
The association has additional attributes. Please check
association class AgentObject.
The association has additional attributes. Please check
association class ObjectEvent.
The association has additional attributes. Please check
association class ObjectLocation.
(*) Inherited association roles are coloured in grey.
Multiplicity
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..*
0..* (allow
duplicates)
6.2.4. ContainmentUnit Class (subclass of CargoUnit)
Containment unit is an entity which holds information about units of goods when transported by ships
contained in containers or bulk.
6.2.4.1. Attributes
UML Name
CommunityStatusOfGood
s
Data type
CommunityStatusType
ContainerMarksAndNumb
er
String
DangerousSubstancesCod
e
DangerousSubstancesTy
pe
EUCISE2020
Description
This enumeration
reflects the
different customs
status of cargo
units on board a
ship
Marks and
number of the
containers, this
shall be the
identification
code as defined
in ISO 6346
This enumeration
defines the
general
categories of
Hazardous cargo,
according to the
International
Maritime
Example
C
(community
goods)
Source
CSQU305438
3
NSW
class2.2
(toxic gases)
IMO IMDG
Page 21 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
FlashPoint
double
GrossQuantity
double
LocationOnBoardContain
er
String
LocationOnBoardGoods
String
NetQuantity
double
OtherMarksAndNumber
String
PackageType
PackageType
EUCISE2020
Description
Dangerous
Goods (IMDG)
code
Flash point in
degrees
centigrade. The
temperature in
degrees Celsius
at which a liquid
will give off
enough
flammable
vapour to be
ignited.
according IMDG
Code DG Class 3
Gross quantity of
the cargo unit
(includes
package)
Location of
container on
board.
Represented with
one upper case
letter (type of
location code), a
colon (:) and the
location code
(numerical or
other depending
of the type of
cargo). See
representation of
CargoLocationTy
pe in ISO 28005
Location of goods
on board
Net quantity of
the cargo unit
(excludes
package)
Marks and
number of the
cargo item if not
covered by ISO
6346
This enumeration
is used to
described the
type of package
used to carry the
cargo unit
Example
Source
NSW
NSW
C:010212
SSN MRG
SSN IRG
NSW
NSW
2 (rigid box
type
prismatic)
UNECE
Recommendatio
n 21
Page 22 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
PackagingMaterial
Data type
PackagingMaterialType
PackingGroupCode
PackingGroupCodeType
PollutionCode
PollutionCodeType
UNDG
UNDGType
UniqueIdentifier
UniqueIdentifier
UnitsOfMeasure
UnitsOfMeasureType
Colour
ColourType
ExternalMarkings
String
Identifier
UniqueIdentifier
EUCISE2020
Description
This enumeration
is used to
described the
type of material
of the package
used to carry the
cargo unit
This enumeration
defines the
danger code,
according to the
level of danger
This enumeration
defines the
pollution code,
according to the
MARPOL
Enumeration for
the United
Nations
Dangerous
Goods
The unique
identifier of the
CargoUnit
This enumeration
defines the units
of measurement
for both
GrossQuantity
and NetQuantity
Colour
information
about the object
External
markings of the
object
Identifier of the
object.
Each
UniqueIdentifier
can be correlated
with other
UniqueIdentifiers
, either manually,
by operators, or
automatically, by
systems, so that
duplicate objects
in the network
can be identified
and brought
together for a
Example
5 (metal)
Source
UNECE
Recommendatio
n 21
I (Great
danger)
IMO IMDG
X ( Noxious
Liquid
Substances)
IMO MARPOL annex II
0004
(AMMONIU
M PICRATE)
UNDG
KGM
(Kilogram)
UNECE
Recommendatio
n 20
Red
EUROSUR
ABER
FLUX
Page 23 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Metadata
Metadata
Name
String
Description
better
understanding of
the information
being shared.
Metadata related
to the object
Name of the
object
Example
ABERIII
Source
NSW
(*) Inherited attributes are coloured in grey.
6.2.4.2. Association Roles
UML Name
Document
InvolvedAgent
Data type
Document
Agent
InvolvedEvent
Event
InvolvedRisk
Location
Risk
Location
Description
The association has additional attributes. Please check
association class AgentObject.
The association has additional attributes. Please check
association class ObjectEvent.
The association has additional attributes. Please check
association class ObjectLocation.
(*) Inherited association roles are coloured in grey.
Multiplicity
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..*
0..* (allow
duplicates)
6.2.5. CargoType Enumeration
This enumeration presents the possible types of cargo.
Source: UNECE Recommendation 21 - annex II
6.2.5.1. Enumeration Values
Value
0
Label
no cargo unit
liquid bulk
goods
1
no cargo unit
solid bulk
goods
2
large freight
containers
3
other freight
containers
4
palletized
5
pre slung
EUCISE2020
Description
includes i) liquids ii) liquified gases iii) molten or slurried
solids, suitable for continuous mechanical handling for
transport by pipeline or loose in a hold, tank or other
compartment integral to a means of transport
includes i) fine powders ii) granular particles iii) large, lumpy,
dry solids, suitable for continuous mechanical handling, for
transport by fixed installations (other than pipeline) or loose
in a hold or other compartment integral to a means of
transport
Goods loaded in/on a freight container 20ft. (6m) or more in
external length; includes lift van, swap/swop body, flat,
moveable tank or similar articles of transport equipment
Goods loaded in/on a freight container less than 20 ft.(6m)
in external length; includes i) rigid Intermediate Bulk
Containers (IBCs) ii) aircraft Unit Load Devices (ULDs);
excludes i) air mode pallets ii) sea or land mode box-, tank-,
post, rack-pallets not exceeding 1.25 m2 deck area
Goods loaded on a deck; includes i) disposable one-way
pallets ii) sea or land mode box-, tank-, post-, rack-pallets
not exceeding 1.25 m2 deck area iii) slip-sheets iv) air mode
pallets v) bricks, ingots, etc. suitably assembled for fork-lift
truck handling
Goods (one or more items) supplied with a sling (or slings)
or various materials (natural/artificial fibre, steel wire, etc.)
and of various designs (loop, ring, cloverleaf, etc.); includes
Source
UNECE
Recommendation 21
- annex II
UNECE
Recommendation 21
- annex II
UNECE
Recommendation 21
- annex II
UNECE
Recommendation 21
- annex II
UNECE
Recommendation 21
- annex II
UNECE
Recommendation 21
- annex II
Page 24 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
Label
6
mobile selfpropelled
units
7
other mobile
units
8
9
reserved
other cargo
types
98
99
other
non-specified
Description
i) “packaged” timber ii) Flexible Intermediate Bulk
Containers (FIBCs)
includes i) road motor vehicles (lorries, buses, cars) and
accompanying trailers, semi-trailers, caravans engaged in
goods/passenger transport ii) motorised road, agricultural,
industrial, etc. vehicles moving in trade iii) live animals “on
the hoof”
non-self-propelled vehicles and equipment on wheels;
includes i) unaccompanied trailers, semi-trailers railwagons,
ship-borne barges engaged in goods transport ii) caravans
and other road, agricultural, industrial, etc. vehicles iii) shipborne port-to-port trailers
all cargo not elsewhere enumerated (i.e. the residual types
of cargo carried in transport: “break-bulk” or “general”
cargo, e.g. boxes, drums, bags, etc. and loose, unpacked
items such as pipes, rods, etc.)
Source
UNECE
Recommendation 21
- annex II
UNECE
Recommendation 21
- annex II
UNECE
Recommendation 21
- annex II
6.2.5.2. Enumeration Usage
The following attributes use this enumeration as data type:
 CargoType (Cargo)
6.2.6. CommunityStatusType Enumeration
This enumeration reflects the different customs status of cargo units on board a ship.
6.2.6.1. Enumeration Values
Value
C
Label
community goods
F
comunity goods
from non-fiscal
territories
X
community goods
being exported
other goods
non-specified
N
NonSpecified
Description
(equivalent to 'T2L') for goods whose community status can
be demonstrated
(equivalent to 'T2LF') for goods whose community status can
be demonstrated, consigned to or originating in a part of the
Community customs territory where the provisions of
Directive 77/388/EEC do not apply
For goods under the export procedure
Source
For all other goods
6.2.6.2. Enumeration Usage
The following attributes use this enumeration as data type:
 CommunityStatusOfGoods (ContainmentUnit)
6.2.7. DangerousSubstancesType Enumeration
This enumeration presents the general categories of Hazardous cargo, according to the International Maritime
Dangerous Goods (IMDG) code. For additional information about IBC, IGC and INF (IBC - Intermediate Bulk
Container, IGC - International Gas Carrier and INF - Irradiated Nuclear Fuel) contact the International Maritime
Organization (IMO).
Source: IMO IMDG
EUCISE2020
Page 25 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
6.2.7.1. Enumeration Values
Value
Class1
Label
class 1 explosives
Class21
Class31
class 2.1
flammable gases
class 2.2 toxic
gases
class 2.3 nonflammable
compressed gases
class 3.1 petrol
Class32
class 3.2 fuel oil
Class33
class 3.3 fuel oil
Class41
class 4.1
flammable solid
class 4.2
spontaneously
combustible
class 4.3
dangerous when
wet
class 5.1 oxidizing
agent
Class22
Class23
Class42
Class43
Class51
Class52
class 5.2 organix
peroxide
Class61
class 6.1 toxic
substances
Class62
class 6.2
infectious
biological
substances
class 7 radioactive
materials
Class7
Class8
EUCISE2020
class 8 corrosives
Description
Should be stored away from the crew’s quarters and the ship’s
boats and immediately under the hold’s hatches
Should be stored away from crew’s quarters and any source of
heat.
Should be stored away from any source of heat, the crew’s
quarters and foodstuffs.
Store on or under the deck in a cool, well-ventilated place.
Containers filled with this kind of gas will expand if heated
and there is a high risk of an explosion.
Combustion at less than 18ºC. Should always be stored above
the deck.
Combustion at between 18ºC and 23ºC. Should be stored
above or below the deck.
Combustion at between 23ºC and 61ºC. Should be stored
below the deck.
Should be stored on top or below the deck. Should be kept
away from living quarters.
Should be stored in well ventilated areas and air should be
able to circulate between the stored materials.
Source
IMO
IMDG
IMO
IMDG
IMO
IMDG
IMO
IMDG
Solids which are inflammable when wet or when in contact
with water. Should be stored in well ventilated, dry areas and
always away from any contact with water.
The substances in this category can create an inflammable
environment when brought into contact with oxygen. For this
reason they should not be stored next to combustible
materials.
The substances in this class can be inflammable or explosive.
They should be stored above deck, covered and in a dry, cool
areas.
Toxic substances are those which can enter the human body
through the mouth and cause death. For this reasons they
should be stored away from foodstuffs, drinks, living quarters
and materials which increase humidity, such as tobacco.
These substances contain microbes which can cause illness.
They should be stored away from foodstuffs, drinks and living
quarters. In case of danger the nearest health authority
should be notified.
Radioactive Materials - These materials should be transported
in specially sealed containers. The seals must always be
completely undamaged. They should preferably be stored
above deck and away from living quarters, foodstuffs,
unprocessed films, pharmaceuticals and chemical substances.
They are divided into three groups according to their level of
radioactivity.
The substances in this class are solids or liquids possessing, in
their original state, the common property of being able, more
or less severely to damage living tissue. The escape of such a
substance from its packaging may also cause damage to other
cargo or the ship.
IMO
IMDG
IMO
IMDG
IMO
IMDG
IMO
IMDG
IMO
IMDG
IMO
IMDG
IMO
IMDG
IMO
IMDG
IMO
IMDG
IMO
IMDG
IMO
IMDG
IMO
IMDG
Page 26 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
Class9
Label
class 9
miscellaneous
dangerous
substances
MHB
MHB materials
hazardous only in
bulk
Other
NonSpecified
other
non-specified
Description
Substances and articles not covered by other classes which
experience has shown, or may show, to be of such a
dangerous character that the provisions of SOLAS should
apply. These include substances that are transported or
offered for transport at temperatures equal to or exceeding
1000 C and in a liquid state, and solids that are transported at
temperatures equal or exceeding 2400 C;
MHB (materials hazardous only in bulk) cargoes are materials
which possess chemical hazards when transported in bulk that
do not meet the criteria for inclusion in the IMDG classes.
They are Combustible solids, Self-heating solids, Solids that
evolve into flammable gas when wet, Solids that evolve toxic
gas when wet, Toxic solids, Corrosive solids. See also IMSBC
code.
Any other dangerous substance type not mentioned above
Type not specified
Source
IMO
IMDG
IMO
IMDG
6.2.7.2. Enumeration Usage
The following attributes use this enumeration as data type:
 DangerousSubstancesCode (ContainmentUnit)
6.2.8. PackageType Enumeration
This enumeration presents the possible types of package used in CargoUnit.
Source: UNECE Recommendation 21 - annex IV
6.2.8.1. Enumeration Values
Value
0
Label
Description
bulk
bulk
loosed unpacked
excluding bulk
rigid box type prismatic
loosed unpacked excluding bulk
rigid drum type cylindrical
4
rigid drum type
cylindrical
rigid bulb type spherical
5
rigid other
rigid other
6
flexible bag type
flexible bag type
7
for future use
for future use
8
reserved
reserved
9
other special packages
other special packages
98
other
99
non-specified
Any other package type not
mentioned above
Package type not specified
1
2
3
EUCISE2020
rigid box type prismatic
rigid bulb type spherical
Source
UNECE Recommendation 21 annex IV
UNECE Recommendation 21 annex IV
UNECE Recommendation 21 annex IV
UNECE Recommendation 21 annex IV
UNECE Recommendation 21 annex IV
UNECE Recommendation 21 annex IV
UNECE Recommendation 21 annex IV
UNECE Recommendation 21 annex IV
UNECE Recommendation 21 annex IV
UNECE Recommendation 21 annex IV
Page 27 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
6.2.8.2. Enumeration Usage
The following attributes use this enumeration as data type:
 PackageType (ContainmentUnit)
6.2.9. PackagingMaterialType Enumeration
This enumeration presents the possible types of packaging material used in CargoUnits.
Source: UNECE Recommendation 21 - annex I
6.2.9.1. Enumeration Values
Value
0
none
Label
none
Description
1
plastics
plastics
2
paper and fibreboard
paper and fibreboard
3
wood
wood
4
for future use
for future use
5
metal
metal
6
glass porcelain ceramic stoneware
7
glass porcelain ceramic
stoneware
textile
8
reserved
reserved
9
98
unknown or not otherwise
enumerated
other
99
non-specified
unknown or not otherwise
enumerated
Any other package material not
mentioned above.
Material type not specified.
textile
Source
UNECE Recommendation 21 annex I
UNECE Recommendation 21 annex I
UNECE Recommendation 21 annex I
UNECE Recommendation 21 annex I
UNECE Recommendation 21 annex I
UNECE Recommendation 21 annex I
UNECE Recommendation 21 annex I
UNECE Recommendation 21 annex I
UNECE Recommendation 21 annex I
UNECE Recommendation 21 annex I
6.2.9.2. Enumeration Usage
The following attributes use this enumeration as data type:
 PackagingMaterial (ContainmentUnit)
6.2.10.
PackingGroupCodeType Enumeration
This enumeration defines the danger code, according to the level of danger from the IMDG (International
Maritime Dangerous Goods).
Source: IMO IMDG
6.2.10.1. Enumeration Values
Value
I
II
III
None
98
99
EUCISE2020
Label
Group I: great danger
Group II: medium danger
Group III: minor danger
None
other
non-specified
Description
Great danger
Medium danger
Minor danger
No danger
Any other code not mentioned above
Code not specified
Source
IMO IMDG
IMO IMDG
IMO IMDG
IMO IMDG
Page 28 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
6.2.10.2. Enumeration Usage
The following attributes use this enumeration as data type:
 PackingGroupCode (ContainmentUnit)
6.2.11.
PollutionCodeType Enumeration
This enumeration defines the pollution code, according to the MARPOL.
Source: IMO MARPOL - annex II
6.2.11.1. Enumeration Values
Value
X
Label
category X
Y
category Y
Z
category Z
OS
other
substances
NonSpecified
nonspecified
Description
Noxious Liquid Substances which, if discharged into the sea from
tank cleaning or deballasting operations, are deemed to present
a major hazard to either marine resources or human health and,
therefore, justify the prohibition of the discharge into the marine
environment
Noxious Liquid Substances which, if discharged into the sea from
tank cleaning or deballasting operations, are deemed to present
a hazard to either marine resources or human health or cause
harm to amenities or other legitimate uses of the sea and
therefore justify a limitation on the quality and quantity of the
discharge into the marine environment
Noxious Liquid Substances which, if discharged into the sea from
tank cleaning or deballasting operations, are deemed to present
a minor hazard to either marine resources or human health and
therefore justify less stringent restrictions on the quality and
quantity of the discharge into the marine environment
substances which have been evaluated and found to fall outside
Category X, Y or Z because they are considered to present no
harm to marine resources, human health, amenities or other
legitimate uses of the sea when discharged into the sea from
tank cleaning of deballasting operations. The discharge of bilge
or ballast water or other residues or mixtures containing these
substances are not subject to any requirements of MARPOL
Annex II
Source
IMO
MARPOL annex II
IMO
MARPOL annex II
IMO
MARPOL annex II
IMO
MARPOL annex II
6.2.11.2. Enumeration Usage
The following attributes use this enumeration as data type:
 PollutionCode (ContainmentUnit)
6.2.12.
SpeciesType Enumeration
This enumeration presents the possible types of species.
Source: ERS
6.2.12.1. Enumeration Values
Value
AAA
AAB
AAC
EUCISE2020
Label
Acipenser naccarii
Acanthopagrus bifasciatus
Amia calva
Description
Adriatic sturgeon
Twobar seabream
Bowfin
Source
ERS
ERS
ERS
Page 29 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
Label
Description
Source
AAD
Acipenser dabryanus
Yangtze sturgeon
ERS
AAE
Antennarius analis
Tailjet frogfish
ERS
WARNING: The current enumeration contains 12423 values. The rest of the values can be found in the CISE
Data model.
6.2.12.2. Enumeration Usage
The following attributes use this enumeration as data type:
 Species (Catch)
6.2.13.
UNDGType Enumeration
This enumeration defines United Nations Dangerous Goods list.
6.2.13.1. Enumeration Values
Value
0004
Label
Description
Source
AMMONIUM PICRATE dry or wetted with
AMMONIUM PICRATE dry or wetted with less
UNDG
less than 10% water, by mass
than 10% water, by mass (Class 1.1D)
0005 CARTRIDGES FOR WEAPONS with bursting CARTRIDGES FOR WEAPONS with bursting
UNDG
charge
charge (Class 1.1F)
0006 CARTRIDGES FOR WEAPONS with bursting CARTRIDGES FOR WEAPONS with bursting
UNDG
charge
charge (Class 1.1E)
0007 CARTRIDGES FOR WEAPONS with bursting CARTRIDGES FOR WEAPONS with bursting
UNDG
charge
charge (Class 1.2F)
0009 AMMUNITION, INCENDIARY with or
AMMUNITION, INCENDIARY with or without
UNDG
without burster, expelling charge or
burster, expelling charge or propelling charge
propelling charge
(Class 1.2G)
WARNING: The current enumeration contains 2164 values. The rest of the values can be found in the CISE
Data model.
6.2.13.2. Enumeration Usage
The following attributes use this enumeration as data type:
 UNDG (ContainmentUnit)
6.2.14.
UnitsOfMeasureType Enumeration
This enumeration presents the considered units of measure for CargoUnits, according to the United Nations
codes for units of measure used in international trade.
Source: UNECE Recommendation 20
6.2.14.1. Enumeration Values
Value
KGM
TNE
Other
99
Label
kilogram
Metric tonne
other
non-specified
Description
kilogram
Metric tonne
Any other unit not mentioned above
Unit not specified
Source
UNECE Recommendation 20
UNECE Recommendation 20
6.2.14.2. Enumeration Usage
The following attributes use this enumeration as data type:
 UnitsOfMeasure (ContainmentUnit)
6.2.15.
EUCISE2020
WeightMeansType Enumeration
Page 30 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
This enumeration presents the different means of weight for fisheries
Source: ERS
6.2.15.1. Enumeration Values
Value
EST
WGH
Label
Estimation
weighing on board
Description
Estimation
weighing on board
Source
ERS
ERS
6.2.15.2. Enumeration Usage
The following attributes use this enumeration as data type:
 WeightMeans (Catch)
EUCISE2020
Page 31 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
7.
Document Core Entity
7.1. UML models
7.2. Elements defined in the Core Vocabulary
7.2.1. AttachedDocument Class (subclass of Document)
7.2.1.1. Attributes
UML
Name
Data
type
Descriptio
n
Conte
nt
XSD::bas
e64Binar
y
XSD::hex
Binary
XSD::any
URI
Content
of the
document
Integrity
check
Uniform
resource
identifier
(URI) is a
string of
characters
Hash
Refere
nceUR
I
EUCISE2020
So
urc
e
Example
e.g.web address of the document "Helsinki VTS Master's Guide"
<ReferenceURI>http://portal.liikennevirasto.fi/portal/page/portal/e
/professionals/vts/HKI_MG%2028052012_en.pdf</ReferenceURI>
Page 32 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data
type
Identif
ier
UniqueId
entifier
Metad
ata
Metadat
a
EUCISE2020
Descriptio
n
So
urc
e
Example
used to
identify a
name of a
web
resource.
Identifier
of the
document
.
Each
UniqueIde
ntifier can
be
correlated
with
other
UniqueIde
ntifiers,
either
manually,
by
operators,
or
automatic
ally, by
systems,
so that
duplicate
objects in
the
network
can be
identified
and
brought
together
for a
better
understan
ding of
the
informati
on being
shared.
Class
Metadata
will be
used to
carry
more
specific
Page 33 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data
type
Subjec
t
String
Title
String
Versio
n
String
EUCISE2020
Descriptio
n
informati
on about
document
s.
The topic
of the
content of
the
resource.
Typically,
a Subject
will be
expressed
as
keywords
or key
phrases or
classificati
on codes
that
describe
the topic
of the
resource.
Recomme
nded best
practice is
to select a
value
from a
controlled
vocabular
y or
formal
classificati
on
scheme
A name
given to
the
resource,
e.g. the
official
name of
the
publicatio
n in
English
language
Indicates
the
So
urc
e
Example
e.g. the document in the previous example would be one of the
many documents belonging to subject VTS or Vessel Traffic Services:
<Subject>Vessel Traffic Services</Subject>
DC
MI
e.g. documents which official english name is "Helsinki VTS Master's
Guide":
<Title>Helsinki VTS Master's Guide</Title>
DC
MI
e.g. version 2.1 of the document
<Name>Version 2.1</Name>
Page 34 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data
type
Descriptio
n
So
urc
e
Example
version
number
of the
document
/resource.
(*) Inherited attributes are coloured in grey.
7.2.1.2. Association Roles
UML Name
Data type
Location
Location
(*) Inherited association roles are coloured in grey.
Description
Multiplicity
0..*
7.2.2. CargoDocument Class (subclass of AttachedDocument)
This sub-class allows the identification and exchange of Cargo related documents and material in electronic
format.
7.2.2.1. Attributes
UML
Name
Data type
Docum
entTyp
e
CargoDoc
umentTyp
e
Conten
t
XSD::base
64Binary
Hash
Refere
nceURI
XSD::hexB
inary
XSD::anyU
RI
Identifi
er
UniqueIde
ntifier
EUCISE2020
Descripti
on
Electronic
material
related to
vessels
cargo or
individual
cargo
items.
Content
of the
document
Integrity
check
Uniform
resource
identifier
(URI) is a
string of
character
s used to
identify a
name of a
web
resource.
Identifier
of the
document
.
Each
UniqueId
entifier
So
urc
e
Example
Cargo manifest:
01
e.g.web address of the document "Helsinki VTS Master's Guide"
<ReferenceURI>http://portal.liikennevirasto.fi/portal/page/portal/
e/professionals/vts/HKI_MG%2028052012_en.pdf</ReferenceURI
>
Page 35 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Metad
ata
Metadata
Subject
String
EUCISE2020
Descripti
on
can be
correlate
d with
other
UniqueId
entifiers,
either
manually,
by
operators
, or
automatic
ally, by
systems,
so that
duplicate
objects in
the
network
can be
identified
and
brought
together
for a
better
understan
ding of
the
informati
on being
shared.
Class
Metadata
will be
used to
carry
more
specific
informati
on about
document
s.
The topic
of the
content
of the
resource.
Typically,
a Subject
will be
So
urc
e
Example
e.g. the document in the previous example would be one of the
many documents belonging to subject VTS or Vessel Traffic
Services:
<Subject>Vessel Traffic Services</Subject>
Page 36 / 367
DC
MI
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Descripti
on
So
urc
e
Example
expressed
as
keywords
or key
phrases
or
classificati
on codes
that
describe
the topic
of the
resource.
Recomme
nded best
practice is
to select a
value
from a
controlled
vocabular
y or
formal
classificati
on
scheme
Title
String
A name
e.g. documents which official english name is "Helsinki VTS
given to
Master's Guide":
the
<Title>Helsinki VTS Master's Guide</Title>
resource,
e.g. the
official
name of
the
publicatio
n in
English
language
Version String
Indicates
e.g. version 2.1 of the document
the
<Name>Version 2.1</Name>
version
number
of the
document
/resource
.
(*) Inherited attributes are coloured in grey.
7.2.2.2. Association Roles
UML Name
Location
EUCISE2020
Data type
Location
Description
Multiplicity
0..*
Page 37 / 367
DC
MI
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
(*) Inherited association roles are coloured in grey.
7.2.3. CertificateDocument Class (subclass of AttachedDocument)
This sub-class allows the identification and exchange of Certificate related documents and material in electronic
format.
Subclass of Document.
7.2.3.1. Attributes
UML
Name
Data type
Docum
entTyp
e
CertificateD
ocumentTyp
e
Conten
t
XSD::base64
Binary
Hash
XSD::hexBin
ary
XSD::anyURI
Refere
nceURI
Identifi
er
EUCISE2020
UniqueIden
tifier
Descripti
on
Documen
ts related
to
Certificat
e
Content
of the
documen
t
Integrity
check
Uniform
resource
identifier
(URI) is a
string of
character
s used to
identify a
name of a
web
resource.
Identifier
of the
documen
t.
Each
UniqueId
entifier
can be
correlate
d with
other
UniqueId
entifiers,
either
manually,
by
operators
, or
automati
cally, by
systems,
So
urc
e
Example
e.g.web address of the document "Helsinki VTS Master's Guide"
<ReferenceURI>http://portal.liikennevirasto.fi/portal/page/porta
l/e/professionals/vts/HKI_MG%2028052012_en.pdf</Reference
URI>
Page 38 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Metad
ata
Metadata
Subject
String
EUCISE2020
Descripti
on
so that
duplicate
objects in
the
network
can be
identified
and
brought
together
for a
better
understa
nding of
the
informati
on being
shared.
Class
Metadata
will be
used to
carry
more
specific
informati
on about
documen
ts.
The topic
of the
content
of the
resource.
Typically,
a Subject
will be
expresse
d as
keywords
or key
phrases
or
classificat
ion codes
that
describe
the topic
of the
resource.
Recomme
So
urc
e
Example
e.g. the document in the previous example would be one of the
many documents belonging to subject VTS or Vessel Traffic
Services:
<Subject>Vessel Traffic Services</Subject>
Page 39 / 367
DC
MI
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Descripti
on
So
urc
e
Example
nded best
practice
is to
select a
value
from a
controlle
d
vocabular
y or
formal
classificat
ion
scheme
Title
String
A name
e.g. documents which official english name is "Helsinki VTS
given to
Master's Guide":
the
<Title>Helsinki VTS Master's Guide</Title>
resource,
e.g. the
official
name of
the
publicatio
n in
English
language
Versio
String
Indicates
e.g. version 2.1 of the document
n
the
<Name>Version 2.1</Name>
version
number
of the
documen
t/resourc
e.
(*) Inherited attributes are coloured in grey.
DC
MI
7.2.3.2. Association Roles
UML Name
Data type
Location
Location
(*) Inherited association roles are coloured in grey.
Description
Multiplicity
0..*
7.2.4. Document Class (subclass of Entity)
The Document is one of the fundamental entities of the overall data model of the information sharing
environment. A Document allows tracing and exchanging information in a persistent manner in almost any
possible electronic format; this information is expected to provide details on and express specific associations
between other Entity Classes such as Agents, Objects, Events, Risks, Locations etc.
7.2.4.1. Attributes
UML
Name
Identifier
EUCISE2020
Data type
UniqueIdentifier
Description
Example
Source
Identifier of the document.
Page 40 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Metadata
Metadata
Subject
String
Title
String
Version
String
Description
Example
Each UniqueIdentifier can be
correlated with other
UniqueIdentifiers, either manually, by
operators, or automatically, by
systems, so that duplicate objects in
the network can be identified and
brought together for a better
understanding of the information
being shared.
Class Metadata will be used to carry
more specific information about
documents.
The topic of the content of the
resource. Typically, a Subject will be
expressed as keywords or key phrases
or classification codes that describe
the topic of the resource.
Recommended best practice is to
select a value from a controlled
vocabulary or formal classification
scheme
A name given to the resource, e.g. the
official name of the publication in
English language
Indicates the version number of the
document/resource.
Source
e.g. the document in the
previous example would
be one of the many
documents belonging to
subject VTS or Vessel
Traffic Services:
<Subject>Vessel Traffic
Services</Subject>
DCMI
e.g. documents which
official english name is
"Helsinki VTS Master's
Guide":
<Title>Helsinki VTS
Master's Guide</Title>
e.g. version 2.1 of the
document
<Name>Version
2.1</Name>
DCMI
7.2.4.2. Association Roles
UML Name
Location
Data type
Location
Description
Multiplicity
0..*
7.2.5. EventDocument Class (subclass of AttachedDocument)
This sub-class allows the identification and exchange of Event related documents and material in electronic
format.
7.2.5.1. Attributes
UML
Name
Data type
Docum
entTyp
e
EventDoc
umentTyp
e
EUCISE2020
Descripti
on
Electronic
material
related to
individual
events (or
more
specificall
y one of
So
urc
e
Example
e.g. an incident report from SafeSeaNet:
<DocumentType>02</DocumentType>
Page 41 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Conten
t
XSD::base
64Binary
Hash
Refere
nceURI
XSD::hexB
inary
XSD::anyU
RI
Identifi
er
UniqueId
entifier
EUCISE2020
Descripti
on
its subclasses:
movemen
t,
anomaly,
incident
or
action).
Content
of the
document
Integrity
check
Uniform
resource
identifier
(URI) is a
string of
character
s used to
identify a
name of a
web
resource.
Identifier
of the
document
.
Each
UniqueId
entifier
can be
correlate
d with
other
UniqueId
entifiers,
either
manually,
by
operators
, or
automatic
ally, by
systems,
so that
duplicate
objects in
the
network
can be
So
urc
e
Example
e.g.web address of the document "Helsinki VTS Master's Guide"
<ReferenceURI>http://portal.liikennevirasto.fi/portal/page/portal/
e/professionals/vts/HKI_MG%2028052012_en.pdf</ReferenceURI
>
Page 42 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Metad
ata
Metadata
Subject
String
EUCISE2020
Descripti
on
identified
and
brought
together
for a
better
understan
ding of
the
informati
on being
shared.
Class
Metadata
will be
used to
carry
more
specific
informati
on about
document
s.
The topic
of the
content
of the
resource.
Typically,
a Subject
will be
expressed
as
keywords
or key
phrases
or
classificati
on codes
that
describe
the topic
of the
resource.
Recomme
nded best
practice is
to select a
value
from a
controlled
So
urc
e
Example
e.g. the document in the previous example would be one of the
many documents belonging to subject VTS or Vessel Traffic
Services:
<Subject>Vessel Traffic Services</Subject>
Page 43 / 367
DC
MI
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Descripti
on
So
urc
e
Example
vocabular
y or
formal
classificati
on
scheme
Title
String
A name
e.g. documents which official english name is "Helsinki VTS
given to
Master's Guide":
the
<Title>Helsinki VTS Master's Guide</Title>
resource,
e.g. the
official
name of
the
publicatio
n in
English
language
Version String
Indicates
e.g. version 2.1 of the document
the
<Name>Version 2.1</Name>
version
number
of the
document
/resource
.
(*) Inherited attributes are coloured in grey.
DC
MI
7.2.5.2. Association Roles
UML Name
Data type
Location
Location
(*) Inherited association roles are coloured in grey.
Description
Multiplicity
0..*
7.2.6. LocationDocument Class (subclass of AttachedDocument)
This sub-class allows the identification and exchange of Location related documents and material in electronic
format.
7.2.6.1. Attributes
UML
Name
Data type
Docum
entTyp
e
LocationDo
cumentTyp
e
Conten
t
XSD::base6
4Binary
EUCISE2020
Descripti
on
Electronic
material
related to
specified
Location.
Content
of the
documen
t
So
urc
e
Example
meteorological maps from specified area
14
Page 44 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Hash
Data type
Refere
nceURI
XSD::hexBi
nary
XSD::anyU
RI
Identifi
er
UniqueIde
ntifier
EUCISE2020
Descripti
on
Integrity
check
Uniform
resource
identifier
(URI) is a
string of
character
s used to
identify a
name of a
web
resource.
Identifier
of the
documen
t.
Each
UniqueId
entifier
can be
correlate
d with
other
UniqueId
entifiers,
either
manually,
by
operators
, or
automati
cally, by
systems,
so that
duplicate
objects in
the
network
can be
identified
and
brought
together
for a
better
understa
nding of
the
informati
So
urc
e
Example
e.g.web address of the document "Helsinki VTS Master's Guide"
<ReferenceURI>http://portal.liikennevirasto.fi/portal/page/portal
/e/professionals/vts/HKI_MG%2028052012_en.pdf</ReferenceU
RI>
Page 45 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Metad
ata
Metadata
Subject
String
Title
String
EUCISE2020
Descripti
on
on being
shared.
Class
Metadata
will be
used to
carry
more
specific
informati
on about
documen
ts.
The topic
of the
content
of the
resource.
Typically,
a Subject
will be
expressed
as
keywords
or key
phrases
or
classificat
ion codes
that
describe
the topic
of the
resource.
Recomme
nded best
practice is
to select
a value
from a
controlle
d
vocabular
y or
formal
classificat
ion
scheme
A name
given to
the
So
urc
e
Example
e.g. the document in the previous example would be one of the
many documents belonging to subject VTS or Vessel Traffic
Services:
<Subject>Vessel Traffic Services</Subject>
DC
MI
e.g. documents which official english name is "Helsinki VTS
Master's Guide":
<Title>Helsinki VTS Master's Guide</Title>
DC
MI
Page 46 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Descripti
on
So
urc
e
Example
resource,
e.g. the
official
name of
the
publicatio
n in
English
language
Version String
Indicates
e.g. version 2.1 of the document
the
<Name>Version 2.1</Name>
version
number
of the
documen
t/resourc
e.
(*) Inherited attributes are coloured in grey.
7.2.6.2. Association Roles
UML Name
Data type
Location
Location
(*) Inherited association roles are coloured in grey.
Description
Multiplicity
0..*
7.2.7. OrganizationDocument Class (subclass of AttachedDocument)
This sub-class allows the identification and exchange of Organization related documents and material in
electronic format.
7.2.7.1. Attributes
UML
Name
Data type
Docum
entTyp
e
Organization
DocumentTy
pe
Conten
t
XSD::base64
Binary
Hash
XSD::hexBina
ry
XSD::anyURI
Refere
nceURI
EUCISE2020
Descripti
on
Electronic
material
related to
individual
identified
Organizat
ion or
one of its
subclasses.
Content
of the
documen
t
Integrity
check
Uniform
resource
identifier
So
urc
e
Example
Documents describing harbour security plans:
01
e.g.web address of the document "Helsinki VTS Master's Guide"
Page 47 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Identifi
er
UniqueIdenti
fier
Metad
ata
Metadata
EUCISE2020
Descripti
on
(URI) is a
string of
character
s used to
identify a
name of
a web
resource.
Identifier
of the
documen
t.
Each
UniqueId
entifier
can be
correlate
d with
other
UniqueId
entifiers,
either
manually,
by
operators
, or
automati
cally, by
systems,
so that
duplicate
objects in
the
network
can be
identified
and
brought
together
for a
better
understa
nding of
the
informati
on being
shared.
Class
Metadata
will be
used to
So
urc
e
Example
<ReferenceURI>http://portal.liikennevirasto.fi/portal/page/port
al/e/professionals/vts/HKI_MG%2028052012_en.pdf</Referenc
eURI>
Page 48 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Subjec
t
String
Title
String
EUCISE2020
Descripti
on
carry
more
specific
informati
on about
documen
ts.
The topic
of the
content
of the
resource.
Typically,
a Subject
will be
expresse
d as
keywords
or key
phrases
or
classificat
ion codes
that
describe
the topic
of the
resource.
Recomm
ended
best
practice
is to
select a
value
from a
controlle
d
vocabular
y or
formal
classificat
ion
scheme
A name
given to
the
resource,
e.g. the
official
name of
So
urc
e
Example
e.g. the document in the previous example would be one of the
many documents belonging to subject VTS or Vessel Traffic
Services:
<Subject>Vessel Traffic Services</Subject>
DC
MI
e.g. documents which official english name is "Helsinki VTS
Master's Guide":
<Title>Helsinki VTS Master's Guide</Title>
DC
MI
Page 49 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Descripti
on
So
urc
e
Example
the
publicatio
n in
English
language
Versio
String
Indicates e.g. version 2.1 of the document
n
the
<Name>Version 2.1</Name>
version
number
of the
documen
t/resourc
e.
(*) Inherited attributes are coloured in grey.
7.2.7.2. Association Roles
UML Name
Data type
Location
Location
(*) Inherited association roles are coloured in grey.
Description
Multiplicity
0..*
7.2.8. PersonDocument Class (subclass of AttachedDocument)
This sub-class allows the identification and exchange of Person related documents and material in electronic
format.
7.2.8.1. Attributes
UML
Name
Data type
Docum
entTyp
e
PersonDoc
umentTyp
e
Conten
t
XSD::base
64Binary
Hash
XSD::hexBi
nary
XSD::anyU
RI
Refere
nceURI
EUCISE2020
Descripti
on
Electronic
material
related to
individual
Persons.
Content
of the
documen
t
Integrity
check
Uniform
resource
identifier
(URI) is a
string of
character
s used to
identify a
name of a
web
resource.
So
urc
e
Example
e.g.web address of the document "Helsinki VTS Master's Guide"
<ReferenceURI>http://portal.liikennevirasto.fi/portal/page/portal/
e/professionals/vts/HKI_MG%2028052012_en.pdf</ReferenceURI
>
Page 50 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Identifi
er
UniqueIde
ntifier
Metad
ata
Metadata
EUCISE2020
Descripti
on
So
urc
e
Example
Identifier
of the
documen
t.
Each
UniqueId
entifier
can be
correlate
d with
other
UniqueId
entifiers,
either
manually,
by
operators
, or
automatic
ally, by
systems,
so that
duplicate
objects in
the
network
can be
identified
and
brought
together
for a
better
understan
ding of
the
informati
on being
shared.
Class
Metadata
will be
used to
carry
more
specific
informati
on about
documen
ts.
Page 51 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Subject
String
Title
String
Version
String
EUCISE2020
Descripti
on
The topic
of the
content
of the
resource.
Typically,
a Subject
will be
expressed
as
keywords
or key
phrases
or
classificati
on codes
that
describe
the topic
of the
resource.
Recomme
nded best
practice is
to select
a value
from a
controlled
vocabular
y or
formal
classificati
on
scheme
A name
given to
the
resource,
e.g. the
official
name of
the
publicatio
n in
English
language
Indicates
the
version
number
of the
Example
e.g. the document in the previous example would be one of the
many documents belonging to subject VTS or Vessel Traffic
Services:
<Subject>Vessel Traffic Services</Subject>
e.g. documents which official english name is "Helsinki VTS
Master's Guide":
<Title>Helsinki VTS Master's Guide</Title>
e.g. version 2.1 of the document
<Name>Version 2.1</Name>
Page 52 / 367
So
urc
e
DC
MI
DC
MI
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Descripti
on
So
urc
e
Example
documen
t/resourc
e.
(*) Inherited attributes are coloured in grey.
7.2.8.2. Association Roles
UML Name
Data type
Location
Location
(*) Inherited association roles are coloured in grey.
Description
Multiplicity
0..*
7.2.9. RiskDocument Class (subclass of AttachedDocument)
This sub-class allows the identification and exchange of Risk related documents and material in electronic
format.
7.2.9.1. Attributes
UML
Name
Data
type
Descripti
on
Docum
entTyp
e
RiskDocu
mentTyp
e
Conten
t
Refere
nceURI
XSD::bas
e64Binar
y
XSD::hex
Binary
XSD::any
URI
Identifi
er
UniqueId
entifier
Electronic
material
related to
individual
risks.
Content
of the
document
Integrity
check
Uniform
resource
identifier
(URI) is a
string of
character
s used to
identify a
name of a
web
resource.
Identifier
of the
document
.
Each
UniqueId
entifier
can be
correlated
with
other
UniqueId
Hash
EUCISE2020
So
urc
e
Example
SafeSeaNet HAZMAT Notifications:
07
e.g.web address of the document "Helsinki VTS Master's Guide"
<ReferenceURI>http://portal.liikennevirasto.fi/portal/page/portal/
e/professionals/vts/HKI_MG%2028052012_en.pdf</ReferenceURI>
Page 53 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data
type
Metad
ata
Metadat
a
Subject
String
EUCISE2020
Descripti
on
entifiers,
either
manually,
by
operators,
or
automatic
ally, by
systems,
so that
duplicate
objects in
the
network
can be
identified
and
brought
together
for a
better
understan
ding of
the
informati
on being
shared.
Class
Metadata
will be
used to
carry
more
specific
informati
on about
document
s.
The topic
of the
content of
the
resource.
Typically,
a Subject
will be
expressed
as
keywords
or key
phrases
So
urc
e
Example
e.g. the document in the previous example would be one of the
many documents belonging to subject VTS or Vessel Traffic
Services:
<Subject>Vessel Traffic Services</Subject>
Page 54 / 367
DC
MI
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data
type
Descripti
on
So
urc
e
Example
or
classificati
on codes
that
describe
the topic
of the
resource.
Recomme
nded best
practice is
to select a
value
from a
controlled
vocabular
y or
formal
classificati
on
scheme
Title
String
A name
e.g. documents which official english name is "Helsinki VTS
given to
Master's Guide":
the
<Title>Helsinki VTS Master's Guide</Title>
resource,
e.g. the
official
name of
the
publicatio
n in
English
language
Version String
Indicates
e.g. version 2.1 of the document
the
<Name>Version 2.1</Name>
version
number
of the
document
/resource.
(*) Inherited attributes are coloured in grey.
7.2.9.2. Association Roles
UML Name
Data type
Location
Location
(*) Inherited association roles are coloured in grey.
7.2.10.
Description
Multiplicity
0..*
Stream Class (subclass of Document)
Stream of information.
7.2.10.1. Attributes
EUCISE2020
Page 55 / 367
DC
MI
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
StreamType
Data type
StreamType
StreamURI
XSD::anyURI
Identifier
UniqueIdentifier
Metadata
Metadata
Subject
String
Title
String
Version
String
Description
Type of the stream. Each stream
type is linked to a specific standard.
Endpoint of the stream, from which
the information can be downloaded.
Identifier of the document.
Each UniqueIdentifier can be
correlated with other
UniqueIdentifiers, either manually,
by operators, or automatically, by
systems, so that duplicate objects in
the network can be identified and
brought together for a better
understanding of the information
being shared.
Class Metadata will be used to carry
more specific information about
documents.
The topic of the content of the
resource. Typically, a Subject will be
expressed as keywords or key
phrases or classification codes that
describe the topic of the resource.
Recommended best practice is to
select a value from a controlled
vocabulary or formal classification
scheme
A name given to the resource, e.g.
the official name of the publication
in English language
Indicates the version number of the
document/resource.
Example
Source
Video
e.g. the document in the
previous example would
be one of the many
documents belonging to
subject VTS or Vessel
Traffic Services:
<Subject>Vessel Traffic
Services</Subject>
DCMI
e.g. documents which
official english name is
"Helsinki VTS Master's
Guide":
<Title>Helsinki VTS
Master's Guide</Title>
e.g. version 2.1 of the
document
<Name>Version
2.1</Name>
DCMI
(*) Inherited attributes are coloured in grey.
7.2.10.2. Association Roles
UML Name
Data type
Location
Location
(*) Inherited association roles are coloured in grey.
7.2.11.
Description
Multiplicity
0..*
VesselDocument Class (subclass of AttachedDocument)
This sub-class allows the identification and exchange of Vessel related documents and material in electronic
format.
7.2.11.1. Attributes
EUCISE2020
Page 56 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Docum
entTyp
e
VesselDoc
umentTyp
e
Conten
t
XSD::base
64Binary
Hash
Refere
nceURI
XSD::hexB
inary
XSD::anyU
RI
Identifi
er
UniqueIde
ntifier
EUCISE2020
Descripti
on
Electronic
material
related to
individual
vessels.
Content
of the
document
Integrity
check
Uniform
resource
identifier
(URI) is a
string of
character
s used to
identify a
name of a
web
resource.
Identifier
of the
document
.
Each
UniqueId
entifier
can be
correlate
d with
other
UniqueId
entifiers,
either
manually,
by
operators
, or
automatic
ally, by
systems,
so that
duplicate
objects in
the
network
can be
identified
and
brought
So
urc
e
Example
Vessel's Certificate of registry:
95
e.g.web address of the document "Helsinki VTS Master's Guide"
<ReferenceURI>http://portal.liikennevirasto.fi/portal/page/portal/
e/professionals/vts/HKI_MG%2028052012_en.pdf</ReferenceURI
>
Page 57 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Metad
ata
Metadata
Subject
String
EUCISE2020
Descripti
on
together
for a
better
understan
ding of
the
informati
on being
shared.
Class
Metadata
will be
used to
carry
more
specific
informati
on about
document
s.
The topic
of the
content
of the
resource.
Typically,
a Subject
will be
expressed
as
keywords
or key
phrases
or
classificati
on codes
that
describe
the topic
of the
resource.
Recomme
nded best
practice is
to select
a value
from a
controlled
vocabular
y or
formal
So
urc
e
Example
e.g. the document in the previous example would be one of the
many documents belonging to subject VTS or Vessel Traffic
Services:
<Subject>Vessel Traffic Services</Subject>
Page 58 / 367
DC
MI
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Data type
Descripti
on
So
urc
e
Example
classificati
on
scheme
Title
String
A name
e.g. documents which official english name is "Helsinki VTS
given to
Master's Guide":
the
<Title>Helsinki VTS Master's Guide</Title>
resource,
e.g. the
official
name of
the
publicatio
n in
English
language
Version String
Indicates
e.g. version 2.1 of the document
the
<Name>Version 2.1</Name>
version
number
of the
document
/resource
.
(*) Inherited attributes are coloured in grey.
DC
MI
7.2.11.2. Association Roles
UML Name
Data type
Location
Location
(*) Inherited association roles are coloured in grey.
7.2.12.
Description
Multiplicity
0..*
CargoDocumentType Enumeration
This enumeration presents the possible types of documents related to cargo.
7.2.12.1. Enumeration Values
Value
01
Label
cargo manifest
02
03
VAT exception
entry summary
declaration
IMOFAL form2 cargo
declaration
IMOFAL form3 ships
stores declaration
IMOFAL form4 crews
effects declaration
notification of dangerous
goods
IMOFAL form7 dangerous
goods
04
05
06
07
08
EUCISE2020
Description
Basic information about the cargo. Would include also links to
further information: bill of lading, cargo bill, liner way bill
Source
Page 59 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
09
10
11
98
99
Label
single administrative
document
catch certificate
fishing logbook
other
non-specified
Description
Source
7.2.12.2. Enumeration Usage
The following attributes use this enumeration as data type:
 DocumentType (CargoDocument)
7.2.13.
CertificateDocumentType Enumeration
7.2.13.1. Enumeration Values
Value
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
EUCISE2020
Label
Description
Source
tonnage certificate
load line certificate
minimum safe manning document
oil pollution prevention certificate
sewage pollution prevention certificate
VDR compliance certificate
ISM compliance document
safety management certificate
ISS certificate
PSS certificate
STPS sa certificate
STPS sp certificate
CSS construction certificate
CSS equipment certificate
CSS radio certificate
CSS certificate
grain authorization document
civil liability certificate
enhanced survey document
NLS certificate
bulk chemicals carriage certificate
int bulk chemicals carriage certificate
bulk liquid gas certificate
int bulk liquid gas certificate
HSC safety certificate
HSC operation permit
IMDG certificate
INF certificate
registry certificate
hull class certificate
engine class certificate
pand I certificate
ILO133 certificate
ILO92 certificate
ITF blue card
declaration of health
Page 60 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
37
38
39
98
99
Label
Description
Source
gas free certificate
de rat certificate
certificate
other
non-specified
7.2.13.2. Enumeration Usage
The following attributes use this enumeration as data type:
 DocumentType (CertificateDocument)
7.2.14.
EventDocumentType Enumeration
This enumeration presents the possible types of documents related to different events (movements, actions,
anomalies, incidents).
7.2.14.1. Enumeration Values
Value
01
Label
regional monitors
02
incident report
03
98
environmental
incident document
evacuation orders
accident report
hazards mapping and
tracking
humanitarian
assistance
organized crime
documents
terrorist thread
documents
ship hijacking
suspicion report
crew hostaging
suspicion report
weapons onboard
suspicion report
initial piracy attack
report
follow-up piracy
attack report
other
99
non-specified
04
05
06
07
08
09
10
11
12
13
Description
Observation reports from different EU regions related to
issues reported via EUROSUR (e.g. irregular migration,
related cross-border crime, crisis, other).
Documents containing the detailed report of incidents
reported via SSN (e.g. waste, situations , pollution,
containers or packages drifting at sea, failed vessel
notifications, VTS rules infringements, banned ships,
insurance failures, anomaly reports by pilots or ports).
Documents and reports that describe environmental
icidents (e.g. oil pollution)
Detailed orders related to evacuation situations.
Detailed reports of accidents in sea.
Source
EUROSUR
SSN
IMO
MSC.1/Circ.1333
Initial report about piracy attack as defined in IMO MSC
Circular 1333.
Follow-up report about piracy attack as defined in IMO
MSC Circular 1333.
Any other document related to events not mentioned
above
Type of document not specified.
IMO
MSC.1/Circ.1333
IMO
MSC.1/Circ.1333
7.2.14.2. Enumeration Usage
EUCISE2020
Page 61 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
The following attributes use this enumeration as data type:
 DocumentType (EventDocument)
7.2.15.
LocationDocumentType Enumeration
This enumeration presents the possible types of documents related to a location.
Source: PPIAF
7.2.15.1. Enumeration Values
Value
Label
Description
Source
01
port law
PPIAF
02
port regulations
PPIAF
03
port services
PPIAF
04
port facilities
PPIAF
05
port dues
PPIAF
WARNING: The current enumeration contains 51 values. The rest of the values can be found in the CISE Data
model.
7.2.15.2. Enumeration Usage
The following attributes use this enumeration as data type:
 DocumentType (LocationDocument)
7.2.16.
OrganizationDocumentType Enumeration
This enumeration presents the possible types of documents that can be related to organizations.
7.2.16.1. Enumeration Values
Value
01
02
Label
harbour security
document
ISPS code
03
98
99
map
other
non-specified
Description
Documents that related to a specific harbour and deal with
security issues.
Documents that are related to an organization and deal with
IMO ISPS Code.
Any type of map related to the organization.
Any other type of document not specified above.
Type of the document not specified.
Source
7.2.16.2. Enumeration Usage
The following attributes use this enumeration as data type:
 DocumentType (OrganizationDocument)
7.2.17.
PersonDocumentType Enumeration
This enumeration presents the possible types of documents that can be related to individual persons.
7.2.17.1. Enumeration Values
Value
01
Label
travel document
02
03
04
national ID
drivers license
seafarers ID
document
EUCISE2020
Description
Document that enables the entry and exit from one country to another
(e.g. Passport).
National identification document.
Document proving the right to drive a car.
Special identification document for seafarers (e.g. SeamansBook)
Source
Page 62 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
05
06
Label
crew certificates
residence permit
07
work permit
08
work certificate
09
10
11
12
13
98
99
health certificate
birth certificate
death certificate
criminal record
photograph
other
non-specified
Description
Certificate of ability to hold a certain post in vessel.
Document proving that a person has right to stay in the country (e.g.
MigrationCard, CruiseShipIDCard (passangers))
Document proving that a person has right to work in the country
(e.g.WorkCard, BlueCard)
Document proving the past employment of a person
(e.g.EmploymentRecordBook)
Document stating the health status of the person.
The official birth certificate of a person
The official death certificate of a person
Persons criminal record
Photograph of a person.
Any other document not mentioned above
Type of the document not specified
Source
7.2.17.2. Enumeration Usage
The following attributes use this enumeration as data type:
 DocumentType (PersonDocument)
7.2.18.
RiskDocumentType Enumeration
This enumeration presents the possible types of documents related to risks.
Source: EUROSUR
7.2.18.1. Enumeration Values
Value
01
02
03
04
05
06
07
08
09
10
11
12
13
98
99
Label
briefing notes
route description
facilitationanalysis
migrant profile
key developments
risk ratings
HAZMAT notification
risk assessment
organised crime documents
terrorist threat documents
ship hijacking suspicion report
crew hostaging suspicion report
weapons on board suspicion report
other
non-specified
Description
Source
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
SSN
TAG
7.2.18.2. Enumeration Usage
The following attributes use this enumeration as data type:
 DocumentType (RiskDocument)
7.2.19.
StreamType Enumeration
Types of streams. Each type is associated to a specific standard.
7.2.19.1. Enumeration Values
EUCISE2020
Page 63 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
Video
ImageMap
VectorialMap
Radar
AIS
Label
video
image map
vectorial map
radar
AIS
Description
Video stream in format MPEG4 H264
Image map in format WMS
Vectorial map in format WFS
VTS exchange format IVEF
Stream format in ITU-RM1371
Source
7.2.19.2. Enumeration Usage
The following attributes use this enumeration as data type:
 StreamType (Stream)
7.2.20.
VesselDocumentType Enumeration
This enumeration presents the possible types of electronic material that can be related to individual vessels.
7.2.20.1. Enumeration Values
Value
001
Label
international
tonnage
certificate
international
load line
certificate
Description
Source
An International Tonnage Certificate (1969) shall be issued to every
ship, the gross and net tonnage of which have been determined in
accordance with the Convention (Tonnage Convention, article 7).
002
An International Load Line Certificate shall be issued under the
provisions of the International Convention on Load Lines, 1966, to
every ship which has been surveyed and marked in accordance with
the Convention or the Convention as modified by the 1988 LL Protocol,
as appropriate (LL Convention, article 16; 1988 LL Protocol, article 16).
003
international
An International Load Line Exemption Certificate shall be issued to any
load line
ship to which an exemption has been granted under and in accordance
exemption
with article 6 of the Load Line Convention or the Convention as
certificate
modified by the 1988 LL Protocol, as appropriate
(LL Convention, article 6; 1988 LL Protocol, article 16)
004
coating technical A Coating Technical File, containing specifications of the coating system
file
applied to dedicated seawater ballast tanks in all types of ships and
double-side skin spaces of bulk carriers of 150 m in length and
upwards, record of the shipyard's and shipowner's coating work,
detailed criteria for coating sections, job specifications, inspection,
maintenance and repair, shall be kept on board and maintained
throughout the life of the ship
(SOLAS 1974, regulation II-1/3-2; Performance standard for protective
coatings for dedicated seawater ballast tanks in all types of ships and
double-side skin spaces of bulk carriers (resolution MSC.215(82)))
005
construction
A set of as-built construction drawings and other plans showing any
drawings
subsequent structural alterations shall be kept on board a ship
constructed on or after 1 January 2007
(SOLAS 1974, regulation II-1/3-7; MSC/Circ.1135 on As-built
construction drawings to be maintained on board the ship and ashore)
WARNING: The current enumeration contains 151 values. The rest of the values can be found in the CISE Data
model.
7.2.20.2. Enumeration Usage
The following attributes use this enumeration as data type:
 DocumentType (VesselDocument)
EUCISE2020
Page 64 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
8.
Event Core Entity
8.1. UML models
8.2. Elements defined in the Core Vocabulary
8.2.1. Event Class (subclass of Entity)
The Event is one of the core entities of the overall data model of the information sharing environment. It is an
entity which holds information about movements, anomalies, incidents or actions which occur in the maritime
domain. Event can have relationships with other events, objects, agents, documents, periods and locations.
Event can also be related to risks in different roles. Event is an abstract entity which has four sub-entities:
Movement, Anomaly, Incident and Action.
8.2.1.1. Attributes
UML Name
Identifier
Data type
UniqueIdentifier
Metadata
Metadata
NatureType
NatureType
EUCISE2020
Description
Identifier of the event.
Each UniqueIdentifier can be correlated
with other UniqueIdentifiers, either
manually, by operators, or automatically,
by systems, so that duplicate objects in
the network can be identified and
brought together for a better
understanding of the information being
shared.
see: Core Vocabularies Specification for
"Metadata"
Enumerated. Is used to define nature of
the event. An event can be observed,
declared, estimated or simulated.
Example
Source
see: Core
Vocabularies
Specification for
"Metadata"
for an observed
event:
01
Page 65 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
OccurrencePeriod
Data type
Period
Description
An Event occurs during a period of time.
Example
Source
CISE
8.2.1.2. Association Roles
UML Name
Document
ImpliedRisk
InvolvedAgent
Data type
Document
Risk
Agent
InvolvedObject
Object
InvolvedWith
Event
Location
Location
Description
The association has additional attributes. Please check
association class AgentEvent.
The association has additional attributes. Please check
association class ObjectEvent.
The association has additional attributes. Please check
association class EventEvent.
The association has additional attributes. Please check
association class EventLocation.
Multiplicity
0..*
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
8.2.2. AgentEvent Association Class
This class allows the association between Agent (or one of its sub-classes: person, organization) and Event (or
one of its sub-classes: movement, incident, anomaly, action). It is not mandatory to associate an Agent with an
Event but one Agent can be associated to multiple different Events. The association further describes the role of
the Agent in the Event.
8.2.2.1. Attributes
UML Name
AgentRole
Data type
AgentRoleInEventType
Description
Enumerated. Describes the
role of Agent in the Event
InvolvementPeriod
Period
The Period of Involvement
Example
the coordinator of
planned action:
01
Source
CISE
8.2.3. EventEvent Association Class
Events (movements, incidents, anomalies, actions) can be involved in zero to multiple events (movements,
incidents, anomalies, actions) in many different roles.
8.2.3.1. Attributes
UML Name
EventRole
Data type
EventRoleInEventType
InvolvementPeriod
Period
Description
Enumerated. Describes the
relationship between two
Events
The Period of Involvement
Example
an event causes
another event : 01
Source
8.2.4. EventLocation Association Class
This class allows the association between Location and Event (or one of its sub-classes: Movement, Anomaly,
Incident and Action). It is not mandatory to associate a Location with an Event but one Location can be
associated to multiple different Events. The association further describes the role of the Location in relation to
the Event.
8.2.4.1. Attributes
UML Name
DateTime
EUCISE2020
Data type
Period
Description
The date and time at which
the Location starts to be
associated to the Event.
Example
for 9am UTC on May
30th, 2002
2002-0530T09:00:00Z
Source
Page 66 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
EventArea
Data type
EventAreaType
Description
LocationRole
LocationRoleInEventType
SourceType
SourceType
Enumerated. Describes the
relationship between the
Event and the Location.
Example
Combat-related
area:
02
The Location is the
start place of the
event:
01
Source
CWA
159311:2009
8.2.5. ObjectEvent Association Class
This class allows the association between Object (or one of its sub-classes: vehicle, cargo) and Event (or one of
its sub-classes: Movement, Anomaly, Incident, Action). It is not mandatory to associate an Object with an Event
but one Object can be associated to multiple different Events. The association further describes the role of the
Object in relation to the Event.
8.2.5.1. Attributes
UML Name
InvolvementPeriod
ObjectRole
Data type
Period
ObjectRoleInEventType
Description
The Period of Involvement
Enumerated. Describes the
relationship between the
Event and the Object.
Example
Source
CISE
The object is the
coordinator of the
event:
01
8.2.6. AgentRoleInEventType Enumeration
This enumeration presents the possible roles that an Agent can have in relation to Event
8.2.6.1. Enumeration Values
Value
01
02
03
04
05
06
07
08
98
99
Label
coordinator
participant
observer
cause
reporter
victim
informed
perpetrator
other
non-specified
Description
Source
Coordinates the Event
Participates the Event
Observes the Event
Causes/has caused the Event
Reports about the Event
Victim of the Event
Is informed about the Event
Is the perpetrator/actor of the Event
Any other role not mentioned above
Role not specified
8.2.6.2. Enumeration Usage
The following attributes use this enumeration as data type:
 AgentRole (AgentEvent)
8.2.7. EventAreaType Enumeration
In order to define the possible types a Location can have when in relation to an Event; we suggest reusing the
work already done during the "tactical situation object" project. Among many artifacts, a list of area type has
been defined. During the scope of the Cooperation project, we chose to limit the enumeration list to the first
level defined by the tactical situation object project. Sub-levels are also defined and their adoption could be
considered in future developments of the data model (see "Disaster and emergency management - Shared
situation awareness - Part 2: Codes for the message structure.").||--Source: ||CWA 15931-1:2009
EUCISE2020
Page 67 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
8.2.7.1. Enumeration Values
Value
Label
Description
AIR
Aerial area
CMB
Combat-related area
DGR
Polluted/dangerous area
FLAME
Area in combustion
GEN
General purpose area
PLUME
Trails of hazardous emissions from an incident
influenced by
the wind and other weather conditions that are laden
with
particulates and gaseous pollutants
Cloud of fine particles resulting from a combustion
suspended
in a gas of hot vapour which potentially can impact on
people
Area where people will be at risk
SMOKE
VULN
Other
NonSpecified
other
nonspecified
Source
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
CWA 159311:2009
Any other role not mentioned above
Role not specified
8.2.7.2. Enumeration Usage
The following attributes use this enumeration as data type:
 EventArea (EventLocation)
8.2.8. EventRoleInEventType Enumeration
This enumeration presents the role an Event can have in respect to another Event.
8.2.8.1. Enumeration Values
Value
01
02
03
04
05
98
99
Label
causes
responds
prevents
encompasses
requires
other
non-specified
Description
Event which is the cause of other Event(s)
Event which responds to other Event(s)
Event which prevents other Event(s)
Event which encompasses the other Event(s)
Event which requires other Event(s)
Any other role not mentioned above
Role not specified
Source
8.2.8.2. Enumeration Usage
The following attributes use this enumeration as data type:
 EventRole (EventEvent)
8.2.9. LocationRoleInEventType Enumeration
This enumeration presents the possible roles that a Location can have in relation to an Event.
EUCISE2020
Page 68 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
8.2.9.1. Enumeration Values
Value
01
02
03
04
98
99
Label
start place
end place
last place
next place
other
non-specified
Description
The Location is the start place of the Event
The Location is the end place of the Event
The Location is the last place known of the Event
The Location is the next place of the Event
Any other role not mentioned above
Role not specified
Source
8.2.9.2. Enumeration Usage
The following attributes use this enumeration as data type:
 LocationRole (EventLocation)
8.2.10.
NatureType Enumeration
This enumeration presents the different natures of an Event.
8.2.10.1. Enumeration Values
Value
01
02
03
04
98
99
Label
observed
declared
estimated
simulated
other
non-specified
Description
The Event is observed
The Event is declared
This Event is estimated
The Event is simulated
Any other type not mentioned above
Type not specified
Source
8.2.10.2. Enumeration Usage
The following attributes use this enumeration as data type:
 NatureType (Event)
8.2.11.
ObjectRoleInEventType Enumeration
This enumeration presents the possible roles that an Object can have in relation to an Event
8.2.11.1. Enumeration Values
Value
01
02
03
04
05
06
07
98
99
Label
coordinator
participant
observer
cause
reporter
victim
mean
other
non-specified
Description
Coordinates the Event
Participates the Event
Observes the Event
Causes/has caused the Event
Reports about the Event
Victim of the Event
A mean used during the Event
Any other role not mentioned above
Role not specified
Source
8.2.11.2. Enumeration Usage
The following attributes use this enumeration as data type:
 ObjectRole (ObjectEvent)
EUCISE2020
Page 69 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
9.
Incident Core Entity
9.1. UML models
9.2. Elements defined in the Core Vocabulary
9.2.1. CrisisIncident Class (subclass of Incident)
The CrisisIncident class is a sub-class of Incident and is used to determine types of incidents related to crisis
situations as defined by the EUROSUR project.
9.2.1.1. Attributes
UML Name
CrisisIncidentType
Data type
CrisisIncidentType
Description
The type of crisis incident
Certainty
CertaintyType
DeathsOnBoard
int
The code denoting the certainty of
the incident as described by the
OASIS Common Alerting Protocol
(OASIS-CAP)
The number of deaths on board as
defined by the draft NSW datasets.
EUCISE2020
Example
Natural
disaster Lightning
strike: 10
observed: 01
0
Source
OASISCAP
NSW
Page 70 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
DiseasesOnBoard
Data type
boolean
InfectionOnBoard
boolean
Instructions
String
NumberOfIIllPersons
int
ResponseType
ResponseType
ResponseUrgency
UrgencyType
Severity
SeverityType
SickAnimalOnBoard
boolean
Identifier
UniqueIdentifier
Metadata
Metadata
NatureType
NatureType
OccurrencePeriod
Period
Description
Indicates the presence of diseases
on board as defined by the draft
NSW datasets.
Indicates the presence of infection
on board as defined by the draft
NSW datasets.
The text describing the
recommended action to be taken by
recipients of the alert message
The number of ill persons on board
as defined by the draft NSW
datasets.
The code denoting the type of
action recommended for the target
audience
The code denoting the urgency of
the incident as described by the
OASIS Common Alerting Protocol
(OASIS-CAP)
The code denoting the severity of
the incident as described by the
OASIS Common Alerting Protocol
(OASIS-CAP)
Indicates the presence of sick
animals on board as defined by the
draft NSW datasets.
Identifier of the event.
Each UniqueIdentifier can be
correlated with other
UniqueIdentifiers, either manually,
by operators, or automatically, by
systems, so that duplicate objects in
the network can be identified and
brought together for a better
understanding of the information
being shared.
see: Core Vocabularies Specification
for "Metadata"
Enumerated. Is used to define
nature of the event. An event can be
observed, declared, estimated or
simulated.
An Event occurs during a period of
time.
Example
False
Source
NSW
False
NSW
Free text
describing
instructions.
0
OASISCAP
shelter: 01
OASISCAP
response
expected: 02
OASISCAP
Severe: 0
OASISCAP
True
NSW
NSW
see: Core
Vocabularies
Specification
for "Metadata"
for an
observed
event:
01
CISE
(*) Inherited attributes are coloured in grey.
9.2.1.2. Association Roles
UML Name
Document
ImpliedRisk
EUCISE2020
Data type
Document
Risk
Description
Multiplicity
0..*
0..*
Page 71 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
InvolvedAgent
Data type
Agent
Description
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class ObjectEvent.
InvolvedWith
Event
The association has additional attributes. Please check
association class EventEvent.
Location
Location
The association has additional attributes. Please check
association class EventLocation.
(*) Inherited association roles are coloured in grey.
Multiplicity
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
9.2.2. Incident Class (subclass of Event)
The class Incident is a sub-class of the abstract class Event. An incident refers to a particular happening,
sometimes criminal but always noteworthy. Incident can have the same associations and relationships than the
parent-class Event. Thus it can have relationship with other agents, objects, documents and locations or it can
be related to risks. An incident can also be associated with other(s) incident(s) (an incident can cause others for
example). Incident has four sub-classes: MaritimeSafetyIncident, IrregularMigrationIncident,
LawInfringementIncident and CrisisIncident.
9.2.2.1. Attributes
UML Name
Certainty
Data type
CertaintyType
DeathsOnBoard
int
DiseasesOnBoard
boolean
InfectionOnBoard
boolean
Instructions
String
NumberOfIIllPersons
int
ResponseType
ResponseType
ResponseUrgency
UrgencyType
Severity
SeverityType
SickAnimalOnBoard
boolean
Identifier
UniqueIdentifier
EUCISE2020
Description
The code denoting the certainty of
the incident as described by the
OASIS Common Alerting Protocol
(OASIS-CAP)
The number of deaths on board as
defined by the draft NSW datasets.
Indicates the presence of diseases on
board as defined by the draft NSW
datasets.
Indicates the presence of infection on
board as defined by the draft NSW
datasets.
The text describing the recommended
action to be taken by recipients of the
alert message
The number of ill persons on board as
defined by the draft NSW datasets.
The code denoting the type of action
recommended for the target audience
The code denoting the urgency of the
incident as described by the OASIS
Common Alerting Protocol (OASISCAP)
The code denoting the severity of the
incident as described by the OASIS
Common Alerting Protocol (OASISCAP)
Indicates the presence of sick animals
on board as defined by the draft NSW
datasets.
Identifier of the event.
Each UniqueIdentifier can be
correlated with other
Example
observed: 01
Source
OASISCAP
0
NSW
False
NSW
False
NSW
Free text
describing
instructions.
0
OASISCAP
shelter: 01
OASISCAP
OASISCAP
response
expected: 02
NSW
Severe: 0
OASISCAP
True
NSW
Page 72 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Metadata
Metadata
NatureType
NatureType
OccurrencePeriod
Period
Description
UniqueIdentifiers, either manually, by
operators, or automatically, by
systems, so that duplicate objects in
the network can be identified and
brought together for a better
understanding of the information
being shared.
see: Core Vocabularies Specification
for "Metadata"
Enumerated. Is used to define nature
of the event. An event can be
observed, declared, estimated or
simulated.
An Event occurs during a period of
time.
Example
Source
see: Core
Vocabularies
Specification
for "Metadata"
for an observed
event:
01
CISE
(*) Inherited attributes are coloured in grey.
9.2.2.2. Association Roles
UML Name
Document
ImpliedRisk
InvolvedAgent
Data type
Document
Risk
Agent
Description
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class ObjectEvent.
InvolvedWith
Event
The association has additional attributes. Please check
association class EventEvent.
Location
Location
The association has additional attributes. Please check
association class EventLocation.
(*) Inherited association roles are coloured in grey.
Multiplicity
0..*
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
9.2.3. IrregularMigrationIncident Class (subclass of Incident)
The IrregularMigrationIncident class is a sub-class of Incident and is used to determine types of incidents
related to irregular migration as defined by the EUROSUR project.
9.2.3.1. Attributes
UML Name
Data type
Description
Example
IrregularMigrationIncidentTyp
e
IrregularMigrationIncidentTyp
e
Irregular
entry
attempt: 03
Certainty
CertaintyType
The type of
irregular
migration
incident
The code
denoting the
certainty of the
incident as
described by the
OASIS Common
Alerting Protocol
(OASIS-CAP)
EUCISE2020
observed:
01
Sourc
e
OASISCAP
Page 73 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
DeathsOnBoard
int
DiseasesOnBoard
boolean
InfectionOnBoard
boolean
Instructions
String
NumberOfIIllPersons
int
ResponseType
ResponseType
ResponseUrgency
UrgencyType
Severity
SeverityType
EUCISE2020
0
Sourc
e
NSW
False
NSW
False
NSW
Free text
describing
instructions.
OASISCAP
0
NSW
shelter: 01
OASISCAP
response
expected:
02
OASISCAP
Severe: 0
OASISCAP
Description
The number of
deaths on board
as defined by the
draft NSW
datasets.
Indicates the
presence of
diseases on
board as defined
by the draft NSW
datasets.
Indicates the
presence of
infection on
board as defined
by the draft NSW
datasets.
The text
describing the
recommended
action to be
taken by
recipients of the
alert message
The number of ill
persons on board
as defined by the
draft NSW
datasets.
The code
denoting the
type of action
recommended
for the target
audience
The code
denoting the
urgency of the
incident as
described by the
OASIS Common
Alerting Protocol
(OASIS-CAP)
The code
denoting the
severity of the
incident as
described by the
OASIS Common
Alerting Protocol
(OASIS-CAP)
Example
Page 74 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
SickAnimalOnBoard
boolean
Identifier
UniqueIdentifier
Metadata
Metadata
NatureType
NatureType
OccurrencePeriod
Period
Description
Indicates the
presence of sick
animals on board
as defined by the
draft NSW
datasets.
Identifier of the
event.
Each
UniqueIdentifier
can be correlated
with other
UniqueIdentifiers
, either manually,
by operators, or
automatically, by
systems, so that
duplicate objects
in the network
can be identified
and brought
together for a
better
understanding of
the information
being shared.
see: Core
Vocabularies
Specification for
"Metadata"
Enumerated. Is
used to define
nature of the
event. An event
can be observed,
declared,
estimated or
simulated.
An Event occurs
during a period
of time.
Example
True
Sourc
e
NSW
see: Core
Vocabularie
s
Specificatio
n for
"Metadata"
for an
observed
event:
01
CISE
(*) Inherited attributes are coloured in grey.
9.2.3.2. Association Roles
UML Name
Document
ImpliedRisk
InvolvedAgent
EUCISE2020
Data type
Document
Risk
Agent
Description
The association has additional attributes. Please check
association class AgentEvent.
Multiplicity
0..*
0..*
0..* (allow
duplicates)
Page 75 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
InvolvedObject
Data type
Object
Description
The association has additional attributes. Please check
association class ObjectEvent.
InvolvedWith
Event
The association has additional attributes. Please check
association class EventEvent.
Location
Location
The association has additional attributes. Please check
association class EventLocation.
(*) Inherited association roles are coloured in grey.
Multiplicity
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
9.2.4. LawInfringementIncident Class (subclass of Incident)
The LawInfringementIncident class is a sub-class of Incident and is used to determine types of incidents related
to law infringement as defined by the EUROSUR project.
9.2.4.1. Attributes
UML Name
LawInfringementIncidentTyp
e
Data type
LawInfringementIncidentTyp
e
Description
The type of law
infringement
incident
Certainty
CertaintyType
DeathsOnBoard
int
DiseasesOnBoard
boolean
InfectionOnBoard
boolean
Instructions
String
NumberOfIIllPersons
int
The code
denoting the
certainty of the
incident as
described by the
OASIS Common
Alerting Protocol
(OASIS-CAP)
The number of
deaths on board
as defined by the
draft NSW
datasets.
Indicates the
presence of
diseases on
board as defined
by the draft NSW
datasets.
Indicates the
presence of
infection on
board as defined
by the draft NSW
datasets.
The text
describing the
recommended
action to be
taken by
recipients of the
alert message
The number of ill
persons on board
as defined by the
EUCISE2020
Example
Human
trafficking Servitude:
05
observed:
01
Source
EUROSU
R
0
NSW
False
NSW
False
NSW
Free text
describing
instructions.
OASISCAP
0
NSW
OASISCAP
Page 76 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
ResponseType
ResponseType
ResponseUrgency
UrgencyType
Severity
SeverityType
SickAnimalOnBoard
boolean
Identifier
UniqueIdentifier
Metadata
Metadata
EUCISE2020
Description
draft NSW
datasets.
The code
denoting the
type of action
recommended
for the target
audience
The code
denoting the
urgency of the
incident as
described by the
OASIS Common
Alerting Protocol
(OASIS-CAP)
The code
denoting the
severity of the
incident as
described by the
OASIS Common
Alerting Protocol
(OASIS-CAP)
Indicates the
presence of sick
animals on board
as defined by the
draft NSW
datasets.
Identifier of the
event.
Each
UniqueIdentifier
can be correlated
with other
UniqueIdentifiers
, either manually,
by operators, or
automatically, by
systems, so that
duplicate objects
in the network
can be identified
and brought
together for a
better
understanding of
the information
being shared.
see: Core
Vocabularies
Example
Source
shelter: 01
OASISCAP
response
expected:
02
OASISCAP
Severe: 0
OASISCAP
True
NSW
see: Core
Vocabularie
s
Page 77 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
NatureType
NatureType
OccurrencePeriod
Period
Description
Specification for
"Metadata"
Enumerated. Is
used to define
nature of the
event. An event
can be observed,
declared,
estimated or
simulated.
An Event occurs
during a period
of time.
Example
Specificatio
n for
"Metadata"
for an
observed
event:
01
Source
CISE
(*) Inherited attributes are coloured in grey.
9.2.4.2. Association Roles
UML Name
Document
ImpliedRisk
InvolvedAgent
Data type
Document
Risk
Agent
Description
Multiplicity
0..*
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class ObjectEvent.
InvolvedWith
Event
The association has additional attributes. Please check
association class EventEvent.
Location
Location
The association has additional attributes. Please check
association class EventLocation.
(*) Inherited association roles are coloured in grey.
9.2.5. MaritimeSafetyIncident Class (subclass of Incident)
The MaritimeSafetyIncident class is a sub-class of Incident and is used to determine types of incidents related to
maritime safety as defined by the SafeSeaNet project.
9.2.5.1. Attributes
UML Name
MaritimeSafetyIncidentType
Data type
MaritimeSafetyIncidentType
Certainty
CertaintyType
DeathsOnBoard
int
DiseasesOnBoard
boolean
EUCISE2020
Description
The type of maritime
safety incident.
The code denoting
the certainty of the
incident as described
by the OASIS
Common Alerting
Protocol (OASIS-CAP)
The number of
deaths on board as
defined by the draft
NSW datasets.
Indicates the
presence of diseases
on board as defined
by the draft NSW
datasets.
Example
pollution
incident: 01
observed: 01
Source
OASISCAP
0
NSW
False
NSW
Page 78 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
InfectionOnBoard
boolean
Instructions
String
NumberOfIIllPersons
int
ResponseType
ResponseType
ResponseUrgency
UrgencyType
Severity
SeverityType
SickAnimalOnBoard
boolean
Identifier
UniqueIdentifier
EUCISE2020
Data type
Description
Indicates the
presence of infection
on board as defined
by the draft NSW
datasets.
The text describing
the recommended
action to be taken by
recipients of the alert
message
The number of ill
persons on board as
defined by the draft
NSW datasets.
The code denoting
the type of action
recommended for
the target audience
The code denoting
the urgency of the
incident as described
by the OASIS
Common Alerting
Protocol (OASIS-CAP)
The code denoting
the severity of the
incident as described
by the OASIS
Common Alerting
Protocol (OASIS-CAP)
Indicates the
presence of sick
animals on board as
defined by the draft
NSW datasets.
Identifier of the
event.
Each
UniqueIdentifier can
be correlated with
other
UniqueIdentifiers,
either manually, by
operators, or
automatically, by
systems, so that
duplicate objects in
the network can be
identified and
brought together for
a better
understanding of the
Example
False
Source
NSW
Free text
describing
instructions.
OASISCAP
0
NSW
shelter: 01
OASISCAP
response
expected: 02
OASISCAP
Severe: 0
OASISCAP
True
NSW
Page 79 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Metadata
Metadata
NatureType
NatureType
OccurrencePeriod
Period
Description
information being
shared.
see: Core
Vocabularies
Specification for
"Metadata"
Example
Enumerated. Is used
to define nature of
the event. An event
can be observed,
declared, estimated
or simulated.
An Event occurs
during a period of
time.
Source
see: Core
Vocabularies
Specification
for
"Metadata"
for an
observed
event:
01
CISE
(*) Inherited attributes are coloured in grey.
9.2.5.2. Association Roles
UML Name
Document
ImpliedRisk
InvolvedAgent
Data type
Document
Risk
Agent
Description
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class ObjectEvent.
InvolvedWith
Event
The association has additional attributes. Please check
association class EventEvent.
Location
Location
The association has additional attributes. Please check
association class EventLocation.
(*) Inherited association roles are coloured in grey.
Multiplicity
0..*
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
9.2.6. PollutionIncident Class (subclass of MaritimeSafetyIncident)
The PollutionIncident is a type of Maritime Safety Incident and is used to exchange specific information about
pollution. The position and extend of the pollution can be described by the entity Location.
9.2.6.1. Attributes
UML Name
AreaCoverPercentage
EUCISE2020
Data type
String
Description
Observer's
assessment of
the percentage
of the boxed
dimensioned
area (length x
width), covered
with pollution. In
percentage. (The
polluted area can
be described by
the entity
Location.)
Example
20
Source
BONN
AGREEMEN
T
Page 80 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Characteristics
String
DriftCourse
int
DriftSpeed
double
PollutionType
PollutionType
Quantity
double
MaritimeSafetyIncidentTyp
e
MaritimeSafetyIncidentTyp
e
Certainty
CertaintyType
EUCISE2020
Data type
Description
Gives type of
pollution (e.g.
type of oil with
viscosity and
pour point,
packaged or bulk
chemical,
sewage). For
chemicals, the
proper name or
United Nations
number, if
known, should
be given.
Appearance, e.g.
liquid, floating
solid, liquid oil,
semi-liquid
sludge, tarry
lumps,
weathered oil,
discolouration of
sea, visible
vapour should
also be given as
well as any
markings on
drums,
containers.
Indicates drift
course in
degrees.
Indicates drift
speed of
pollution knots.
In cases of air
pollution (gas
cloud), drift
speed should be
indicated in
m/sec The pollution
type observed.
Example
Venezuela
crude.
Viscosity
3.780 Cs at
37.8°C.
Rather
viscous
Source
BONN
AGREEMEN
T
138
BONN
AGREEMEN
T
BONN
AGREEMEN
T
Maximum
quantity of oil
pollution in cubic
metres.
The type of
maritime safety
incident.
The code
denoting the
51.4
0.1
OIL
BONN
AGREEMEN
T
BONN
AGREEMEN
T
pollution
incident: 01
observed:
01
OASIS-CAP
Page 81 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
DeathsOnBoard
int
DiseasesOnBoard
boolean
InfectionOnBoard
boolean
Instructions
String
NumberOfIIllPersons
int
ResponseType
ResponseType
ResponseUrgency
UrgencyType
Severity
SeverityType
EUCISE2020
Description
certainty of the
incident as
described by the
OASIS Common
Alerting Protocol
(OASIS-CAP)
The number of
deaths on board
as defined by the
draft NSW
datasets.
Indicates the
presence of
diseases on
board as defined
by the draft NSW
datasets.
Indicates the
presence of
infection on
board as defined
by the draft NSW
datasets.
The text
describing the
recommended
action to be
taken by
recipients of the
alert message
The number of ill
persons on board
as defined by the
draft NSW
datasets.
The code
denoting the
type of action
recommended
for the target
audience
The code
denoting the
urgency of the
incident as
described by the
OASIS Common
Alerting Protocol
(OASIS-CAP)
The code
denoting the
severity of the
incident as
Example
Source
0
NSW
False
NSW
False
NSW
Free text
describing
instructions.
OASIS-CAP
0
NSW
shelter: 01
OASIS-CAP
response
expected:
02
OASIS-CAP
Severe: 0
OASIS-CAP
Page 82 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
SickAnimalOnBoard
boolean
Identifier
UniqueIdentifier
Metadata
Metadata
NatureType
NatureType
OccurrencePeriod
Period
Description
described by the
OASIS Common
Alerting Protocol
(OASIS-CAP)
Indicates the
presence of sick
animals on board
as defined by the
draft NSW
datasets.
Identifier of the
event.
Each
UniqueIdentifier
can be correlated
with other
UniqueIdentifiers
, either manually,
by operators, or
automatically, by
systems, so that
duplicate objects
in the network
can be identified
and brought
together for a
better
understanding of
the information
being shared.
see: Core
Vocabularies
Specification for
"Metadata"
Enumerated. Is
used to define
nature of the
event. An event
can be observed,
declared,
estimated or
simulated.
An Event occurs
during a period
of time.
Example
True
Source
NSW
see: Core
Vocabularie
s
Specificatio
n for
"Metadata"
for an
observed
event:
01
CISE
(*) Inherited attributes are coloured in grey.
9.2.6.2. Association Roles
UML Name
Document
ImpliedRisk
EUCISE2020
Data type
Document
Risk
Description
Multiplicity
0..*
0..*
Page 83 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
InvolvedAgent
Data type
Agent
Description
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class ObjectEvent.
InvolvedWith
Event
The association has additional attributes. Please check
association class EventEvent.
Location
Location
The association has additional attributes. Please check
association class EventLocation.
(*) Inherited association roles are coloured in grey.
Multiplicity
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
9.2.7. CertaintyType Enumeration
This enumeration presents the certainty of an incident as defined by the OASIS common alerting protocol.
Source: OASIS-CAP
9.2.7.1. Enumeration Values
Value
01
02
03
04
05
98
99
Label
observed
likely
possible
unlikely
unknown
other
non-specified
Description
Determined to have occurred or to be ongoing
Likely (p > ~50%)
Possible but not likely (p <= ~50%)
Not expected to occur (p ~ 0)
Certainty unknown
Any other certainty not mentioned above
Certainty not specified
Source
OASIS CAP
OASIS CAP
OASIS CAP
OASIS CAP
OASIS CAP
9.2.7.2. Enumeration Usage
The following attributes use this enumeration as data type:
 Certainty (Incident)
9.2.8. CrisisIncidentType Enumeration
This enumeration presents the incident types related to crisis situations.
9.2.8.1. Enumeration Values
Value
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
Label
natural disaster tsunami
natural disaster earthquake
natural disaster heat wave
natural disaster wild fire
natural disaster flood
natural disaster volcanic eruption
natural disaster storm
natural disaster snow storm
natural disaster tropical storm
natural disaster lightning strike
natural disaster landslide
natural disaster avalanche
natural disaster outbreak of infectious disease and
other bio hazard
natural disaster other
man made disaster man made fire
man made disaster man made explosion
man made disaster maritime accident
EUCISE2020
Description
Source
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
Page 84 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
98
Label
man made disaster aircraft accident
man made disaster radiation
man made disaster oil pollution
man made disaster waste pollution
man made disaster any other man made disaster
violence assassination
man made disaster terrorist attack
violence bombing
violence disorder protest mutiny
violence air missile attack
violence bio chemical attack
violence heavy weapons fire
violence shooting
violence stabbing
violence physical attack
violence execution
violence vandalism
violence robbery
violence kidnapping hostage taking
mines explosives
armed conflict
humanitarian crisis
other
99
non-specified
Description
Source
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
Any other response not
mentioned above
Response not specified
9.2.8.2. Enumeration Usage
The following attributes use this enumeration as data type:
 CrisisIncidentType (CrisisIncident)
9.2.9. IrregularMigrationIncidentType Enumeration
This enumeration presents the irregular migration incident types.
Source: EUROSUR
9.2.9.1. Enumeration Values
Value
01
02
03
04
05
06
07
08
09
10
98
99
Label
irregular border entry
event refused border entry
irregular entry attempt
irregular border exit
refused border entry
irregular exit attempt
irregular stay
facilitator interception
facilitator disclosure
interception in third country territory
other
non-specified
Description
Irregular border entry
Refused border entry
Irregular entry attempt
Irregular border exit
Refused border entry
Irregular exit attempt
Irregular stay
Facilitator interception
Facilitator disclosure
Event::Interception in third country territory
Any other incident not mentioned above
Incident not specified
Source
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
9.2.9.2. Enumeration Usage
The following attributes use this enumeration as data type:
EUCISE2020
Page 85 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0

IrregularMigrationIncidentType (IrregularMigrationIncident)
9.2.10.
LawInfringementIncidentType Enumeration
This enumeration presents the law infringement incident types.
Source: EUROSUR
9.2.10.1. Enumeration Values
Value
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
Label
human trafficking exploitation of prostitution of others
human trafficking other forms of sexual exploitation
human trafficking forced labour or services
human trafficking slavery or practices similar to slavery
human trafficking servitude
human trafficking exploitation of activities associated
with begging or of unlawful activities
human trafficking removal of organs
human trafficking other
drug smuggling marihuana
drug smuggling cocaine
drug smuggling hashish
drug smuggling cannabis
drug smuggling heroin
drug smuggling amphetamine
drug smuggling metamphetamine
drug smuggling ecstasy
drug smuggling opium
drug smuggling hallucinogens
drug smuggling other drugs
goods smuggling goods carried with no required permits
goods smuggling excise goods
goods smuggling counterfeited products
goods smuggling natural resources minerals
goods smuggling threatened species
goods smuggling cultural heritage goods
smuggling in waste and other hazardous material waste
smuggling in waste and other hazardous material
chemical
smuggling in waste and other hazardous material
biohazard
smuggling in waste and other hazardous material radio
active
smuggling in waste and other hazardous material nuclear
smuggling in waste and other hazardous material other
dangerous substances
smuggling in weapon and related accessories arms
weapons
smuggling in weapon and related accessories weapons of
mass destruction
smuggling in weapon and related accessories
ammunition
smuggling in weapon and related accessories explosives
smuggling in other material
other related cross border criminal activity stolen vehicle
EUCISE2020
Description
Source
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
Page 86 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
38
39
40
41
42
43
98
Label
other related cross border criminal activity document
falsification fraud
other related cross border criminal activity other
law infringement by vessels
illegal flight of an aircraft
law infringement by vehicles
other administrative offense
other
99
non-specified
Description
Source
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
Any other response not
mentioned above
Response not specified
9.2.10.2. Enumeration Usage
The following attributes use this enumeration as data type:
 LawInfringementIncidentType (LawInfringementIncident)
9.2.11.
MaritimeSafetyIncidentType Enumeration
This enumeration presents the maritime safety incident types.
Source: SSN IRG
9.2.11.1. Enumeration Values
Value
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
98
99
Label
pollution
waste
lost found containers
VTS rules infringement
banned ship
insurance failure
result inspection
pilot or port report
fire
collision
medico
grounding
flooding
list
capsizing
engine failure
structural failure
steering gear failure
electrical generating system failure
navigation equipment failure
communication equipment failure
incident nature abandon ship
incident nature sinking
detained ship
other
non-specified
Description
Pollution
Waste
Lost or Found Containers
VTS Rules Infringement
Banned Ship
Insurance Failure
Result Inspection
Pilot Or Port Report
Fire
Collision
Medico
Grounding
Flooding
List
Capsizing
Engine Failure
Structural failure
Steering gear failure
Electrical generating system failure
Navigation equipment failure
Communication equipment failure
Abandon ship
Sinking
DetainedShip
Any other incident not mentioned above
Incident not specified
Source
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
SSN IRG
9.2.11.2. Enumeration Usage
The following attributes use this enumeration as data type:
 MaritimeSafetyIncidentType (MaritimeSafetyIncident)
EUCISE2020
Page 87 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
9.2.12.
PollutionType Enumeration
9.2.12.1. Enumeration Values
Value
OIL
CHEM
FISH
VEG
OTH
UNK
Label
Oil
Chemical
Fish Oil or Waste
Vegetable Oil or Waste
Other
Unknown
Description
Oil
Chemical
Fish Oil or Waste
Vegetable Oil or Waste
Other
Unknown
Source
BONN AGREEMENT
BONN AGREEMENT
BONN AGREEMENT
BONN AGREEMENT
BONN AGREEMENT
BONN AGREEMENT
9.2.12.2. Enumeration Usage
The following attributes use this enumeration as data type:
 PollutionType (PollutionIncident)
9.2.13.
ResponseType Enumeration
This enumeration presents the incident’s response types as defined by the OASIS common alerting protocol.
Source: OASIS-CAP
9.2.13.1. Enumeration Values
Value
01
Label
shelter
Description
Take shelter in place or per <instruction>
02
evacuate
Relocate as instructed in the <instruction>
03
prepare
Make preparations per the <instruction>
04
execute
Execute a pre-planned activity identified in <instruction>
05
avoid
Avoid the subject event as per the <instruction>
06
monitor
Attend to information sources as described in <instruction>
07
assess
08
all clear
09
none
Evaluate the information in this message. (This value SHOULD NOT be
used in public warning applications.)
The subject event no longer poses a threat or concern and any follow on
action is described in <instruction>
No action recommended
98
99
other
nonspecified
Source
OASIS
CAP
OASIS
CAP
OASIS
CAP
OASIS
CAP
OASIS
CAP
OASIS
CAP
OASIS
CAP
OASIS
CAP
OASIS
CAP
Any other response not mentioned above
Response not specified
9.2.13.2. Enumeration Usage
The following attributes use this enumeration as data type:
 ResponseType (Incident)
9.2.14.
EUCISE2020
SeverityType Enumeration
Page 88 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
This enumeration presents the severity of an incident as defined by the OASIS common alerting protocol.
Source: OASIS-CAP
9.2.14.1. Enumeration Values
Value
01
02
03
04
05
98
99
Label
extreme
severe
moderate
minor
unknown
other
non-specified
Description
Extraordinary threat to life or property
Significant threat to life or property
Possible threat to life or property
Minimal threat to life or property
Severity unknown
Any other severity not mentioned above
Severity not specified
Source
OASIS CAP
OASIS CAP
OASIS CAP
OASIS CAP
OASIS CAP
9.2.14.2. Enumeration Usage
The following attributes use this enumeration as data type:
 Severity (Incident)
9.2.15.
UrgencyType Enumeration
This enumeration presents the urgency of an incident response as defined by the OASIS common alerting
protocol.
Source: OASIS-CAP
9.2.15.1. Enumeration Values
Value
01
02
03
04
05
98
99
Label
immediate
expected
future
past
unknown
other
non-specified
Description
Responsive action should be taken immediately
Responsive action should be taken soon (within next hour)
Responsive action should be taken in the near future
Responsive action is no longer required
Urgency not known
Any other urgency not mentioned above
Urgency not specified
Source
OASIS CAP
OASIS CAP
OASIS CAP
OASIS CAP
OASIS CAP
9.2.15.2. Enumeration Usage
The following attributes use this enumeration as data type:
 ResponseUrgency (Incident)
EUCISE2020
Page 89 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
10. Location Core Entity
10.1. UML models
10.2. Elements defined in the Core Vocabulary
10.2.1.
Location Class (subclass of Entity)
Locations can be described in three principal ways: by using a place name, geometry or an address. The specific
context will determine which method of describing a location is most appropriate. ISO 19112 defines a location
as "an identifiable geographic place". With this in mind, "Eiffel Tower", "Madrid" and "California" are all
locations and this is a common way of representing locations in public sector data, i.e. simply by using a
recognized name. Such identifiers are common although they can be highly ambiguous as many places share
the same or similar names.
In addition to a simple (string) label or name for a Location, the identifier property allows defining a Location by
a Uniform Resource Identifier (URI), such as a GeoNames or DBpedia URI.
No cardinality constraints are placed on any property of the Location class so as to maximize flexibility.
10.2.1.1. Attributes
EUCISE2020
Page 90 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Geometry
Geometry
LocationQualitativeAccuracy
LocationQualitativeAccuracyType
LocationZone
LocationZoneType
Metadata
Metadata
OperationalPurpose
OperationalPurposeType
10.2.2.
Data type
Description
A Geometry Object
which represents a
Georeference
Describes the
qualitative accuracy
of location:
high/medium/low
Provides the types of
location.
Enumerated
Provides a
placeholder for
Metadata
Provides the types of
operational purpose.
Enumerated
Example
Source
High
High
Seas
Search
area
MeteoOceanographicCondition Class (subclass of Entity)
This class allows the description of the meteorological oceanographic condition of a given Location.
10.2.2.1. Attributes
UML Name
AirTemperature
Data type
double
CloudCeiling
int
CloudCover
CloudCoverType
Precipitation
ReferencePeriod
Salinity
int
Period
double
SeaCondition
SeaConditionType
SeaLevelPressure
double
SourceType
SourceType
TidalCurrentDirection
double
EUCISE2020
Description
Air temperature is a measure of
how hot or cold the air is. It is
the most commonly measured
weather parameter.
Ceiling is a measurement of the
cloud base height relative to the
ground (in meters).
Cloud cover (also known as
cloudiness, cloudage or cloud
amount) refers to the fraction of
the sky obscured by clouds
when observed from a particular
location.
Period of reference
Salinity is the saltiness or
dissolved salt content of the sea
(in g per Kg of water).
In oceanography, a sea state is
the general condition of the free
surface on a large body of
water—with respect to wind
waves and swell—at a certain
location and moment.
Atmospheric pressure at sea
level (in HPa).
Indicate if the oceanographic
condition was observed or
estimated. Enumerated.
Indicates current direction in
degrees andknots. The direction
Example
Source
2000(m)
4 (sky half
cloudy)
5 (g/Kg)
04
(moderate)
100.15
(HPa)
Observed
180
SSN IRG
Page 91 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
TidalCurrentSpeed
double
Tides
TidesType
Visibility
double
WaterTemperature
WaveDirection
double
double
WaveHeight
double
WeatherCondition
WeatherConditionType
WindCurrentDirection
double
WindCurrentSpeed
double
Description
always indicates the direction in
which the current is flowing
Indicates current speed in tenths
of knots.
Tides are the rise and fall of sea
levels caused by the combined
effects of gravitational forces
exerted by the Moon, Sun, and
rotation of the Earth.
Visibility should be indicated in
nautical miles.
Water temperature.
Idicates wave direction in
degrees.
Indicates the wave height in
metres.
Type of weather condition.
Enumerated.
Indicates wind direction in
degrees. The direction always
indicates from where the wind is
blowing.
Indicates wind speed in m/sec.
Example
0.3
Source
SSN IRG
low (low
tides)
10
SSN IRG
180
SSN IRG
2
SSN IRG
HUM
270
CWA
159311:2009
SSN IRG
10
SSN IRG
10.2.2.2. Association Roles
UML Name
Location
10.2.3.
Data type
Location
Description
Multiplicity
0..1
NamedLocation Class (subclass of Location)
Location with a given name.
10.2.3.1. Attributes
UML Name
GeographicIdentifie
r
EUCISE2020
Data type
XSD::anyURI
Description
Example
A URI that identifies the
location.
GeoNames.org provides
stable, widely
recognized identifiers
for more than 10 million
geographical names that
can be used as links to
further information. For
example,
http://sws.geonames.or
g/593116/ identifies the
Lithuanian capital
Vilnius. Unfortunately
these URIs cannot easily
be automatically
deduced since the URI
scheme uses simple
http://sws.geonames.or
g/593116/
Sour
ce
IETF
RFC
398
6
Page 92 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
GeographicName
EUCISE2020
Data type
String
Description
numeric codes. Finding
a GeoNames identifier
for a Location is almost
always a manual
process. Where such
identifiers are known or
can be found, however,
it is recommended that
they be used.
The use of a URIs has
added advantages:
1.it can be used by
automated systems to
look up additional data
(linked data);
2. a triple store may
store only one copy of
the URI, whereas if a
string is used, a copy of
that string is always
stored for each and
every person in the
database. Thus, in large
data sets, the saving on
memory capacity and
the improvement in
transmission efficiency
can be substantial.
String A geographic
name is a proper noun
applied to a spatial
object. The following are
all valid geographic
names for the Greek
capital:
• Ana (the Greek
endonym written in the
Greek script)
• Athina (the standard
Romanisation of the
endonym)
• Athens (the English
language exonym)
The country codes
defined in ISO 3166 may
be used as geographic
names and these are
generally preferred over
either the long form or
short form of a country’s
name (as they are less
error prone). The
Example
Athens
Sour
ce
ISA
COR
E
Page 93 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Description
Geometry
Geometry
LocationQualitative
Accuracy
LocationQualitativeAcc
uracyType
LocationZone
LocationZoneType
Metadata
Metadata
OperationalPurpose
OperationalPurposeTyp
e
Example
Publications Office of
the European Union
recommends the use of
ISO 3166-1 codes for
countries in all cases
except two:
• use ‘UK’ in preference
to the ISO 3166 code GB
for the United Kingdom;
• use ‘EL’ in preference
to the ISO 3166 code GR
for Greece.
Where a country has
changed its name or no
longer exists (such as
Czechoslovakia,
Yugoslavia etc.) use the
ISO 3166-3 code [ISO
3166-3].
A Geometry Object
which represents a
Georeference
Describes the qualitative
accuracy of location:
high/medium/low
Provides the types of
location. Enumerated
Provides a placeholder
for Metadata
Provides the types of
operational purpose.
Enumerated
Sour
ce
High
High Seas
Search area
(*) Inherited attributes are coloured in grey.
10.2.4.
PortFacilityLocation Class (subclass of Location)
Location of one of the facilities contained in a port.
10.2.4.1. Attributes
UML Name
PortFacilityName
PortFacilityNumber
EUCISE2020
Data type
String
String
Description
Example
Source
Port facility
identified by its IMO
port facility number.
Port facility number
is used identify each
port facility within
each port. Where
the whole port is
being classified as a
single port facility,
this number is 0000.
The port facility
Port
facility
assigned
with
number
0000:
0000
NSW
Page 94 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Description
number is not
duplicated inside
one port but the
same number can be
reused in different
ports. When used in
connection with the
port code forms an
unique identification
for each port facility.
PortSecurityLevel
Geometry
ISPSSecurityLevelType
Geometry
LocationQualitativeAccuracy
LocationQualitativeAccuracyType
LocationZone
LocationZoneType
Metadata
Metadata
OperationalPurpose
OperationalPurposeType
A Geometry Object
which represents a
Georeference
Describes the
qualitative accuracy
of location:
high/medium/low
Provides the types of
location.
Enumerated
Provides a
placeholder for
Metadata
Provides the types of
operational purpose.
Enumerated
Example
Source
High
High
Seas
Search
area
(*) Inherited attributes are coloured in grey.
10.2.5.
PortLocation Class (subclass of Location)
Location describing the position/area of a port.
10.2.5.1. Attributes
UML Name
LocationCode
EUCISE2020
Data type
String
Description
A location is defined as
any named
geographical place,
recognized by a
competent national
body, either with
permanent facilities
used for goods
movement associated
with trade, and used
for these purposes, or
proposed by the
government
concerned or by a
competent national or
international
organization for
inclusion in the
Exampl
e
NOOSL
Source
UN/LOCOD
E
Page 95 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Description
Exampl
e
Source
UN/LOCODE. A port is
any location with
permanent facilities at
which vessels can load
or discharge cargo
moving in maritime
traffic. An anchoring
area is any location
official recommended
for anchoring. There
are areas dedicated for
different type of
vessels or general.
Such areas are
announced in
notifications or in sea
charts.
A code is data
transformation or data
representation in
different forms
according to preestablish rules.
(Definition adapted
from ISO 5127-1:1983)
A code element is
result of applying a
code to an element in
a set of elements to be
coded. In UN/LOCODE,
one code element
represents the name
of a port, or a location,
i.e. anchoring area,
and in addition
possible subsidiary
location, i.e. an ISPSarea or -terminal.
(Definition adapted
from ISO 2382-4/1987)
A five-character code
element is provided
for each location
included UN/LOCODE
and consists of:
a) two letters
identifying the
country, according to
the ISO 3166 twoletter Code for the
representation of
names of countries,
EUCISE2020
Page 96 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Description
Exampl
e
Source
and UN/ECE/FAL
recommendation No.
3, and
b) three characters
identifying the location
within the country.
e.g. A vessel call for
Norway, Oslo in the
five-character code
elements is: “NOOSL”
the official Locode list
of SSN is obtained
from the UNECE
(http://www.unece.or
g/),
PortName
PortSecurityLevel
String
ISPSSecurityLevelType
Geometry
Geometry
LocationQualitativeAccur
acy
LocationQualitativeAccuracyT
ype
LocationZone
LocationZoneType
Metadata
Metadata
OperationalPurpose
OperationalPurposeType
Enumerated. Port's
security level
according to ISPS
standard.
A Geometry Object
which represents a
Georeference
Describes the
qualitative accuracy of
location:
high/medium/low
Provides the types of
location. Enumerated
Provides a placeholder
for Metadata
Provides the types of
operational purpose.
Enumerated
Port
has
been
assigne
d the
ISPS
Securit
y level
2: 02
NSW::Voya
ge
High
High
Seas
Search
area
(*) Inherited attributes are coloured in grey.
10.2.6.
Geometry Datatype
This class allows the definition of Georeferenced areas.
10.2.6.1. Attributes
UML Name
Altitude
EUCISE2020
Data
type
Strin
g
Description
Geographic
Altitude,
expressed
using the
Example
Sourc
e
37° 59' 0" N
Page 97 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data
type
Latitude
Strin
g
Longitude
Strin
g
WKT
Strin
g
XMLGeometr
y
Strin
g
10.2.7.
Description
WGS84
reference.
Geographic
Latitude,
expressed
using the
WGS84
reference.
Geographic
Longitude,
expressed
using the
WGS84
reference.
Well-known
text (WKT)
is a text
markup
language for
representin
g vector
geometry
objects on a
map
Geometry
defined by
an XML file
such as KML
Sourc
e
Example
37° 59' 0" N
23° 44' 0" E
POINT (30 10)
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2">
<Placemark>
<name>Simple placemark</name>
<description>Attached to the ground. Intelligently places
itself
at the height of the underlying terrain.
</description>
<Point> <coordinates>122.0822035425683,37.42228990140251,0</coordinates
>
</Point>
</Placemark>
</kml>
CloudCoverType Enumeration
Cloud cover is estimated in terms of how many eighths of the sky are covered in cloud, ranging from 0 oktas
(completely clear sky) through to 8 oktas (completely overcast).
10.2.7.1. Enumeration Values
Value
0
1
2
3
4
5
6
EUCISE2020
Label
clear sky
1 okta
2 oktas
3 oktas
4 oktas
5 oktas
6 oktas
Description
Sky completely clear
Source
Sky half cloudy
Page 98 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
Label
7 oktas
8 oktas
sky obscured
7
8
9
Description
Source
Sky completely cloudy
Sky obstructed from view
10.2.7.2. Enumeration Usage
The following attributes use this enumeration as data type:
 CloudCover (MeteoOceanographicCondition)
10.2.8.
LocationQualitativeAccuracyType Enumeration
10.2.8.1. Enumeration Values
Value
01
02
03
98
99
Label
high
medium
low
other
non-specified
Description
High qualitative accuracy
Medium qualitative accuracy
Low qualitative accuracy
Qualitative accuracy not listed here
The qualitative accuracy is not declared
Source
10.2.8.2. Enumeration Usage
The following attributes use this enumeration as data type:
 LocationQualitativeAccuracy (Location)
10.2.9.
LocationZoneType Enumeration
Source: EUROSUR
10.2.9.1. Enumeration Values
Value
01
02
10
11
Label
high seas
territorial
waters
coast line
contiguous
zone
port
control point
green border
inland
exclusive
economic area
third country
INW
12
NAT
Third country
Inland waterway. A body of water, such as a river, canal or lake. It
may be navigable if it is deep and wide enough for a vessel to pass
and there are no obstructions.
Natural / rural environment
98
99
other
non-specified
Location type not listed here
The location type is not declared
03
04
05
06
07
08
09
EUCISE2020
High seas
Territorial waters
Description
Source
EUROSUR
EUROSUR
Coast line
Contiguous zone
EUROSUR
EUROSUR
Port
Control point
Green border
Inland
Exclusive Economic Area
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
EUROSUR
CWA 159311:2009
CWA 159311:2009
Page 99 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
10.2.9.2. Enumeration Usage
The following attributes use this enumeration as data type:
 LocationZone (Location)
10.2.10.
MetocType Enumeration
10.2.10.1.
Value
Enumeration Values
Label
observed
declared
estimated
simulated
other
non-specified
01
02
03
04
98
99
10.2.11.
Description
By observation
By declaration
By estimation
By simulation
METOC type not listed here
The METOC type is not declared
Source
OperationalPurposeType Enumeration
10.2.11.1.
Value
01
02
98
99
Enumeration Values
Label
search area
surveillance area
other
non-specified
10.2.11.2.
Description
Search area
Surveillance area
Operational purpose not listed here
The operational purpose is not declared
Source
Enumeration Usage
The following attributes use this enumeration as data type:
 OperationalPurpose (Location)
10.2.12.
SeaConditionType Enumeration
10.2.12.1.
Value
00
01
02
03
04
05
06
07
08
09
Enumeration Values
Label
calm (glassy)
calm (rippled)
smooth (wavelets)
slight
moderate
rough
very rough
high
very high
phenomenal
10.2.12.2.
Description
0 metres (0 ft)
Waves from 0 to 0.1 metres (0.00 to 0.33 ft)
Waves from 0.1 to 0.5 metres (3.9 in to 1 ft 7.7 in)
Waves from 0.5 to 1.25 metres (1 ft 8 in to 4 ft 1 in)
Waves from 1.25 to 2.5 metres (4 ft 1 in to 8 ft 2 in)
Waves from 2.5 to 4 metres (8 ft 2 in to 13 ft 1 in)
Waves from 4 to 6 metres (13 to 20 ft)
Waves from 6 to 9 metres (20 to 30 ft)
Waves from 9 to 14 metres (30 to 46 ft)
Waves over 14 metres (46 ft)
Source
WMO
WMO
WMO
WMO
WMO
WMO
WMO
WMO
WMO
WMO
Enumeration Usage
The following attributes use this enumeration as data type:
 SeaCondition (MeteoOceanographicCondition)
EUCISE2020
Page 100 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
10.2.13.
TidesType Enumeration
10.2.13.1.
Enumeration Values
Value
Low
High
Label
low tides
high tides
10.2.13.2.
Description
Source
low tides
high tides
Enumeration Usage
The following attributes use this enumeration as data type:
 Tides (MeteoOceanographicCondition)
10.2.14.
WeatherConditionType Enumeration
Source: CWA 15931-1:2009
10.2.14.1.
Enumeration Values
Value
HUM
Label
hum
weather
ICY
icy
weather
Icy conditions
TDS
tds
weather
Thunderstorm conditions
WIN
win
weather
Windy conditions
DRZLE
drzle
weather
FOG
fog
weather
Other
NonSpecified
other
nonspecified
Drizzle. Fairly uniform precipitation composed exclusively of fine
drops very close together. Drizzle appears to float while following air
currents although, unlike fog droplets, it falls to the ground. It
usually falls from low stratus clouds and is frequently accompanied
by low visibility and fog.
Fog/mist. A visible aggregate of minute water particles (droplets)
which are based on the Earth’s surface, extends vertically, and
reduceshorizontal visibility to less than 5/8 mile (1,000 meters).
Unlike drizzle, FOG does not fall to the ground.
Weather Condition type not listed here
Weather Condition type is not declared
10.2.14.2.
Description
Humid conditions
Source
CWA
159311:2009
CWA
159311:2009
CWA
159311:2009
CWA
159311:2009
CWA
159311:2009
CWA
159311:2009
Enumeration Usage
The following attributes use this enumeration as data type:
 WeatherCondition (MeteoOceanographicCondition)
EUCISE2020
Page 101 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
11. Metadata Core Entity
11.1. UML models
11.2. Elements defined in the Core Vocabulary
11.2.1.
Metadata Datatype
The class provides information about the properties of the data communicated through the system, excluding
the content of the data.
11.2.1.1. Attributes
UML Name
Data type
Description
Abstract
String
A short account of the resource.
Comments
String
Additional comments on the
resource.
CreationDate
XSD::DateTime
Creator
Agent
The date and time the information
was created.
An entity primarily responsible for
making the resource.
EUCISE2020
Examp
le
Free
text
abstra
ct
descri
bing
the
data
Comm
ents as
free
text
Source
DC::Terms
Finnish
Border
Guard
Page 102 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Description
Description
String
A detailed account of the resource.
Designation
String
FileMediaType
FileMediaType
Refers to the class/entity which is
described by the metadata.
Content types and subtypes as
defined in RFC 2046
(Main types include: application,
audio, example, image, message,
model, multipart, text, video)
FileSchema
XSD::anyURI
FileURI
XSD::anyURI
InformationReliabil
ityLevel
InformationSecurit
yClassification
InformationSensitiv
ityDegree
InformationReliability
LevelType
InformationSecurityCl
assificationType
InformationSensitivity
DegreeType
Enumerated
Language
String
PublicationDate
XSD::DateTime
Publisher
Agent
Alpha-3 codes which represent the
names of language of the resource.
For the languages which are
defined with two codes, the
´terminological´ code (ISO 639-2/T)
is used instead of the
´bibliographic´ one (see
http://www.iso.org/iso/catalogue_
detail?csnumber=4767).
The date and time the information
was published
An entity responsible for making
the resource available.
ValidityPeriod
Period
11.2.2.
Examp
le
free
text
descri
bing
the
data
image/
jpeg or
video/
mpeg
etc.
Source
DC::Terms
ETF:RFC2046:
:ContentType::MediaT
ype
IETF::RFC398
6::URI
IETF::RFC398
6::URI
Enumerated
This enumeration presents the
possible values for information
sensitivity degree. The Traffic Light
Protocol (TLP) of US-CERT is
applied (http://www.uscert.gov/tlp ).
EU
Secret
AMBE
R
pol for
Polish
Traffic Light
Protocol
(TLP) of USCERT is
applied
(http://www.
uscert.gov/tlp )
ISO 639-2/T
Finnish
Border
Guard
Validity for a specific Period of time
FileMediaType Enumeration
Content types and subtypes as defined in RFC 2046||(Main types include: application, audio, example, image,
message, model, multipart, text, video)
Source: IETF RFC 2046
11.2.2.1. Enumeration Values
EUCISE2020
Page 103 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
.3dm
.avi
.jpeg
Label
Description
Source
x-world/x-3dmf
video/avi
image/jpeg
11.2.2.2. Enumeration Usage
The following attributes use this enumeration as data type:
 FileMediaType (Metadata)
11.2.3.
InformationReliabilityLevelType Enumeration
This enumeration provides a quantitative evaluation of the reliability level of the information that is provided.
11.2.3.1. Enumeration Values
Value
01
Label
very high confidence, verified data
02
high confidence
03
confident
04
low confidence, unsure source of
verification
very low confidence, no verification, cooperative target
non-specified
05
99
Description
Information and material whose owner is
extremely confident of
Information and material whose owner is very
confident of
Information and material whose owner is
confident of
Information and material whose owner is not
confident of
Information and material whose owner is very
unconfident of
Information and material whose reliability is
not specified
Source
11.2.3.2. Enumeration Usage
The following attributes use this enumeration as data type:
 InformationReliabilityLevel (Metadata)
11.2.4.
InformationSecurityClassificationType Enumeration
This enumeration presents the possible values for information security classification. The enumeration is based
in the security rules for protecting EU classified information (<a href="http://eurlex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2011:141:0017:0065:EN:PDF"><font
color="#000080"><u>http://eurlex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2011:141:0017:0065:EN:PDF</u></font></a> ).
11.2.4.1. Enumeration Values
Value
01
Label
EU top
secret
02
EU secret
03
EU
confidential
EUCISE2020
Description
Information and material the unauthorized disclosure of which could cause
exceptionally grave prejudice to the essential interests of the European
Union or of one or more of the Member States
Information and material the unauthorized disclosure of which could
seriously harm the essential interests of the European Union or of one or
more of the Member States
Information and material the unauthorized disclosure of which could harm
the essential interests of the European Union or of one or more of the
Member States
Source
Page 104 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
04
Label
EU restricted
05
nonclassified
nonspecified
99
Description
Information and material the unauthorized disclosure of which could be
disadvantageous to the interests of the European Union or of one or more
of the Member States
It can be used for information and material whose classification level is still
pending
It can be used for information and material whose classification level is not
specified
Source
11.2.4.2. Enumeration Usage
The following attributes use this enumeration as data type:
 InformationSecurityClassification (Metadata)
11.2.5.
InformationSensitivityDegreeType Enumeration
This enumeration presents the possible values for information sensitivity degree. The Traffic Light Protocol (TLP)
of US-CERT is applied (<a href="http://www.us-cert.gov/tlp"><font color="#000080"><u>http://www.uscert.gov/tlp</u></font></a> ).
Source: US-CERT
11.2.5.1. Enumeration Values
Value
01
Label
red
02
amber
03
green
04
white
99
nonspecified
Description
TLP: RED when information cannot be effectively acted upon by additional
parties, and could lead to impacts on a party's privacy, reputation, or
operations if misused.
TLP: AMBER when information requires support to be effectively acted upon,
but carries risks to privacy, reputation, or operations if shared outside of the
organizations involved.
TLP: GREEN when information is useful for the awareness of all participating
organizations as well as with peers within the broader community or sector.
TLP: WHITE when information carries minimal or no foreseeable risk of
misuse, in accordance with applicable rules and procedures for public release.
It can be used for information and material whose classification level is not
specified
Source
11.2.5.2. Enumeration Usage
The following attributes use this enumeration as data type:
 InformationSensitivityDegree (Metadata)
EUCISE2020
Page 105 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
12. Movement Core Entity
12.1. UML models
12.2. Elements defined in the Core Vocabulary
12.2.1.
Movement Class (subclass of Event)
It is a subclass of event. The Movement entity is linked to Voyage. Movement can be actual (e.g. current
position, heading and speed), Historical data or planned in the future and can also be expressed taking into
account other entities as location, object, etc.
12.2.1.1. Attributes
UML Name
MovementType
Data type
MovementType
Purpose
VoyageNumber
String
String
Identifier
UniqueIdentifier
EUCISE2020
Description
Many different movements types can be
described
The purpose of the movement
This is an operator-assigned reference
code for a voyage and serves the
purpose of the operator.
Identifier of the event.
Each UniqueIdentifier can be correlated
with other UniqueIdentifiers, either
manually, by operators, or automatically,
Example
Route Plan
Leisure
111124
Source
NSW
Page 106 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Metadata
Metadata
NatureType
NatureType
Description
by systems, so that duplicate objects in
the network can be identified and
brought together for a better
understanding of the information being
shared.
see: Core Vocabularies Specification for
"Metadata"
Enumerated. Is used to define nature of
the event. An event can be observed,
declared, estimated or simulated.
OccurrencePeriod Period
An Event occurs during a period of time.
(*) Inherited attributes are coloured in grey.
Example
Source
see: Core
Vocabularies
Specification for
"Metadata"
for an observed
event:
01
CISE
12.2.1.2. Association Roles
UML Name
Document
ImpliedRisk
InvolvedAgent
Data type
Document
Risk
Agent
Description
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class ObjectEvent.
InvolvedWith
Event
The association has additional attributes. Please check
association class EventEvent.
Location
Location
The association has additional attributes. Please check
association class EventLocation.
(*) Inherited association roles are coloured in grey.
12.2.2.
Multiplicity
0..*
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
MovementType Enumeration
This enumeration presents the possible types of processes used to perform the objects’ correlation.
12.2.2.1. Enumeration Values
Value
01
Label
route plan
02
03
04
voyage
voyage leg
search
pattern
patrol route
plan
other
nonspecified
05
98
99
Description
Expected locations/direction and movements that a vessels will follow
during a voyage. It is known before departure
Journey involving travel by sea
Stage of a Voyage
Search pattern for a certain area
Source
Patrol route plan for a certain area
Movement type not included above
Movement type non-specified
12.2.2.2. Enumeration Usage
The following attributes use this enumeration as data type:
 MovementType (Movement)
EUCISE2020
Page 107 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
13. Object Core Entity
13.1. UML models
13.2. Elements defined in the Core Vocabulary
13.2.1.
Aircraft Class (subclass of Vehicle)
13.2.1.1. Attributes
UML Name
MaximumSpeed
Data type
double
Nationality
String
Description
The vehicle’s maximum speed
measured in knots
Two-letter country codes to represent
countries, dependent territories, and
special areas of geographical interest.
Represent the flag for a Vessel.
TotalPersonsOnBoard
Colour
ExternalMarkings
Identifier
int
ColourType
String
UniqueIdentifier
The total number of persons on board
Colour information about the object
External markings of the object
Identifier of the object.
EUCISE2020
Example
20
Source
EUROSUR
Country
code for
Portugal:
PT
(Country
code for
Portugal)
10
Red
ABER
ISO 31661
EUROSUR
FLUX
Page 108 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Metadata
Metadata
Name
String
(*) Inherited attributes are coloured in grey.
Description
Each UniqueIdentifier can be correlated
with other UniqueIdentifiers, either
manually, by operators, or
automatically, by systems, so that
duplicate objects in the network can be
identified and brought together for a
better understanding of the
information being shared.
Metadata related to the object
Name of the object
Example
ABERIII
Source
NSW
13.2.1.2. Association Roles
UML Name
Cargo
CorrespondentAsset
Document
InvolvedAgent
Data type
Cargo
OperationalAsset
Document
Agent
InvolvedEvent
Event
InvolvedRisk
Location
Risk
Location
Description
The association has additional attributes.
Please check association class AgentObject.
The association has additional attributes.
Please check association class ObjectEvent.
The association has additional attributes.
Please check association class ObjectLocation.
Vehicles
Vehicle
(*) Inherited association roles are coloured in grey.
Multiplicity
0..1
0..1
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..*
0..* (allow
duplicates)
0..*
13.2.1.3. Constraints
Name
Description
OCL Constraint
Minimum of
The number of TotalPersonsOnBoard can not be smaller than
TotalPersonsOnBoard
the sum of master/crewmembers and passengers
(*) Inherited constraints are coloured in grey.
13.2.2.
LandVehicle Class (subclass of Vehicle)
13.2.2.1. Attributes
UML Name
MaximumSpeed
Data type
double
Nationality
String
Description
The vehicle’s maximum speed
measured in knots
Two-letter country codes to represent
countries, dependent territories, and
special areas of geographical interest.
Represent the flag for a Vessel.
TotalPersonsOnBoard
Colour
ExternalMarkings
Identifier
int
ColourType
String
UniqueIdentifier
The total number of persons on board
Colour information about the object
External markings of the object
Identifier of the object.
EUCISE2020
Example
20
Source
EUROSUR
Country
code for
Portugal:
PT
(Country
code for
Portugal)
10
Red
ABER
ISO 31661
EUROSUR
FLUX
Page 109 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Metadata
Metadata
Name
String
(*) Inherited attributes are coloured in grey.
Description
Each UniqueIdentifier can be correlated
with other UniqueIdentifiers, either
manually, by operators, or
automatically, by systems, so that
duplicate objects in the network can be
identified and brought together for a
better understanding of the
information being shared.
Metadata related to the object
Name of the object
Example
ABERIII
Source
NSW
13.2.2.2. Association Roles
UML Name
Cargo
CorrespondentAsset
Document
InvolvedAgent
Data type
Cargo
OperationalAsset
Document
Agent
InvolvedEvent
Event
InvolvedRisk
Location
Risk
Location
Description
The association has additional attributes.
Please check association class AgentObject.
The association has additional attributes.
Please check association class ObjectEvent.
The association has additional attributes.
Please check association class ObjectLocation.
Vehicles
Vehicle
(*) Inherited association roles are coloured in grey.
Multiplicity
0..1
0..1
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..*
0..* (allow
duplicates)
0..*
13.2.2.3. Constraints
Name
Description
OCL Constraint
Minimum of
The number of TotalPersonsOnBoard can not be smaller than
TotalPersonsOnBoard
the sum of master/crewmembers and passengers
(*) Inherited constraints are coloured in grey.
13.2.3.
Object Class (subclass of Entity)
The Object entity is one of the core entities of the overall data model. It is an abstract entity (it cannot been
used as such) that holds information about physical entities from the maritime domain like vehicles (vessels,
aircrafts and land vehicles) and cargo. Object has relationships with Event, Agent, Document, Risk and Location.
Object can also be associated with another Object.
13.2.3.1. Attributes
UML Name
Colour
ExternalMarkings
Identifier
Data type
ColourType
String
UniqueIdentifier
Metadata
Metadata
EUCISE2020
Description
Colour information about the object
External markings of the object
Identifier of the object.
Each UniqueIdentifier can be correlated with
other UniqueIdentifiers, either manually, by
operators, or automatically, by systems, so
that duplicate objects in the network can be
identified and brought together for a better
understanding of the information being
shared.
Metadata related to the object
Example
Red
ABER
Source
EUROSUR
FLUX
Page 110 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Name
Data type
String
Description
Name of the object
Example
ABERIII
Source
NSW
13.2.3.2. Association Roles
UML Name
Document
InvolvedAgent
Data type
Document
Agent
InvolvedEvent
Event
InvolvedRisk
Location
Risk
Location
13.2.4.
Description
Multiplicity
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..*
0..* (allow
duplicates)
The association has additional attributes. Please check
association class AgentObject.
The association has additional attributes. Please check
association class ObjectEvent.
The association has additional attributes. Please check
association class ObjectLocation.
Vehicle Class (subclass of Object)
The Vehicle is a sub-class of Object and is used to determine types of physical moving objects related to
maritime. The class Vehicle inherits the attributes and relationships of Object. Vehicle has three sub-classes:
Vessel, Aircraft and LandVehicle.
13.2.4.1. Attributes
UML Name
MaximumSpeed
Data type
double
Nationality
String
TotalPersonsOnBoard
Colour
ExternalMarkings
Identifier
int
ColourType
String
UniqueIdentifier
Metadata
Metadata
Name
String
(*) Inherited attributes are coloured in grey.
Description
The vehicle’s maximum speed
measured in knots
Two-letter country codes to represent
countries, dependent territories, and
special areas of geographical interest.
Represent the flag for a Vessel.
The total number of persons on board
Colour information about the object
External markings of the object
Identifier of the object.
Each UniqueIdentifier can be correlated
with other UniqueIdentifiers, either
manually, by operators, or
automatically, by systems, so that
duplicate objects in the network can be
identified and brought together for a
better understanding of the
information being shared.
Metadata related to the object
Name of the object
Example
20
Source
EUROSUR
Country
code for
Portugal:
PT
(Country
code for
Portugal)
10
Red
ABER
ISO 31661
ABERIII
NSW
EUROSUR
FLUX
13.2.4.2. Association Roles
UML Name
Cargo
CorrespondentAsset
Document
InvolvedAgent
EUCISE2020
Data type
Cargo
OperationalAsset
Document
Agent
Description
The association has additional attributes.
Please check association class AgentObject.
Multiplicity
0..1
0..1
0..*
0..* (allow
duplicates)
Page 111 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
InvolvedEvent
Data type
Event
InvolvedRisk
Location
Risk
Location
Description
The association has additional attributes.
Please check association class ObjectEvent.
Multiplicity
0..* (allow
duplicates)
0..*
0..* (allow
duplicates)
0..*
The association has additional attributes.
Please check association class ObjectLocation.
Vehicles
Vehicle
(*) Inherited association roles are coloured in grey.
13.2.4.3. Constraints
Name
Minimum of
TotalPersonsOnBoard
13.2.5.
Description
OCL Constraint
The number of TotalPersonsOnBoard can not be smaller than
the sum of master/crewmembers and passengers
ObjectLocation Association Class
This class allows the association between Object (or one of its sub-classes: Vehicle, CargoPackage) and Location.
It is not mandatory to associate an Object with a Location but one or many Object can be associated to a
Location through this class. The association further describes the role of the Object in relation to the Location
and other useful data.
13.2.5.1. Attributes
UML Name
COG
Data type
double
Description
Course over ground in
degrees
120
Heading
double
Heading of the object
120
LocationRole
LocationRoleType
Port of
embarkation of
the Vessel: 001
Metadata
Metadata
PeriodOfTime
Period
PlacementPurpose
PlacementPurposeType
PlannedOperations
PlannedOperationsType
PlannedWorks
PlannedWorksType
SensorType
SensorType
SOG
double
Enumerated. Describes
the relationship
between the Object
and the Location.
Metadata linked to the
localisation of the
object
Defines the duration of
the relationship
between the Object
and the Location.
Defines the reason
why the object is at a
location
Defines the planned
operations for which
the object is at the
location
Defines the planned
works the object will
undergo when at the
location
Defines the sensor
origin of the position
Speed on ground in
knots
EUCISE2020
Example
Source
ITU-R
M.13711
ITU-R
M.13711
01 (In Transit)
NSW
01 (loading)
NSW
01 (inspection)
NSW
01 (sighting)
12
Page 112 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
SourceType
Data type
SourceType
SpecialSecurityMeasures
String
Speed
double
13.2.6.
Description
Defines how the
location of the object
has been determined
Defines security
measures to be apply
when the object is a
the location
Speed of the object in
knots
Example
Observation
description of
security
measures
Source
NSW
12
ColourType Enumeration
Source: EUROSUR
13.2.6.1. Enumeration Values
Value
Cyan
Grey
Yellow
White
Black
Pink
Green
Blue
Brown
Orange
Violet
Red
Label
Description
Source
cyan
grey
yellow
white
black
pink
green
blue
brown
orange
violet
red
13.2.6.2. Enumeration Usage
The following attributes use this enumeration as data type:
 Colour (Object)
13.2.7.
LocationRoleType Enumeration
13.2.7.1. Enumeration Values
Value
001
002
003
004
005
006
999
Label
Port of embarkation
Port of disembarkation
Port of registry
Lengthened place
Port of loading
Port of discharge
non-specified
Description
Port of embarkation (for vessel)
Port of disembarkation (for vessel)
Port of registry (for vessel)
Lengthened place (for vessel)
Port of loading (for cargo)
Port of discharge (for cargo)
Non specified
Source
13.2.7.2. Enumeration Usage
The following attributes use this enumeration as data type:
 LocationRole (ObjectLocation)
EUCISE2020
Page 113 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
13.2.8.
PlacementPurposeType Enumeration
This enumeration describes the reason of placement of an object to a location. An object can be at a location
because it is in transit. A vessel (i.e. an object) can also be assigned to a location.
Source: NSW
13.2.8.1. Enumeration Values
Value
01
02
98
99
Label
in transit
assigned
other
non-specified
Description
The Object is at a Location during a transit
The Object is assigned to the Location
Any other type not mentioned above
Type not specified
Source
13.2.8.2. Enumeration Usage
The following attributes use this enumeration as data type:
 PlacementPurpose (ObjectLocation)
13.2.9.
PlannedOperationsType Enumeration
This enumeration presents the possible planned operations for which an Object is at a Location.
Source: NSW
13.2.9.1. Enumeration Values
Value
01
02
98
99
Label
loading
unloading
other
non-specified
Description
The Object is at the Location to load cargo
The Object is at the Location to unload cargo
Any other operation not mentioned above
Operation not specified
Source
NSW
NSW
13.2.9.2. Enumeration Usage
The following attributes use this enumeration as data type:
 PlannedOperations (ObjectLocation)
13.2.10.
PlannedWorksType Enumeration
This enumeration presents the possible planned works which can explain that an Object is at a Location.
Source: NSW
13.2.10.1.
Value
01
02
98
99
Enumeration Values
Label
inspection
maintenance and repair
other
non-specified
13.2.10.2.
Description
The Object is at a Location for Inspection
The Object is at a Location for Maintenance and repair
Any other works not mentioned above
Works not specified
Source
NSW
NSW
Enumeration Usage
The following attributes use this enumeration as data type:
 PlannedWorks (ObjectLocation)
13.2.11.
SensorType Enumeration
This enumeration presents the Sensor at the origin of an association between an Object and a Location.
EUCISE2020
Page 114 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
13.2.11.1.
Value
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
98
99
Enumeration Values
Label
sighting
underwater sensor
maritime radar
synthetic aperture radar
EOIR optronic system
maritime moving target identification
signal interception systems COMINT
signal interception systems ELINT
environmental sensing systems
automatic identification system
vessel monitoring system
long range identification tracking
automatic vehicle location
acoustic systems
non-traditional sources
other
non-specified
13.2.11.2.
Description
The Object is observed at the Location
Underwater sensor
Maritime radar
Synthetic aperture radar
EO/IR Optronic system
Maritime moving target identification
Signal interception systems COMINT
Signal interception systems ELINT
Environmental sensing systems
Automatic Identification System (AIS)
Vessel monitoring system (VMS)
Long range identification and tracking (LRIT)
Automatic vehicle location (AVL)
Acoustic Systems ACINT
Non-traditional sources
Any other sensor not mentioned above
Sensor not specified
Source
Enumeration Usage
The following attributes use this enumeration as data type:
 SensorType (ObjectLocation)
13.2.12.
SourceType Enumeration
This enumeration defines how the placement of an object to a location has been determined. The location of an
object can be observed, declared, estimated or simulated.
13.2.12.1.
Value
01
02
03
04
05
98
99
Label
observation
declaration
estimation
simulation
correlation
other
non-specified
13.2.12.2.
Enumeration Values
Description
The location of the object is observed
The location of the object is declared
The location of the object is estimated
The location of the object is simulated
The location of the object has been correlated
Any other type not mentioned above
Type not specified
Source
Enumeration Usage
The following attributes use this enumeration as data type:
 SourceType (EventLocation)

SourceType (MeteoOceanographicCondition)

SourceType (ObjectLocation)
EUCISE2020
Page 115 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
14. OperationalAsset Core Entity
14.1. UML models
14.2. Elements defined in the Core Vocabulary
14.2.1.
OperationalAsset Class (subclass of Entity)
An Operational Asset is an Object (in particular means of observation or transportation, but also including
associated sensors, means of communication and means of intervention such as deterrence or neutralization of
threats, fire fighting, pollution containment etc.) enabling operational Actions (most often at sea or on sea
shores) of the Agents mandated by public Organizations in charge of Maritime Safety and Security.
14.2.1.1. Attributes
UML Name
AvailabilityPeriod
EUCISE2020
Data type
Period
Description
Defines the time period of
Agent involvement in the
Event. Can be either defined
by start and end dates/times
or duration.
• Format for date is: CCYYMM-DD
Example
Date (e.g. 27th
October year 2013):
2013-10-27
Time (e.g. 20
minutes and 45
seconds past noon):
12:20:45
Sourc
e
CISE
Page 116 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Description
Example
• Format for time is:
hh:mm:ss
• Format for duration is:
P[yY][mM][dD][T[hH][mM][s[
.s]S]]
See also : Core Vocabularities
Specification for "Period"
Identifier of the operational
asset.
Each UniqueIdentifier can be
correlated with other
UniqueIdentifiers, either
manually, by operators, or
automatically, by systems, so
that duplicate objects in the
network can be identified
and brought together for a
better understanding of the
information being shared.
MaxPassengers of an
OperationalAsset
Max. Speed of the
Operational Asset measured
in knots
see: Core Vocabulary
Specification for "Metadata"
Duration (e.g. 7
years, 3 months, 8
days, 8 hours, 31
minutes and 52.05
seconds):
P7Y3M8DT8H31M52.
05S
Identifier
UniqueIdentifier
MaxPassengers
int
MaxSpeed
double
Metadata
Metadata
OperationalAssetT
ype
OperationalCapabi
lity
OperationalAssetType
Asset type
OperationalCapability
Type
Range
double
Defines the Asset Capability
to perform as intended in an
operation
Range of the Operational
Asset
ReadinessState
XSD::Time
EUCISE2020
The lexical space of xsd:time
is identical to the time part
of xsd:dateTime
(hh:mm:ss[Z|(+|-)hh:mm]),
and its value space is the set
of points in time recurring
daily.
The period (one day) is fixed,
and no calendars other than
Gregorian are supported.
Sourc
e
200 passengers
12
see: Core Vocabulary
Specification for
"Metadata"
Cruiser
Search and rescue
Coastal Radar with 09 range miles of
detection
Valid values include
21:32:52,
21:32:52+02:00,
19:32:52Z,
19:32:52+00:00, and
21:32:52.12679.
Invalid values include
21:32 (all the parts
must be specified),
25:25:10 (the hour
part is out of range),
-10:00:00 (the hour
part is out of range),
and 1:20:10 (all the
digits must be
supplied).
Page 117 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
14.2.1.2. Association Roles
UML Name
CorrespondentVehicle
14.2.2.
Data type
Vehicle
Description
Multiplicity
1
OperationalAssetType Enumeration
This enumeration presents the possible types of operational assets.
14.2.2.1. Enumeration Values
Value
01
Label
aircraft
02
helicopter
03
patrol boat
04
UAV
05
06
submarine
frigate
07
speed boat
08
drone
09
tank
10
truck
11
4x4
12
13
14
15
carrier
ambulance
motorcycle
artillery
vehicle
desert patrol
vehicle
16
17
tractor
18
19
20
wrecker
trailer
humvee
21
22
firetrack
van
EUCISE2020
Description
An aircraft is a machine that is able to fly by gaining support from the air,
or, in general, the atmosphere of a planet. It counters the force of gravity
by using either static lift or by using the dynamic lift of an airfoil, or in a few
cases the downward thrust from jet engines.
A helicopter is a type of rotorcraft in which lift and thrust are supplied by
rotors
Operated by navies, coast guards and police. Function – defense of coastal
waters, rivers and estuaries, borders security and law enforcement. May
have an anti-surface role
An unmanned aerial vehicle (UAV), also known as a drone, is an aircraft
without a human pilot on board
A submarine is a watercraft capable of independent operation underwater
Smaller than destroyers, one or two missions. Protect naval groups and
merchant ships. Anti-submarine warfare. Fleet air defense. Anti-surface
warships
A motorboat, speedboat, or powerboat is a boat which is powered by an
engine
Drone is the popular term for an unmanned aircraft. It is still a UAV
however a drone is flown by software with pre-programmed behavior save
for additional commands by the operators
A tank is a tracked, armoured fighting vehicle designed for front-line
combat which combines operational mobility and tactical offensive and
defensive capabilities
A truck (US, CA and AU) or lorry (UK and Ireland) is a motor vehicle
designed to transport cargo. Also military use.
Four-wheel drive, All-wheel drive, AWD, 4WD, or 4×4 is a four-wheeled
vehicle with a drivetrain that allows all four wheels to receive torque from
the engine
Vehicle for transport
Ambulance
Motorcycle
Vehicle artillery equipped with an own propel system to move towards its
target
The Desert Patrol Vehicle (DPV), formerly called the Fast Attack Vehicle
(FAV), is a high-speed, lightly armored sandrail-like vehicle first used in
combat during the Gulf War in 1991
A tractor is an engineering vehicle specifically designed to deliver a high
tractive effort (or torque) at slow speeds
A vehicle used to tow away broken-down cars
A trailer is generally an unpowered vehicle pulled by a powered vehicle
The High Mobility Multipurpose Wheeled Vehicle (HMMWV), commonly
known as the Humvee, is a four-wheel drive military automobile produced
by AM General
Vehicle used for Firefighting
A van is a kind of vehicle used for transporting goods or people
Source
Page 118 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
23
Label
UUV
24
25
26
27
28
ROV
USV
sea platform
aeroplane
destroyer
29
cruiser
30
aircraft
carrier
31
corvette
32
auxiliary
ships
landing ships
assault ships
mine
warfare
ships
strategic
fixed assets
ballons
other
33
34
35
36
37
98
Description
Unmanned underwater vehicles (UUV), sometimes known as underwater
drones, are any vehicles that are able to operate underwater without a
human occupant. These vehicles may be divided into two categories,
Remotely operated underwater vehicles (ROVs) and Autonomous
underwater vehicles (AUVs)
ROV controlled by a remote human operato
USV operate independently of direct human input
Platform that stand on the sea for different purposes
Aeroplane
Fast warships providing multi-mission offensive and defensive capability,
independently or in fleet support
Multi-mission warships capable of engaging multiple simultaneous targets
and employed in force support or independent action
An aircraft carrier is a warship with a full-length flight deck and facilities for
carrying, arming, deploying and recovering aircraft, acting as a seagoing
airbase
Small frigates. Protect naval and merchant ships. Anti-submarine warfare.
Fleet defence (anti-aircraft mission)
Re-supply Ship. Replenishment at Sea
Source
Smaller then assault ships
Air Cushioned Vehicles
Mine Warfare Ships
Strategic/fixed assets
Ballons
Other
14.2.2.2. Enumeration Usage
The following attributes use this enumeration as data type:
 OperationalAssetType (OperationalAsset)
14.2.3.
OperationalCapabilityType Enumeration
This enumeration presents the possible types of operational capabilities.
14.2.3.1. Enumeration Values
Value
01
Label
search and rescue
02
oil pollution
03
telecommunications
TLC
04
patrolling
05
piracy attack
EUCISE2020
Description
Search for and provision of aid to people who are in distress or
imminent danger
Pollution due to release of a liquid petroleum hydrocarbon into
the environment, especially marine areas, due to human activity
Can be accommodated within any of the listed
OperationalCapability. It is the transmission of signals over long
distances
The act of moving about an area especially by an authorized and
trained person or group, for purposes of observation, inspection,
or security
Act of robbery or criminal violence at sea. The term can include
acts committed on land, in the air, or in other major bodies of
water or on a shore. It does not normally include crimes
Source
Page 119 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
Label
06
illegal migration
07
counter drug
smuggling
08
counter illegal fishing
09
10
firefighting
coordination
11
simulation
12
mobility
13
training
14
maintenance
15
sustainability
16
intelligence
surveillance
reconnaissance
17
98
C2 W command and
control warfare
other
99
non-specified
Description
committed against persons traveling on the same vessel as the
perpetrator (e.g. one passenger stealing from others on the same
vessel). The term has been used throughout history to refer to
raids across land borders by non-state agents.
Refers to the migration of people across national borders in a way
that violates the immigration laws of the destined country. In
concrete detection of Cayucos, mother ships and border
monitoring
Refers to a global illicit trade involving the cultivation,
manufacture, distribution and sale of substances which are
subject to drug prohibition laws
Illegal fishing is the fishing which takes place where vessels
operate in violation of the fishery laws. It normally applies to the
fisheries which are under the jurisdiction of the coastal state
regulated by the regional organizations.
Attempting to control and extinguish fires
Operating principle. Command and control that involves multiple,
diverse, networked teams that can involve national and coalition
partners and non-military agencies, challenging the commander
to deal with options along various dimensions.
Operating principle. Imitation of the operation of a real-world
process or system over time. The act of simulating something first
requires that a model be developed; this model represents the
key characteristics or behaviors/functions of the selected physical
or abstract system or process. The model represents the system
itself, whereas the simulation represents the operation of the
system over time
Operating principle. It allows disposing of the necessary means in
order to allow strategic deployment and high mobility of assets
and personnel required for the operations.
Operating principle. In general, training is the acquisition of
knowledge, skills, and competencies as a result of the teaching of
vocational or practical skills and knowledge that relate to specific
useful competencies.
Operating principle. Operating principle. In general, all actions
which have the objective of retaining or restoring an item in or to
a state in which it can perform its required function. The actions
include the combination of all technical and corresponding
administrative, managerial, and supervision actions
Operating principle. This capability is oriented to guarantee the
sustainability of the assets deployed during a long period of time.
Fall within the ISTAR concept, which is fundamentally obtaining
information and intelligence to support the planning and conduct
of operations. It is a practice that links several battlefield
functions together to assist a combat force in employing its
sensors and managing the information they gather.
Electronic Warfare encompasses all that is command and control
capability, also PSYOPS (includes deception- simulation)
Other not included above
-Source
Non-specified
Source
14.2.3.2. Enumeration Usage
EUCISE2020
Page 120 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
The following attributes use this enumeration as data type:
 OperationalCapability (OperationalAsset)
EUCISE2020
Page 121 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
15. Organization Core Entity
15.1. UML models
15.2. Elements defined in the Core Vocabulary
15.2.1.
FormalOrganization Class (subclass of Organization)
A particular sub-class of organization FormalOrganization can be used to indicate organizations that are
recognized in the world at large, in particular in legal jurisdictions, with associated rights and responsibilities.
Examples include a corporation, charity, government or church.
15.2.1.1. Attributes
UML Name
FormalOrganizationNa
me
AlternativeName
EUCISE2020
Data type
String
String
Description
Name of the
organization
Any other
name used.
This attribute
can be used for
Example
Sourc
e
Red cross
Rajavartiolaitos
Page 122 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
IdentificationNumber
String
LegalName
String
OrganizationClassificat
ion
OrganizationClassificationT
ype
OrganizationPurpose
OrganizationPurposeType
OrganizationRole
OrganizationRoleType
EUCISE2020
Description
example for the
official name of
the
organization in
the native
language.
Business ID
number of the
organisation in
international
format.
The official
name of the
organization. It
is
recommended
to use the
official English
translation.
Enumerated.
Formal
classification of
organization.
Enumerated.
Defines the
purpose of the
organization.
The purpose is
modeled using
the CISE user
community
plus some
additional
options where
those are not
applicable.
There can be
more than one
purpose
connected to
one
organization.
Enumerated.
Organization
role as
described by
the different
roles defined in
SafeSeaNet
system.
Example
Sourc
e
The business number of
the Finnish Border Guard:
FI02460035
Finnish Border Guard
Government authority on
national level: 01
W3C
Oont
Authority responsible for
border control: 07
W3C
Oont
A body responsible for
coordinating search and
rescue operations or
operations to tackle
pollution at sea (Coastal
station): 02
SSN
MRG
Page 123 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
ContactInformation
EUCISE2020
Data type
String
Description
Example
vCard [IETF
RFC6350] is a
data format for
representing
and exchanging
information
about
individuals and
other entities.
It is a textbased format
(as opposed to
a binary
format). xCard
[IETF RFC6351]
is an XML
representation
for vCard. All
available
attributes are
described in
the vCard
document [IETF
RFC6350] and
listed bellow:
• General
Properties
(BEGIN, END,
SOURCE, KIND,
XML)
• Identification
Properties (FN,
N, NICKNAME,
PHOTO, BDAY,
ANNIVERSARY,
GENDER)
• Delivery
Addressing
Properties
(ADR)
•
Communication
s Properties
(TEL, EMAIL,
IMPP, LANG)
• Geographical
Properties (TZ,
GEO)
•
Organizational
Properties
(TITLE, ROLE,
Name of a person called
Mr John Brown, M.Sc.:
<fn><text>Mr John
Brown, M.Sc.</text></fn>
<n>
Sourc
e
IETF
RFC
6351
<surname>Brown</surna
me>
<given>John</given>
<additional/>
<prefix>Mr<prefix/>
<suffix>M.Sc.<suffix/>
</n>
more examples found in:
[IETF RFC6351]
Page 124 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Identifier
UniqueIdentifier
IsOfInterest
boolean
EUCISE2020
Description
LOGO, ORG,
MEMBER,
RELATED)
• Explanatory
Properties
(CATEGORIES,
NOTE, PRODID,
REV, SOUND,
UID,
CLIENTPIDMAP,
URL, VERSION)
• Security
Properties
(KEY)
• Calendar
Properties
(FBURL,
CALADRURI,
CALURI)
Identifier of the
agent.
Each
UniqueIdentifie
r can be
correlated with
other
UniqueIdentifie
rs, either
manually, by
operators, or
automatically,
by systems, so
that duplicate
objects in the
network can be
identified and
brought
together for a
better
understanding
of the
information
being shared.
Attribute is
flagging an
interest to
follow more
closely any
activities
related to the
Agent. Value of
the attribute
Example
Sourc
e
0
Page 125 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
IsSuspect
boolean
Metadata
Metadata
Nationality
String
Description
can be either
true or false
(true = 1 and
false = 0)
Attribute is
flagging a
possible
suspicion of
illegal activities
related to the
Agent. Value of
the attribute
can be either
true or false
(true = 1 and
false = 0)
see: Core
Vocabulary
Specification
for "Metadata"
Three-letter
country codes
to represent
countries,
dependent
territories, and
special areas of
geographical
interest
Sourc
e
Example
There is some suspect
related to the agent:
1
DCMI
Portugal: PT
ISO
31661
(alph
a-2 )
(*) Inherited attributes are coloured in grey.
15.2.1.2. Association Roles
UML Name
Document
InvolvedEvent
Data type
Document
Event
Description
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class AgentObject.
InvolvedRisk
Risk
The association has additional attributes. Please check
association class AgentRisk.
InvolvedWith
Agent
The association has additional attributes. Please check
association class AgentAgent.
Location
Location
The association has additional attributes. Please check
association class AgentLocation.
(*) Inherited association roles are coloured in grey.
15.2.2.
Multiplicity
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
Organization Class (subclass of Agent)
The class Organization is a sub-class of an abstract class Agent. Organization represents a structured and legally
recognized association of humans and material resources for some common purpose or reason for existence
which goes beyond the set of people belonging to it. An organization may itself be involved as actor or target in
the various events and activities. Organization can have the same associations and relationships than the
parent-class Agent. Thus it can have relationship with other agents, objects and locations or it can be related to
EUCISE2020
Page 126 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
risks in different roles. Organization has four sub-classes: OrganizationalUnit, PortOrganization,
FormalOrganization and OrganizationalCollaboration.
15.2.2.1. Attributes
UML Name
Data type
Description
Any other
name used.
This attribute
can be used for
example for the
official name of
the
organization in
the native
language.
Business ID
number of the
organisation in
international
format.
The official
name of the
organization. It
is
recommended
to use the
official English
translation.
Enumerated.
Formal
classification of
organization.
Enumerated.
Defines the
purpose of the
organization.
The purpose is
modeled using
the CISE user
community
plus some
additional
options where
those are not
applicable.
There can be
more than one
purpose
connected to
one
organization.
Enumerated.
Organization
AlternativeName
String
IdentificationNumber
String
LegalName
String
OrganizationClassificat
ion
OrganizationClassificationT
ype
OrganizationPurpose
OrganizationPurposeType
OrganizationRole
OrganizationRoleType
EUCISE2020
Example
Sourc
e
Rajavartiolaitos
The business number of
the Finnish Border Guard:
FI02460035
Finnish Border Guard
Government authority on
national level: 01
W3C
Oont
Authority responsible for
border control: 07
W3C
Oont
A body responsible for
coordinating search and
SSN
MRG
Page 127 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
ContactInformation
EUCISE2020
Data type
String
Description
role as
described by
the different
roles defined in
SafeSeaNet
system.
vCard [IETF
RFC6350] is a
data format for
representing
and exchanging
information
about
individuals and
other entities.
It is a textbased format
(as opposed to
a binary
format). xCard
[IETF RFC6351]
is an XML
representation
for vCard. All
available
attributes are
described in
the vCard
document [IETF
RFC6350] and
listed bellow:
• General
Properties
(BEGIN, END,
SOURCE, KIND,
XML)
• Identification
Properties (FN,
N, NICKNAME,
PHOTO, BDAY,
ANNIVERSARY,
GENDER)
• Delivery
Addressing
Properties
(ADR)
•
Communication
s Properties
(TEL, EMAIL,
IMPP, LANG)
Example
Sourc
e
rescue operations or
operations to tackle
pollution at sea (Coastal
station): 02
Name of a person called
Mr John Brown, M.Sc.:
<fn><text>Mr John
Brown, M.Sc.</text></fn>
<n>
IETF
RFC
6351
<surname>Brown</surna
me>
<given>John</given>
<additional/>
<prefix>Mr<prefix/>
<suffix>M.Sc.<suffix/>
</n>
more examples found in:
[IETF RFC6351]
Page 128 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Identifier
UniqueIdentifier
IsOfInterest
boolean
EUCISE2020
Description
• Geographical
Properties (TZ,
GEO)
•
Organizational
Properties
(TITLE, ROLE,
LOGO, ORG,
MEMBER,
RELATED)
• Explanatory
Properties
(CATEGORIES,
NOTE, PRODID,
REV, SOUND,
UID,
CLIENTPIDMAP,
URL, VERSION)
• Security
Properties
(KEY)
• Calendar
Properties
(FBURL,
CALADRURI,
CALURI)
Identifier of the
agent.
Each
UniqueIdentifie
r can be
correlated with
other
UniqueIdentifie
rs, either
manually, by
operators, or
automatically,
by systems, so
that duplicate
objects in the
network can be
identified and
brought
together for a
better
understanding
of the
information
being shared.
Attribute is
flagging an
Example
Sourc
e
0
Page 129 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
IsSuspect
boolean
Metadata
Metadata
Nationality
String
Description
interest to
follow more
closely any
activities
related to the
Agent. Value of
the attribute
can be either
true or false
(true = 1 and
false = 0)
Attribute is
flagging a
possible
suspicion of
illegal activities
related to the
Agent. Value of
the attribute
can be either
true or false
(true = 1 and
false = 0)
see: Core
Vocabulary
Specification
for "Metadata"
Three-letter
country codes
to represent
countries,
dependent
territories, and
special areas of
geographical
interest
Sourc
e
Example
There is some suspect
related to the agent:
1
DCMI
Portugal: PT
ISO
31661
(alph
a-2 )
(*) Inherited attributes are coloured in grey.
15.2.2.2. Association Roles
UML Name
Document
InvolvedEvent
Data type
Document
Event
Description
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class AgentObject.
InvolvedRisk
Risk
The association has additional attributes. Please check
association class AgentRisk.
InvolvedWith
Agent
The association has additional attributes. Please check
association class AgentAgent.
Location
Location
The association has additional attributes. Please check
association class AgentLocation.
(*) Inherited association roles are coloured in grey.
EUCISE2020
Multiplicity
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
Page 130 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
15.2.3.
OrganizationalCollaboration Class (subclass of Organization)
The sub-class OrganizationalCollaboration is defined to describe a collaboration between two or more
Organizations such as a project. OrganizationalCollaboration meets the criteria for being an Organization in that
it has an identity and defined purpose independent of its particular members but is neither a formally
recognized legal entity nor a sub-unit within some larger organization. Might typically have a shorter lifetime
than the Organizations within it, but not necessarily.
15.2.3.1. Attributes
UML Name
Data type
AlternativeName
String
IdentificationNumber
String
LegalName
String
OrganizationClassificat
ion
OrganizationClassificationT
ype
OrganizationPurpose
OrganizationPurposeType
EUCISE2020
Description
Any other
name used.
This attribute
can be used for
example for the
official name of
the
organization in
the native
language.
Business ID
number of the
organisation in
international
format.
The official
name of the
organization. It
is
recommended
to use the
official English
translation.
Enumerated.
Formal
classification of
organization.
Enumerated.
Defines the
purpose of the
organization.
The purpose is
modeled using
the CISE user
community
plus some
additional
options where
those are not
applicable.
There can be
more than one
purpose
Example
Sourc
e
Rajavartiolaitos
The business number of
the Finnish Border Guard:
FI02460035
Finnish Border Guard
Government authority on
national level: 01
W3C
Oont
Authority responsible for
border control: 07
W3C
Oont
Page 131 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
OrganizationRole
OrganizationRoleType
ContactInformation
String
EUCISE2020
Description
connected to
one
organization.
Enumerated.
Organization
role as
described by
the different
roles defined in
SafeSeaNet
system.
vCard [IETF
RFC6350] is a
data format for
representing
and exchanging
information
about
individuals and
other entities.
It is a textbased format
(as opposed to
a binary
format). xCard
[IETF RFC6351]
is an XML
representation
for vCard. All
available
attributes are
described in
the vCard
document [IETF
RFC6350] and
listed bellow:
• General
Properties
(BEGIN, END,
SOURCE, KIND,
XML)
• Identification
Properties (FN,
N, NICKNAME,
PHOTO, BDAY,
ANNIVERSARY,
GENDER)
• Delivery
Addressing
Properties
(ADR)
Example
Sourc
e
A body responsible for
coordinating search and
rescue operations or
operations to tackle
pollution at sea (Coastal
station): 02
SSN
MRG
Name of a person called
Mr John Brown, M.Sc.:
<fn><text>Mr John
Brown, M.Sc.</text></fn>
<n>
IETF
RFC
6351
<surname>Brown</surna
me>
<given>John</given>
<additional/>
<prefix>Mr<prefix/>
<suffix>M.Sc.<suffix/>
</n>
more examples found in:
[IETF RFC6351]
Page 132 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Identifier
EUCISE2020
Data type
UniqueIdentifier
Description
Example
Sourc
e
•
Communication
s Properties
(TEL, EMAIL,
IMPP, LANG)
• Geographical
Properties (TZ,
GEO)
•
Organizational
Properties
(TITLE, ROLE,
LOGO, ORG,
MEMBER,
RELATED)
• Explanatory
Properties
(CATEGORIES,
NOTE, PRODID,
REV, SOUND,
UID,
CLIENTPIDMAP,
URL, VERSION)
• Security
Properties
(KEY)
• Calendar
Properties
(FBURL,
CALADRURI,
CALURI)
Identifier of the
agent.
Each
UniqueIdentifie
r can be
correlated with
other
UniqueIdentifie
rs, either
manually, by
operators, or
automatically,
by systems, so
that duplicate
objects in the
network can be
identified and
brought
together for a
better
understanding
Page 133 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
IsOfInterest
boolean
IsSuspect
boolean
Metadata
Metadata
Nationality
String
Description
of the
information
being shared.
Attribute is
flagging an
interest to
follow more
closely any
activities
related to the
Agent. Value of
the attribute
can be either
true or false
(true = 1 and
false = 0)
Attribute is
flagging a
possible
suspicion of
illegal activities
related to the
Agent. Value of
the attribute
can be either
true or false
(true = 1 and
false = 0)
see: Core
Vocabulary
Specification
for "Metadata"
Three-letter
country codes
to represent
countries,
dependent
territories, and
special areas of
geographical
interest
Sourc
e
Example
0
There is some suspect
related to the agent:
1
DCMI
Portugal: PT
ISO
31661
(alph
a-2 )
(*) Inherited attributes are coloured in grey.
15.2.3.2. Association Roles
UML Name
Document
InvolvedEvent
Data type
Document
Event
InvolvedObject
Object
InvolvedRisk
Risk
EUCISE2020
Description
The association has additional attributes. Please check
association class AgentEvent.
The association has additional attributes. Please check
association class AgentObject.
The association has additional attributes. Please check
association class AgentRisk.
Multiplicity
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
Page 134 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
InvolvedWith
Data type
Agent
Location
Location
Description
The association has additional attributes. Please check
association class AgentAgent.
The association has additional attributes. Please check
association class AgentLocation.
Multiplicity
0..* (allow
duplicates)
0..* (allow
duplicates)
2..*
Participant
Organization
(*) Inherited association roles are coloured in grey.
15.2.4.
OrganizationalUnit Class (subclass of Organization)
In some cases it is useful to refer to departments or organizational units such as the IT department which only
have meaning within the context of the containing organization and would not be regarded as a legal entity in
its own right. This situation is supported by a subclass of Organization called OrganizationalUnit.
15.2.4.1. Attributes
UML Name
Data type
Description
UnitIdentifier
String
Defines the
name of the
organizational
unit
AlternativeName
String
IdentificationNumber
String
LegalName
String
OrganizationClassificat
ion
OrganizationClassificationT
ype
OrganizationPurpose
OrganizationPurposeType
Any other
name used.
This attribute
can be used for
example for the
official name of
the
organization in
the native
language.
Business ID
number of the
organisation in
international
format.
The official
name of the
organization. It
is
recommended
to use the
official English
translation.
Enumerated.
Formal
classification of
organization.
Enumerated.
Defines the
purpose of the
organization.
The purpose is
modeled using
EUCISE2020
Example
Sourc
e
Administrative unit
responsible of flight
operations inside the
Finnish Border Guard: Air
Patrol Squadron
Rajavartiolaitos
The business number of
the Finnish Border Guard:
FI02460035
Finnish Border Guard
Government authority on
national level: 01
W3C
Oont
Authority responsible for
border control: 07
W3C
Oont
Page 135 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
OrganizationRole
OrganizationRoleType
ContactInformation
String
EUCISE2020
Description
the CISE user
community
plus some
additional
options where
those are not
applicable.
There can be
more than one
purpose
connected to
one
organization.
Enumerated.
Organization
role as
described by
the different
roles defined in
SafeSeaNet
system.
vCard [IETF
RFC6350] is a
data format for
representing
and exchanging
information
about
individuals and
other entities.
It is a textbased format
(as opposed to
a binary
format). xCard
[IETF RFC6351]
is an XML
representation
for vCard. All
available
attributes are
described in
the vCard
document [IETF
RFC6350] and
listed bellow:
• General
Properties
(BEGIN, END,
SOURCE, KIND,
XML)
Example
Sourc
e
A body responsible for
coordinating search and
rescue operations or
operations to tackle
pollution at sea (Coastal
station): 02
SSN
MRG
Name of a person called
Mr John Brown, M.Sc.:
<fn><text>Mr John
Brown, M.Sc.</text></fn>
<n>
IETF
RFC
6351
<surname>Brown</surna
me>
<given>John</given>
<additional/>
<prefix>Mr<prefix/>
<suffix>M.Sc.<suffix/>
</n>
more examples found in:
[IETF RFC6351]
Page 136 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Identifier
EUCISE2020
Data type
UniqueIdentifier
Description
Example
Sourc
e
• Identification
Properties (FN,
N, NICKNAME,
PHOTO, BDAY,
ANNIVERSARY,
GENDER)
• Delivery
Addressing
Properties
(ADR)
•
Communication
s Properties
(TEL, EMAIL,
IMPP, LANG)
• Geographical
Properties (TZ,
GEO)
•
Organizational
Properties
(TITLE, ROLE,
LOGO, ORG,
MEMBER,
RELATED)
• Explanatory
Properties
(CATEGORIES,
NOTE, PRODID,
REV, SOUND,
UID,
CLIENTPIDMAP,
URL, VERSION)
• Security
Properties
(KEY)
• Calendar
Properties
(FBURL,
CALADRURI,
CALURI)
Identifier of the
agent.
Each
UniqueIdentifie
r can be
correlated with
other
UniqueIdentifie
rs, either
manually, by
operators, or
Page 137 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
IsOfInterest
boolean
IsSuspect
boolean
Metadata
Metadata
Nationality
String
Description
automatically,
by systems, so
that duplicate
objects in the
network can be
identified and
brought
together for a
better
understanding
of the
information
being shared.
Attribute is
flagging an
interest to
follow more
closely any
activities
related to the
Agent. Value of
the attribute
can be either
true or false
(true = 1 and
false = 0)
Attribute is
flagging a
possible
suspicion of
illegal activities
related to the
Agent. Value of
the attribute
can be either
true or false
(true = 1 and
false = 0)
see: Core
Vocabulary
Specification
for "Metadata"
Three-letter
country codes
to represent
countries,
dependent
territories, and
special areas of
geographical
interest
Example
Sourc
e
0
There is some suspect
related to the agent:
1
DCMI
Portugal: PT
ISO
31661
(alph
a-2 )
(*) Inherited attributes are coloured in grey.
EUCISE2020
Page 138 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
15.2.4.2. Association Roles
UML Name
Document
InvolvedEvent
Data type
Document
Event
Description
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class AgentObject.
InvolvedRisk
Risk
The association has additional attributes. Please check
association class AgentRisk.
InvolvedWith
Agent
The association has additional attributes. Please check
association class AgentAgent.
Location
Location
The association has additional attributes. Please check
association class AgentLocation.
(*) Inherited association roles are coloured in grey.
15.2.5.
Multiplicity
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
PortOrganization Class (subclass of Organization)
A particular sub-class of organization has been defined to be used when modelling IMO recognized ports.
PortOrganization carries some additional attributes that carry information relevant only to ports. Subclass of
Organization.
15.2.5.1. Attributes
UML Name
IMOCompanyIdentificationN
umber
EUCISE2020
Data type
String
Description
MO unique
company and
registered
owner
identification
number.
Unique
number given
to company or
registered
owner of a
vessel. The
IMO Unique
Company and
Registered
Owner
Identification
Number
Scheme was
introduced
through the
adoption by
the Maritime
Safety
Committee
(MSC), at its
seventyeighth session
(12 to 21 May
2004), of
Example
IMOCompany1234567
Sourc
e
NSW
Page 139 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Description
Example
Sourc
e
resolution
MSC.160(78).
Its purpose is
to assign a
permanent
number for
identification
purposes to
each company
and/or
registered
owner
managing
ships of 100
gross tonnage
and above
engaged on
international
voyages.
Additionally,
Administratio
ns are invited
to participate
in the scheme
to the extent
they desire by
assigning an
IMO unique
company and
registered
owner
identification
number to
each company
and/or
registered
owner
managing
ships of 100
gross tonnage
and above not
engaged on
international
voyages. The
procedures
for the
implementati
on of
resolution
MSC.160(78)
were initially
circulated by
EUCISE2020
Page 140 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
AlternativeName
String
IdentificationNumber
String
LegalName
String
OrganizationClassification
OrganizationClassificatio
nType
OrganizationPurpose
OrganizationPurposeTyp
e
EUCISE2020
Description
means of
Circular letter
No.2554,
dated 24 June
2004.
Any other
name used.
This attribute
can be used
for example
for the official
name of the
organization
in the native
language.
Business ID
number of the
organisation
in
international
format.
The official
name of the
organization.
It is
recommended
to use the
official English
translation.
Enumerated.
Formal
classification
of
organization.
Enumerated.
Defines the
purpose of
the
organization.
The purpose is
modeled
using the CISE
user
community
plus some
additional
options where
those are not
applicable.
There can be
more than
one purpose
Example
Sourc
e
Rajavartiolaitos
The business number of
the Finnish Border
Guard:
FI02460035
Finnish Border Guard
Government authority
on national level: 01
W3C
Oont
Authority responsible
for border control: 07
W3C
Oont
Page 141 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
OrganizationRole
OrganizationRoleType
ContactInformation
String
EUCISE2020
Description
connected to
one
organization.
Enumerated.
Organization
role as
described by
the different
roles defined
in SafeSeaNet
system.
vCard [IETF
RFC6350] is a
data format
for
representing
and
exchanging
information
about
individuals
and other
entities. It is a
text-based
format (as
opposed to a
binary
format). xCard
[IETF
RFC6351] is an
XML
representatio
n for vCard.
All available
attributes are
described in
the vCard
document
[IETF
RFC6350] and
listed bellow:
• General
Properties
(BEGIN, END,
SOURCE,
KIND, XML)
•
Identification
Properties
(FN, N,
NICKNAME,
PHOTO, BDAY,
Example
Sourc
e
A body responsible for
coordinating search and
rescue operations or
operations to tackle
pollution at sea (Coastal
station): 02
SSN
MRG
Name of a person called
Mr John Brown, M.Sc.:
<fn><text>Mr John
Brown,
M.Sc.</text></fn>
<n>
IETF
RFC
6351
<surname>Brown</surn
ame>
<given>John</given>
<additional/>
<prefix>Mr<prefix/>
<suffix>M.Sc.<suffix/>
</n>
more examples found
in: [IETF RFC6351]
Page 142 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Identifier
EUCISE2020
Data type
UniqueIdentifier
Description
Example
Sourc
e
ANNIVERSARY,
GENDER)
• Delivery
Addressing
Properties
(ADR)
•
Communicatio
ns Properties
(TEL, EMAIL,
IMPP, LANG)
•
Geographical
Properties (TZ,
GEO)
•
Organizational
Properties
(TITLE, ROLE,
LOGO, ORG,
MEMBER,
RELATED)
• Explanatory
Properties
(CATEGORIES,
NOTE,
PRODID, REV,
SOUND, UID,
CLIENTPIDMA
P, URL,
VERSION)
• Security
Properties
(KEY)
• Calendar
Properties
(FBURL,
CALADRURI,
CALURI)
Identifier of
the agent.
Each
UniqueIdentifi
er can be
correlated
with other
UniqueIdentifi
ers, either
manually, by
operators, or
automatically,
by systems, so
Page 143 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
IsOfInterest
boolean
IsSuspect
boolean
Metadata
Metadata
Nationality
String
EUCISE2020
Description
that duplicate
objects in the
network can
be identified
and brought
together for a
better
understanding
of the
information
being shared.
Attribute is
flagging an
interest to
follow more
closely any
activities
related to the
Agent. Value
of the
attribute can
be either true
or false (true =
1 and false =
0)
Attribute is
flagging a
possible
suspicion of
illegal
activities
related to the
Agent. Value
of the
attribute can
be either true
or false (true =
1 and false =
0)
see: Core
Vocabulary
Specification
for
"Metadata"
Three-letter
country codes
to represent
countries,
dependent
territories,
and special
areas of
Example
Sourc
e
0
There is some suspect
related to the agent:
1
DCMI
Portugal: PT
ISO
3166
-1
(alph
a-2 )
Page 144 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Description
Example
Sourc
e
geographical
interest
(*) Inherited attributes are coloured in grey.
15.2.5.2. Association Roles
UML Name
Document
InvolvedEvent
Data type
Document
Event
Description
Multiplicity
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class AgentObject.
InvolvedRisk
Risk
The association has additional attributes. Please check
association class AgentRisk.
InvolvedWith
Agent
The association has additional attributes. Please check
association class AgentAgent.
Location
Location
The association has additional attributes. Please check
association class AgentLocation.
(*) Inherited association roles are coloured in grey.
15.2.6.
OrganizationClassificationType Enumeration
This enumeration presents the formal classification (status) of organization.
15.2.6.1. Enumeration Values
Value
01
02
03
04
05
06
07
98
99
Label
governmental
european
member state
non-governmental
criminal
private
inter governmental
other
non-specified
Description
Governmental organization.
European agency.
Representing the government of a member state.
International organization, independent of governments.
Company involved in organized crime.
Private sector company.
International organization between governments.
Any other not mentioned before
Not declared
Source
15.2.6.2. Enumeration Usage
The following attributes use this enumeration as data type:
 OrganizationClassification (Organization)
15.2.7.
OrganizationPurposeType Enumeration
This enumeration presents the general purpose of the organization.
15.2.7.1. Enumeration Values
Value
01
Label
general law
enforcement
02
customs
EUCISE2020
Description
Authorities responsible for:
• Monitoring of compliance with applicable legislation in sea areas,
where there is policing competence; support to enforcement and/or
response operations
Authorities responsible for:
• Monitoring of compliance with customs regulations on the import,
export and movement of goods; support of enforcement operations
Source
Page 145 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
Label
03
marine
environment
04
maritime safety
and security
05
defence
06
fisheries control
07
border control
08
profitable
09
non-profitable
98
99
other
non-specified
Description
• Early warning/identification of criminal trafficking of goods (narcotics,
weapons, etc.); support of response operations
Authorities responsible for:
• Monitoring of compliance with regulations on the protection of the
marine environment; support of enforcement operations
• Early warning/identification of incidents/accidents that may have an
environmental impact; support of pollution response operations
Authorities responsible for:
• Monitoring of compliance with regulations on the safety and
prevention of pollution caused by ships (construction, equipment,
crew/passengers, cargo); support of enforcement operations
• Monitoring of compliance with regulations on the safety of navigation
(vessel traffic safety); support of enforcement operations
• Monitoring of compliance with regulations on the security of ships;
support of enforcement operations
• Supporting safe and efficient flow of vessel traffic; vessel traffic
management
• Early warning/identification of ships/persons in distress; support of
response operations (search and rescue, salvage, place of refuge)
• Early warning/identification of maritime security threats, within the
scope of SOLAS Chapter XI-2; support of response operations
• Early warning/identification of threats/acts of piracy or armed
robbery; support of response operations
Authorities responsible for:
• Monitoring in support of general Defence tasks, such as: exercising
national sovereignty at sea; combating terrorism and other hostile
activities outside the EU; other Common Security and Defence Policy
tasks, as defined in Articles 42 and 43 TEU.
Authorities responsible for:
• Monitoring of compliance with regulations on fisheries; support of
enforcement operations
• Early warning/identification of illegal fisheries or fish landings;
support of response operations
Authorities responsible for:
• Monitoring of compliance with regulations on immigration and border
crossing; support of enforcement operations
• Early warning/identification of cases of illegal migration or trafficking
in human beings; support of response operations
Not authority. Private or public organization/company which is expected
to make profit.
Nor authority. Private or public organization which is not expected to
make profit.
Any other not mentioned before
Not declared
Source
15.2.7.2. Enumeration Usage
The following attributes use this enumeration as data type:
 OrganizationPurpose (Organization)
15.2.8.
OrganizationRoleType Enumeration
Source: SSN MRG
EUCISE2020
Page 146 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
15.2.8.1. Enumeration Values
Value
01
Label
port
authority
02
coastal
station
03
port state
control
04
national
competent
authority
05
inspection
authority
other
non-specified
98
99
Description
SSN::Port authority. Port Authority means the competent authority or
body designated by Member States for each port to receive and pass on
information reported pursuant to the directive.
SSN::Coastal station. Coastal Station means any of the following,
designated by Member States pursuant to the directive:
• A vessel traffic service (VTS)
• A shore-based installation responsible for a mandatory reporting system
approved (adopted) by the IMO
• A body responsible for coordinating search and rescue operations or
operations to tackle pollution at sea
SSN::Port state control. The competent authority for inspecting the foreign
ships in national ports to verify that the condition of the ship and its
equipment comply with the requirements of international regulations and
that the ship is manned and operated in compliance with these rules.
SSN::National competent authority. Physical entity designated by Member
States in charge of handling and exchanging the SafeSeaNet messages
related to the maritime safety and the traffic monitoring directive. The
single point of contact within the Member State is designated as NCA in
the framework of SafeSeaNet.
SSN::Incident::Inspection authority. Competent authority for incident
inspections.
Any other not mentioned before
Not declared
Source
15.2.8.2. Enumeration Usage
The following attributes use this enumeration as data type:
 OrganizationRole (Organization)
EUCISE2020
Page 147 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
16. Period Core Entity
16.1. UML models
16.2. Elements defined in the Core Vocabulary
16.2.1.
Period Datatype
The class Period is used to define a time interval which can be expressed by:
 only a duration (i.e. one month),

a duration and a start (resp. end) date [ex.: a period of ten days starting (resp. ending) on
December 10th, 2002], in this case the period is assumed to start (resp. end) on December 10th
at 0:00 (resp. 23:59).

a duration and a start (resp. end) time [ex.: a period of ten days starting (resp. ending) at 10am],

a duration and start (resp. end) date and time (ex.: a period of ten days starting (resp. ending)
on December 10th, 2002, 10am),

a start Date and an end Date (ex.: December 3rd, 2002 & January 24th 2010),

a start Time and an end Time (ex.: 9am and 10pm),

a start date and start time following by an end date and end time (ex.: December 3rd, 2002 at
10pm and January 24th, 2010 at 9am).
16.2.1.1. Attributes
EUCISE2020
Page 148 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML
Name
Duration
Data type
XSD::Duration
Description
The Duration attribute is used to define a
time interval. It is from the standard XML
schema Duration type (XSD:Duration).
The time interval is specified in the following
form "PnYnMnDTnHnMnS" where:
•P indicates the period (required)
•nY indicates the number of years
•nM indicates the number of months
•nD indicates the number of days
•T indicates the start of a time section
(required if you are going to specify hours,
minutes, or seconds)
•nH indicates the number of hours
•nM indicates the number of minutes
•nS indicates the number of seconds.
EndDate
XSD::Date
EndTime
XSD::Time
StartDate
XSD::Date
To specify a negative duration, enter a minus
sign before the P.
The EndDate attribute is used to specify the
end date of something located in time. It is
from the standard XML Schema Date type
(XSD:Date).
The EndTime attribute is used to specify the
end time of something located in time. It is
from the standard XML Schema Time type
(XSD:Time).
The StartDate attribute is used to specify a
starting date. It is from the standard XML
Schema Date type (XSD:Date).
Example
Source
“P5Y” for a period of
five years.
“PT15H” for a period
of 15 hours.
“-P10D” for a period
of -10 days (useful
when combined to an
End Date.
2002-09-24
09:00:00
2002-09-24
The start date is specified in the following
form "YYYY-MM-DD" where:
•YYYY indicates the year
•MM indicates the month
•DD indicates the day
StartTime
XSD::Time
Note: All components are required!
The StartTime attribute is used to specify a
starting time. . It is from the standard XML
Schema Time type (XSD:Time).
09:00:00
The time is specified in the following form
"hh:mm:ss" where:
•hh indicates the hour
•mm indicates the minute
•ss indicates the second
Note: All components are required!
EUCISE2020
Page 149 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
16.2.1.2. Constraints
Name
Coherent
Duration
Earlier
EndDate
Description
StartDate + StartTime plus
Duration equals EndDate +
Endtime
EndDate can not be earlier than
StartDate
Earlier
EndTime
Mandatory
Fields
EndTime can not be earlier than
StartTime
StartDate or EndDate or
Duration must be filled
EUCISE2020
OCL Constraint
context Period::Duration(): Float
post: result = self.EndDate + self.EndTime - (self.StartDate
+ self.StartTime)
context Period
inv: self.EndDate.DateTimeAsFloat >
self.StartDate.DateTimeAsFloat
context Period
inv: self.EndTime > self.StartTime
context: Period
inv: ( self.StartDate.isNull=true and
self.EndDate.isNull=true and self.Duration.isNull=true ) =
false
Page 150 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
17. Person Core Entity
17.1. UML models
17.2. Elements defined in the Core Vocabulary
17.2.1.
Person Class (subclass of Agent)
The Person Class is a sub class of the more general 'Agent' class that encompasses organizations, legal entities,
groups etc. - any entity that is able to carry out actions. The data type properties of the Person class do not have
any cardinality restrictions and as such all are optional. However, guidance is provided for the usage of each
property in the following sections.
17.2.1.1. Attributes
UML Name
AlternativeName
EUCISE2020
Data type
String
Description
Any name by which an
individual is known other than
their full name. Many
individuals use a short form of
their name, a 'middle' name as
a 'first' name or a professional
name. For example, the British
politician and former UN High
Example
Lord Ashdown
Sourc
e
ISA
CORE
Page 151 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
BirthDate
XSD::Date
BirthName
String
DateOfDeath
XSD::DateTime
FamilyName
String
FullName
String
EUCISE2020
Description
Representative for Bosnia and
Herzegovina, Jeremy John
Durham Ashdown, Baron
Ashdown of Norton-subHamdon, is usually referred to
simply as 'Paddy Ashdown' or
'Lord Ashdown'.
A date that specifies the birth
date of a person. Format yyyymm-dd
All data associated with an
individual are subject to
change. Names can change for
a variety of reasons, either
formally or informally, and new
information may come to light
that means that a correction or
clarification can be made to an
existing record. Birth names
tend to be persistent however
and for this reason they are
recorded by some public sector
information systems. There is
no granularity for birth name the full name should be
recorded in a single field.
A date that specifies the death
date of a person. Format yyyymm-ddThh:mm:ss
A family name is usually shared
by members of a family. This
attribute also carries prefixes or
suffixes which are part of the
Family Name, e.g. “de Boer”,
“van de Putte”, “von und
zuOrlow”. Multiple family
names, such as are commonly
found in Hispanic countries, are
recorded in the single Family
Name field so that, for example,
Miguel de Cervantes Saavedra's
Family Name would be
recorded as "de Cervantes
Saavedra".
Complete name of a person.
The Full Name is the most
reliable label for an individual
and as such its use is strongly
encouraged, irrespective of
whether that name is broken
down using the more granular
elements. A name usually sticks
Example
Sourc
e
1930-06-22
ISA
CORE
Johan
ISA
CORE
1930-06-22T19:15:30
ISA
CORE
de Cervantes Saavedra
ISA
CORE
George Smith
ISA
CORE
Page 152 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Gender
GenderType
GivenName
String
PatronymicName
String
EUCISE2020
Description
with a person for a long time
period. In some European
countries a name may only be
changed according to certain
laws and life events, e.g.
marriage. The name
denominates a natural person
even if he/she changes their
address. Documents like birth
certificate or diploma usually
don’t carry an address but
always the name. Thus the
name is one of the core
attributes. However it is not
sufficient to identify a person
since there are combinations of
very common names like Smith
in the UK, Meier in Germany, or
Li in China.
The gender of an individual.
Eurostat SCL - Sex [SCLS]
possible values:
Female/Male/Other/Unknown/
Not applicable.
A given name, or multiple given
names, are the denominator(s)
that identify an individual
within a family. These are given
to a person by his or her
parents at birth or may be
legally recognised as 'given
names' through a formal
process. All given names are
ordered in one field so that, for
example, the Given Name for
Johan Sebastian Bach is 'Johan
Sebastian.'
Patronymic names are
important in some countries.
Iceland does not have a concept
of 'family name' in the way that
many other European countries
do, for example. Erik
Magnusson and Erika
Magnusdottir are siblings, both
offspring of Magnus,
irrespective of his patronymic
name. In Bulgaria and Russia,
patronymic names are in every
day usage, for example, the
Sergeyevich in 'Mikhail
Sergeyevich Gorbachev'.
Example
Sourc
e
Female
ISA
CORE
Johan Sebastian
ISA
CORE
Sergeyevich
ISA
CORE
Page 153 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Description
Example
Sourc
e
Patronymic names refer to a
father's given name, not the
family name inherited from the
mother and father as is the case
in countries such as Spain and
Portugal. Again referring to the
example of Miguel de Cervantes
Saavedra's, the patronymic
name element would be
unused.
PersonIdentifiers
ContactInformati
on
Identifier
EUCISE2020
PersonIdentifi
er
String
UniqueIdentifi
er
vCard [IETF RFC6350] is a data
format for representing and
exchanging information about
individuals and other entities. It
is a text-based format (as
opposed to a binary format).
xCard [IETF RFC6351] is an XML
representation for vCard. All
available attributes are
described in the vCard
document [IETF RFC6350] and
listed bellow:
• General Properties (BEGIN,
END, SOURCE, KIND, XML)
• Identification Properties (FN,
N, NICKNAME, PHOTO, BDAY,
ANNIVERSARY, GENDER)
• Delivery Addressing
Properties (ADR)
• Communications Properties
(TEL, EMAIL, IMPP, LANG)
• Geographical Properties (TZ,
GEO)
• Organizational Properties
(TITLE, ROLE, LOGO, ORG,
MEMBER, RELATED)
• Explanatory Properties
(CATEGORIES, NOTE, PRODID,
REV, SOUND, UID,
CLIENTPIDMAP, URL, VERSION)
• Security Properties (KEY)
• Calendar Properties (FBURL,
CALADRURI, CALURI)
Identifier of the agent.
Each UniqueIdentifier can be
correlated with other
UniqueIdentifiers, either
manually, by operators, or
automatically, by systems, so
that duplicate objects in the
Name of a person called
Mr John Brown, M.Sc.:
<fn><text>Mr John Brown,
M.Sc.</text></fn>
<n>
IETF
RFC
6351
<surname>Brown</surna
me>
<given>John</given>
<additional/>
<prefix>Mr<prefix/>
<suffix>M.Sc.<suffix/>
</n>
more examples found in:
[IETF RFC6351]
Page 154 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
IsOfInterest
boolean
IsSuspect
boolean
Metadata
Metadata
Nationality
String
Description
network can be identified and
brought together for a better
understanding of the
information being shared.
Attribute is flagging an interest
to follow more closely any
activities related to the Agent.
Value of the attribute can be
either true or false (true = 1 and
false = 0)
Attribute is flagging a possible
suspicion of illegal activities
related to the Agent. Value of
the attribute can be either true
or false (true = 1 and false = 0)
see: Core Vocabulary
Specification for "Metadata"
Three-letter country codes to
represent countries, dependent
territories, and special areas of
geographical interest
Sourc
e
Example
0
There is some suspect
related to the agent:
1
DCMI
Portugal: PT
ISO
31661
(alpha
-2 )
(*) Inherited attributes are coloured in grey.
17.2.1.2. Association Roles
UML Name
Document
InvolvedEvent
Data type
Document
Event
Description
The association has additional attributes. Please check
association class AgentEvent.
InvolvedObject Object
The association has additional attributes. Please check
association class AgentObject.
InvolvedRisk
Risk
The association has additional attributes. Please check
association class AgentRisk.
InvolvedWith
Agent
The association has additional attributes. Please check
association class AgentAgent.
Location
Location
The association has additional attributes. Please check
association class AgentLocation.
(*) Inherited association roles are coloured in grey.
17.2.2.
Multiplicity
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
0..* (allow
duplicates)
PersonIdentifier Datatype
The PersonIdentifier class allows the identification of the Person by means of a document of given type and
related id number, according to the different countries policy.
17.2.2.1. Attributes
UML Name
IdentifierType
Data type
PersonIdentificationType
IdentifierValue
String
17.2.3.
Description
Type of document identifying the
Person
Identification number of document
Example
IdentityCard
Source
199000592
GenderType Enumeration
The gender of an individual.
EUCISE2020
Page 155 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Source: Eurostat SCL - Sex [SCLS]
17.2.3.1. Enumeration Values
Value
01
02
03
04
05
Label
female
male
other
unknown
not applicable
Description
Female
Male
Other gender, not male neither female
Unknown
Not Applicable
Source
17.2.3.2. Enumeration Usage
The following attributes use this enumeration as data type:
 Gender (Person)
17.2.4.
PersonIdentificationType Enumeration
17.2.4.1. Enumeration Values
Value
01
02
03
04
05
06
98
99
Label
identity card
social security card
passport
fiscal document
VISA
crew master book
other
non-specified
Description
Identity Card
Social Security Card
Passport
Fiscal Document
Visa International Service Association Card
Crew Master Book
Other value not included in the list
Not Specified
Source
17.2.4.2. Enumeration Usage
The following attributes use this enumeration as data type:
 IdentifierType (PersonIdentifier)
EUCISE2020
Page 156 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
18. Risk Core Entity
18.1. UML models
18.2. Elements defined in the Core Vocabulary
18.2.1.
Risk Class (subclass of Entity)
The class Risk is used to represent a more or less probable situation involving exposure to danger concerning
the maritime domain. The notion of risk is usually very subjective and, in a first step, we decided to keep the
definition of the class simple in order to ease its adoption. Further work could be used to detail the risk
definition and introduce metrics regarding probability and severity.
18.2.1.1. Attributes
UML Name
Identifier
Data type
UniqueIdentifier
Metadata
Metadata
EUCISE2020
Description
Identifier of the risk.
Each UniqueIdentifier can be
correlated with other
UniqueIdentifiers, either manually,
by operators, or automatically, by
systems, so that duplicate objects in
the network can be identified and
brought together for a better
understanding of the information
being shared.
The Metadata of a Risk
Example
Source
Page 157 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
OccurrencePeriod
Data type
Period
RiskLevel
RiskLevelType
RiskProbability
RiskProbabilityType
RiskSeverity
RiskSeverityType
RiskType
RiskType
Description
Defines the period of time
concerned by the Risk.
The risk level is used to define the
importance of a risk on the
maritime domain.
The probability of occurrence of the
risk
The importance of the
consequences of the risk
Identifies the type of the risk
Example
Source
for an medium
risk level
02
for an occasional
risk: 03
for risk with few
consequences on
the maritime
activities: 03
for an accident
risk: 01
18.2.1.2. Association Roles
UML Name
Document
ImpliedEvent
InvolvedAgent
Data type
Document
Event
Agent
InvolvedObject
Location
Object
Location
Description
Multiplicity
0..*
0..*
0..* (allow
duplicates)
0..*
0..*
The association has additional attributes. Please check
association class AgentRisk.
18.2.1.3. Constraints
Name
Coherent
Level
18.2.2.
OCL
Constraint
Description
The Level attribute must be defined in accordance with the Probability and
Severity attributes when present.
RiskLevelType Enumeration
The risk level is defined regarding the impact of the risk’s occurrence. It is a combination of the two previous
data: risk probability and risk severity. A risk which occurs frequently and has a critical severity will have a high
risk level. Respectively, a low probability risk with negligible severity will have a low risk level. This enumeration
presents the possible risk levels.
18.2.2.1. Enumeration Values
Value
01
02
03
Label
high
medium
low
98
99
other
nonspecified
Description
A high level risk occurs frequently and has important consequences
Medium level risks have medium impact on maritime activities
A low level risk has a low impact on maritime activities (improbable or rare
risk, risk with negligible severity)
Risk level not included above
Risk level non-specified
Source
18.2.2.2. Enumeration Usage
The following attributes use this enumeration as data type:
 RiskLevel (Risk)
18.2.3.
EUCISE2020
RiskProbabilityType Enumeration
Page 158 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
18.2.3.1. Enumeration Values
Value
01
02
03
04
05
98
99
Label
frequent
probable
occasional
rare
improbable
other
non-specified
Description
The risk occurs frequently
The risk is probable
The risk could occur on some occasions
The occurrence of the risk is rare
The risk is improbable
Risk Probability not included above
Risk Probability non-specified
Source
18.2.3.2. Enumeration Usage
The following attributes use this enumeration as data type:
 RiskProbability (Risk)
18.2.4.
RiskSeverityType Enumeration
This enumeration presents the different severities which can be assigned to a risk.
18.2.4.1. Enumeration Values
Value
01
Label
catastrophic
02
critical
03
marginal
04
98
99
negligible
other
nonspecified
Description
A major catastrophic event is the consequence of the risk (death of people,
major pollution…)
The occurrence of the risk leads to major consequences affecting maritime
activities (maritime traffic blocked…)
The risk’s consequences are marginal. The risk as no impact on maritime
activities, people or cargo.
The risk’s consequences are negligible.
Risk severity not included above
Risk severity non-specified
Source
18.2.4.2. Enumeration Usage
The following attributes use this enumeration as data type:
 RiskSeverity (Risk)
18.2.5.
RiskType Enumeration
This enumeration presents the possible types of Risks.
18.2.5.1. Enumeration Values
Value
01
02
03
04
05
06
07
08
09
10
98
EUCISE2020
Label
accident
illegal immigration
drug trafficking
collision
human trafficking
smuggling
illegal fishing
weapons trafficking
fire
pollution
other
Description
Accident
Illegal Immigration
Drug Trafficking
Collision
Human Trafficking
Smuggling
Illegal Fishing
Weapons Trafficking
Fire
Pollution
Risk type not included above
Source
Page 159 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
99
Label
non-specified
Description
Risk type non-specified
Source
18.2.5.2. Enumeration Usage
The following attributes use this enumeration as data type:
 RiskType (Risk)
EUCISE2020
Page 160 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
19. UniqueIdentifier Core Entity
19.1. UML models
19.2. Elements defined in the Core Vocabulary
19.2.1.
UniqueIdentifier Class
The Unique Identifier is a fundamental entity of the overall data model of the information sharing environment,
since it will allow, as it name implies, to uniquely identify each and every single data object exchanged through
the network. With this identifier it will also be possible for the legacy systems to keep trace of the relationships
between their data objects and those from the information sharing environment. It will be possible to
understand who and when is publishing each and every data object in the network.
19.2.1.1. Attributes
UML Name
GeneratedBy
Data type
Organization
GeneratedIn
XSD::DateTime
UUID
String
Description
Organization that generated the Unique
Identifier object
Date and time when this UUID was
generated
UUID is represented by 32 hexadecimal
digits, displayed in five groups separated
by hyphens, in the form 8-4-4-4-12 for a
total of 36 characters (32 alphanumeric
characters and four hyphens
Example
19 OCT 2013
22:36:45
550e8400-e29b41d4-a716446655440000
Source
IETF
RFC
4122
19.2.1.2. Association Roles
UML Name
correlatedWith
Data type
UniqueIdentifier
Description
The association has additional attributes. Please
check association class CorrelatedWith.
Multiplicity
0..* (allow
duplicates)
19.2.1.3. Constraints
EUCISE2020
Page 161 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Name
No selfcorrelations
Description
object can not be correlated with
itself
Uniqueness
19.2.2.
There is only one object for each
uniqueidentifier
OCL Constraint
context: UniqueIdentifier
inv: self.correlatesTo <> self
context: UniqueIdentifier
inv: self.correlatedBy <> self
context: UniqueIdentifier
inv: UniqueIdentifier->allInstances()->forAll(n1,
n2| n1.UUID<>n2.UUID)
CorrelatedWith Association Class
This class allows the correlation among the different objects in the information sharing environment. This
correlation will allow the identification and "merging" of duplicate objects in the network, thus making the
information shared more understandable.
19.2.2.1. Attributes
UML Name
CorrelatedBy
CorrelatedIn
Data type
Organization
XSD::DateTime
CorrelationType
CorrelationType
19.2.3.
Description
Organization that correlated two UUIDs
Date and time when this correlation
was made
Process used to perform the correlation
Example
Source
19 OCT 2013
22:36:45
Manual
CorrelationType Enumeration
This enumeration presents the possible types of processes used to perform the objects correlation.
19.2.3.1. Enumeration Values
Value
01
02
98
99
Label
manual
automatic
other
non-specified
Description
Correlation performed by an operator
Correlation performed automatically by a system
Correlation performed by any other process not listed here
The correlation process is not declared
Source
19.2.3.2. Enumeration Usage
The following attributes use this enumeration as data type:
 CorrelationType (CorrelatedWith)
EUCISE2020
Page 162 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
20. Vessel Core Entity
20.1. UML models
EUCISE2020
Page 163 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
EUCISE2020
Page 164 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
20.2. Elements defined in the Core Vocabulary
20.2.1.
Vessel Class (subclass of Vehicle)
The class Vessel is a sub-class of the class Vehicle. A vessel refers to a ship or a boat. Vessel has the same
associations and relationships than its parent-classes Vehicle and Object. Thus it can have relationship with
Document, Risk, Event, Location, and Agent. It can also be associated with OperationalAsset.
20.2.1.1. Attributes
UML Name
Arrangement
Beam
String
int
Breadth
int
CallSign
String
ConditionOfTheCargoAndB
allast
ConditionOfTheCargoAndBalla
stType
ContainerCapacity
int
Deadweight
int
Depth
DesignSpeed
double
double
Draught
double
FishingGear
FishingGearType
GrossTonnage
double
HullMaterial
HullMaterialType
IMONumber
long
EUCISE2020
Data type
Description
Arrangement
Beam
measurement
in meters.
Distance side
to side of the
vessel in
meters
Callsign as
defined by
ITU-R M.1371
Indicates the
current load of
cargo and
ballast
Container
capacity in
feet. Available
in common
standard
lengths of 20ft (6.1 m), 40ft (12.2 m), 45ft (13.7 m), 48ft (14.6 m),
and 53-ft (16.2
m).
Dead weight in
tonnes
Depth
Design speed
in knots
Draught in
meter
Indicates the
type of fishing
gear aboard
the vessel
Gross tonnage
(no unit)
Hull material
The IMO
number of the
vessel.
Example
Source
30
32
MTDM5
ITU-R
M.13711
NSW
Full
20 (20-ft)
ISO
container
dimensio
ns and
payloads
53807
12
1.2 (1.2
meters)
05 (lift nets)
FAO
48788
NSW
High Strength
Steel
9074729
IMO ISPS
Code
Page 165 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
INFShipClass
Data type
INFClassType
INMARSATNumber
String
IRNumber
String
IsBanned
boolean
IsFishing
boolean
ISPSSSecurityLevel
ISPSSecurityLevelType
Length
double
LengthenedYear
int
LOA
double
MMSI
long
NavigationalStatus
NavigationalStatusType
NetTonnage
RegionalIdentification
double
String
RegistryDate
RegistryNumber
XSD::Date
String
SegregatedBallastVolume
double
EUCISE2020
Description
International
Code for the
Safe Carriage
of Packaged
Irradiated
Nuclear Fuel,
Plutonium and
High-Level
Radioactive
Wastes on
Board Ships
INMARSAT
number
Information
request
number for
the vessel.
Indicates if a
vessel is
banned
Indicates if a
vessel is
currently
fishing
International
Ship and Port
Security levels
as defined by
the ISPS code
Length in
meters.
Lengthened
year
Length overall
of the vessel in
meters.
MMSI number
as defined by
ITU-R M.1371
Navigational
status
enumeration
defined by the
IVEF standard
Net tonnage
Regional
identification
Registry date
Registry
number
Separated
volume of
ballast
Example
INF1
Source
IMO ISPS
Code
00870+mobile
number
NSW
FALSE
FALSE
01 (Security
Level 1)
IMO ISPS
Code
294
2010
294
232000000
01 (At Anchor)
ITU-R
M.13711
IALA IVEF
47000
NSW
1952-12-21
212056
NSW
NSW
200
Page 166 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
ShipConfiguration
Data type
ShipConfigurationType
ShipType
VesselType
UnderSanitaryMeasure
SanitaryMeasureType
UVI
String
YearBuilt
int
MaximumSpeed
double
Nationality
String
TotalPersonsOnBoard
int
Colour
ColourType
ExternalMarkings
String
Identifier
UniqueIdentifier
EUCISE2020
Description
Indicates the
hull
configuration
of the vessel
Different types
of vessels.
Sanitary
measure to be
taken in
respect to the
vessel
Unique vessel
identifier
defined by the
FAO.
Year when the
vessel was
built
The vehicle’s
maximum
speed
measured in
knots
Two-letter
country codes
to represent
countries,
dependent
territories, and
special areas
of
geographical
interest.
Represent the
flag for a
Vessel.
The total
number of
persons on
board
Colour
information
about the
object
External
markings of
the object
Identifier of
the object.
Each
UniqueIdentifi
er can be
correlated
Example
Double hull
tanker
Source
NSW
Passenger ship
IMO
GISIS
NSW
04
(Decontaminati
on)
235210
FAO
1990
20
EUROSU
R
Country code
for Portugal:
PT (Country
code for
Portugal)
ISO
3166-1
10
Red
EUROSU
R
ABER
FLUX
Page 167 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
UML Name
Data type
Metadata
Metadata
Name
String
Description
with other
UniqueIdentifi
ers, either
manually, by
operators, or
automatically,
by systems, so
that duplicate
objects in the
network can
be identified
and brought
together for a
better
understanding
of the
information
being shared.
Metadata
related to the
object
Name of the
object
Example
ABERIII
Source
NSW
(*) Inherited attributes are coloured in grey.
20.2.1.2. Association Roles
UML Name
Cargo
CorrespondentAsset
Document
InvolvedAgent
Data type
Cargo
OperationalAsset
Document
Agent
InvolvedEvent
Event
InvolvedRisk
Location
Risk
Location
Description
The association has additional attributes.
Please check association class AgentObject.
The association has additional attributes.
Please check association class ObjectEvent.
The association has additional attributes.
Please check association class ObjectLocation.
Vehicles
Vehicle
(*) Inherited association roles are coloured in grey.
Multiplicity
0..1
0..1
0..*
0..* (allow
duplicates)
0..* (allow
duplicates)
0..*
0..* (allow
duplicates)
0..*
20.2.1.3. Constraints
Name
Description
OCL Constraint
Minimum of
The number of TotalPersonsOnBoard can not be smaller than
TotalPersonsOnBoard
the sum of master/crewmembers and passengers
(*) Inherited constraints are coloured in grey.
20.2.2.
ConditionOfTheCargoAndBallastType Enumeration
This enumeration presents the vessel load’s condition.
Source: NSW
20.2.2.1. Enumeration Values
EUCISE2020
Page 168 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
01
02
03
98
99
Label
full
empty
inerted
other
non-specified
Description
Vessel fully loaded
Vessel empty
Load inerted
Any other condition not mentioned above
Condition not specified
Source
NSW
NSW
NSW
20.2.2.2. Enumeration Usage
The following attributes use this enumeration as data type:
 ConditionOfTheCargoAndBallast (Vessel)
20.2.3.
FishingGearType Enumeration
This enumeration presents the list of fishing gears a vessel can be equipped with according to UN FAO rules.
Source: UN/FAO
20.2.3.1. Enumeration Values
Value
01
02
03
04
05
06
07
08
09
10
11
98
99
Label
surrounding nets
seine nets
trawl nets
dredges
lift nets
falling nets
gillnets and entangling nets
traps
hooks and lines
grappling and wounding gears
stupefying devices
other
non-specified
Description
Surrounding nets
Seine nets
Trawl nets
Dredges
Lift nets
Falling nets
Gillnets and entangling nets
Traps
Hooks and lines
Grappling and wounding gears
Stupefying devices
Any other gear not mentioned above
Gear not specified
Source
FAO FGM
FAO FGM
FAO FGM
FAO FGM
FAO FGM
FAO FGM
FAO FGM
FAO FGM
FAO FGM
FAO FGM
FAO FGM
20.2.3.2. Enumeration Usage
The following attributes use this enumeration as data type:
 FishingGear (Vessel)
20.2.4.
HullMaterialType Enumeration
This enumeration presents hull material types.
20.2.4.1. Enumeration Values
Value
01
98
99
Label
high strength steel
other
non-specified
Description
High Strength Steel
Any other type not mentioned above
Type not specified
Source
20.2.4.2. Enumeration Usage
The following attributes use this enumeration as data type:
 HullMaterial (Vessel)
20.2.5.
EUCISE2020
INFClassType Enumeration
Page 169 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
This enumeration presents the list of international codes for the Safe Carriage of Packaged Irradiated Nuclear
Fuel, Plutonium and High-Level Radioactive Wastes.||See
http://www.imo.org/OurWork/Safety/Cargoes/Pages/IrradiatedNuclearFuel.aspx for further details.
Source: IMO FSI 21/18
20.2.5.1. Enumeration Values
Value
INF1
Label
Class INF1
INF2
Class INF2
INF3
Class INF3
98
99
other
nonspecified
Description
Class INF 1 ship - Ships which are certified to carry INF cargo with an
aggregate activity less than 4,000 TBq (TeraBecquerel= measurement of
radioactivity)
Class INF 2 ship - Ships which are certified to carry irradiated nuclear fuel or
high-level radioactive wastes with an aggregate activity less than 2 x 106
TBq and ships which are certified to carry plutonium with an aggregate
activity less than 2 x 105 TBq.
Class INF 3 ship - Ships which are certified to carry irradiated nuclear fuel or
high-level radioactive wastes and ships which are certified to carry
plutonium with no restriction of the maximum aggregate activity of the
materials
Any class not mentioned above
Class not specified
Source
IMO FSI
21/18
IMO FSI
21/18
IMO FSI
21/18
20.2.5.2. Enumeration Usage
The following attributes use this enumeration as data type:
 INFShipClass (Vessel)
20.2.6.
ISPSSecurityLevelType Enumeration
This enumeration presents the possible values for the security level of the port.||(This enumeration presents
the three levels of the ISPS code. See
http://www.imo.org/blast/mainframe.asp?topic_id=583&doc_id=2689#code for further details.)
Source: IMO ISPS Code
20.2.6.1. Enumeration Values
Value
01
Label
security
level1
02
security
level2
03
security
level3
98
99
other
nonspecified
Description
Normal, the level at which the ship or port facility normally operates.
Security level 1 means the level for which minimum appropriate protective
security measures shall be maintained at all times.
Heightened, the level applying for as long as there is a heightened risk of a
security incident. Security level 2 means the level for which appropriate
additional protective security measures shall be maintained for a period of
time as a result of heightened risk of a security incident.
Exceptional, the level applying for the period of time when there is the
probable or imminent risk of a security incident. Security level 3 means the
level for which further specific protective security measures shall be
maintained for a limited period of time when a security incident is probable
or imminent, although it may not be possible to identify the specific target.
Any other security level not mentioned above
Security level not specified
Source
IMO
ISPS
Code
IMO
ISPS
Code
IMO
ISPS
Code
20.2.6.2. Enumeration Usage
The following attributes use this enumeration as data type:
EUCISE2020
Page 170 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0

PortSecurityLevel (PortFacilityLocation)

ISPSSSecurityLevel (Vessel)

PortSecurityLevel (PortLocation)
20.2.7.
NavigationalStatusType Enumeration
This enumeration presents the different types of navigational statuses in accordance with the inter VTS
exchange format.
Source: IALA IVEF
20.2.7.1. Enumeration Values
Value
00
Label
under way using engine
Description
Under way using engine
01
at anchor
At anchor
02
not under command
Not under command
03
restricted manoeuvrability
Restricted manoeuvrability
04
constrained by her draught
Constrained by her draught
05
moored
Moored
06
aground
Aground
07
engaged in fishing
Engaged in fishing
08
under way sailing
Under way sailing
09
engaged in fishing other than trawling
Engaged in fishing other than trawling
10
air cushion vessel in non-displamenet
mode or WIG craft taking off landing or in
flight
power driven vessel towing astern
Air-cushion vessel in non-displacement
mode or WIG craft taking off, landing or in
flight
Power driven vessel towing astern
13
power driven vessel towig ahead or
pushing alongside
in distress or requiring assistance
Power driven vessel towing ahead or
pushing alongside
In distress or requiring assistance
14
AISSART seeking to attract attention
AIS SART, seeking to attract attention
15
undefined default
Undefined default
98
99
other
non-specified
Any other severity not mentioned above
Severity not specified
11
12
Source
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
IALA
IVEF
20.2.7.2. Enumeration Usage
The following attributes use this enumeration as data type:
 NavigationalStatus (Vessel)
EUCISE2020
Page 171 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
20.2.8.
SanitaryMeasureType Enumeration
This enumeration presents the list of sanitary measure a vessel can be the object of.
Source: NSW
20.2.8.1. Enumeration Values
Value
01
02
03
04
98
99
Label
quarantine
isolation
disinfection
decontamination
other
non-specified
Description
Quarantine
Isolation
Disinfection
Decontamination
Any other sanitary measure not mentioned above
Sanitary measure not specified
Source
NSW
NSW
NSW
NSW
20.2.8.2. Enumeration Usage
The following attributes use this enumeration as data type:
 UnderSanitaryMeasure (Vessel)
20.2.9.
ShipConfigurationType Enumeration
This enumeration presents the list of ship configuration types.
Source: NSW
20.2.9.1. Enumeration Values
Value
SHT
SHTBHT
DHT
98
Label
Single hull tanker
Single hull with segregatted ballast
tanks
Double hull tanker
other
99
non-specified
Description
Single hull tanker
Single hull with segregated ballast tanks
Source
NSW
NSW
Double hull tanker
Any other ship configuration type not mentioned
above
Ship configuration type not specified
NSW
20.2.9.2. Enumeration Usage
The following attributes use this enumeration as data type:
 ShipConfiguration (Vessel)
20.2.10.
VesselType Enumeration
This enumeration presents the different types of Vessel. This list is limited to general type of vessel. It could be
detailed in further modeling activities.
Source: IMO GISIS
20.2.10.1.
Value
01
02
03
04
05
06
07
EUCISE2020
Enumeration Values
Label
passenger ship
fishing vessel
nuclear ship
bulk carrier
oil tanker
general cargo ship
high speed craft
Description
Passenger ship
Fishing vessel
Nuclear ship
Bulk carrier
Oil tanker
General cargo ship
High-speed craft
Source
IMO GISIS
IMO GISIS
IMO GISIS
IMO GISIS
IMO GISIS
IMO GISIS
IMO GISIS
Page 172 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Value
08
09
98
99
Label
mobile off shore drilling unit
special purpose ship
other
non-specified
20.2.10.2.
Description
Mobile off-shore drilling unit
Special purpose ship
Any other certainty not mentioned above
Certainty not specified
Source
IMO GISIS
IMO GISIS
Enumeration Usage
The following attributes use this enumeration as data type:
 ShipType (Vessel)
EUCISE2020
Page 173 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
21. References
The following information sources were used during the design of the model:
Reference
Author
Title
Disaster and emergency management - Shared situation awareness Part 1: Message structure
(http://standards.cen.eu/dyn/www/f?p=204:110:0::::FSP_PROJECT:3267
6&cs=1DB63724BE7CED45756D9BACF421AFCDB https://www.oasisopen.org/committees/download.php/42411/CWA_15931-1.pdf)
WCO
Europea
n
Committ
ee for
Standard
ization
WCO
DCMI
DC
ERS
Fisheries
IMO FAL
IMO
FAO FGM
FLUX
UN/FAO
UN/CEF
ACT
BONN
AGREEME
NT
Bonn
Agreem
ent
Secretari
at
ITU-R
CWA
159311:2009
ITU-R
M.1371-1
IMO
MARPOL annex II
IMO
IMO
IMDG
IMO GISIS
IMO
IETF RFC
3986
W3C XSD
1
IETF
EUCISE2020
IMO
W3C
WCO Data Model
(http://www.wcoomd.org/en/topics/facilitation/instrument-andtools/tools/pf_tools_datamodel.aspx)
DCMI Metadata Terms
Date Version
11 Feb
2009 -
-
Commission Implementing Regulation (EU) No 404/2011 of 8 April 2011
laying down detailed rules for the implementation of Council Regulation
(EC) No 1224/2009 establishing a Community control system for
ensuring compliance with the rules of the Common Fisheries Policy
(http://eurlex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32011R0404:EN:NO
T http://ec.europa.eu/fisheries/cfp/control/codes/index_en.htm)
FAL Forms and Certificates
(http://www.imo.org/OurWork/Facilitation/FormsCertificates/Pages/Def
ault.aspx)
Fishing gears and methods (http://www.fao.org/fishery/topic/1617/en)
Business Requirements Specification (BRS) - Fisheries Language for
Universal eXchange
Bonn Agreement counter pollution manual
(http://www.bonnagreement.org/site/assets/files/3946/bonn_agreeme
nt_counter_pollution_manual.pdf
http://www.bonnagreement.org/manuals)
Recommendation ITU-R M.1371-1. Technical characteristics for a
universal shipborne automatic identification system using time division
multiple access in the VHF maritime mobile band
(https://archive.org/details/gov.law.itu-r.M-1371-1.2001)
Regulations for the control of pollution by noxious liquid substances in
bulk
(http://www.imo.org/About/Conventions/ListOfConventions/Pages/Inte
rnational-Convention-for-the-Prevention-of-Pollution-from-Ships(MARPOL).aspx
http://www.imo.org/blast/mainframe.asp?topic_id=848&doc_id=4405)
International Maritime Dangerous Goods (IMDG) Code
(http://www.imo.org/Publications/IMDGCode/Pages/Default.aspx)
IMO Global Integrated Shipping Information System (GISIS)
(http://gisis.imo.org/Public/Default.aspx)
Uniform Resource Identifier (URI): Generic Syntax
(http://www.ietf.org/rfc/rfc3986.txt)
W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures. W3C
Recommendation (http://www.w3.org/TR/xmlschema11-1/)
14 Jun
2012 08 Apr
2011 -
No date -
2013 22 May
2013 0.5.2
Draft
May
2014 -
2001 -
-
No date 05 Apr
2012 -
Page 174 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Reference
Author
W3C XSD
2
IALA IVEF
W3C
ISO 6346
ISO
ISO 8601
ISO
OASIS
CAP
OASIS
IMO FSI
21/18
IMO
ISA CORE
ISA
EUROSUR
Frontex
UNECE
Recomme
ndation
21 annex IV
UNECE
ANSI /
NISO
Z39.852007
e-NOA/D
ANSI/NI
SO
IMO
MSC.1/Cir
c.1333
IALA
The
United
States
Coast
Guard
(USCG)
IMO
IMO ISPS
Code
IMO
UN/LOCO
DE
UN/CEF
ACT
EUCISE2020
Title
XML Schema Part 2: Datatypes Second Edition. W3C Recommendation
(http://dublincore.org/documents/dcmi-terms/)
IALA Recommendation V-145 on the Inter-VTS Exchange Format (IVEF)
Service (http://www.iala-aism.org/publications/1707091216/inter-vtsexchange-format-service-145)
Freight containers -- Coding, identification and marking
(http://www.iso.org/iso/catalogue_detail?csnumber=20453)
Date and time format
(http://www.iso.org/iso/home/standards/iso8601.htm)
Common Alerting Protocol Version 1.2 (http://docs.oasisopen.org/emergency/cap/v1.2/CAP-v1.2-os.pdf)
Report to the Maritime Safety Committee and the Marine Environment
Protection Committee. Annex 1 Draft FAL.2-MEPC.1-MSC.1 Circular on
List of Certificates and Documents Required to be Carried on Board
Ships.
ISA Core Vocabularies Specification
(https://joinup.ec.europa.eu/catalogue/distribution/core_vocabularieslocation_v100_specification_pdf)
Events Catalogue and some aspects of the visualization policy in the
Events Layer of EUROSUR network
Recommendation N°. 21 - Codes for Passengers, Types of Cargo,
Packages and Packaging Materials (with Complementary Codes for
Package Names) Annex IV (http://www.unece.org/tradewelcome/areasof-work/un-centre-for-trade-facilitation-and-e-businessuncefact/outputs/cefactrecommendationsrec-index/list-of-tradefacilitation-recommendations-n-21-to-24.html
http://www.unece.org/fileadmin/DAM/cefact/recommendations/rec21/
rec21rev2_rev_96trd211.pdf)
The Dublin Core Metadata Element Set
(http://www.niso.org/apps/group_public/download.php/6576/The%20
Dublin%20Core%20Metadata%20Element%20Set.pdf)
Date Version
28 Oct
2004 14 Jun
2011 Edition 1
01 Jul
2010 1.2
07 Mar
2013 -
11 May
2012 1.00
21 May
2012 2.0
1996 ECE/TRA
DE/211
-
Electronic Notice of Arrival/Departure (e-NOA/D)
(http://www.mxak.org/regulations/pdfs/enoagde.pdf)
07 Aug
2008 -
Piracy and Armed Robbery against Ships. Recommendations to
Governments for preventing and suppressing piracy and armed robbery
against ships
(http://www.imo.org/OurWork/Security/PiracyArmedRobbery/Guidanc
e/Documents/MSC.1-Circ.1333.pdf)
International Ship and Port Facility Security Code (ISPS Code)
(http://www.imo.org/ourwork/security/instruments/pages/ispscode.asp
x)
UN/LOCODE Code List by Country
(http://www.unece.org/cefact/locode/service/location.html)
26 Jun
2009 -
-
-
Page 175 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Reference
Author
ISO 31661
ISO
IETF RFC
6350
IETF RFC
2046
ISO
15836:20
09
IETF RFC
6351
CWA
159312:2009
IETF
SSN IRG
IETF
Codes for the representation of names of countries and their
subdivisions – Part 1: Country codes
(http://www.iso.org/iso/home/standards/country_codes.htm)
vCard Format Specification (https://tools.ietf.org/html/rfc6350)
-
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
(https://www.ietf.org/rfc/rfc2046.txt)
Information and documentation -- The Dublin Core metadata element
set (http://www.iso.org/iso/catalogue_detail.htm?csnumber=52142)
-
IETF
xCard: vCard XML Representation (https://tools.ietf.org/html/rfc6351)
-
Europea
n
Committ
ee for
Standard
ization
EMSA
Disaster and emergency management - Shared situation awareness Part 2: Codes for the message structure
(http://standards.cen.eu/dyn/www/f?p=204:110:0::::FSP_PROJECT:3267
7&cs=17A5CA3C1AC669C16019C1B19DE7EA570 https://www.oasisopen.org/committees/download.php/42412/CWA_15931-2.pdf)
11 Feb
2009 -
SafeSeaNet Incident Report Guidelines
(http://www.emsa.europa.eu/documents/technicaldocumentation/224-ssn-documentation/1137-ssn-incident-reportguidelines-v191.html)
A Universally Unique IDentifier (UUID) URN Namespace
(https://www.ietf.org/rfc/rfc4122.txt)
The Dublin Core Metadata Element Set
(https://tools.ietf.org/html/rfc5013)
SafeSeaNet XML Messaging Reference Guide v2.07
(http://www.emsa.europa.eu/documents/technicaldocumentation/224-ssn-documentation/1142-ssn-xml-message-guidedraft-v207.html)
Recommendation N°. 21 - Codes for Passengers, Types of Cargo,
Packages and Packaging Materials (with Complementary Codes for
Package Names) Annex II (http://www.unece.org/tradewelcome/areasof-work/un-centre-for-trade-facilitation-and-e-businessuncefact/outputs/cefactrecommendationsrec-index/list-of-tradefacilitation-recommendations-n-21-to-24.html
http://www.unece.org/fileadmin/DAM/cefact/recommendations/rec21/
rec21rev2_rev_96trd211.pdf)
eMS sub-group on data mapping and functionalities. Data Mapping
Report
18 Oct
2012 1.91
ISO
IETF RFC
4122
IETF RFC
5013
SSN MRG
IETF
UNECE
Recomme
ndation
21 annex II
UNECE
NSW
eMS
UNECE
Recomme
ndation
20
UNECE
UNECE
Recomme
ndation
21
UNECE
EUCISE2020
Date Version
-
Title
IETF
EMSA
Recommendation N°. 20 - Codes for Units of Measure Used in
International Trade (http://www.unece.org/tradewelcome/areas-ofwork/un-centre-for-trade-facilitation-and-e-businessuncefact/outputs/cefactrecommendationsrec-index/list-of-tradefacilitation-recommendations-n-16-to-20.html
http://www.unece.org/fileadmin/DAM/cefact/recommendations/rec20/
rec20.zip)
Recommendation N°. 21 - Codes for Passengers, Types of Cargo,
Packages and Packaging Materials (with Complementary Codes for
Package Names) (http://www.unece.org/tradewelcome/areas-ofwork/un-centre-for-trade-facilitation-and-e-business-
-
19 Dec
2012 2.07
1996 ECE/TRA
DE/211
15 Nov
2013 1.0
2012 -
2012 -
Page 176 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Reference
Author
UNDG
UNECE
UNECE
Recomme
ndation
21 annex I
UNECE
W3C
OOnt
W3C
EUCISE2020
Date Version
Title
uncefact/outputs/cefactrecommendationsrec-index/list-of-tradefacilitation-recommendations-n-21-to-24.html
http://www.unece.org/fileadmin/DAM/cefact/recommendations/rec21/
rec21.zip)
European Agreement concerning the International Carriage of
Dangerous Goods by Road. ADR applicable as from 1 January 2011
(http://www.unece.org/fileadmin/DAM/trans/danger/publi/adr/adr201
1/English/Part3.pdf
http://www.unece.org/trans/danger/publi/adr/adr2011/11contentse.ht
ml)
Recommendation N°. 21 - Codes for Passengers, Types of Cargo,
Packages and Packaging Materials (with Complementary Codes for
Package Names) Annex I (http://www.unece.org/tradewelcome/areasof-work/un-centre-for-trade-facilitation-and-e-businessuncefact/outputs/cefactrecommendationsrec-index/list-of-tradefacilitation-recommendations-n-21-to-24.html
http://www.unece.org/fileadmin/DAM/cefact/recommendations/rec21/
rec21rev2_rev_96trd211.pdf)
The Organization Ontology - W3C Candidate Recommendation
(http://www.w3.org/TR/2013/CR-vocab-org-20130625/)
2010 -
1996 ECE/TRA
DE/211
25 Jun
2013 -
Page 177 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
XML Schemas for the CISE Core Data Specifications
EUCISE2020
Page 178 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
1.
Document Metadata
Document title
Publisher
Modified
Version
Status
EUCISE2020
CISE XML Schemas
DG JRC
2015-11-06
Data Model V1.4
Final
Page 179 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
2.
Schemas
2.1. schema data/Movement.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:movement="http://www.cise.eu/datamodel/Entity/Movement/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Movement/" schemaLocation="Entity/Movement/MovementType
.xsd"/>
<xs:element name="Movement" type="movement:MovementType"/>
</xs:schema>
2.2. schema data/Cargo.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" eleme
ntFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Cargo/" schemaLocation="Entity/Cargo/CargoType.xsd"/>
<xs:element name="Cargo" type="cargo:CargoType"/>
</xs:schema>
2.3. schema data/Action.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:action="http://www.cise.eu/datamodel/Entity/Action/" ele
mentFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Action/" schemaLocation="Entity/Action/ActionType.xsd"/
>
<xs:element name="Action" type="action:ActionType"/>
</xs:schema>
2.4. schema data/VesselDocument.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="Entity/Document/VesselDocume
ntType.xsd"/>
<xs:element name="VesselDocument" type="document:VesselDocumentType"/>
</xs:schema>
2.5. schema data/OrganizationalCollaboration.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Organization/" schemaLocation="Entity/Organization/Orga
nizationalCollaborationType.xsd"/>
<xs:element name="OrganizationalCollaboration" type="organization:OrganizationalCollaborationType"/>
</xs:schema>
2.6. schema data/PortLocation.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="Entity/Location/PortLocation
Type.xsd"/>
<xs:element name="PortLocation" type="location:PortLocationType"/>
</xs:schema>
2.7. schema data/NamedLocation.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="Entity/Location/NamedLocatio
nType.xsd"/>
EUCISE2020
Page 180 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:element name="NamedLocation" type="location:NamedLocationType"/>
</xs:schema>
2.8. schema data/PollutionIncident.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Incident/" schemaLocation="Entity/Incident/PollutionInc
identType.xsd"/>
<xs:element name="PollutionIncident" type="incident:PollutionIncidentType"/>
</xs:schema>
2.9. schema data/Vessel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:51] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" ele
mentFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Vessel/" schemaLocation="Entity/Vessel/VesselType.xsd"/
>
<xs:element name="Vessel" type="vessel:VesselType"/>
</xs:schema>
2.10. schema data/CargoDocument.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="Entity/Document/CargoDocumen
tType.xsd"/>
<xs:element name="CargoDocument" type="document:CargoDocumentType"/>
</xs:schema>
2.11. schema data/LocationDocument.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="Entity/Document/LocationDocu
mentType.xsd"/>
<xs:element name="LocationDocument" type="document:LocationDocumentType"/>
</xs:schema>
2.12. schema data/Stream.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="Entity/Document/StreamType.x
sd"/>
<xs:element name="Stream" type="document:StreamType"/>
</xs:schema>
2.13. schema data/PortFacilityLocation.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="Entity/Location/PortFacility
LocationType.xsd"/>
<xs:element name="PortFacilityLocation" type="location:PortFacilityLocationType"/>
</xs:schema>
2.14. schema data/MaritimeSafetyIncident.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Incident/" schemaLocation="Entity/Incident/MaritimeSafe
EUCISE2020
Page 181 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
tyIncidentType.xsd"/>
<xs:element name="MaritimeSafetyIncident" type="incident:MaritimeSafetyIncidentType"/>
</xs:schema>
2.15. schema data/Entity/Period/Period.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:period="http://www.cise.eu/datamodel/Entity/Period/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Period/">
<xs:complexType name="Period">
<xs:annotation>
<xs:documentation>The class Period is used to define a time interval which can be expressed by:||&lt;ul&g
t;||
&lt;li&gt;only a duration (i.e. one month),&lt;/li&gt;||
&lt;li&gt;a duration and a start (resp. end) date
[ex.: a period of ten days starting (resp. ending) on December 10th, 2002], in this case the period is assumed to sta
rt (resp. end) on December 10&lt;sup&gt;th&lt;/sup&gt; at 0:00 (resp. 23:59).&lt;/li&gt;||
&lt;li&gt;a duration and
a start (resp. end) time [ex.: a period of ten days starting (resp. ending) at 10am],&lt;/li&gt;|| &lt;li&gt;a durati
on and start (resp. end) date and time (ex.: a period of ten days starting (resp. ending) on December 10th, 2002, 10a
m),&lt;/li&gt;|| &lt;li&gt;a start Date and an end Date (ex.: December 3rd, 2002 &amp;amp; January 24&lt;sup&gt;th&lt
;/sup&gt; 2010),&lt;/li&gt;||
&lt;li&gt;a start Time and an end Time (ex.: 9am and 10pm),&lt;/li&gt;||
&lt;li&gt
;a start date and start time following by an end date and end time (ex.: December 3&lt;sup&gt;rd&lt;/sup&gt;, 2002 at
10pm and January 24&lt;sup&gt;th&lt;/sup&gt;, 2010 at 9am).&lt;/li&gt;||&lt;/ul&gt;</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="Duration" type="xs:duration" minOccurs="0"/>
<xs:element name="EndDate" type="xs:date" minOccurs="0"/>
<xs:element name="EndTime" type="xs:time" minOccurs="0"/>
<xs:element name="StartDate" type="xs:date" minOccurs="0"/>
<xs:element name="StartTime" type="xs:time" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
2.16. schema data/Entity/Event/LocationRoleInEventEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Event/">
<xs:simpleType name="LocationRoleInEventEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible roles that a Location can have in relation to an
Event.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">start place. DESCRIPTION: The Location is the start place of the
Event</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">end place. DESCRIPTION: The Location is the end place of the Even
t</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">last place. DESCRIPTION: The Location is the last place known of
the Event</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">next place. DESCRIPTION: The Location is the next place of the Ev
ent</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other role not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
EUCISE2020
Page 182 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Role not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.17. schema data/Entity/Event/EventAreaEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Event/">
<xs:simpleType name="EventAreaEnumType">
<xs:annotation>
<xs:documentation>In order to define the possible types a Location can have when in relation to an Event;
we suggest reusing the work already done during the "tactical situation object" project. Among many artifacts, a list
of area type has been defined. During the scope of the Cooperation project, we chose to limit the enumeration list to
the first level defined by the tactical situation object project. Sub-levels are also defined and their adoption coul
d be considered in future developments of the data model (see "Disaster and emergency management - Shared situation a
wareness - Part 2: Codes for the message structure.").||--Source: ||CWA 15931-1:2009</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="AIR">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Aerial area</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CMB">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Combat-related area</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="DGR">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Polluted/dangerous area</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FLAME">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Area in combustion</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GEN">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: General purpose area</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PLUME">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Trails of hazardous emissions from an incident inf
luenced by\nthe wind and other weather conditions that are laden with\nparticulates and gaseous pollutants</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="SMOKE">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Cloud of fine particles resulting from a combustio
n suspended\nin a gas of hot vapour which potentially can impact on people</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="VULN">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Area where people will be at risk</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Other">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other role not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NonSpecified">
<xs:annotation>
EUCISE2020
Page 183 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Role not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.18. schema data/Entity/Event/ObjectRoleInEventEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Event/">
<xs:simpleType name="ObjectRoleInEventEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible roles that an Object can have in relation to an
Event</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">coordinator. DESCRIPTION: Coordinates the Event</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">participant. DESCRIPTION: Participates the Event</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">observer. DESCRIPTION: Observes the Event</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">cause. DESCRIPTION: Causes/has caused the Event</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">reporter. DESCRIPTION: Reports about the Event</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">victim. DESCRIPTION: Victim of the Event</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">mean. DESCRIPTION: A mean used during the Event</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other role not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Role not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.19. schema data/Entity/Event/EventRoleInEventEnumType.xsd
EUCISE2020
Page 184 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Event/">
<xs:simpleType name="EventRoleInEventEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the role an Event can have in respect to another Event.</xs:d
ocumentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">causes. DESCRIPTION: Event which is the cause of other Event(s)</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">responds. DESCRIPTION: Event which responds to other Event(s)</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">prevents. DESCRIPTION: Event which prevents other Event(s)</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">encompasses. DESCRIPTION: Event which encompasses the other Event
(s)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">requires. DESCRIPTION: Event which requires other Event(s)</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other role not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Role not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.20. schema data/Entity/Event/NatureEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Event/">
<xs:simpleType name="NatureEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the different natures of an Event.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">observed. DESCRIPTION: The Event is observed</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">declared. DESCRIPTION: The Event is declared</xs:documentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 185 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">estimated. DESCRIPTION: This Event is estimated</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">simulated. DESCRIPTION: The Event is simulated</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other type not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Type not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.21. schema data/Entity/Event/EventType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" xmlns
:entity="http://www.cise.eu/datamodel/Entity/" xmlns:metadata="http://www.cise.eu/datamodel/Entity/Metadata/" xmlns:p
eriod="http://www.cise.eu/datamodel/Entity/Period/" xmlns:uniqueidentifier="http://www.cise.eu/datamodel/Entity/Uniqu
eIdentifier/" targetNamespace="http://www.cise.eu/datamodel/Entity/Event/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Metadata/" schemaLocation="../Metadata/Metadata.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" schemaLocation="../UniqueIdentifier/
UniqueIdentifierType.xsd"/>
<xs:include schemaLocation="NatureEnumType.xsd"/>
<xs:complexType name="EventType" abstract="true">
<xs:annotation>
<xs:documentation>The Event is one of the core entities of the overall data model of the information shar
ing environment. It is an entity which holds information about movements, anomalies, incidents or actions which occur
in the maritime domain. Event can have relationships with other events, objects, agents, documents, periods and locat
ions. Event can also be related to risks in different roles. Event is an abstract entity which has four sub-entities:
Movement, Anomaly, Incident and Action.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Identifier" type="uniqueidentifier:UniqueIdentifierType" minOccurs="0"/>
<xs:element name="Metadata" type="metadata:Metadata" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="NatureType" type="event:NatureEnumType" minOccurs="0"/>
<xs:element name="OccurrencePeriod" type="period:Period" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.22. schema data/Entity/Event/AgentRoleInEventEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Event/">
<xs:simpleType name="AgentRoleInEventEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible roles that an Agent can have in relation to Even
t</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">coordinator. DESCRIPTION: Coordinates the Event</xs:documentation
EUCISE2020
Page 186 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">participant. DESCRIPTION: Participates the Event</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">observer. DESCRIPTION: Observes the Event</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">cause. DESCRIPTION: Causes/has caused the Event</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">reporter. DESCRIPTION: Reports about the Event</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">victim. DESCRIPTION: Victim of the Event</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">informed. DESCRIPTION: Is informed about the Event</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">perpetrator. DESCRIPTION: Is the perpetrator/actor of the Event</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other role not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Role not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.23. schema data/Entity/Action/MissionEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:action="http://www.cise.eu/datamodel/Entity/Action/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Action/">
<xs:simpleType name="MissionEnumType">
<xs:annotation>
<xs:documentation>In order to define the type of mission associated to an action. We suggest reusing the
work already done during the "tactical situation object" project. Among many artifacts, a list of mission type has be
en defined.||During the scope of the Cooperation project, we chose to limit the enumeration list to the first level d
efined by the tactical situation object project. Sub-levels are also defined and their adoption could be considered i
n future developments of the data model (see "Disaster and emergency management - Shared situation awareness - Part 2
: Codes for the message structure.").</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="C2">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Command &amp;amp; Control</xs:documentation>
EUCISE2020
Page 187 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CBRN">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Activities related to chemical, bacteriological, r
adioactive and nuclear substances</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FF">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Fire Fighting missions</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FSTT">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Fire Services Technical Intervention</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GEN">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Generic activities</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="INT">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Intelligence</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MAC">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Multi-agency Cooperation</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MIL">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Military activities</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NET">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Network and telecommunication activities</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="OPR">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Use Operational Resources</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="POL">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Police activities</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="REC">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Reconstruction/rehabilitation activities</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="RSC">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Rescue activities</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="SAV">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Save and Rescue Endangered Life</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="SCS">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Support Community Safety</xs:documentation>
</xs:annotation>
EUCISE2020
Page 188 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="SOC">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Social and media/communication activities</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Other">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Mission type not included above</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NonSpecified">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Mission type non-specified</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.24. schema data/Entity/Action/ActionPriorityEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:action="http://www.cise.eu/datamodel/Entity/Action/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Action/">
<xs:simpleType name="ActionPriorityEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the different priorities which can be assigned to an Action.<
/xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">high. DESCRIPTION: Used to identify a high priority Action</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">medium. DESCRIPTION: Used to identify a medium priority Action</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">low. DESCRIPTION: Used to identify a low priority Action</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Action status not included above</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Action status non-specified</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.25. schema data/Entity/Action/ActionType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:action="http://www.cise.eu/datamodel/Entity/Action/" xml
ns:event="http://www.cise.eu/datamodel/Entity/Event/" targetNamespace="http://www.cise.eu/datamodel/Entity/Action/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Event/EventType.xsd"/>
EUCISE2020
Page 189 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:include schemaLocation="ActionEnumType.xsd"/>
<xs:include schemaLocation="ActionStatusEnumType.xsd"/>
<xs:include schemaLocation="MissionEnumType.xsd"/>
<xs:include schemaLocation="ActionPriorityEnumType.xsd"/>
<xs:complexType name="ActionType">
<xs:annotation>
<xs:documentation>It is a subclass of Event. The Action entity may be linked to Incident, Anomaly and can
also be expressed taking into account other entities as location, object, etc.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="event:EventType">
<xs:sequence>
<xs:element name="ActionStatus" type="action:ActionStatusEnumType" minOccurs="0"/>
<xs:element name="ActionType" type="action:ActionEnumType" minOccurs="0"/>
<xs:element name="Mission" type="action:MissionEnumType" minOccurs="0"/>
<xs:element name="Priority" type="action:ActionPriorityEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.26. schema data/Entity/Action/ActionEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:action="http://www.cise.eu/datamodel/Entity/Action/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Action/">
<xs:simpleType name="ActionEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of Actions.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">inspection. DESCRIPTION: A inspection action as defined in the EU
ROSUR system</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">confirmation. DESCRIPTION: A confirmation action</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">rescue. DESCRIPTION: A rescue action as defined in the EUROSUR sy
stem</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">deterrence. DESCRIPTION: An action intended to dissuade an advers
ary from undertaking an action not yet started</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">assistance. DESCRIPTION: An assistance action.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">acknowledgment. DESCRIPTION: An action resulting in an acknowledg
ement</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">exercise. DESCRIPTION: An action defined as an exercise</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
EUCISE2020
Page 190 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">search. DESCRIPTION: A search action.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">detection. DESCRIPTION: A detection action</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">tracking. DESCRIPTION: A tracking action</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">interception. DESCRIPTION: An interception action</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Action type not included above</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Action type non-specified</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.27. schema data/Entity/Action/ActionStatusEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:action="http://www.cise.eu/datamodel/Entity/Action/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Action/">
<xs:simpleType name="ActionStatusEnumType">
<xs:annotation>
<xs:documentation>In order to define the statuses associated to an action, we suggest reusing the work al
ready done during the "Tactical Situation Object" project. Among many artifacts, a list of action statuses has been d
efined. This enumeration presents the possible statuses of an Action.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">aborted. DESCRIPTION: Action aborted</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">cancelled. DESCRIPTION: Action canceled</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">completed. DESCRIPTION: Action completed</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">in progress. DESCRIPTION: Action InProgress (2 additional digits
- such as IPR50 - may provide the percentage of completeness of the action)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">not started. DESCRIPTION: Action is not started</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
EUCISE2020
Page 191 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">paused. DESCRIPTION: Action is paused</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Action status not included above</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Action status non-specified</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.28. schema data/Entity/Cargo/PackageEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:simpleType name="PackageEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of package used in CargoUnit.</xs:document
ation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="0">
<xs:annotation>
<xs:documentation xml:lang="en">bulk. DESCRIPTION: bulk</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="1">
<xs:annotation>
<xs:documentation xml:lang="en">loosed unpacked excluding bulk. DESCRIPTION: loosed unpacked excl
uding bulk</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="2">
<xs:annotation>
<xs:documentation xml:lang="en">rigid box type prismatic. DESCRIPTION: rigid box type prismatic</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="3">
<xs:annotation>
<xs:documentation xml:lang="en">rigid drum type cylindrical. DESCRIPTION: rigid drum type cylindr
ical</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="4">
<xs:annotation>
<xs:documentation xml:lang="en">rigid bulb type spherical. DESCRIPTION: rigid bulb type spherical
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="5">
<xs:annotation>
<xs:documentation xml:lang="en">rigid other. DESCRIPTION: rigid other</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="6">
<xs:annotation>
<xs:documentation xml:lang="en">flexible bag type. DESCRIPTION: flexible bag type</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="7">
<xs:annotation>
<xs:documentation xml:lang="en">for future use. DESCRIPTION: for future use</xs:documentation>
</xs:annotation>
EUCISE2020
Page 192 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="8">
<xs:annotation>
<xs:documentation xml:lang="en">reserved. DESCRIPTION: reserved</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="9">
<xs:annotation>
<xs:documentation xml:lang="en">other special packages. DESCRIPTION: other special packages</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other package type not mentioned above</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Package type not specified</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.29. schema data/Entity/Cargo/CommunityStatusEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:simpleType name="CommunityStatusEnumType">
<xs:annotation>
<xs:documentation>This enumeration reflects the different customs status of cargo units on board a ship.<
/xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="C">
<xs:annotation>
<xs:documentation xml:lang="en">community goods. DESCRIPTION: (equivalent to 'T2L') for goods who
se community status can be demonstrated</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="F">
<xs:annotation>
<xs:documentation xml:lang="en">comunity goods from non-fiscal territories. DESCRIPTION: (equival
ent to 'T2LF') for goods whose community status can be demonstrated, consigned to or originating in a part of the Com
munity customs territory where the provisions of Directive 77/388/EEC do not apply</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="X">
<xs:annotation>
<xs:documentation xml:lang="en">community goods being exported. DESCRIPTION: For goods under the
export procedure</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="N">
<xs:annotation>
<xs:documentation xml:lang="en">other goods. DESCRIPTION: For all other goods</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NonSpecified">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.30. schema data/Entity/Cargo/CargoEnumType.xsd
EUCISE2020
Page 193 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:simpleType name="CargoEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of cargo.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="0">
<xs:annotation>
<xs:documentation xml:lang="en">no cargo unit liquid bulk goods. DESCRIPTION: includes i) liquids
ii) liquified gases iii) molten or slurried solids, suitable for continuous mechanical handling for transport by pipe
line or loose in a hold, tank or other compartment integral to a means of transport</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="1">
<xs:annotation>
<xs:documentation xml:lang="en">no cargo unit solid bulk goods. DESCRIPTION: includes i) fine pow
ders ii) granular particles iii) large, lumpy, dry solids, suitable for continuous mechanical handling, for transport
by fixed installations (other than pipeline) or loose in a hold or other compartment integral to a means of transport
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="2">
<xs:annotation>
<xs:documentation xml:lang="en">large freight containers. DESCRIPTION: Goods loaded in/on a freig
ht container 20ft. (6m) or more in external length; includes lift van, swap/swop body, flat, moveable tank or similar
articles of transport equipment</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="3">
<xs:annotation>
<xs:documentation xml:lang="en">other freight containers. DESCRIPTION: Goods loaded in/on a freig
ht container less than 20 ft.(6m) in external length; includes i) rigid Intermediate Bulk Containers (IBCs) ii) aircr
aft Unit Load Devices (ULDs); excludes i) air mode pallets ii) sea or land mode box-, tank-, post, rack-pallets not e
xceeding 1.25 m2 deck area</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="4">
<xs:annotation>
<xs:documentation xml:lang="en">palletized. DESCRIPTION: Goods loaded on a deck; includes i) disp
osable one-way pallets ii) sea or land mode box-, tank-, post-, rack-pallets not exceeding 1.25 m2 deck area iii) sli
p-sheets iv) air mode pallets v) bricks, ingots, etc. suitably assembled for fork-lift truck handling</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="5">
<xs:annotation>
<xs:documentation xml:lang="en">pre slung. DESCRIPTION: Goods (one or more items) supplied with a
sling (or slings) or various materials (natural/artificial fibre, steel wire, etc.) and of various designs (loop, rin
g, cloverleaf, etc.); includes i) “packaged” timber ii) Flexible Intermediate Bulk Containers (FIBCs)</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="6">
<xs:annotation>
<xs:documentation xml:lang="en">mobile self-propelled units. DESCRIPTION: includes i) road motor
vehicles (lorries, buses, cars) and accompanying trailers, semi-trailers, caravans engaged in goods/passenger transpo
rt ii) motorised road, agricultural, industrial, etc. vehicles moving in trade iii) live animals “on the hoof”</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="7">
<xs:annotation>
<xs:documentation xml:lang="en">other mobile units. DESCRIPTION: non-self-propelled vehicles and
equipment on wheels; includes i) unaccompanied trailers, semi-trailers railwagons, ship-borne barges engaged in goods
transport ii) caravans and other road, agricultural, industrial, etc. vehicles iii) ship-borne port-to-port trailers<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="8">
<xs:annotation>
<xs:documentation xml:lang="en">reserved. DESCRIPTION: </xs:documentation>
</xs:annotation>
EUCISE2020
Page 194 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="9">
<xs:annotation>
<xs:documentation xml:lang="en">other cargo types. DESCRIPTION: all cargo not elsewhere enumerate
d (i.e. the residual types of cargo carried in transport: “break-bulk” or “general” cargo, e.g. boxes, drums, bags, e
tc. and loose, unpacked items such as pipes, rods, etc.)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.31. schema data/Entity/Cargo/WeightMeansEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:simpleType name="WeightMeansEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the different means of weight for fisheries</xs:documentation
>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="EST">
<xs:annotation>
<xs:documentation xml:lang="en">Estimation. DESCRIPTION: Estimation </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="WGH">
<xs:annotation>
<xs:documentation xml:lang="en">weighing on board. DESCRIPTION: weighing on board</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.32. schema data/Entity/Cargo/PackingGroupCodeEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:simpleType name="PackingGroupCodeEnumType">
<xs:annotation>
<xs:documentation>This enumeration defines the danger code, according to the level of danger from the IMD
G (International Maritime Dangerous Goods).</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="I">
<xs:annotation>
<xs:documentation xml:lang="en">Group I: great danger. DESCRIPTION: Great danger</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="II">
<xs:annotation>
<xs:documentation xml:lang="en">Group II: medium danger. DESCRIPTION: Medium danger</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="III">
<xs:annotation>
<xs:documentation xml:lang="en">Group III: minor danger. DESCRIPTION: Minor danger</xs:documentat
EUCISE2020
Page 195 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="None">
<xs:annotation>
<xs:documentation xml:lang="en">None. DESCRIPTION: No danger</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other code not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Code not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.33. schema data/Entity/Cargo/CatchType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" xmlns
:uniqueidentifier="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" targetNamespace="http://www.cise.eu/datamod
el/Entity/Cargo/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" schemaLocation="../UniqueIdentifier/
UniqueIdentifierType.xsd"/>
<xs:include schemaLocation="CargoUnitType.xsd"/>
<xs:include schemaLocation="SpeciesEnumType.xsd"/>
<xs:include schemaLocation="WeightMeansEnumType.xsd"/>
<xs:complexType name="CatchType">
<xs:annotation>
<xs:documentation>A Catch refers to a set of distinct species catch in the see/ocean by a fishing vessel.
Catch has the same associations and relationships than its parent-class Object. Thus it can have relationship with Do
cument, Risk, Event, Location, and Agent.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="cargo:CargoUnitType">
<xs:sequence>
<xs:element name="CatchWeight" type="xs:double" minOccurs="0"/>
<xs:element name="FishNumber" type="xs:int" minOccurs="0"/>
<xs:element name="NetHeld" type="xs:double" minOccurs="0"/>
<xs:element name="QuantityHeld" type="xs:double" minOccurs="0"/>
<xs:element name="SizeDeclaration" type="xs:double" minOccurs="0"/>
<xs:element name="Species" type="cargo:SpeciesEnumType" minOccurs="0"/>
<xs:element name="TotalNumber" type="xs:int" minOccurs="0"/>
<xs:element name="TotalWeight" type="xs:double" minOccurs="0"/>
<xs:element name="UniqueIdentifier" type="uniqueidentifier:UniqueIdentifierType" minOccurs="0"/>
<xs:element name="WeightMeans" type="cargo:WeightMeansEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.34. schema data/Entity/Cargo/DangerousSubstancesEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:simpleType name="DangerousSubstancesEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the general categories of Hazardous cargo, according to the I
nternational Maritime Dangerous Goods (IMDG) code. For additional information about IBC, IGC and INF (IBC - Intermedi
ate Bulk Container, IGC - International Gas Carrier and INF - Irradiated Nuclear Fuel) contact the International Mari
time Organization (IMO).</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="Class1">
<xs:annotation>
EUCISE2020
Page 196 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">class 1 explosives. DESCRIPTION: Should be stored away from the c
rew’s quarters and the ship’s boats and immediately under the hold’s hatches</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class21">
<xs:annotation>
<xs:documentation xml:lang="en">class 2.1 flammable gases. DESCRIPTION: Should be stored away fro
m crew’s quarters and any source of heat.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class22">
<xs:annotation>
<xs:documentation xml:lang="en">class 2.2 toxic gases. DESCRIPTION: Should be stored away from an
y source of heat, the crew’s quarters and foodstuffs.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class23">
<xs:annotation>
<xs:documentation xml:lang="en">class 2.3 non-flammable compressed gases. DESCRIPTION: Store on o
r under the deck in a cool, well-ventilated place. Containers filled with this kind of gas will expand if heated and
there is a high risk of an explosion.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class31">
<xs:annotation>
<xs:documentation xml:lang="en">class 3.1 petrol. DESCRIPTION: Combustion at less than 18ºC. Shou
ld always be stored above the deck.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class32">
<xs:annotation>
<xs:documentation xml:lang="en">class 3.2 fuel oil. DESCRIPTION: Combustion at between 18ºC and 2
3ºC. Should be stored above or below the deck.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class33">
<xs:annotation>
<xs:documentation xml:lang="en">class 3.3 fuel oil. DESCRIPTION: Combustion at between 23ºC and 6
1ºC. Should be stored below the deck.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class41">
<xs:annotation>
<xs:documentation xml:lang="en">class 4.1 flammable solid. DESCRIPTION: Should be stored on top o
r below the deck. Should be kept away from living quarters.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class42">
<xs:annotation>
<xs:documentation xml:lang="en">class 4.2 spontaneously combustible. DESCRIPTION: Should be store
d in well ventilated areas and air should be able to circulate between the stored materials.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class43">
<xs:annotation>
<xs:documentation xml:lang="en">class 4.3 dangerous when wet. DESCRIPTION: Solids which are infla
mmable when wet or when in contact with water. Should be stored in well ventilated, dry areas and always away from an
y contact with water.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class51">
<xs:annotation>
<xs:documentation xml:lang="en">class 5.1 oxidizing agent. DESCRIPTION: The substances in this ca
tegory can create an inflammable environment when brought into contact with oxygen. For this reason they should not b
e stored next to combustible materials.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class52">
<xs:annotation>
<xs:documentation xml:lang="en">class 5.2 organix peroxide. DESCRIPTION: The substances in this c
lass can be inflammable or explosive. They should be stored above deck, covered and in a dry, cool areas.</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class61">
EUCISE2020
Page 197 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">class 6.1 toxic substances. DESCRIPTION: Toxic substances are tho
se which can enter the human body through the mouth and cause death. For this reasons they should be stored away from
foodstuffs, drinks, living quarters and materials which increase humidity, such as tobacco.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class62">
<xs:annotation>
<xs:documentation xml:lang="en">class 6.2 infectious biological substances. DESCRIPTION: These su
bstances contain microbes which can cause illness. They should be stored away from foodstuffs, drinks and living quar
ters. In case of danger the nearest health authority should be notified.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class7">
<xs:annotation>
<xs:documentation xml:lang="en">class 7 radioactive materials. DESCRIPTION: Radioactive Materials
- These materials should be transported in specially sealed containers. The seals must always be completely undamaged
. They should preferably be stored above deck and away from living quarters, foodstuffs, unprocessed films, pharmaceu
ticals and chemical substances. They are divided into three groups according to their level of radioactivity.</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class8">
<xs:annotation>
<xs:documentation xml:lang="en">class 8 corrosives. DESCRIPTION: The substances in this class are
solids or liquids possessing, in their original state, the common property of being able, more or less severely to da
mage living tissue. The escape of such a substance from its packaging may also cause damage to other cargo or the shi
p.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Class9">
<xs:annotation>
<xs:documentation xml:lang="en">class 9 miscellaneous dangerous substances. DESCRIPTION: Substanc
es and articles not covered by other classes which experience has shown, or may show, to be of such a dangerous chara
cter that the provisions of SOLAS should apply. These include substances that are transported or offered for transpor
t at temperatures equal to or exceeding 1000 C and in a liquid state, and solids that are transported at temperatures
equal or exceeding 2400 C;</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MHB">
<xs:annotation>
<xs:documentation xml:lang="en">MHB materials hazardous only in bulk. DESCRIPTION: MHB (materials
hazardous only in bulk) cargoes are materials which possess chemical hazards when transported in bulk that do not mee
t the criteria for inclusion in the IMDG classes. They are Combustible solids, Self-heating solids, Solids that evolv
e into flammable gas when wet, Solids that evolve toxic gas when wet, Toxic solids, Corrosive solids. See also IMSBC
code.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Other">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other dangerous substance type not mentio
ned above</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NonSpecified">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Type not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.35. schema data/Entity/Cargo/ContainmentUnitType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" xmlns
:uniqueidentifier="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" targetNamespace="http://www.cise.eu/datamod
el/Entity/Cargo/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" schemaLocation="../UniqueIdentifier/
UniqueIdentifierType.xsd"/>
<xs:include schemaLocation="CargoUnitType.xsd"/>
<xs:include schemaLocation="PackageEnumType.xsd"/>
<xs:include schemaLocation="UnitsOfMeasureEnumType.xsd"/>
<xs:include schemaLocation="PackagingMaterialEnumType.xsd"/>
EUCISE2020
Page 198 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:include schemaLocation="DangerousSubstancesEnumType.xsd"/>
<xs:include schemaLocation="UNDGEnumType.xsd"/>
<xs:include schemaLocation="PollutionCodeEnumType.xsd"/>
<xs:include schemaLocation="PackingGroupCodeEnumType.xsd"/>
<xs:include schemaLocation="CommunityStatusEnumType.xsd"/>
<xs:complexType name="ContainmentUnitType">
<xs:annotation>
<xs:documentation>Containment unit is an entity which holds information about units of goods when transpo
rted by ships contained in containers or bulk.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="cargo:CargoUnitType">
<xs:sequence>
<xs:element name="CommunityStatusOfGoods" type="cargo:CommunityStatusEnumType" minOccurs="0"/>
<xs:element name="ContainerMarksAndNumber" type="xs:string" minOccurs="0"/>
<xs:element name="DangerousSubstancesCode" type="cargo:DangerousSubstancesEnumType" minOccurs="0"
/>
<xs:element name="FlashPoint" type="xs:double" minOccurs="0"/>
<xs:element name="GrossQuantity" type="xs:double" minOccurs="0"/>
<xs:element name="LocationOnBoardContainer" type="xs:string" minOccurs="0"/>
<xs:element name="LocationOnBoardGoods" type="xs:string" minOccurs="0"/>
<xs:element name="NetQuantity" type="xs:double" minOccurs="0"/>
<xs:element name="OtherMarksAndNumber" type="xs:string" minOccurs="0"/>
<xs:element name="PackageType" type="cargo:PackageEnumType" minOccurs="0"/>
<xs:element name="PackagingMaterial" type="cargo:PackagingMaterialEnumType" minOccurs="0"/>
<xs:element name="PackingGroupCode" type="cargo:PackingGroupCodeEnumType" minOccurs="0"/>
<xs:element name="PollutionCode" type="cargo:PollutionCodeEnumType" minOccurs="0"/>
<xs:element name="UNDG" type="cargo:UNDGEnumType" minOccurs="0"/>
<xs:element name="UniqueIdentifier" type="uniqueidentifier:UniqueIdentifierType" minOccurs="0"/>
<xs:element name="UnitsOfMeasure" type="cargo:UnitsOfMeasureEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.36. schema data/Entity/Cargo/CargoUnitType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" xmlns
:object="http://www.cise.eu/datamodel/Entity/Object/" targetNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Object/ObjectType.xsd"/>
<xs:complexType name="CargoUnitType" abstract="true">
<xs:annotation>
<xs:documentation>CargoUnit is an entity which holds information about units of goods when transported by
ships. The subclasses of CargoUnit can represent either the whole cargo in a vehicle or a part of it.</xs:documentati
on>
</xs:annotation>
<xs:complexContent>
<xs:extension base="object:ObjectType">
<xs:sequence>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.37. schema data/Entity/Cargo/UnitsOfMeasureEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:simpleType name="UnitsOfMeasureEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the considered units of measure for CargoUnits, according to
the United Nations codes for units of measure used in international trade.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="KGM">
<xs:annotation>
<xs:documentation xml:lang="en">kilogram. DESCRIPTION: kilogram</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="TNE">
EUCISE2020
Page 199 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">Metric tonne. DESCRIPTION: Metric tonne</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Other">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other unit not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Unit not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.38. schema data/Entity/Cargo/SpeciesEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:simpleType name="SpeciesEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of species.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="AAA">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser naccarii. DESCRIPTION: Adriatic sturgeon</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAB">
<xs:annotation>
<xs:documentation xml:lang="en">Acanthopagrus bifasciatus. DESCRIPTION: Twobar seabream</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAC">
<xs:annotation>
<xs:documentation xml:lang="en">Amia calva. DESCRIPTION: Bowfin</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAD">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser dabryanus. DESCRIPTION: Yangtze sturgeon</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAE">
<xs:annotation>
<xs:documentation xml:lang="en">Antennarius analis. DESCRIPTION: Tailjet frogfish</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAF">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser fulvescens. DESCRIPTION: Lake sturgeon</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAG">
<xs:annotation>
<xs:documentation xml:lang="en">Anguilla bengalensis. DESCRIPTION: Indian mottled eel</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAH">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser schrenckii. DESCRIPTION: Amur sturgeon</xs:documentatio
n>
</xs:annotation>
EUCISE2020
Page 200 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="AAI">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser sinensis. DESCRIPTION: Chinese sturgeon</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAJ">
<xs:annotation>
<xs:documentation xml:lang="en">Anguilla mossambica. DESCRIPTION: African longfin eel</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAK">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser mikadoi. DESCRIPTION: Sakhalin sturgeon</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAL">
<xs:annotation>
<xs:documentation xml:lang="en">Anguilla marmorata. DESCRIPTION: Giant mottled eel</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAM">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser medirostris. DESCRIPTION: Green sturgeon</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAN">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser nudiventris. DESCRIPTION: Fringebarbel sturgeon</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAO">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser oxyrinchus. DESCRIPTION: Atlantic sturgeon</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAP">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser persicus. DESCRIPTION: Persian sturgeon</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAQ">
<xs:annotation>
<xs:documentation xml:lang="en">Anguilla dieffenbachii. DESCRIPTION: New Zealand longfin eel</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAR">
<xs:annotation>
<xs:documentation xml:lang="en">Anguilla reinhardtii. DESCRIPTION: Speckled longfin eel</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAS">
<xs:annotation>
<xs:documentation xml:lang="en">Astacus astacus. DESCRIPTION: Noble crayfish</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAT">
<xs:annotation>
<xs:documentation xml:lang="en">Anguilla bicolor. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAU">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser multiscutatus. DESCRIPTION: Japanese sturgeon</xs:docum
entation>
EUCISE2020
Page 201 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAV">
<xs:annotation>
<xs:documentation xml:lang="en">Acaronia vultuosa. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAW">
<xs:annotation>
<xs:documentation xml:lang="en">Anableps anableps. DESCRIPTION: Largescale foureyes</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAX">
<xs:annotation>
<xs:documentation xml:lang="en">Aaptosyax grypus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAY">
<xs:annotation>
<xs:documentation xml:lang="en">Acipenser brevirostrum. DESCRIPTION: Shortnose sturgeon</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AAZ">
<xs:annotation>
<xs:documentation xml:lang="en">Aploactis aspera. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABA">
<xs:annotation>
<xs:documentation xml:lang="en">Albulichthys albuloides. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABB">
<xs:annotation>
<xs:documentation xml:lang="en">Abbottina rivularis. DESCRIPTION: Chinese false gudgeon</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABC">
<xs:annotation>
<xs:documentation xml:lang="en">Amblypharyngodon microlepis. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABD">
<xs:annotation>
<xs:documentation xml:lang="en">Alburnus albidus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABE">
<xs:annotation>
<xs:documentation xml:lang="en">Aborichthys elongatus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABF">
<xs:annotation>
<xs:documentation xml:lang="en">Haliotis rufescens. DESCRIPTION: Red abalone</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABG">
<xs:annotation>
<xs:documentation xml:lang="en">Haliotis gigantea. DESCRIPTION: Giant abalone</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABH">
<xs:annotation>
<xs:documentation xml:lang="en">Astroblepus chotae. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABI">
<xs:annotation>
<xs:documentation xml:lang="en">Alburnoides bipunctatus. DESCRIPTION: Schneider</xs:documentation
>
</xs:annotation>
EUCISE2020
Page 202 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="ABJ">
<xs:annotation>
<xs:documentation xml:lang="en">Haliotis discus. DESCRIPTION: Japanese abalone</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABK">
<xs:annotation>
<xs:documentation xml:lang="en">Blicca bjoerkna. DESCRIPTION: White bream</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABL">
<xs:annotation>
<xs:documentation xml:lang="en">Amblypharyngodon melettinus. DESCRIPTION: Attentive carplet</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABM">
<xs:annotation>
<xs:documentation xml:lang="en">Haliotis diversicolor. DESCRIPTION: Small abalone</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABN">
<xs:annotation>
<xs:documentation xml:lang="en">Acanthobunocephalus nicoi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABO">
<xs:annotation>
<xs:documentation xml:lang="en">Amblypharyngodon mola. DESCRIPTION: Mola carplet</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABP">
<xs:annotation>
<xs:documentation xml:lang="en">Haliotis midae. DESCRIPTION: Perlemoen abalone</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABQ">
<xs:annotation>
<xs:documentation xml:lang="en">Abramites eques. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABR">
<xs:annotation>
<xs:documentation xml:lang="en">Haliotis rubra. DESCRIPTION: Blacklip abalone</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABS">
<xs:annotation>
<xs:documentation xml:lang="en">Penaeus aztecus. DESCRIPTION: Northern brown shrimp</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABT">
<xs:annotation>
<xs:documentation xml:lang="en">Amblyrhynchichthys truncatus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABU">
<xs:annotation>
<xs:documentation xml:lang="en">Abudefduf saxatilis. DESCRIPTION: Sergeant-major</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABV">
<xs:annotation>
<xs:documentation xml:lang="en">Alabes parvulus. DESCRIPTION: Pygmy shore-eel</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABW">
<xs:annotation>
<xs:documentation xml:lang="en">Ablabys binotatus. DESCRIPTION: Redskinfish</xs:documentation>
</xs:annotation>
EUCISE2020
Page 203 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="ABX">
<xs:annotation>
<xs:documentation xml:lang="en">Haliotis spp. DESCRIPTION: Abalones nei</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABY">
<xs:annotation>
<xs:documentation xml:lang="en">Amblyopsis rosae. DESCRIPTION: Ozark cavefish</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ABZ">
<xs:annotation>
<xs:documentation xml:lang="en">Ammodytes tobianus. DESCRIPTION: Small sandeel</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACA">
<xs:annotation>
<xs:documentation xml:lang="en">Acromycter nezumi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACB">
<xs:annotation>
<xs:documentation xml:lang="en">Scapharca broughtonii. DESCRIPTION: Inflated ark</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACC">
<xs:annotation>
<xs:documentation xml:lang="en">Gymnocephalus cernuus. DESCRIPTION: Ruffe</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACD">
<xs:annotation>
<xs:documentation xml:lang="en">Chlopsis dentatus. DESCRIPTION: Mottled false moray</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACE">
<xs:annotation>
<xs:documentation xml:lang="en">Paruroconger drachi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACF">
<xs:annotation>
<xs:documentation xml:lang="en">Acestrorhynchus falcatus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACG">
<xs:annotation>
<xs:documentation xml:lang="en">Acanthogobius ommaturus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACH">
<xs:annotation>
<xs:documentation xml:lang="en">Salvelinus alpinus. DESCRIPTION: Arctic char</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACI">
<xs:annotation>
<xs:documentation xml:lang="en">Acnodon normani. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACJ">
<xs:annotation>
<xs:documentation xml:lang="en">Japonoconger africanus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACK">
<xs:annotation>
<xs:documentation xml:lang="en">Kaupichthys hyoproroides. DESCRIPTION: False moray</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACL">
EUCISE2020
Page 204 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">Heteroconger longissimus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACM">
<xs:annotation>
<xs:documentation xml:lang="en">Macrocephenchelys brachialis. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACN">
<xs:annotation>
<xs:documentation xml:lang="en">Aculeola nigra. DESCRIPTION: Hooktooth dogfish</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACO">
<xs:annotation>
<xs:documentation xml:lang="en">Coloconger raniceps. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACP">
<xs:annotation>
<xs:documentation xml:lang="en">Chilorhinus platyrhynchus. DESCRIPTION: Flatnose xenocongrid eel<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACQ">
<xs:annotation>
<xs:documentation xml:lang="en">Astrocottus leprops. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACR">
<xs:annotation>
<xs:documentation xml:lang="en">Acropomatidae. DESCRIPTION: Glow-bellies, splitfins nei</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACS">
<xs:annotation>
<xs:documentation xml:lang="en">Heteroconger hassi. DESCRIPTION: Spotted garden-eel</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACT">
<xs:annotation>
<xs:documentation xml:lang="en">Paraconger caudilimbatus. DESCRIPTION: Margintail conger</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACU">
<xs:annotation>
<xs:documentation xml:lang="en">Lumiconger arafura. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACV">
<xs:annotation>
<xs:documentation xml:lang="en">Acanthocepola abbreviata. DESCRIPTION: Bandfish</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACW">
<xs:annotation>
<xs:documentation xml:lang="en">Amblycirrhitus earnshawi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACX">
<xs:annotation>
<xs:documentation xml:lang="en">Acanthaxius caespitosa. DESCRIPTION: Deep-water mud lobster</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ACY">
<xs:annotation>
<xs:documentation xml:lang="en">Parabathymyrus macrophthalmus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 205 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="ACZ">
<xs:annotation>
<xs:documentation xml:lang="en">Cambaridae. DESCRIPTION: American crayfishes nei</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADA">
<xs:annotation>
<xs:documentation xml:lang="en">Aspidoras albater. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADB">
<xs:annotation>
<xs:documentation xml:lang="en">Adontosternarchus balaenops. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADC">
<xs:annotation>
<xs:documentation xml:lang="en">Acrochordonichthys chamaeleon. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADD">
<xs:annotation>
<xs:documentation xml:lang="en">Derichthys serpentinus. DESCRIPTION: Narrownecked oceanic eel</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADE">
<xs:annotation>
<xs:documentation xml:lang="en">Allotoca dugesii. DESCRIPTION: Opal allotoca</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADF">
<xs:annotation>
<xs:documentation xml:lang="en">Aspredinichthys filamentosus. DESCRIPTION: Sevenbarbed banjo</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADG">
<xs:annotation>
<xs:documentation xml:lang="en">Anadoras grypus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADH">
<xs:annotation>
<xs:documentation xml:lang="en">Amblyglyphidodon aureus. DESCRIPTION: Golden damselfish</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADI">
<xs:annotation>
<xs:documentation xml:lang="en">Aplocheilus dayi. DESCRIPTION: Ceylon killifish</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADJ">
<xs:annotation>
<xs:documentation xml:lang="en">Pardachirus pavoninus. DESCRIPTION: Peacock sole</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADK">
<xs:annotation>
<xs:documentation xml:lang="en">Artedidraco skottsbergi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADL">
<xs:annotation>
<xs:documentation xml:lang="en">Antipodocottus elegans. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADM">
<xs:annotation>
<xs:documentation xml:lang="en">Autanadoras milesi. DESCRIPTION: </xs:documentation>
</xs:annotation>
EUCISE2020
Page 206 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="ADN">
<xs:annotation>
<xs:documentation xml:lang="en">Nessorhamphus ingolfianus. DESCRIPTION: Duckbill oceanic eel</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADO">
<xs:annotation>
<xs:documentation xml:lang="en">Artediellus dydymovi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADP">
<xs:annotation>
<xs:documentation xml:lang="en">Austrofundulus dolichopterus. DESCRIPTION: Saberfin killie</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADQ">
<xs:annotation>
<xs:documentation xml:lang="en">Antipathes dichotoma. DESCRIPTION: Black coral</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADR">
<xs:annotation>
<xs:documentation xml:lang="en">Aspredo aspredo. DESCRIPTION: Banjo</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADS">
<xs:annotation>
<xs:documentation xml:lang="en">Arnoldichthys spilopterus. DESCRIPTION: Niger tetra</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADT">
<xs:annotation>
<xs:documentation xml:lang="en">Pardachirus marmoratus. DESCRIPTION: Finless sole</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADU">
<xs:annotation>
<xs:documentation xml:lang="en">Allodontichthys hubbsi. DESCRIPTION: Whitepatched splitfin</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADV">
<xs:annotation>
<xs:documentation xml:lang="en">Apuredoras rivasi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADW">
<xs:annotation>
<xs:documentation xml:lang="en">Artedius corallinus. DESCRIPTION: Coralline sculpin</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADX">
<xs:annotation>
<xs:documentation xml:lang="en">Adinia xenica. DESCRIPTION: Diamond killifish</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADY">
<xs:annotation>
<xs:documentation xml:lang="en">Aspredo cotylephorus. DESCRIPTION: Banded banjo</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ADZ">
<xs:annotation>
<xs:documentation xml:lang="en">Artedidraco glareobarbatus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEA">
<xs:annotation>
EUCISE2020
Page 207 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">Alestes lateralis. DESCRIPTION: Stripped robber</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEB">
<xs:annotation>
<xs:documentation xml:lang="en">Alestes baremoze. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEC">
<xs:annotation>
<xs:documentation xml:lang="en">Astronesthes cyclophotus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AED">
<xs:annotation>
<xs:documentation xml:lang="en">Alestes dentex. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEE">
<xs:annotation>
<xs:documentation xml:lang="en">Einara edentula. DESCRIPTION: Toothless smooth-head</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEF">
<xs:annotation>
<xs:documentation xml:lang="en">Apteronotus albifrons. DESCRIPTION: Black ghost</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEG">
<xs:annotation>
<xs:documentation xml:lang="en">Astronesthes gemmifer. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEH">
<xs:annotation>
<xs:documentation xml:lang="en">Alestopetersius brichardi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEI">
<xs:annotation>
<xs:documentation xml:lang="en">Auchenipterus nigripinnis. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEJ">
<xs:annotation>
<xs:documentation xml:lang="en">Astronesthes indicus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEK">
<xs:annotation>
<xs:documentation xml:lang="en">Herwigia kreffti. DESCRIPTION: Krefft's smooth-head</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEL">
<xs:annotation>
<xs:documentation xml:lang="en">Leptoderma lubricum. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEM">
<xs:annotation>
<xs:documentation xml:lang="en">Aethotaxis mitopteryx. DESCRIPTION: Longfin icedevil</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEN">
<xs:annotation>
<xs:documentation xml:lang="en">Ericara niger. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEO">
<xs:annotation>
EUCISE2020
Page 208 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">Astronesthes leucopogon. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEP">
<xs:annotation>
<xs:documentation xml:lang="en">Astronesthes neopogon. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AER">
<xs:annotation>
<xs:documentation xml:lang="en">Aequidens rivulatus. DESCRIPTION: Green terror</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AES">
<xs:annotation>
<xs:documentation xml:lang="en">Pandalus montagui. DESCRIPTION: Aesop shrimp</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AET">
<xs:annotation>
<xs:documentation xml:lang="en">Aetapcus maculatus. DESCRIPTION: Warty prowfish</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEU">
<xs:annotation>
<xs:documentation xml:lang="en">Auchenoceros punctatus. DESCRIPTION: Ahuru</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEV">
<xs:annotation>
<xs:documentation xml:lang="en">Asemichthys taylori. DESCRIPTION: Spinynose sculpin</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEW">
<xs:annotation>
<xs:documentation xml:lang="en">Atherinosoma wallacei. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEX">
<xs:annotation>
<xs:documentation xml:lang="en">Aethiomastacembelus sexdecimspinus. DESCRIPTION: </xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEY">
<xs:annotation>
<xs:documentation xml:lang="en">Apteronotus leptorhynchus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AEZ">
<xs:annotation>
<xs:documentation xml:lang="en">Abyssocottus elochini. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFA">
<xs:annotation>
<xs:documentation xml:lang="en">Forbesichthys agassizi. DESCRIPTION: Spring cavefish</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFB">
<xs:annotation>
<xs:documentation xml:lang="en">Aphyoplatys duboisi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFC">
<xs:annotation>
<xs:documentation xml:lang="en">Atherinopsis californiensis. DESCRIPTION: Jack silverside</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFD">
<xs:annotation>
EUCISE2020
Page 209 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">Aphanius dispar. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFE">
<xs:annotation>
<xs:documentation xml:lang="en">Aplocheilichthys fuelleborni. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFF">
<xs:annotation>
<xs:documentation xml:lang="en">Atherion africanus. DESCRIPTION: Pricklenose silverside</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFG">
<xs:annotation>
<xs:documentation xml:lang="en">Asthenomacrurus fragilis. DESCRIPTION: Fragile grenadier</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFH">
<xs:annotation>
<xs:documentation xml:lang="en">Aphyosemion ahli. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFI">
<xs:annotation>
<xs:documentation xml:lang="en">Conocara fiolenti. DESCRIPTION: Fiolenti's smooth-head</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFJ">
<xs:annotation>
<xs:documentation xml:lang="en">Aphanius iberus. DESCRIPTION: Spanish toothcarp</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFK">
<xs:annotation>
<xs:documentation xml:lang="en">Apsilus fuscus. DESCRIPTION: African forktail snapper</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFL">
<xs:annotation>
<xs:documentation xml:lang="en">Antennatus flagellatus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFM">
<xs:annotation>
<xs:documentation xml:lang="en">Adamas formosus. DESCRIPTION: Starhead killi</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFN">
<xs:annotation>
<xs:documentation xml:lang="en">Antennarius nummifer. DESCRIPTION: Spotfin frogfish</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFO">
<xs:annotation>
<xs:documentation xml:lang="en">Aspidophoroides bartoni. DESCRIPTION: Aleutian alligatorfish</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFP">
<xs:annotation>
<xs:documentation xml:lang="en">Amphiprion akallopisos. DESCRIPTION: Skunk clownfish</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFQ">
<xs:annotation>
<xs:documentation xml:lang="en">Paphies australis. DESCRIPTION: Pipi wedge clam</xs:documentation
>
EUCISE2020
Page 210 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFR">
<xs:annotation>
<xs:documentation xml:lang="en">Alloophorus robustus. DESCRIPTION: Bulldog goodeid</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFS">
<xs:annotation>
<xs:documentation xml:lang="en">Aphanius fasciatus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFT">
<xs:annotation>
<xs:documentation xml:lang="en">Agonus cataphractus. DESCRIPTION: Hooknose</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFU">
<xs:annotation>
<xs:documentation xml:lang="en">Alfaro cultratus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFV">
<xs:annotation>
<xs:documentation xml:lang="en">Aulorhynchus flavidus. DESCRIPTION: Tube-snout</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFW">
<xs:annotation>
<xs:documentation xml:lang="en">Assessor flavissimus. DESCRIPTION: Yellow devilfish</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFX">
<xs:annotation>
<xs:documentation xml:lang="en">Amphibolis antarctica. DESCRIPTION: Sea nymph</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFY">
<xs:annotation>
<xs:documentation xml:lang="en">Amphiprion akindynos. DESCRIPTION: Barrier reef anemonefish</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AFZ">
<xs:annotation>
<xs:documentation xml:lang="en">Afronandus sheljuzhkoi. DESCRIPTION: Fourspine leaffish</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGA">
<xs:annotation>
<xs:documentation xml:lang="en">Guentherus altivela. DESCRIPTION: Jellynose</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGB">
<xs:annotation>
<xs:documentation xml:lang="en">Antipathes grandis. DESCRIPTION: Umimatsu, pine coral</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGC">
<xs:annotation>
<xs:documentation xml:lang="en">Amblygaster clupeoides. DESCRIPTION: Bleeker smoothbelly sardinel
la</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGD">
<xs:annotation>
<xs:documentation xml:lang="en">Gymnothorax maderensis. DESCRIPTION: Sharktooth moray</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGE">
EUCISE2020
Page 211 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">Agosia chrysogaster. DESCRIPTION: Longfin dace</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGF">
<xs:annotation>
<xs:documentation xml:lang="en">Agmus lyriformis. DESCRIPTION: Gnarled catfish</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGG">
<xs:annotation>
<xs:documentation xml:lang="en">Gymnothorax moringa. DESCRIPTION: Spotted moray</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGH">
<xs:annotation>
<xs:documentation xml:lang="en">Gymnotus pantherinus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGI">
<xs:annotation>
<xs:documentation xml:lang="en">Gymnothorax polygonius. DESCRIPTION: Polygon moray</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGJ">
<xs:annotation>
<xs:documentation xml:lang="en">Argobuccinum olearium. DESCRIPTION: Oil-vessel triton</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGK">
<xs:annotation>
<xs:documentation xml:lang="en">Gymnothorax unicolor. DESCRIPTION: Brown moray</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGL">
<xs:annotation>
<xs:documentation xml:lang="en">Amblygaster leiogaster. DESCRIPTION: Smoothbelly sardinella</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGM">
<xs:annotation>
<xs:documentation xml:lang="en">Alligator mississippiensis. DESCRIPTION: American alligator</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGN">
<xs:annotation>
<xs:documentation xml:lang="en">Squatina squatina. DESCRIPTION: Angelshark</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGO">
<xs:annotation>
<xs:documentation xml:lang="en">Gymnothorax pseudothyrsoideus. DESCRIPTION: Highfin moray</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGP">
<xs:annotation>
<xs:documentation xml:lang="en">Agrostichthys parkeri. DESCRIPTION: Streamer fish</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGQ">
<xs:annotation>
<xs:documentation xml:lang="en">Aulostomus strigosus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGR">
<xs:annotation>
<xs:documentation xml:lang="en">Aplodinotus grunniens. DESCRIPTION: Freshwater drum</xs:documenta
tion>
EUCISE2020
Page 212 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGS">
<xs:annotation>
<xs:documentation xml:lang="en">Amblygaster sirm. DESCRIPTION: Spotted sardinella</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGT">
<xs:annotation>
<xs:documentation xml:lang="en">Gymnothorax meleagris. DESCRIPTION: Turkey moray</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGU">
<xs:annotation>
<xs:documentation xml:lang="en">Gymnothorax rueppelliae. DESCRIPTION: Banded moray</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGV">
<xs:annotation>
<xs:documentation xml:lang="en">Altolamprologus calvus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGW">
<xs:annotation>
<xs:documentation xml:lang="en">Anoplogaster cornuta. DESCRIPTION: Common fangtooth</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGX">
<xs:annotation>
<xs:documentation xml:lang="en">Gymnothorax mordax. DESCRIPTION: California moray</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGY">
<xs:annotation>
<xs:documentation xml:lang="en">Gymnothorax porphyreus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AGZ">
<xs:annotation>
<xs:documentation xml:lang="en">Argyrocottus zanderi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHA">
<xs:annotation>
<xs:documentation xml:lang="en">Acanthorhodeus asmussii. DESCRIPTION: Russian bitterling</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHB">
<xs:annotation>
<xs:documentation xml:lang="en">Atopochilus chabanaudi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHC">
<xs:annotation>
<xs:documentation xml:lang="en">Anchovia macrolepidota. DESCRIPTION: Bigscale anchovy</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHD">
<xs:annotation>
<xs:documentation xml:lang="en">Abythites lepidogenys. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHE">
<xs:annotation>
<xs:documentation xml:lang="en">Archaulus biseriatus. DESCRIPTION: Scaled sculpin</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 213 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="AHF">
<xs:annotation>
<xs:documentation xml:lang="en">Aphanotorulus frankei. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHG">
<xs:annotation>
<xs:documentation xml:lang="en">Psephurus gladius. DESCRIPTION: Chinese swordfish</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHH">
<xs:annotation>
<xs:documentation xml:lang="en">Atherina hepsetus. DESCRIPTION: Mediterranean sand smelt</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHI">
<xs:annotation>
<xs:documentation xml:lang="en">Acanthocleithron chapini. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHJ">
<xs:annotation>
<xs:documentation xml:lang="en">Amaralia hypsiurus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHK">
<xs:annotation>
<xs:documentation xml:lang="en">Alertichthys blacki. DESCRIPTION: Alert pigfish</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHL">
<xs:annotation>
<xs:documentation xml:lang="en">Acanthalburnus microlepis. DESCRIPTION: Blackbrow bleak</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHM">
<xs:annotation>
<xs:documentation xml:lang="en">Huso dauricus. DESCRIPTION: Kaluga</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHN">
<xs:annotation>
<xs:documentation xml:lang="en">Anthias anthias. DESCRIPTION: Swallowtail seaperch</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHO">
<xs:annotation>
<xs:documentation xml:lang="en">Alcichthys alcicornis. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHP">
<xs:annotation>
<xs:documentation xml:lang="en">Panturichthys isognathus. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHQ">
<xs:annotation>
<xs:documentation xml:lang="en">Cantheschenia grandisquamis. DESCRIPTION: Large-scaled leatherjac
ket</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AHR">
<xs:annotation>
2.39. schema data/Entity/Cargo/PollutionCodeEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:simpleType name="PollutionCodeEnumType">
EUCISE2020
Page 214 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation>This enumeration defines the pollution code, according to the MARPOL.</xs:documentation
>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="X">
<xs:annotation>
<xs:documentation xml:lang="en">category X. DESCRIPTION: Noxious Liquid Substances which, if disc
harged into the sea from tank cleaning or deballasting operations, are deemed to present a major hazard to either mar
ine resources or human health and, therefore, justify the prohibition of the discharge into the marine environment</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Y">
<xs:annotation>
<xs:documentation xml:lang="en">category Y. DESCRIPTION: Noxious Liquid Substances which, if disc
harged into the sea from tank cleaning or deballasting operations, are deemed to present a hazard to either marine re
sources or human health or cause harm to amenities or other legitimate uses of the sea and therefore justify a limita
tion on the quality and quantity of the discharge into the marine environment</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Z">
<xs:annotation>
<xs:documentation xml:lang="en">category Z. DESCRIPTION: Noxious Liquid Substances which, if dis
charged into the sea from tank cleaning or deballasting operations, are deemed to present a minor hazard to either ma
rine resources or human health and therefore justify less stringent restrictions on the quality and quantity of the d
ischarge into the marine environment</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="OS">
<xs:annotation>
<xs:documentation xml:lang="en">other substances. DESCRIPTION: substances which have been evaluat
ed and found to fall outside Category X, Y or Z because they are considered to present no harm to marine resources, h
uman health, amenities or other legitimate uses of the sea when discharged into the sea from tank cleaning of deballa
sting operations. The discharge of bilge or ballast water or other residues or mixtures containing these substances a
re not subject to any requirements of MARPOL Annex II</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NonSpecified">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.40. schema data/Entity/Cargo/UNDGEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:simpleType name="UNDGEnumType">
<xs:annotation>
<xs:documentation>This enumeration defines United Nations Dangerous Goods list.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="0004">
<xs:annotation>
<xs:documentation xml:lang="en">AMMONIUM PICRATE dry or wetted with less than 10% water, by mass.
DESCRIPTION: AMMONIUM PICRATE dry or wetted with less than 10% water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0005">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES FOR WEAPONS with bursting charge. DESCRIPTION: CARTRID
GES FOR WEAPONS with bursting charge (Class 1.1F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0006">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES FOR WEAPONS with bursting charge. DESCRIPTION: CARTRID
GES FOR WEAPONS with bursting charge (Class 1.1E)</xs:documentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 215 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="0007">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES FOR WEAPONS with bursting charge. DESCRIPTION: CARTRID
GES FOR WEAPONS with bursting charge (Class 1.2F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0009">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, INCENDIARY with or without burster, expelling charge
or propelling charge. DESCRIPTION: AMMUNITION, INCENDIARY with or without burster, expelling charge or propelling cha
rge (Class 1.2G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0010">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, INCENDIARY with or without burster, expelling charge
or propelling charge. DESCRIPTION: AMMUNITION, INCENDIARY with or without burster, expelling charge or propelling cha
rge (Class 1.3G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0012">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES FOR WEAPONS, INERT PROJECTILE or CARTRIDGES, SMALL ARM
S. DESCRIPTION: CARTRIDGES FOR WEAPONS, INERT PROJECTILE or CARTRIDGES, SMALL ARMS (Class 1.4S)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0014">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES FOR WEAPONS, BLANK or CARTRIDGES, SMALL ARMS, BLANK. D
ESCRIPTION: CARTRIDGES FOR WEAPONS, BLANK or CARTRIDGES, SMALL ARMS, BLANK (Class 1.4S)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0015">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, SMOKE with or without burster, expelling charge or pr
opelling charge. DESCRIPTION: AMMUNITION, SMOKE with or without burster, expelling charge or propelling charge (Class
1.2G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0016">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, SMOKE with or without burster, expelling charge or pr
opelling charge. DESCRIPTION: AMMUNITION, SMOKE with or without burster, expelling charge or propelling charge (Class
1.3G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0018">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, TEAR-PRODUCING with burster, expelling charge or prop
elling charge. DESCRIPTION: AMMUNITION, TEAR-PRODUCING with burster, expelling charge or propelling charge (Class 1.2
G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0019">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, TEAR-PRODUCING with burster, expelling charge or prop
elling charge. DESCRIPTION: AMMUNITION, TEAR-PRODUCING with burster, expelling charge or propelling charge (Class 1.3
G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0020">
<xs:annotation>
<xs:documentation xml:lang="en">Ammunition, toxic with burster, expelling charge or propelling ch
arge. DESCRIPTION: Ammunition, toxic with burster, expelling charge or propelling charge (Class 1.2K)</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0021">
<xs:annotation>
<xs:documentation xml:lang="en">Ammunition, toxic with burster, expelling charge or propelling ch
arge. DESCRIPTION: Ammunition, toxic with burster, expelling charge or propelling charge (Class 1.3K)</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0027">
EUCISE2020
Page 216 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">BLACK POWDER (GUNPOWDER), granular or as a meal. DESCRIPTION: BLA
CK POWDER (GUNPOWDER), granular or as a meal (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0028">
<xs:annotation>
<xs:documentation xml:lang="en">BLACK POWDER (GUNPOWDER), COMPRESSED or BLACK POWDER (GUNPOWDER),
IN PELLETS. DESCRIPTION: BLACK POWDER (GUNPOWDER), COMPRESSED or BLACK POWDER (GUNPOWDER), IN PELLETS (Class 1.1D)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0029">
<xs:annotation>
<xs:documentation xml:lang="en">DETONATORS, NON-ELECTRIC for blasting. DESCRIPTION: DETONATORS, N
ON-ELECTRIC for blasting (Class 1.1B)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0030">
<xs:annotation>
<xs:documentation xml:lang="en">DETONATORS, ELECTRIC for blasting. DESCRIPTION: DETONATORS, ELECT
RIC for blasting (Class 1.1B)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0033">
<xs:annotation>
<xs:documentation xml:lang="en">BOMBS with bursting charge. DESCRIPTION: BOMBS with bursting char
ge (Class 1.1F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0034">
<xs:annotation>
<xs:documentation xml:lang="en">BOMBS with bursting charge. DESCRIPTION: BOMBS with bursting char
ge (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0035">
<xs:annotation>
<xs:documentation xml:lang="en">BOMBS with bursting charge. DESCRIPTION: BOMBS with bursting char
ge (Class 1.2D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0037">
<xs:annotation>
<xs:documentation xml:lang="en">BOMBS, PHOTO-FLASH. DESCRIPTION: BOMBS, PHOTO-FLASH (Class 1.1F)<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0038">
<xs:annotation>
<xs:documentation xml:lang="en">BOMBS, PHOTO-FLASH. DESCRIPTION: BOMBS, PHOTO-FLASH (Class 1.1D)<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0039">
<xs:annotation>
<xs:documentation xml:lang="en">BOMBS, PHOTO-FLASH. DESCRIPTION: BOMBS, PHOTO-FLASH (Class 1.2G)<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0042">
<xs:annotation>
<xs:documentation xml:lang="en">BOOSTERS without detonator. DESCRIPTION: BOOSTERS without detonat
or (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0043">
<xs:annotation>
<xs:documentation xml:lang="en">BURSTERS, explosive. DESCRIPTION: BURSTERS, explosive (Class 1.1D
)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0044">
<xs:annotation>
<xs:documentation xml:lang="en">PRIMERS, CAP TYPE. DESCRIPTION: PRIMERS, CAP TYPE (Class 1.4S)</x
EUCISE2020
Page 217 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0048">
<xs:annotation>
<xs:documentation xml:lang="en">CHARGES, DEMOLITION. DESCRIPTION: CHARGES, DEMOLITION (Class 1.1D
)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0049">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES, FLASH. DESCRIPTION: CARTRIDGES, FLASH (Class 1.1G)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0050">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES, FLASH. DESCRIPTION: CARTRIDGES, FLASH (Class 1.3G)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0054">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES, SIGNAL. DESCRIPTION: CARTRIDGES, SIGNAL (Class 1.3G)<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0055">
<xs:annotation>
<xs:documentation xml:lang="en">CASES, CARTRIDGE, EMPTY, WITH PRIMER. DESCRIPTION: CASES, CARTRID
GE, EMPTY, WITH PRIMER (Class 1.4S)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0056">
<xs:annotation>
<xs:documentation xml:lang="en">CHARGES, DEPTH. DESCRIPTION: CHARGES, DEPTH (Class 1.1D)</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0059">
<xs:annotation>
<xs:documentation xml:lang="en">CHARGES, SHAPED without detonator. DESCRIPTION: CHARGES, SHAPED w
ithout detonator (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0060">
<xs:annotation>
<xs:documentation xml:lang="en">CHARGES, SUPPLEMENTARY, EXPLOSIVE. DESCRIPTION: CHARGES, SUPPLEME
NTARY, EXPLOSIVE (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0065">
<xs:annotation>
<xs:documentation xml:lang="en">CORD, DETONATING, flexible. DESCRIPTION: CORD, DETONATING, flexib
le (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0066">
<xs:annotation>
<xs:documentation xml:lang="en">CORD, IGNITER. DESCRIPTION: CORD, IGNITER (Class 1.4G)</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0070">
<xs:annotation>
<xs:documentation xml:lang="en">CUTTERS, CABLE, EXPLOSIVE. DESCRIPTION: CUTTERS, CABLE, EXPLOSIVE
(Class 1.4S)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0072">
<xs:annotation>
<xs:documentation xml:lang="en">CYCLOTRIMETHYLENETRINITRAMINE (CYCLONITE; HEXOGEN; RDX), WETTED w
ith not less than 15% water, by mass. DESCRIPTION: CYCLOTRIMETHYLENETRINITRAMINE (CYCLONITE; HEXOGEN; RDX), WETTED wi
th not less than 15% water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
EUCISE2020
Page 218 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="0073">
<xs:annotation>
<xs:documentation xml:lang="en">DETONATORS FOR AMMUNITION. DESCRIPTION: DETONATORS FOR AMMUNITION
(Class 1.1B)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0074">
<xs:annotation>
<xs:documentation xml:lang="en">DIAZODINITROPHENOL, WETTED with not less than 40% water, or mixtu
re of alcohol and water, by mass. DESCRIPTION: DIAZODINITROPHENOL, WETTED with not less than 40% water, or mixture of
alcohol and water, by mass (Class 1.1A)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0075">
<xs:annotation>
<xs:documentation xml:lang="en">DIETHYLENEGLYCOL DINITRATE, DESENSITIZED with not less than 25% n
on-volatile, water-insoluble phlegmatizer, by mass. DESCRIPTION: DIETHYLENEGLYCOL DINITRATE, DESENSITIZED with not le
ss than 25% non-volatile, water-insoluble phlegmatizer, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0076">
<xs:annotation>
<xs:documentation xml:lang="en">DINITROPHENOL, dry or wetted with less than 15% water, by mass. D
ESCRIPTION: DINITROPHENOL, dry or wetted with less than 15% water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0077">
<xs:annotation>
<xs:documentation xml:lang="en">DINITROPHENOLATES, alkali metals, dry or wetted with less than 15
% water, by mass. DESCRIPTION: DINITROPHENOLATES, alkali metals, dry or wetted with less than 15% water, by mass (Cla
ss 1.3C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0078">
<xs:annotation>
<xs:documentation xml:lang="en">DINITRORESORCINOL, dry or wetted with less than 15% water, by mas
s. DESCRIPTION: DINITRORESORCINOL, dry or wetted with less than 15% water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0079">
<xs:annotation>
<xs:documentation xml:lang="en">HEXANITRODIPHENYLAMINE (DIPICRYLAMINE; HEXYL). DESCRIPTION: HEXAN
ITRODIPHENYLAMINE (DIPICRYLAMINE; HEXYL) (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0081">
<xs:annotation>
<xs:documentation xml:lang="en">EXPLOSIVE, BLASTING, TYPE A. DESCRIPTION: EXPLOSIVE, BLASTING, TY
PE A (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0082">
<xs:annotation>
<xs:documentation xml:lang="en">EXPLOSIVE, BLASTING, TYPE B. DESCRIPTION: EXPLOSIVE, BLASTING, TY
PE B (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0083">
<xs:annotation>
<xs:documentation xml:lang="en">EXPLOSIVE, BLASTING, TYPE C. DESCRIPTION: EXPLOSIVE, BLASTING, TY
PE C (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0084">
<xs:annotation>
<xs:documentation xml:lang="en">EXPLOSIVE, BLASTING, TYPE D. DESCRIPTION: EXPLOSIVE, BLASTING, TY
PE D (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0092">
<xs:annotation>
<xs:documentation xml:lang="en">FLARES, SURFACE. DESCRIPTION: FLARES, SURFACE (Class 1.3G)</xs:do
cumentation>
</xs:annotation>
EUCISE2020
Page 219 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="0093">
<xs:annotation>
<xs:documentation xml:lang="en">FLARES, AERIAL. DESCRIPTION: FLARES, AERIAL (Class 1.3G)</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0094">
<xs:annotation>
<xs:documentation xml:lang="en">FLASH POWDER. DESCRIPTION: FLASH POWDER (Class 1.1G)</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0099">
<xs:annotation>
<xs:documentation xml:lang="en">FRACTURING DEVICES, EXPLOSIVE without detonator, for oil wells. D
ESCRIPTION: FRACTURING DEVICES, EXPLOSIVE without detonator, for oil wells (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0101">
<xs:annotation>
<xs:documentation xml:lang="en">FUSE, NON-DETONATING. DESCRIPTION: FUSE, NON-DETONATING (Class 1.
3G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0102">
<xs:annotation>
<xs:documentation xml:lang="en">CORD (FUSE), DETONATING, metal clad. DESCRIPTION: CORD (FUSE), DE
TONATING, metal clad (Class 1.2D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0103">
<xs:annotation>
<xs:documentation xml:lang="en">FUSE, IGNITER, tubular, metal clad. DESCRIPTION: FUSE, IGNITER, t
ubular, metal clad (Class 1.4G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0104">
<xs:annotation>
<xs:documentation xml:lang="en">CORD (FUSE), DETONATING, MILD EFFECT, metal clad. DESCRIPTION: CO
RD (FUSE), DETONATING, MILD EFFECT, metal clad (Class 1.4D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0105">
<xs:annotation>
<xs:documentation xml:lang="en">FUSE, SAFETY. DESCRIPTION: FUSE, SAFETY (Class 1.4S)</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0106">
<xs:annotation>
<xs:documentation xml:lang="en">FUZES, DETONATING. DESCRIPTION: FUZES, DETONATING (Class 1.1B)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0107">
<xs:annotation>
<xs:documentation xml:lang="en">FUZES, DETONATING. DESCRIPTION: FUZES, DETONATING (Class 1.2B)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0110">
<xs:annotation>
<xs:documentation xml:lang="en">GRENADES, PRACTICE, hand or rifle. DESCRIPTION: GRENADES, PRACTIC
E, hand or rifle (Class 1.4S)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0113">
<xs:annotation>
<xs:documentation xml:lang="en">GUANYLNITROSAMINOGUANYLIDENE HYDRAZINE, WETTED with not less than
30% water, by mass. DESCRIPTION: GUANYLNITROSAMINOGUANYLIDENE HYDRAZINE, WETTED with not less than 30% water, by mass
(Class 1.1A)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0114">
EUCISE2020
Page 220 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">GUANYLNITROSAMINOGUANYLTETRAZENE (TETRAZENE), WETTED with not les
s than 30% water, or mixture of alcohol and water, by mass. DESCRIPTION: GUANYLNITROSAMINOGUANYLTETRAZENE (TETRAZENE)
, WETTED with not less than 30% water, or mixture of alcohol and water, by mass (Class 1.1A)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0118">
<xs:annotation>
<xs:documentation xml:lang="en">HEXOLITE (HEXOTOL), dry or wetted with less than 15% water, by ma
ss. DESCRIPTION: HEXOLITE (HEXOTOL), dry or wetted with less than 15% water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0121">
<xs:annotation>
<xs:documentation xml:lang="en">IGNITERS. DESCRIPTION: IGNITERS (Class 1.1G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0124">
<xs:annotation>
<xs:documentation xml:lang="en">JET PERFORATING GUNS, CHARGED, oil well, without detonator. DESCR
IPTION: JET PERFORATING GUNS, CHARGED, oil well, without detonator (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0129">
<xs:annotation>
<xs:documentation xml:lang="en">LEAD AZIDE, WETTED with not less than 20% water, or mixture of al
cohol and water, by mass. DESCRIPTION: LEAD AZIDE, WETTED with not less than 20% water, or mixture of alcohol and wat
er, by mass (Class 1.1A)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0130">
<xs:annotation>
<xs:documentation xml:lang="en">LEAD STYPHNATE (LEAD TRINITRORESORCINATE), WETTED with not less t
han 20% water, or mixture of alcohol and water, by mass. DESCRIPTION: LEAD STYPHNATE (LEAD TRINITRORESORCINATE), WETT
ED with not less than 20% water, or mixture of alcohol and water, by mass (Class 1.1A)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0131">
<xs:annotation>
<xs:documentation xml:lang="en">LIGHTERS, FUSE. DESCRIPTION: LIGHTERS, FUSE (Class 1.4S)</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0132">
<xs:annotation>
<xs:documentation xml:lang="en">DEFLAGRATING METAL SALTS OF AROMATIC NITRODERIVATIVES, N.O.S.. DE
SCRIPTION: DEFLAGRATING METAL SALTS OF AROMATIC NITRODERIVATIVES, N.O.S. (Class 1.3C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0133">
<xs:annotation>
<xs:documentation xml:lang="en">MANNITOL HEXANITRATE (NITROMANNITE), WETTED with not less than 40
% water, or mixture of alcohol and water, by mass. DESCRIPTION: MANNITOL HEXANITRATE (NITROMANNITE), WETTED with not
less than 40% water, or mixture of alcohol and water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0135">
<xs:annotation>
<xs:documentation xml:lang="en">MERCURY FULMINATE, WETTED with not less than 20% water, or mixtur
e of alcohol and water, by mass. DESCRIPTION: MERCURY FULMINATE, WETTED with not less than 20% water, or mixture of a
lcohol and water, by mass (Class 1.1A)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0136">
<xs:annotation>
<xs:documentation xml:lang="en">MINES with bursting charge. DESCRIPTION: MINES with bursting char
ge (Class 1.1F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0137">
<xs:annotation>
<xs:documentation xml:lang="en">MINES with bursting charge. DESCRIPTION: MINES with bursting char
ge (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 221 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="0138">
<xs:annotation>
<xs:documentation xml:lang="en">MINES with bursting charge. DESCRIPTION: MINES with bursting char
ge (Class 1.2D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0143">
<xs:annotation>
<xs:documentation xml:lang="en">NITROGLYCERIN, DESENSITIZED with not less than 40% non-volatile w
ater-insoluble phlegmatizer, by mass. DESCRIPTION: NITROGLYCERIN, DESENSITIZED with not less than 40% non-volatile wa
ter-insoluble phlegmatizer, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0144">
<xs:annotation>
<xs:documentation xml:lang="en">NITROGLYCERIN SOLUTION IN ALCOHOL with more than 1% but not more
than 10% nitroglycerin. DESCRIPTION: NITROGLYCERIN SOLUTION IN ALCOHOL with more than 1% but not more than 10% nitrog
lycerin (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0146">
<xs:annotation>
<xs:documentation xml:lang="en">NITROSTARCH, dry or wetted with less than 20% water, by mass. DES
CRIPTION: NITROSTARCH, dry or wetted with less than 20% water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0147">
<xs:annotation>
<xs:documentation xml:lang="en">NITRO UREA. DESCRIPTION: NITRO UREA (Class 1.1D)</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0150">
<xs:annotation>
<xs:documentation xml:lang="en">PENTAERYTHRITE TETRANITRATE (PENTAERYTHRITOL TETRANITRATE; PETN),
WETTED with not less than 25% water, by mass, or DESENSITIZED with not less than 15% phlegmatizer, by mass. DESCRIPTI
ON: PENTAERYTHRITE TETRANITRATE (PENTAERYTHRITOL TETRANITRATE; PETN), WETTED with not less than 25% water, by mass, o
r DESENSITIZED with not less than 15% phlegmatizer, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0151">
<xs:annotation>
<xs:documentation xml:lang="en">PENTOLITE, dry or wetted with less than 15% water, by mass. DESCR
IPTION: PENTOLITE, dry or wetted with less than 15% water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0153">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITROANILINE (PICRAMIDE). DESCRIPTION: TRINITROANILINE (PICRAM
IDE) (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0154">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITROPHENOL (PICRIC ACID), dry or wetted with less than 30% wa
ter, by mass. DESCRIPTION: TRINITROPHENOL (PICRIC ACID), dry or wetted with less than 30% water, by mass (Class 1.1D)
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0155">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITROCHLOROBENZENE (PICRYL CHLORIDE). DESCRIPTION: TRINITROCHL
OROBENZENE (PICRYL CHLORIDE) (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0159">
<xs:annotation>
<xs:documentation xml:lang="en">POWDER CAKE (POWDER PASTE), WETTED with not less than 25% water,
by mass. DESCRIPTION: POWDER CAKE (POWDER PASTE), WETTED with not less than 25% water, by mass (Class 1.3C)</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0160">
<xs:annotation>
<xs:documentation xml:lang="en">POWDER, SMOKELESS. DESCRIPTION: POWDER, SMOKELESS (Class 1.1C)</x
EUCISE2020
Page 222 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0161">
<xs:annotation>
<xs:documentation xml:lang="en">POWDER, SMOKELESS. DESCRIPTION: POWDER, SMOKELESS (Class 1.3C)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0167">
<xs:annotation>
<xs:documentation xml:lang="en">PROJECTILES with bursting charge. DESCRIPTION: PROJECTILES with b
ursting charge (Class 1.1F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0168">
<xs:annotation>
<xs:documentation xml:lang="en">PROJECTILES with bursting charge. DESCRIPTION: PROJECTILES with b
ursting charge (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0169">
<xs:annotation>
<xs:documentation xml:lang="en">PROJECTILES with bursting charge. DESCRIPTION: PROJECTILES with b
ursting charge (Class 1.2D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0171">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, ILLUMINATING with or without burster, expelling charg
e or propelling charge. DESCRIPTION: AMMUNITION, ILLUMINATING with or without burster, expelling charge or propelling
charge (Class 1.2G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0173">
<xs:annotation>
<xs:documentation xml:lang="en">RELEASE DEVICES, EXPLOSIVE. DESCRIPTION: RELEASE DEVICES, EXPLOSI
VE (Class 1.4S)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0174">
<xs:annotation>
<xs:documentation xml:lang="en">RIVETS, EXPLOSIVE. DESCRIPTION: RIVETS, EXPLOSIVE (Class 1.4S)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0180">
<xs:annotation>
<xs:documentation xml:lang="en">ROCKETS with bursting charge. DESCRIPTION: ROCKETS with bursting
charge (Class 1.1F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0181">
<xs:annotation>
<xs:documentation xml:lang="en">ROCKETS with bursting charge. DESCRIPTION: ROCKETS with bursting
charge (Class 1.1E)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0182">
<xs:annotation>
<xs:documentation xml:lang="en">ROCKETS with bursting charge. DESCRIPTION: ROCKETS with bursting
charge (Class 1.2E)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0183">
<xs:annotation>
<xs:documentation xml:lang="en">ROCKETS with inert head. DESCRIPTION: ROCKETS with inert head (Cl
ass 1.3C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0186">
<xs:annotation>
<xs:documentation xml:lang="en">ROCKET MOTORS. DESCRIPTION: ROCKET MOTORS (Class 1.3C)</xs:docume
ntation>
</xs:annotation>
EUCISE2020
Page 223 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="0190">
<xs:annotation>
<xs:documentation xml:lang="en">SAMPLES, EXPLOSIVE, other than initiating explosive. DESCRIPTION:
SAMPLES, EXPLOSIVE, other than initiating explosive (Class 1)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0191">
<xs:annotation>
<xs:documentation xml:lang="en">SIGNAL DEVICES, HAND. DESCRIPTION: SIGNAL DEVICES, HAND (Class 1.
4G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0192">
<xs:annotation>
<xs:documentation xml:lang="en">SIGNALS, RAILWAY TRACK, EXPLOSIVE. DESCRIPTION: SIGNALS, RAILWAY
TRACK, EXPLOSIVE (Class 1.1G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0193">
<xs:annotation>
<xs:documentation xml:lang="en">SIGNALS, RAILWAY TRACK, EXPLOSIVE. DESCRIPTION: SIGNALS, RAILWAY
TRACK, EXPLOSIVE (Class 1.4S)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0194">
<xs:annotation>
<xs:documentation xml:lang="en">SIGNALS, DISTRESS, ship. DESCRIPTION: SIGNALS, DISTRESS, ship (Cl
ass 1.1G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0195">
<xs:annotation>
<xs:documentation xml:lang="en">SIGNALS, DISTRESS, ship. DESCRIPTION: SIGNALS, DISTRESS, ship (Cl
ass 1.3G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0196">
<xs:annotation>
<xs:documentation xml:lang="en">SIGNALS, SMOKE. DESCRIPTION: SIGNALS, SMOKE (Class 1.1G)</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0197">
<xs:annotation>
<xs:documentation xml:lang="en">SIGNALS, SMOKE. DESCRIPTION: SIGNALS, SMOKE (Class 1.4G)</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0204">
<xs:annotation>
<xs:documentation xml:lang="en">SOUNDING DEVICES, EXPLOSIVE. DESCRIPTION: SOUNDING DEVICES, EXPLO
SIVE (Class 1.2F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0207">
<xs:annotation>
<xs:documentation xml:lang="en">TETRANITROANILINE. DESCRIPTION: TETRANITROANILINE (Class 1.1D)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0208">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITROPHENYLMETHYLNITRAMINE (TETRYL). DESCRIPTION: TRINITROPHEN
YLMETHYLNITRAMINE (TETRYL) (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0209">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITROTOLUENE (TNT), dry or wetted with less than 30% water, by
mass. DESCRIPTION: TRINITROTOLUENE (TNT), dry or wetted with less than 30% water, by mass (Class 1.1D)</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0212">
EUCISE2020
Page 224 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">TRACERS FOR AMMUNITION. DESCRIPTION: TRACERS FOR AMMUNITION (Clas
s 1.3G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0213">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITROANISOLE. DESCRIPTION: TRINITROANISOLE (Class 1.1D)</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0214">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITROBENZENE, dry or wetted with less than 30% water, by mass.
DESCRIPTION: TRINITROBENZENE, dry or wetted with less than 30% water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0215">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITROBENZOIC ACID, dry or wetted with less than 30% water, by
mass. DESCRIPTION: TRINITROBENZOIC ACID, dry or wetted with less than 30% water, by mass (Class 1.1D)</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0216">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITRO-m-CRESOL. DESCRIPTION: TRINITRO-m-CRESOL (Class 1.1D)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0217">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITRONAPHTHALENE. DESCRIPTION: TRINITRONAPHTHALENE (Class 1.1D
)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0218">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITROPHENETOLE. DESCRIPTION: TRINITROPHENETOLE (Class 1.1D)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0219">
<xs:annotation>
<xs:documentation xml:lang="en">TRINITRORESORCINOL (STYPHNIC ACID), dry or wetted with less than
20% water, or mixture of alcohol and water, by mass. DESCRIPTION: TRINITRORESORCINOL (STYPHNIC ACID), dry or wetted w
ith less than 20% water, or mixture of alcohol and water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0220">
<xs:annotation>
<xs:documentation xml:lang="en">UREA NITRATE, dry or wetted with less than 20% water, by mass. DE
SCRIPTION: UREA NITRATE, dry or wetted with less than 20% water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0221">
<xs:annotation>
<xs:documentation xml:lang="en">WARHEADS, TORPEDO with bursting charge. DESCRIPTION: WARHEADS, TO
RPEDO with bursting charge (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0222">
<xs:annotation>
<xs:documentation xml:lang="en">AMMONIUM NITRATE with more than 0.2% combustible substances, incl
uding any organic substance calculated as carbon, to the exclusion of any other added substance. DESCRIPTION: AMMONIU
M NITRATE with more than 0.2% combustible substances, including any organic substance calculated as carbon, to the ex
clusion of any other added substance (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0223">
<xs:annotation>
<xs:documentation xml:lang="en">AMMONIUM NITRATE FERTILIZER, which is more liable to explode than
ammonium nitrate with 0.2% combustible substances, including any organic substance calculated as carbon, to the exclu
sion of any other added substance. DESCRIPTION: AMMONIUM NITRATE FERTILIZER, which is more liable to explode than amm
onium nitrate with 0.2% combustible substances, including any organic substance calculated as carbon, to the exclusio
EUCISE2020
Page 225 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
n of any other added substance (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0224">
<xs:annotation>
<xs:documentation xml:lang="en">BARIUM AZIDE, dry or wetted with less than 50% water, by mass. DE
SCRIPTION: BARIUM AZIDE, dry or wetted with less than 50% water, by mass (Class 1.1A)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0225">
<xs:annotation>
<xs:documentation xml:lang="en">BOOSTERS WITH DETONATOR. DESCRIPTION: BOOSTERS WITH DETONATOR (Cl
ass 1.1B)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0226">
<xs:annotation>
<xs:documentation xml:lang="en">CYCLOTETRAMETHYLENETETRANITRAMINE (HMX; OCTOGEN), WETTED with not
less than 15% water, by mass. DESCRIPTION: CYCLOTETRAMETHYLENETETRANITRAMINE (HMX; OCTOGEN), WETTED with not less tha
n 15% water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0234">
<xs:annotation>
<xs:documentation xml:lang="en">SODIUM DINITRO-o-CRESOLATE, dry or wetted with less than 15% wate
r, by mass. DESCRIPTION: SODIUM DINITRO-o-CRESOLATE, dry or wetted with less than 15% water, by mass (Class 1.3C)</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0235">
<xs:annotation>
<xs:documentation xml:lang="en">SODIUM PICRAMATE, dry or wetted with less than 20% water, by mass
. DESCRIPTION: SODIUM PICRAMATE, dry or wetted with less than 20% water, by mass (Class 1.3C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0236">
<xs:annotation>
<xs:documentation xml:lang="en">ZIRCONIUM PICRAMATE, dry or wetted with less than 20% water, by m
ass. DESCRIPTION: ZIRCONIUM PICRAMATE, dry or wetted with less than 20% water, by mass (Class 1.3C)</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0237">
<xs:annotation>
<xs:documentation xml:lang="en">CHARGES, SHAPED, FLEXIBLE, LINEAR. DESCRIPTION: CHARGES, SHAPED,
FLEXIBLE, LINEAR (Class 1.4D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0238">
<xs:annotation>
<xs:documentation xml:lang="en">ROCKETS, LINE-THROWING. DESCRIPTION: ROCKETS, LINE-THROWING (Clas
s 1.2G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0240">
<xs:annotation>
<xs:documentation xml:lang="en">ROCKETS, LINE-THROWING. DESCRIPTION: ROCKETS, LINE-THROWING (Clas
s 1.3G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0241">
<xs:annotation>
<xs:documentation xml:lang="en">EXPLOSIVE, BLASTING, TYPE E. DESCRIPTION: EXPLOSIVE, BLASTING, TY
PE E (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0242">
<xs:annotation>
<xs:documentation xml:lang="en">CHARGES, PROPELLING, FOR CANNON. DESCRIPTION: CHARGES, PROPELLING
, FOR CANNON (Class 1.3C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0243">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, INCENDIARY, WHITE PHOSPHORUS with burster, expelling
EUCISE2020
Page 226 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
charge or propelling charge. DESCRIPTION: AMMUNITION, INCENDIARY, WHITE PHOSPHORUS with burster, expelling charge or
propelling charge (Class 1.2H)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0244">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, INCENDIARY, WHITE PHOSPHORUS with burster, expelling
charge or propelling charge. DESCRIPTION: AMMUNITION, INCENDIARY, WHITE PHOSPHORUS with burster, expelling charge or
propelling charge (Class 1.3H)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0245">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, SMOKE, WHITE PHOSPHORUS with burster, expelling charg
e or propelling charge. DESCRIPTION: AMMUNITION, SMOKE, WHITE PHOSPHORUS with burster, expelling charge or propelling
charge (Class 1.2H)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0246">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, SMOKE, WHITE PHOSPHORUS with burster, expelling charg
e or propelling charge. DESCRIPTION: AMMUNITION, SMOKE, WHITE PHOSPHORUS with burster, expelling charge or propelling
charge (Class 1.3H)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0247">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, INCENDIARY, liquid or gel, with burster, expelling ch
arge or propelling charge. DESCRIPTION: AMMUNITION, INCENDIARY, liquid or gel, with burster, expelling charge or prop
elling charge (Class 1.3J)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0248">
<xs:annotation>
<xs:documentation xml:lang="en">CONTRIVANCES, WATER-ACTIVATED with burster, expelling charge or p
ropelling charge. DESCRIPTION: CONTRIVANCES, WATER-ACTIVATED with burster, expelling charge or propelling charge (Cla
ss 1.2L)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0249">
<xs:annotation>
<xs:documentation xml:lang="en">CONTRIVANCES, WATER-ACTIVATED with burster, expelling charge or p
ropelling charge. DESCRIPTION: CONTRIVANCES, WATER-ACTIVATED with burster, expelling charge or propelling charge (Cla
ss 1.3L)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0250">
<xs:annotation>
<xs:documentation xml:lang="en">ROCKET MOTORS WITH HYPERGOLIC LIQUIDS with or without expelling c
harge. DESCRIPTION: ROCKET MOTORS WITH HYPERGOLIC LIQUIDS with or without expelling charge (Class 1.3L)</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0254">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, ILLUMINATING with or without burster, expelling charg
e or propelling charge. DESCRIPTION: AMMUNITION, ILLUMINATING with or without burster, expelling charge or propelling
charge (Class 1.3G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0255">
<xs:annotation>
<xs:documentation xml:lang="en">DETONATORS, ELECTRIC for blasting. DESCRIPTION: DETONATORS, ELECT
RIC for blasting (Class 1.4B)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0257">
<xs:annotation>
<xs:documentation xml:lang="en">FUZES, DETONATING. DESCRIPTION: FUZES, DETONATING (Class 1.4B)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0266">
<xs:annotation>
<xs:documentation xml:lang="en">OCTOLITE (OCTOL), dry or wetted with less than 15% water, by mass
EUCISE2020
Page 227 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
. DESCRIPTION: OCTOLITE (OCTOL), dry or wetted with less than 15% water, by mass (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0267">
<xs:annotation>
<xs:documentation xml:lang="en">DETONATORS, NON-ELECTRIC for blasting. DESCRIPTION: DETONATORS, N
ON-ELECTRIC for blasting (Class 1.4B)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0268">
<xs:annotation>
<xs:documentation xml:lang="en">BOOSTERS WITH DETONATOR. DESCRIPTION: BOOSTERS WITH DETONATOR (Cl
ass 1.2B)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0271">
<xs:annotation>
<xs:documentation xml:lang="en">CHARGES, PROPELLING. DESCRIPTION: CHARGES, PROPELLING (Class 1.1C
)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0272">
<xs:annotation>
<xs:documentation xml:lang="en">CHARGES, PROPELLING. DESCRIPTION: CHARGES, PROPELLING (Class 1.3C
)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0275">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES, POWER DEVICE. DESCRIPTION: CARTRIDGES, POWER DEVICE (
Class 1.3C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0276">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES, POWER DEVICE. DESCRIPTION: CARTRIDGES, POWER DEVICE (
Class 1.4C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0277">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES, OIL WELL. DESCRIPTION: CARTRIDGES, OIL WELL (Class 1.
3C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0278">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES, OIL WELL. DESCRIPTION: CARTRIDGES, OIL WELL (Class 1.
4C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0279">
<xs:annotation>
<xs:documentation xml:lang="en">CHARGES, PROPELLING, FOR CANNON. DESCRIPTION: CHARGES, PROPELLING
, FOR CANNON (Class 1.1C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0280">
<xs:annotation>
<xs:documentation xml:lang="en">ROCKET MOTORS. DESCRIPTION: ROCKET MOTORS (Class 1.1C)</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0281">
<xs:annotation>
<xs:documentation xml:lang="en">ROCKET MOTORS. DESCRIPTION: ROCKET MOTORS (Class 1.2C)</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0282">
<xs:annotation>
<xs:documentation xml:lang="en">NITROGUANIDINE (PICRITE), dry or wetted with less than 20% water,
by mass. DESCRIPTION: NITROGUANIDINE (PICRITE), dry or wetted with less than 20% water, by mass (Class 1.1D)</xs:docu
mentation>
</xs:annotation>
EUCISE2020
Page 228 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="0283">
<xs:annotation>
<xs:documentation xml:lang="en">BOOSTERS without detonator. DESCRIPTION: BOOSTERS without detonat
or (Class 1.2D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0284">
<xs:annotation>
<xs:documentation xml:lang="en">GRENADES, hand or rifle, with bursting charge. DESCRIPTION: GRENA
DES, hand or rifle, with bursting charge (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0285">
<xs:annotation>
<xs:documentation xml:lang="en">GRENADES, hand or rifle, with bursting charge. DESCRIPTION: GRENA
DES, hand or rifle, with bursting charge (Class 1.2D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0286">
<xs:annotation>
<xs:documentation xml:lang="en">WARHEADS, ROCKET with bursting charge. DESCRIPTION: WARHEADS, ROC
KET with bursting charge (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0287">
<xs:annotation>
<xs:documentation xml:lang="en">WARHEADS, ROCKET with bursting charge. DESCRIPTION: WARHEADS, ROC
KET with bursting charge (Class 1.2D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0288">
<xs:annotation>
<xs:documentation xml:lang="en">CHARGES, SHAPED, FLEXIBLE, LINEAR. DESCRIPTION: CHARGES, SHAPED,
FLEXIBLE, LINEAR (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0289">
<xs:annotation>
<xs:documentation xml:lang="en">CORD, DETONATING, flexible. DESCRIPTION: CORD, DETONATING, flexib
le (Class 1.4D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0290">
<xs:annotation>
<xs:documentation xml:lang="en">CORD (FUSE), DETONATING, metal clad. DESCRIPTION: CORD (FUSE), DE
TONATING, metal clad (Class 1.1D)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0291">
<xs:annotation>
<xs:documentation xml:lang="en">BOMBS with bursting charge. DESCRIPTION: BOMBS with bursting char
ge (Class 1.2F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0292">
<xs:annotation>
<xs:documentation xml:lang="en">GRENADES, hand or rifle, with bursting charge. DESCRIPTION: GRENA
DES, hand or rifle, with bursting charge (Class 1.1F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0293">
<xs:annotation>
<xs:documentation xml:lang="en">GRENADES, hand or rifle, with bursting charge. DESCRIPTION: GRENA
DES, hand or rifle, with bursting charge (Class 1.2F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0294">
<xs:annotation>
<xs:documentation xml:lang="en">MINES with bursting charge. DESCRIPTION: MINES with bursting char
ge (Class 1.2F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0295">
<xs:annotation>
EUCISE2020
Page 229 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">ROCKETS with bursting charge. DESCRIPTION: ROCKETS with bursting
charge (Class 1.2F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0296">
<xs:annotation>
<xs:documentation xml:lang="en">SOUNDING DEVICES, EXPLOSIVE. DESCRIPTION: SOUNDING DEVICES, EXPLO
SIVE (Class 1.1F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0297">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, ILLUMINATING with or without burster, expelling charg
e or propelling charge. DESCRIPTION: AMMUNITION, ILLUMINATING with or without burster, expelling charge or propelling
charge (Class 1.4G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0299">
<xs:annotation>
<xs:documentation xml:lang="en">BOMBS, PHOTO-FLASH. DESCRIPTION: BOMBS, PHOTO-FLASH (Class 1.3G)<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0300">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, INCENDIARY with or without burster, expelling charge
or propelling charge. DESCRIPTION: AMMUNITION, INCENDIARY with or without burster, expelling charge or propelling cha
rge (Class 1.4G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0301">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, TEAR-PRODUCING with burster, expelling charge or prop
elling charge. DESCRIPTION: AMMUNITION, TEAR-PRODUCING with burster, expelling charge or propelling charge (Class 1.4
G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0303">
<xs:annotation>
<xs:documentation xml:lang="en">AMMUNITION, SMOKE with or without burster, expelling charge or pr
opelling charge. DESCRIPTION: AMMUNITION, SMOKE with or without burster, expelling charge or propelling charge (Class
1.4G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0305">
<xs:annotation>
<xs:documentation xml:lang="en">FLASH POWDER. DESCRIPTION: FLASH POWDER (Class 1.3G)</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0306">
<xs:annotation>
<xs:documentation xml:lang="en">TRACERS FOR AMMUNITION. DESCRIPTION: TRACERS FOR AMMUNITION (Clas
s 1.4G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0312">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES, SIGNAL. DESCRIPTION: CARTRIDGES, SIGNAL (Class 1.4G)<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0313">
<xs:annotation>
<xs:documentation xml:lang="en">SIGNALS, SMOKE. DESCRIPTION: SIGNALS, SMOKE (Class 1.2G)</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0314">
<xs:annotation>
<xs:documentation xml:lang="en">IGNITERS. DESCRIPTION: IGNITERS (Class 1.2G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0315">
<xs:annotation>
EUCISE2020
Page 230 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">IGNITERS. DESCRIPTION: IGNITERS (Class 1.3G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0316">
<xs:annotation>
<xs:documentation xml:lang="en">FUZES, IGNITING. DESCRIPTION: FUZES, IGNITING (Class 1.3G)</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0317">
<xs:annotation>
<xs:documentation xml:lang="en">FUZES, IGNITING. DESCRIPTION: FUZES, IGNITING (Class 1.4G)</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0318">
<xs:annotation>
<xs:documentation xml:lang="en">GRENADES, PRACTICE, hand or rifle. DESCRIPTION: GRENADES, PRACTIC
E, hand or rifle (Class 1.3G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0319">
<xs:annotation>
<xs:documentation xml:lang="en">PRIMERS, TUBULAR. DESCRIPTION: PRIMERS, TUBULAR (Class 1.3G)</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0320">
<xs:annotation>
<xs:documentation xml:lang="en">PRIMERS, TUBULAR. DESCRIPTION: PRIMERS, TUBULAR (Class 1.4G)</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0321">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES FOR WEAPONS with bursting charge. DESCRIPTION: CARTRID
GES FOR WEAPONS with bursting charge (Class 1.2E)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0322">
<xs:annotation>
<xs:documentation xml:lang="en">ROCKET MOTORS WITH HYPERGOLIC LIQUIDS with or without expelling c
harge. DESCRIPTION: ROCKET MOTORS WITH HYPERGOLIC LIQUIDS with or without expelling charge (Class 1.2L)</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0323">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES, POWER DEVICE. DESCRIPTION: CARTRIDGES, POWER DEVICE (
Class 1.4S)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0324">
<xs:annotation>
<xs:documentation xml:lang="en">PROJECTILES with bursting charge. DESCRIPTION: PROJECTILES with b
ursting charge (Class 1.2F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0325">
<xs:annotation>
<xs:documentation xml:lang="en">IGNITERS. DESCRIPTION: IGNITERS (Class 1.4G)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0326">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES FOR WEAPONS, BLANK. DESCRIPTION: CARTRIDGES FOR WEAPON
S, BLANK (Class 1.1C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0327">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES FOR WEAPONS, BLANK or CARTRIDGES, SMALL ARMS, BLANK. D
ESCRIPTION: CARTRIDGES FOR WEAPONS, BLANK or CARTRIDGES, SMALL ARMS, BLANK (Class 1.3C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 231 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="0328">
<xs:annotation>
<xs:documentation xml:lang="en">CARTRIDGES FOR WEAPONS, INERT PROJECTILE. DESCRIPTION: CARTRIDGES
FOR WEAPONS, INERT PROJECTILE (Class 1.2C)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0329">
<xs:annotation>
<xs:documentation xml:lang="en">TORPEDOES with bursting charge. DESCRIPTION: TORPEDOES with burst
ing charge (Class 1.1E)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0330">
<xs:annotation>
<xs:documentation xml:lang="en">TORPEDOES with bursting charge. DESCRIPTION: TORPEDOES with burst
ing charge (Class 1.1F)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="0331">
<xs:annotation>
2.41. schema data/Entity/Cargo/PackagingMaterialEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:simpleType name="PackagingMaterialEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of packaging material used in CargoUnits.<
/xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="0">
<xs:annotation>
<xs:documentation xml:lang="en">none. DESCRIPTION: none</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="1">
<xs:annotation>
<xs:documentation xml:lang="en">plastics. DESCRIPTION: plastics</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="2">
<xs:annotation>
<xs:documentation xml:lang="en">paper and fibreboard. DESCRIPTION: paper and fibreboard</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="3">
<xs:annotation>
<xs:documentation xml:lang="en">wood. DESCRIPTION: wood</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="4">
<xs:annotation>
<xs:documentation xml:lang="en">for future use. DESCRIPTION: for future use</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="5">
<xs:annotation>
<xs:documentation xml:lang="en">metal. DESCRIPTION: metal</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="6">
<xs:annotation>
<xs:documentation xml:lang="en">glass porcelain ceramic stoneware. DESCRIPTION: glass porcelain c
eramic stoneware</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="7">
<xs:annotation>
<xs:documentation xml:lang="en">textile. DESCRIPTION: textile</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="8">
EUCISE2020
Page 232 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">reserved. DESCRIPTION: reserved</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="9">
<xs:annotation>
<xs:documentation xml:lang="en">unknown or not otherwise enumerated. DESCRIPTION: unknown or not
otherwise enumerated</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other package material not mentioned abov
e.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Material type not specified.</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.42. schema data/Entity/Cargo/CargoType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Cargo/">
<xs:include schemaLocation="CargoUnitType.xsd"/>
<xs:include schemaLocation="CargoEnumType.xsd"/>
<xs:complexType name="CargoType">
<xs:annotation>
<xs:documentation>A Cargo refers to a set of goods transported by a ship between two ports.</xs:documenta
tion>
</xs:annotation>
<xs:complexContent>
<xs:extension base="cargo:CargoUnitType">
<xs:sequence>
<xs:element name="CargoType" type="cargo:CargoEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.43. schema data/Entity/OperationalAsset/OperationalAssetType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:operationalasset="http://www.cise.eu/datamodel/Entity/Op
erationalAsset/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:metadata="http://www.cise.eu/datamodel/Ent
ity/Metadata/" xmlns:period="http://www.cise.eu/datamodel/Entity/Period/" xmlns:uniqueidentifier="http://www.cise.eu/
datamodel/Entity/UniqueIdentifier/" targetNamespace="http://www.cise.eu/datamodel/Entity/OperationalAsset/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Metadata/" schemaLocation="../Metadata/Metadata.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" schemaLocation="../UniqueIdentifier/
UniqueIdentifierType.xsd"/>
<xs:include schemaLocation="OperationalCapabilityEnumType.xsd"/>
<xs:include schemaLocation="OperationalAssetEnumType.xsd"/>
<xs:complexType name="OperationalAssetType">
<xs:annotation>
<xs:documentation>An Operational Asset is an Object (in particular means of observation or transportation
, but also including associated sensors, means of communication and means of intervention such as deterrence or neutr
alization of threats, fire fighting, pollution containment etc.) enabling operational Actions (most often at sea or o
n sea shores) of the Agents mandated by public Organizations in charge of Maritime Safety and Security.</xs:documenta
tion>
</xs:annotation>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="AvailabilityPeriod" type="period:Period" minOccurs="0"/>
EUCISE2020
Page 233 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:element
<xs:element
<xs:element
<xs:element
<xs:element
name="Identifier" type="uniqueidentifier:UniqueIdentifierType" minOccurs="0"/>
name="MaxPassengers" type="xs:int" minOccurs="0"/>
name="MaxSpeed" type="xs:double" minOccurs="0"/>
name="Metadata" type="metadata:Metadata" minOccurs="0" maxOccurs="unbounded"/>
name="OperationalAssetType" type="operationalasset:OperationalAssetEnumType" minOccur
s="0"/>
<xs:element name="OperationalCapability" type="operationalasset:OperationalCapabilityEnumType" mi
nOccurs="0"/>
<xs:element name="Range" type="xs:double" minOccurs="0"/>
<xs:element name="ReadinessState" type="xs:time" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.44. schema data/Entity/OperationalAsset/OperationalAssetEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:operationalasset="http://www.cise.eu/datamodel/Entity/Op
erationalAsset/" targetNamespace="http://www.cise.eu/datamodel/Entity/OperationalAsset/">
<xs:simpleType name="OperationalAssetEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of operational assets.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">aircraft. DESCRIPTION: An aircraft is a machine that is able to f
ly by gaining support from the air, or, in general, the atmosphere of a planet. It counters the force of gravity by u
sing either static lift or by using the dynamic lift of an airfoil, or in a few cases the downward thrust from jet en
gines.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">helicopter. DESCRIPTION: A helicopter is a type of rotorcraft in
which lift and thrust are supplied by rotors</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">patrol boat. DESCRIPTION: Operated by navies, coast guards and po
lice. Function – defense of coastal waters, rivers and estuaries, borders security and law enforcement. May have an a
nti-surface role</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">UAV. DESCRIPTION: An unmanned aerial vehicle (UAV), also known as
a drone, is an aircraft without a human pilot on board</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">submarine. DESCRIPTION: A submarine is a watercraft capable of in
dependent operation underwater</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">frigate. DESCRIPTION: Smaller than destroyers, one or two mission
s. Protect naval groups and merchant ships. Anti-submarine warfare. Fleet air defense. Anti-surface warships</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">speed boat. DESCRIPTION: A motorboat, speedboat, or powerboat is
a boat which is powered by an engine</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">drone. DESCRIPTION: Drone is the popular term for an unmanned air
EUCISE2020
Page 234 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
craft. It is still a UAV however a drone is flown by software with pre-programmed behavior save for additional comman
ds by the operators</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">tank. DESCRIPTION: A tank is a tracked, armoured fighting vehicle
designed for front-line combat which combines operational mobility and tactical offensive and defensive capabilities<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">truck. DESCRIPTION: A truck (US, CA and AU) or lorry (UK and Irel
and) is a motor vehicle designed to transport cargo. Also military use.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">4x4. DESCRIPTION: Four-wheel drive, All-wheel drive, AWD, 4WD, or
4×4 is a four-wheeled vehicle with a drivetrain that allows all four wheels to receive torque from the engine</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">carrier. DESCRIPTION: Vehicle for transport</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">ambulance. DESCRIPTION: Ambulance</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="14">
<xs:annotation>
<xs:documentation xml:lang="en">motorcycle. DESCRIPTION: Motorcycle</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="15">
<xs:annotation>
<xs:documentation xml:lang="en">artillery vehicle. DESCRIPTION: Vehicle artillery equipped with a
n own propel system to move towards its target</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="16">
<xs:annotation>
<xs:documentation xml:lang="en">desert patrol vehicle. DESCRIPTION: The Desert Patrol Vehicle (DP
V), formerly called the Fast Attack Vehicle (FAV), is a high-speed, lightly armored sandrail-like vehicle first used
in combat during the Gulf War in 1991</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="17">
<xs:annotation>
<xs:documentation xml:lang="en">tractor. DESCRIPTION: A tractor is an engineering vehicle specifi
cally designed to deliver a high tractive effort (or torque) at slow speeds</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="18">
<xs:annotation>
<xs:documentation xml:lang="en">wrecker. DESCRIPTION: A vehicle used to tow away broken-down cars
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="19">
<xs:annotation>
<xs:documentation xml:lang="en">trailer. DESCRIPTION: A trailer is generally an unpowered vehicle
pulled by a powered vehicle</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="20">
<xs:annotation>
<xs:documentation xml:lang="en">humvee. DESCRIPTION: The High Mobility Multipurpose Wheeled Vehic
le (HMMWV), commonly known as the Humvee, is a four-wheel drive military automobile produced by AM General</xs:docume
ntation>
EUCISE2020
Page 235 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="21">
<xs:annotation>
<xs:documentation xml:lang="en">firetrack. DESCRIPTION: Vehicle used for Firefighting</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="22">
<xs:annotation>
<xs:documentation xml:lang="en">van. DESCRIPTION: A van is a kind of vehicle used for transportin
g goods or people</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="23">
<xs:annotation>
<xs:documentation xml:lang="en">UUV. DESCRIPTION: Unmanned underwater vehicles (UUV), sometimes k
nown as underwater drones, are any vehicles that are able to operate underwater without a human occupant. These vehic
les may be divided into two categories, Remotely operated underwater vehicles (ROVs) and Autonomous underwater vehicl
es (AUVs)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="24">
<xs:annotation>
<xs:documentation xml:lang="en">ROV. DESCRIPTION: ROV controlled by a remote human operato</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="25">
<xs:annotation>
<xs:documentation xml:lang="en">USV. DESCRIPTION: USV operate independently of direct human input
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="26">
<xs:annotation>
<xs:documentation xml:lang="en">sea platform. DESCRIPTION: Platform that stand on the sea for dif
ferent purposes</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="27">
<xs:annotation>
<xs:documentation xml:lang="en">aeroplane. DESCRIPTION: Aeroplane</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="28">
<xs:annotation>
<xs:documentation xml:lang="en">destroyer. DESCRIPTION: Fast warships providing multi-mission off
ensive and defensive capability, independently or in fleet support</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="29">
<xs:annotation>
<xs:documentation xml:lang="en">cruiser. DESCRIPTION: Multi-mission warships capable of engaging
multiple simultaneous targets and employed in force support or independent action</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="30">
<xs:annotation>
<xs:documentation xml:lang="en">aircraft carrier. DESCRIPTION: An aircraft carrier is a warship w
ith a full-length flight deck and facilities for carrying, arming, deploying and recovering aircraft, acting as a sea
going airbase</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="31">
<xs:annotation>
<xs:documentation xml:lang="en">corvette. DESCRIPTION: Small frigates. Protect naval and merchant
ships. Anti-submarine warfare. Fleet defence (anti-aircraft mission)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="32">
<xs:annotation>
<xs:documentation xml:lang="en">auxiliary ships. DESCRIPTION: Re-supply Ship. Replenishment at Se
a</xs:documentation>
</xs:annotation>
EUCISE2020
Page 236 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="33">
<xs:annotation>
<xs:documentation xml:lang="en">landing ships. DESCRIPTION: Smaller then assault ships</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="34">
<xs:annotation>
<xs:documentation xml:lang="en">assault ships. DESCRIPTION: Air Cushioned Vehicles</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="35">
<xs:annotation>
<xs:documentation xml:lang="en">mine warfare ships. DESCRIPTION: Mine Warfare Ships</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="36">
<xs:annotation>
<xs:documentation xml:lang="en">strategic fixed assets. DESCRIPTION: Strategic/fixed assets</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="37">
<xs:annotation>
<xs:documentation xml:lang="en">ballons. DESCRIPTION: Ballons</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Other</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.45. schema data/Entity/OperationalAsset/OperationalCapabilityEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:operationalasset="http://www.cise.eu/datamodel/Entity/Op
erationalAsset/" targetNamespace="http://www.cise.eu/datamodel/Entity/OperationalAsset/">
<xs:simpleType name="OperationalCapabilityEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of operational capabilities.</xs:documenta
tion>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">search and rescue. DESCRIPTION: Search for and provision of aid t
o people who are in distress or imminent danger</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">oil pollution. DESCRIPTION: Pollution due to release of a liquid
petroleum hydrocarbon into the environment, especially marine areas, due to human activity</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">telecommunications TLC. DESCRIPTION: Can be accommodated within a
ny of the listed OperationalCapability. It is the transmission of signals over long distances</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">patrolling. DESCRIPTION: The act of moving about an area especial
ly by an authorized and trained person or group, for purposes of observation, inspection, or security</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 237 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">piracy attack. DESCRIPTION: Act of robbery or criminal violence a
t sea. The term can include acts committed on land, in the air, or in other major bodies of water or on a shore. It d
oes not normally include crimes committed against persons traveling on the same vessel as the perpetrator (e.g. one p
assenger stealing from others on the same vessel). The term has been used throughout history to refer to raids across
land borders by non-state agents.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">illegal migration. DESCRIPTION: Refers to the migration of people
across national borders in a way that violates the immigration laws of the destined country. In concrete detection of
Cayucos, mother ships and border monitoring</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">counter drug smuggling. DESCRIPTION: Refers to a global illicit t
rade involving the cultivation, manufacture, distribution and sale of substances which are subject to drug prohibitio
n laws</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">counter illegal fishing. DESCRIPTION: Illegal fishing is the fish
ing which takes place where vessels operate in violation of the fishery laws. It normally applies to the fisheries wh
ich are under the jurisdiction of the coastal state regulated by the regional organizations.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">firefighting. DESCRIPTION: Attempting to control and extinguish f
ires</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">coordination. DESCRIPTION: Operating principle. Command and contr
ol that involves multiple, diverse, networked teams that can involve national and coalition partners and non-military
agencies, challenging the commander to deal with options along various dimensions.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">simulation. DESCRIPTION: Operating principle. Imitation of the op
eration of a real-world process or system over time. The act of simulating something first requires that a model be d
eveloped; this model represents the key characteristics or behaviors/functions of the selected physical or abstract s
ystem or process. The model represents the system itself, whereas the simulation represents the operation of the syst
em over time</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">mobility. DESCRIPTION: Operating principle. It allows disposing o
f the necessary means in order to allow strategic deployment and high mobility of assets and personnel required for t
he operations.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">training. DESCRIPTION: Operating principle. In general, training
is the acquisition of knowledge, skills, and competencies as a result of the teaching of vocational or practical skil
ls and knowledge that relate to specific useful competencies.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="14">
<xs:annotation>
<xs:documentation xml:lang="en">maintenance. DESCRIPTION: Operating principle. Operating principl
e. In general, all actions which have the objective of retaining or restoring an item in or to a state in which it ca
n perform its required function. The actions include the combination of all technical and corresponding administrativ
e, managerial, and supervision actions</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="15">
EUCISE2020
Page 238 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">sustainability. DESCRIPTION: Operating principle. This capability
is oriented to guarantee the sustainability of the assets deployed during a long period of time.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="16">
<xs:annotation>
<xs:documentation xml:lang="en">intelligence surveillance reconnaissance. DESCRIPTION: Fall withi
n the ISTAR concept, which is fundamentally obtaining information and intelligence to support the planning and conduc
t of operations. It is a practice that links several battlefield functions together to assist a combat force in emplo
ying its sensors and managing the information they gather.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="17">
<xs:annotation>
<xs:documentation xml:lang="en">C2 W command and control warfare. DESCRIPTION: Electronic Warfare
encompasses all that is command and control capability, also PSYOPS (includes deception- simulation)</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Other not included above\n-Source</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Non-specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.46. schema data/Entity/Risk/RiskType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:risk="http://www.cise.eu/datamodel/Entity/Risk/" xmlns:e
ntity="http://www.cise.eu/datamodel/Entity/" xmlns:metadata="http://www.cise.eu/datamodel/Entity/Metadata/" xmlns:per
iod="http://www.cise.eu/datamodel/Entity/Period/" xmlns:uniqueidentifier="http://www.cise.eu/datamodel/Entity/UniqueI
dentifier/" targetNamespace="http://www.cise.eu/datamodel/Entity/Risk/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Metadata/" schemaLocation="../Metadata/Metadata.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" schemaLocation="../UniqueIdentifier/
UniqueIdentifierType.xsd"/>
<xs:include schemaLocation="RiskSeverityEnumType.xsd"/>
<xs:include schemaLocation="RiskProbabilityEnumType.xsd"/>
<xs:include schemaLocation="RiskLevelEnumType.xsd"/>
<xs:include schemaLocation="RiskEnumType.xsd"/>
<xs:complexType name="RiskType">
<xs:annotation>
<xs:documentation>The class Risk is used to represent a more or less probable situation involving exposur
e to danger concerning the maritime domain. The notion of risk is usually very subjective and, in a first step, we de
cided to keep the definition of the class simple in order to ease its adoption. Further work could be used to detail
the risk definition and introduce metrics regarding probability and severity.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Identifier" type="uniqueidentifier:UniqueIdentifierType" minOccurs="0"/>
<xs:element name="Metadata" type="metadata:Metadata" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="OccurrencePeriod" type="period:Period" minOccurs="0"/>
<xs:element name="RiskLevel" type="risk:RiskLevelEnumType" minOccurs="0"/>
<xs:element name="RiskProbability" type="risk:RiskProbabilityEnumType" minOccurs="0"/>
<xs:element name="RiskSeverity" type="risk:RiskSeverityEnumType" minOccurs="0"/>
<xs:element name="RiskType" type="risk:RiskEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
EUCISE2020
Page 239 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
2.47. schema data/Entity/Risk/RiskSeverityEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:risk="http://www.cise.eu/datamodel/Entity/Risk/" targetN
amespace="http://www.cise.eu/datamodel/Entity/Risk/">
<xs:simpleType name="RiskSeverityEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the different severities which can be assigned to a risk.</xs
:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">catastrophic. DESCRIPTION: A major catastrophic event is the cons
equence of the risk (death of people, major pollution…)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">critical. DESCRIPTION: The occurrence of the risk leads to major
consequences affecting maritime activities (maritime traffic blocked…)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">marginal. DESCRIPTION: The risk’s consequences are marginal. The
risk as no impact on maritime activities, people or cargo.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">negligible. DESCRIPTION: The risk’s consequences are negligible.<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Risk severity not included above</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Risk severity non-specified</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.48. schema data/Entity/Risk/RiskProbabilityEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:risk="http://www.cise.eu/datamodel/Entity/Risk/" targetN
amespace="http://www.cise.eu/datamodel/Entity/Risk/">
<xs:simpleType name="RiskProbabilityEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">frequent. DESCRIPTION: The risk occurs frequently</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">probable. DESCRIPTION: The risk is probable</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
EUCISE2020
Page 240 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">occasional. DESCRIPTION: The risk could occur on some occasions</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">rare. DESCRIPTION: The occurrence of the risk is rare</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">improbable. DESCRIPTION: The risk is improbable</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Risk Probability not included above</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Risk Probability non-specified</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.49. schema data/Entity/Risk/RiskEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:risk="http://www.cise.eu/datamodel/Entity/Risk/" targetN
amespace="http://www.cise.eu/datamodel/Entity/Risk/">
<xs:simpleType name="RiskEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of Risks.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">accident. DESCRIPTION: Accident</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">illegal immigration. DESCRIPTION: Illegal Immigration</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">drug trafficking. DESCRIPTION: Drug Trafficking</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">collision. DESCRIPTION: Collision</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">human trafficking. DESCRIPTION: Human Trafficking</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">smuggling. DESCRIPTION: Smuggling</xs:documentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 241 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">illegal fishing. DESCRIPTION: Illegal Fishing</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">weapons trafficking. DESCRIPTION: Weapons Trafficking</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">fire. DESCRIPTION: Fire</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">pollution. DESCRIPTION: Pollution</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Risk type not included above</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Risk type non-specified</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.50. schema data/Entity/Risk/RiskLevelEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:risk="http://www.cise.eu/datamodel/Entity/Risk/" targetN
amespace="http://www.cise.eu/datamodel/Entity/Risk/">
<xs:simpleType name="RiskLevelEnumType">
<xs:annotation>
<xs:documentation>The risk level is defined regarding the impact of the risk’s occurrence. It is a combin
ation of the two previous data: risk probability and risk severity. A risk which occurs frequently and has a critical
severity will have a high risk level. Respectively, a low probability risk with negligible severity will have a low r
isk level. This enumeration presents the possible risk levels.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">high. DESCRIPTION: A high level risk occurs frequently and has im
portant consequences</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">medium. DESCRIPTION: Medium level risks have medium impact on mar
itime activities</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">low. DESCRIPTION: A low level risk has a low impact on maritime a
ctivities (improbable or rare risk, risk with negligible severity)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Risk level not included above</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
EUCISE2020
Page 242 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Risk level non-specified</xs:document
ation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.51. schema data/Entity/Metadata/InformationReliabilityLevelEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:metadata="http://www.cise.eu/datamodel/Entity/Metadata/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Metadata/">
<xs:simpleType name="InformationReliabilityLevelEnumType">
<xs:annotation>
<xs:documentation>This enumeration provides a quantitative evaluation of the reliability level of the inf
ormation that is provided.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">very high confidence, verified data. DESCRIPTION: Information and
material whose owner is extremely confident of</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">high confidence. DESCRIPTION: Information and material whose owne
r is very confident of</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">confident. DESCRIPTION: Information and material whose owner is c
onfident of</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">low confidence, unsure source of verification. DESCRIPTION: Infor
mation and material whose owner is not confident of</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">very low confidence, no verification, co-operative target. DESCRI
PTION: Information and material whose owner is very unconfident of</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Information and material whose reliab
ility is not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.52. schema data/Entity/Metadata/FileMediaEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:metadata="http://www.cise.eu/datamodel/Entity/Metadata/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Metadata/">
<xs:simpleType name="FileMediaEnumType">
<xs:annotation>
<xs:documentation>Content types and subtypes as defined in RFC 2046||(Main types include: application, au
dio, example, image, message, model, multipart, text, video)</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value=".3dm">
<xs:annotation>
<xs:documentation xml:lang="en">x-world/x-3dmf. DESCRIPTION: </xs:documentation>
EUCISE2020
Page 243 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value=".avi">
<xs:annotation>
<xs:documentation xml:lang="en">video/avi. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value=".jpeg">
<xs:annotation>
<xs:documentation xml:lang="en">image/jpeg. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.53. schema data/Entity/Metadata/InformationSecurityClassificationEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:metadata="http://www.cise.eu/datamodel/Entity/Metadata/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Metadata/">
<xs:simpleType name="InformationSecurityClassificationEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible values for information security classification.
The enumeration is based in the security rules for protecting EU classified information (&lt;a href="http://eur-lex.e
uropa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2011:141:0017:0065:EN:PDF"&gt;&lt;font color="#000080"&gt;&lt;u&gt;http://
eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2011:141:0017:0065:EN:PDF&lt;/u&gt;&lt;/font&gt;&lt;/a&gt; ).</xs
:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">EU top secret. DESCRIPTION: Information and material the unauthor
ized disclosure of which could cause exceptionally grave prejudice to the essential interests of the European Union o
r of one or more of the Member States</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">EU secret. DESCRIPTION: Information and material the unauthorized
disclosure of which could seriously harm the essential interests of the European Union or of one or more of the Membe
r States</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">EU confidential. DESCRIPTION: Information and material the unauth
orized disclosure of which could harm the essential interests of the European Union or of one or more of the Member S
tates</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">EU restricted. DESCRIPTION: Information and material the unauthor
ized disclosure of which could be disadvantageous to the interests of the European Union or of one or more of the Mem
ber States</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">non-classified. DESCRIPTION: It can be used for information and m
aterial whose classification level is still pending</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: It can be used for information and ma
terial whose classification level is not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
EUCISE2020
Page 244 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
2.54. schema data/Entity/Metadata/Metadata.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:metadata="http://www.cise.eu/datamodel/Entity/Metadata/"
xmlns:agent="http://www.cise.eu/datamodel/Entity/Agent/" xmlns:period="http://www.cise.eu/datamodel/Entity/Period/" t
argetNamespace="http://www.cise.eu/datamodel/Entity/Metadata/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Agent/AgentType.xsd"/>
<xs:include schemaLocation="InformationSensitivityDegreeEnumType.xsd"/>
<xs:include schemaLocation="InformationReliabilityLevelEnumType.xsd"/>
<xs:include schemaLocation="InformationSecurityClassificationEnumType.xsd"/>
<xs:include schemaLocation="FileMediaEnumType.xsd"/>
<xs:complexType name="Metadata">
<xs:annotation>
<xs:documentation>The class provides information about the properties of the data communicated through th
e system, excluding the content of the data.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="Abstract" type="xs:string" minOccurs="0"/>
<xs:element name="Comments" type="xs:string" minOccurs="0"/>
<xs:element name="CreationDate" type="xs:dateTime" minOccurs="0"/>
<xs:element name="Creator" type="agent:AgentType" minOccurs="0"/>
<xs:element name="Description" type="xs:string" minOccurs="0"/>
<xs:element name="Designation" type="xs:string" minOccurs="0"/>
<xs:element name="FileMediaType" type="metadata:FileMediaEnumType" minOccurs="0"/>
<xs:element name="FileSchema" type="xs:anyURI" minOccurs="0"/>
<xs:element name="FileURI" type="xs:anyURI" minOccurs="0"/>
<xs:element name="InformationReliabilityLevel" type="metadata:InformationReliabilityLevelEnumType" minOcc
urs="0"/>
<xs:element name="InformationSecurityClassification" type="metadata:InformationSecurityClassificationEnum
Type" minOccurs="0"/>
<xs:element name="InformationSensitivityDegree" type="metadata:InformationSensitivityDegreeEnumType" minO
ccurs="0"/>
<xs:element name="Language" type="xs:string" minOccurs="0"/>
<xs:element name="PublicationDate" type="xs:dateTime" minOccurs="0"/>
<xs:element name="Publisher" type="agent:AgentType" minOccurs="0"/>
<xs:element name="ValidityPeriod" type="period:Period" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
2.55. schema data/Entity/Metadata/InformationSensitivityDegreeEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:metadata="http://www.cise.eu/datamodel/Entity/Metadata/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Metadata/">
<xs:simpleType name="InformationSensitivityDegreeEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible values for information sensitivity degree. The T
raffic Light Protocol (TLP) of US-CERT is applied (&lt;a href="http://www.us-cert.gov/tlp"&gt;&lt;font color="#000080
"&gt;&lt;u&gt;http://www.us-cert.gov/tlp&lt;/u&gt;&lt;/font&gt;&lt;/a&gt; ).</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">red. DESCRIPTION: TLP: RED when information cannot be effectively
acted upon by additional parties, and could lead to impacts on a party's privacy, reputation, or operations if misuse
d.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">amber. DESCRIPTION: TLP: AMBER when information requires support
to be effectively acted upon, but carries risks to privacy, reputation, or operations if shared outside of the organi
zations involved.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">green. DESCRIPTION: TLP: GREEN when information is useful for the
awareness of all participating organizations as well as with peers within the broader community or sector.</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 245 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">white. DESCRIPTION: TLP: WHITE when information carries minimal o
r no foreseeable risk of misuse, in accordance with applicable rules and procedures for public release.</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: It can be used for information and ma
terial whose classification level is not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.56. schema data/Entity/Agent/AgentRoleInObjectEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:agent="http://www.cise.eu/datamodel/Entity/Agent/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Agent/">
<xs:simpleType name="AgentRoleInObjectEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the relationship between Agent and Object.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">owner. DESCRIPTION: Owns the object</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">ship agent. DESCRIPTION: Is the agent of the object</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">passenger. DESCRIPTION: Is a passenger of the object</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">crew member. DESCRIPTION: Is a member of the crew of the object</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">captain master. DESCRIPTION: Is the master of the object</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">ship operating company. DESCRIPTION: Is the master of the object<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">company security officer. DESCRIPTION: Is the security officer of
the company</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">employee. DESCRIPTION: Is an employee of the object</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
EUCISE2020
Page 246 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">vessel builder. DESCRIPTION: The Vessel Builder</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">vessel charterer. DESCRIPTION: The Vessel Charterer</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">vessel registered owner. DESCRIPTION: The Vessel Registered Owner
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">vessel company. DESCRIPTION: The Vessel Company</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">shipping agent. DESCRIPTION: Shipping agent of the goods</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="14">
<xs:annotation>
<xs:documentation xml:lang="en">declarant. DESCRIPTION: Declarant of the goods</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="15">
<xs:annotation>
<xs:documentation xml:lang="en">carrier agent. DESCRIPTION: Carrier agent of the goods</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="16">
<xs:annotation>
<xs:documentation xml:lang="en">shipping line. DESCRIPTION: Shipping line for the goods</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="17">
<xs:annotation>
<xs:documentation xml:lang="en">customs broker. DESCRIPTION: Customs broker of the goods</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="18">
<xs:annotation>
<xs:documentation xml:lang="en">DPG contact point. DESCRIPTION: DGP (dangerous and polluting good
s) contact point</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other role not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Role not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.57. schema data/Entity/Agent/DutyEnumType.xsd
EUCISE2020
Page 247 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:agent="http://www.cise.eu/datamodel/Entity/Agent/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Agent/">
<xs:simpleType name="DutyEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the role of Agent in relation to Risk.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="001">
<xs:annotation>
<xs:documentation xml:lang="en">able seaman. DESCRIPTION: Able Seaman</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="002">
<xs:annotation>
<xs:documentation xml:lang="en">agent. DESCRIPTION: Agent</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="003">
<xs:annotation>
<xs:documentation xml:lang="en">asst food bev mngr. DESCRIPTION: Assistant Food and Beverage Mana
ger</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="004">
<xs:annotation>
<xs:documentation xml:lang="en">bar manager. DESCRIPTION: Bar Manager</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="005">
<xs:annotation>
<xs:documentation xml:lang="en">bar service. DESCRIPTION: Bar Service</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="006">
<xs:annotation>
<xs:documentation xml:lang="en">bosun. DESCRIPTION: Bosun</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="007">
<xs:annotation>
<xs:documentation xml:lang="en">cadet. DESCRIPTION: Cadet</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="008">
<xs:annotation>
<xs:documentation xml:lang="en">captain. DESCRIPTION: Captain</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="009">
<xs:annotation>
<xs:documentation xml:lang="en">cargo technician. DESCRIPTION: Cargo Technician</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="010">
<xs:annotation>
<xs:documentation xml:lang="en">casino staff. DESCRIPTION: Casino Staff</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="011">
<xs:annotation>
<xs:documentation xml:lang="en">chief cook. DESCRIPTION: Chief Cook</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="012">
<xs:annotation>
<xs:documentation xml:lang="en">chief electrician. DESCRIPTION: Chief Electrician</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="013">
<xs:annotation>
<xs:documentation xml:lang="en">chief housekeeper. DESCRIPTION: Chief Housekeeper</xs:documentati
EUCISE2020
Page 248 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="014">
<xs:annotation>
<xs:documentation xml:lang="en">chief engineer. DESCRIPTION: Chief Engineer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="015">
<xs:annotation>
<xs:documentation xml:lang="en">chief master. DESCRIPTION: Chief Master</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="016">
<xs:annotation>
<xs:documentation xml:lang="en">chief mate. DESCRIPTION: Chief Mate</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="017">
<xs:annotation>
<xs:documentation xml:lang="en">chief officer. DESCRIPTION: Chief Officer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="018">
<xs:annotation>
<xs:documentation xml:lang="en">chief purser. DESCRIPTION: Chief Purser</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="019">
<xs:annotation>
<xs:documentation xml:lang="en">chief steward. DESCRIPTION: Chief Steward</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="020">
<xs:annotation>
<xs:documentation xml:lang="en">class surveyor. DESCRIPTION: Class Surveyor</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="021">
<xs:annotation>
<xs:documentation xml:lang="en">CSO. DESCRIPTION: Company Security Officer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="022">
<xs:annotation>
<xs:documentation xml:lang="en">cook. DESCRIPTION: Cook</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="023">
<xs:annotation>
<xs:documentation xml:lang="en">crane operator. DESCRIPTION: Crane Operator</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="024">
<xs:annotation>
<xs:documentation xml:lang="en">crew member. DESCRIPTION: Crew Member</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="025">
<xs:annotation>
<xs:documentation xml:lang="en">cruise director. DESCRIPTION: Cruise Director</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="026">
<xs:annotation>
<xs:documentation xml:lang="en">cruise staff. DESCRIPTION: Cruise Staff</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="027">
<xs:annotation>
<xs:documentation xml:lang="en">deck apprentice. DESCRIPTION: Deck Apprentice</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="028">
<xs:annotation>
EUCISE2020
Page 249 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">deck fitter. DESCRIPTION: Deck Filter</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="029">
<xs:annotation>
<xs:documentation xml:lang="en">deck officer. DESCRIPTION: Deck Officer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="030">
<xs:annotation>
<xs:documentation xml:lang="en">deckhand. DESCRIPTION: Deckhand, Deck Crew</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="031">
<xs:annotation>
<xs:documentation xml:lang="en">doctor. DESCRIPTION: Doctor</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="032">
<xs:annotation>
<xs:documentation xml:lang="en">donkeyman. DESCRIPTION: Donkeyman</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="033">
<xs:annotation>
<xs:documentation xml:lang="en">electrical engineer. DESCRIPTION: Electrical Engineer</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="034">
<xs:annotation>
<xs:documentation xml:lang="en">electrical officer. DESCRIPTION: Electrical Officer</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="035">
<xs:annotation>
<xs:documentation xml:lang="en">electrician. DESCRIPTION: Electrician</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="036">
<xs:annotation>
<xs:documentation xml:lang="en">engineer cadet. DESCRIPTION: Engineer Cadet, Engine Apprentice</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="037">
<xs:annotation>
<xs:documentation xml:lang="en">engineering crew. DESCRIPTION: Engineering Crew, Engine Crew</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="038">
<xs:annotation>
<xs:documentation xml:lang="en">engine fitter. DESCRIPTION: Engine Fitter</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="039">
<xs:annotation>
<xs:documentation xml:lang="en">entertainment. DESCRIPTION: Entertainment</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="040">
<xs:annotation>
<xs:documentation xml:lang="en">facilities crew. DESCRIPTION: Facilities Crew</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="041">
<xs:annotation>
<xs:documentation xml:lang="en">facilities manager. DESCRIPTION: Facilities Manager</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="042">
<xs:annotation>
EUCISE2020
Page 250 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">first asst engineer. DESCRIPTION: First Assistant Engineer</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="043">
<xs:annotation>
<xs:documentation xml:lang="en">first engineer. DESCRIPTION: First Engineer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="044">
<xs:annotation>
<xs:documentation xml:lang="en">first mate. DESCRIPTION: First Mate</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="045">
<xs:annotation>
<xs:documentation xml:lang="en">first officer. DESCRIPTION: First Officer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="046">
<xs:annotation>
<xs:documentation xml:lang="en">fitter. DESCRIPTION: Fitter</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="047">
<xs:annotation>
<xs:documentation xml:lang="en">fourth officer. DESCRIPTION: Fourth Officer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="048">
<xs:annotation>
<xs:documentation xml:lang="en">food bev mngr. DESCRIPTION: Food and Beverage Manager, Catering O
fficer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="049">
<xs:annotation>
<xs:documentation xml:lang="en">food service. DESCRIPTION: Food Service, Catering Crew</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="050">
<xs:annotation>
<xs:documentation xml:lang="en">fourth asst engineer. DESCRIPTION: Fourth Assistant Engineer, Fou
rth Engineer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="051">
<xs:annotation>
<xs:documentation xml:lang="en">greaser. DESCRIPTION: Greaser</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="052">
<xs:annotation>
<xs:documentation xml:lang="en">hospitality. DESCRIPTION: Hospitality</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="053">
<xs:annotation>
<xs:documentation xml:lang="en">hotel director. DESCRIPTION: Hotel Director</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="054">
<xs:annotation>
<xs:documentation xml:lang="en">hotel staff. DESCRIPTION: Hotel Staff</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="055">
<xs:annotation>
<xs:documentation xml:lang="en">housekeeping staff. DESCRIPTION: Housekeeping Staff</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="056">
<xs:annotation>
EUCISE2020
Page 251 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">information technology. DESCRIPTION: Information Technology</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="057">
<xs:annotation>
<xs:documentation xml:lang="en">junior engineer. DESCRIPTION: Junior Engineer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="058">
<xs:annotation>
<xs:documentation xml:lang="en">laundry master. DESCRIPTION: Laundry Master</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="059">
<xs:annotation>
<xs:documentation xml:lang="en">lifeboatman. DESCRIPTION: Lifeboatman</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="060">
<xs:annotation>
<xs:documentation xml:lang="en">maitred. DESCRIPTION: Maitred</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="061">
<xs:annotation>
<xs:documentation xml:lang="en">marine crew. DESCRIPTION: Marine Crew</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="062">
<xs:annotation>
<xs:documentation xml:lang="en">marketing revenue mngr. DESCRIPTION: Marketing Revenue Manager</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="063">
<xs:annotation>
<xs:documentation xml:lang="en">master. DESCRIPTION: Master</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="064">
<xs:annotation>
<xs:documentation xml:lang="en">master first class plilot. DESCRIPTION: Master First Class Pilot<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="065">
<xs:annotation>
<xs:documentation xml:lang="en">mate first class pilot. DESCRIPTION: Mate First Class Pilot</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="066">
<xs:annotation>
<xs:documentation xml:lang="en">mechanic. DESCRIPTION: Mechanic</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="067">
<xs:annotation>
<xs:documentation xml:lang="en">medical staff. DESCRIPTION: Medical Staff</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="068">
<xs:annotation>
<xs:documentation xml:lang="en">messman. DESCRIPTION: Messman</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="069">
<xs:annotation>
<xs:documentation xml:lang="en">motorman. DESCRIPTION: Motorman</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="070">
<xs:annotation>
<xs:documentation xml:lang="en">oiler. DESCRIPTION: Oiler</xs:documentation>
EUCISE2020
Page 252 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="071">
<xs:annotation>
<xs:documentation xml:lang="en">operator. DESCRIPTION: Operator</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="072">
<xs:annotation>
<xs:documentation xml:lang="en">ordinairy seaman. DESCRIPTION: Ordinairy Seaman</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="073">
<xs:annotation>
<xs:documentation xml:lang="en">owner. DESCRIPTION: Owner</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="074">
<xs:annotation>
<xs:documentation xml:lang="en">painter. DESCRIPTION: Painter</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="075">
<xs:annotation>
<xs:documentation xml:lang="en">porter. DESCRIPTION: Porter</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="076">
<xs:annotation>
<xs:documentation xml:lang="en">provision. DESCRIPTION: Provision</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="077">
<xs:annotation>
<xs:documentation xml:lang="en">provision master. DESCRIPTION: Provision Master</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="078">
<xs:annotation>
<xs:documentation xml:lang="en">pumpman. DESCRIPTION: Pumpman, Pump Man</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="079">
<xs:annotation>
<xs:documentation xml:lang="en">QMED. DESCRIPTION: QMED</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="080">
<xs:annotation>
<xs:documentation xml:lang="en">radio officer. DESCRIPTION: Radio Officer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="081">
<xs:annotation>
<xs:documentation xml:lang="en">reeferman. DESCRIPTION: Reeferman</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="082">
<xs:annotation>
<xs:documentation xml:lang="en">repair man. DESCRIPTION: Repair Man</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="083">
<xs:annotation>
<xs:documentation xml:lang="en">ridding crew. DESCRIPTION: Ridding Crew</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="084">
<xs:annotation>
<xs:documentation xml:lang="en">safety and security. DESCRIPTION: Safety And Security</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 253 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="085">
<xs:annotation>
<xs:documentation xml:lang="en">second asst engineer. DESCRIPTION: Second Assistant Engineer, Sec
ond Engineer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="086">
<xs:annotation>
<xs:documentation xml:lang="en">second mate. DESCRIPTION: Second Mate</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="087">
<xs:annotation>
<xs:documentation xml:lang="en">second officer. DESCRIPTION: Second Officer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="088">
<xs:annotation>
<xs:documentation xml:lang="en">SSO. DESCRIPTION: Ship Security Officer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="089">
<xs:annotation>
<xs:documentation xml:lang="en">staff captain. DESCRIPTION: Staff Captain</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="090">
<xs:annotation>
<xs:documentation xml:lang="en">steward. DESCRIPTION: Steward</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="091">
<xs:annotation>
<xs:documentation xml:lang="en">superintendent. DESCRIPTION: Superintendent</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="092">
<xs:annotation>
<xs:documentation xml:lang="en">tankerman. DESCRIPTION: Tankerman</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="093">
<xs:annotation>
<xs:documentation xml:lang="en">third asst engineer. DESCRIPTION: Third Assistant Engineer, Third
Engineer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="094">
<xs:annotation>
<xs:documentation xml:lang="en">third mate. DESCRIPTION: Third Mate</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="095">
<xs:annotation>
<xs:documentation xml:lang="en">third officer. DESCRIPTION: Third Officer</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="096">
<xs:annotation>
<xs:documentation xml:lang="en">third party. DESCRIPTION: Third Party</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="097">
<xs:annotation>
<xs:documentation xml:lang="en">truck mechanic. DESCRIPTION: Truck Mechanic</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="098">
<xs:annotation>
<xs:documentation xml:lang="en">tunnelman. DESCRIPTION: Tunnelman</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="099">
<xs:annotation>
<xs:documentation xml:lang="en">utility person. DESCRIPTION: Utility Person</xs:documentation>
EUCISE2020
Page 254 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="100">
<xs:annotation>
<xs:documentation xml:lang="en">vetting inspector. DESCRIPTION: Vetting inspector</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="101">
<xs:annotation>
<xs:documentation xml:lang="en">welder. DESCRIPTION: Welder</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="102">
<xs:annotation>
<xs:documentation xml:lang="en">wiper. DESCRIPTION: Wiper</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="103">
<xs:annotation>
<xs:documentation xml:lang="en">yard personell. DESCRIPTION: Yard Personnel</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="998">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other duty not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="999">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Duty not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.58. schema data/Entity/Agent/ISO3166CountryCodeEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:agent="http://www.cise.eu/datamodel/Entity/Agent/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Agent/">
<xs:simpleType name="ISO3166CountryCodeEnumType">
<xs:annotation>
<xs:documentation>contains the Codes Of Nationality according to ISO3166 Standard</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="AC">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Ascension Island</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AD">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Andorra</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AE">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: United Arab Emirates</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AF">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Afghanistan</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AG">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Antigua and Barbuda</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AI">
<xs:annotation>
EUCISE2020
Page 255 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AL">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AM">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AO">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AQ">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AR">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AS">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AT">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AU">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AW">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AX">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AZ">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BA">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BB">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BD">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BE">
<xs:annotation>
EUCISE2020
DESCRIPTION: Anguilla</xs:documentation>
DESCRIPTION: Albania</xs:documentation>
DESCRIPTION: Armenia</xs:documentation>
DESCRIPTION: Angola</xs:documentation>
DESCRIPTION: Antarctica</xs:documentation>
DESCRIPTION: Argentina</xs:documentation>
DESCRIPTION: American Samoa</xs:documentation>
DESCRIPTION: Austria</xs:documentation>
DESCRIPTION: Australia</xs:documentation>
DESCRIPTION: Aruba</xs:documentation>
DESCRIPTION: Åland Islands</xs:documentation>
DESCRIPTION: Azerbaijan</xs:documentation>
DESCRIPTION: Bosnia and Herzegovina</xs:documentation>
DESCRIPTION: Barbados</xs:documentation>
DESCRIPTION: Bangladesh</xs:documentation>
Page 256 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">. DESCRIPTION: Belgium</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BF">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Burkina Faso</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BG">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Bulgaria</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BH">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Bahrain</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BI">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Burundi</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BJ">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Benin</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BL">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Saint Barthélemy</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BM">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Bermuda</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BN">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Brunei Darussalam</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BO">
<xs:annotation>
<xs:documentation xml:lang="en">Bolivia. DESCRIPTION: Plurinational State of Bolivia</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BQ">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Bonaire, Sint Eustatius and Saba</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BR">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BS">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BT">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BV">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
EUCISE2020
DESCRIPTION: Brazil</xs:documentation>
DESCRIPTION: Bahamas</xs:documentation>
DESCRIPTION: Bhutan</xs:documentation>
DESCRIPTION: Bouvet Island</xs:documentation>
Page 257 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="BW">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Botswana</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BY">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Belarus</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="BZ">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Belize</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CA">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Canada</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CC">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Cocos (Keeling) Islands</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CD">
<xs:annotation>
<xs:documentation xml:lang="en">Congo. DESCRIPTION: The Democratic Republic of the Congo</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CF">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CG">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CH">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CI">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CK">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CL">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CM">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CN">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CO">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
EUCISE2020
DESCRIPTION: Central African Republic</xs:documentation>
DESCRIPTION: Congo</xs:documentation>
DESCRIPTION: Switzerland</xs:documentation>
DESCRIPTION: Côte d'Ivoire</xs:documentation>
DESCRIPTION: Cook Islands</xs:documentation>
DESCRIPTION: Chile</xs:documentation>
DESCRIPTION: Cameroon</xs:documentation>
DESCRIPTION: China</xs:documentation>
DESCRIPTION: Colombia</xs:documentation>
Page 258 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="CP">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CR">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CU">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CV">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CW">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CX">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CY">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CZ">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="DE">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="DG">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="DJ">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="DK">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="DM">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="DO">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="DZ">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
EUCISE2020
DESCRIPTION: Clipperton Island</xs:documentation>
DESCRIPTION: Costa Rica</xs:documentation>
DESCRIPTION: Cuba</xs:documentation>
DESCRIPTION: Cape Verde</xs:documentation>
DESCRIPTION: Curaçao</xs:documentation>
DESCRIPTION: Christmas Island</xs:documentation>
DESCRIPTION: Cyprus</xs:documentation>
DESCRIPTION: Czech Republic</xs:documentation>
DESCRIPTION: Germany</xs:documentation>
DESCRIPTION: Diego Garcia</xs:documentation>
DESCRIPTION: Djibouti</xs:documentation>
DESCRIPTION: Denmark</xs:documentation>
DESCRIPTION: Dominica</xs:documentation>
DESCRIPTION: Dominican Republic</xs:documentation>
DESCRIPTION: Algeria</xs:documentation>
Page 259 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="EA">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Ceuta, Melilla</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="EC">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Ecuador</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="EE">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Estonia</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="EG">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Egypt</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="EH">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Western Sahara</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ER">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Eritrea</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ES">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Spain</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ET">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Ethiopia</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="EU">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: European Union</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FI">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Finland</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FJ">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Fiji</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FK">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Falkland Islands (Malvinas)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FM">
<xs:annotation>
<xs:documentation xml:lang="en">Micronesia. DESCRIPTION: Federated States of Micronesia</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FO">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Faroe Islands</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FR">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: France</xs:documentation>
EUCISE2020
Page 260 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FX">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GA">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GB">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GD">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GE">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GF">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GG">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GH">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GI">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GL">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GM">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GN">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GP">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GQ">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GR">
<xs:annotation>
<xs:documentation xml:lang="en">.
EUCISE2020
DESCRIPTION: France, Metropolitan</xs:documentation>
DESCRIPTION: Gabon</xs:documentation>
DESCRIPTION: United Kingdom</xs:documentation>
DESCRIPTION: Grenada</xs:documentation>
DESCRIPTION: Georgia</xs:documentation>
DESCRIPTION: French Guiana</xs:documentation>
DESCRIPTION: Guernsey</xs:documentation>
DESCRIPTION: Ghana</xs:documentation>
DESCRIPTION: Gibraltar</xs:documentation>
DESCRIPTION: Greenland</xs:documentation>
DESCRIPTION: Gambia</xs:documentation>
DESCRIPTION: Guinea</xs:documentation>
DESCRIPTION: Guadeloupe</xs:documentation>
DESCRIPTION: Equatorial Guinea</xs:documentation>
DESCRIPTION: Greece</xs:documentation>
Page 261 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GS">
<xs:annotation>
<xs:documentation xml:lang="en">.
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GT">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GU">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GW">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="GY">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="HK">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="HM">
<xs:annotation>
<xs:documentation xml:lang="en">.
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="HN">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="HR">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="HT">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="HU">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="IC">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ID">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="IE">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="IL">
EUCISE2020
DESCRIPTION: South Georgia and the South Sandwich Islands</xs:d
DESCRIPTION: Guatemala</xs:documentation>
DESCRIPTION: Guam</xs:documentation>
DESCRIPTION: Guinea-Bissau</xs:documentation>
DESCRIPTION: Guyana</xs:documentation>
DESCRIPTION: Hong Kong</xs:documentation>
DESCRIPTION: Heard Island and McDonald Islands</xs:documentatio
DESCRIPTION: Honduras</xs:documentation>
DESCRIPTION: Croatia</xs:documentation>
DESCRIPTION: Haiti</xs:documentation>
DESCRIPTION: Hungary</xs:documentation>
DESCRIPTION: Canary Islands</xs:documentation>
DESCRIPTION: Indonesia</xs:documentation>
DESCRIPTION: Ireland</xs:documentation>
Page 262 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Israel</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="IM">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Isle of Man</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="IN">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: India</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="IO">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: British Indian Ocean Territory</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="IQ">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Iraq</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="IR">
<xs:annotation>
<xs:documentation xml:lang="en">Iran. DESCRIPTION: Islamic Republic of Iran</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="IS">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Iceland</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="IT">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Italy</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="JE">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Jersey</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="JM">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Jamaica</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="JO">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Jordan</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="JP">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Japan</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="KE">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Kenya</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="KG">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Kyrgyzstan</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="KH">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Cambodia</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="KI">
EUCISE2020
Page 263 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Kiribati</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="KM">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Comoros</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="KN">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Saint Kitts and Nevis</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="KP">
<xs:annotation>
<xs:documentation xml:lang="en">NorthKorea. DESCRIPTION: Democratic People's Republic of Korea</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="KR">
<xs:annotation>
<xs:documentation xml:lang="en">SouthKorea. DESCRIPTION: Republic of Korea</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="KW">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Kuwait</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="KY">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Cayman Islands</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="KZ">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Kazakhstan</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="LA">
<xs:annotation>
<xs:documentation xml:lang="en">Laos. DESCRIPTION: Lao People's Democratic Republic</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="LB">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Lebanon</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="LC">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Saint Lucia</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="LI">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Liechtenstein</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="LK">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Sri Lanka</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="LR">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Liberia</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="LS">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Lesotho</xs:documentation>
</xs:annotation>
EUCISE2020
Page 264 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="LT">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Lithuania</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="LU">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Luxembourg</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="LV">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Latvia</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="LY">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Libya</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MA">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Morocco</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MC">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Monaco</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MD">
<xs:annotation>
<xs:documentation xml:lang="en">Moldova. DESCRIPTION: Republic of Moldova</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ME">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Montenegro</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MF">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Saint Martin (French part)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MG">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Madagascar</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MH">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Marshall Islands</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MK">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: The former Yugoslav Republic of Macedonia</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ML">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Mali</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MM">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Myanmar</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MN">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Mongolia</xs:documentation>
EUCISE2020
Page 265 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MO">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MP">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MQ">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MR">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MS">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MT">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MU">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MV">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MW">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MX">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MY">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="MZ">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NA">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NC">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NE">
<xs:annotation>
<xs:documentation xml:lang="en">.
EUCISE2020
DESCRIPTION: Macao</xs:documentation>
DESCRIPTION: Northern Mariana Islands</xs:documentation>
DESCRIPTION: Martinique</xs:documentation>
DESCRIPTION: Mauritania</xs:documentation>
DESCRIPTION: Montserrat</xs:documentation>
DESCRIPTION: Malta</xs:documentation>
DESCRIPTION: Mauritius</xs:documentation>
DESCRIPTION: Maldives</xs:documentation>
DESCRIPTION: Malawi</xs:documentation>
DESCRIPTION: Mexico</xs:documentation>
DESCRIPTION: Malaysia</xs:documentation>
DESCRIPTION: Mozambique</xs:documentation>
DESCRIPTION: Namibia</xs:documentation>
DESCRIPTION: New Caledonia</xs:documentation>
DESCRIPTION: Niger</xs:documentation>
Page 266 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NF">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NG">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NI">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NL">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NO">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NP">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NR">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NU">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NZ">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="OM">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PA">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PE">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PF">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PG">
<xs:annotation>
<xs:documentation xml:lang="en">.
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PH">
<xs:annotation>
<xs:documentation xml:lang="en">.
EUCISE2020
DESCRIPTION: Norfolk Island</xs:documentation>
DESCRIPTION: Nigeria</xs:documentation>
DESCRIPTION: Nicaragua</xs:documentation>
DESCRIPTION: Netherlands</xs:documentation>
DESCRIPTION: Norway</xs:documentation>
DESCRIPTION: Nepal</xs:documentation>
DESCRIPTION: Nauru</xs:documentation>
DESCRIPTION: Niue</xs:documentation>
DESCRIPTION: New Zealand</xs:documentation>
DESCRIPTION: Oman</xs:documentation>
DESCRIPTION: Panama</xs:documentation>
DESCRIPTION: Peru</xs:documentation>
DESCRIPTION: French Polynesia</xs:documentation>
DESCRIPTION: Papua New Guinea</xs:documentation>
DESCRIPTION: Philippines</xs:documentation>
Page 267 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PK">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Pakistan</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PL">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Poland</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PM">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Saint Pierre and Miquelon</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PN">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Pitcairn</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PR">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Puerto Rico</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PS">
<xs:annotation>
<xs:documentation xml:lang="en">Palestine. DESCRIPTION: State of Palestine</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PT">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Portugal</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PW">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Palau</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="PY">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Paraguay</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="QA">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Qatar</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="RE">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Réunion</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="RO">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Romania</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="RS">
<xs:annotation>
<xs:documentation xml:lang="en">. DESCRIPTION: Serbia</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="RU">
<xs:annotation>
<xs:documentation xml:lang="en">Russia. DESCRIPTION: Russian Federation</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="RW">
<xs:annotation>
EUCISE2020
Page 268 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
2.59. schema data/Entity/Agent/AgentRoleInLocationEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:agent="http://www.cise.eu/datamodel/Entity/Agent/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Agent/">
<xs:simpleType name="AgentRoleInLocationEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the relationship between Agent and Location.</xs:documentatio
n>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">owns. DESCRIPTION: Owns the location</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">is located in. DESCRIPTION: Is the (permanent) location of the ag
ent</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">country of birth. DESCRIPTION: Is the country where the agent was
birth</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">place of birth. DESCRIPTION: Is the place where the agent was bir
th</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">country of death. DESCRIPTION: Is the country where the agent die
d</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">place of death. DESCRIPTION: Is the place where the agent died</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">embarkation port. DESCRIPTION: Port in which the agent embarked</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">disembarkation port. DESCRIPTION: Port in which the agent disemba
rked</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">country of residence. DESCRIPTION: The country in which the agent
normally resides</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other relationship not mentioned above</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Relationship not specified</xs:docume
ntation>
EUCISE2020
Page 269 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.60. schema data/Entity/Agent/AgentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:agent="http://www.cise.eu/datamodel/Entity/Agent/" xmlns
:entity="http://www.cise.eu/datamodel/Entity/" xmlns:metadata="http://www.cise.eu/datamodel/Entity/Metadata/" xmlns:u
niqueidentifier="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" targetNamespace="http://www.cise.eu/datamodel
/Entity/Agent/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Metadata/" schemaLocation="../Metadata/Metadata.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" schemaLocation="../UniqueIdentifier/
UniqueIdentifierType.xsd"/>
<xs:complexType name="AgentType" abstract="true">
<xs:annotation>
<xs:documentation>The Agent is one of the core entities of the overall data model of the information shar
ing environment. By definition, an Agent is an operative entity that plays a role in any Event, owns, handles or oper
ates Objects such as Cargo or Assets, creates and exploits Documents etc. It is an entity which holds information abo
ut individual persons or organizations which are involved as actors or targets in the various events and activities.
Agent can have relationship with other agents, objects and locations. Agent can also be related to risks in different
roles. Agent is an abstract entity which has two sub-entities Person and Organization.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="ContactInformation" type="xs:string" minOccurs="0"/>
<xs:element name="Identifier" type="uniqueidentifier:UniqueIdentifierType" minOccurs="0"/>
<xs:element name="IsOfInterest" type="xs:boolean" minOccurs="0"/>
<xs:element name="IsSuspect" type="xs:boolean" minOccurs="0"/>
<xs:element name="Metadata" type="metadata:Metadata" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="Nationality" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.61. schema data/Entity/Agent/AgentRoleInRiskEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:agent="http://www.cise.eu/datamodel/Entity/Agent/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Agent/">
<xs:simpleType name="AgentRoleInRiskEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the role of Agent in relation to Risk.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">cause. DESCRIPTION: Agent is the cause of the risk</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">involved. DESCRIPTION: Agent is somehow involved in the risk</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">reports. DESCRIPTION: Agent is reporting of the risk</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other relation not mentioned above</xs:do
cumentation>
</xs:annotation>
EUCISE2020
Page 270 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Relation not specified</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.62. schema data/Entity/Agent/AgentRoleInAgentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:agent="http://www.cise.eu/datamodel/Entity/Agent/" targe
tNamespace="http://www.cise.eu/datamodel/Entity/Agent/">
<xs:simpleType name="AgentRoleInAgentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the relationship between two Agents.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">leads. DESCRIPTION: Agent who leads the other Agent(s)</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">works for. DESCRIPTION: Agent who works for the other Agent(s)</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">manages security CSO. DESCRIPTION: Person who manages the securit
y of an organization</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">encompasses. DESCRIPTION: Agent who encompasses the other Agent(s
)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">owns. DESCRIPTION: Person who owns the organization.</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other role/relationship not mentioned abo
ve</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Role not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.63. schema data/Entity/Vessel/HullMaterialEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:51] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Vessel/">
<xs:simpleType name="HullMaterialEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents hull material types.</xs:documentation>
EUCISE2020
Page 271 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">high strength steel. DESCRIPTION: High Strength Steel</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other type not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Type not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.64. schema data/Entity/Vessel/VesselType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:51] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" xml
ns:object="http://www.cise.eu/datamodel/Entity/Object/" targetNamespace="http://www.cise.eu/datamodel/Entity/Vessel/"
>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Object/VehicleType.xsd"/>
<xs:include schemaLocation="HullMaterialEnumType.xsd"/>
<xs:include schemaLocation="ShipConfigurationEnumType.xsd"/>
<xs:include schemaLocation="SanitaryMeasureEnumType.xsd"/>
<xs:include schemaLocation="ConditionOfTheCargoAndBallastEnumType.xsd"/>
<xs:include schemaLocation="ISPSSecurityLevelEnumType.xsd"/>
<xs:include schemaLocation="VesselEnumType.xsd"/>
<xs:include schemaLocation="FishingGearEnumType.xsd"/>
<xs:include schemaLocation="INFClassEnumType.xsd"/>
<xs:include schemaLocation="NavigationalStatusEnumType.xsd"/>
<xs:complexType name="VesselType">
<xs:annotation>
<xs:documentation>The class Vessel is a sub-class of the class Vehicle. A vessel refers to a ship or a bo
at. Vessel has the same associations and relationships than its parent-classes Vehicle and Object. Thus it can have r
elationship with Document, Risk, Event, Location, and Agent. It can also be associated with OperationalAsset.</xs:doc
umentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="object:VehicleType">
<xs:sequence>
<xs:element name="Arrangement" type="xs:string" minOccurs="0"/>
<xs:element name="Beam" type="xs:int" minOccurs="0"/>
<xs:element name="Breadth" type="xs:int" minOccurs="0"/>
<xs:element name="CallSign" type="xs:string" minOccurs="0"/>
<xs:element name="ConditionOfTheCargoAndBallast" type="vessel:ConditionOfTheCargoAndBallastEnumTy
pe" minOccurs="0"/>
<xs:element name="ContainerCapacity" type="xs:int" minOccurs="0"/>
<xs:element name="Deadweight" type="xs:int" minOccurs="0"/>
<xs:element name="Depth" type="xs:double" minOccurs="0"/>
<xs:element name="DesignSpeed" type="xs:double" minOccurs="0"/>
<xs:element name="Draught" type="xs:double" minOccurs="0"/>
<xs:element name="FishingGear" type="vessel:FishingGearEnumType" minOccurs="0"/>
<xs:element name="GrossTonnage" type="xs:double" minOccurs="0"/>
<xs:element name="HullMaterial" type="vessel:HullMaterialEnumType" minOccurs="0"/>
<xs:element name="IMONumber" type="xs:long" minOccurs="0"/>
<xs:element name="INFShipClass" type="vessel:INFClassEnumType" minOccurs="0"/>
<xs:element name="INMARSATNumber" type="xs:string" minOccurs="0"/>
<xs:element name="IRNumber" type="xs:string" minOccurs="0"/>
<xs:element name="ISPSSSecurityLevel" type="vessel:ISPSSecurityLevelEnumType" minOccurs="0"/>
<xs:element name="IsBanned" type="xs:boolean" minOccurs="0"/>
<xs:element name="IsFishing" type="xs:boolean" minOccurs="0"/>
<xs:element name="LOA" type="xs:double" minOccurs="0"/>
<xs:element name="Length" type="xs:double" minOccurs="0"/>
<xs:element name="LengthenedYear" type="xs:int" minOccurs="0"/>
<xs:element name="MMSI" type="xs:long" minOccurs="0"/>
<xs:element name="NavigationalStatus" type="vessel:NavigationalStatusEnumType" minOccurs="0"/>
EUCISE2020
Page 272 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:element
<xs:element
<xs:element
<xs:element
<xs:element
<xs:element
<xs:element
<xs:element
<xs:element
<xs:element
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
name="NetTonnage" type="xs:double" minOccurs="0"/>
name="RegionalIdentification" type="xs:string" minOccurs="0"/>
name="RegistryDate" type="xs:date" minOccurs="0"/>
name="RegistryNumber" type="xs:string" minOccurs="0"/>
name="SegregatedBallastVolume" type="xs:double" minOccurs="0"/>
name="ShipConfiguration" type="vessel:ShipConfigurationEnumType" minOccurs="0"/>
name="ShipType" type="vessel:VesselEnumType" minOccurs="0" maxOccurs="unbounded"/>
name="UVI" type="xs:string" minOccurs="0"/>
name="UnderSanitaryMeasure" type="vessel:SanitaryMeasureEnumType" minOccurs="0"/>
name="YearBuilt" type="xs:int" minOccurs="0"/>
2.65. schema data/Entity/Vessel/ConditionOfTheCargoAndBallastEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:51] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Vessel/">
<xs:simpleType name="ConditionOfTheCargoAndBallastEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the vessel load’s condition.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">full. DESCRIPTION: Vessel fully loaded</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">empty. DESCRIPTION: Vessel empty</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">inerted. DESCRIPTION: Load inerted</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other condition not mentioned above</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Condition not specified</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.66. schema data/Entity/Vessel/ShipConfigurationEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:51] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Vessel/">
<xs:simpleType name="ShipConfigurationEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the list of ship configuration types.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="SHT">
<xs:annotation>
<xs:documentation xml:lang="en">Single hull tanker. DESCRIPTION: Single hull tanker</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="SHTBHT">
EUCISE2020
Page 273 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">Single hull with segregatted ballast tanks. DESCRIPTION: Single h
ull with segregated ballast tanks</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="DHT">
<xs:annotation>
<xs:documentation xml:lang="en">Double hull tanker. DESCRIPTION: Double hull tanker</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other ship configuration type not mention
ed above</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Ship configuration type not specified
</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.67. schema data/Entity/Vessel/FishingGearEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:51] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Vessel/">
<xs:simpleType name="FishingGearEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the list of fishing gears a vessel can be equipped with accor
ding to UN FAO rules.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">surrounding nets. DESCRIPTION: Surrounding nets</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">seine nets. DESCRIPTION: Seine nets</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">trawl nets. DESCRIPTION: Trawl nets</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">dredges. DESCRIPTION: Dredges</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">lift nets. DESCRIPTION: Lift nets</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">falling nets. DESCRIPTION: Falling nets</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">gillnets and entangling nets. DESCRIPTION: Gillnets and entanglin
g nets</xs:documentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 274 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">traps. DESCRIPTION: Traps</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">hooks and lines. DESCRIPTION: Hooks and lines</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">grappling and wounding gears. DESCRIPTION: Grappling and wounding
gears</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">stupefying devices. DESCRIPTION: Stupefying devices</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other gear not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Gear not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.68. schema data/Entity/Vessel/INFClassEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:51] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Vessel/">
<xs:simpleType name="INFClassEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the list of international codes for the Safe Carriage of Pack
aged Irradiated Nuclear Fuel, Plutonium and High-Level Radioactive Wastes.||See http://www.imo.org/OurWork/Safety/Car
goes/Pages/IrradiatedNuclearFuel.aspx for further details.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="INF1">
<xs:annotation>
<xs:documentation xml:lang="en">Class INF1. DESCRIPTION: Class INF 1 ship - Ships which are certi
fied to carry INF cargo with an aggregate activity less than 4,000 TBq (TeraBecquerel= measurement of radioactivity)<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="INF2">
<xs:annotation>
<xs:documentation xml:lang="en">Class INF2. DESCRIPTION: Class INF 2 ship - Ships which are certi
fied to carry irradiated nuclear fuel or high-level radioactive wastes with an aggregate activity less than 2 x 106 T
Bq and ships which are certified to carry plutonium with an aggregate activity less than 2 x 105 TBq.</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="INF3">
<xs:annotation>
<xs:documentation xml:lang="en">Class INF3. DESCRIPTION: Class INF 3 ship - Ships which are certi
fied to carry irradiated nuclear fuel or high-level radioactive wastes and ships which are certified to carry plutoni
um with no restriction of the maximum aggregate activity of the materials</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any class not mentioned above</xs:documentati
on>
EUCISE2020
Page 275 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Class not specified</xs:documentation
>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.69. schema data/Entity/Vessel/SanitaryMeasureEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:51] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Vessel/">
<xs:simpleType name="SanitaryMeasureEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the list of sanitary measure a vessel can be the object of.</
xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">quarantine. DESCRIPTION: Quarantine</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">isolation. DESCRIPTION: Isolation</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">disinfection. DESCRIPTION: Disinfection</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">decontamination. DESCRIPTION: Decontamination</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other sanitary measure not mentioned abov
e</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Sanitary measure not specified</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.70. schema data/Entity/Vessel/NavigationalStatusEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:51] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Vessel/">
<xs:simpleType name="NavigationalStatusEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the different types of navigational statuses in accordance wi
th the inter VTS exchange format.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="00">
<xs:annotation>
<xs:documentation xml:lang="en">under way using engine. DESCRIPTION: Under way using engine</xs:d
ocumentation>
EUCISE2020
Page 276 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">at anchor. DESCRIPTION: At anchor</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">not under command. DESCRIPTION: Not under command</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">restricted manoeuvrability. DESCRIPTION: Restricted manoeuvrabili
ty</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">constrained by her draught. DESCRIPTION: Constrained by her draug
ht</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">moored. DESCRIPTION: Moored</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">aground. DESCRIPTION: Aground</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">engaged in fishing. DESCRIPTION: Engaged in fishing</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">under way sailing. DESCRIPTION: Under way sailing</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">engaged in fishing other than trawling. DESCRIPTION: Engaged in f
ishing other than trawling</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">air cushion vessel in non-displamenet mode or WIG craft taking of
f landing or in flight. DESCRIPTION: Air-cushion vessel in non-displacement mode or WIG craft taking off, landing or
in flight</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">power driven vessel towing astern. DESCRIPTION: Power driven vess
el towing astern</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">power driven vessel towig ahead or pushing alongside. DESCRIPTION
: Power driven vessel towing ahead or pushing alongside</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">in distress or requiring assistance. DESCRIPTION: In distress or
EUCISE2020
Page 277 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
requiring assistance</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="14">
<xs:annotation>
<xs:documentation xml:lang="en">AISSART seeking to attract attention. DESCRIPTION: AIS SART, seek
ing to attract attention</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="15">
<xs:annotation>
<xs:documentation xml:lang="en">undefined default. DESCRIPTION: Undefined default</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other severity not mentioned above</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Severity not specified</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.71. schema data/Entity/Vessel/VesselEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:51] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Vessel/">
<xs:simpleType name="VesselEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the different types of Vessel. This list is limited to genera
l type of vessel. It could be detailed in further modeling activities.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">passenger ship. DESCRIPTION: Passenger ship</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">fishing vessel. DESCRIPTION: Fishing vessel</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">nuclear ship. DESCRIPTION: Nuclear ship</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">bulk carrier. DESCRIPTION: Bulk carrier</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">oil tanker. DESCRIPTION: Oil tanker</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">general cargo ship. DESCRIPTION: General cargo ship</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
EUCISE2020
Page 278 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">high speed craft. DESCRIPTION: High-speed craft</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">mobile off shore drilling unit. DESCRIPTION: Mobile off-shore dri
lling unit</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">special purpose ship. DESCRIPTION: Special purpose ship</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other certainty not mentioned above</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Certainty not specified</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.72. schema data/Entity/Vessel/ISPSSecurityLevelEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:51] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Vessel/">
<xs:simpleType name="ISPSSecurityLevelEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible values for the security level of the port.||(Thi
s enumeration presents the three levels of the ISPS code. See http://www.imo.org/blast/mainframe.asp?topic_id=583&amp
;amp;doc_id=2689#code for further details.)</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">security level1. DESCRIPTION: Normal, the level at which the ship
or port facility normally operates. Security level 1 means the level for which minimum appropriate protective securit
y measures shall be maintained at all times.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">security level2. DESCRIPTION: Heightened, the level applying for
as long as there is a heightened risk of a security incident. Security level 2 means the level for which appropriate
additional protective security measures shall be maintained for a period of time as a result of heightened risk of a
security incident.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">security level3. DESCRIPTION: Exceptional, the level applying for
the period of time when there is the probable or imminent risk of a security incident. Security level 3 means the lev
el for which further specific protective security measures shall be maintained for a limited period of time when a se
curity incident is probable or imminent, although it may not be possible to identify the specific target.</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other security level not mentioned above<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
EUCISE2020
Page 279 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Security level not specified</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.73. schema data/Entity/Anomaly/AnomalyEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:anomaly="http://www.cise.eu/datamodel/Entity/Anomaly/" t
argetNamespace="http://www.cise.eu/datamodel/Entity/Anomaly/">
<xs:simpleType name="AnomalyEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the different types of anomalies.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">unexpected movement. DESCRIPTION: Unexpected movement</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">cargo leaking. DESCRIPTION: Cargo leaking</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">shifting of cargo. DESCRIPTION: Shifting of cargo</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">vessel out of traffic lanes. DESCRIPTION: Vessel out of traffic l
anes</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">vessel with erratic movements. DESCRIPTION: Vessel with erratic m
ovements</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">stain of oil sighted. DESCRIPTION: Stain of oil sighted</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">detecion of changes in AIS parameters. DESCRIPTION: Detection of
changes in AIS parameters</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">performing AIS spoofing. DESCRIPTION: Performing AIS spoofing</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">without AIS transmission. DESCRIPTION: Without AIS transmission</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">do not answer on VHF ch16. DESCRIPTION: Do not answer on VHF Ch 1
EUCISE2020
Page 280 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
6</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other anomaly type not mentioned above</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Anomaly type not specified</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.74. schema data/Entity/Anomaly/AnomalyType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:anomaly="http://www.cise.eu/datamodel/Entity/Anomaly/" x
mlns:event="http://www.cise.eu/datamodel/Entity/Event/" targetNamespace="http://www.cise.eu/datamodel/Entity/Anomaly/
">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Event/EventType.xsd"/>
<xs:include schemaLocation="AnomalyEnumType.xsd"/>
<xs:complexType name="AnomalyType">
<xs:annotation>
<xs:documentation>The class Anomaly is a sub-class of the class Event. An anomaly is used to characterize
an unusual event which deserves to be noted or reported. Anomaly has the same associations and relationships than its
parent-class Event. Thus it can have relationship with Document, Risk, Event, Object, Period, Location, and Agent.</x
s:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="event:EventType">
<xs:sequence>
<xs:element name="AnomalyType" type="anomaly:AnomalyEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.75. schema data/Entity/Organization/OrganizationRoleEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" targetNamespace="http://www.cise.eu/datamodel/Entity/Organization/">
<xs:simpleType name="OrganizationRoleEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">port authority. DESCRIPTION: SSN::Port authority. Port Authority
means the competent authority or body designated by Member States for each port to receive and pass on information re
ported pursuant to the directive.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">coastal station. DESCRIPTION: SSN::Coastal station. Coastal Stati
on means any of the following, designated by Member States pursuant to the directive:\n•
A vessel traffic service (
VTS)\n•
A shore-based installation responsible for a mandatory reporting system approved (adopted) by the IMO\n•
A body responsible for coordinating search and rescue operations or operations to tackle pollution at sea</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">port state control. DESCRIPTION: SSN::Port state control. The com
petent authority for inspecting the foreign ships in national ports to verify that the condition of the ship and its
EUCISE2020
Page 281 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
equipment comply with the requirements of international regulations and that the ship is manned and operated in compl
iance with these rules.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">national competent authority. DESCRIPTION: SSN::National competen
t authority. Physical entity designated by Member States in charge of handling and exchanging the SafeSeaNet messages
related to the maritime safety and the traffic monitoring directive. The single point of contact within the Member St
ate is designated as NCA in the framework of SafeSeaNet.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">inspection authority. DESCRIPTION: SSN::Incident::Inspection auth
ority. Competent authority for incident inspections.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other not mentioned before</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Not declared</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.76. schema data/Entity/Organization/FormalOrganizationType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" targetNamespace="http://www.cise.eu/datamodel/Entity/Organization/">
<xs:include schemaLocation="OrganizationType.xsd"/>
<xs:complexType name="FormalOrganizationType">
<xs:annotation>
<xs:documentation>A particular sub-class of organization FormalOrganization can be used to indicate organ
izations that are recognized in the world at large, in particular in legal jurisdictions, with associated rights and
responsibilities. Examples include a corporation, charity, government or church.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="organization:OrganizationType">
<xs:sequence>
<xs:element name="FormalOrganizationName" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.77. schema data/Entity/Organization/OrganizationType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" xmlns:agent="http://www.cise.eu/datamodel/Entity/Agent/" targetNamespace="http://www.cise.eu/datamodel/Entit
y/Organization/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Agent/AgentType.xsd"/>
<xs:include schemaLocation="OrganizationRoleEnumType.xsd"/>
<xs:include schemaLocation="OrganizationPurposeEnumType.xsd"/>
<xs:include schemaLocation="OrganizationClassificationEnumType.xsd"/>
<xs:complexType name="OrganizationType" abstract="true">
<xs:annotation>
<xs:documentation>The class Organization is a sub-class of an abstract class Agent. Organization represen
ts a structured and legally recognized association of humans and material resources for some common purpose or reason
for existence which goes beyond the set of people belonging to it. An organization may itself be involved as actor or
target in the various events and activities. Organization can have the same associations and relationships than the p
arent-class Agent. Thus it can have relationship with other agents, objects and locations or it can be related to ris
ks in different roles. Organization has four sub-classes: OrganizationalUnit, PortOrganization, FormalOrganization an
d OrganizationalCollaboration.</xs:documentation>
EUCISE2020
Page 282 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
<xs:complexContent>
<xs:extension base="agent:AgentType">
<xs:sequence>
<xs:element name="AlternativeName" type="xs:string" minOccurs="0"/>
<xs:element name="IdentificationNumber" type="xs:string" minOccurs="0"/>
<xs:element name="LegalName" type="xs:string" minOccurs="0"/>
<xs:element name="OrganizationClassification" type="organization:OrganizationClassificationEnumTy
pe" minOccurs="0"/>
<xs:element name="OrganizationPurpose" type="organization:OrganizationPurposeEnumType" minOccurs=
"0" maxOccurs="unbounded"/>
<xs:element name="OrganizationRole" type="organization:OrganizationRoleEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.78. schema data/Entity/Organization/OrganizationClassificationEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" targetNamespace="http://www.cise.eu/datamodel/Entity/Organization/">
<xs:simpleType name="OrganizationClassificationEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the formal classification (status) of organization.</xs:docum
entation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">governmental. DESCRIPTION: Governmental organization.</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">european. DESCRIPTION: European agency.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">member state. DESCRIPTION: Representing the government of a membe
r state.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">non-governmental. DESCRIPTION: International organization, indepe
ndent of governments.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">criminal. DESCRIPTION: Company involved in organized crime.</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">private. DESCRIPTION: Private sector company.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">inter governmental. DESCRIPTION: International organization betwe
en governments.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other not mentioned before</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 283 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Not declared</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.79. schema data/Entity/Organization/OrganizationalUnitType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" targetNamespace="http://www.cise.eu/datamodel/Entity/Organization/">
<xs:include schemaLocation="OrganizationType.xsd"/>
<xs:complexType name="OrganizationalUnitType">
<xs:annotation>
<xs:documentation>In some cases it is useful to refer to departments or organizational units such as the
IT department which only have meaning within the context of the containing organization and would not be regarded as
a legal entity in its own right. This situation is supported by a subclass of Organization called OrganizationalUnit.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="organization:OrganizationType">
<xs:sequence>
<xs:element name="UnitIdentifier" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.80. schema data/Entity/Organization/PortOrganizationType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" targetNamespace="http://www.cise.eu/datamodel/Entity/Organization/">
<xs:include schemaLocation="OrganizationType.xsd"/>
<xs:complexType name="PortOrganizationType">
<xs:annotation>
<xs:documentation>A particular sub-class of organization has been defined to be used when modelling IMO r
ecognized ports. PortOrganization carries some additional attributes that carry information relevant only to ports. S
ubclass of Organization.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="organization:OrganizationType">
<xs:sequence>
<xs:element name="IMOCompanyIdentificationNumber" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.81. schema data/Entity/Organization/OrganizationalCollaborationType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" targetNamespace="http://www.cise.eu/datamodel/Entity/Organization/">
<xs:include schemaLocation="OrganizationType.xsd"/>
<xs:complexType name="OrganizationalCollaborationType">
<xs:annotation>
<xs:documentation>The sub-class OrganizationalCollaboration is defined to describe a collaboration betwee
n two or more Organizations such as a project. OrganizationalCollaboration meets the criteria for being an Organizati
on in that it has an identity and defined purpose independent of its particular members but is neither a formally rec
ognized legal entity nor a sub-unit within some larger organization. Might typically have a shorter lifetime than the
Organizations within it, but not necessarily.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="organization:OrganizationType">
<xs:sequence>
</xs:sequence>
</xs:extension>
EUCISE2020
Page 284 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.82. schema data/Entity/Organization/OrganizationPurposeEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" targetNamespace="http://www.cise.eu/datamodel/Entity/Organization/">
<xs:simpleType name="OrganizationPurposeEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the general purpose of the organization.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">general law enforcement. DESCRIPTION: Authorities responsible for
:\n•
Monitoring of compliance with applicable legislation in sea areas, where there is policing competence; support
to enforcement and/or response operations</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">customs. DESCRIPTION: Authorities responsible for:\n•
Monitorin
g of compliance with customs regulations on the import, export and movement of goods; support of enforcement operatio
ns\n• Early warning/identification of criminal trafficking of goods (narcotics, weapons, etc.); support of response o
perations</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">marine environment. DESCRIPTION: Authorities responsible for:\n•
Monitoring of compliance with regulations on the protection of the marine environment; support of enforcement operati
ons\n• Early warning/identification of incidents/accidents that may have an environmental impact; support of pollutio
n response operations</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">maritime safety and security. DESCRIPTION: Authorities responsibl
e for:\n• Monitoring of compliance with regulations on the safety and prevention of pollution caused by ships (const
ruction, equipment, crew/passengers, cargo); support of enforcement operations\n• Monitoring of compliance with regul
ations on the safety of navigation (vessel traffic safety); support of enforcement operations\n• Monitoring of compli
ance with regulations on the security of ships; support of enforcement operations\n•
Supporting safe and efficient
flow of vessel traffic; vessel traffic management\n• Early warning/identification of ships/persons in distress; supp
ort of response operations (search and rescue, salvage, place of refuge)\n• Early warning/identification of maritime
security threats, within the scope of SOLAS Chapter XI-2; support of response operations\n•
Early warning/identifi
cation of threats/acts of piracy or armed robbery; support of response operations</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">defence. DESCRIPTION: Authorities responsible for:\n•
Monitorin
g in support of general Defence tasks, such as: exercising national sovereignty at sea; combating terrorism and other
hostile activities outside the EU; other Common Security and Defence Policy tasks, as defined in Articles 42 and 43 T
EU.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">fisheries control. DESCRIPTION: Authorities responsible for:\n• M
onitoring of compliance with regulations on fisheries; support of enforcement operations\n•
Early warning/identifi
cation of illegal fisheries or fish landings; support of response operations</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">border control. DESCRIPTION: Authorities responsible for:\n•
M
onitoring of compliance with regulations on immigration and border crossing; support of enforcement operations\n• Ea
rly warning/identification of cases of illegal migration or trafficking in human beings; support of response operatio
ns</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
EUCISE2020
Page 285 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">profitable. DESCRIPTION: Not authority. Private or public organiz
ation/company which is expected to make profit.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">non-profitable. DESCRIPTION: Nor authority. Private or public org
anization which is not expected to make profit.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other not mentioned before</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Not declared</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.83. schema data/Entity/Incident/CrisisIncidentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:include schemaLocation="CrisisIncidentEnumType.xsd"/>
<xs:include schemaLocation="IncidentType.xsd"/>
<xs:complexType name="CrisisIncidentType">
<xs:annotation>
<xs:documentation>The CrisisIncident class is a sub-class of Incident and is used to determine types of i
ncidents related to crisis situations as defined by the EUROSUR project.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="incident:IncidentType">
<xs:sequence>
<xs:element name="CrisisIncidentType" type="incident:CrisisIncidentEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.84. schema data/Entity/Incident/LawInfringementIncidentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:include schemaLocation="LawInfringementIncidentEnumType.xsd"/>
<xs:include schemaLocation="IncidentType.xsd"/>
<xs:complexType name="LawInfringementIncidentType">
<xs:annotation>
<xs:documentation>The LawInfringementIncident class is a sub-class of Incident and is used to determine t
ypes of incidents related to law infringement as defined by the EUROSUR project.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="incident:IncidentType">
<xs:sequence>
<xs:element name="LawInfringementIncidentType" type="incident:LawInfringementIncidentEnumType" mi
nOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.85. schema data/Entity/Incident/PollutionEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
EUCISE2020
Page 286 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:simpleType name="PollutionEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="OIL">
<xs:annotation>
<xs:documentation xml:lang="en">Oil. DESCRIPTION: Oil</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="CHEM">
<xs:annotation>
<xs:documentation xml:lang="en">Chemical. DESCRIPTION: Chemical</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FISH">
<xs:annotation>
<xs:documentation xml:lang="en">Fish Oil or Waste. DESCRIPTION: Fish Oil or Waste</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="VEG">
<xs:annotation>
<xs:documentation xml:lang="en">Vegetable Oil or Waste. DESCRIPTION: Vegetable Oil or Waste</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="OTH">
<xs:annotation>
<xs:documentation xml:lang="en">Other. DESCRIPTION: Other</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="UNK">
<xs:annotation>
<xs:documentation xml:lang="en">Unknown. DESCRIPTION: Unknown</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.86. schema data/Entity/Incident/SeverityEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:simpleType name="SeverityEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the severity of an incident as defined by the OASIS common al
erting protocol.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">extreme. DESCRIPTION: Extraordinary threat to life or property</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">severe. DESCRIPTION: Significant threat to life or property</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">moderate. DESCRIPTION: Possible threat to life or property</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">minor. DESCRIPTION: Minimal threat to life or property</xs:docume
EUCISE2020
Page 287 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">unknown. DESCRIPTION: Severity unknown</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other severity not mentioned above</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Severity not specified</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.87. schema data/Entity/Incident/IncidentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" targetNamespace="http://www.cise.eu/datamodel/Entity/Inciden
t/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Event/EventType.xsd"/>
<xs:include schemaLocation="UrgencyEnumType.xsd"/>
<xs:include schemaLocation="CertaintyEnumType.xsd"/>
<xs:include schemaLocation="SeverityEnumType.xsd"/>
<xs:include schemaLocation="ResponseEnumType.xsd"/>
<xs:complexType name="IncidentType" abstract="true">
<xs:annotation>
<xs:documentation>The class Incident is a sub-class of the abstract class Event. An incident refers to a
particular happening, sometimes criminal but always noteworthy. Incident can have the same associations and relations
hips than the parent-class Event. Thus it can have relationship with other agents, objects, documents and locations o
r it can be related to risks. An incident can also be associated with other(s) incident(s) (an incident can cause oth
ers for example). Incident has four sub-classes: MaritimeSafetyIncident, IrregularMigrationIncident, LawInfringementI
ncident and CrisisIncident.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="event:EventType">
<xs:sequence>
<xs:element name="Certainty" type="incident:CertaintyEnumType" minOccurs="0"/>
<xs:element name="DeathsOnBoard" type="xs:int" minOccurs="0"/>
<xs:element name="DiseasesOnBoard" type="xs:boolean" minOccurs="0"/>
<xs:element name="InfectionOnBoard" type="xs:boolean" minOccurs="0"/>
<xs:element name="Instructions" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="NumberOfIIllPersons" type="xs:int" minOccurs="0"/>
<xs:element name="ResponseType" type="incident:ResponseEnumType" minOccurs="0" maxOccurs="unbound
ed"/>
<xs:element name="ResponseUrgency" type="incident:UrgencyEnumType" minOccurs="0"/>
<xs:element name="Severity" type="incident:SeverityEnumType" minOccurs="0"/>
<xs:element name="SickAnimalOnBoard" type="xs:boolean" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.88. schema data/Entity/Incident/LawInfringementIncidentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:simpleType name="LawInfringementIncidentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the law infringement incident types.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
EUCISE2020
Page 288 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">human trafficking exploitation of prostitution of others. DESCRIP
TION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">human trafficking other forms of sexual exploitation. DESCRIPTION
: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">human trafficking forced labour or services. DESCRIPTION: </xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">human trafficking slavery or practices similar to slavery. DESCRI
PTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">human trafficking servitude. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">human trafficking exploitation of activities associated with begg
ing or of unlawful activities. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">human trafficking removal of organs. DESCRIPTION: </xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">human trafficking other. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">drug smuggling marihuana. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">drug smuggling cocaine. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">drug smuggling hashish. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">drug smuggling cannabis. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">drug smuggling heroin. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="14">
<xs:annotation>
<xs:documentation xml:lang="en">drug smuggling amphetamine. DESCRIPTION: </xs:documentation>
</xs:annotation>
EUCISE2020
Page 289 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="15">
<xs:annotation>
<xs:documentation xml:lang="en">drug smuggling metamphetamine. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="16">
<xs:annotation>
<xs:documentation xml:lang="en">drug smuggling ecstasy. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="17">
<xs:annotation>
<xs:documentation xml:lang="en">drug smuggling opium. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="18">
<xs:annotation>
<xs:documentation xml:lang="en">drug smuggling hallucinogens. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="19">
<xs:annotation>
<xs:documentation xml:lang="en">drug smuggling other drugs. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="20">
<xs:annotation>
<xs:documentation xml:lang="en">goods smuggling goods carried with no required permits. DESCRIPTI
ON: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="21">
<xs:annotation>
<xs:documentation xml:lang="en">goods smuggling excise goods. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="22">
<xs:annotation>
<xs:documentation xml:lang="en">goods smuggling counterfeited products. DESCRIPTION: </xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="23">
<xs:annotation>
<xs:documentation xml:lang="en">goods smuggling natural resources minerals. DESCRIPTION: </xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="24">
<xs:annotation>
<xs:documentation xml:lang="en">goods smuggling threatened species. DESCRIPTION: </xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="25">
<xs:annotation>
<xs:documentation xml:lang="en">goods smuggling cultural heritage goods. DESCRIPTION: </xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="26">
<xs:annotation>
<xs:documentation xml:lang="en">smuggling in waste and other hazardous material waste. DESCRIPTIO
N: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="27">
<xs:annotation>
<xs:documentation xml:lang="en">smuggling in waste and other hazardous material chemical. DESCRIP
TION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="28">
<xs:annotation>
EUCISE2020
Page 290 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">smuggling in waste and other hazardous material biohazard. DESCRI
PTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="29">
<xs:annotation>
<xs:documentation xml:lang="en">smuggling in waste and other hazardous material radio active. DES
CRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="30">
<xs:annotation>
<xs:documentation xml:lang="en">smuggling in waste and other hazardous material nuclear. DESCRIPT
ION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="31">
<xs:annotation>
<xs:documentation xml:lang="en">smuggling in waste and other hazardous material other dangerous s
ubstances. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="32">
<xs:annotation>
<xs:documentation xml:lang="en">smuggling in weapon and related accessories arms weapons. DESCRIP
TION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="33">
<xs:annotation>
<xs:documentation xml:lang="en">smuggling in weapon and related accessories weapons of mass destr
uction. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="34">
<xs:annotation>
<xs:documentation xml:lang="en">smuggling in weapon and related accessories ammunition. DESCRIPTI
ON: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="35">
<xs:annotation>
<xs:documentation xml:lang="en">smuggling in weapon and related accessories explosives. DESCRIPTI
ON: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="36">
<xs:annotation>
<xs:documentation xml:lang="en">smuggling in other material. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="37">
<xs:annotation>
<xs:documentation xml:lang="en">other related cross border criminal activity stolen vehicle. DESC
RIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="38">
<xs:annotation>
<xs:documentation xml:lang="en">other related cross border criminal activity document falsificati
on fraud. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="39">
<xs:annotation>
<xs:documentation xml:lang="en">other related cross border criminal activity other. DESCRIPTION:
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="40">
<xs:annotation>
<xs:documentation xml:lang="en">law infringement by vessels. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="41">
EUCISE2020
Page 291 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">illegal flight of an aircraft. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="42">
<xs:annotation>
<xs:documentation xml:lang="en">law infringement by vehicles. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="43">
<xs:annotation>
<xs:documentation xml:lang="en">other administrative offense. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other response not mentioned above</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Response not specified</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.89. schema data/Entity/Incident/CertaintyEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:simpleType name="CertaintyEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the certainty of an incident as defined by the OASIS common a
lerting protocol.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">observed. DESCRIPTION: Determined to have occurred or to be ongoi
ng</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">likely. DESCRIPTION: Likely (p &gt; ~50%)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">possible. DESCRIPTION: Possible but not likely (p &lt;= ~50%)</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">unlikely. DESCRIPTION: Not expected to occur (p ~ 0)</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">unknown. DESCRIPTION: Certainty unknown</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other certainty not mentioned above</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 292 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Certainty not specified</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.90. schema data/Entity/Incident/UrgencyEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:simpleType name="UrgencyEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the urgency of an incident response as defined by the OASIS c
ommon alerting protocol.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">immediate. DESCRIPTION: Responsive action should be taken immedia
tely</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">expected. DESCRIPTION: Responsive action should be taken soon (wi
thin next hour)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">future. DESCRIPTION: Responsive action should be taken in the nea
r future</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">past. DESCRIPTION: Responsive action is no longer required</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">unknown. DESCRIPTION: Urgency not known</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other urgency not mentioned above</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Urgency not specified</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.91. schema data/Entity/Incident/CrisisIncidentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:simpleType name="CrisisIncidentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the incident types related to crisis situations.</xs:document
EUCISE2020
Page 293 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
ation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">natural
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">natural
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">natural
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">natural
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">natural
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">natural
disaster tsunami. DESCRIPTION: </xs:documentation>
disaster earthquake. DESCRIPTION: </xs:documentation>
disaster heat wave. DESCRIPTION: </xs:documentation>
disaster wild fire. DESCRIPTION: </xs:documentation>
disaster flood. DESCRIPTION: </xs:documentation>
disaster volcanic eruption. DESCRIPTION: </xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">natural
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">natural
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">natural
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">natural
disaster storm. DESCRIPTION: </xs:documentation>
disaster snow storm. DESCRIPTION: </xs:documentation>
disaster tropical storm. DESCRIPTION: </xs:documentation>
disaster lightning strike. DESCRIPTION: </xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">natural
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">natural
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">natural
ard. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="14">
<xs:annotation>
<xs:documentation xml:lang="en">natural
</xs:annotation>
EUCISE2020
disaster landslide. DESCRIPTION: </xs:documentation>
disaster avalanche. DESCRIPTION: </xs:documentation>
disaster outbreak of infectious disease and other bio haz
disaster other. DESCRIPTION: </xs:documentation>
Page 294 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="15">
<xs:annotation>
<xs:documentation xml:lang="en">man made disaster man made fire. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="16">
<xs:annotation>
<xs:documentation xml:lang="en">man made disaster man made explosion. DESCRIPTION: </xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="17">
<xs:annotation>
<xs:documentation xml:lang="en">man made disaster maritime accident. DESCRIPTION: </xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="18">
<xs:annotation>
<xs:documentation xml:lang="en">man made disaster aircraft accident. DESCRIPTION: </xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="19">
<xs:annotation>
<xs:documentation xml:lang="en">man made disaster radiation. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="20">
<xs:annotation>
<xs:documentation xml:lang="en">man made disaster oil pollution. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="21">
<xs:annotation>
<xs:documentation xml:lang="en">man made disaster waste pollution. DESCRIPTION: </xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="22">
<xs:annotation>
<xs:documentation xml:lang="en">man made
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="23">
<xs:annotation>
<xs:documentation xml:lang="en">violence
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="24">
<xs:annotation>
<xs:documentation xml:lang="en">man made
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="25">
<xs:annotation>
<xs:documentation xml:lang="en">violence
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="26">
<xs:annotation>
<xs:documentation xml:lang="en">violence
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="27">
<xs:annotation>
<xs:documentation xml:lang="en">violence
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="28">
<xs:annotation>
EUCISE2020
disaster any other man made disaster. DESCRIPTION: </xs:
assassination. DESCRIPTION: </xs:documentation>
disaster terrorist attack. DESCRIPTION: </xs:documentati
bombing. DESCRIPTION: </xs:documentation>
disorder protest mutiny. DESCRIPTION: </xs:documentation
air missile attack. DESCRIPTION: </xs:documentation>
Page 295 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">violence
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="29">
<xs:annotation>
<xs:documentation xml:lang="en">violence
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="30">
<xs:annotation>
<xs:documentation xml:lang="en">violence
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="31">
<xs:annotation>
<xs:documentation xml:lang="en">violence
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="32">
<xs:annotation>
<xs:documentation xml:lang="en">violence
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="33">
<xs:annotation>
<xs:documentation xml:lang="en">violence
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="34">
<xs:annotation>
<xs:documentation xml:lang="en">violence
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="35">
<xs:annotation>
<xs:documentation xml:lang="en">violence
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="36">
<xs:annotation>
<xs:documentation xml:lang="en">violence
bio chemical attack. DESCRIPTION: </xs:documentation>
heavy weapons fire. DESCRIPTION: </xs:documentation>
shooting. DESCRIPTION: </xs:documentation>
stabbing. DESCRIPTION: </xs:documentation>
physical attack. DESCRIPTION: </xs:documentation>
execution. DESCRIPTION: </xs:documentation>
vandalism. DESCRIPTION: </xs:documentation>
robbery. DESCRIPTION: </xs:documentation>
kidnapping hostage taking. DESCRIPTION: </xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="37">
<xs:annotation>
<xs:documentation xml:lang="en">mines explosives. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="38">
<xs:annotation>
<xs:documentation xml:lang="en">armed conflict. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="39">
<xs:annotation>
<xs:documentation xml:lang="en">humanitarian crisis. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other response not mentioned above</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Response not specified</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
EUCISE2020
Page 296 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
2.92. schema data/Entity/Incident/ResponseEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:simpleType name="ResponseEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the incident’s response types as defined by the OASIS common
alerting protocol.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">shelter. DESCRIPTION: Take shelter in place or per &lt;instructio
n&gt;</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">evacuate. DESCRIPTION: Relocate as instructed in the &lt;instruct
ion&gt;</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">prepare. DESCRIPTION: Make preparations per the &lt;instruction&g
t;</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">execute. DESCRIPTION: Execute a pre-planned activity identified i
n &lt;instruction&gt;</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">avoid. DESCRIPTION: Avoid the subject event as per the &lt;instru
ction&gt;</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">monitor. DESCRIPTION: Attend to information sources as described
in &lt;instruction&gt;</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">assess. DESCRIPTION: Evaluate the information in this message. (T
his value SHOULD NOT be used in public warning applications.)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">all clear. DESCRIPTION: The subject event no longer poses a threa
t or concern and any follow on action is described in &lt;instruction&gt;</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">none. DESCRIPTION: No action recommended</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other response not mentioned above</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Response not specified</xs:documentat
ion>
EUCISE2020
Page 297 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.93. schema data/Entity/Incident/IrregularMigrationIncidentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:simpleType name="IrregularMigrationIncidentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the irregular migration incident types.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">irregular border entry. DESCRIPTION: Irregular border entry</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">event refused border entry. DESCRIPTION: Refused border entry</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">irregular entry attempt. DESCRIPTION: Irregular entry attempt</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">irregular border exit. DESCRIPTION: Irregular border exit</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">refused border entry. DESCRIPTION: Refused border entry</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">irregular exit attempt. DESCRIPTION: Irregular exit attempt</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">irregular stay. DESCRIPTION: Irregular stay</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">facilitator interception. DESCRIPTION: Facilitator interception</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">facilitator disclosure. DESCRIPTION: Facilitator disclosure</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">interception in third country territory. DESCRIPTION: Event::Inte
rception in third country territory</xs:documentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 298 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other incident not mentioned above</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Incident not specified</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.94. schema data/Entity/Incident/MaritimeSafetyIncidentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:include schemaLocation="IncidentType.xsd"/>
<xs:include schemaLocation="MaritimeSafetyIncidentEnumType.xsd"/>
<xs:complexType name="MaritimeSafetyIncidentType">
<xs:annotation>
<xs:documentation>The MaritimeSafetyIncident class is a sub-class of Incident and is used to determine ty
pes of incidents related to maritime safety as defined by the SafeSeaNet project.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="incident:IncidentType">
<xs:sequence>
<xs:element name="MaritimeSafetyIncidentType" type="incident:MaritimeSafetyIncidentEnumType" minO
ccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.95. schema data/Entity/Incident/MaritimeSafetyIncidentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:simpleType name="MaritimeSafetyIncidentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the maritime safety incident types.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">pollution. DESCRIPTION: Pollution</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">waste. DESCRIPTION: Waste</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">lost found containers. DESCRIPTION: Lost or Found Containers</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">VTS rules infringement. DESCRIPTION: VTS Rules Infringement</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">banned ship. DESCRIPTION: Banned Ship</xs:documentation>
EUCISE2020
Page 299 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">insurance failure. DESCRIPTION: Insurance Failure</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">result inspection. DESCRIPTION: Result Inspection</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">pilot or port report. DESCRIPTION: Pilot Or Port Report</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">fire. DESCRIPTION: Fire</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">collision. DESCRIPTION: Collision</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">medico. DESCRIPTION: Medico</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">grounding. DESCRIPTION: Grounding</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">flooding. DESCRIPTION: Flooding</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="14">
<xs:annotation>
<xs:documentation xml:lang="en">list. DESCRIPTION: List</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="15">
<xs:annotation>
<xs:documentation xml:lang="en">capsizing. DESCRIPTION: Capsizing</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="16">
<xs:annotation>
<xs:documentation xml:lang="en">engine failure. DESCRIPTION: Engine Failure</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="17">
<xs:annotation>
<xs:documentation xml:lang="en">structural failure. DESCRIPTION: Structural failure</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="18">
<xs:annotation>
<xs:documentation xml:lang="en">steering gear failure. DESCRIPTION: Steering gear failure</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="19">
<xs:annotation>
<xs:documentation xml:lang="en">electrical generating system failure. DESCRIPTION: Electrical gen
EUCISE2020
Page 300 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
erating system failure</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="20">
<xs:annotation>
<xs:documentation xml:lang="en">navigation equipment failure. DESCRIPTION: Navigation equipment f
ailure</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="21">
<xs:annotation>
<xs:documentation xml:lang="en">communication equipment failure. DESCRIPTION: Communication equip
ment failure</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="22">
<xs:annotation>
<xs:documentation xml:lang="en">incident nature abandon ship. DESCRIPTION: Abandon ship</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="23">
<xs:annotation>
<xs:documentation xml:lang="en">incident nature sinking. DESCRIPTION: Sinking</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="24">
<xs:annotation>
<xs:documentation xml:lang="en">detained ship. DESCRIPTION: DetainedShip</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other incident not mentioned above</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Incident not specified</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.96. schema data/Entity/Incident/IrregularMigrationIncidentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:include schemaLocation="IrregularMigrationIncidentEnumType.xsd"/>
<xs:include schemaLocation="IncidentType.xsd"/>
<xs:complexType name="IrregularMigrationIncidentType">
<xs:annotation>
<xs:documentation>The IrregularMigrationIncident class is a sub-class of Incident and is used to determin
e types of incidents related to irregular migration as defined by the EUROSUR project.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="incident:IncidentType">
<xs:sequence>
<xs:element name="IrregularMigrationIncidentType" type="incident:IrregularMigrationIncidentEnumTy
pe" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.97. schema data/Entity/Incident/PollutionIncidentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
EUCISE2020
Page 301 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
targetNamespace="http://www.cise.eu/datamodel/Entity/Incident/">
<xs:include schemaLocation="PollutionEnumType.xsd"/>
<xs:include schemaLocation="MaritimeSafetyIncidentType.xsd"/>
<xs:complexType name="PollutionIncidentType">
<xs:annotation>
<xs:documentation>The PollutionIncident is a type of Maritime Safety Incident and is used to exchange spe
cific information about pollution. The position and extend of the pollution can be described by the entity Location.<
/xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="incident:MaritimeSafetyIncidentType">
<xs:sequence>
<xs:element name="AreaCoverPercentage" type="xs:string" minOccurs="0"/>
<xs:element name="Characteristics" type="xs:string" minOccurs="0"/>
<xs:element name="DriftCourse" type="xs:int" minOccurs="0"/>
<xs:element name="DriftSpeed" type="xs:double" minOccurs="0"/>
<xs:element name="PollutionType" type="incident:PollutionEnumType" minOccurs="0"/>
<xs:element name="Quantity" type="xs:double" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.98. schema data/Entity/Object/VehicleType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Object/">
<xs:include schemaLocation="ObjectType.xsd"/>
<xs:complexType name="VehicleType" abstract="true">
<xs:annotation>
<xs:documentation>The Vehicle is a sub-class of Object and is used to determine types of physical moving
objects related to maritime. The class Vehicle inherits the attributes and relationships of Object. Vehicle has three
sub-classes: Vessel, Aircraft and LandVehicle.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="object:ObjectType">
<xs:sequence>
<xs:element name="MaximumSpeed" type="xs:double" minOccurs="0"/>
<xs:element name="Nationality" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="TotalPersonsOnBoard" type="xs:int" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.99. schema data/Entity/Object/LocationRoleEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Object/">
<xs:simpleType name="LocationRoleEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="001">
<xs:annotation>
<xs:documentation xml:lang="en">Port of embarkation. DESCRIPTION: Port of embarkation (for vessel
)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="002">
<xs:annotation>
<xs:documentation xml:lang="en">Port of disembarkation. DESCRIPTION: Port of disembarkation (for
vessel)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="003">
<xs:annotation>
<xs:documentation xml:lang="en">Port of registry. DESCRIPTION: Port of registry (for vessel)</xs:
documentation>
EUCISE2020
Page 302 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="004">
<xs:annotation>
<xs:documentation xml:lang="en">Lengthened place. DESCRIPTION: Lengthened place (for vessel)</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="005">
<xs:annotation>
<xs:documentation xml:lang="en">Port of loading. DESCRIPTION: Port of loading (for cargo)</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="006">
<xs:annotation>
<xs:documentation xml:lang="en">Port of discharge. DESCRIPTION: Port of discharge (for cargo)</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="999">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Non specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.100. schema data/Entity/Object/ColourEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Object/">
<xs:simpleType name="ColourEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="Cyan">
<xs:annotation>
<xs:documentation xml:lang="en">cyan. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Grey">
<xs:annotation>
<xs:documentation xml:lang="en">grey. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Yellow">
<xs:annotation>
<xs:documentation xml:lang="en">yellow. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="White">
<xs:annotation>
<xs:documentation xml:lang="en">white. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Black">
<xs:annotation>
<xs:documentation xml:lang="en">black. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Pink">
<xs:annotation>
<xs:documentation xml:lang="en">pink. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Green">
<xs:annotation>
<xs:documentation xml:lang="en">green. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Blue">
EUCISE2020
Page 303 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">blue. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Brown">
<xs:annotation>
<xs:documentation xml:lang="en">brown. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Orange">
<xs:annotation>
<xs:documentation xml:lang="en">orange. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Violet">
<xs:annotation>
<xs:documentation xml:lang="en">violet. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Red">
<xs:annotation>
<xs:documentation xml:lang="en">red. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.101. schema data/Entity/Object/AircraftType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Object/">
<xs:include schemaLocation="VehicleType.xsd"/>
<xs:complexType name="AircraftType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:complexContent>
<xs:extension base="object:VehicleType">
<xs:sequence>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.102. schema data/Entity/Object/PlannedWorksEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Object/">
<xs:simpleType name="PlannedWorksEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible planned works which can explain that an Object i
s at a Location.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">inspection. DESCRIPTION: The Object is at a Location for Inspecti
on</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">maintenance and repair. DESCRIPTION: The Object is at a Location
for Maintenance and repair</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other works not mentioned above</xs:docum
entation>
EUCISE2020
Page 304 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Works not specified</xs:documentation
>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.103. schema data/Entity/Object/PlacementPurposeEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Object/">
<xs:simpleType name="PlacementPurposeEnumType">
<xs:annotation>
<xs:documentation>This enumeration describes the reason of placement of an object to a location. An objec
t can be at a location because it is in transit. A vessel (i.e. an object) can also be assigned to a location.</xs:do
cumentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">in transit. DESCRIPTION: The Object is at a Location during a tra
nsit</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">assigned. DESCRIPTION: The Object is assigned to the Location</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other type not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Type not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.104. schema data/Entity/Object/LandVehicleType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Object/">
<xs:include schemaLocation="VehicleType.xsd"/>
<xs:complexType name="LandVehicleType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:complexContent>
<xs:extension base="object:VehicleType">
<xs:sequence>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.105. schema data/Entity/Object/PlannedOperationsEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
EUCISE2020
Page 305 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Object/">
<xs:simpleType name="PlannedOperationsEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible planned operations for which an Object is at a L
ocation.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">loading. DESCRIPTION: The Object is at the Location to load cargo
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">unloading. DESCRIPTION: The Object is at the Location to unload c
argo</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other operation not mentioned above</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Operation not specified</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.106. schema data/Entity/Object/SensorEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Object/">
<xs:simpleType name="SensorEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the Sensor at the origin of an association between an Object
and a Location.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">sighting. DESCRIPTION: The Object is observed at the Location</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">underwater sensor. DESCRIPTION: Underwater sensor</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">maritime radar. DESCRIPTION: Maritime radar</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">synthetic aperture radar. DESCRIPTION: Synthetic aperture radar</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">EOIR optronic system. DESCRIPTION: EO/IR Optronic system</xs:docu
mentation>
</xs:annotation>
EUCISE2020
Page 306 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">maritime moving target identification. DESCRIPTION: Maritime movi
ng target identification</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">signal interception systems COMINT. DESCRIPTION: Signal intercept
ion systems COMINT</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">signal interception systems ELINT. DESCRIPTION: Signal intercepti
on systems ELINT</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">environmental sensing systems. DESCRIPTION: Environmental sensing
systems</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">automatic identification system. DESCRIPTION: Automatic Identific
ation System (AIS)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">vessel monitoring system. DESCRIPTION: Vessel monitoring system (
VMS)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">long range identification tracking. DESCRIPTION: Long range ident
ification and tracking (LRIT)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">automatic vehicle location. DESCRIPTION: Automatic vehicle locati
on (AVL)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="14">
<xs:annotation>
<xs:documentation xml:lang="en">acoustic systems. DESCRIPTION: Acoustic Systems ACINT</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="15">
<xs:annotation>
<xs:documentation xml:lang="en">non-traditional sources. DESCRIPTION: Non-traditional sources</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other sensor not mentioned above</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Sensor not specified</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
EUCISE2020
Page 307 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:simpleType>
</xs:schema>
2.107. schema data/Entity/Object/ObjectType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" xml
ns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:metadata="http://www.cise.eu/datamodel/Entity/Metadata/" xmlns
:uniqueidentifier="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" targetNamespace="http://www.cise.eu/datamod
el/Entity/Object/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Metadata/" schemaLocation="../Metadata/Metadata.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" schemaLocation="../UniqueIdentifier/
UniqueIdentifierType.xsd"/>
<xs:include schemaLocation="ColourEnumType.xsd"/>
<xs:complexType name="ObjectType" abstract="true">
<xs:annotation>
<xs:documentation>The Object entity is one of the core entities of the overall data model. It is an abstr
act entity (it cannot been used as such) that holds information about physical entities from the maritime domain like
vehicles (vessels, aircrafts and land vehicles) and cargo. Object has relationships with Event, Agent, Document, Risk
and Location. Object can also be associated with another Object.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Colour" type="object:ColourEnumType" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="ExternalMarkings" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="Identifier" type="uniqueidentifier:UniqueIdentifierType" minOccurs="0"/>
<xs:element name="Metadata" type="metadata:Metadata" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="Name" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.108. schema data/Entity/Object/SourceEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Object/">
<xs:simpleType name="SourceEnumType">
<xs:annotation>
<xs:documentation>This enumeration defines how the placement of an object to a location has been determin
ed. The location of an object can be observed, declared, estimated or simulated.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">observation. DESCRIPTION: The location of the object is observed<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">declaration. DESCRIPTION: The location of the object is declared<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">estimation. DESCRIPTION: The location of the object is estimated<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">simulation. DESCRIPTION: The location of the object is simulated<
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">correlation. DESCRIPTION: The location of the object has been cor
EUCISE2020
Page 308 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
related</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other type not mentioned above</xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Type not specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.109. schema data/Entity/UniqueIdentifier/UniqueIdentifierType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:uniqueidentifier="http://www.cise.eu/datamodel/Entity/Un
iqueIdentifier/" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organization/" targetNamespace="http://www.c
ise.eu/datamodel/Entity/UniqueIdentifier/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Organization/" schemaLocation="../Organization/Organiza
tionType.xsd"/>
<xs:complexType name="UniqueIdentifierType">
<xs:annotation>
<xs:documentation>The Unique Identifier is a fundamental entity of the overall data model of the informat
ion sharing environment, since it will allow, as it name implies, to uniquely identify each and every single data obj
ect exchanged through the network. With this identifier it will also be possible for the legacy systems to keep trace
of the relationships between their data objects and those from the information sharing environment. It will be possib
le to understand who and when is publishing each and every data object in the network.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="GeneratedBy" type="organization:OrganizationType" minOccurs="0"/>
<xs:element name="GeneratedIn" type="xs:dateTime" minOccurs="0"/>
<xs:element name="UUID" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
2.110. schema data/Entity/UniqueIdentifier/CorrelationEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:uniqueidentifier="http://www.cise.eu/datamodel/Entity/Un
iqueIdentifier/" targetNamespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/">
<xs:simpleType name="CorrelationEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of processes used to perform the objects c
orrelation.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">manual. DESCRIPTION: Correlation performed by an operator</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">automatic. DESCRIPTION: Correlation performed automatically by a
system</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Correlation performed by any other process no
t listed here</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: The correlation process is not declar
EUCISE2020
Page 309 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
ed</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.111. schema data/Entity/Person/PersonIdentificationEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:person="http://www.cise.eu/datamodel/Entity/Person/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Person/">
<xs:simpleType name="PersonIdentificationEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">identity card. DESCRIPTION: Identity Card</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">social security card. DESCRIPTION: Social Security Card</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">passport. DESCRIPTION: Passport</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">fiscal document. DESCRIPTION: Fiscal Document</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">VISA. DESCRIPTION: Visa International Service Association Card</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">crew master book. DESCRIPTION: Crew Master Book</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Other value not included in the list</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Not Specified</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.112. schema data/Entity/Person/PersonType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:person="http://www.cise.eu/datamodel/Entity/Person/" xml
ns:agent="http://www.cise.eu/datamodel/Entity/Agent/" targetNamespace="http://www.cise.eu/datamodel/Entity/Person/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Agent/AgentType.xsd"/>
<xs:include schemaLocation="GenderEnumType.xsd"/>
<xs:include schemaLocation="PersonIdentifier.xsd"/>
<xs:complexType name="PersonType">
EUCISE2020
Page 310 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation>The Person Class is a sub class of the more general 'Agent' class that encompasses orga
nizations, legal entities, groups etc. - any entity that is able to carry out actions. The data type properties of th
e Person class do not have any cardinality restrictions and as such all are optional. However, guidance is provided f
or the usage of each property in the following sections.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="agent:AgentType">
<xs:sequence>
<xs:element name="AlternativeName" type="xs:string" minOccurs="0"/>
<xs:element name="BirthDate" type="xs:date" minOccurs="0"/>
<xs:element name="BirthName" type="xs:string" minOccurs="0"/>
<xs:element name="DateOfDeath" type="xs:dateTime" minOccurs="0"/>
<xs:element name="FamilyName" type="xs:string" minOccurs="0"/>
<xs:element name="FullName" type="xs:string" minOccurs="0"/>
<xs:element name="Gender" type="person:GenderEnumType" minOccurs="0"/>
<xs:element name="GivenName" type="xs:string" minOccurs="0"/>
<xs:element name="PatronymicName" type="xs:string" minOccurs="0"/>
<xs:element name="PersonIdentifiers" type="person:PersonIdentifier" minOccurs="0" maxOccurs="unbo
unded"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.113. schema data/Entity/Person/GenderEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:person="http://www.cise.eu/datamodel/Entity/Person/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Person/">
<xs:simpleType name="GenderEnumType">
<xs:annotation>
<xs:documentation>The gender of an individual.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">female. DESCRIPTION: Female</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">male. DESCRIPTION: Male</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Other gender, not male neither female</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">unknown. DESCRIPTION: Unknown</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">not applicable. DESCRIPTION: Not Applicable</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.114. schema data/Entity/Person/PersonIdentifier.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:person="http://www.cise.eu/datamodel/Entity/Person/" tar
getNamespace="http://www.cise.eu/datamodel/Entity/Person/">
<xs:include schemaLocation="PersonIdentificationEnumType.xsd"/>
<xs:complexType name="PersonIdentifier">
<xs:annotation>
EUCISE2020
Page 311 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation>The PersonIdentifier class allows the identification of the Person by means of a docume
nt of given type and related id number, according to the different countries policy.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="IdentifierType" type="person:PersonIdentificationEnumType" minOccurs="0"/>
<xs:element name="IdentifierValue" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
2.115. schema data/Entity/Document/CargoDocumentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:include schemaLocation="AttachedDocumentType.xsd"/>
<xs:include schemaLocation="CargoDocumentEnumType.xsd"/>
<xs:complexType name="CargoDocumentType">
<xs:annotation>
<xs:documentation>This sub-class allows the identification and exchange of Cargo related documents and ma
terial in electronic format.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="document:AttachedDocumentType">
<xs:sequence>
<xs:element name="DocumentType" type="document:CargoDocumentEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.116. schema data/Entity/Document/PersonDocumentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:include schemaLocation="AttachedDocumentType.xsd"/>
<xs:include schemaLocation="PersonDocumentEnumType.xsd"/>
<xs:complexType name="PersonDocumentType">
<xs:annotation>
<xs:documentation>This sub-class allows the identification and exchange of Person related documents and m
aterial in electronic format.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="document:AttachedDocumentType">
<xs:sequence>
<xs:element name="DocumentType" type="document:PersonDocumentEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.117. schema data/Entity/Document/OrganizationDocumentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:include schemaLocation="AttachedDocumentType.xsd"/>
<xs:include schemaLocation="OrganizationDocumentEnumType.xsd"/>
<xs:complexType name="OrganizationDocumentType">
<xs:annotation>
<xs:documentation>This sub-class allows the identification and exchange of Organization related documents
and material in electronic format.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="document:AttachedDocumentType">
<xs:sequence>
<xs:element name="DocumentType" type="document:OrganizationDocumentEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
EUCISE2020
Page 312 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:complexType>
</xs:schema>
2.118. schema data/Entity/Document/StreamEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:simpleType name="StreamEnumType">
<xs:annotation>
<xs:documentation>Types of streams. Each type is associated to a specific standard.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="Video">
<xs:annotation>
<xs:documentation xml:lang="en">video. DESCRIPTION: Video stream in format MPEG4 H264</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ImageMap">
<xs:annotation>
<xs:documentation xml:lang="en">image map. DESCRIPTION: Image map in format WMS</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="VectorialMap">
<xs:annotation>
<xs:documentation xml:lang="en">vectorial map. DESCRIPTION: Vectorial map in format WFS</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Radar">
<xs:annotation>
<xs:documentation xml:lang="en">radar. DESCRIPTION: VTS exchange format IVEF</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="AIS">
<xs:annotation>
<xs:documentation xml:lang="en">AIS. DESCRIPTION: Stream format in ITU-RM1371</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.119. schema data/Entity/Document/VesselDocumentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:include schemaLocation="AttachedDocumentType.xsd"/>
<xs:include schemaLocation="VesselDocumentEnumType.xsd"/>
<xs:complexType name="VesselDocumentType">
<xs:annotation>
<xs:documentation>This sub-class allows the identification and exchange of Vessel related documents and m
aterial in electronic format.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="document:AttachedDocumentType">
<xs:sequence>
<xs:element name="DocumentType" type="document:VesselDocumentEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.120. schema data/Entity/Document/LocationDocumentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:include schemaLocation="AttachedDocumentType.xsd"/>
EUCISE2020
Page 313 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:include schemaLocation="LocationDocumentEnumType.xsd"/>
<xs:complexType name="LocationDocumentType">
<xs:annotation>
<xs:documentation>This sub-class allows the identification and exchange of Location related documents and
material in electronic format.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="document:AttachedDocumentType">
<xs:sequence>
<xs:element name="DocumentType" type="document:LocationDocumentEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.121. schema data/Entity/Document/CertificateDocumentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:include schemaLocation="AttachedDocumentType.xsd"/>
<xs:include schemaLocation="CertificateDocumentEnumType.xsd"/>
<xs:complexType name="CertificateDocumentType">
<xs:annotation>
<xs:documentation>This sub-class allows the identification and exchange of Certificate related documents
and material in electronic format.||Subclass of Document.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="document:AttachedDocumentType">
<xs:sequence>
<xs:element name="DocumentType" type="document:CertificateDocumentEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.122. schema data/Entity/Document/DocumentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:metadata="http://www.cise.eu/datamodel/Entity/Metadata/" xm
lns:uniqueidentifier="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" targetNamespace="http://www.cise.eu/data
model/Entity/Document/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Metadata/" schemaLocation="../Metadata/Metadata.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" schemaLocation="../UniqueIdentifier/
UniqueIdentifierType.xsd"/>
<xs:complexType name="DocumentType" abstract="true">
<xs:annotation>
<xs:documentation>The Document is one of the fundamental entities of the overall data model of the inform
ation sharing environment. A Document allows tracing and exchanging information in a persistent manner in almost any
possible electronic format; this information is expected to provide details on and express specific associations betw
een other Entity Classes such as Agents, Objects, Events, Risks, Locations etc.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Identifier" type="uniqueidentifier:UniqueIdentifierType" minOccurs="0"/>
<xs:element name="Metadata" type="metadata:Metadata" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="Subject" type="xs:string" minOccurs="0"/>
<xs:element name="Title" type="xs:string" minOccurs="0"/>
<xs:element name="Version" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.123. schema data/Entity/Document/RiskDocumentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
EUCISE2020
Page 314 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:include schemaLocation="AttachedDocumentType.xsd"/>
<xs:include schemaLocation="RiskDocumentEnumType.xsd"/>
<xs:complexType name="RiskDocumentType">
<xs:annotation>
<xs:documentation>This sub-class allows the identification and exchange of Risk related documents and mat
erial in electronic format.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="document:AttachedDocumentType">
<xs:sequence>
<xs:element name="DocumentType" type="document:RiskDocumentEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.124. schema data/Entity/Document/CargoDocumentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:simpleType name="CargoDocumentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of documents related to cargo.</xs:documen
tation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">cargo manifest. DESCRIPTION: Basic information about the cargo. W
ould include also links to further information: bill of lading, cargo bill, liner way bill</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">VAT exception. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">entry summary declaration. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">IMOFAL form2 cargo declaration. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">IMOFAL form3 ships stores declaration. DESCRIPTION: </xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">IMOFAL form4 crews effects declaration. DESCRIPTION: </xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">notification of dangerous goods. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">IMOFAL form7 dangerous goods. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
EUCISE2020
Page 315 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">single administrative document. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">catch certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">fishing logbook. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.125. schema data/Entity/Document/AttachedDocumentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:include schemaLocation="DocumentType.xsd"/>
<xs:complexType name="AttachedDocumentType" abstract="true">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:complexContent>
<xs:extension base="document:DocumentType">
<xs:sequence>
<xs:element name="Content" type="xs:base64Binary" minOccurs="0"/>
<xs:element name="Hash" type="xs:hexBinary" minOccurs="0"/>
<xs:element name="ReferenceURI" type="xs:anyURI" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.126. schema data/Entity/Document/CertificateDocumentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:simpleType name="CertificateDocumentEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">tonnage certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">load line certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">minimum safe manning document. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 316 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">oil pollution prevention certificate. DESCRIPTION: </xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">sewage pollution prevention certificate. DESCRIPTION: </xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">VDR compliance certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">ISM compliance document. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">safety management certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">ISS certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">PSS certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">STPS sa certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">STPS sp certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">CSS construction certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="14">
<xs:annotation>
<xs:documentation xml:lang="en">CSS equipment certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="15">
<xs:annotation>
<xs:documentation xml:lang="en">CSS radio certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="16">
<xs:annotation>
<xs:documentation xml:lang="en">CSS certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="17">
<xs:annotation>
<xs:documentation xml:lang="en">grain authorization document. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="18">
<xs:annotation>
<xs:documentation xml:lang="en">civil liability certificate. DESCRIPTION: </xs:documentation>
EUCISE2020
Page 317 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="19">
<xs:annotation>
<xs:documentation xml:lang="en">enhanced survey document. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="20">
<xs:annotation>
<xs:documentation xml:lang="en">NLS certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="21">
<xs:annotation>
<xs:documentation xml:lang="en">bulk chemicals carriage certificate. DESCRIPTION: </xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="22">
<xs:annotation>
<xs:documentation xml:lang="en">int bulk chemicals carriage certificate. DESCRIPTION: </xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="23">
<xs:annotation>
<xs:documentation xml:lang="en">bulk liquid gas certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="24">
<xs:annotation>
<xs:documentation xml:lang="en">int bulk liquid gas certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="25">
<xs:annotation>
<xs:documentation xml:lang="en">HSC safety certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="26">
<xs:annotation>
<xs:documentation xml:lang="en">HSC operation permit. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="27">
<xs:annotation>
<xs:documentation xml:lang="en">IMDG certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="28">
<xs:annotation>
<xs:documentation xml:lang="en">INF certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="29">
<xs:annotation>
<xs:documentation xml:lang="en">registry certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="30">
<xs:annotation>
<xs:documentation xml:lang="en">hull class certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="31">
<xs:annotation>
<xs:documentation xml:lang="en">engine class certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="32">
<xs:annotation>
<xs:documentation xml:lang="en">pand I certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="33">
EUCISE2020
Page 318 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">ILO133 certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="34">
<xs:annotation>
<xs:documentation xml:lang="en">ILO92 certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="35">
<xs:annotation>
<xs:documentation xml:lang="en">ITF blue card. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="36">
<xs:annotation>
<xs:documentation xml:lang="en">declaration of health. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="37">
<xs:annotation>
<xs:documentation xml:lang="en">gas free certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="38">
<xs:annotation>
<xs:documentation xml:lang="en">de rat certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="39">
<xs:annotation>
<xs:documentation xml:lang="en">certificate. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.127. schema data/Entity/Document/EventDocumentType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:include schemaLocation="AttachedDocumentType.xsd"/>
<xs:include schemaLocation="EventDocumentEnumType.xsd"/>
<xs:complexType name="EventDocumentType">
<xs:annotation>
<xs:documentation>This sub-class allows the identification and exchange of Event related documents and ma
terial in electronic format.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="document:AttachedDocumentType">
<xs:sequence>
<xs:element name="DocumentType" type="document:EventDocumentEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.128. schema data/Entity/Document/LocationDocumentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
EUCISE2020
Page 319 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:simpleType name="LocationDocumentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of documents related to a location.</xs:do
cumentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">port law. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">port regulations. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">port services. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">port facilities. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">port dues. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">port infrastructures. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">port planning and development. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">operational infrastructures. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">maritime access. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">marine services and facilities. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">harbormaster. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">hydrographic map. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">maritime infrastructures. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="14">
<xs:annotation>
<xs:documentation xml:lang="en">meteorological maps. DESCRIPTION: </xs:documentation>
EUCISE2020
Page 320 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="15">
<xs:annotation>
<xs:documentation xml:lang="en">oceanographic maps per season. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="16">
<xs:annotation>
<xs:documentation xml:lang="en">legal maps. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="17">
<xs:annotation>
<xs:documentation xml:lang="en">marine resources. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="18">
<xs:annotation>
<xs:documentation xml:lang="en">marine resources potential. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="19">
<xs:annotation>
<xs:documentation xml:lang="en">remnent pollution. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="20">
<xs:annotation>
<xs:documentation xml:lang="en">seabed hazards. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="21">
<xs:annotation>
<xs:documentation xml:lang="en">natura2000 areas. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="22">
<xs:annotation>
<xs:documentation xml:lang="en">areas MARPOL. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="23">
<xs:annotation>
<xs:documentation xml:lang="en">location of areas with rich archaeological heritage. DESCRIPTION:
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="24">
<xs:annotation>
<xs:documentation xml:lang="en">location of PSSA particulary sensitive areas. DESCRIPTION: </xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="25">
<xs:annotation>
<xs:documentation xml:lang="en">location of other types of marine protected areas. DESCRIPTION: <
/xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="26">
<xs:annotation>
<xs:documentation xml:lang="en">location of sensitive areas for cetaceans and type of restriction
s for maritime operations according national laws. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="27">
<xs:annotation>
<xs:documentation xml:lang="en">change frequency of observations of endangered and protected spec
ies. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="28">
<xs:annotation>
<xs:documentation xml:lang="en">locations of migratory paths or routes. DESCRIPTION: </xs:documen
EUCISE2020
Page 321 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="29">
<xs:annotation>
<xs:documentation xml:lang="en">sea state wind and current information. DESCRIPTION: </xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="30">
<xs:annotation>
<xs:documentation xml:lang="en">sea surface temperature information. DESCRIPTION: </xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="31">
<xs:annotation>
<xs:documentation xml:lang="en">air temperature information. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="32">
<xs:annotation>
<xs:documentation xml:lang="en">visibility information. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="33">
<xs:annotation>
<xs:documentation xml:lang="en">wave height information. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="34">
<xs:annotation>
<xs:documentation xml:lang="en">global region tides information. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="35">
<xs:annotation>
<xs:documentation xml:lang="en">ice information. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="36">
<xs:annotation>
<xs:documentation xml:lang="en">currentsm salinity temperature opacity at different depth. DESCRI
PTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="37">
<xs:annotation>
<xs:documentation xml:lang="en">chemical concentrations in water column. DESCRIPTION: </xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="38">
<xs:annotation>
<xs:documentation xml:lang="en">elaborated sectoral information. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="39">
<xs:annotation>
<xs:documentation xml:lang="en">emerging areas rich in nutrients and particular marine currents.
DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="40">
<xs:annotation>
<xs:documentation xml:lang="en">real time closure of fishing areas. DESCRIPTION: </xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="41">
<xs:annotation>
<xs:documentation xml:lang="en">information about past piracy incidents. DESCRIPTION: </xs:docume
ntation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 322 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="42">
<xs:annotation>
<xs:documentation xml:lang="en">maps of piracy incident distribution. DESCRIPTION: </xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="43">
<xs:annotation>
<xs:documentation xml:lang="en">maps of ship traffic distribution per ship type and per season. D
ESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="44">
<xs:annotation>
<xs:documentation xml:lang="en">shore bases of pirates and their current activity level. DESCRIPT
ION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="45">
<xs:annotation>
<xs:documentation xml:lang="en">actual locations of merchant and fishing ships. DESCRIPTION: </xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="46">
<xs:annotation>
<xs:documentation xml:lang="en">actual locations of naval patrol ships. DESCRIPTION: </xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="47">
<xs:annotation>
<xs:documentation xml:lang="en">pirate ships atacks locations. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="48">
<xs:annotation>
<xs:documentation xml:lang="en">locations of bases of patrol assets. DESCRIPTION: </xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="49">
<xs:annotation>
<xs:documentation xml:lang="en">maps of past non-piracy incidents distribution not only on sea bu
t also on the shores. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.129. schema data/Entity/Document/VesselDocumentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:simpleType name="VesselDocumentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of electronic material that can be related
to individual vessels.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="001">
<xs:annotation>
<xs:documentation xml:lang="en">international tonnage certificate. DESCRIPTION: An International
EUCISE2020
Page 323 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
Tonnage Certificate (1969) shall be issued to every ship, the gross and net tonnage of which have been determined in
accordance with the Convention (Tonnage Convention, article 7).</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="002">
<xs:annotation>
<xs:documentation xml:lang="en">international load line certificate. DESCRIPTION: An Internationa
l Load Line Certificate shall be issued under the provisions of the International Convention on Load Lines, 1966, to
every ship which has been surveyed and marked in accordance with the Convention or the Convention as modified by the
1988 LL Protocol, as appropriate (LL Convention, article 16; 1988 LL Protocol, article 16).</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="003">
<xs:annotation>
<xs:documentation xml:lang="en">international load line exemption certificate. DESCRIPTION: An In
ternational Load Line Exemption Certificate shall be issued to any ship to which an exemption has been granted under
and in accordance with article 6 of the Load Line Convention or the Convention as modified by the 1988 LL Protocol, a
s appropriate\n(LL Convention, article 6; 1988 LL Protocol, article 16)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="004">
<xs:annotation>
<xs:documentation xml:lang="en">coating technical file. DESCRIPTION: A Coating Technical File, co
ntaining specifications of the coating system applied to dedicated seawater ballast tanks in all types of ships and d
ouble-side skin spaces of bulk carriers of 150 m in length and upwards, record of the shipyard's and shipowner's coat
ing work, detailed criteria for coating sections, job specifications, inspection, maintenance and repair, shall be ke
pt on board and maintained throughout the life of the ship\n(SOLAS 1974, regulation II-1/3-2; Performance standard fo
r protective coatings for dedicated seawater ballast tanks in all types of ships and double-side skin spaces of bulk
carriers (resolution MSC.215(82)))</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="005">
<xs:annotation>
<xs:documentation xml:lang="en">construction drawings. DESCRIPTION: A set of as-built constructio
n drawings and other plans showing any subsequent structural alterations shall be kept on board a ship constructed on
or after 1 January 2007\n(SOLAS 1974, regulation II-1/3-7; MSC/Circ.1135 on As-built construction drawings to be main
tained on board the ship and ashore)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="006">
<xs:annotation>
<xs:documentation xml:lang="en">ship construction file. DESCRIPTION: A Ship Construction File wit
h specific information should be kept on board oil tankers of 150 m in length and above and bulk carriers of 150 m in
length and above, constructed with single deck, top-side tanks and hopper side tanks in cargo spaces, excluding ore c
arriers and combination carriers:\n.1 for which the building contract is placed on or after 1 July 2016;\n.2 in the a
bsence of a building contract, the keels of which are laid or which are at a similar stage of construction on or afte
r 1 July 2017; or\n.3 the delivery of which is on or after 1 July 2020 shall carry a Ship Construction File containin
g information in accordance with regulations and guidelines,\nand updated as appropriate throughout the ship's life i
n order to facilitate safe operation, maintenance, survey, repair and emergency measures.\n(SOLAS 1974, regulation II
-1/3-10; MSC.1/Circ.1343 on Guidelines for the information to be included in a Ship Construction File)</xs:documentat
ion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="007">
<xs:annotation>
<xs:documentation xml:lang="en">intact stability booklet. DESCRIPTION: Every passenger ship regar
dless of size and every cargo ship of 24 metres and over shall be inclined on completion and the elements of their st
ability determined. The master shall be supplied with a Stability Booklet containing such information as is necessary
to enable him, by rapid and simple procedures, to obtain accurate guidance as to the stability of the ship under vary
ing conditions of service. For bulk carriers, the information required in a bulk carrier booklet may be contained in
the stability booklet.\n(SOLAS 1974, regulations II-1/5 and II-1/5-1; LL Convention; 1988 LL Protocol, regulation 10)
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="008">
<xs:annotation>
<xs:documentation xml:lang="en">damage control plans and booklets. DESCRIPTION: On passenger and
cargo ships, there shall be permanently exhibited plans showing clearly for each deck and hold the boundaries of the
watertight compartments, the openings therein with the means of closure and position of any controls thereof, and the
arrangements for the correction of any list due to flooding. Booklets containing the aforementioned information shall
be made available to the officers of the ship.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="009">
<xs:annotation>
EUCISE2020
Page 324 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation xml:lang="en">minimum safe manning document. DESCRIPTION: Every ship to which c
hapter I of the Convention applies shall be provided with an appropriate safe manning document or equivalent issued b
y the Administration as evidence of the minimum safe manning.\n(SOLAS 1974, regulation V/14.2)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="010">
<xs:annotation>
<xs:documentation xml:lang="en">fire safety training manual. DESCRIPTION: A training manual shall
be written in the working language of the ship and shall be provided in each crew mess room and recreation room or in
each crew cabin. The manual shall contain the instructions and information required in regulation II-2/15.2.3.4. Part
of such information may be provided in the form of audio-visual aids in lieu of the manual.\n(SOLAS 1974, regulation
II-2/15.2.3)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="011">
<xs:annotation>
<xs:documentation xml:lang="en">fire control plan booklet. DESCRIPTION: General arrangement plans
shall be permanently exhibited for the guidance of the ship's officers, showing clearly for each deck the control sta
tions, the various fire sections together with particulars of the fire detection and fire alarm systems and the fireextinguishing appliances, etc. Alternatively, at the discretion of the Administration, the aforementioned details may
be set out in a booklet, a copy of which shall be supplied to each officer, and one copy shall at all times be availa
ble on board in an accessible position. Plans and booklets shall be kept up to date; any alterations shall be recorde
d as soon as practicable. A duplicate set of fire control plans or a booklet containing such plans shall be permanent
ly stored in a prominently marked weathertight enclosure outside the deckhouse for the assistance of shore-side firefighting personnel.\n(SOLAS 1974, regulations II-2/15.2.4 and II-2/15.3.2)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="012">
<xs:annotation>
<xs:documentation xml:lang="en">onboard training and drills record. DESCRIPTION: Fire drills shal
l be conducted and recorded in accordance with the provisions of regulations III/19.3 and III/19.5.\n(SOLAS 1974, reg
ulation II-2/15.2.2.5)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="013">
<xs:annotation>
<xs:documentation xml:lang="en">fire safety operational booklet. DESCRIPTION: The fire safety ope
rational booklet shall contain the necessary information and instructions for the safe operation of the ship and carg
o handling operations in relation to fire safety. The booklet shall be written in the working language of the ship an
d be provided in each crew mess room and recreation room or in each crew cabin. The booklet may be combined with the
fire safety training manuals required in regulation II-2/15.2.3.\n(SOLAS 1974, regulation II-2/16.2)</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="014">
<xs:annotation>
<xs:documentation xml:lang="en">maintenance plans. DESCRIPTION: The maintenance plan shall includ
e the necessary information about fire protection systems and fire-fighting systems and appliances as required under
regulation II-2/14.2.2. For tankers, additional requirements are referred to in regulation II-2/14.4.\n(SOLAS 1974, r
egulations II-2/14.2.2 and II-2/14.4)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="015">
<xs:annotation>
<xs:documentation xml:lang="en">training manual. DESCRIPTION: refer to document: IMO FSI 21/18, R
eport to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-M
SC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="016">
<xs:annotation>
<xs:documentation xml:lang="en">records of navigational activities. DESCRIPTION: refer to documen
t: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, d
raft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="017">
<xs:annotation>
<xs:documentation xml:lang="en">manoeuvring booklet. DESCRIPTION: refer to document: IMO FSI 21/1
8, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC
.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="018">
EUCISE2020
Page 325 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">certificates for masters officers or ratings. DESCRIPTION: refer
to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee;
ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ship
s</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="019">
<xs:annotation>
<xs:documentation xml:lang="en">records of hours of rest. DESCRIPTION: refer to document: IMO FSI
21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="020">
<xs:annotation>
<xs:documentation xml:lang="en">international oil pollution prevention certificate. DESCRIPTION:
refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Commi
ttee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on boar
d ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="021">
<xs:annotation>
<xs:documentation xml:lang="en">oil record book. DESCRIPTION: refer to document: IMO FSI 21/18, R
eport to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-M
SC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="022">
<xs:annotation>
<xs:documentation xml:lang="en">ship board oil pollution emergency plan. DESCRIPTION: refer to do
cument: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX
1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="023">
<xs:annotation>
<xs:documentation xml:lang="en">international sewage pollution prevention certificate. DESCRIPTIO
N: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Co
mmittee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on b
oard ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="024">
<xs:annotation>
<xs:documentation xml:lang="en">garbage management plan. DESCRIPTION: refer to document: IMO FSI
21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="025">
<xs:annotation>
<xs:documentation xml:lang="en">garbage record book. DESCRIPTION: refer to document: IMO FSI 21/1
8, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC
.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="026">
<xs:annotation>
<xs:documentation xml:lang="en">voyage data recorder system certificate of compliance. DESCRIPTIO
N: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Co
mmittee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on b
oard ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="027">
<xs:annotation>
<xs:documentation xml:lang="en">cargo securing manual. DESCRIPTION: refer to document: IMO FSI 21
/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-ME
PC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="028">
EUCISE2020
Page 326 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">document of compliance. DESCRIPTION: refer to document: IMO FSI 2
1/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-M
EPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="029">
<xs:annotation>
<xs:documentation xml:lang="en">safety management certificate. DESCRIPTION: refer to document: IM
O FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft
FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="030">
<xs:annotation>
<xs:documentation xml:lang="en">international ship security certificate. DESCRIPTION: refer to do
cument: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX
1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="031">
<xs:annotation>
<xs:documentation xml:lang="en">interim international ship security certificate. DESCRIPTION: ref
er to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committe
e; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board s
hips</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="032">
<xs:annotation>
<xs:documentation xml:lang="en">ship security plan and associated records. DESCRIPTION: refer to
document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANN
EX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="033">
<xs:annotation>
<xs:documentation xml:lang="en">continuous synopsis record. DESCRIPTION: refer to document: IMO F
SI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL
.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="034">
<xs:annotation>
<xs:documentation xml:lang="en">international anti fouling system certificate. DESCRIPTION: refer
to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee;
ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ship
s</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="035">
<xs:annotation>
<xs:documentation xml:lang="en">declaration on anti fouling system. DESCRIPTION: refer to documen
t: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, d
raft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="036">
<xs:annotation>
<xs:documentation xml:lang="en">international air pollution prevention certificate. DESCRIPTION:
refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Commi
ttee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on boar
d ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="037">
<xs:annotation>
<xs:documentation xml:lang="en">ozone depleting substances record book. DESCRIPTION: refer to doc
ument: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX
1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:
EUCISE2020
Page 327 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="038">
<xs:annotation>
<xs:documentation xml:lang="en">fuel oil change over procedure and logbook. DESCRIPTION: refer to
document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANN
EX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="039">
<xs:annotation>
<xs:documentation xml:lang="en">manufacturers operating manual for incinerators. DESCRIPTION: ref
er to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committe
e; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board s
hips</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="040">
<xs:annotation>
<xs:documentation xml:lang="en">bunker delivery noe and representative sample. DESCRIPTION: refer
to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee;
ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ship
s</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="041">
<xs:annotation>
<xs:documentation xml:lang="en">technical file- marine diesel engine. DESCRIPTION: refer to docum
ent: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1,
draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="042">
<xs:annotation>
<xs:documentation xml:lang="en">record book of engine parameters. DESCRIPTION: refer to document:
IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draf
t FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="043">
<xs:annotation>
<xs:documentation xml:lang="en">exemption certificate. DESCRIPTION: refer to document: IMO FSI 21
/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-ME
PC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="044">
<xs:annotation>
<xs:documentation xml:lang="en">LRIT conformance test report. DESCRIPTION: refer to document: IMO
FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FA
L.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="045">
<xs:annotation>
<xs:documentation xml:lang="en">passenger ship safety certificate. DESCRIPTION: refer to document
: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, dr
aft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="046">
<xs:annotation>
<xs:documentation xml:lang="en">specia trade passenger ship safety certificate. DESCRIPTION: refe
r to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee
; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board sh
ips</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="047">
EUCISE2020
Page 328 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">special trade passenger ship space certificate. DESCRIPTION: refe
r to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee
; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board sh
ips</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="048">
<xs:annotation>
<xs:documentation xml:lang="en">search and rescue cooperation plan. DESCRIPTION: refer to documen
t: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, d
raft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="049">
<xs:annotation>
<xs:documentation xml:lang="en">list of operational limitations. DESCRIPTION: refer to document:
IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draf
t FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="050">
<xs:annotation>
<xs:documentation xml:lang="en">decision support system for masters. DESCRIPTION: refer to docume
nt: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1,
draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="051">
<xs:annotation>
<xs:documentation xml:lang="en">cargo ship safety construction certificate. DESCRIPTION: refer to
document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANN
EX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="052">
<xs:annotation>
<xs:documentation xml:lang="en">cargo ship safety equipment certificate. DESCRIPTION: refer to do
cument: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX
1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="053">
<xs:annotation>
<xs:documentation xml:lang="en">cargo ship safety radio certificate. DESCRIPTION: refer to docume
nt: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1,
draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="054">
<xs:annotation>
<xs:documentation xml:lang="en">cargo ship safety certificate. DESCRIPTION: refer to document: IM
O FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft
FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="055">
<xs:annotation>
<xs:documentation xml:lang="en">authorization for the carriage of grain. DESCRIPTION: refer to do
cument: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX
1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="056">
<xs:annotation>
<xs:documentation xml:lang="en">certificate of insurance for oil pollution damage. DESCRIPTION: r
efer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Commit
EUCISE2020
Page 329 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
tee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board
ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="057">
<xs:annotation>
<xs:documentation xml:lang="en">certificate of insurance for bunker oil pollution damage. DESCRIP
TION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection
Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on
board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="058">
<xs:annotation>
<xs:documentation xml:lang="en">enhanced survey report file. DESCRIPTION: refer to document: IMO
FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FA
L.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="059">
<xs:annotation>
<xs:documentation xml:lang="en">record of oil discharge monitoring and control system. DESCRIPTIO
N: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Co
mmittee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on b
oard ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="060">
<xs:annotation>
<xs:documentation xml:lang="en">oil discharge monitoring and control operational manual. DESCRIPT
ION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection
Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on
board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="061">
<xs:annotation>
<xs:documentation xml:lang="en">ship structure access manual. DESCRIPTION: refer to document: IMO
FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FA
L.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="062">
<xs:annotation>
<xs:documentation xml:lang="en">bulk carrier booklet. DESCRIPTION: refer to document: IMO FSI 21/
18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEP
C.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="063">
<xs:annotation>
<xs:documentation xml:lang="en">crude oil washing operation and equipment manual. DESCRIPTION: re
fer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committ
ee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board
ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="064">
<xs:annotation>
<xs:documentation xml:lang="en">condition assessment scheme statement of compliance. DESCRIPTION:
refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Commi
ttee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on boar
d ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="065">
<xs:annotation>
<xs:documentation xml:lang="en">subdivision and stability information. DESCRIPTION: refer to docu
ment: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1
, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 330 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="066">
<xs:annotation>
<xs:documentation xml:lang="en">VOC management plan. DESCRIPTION: refer to document: IMO FSI 21/1
8, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC
.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="067">
<xs:annotation>
<xs:documentation xml:lang="en">international pollution prevention certificate for noxious liquid
substances. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Env
ironment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents requi
red to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="068">
<xs:annotation>
<xs:documentation xml:lang="en">cargo record book. DESCRIPTION: refer to document: IMO FSI 21/18,
Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="069">
<xs:annotation>
<xs:documentation xml:lang="en">procedures and arrangements manual. DESCRIPTION: refer to documen
t: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, d
raft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="070">
<xs:annotation>
<xs:documentation xml:lang="en">ship board marine pollution emergency plan for noxious liquid sub
stances. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Enviro
nment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required
to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="071">
<xs:annotation>
<xs:documentation xml:lang="en">certificate of fitness for the carriage of dangerous chemicals in
bulk. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environme
nt Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to
be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="072">
<xs:annotation>
<xs:documentation xml:lang="en">international certificate of fitness for the carriage of dangerou
s chemicals in bulk. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the M
arine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Docume
nts required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="073">
<xs:annotation>
<xs:documentation xml:lang="en">certificate of fitness for the carriage of liquified gases in bul
k. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment
Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be
carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="074">
<xs:annotation>
<xs:documentation xml:lang="en">international certificate of fitness for the carriage of liquifie
d gases in bulk. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marin
e Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents
required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="075">
<xs:annotation>
<xs:documentation xml:lang="en">high speed craft safety certificate. DESCRIPTION: refer to docume
nt: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1,
draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:doc
EUCISE2020
Page 331 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="076">
<xs:annotation>
<xs:documentation xml:lang="en">permit to operate high speed craft. DESCRIPTION: refer to documen
t: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, d
raft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="077">
<xs:annotation>
<xs:documentation xml:lang="en">compliance with special requirements for ships carrying dangerous
goods. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environm
ent Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required t
o be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="078">
<xs:annotation>
<xs:documentation xml:lang="en">dangerous goods manifest. DESCRIPTION: refer to document: IMO FSI
21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="079">
<xs:annotation>
<xs:documentation xml:lang="en">dangerous good stowage plan. DESCRIPTION: refer to document: IMO
FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FA
L.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="080">
<xs:annotation>
<xs:documentation xml:lang="en">international certificate of fitness for carriage of INF cargo. D
ESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Prot
ection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be car
ried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="081">
<xs:annotation>
<xs:documentation xml:lang="en">nuclear cargo ship safety certificate. DESCRIPTION: refer to docu
ment: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1
, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="082">
<xs:annotation>
<xs:documentation xml:lang="en">nuclear passenger ship safety certificate. DESCRIPTION: refer to
document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANN
EX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="083">
<xs:annotation>
<xs:documentation xml:lang="en">special purpose ship safety certificate. DESCRIPTION: refer to do
cument: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX
1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="084">
<xs:annotation>
<xs:documentation xml:lang="en">off shore supply vessel document of compliance. DESCRIPTION: refe
r to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee
; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board sh
ips</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="085">
EUCISE2020
Page 332 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">certificate of fitness for off shore support vessels. DESCRIPTION
: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Com
mittee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on bo
ard ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="086">
<xs:annotation>
<xs:documentation xml:lang="en">diving system safety certificate. DESCRIPTION: refer to document:
IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draf
t FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="087">
<xs:annotation>
<xs:documentation xml:lang="en">dynamically supported craft construction and equipment certificat
e. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment
Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be
carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="088">
<xs:annotation>
<xs:documentation xml:lang="en">mobile off shore drilling unit safety certificate. DESCRIPTION: r
efer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Commit
tee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board
ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="089">
<xs:annotation>
<xs:documentation xml:lang="en">wing in ground craft safety certificate. DESCRIPTION: refer to do
cument: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX
1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="090">
<xs:annotation>
<xs:documentation xml:lang="en">permit to operate WIG craft. DESCRIPTION: refer to document: IMO
FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FA
L.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="091">
<xs:annotation>
<xs:documentation xml:lang="en">noise survey report. DESCRIPTION: refer to document: IMO FSI 21/1
8, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC
.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="092">
<xs:annotation>
<xs:documentation xml:lang="en">maritime declaration of health. DESCRIPTION: refer to document: I
MO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft
FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="093">
<xs:annotation>
<xs:documentation xml:lang="en">crew list. DESCRIPTION: refer to document: IMO FSI 21/18, Report
to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 C
ircular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="094">
<xs:annotation>
<xs:documentation xml:lang="en">passengers list. DESCRIPTION: refer to document: IMO FSI 21/18, R
eport to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-M
SC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
EUCISE2020
Page 333 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="095">
<xs:annotation>
<xs:documentation xml:lang="en">cargo declaration. DESCRIPTION: refer to document: IMO FSI 21/18,
Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="096">
<xs:annotation>
<xs:documentation xml:lang="en">ships stores declaration. DESCRIPTION: refer to document: IMO FSI
21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="097">
<xs:annotation>
<xs:documentation xml:lang="en">general declaration. DESCRIPTION: refer to document: IMO FSI 21/1
8, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC
.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="098">
<xs:annotation>
<xs:documentation xml:lang="en">crews effects declaration. DESCRIPTION: refer to document: IMO FS
I 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.
2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="099">
<xs:annotation>
<xs:documentation xml:lang="en">emergency towing procedures. DESCRIPTION: refer to document: IMO
FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FA
L.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="100">
<xs:annotation>
<xs:documentation xml:lang="en">deck log book. DESCRIPTION: refer to document: IMO FSI 21/18, Rep
ort to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC
.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="101">
<xs:annotation>
<xs:documentation xml:lang="en">operating and maintenance manual. DESCRIPTION: refer to document:
IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draf
t FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="102">
<xs:annotation>
<xs:documentation xml:lang="en">A amax ratio information. DESCRIPTION: refer to document: IMO FSI
21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="103">
<xs:annotation>
<xs:documentation xml:lang="en">documention evaluation of the alternative design and arrangements
. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment P
rotection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be
carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="104">
<xs:annotation>
<xs:documentation xml:lang="en">instruction manual for inert gas systems. DESCRIPTION: refer to d
ocument: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNE
X 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</x
s:documentation>
</xs:annotation>
EUCISE2020
Page 334 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="105">
<xs:annotation>
<xs:documentation xml:lang="en">muster list. DESCRIPTION: refer to document: IMO FSI 21/18, Repor
t to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1
Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="106">
<xs:annotation>
<xs:documentation xml:lang="en">emergency instructions. DESCRIPTION: refer to document: IMO FSI 2
1/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-M
EPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="107">
<xs:annotation>
<xs:documentation xml:lang="en">ship specific plans and procedures for recovery of persons from t
he water. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Envir
onment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents require
d to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="108">
<xs:annotation>
<xs:documentation xml:lang="en">training manual for lifesaving appliances. DESCRIPTION: refer to
document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANN
EX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="109">
<xs:annotation>
<xs:documentation xml:lang="en">instructions for on board maintenance of life saving appliances.
DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Pro
tection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be ca
rried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="110">
<xs:annotation>
<xs:documentation xml:lang="en">radio record. DESCRIPTION: refer to document: IMO FSI 21/18, Repo
rt to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.
1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="111">
<xs:annotation>
<xs:documentation xml:lang="en">AIS test report. DESCRIPTION: refer to document: IMO FSI 21/18, R
eport to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-M
SC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="112">
<xs:annotation>
<xs:documentation xml:lang="en">international code of signals. DESCRIPTION: refer to document: IM
O FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft
FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="113">
<xs:annotation>
<xs:documentation xml:lang="en">deviation curve for magnetic process. DESCRIPTION: refer to docum
ent: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1,
draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="114">
<xs:annotation>
<xs:documentation xml:lang="en">nautical publications. DESCRIPTION: refer to document: IMO FSI 21
/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-ME
PC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
EUCISE2020
Page 335 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="115">
<xs:annotation>
<xs:documentation xml:lang="en">material safety data sheets. DESCRIPTION: refer to document: IMO
FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FA
L.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="116">
<xs:annotation>
<xs:documentation xml:lang="en">cargo handling booklet. DESCRIPTION: refer to document: IMO FSI 2
1/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-M
EPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="117">
<xs:annotation>
<xs:documentation xml:lang="en">shipboard emergency plan. DESCRIPTION: refer to document: IMO FSI
21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="118">
<xs:annotation>
<xs:documentation xml:lang="en">high speed craft operating manual. DESCRIPTION: refer to document
: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, dr
aft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="119">
<xs:annotation>
<xs:documentation xml:lang="en">route operational manual. DESCRIPTION: refer to document: IMO FSI
21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="120">
<xs:annotation>
<xs:documentation xml:lang="en">training manual. DESCRIPTION: refer to document: IMO FSI 21/18, R
eport to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-M
SC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="121">
<xs:annotation>
<xs:documentation xml:lang="en">maintenance and servicing manual. DESCRIPTION: refer to document:
IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draf
t FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="122">
<xs:annotation>
<xs:documentation xml:lang="en">type rafting certificate. DESCRIPTION: refer to document: IMO FSI
21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="123">
<xs:annotation>
<xs:documentation xml:lang="en">copy of IBC code. DESCRIPTION: refer to document: IMO FSI 21/18,
Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="124">
<xs:annotation>
<xs:documentation xml:lang="en">copy of IGC code. DESCRIPTION: refer to document: IMO FSI 21/18,
Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="125">
EUCISE2020
Page 336 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">statement of compliance with CAS. DESCRIPTION: refer to document:
IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draf
t FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="126">
<xs:annotation>
<xs:documentation xml:lang="en">dedicated clean ballast tank operational manual. DESCRIPTION: ref
er to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committe
e; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board s
hips</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="127">
<xs:annotation>
<xs:documentation xml:lang="en">operations and equipment manual for crude oil washing systems. DE
SCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Prote
ction Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carr
ied on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="128">
<xs:annotation>
<xs:documentation xml:lang="en">record of oil discharge monitoring and control system for the las
t ballast voyage. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Mari
ne Environment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents
required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="129">
<xs:annotation>
<xs:documentation xml:lang="en">oil discharge monitoring and control system operational manual. D
ESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Prot
ection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be car
ried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="130">
<xs:annotation>
<xs:documentation xml:lang="en">damage survival capability information. DESCRIPTION: refer to doc
ument: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX
1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="131">
<xs:annotation>
<xs:documentation xml:lang="en">ship to ship operations plans. DESCRIPTION: refer to document: IM
O FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft
FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="132">
<xs:annotation>
<xs:documentation xml:lang="en">result of calculation of moderate rate of discharge in accordance
with MEPC157. DESCRIPTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine E
nvironment Protection Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents req
uired to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="133">
<xs:annotation>
<xs:documentation xml:lang="en">engine international air pollution prevention certificate. DESCRI
PTION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protectio
n Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried
on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="134">
<xs:annotation>
<xs:documentation xml:lang="en">international energy efficiency certificate. DESCRIPTION: refer t
o document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; A
EUCISE2020
Page 337 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
NNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships
</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="135">
<xs:annotation>
<xs:documentation xml:lang="en">list of equipment containing ozone depleting substances. DESCRIPT
ION: refer to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection
Committee; ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on
board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="136">
<xs:annotation>
<xs:documentation xml:lang="en">fuel oil changeover procedures and logbook. DESCRIPTION: refer to
document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANN
EX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="137">
<xs:annotation>
<xs:documentation xml:lang="en">ship energy efficiency management plan. DESCRIPTION: refer to doc
ument: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX
1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:
documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="138">
<xs:annotation>
<xs:documentation xml:lang="en">energy efficiency design index technical file. DESCRIPTION: refer
to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee;
ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ship
s</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="139">
<xs:annotation>
<xs:documentation xml:lang="en">maritime labour certificate. DESCRIPTION: refer to document: IMO
FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FA
L.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="140">
<xs:annotation>
<xs:documentation xml:lang="en">certificate of compliance for ILO92. DESCRIPTION: refer to docume
nt: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1,
draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="141">
<xs:annotation>
<xs:documentation xml:lang="en">certificate of compliance for ILO133. DESCRIPTION: refer to docum
ent: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1,
draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="142">
<xs:annotation>
<xs:documentation xml:lang="en">medical certificate for ILO73. DESCRIPTION: refer to document: IM
O FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft
FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="143">
<xs:annotation>
<xs:documentation xml:lang="en">load test certificate for ILO152. DESCRIPTION: refer to document:
IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draf
t FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documen
tation>
</xs:annotation>
EUCISE2020
Page 338 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="144">
<xs:annotation>
<xs:documentation xml:lang="en">declaration of maritime labour compliance. DESCRIPTION: refer to
document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANN
EX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="145">
<xs:annotation>
<xs:documentation xml:lang="en">register book for ILO152. DESCRIPTION: refer to document: IMO FSI
21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="146">
<xs:annotation>
<xs:documentation xml:lang="en">ship sanitation control exemption certificate. DESCRIPTION: refer
to document: IMO FSI 21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee;
ANNEX 1, draft FAL.2-MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ship
s</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="147">
<xs:annotation>
<xs:documentation xml:lang="en">radio station license. DESCRIPTION: refer to document: IMO FSI 21
/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-ME
PC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="148">
<xs:annotation>
<xs:documentation xml:lang="en">radio service document. DESCRIPTION: refer to document: IMO FSI 2
1/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2-M
EPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="149">
<xs:annotation>
<xs:documentation xml:lang="en">certificate of registry. DESCRIPTION: refer to document: IMO FSI
21/18, Report to the Maritime Safety Committee and the Marine Environment Protection Committee; ANNEX 1, draft FAL.2MEPC.1-MSC.1 Circular on list of Certificates and Documents required to be carried on board ships</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="998">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other type of document not mentioned abov
e</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="999">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Type of the document not specified</x
s:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.130. schema data/Entity/Document/OrganizationDocumentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:simpleType name="OrganizationDocumentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of documents that can be related to organi
zations.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">harbour security document. DESCRIPTION: Documents that related to
EUCISE2020
Page 339 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
a specific harbour and deal with security issues.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">ISPS code. DESCRIPTION: Documents that are related to an organiza
tion and deal with IMO ISPS Code.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">map. DESCRIPTION: Any type of map related to the organization.</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other type of document not specified abov
e.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Type of the document not specified.</
xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.131. schema data/Entity/Document/PersonDocumentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:simpleType name="PersonDocumentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of documents that can be related to indivi
dual persons.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">travel document. DESCRIPTION: Document that enables the entry and
exit from one country to another (e.g. Passport).</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">national ID. DESCRIPTION: National identification document.</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">drivers license. DESCRIPTION: Document proving the right to drive
a car.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">seafarers ID document. DESCRIPTION: Special identification docume
nt for seafarers (e.g. SeamansBook)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">crew certificates. DESCRIPTION: Certificate of ability to hold a
certain post in vessel.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">residence permit. DESCRIPTION: Document proving that a person has
EUCISE2020
Page 340 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
right to stay in the country (e.g. MigrationCard, CruiseShipIDCard (passangers))</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">work permit. DESCRIPTION: Document proving that a person has righ
t to work in the country (e.g.WorkCard, BlueCard)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">work certificate. DESCRIPTION: Document proving the past employme
nt of a person (e.g.EmploymentRecordBook)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">health certificate. DESCRIPTION: Document stating the health stat
us of the person.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">birth certificate. DESCRIPTION: The official birth certificate of
a person</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">death certificate. DESCRIPTION: The official death certificate of
a person</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">criminal record. DESCRIPTION: Persons criminal record</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">photograph. DESCRIPTION: Photograph of a person.</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other document not mentioned above</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Type of the document not specified</x
s:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.132. schema data/Entity/Document/StreamType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:include schemaLocation="DocumentType.xsd"/>
<xs:include schemaLocation="StreamEnumType.xsd"/>
<xs:complexType name="StreamType">
<xs:annotation>
<xs:documentation>Stream of information.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="document:DocumentType">
<xs:sequence>
EUCISE2020
Page 341 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:element name="StreamType" type="document:StreamEnumType" minOccurs="0"/>
<xs:element name="StreamURI" type="xs:anyURI" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.133. schema data/Entity/Document/RiskDocumentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:simpleType name="RiskDocumentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of documents related to risks.</xs:documen
tation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01 ">
<xs:annotation>
<xs:documentation xml:lang="en">briefing notes. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">route description. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">facilitationanalysis. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">migrant profile. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">key developments. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">risk ratings. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">HAZMAT notification. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">risk assessment. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">organised crime documents. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">terrorist threat documents. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">ship hijacking suspicion report. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
EUCISE2020
Page 342 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">crew hostaging suspicion report. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">weapons on board suspicion report. DESCRIPTION: </xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.134. schema data/Entity/Document/EventDocumentEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Document/">
<xs:simpleType name="EventDocumentEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of documents related to different events (
movements, actions, anomalies, incidents).</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">regional monitors. DESCRIPTION: Observation reports from differen
t EU regions related to issues reported via EUROSUR (e.g. irregular migration, related cross-border crime, crisis, ot
her).</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">incident report. DESCRIPTION: Documents containing the detailed r
eport of incidents reported via SSN (e.g. waste, situations , pollution, containers or packages drifting at sea, fail
ed vessel notifications, VTS rules infringements, banned ships, insurance failures, anomaly reports by pilots or port
s).</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">environmental incident document. DESCRIPTION: Documents and repor
ts that describe environmental icidents (e.g. oil pollution)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">evacuation orders. DESCRIPTION: Detailed orders related to evacua
tion situations.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">accident report. DESCRIPTION: Detailed reports of accidents in se
a.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">hazards mapping and tracking humanitarian assistance. DESCRIPTION
: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
EUCISE2020
Page 343 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">organized crime documents. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">terrorist thread documents. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">ship hijacking suspicion report. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">crew hostaging suspicion report. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">weapons onboard suspicion report. DESCRIPTION: </xs:documentation
>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">initial piracy attack report. DESCRIPTION: Initial report about p
iracy attack as defined in IMO MSC Circular 1333.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="13">
<xs:annotation>
<xs:documentation xml:lang="en">follow-up piracy attack report. DESCRIPTION: Follow-up report abo
ut piracy attack as defined in IMO MSC Circular 1333.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Any other document related to events not ment
ioned above</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Type of document not specified.</xs:d
ocumentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.135. schema data/Entity/Movement/MovementType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:movement="http://www.cise.eu/datamodel/Entity/Movement/"
xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" targetNamespace="http://www.cise.eu/datamodel/Entity/Movemen
t/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Event/EventType.xsd"/>
<xs:include schemaLocation="MovementEnumType.xsd"/>
<xs:complexType name="MovementType">
<xs:annotation>
<xs:documentation>It is a subclass of event. The Movement entity is linked to Voyage. Movement can be act
ual (e.g. current position, heading and speed), Historical data or planned in the future and can also be expressed ta
king into account other entities as location, object, etc.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="event:EventType">
<xs:sequence>
<xs:element name="MovementType" type="movement:MovementEnumType" minOccurs="0"/>
<xs:element name="Purpose" type="xs:string" minOccurs="0"/>
<xs:element name="VoyageNumber" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:extension>
EUCISE2020
Page 344 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.136. schema data/Entity/Movement/MovementEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:movement="http://www.cise.eu/datamodel/Entity/Movement/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Movement/">
<xs:simpleType name="MovementEnumType">
<xs:annotation>
<xs:documentation>This enumeration presents the possible types of processes used to perform the objects’
correlation.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">route plan. DESCRIPTION: Expected locations/direction and movemen
ts that a vessels will follow during a voyage. It is known before departure</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">voyage. DESCRIPTION: Journey involving travel by sea</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">voyage leg. DESCRIPTION: Stage of a Voyage</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">search pattern. DESCRIPTION: Search pattern for a certain area</x
s:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">patrol route plan. DESCRIPTION: Patrol route plan for a certain a
rea</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Movement type not included above</xs:document
ation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Movement type non-specified</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.137. schema data/Entity/Location/OperationalPurposeEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:simpleType name="OperationalPurposeEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">search area. DESCRIPTION: Search area</xs:documentation>
</xs:annotation>
EUCISE2020
Page 345 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">surveillance area. DESCRIPTION: Surveillance area</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Operational purpose not listed here</xs:docum
entation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: The operational purpose is not declar
ed</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.138. schema data/Entity/Location/LocationQualitativeAccuracyEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:simpleType name="LocationQualitativeAccuracyEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">high. DESCRIPTION: High qualitative accuracy</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">medium. DESCRIPTION: Medium qualitative accuracy</xs:documentatio
n>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">low. DESCRIPTION: Low qualitative accuracy</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Qualitative accuracy not listed here</xs:docu
mentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: The qualitative accuracy is not decla
red</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.139. schema data/Entity/Location/WeatherConditionEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:simpleType name="WeatherConditionEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
EUCISE2020
Page 346 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:restriction base="xs:string">
<xs:enumeration value="HUM">
<xs:annotation>
<xs:documentation xml:lang="en">hum weather. DESCRIPTION: Humid conditions</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="ICY">
<xs:annotation>
<xs:documentation xml:lang="en">icy weather. DESCRIPTION: Icy conditions</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="TDS">
<xs:annotation>
<xs:documentation xml:lang="en">tds weather. DESCRIPTION: Thunderstorm conditions</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="WIN">
<xs:annotation>
<xs:documentation xml:lang="en">win weather. DESCRIPTION: Windy conditions</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="DRZLE">
<xs:annotation>
<xs:documentation xml:lang="en">drzle weather. DESCRIPTION: Drizzle. Fairly uniform precipitation
composed exclusively of fine drops very close together. Drizzle appears to float while following air currents althoug
h, unlike fog droplets, it falls to the ground. It usually falls from low stratus clouds and is frequently accompanie
d by low visibility and fog.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="FOG">
<xs:annotation>
<xs:documentation xml:lang="en">fog weather. DESCRIPTION: Fog/mist. A visible aggregate of minute
water particles (droplets) which are based on the Earth’s surface, extends vertically, and reduceshorizontal visibili
ty to less than 5/8 mile (1,000 meters). Unlike drizzle, FOG does not fall to the ground.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="Other">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Weather Condition type not listed here</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="NonSpecified">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: Weather Condition type is not declare
d</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.140. schema data/Entity/Location/CloudCoverEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:simpleType name="CloudCoverEnumType">
<xs:annotation>
<xs:documentation>Cloud cover is estimated in terms of how many eighths of the sky are covered in cloud,
ranging from 0 oktas (completely clear sky) through to 8 oktas (completely overcast).</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="0">
<xs:annotation>
<xs:documentation xml:lang="en">clear sky. DESCRIPTION: Sky completely clear</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="1">
<xs:annotation>
<xs:documentation xml:lang="en">1 okta. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="2">
EUCISE2020
Page 347 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">2 oktas. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="3">
<xs:annotation>
<xs:documentation xml:lang="en">3 oktas. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="4">
<xs:annotation>
<xs:documentation xml:lang="en">4 oktas. DESCRIPTION: Sky half cloudy</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="5">
<xs:annotation>
<xs:documentation xml:lang="en">5 oktas. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="6">
<xs:annotation>
<xs:documentation xml:lang="en">6 oktas. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="7">
<xs:annotation>
<xs:documentation xml:lang="en">7 oktas. DESCRIPTION: </xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="8">
<xs:annotation>
<xs:documentation xml:lang="en">8 oktas. DESCRIPTION: Sky completely cloudy</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="9">
<xs:annotation>
<xs:documentation xml:lang="en">sky obscured. DESCRIPTION: Sky obstructed from view</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.141. schema data/Entity/Location/LocationType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:metadata="http://www.cise.eu/datamodel/Entity/Metadata/" ta
rgetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Metadata/" schemaLocation="../Metadata/Metadata.xsd"/>
<xs:include schemaLocation="Geometry.xsd"/>
<xs:include schemaLocation="LocationQualitativeAccuracyEnumType.xsd"/>
<xs:include schemaLocation="OperationalPurposeEnumType.xsd"/>
<xs:include schemaLocation="LocationZoneEnumType.xsd"/>
<xs:complexType name="LocationType">
<xs:annotation>
<xs:documentation>Locations can be described in three principal ways: by using a place name, geometry or
an address. The specific context will determine which method of describing a location is most appropriate. ISO 19112
defines a location as "an identifiable geographic place". With this in mind, "Eiffel Tower", "Madrid" and "California
" are all locations and this is a common way of representing locations in public sector data, i.e. simply by using a
recognized name. Such identifiers are common although they can be highly ambiguous as many places share the same or s
imilar names.||In addition to a simple (string) label or name for a Location, the identifier property allows defining
a Location by a Uniform Resource Identifier (URI), such as a GeoNames or DBpedia URI.||No cardinality constraints are
placed on any property of the Location class so as to maximize flexibility.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Geometry" type="location:Geometry" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="LocationQualitativeAccuracy" type="location:LocationQualitativeAccuracyEnumType
" minOccurs="0"/>
<xs:element name="LocationZone" type="location:LocationZoneEnumType" minOccurs="0" maxOccurs="unb
ounded"/>
EUCISE2020
Page 348 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:element name="Metadata" type="metadata:Metadata" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="OperationalPurpose" type="location:OperationalPurposeEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.142. schema data/Entity/Location/TidesEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:simpleType name="TidesEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="Low">
<xs:annotation>
<xs:documentation xml:lang="en">low tides. DESCRIPTION: low tides</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="High">
<xs:annotation>
<xs:documentation xml:lang="en">high tides. DESCRIPTION: high tides</xs:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.143. schema data/Entity/Location/LocationZoneEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:simpleType name="LocationZoneEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">high seas. DESCRIPTION: High seas</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">territorial waters. DESCRIPTION: Territorial waters</xs:documenta
tion>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">coast line. DESCRIPTION: Coast line</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">contiguous zone. DESCRIPTION: Contiguous zone</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">port. DESCRIPTION: Port</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">control point. DESCRIPTION: Control point</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
EUCISE2020
Page 349 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:annotation>
<xs:documentation xml:lang="en">green border. DESCRIPTION: Green border</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">inland. DESCRIPTION: Inland</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">exclusive economic area. DESCRIPTION: Exclusive Economic Area</xs
:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="10">
<xs:annotation>
<xs:documentation xml:lang="en">third country. DESCRIPTION: Third country</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="11">
<xs:annotation>
<xs:documentation xml:lang="en">INW. DESCRIPTION: Inland waterway. A body of water, such as a riv
er, canal or lake. It may be navigable if it is deep and wide enough for a vessel to pass and there are no obstructio
ns.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="12">
<xs:annotation>
<xs:documentation xml:lang="en">NAT. DESCRIPTION: Natural / rural environment</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: Location type not listed here</xs:documentati
on>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: The location type is not declared</xs
:documentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.144. schema data/Entity/Location/PortLocationType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" targetNamespace="http://www.cise.eu/datamodel/Entity/Locat
ion/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Vessel/" schemaLocation="../Vessel/ISPSSecurityLevelEnu
mType.xsd"/>
<xs:include schemaLocation="LocationType.xsd"/>
<xs:complexType name="PortLocationType">
<xs:annotation>
<xs:documentation>Location describing the position/area of a port.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="location:LocationType">
<xs:sequence>
<xs:element name="LocationCode" type="xs:string" minOccurs="0"/>
<xs:element name="PortName" type="xs:string" minOccurs="0"/>
<xs:element name="PortSecurityLevel" type="vessel:ISPSSecurityLevelEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.145. schema data/Entity/Location/Geometry.xsd
EUCISE2020
Page 350 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:complexType name="Geometry">
<xs:annotation>
<xs:documentation>This class allows the definition of Georeferenced areas.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="Altitude" type="xs:string" minOccurs="0"/>
<xs:element name="Latitude" type="xs:string" minOccurs="0"/>
<xs:element name="Longitude" type="xs:string" minOccurs="0"/>
<xs:element name="WKT" type="xs:string" minOccurs="0"/>
<xs:element name="XMLGeometry" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
2.146. schema data/Entity/Location/MetocEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:simpleType name="MetocEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">observed. DESCRIPTION: By observation</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">declared. DESCRIPTION: By declaration</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">estimated. DESCRIPTION: By estimation</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">simulated. DESCRIPTION: By simulation</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="98">
<xs:annotation>
<xs:documentation xml:lang="en">other. DESCRIPTION: METOC type not listed here</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="99">
<xs:annotation>
<xs:documentation xml:lang="en">non-specified. DESCRIPTION: The METOC type is not declared</xs:do
cumentation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.147. schema data/Entity/Location/PortFacilityLocationType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
xmlns:vessel="http://www.cise.eu/datamodel/Entity/Vessel/" targetNamespace="http://www.cise.eu/datamodel/Entity/Locat
ion/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Vessel/" schemaLocation="../Vessel/ISPSSecurityLevelEnu
mType.xsd"/>
<xs:include schemaLocation="LocationType.xsd"/>
<xs:complexType name="PortFacilityLocationType">
<xs:annotation>
EUCISE2020
Page 351 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:documentation>Location of one of the facilities contained in a port.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="location:LocationType">
<xs:sequence>
<xs:element name="PortFacilityName" type="xs:string" minOccurs="0"/>
<xs:element name="PortFacilityNumber" type="xs:string" minOccurs="0"/>
<xs:element name="PortSecurityLevel" type="vessel:ISPSSecurityLevelEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.148. schema data/Entity/Location/NamedLocationType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:include schemaLocation="LocationType.xsd"/>
<xs:complexType name="NamedLocationType">
<xs:annotation>
<xs:documentation>Location with a given name.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="location:LocationType">
<xs:sequence>
<xs:element name="GeographicIdentifier" type="xs:anyURI" minOccurs="0"/>
<xs:element name="GeographicName" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.149. schema data/Entity/Location/SeaConditionEnumType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
targetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:simpleType name="SeaConditionEnumType">
<xs:annotation>
<xs:documentation/>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="00">
<xs:annotation>
<xs:documentation xml:lang="en">calm (glassy). DESCRIPTION: 0 metres (0 ft)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="01">
<xs:annotation>
<xs:documentation xml:lang="en">calm (rippled). DESCRIPTION: Waves from 0 to 0.1 metres (0.00 to
0.33 ft)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="02">
<xs:annotation>
<xs:documentation xml:lang="en">smooth (wavelets). DESCRIPTION: Waves from 0.1 to 0.5 metres (3.
9 in to 1 ft 7.7 in)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="03">
<xs:annotation>
<xs:documentation xml:lang="en">slight. DESCRIPTION: Waves from 0.5 to 1.25 metres (1 ft 8 in to
4 ft 1 in)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="04">
<xs:annotation>
<xs:documentation xml:lang="en">moderate. DESCRIPTION: Waves from 1.25 to 2.5 metres (4 ft 1 in t
o 8 ft 2 in)</xs:documentation>
</xs:annotation>
</xs:enumeration>
EUCISE2020
Page 352 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:enumeration value="05">
<xs:annotation>
<xs:documentation xml:lang="en">rough. DESCRIPTION: Waves from 2.5 to 4 metres (8 ft 2 in to 13 f
t 1 in)</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="06">
<xs:annotation>
<xs:documentation xml:lang="en">very rough. DESCRIPTION: Waves from 4 to 6 metres (13 to 20 ft)</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="07">
<xs:annotation>
<xs:documentation xml:lang="en">high. DESCRIPTION: Waves from 6 to 9 metres (20 to 30 ft)</xs:doc
umentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="08">
<xs:annotation>
<xs:documentation xml:lang="en">very high. DESCRIPTION: Waves from 9 to 14 metres (30 to 46 ft)</
xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="09">
<xs:annotation>
<xs:documentation xml:lang="en">phenomenal. DESCRIPTION: Waves over 14 metres (46 ft)</xs:documen
tation>
</xs:annotation>
</xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:schema>
2.150. schema data/Entity/Location/MeteoOceanographicConditionType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" xmlns:
period="http://www.cise.eu/datamodel/Entity/Period/" targetNamespace="http://www.cise.eu/datamodel/Entity/Location/">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Object/SourceEnumType.xsd"/
>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Period/Period.xsd"/>
<xs:include schemaLocation="SeaConditionEnumType.xsd"/>
<xs:include schemaLocation="WeatherConditionEnumType.xsd"/>
<xs:include schemaLocation="CloudCoverEnumType.xsd"/>
<xs:include schemaLocation="TidesEnumType.xsd"/>
<xs:complexType name="MeteoOceanographicConditionType">
<xs:annotation>
<xs:documentation>This class allows the description of the meteorological oceanographic condition of a gi
ven Location.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="AirTemperature" type="xs:double" minOccurs="0"/>
<xs:element name="CloudCeiling" type="xs:int" minOccurs="0"/>
<xs:element name="CloudCover" type="location:CloudCoverEnumType" minOccurs="0"/>
<xs:element name="Precipitation" type="xs:int" minOccurs="0"/>
<xs:element name="ReferencePeriod" type="period:Period" minOccurs="0"/>
<xs:element name="Salinity" type="xs:double" minOccurs="0"/>
<xs:element name="SeaCondition" type="location:SeaConditionEnumType" minOccurs="0"/>
<xs:element name="SeaLevelPressure" type="xs:double" minOccurs="0"/>
<xs:element name="SourceType" type="object:SourceEnumType" minOccurs="0"/>
<xs:element name="TidalCurrentDirection" type="xs:double" minOccurs="0"/>
<xs:element name="TidalCurrentSpeed" type="xs:double" minOccurs="0"/>
<xs:element name="Tides" type="location:TidesEnumType" minOccurs="0"/>
<xs:element name="Visibility" type="xs:double" minOccurs="0"/>
<xs:element name="WaterTemperature" type="xs:double" minOccurs="0"/>
<xs:element name="WaveDirection" type="xs:double" minOccurs="0"/>
<xs:element name="WaveHeight" type="xs:double" minOccurs="0"/>
<xs:element name="WeatherCondition" type="location:WeatherConditionEnumType" minOccurs="0"/>
<xs:element name="WindCurrentDirection" type="xs:double" minOccurs="0"/>
<xs:element name="WindCurrentSpeed" type="xs:double" minOccurs="0"/>
EUCISE2020
Page 353 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
2.151. schema data/Entity/EntityType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:entity="http://www.cise.eu/datamodel/Entity/" targetName
space="http://www.cise.eu/datamodel/Entity/">
<xs:complexType name="EntityType" abstract="true">
<xs:annotation>
<xs:documentation>Abtract class representing an entity of the CISE data model.</xs:documentation>
</xs:annotation>
<xs:sequence>
</xs:sequence>
</xs:complexType>
</xs:schema>
2.152. schema data/Aircraft.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" ele
mentFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="Entity/Object/AircraftType.xsd
"/>
<xs:element name="Aircraft" type="object:AircraftType"/>
</xs:schema>
2.153. schema data/IrregularMigrationIncident.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Incident/" schemaLocation="Entity/Incident/IrregularMig
rationIncidentType.xsd"/>
<xs:element name="IrregularMigrationIncident" type="incident:IrregularMigrationIncidentType"/>
</xs:schema>
2.154. schema data/PersonDocument.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="Entity/Document/PersonDocume
ntType.xsd"/>
<xs:element name="PersonDocument" type="document:PersonDocumentType"/>
</xs:schema>
2.155. schema data/CertificateDocument.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="Entity/Document/CertificateD
ocumentType.xsd"/>
<xs:element name="CertificateDocument" type="document:CertificateDocumentType"/>
</xs:schema>
2.156. schema data/MeteoOceanographicCondition.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="Entity/Location/MeteoOceanog
raphicConditionType.xsd"/>
<xs:element name="MeteoOceanographicCondition" type="location:MeteoOceanographicConditionType"/>
</xs:schema>
EUCISE2020
Page 354 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
2.157. schema data/ContainmentUnit.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" eleme
ntFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Cargo/" schemaLocation="Entity/Cargo/ContainmentUnitTyp
e.xsd"/>
<xs:element name="ContainmentUnit" type="cargo:ContainmentUnitType"/>
</xs:schema>
2.158. schema data/OperationalAsset.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:operationalasset="http://www.cise.eu/datamodel/Entity/Op
erationalAsset/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/OperationalAsset/" schemaLocation="Entity/OperationalAs
set/OperationalAssetType.xsd"/>
<xs:element name="OperationalAsset" type="operationalasset:OperationalAssetType"/>
</xs:schema>
2.159. schema data/LandVehicle.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" ele
mentFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="Entity/Object/LandVehicleType.
xsd"/>
<xs:element name="LandVehicle" type="object:LandVehicleType"/>
</xs:schema>
2.160. schema data/rels/VehicleCargoRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:cargo="h
ttp://www.cise.eu/datamodel/Entity/Cargo/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:object="http://w
ww.cise.eu/datamodel/Entity/Object/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="qualifi
ed" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/VehicleType.x
sd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Cargo/" schemaLocation="../Entity/Cargo/CargoType.xsd"/
>
<xs:element name="VehicleCargoRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Vehicle" type="object:VehicleType"/>
<xs:element name="Cargo" type="cargo:CargoType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.161. schema data/rels/PortFacilityRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/" targetNamespace=
"http://www.cise.eu/datamodel/rels/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="../Entity/Location/PortFacil
ityLocationType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="../Entity/Location/PortLocat
ionType.xsd"/>
<xs:element name="PortFacilityRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
EUCISE2020
Page 355 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:sequence>
<xs:element name="PortFacilityLocation" type="location:PortFacilityLocationType"/>
<xs:element name="PortLocation" type="location:PortLocationType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.162. schema data/rels/RefersToDocumentRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:agent="h
ttp://www.cise.eu/datamodel/Entity/Agent/" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/" xmlns:entit
y="http://www.cise.eu/datamodel/Entity/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="qua
lified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="../Entity/Document/DocumentT
ype.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/AgentType.xsd"/
>
<xs:element name="RefersToDocumentRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Document" type="document:DocumentType"/>
<xs:element name="Agent" type="agent:AgentType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.163. schema data/rels/ObjectEventRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" xmlns:object="http://w
ww.cise.eu/datamodel/Entity/Object/" xmlns:period="http://www.cise.eu/datamodel/Entity/Period/" targetNamespace="http
://www.cise.eu/datamodel/rels/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/ObjectType.xs
d"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Entity/Event/ObjectRoleInEve
ntEnumType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Entity/Event/EventType.xsd"/
>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Entity/Period/Period.xsd"/>
<xs:element name="ObjectEventRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Object" type="object:ObjectType"/>
<xs:element name="Event" type="event:EventType"/>
<xs:element name="ObjectRole" type="event:ObjectRoleInEventEnumType" minOccurs="0"/>
<xs:element name="InvolvementPeriod" type="period:Period" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.164. schema data/rels/LinkedToRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organization/" targetNa
mespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="qualified" attributeFormDefault="qualified">
EUCISE2020
Page 356 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Organization/" schemaLocation="../Entity/Organization/O
rganizationType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Organization/" schemaLocation="../Entity/Organization/O
rganizationalCollaborationType.xsd"/>
<xs:element name="LinkedToRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="OrganizationalCollaboration" type="organization:OrganizationalCollaboration
Type"/>
<xs:element name="Organization" type="organization:OrganizationType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.165. schema data/rels/AgentRiskRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:agent="h
ttp://www.cise.eu/datamodel/Entity/Agent/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:period="http://w
ww.cise.eu/datamodel/Entity/Period/" xmlns:risk="http://www.cise.eu/datamodel/Entity/Risk/" targetNamespace="http://w
ww.cise.eu/datamodel/rels/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Risk/" schemaLocation="../Entity/Risk/RiskType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/AgentRoleInRisk
EnumType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Entity/Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/AgentType.xsd"/
>
<xs:element name="AgentRiskRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Agent" type="agent:AgentType"/>
<xs:element name="Risk" type="risk:RiskType"/>
<xs:element name="AgentRole" type="agent:AgentRoleInRiskEnumType" minOccurs="0"/>
<xs:element name="InvolvementPeriod" type="period:Period" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.166. schema data/rels/MetocLocationRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/" targetNamespace=
"http://www.cise.eu/datamodel/rels/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="../Entity/Location/MeteoOcea
nographicConditionType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="../Entity/Location/LocationT
ype.xsd"/>
<xs:element name="MetocLocationRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="MeteoOceanographicCondition" type="location:MeteoOceanographicConditionType
"/>
<xs:element name="Location" type="location:LocationType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
EUCISE2020
Page 357 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:element>
</xs:schema>
2.167. schema data/rels/VehicleCarriesVehicleRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" targetNamespace="htt
p://www.cise.eu/datamodel/rels/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/VehicleType.x
sd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:element name="VehicleCarriesVehicleRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="VehicleOrigin" type="object:VehicleType"/>
<xs:element name="VehicleTarget" type="object:VehicleType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.168. schema data/rels/AgentEventRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:agent="h
ttp://www.cise.eu/datamodel/Entity/Agent/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:event="http://ww
w.cise.eu/datamodel/Entity/Event/" xmlns:period="http://www.cise.eu/datamodel/Entity/Period/" targetNamespace="http:/
/www.cise.eu/datamodel/rels/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Entity/Event/AgentRoleInEven
tEnumType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Entity/Event/EventType.xsd"/
>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Entity/Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/AgentType.xsd"/
>
<xs:element name="AgentEventRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Agent" type="agent:AgentType"/>
<xs:element name="Event" type="event:EventType"/>
<xs:element name="AgentRole" type="event:AgentRoleInEventEnumType" minOccurs="0"/>
<xs:element name="InvolvementPeriod" type="period:Period" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.169. schema data/rels/AgentAgentRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:agent="h
ttp://www.cise.eu/datamodel/Entity/Agent/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:period="http://w
ww.cise.eu/datamodel/Entity/Period/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="qualifi
ed" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/DutyEnumType.xs
d"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/AgentRoleInAgen
tEnumType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Entity/Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/AgentType.xsd"/
>
<xs:element name="AgentAgentRel">
EUCISE2020
Page 358 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="AgentOrigin" type="agent:AgentType"/>
<xs:element name="AgentTarget" type="agent:AgentType"/>
<xs:element name="AgentRole" type="agent:AgentRoleInAgentEnumType" minOccurs="0"/>
<xs:element name="Duty" type="agent:DutyEnumType" minOccurs="0"/>
<xs:element name="InvolvementPeriod" type="period:Period" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.170. schema data/rels/RefersToLocationRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:document
="http://www.cise.eu/datamodel/Entity/Document/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:location="
http://www.cise.eu/datamodel/Entity/Location/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefaul
t="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="../Entity/Document/DocumentT
ype.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="../Entity/Location/LocationT
ype.xsd"/>
<xs:element name="RefersToLocationRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Document" type="document:DocumentType"/>
<xs:element name="Location" type="location:LocationType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.171. schema data/rels/ObjectDescribedByDocumentRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:document
="http://www.cise.eu/datamodel/Entity/Document/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:object="ht
tp://www.cise.eu/datamodel/Entity/Object/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="q
ualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/ObjectType.xs
d"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="../Entity/Document/DocumentT
ype.xsd"/>
<xs:element name="ObjectDescribedByDocumentRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Document" type="document:DocumentType"/>
<xs:element name="Object" type="object:ObjectType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.172. schema data/rels/EventRiskRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" xmlns:risk="http://www
EUCISE2020
Page 359 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
.cise.eu/datamodel/Entity/Risk/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="qualified"
attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Risk/" schemaLocation="../Entity/Risk/RiskType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Entity/Event/EventType.xsd"/
>
<xs:element name="EventRiskRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Event" type="event:EventType"/>
<xs:element name="Risk" type="risk:RiskType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.173. schema data/rels/CorrespondsToRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" xmlns:operationalass
et="http://www.cise.eu/datamodel/Entity/OperationalAsset/" targetNamespace="http://www.cise.eu/datamodel/rels/" eleme
ntFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/VehicleType.x
sd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/OperationalAsset/" schemaLocation="../Entity/Operationa
lAsset/OperationalAssetType.xsd"/>
<xs:element name="CorrespondsToRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="OperationalAsset" type="operationalasset:OperationalAssetType"/>
<xs:element name="Vehicle" type="object:VehicleType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.174. schema data/rels/CorrelatedWithRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organization/" xmlns:un
iqueidentifier="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" targetNamespace="http://www.cise.eu/datamodel/
rels/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" schemaLocation="../Entity/UniqueIden
tifier/CorrelationEnumType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Organization/" schemaLocation="../Entity/Organization/O
rganizationType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" schemaLocation="../Entity/UniqueIden
tifier/UniqueIdentifierType.xsd"/>
<xs:element name="CorrelatedWithRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="UniqueIdentifierOrigin" type="uniqueidentifier:UniqueIdentifierType"/>
<xs:element name="UniqueIdentifierTarget" type="uniqueidentifier:UniqueIdentifierType"/>
<xs:element name="CorrelationType" type="uniqueidentifier:CorrelationEnumType" minOccurs="0"/
>
<xs:element name="CorrelatedIn" type="xs:dateTime" minOccurs="0"/>
<xs:element name="CorrelatedBy" type="organization:OrganizationType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
EUCISE2020
Page 360 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:complexType>
</xs:element>
</xs:schema>
2.175. schema data/rels/ObjectLocationRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/" xmlns:metadata="
http://www.cise.eu/datamodel/Entity/Metadata/" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" xmlns:perio
d="http://www.cise.eu/datamodel/Entity/Period/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefau
lt="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Metadata/" schemaLocation="../Entity/Metadata/Metadata.
xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/SensorEnumTyp
e.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/LocationRoleE
numType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/PlacementPurp
oseEnumType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/ObjectType.xs
d"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/SourceEnumTyp
e.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/PlannedOperat
ionsEnumType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Entity/Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/PlannedWorksE
numType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="../Entity/Location/LocationT
ype.xsd"/>
<xs:element name="ObjectLocationRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Object" type="object:ObjectType"/>
<xs:element name="Location" type="location:LocationType"/>
<xs:element name="COG" type="xs:double" minOccurs="0"/>
<xs:element name="Heading" type="xs:double" minOccurs="0"/>
<xs:element name="Metadata" type="metadata:Metadata" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="PeriodOfTime" type="period:Period" minOccurs="0"/>
<xs:element name="SourceType" type="object:SourceEnumType" minOccurs="0"/>
<xs:element name="PlacementPurpose" type="object:PlacementPurposeEnumType" minOccurs="0"/>
<xs:element name="PlannedOperations" type="object:PlannedOperationsEnumType" minOccurs="0" ma
xOccurs="unbounded"/>
<xs:element name="PlannedWorks" type="object:PlannedWorksEnumType" minOccurs="0"/>
<xs:element name="SensorType" type="object:SensorEnumType" minOccurs="0"/>
<xs:element name="SOG" type="xs:double" minOccurs="0"/>
<xs:element name="SpecialSecurityMeasures" type="xs:string" minOccurs="0"/>
<xs:element name="Speed" type="xs:double" minOccurs="0"/>
<xs:element name="LocationRole" type="object:LocationRoleEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.176. schema data/rels/EventLocationRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" xmlns:location="http:/
/www.cise.eu/datamodel/Entity/Location/" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" xmlns:period="htt
p://www.cise.eu/datamodel/Entity/Period/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="qu
alified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Entity/Event/EventAreaEnumTy
pe.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/SourceEnumTyp
e.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Entity/Event/LocationRoleInE
EUCISE2020
Page 361 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
ventEnumType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Entity/Event/EventType.xsd"/
>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Entity/Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="../Entity/Location/LocationT
ype.xsd"/>
<xs:element name="EventLocationRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Location" type="location:LocationType"/>
<xs:element name="Event" type="event:EventType"/>
<xs:element name="DateTime" type="period:Period" minOccurs="0"/>
<xs:element name="EventArea" type="event:EventAreaEnumType" minOccurs="0"/>
<xs:element name="LocationRole" type="event:LocationRoleInEventEnumType" minOccurs="0"/>
<xs:element name="SourceType" type="object:SourceEnumType" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.177. schema data/rels/EventDescribedByDocumentRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:document
="http://www.cise.eu/datamodel/Entity/Document/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:event="htt
p://www.cise.eu/datamodel/Entity/Event/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="qua
lified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Entity/Event/EventType.xsd"/
>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="../Entity/Document/DocumentT
ype.xsd"/>
<xs:element name="EventDescribedByDocumentRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Document" type="document:DocumentType"/>
<xs:element name="Event" type="event:EventType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.178. schema data/rels/EventEventRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:event="http://www.cise.eu/datamodel/Entity/Event/" xmlns:period="http://w
ww.cise.eu/datamodel/Entity/Period/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="qualifi
ed" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Entity/Event/EventType.xsd"/
>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Entity/Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Event/" schemaLocation="../Entity/Event/EventRoleInEven
tEnumType.xsd"/>
<xs:element name="EventEventRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="EventOrigin" type="event:EventType"/>
<xs:element name="EventTarget" type="event:EventType"/>
<xs:element name="EventRole" type="event:EventRoleInEventEnumType" minOccurs="0"/>
<xs:element name="InvolvementPeriod" type="period:Period" minOccurs="0"/>
</xs:sequence>
</xs:extension>
EUCISE2020
Page 362 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.179. schema data/rels/RiskDescribedByDocumentRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:document
="http://www.cise.eu/datamodel/Entity/Document/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:risk="http
://www.cise.eu/datamodel/Entity/Risk/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="quali
fied" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Risk/" schemaLocation="../Entity/Risk/RiskType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="../Entity/Document/DocumentT
ype.xsd"/>
<xs:element name="RiskDescribedByDocumentRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Document" type="document:DocumentType"/>
<xs:element name="Risk" type="risk:RiskType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.180. schema data/rels/AgentObjectRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:agent="h
ttp://www.cise.eu/datamodel/Entity/Agent/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:object="http://w
ww.cise.eu/datamodel/Entity/Object/" xmlns:period="http://www.cise.eu/datamodel/Entity/Period/" targetNamespace="http
://www.cise.eu/datamodel/rels/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/AgentRoleInObje
ctEnumType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/DutyEnumType.xs
d"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/ObjectType.xs
d"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Entity/Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/AgentType.xsd"/
>
<xs:element name="AgentObjectRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Agent" type="agent:AgentType"/>
<xs:element name="Object" type="object:ObjectType"/>
<xs:element name="AgentRole" type="agent:AgentRoleInObjectEnumType" minOccurs="0"/>
<xs:element name="Duty" type="agent:DutyEnumType" minOccurs="0"/>
<xs:element name="InvolvementPeriod" type="period:Period" minOccurs="0"/>
<xs:element name="TransitPassenger" type="xs:boolean" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.181. schema data/rels/CargoCargoUnitRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:cargo="h
ttp://www.cise.eu/datamodel/Entity/Cargo/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" targetNamespace="http:
//www.cise.eu/datamodel/rels/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Cargo/" schemaLocation="../Entity/Cargo/CargoUnitType.x
sd"/>
EUCISE2020
Page 363 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Cargo/" schemaLocation="../Entity/Cargo/CargoType.xsd"/
>
<xs:element name="CargoCargoUnitRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Cargo" type="cargo:CargoType"/>
<xs:element name="CargoUnit" type="cargo:CargoUnitType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.182. schema data/rels/AgentLocationRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:agent="h
ttp://www.cise.eu/datamodel/Entity/Agent/" xmlns:entity="http://www.cise.eu/datamodel/Entity/" xmlns:location="http:/
/www.cise.eu/datamodel/Entity/Location/" xmlns:period="http://www.cise.eu/datamodel/Entity/Period/" targetNamespace="
http://www.cise.eu/datamodel/rels/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/AgentRoleInLoca
tionEnumType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Period/" schemaLocation="../Entity/Period/Period.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Agent/" schemaLocation="../Entity/Agent/AgentType.xsd"/
>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="../Entity/Location/LocationT
ype.xsd"/>
<xs:element name="AgentLocationRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Agent" type="agent:AgentType"/>
<xs:element name="Location" type="location:LocationType"/>
<xs:element name="AgentRole" type="agent:AgentRoleInLocationEnumType" minOccurs="0"/>
<xs:element name="InvolvementPeriod" type="period:Period" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.183. schema data/rels/ObjectRiskRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:49] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:object="http://www.cise.eu/datamodel/Entity/Object/" xmlns:risk="http://w
ww.cise.eu/datamodel/Entity/Risk/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="qualified
" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Risk/" schemaLocation="../Entity/Risk/RiskType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Object/" schemaLocation="../Entity/Object/ObjectType.xs
d"/>
<xs:element name="ObjectRiskRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Risk" type="risk:RiskType"/>
<xs:element name="Object" type="object:ObjectType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
EUCISE2020
Page 364 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
2.184. schema data/rels/RiskLocationRel.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rels="http://www.cise.eu/datamodel/rels/" xmlns:entity="
http://www.cise.eu/datamodel/Entity/" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/" xmlns:risk="http
://www.cise.eu/datamodel/Entity/Risk/" targetNamespace="http://www.cise.eu/datamodel/rels/" elementFormDefault="quali
fied" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Risk/" schemaLocation="../Entity/Risk/RiskType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/" schemaLocation="../Entity/EntityType.xsd"/>
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="../Entity/Location/LocationT
ype.xsd"/>
<xs:element name="RiskLocationRel">
<xs:complexType>
<xs:complexContent>
<xs:extension base="entity:EntityType">
<xs:sequence>
<xs:element name="Risk" type="risk:RiskType"/>
<xs:element name="Location" type="location:LocationType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:schema>
2.185. schema data/FormalOrganization.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Organization/" schemaLocation="Entity/Organization/Form
alOrganizationType.xsd"/>
<xs:element name="FormalOrganization" type="organization:FormalOrganizationType"/>
</xs:schema>
2.186. schema data/Anomaly.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:anomaly="http://www.cise.eu/datamodel/Entity/Anomaly/" e
lementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Anomaly/" schemaLocation="Entity/Anomaly/AnomalyType.xs
d"/>
<xs:element name="Anomaly" type="anomaly:AnomalyType"/>
</xs:schema>
2.187. schema data/LawInfringementIncident.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Incident/" schemaLocation="Entity/Incident/LawInfringem
entIncidentType.xsd"/>
<xs:element name="LawInfringementIncident" type="incident:LawInfringementIncidentType"/>
</xs:schema>
2.188. schema data/Catch.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:46] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cargo="http://www.cise.eu/datamodel/Entity/Cargo/" eleme
ntFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Cargo/" schemaLocation="Entity/Cargo/CatchType.xsd"/>
<xs:element name="Catch" type="cargo:CatchType"/>
</xs:schema>
2.189. schema data/OrganizationalUnit.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Organization/" schemaLocation="Entity/Organization/Orga
EUCISE2020
Page 365 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
nizationalUnitType.xsd"/>
<xs:element name="OrganizationalUnit" type="organization:OrganizationalUnitType"/>
</xs:schema>
2.190. schema data/Location.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:location="http://www.cise.eu/datamodel/Entity/Location/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Location/" schemaLocation="Entity/Location/LocationType
.xsd"/>
<xs:element name="Location" type="location:LocationType"/>
</xs:schema>
2.191. schema data/Person.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:person="http://www.cise.eu/datamodel/Entity/Person/" ele
mentFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Person/" schemaLocation="Entity/Person/PersonType.xsd"/
>
<xs:element name="Person" type="person:PersonType"/>
</xs:schema>
2.192. schema data/UniqueIdentifier.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:uniqueidentifier="http://www.cise.eu/datamodel/Entity/Un
iqueIdentifier/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/UniqueIdentifier/" schemaLocation="Entity/UniqueIdentif
ier/UniqueIdentifierType.xsd"/>
<xs:element name="UniqueIdentifier" type="uniqueidentifier:UniqueIdentifierType"/>
</xs:schema>
2.193. schema data/RiskDocument.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="Entity/Document/RiskDocument
Type.xsd"/>
<xs:element name="RiskDocument" type="document:RiskDocumentType"/>
</xs:schema>
2.194. schema data/Risk.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:risk="http://www.cise.eu/datamodel/Entity/Risk/" element
FormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Risk/" schemaLocation="Entity/Risk/RiskType.xsd"/>
<xs:element name="Risk" type="risk:RiskType"/>
</xs:schema>
2.195. schema data/EventDocument.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="Entity/Document/EventDocumen
tType.xsd"/>
<xs:element name="EventDocument" type="document:EventDocumentType"/>
</xs:schema>
2.196. schema data/PortOrganization.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:50] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:organization="http://www.cise.eu/datamodel/Entity/Organi
zation/" elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Organization/" schemaLocation="Entity/Organization/Port
EUCISE2020
Page 366 / 367
EUCISE2020 : Technical Specifications
Deliverable D4.3
Revision 1.0
OrganizationType.xsd"/>
<xs:element name="PortOrganization" type="organization:PortOrganizationType"/>
</xs:schema>
2.197. schema data/OrganizationDocument.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:47] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:document="http://www.cise.eu/datamodel/Entity/Document/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Document/" schemaLocation="Entity/Document/Organization
DocumentType.xsd"/>
<xs:element name="OrganizationDocument" type="document:OrganizationDocumentType"/>
</xs:schema>
2.198. schema data/CrisisIncident.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by EC JRC XSD Generator v1.0.0-SNAPSHOT [model: Data Model V1.4 - gendate: 2015-11-06 11:32:48] -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:incident="http://www.cise.eu/datamodel/Entity/Incident/"
elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:import namespace="http://www.cise.eu/datamodel/Entity/Incident/" schemaLocation="Entity/Incident/CrisisIncide
ntType.xsd"/>
<xs:element name="CrisisIncident" type="incident:CrisisIncidentType"/>
</xs:schema>
EUCISE2020
Page 367 / 367