The Cruise pattern describes ocean science cruises. This pattern is obtained by combining and reusing existing patterns, while keeping the amount of abstract ontological commitments to a minimum.
The Cruise pattern can be dissected into three parts. First, a cruise is an abstraction of a path/route undertaken by a vessel, which is a physical object, through space within a certain time duration. This is captured by modeling a cruise to have exactly one trajectory, consisting of spatiotemporal segments traversed by a vessel. Second, a cruise can be understood as an event, which provides role performed by agents, pertaining activities conducted in/during a cruise. Our modeling of event through the Event pattern views events as something that not only provide roles to agents, but also occurs within some spatiotemporal boundary. Consequently, the first and second parts mentioned earlier can be together seen as a kind of complicated event. In fact, both the first and second parts motivate the alignment with the Agent pattern, Agent Role pattern, and obviously, the Event pattern. Alignment with the Event pattern is in particular rather complicated since the spatiotemporal information of a cruise is implicitly given by its associated trajectory.
Next, for the third part, we understand that a cruise may have other, non-spatiotemporal information relevant to it. For instance, information about funding awards that fund it, or programs associated with it. This is modeled by reusing the Information Object pattern. Note that every information object can be realized by a number of information realization, which includes digital objects (papers, reports, etc.) about the cruise. All the above modeling choices allows us to distinguish a cruise from both the information object that describes it and the physical object, i.e., vessel, by which it is undertaken.
IRI: http://schema.geolink.org/1.0/pattern/cruise#Cruise
IRI: http://schema.geolink.org/1.0/pattern/cruise#Port
Represents ports that may be relevant for a cruise.
IRI: http://schema.geolink.org/1.0/pattern/cruise#CruiseTrajectory
A trajectory is given by a collection of fixes, representing time-stamped locations. Non-spatiotemporal information specific to a fix can be included by assigning it some attributes, for example, to indicate that the fix is the arrival to some port stop. The ordering of the fixes is based on their temporal information, although such an ordering is not axiomatized in this pattern. Between two consecutive fixes, we can define a segment, which is traversed by some moving object. There is no requirement forcing that all segments in the trajectory can only be traversed by the same moving object.
In the context of GeoLink project, the data typically already contains ordering of fixes, i.e., the nextFix relation is explicit in the data, and thus, segments are auto-instantiated from it. This is motivated by real scenarios whereby indeed only properties of fixes will often be known, in particular their locations, and temporal extension, whether they are at ports, whether they are arrival or departure fixes from ports, and in which sequence the fixes occurred. The traversing vessel will usually also be known. However, trajectory segments to which the trajectory pattern attaches information about the vessel are usually not explicitly represented in the data.
IRI: http://schema.geolink.org/1.0/pattern/cruise#atPort
atPort connects a fix to an instance of Port. It is used when the fix corresponds to a port stop in the beginning, middle, or end of a cruise.
IRI: http://schema.geolink.org/1.0/pattern/cruise#hasRelatedCruise
IRI: http://schema.geolink.org/1.0/pattern/cruise#hasTrajectory
The hasTrajectory connects a cruise to its trajectory.
IRI: http://schema.geolink.org/1.0/pattern/cruise#r_Port
The class Port typecasted as an object property. Logically, r_Port(x,x) <-> Port(x)
IRI: http://schema.geolink.org/1.0/pattern/cruise#traveledBy
If a cruise is undertaken by a vessel, then its trajectory is traveled by the vessel.
IRI: http://schema.geolink.org/1.0/pattern/cruise#undertakenBy
This connects a cruise to the vessel on which the cruise is conducted.
IRI: http://schema.geolink.org/1.0/pattern/cruise#DASE_RULE
fix and (atPortop some Portc) is subclass of
inverse has fix only Trajectoryc
segment and (traversed by some vessel) is subclass of
inverse has segment only Trajectoryc
agent role, Cruisec, Trajectoryc, Portc, funding award, information object, program, fix, position, segment, vessel
This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.
A cruise is an event through the alignment with Event pattern. A cruise has exactly one trajectory, is undertaken by exactly one vessel, and is described by exactly one information object. Additionally, this information object describes exactly only the cruise. If a cruise is undertaken by a vessel, then the trajectory of the cruise has to be traveled by the vessel. Note that since isTraveledBy is implied by a property chain, OWL 2 specification forbids us to express a cardinality restriction using this peroperty. Consequently, we cannot axiomatize that the trajectory of a cruise can only be traveled by one vessel.
Involvements of agents in a cruise is modeled via the AgentRole, which is aligned to the Agent Role pattern. A cruise may be funded by some funding award, associated with some program, and related to some other cruise. These information are attached to the information object associated with a cruise.