You are granted a license to use, reproduce and create derivative works of this document under Creative Commons Attribution 3.0 Unported License. This copyright applies todatAcron Ontology specification and RDF.
Motivated by real-life emerging needs in critical domains, this ontology provides a coherent and generic representation of semantic trajectories, in association with related events and contextual information. The main contribution of this ontology is the representation of semantic trajectories at different levels of spatiotemporal analysis. This version currently focus on aviation and maritime conceptualizations.
Many critical domains w.r.t. economy and safety, such as the Maritime and the Aviation domains, where Situation Awareness (MSA) and Air Traffic Management (ATM), respectively, are of importance, require analysis of moving objects’ behaviour over time: Challenges concern effective detection and forecasting of moving entities’ trajectories, as well as recognition and prediction of important events by exploiting information about entities’ behaviour and contextual data. Due to these needs, semantic trajectories are turned into “first-class citizens”, forming a paradigm shift towards operations that are built and revolve around the notion of trajectory. Our work focuses on trajectories and aims to build solutions towards managing data that are connected via, and contribute to enriched views of trajectories: Doing so, we revisit the notion of semantic trajectory and build on it. Specifically, it is expected that we will be able torepresent, store and manipulate the wealth ofinformation available in disparate and heterogeneous data sources, integrated in arepresentation where trajectories are the main entities, towards computing meaningfulmoving patterns so as to recognize and predict the behaviour and states ofmoving objects. Therefore, motivated by real-life emerging needs in MSA and ATM domains, this paper proposes a coherent and generic ontology for the representation of semantic trajectories, in association with related events and contextual information.The main contribution of the proposedontology is the representation of semantic trajectories at different levels ofspatio-temporal analysis: Trajectories may be seen as temporal sequences of moving objects’ positions derived from raw data, of mere geometries, oftemporal sequences of raw data aggregations signifying meaningful events(generalizing on the stops and moves model [8]), providing a synoptic view of raw trajectories [7], and as temporal sequences of non-overlapping meaningfultrajectories segments (each revealing specific behaviour, event, goal, activityetc). Representations at any such level of analysis should be linked to each other, as well as to contextual information and co-occurring events: These are important features for performing informed analysis tasks at different levels of detail/analysis, consulting raw data and/or semantic information associated with it.
Existing approaches for the representation of semantic trajectories either (a) use plain textual annotations instead of semantic links to other entities [1], [2], [3], hindering the provision of a fully-fledged representation where trajectories are semantically linked with other data or with semantic resources associated with moving objects’ behaviour; (b) constrain the types of events that can be used for structuring a trajectory [1], [2]; or (c) make assumptions on the constituents of trajectories [3], [6], [4] (e.g. semantic trajectories in [3] are sequences of sub-trajectories, while in [4] are sequences of episodes). To a greater extent than previous proposals, the proposed ontologysupports the representation of trajectoriesat multiple, interlinked levels of analysis: For instance, although [4] provides a rich set of constructs for the representation of semantic trajectories, these are sequences of episodes, each associated with raw trajectory data, and optionally, with a spatio-temporal model of movement. However, there is no fine association between abstract models of movements and raw data. On the other hand, [3] provides a two-levels analysis where semantic trajectories are lists of semantic sub-trajectories, and each sub-trajectory in its own turn is a list of semantic points. Regarding events and episodes, these are connected to specific resources at specific levels of analysis: In [3] events -mostly related to the environment rather than to the trajectory itself- are connected to points only (something that may lead to ambiguities in some cases), while in [4] episodes concern things happening in the trajectory itself, and may be associated to specific models of movement: It is not clear how multiple models of a single trajectory -each at a different level of analysis- connected to a single episode, are associated. Finally, contextual information in [4] is related to movement models, episodes or semantic trajectories, which is quite generic, while in [3] environment attributes are associated to points only, and are assigned specific values.
The datAcron ontology was developed by group consensus over a period of 12 months following the HCOME methodology [5]. It has been designed to be used as a core ontology for the MSA and ATM domains, following a data-driven approach towards supporting analysis tasks. Its development has been driven by ontologies related to our objectives (e.g. DUL, SimpleFeature, NASA Sweet and SSN) as well as schemas and specifications regarding data sources from the different domains.
The main concepts and properties in the datAcron ontology regarding trajectories, are depicted in Figure 1. Starting from the definitions about raw, structured and
semantic trajectories provided in [7], araw trajectory is a temporal sequence of raw data specifying the moving object’s spatio-temporal positions. Raw data can be aggregated, analyzed and semantically annotated, providing multiple abstractions of a trajectory. A maximal sequence of raw data that comply with a given pattern, define anepisode. In this work we focus onevents as a generalisation of episodes, taking also into consideration -in conjunction to movement data-contextual information (i.e. any information -mostly about the environment of an object- that affects its movement).
Events represent specific, aggregated or abstract happenings instantiating an event pattern (whose description is not part of the ontology) and are distinguished to
low-level events regarding information about a single trajectory, isolated from its context, andhigh-level events regarding information from multiple objects’ trajectories and/or contextual information. Each event is associated with one or more moving objects, and it has spatial, temporal and domain-specific
properties.
A semantic trajectory consists of a sequence of temporally non-overlapping trajectory parts that can be eithersemantic nodes, raw positions reported from sensing devises, or trajectory segments. Each trajectory part may be associated to a specificgeometry, representing a point or region of occurrence, and atemporal entity specifying an instant or time interval of occurrence. A semantic node provides a meaningful abstraction or aggregation of raw positions. E.g. a set of raw positions may signify a “turn” event: This set can be represented as a single semantic node, associated to a low-level event of type “turn”. Each semantic node or trajectory segment, may be associated with any trajectory part at a finer level of analysis; e.g. with a set of raw positions representing a “turn” or the last and first point of a “gap of communication”. Atrajectory segment is a trajectory itself, part of a whole trajectory. Segmentation of trajectories can be done with different objectives depending on the application and target analysis. A structured trajectory is a meaningful sequence of non-overlapping semantic trajectory parts. Any trajectory part may be associated with an event that co-occurs with it spatially and/or temporally: E.g. A bad weather region may co-occur with a trajectory crossing-it (thus, related spatially) during a time period (related temporally). It must be pointed out that each trajectory part can be associated with different trajectories of the same moving object: E.g. with the planned and with the actual trajectory of that object.
According to the above specifications, and as Figure 1 shows, a trajectory -for instance- can be segmented to non-overlapping semantic trajectory segments, each corresponding to one or more semantic nodes. Each semantic node may be associated with a specific raw position or a temporally ordered sequence of raw positions of a moving object. Trajectory parts can be associated with contextual information, and they can be associated with events that happen independently from the trajectory but co-occur with the trajectory affecting the moving object’s behaviour. In such a representation, one may consider a trajectory either as a list of non-overlapping trajectory segments, or as lists of semantic nodes, or even lists of raw trajectory data, or as a simple geometric object occurring in a specific time interval, also considering different mixtures of these levels of analysis, depending on analysis needs. Furthermore, it must be noticed that the notion of event comprises happenings due to the trajectory itself (e.g. a “gap of communication”) also in conjunction to contextual information (e.g. vessel in a protected or in a bad-weather area). Such events, associated to constructs at any level of abstraction can be further inspected and justified by information at lower-levels of analysis, or be further abstracted and generalised to more abstract levels.
One of the simple queries that could be constructed, is to retrieve all the archived sector configurations, the airspaces affected, the time period and the corresponding capacities. The following listing demonstrates the query in SPARQL:
Since capacity value "999" indicates “undefined capacity”, we can improve the above query with a FILTER operator, e.g.
Obviously, the above query can be further restricted to a specific airspace, configuration or time window. For example, a query requesting all the archived sector configurations for airspace :Airspace_LSAGCTA, is:
The above query returns 2049 results since the airspace :Airspace_LSAGCTA is the most frequently configured airspace in our archived triples. Indeed, a query that retrieves the frequency of configurations applied on all airspaces, would be:
Finally, a query that requests the sector configurations that hold for a specific time window, e.g. between 2016-04-28T00:00:00 and 2016-04-28T05:00:00, will be:
Please notice that in this example we use a string comparison to the values of ?start and ?end. Another approach can be using the xsd namespace1 , as indicated in the Virtuoso guide2
One of the core concepts in the datAcron ontology is the trajectory and its parts, i.e. trajectory segments or nodes. A query for the URIs of regulated flights, departure, destination and their intended trajectories in SPARQL will be:
Please, notice that the property path dul:hasConstituent/:hasWKT in this example returns the well-known-text (WKT) of the geometry of each trajectory, i.e. there is no need to traverse the semantic nodes of each trajectory in order to construct the geometry of the trajectory. Specifically, the above query restricted for the intended trajectory of the flight plan :flight_plan_AA51136505, will be:
The trajectory in the result, departures from the airport of Beograd Surcin and arrives at “Charles De Gaulle” of Paris, as illustrated in the following figure 2
The trajectory parts can be either a sequence of segments or a sequence of nodes. Each segment can also be a sequence of segments or nodes and so on. A trajectory is related with its parts with the property :hasPart which is sub-property of the transitive property dul:hasPart. For example, we can get the position, time instance, and any other linked information of each semantic node of a trajectory (e.g. :traj_AA51114077_20160401003000), using the query:
where ?p will return any links asserted for each ?node and ?o, (e.g. such as nearby weather conditions or spatial relations).
The spatio-temporal information of each trajectory or trajectory part, we can be further employed in spatio-temporal queries, using the predefined in the triple store functions. For example, to retrieve all the vessels that had been (at some time) within a range of 5Km from the point (13.139045 44.466133), we can submit the following query:
where bif:st_distance() computes the distance between two geometries, and bif:st_geomfromtext() constructs the geometry from its WKT value. The above query further more requests (optionally) events linked to each node and weather conditions.
We can also filter the temporal values of nodes, i.e. using the variable ?time in FILTER expressions. For example, to retrieve only those vessels that had been around the point 13.139045 44.466133 and between "2016-01-08 14:12:41" and "2016-01-08 16:12:41", the query will be:
A similar spatial query, is to retrieve all the semantic nodes of vessels that have crossed a specific area. In this case, the geometry of the area of interest is also required, i.e. it can be any geometry related to a resource in the store (e.g. a Natura2000 region), or it can be manually defined as a Well-Known-Text. For example, the following query will retrieve all the vessels within an area defined by "POLYGON((10 50,15 50,15 40,10 40,10 50))", for "2016-01-08":
A refinement of the above query, will be the retrieval of all the semantic nodes in the area of interest, for a specific day/time (or interval), and for a specific vessel. For example, we can request the semantic nodes of vessel :ves209996000, and the status of the vessel at each semantic node, for the above area and any time after "2016-01-08", ordered by ?time:
Another example query, is the retrieval of sector configurations with the activated airblocks:
The result set can be exported to CSV and given the serialized geometries of airblocks, the sector configurations can be visualized in any GIS software.
IRI: http://www.datacron-project.eu/datAcron#ADRBoundaryWaypoint
IRI: http://www.datacron-project.eu/datAcron#ADRRefWaypoint
IRI: http://www.datacron-project.eu/datAcron#ATC_AccidentCausedRegulation
IRI: http://www.datacron-project.eu/datAcron#ATC_AerodromeCapacityRegulation
G: Aerodrome capacity
IRI: http://www.datacron-project.eu/datAcron#ATC_AirportFalicilitiesLimitationRegulation
87: Airport Facilities, parking stands, ramp congestion, buildings, gate limitations, ...
IRI: http://www.datacron-project.eu/datAcron#ATC_AirspaceManagementRegulation
M: Airspace management
IRI: http://www.datacron-project.eu/datAcron#ATC_Capacity
C: ATC capacity regulation
IRI: http://www.datacron-project.eu/datAcron#ATC_DeIcingRegulation
D: De-Icing
IRI: http://www.datacron-project.eu/datAcron#ATC_EnvironmentalIssueRegulation
V: Environmental issue like noise
IRI: http://www.datacron-project.eu/datAcron#ATC_Equipment
T: ATC equipment
IRI: http://www.datacron-project.eu/datAcron#ATC_ImmigrationCustomsHealthRegulation
86: Immigration, Customs, Health
IRI: http://www.datacron-project.eu/datAcron#ATC_IndustrialAction
I: ATC industrial action
IRI: http://www.datacron-project.eu/datAcron#ATC_OtherRegulation
O: Other
IRI: http://www.datacron-project.eu/datAcron#ATC_OtherRegulationAtDestination
88: Restrictions at airport of destination, airport/runway closed due obstruction, industrial action, staff shortage, political unrest, noise abatement, night curfew, special flights, ...
IRI: http://www.datacron-project.eu/datAcron#ATC_RestrictionAtDepartureRegulation
89: Restrictions at airport of departure, airport/runway closed due obstruction, industrial action, staff shortage, political unrest, noise abatement, night curfew, special flights, start-up and pushback, ...
IRI: http://www.datacron-project.eu/datAcron#ATC_RestrictionAtDestinationRegulation
83: ATC restriction at destination
IRI: http://www.datacron-project.eu/datAcron#ATC_RestrictionRegulation
81: ATC restriction en-route or capacity
IRI: http://www.datacron-project.eu/datAcron#ATC_RestrictionStaffShortageRegulation
82: ATC restriction due to staff shortage or equipment failure en-route
IRI: http://www.datacron-project.eu/datAcron#ATC_RestrictionWeatherAtDestinationRegulation
84: ATC restriction due to weather at destination
IRI: http://www.datacron-project.eu/datAcron#ATC_Routing
R: ATC routing
IRI: http://www.datacron-project.eu/datAcron#ATC_SecurityRegulation
85: Mandatory security
IRI: http://www.datacron-project.eu/datAcron#ATC_SpecialEventRegulation
P: Special event
IRI: http://www.datacron-project.eu/datAcron#ATC_Staffin
S: ATC staffin
IRI: http://www.datacron-project.eu/datAcron#ATC_WeatherAlternateRegulation
73: Weather en route and alternate
IRI: http://www.datacron-project.eu/datAcron#ATC_WeatherRegulation
W: Weather
IRI: http://www.datacron-project.eu/datAcron#ATSRoute
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Abstract
Any Entity that cannot be located in space-time. E.g. mathematical entities: formal semantics elements, regions within dimensional spaces, etc.
IRI: http://www.datacron-project.eu/datAcron#Accommodation_Barge
IRI: http://www.datacron-project.eu/datAcron#Accommodation_Jack_Up
IRI: http://www.datacron-project.eu/datAcron#Accommodation_Platform
IRI: http://www.datacron-project.eu/datAcron#Accommodation_Ship
IRI: http://www.datacron-project.eu/datAcron#Accommodation_Vessel
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Action
An Event with at least one Agent that isParticipantIn it, and that executes a Task that typically isDefinedIn a Plan, Workflow, Project, etc.
IRI: http://www.datacron-project.eu/datAcron#ActualTrajectory
A trajectory built upon the actual (raw or aggregated) sequence of positions of the moving object
IRI: http://www.datacron-project.eu/datAcron#Aerodrome
IRI: http://www.datacron-project.eu/datAcron#AerodromeClassA
All operations must be conducted under IFR. All aircraft are subject to ATC clearance. All flights are separated from each other by ATC.
IRI: http://www.datacron-project.eu/datAcron#AerodromeClassB
Operations may be conducted under IFR, SVFR, or VFR. All aircraft are subject to ATC clearance. All flights are separated from each other by ATC.
IRI: http://www.datacron-project.eu/datAcron#AerodromeClassC
Operations may be conducted under IFR, SVFR, or VFR. All aircraft are subject to ATC clearance (country-specific variations notwithstanding). Aircraft operating under IFR and SVFR are separated from each other and from flights operating under VFR, but VFR flights are not separated from each other. Flights operating under VFR are given traffic information in respect of other VFR flights.
IRI: http://www.datacron-project.eu/datAcron#AerodromeClassD
Operations may be conducted under IFR, SVFR, or VFR. All flights are subject to ATC clearance (country-specific variations notwithstanding). Aircraft operating under IFR and SVFR are separated from each other, and are given traffic information in respect of VFR flights. Flights operating under VFR are given traffic information in respect of all other flights.
IRI: http://www.datacron-project.eu/datAcron#AerodromeClassE
Operations may be conducted under IFR, SVFR, or VFR. Aircraft operating under IFR and SVFR are separated from each other, and are subject to ATC clearance. Flights under VFR are not subject to ATC clearance. As far as is practical, traffic information is given to all flights in respect of VFR flights.
IRI: http://www.datacron-project.eu/datAcron#AerodromeClassF
Operations may be conducted under IFR or VFR. ATC separation will be provided, so far as practical, to aircraft operating under IFR. Traffic Information may be given as far as is practical in respect of other flights.
IRI: http://www.datacron-project.eu/datAcron#AerodromeClassG
Operations may be conducted under IFR or VFR. ATC has no authority but VFR minimums are to be known by pilots. Traffic Information may be given as far as is practical in respect of other flights.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Agent
Additional comment: a computational agent can be considered as a PhysicalAgent that realizes a certain class of algorithms (that can be considered as instances of InformationObject) that allow to obtain some behaviors that are considered typical of agents in general. For an ontology of computational objects based on DOLCE see e.g. http://www.loa-cnr.it/COS/COS.owl, and http://www.loa-cnr.it/KCO/KCO.owl.
IRI: http://www.datacron-project.eu/datAcron#Aggregates_Barge
IRI: http://www.datacron-project.eu/datAcron#Aggregates_Carrier
IRI: http://www.datacron-project.eu/datAcron#Air_Cushion_Passenger_Ship
IRI: http://www.datacron-project.eu/datAcron#Air_Cushion_Patrol_Vessel
IRI: http://www.datacron-project.eu/datAcron#Air_Cushion_Ro-Ro_Passenger_Sh
IRI: http://www.datacron-project.eu/datAcron#Air_Cushion_Vessel
IRI: http://www.datacron-project.eu/datAcron#Air_Cushion_Work_Vessel
IRI: http://www.datacron-project.eu/datAcron#Aircraft
The class of moving objects with flying capabilities. Please notice that aviation specific classes and properties are provided in a separate module
IRI: http://www.datacron-project.eu/datAcron#AircraftModel
IRI: http://www.datacron-project.eu/datAcron#AircraftOwner
An operator who owns at least one aircraft. It can be identified by the operator's ICAO code, or it can be private or unknown.
IRI: http://www.datacron-project.eu/datAcron#Airline
IRI: http://www.datacron-project.eu/datAcron#Airship_hanger
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Amount
A quantity, independently from how it is measured, computed, etc.
IRI: http://www.datacron-project.eu/datAcron#Anchor_Handling_Fire_Fighting
IRI: http://www.datacron-project.eu/datAcron#Anchor_Handling_Salvage_Tug
IRI: http://www.datacron-project.eu/datAcron#Anchor_Handling_Vessel
IRI: http://www.datacron-project.eu/datAcron#Antenna
IRI: http://www.datacron-project.eu/datAcron#AntiPollution_Vessel
IRI: http://www.datacron-project.eu/datAcron#ArrivalLeg
A portion of an arrival procedure (STAR) as defined by two consecutive significant points.
IRI: http://www.datacron-project.eu/datAcron#Articulated_Pusher_Tug
IRI: http://www.datacron-project.eu/datAcron#Asphalt_Bitumen_Tanker
IRI: http://www.datacron-project.eu/datAcron#AviationLowLevelEvent
IRI: http://www.datacron-project.eu/datAcron#AviationRoute
IRI: http://www.datacron-project.eu/datAcron#Backhoe_Dredger
IRI: http://www.datacron-project.eu/datAcron#Balloonport
IRI: http://www.datacron-project.eu/datAcron#Barge
IRI: http://www.datacron-project.eu/datAcron#Barge_Carrier
IRI: http://www.datacron-project.eu/datAcron#Beacon
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#BiologicalObject
IRI: http://www.datacron-project.eu/datAcron#BlacklistReport
IRI: http://www.datacron-project.eu/datAcron#blacklisted
A blacklisted vessel
IRI: http://www.datacron-project.eu/datAcron#Box
IRI: http://www.datacron-project.eu/datAcron#Bucket_Dredger
IRI: http://www.datacron-project.eu/datAcron#Bucket_Dredger_Pontoon
IRI: http://www.datacron-project.eu/datAcron#Bucket_Hopper_Dredger
IRI: http://www.datacron-project.eu/datAcron#Bucket_Ladder_Dredger
IRI: http://www.datacron-project.eu/datAcron#Bucket_Wheel_Suction_Dredger
IRI: http://www.datacron-project.eu/datAcron#BulkCarrier
Bulk carrier means a ship which is constructed generally with single deck, top-side tanks and hopper side tanks in cargo spaces, and is intended primarily to carry dry cargo in bulk, and includes such types as ore carriers and combination carriers. (SOLAS IX/1.6). Bulk carrier means a ship which is intended primarily to carry dry cargo in bulk, including such types as ore carriers and combination carriers. (SOLAS XII/1.1)
IRI: http://www.datacron-project.eu/datAcron#Bulk_Carrier
IRI: http://www.datacron-project.eu/datAcron#Bulk_Carrier_With_Vehicle_Deck
IRI: http://www.datacron-project.eu/datAcron#Bulk_Storage_Barge
IRI: http://www.datacron-project.eu/datAcron#Bulker
IRI: http://www.datacron-project.eu/datAcron#Bunker
A bunker is generally applied to the storage of petroleum products in tanks, and the practice and business of refueling ships. Bunkering operations are located at seaports, and they include the storage of bunker (ship) fuels and the provision of the fuel to vessels. Bunkering includes the shipboard logistics of loading fuel and distributing it among available bunkers (on-board fuel tanks).
IRI: http://www.datacron-project.eu/datAcron#Bunkering_Tanker
IRI: http://www.datacron-project.eu/datAcron#Buoy
An anchored float serving as a navigation mark, to show reefs or other hazards, or for mooring
IRI: http://www.datacron-project.eu/datAcron#Buoy-Laying_Vessel
IRI: http://www.datacron-project.eu/datAcron#Cable_Layer
IRI: http://www.datacron-project.eu/datAcron#Cabu_Carrier
IRI: http://www.datacron-project.eu/datAcron#Cape
IRI: http://www.datacron-project.eu/datAcron#Cargo_Barge
IRI: http://www.datacron-project.eu/datAcron#Cargo_Containership
IRI: http://www.datacron-project.eu/datAcron#CargoHazard_A_Major
IRI: http://www.datacron-project.eu/datAcron#CargoHazard_C_Minor
IRI: http://www.datacron-project.eu/datAcron#CargoHazard_D_Recognizable
IRI: http://www.datacron-project.eu/datAcron#Cargo_Vessel
IRI: http://www.datacron-project.eu/datAcron#Cement_Barge
IRI: http://www.datacron-project.eu/datAcron#Cement_Carrier
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#ChemicalObject
IRI: http://www.datacron-project.eu/datAcron#Chemical_Tanker
IRI: http://www.datacron-project.eu/datAcron#City
IRI: http://www.datacron-project.eu/datAcron#Civil_Aerodrome
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Classification
A special kind of Situation that allows to include time indexing for the classifies relation in situations. For example, if a Situation s 'my old cradle is used in these days as a flower pot' isSettingFor the entity 'my old cradle' and the TimeIntervals '8June2007' and '10June2007', and we know that s satisfies a functional Description for aesthetic objects, which defines the Concepts 'flower pot' and 'flower', then we also need to know what concept classifies 'my old cradle' at what time. In order to solve this issue, we need to create a sub-situation s' for the classification time: 'my old cradle is a flower pot in 8June2007'. Such sub-situation s' isPartOf s.
IRI: http://www.datacron-project.eu/datAcron#ClosedTrajectory
A Trajectory where the destination is reached
IRI: http://www.datacron-project.eu/datAcron#Co2_Tanker
IRI: http://www.datacron-project.eu/datAcron#CoastalBreakwaterPort
Coastal Breakwater port.
IRI: http://www.datacron-project.eu/datAcron#CoastalNaturalPort
Coastal Natural port.
IRI: http://www.datacron-project.eu/datAcron#CoastalTideGatePort
Coastal Tide Gate port.
IRI: http://www.datacron-project.eu/datAcron#Coastline
A line following the general contour of the shore, except that in cases of inlets or bays less than 30 nautical miles in width, the line shall pass directly across the inlet or bay to intersect the general contour on the opposite side.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Collection
Any container for entities that share one or more common properties. E.g. "stone objects", "the nurses", "the Louvre Aegyptian collection", all the elections for the Italian President of the Republic. A collection is not a logical class: a collection is a first-order entity, while a class is second-order.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Collective
A Collection whose members are agents, e.g. "the nurses", "the Italian rockabilly fans". Collectives, facon de parler, can act as agents, although they are not assumed here to be agents (they are even disjoint from the class SocialAgent). This is represented by admitting collectives in the range of the relations having Agent in their domain or range.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#CollectiveAgent
A SocialAgent that is actedBy agents that are (and act as) members of a Collective. A collective agent can have roles that are also roles of those agents. For example, in sociology, a 'group action' is the situation in which a number of people (that result to be members of a collective) in a given area behave in a coordinated way in order to achieve a (often common) goal. The Agent in such a Situation is not single, but a CollectiveAgent (a Group). This can be generalized to the notion of social movement, which assumes a large Community or even the entire Society as agents. The difference between a CollectiveAgent and an Organization is that a Description that introduces a CollectiveAgent is also one that unifies the corresponding Collective. In practice, this difference makes collective agents 'less stable' than organizations, because they have a dedicated, publicly recognizable Description that is conceived to introduce them.
IRI: http://www.datacron-project.eu/datAcron#Combat_Vessel
IRI: http://www.datacron-project.eu/datAcron#Command_Vessel
IRI: http://www.datacron-project.eu/datAcron#Communication_tower
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Community
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Concept
A Concept is a SocialObject, and isDefinedIn some Description; once defined, a Concept can be used in other Description(s). If a Concept isDefinedIn exactly one Description, see the LocalConcept class. The classifies relation relates Concept(s) to Entity(s) at some TimeInterval
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Configuration
A
collection whose members are 'unified', i.e. organized according to a
certain schema that can be represented by a Description.
Typically, a configuration is the collection that emerges out of a
composed entity: an industrial artifact, a plan, a discourse, etc.
E.g.
a physical book has a configuration provided by the part-whole schema
that holds together its cover, pages, ink. That schema, based on the
individual relations between the book and its parts, can be represented
in a reified way by means of a (structural) description, which is said
to 'unify' the book configuration.
IRI: http://www.datacron-project.eu/datAcron#Construction_Support_Vessel
IRI: http://www.datacron-project.eu/datAcron#Container_Ship
IRI: http://www.datacron-project.eu/datAcron#ContextualInformation
Information provided from other than the sensors data
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Contract
(The content of) an agreement between at least two agents that play a Party Role, about some contract object (a Task to be executed).
IRI: http://www.datacron-project.eu/datAcron#Control_tower
IRI: http://www.datacron-project.eu/datAcron#CoordWaypoint
IRI: http://www.datacron-project.eu/datAcron#Country
IRI: http://www.datacron-project.eu/datAcron#Crane_Barge
IRI: http://www.datacron-project.eu/datAcron#Crane_Jack_Up
IRI: http://www.datacron-project.eu/datAcron#Crane_Ship
IRI: http://www.datacron-project.eu/datAcron#Crew_Boat
IRI: http://www.datacron-project.eu/datAcron#Crude_Oil_Tanker
IRI: http://www.datacron-project.eu/datAcron#Cutter_Suction_Dredger
IRI: http://www.datacron-project.eu/datAcron#Cutter_Suction_Hopper_Dredger
IRI: http://www.datacron-project.eu/datAcron#Deck_Cargo_Pontoon
IRI: http://www.datacron-project.eu/datAcron#Deck_Cargo_Ship
IRI: http://www.datacron-project.eu/datAcron#DepartureLeg
A portion of an departure procedure as defined by two consecutive significant points.
IRI: http://www.datacron-project.eu/datAcron#DepressionSpot
IRI: http://www.datacron-project.eu/datAcron#Desalination_Pontoon
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Description
A Description is a SocialObject that represents a conceptualization. It can be thought also as a 'descriptive context' that uses or defines concepts in order to create a view on a 'relational context' (cf. Situation) out of a set of data or observations. For example, a Plan is a Description of some actions to be executed by agents in a certain way, with certain parameters; a Diagnosis is a Description that provides an interpretation for a set of observed entities, etc.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Design
A Description of the Situation, in terms of structure and function, held by an Entity for some reason. A design is usually accompanied by the rationales behind the construction of the designed Entity (i.e. of the reasons why a design is claimed to be as such). For example, the actual design (a Situation) of a car or of a law is based on both the specification (a Description) of the structure, and the rationales used to construct cars or laws. While designs typically describe entities to be constructed, they can also be used to describe 'refunctionalized' entities, or to hypothesize unknown functions. For example, a cradle can be refunctionalized as a flowerpot based on a certain home design.
IRI: http://www.datacron-project.eu/datAcron#DesignatedPoint
A geographical location not marked by the site of a radio navigation aid, used in defining an ATS route, the flight path of an aircraft or for other navigation or ATS purposes.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#DesignedArtifact
A PhysicalArtifact that is also described by a Design. This excludes simple recycling or refunctionalization of natural objects. Most common sense 'artifacts' can be included in this class: cars, lamps, houses, chips, etc.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#DesignedSubstance
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Diagnosis
A Description of the Situation of a system, usually applied in order to control a normal behaviour, or to explain a notable behavior (e.g. a functional breakdown).
IRI: http://www.datacron-project.eu/datAcron#Direction_Finder
Also known as DF
IRI: http://www.datacron-project.eu/datAcron#Distance_Measuring_Equipment
Also known as DME
IRI: http://www.datacron-project.eu/datAcron#Dive_Vessel
IRI: http://www.datacron-project.eu/datAcron#Diving_Support_Platform
IRI: http://www.datacron-project.eu/datAcron#Diving_Support_Vessel
IRI: http://www.datacron-project.eu/datAcron#Document
A physical or digital document, issued by an Agent or Moving object
IRI: http://www.datacron-project.eu/datAcron#Dredger
IRI: http://www.datacron-project.eu/datAcron#Dredger_Vessel
IRI: http://www.datacron-project.eu/datAcron#Dredging_Pontoon
IRI: http://www.datacron-project.eu/datAcron#Drill_Barge
IRI: http://www.datacron-project.eu/datAcron#Drill_Ship
IRI: http://www.datacron-project.eu/datAcron#Drilling_Jack_Up
IRI: http://www.datacron-project.eu/datAcron#Dynamic
Contextual information that can change w.r.t. time
IRI: http://www.datacron-project.eu/datAcron#EEZ_Zone
Exclusive Economic zone
IRI: http://www.datacron-project.eu/datAcron#ESS_station
extended service set (ESS): A set of one or more interconnected basic service sets (BSSs) and integrated local area networks (LANs) that appears as a single BSS to the logical link control layer at any station associated with one of those BSSs.
IRI: http://www.datacron-project.eu/datAcron#Edible_Oil_Tanker
IRI: http://www.datacron-project.eu/datAcron#ElevatedPlace
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Entity
Anything: real, possible, or imaginary, which some modeller wants to talk about for some purpose.
IRI: http://www.datacron-project.eu/datAcron#Environmental
Environmental events affecting moving objects' behaviour
IRI: http://www.datacron-project.eu/datAcron#Event
A sub-class of Events that refer or affect moving objects in datAcron domain (i.e. maritime and aviation)
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Event
Any physical, social, or mental process, event, or state.
More theoretically, events can be classified in different ways, possibly based on 'aspect' (e.g. stative, continuous, accomplishement, achievement, etc.), on 'agentivity' (e.g. intentional, natural, etc.), or on 'typical participants' (e.g. human, physical, abstract, food, etc.). Here no special direction is taken, and the following explains why: events are related to observable situations, and they can have different views at a same time. If a position has to be suggested here anyway, the participant-based classification of events seems the most stable and appropriate for many modelling problems.
(1) Alternative aspectual views
Consider a same event 'rock erosion in the Sinni valley': it can be conceptualized as an accomplishment (what has brought a certain state to occur), as an achievement (the state resulting from a previous accomplishment), as a punctual event (if we collapse the time interval of the erosion into a time point), or as a transition (something that has changed from a state to a different one). In the erosion case, we could therefore have good motivations to shift from one aspect to another: a) causation focus, b) effectual focus, c) historical condensation, d) transition (causality).
The different views refer to the same event, but are still different: how to live with this seeming paradox? A typical solution e.g. in linguistics (cf. Levin's aspectual classes) and in DOLCE Full (cf. WonderWeb D18 axiomatization) is to classify events based on aspectual differences. But this solution would create different identities for a same event, where the difference is only based on the modeller's attitude. An alternative solution is applied here, and exploits the notion of (observable) Situation; a Situation is a view, consistent with a Description, which can be observed of a set of entities. It can also be seen as a 'relational context' created by an observer on the basis of a 'frame'. Therefore, a Situation allows to create a context where each particular view can have a proper identity, while the Event preserves its own identity. For example, ErosionAsAccomplishment is a Situation where rock erosion is observed as a process leading to a certain achievement: the conditions (roles, parameters) that suggest such view are stated in a Description, which acts as a 'theory of accomplishments'. Similarly, ErosionAsTransition is a Situation where rock erosion is observed as an event that has changed a state to another: the conditions for such interpretation are stated in a different Description, which acts as a 'theory of state transitions'. Consider that in no case the actual event is changed or enriched in parts by the aspectual view.
(2) Alternative intentionality views
Similarly to aspectual views, several intentionality views can be provided for a same Event. For example, one can investigate if an avalanche has been caused by immediate natural forces, or if there is any hint of an intentional effort to activate those natural forces. Also in this case, the Event as such has not different identities, while the causal analysis generates situations with different identities, according to what Description is taken for interpreting the Event. On the other hand, if the possible actions of an Agent causing the starting of an avalanche are taken as parts of the Event, then this makes its identity change, because we are adding a part to it. Therefore, if intentionality is a criterion to classify events or not, this depends on if an ontology designer wants to consider causality as a relevant dimension for events' identity.
(3) Alternative participant views
A slightly different case is when we consider the basic participants to an Event. In this case, the identity of the Event is affected by the participating objects, because it depends on them. For example, if snow, mountain slopes, wind, waves, etc. are considered as an avalanche basic participants, or if we also want to add water, human agents, etc., that makes the identity of an avalanche change. Anyway, this approach to event classification is based on the designer's choices, and more accurately mirrors lexical or commonsense classifications (see. e.g. WordNet 'supersenses' for verb synsets).
Ultimately, this discussion has no end, because realists will keep defending the idea that events in reality are not changed by the way we describe them, while constructivists will keep defending the idea that, whatever 'true reality' is about, it can't be modelled without the theoretical burden of how we observe and describe it. Both positions are in principle valid, but, if taken too radically, they focus on issues that are only partly relevant to the aim of computational ontologies, which only attempt to assist domain experts in representing what they want to conceptualize a certain portion of reality according to their own ideas. For this reason, in this ontology both events and situations are allowed, together with descriptions, in order to encode the modelling needs, independently from the position (if any) chosen by the designer.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#EventType
A Concept that classifies an Event . An event type describes how an Event should be interpreted, executed, expected, seen, etc., according to the Description that the EventType isDefinedIn (or used in)
IRI: http://www.datacron-project.eu/datAcron#Exhibition_Ship
IRI: http://www.datacron-project.eu/datAcron#FAO_area
IRI: http://www.datacron-project.eu/datAcron#FM_Airblock
The building unit of Airspace Volumes. Each airspace volume is defined by a finite set of airblocks. An airblock 3D is a 3D volume defined by: i) the airblock, ii) a value for lower altitude bound, iii) a value for upper altitude bound.
IRI: http://www.datacron-project.eu/datAcron#FM_Airspace
A 3D airspace, composed by 3D airblocks and the specified capacity.
IRI: http://www.datacron-project.eu/datAcron#FM_CTFM
CTFM is the profile based on the real track reports of the flown flight submitted by the different ACCs to EUROCONTROL. Notice that many flights might not contain the CTFM
IRI: http://www.datacron-project.eu/datAcron#FM_Configuration
IRI: http://www.datacron-project.eu/datAcron#FM_FP_EntersSecror
IRI: http://www.datacron-project.eu/datAcron#FM_FTFM
The last submitted flight plan from the airline, before take-off
IRI: http://www.datacron-project.eu/datAcron#FM_Flight_Plan
IRI: http://www.datacron-project.eu/datAcron#FM_FlightPlanGeneration
IRI: http://www.datacron-project.eu/datAcron#FM_FlightPlanNode
A semantic node that provides information about intended trajectory
IRI: http://www.datacron-project.eu/datAcron#FM_FlightPlanTrajectory
A sub-class of intended trajectory, which is reported in a FM_FlightPlan
IRI: http://www.datacron-project.eu/datAcron#FM_RTFM
The regulated Flight plan submitted by an airline. Notice that not all the flights are regulated (i.e. there is no RTFM for these flights)
IRI: http://www.datacron-project.eu/datAcron#FM_Regulation
A flow management regulation applied on a spatiotemporal region
IRI: http://www.datacron-project.eu/datAcron#Factory_Trawler
IRI: http://www.datacron-project.eu/datAcron#Ferry
IRI: http://www.datacron-project.eu/datAcron#Fire_Fighting_Supply_Vessel
IRI: http://www.datacron-project.eu/datAcron#Fire_Fighting_Tractor_Tug
IRI: http://www.datacron-project.eu/datAcron#Fire_Fighting_Vessel
IRI: http://www.datacron-project.eu/datAcron#Fish_Carrier
IRI: http://www.datacron-project.eu/datAcron#Fish_Factory
IRI: http://www.datacron-project.eu/datAcron#fish_passage
IRI: http://www.datacron-project.eu/datAcron#Fish_Storage_Barge
IRI: http://www.datacron-project.eu/datAcron#Fishery_Patrol_Vessel
IRI: http://www.datacron-project.eu/datAcron#Fishery_Protection_Research
IRI: http://www.datacron-project.eu/datAcron#Fishery_Research_Vessel
IRI: http://www.datacron-project.eu/datAcron#Fishery_Support_Vessel
IRI: http://www.datacron-project.eu/datAcron#FishingRegion
IRI: http://www.datacron-project.eu/datAcron#Fishing_Vessel
A fishing vessel is a vessel used for catching fish, whales, seals, walrus or other living resources of the sea. (SOLAS I/2). Fishing vessel means any vessel used commercially for catching fish, whales, seals, walrus or other living resources of the sea. (SFV 1993 article 2)
IRI: http://www.datacron-project.eu/datAcron#FixingDeviceType
IRI: http://www.datacron-project.eu/datAcron#Floating_Crane
IRI: http://www.datacron-project.eu/datAcron#Floating_Hotel
IRI: http://www.datacron-project.eu/datAcron#Floating_Hotel_Restaurant
IRI: http://www.datacron-project.eu/datAcron#Floating_Linkspan
IRI: http://www.datacron-project.eu/datAcron#Floating_Sheerleg
IRI: http://www.datacron-project.eu/datAcron#Floating_Storage_Production
IRI: http://www.datacron-project.eu/datAcron#Fly_by_waypoint
Fly-by waypoint. A waypoint which requires turn anticipation to allow tangential interception of the next segment of a route or procedure
IRI: http://www.datacron-project.eu/datAcron#Flyover_waypoint
Flyover waypoint. A waypoint at which a turn is initiated in order to join the next segment of a route or procedure.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#FormalEntity
Entities that are formally defined and are considered independent from the social context in which they are used. They cannot be localized in space or time. Also called 'Platonic entities'. Mathematical and logical entities are included in this class: sets, categories, tuples, costants, variables, etc. Abstract formal entities are distinguished from information objects, which are supposed to be part of a social context, and are localized in space and time, therefore being (social) objects. For example, the class 'Quark' is an abstract formal entity from the purely set-theoretical perspective, but it is an InformationObject from the viewpoint of ontology design, when e.g. implemented in a logical language like OWL. Abstract formal entities are also distinguished from Concept(s), Collection(s), and Description(s), which are part of a social context, therefore being SocialObject(s) as well. For example, the class 'Quark' is an abstract FormalEntity from the purely set-theoretical perspective, but it is a Concept within history of science and cultural dynamics.
These distinctions allow to represent two different notions of 'semantics': the first one is abstract and formal ('formal semantics'), and formallyInterprets symbols that are about entities whatsoever; for example, the term 'Quark' isAbout the Collection of all quarks, and that Collection isFormalGroundingFor the abstract class 'Quark' (in the extensional sense). The second notion is social, localized in space-time ('social semantics'), and can be used to interpret entities in the intensional sense. For example, the Collection of all quarks isCoveredBy the Concept 'Quark', which is also expressed by the term 'Quark'.
IRI: http://www.datacron-project.eu/datAcron#Fruit_Juice_Tanker
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#FunctionalSubstance
IRI: http://www.datacron-project.eu/datAcron#GPS_Survey_station
IRI: http://www.datacron-project.eu/datAcron#Gas_Carrier
IRI: http://www.datacron-project.eu/datAcron#GeneralCargo
General cargo ship: A ship with a multi-deck or single-deck hull designed primarily for the carriage of general cargo. (MEPC.1/Circ.681 Annex)
IRI: http://www.datacron-project.eu/datAcron#General_Cargo
IRI: http://www.datacron-project.eu/datAcron#Geometry
The geometry is an abstract entity in this domain, since we do not need geometry specific properties, such as CSR, WKT representation etc. The URI of the geometry refers to the serialized geometry where the low level details are provided.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Goal
The Description of a Situation that is desired by an Agent, and usually associated to a Plan that describes how to actually achieve it
IRI: http://www.datacron-project.eu/datAcron#Grab_Dredger
IRI: http://www.datacron-project.eu/datAcron#Grab_Dredger_Pontoon
IRI: http://www.datacron-project.eu/datAcron#Grab_Hopper_Dredger
IRI: http://www.datacron-project.eu/datAcron#Grain_Elevating_Pontoon
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Group
A CollectiveAgent whose acting agents conceptualize a same SocialRelation .
IRI: http://www.datacron-project.eu/datAcron#HeavyAircraft
IRI: http://www.datacron-project.eu/datAcron#Heavy_Lift_Vessel
IRI: http://www.datacron-project.eu/datAcron#Heavy_Load_Carrier
IRI: http://www.datacron-project.eu/datAcron#Heliport
IRI: http://www.datacron-project.eu/datAcron#HighLevel
A subclass of events in datAcron domain, where contextual information need to be consulted jointly with the sensor's data
IRI: http://www.datacron-project.eu/datAcron#HighSpeed
High-speed craft is a craft capable of a maximum speed, in metres per second (m/s), equal to or exceeding 3.7 times the one-sixth power of the volume of displacement corresponding to the design waterline (m³), excluding craft the hull of which is supported completely clear above the water surface in non-displacement mode by aerodynamic forces generated by ground effect. (SOLAS X/1.2, HSC Code 2000 para 1.4.30)
IRI: http://www.datacron-project.eu/datAcron#Hopper_Barge
IRI: http://www.datacron-project.eu/datAcron#Hopper_Dredger
IRI: http://www.datacron-project.eu/datAcron#Hospital_Ship
IRI: http://www.datacron-project.eu/datAcron#Houseboat
IRI: http://www.datacron-project.eu/datAcron#Hovercraft
IRI: http://www.datacron-project.eu/datAcron#Hydrofoil
IRI: http://www.datacron-project.eu/datAcron#ICAOWaypoint
IRI: http://www.datacron-project.eu/datAcron#ILS_collocated_DME
ILS_DME: . Collocation can be with the antenna or the loc. See NavaidComponent collocationGroup
IRI: http://www.datacron-project.eu/datAcron#Icebreaker
IRI: http://www.datacron-project.eu/datAcron#Incinerator
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#InformationEntity
A piece of information, be it concretely realized or not.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#InformationObject
A piece of information, such as a musical composition, a text, a word, a picture, independently from how it is concretely realized.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#InformationRealization
A concrete realization of an InformationObject, e.g. the written document containing the text of a law.
IRI: http://www.datacron-project.eu/datAcron#Inland_Cargo
IRI: http://www.datacron-project.eu/datAcron#Inland_Dredger
IRI: http://www.datacron-project.eu/datAcron#Inland_Ferry
IRI: http://www.datacron-project.eu/datAcron#Inland_Passengers_Ship
IRI: http://www.datacron-project.eu/datAcron#Inland_Ro-Ro_Cargo_Ship
IRI: http://www.datacron-project.eu/datAcron#Inland_Supply_Vessel
IRI: http://www.datacron-project.eu/datAcron#Inland_Tanker
IRI: http://www.datacron-project.eu/datAcron#Inland_Tug
IRI: http://www.datacron-project.eu/datAcron#Instant
A time instant
IRI: http://www.datacron-project.eu/datAcron#Instrument_Landing_System
Also known as ILS
IRI: http://www.datacron-project.eu/datAcron#IntendedTrajectory
A reported trajectory that an Agent intents to follow
IRI: http://www.datacron-project.eu/datAcron#InternationalFerryLine
IRI: http://www.datacron-project.eu/datAcron#Island
Any part of land surrounded with water.
IRI: http://www.datacron-project.eu/datAcron#Jack_Up_Barge
IRI: http://www.datacron-project.eu/datAcron#Jacket_Launching_Pontoon
IRI: http://www.datacron-project.eu/datAcron#Joint_Aerodrome
IRI: http://www.datacron-project.eu/datAcron#Kelp_Dredger
IRI: http://www.datacron-project.eu/datAcron#LOC_collocated_DME
LOC_DME collocation Group
IRI: http://www.datacron-project.eu/datAcron#LakeCanalPort
Lake or Canal port. See Pub150bk.pdf
IRI: http://www.datacron-project.eu/datAcron#LandRoute
IRI: http://www.datacron-project.eu/datAcron#Landing_Craft
IRI: http://www.datacron-project.eu/datAcron#LargeSizePort
The classification of harbor size is based on several applicable factors, including area, facilities, and wharf space. It is not based on area alone or on any other single factor.
IRI: http://www.datacron-project.eu/datAcron#Law_Enforce
IRI: http://www.datacron-project.eu/datAcron#LightAircraft
IRI: http://www.datacron-project.eu/datAcron#Lighthouse
IRI: http://www.datacron-project.eu/datAcron#Limestone_Carrier
IRI: http://www.datacron-project.eu/datAcron#Livestock_Carrier
IRI: http://www.datacron-project.eu/datAcron#Lng_Tanker
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#LocalConcept
A Concept that isDefinedIn exactly 1 Description. For example, the Concept 'coffee' in a 'preparesCoffee' relation can be defined in that relation, and for all other Description(s) that use it, the isConceptUsedIn property should be applied. Notice therefore that not necessarily all Concept(s) isDefinedIn exactly 1 Description.
IRI: http://www.datacron-project.eu/datAcron#Local_Vessel
IRI: http://www.datacron-project.eu/datAcron#Localizer_Navaid
Also known as LOC
IRI: http://www.datacron-project.eu/datAcron#Logistics_Naval_Vessel
IRI: http://www.datacron-project.eu/datAcron#LowLevel
A sub-class of event that can be identified only by the sensor's recordings
IRI: http://www.datacron-project.eu/datAcron#Lpg_Chemical_Tanker
IRI: http://www.datacron-project.eu/datAcron#Lpg_Tanker
IRI: http://www.datacron-project.eu/datAcron#MLS_collocated_DME
MLS_DME collocation Group
IRI: http://www.datacron-project.eu/datAcron#Maintenance_Vessel
IRI: http://www.datacron-project.eu/datAcron#major_Aerodrome
IRI: http://www.datacron-project.eu/datAcron#marina
IRI: http://www.datacron-project.eu/datAcron#MarineHeritage
IRI: http://www.datacron-project.eu/datAcron#marine_region
The surface where any vessel can autonomously moved, separated into regions. This surface includes rivers, estuaries, lakes and open sea
IRI: http://www.datacron-project.eu/datAcron#MarineRoute
IRI: http://www.datacron-project.eu/datAcron#MaritimeLowLevelEvent
IRI: http://www.datacron-project.eu/datAcron#Marker_Beacon
Also known as MKR
IRI: http://www.datacron-project.eu/datAcron#medical_Heliport
IRI: http://www.datacron-project.eu/datAcron#Medical_Trans
IRI: http://www.datacron-project.eu/datAcron#MediumAircraft
IRI: http://www.datacron-project.eu/datAcron#MediumSizePort
The classification of harbor size is based on several applicable factors, including area, facilities, and wharf space. It is not based on area alone or on any other single factor.
IRI: http://www.datacron-project.eu/datAcron#meteorological_station
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Method
A method is a Description that defines or uses concepts in order to guide carrying out actions aimed at a solution with respect to a problem. It is different from a Plan, because plans could be carried out in order to follow a method, but a method can be followed by executing alternative plans.
IRI: http://www.datacron-project.eu/datAcron#micro_Aerodrome
IRI: http://www.datacron-project.eu/datAcron#micro_ultralight_Aerodrome
IRI: http://www.datacron-project.eu/datAcron#Microwave_Landing_System
Also known as MLS
IRI: http://www.datacron-project.eu/datAcron#mid_Aerodrome
IRI: http://www.datacron-project.eu/datAcron#Military_Aerodrome
IRI: http://www.datacron-project.eu/datAcron#Military_Heliport
IRI: http://www.datacron-project.eu/datAcron#Military_Ops
IRI: http://www.datacron-project.eu/datAcron#Mine_Hunter
IRI: http://www.datacron-project.eu/datAcron#Minesweeper
IRI: http://www.datacron-project.eu/datAcron#Mining_Vessel
IRI: http://www.datacron-project.eu/datAcron#Mission_Ship
IRI: http://www.datacron-project.eu/datAcron#MobileOffshoreDrillingUnit
Mobile offshore drilling unit (MODU) means a vessel capable of engaging in drilling operations for the exploration for or exploitation of resources beneath the sea-bed such as liquid or gaseous hydrocarbons, sulphur or salt. (SOLAS IX/1, MODU Code 2009 para 1.3.40)
IRI: http://www.datacron-project.eu/datAcron#Mooring_Vessel
IRI: http://www.datacron-project.eu/datAcron#Motor_Hopper
IRI: http://www.datacron-project.eu/datAcron#Mountain
IRI: http://www.datacron-project.eu/datAcron#MovingObject
A moving object in the datAcron domain
IRI: http://www.datacron-project.eu/datAcron#Multi_Purpose_Offshore_Vessel
IRI: http://www.datacron-project.eu/datAcron#Multi-Purpose_Vessel
IRI: http://www.datacron-project.eu/datAcron#Museum_Ship
IRI: http://www.datacron-project.eu/datAcron#NATRoute
IRI: http://www.datacron-project.eu/datAcron#NDB_and_DME
NDB_DME
IRI: http://www.datacron-project.eu/datAcron#NON_ATC_Equipment
E: Equipment NON-ATC
IRI: http://www.datacron-project.eu/datAcron#NON_ATC_IndustrialAction
N: Industrial action NON-ATC
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Narrative
IRI: http://www.datacron-project.eu/datAcron#National_borders
Includes maritime borders between states
IRI: http://www.datacron-project.eu/datAcron#NationalFerryLine
IRI: http://www.datacron-project.eu/datAcron#Natura2000_zone
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#NaturalPerson
A person in the physical commonsense intuition: 'have you seen that person walking down the street?'
IRI: http://www.datacron-project.eu/datAcron#Navaid
A navaid is a physical device on the ground that airplanes can detect and fly to. Modern examples include NDBs and VORs, which both transmit radio signals that aircraft can follow and home in on. An older example would be a lighted beacon that can shine through night and clouds (used by the USPS before the air navigation system was built). A navaid is different from a waypoint, which is not necessarily a physical place (i.e. it can be a named point used as reference).
IRI: http://www.datacron-project.eu/datAcron#Naval_Auxiliary_Tug
IRI: http://www.datacron-project.eu/datAcron#Naval_Naval_Auxiliary_Vessel
IRI: http://www.datacron-project.eu/datAcron#Naval_Patrol_Vessel
IRI: http://www.datacron-project.eu/datAcron#Naval_Research_Vessel
IRI: http://www.datacron-project.eu/datAcron#Naval_Salvage_Vessel
IRI: http://www.datacron-project.eu/datAcron#Node
A semantic node provides a meaningful abstraction or aggregation of raw positions
IRI: http://www.datacron-project.eu/datAcron#Non_Directional_Radio_Beacon
Also known as NDB
IRI: http://www.datacron-project.eu/datAcron#Non_Directional_Radio_Beacon_and_Marker_Beacon
NDB_MKR
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Norm
A social norm.
IRI: http://www.datacron-project.eu/datAcron#Nuclear_Fuel_Carrier
IRI: http://www.datacron-project.eu/datAcron#NuclearShip
A nuclear ship is a ship provided with a nuclear power plant. (SOLAS I/2)
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Object
Any physical, social, or mental object, or a substance. Following DOLCE Full, objects are always participating in some event (at least their own life), and are spatially located.
IRI: http://www.datacron-project.eu/datAcron#Obo_Carrier
IRI: http://www.datacron-project.eu/datAcron#Offshore_Construction_Jack_Up
IRI: http://www.datacron-project.eu/datAcron#Offshore_Safety_Vessel
IRI: http://www.datacron-project.eu/datAcron#Offshore_Supply_Ship
IRI: http://www.datacron-project.eu/datAcron#Oil_Chemical_Tanker
IRI: http://www.datacron-project.eu/datAcron#Oil_Products_Tanker
IRI: http://www.datacron-project.eu/datAcron#OpenRoadsteadPort
Open Roadstead port. See Pub150bk.pdf
IRI: http://www.datacron-project.eu/datAcron#OpenTrajectory
A Trajectory where the final destination is not yet met.
IRI: http://www.datacron-project.eu/datAcron#Operational
An operational event triggered by an authorized/operator agent in a spatiotemporal region
IRI: http://www.datacron-project.eu/datAcron#Operator
IRI: http://www.datacron-project.eu/datAcron#Ore_Carrier
IRI: http://www.datacron-project.eu/datAcron#Ore_Oil_Carrier
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Organism
A physical objects with biological characteristics, typically that organisms can self-reproduce.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Organization
An internally structured, conventionally created SocialAgent, needing a specific Role and Agent that plays it, in order to act.
IRI: http://www.datacron-project.eu/datAcron#Paddle_Ship
IRI: http://www.datacron-project.eu/datAcron#Pallet_Carrier
IRI: http://www.datacron-project.eu/datAcron#Paragliding
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Parameter
A Concept that classifies a Region; the difference between a Region and a Parameter is that regions represent sets of observable values, e.g. the height of a given building, while parameters represent constraints or selections on observable values, e.g. 'VeryHigh'. Therefore, parameters can also be used to constrain regions, e.g. VeryHigh on a subset of values of the Region Height applied to buildings, or to add an external selection criterion , such as measurement units, to regions, e.g. Meter on a subset of values from the Region Length applied to the Region Length applied to roads.
IRI: http://www.datacron-project.eu/datAcron#PassElev
IRI: http://www.datacron-project.eu/datAcron#Passenger_Cargo_Ship
IRI: http://www.datacron-project.eu/datAcron#Passenger_Vessel
IRI: http://www.datacron-project.eu/datAcron#Passengers_Landing_Craft
IRI: http://www.datacron-project.eu/datAcron#Passengers_Ship
A passenger ship is a ship which carries more than twelve passengers. (SOLAS I/2)
IRI: http://www.datacron-project.eu/datAcron#Patrol_Vessel
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Pattern
Any invariance detected from a dataset, or from observation; also, any invariance proposed based on top-down considerations. E.g. patterns detected and abstracted by an organism, by pattern recognition algorithms, by machine learning techniques, etc. An occurrence of a pattern is an 'observable', or detected Situation
IRI: http://www.datacron-project.eu/datAcron#Pearl_Shells_Carrier
IRI: http://www.datacron-project.eu/datAcron#Period
A temproral interval
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Person
Persons in commonsense intuition, which does not apparently distinguish between either natural or social persons.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Personification
A social entity with agentive features, but whose status is the result of a cultural transformation from e.g. a PhysicalObject, an Event, an Abstract, another SocialObject, etc. For example: the holy grail, deus ex machina, gods, magic wands, etc.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalAgent
A PhysicalObject that is capable of self-representing (conceptualizing) a Description in order to plan an Action. A PhysicalAgent is a substrate for (actsFor) a Social Agent
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalArtifact
Any PhysicalObject that isDescribedBy a Plan . This axiomatization is weak, but allows to talk of artifacts in a very general sense, i.e. including recycled objects, objects with an intentional functional change, natural objects that are given a certain function, even though they are not modified or structurally designed, etc. PhysicalArtifact(s) are not considered disjoint from PhysicalBody(s), in order to allow a dual classification when needed. E.g., FunctionalSubstance(s) are included here as well. Immaterial (non-physical) artifacts (e.g. texts, ideas, cultural movements, corporations, communities, etc. can be modelled as social objects (see SocialObject), which are all 'artifactual' in the weak sense assumed here.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalAttribute
Physical value of a physical object, e.g. density, color, etc.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalBody
Physical bodies are PhysicalObject(s), for which we tend to neutralize any possible artifactual character. They can have several granularity levels: geological, chemical, physical, biological, etc.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalObject
Any Object that has a proper space region. The prototypical physical object has also an associated mass, but the nature of its mass can greatly vary based on the epistemological status of the object (scientifically measured, subjectively possible, imaginary).
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalPlace
A physical object that is inherently located; for example, a water area.
IRI: http://www.datacron-project.eu/datAcron#Pile_Driving_Vessel
IRI: http://www.datacron-project.eu/datAcron#Pilot_Ship
IRI: http://www.datacron-project.eu/datAcron#Pilot_Vessel
IRI: http://www.datacron-project.eu/datAcron#Pipe_Burying_Vessel
IRI: http://www.datacron-project.eu/datAcron#Pipe_Carrier
IRI: http://www.datacron-project.eu/datAcron#Pipe_Layer
IRI: http://www.datacron-project.eu/datAcron#Pipe_Layer_Platform
IRI: http://www.datacron-project.eu/datAcron#Pipelay_Crane_Vessel
IRI: http://www.datacron-project.eu/datAcron#Place
A physical place described by a geometry, name, ICAO, IATA etc codes. Please notice that aviation or marine places are described in separate modules
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Place
A location, in a very generic sense: a political geographic entity (Roma, Lesotho), a non-material location determined by the presence of other entities ("the area close to Roma"), pivot events or signs ("the area where the helicopter fell"), complements of other entities ("the area under the table"), etc. In this generic sense, a Place is an "approximate" location. For an "absolute" location, see the class SpaceRegion
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Plan
A Description having an explicit Goal, to be achieved by executing the plan
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PlanExecution
Plan executions are situations that proactively satisfy a plan. Subplan executions are proper parts of the whole plan execution.
IRI: http://www.datacron-project.eu/datAcron#Plateau
IRI: http://www.datacron-project.eu/datAcron#Platform
IRI: http://www.datacron-project.eu/datAcron#Pleasure_Craft
IRI: http://www.datacron-project.eu/datAcron#Point
IRI: http://www.datacron-project.eu/datAcron#Pollution_Control_Vessel
IRI: http://www.datacron-project.eu/datAcron#PopulatedPlace
IRI: http://www.datacron-project.eu/datAcron#Port
IRI: http://www.datacron-project.eu/datAcron#Port_Tender
IRI: http://www.datacron-project.eu/datAcron#Powder_Carrier
IRI: http://www.datacron-project.eu/datAcron#Power_Station_Vessel
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Process
This is a placeholder for events that are considered in their evolution, or anyway not strictly dependent on agents, tasks, and plans. See Event class for some thoughts on classifying events. See also 'Transition'.
IRI: http://www.datacron-project.eu/datAcron#Production_Testing_Vessel
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Project
A Plan that defines Role(s), Task(s), and a specific structure for tasks to be executed in relation to goals to be achieved, in order to achieve the main goal of the project. In other words, a project is a plan with a subgoal structure and multiple roles and tasks.
IRI: http://www.datacron-project.eu/datAcron#ProtectedZone
IRI: http://www.datacron-project.eu/datAcron#Pumping_Platform
IRI: http://www.datacron-project.eu/datAcron#Pusher_Tug
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Quality
Any aspect of an Entity (but not a part of it), which cannot exist without that Entity. For example, the way the surface of a specific PhysicalObject looks like, or the specific light of a place at a certain time, are examples of Quality, while the encoding of a Quality into e.g. a PhysicalAttribute should be modeled as a Region. From the design viewpoint, the Quality-Region distinction is useful only when individual aspects of an Entity are considered in a domain of discourse. For example, in an automotive context, it would be irrelevant to consider the aspects of car windows for a specific car, unless the factory wants to check a specific window against design parameters (anomaly detection). On the other hand, in an antiques context, the individual aspects for a specific piece of furniture are a major focus of attention, and may constitute the actual added value, because the design parameters for old furniture are often not fixed, and may not be viewed as 'anomalies'.
IRI: http://www.datacron-project.eu/datAcron#Radar
IRI: http://www.datacron-project.eu/datAcron#Radar_Platform
IRI: http://www.datacron-project.eu/datAcron#radar_station
IRI: http://www.datacron-project.eu/datAcron#radar_tower
IRI: http://www.datacron-project.eu/datAcron#Radar_Vessel
IRI: http://www.datacron-project.eu/datAcron#Radio_Ship
IRI: http://www.datacron-project.eu/datAcron#Rail_Vehicles_Carrier
IRI: http://www.datacron-project.eu/datAcron#RawPosition
raw data specifying the moving object's spatio-temporal position
IRI: http://www.datacron-project.eu/datAcron#Reefer
IRI: http://www.datacron-project.eu/datAcron#Reefer_Containership
IRI: http://www.datacron-project.eu/datAcron#Reefs
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Region
Any region in a dimensional space (a dimensional space is a maximal Region), which can be used as a value for a quality of an Entity . For example, TimeInterval, SpaceRegion, PhysicalAttribute, Amount, SocialAttribute are all subclasses of Region. Regions are not data values in the ordinary knowledge representation sense; in order to get patterns for modelling data, see the properties: representsDataValue and hasDataValue
IRI: http://www.datacron-project.eu/datAcron#RegulatedTrajectory
A trajectory that has been regulated
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Relation
Relations are descriptions that can be considered as the counterpart of formal relations (that are included in the FormalEntity class). For example, 'givingGrantToInstitution(x,y,z)' with three argument types: Provider(x),Grant(y),Recipient(z), can have a Relation counterpart: 'GivingGrantToInstitution', which defines three Concept instances: Provider,Grant,Recipient. Since social objects are not formal entities, Relation includes here any 'relation-like' entity in common sense, including social relations.
IRI: http://www.datacron-project.eu/datAcron#Repair_Ship
IRI: http://www.datacron-project.eu/datAcron#Replenishment_Vessel
IRI: http://www.datacron-project.eu/datAcron#Research_Survey_Vessel
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Right
A legal position by which an Agent is entitled to obtain something from another Agent , under specified circumstances, through an enforcement explicited either in a Law, Contract , etc.
IRI: http://www.datacron-project.eu/datAcron#RiverBasinNPort
River Basin N - None port. See Pub150bk.pdf
IRI: http://www.datacron-project.eu/datAcron#RiverNaturalPort
River Natural port.
IRI: http://www.datacron-project.eu/datAcron#RiverTideGatePort
River Tide Gate port. See Pub150bk.pdf
IRI: http://www.datacron-project.eu/datAcron#Ro-Ro_Cargo
IRI: http://www.datacron-project.eu/datAcron#Ro-Ro_Container_Carrier
IRI: http://www.datacron-project.eu/datAcron#Ro-Ro_Passenger_Ship
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Role
A Concept that classifies an Object
IRI: http://www.datacron-project.eu/datAcron#Route
A course taken in getting from a starting point to a destination. A route is not bound to specific moving entities and has no requirement for time reference in the intermediate points. For example, the route that connects two sea ports, exists irrevelantly to the departure/arrival time.
IRI: http://www.datacron-project.eu/datAcron#RouteAvailability
IRI: http://www.datacron-project.eu/datAcron#RouteSegment
IRI: http://www.datacron-project.eu/datAcron#SAR_Aircraft
IRI: http://www.datacron-project.eu/datAcron#SAR_Vessel
IRI: http://www.datacron-project.eu/datAcron#Sailing_Vessel
IRI: http://www.datacron-project.eu/datAcron#Salvage_Rescue_Vessel
IRI: http://www.datacron-project.eu/datAcron#Sand_Suction_Dredger
IRI: http://www.datacron-project.eu/datAcron#Sealer
IRI: http://www.datacron-project.eu/datAcron#Seaplane_Aerodrome
IRI: http://www.datacron-project.eu/datAcron#Segment
A trajectory part
IRI: http://www.datacron-project.eu/datAcron#SegmentLeg
A portion of a procedure as defined by two consecutive significant points.
IRI: http://www.datacron-project.eu/datAcron#Self_Discharging_Bulk_Carrier
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Set
IRI: http://www.datacron-project.eu/datAcron#Shuttle_Tanker
IRI: http://www.datacron-project.eu/datAcron#SignificantPoint
A link class that allows selecting between a navaid system, a runway point, an airport reference point, an aiming point or a fix designated point. SignificantPoint accounts for a specified geographical location used to define an ATS route, the flight path of an aircraft or for other navigation/ATS purposes.
IRI: http://www.datacron-project.eu/datAcron#Simplified_Directional_Facility
Also known as SDF
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Situation
A view, consistent with ('satisfying') a Description, on a set of entities. It can also be seen as a 'relational context' created by an observer on the basis of a 'frame' (i.e. a Description). For example, a PlanExecution is a context including some actions executed by agents according to certain parameters and expected tasks to be achieved from a Plan; a DiagnosedSituation is a context of observed entities that is interpreted on the basis of a Diagnosis, etc. Situation is also able to represent reified n-ary relations, where isSettingFor is the top-level relation for all binary projections of the n-ary relation. If used in a transformation pattern for n-ary relations, the designer should take care of creating only one subclass of Situation for each n-ary relation, otherwise the 'identification constraint' (Calvanese et al., IJCAI 2001) could be violated.
IRI: http://www.datacron-project.eu/datAcron#Sludge_Carrier
IRI: http://www.datacron-project.eu/datAcron#small_Aerodrome
IRI: http://www.datacron-project.eu/datAcron#small_plus_Aerodrome
IRI: http://www.datacron-project.eu/datAcron#SmallSizePort
The classification of harbor size is based on several applicable factors, including area, facilities, and wharf space. It is not based on area alone or on any other single factor.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#SocialAgent
Any individual whose existence is granted simply by its social communicability and capability of action (through some PhysicalAgent).
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#SocialObjectAttribute
Any Region in a dimensional space that is used to represent some characteristic of a SocialObject, e.g. judgment values, social scalars, statistical attributes over a collection of entities, etc.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#SocialObject
Any Object that exists only within some communication Event, in which at least one PhysicalObject participates in. In other words, all objects that have been or are created in the process of social communication: for the sake of communication (InformationObject), for incorporating new individuals (SocialAgent, Place), for contextualizing existing entities (Situation), for collecting existing entities (Collection), or for describing existing entities (Description, Concept). Being dependent on communication, all social objects need to be expressed by some information object (information object are self-expressing).
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#SocialPerson
A SocialAgent that needs the existence of a specific NaturalPerson in order to act (but the lifetime of the NaturalPerson has only to overlap that of the SocialPerson).
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#SocialRelation
Any social relationship
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#SpaceRegion
Any Region in a dimensional space that is used to localize an Entity ; i.e., it is not used to represent some characteristic (e.g. it excludes time intervals, colors, size values, judgment values, etc.). Differently from a Place , a space region has a specific dimensional space.
IRI: http://www.datacron-project.eu/datAcron#SpatioTemporal
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#SpatioTemporalRegion
IRI: http://www.datacron-project.eu/datAcron#Special_Craft
IRI: http://www.datacron-project.eu/datAcron#Special_Vessel
Special purpose ship (SPS) means a mechanically self-propelled ship which by reason of its function carries on board more than 12 special personnel. (SPS Code para 1.3.12)
IRI: http://www.datacron-project.eu/datAcron#Spot_elevation
IRI: http://www.datacron-project.eu/datAcron#StandardInstrumentArrival
In aviation, a standard terminal arrival route or standard terminal arrival (STAR) is a published procedure followed by aircrafts on an IFR flight plan just before reaching a destination airport. A STAR is an ATC-coded IFR arrival route established for application to arriving IFR aircraft destined for certain airports
IRI: http://www.datacron-project.eu/datAcron#StandardInstrumentDeparture
In aviation, a standard terminal departure route or standard terminal arrival (STAR) is a published procedure followed by aircrafts on an IFR flight plan leaving a departure airport.
IRI: http://www.datacron-project.eu/datAcron#Standby_Safety_Vessel
IRI: http://www.datacron-project.eu/datAcron#Static
Contextual information that will never change
IRI: http://www.datacron-project.eu/datAcron#Steam_Supply_Pontoon
IRI: http://www.datacron-project.eu/datAcron#Stone_Carrier
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Substance
Any PhysicalBody that has not necessarily specified (designed) boundaries, e.g. a pile of trash, some sand, etc. In this sense, an artistic object made of trash or a dose of medicine in the form of a pill would be a FunctionalSubstance, and a DesignedArtifact, since its boundaries are specified by a Design; aleatoric objects that are outcomes of an artistic process might be still considered DesignedArtifact(s), and Substance(s).
IRI: http://www.datacron-project.eu/datAcron#Suction_Dredger
IRI: http://www.datacron-project.eu/datAcron#Suction_Dredger_Pontoon
IRI: http://www.datacron-project.eu/datAcron#Suction_Hopper_Dredger
IRI: http://www.datacron-project.eu/datAcron#Supply_Jack_Up
IRI: http://www.datacron-project.eu/datAcron#Supply_Tender
IRI: http://www.datacron-project.eu/datAcron#Supply_Vessel
IRI: http://www.datacron-project.eu/datAcron#Support_Jack_Up
IRI: http://www.datacron-project.eu/datAcron#Support_Vessel
IRI: http://www.datacron-project.eu/datAcron#SurveillanceStation
IRI: http://www.datacron-project.eu/datAcron#SyntheticTrajectory
A trajectory that is constructed by a simulation process. This is not necessary an intended trajectory, while intended trajectories can be produced from simulation processes. A major dofference from intended trajectory, is that simulation and generation of synthetic trajectories can be refer to both past and future temporal periods, while intended trajectory refers to only future time periods.
IRI: http://www.datacron-project.eu/datAcron#Tactical_Air_Navigation_Beacon
Also known as TACAN
IRI: http://www.datacron-project.eu/datAcron#Tank_Barge
IRI: http://www.datacron-project.eu/datAcron#Tank-Cleaning_Vessel
IRI: http://www.datacron-project.eu/datAcron#Tanker
Oil tanker means a ship constructed or adapted primarily to carry oil in bulk in its cargo spaces and includes combination carriers, any "NLS tanker" as defined in Annex II of the present Convention and any gas carrier as defined in regulation 3.20 of chapter II-1 of SOLAS 74 (as amended), when carrying a cargo or part cargo of oil in bulk. (MARPOL Annex I reg. 1.5)
IRI: http://www.datacron-project.eu/datAcron#TankerHazard_A_Major
IRI: http://www.datacron-project.eu/datAcron#TankerHazard_B
IRI: http://www.datacron-project.eu/datAcron#TankerHazard_C_Minor
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Task
An EventType that classifies an Action to be executed. For example, reaching a destination is a task that can be executed by performing certain actions, e.g. driving a car, buying a train ticket, etc. The actions to execute a task can also be organized according to a Plan that is not the same as the one that defines the task (if any). For example, reaching a destination could be defined by a plan to get on holidays, while the plan to execute the task can consist of putting some travels into a sequence.
IRI: http://www.datacron-project.eu/datAcron#Tender
IRI: http://www.datacron-project.eu/datAcron#TerminalWaypoint
IRI: http://www.datacron-project.eu/datAcron#Theatre_Vessel
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Theory
A Theory is a Description that represents a set of assumptions for describing something, usually general. Scientific, philosophical, and commonsense theories can be included here. This class can also be used to act as 'naturalized reifications' of logical theories (of course, they will be necessarily incomplete in this case, because second-order entities are represented as first-order ones).
IRI: http://www.datacron-project.eu/datAcron#Timber_Carrier
IRI: http://www.datacron-project.eu/datAcron#Time
Any temporal entity. Please notice that the super-class 'Time interval' is not restricted to proper intervals, i.e. starting time is not necessary different from ending time.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#TimeInterval
Any Region in a dimensional space that aims at representing time.
IRI: http://www.datacron-project.eu/datAcron#Torpedo_Recovery_Vessel
IRI: http://www.datacron-project.eu/datAcron#tower_fixpoint
IRI: http://www.datacron-project.eu/datAcron#Towing_Pushing
IRI: http://www.datacron-project.eu/datAcron#Towing_Vessel
IRI: http://www.datacron-project.eu/datAcron#Tractor_Tug
IRI: http://www.datacron-project.eu/datAcron#Trailing_Suction_Dredger
IRI: http://www.datacron-project.eu/datAcron#Trailing_Suction_Hopper_Dredge
IRI: http://www.datacron-project.eu/datAcron#Training_Ship
IRI: http://www.datacron-project.eu/datAcron#Trajectory
A trajectory consists of a sequence of temporally non-overlapping trajectory parts that can be either semantic nodes, raw positions reported from sensing devises, or trajectory segments. Each trajectory part may be associated to a specific geometry, representing a point or region of occurrence, and a temporal entity specifying an instant or time interval of occurrence.
IRI: http://www.datacron-project.eu/datAcron#TrajectoryCluster
A set of trajectories of one or more moving objects that have common spatio-temporal or contextual features, such as departure, destination, intermediate positions, etc
IRI: http://www.datacron-project.eu/datAcron#TrajectoryPart
A Node, a raw position or a segment of a trajectory
IRI: http://www.datacron-project.eu/datAcron#Trans_Shipment_Barge
IRI: http://www.datacron-project.eu/datAcron#Trans_Shipment_Vessel
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Transition
A transition is a Situation that creates a context for three TimeInterval(s), two additional different Situation(s), one Event, one Process, and at least one Object: the Event is observed as the cause for the transition, one Situation is the state before the transition, the second Situation is the state after the transition, the Process is the invariance under some different transitions (including the one represented here), in which at least one Object is situated. Finally, the time intervals position the situations and the transitional event in time. This class of situations partly encodes the ontology underlying typical engineering algebras for processes, e.g. Petri Nets. A full representation of the transition ontology is outside the expressivity of OWL, because we would need qualified cardinality restrictions, coreference, property equivalence, and property composition.
IRI: http://www.datacron-project.eu/datAcron#transmitter
IRI: http://www.datacron-project.eu/datAcron#Transponder_Landing_System
Also known as TLS
IRI: http://www.datacron-project.eu/datAcron#Trawler
IRI: http://www.datacron-project.eu/datAcron#Trenching_Support_Vessel
IRI: http://www.datacron-project.eu/datAcron#Troopship
IRI: http://www.datacron-project.eu/datAcron#Tug
IRI: http://www.datacron-project.eu/datAcron#Tug_Fire_Fighting_Vessel
IRI: http://www.datacron-project.eu/datAcron#Tug_Ice_Breaker
IRI: http://www.datacron-project.eu/datAcron#Tug_Pilot_Ship
IRI: http://www.datacron-project.eu/datAcron#Tug_Supply_Vessel
IRI: http://www.datacron-project.eu/datAcron#Tug_Support
IRI: http://www.datacron-project.eu/datAcron#Tug_Tender
IRI: http://www.datacron-project.eu/datAcron#Tug_Vessel
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#TypeCollection
A Collection whose members are the maximal set of individuals that share the same (named) type, e.g. "the gem stones", "the Italians". This class is very useful to apply a variety of the so-called "ClassesAsValues" design pattern, when it is used to talk about the extensional aspect of a class. An alternative variety of the pattern applies to the intensional aspect of a class, and the class Concept should be used instead.
IRI: http://www.datacron-project.eu/datAcron#TyphoonHarborPort
Typhoon Harbor port. See Pub150bk.pdf
IRI: http://www.datacron-project.eu/datAcron#Unclassified_navaid
Undefined Navaid type
IRI: http://www.datacron-project.eu/datAcron#UndefinedRoute
IRI: http://www.datacron-project.eu/datAcron#Undefined_Vessel
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#UnitOfMeasure
Units of measure are conceptualized here as parameters on regions, which can be valued as datatype values.
IRI: http://www.datacron-project.eu/datAcron#UnknownModelCategory
IRI: http://www.datacron-project.eu/datAcron#Utility_Vessel
IRI: http://www.datacron-project.eu/datAcron#VHF_Omnidirectional_Radio_Range
Also known as VOR
IRI: http://www.datacron-project.eu/datAcron#VOR_and_DME
VOR_DME
IRI: http://www.datacron-project.eu/datAcron#VOR_and_TACAN
VORTAC
IRI: http://www.datacron-project.eu/datAcron#Vegetable_Animal_Oil_Tanker
IRI: http://www.datacron-project.eu/datAcron#Vehicle_Carrier
IRI: http://www.datacron-project.eu/datAcron#Vehicles_Carrier
IRI: http://www.datacron-project.eu/datAcron#VerySmallSizePort
The classification of harbor size is based on several applicable factors, including area, facilities, and wharf space. It is not based on area alone or on any other single factor.
IRI: http://www.datacron-project.eu/datAcron#Vessel
The class of moving objects with floating capabilities. Please notice that aviation specific classes and properties are provided in a separate module
IRI: http://www.datacron-project.eu/datAcron#VesselType
IRI: http://www.datacron-project.eu/datAcron#WIG_Vessel
IRI: http://www.datacron-project.eu/datAcron#Waste_Disposal_Vessel
IRI: http://www.datacron-project.eu/datAcron#Water_Jet_Dredging_Pontoon
IRI: http://www.datacron-project.eu/datAcron#Water_Tanker
IRI: http://www.datacron-project.eu/datAcron#Waypoint
Waypoint. A specified geographical location used to define an area navigation route or the flight path of an aircraft employing area navigation. Example: "the airplane is located 10 miles north of WOODY"
IRI: http://www.datacron-project.eu/datAcron#WeatherCondition
A weather condition reported for an associated Region
IRI: http://www.datacron-project.eu/datAcron#Well_Stimulation_Vessel
IRI: http://www.datacron-project.eu/datAcron#Whale_Factory
IRI: http://www.datacron-project.eu/datAcron#Whaler
IRI: http://www.datacron-project.eu/datAcron#Wine_Tanker
IRI: http://www.datacron-project.eu/datAcron#Wing_In_Ground_Effect_Vessel
IRI: http://www.datacron-project.eu/datAcron#Wood_Chips_Carrier
IRI: http://www.datacron-project.eu/datAcron#Work_Pontoon
IRI: http://www.datacron-project.eu/datAcron#Work_Vessel
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Workflow
A Plan that defines Role(s), Task(s), and a specific structure for tasks to be executed, usually supporting the work of an Organization
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#WorkflowExecution
IRI: http://www.datacron-project.eu/datAcron#Yacht
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#actsFor
The relation holding between any Agent, and a SocialAgent. In principle, a SocialAgent requires at least one PhysicalAgent in order to act, but this dependency can be 'delegated'; e.g. a university can be acted for by a department, which on its turm is acted for by physical agents.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#actsThrough
The relation holding between a PhysicalAgent and a SocialAgent. In principle, a SocialAgent requires at least one PhysicalAgent in order to act, but this dependency can be 'delegated', e.g. a university can be acted for by a department, which is acted for by physical agents. AKA isActedBy
IRI: http://www.datacron-project.eu/datAcron#Aerodrome_serves_City
IRI: http://www.datacron-project.eu/datAcron#affects
IRI: http://www.datacron-project.eu/datAcron#AircraftOwnedBy
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#associatedWith
A catch-all object property, useful for alignment and querying purposes.
has characteristics: symmetric, transitive
IRI: http://www.datacron-project.eu/datAcron#belongsTo
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#characterizes
A relation between concepts and collections, where a Concept is said to characterize a Collection; it corresponds to a link between the (reified) intensional and extensional interpretations of a proper subset of a (reified) class. This is different from covers, because it refers to an interpretation the entire reified class. E.g. the collection of vintage saxophones is characterized by the Concept 'manufactured by hand', while it gets covered by the Concept 'Saxophone' with the Parameter 'Vintage'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#classifies
A relation between a Concept and an Entity, e.g. the Role 'student' classifies a Person 'John'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#coparticipatesWith
A relation between two objects participating in a same Event; e.g., 'Vitas and Jimmy are playing tennis'.
has characteristics: symmetric
IRI: http://www.datacron-project.eu/datAcron#comprises
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#conceptualizes
A relation stating that an Agent is internally representing a SocialObject: situations, descriptions, concepts, etc. E.g., 'John believes in the conspiracy theory'; 'Niels Bohr created the solar-system metaphor for the atomic theory'; 'Jacques assumes all swans are white'; 'the task force members share the attack plan'. Conceptualizations can be distinguished into different forms, primarily based on the type of SocialObject that is conceptualized. Descriptions and concepts can be 'assumed', situations can be 'believed' or 'known', plans can be 'adopted', etc. (see ontology: http://www.ontologydesignpatterns.org/ont/dul/Conceptualization.owl.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#concretelyExpresses
A relation between an InformationRealization and a Description, e.g. 'the printout of the Italian Constitution concretelyExpresses the Italian Constitution'. It should be supplied also with a rule stating that the InformationRealization realizes an InformationObject that expresses the Description
IRI: http://www.datacron-project.eu/datAcron#configurationOfAirspace
IRI: http://www.datacron-project.eu/datAcron#controlledByATC
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#covers
A relation between concepts and collections, where a Concept is said to cover a Collection; it corresponds to a link between the (reified) intensional and extensional interpretations of a (reified) class. E.g. the collection of vintage saxophones is covered by the Concept 'Saxophone' with the Parameter 'Vintage'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#defines
A relation between a Description and a Concept, e.g. a Workflow for a governmental Organization defines the Role 'officer', or 'the Italian Traffic Law defines the role Vehicle'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#definesRole
A relation between a description and a role, e.g. the recipe for a cake defines the role 'ingredient'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#definesTask
A relation between a description and a task, e.g. the recipe for a cake defines the task 'boil'.
IRI: http://www.datacron-project.eu/datAcron#departureAirport
IRI: http://www.datacron-project.eu/datAcron#departureOfTrajectory
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#describes
The relation between a Description and an Entity : a Description gives a unity to a Collection of parts (the components), or constituents, by assigning a Role to each of them in the context of a whole Object (the system). A same Entity can be given different descriptions, for example, an old cradle can be given a unifying Description based on the original aesthetic design, the functionality it was built for, or a new aesthetic functionality in which it can be used as a flower pot.
IRI: http://www.datacron-project.eu/datAcron#destinationAirport
IRI: http://www.datacron-project.eu/datAcron#destinationOfTrajectory
IRI: http://www.datacron-project.eu/datAcron#directPartOfFAO
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#directlyFollows
The intransitive follows relation. For example, Wednesday directly precedes Thursday. Directness of precedence depends on the designer conceptualization.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#directlyPrecedes
The intransitive precedes relation. For example, Monday directly precedes Tuesday. Directness of precedence depends on the designer conceptualization.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#executesTask
A relation between an action and a task, e.g. 'putting some water in a pot and putting the pot on a fire until the water starts bubbling' executes the task 'boiling'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#expands
A partial order relation that holds between descriptions. It represents the proper part relation between a description and another description featuring the same properties as the former, with at least one additional one. Descriptions can be expanded either by adding other descriptions as parts, or by refining concepts that are used by them. An 'intention' to expand must be present (unless purely formal theories are considered, but even in this case a criterion of relevance is usually active).
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#expresses
A relation between an InformationObject and a 'meaning', generalized here as a 'SocialObject'. For example: 'A Beehive is a structure in which bees are kept, typically in the form of a dome or box.' (Oxford dictionary)'; 'the term Beehive expresses the concept Beehive in my apiculture ontology'. The intuition for 'meaning' is intended to be very broad. A separate, large comment is included for those who want to investigate more on what kind of meaning can be represented in what form.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#expressesConcept
A relation between an InformationObject and a Concept , e.g. the term "dog" expresses the Concept "dog". For expressing a relational meaning, see the more general object property: expresses
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#farFrom
Generic distance relation between any Entity(s). E.g. Rome is far from Beijing, astronomy is far from necromancy.
has characteristics: symmetric
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#follows
A relation between entities, expressing a 'sequence' schema. E.g. 'year 2000 follows 1999', 'preparing coffee' follows 'deciding what coffee to use', 'II World War follows I World War', etc. It can be used between tasks, processes or time intervals, and subproperties would fit best in order to distinguish the different uses.
has characteristics: transitive
IRI: http://www.datacron-project.eu/datAcron#hasAircraftModel
IRI: http://www.datacron-project.eu/datAcron#hasAirlineCountry
Each airline is located at a country. This property expresses the relation between an airline and the country it is located in.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasCommonBoundary
A relation to encode either formal or informal characterizations of 'boundaries' common to two different entities: an Event that ends when another begins, two abstract regions that have a common topological boundary, two objects that are said to be 'in contact' from a commonsense perspective, etc.
has characteristics: symmetric
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasComponent
The hasPart relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the Object.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasConstituent
'Constituency' depends on some layering of the world described by the ontology. For example, scientific granularities (e.g. body-organ-tissue-cell) or ontological 'strata' (e.g. social-mental-biological-physical) are typical layerings. Intuitively, a constituent is a part belonging to a lower layer. Since layering is actually a partition of the world described by the ontology, constituents are not properly classified as parts, although this kinship can be intuitive for common sense. A desirable advantage of this distinction is that we are able to talk e.g. of physical constituents of non-physical objects (e.g. systems), while this is not possible in terms of parts. Example of are the persons constituting a social system, the molecules constituting a person, the atoms constituting a river, etc. In all these examples, we notice a typical discontinuity between the constituted and the constituent object: e.g. a social system is conceptualized at a different layer from the persons that constitute it, a person is conceptualized at a different layer from the molecules that constitute them, and a river is conceptualized at a different layer from the atoms that constitute it.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasConstraint
A relation between parameters and entities. It allows to assert generic constraints (encoded as parameters), e.g. MinimumAgeForDriving isConstraintFor John (where John is a legal subject under the TrafficLaw). The intended semantics (not expressible in OWL) is that a Parameter isParameterFor a Concept that classifies an Entity; moreover, it entails that a Parameter parametrizes a Region that isRegionFor that Entity.
IRI: http://www.datacron-project.eu/datAcron#hasContextualFeature
IRI: http://www.datacron-project.eu/datAcron#hasDeparture
IRI: http://www.datacron-project.eu/datAcron#hasDependenceTo
An entity is dependent from another entity, e.g. an airport that depends on another collocated airport
IRI: http://www.datacron-project.eu/datAcron#hasDestination
IRI: http://www.datacron-project.eu/datAcron#hasEnd
IRI: http://www.datacron-project.eu/datAcron#hasEndInstant
IRI: http://www.datacron-project.eu/datAcron#hasEndingNavAid
IRI: http://www.datacron-project.eu/datAcron#hasEndingPoint
IRI: http://www.datacron-project.eu/datAcron#hasGeometry
IRI: http://www.datacron-project.eu/datAcron#hasHighPoint
IRI: http://www.datacron-project.eu/datAcron#hasIFR_ApproachFix_Navaid
IRI: http://www.datacron-project.eu/datAcron#hasIFR_ApproachFix_Point
IRI: http://www.datacron-project.eu/datAcron#hasIFR_DesignatedPoint
IRI: http://www.datacron-project.eu/datAcron#hasIFR_Navaid
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasLocation
A generic, relative spatial location, holding between any entities. E.g. 'the cat is on the mat', 'Omar is in Samarcanda', 'the wound is close to the femural artery'. For 'absolute' locations, see SpaceRegion
IRI: http://www.datacron-project.eu/datAcron#hasLowPoint
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasMember
A relation between collections and entities, e.g. 'my collection of saxophones includes an old Adolphe Sax original alto' (i.e. my collection has member an Adolphe Sax alto).
IRI: http://www.datacron-project.eu/datAcron#hasOpeningPeriod
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasParameter
A Concept can have a Parameter that constrains the attributes that a classified Entity can have in a certain Situation, e.g. a 4WheelDriver Role definedIn the ItalianTrafficLaw has a MinimumAge parameter on the Amount 16.
IRI: http://www.datacron-project.eu/datAcron#hasPart
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasPart
A schematic relation between any entities, e.g. 'the human body has a brain as part', '20th century contains year 1923', 'World War II includes the Pearl Harbour event'. Subproperties and restrictions can be used to specialize hasPart for objects, events, etc.
has characteristics: transitive
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasParticipant
A relation between an object and a process, e.g. 'John took part in the discussion', 'a large mass of snow fell during the avalanche', or 'a cook, some sugar, flour, etc. are all present in the cooking of a cake'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasPostcondition
Direct succession applied to situations. E.g., 'A postcondition of our Plan is to have things settled'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasPrecondition
Direct precedence applied to situations. E.g., 'A precondition to declare war against a foreign country is claiming to find nuclear weapons in it'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasQuality
A relation between entities and qualities, e.g. 'Dmitri's skin is yellowish'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasRegion
A relation between entities and regions, e.g. 'the number of wheels of that truck is 12', 'the time of the experiment is August 9th, 2004', 'the whale has been localized at 34 degrees E, 20 degrees S'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasRole
A relation between an object and a role, e.g. the person 'John' has role 'student'.
IRI: http://www.datacron-project.eu/datAcron#hasRouteAvailability
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasSetting
A relation between entities and situations, e.g. 'this morning I've prepared my coffee with a new fantastic Arabica', i.e.: (an amount of) a new fantastic Arabica hasSetting the preparation of my coffee this morning.
IRI: http://www.datacron-project.eu/datAcron#hasStart
IRI: http://www.datacron-project.eu/datAcron#hasStartInstant
IRI: http://www.datacron-project.eu/datAcron#hasStartingNavAid
IRI: http://www.datacron-project.eu/datAcron#hasStartingPoint
This property identifies the starting point of a SengmentLeg, such as DepartureLeg/ArrivalLeg.
IRI: http://www.datacron-project.eu/datAcron#hasSuccessor
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasTask
A relation between roles and tasks, e.g. 'students have the duty of giving exams' (i.e. the Role 'student' hasTask the Task 'giving exams').
IRI: http://www.datacron-project.eu/datAcron#hasTemporalFeature
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasTimeInterval
The generic relation between events and time intervals.
IRI: http://www.datacron-project.eu/datAcron#hasVesselCountry
The country a specific vessel belongs.
IRI: http://www.datacron-project.eu/datAcron#has_vesselFixingDeviceType
IRI: http://www.datacron-project.eu/datAcron#has_vesselLengthRegistered
IRI: http://www.datacron-project.eu/datAcron#has_vesselNetTonnage
IRI: http://www.datacron-project.eu/datAcron#has_vesselWidthRegistered
IRI: http://www.datacron-project.eu/datAcron#hasWeatherConditions
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#includesAction
A relation between situations and actions, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: the preparation of my coffee this morning included a burning of my fingers).
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#includesAgent
A relation between situations and persons, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: the preparation of my coffee this morning included me).
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#includesEvent
A relation between situations and events, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: the preparation of my coffee this morning included a burning of my fingers).
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#includesObject
A relation between situations and objects, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: the preparation of my coffee this morning included me).
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#includesTime
A relation between situations and time intervals, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: preparing my coffee was held this morning). A data value attached to the time interval typically complements this modelling pattern.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#introduces
A relation between a Description and a SocialAgent, e.g. a Constitutional Charter introduces the SocialAgent 'PresidentOfRepublic'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#involvesAgent
Agent participation.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isAbout
A relation between information objects and any Entity (including information objects). It can be used to talk about e.g. entities are references of proper nouns: the proper noun 'Leonardo da Vinci' isAbout the Person Leonardo da Vinci; as well as to talk about sets of entities that can be described by a common noun: the common noun 'person' isAbout the set of all persons in a domain of discourse, which can be represented in DOLCE-Ultralite as an individual of the class: Collection . The isAbout relation is reflexive (not expressible in OWL1.0), because information objects are also about themselves.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isActionIncludedIn
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isAgentIncludedIn
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isAgentInvolvedIn
Agent participation.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isCharacterizedBy
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isClassifiedBy
A relation between a Concept and an Entity, e.g. 'John is considered a typical rude man'; your last concert constitutes the achievement of a lifetime; '20-year-old means she's mature enough'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isComponentOf
The hasPart relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the Object.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isConceptExpressedBy
A relation between an InformationObject and a Concept , e.g. the term "dog" expresses the Concept "dog". For expressing a relational meaning, see the more general object property: expresses
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isConceptUsedIn
A more generic relation holding between a Description and a Concept. In order to be used, a Concept must be previously definedIn another Description
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isConceptualizedBy
A relation stating that an Agent is internally representing a Description . E.g., 'John believes in the conspiracy theory'; 'Niels Bohr created a solar-system metaphor for his atomic theory'; 'Jacques assumes all swans are white'; 'the task force shares the attack plan'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isConcretelyExpressedBy
A relation between an InformationRealization and a Description, e.g. 'the printout of the Italian Constitution concretelyExpresses the Italian Constitution'. It should be supplied also with a rule stating that the InformationRealization realizes an InformationObject that expresses the Description
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isConstituentOf
'Constituency' depends on some layering of the world described by the ontology. For example, scientific granularities (e.g. body-organ-tissue-cell) or ontological 'strata' (e.g. social-mental-biological-physical) are typical layerings. Intuitively, a constituent is a part belonging to a lower layer. Since layering is actually a partition of the world described by the ontology, constituents are not properly classified as parts, although this kinship can be intuitive for common sense. A desirable advantage of this distinction is that we are able to talk e.g. of physical constituents of non-physical objects (e.g. systems), while this is not possible in terms of parts. Example of are the persons constituting a social system, the molecules constituting a person, the atoms constituting a river, etc. In all these examples, we notice a typical discontinuity between the constituted and the constituent object: e.g. a social system is conceptualized at a different layer from the persons that constitute it, a person is conceptualized at a different layer from the molecules that constitute them, and a river is conceptualized at a different layer from the atoms that constitute it.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isConstraintFor
A relation between parameters and entities. It allows to assert generic constraints (encoded as parameters), e.g. MinimumAgeForDriving isConstraintFor John (where John is a legal subject under the TrafficLaw). The intended semantics (not expressible in OWL) is that a Parameter isConstraintFor and Entity if the Parameter isParameterFor a Concept that classifies that Entity; moreover, it entails that a Parameter parametrizes a Region that isRegionFor that Entity. The use in OWL is therefore a shortcut to annotate what Parameter constrains what Entity
IRI: http://www.datacron-project.eu/datAcron#is_corresponding_to
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isCoveredBy
A relation between concepts and collections, where a Concept is said to cover a Collection; it corresponds to a link between the (reified) intensional and extensional interpretations of a (reified) class. E.g. the collection of vintage saxophones is covered by the Concept 'Saxophone' with the Parameter 'Vintage'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isDefinedIn
A relation between a Description and a Concept, e.g. a Workflow for a governmental Organization defines the Role 'officer', or 'the Italian Traffic Law defines the role Vehicle'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isDescribedBy
The relation between an Entity and a Description: a Description gives a unity to a Collection of parts (the components), or constituents, by assigning a Role to each of them in the context of a whole Object (the system). A same Entity can be given different descriptions, for example, an old cradle can be given a unifying Description based on the original aesthetic design, the functionality it was built for, or a new aesthetic functionality in which it can be used as a flower pot.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isEventIncludedIn
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isExecutedIn
A relation between an action and a task, e.g. 'putting some water in a pot and putting the pot on a fire until the water starts bubbling' executes the task 'boiling'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isExpandedIn
A partial order relation that holds between descriptions. It represents the proper part relation between a description and another description featuring the same properties as the former, with at least one additional one. Descriptions can be expanded either by adding other descriptions as parts, or by refining concepts that are used by them. An 'intention' to expand must be present (unless purely formal theories are considered, but even in this case a criterion of relevance is usually active).
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isExpressedBy
A relation between a dul:SocialObject (the 'meaning') and a dul:InformationObject (the 'expression'). For example: 'A Beehive is a structure in which bees are kept, typically in the form of a dome or box.' (Oxford dictionary)'; 'the term Beehive expresses the concept Beehive in my apiculture ontology'. The intuition for 'meaning' is intended to be very broad. A separate, large comment is included in the encoding of 'expresses', for those who want to investigate more on what kind of meaning can be represented in what form.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#sameSettingAs
A relation between two entities participating in a same Situation; e.g., 'Our company provides an antivenom service' (the situation is the service, the two entities are the company and the antivenom).
has characteristics: symmetric
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isIntroducedBy
A relation between a Description and a SocialAgent, e.g. a Constitutional Charter introduces the SocialAgent 'PresidentOfRepublic'.
IRI: http://www.datacron-project.eu/datAcron#isKnownAs
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isLocationOf
A generic, relative localization, holding between any entities. E.g. 'Rome is the seat of the Pope', 'the liver is the location of the tumor'. For 'absolute' locations, see SpaceRegion
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isMemberOf
A relation between collections and entities, e.g. 'the Night Watch by Rembrandt is in the Rijksmuseum collection'; 'Davide is member of the Pen Club', 'Igor is one the subjects chosen for the experiment'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isObjectIncludedIn
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isObservableAt
A relation to represent a (past, present or future) TimeInterval at which an Entity is observable. In order to encode a specific time, a data value should be related to the TimeInterval. An alternative way of representing time is the datatype property: hasIntervalDate
IRI: http://www.datacron-project.eu/datAcron#isOwnershipOf
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isParameterFor
A Concept can have a Parameter that constrains the attributes that a classified Entity can have in a certain Situation, e.g. a 4WheelDriver Role definedIn the ItalianTrafficLaw has a MinimumAge parameter on the Amount 16.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isParametrizedBy
The relation between a Parameter, e.g. 'MajorAge', and a Region, e.g. '>17 year'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isPartOf
A relation between any entities, e.g.'brain is a part of the human body'.
has characteristics: transitive
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isParticipantIn
A relation between an object and a process, e.g. 'John took part in the discussion', 'a large mass of snow fell during the avalanche', or 'a cook, some sugar, flour, etc. are all present in the cooking of a cake'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isPostconditionOf
Direct succession applied to situations. E.g., 'Taking some rest is a postcondition of my search for a hotel'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isPreconditionOf
Direct precedence applied to situations. E.g., 'claiming to find nuclear weapons in a foreign country is a precondition to declare war against it'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isQualityOf
A relation between entities and qualities, e.g. 'Dmitri's skin is yellowish'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isRealizedBy
A relation between an information realization and an information object, e.g. the paper copy of the Italian Constitution realizes the text of the Constitution.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isReferenceOf
A relation between information objects and any Entity (including information objects). It can be used to talk about e.g. entities are references of proper nouns: the proper noun 'Leonardo da Vinci' isAbout the Person Leonardo da Vinci; as well as to talk about sets of entities that can be described by a common noun: the common noun 'person' isAbout the set of all persons in a domain of discourse, which can be represented in DOLCE-Ultralite as an individual of the class: Collection . The isReferenceOf relation is irreflexive, differently from its inverse isAbout.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isReferenceOfInformationRealizedBy
The relation between entities and information realizations, e.g. between Italy and a paper copy of the text of the Italian Constitution.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isRegionFor
A relation between entities and regions, e.g. 'the color of my car is red'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isRelatedToConcept
Any relation between concepts, e.g. superordinated, conceptual parthood, having a parameter, having a task, superordination, etc.
has characteristics: symmetric
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isRelatedToDescription
Any relation between descriptions.
has characteristics: symmetric
IRI: http://www.datacron-project.eu/datAcron#isReportedBy
An Information entity (e.g. Document) that has been reported by another entity. For example a blacklist report that has been reported by a maritime authority
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isRoleDefinedIn
A relation between a description and a role, e.g. the role 'Ingredient' is defined in the recipe for a cake.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isRoleOf
A relation between an object and a role, e.g. 'student' is the role of 'John'.
IRI: http://www.datacron-project.eu/datAcron#isRouteForPort
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isSatisfiedBy
A relation between a Situation and a Description, e.g. the execution of a Plan satisfies that plan.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isSettingFor
A relation between situations and entities, e.g. 'this morning I've prepared my coffee with a new fantastic Arabica', i.e.: the preparation of my coffee this morning is the setting for (an amount of) a new fantastic Arabica.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isSpecializedBy
A partial order relation that holds between social objects. It represents the subsumption relation between e.g. a Concept and another Concept that is broader in extensional interpretation, but narrowe in intensional interpretation. E.g. PhDStudent Role specializes Student Role
has characteristics: transitive
IRI: http://www.datacron-project.eu/datAcron#isStandardInstrumentArrivalForAirport
IRI: http://www.datacron-project.eu/datAcron#isStandardInstrumentDepartureForAirport
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isSubordinatedTo
Direct succession applied to concepts. E.g. the role 'Officer' is subordinated to 'Director'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isSuperordinatedTo
Direct precedence applied to concepts. E.g. the role 'Executive' is superordinated to 'DepartmentManager'.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isTaskDefinedIn
A relation between a description and a task, e.g. the task 'boil' is defined in a recipe for a cake.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isTaskOf
A relation between roles and tasks, e.g. 'students have the duty of giving exams' (i.e. the Role 'student' hasTask the Task 'giving exams').
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isTimeIncludedIn
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isTimeIntervalOf
The generic relation between time intervals and events.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isTimeOfObservationOf
A relation to represent a (past, present or future) TimeInterval at which an Entity is observable. In order to encode a specific time, a data value should be related to the TimeInterval. An alternative way of representing time is the datatype property: hasIntervalDate
IRI: http://www.datacron-project.eu/datAcron#isTypeOf
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isUnifiedBy
A Collection has a unification criterion, provided by a Description; for example, a community of practice can be unified by a shared theory or interest, e.g. the community that makes research on mirror neurons shares some core knowledge about mirror neurons, which can be represented as a Description MirrorNeuronTheory that unifies the community. There can be several unifying descriptions.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#nearTo
Generic distance relation between any Entity(s). E.g. Rome is near to Florence, astronomy is near to physics.
has characteristics: symmetric
IRI: http://www.datacron-project.eu/datAcron#occurs
IRI: http://www.datacron-project.eu/datAcron#ofAirspaceLayer
IRI: http://www.datacron-project.eu/datAcron#ofMovingObject
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#overlaps
A schematic relation between any entities, e.g. 'the chest region overlaps with the abdomen region', 'my spoken words overlap with hers', 'the time of my leave overlaps with the time of your arrival', 'fibromyalgia overlaps with other conditions'. Subproperties and restrictions can be used to specialize overlaps for objects, events, time intervals, etc.
has characteristics: symmetric
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#parametrizes
The relation between a Parameter, e.g. 'MajorAgeLimit', and a Region, e.g. '18_year'. For a more data-oriented relation, see hasDataValue
IRI: http://www.datacron-project.eu/datAcron#partOfCountry
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#precedes
A relation between entities, expressing a 'sequence' schema. E.g. 'year 1999 precedes 2000', 'deciding what coffee to use' precedes 'preparing coffee', 'World War II follows World War I', 'in the Milan to Rome autoroute, Bologna precedes Florence', etc. It can then be used between tasks, processes, time intervals, spatially locate objects, situations, etc. Subproperties can be defined in order to distinguish the different uses.
has characteristics: transitive
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#realizes
A relation between an information realization and an information object, e.g. the paper copy of the Italian Constitution realizes the text of the Constitution.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#realizesInformationAbout
The relation between entities and information realizations, e.g. between Italy and a paper copy of the text of the Italian Constitution.
IRI: http://www.datacron-project.eu/datAcron#reportsTrajectory
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#satisfies
A relation between a Situation and a Description, e.g. the execution of a Plan satisfies that plan.
IRI: http://www.datacron-project.eu/datAcron#sovereignt_of
Example: the EEZ of a country, is under the sovereignt of that country
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#specializes
A partial order relation that holds between social objects. It mainly represents the subsumption relation between e.g. a Concept or Description and another Concept (resp. Description) that is broader in extensional interpretation, but narrower in intensional interpretation. For example, the role PhDStudent specializes the role Student. Another possible use is between a Collection that isCoveredBy a Concept A, and another Collection that isCoveredBy a Concept B that on its turm specializes A. For example, the 70,000 series Selmer Mark VI saxophone Collection specializes the Selmer Mark VI saxophone Collection.
has characteristics: transitive
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#unifies
A Collection has a unification criterion, provided by a Description; for example, a community of practice can be unified by a shared theory or interest, e.g. the community that makes research on mirror neurons shares some core knowledge about mirror neurons, which can be represented as a Description MirrorNeuronTheory that unifies the community. There can be several unifying descriptions.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#usesConcept
A generic relation holding between a Description and a Concept. In order to be used, a Concept must be previously definedIn another Description. This last condition cannot be encoded for object properties in OWL.
IRI: http://www.datacron-project.eu/datAcron#vesselRegisteredAtPort
IRI: http://www.datacron-project.eu/datAcron#Aircraft_icao_code
IRI: http://www.datacron-project.eu/datAcron#AircraftModelAbsoluteCeiling
IRI: http://www.datacron-project.eu/datAcron#AircraftModelDepiction
IRI: http://www.datacron-project.eu/datAcron#AircraftModelDescription
IRI: http://www.datacron-project.eu/datAcron#AircraftModelFuelCapacity
IRI: http://www.datacron-project.eu/datAcron#AircraftModelHeight
IRI: http://www.datacron-project.eu/datAcron#AircraftModelLandingDistance
IRI: http://www.datacron-project.eu/datAcron#AircraftModelLength
IRI: http://www.datacron-project.eu/datAcron#AircraftModelMaxClimbRate
IRI: http://www.datacron-project.eu/datAcron#AircraftModelMaxLift
IRI: http://www.datacron-project.eu/datAcron#AircraftModelMaxRange
IRI: http://www.datacron-project.eu/datAcron#AircraftModelMaxSpeed
IRI: http://www.datacron-project.eu/datAcron#AircraftModelOptimumCeiling
IRI: http://www.datacron-project.eu/datAcron#AircraftModelOptimumSpeed
IRI: http://www.datacron-project.eu/datAcron#AircraftModelPersonsOnBoard
IRI: http://www.datacron-project.eu/datAcron#AircraftModelTakeOffDistance
IRI: http://www.datacron-project.eu/datAcron#AircraftModelWingSpan
IRI: http://www.datacron-project.eu/datAcron#Aircraft_name
IRI: http://www.datacron-project.eu/datAcron#duration
The duration of the interval in minutes
IRI: http://www.datacron-project.eu/datAcron#EOBT
The Estimated Off-Block time submitted in the Flight plan
IRI: http://www.datacron-project.eu/datAcron#elevationOfPlace
IRI: http://www.datacron-project.eu/datAcron#FP_CruiseSpeedAltitude
The reported cruise speed altitude in the flight plan
IRI: http://www.datacron-project.eu/datAcron#hasAircraftRegID
IRI: http://www.datacron-project.eu/datAcron#hasAirlineIATA2code
IRI: http://www.datacron-project.eu/datAcron#hasAirlineICAO3code
IRI: http://www.datacron-project.eu/datAcron#hasAirlineName
IRI: http://www.datacron-project.eu/datAcron#hasAirspeed
IRI: http://www.datacron-project.eu/datAcron#hasAltitude
Pressure Altitude (meters). The vertical distance of a level, a point or an object considered as a point, measured from mean sea level (MSL).
IRI: http://www.datacron-project.eu/datAcron#hasCapacity
IRI: http://www.datacron-project.eu/datAcron#hasCountryCode
IRI: http://www.datacron-project.eu/datAcron#has_country_code
The country code of the specific state
IRI: http://www.datacron-project.eu/datAcron#hasDescription
A textual description of an entity
IRI: http://www.datacron-project.eu/datAcron#hasDesignatedType
IRI: http://www.datacron-project.eu/datAcron#hasDirection
The direction of RouteSegment availability
IRI: http://www.datacron-project.eu/datAcron#has_draught
Draught is the distance between the waterline and the bottom of the keel of the vessel.
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasEventDate
A datatype property that encodes values from xsd:date for an Event; a same Event can have more than one xsd:date value: begin date, end date, date at which the interval holds, as well as dates expressed in different formats: xsd:gYear, xsd:dateTime, etc.
IRI: http://www.datacron-project.eu/datAcron#has_FStationID
The ID of the port in EuroGlobalMap datasource.
IRI: http://www.datacron-project.eu/datAcron#hasHeading
Heading. The heading of the moving object associated to this semantic node. The direction in which the longitudinal axis of an object is pointed, usually expressed in degrees from North (true, magnetic, compass or grid).
IRI: http://www.datacron-project.eu/datAcron#hasIATAcode
IRI: http://www.datacron-project.eu/datAcron#hasICAOcode
IRI: http://www.datacron-project.eu/datAcron#hasIFR_availability
IRI: http://www.datacron-project.eu/datAcron#hasIFR_designator
IRI: http://www.datacron-project.eu/datAcron#hasIFR_instruction
IRI: http://www.datacron-project.eu/datAcron#hasIMOcode
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasIntervalDate
A datatype property that encodes values from xsd:date for a TimeInterval; a same TimeInterval can have more than one xsd:date value: begin date, end date, date at which the interval holds, as well as dates expressed in different formats: xsd:gYear, xsd:dateTime, etc.
IRI: http://www.datacron-project.eu/datAcron#hasLattitude
IRI: http://www.datacron-project.eu/datAcron#hasLength
IRI: http://www.datacron-project.eu/datAcron#hasLongitude
IRI: http://www.datacron-project.eu/datAcron#hasLowerLevel
Used by Airblock and RouteSegment entities
IRI: http://www.datacron-project.eu/datAcron#hasLowerLevelReference
IRI: http://www.datacron-project.eu/datAcron#hasMBR_WKT
IRI: http://www.datacron-project.eu/datAcron#hasManifacturer
IRI: http://www.datacron-project.eu/datAcron#hasMass
The reported current mass of the moving object (Kgr)
IRI: http://www.datacron-project.eu/datAcron#hasName
A brief natural language reference for an entity
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasParameterDataValue
Parametrizes values from a datatype. For example, a Parameter MinimumAgeForDriving hasParameterDataValue 18 on datatype xsd:int, in the Italian traffic code. In this example, MinimumAgeForDriving isDefinedIn the Norm ItalianTrafficCodeAgeDriving. More complex parametrization requires workarounds. E.g. AgeRangeForDrugUsage could parametrize data value: 14 to 50 on the datatype: xsd:int. Since complex datatypes are not allowed in OWL1.0, a solution to this can only work by creating two 'sub-parameters': MinimumAgeForDrugUsage (that hasParameterDataValue 14) and MaximumAgeForDrugUsage (that hasParameterDataValue 50), which are components of (cf. hasComponent) the main Parameter AgeRangeForDrugUsage. Ordering on subparameters can be created by using or specializing the object property 'precedes'.
IRI: http://www.datacron-project.eu/datAcron#hasPlaceName
IRI: http://www.datacron-project.eu/datAcron#hasPopulation
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasRegionDataValue
A datatype property that encodes values for a Region, e.g. a float for the Region Height.
IRI: http://www.datacron-project.eu/datAcron#hasRouteDesNumber
The designator number of an aviation Route
IRI: http://www.datacron-project.eu/datAcron#hasRouteDesPrefix
The Designator prefix of an aviation route
IRI: http://www.datacron-project.eu/datAcron#hasRouteDesSecondLetter
The Route Designator Second Letter provided for an aviation route
IRI: http://www.datacron-project.eu/datAcron#hasRouteMultipleId
A suffix for the route designator, indicating alternates for homonymous routes (especially for military training routes).
IRI: http://www.datacron-project.eu/datAcron#hasRouteStatus
IRI: http://www.datacron-project.eu/datAcron#hasSourceID
The identification provided at the source of the entity
IRI: http://www.datacron-project.eu/datAcron#hasSpeed
The speed measurement on earth surface
IRI: http://www.datacron-project.eu/datAcron#hasUpperLevel
Used by Airblock and RouteSegment entities
IRI: http://www.datacron-project.eu/datAcron#hasUpperLevelReference
IRI: http://www.datacron-project.eu/datAcron#has_vesselCallSign
IRI: http://www.datacron-project.eu/datAcron#has_vesselDeadWeight
IRI: http://www.datacron-project.eu/datAcron#has_vesselFlag
IRI: http://www.datacron-project.eu/datAcron#has_vesselFuelCapacity
IRI: http://www.datacron-project.eu/datAcron#has_vesselGrossTonnage
IRI: http://www.datacron-project.eu/datAcron#has_vesselIMO
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#has_vesselLengthOverall
IRI: http://www.datacron-project.eu/datAcron#has_vesselMMSI
IRI: http://www.datacron-project.eu/datAcron#hasWKT
IRI: http://www.datacron-project.eu/datAcron#hasWPI
The WorldPortIndex identification of a port
IRI: http://www.datacron-project.eu/datAcron#has_WPI
The World Port Index ID of a port
IRI: http://www.datacron-project.eu/datAcron#ITOT
The Initial take off time submitted in the flight plan
IRI: http://www.datacron-project.eu/datAcron#isPeriodicForDay
IRI: http://www.datacron-project.eu/datAcron#powerAux
IRI: http://www.datacron-project.eu/datAcron#powerMain
IRI: http://www.datacron-project.eu/datAcron#RegulationAiracCycle
IRI: http://www.datacron-project.eu/datAcron#RegulationDescription
A short description for the regulation (if available)
IRI: http://www.datacron-project.eu/datAcron#reportedDewPoint
The reported dew point in a weather condition report
IRI: http://www.datacron-project.eu/datAcron#reportedMaxTemperature
The maximum temperature reported in a weather condition report
IRI: http://www.datacron-project.eu/datAcron#reportedMinTemperature
The minimum temperature reported in a weather condition report
IRI: http://www.datacron-project.eu/datAcron#reportedPressure
The reported pressure in a weather condition report
IRI: http://www.datacron-project.eu/datAcron#shipTypeDescription
IRI: http://www.datacron-project.eu/datAcron#TimeEnd
IRI: http://www.datacron-project.eu/datAcron#TimeStart
IRI: http://www.datacron-project.eu/datAcron#vesselConstructedAt
IRI: http://www.datacron-project.eu/datAcron#vesselConstructedYear
IRI: http://www.datacron-project.eu/datAcron#vesselName
IRI: http://www.datacron-project.eu/datAcron#windDirectionMax
The wind direction of a weather condition reported
IRI: http://www.datacron-project.eu/datAcron#windDirectionMin
The wind direction of a weather condition reported
IRI: http://www.datacron-project.eu/datAcron#windSpeedMax
The wind speed of a weather condition reported
IRI: http://www.datacron-project.eu/datAcron#windSpeedMin
The wind speed of a weather condition reported
IRI: http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasDataValue
IRI: http://www.datacron-project.eu/datAcron#AltitudeChange
The event describing that an aircraft changes its flight level
IRI: http://www.datacron-project.eu/datAcron#Chayka
IRI: http://www.datacron-project.eu/datAcron#GLONASS
IRI: http://www.datacron-project.eu/datAcron#GPS
IRI: http://www.datacron-project.eu/datAcron#GPS_GLONASS
IRI: http://www.datacron-project.eu/datAcron#Galileo
IRI: http://www.datacron-project.eu/datAcron#GapEnd
The event describing that an aircraft has been rediscovered from a communication gap
IRI: http://www.datacron-project.eu/datAcron#HeadingChange
The event describing that an aircraft has changed direction
IRI: http://www.datacron-project.eu/datAcron#integrated_navigation_system
IRI: http://www.datacron-project.eu/datAcron#internal_GNSS
An internal GNSS Fixing device used on a vessel
IRI: http://www.datacron-project.eu/datAcron#Landing
The event describing that an aircraft reaches the destination airport
IRI: http://www.datacron-project.eu/datAcron#Loran_C
IRI: http://www.datacron-project.eu/datAcron#not_associated_10
This class is a placeholder for Fixing device type. Instances from data in ''notassociated*'' classes indicate an error.
IRI: http://www.datacron-project.eu/datAcron#not_associated_11
This class is a placeholder for Fixing device type. Instances from data in ''notassociated*'' classes indicate an error.
IRI: http://www.datacron-project.eu/datAcron#not_associated_12
This class is a placeholder for Fixing device type. Instances from data in ''notassociated*'' classes indicate an error.
IRI: http://www.datacron-project.eu/datAcron#not_associated_13
This class is a placeholder for Fixing device type. Instances from data in ''notassociated*'' classes indicate an error.
IRI: http://www.datacron-project.eu/datAcron#not_associated_14
This class is a placeholder for Fixing device type. Instances from data in ''notassociated*'' classes indicate an error.
IRI: http://www.datacron-project.eu/datAcron#not_associated_9
This class is a placeholder for Fixing device type. Instances from data in ''notassociated*'' classes indicate an error.
IRI: http://www.datacron-project.eu/datAcron#ParkedEnd
The event describing that an aircraft now starts moving (i.e. from the apron of an airport)
IRI: http://www.datacron-project.eu/datAcron#ParkedStart
The event describing that an aircraft is now stopped (i.e. at the apron of an airport)
IRI: http://www.datacron-project.eu/datAcron#SlowMotionEnd
The event describing that an aircraft moves in slow motion
IRI: http://www.datacron-project.eu/datAcron#SlowMotionStart
The event describing that an aircraft moves in slow motion
IRI: http://www.datacron-project.eu/datAcron#SpeedChangeEnd
The event describing that an aircraft stops changing its speed (i.e. it stabilizes its speed)
IRI: http://www.datacron-project.eu/datAcron#SpeedChangeStart
The event describing that an aircraft starts changing its speed (i.e. accelerating/deccelerating)
IRI: http://www.datacron-project.eu/datAcron#StoppedEnd
The event describing that a vessel has started moving
IRI: http://www.datacron-project.eu/datAcron#StoppedInit
The event describing that a vessel has stopped moving
IRI: http://www.datacron-project.eu/datAcron#surveyed
IRI: http://www.datacron-project.eu/datAcron#TakeOff
The event describing that an aircraft leaves the departure airport
IRI: http://www.datacron-project.eu/datAcron#undefined
An undefined Fixing device used on a vessel
1. Alvares, L.O., Bogorny, V., Kuijpers, B., de Macêdo, J.A.F., Moelans, B., Vaisman, A.A.: A model for enriching trajectories with semantic geographical information. In: GIS. p. 22 (2007)
2. Baglioni, M., de Macêdo, J.A.F., Renso, C., Trasarti, R., Wachowicz, M.: Towards semantic interpretation of movement behavior. In: Advances in GIScience, pp. 271–288. Springer (2009)
3. Bogorny, V., Renso, C., de Aquino, A.R., de Lucca Siqueira, F., Alvares, L.O.: Constant - A conceptual data model for semantic trajectories of moving objects. Trans. GIS 18(1), 66–88 (2014)
4. Fileto, R., May, C., Renso, C., Pelekis, N., Klein, D., Theodoridis, Y.: The baquaraknowledge-based framework for semantic enrichment and analysis of movement data. Data Knowl. Eng. 98, 104–122 (2015)
5. Kotis, K., Vouros, G.A.: Human-centered ontology engineering: The HCOME methodology. Knowl. Inf. Syst. 10(1), 109–131 (2006)
6. Nogueira, T.P., Martin, H.: Querying semantic trajectory episodes. In: Proc. of MobiGIS. pp. 23–30 (2015)
7. Parent, C., Spaccapietra, S., Renso, C., Andrienko, G.L., Andrienko, N.V., Bogorny, V., Damiani, M.L., Gkoulalas-Divanis, A., de Macêdo, J.A.F., Pelekis, N., Theodoridis, Y., Yan, Z.: Semantic trajectories modeling and analysis. ACM Comput. Surv. 45(4), 42 (2013)
8. Spaccapietra, S., Parent, C., Damiani, M.L., de Macêdo, J.A.F., Porto, F., Vangenot, C.: A conceptual view on trajectories. Data Knowl. Eng. 65(1), 126–146 (2008)
This work is supported by the datAcron project, which has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No 687591.
A: Accident / incident