GeoSPARQL Ontology
type: Ontology
contributor: https://orcid.org/0000-0001-8269-8171
contributor: Matthew Perry
  type: Person
  affiliation: Oracle Corporation
created: 2017-04-17
created: 2017-10-22
created: 2020-09-09
creator: http://orcid.org/0000-0002-3884-3420
creator: Jerry Hobbs
description: An RDF/OWL vocabulary for representing spatial information
description: This ontology as a network of 8 ontology patterns relies on the SSN ontology and represents a smart environment. Each pattern model one aspect of such environments including temporal, spatial, objects, network, observation etc. The patterns are: https://w3id.org/smartenvironment/patterns/time.owl https://w3id.org/smartenvironment/patterns/geometry.owl https://w3id.org/smartenvironment/patterns/event.owl https://w3id.org/smartenvironment/patterns/object.owl https://w3id.org/smartenvironment/patterns/sensing.owl https://w3id.org/smartenvironment/patterns/situation.owl https://w3id.org/smartenvironment/patterns/place.owl https://w3id.org/smartenvironment/patterns/network.owl The links between each pair of modules is provided by specializing ther concepts' definition.
description: This ontology describes sensors, actuators and observations, and related concepts. It does not describe domain concepts, time, locations, etc. these are intended to be included from other ontologies via OWL imports.
description: This ontology describes the spatial features of things used in a smart environment. Thease feartures include the geometerical representation of objects along with the spatial and directional relations between them. This ontology relies on the two other spatial related ontologies http://www.opengis.net/ont/geosparql and http://www.observedchange.com/tisc/ns/
description: This ontology is based on the SSN Ontology by the W3C Semantic Sensor Networks Incubator Group (SSN-XG), together with considerations from the W3C/OGC Spatial Data on the Web Working Group.
description: This ontology mainly relies on the SSN ontology (http://www.w3.org/ns/ssn/) and describes a sensing process in the context on smart environment. It provides information about the sensors, the observation process and the configuration of the sensors.
description: This ontology pattern extends the OWL-Time ontology (https://www.w3.org/2006/time) and describes time in the form of time stamps, time intervals with specific starting and ending points, as well as temporal distance that indicates a relative time distance to a given time point, in the form of an interval. By relative time distance, we mean a distance regardless of the exact timepoints.
description: This pattern relies on the SSN ontology and represents sensors and the other modules needed to deploy a network in a smart environment. The concept of Network is modeled in this pattern as a System with number of sub systems in the form of Networkmodules (i.e., NodeStations and Nodes). The class Node represents the details about the content of each node station. Depending on their roles, nodes of a network are devided into types of node senders (whcih observe a phenomenon) and receivers (which receive the observation data).
description: This pattern represents the spatial structure of the smart environment in terms of its sections (e.g., rooms in case of a smart home). This pattern uses the Smart Environment Geometry pattern, DULCE and SSN ontologies.
description: This pattern specializes the ontologies DULCE (http://www.ontologydesignpatterns.org/ont/dul/DUL.owl) and SSN (http://www.w3.org/ns/ssn/). This ontology describes a situation in the context on smart environment (e.g., stove is on). In this ontology, a situation is expressed by a feature of interest (e.g., stove), its property (e.g., electriccurrent) and a specific state of this peroperty (e.g., on or off). This ontology relies on the two other ontologies DULCE (http://www.ontologydesignpatterns.org/ont/dul/DUL.owl) and SSN (http://www.w3.org/ns/ssn/).
is version of: owl-time
license: Software
license: copyright-software-and-document
license: https://creativecommons.org/licenses/by/4.0/
license: https://www.ogc.org/license
modified: 2017-04-06
modified: 2021-10-27
replaces: http://www.opengis.net/ont/geosparql/1.0
rights: Copyright 2017 W3C/OGC.
rights: Copyright © 2006-2017 W3C, OGC. W3C and OGC liability, trademark and document use rules apply.
source: http://www.opengis.net/doc/IS/geosparql/1.1
source: OGC GeoSPARQL - A Geographic Query Language for RDF Data OGC 11-052r5
title: Semantic Sensor Network Ontology
title: Sensor, Observation, Sample, and Actuator (SOSA) Ontology
title: Smart Environment Event Ontology Pattern
title: Smart Environment Geometry Ontology Pattern
title: Smart Environment Network Ontology Pattern
title: Smart Environment Object Ontology Pattern
title: Smart Environment Place Ontology Pattern
title: Smart Environment Sensing Ontology Pattern
title: Smart Environment Situation Ontology Pattern
title: Smart Environment Time Ontology Pattern
title: SmartEnv Ontology
preferred namespace prefix: time.owl
preferred namespace prefix: geo
preferred namespace prefix: https://w3id.org/smartenvironment/patterns/event.owl
preferred namespace prefix: se-event
preferred namespace prefix: se-geometry
preferred namespace prefix: se-network
preferred namespace prefix: se-object
preferred namespace prefix: se-place
preferred namespace prefix: se-sensing
preferred namespace prefix: se-situ
preferred namespace prefix: se-time
preferred namespace prefix: sh
preferred namespace prefix: sosa
preferred namespace prefix: ssn
preferred namespace uri: https://w3id.org/smartenvironment/patterns/geometry.owl
preferred namespace uri: https://w3id.org/smartenvironment/patterns/sensing.owl
preferred namespace uri: http://www.opengis.net/ont/geosparql#
preferred namespace uri: http://www.w3.org/ns/sosa/
preferred namespace uri: http://www.w3.org/ns/ssn/
covers requirements: How many and what sections are there in a smart environment?
covers requirements: What are node holders, in other words, which objects are used as the holder of sensors in a smart environment?
covers requirements: What are smart objects, in other words, which objects are the interest of an observation process?
covers requirements: What are the feature of interests considered within an observation proces?
covers requirements: What are the possible states of the feature of interests (objects under the observation process) in a smart environment?
covers requirements: What are the preconditions of a complex event? And what is the temporal distance between a complex event and its preconditions?
covers requirements: What are the spatial relations among objects or sections in a smart environment?
covers requirements: What are the spatial/directional relations between sections or between sections and objects in an environment?
covers requirements: What is the confuguration (e.g.,, sampling rate) set for a given sensor?
covers requirements: What is the node receiving the data from a giveb sensor?
covers requirements: What is the output (result) of a sensing process?
covers requirements: What is the temporal distance between two specific time steps?
covers requirements: What is the time interval between two specific timestamps in the form of dates?
covers requirements: What sensors make a sensing (observation) process?
covers requirements: When does an Event occur? (Dul:TimeInterval)
covers requirements: Where are the locations of objects in an environment?
covers requirements: Which property of an object (i.e, feature of interest) is used to conceptualize a situation?
covers requirements: Which situation (including a feature of interest; its property and its state) has been captured in the form of a manifestation event?
covers requirements: Which types of nodes are available in a network?
covers requirements: Who has participated in a given event? (Dul:Agent)

DGGS Literal
type: Datatype
definition: A textual serialization of a Discrete Global Grid (DGGS) Geometry object.
example: C.1.2.4
example: "<https://w3id.org/dggs/auspix> OrdinateList (R3234)"^^<http://www.opengis.net/ont/geosparql#dggsLiteral>
scope note: This datatype is not expected to be used directly but to serve as an abstract datatype for a series of specific DGGS literal types, for specific DGGS implementations

GeoJSON Literal
type: Datatype
definition: A GeoJSON serialization of a Geometry object.
example: C.1.2.4

GML Literal
type: Datatype
definition: A GML serialization of a Geometry object.
example: C.1.2.4

KML Literal
type: Datatype
definition: A KML serialization of a Geometry object.
example: C.1.2.4

Well-known Text Literal
type: Datatype
definition: A Well-known Text serialization of a Geometry object.
example: C.2.2.2

Generalized day
type: Datatype
comment: Day of month - formulated as a text string with a pattern constraint to reproduce the same lexical form as gDay, except that values up to 99 are permitted, in order to support calendars with more than 31 days in a month. Note that the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type.
comment: Día del mes - formulado como una cadena de texto con una restricción patrón para reproducir la misma forma léxica que gDay, excepto que se permiten valores hasta el 99, con el propósito de proporcionar soporte a calendarios con meses con más de 31 días. Nótese que el espacio de valores no está definido, por tanto, un procesador genérico de OWL2 no puede computar relaciones de orden de valores de este tipo. @es
label: Día generalizado @es

Generalized month
type: Datatype
comment: Mes del año - formulado como una cadena de texto con una restricción patrón para reproducir la misma forma léxica que gMonth, excepto que se permiten valores hasta el 20, con el propósito de proporcionar soporte a calendarios con años con más de 12 meses. Nótese que el espacio de valores no está definido, por tanto, un procesador genérico de OWL2 no puede computar relaciones de orden de valores de este tipo. @es
comment: Month of year - formulated as a text string with a pattern constraint to reproduce the same lexical form as gMonth, except that values up to 20 are permitted, in order to support calendars with more than 12 months in the year. Note that the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type.
label: Mes generalizado @es

Generalized year
type: Datatype
comment: Número de año - formulado como una cadena de texto con una restricción patrón para reproducir la misma forma léxica que gYear, aunque no está restringido a valores del calendario gregoriano. Nótese que el espacio de valores no está definido, por tanto, un procesador genérico de OWL2 no puede computar relaciones de orden de valores de este tipo. @es
comment: Year number - formulated as a text string with a pattern constraint to reproduce the same lexical form as gYear, but not restricted to values from the Gregorian calendar. Note that the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type.
label: Año generalizado @es

acts for
type: ObjectProperty
sub property of: associatedWith
inverse of: acts through
domain: Agent
range: Social agent
comment: 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.
label: agisce per @it

acts through
type: ObjectProperty
sub property of: associatedWith
domain: Social agent
range: Agent
comment: 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
label: agisce mediante @it

associatedWith
type: ObjectProperty
type: SymmetricProperty
type: TransitiveProperty
domain: Entity
range: Entity
comment: A catch-all object property, useful for alignment and querying purposes. It is declared as both transitive and symmetric, in order to reason an a maximal closure of associations between individuals.

characterizes
type: ObjectProperty
sub property of: associatedWith
inverse of: is characterized by {@en-us}
domain: Concept
range: Collection
comment: 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'.
label: caratterizza @it

classifies
type: ObjectProperty
sub property of: associatedWith
inverse of: is classified by
domain: Concept
range: Entity
comment: A relation between a Concept and an Entity, e.g. the Role 'student' classifies a Person 'John'.
label: classifica @it

conceptualizes
type: ObjectProperty
sub property of: associatedWith
inverse of: is conceptualized by
domain: Agent
range: Social object
comment: 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.
label: concettualizza @it

concretely expresses
type: ObjectProperty
sub property of: associatedWith
inverse of: is concretely expressed by
domain: Information realization
range: Social object
comment: 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
label: esprime concretamente @it

co-participates with
type: ObjectProperty
sub property of: associatedWith
type: SymmetricProperty
domain: Object
range: Object
property chain axiom: is participant in
property chain axiom: has participant
comment: A relation between two objects participating in a same Event; e.g., 'Vitas and Jimmy are playing tennis'.
label: copartecipa con @it

covers
type: ObjectProperty
sub property of: associatedWith
inverse of: is covered by
domain: Concept
range: Collection
comment: 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'.
label: ricopre @it

defines
type: ObjectProperty
sub property of: uses concept
inverse of: is defined in
domain: Description
range: Concept
comment: 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'.
label: definisce @it

defines role
type: ObjectProperty
sub property of: defines
inverse of: is role defined in
domain: Description
range: Role
comment: A relation between a description and a role, e.g. the recipe for a cake defines the role 'ingredient'.
label: definisce il ruolo @it

defines task
type: ObjectProperty
sub property of: defines
inverse of: is task defined in
domain: Description
range: Task
comment: A relation between a description and a task, e.g. the recipe for a cake defines the task 'boil'.
label: definisce il task @it

describes
type: ObjectProperty
sub property of: associatedWith
inverse of: is described by
domain: Description
range: Entity
property chain axiom: defines
property chain axiom: classifies
property chain axiom: uses concept
comment: 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.
label: descrive @it

directly follows
type: ObjectProperty
sub property of: follows
inverse of: directly precedes
domain: Entity
range: Entity
comment: The intransitive follows relation. For example, Wednesday directly precedes Thursday. Directness of precedence depends on the designer conceptualization.
label: segue direttamente @it

directly precedes
type: ObjectProperty
sub property of: precedes
domain: Entity
range: Entity
comment: The intransitive precedes relation. For example, Monday directly precedes Tuesday. Directness of precedence depends on the designer conceptualization.
label: precede direttamente @it

executes task
type: ObjectProperty
sub property of: is classified by
inverse of: is executed in
domain: Action
range: Task
comment: 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'.
label: esegue il task @it

expands
type: ObjectProperty
sub property of: is related to description
inverse of: is expanded in
domain: Description
range: Description
comment: 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).
label: espande @it

expresses
type: ObjectProperty
sub property of: associatedWith
inverse of: is expressed by
domain: Information object
range: Social object
property chain axiom: has part
comment: 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.
comment: This is a large comment field for those who want to investigate the different uses of the 'expresses' relation for modeling different approaches to meaning characterization and modeling. For example, in all these cases, some aspect of meaning is involved: - Beehive means "a structure in which bees are kept, typically in the form of a dome or box." (Oxford dictionary) - 'Beehive' is a synonym in noun synset 09218159 "beehive|hive" (WordNet) - 'the term Beehive can be interpreted as the fact of 'being a beehive', i.e. a relation that holds for concepts such as Bee, Honey, Hosting, etc.' - 'the text of Italian apiculture regulation expresses a rule by which beehives should be kept at least one kilometer away from inhabited areas' - 'the term Beehive expresses the concept Beehive' - ''Beehive' for apiculturists does not express the same meaning as for, say, fishermen' - 'Your meaning of 'Beautiful' does not seem to fit mine' - ''Beehive' is formally interpreted as the set of all beehives' - 'from the term 'Beehive', we can build a vector space of statistically significant cooccurring terms in the documents that contain it' - the lexeme 'Belly' expresses the role 'Body_Part' in the frame 'ObservableBodyParts' (FrameNet) As the examples suggest, the 'meaning of meaning' is dependent on the background approach/theory that one assumes. One can hardly make a summary of the too many approaches and theories of meaning, therefore this relation is maybe the most controversial and difficult to explain; normally, in such cases it would be better to give up formalizing. However, the usefulness of having a 'semantic abstraction' in modeling information objects is so high (e.g. for the semantic web, interoperability, reengineering, etc.), that we accept this challenging task, although without taking any particular position in the debate. We provide here some examples, which we want to generalize upon when using the 'expresses' relation to model semantic aspects of social reality. In …
label: esprime @it

expresses concept
type: ObjectProperty
sub property of: expresses
inverse of: is concept expressed by
domain: Information object
range: Concept
comment: 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
label: esprime il concetto @it

far from
type: ObjectProperty
sub property of: associatedWith
type: SymmetricProperty
domain: Entity
range: Entity
comment: Generic distance relation between any Entity(s). E.g. Rome is far from Beijing, astronomy is far from necromancy.

follows
type: ObjectProperty
sub property of: associatedWith
inverse of: precedes
type: TransitiveProperty
domain: Entity
range: Entity
comment: 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.
label: segue @it

has common boundary
type: ObjectProperty
sub property of: associatedWith
type: SymmetricProperty
domain: Entity
range: Entity
comment: 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 component
type: ObjectProperty
sub property of: has proper part
inverse of: is component of
type: AsymmetricProperty
domain: Entity
range: Entity
comment: The hasProperPart relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the Object.
label: ha componente @it

has constituent
type: ObjectProperty
sub property of: associatedWith
inverse of: is constituent of
domain: Entity
range: Entity
comment: '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.
label: ha costituente @it

has constraint
type: ObjectProperty
sub property of: is classified by
inverse of: is constraint for
domain: Entity
range: Parameter
comment: 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.
label: ha vincolo @it

hasInScope
type: ObjectProperty
sub property of: associatedWith
domain: Situation
range: Situation
property chain axiom: is setting for
property chain axiom: is satisfied by
creator: Aldo Gangemi
date: 2024-02-04T11:18:50+00:00

has location
type: ObjectProperty
sub property of: associatedWith
inverse of: is location of
domain: Entity
range: Entity
comment: 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
label: ha localizzazione @it

has member
type: ObjectProperty
sub property of: associatedWith
inverse of: is member of
domain: Collection
range: Entity
comment: 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).
label: ha membro @it

has parameter
type: ObjectProperty
sub property of: is related to concept
inverse of: is parameter for
domain: Concept
range: Parameter
comment: 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.
label: ha parametro @it

has part
type: ObjectProperty
sub property of: associatedWith
inverse of: is part of
type: TransitiveProperty
type: ReflexiveProperty
domain: Entity
range: Entity
property chain axiom:
  inverse of: includesWhole
property chain axiom: includesPart
comment: 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'. Parthood should assume the basic properties of mereology: transitivity, antisymmetry, and reflexivity (propert Parthood of course misses reflexivity). However, antisymmetry is not supported in OWL2 explicitly, therefore DUL has to adopt one of two patterns: 1) dropping asymmetry axioms, while granting reflexivity: this means that symmetry is not enforced, but permitted for the case of reflexivity. Of course, in this way we cannot prevent symmetric usages of hasPart; 2) dropping the reflexivity axiom, and enforce asymmetry: in this case, we would prevent all symmetric usages, but we loose the possibility of enforcing reflexivity, which is commonsensical in parthood. In DUL, we adopt pattern #1 for partOf, and pattern #2 for properPartOf, which seems a good approximation: due to the lack of inheritance of property characteristics, each asymmetric hasPropertPart assertion would also be a reflexive hasPart assertion (reflexive reduction design pattern). Subproperties and restrictions can be used to specialize hasPart for objects, events, etc.
label: ha parte @it

has participant
type: ObjectProperty
sub property of: associatedWith
inverse of: is participant in
domain: Event
range: Object
comment: 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'.
label: ha come partecipante @it

has postcondition
type: ObjectProperty
sub property of: directly precedes
inverse of: is postcondition of
domain: Class
  union of: Event
  union of: Situation
range: Class
  union of: Event
  union of: Situation
comment: Direct succession applied to situations. E.g., 'A postcondition of our Plan is to have things settled'.
label: ha postcondizione @it

has precondition
type: ObjectProperty
sub property of: directly follows
inverse of: is precondition of
domain: Class
  union of: Event
  union of: Situation
range: Class
  union of: Event
  union of: Situation
comment: Direct precedence applied to situations. E.g., 'A precondition to declare war against a foreign country is claiming to find nuclear weapons in it'.
label: ha precondizione @it

has proper part
type: ObjectProperty
sub property of: has part
inverse of: is propert part of
type: TransitiveProperty
comment: Asymmetric (so including irreflexive) parthood.

has quality
type: ObjectProperty
sub property of: associatedWith
inverse of: is quality of
domain: Entity
range: Quality
comment: A relation between entities and qualities, e.g. 'Dmitri's skin is yellowish'.
label: ha qualità @it

has region
type: ObjectProperty
sub property of: associatedWith
inverse of: is region for
domain: Entity
range: Region
comment: 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'.
label: ha attributo @it

has role
type: ObjectProperty
sub property of: is classified by
inverse of: is role of
domain: Object
range: Role
comment: A relation between an object and a role, e.g. the person 'John' has role 'student'.
label: ha ruolo @it

has setting
type: ObjectProperty
sub property of: associatedWith
inverse of: is setting for
domain: Entity
range: Situation
comment: 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.
label: è nel contesto di @it

has task
type: ObjectProperty
sub property of: is related to concept
inverse of: is task of
domain: Role
range: Task
comment: 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').
label: ha come obiettivo @it

has time interval
type: ObjectProperty
sub property of: has region
inverse of: is time interval of
domain: Event
range: Time interval
comment: The generic relation between events and time intervals.
label: ha intervallo temporale @it

includes action
type: ObjectProperty
sub property of: includes event
inverse of: is action included in
domain: Situation
range: Action
comment: 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).
label: include azione @it

includes agent
type: ObjectProperty
sub property of: includes object
inverse of: is agent included in
domain: Situation
range: Agent
comment: 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).
label: include l'agente @it

includes event
type: ObjectProperty
sub property of: is setting for
inverse of: is event included in
domain: Situation
range: Event
comment: 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).
label: include l'evento @it

includes object
type: ObjectProperty
sub property of: is setting for
inverse of: is object included in
domain: Situation
range: Object
comment: 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).
label: include l'oggetto @it

includesPart
type: ObjectProperty
sub property of: is setting for
creator: Aldo Gangemi
date: 2021-04-03T14:11:09+00:00

includes time
type: ObjectProperty
sub property of: is setting for
inverse of: is time included in
domain: Situation
range: Time interval
comment: 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.
label: include tempo @it

includesWhole
type: ObjectProperty
sub property of: is setting for
creator: Aldo Gangemi
date: 2021-04-03T14:11:01+00:00

introduces
type: ObjectProperty
sub property of: associatedWith
inverse of: is introduced by
domain: Description
range: Social agent
comment: A relation between a Description and a SocialAgent, e.g. a Constitutional Charter introduces the SocialAgent 'PresidentOfRepublic'.
label: introduce @it

involves agent
type: ObjectProperty
sub property of: has participant
inverse of: is agent involved in
domain: Event
range: Agent
comment: Agent participation.
label: coinvolge agente @it

is about
type: ObjectProperty
sub property of: associatedWith
inverse of: is reference of
domain: Information object
range: Entity
comment: A relation between an information object and an Entity (including information objects). It can be used to talk about entities that 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: dul:Collection. A specific sentence may use common nouns with either a singular or plural reference, or it can even refer to all possible references (e.g. in a lexicographic definition): all those uses are kinds of aboutness. The isAbout relation is sometimes considered as reflexive, however this is semiotically inaccurate, because information can be about itself ('de dicto' usage, as in 'John is four character long'), but it is typically about something else ('de re' usage, as in 'John loves Mary'). If a reflexivity exists in general, it rather concerns its realisation, which is always associated with an event, e.g. an utterance, which makes the information denoting itself, besides its aboutness. This is implemented in DUL with the dul:realizesSelfInformation property, which is used with local reflexivity in the dul:InformationRealization class.
label: si riferisce a @it

is action included in
type: ObjectProperty
sub property of: is event included in
domain: Action
range: Situation
label: è un'azione nel contesto di @it

is agent included in
type: ObjectProperty
sub property of: is object included in
domain: Agent
range: Situation
label: è un agente nel contesto di @it

is agent involved in
type: ObjectProperty
sub property of: is participant in
domain: Agent
range: Event
comment: Agent participation.
label: è un agente coinvolto in @it

is characterized by {@en-us}
type: ObjectProperty
sub property of: associatedWith
domain: Collection
range: Concept
label: is characterized by
label: è caratterizzato da @it

is classified by
type: ObjectProperty
sub property of: associatedWith
domain: Entity
range: Concept
comment: 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'.
label: è classificato da @it

is component of
type: ObjectProperty
sub property of: is propert part of
type: AsymmetricProperty
domain: Entity
range: Entity
comment: The asymmetric isProperPartOf relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the Object.
label: è componente di @it

is concept expressed by
type: ObjectProperty
sub property of: is expressed by
domain: Concept
range: Information object
comment: 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
label: è un concetto espresso da @it

is concept used in
type: ObjectProperty
sub property of: associatedWith
inverse of: uses concept
domain: Concept
range: Description
comment: A more generic relation holding between a Description and a Concept. In order to be used, a Concept must be previously definedIn another Description
label: è un concetto usato in @it

is conceptualized by
type: ObjectProperty
sub property of: associatedWith
domain: Social object
range: Agent
comment: 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'.
label: è concettualizzato da @it

is concretely expressed by
type: ObjectProperty
sub property of: associatedWith
domain: Social object
range: Information realization
comment: 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
label: è espresso concretamente da @it

is constituent of
type: ObjectProperty
sub property of: associatedWith
domain: Entity
range: Entity
comment: '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.
label: è costituente di @it

is constraint for
type: ObjectProperty
sub property of: classifies
domain: Parameter
range: Entity
comment: 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
label: è un vincolo per @it

is covered by
type: ObjectProperty
sub property of: associatedWith
domain: Collection
range: Concept
comment: 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'.
label: è ricoperto da @it

is defined in
type: ObjectProperty
sub property of: is concept used in
domain: Concept
range: Description
comment: 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'.
label: è definito in @it

is described by
type: ObjectProperty
sub property of: associatedWith
domain: Entity
range: Description
comment: 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.
label: è descritto da @it

is event included in
type: ObjectProperty
sub property of: has setting
domain: Event
range: Situation
label: è un evento nel contesto di @it

is executed in
type: ObjectProperty
sub property of: classifies
domain: Task
range: Action
comment: 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'.
label: è eseguito mediante @it

is expanded in
type: ObjectProperty
sub property of: is related to description
domain: Description
range: Description
comment: 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).
label: è espansa in @it

is expressed by
type: ObjectProperty
sub property of: associatedWith
domain: Social object
range: Information object
comment: 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.
label: è espresso da @it

is introduced by
type: ObjectProperty
sub property of: associatedWith
domain: Social agent
range: Description
comment: A relation between a Description and a SocialAgent, e.g. a Constitutional Charter introduces the SocialAgent 'PresidentOfRepublic'.
label: è introdotto da @it

is location of
type: ObjectProperty
sub property of: associatedWith
domain: Entity
range: Entity
comment: 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
label: è una localizzazione di @it

is member of
type: ObjectProperty
sub property of: associatedWith
domain: Entity
range: Collection
comment: 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'.
label: è membro di @it

is object included in
type: ObjectProperty
sub property of: has setting
domain: Object
range: Situation
label: è un oggetto nel contesto di @it

is observable at
type: ObjectProperty
sub property of: has region
inverse of: is time of observation of
domain: Entity
range: Time interval
comment: 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
label: è osservabile a @it

is parameter for
type: ObjectProperty
sub property of: is related to concept
domain: Parameter
range: Concept
comment: 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.
label: è un parametro per @it

is parametrized by
type: ObjectProperty
sub property of: is classified by
inverse of: parametrizes
domain: Region
range: Parameter
comment: The relation between a Parameter, e.g. 'MajorAge', and a Region, e.g. '>17 year'.
label: è parametrizzato da @it

is part of
type: ObjectProperty
sub property of: associatedWith
type: TransitiveProperty
type: ReflexiveProperty
domain: Entity
range: Entity
comment: A relation between any entities, e.g. 'brain is a part of the human body'. See dul:hasPart for additional documentation.
label: è parte di @it

is participant in
type: ObjectProperty
sub property of: associatedWith
domain: Object
range: Event
comment: 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'.
label: è un partecipante a @it

is postcondition of
type: ObjectProperty
sub property of: directly follows
domain: Class
  union of: Event
  union of: Situation
range: Class
  union of: Event
  union of: Situation
comment: Direct succession applied to situations. E.g., 'Taking some rest is a postcondition of my search for a hotel'.
label: è postcondizione di @it

is precondition of
type: ObjectProperty
sub property of: directly precedes
domain: Class
  union of: Event
  union of: Situation
range: Class
  union of: Event
  union of: Situation
comment: Direct precedence applied to situations. E.g., 'claiming to find nuclear weapons in a foreign country is a precondition to declare war against it'.
label: è precondizione di @it

is propert part of
type: ObjectProperty
sub property of: is part of
type: TransitiveProperty
comment: See dul:hasProperPart for additional documentation.

is quality of
type: ObjectProperty
sub property of: associatedWith
domain: Quality
range: Entity
comment: A relation between entities and qualities, e.g. 'Dmitri's skin is yellowish'.
label: è una qualità di @it

is realized by
type: ObjectProperty
sub property of: associatedWith
inverse of: realizes
domain: Information object
range: Information realization
comment: 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.
label: è realizzato da @it

is reference of
type: ObjectProperty
sub property of: associatedWith
domain: Entity
range: Information object
comment: 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.
label: è il riferimento di @it

is reference of information realized by
type: ObjectProperty
sub property of: associatedWith
inverse of: realizes information about
domain: Entity
range: Information realization
comment: The relation between entities and information realizations, e.g. between Italy and a paper copy of the text of the Italian Constitution.
label: è riferimento dell'informazione realizzata da @it

is region for
type: ObjectProperty
sub property of: associatedWith
domain: Region
range: Entity
comment: A relation between entities and regions, e.g. 'the color of my car is red'.
label: è una regione di @it

is related to concept
type: ObjectProperty
sub property of: associatedWith
type: SymmetricProperty
domain: Concept
range: Concept
comment: Any relation between concepts, e.g. superordinated, conceptual parthood, having a parameter, having a task, superordination, etc.
label: è associato al concetto @it

is related to description
type: ObjectProperty
sub property of: associatedWith
type: SymmetricProperty
domain: Description
range: Description
comment: Any relation between descriptions.
label: è associata alla descrizione @it

is role defined in
type: ObjectProperty
sub property of: is defined in
domain: Role
range: Description
comment: A relation between a description and a role, e.g. the role 'Ingredient' is defined in the recipe for a cake.
label: è un ruolo definito in @it

is role of
type: ObjectProperty
sub property of: classifies
domain: Role
range: Object
comment: A relation between an object and a role, e.g. 'student' is the role of 'John'.
label: è un ruolo di @it

is satisfied by
type: ObjectProperty
sub property of: associatedWith
inverse of: satisfies
domain: Description
range: Situation
comment: A relation between a Situation and a Description, e.g. the execution of a Plan satisfies that plan.
label: è soddisfatta da @it

is setting for
type: ObjectProperty
sub property of: associatedWith
domain: Situation
range: Entity
comment: 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.
label: include @it

is specialized by
type: ObjectProperty
sub property of: associatedWith
inverse of: specializes
type: TransitiveProperty
domain: Social object
range: Social object
comment: 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
label: è specializzato da @it

is subordinated to
type: ObjectProperty
sub property of: directly follows
sub property of: is related to concept
inverse of: is superordinated to
domain: Concept
range: Concept
comment: Direct succession applied to concepts. E.g. the role 'Officer' is subordinated to 'Director'.
label: è subordinato a @it

is superordinated to
type: ObjectProperty
sub property of: directly precedes
sub property of: is related to concept
domain: Concept
range: Concept
comment: Direct precedence applied to concepts. E.g. the role 'Executive' is superordinated to 'DepartmentManager'.
label: è superordinato a @it

is task defined in
type: ObjectProperty
sub property of: is defined in
domain: Task
range: Description
comment: A relation between a description and a task, e.g. the task 'boil' is defined in a recipe for a cake.
label: è un task definito in @it

is task of
type: ObjectProperty
sub property of: is related to concept
domain: Task
range: Role
comment: 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').
label: è un obiettivo per @it

is time included in
type: ObjectProperty
sub property of: has setting
domain: Time interval
range: Situation
label: è un tempo nel contesto di @it

is time interval of
type: ObjectProperty
sub property of: is region for
domain: Time interval
range: Event
comment: The generic relation between time intervals and events.
label: intervallo temporale di @it

is time of observation of
type: ObjectProperty
sub property of: is region for
domain: Time interval
range: Entity
comment: 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
label: è il tempo di osservazione di @it

is unified by
type: ObjectProperty
sub property of: associatedWith
inverse of: unifies
domain: Collection
range: Description
comment: 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.
label: è unificato da @it

near to
type: ObjectProperty
sub property of: associatedWith
type: SymmetricProperty
domain: Entity
range: Entity
comment: Generic distance relation between any Entity(s). E.g. Rome is near to Florence, astronomy is near to physics.

overlaps
type: ObjectProperty
sub property of: associatedWith
type: SymmetricProperty
domain: Entity
range: Entity
comment: 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.
label: sovrapposto a @it

parametrizes
type: ObjectProperty
sub property of: classifies
domain: Parameter
range: Region
comment: The relation between a Parameter, e.g. 'MajorAgeLimit', and a Region, e.g. '18_year'. For a more data-oriented relation, see hasDataValue
label: parametrizza @it

precedes
type: ObjectProperty
sub property of: associatedWith
type: TransitiveProperty
domain: Entity
range: Entity
comment: 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.
label: precede @it

realizes
type: ObjectProperty
sub property of: associatedWith
domain: Information realization
range: Information object
comment: 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.
label: realizza @it

realizes information about
type: ObjectProperty
sub property of: associatedWith
domain: Information realization
range: Entity
property chain axiom: realizes
property chain axiom: is about
comment: The relation between entities and information realizations, e.g. between Italy and a paper copy of the text of the Italian Constitution.
label: realizza informazione che si riferisce a @it

realizesSelfInformation
type: ObjectProperty
sub property of: realizes information about
creator: Aldo Gangemi
date: 2021-04-05T22:31:22+00:00
comment: This relation is a workaround to enable local reflexivity axioms (Self) working with non-simple properties; in this case, dul:realizesInformation About.

is in the same setting as
type: ObjectProperty
sub property of: associatedWith
type: SymmetricProperty
domain: Entity
range: Entity
property chain axiom: has setting
property chain axiom: is setting for
comment: 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). @it
label: è nella stessa situazione di @it

satisfies
type: ObjectProperty
sub property of: associatedWith
domain: Situation
range: Description
comment: A relation between a Situation and a Description, e.g. the execution of a Plan satisfies that plan.
label: soddisfa @it

specializes
type: ObjectProperty
sub property of: associatedWith
type: TransitiveProperty
domain: Social object
range: Social object
comment: 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.
label: specializza @it

unifies
type: ObjectProperty
sub property of: associatedWith
domain: Description
range: Collection
comment: 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.
label: unifica @it

uses concept
type: ObjectProperty
sub property of: associatedWith
domain: Description
range: Concept
comment: 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.
label: usa il concetto @it

default geometry
type: ObjectProperty
equivalent property: has default geometry
sub property of: has geometry
domain: Feature
range: Geometry
definition: The default Geometry to be used in spatial calculations. It is usually the most detailed Geometry.
example: C.1.2.2
example: C.2.1
note: Duplicate properties defaultGeometry and hasDefaultGeometry exist because of an inconsistency between ontology and documentation in GeoSPARQL 1.0. Only hasDefaultGeometry is described in the documention.

contains
type: ObjectProperty
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially contains the object SpatialObject. DE-9IM: T*TFF*FF*

covered by
type: ObjectProperty
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject is spatially covered by the object SpatialObject. DE-9IM: TFF*TFT**

covers
type: ObjectProperty
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially covers the object SpatialObject. DE-9IM: T*TFT*FF*

disjoint
type: ObjectProperty
equivalent property: disconnected
equivalent property: disjoint
domain: SpatialObject
range: SpatialObject
property disjoint with: intersects
definition: States that the subject SpatialObject is spatially disjoint from the object SpatialObject. DE-9IM: FF*FF****

equals
type: ObjectProperty
equivalent property: equals
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially equals the object SpatialObject. DE-9IM: TFFFTFFFT

inside
type: ObjectProperty
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject is spatially inside the object SpatialObject. DE-9IM: TFF*FFT**

meet
type: ObjectProperty
equivalent property: externally connected
equivalent property: touches
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially meets the object SpatialObject. DE-9IM: FT******* ^ F**T***** ^ F***T****

overlap
type: ObjectProperty
equivalent property: partially overlapping
equivalent property: overlaps
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially overlaps the object SpatialObject. DE-9IM: T*T***T**

has area
type: ObjectProperty
sub property of: has size
domain: SpatialObject
definition: The area of a Spatial Object.
example: C.1.1.2.4
example: C.1.2.2

has bounding box
type: ObjectProperty
sub property of: has geometry
domain: Feature
range: Geometry
definition: The minimum or smallest bounding or enclosing box of a given Feature.
example: C.1.2.2
scope note: The target is a Geometry that defines a rectilinear region whose edges are aligned with the axes of the coordinate reference system, which exactly contains the Feature, for example an instance of http://www.opengis.net/ont/sf#envelope.

has centroid
type: ObjectProperty
sub property of: has geometry
domain: Feature
range: Geometry
definition: The arithmetic mean position of all the Geometry points of a given Feature.
example: C.1.2.2
scope note: The target Geometry shall describe a point, for example an instance of http://www.opengis.net/ont/sf#Point.

has default geometry
type: ObjectProperty
sub property of: has geometry
domain: Feature
range: Geometry
definition: The default Geometry to be used in spatial calculations. It is usually the most detailed Geometry.
note: Duplicate properties defaultGeometry and hasDefaultGeometry exist because of an inconsistency between ontology and documentation in GeoSPARQL 1.0. Only hasDefaultGeometry is described in the documention.

has geometry
type: ObjectProperty
domain: Feature
range: Geometry
definition: A spatial representation for a given Feature.
example: C.1.1.2.2
example: C.1.1.2.3
example: C.1.1.2.4
example: C.1.1.2.5
example: C.1.1.2.6
example: C.1.1.2.8
example: C.1.1.3.2
example: C.1.1.3.3
example: C.1.2.2
example: C.1.2.3
example: C.1.2.4
example: C.2

has length
type: ObjectProperty
sub property of: has size
domain: SpatialObject
definition: The length of a Spatial Object.
example: C.1.1.2.7
example: C.1.2.2

has perimeter length
type: ObjectProperty
sub property of: has size
domain: SpatialObject
definition: The length of the perimeter of a Spatial Object.
example: C.1.1.1.2

has size
type: ObjectProperty
domain: SpatialObject
definition: Subproperties of this property are used to indicate the size of a Spatial Object as a measurement or estimate of one or more dimensions of the Spatial Object's spatial presence.
note: The recommended way to specify size is by using a subproperty of hasMetricSize. Subproperties of hasSize can be used if more complex expressions are necessary, for example if the unit of length can not be converted to meter, or if additional data are needed to describe the measurement or estimate.

has spatial accuracy
type: ObjectProperty
domain: Geometry
definition: The positional accuracy of the coordinates of a Geometry.
example: C.1.2.3
note: Spatial accuracy is applicable when a Geometry is used to represent a Feature. It is expressed as a distance that indicates the truthfullness of the positions (coordinates) that define the Geometry. In this case accuracy defines a zone surrounding each coordinate within wich the real positions are known to be. The accuracy value defines this zone as a distance from the coordinate(s) in all directions (e.g. a line, a circle or a sphere, depending on spatial dimension).

has spatial resolution
type: ObjectProperty
domain: Geometry
definition: The spatial resolution of a Geometry.
example: C.1.2.2
note: Spatial resolution specifies the level of detail of a Geometry. It the smallest distinguishable distance between spatially adjacent coordinates.

has volume
type: ObjectProperty
sub property of: has size
domain: SpatialObject
definition: The volume of a three-dimensional Spatial Object.
example: C.1.2.2

disconnected
type: ObjectProperty
equivalent property: disjoint
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject is spatially disjoint from the object SpatialObject. DE-9IM: FFTFFTTTT

externally connected
type: ObjectProperty
equivalent property: touches
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially meets the object SpatialObject. DE-9IM: FFTFTTTTT

equals
type: ObjectProperty
equivalent property: equals
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially equals the object SpatialObject. DE-9IM: TFFFTFFFT

non-tangential proper part
type: ObjectProperty
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject is spatially inside the object SpatialObject. DE-9IM: TFFTFFTTT

non-tangential proper part inverse
type: ObjectProperty
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially contains the object SpatialObject. DE-9IM: TTTFFTFFT

partially overlapping
type: ObjectProperty
equivalent property: overlaps
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially overlaps the object SpatialObject. DE-9IM: TTTTTTTTT

tangential proper part
type: ObjectProperty
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject is spatially covered by the object SpatialObject. DE-9IM: TFFTTFTTT

tangential proper part inverse
type: ObjectProperty
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially covers the object SpatialObject. DE-9IM: TTTFTTFFT

contains
type: ObjectProperty
sub property of: has spatial relation
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially contains the object SpatialObject. DE-9IM: T*****FF*

crosses
type: ObjectProperty
sub property of: has spatial relation
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially crosses the object SpatialObject. DE-9IM: T*T******

disjoint
type: ObjectProperty
sub property of: has spatial relation
domain: SpatialObject
range: SpatialObject
property disjoint with: intersects
definition: States that the subject SpatialObject is spatially disjoint from the object SpatialObject. DE-9IM: FF*FF****

equals
type: ObjectProperty
sub property of: has spatial relation
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially equals the object SpatialObject. DE-9IM: TFFFTFFFT

intersects
type: ObjectProperty
sub property of: has spatial relation
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject is not spatially disjoint from the object SpatialObject. DE-9IM: T******** ^ *T******* ^ ***T***** ^ ****T****

overlaps
type: ObjectProperty
sub property of: has spatial relation
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially overlaps the object SpatialObject. DE-9IM: T*T***T**

touches
type: ObjectProperty
sub property of: has spatial relation
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject spatially touches the object SpatialObject. DE-9IM: FT******* ^ F**T***** ^ F***T****

within
type: ObjectProperty
sub property of: has spatial relation
domain: SpatialObject
range: SpatialObject
definition: States that the subject SpatialObject is spatially within the object SpatialObject. DE-9IM: T*F**F***

after
type: ObjectProperty
inverse of: before
domain: Temporal entity
range: Temporal entity
comment: Asume una dirección en el tiempo. Si una entidad temporal T1 está después de otra entidad temporal T2, entonces el principio de T1 está después del final de T2. @es
comment: Gives directionality to time. If a temporal entity T1 is after another temporal entity T2, then the beginning of T1 is after the end of T2.
label: después @es

before
type: ObjectProperty
type: TransitiveProperty
domain: Temporal entity
range: Temporal entity
comment: Asume una dirección en el tiempo. Si una entidad temporal T1 está antes que otra entidad temporal T2, entonces el final de T1 está antes que el principio de T2. Así, "antes" se puede considerar básica para instantes y derivada para intervalos. @es
comment: Gives directionality to time. If a temporal entity T1 is before another temporal entity T2, then the end of T1 is before the beginning of T2. Thus, "before" can be considered to be basic to instants and derived for intervals.
label: antes @es

day of week
type: ObjectProperty
domain: Generalized date-time description
range: Day of week
comment: El día de la semana, cuyo valor es un miembro de la clase 'día de la semana'.
comment: The day of week, whose value is a member of the class time:DayOfWeek
label: día de la semana @es

has beginning
type: ObjectProperty
sub property of: has time
domain: Temporal entity
range: Time instant
comment: Beginning of a temporal entity
comment: Comienzo de una entidad temporal. @es
label: tiene principio @es
definition: Beginning of a temporal entity.

has Date-Time description
type: ObjectProperty
domain: Date-time interval
range: Generalized date-time description
comment: Valor de intervalo de fecha-hora expresado como un valor estructurado. El principio y el final del intervalo coincide con los límites del elemento más corto en la descripción. @es
comment: Value of DateTimeInterval expressed as a structured value. The beginning and end of the interval coincide with the limits of the shortest element in the description.
label: tiene descripción fecha-hora @es

has duration
type: ObjectProperty
sub property of: has temporal duration
range: duración de tiempo
comment: Duración de una entidad temporal, expresada como un valor escalado o un valor nominal. @es
comment: Duration of a temporal entity, expressed as a scaled value or nominal value
label: tiene duración @es
definition: Duración de una entidad temporal, evento o actividad, o cosa, expresada como un valor escalado. @es
definition: Duration of a temporal entity, event or activity, or thing, expressed as a scaled value

has duration description
type: ObjectProperty
sub property of: has temporal duration
range: Generalized duration description
comment: Duración de una entidad temporal, expresada utilizando una descripción estructurada. @es
comment: Duration of a temporal entity, expressed using a structured description
label: tiene descripción de duración @es

has end
type: ObjectProperty
sub property of: has time
domain: Temporal entity
range: Time instant
comment: End of a temporal entity.
comment: Final de una entidad temporal. @es
label: tiene fin @es

Temporal reference system used
type: ObjectProperty
type: FunctionalProperty
domain: Class
  union of: Generalized duration description
  union of: Temporal position
range: Temporal Reference System
comment: El sistema de referencia temporal utilizado por una posición temporal o descripción de extensión. @es
comment: The temporal reference system used by a temporal position or extent description.
label: sistema de referencia temporal utilizado @es

has temporal duration
type: ObjectProperty
domain: Temporal entity
range: Temporal duration
comment: Duración de una entidad temporal. @es
comment: Duration of a temporal entity.
label: tiene duración temporal @es

has time
type: ObjectProperty
range: Temporal entity
comment: Proporciona soporte a la asociación de una entidad temporal (instante o intervalo) a cualquier cosa. @es
comment: Supports the association of a temporal entity (instant or interval) to any thing
label: tiene tiempo @es
editorial note: Característica arriesgada -añadida en la revisión del 2017 que no ha sido todavía utilizada de forma amplia. @es
editorial note: Feature at risk - added in 2017 revision, and not yet widely used.

in date-time description
type: ObjectProperty
sub property of: Temporal position
domain: Time instant
range: Generalized date-time description
comment: Posición de un instante, expresada utilizando una descripción estructurada. @es
comment: Position of an instant, expressed using a structured description
label: en descripción de fecha-hora @es

Temporal position
type: ObjectProperty
domain: Time instant
range: Temporal position
comment: Posición de un instante de tiempo. @es
comment: Position of a time instant
label: posición temporal @es

Time position
type: ObjectProperty
sub property of: Temporal position
domain: Time instant
range: Time position
comment: Posición de un instante, expresada como una coordenada temporal o un valor nominal. @es
comment: Position of an instant, expressed as a temporal coordinate or nominal value
label: posición de tiempo @es
definition: Position of a time instant expressed as a TimePosition

has time instant inside
type: ObjectProperty
domain: Time interval
range: Time instant
comment: An instant that falls inside the interval. It is not intended to include beginnings and ends of intervals.
comment: Un instante que cae dentro del intervalo. Se asume que no es ni el principio ni el final de ningún intervalo. @es
label: tiene instante de tiempo dentro @es

interval after
type: ObjectProperty
sub property of: after
sub property of: interval disjoint
inverse of: interval before
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalAfter another proper interval T2, then the beginning of T1 is after the end of T2.
comment: Si un intervalo propio T1 es posterior a otro intervalo propio T2, entonces el principio de T1 está después que el final de T2.
label: intervalo posterior @es

interval before
type: ObjectProperty
sub property of: before
sub property of: interval disjoint
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalBefore another proper interval T2, then the end of T1 is before the beginning of T2.
comment: Si un intervalo propio T1 está antes que otro intervalo propio T2, entonces el final de T1 está antes que el principio de T2. @es
label: intervalo anterior @es

interval contains
type: ObjectProperty
inverse of: interval during
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalContains another proper interval T2, then the beginning of T1 is before the beginning of T2, and the end of T1 is after the end of T2.
comment: Si un intervalo propio T1 contiene otro intervalo propio T2, entonces el principio de T1 está antes que el principio de T2, y el final de T1 está después del final de T2. @es
label: intervalo contiene @es

interval disjoint
type: ObjectProperty
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalDisjoint another proper interval T2, then the beginning of T1 is after the end of T2, or the end of T1 is before the beginning of T2, i.e. the intervals do not overlap in any way, but their ordering relationship is not known.
comment: Si un intervalo propio T1 es disjunto con otro intervalo propio T2, entonces el principio de T1 está después del final de T2, o el final de T1 está antes que el principio de T2, es decir, los intervalos no se solapan de ninguna forma, aunque su relación de orden no se conozca. @es
label: intervalo disjunto @es
note: Esta relación entre intervalos no estaba incluida en las 13 relaciones básicas definidas por Allen (1984), pero está definida en T.3 como la unión de 'intervalo anterior' con 'intervalo posterior'. Sin embargo, esto está fuera de la expresividad de OWL2, por tanto, está implementado como una propiedad explícita, con 'intervalo anterior' e 'intervalo posterior' como sub-propiedades. @es
note: This interval relation is not included in the 13 basic relationships defined in Allen (1984), but is defined in (T.3) as the union of :intervalBefore v :intervalAfter . However, that is outside OWL2 expressivity, so is implemented as an explicit property, with :intervalBefore , :intervalAfter as sub-properties

interval during
type: ObjectProperty
sub property of: interval in
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalDuring another proper interval T2, then the beginning of T1 is after the beginning of T2, and the end of T1 is before the end of T2.
comment: Si un intervalo propio T1 está durante otro intervalo propio T2, entonces del principio de T1 está después del principio de T2, y el final de T1 está antes que el final de T2. @es
label: intervalo durante @es

interval equals
type: ObjectProperty
domain: Proper interval
range: Proper interval
property disjoint with: interval in
comment: If a proper interval T1 is intervalEquals another proper interval T2, then the beginning of T1 is coincident with the beginning of T2, and the end of T1 is coincident with the end of T2.
comment: Si un intervalo propio T1 es igual a otro intervalo propio T2, entonces el principio de T1 coincide con el principio de T2, y el final de T1 coincide con el final de T2. @es
label: intervalo igual @es

interval finished by
type: ObjectProperty
inverse of: interval finishes
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalFinishedBy another proper interval T2, then the beginning of T1 is before the beginning of T2, and the end of T1 is coincident with the end of T2.
comment: Si un intervalo propio T1 está terminado por otro intervalo propio T2, entonces el principio de T1 está antes que el principio de T2, y el final de T1 coincide con el final de T2. @es
label: intervalo terminado por @es

interval finishes
type: ObjectProperty
sub property of: interval in
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalFinishes another proper interval T2, then the beginning of T1 is after the beginning of T2, and the end of T1 is coincident with the end of T2.
comment: Si un intervalo propio T1 termina otro intervalo propio T2, entonces del principio de T1 está después del principio de T2, y el final de T1 coincide con el final de T2. @es
label: intervalo termina @es

interval in
type: ObjectProperty
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalIn another proper interval T2, then the beginning of T1 is after the beginning of T2 or is coincident with the beginning of T2, and the end of T1 is before the end of T2, or is coincident with the end of T2, except that end of T1 may not be coincident with the end of T2 if the beginning of T1 is coincident with the beginning of T2.
comment: Si un intervalo propio T1 es un intervalo interior a otro intervalo propio T2, entonces el principio de T1 está después del principio de T2 o coincide con el principio de T2, y el final de T1 está antes que el final de T2, o coincide con el final de T2, excepto que el final de T1 puede no coincidir con el final de T2 si el principio de T1 coincide con el principio de T2. @es
label: intervalo interior @es
note: Esta relación entre intervalos no estaba incluida en las 13 relaciones básicas definidas por Allen (1984), pero se hace referencia a ella como "una relación importante" en Allen y Ferguson (1997). Es la unión disjunta de 'intervalo empieza', 'intervalo durante' y con 'intervalo termina'. Sin embargo, esto está fuera de la expresividad de OWL2, por tanto, se implementa como una propiedad explícita, con 'intervalo empieza', 'intervalo durante' e 'intervalo termina' como sub-propiedades. @es
note: This interval relation is not included in the 13 basic relationships defined in Allen (1984), but is referred to as 'an important relationship' in Allen and Ferguson (1997). It is the disjoint union of :intervalStarts v :intervalDuring v :intervalFinishes . However, that is outside OWL2 expressivity, so is implemented as an explicit property, with :intervalStarts , :intervalDuring , :intervalFinishes as sub-properties

interval meets
type: ObjectProperty
inverse of: interval met by
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalMeets another proper interval T2, then the end of T1 is coincident with the beginning of T2.
comment: Si un intervalo propio T1 se encuentra con otro intervalo propio T2, entonces el final de T1 coincide con el principio de T2. @es
label: intervalo se encuentra @es

interval met by
type: ObjectProperty
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalMetBy another proper interval T2, then the beginning of T1 is coincident with the end of T2.
comment: Si un intervalo propio T1 es 'intervalo encontrado por' otro intervalo propio T2, entonces el principio de T1 coincide con el final de T2. @es
label: intervalo encontrado por @es

interval overlapped by
type: ObjectProperty
inverse of: interval overlaps
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalOverlappedBy another proper interval T2, then the beginning of T1 is after the beginning of T2, the beginning of T1 is before the end of T2, and the end of T1 is after the end of T2.
comment: Si un intervalo propio T1 es 'intervalo solapado por' otro intervalo propio T2, entonces el principio de T1 es posterior al principio de T2, y el principio de T1 es anterior al final de T2, y el final de T1 es posterior al final de T2. @es
label: intervalo solapado por @es

interval overlaps
type: ObjectProperty
domain: Proper interval
range: Proper interval
comment: Asume una dirección en el tiempo. Si una entidad temporal T1 está después de otra entidad temporal T2, entonces el principio de T1 está después del final de T2. @es
comment: If a proper interval T1 is intervalOverlaps another proper interval T2, then the beginning of T1 is before the beginning of T2, the end of T1 is after the beginning of T2, and the end of T1 is before the end of T2.
comment: Si un intervalo propio T1 se solapa con otro intervalo propio T2, entonces el principio de T1 es anterior al principio de T2, el final de T1 es posterior al principio de T2, y el final de T1 es anterior al final de T2. @es
label: intervalo se solapa @es

interval started by
type: ObjectProperty
inverse of: interval starts
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalStarted another proper interval T2, then the beginning of T1 is coincident with the beginning of T2, and the end of T1 is after the end of T2.
comment: Si un intervalo propio T1 es empezado por otro intervalo propio T2, entonces el principio de T1 coincide con el principio de T2, y el final de T1 es posterior al final de T2. @es

interval starts
type: ObjectProperty
sub property of: interval in
domain: Proper interval
range: Proper interval
comment: If a proper interval T1 is intervalStarts another proper interval T2, then the beginning of T1 is coincident with the beginning of T2, and the end of T1 is before the end of T2.
comment: Si un intervalo propio T1 empieza otro intervalo propio T2, entonces del principio de T1 con el principio de T2, y el final de T1 es anterior al final de T2. @es
label: intervalo empieza @es
definition: Si un intervalo propio T1 empieza otro intervalo propio T2, entonces del principio de T1 con el final de T2, y el final de T1 es anterior al final de T2. @es

month of year
type: ObjectProperty
domain: Generalized date-time description
range: Month of year
comment: El mes del año, cuyo valor es un miembro de la clase 'mes del año'. @es
comment: The month of the year, whose value is a member of the class time:MonthOfYear
label: mes del año @es
editorial note: Característica arriesgada - añadida en la revisión de 2017, y todavía no ampliamente utilizada. @es
editorial note: Feature at risk - added in 2017 revision, and not yet widely used.

in time zone
type: ObjectProperty
domain: Generalized date-time description
range: Time Zone
comment: The time zone for clock elements in the temporal position
label: en huso horario @es
history note: En la versión original de OWL-Time de 2006, el rango de 'en huso horario' se definió en un espacio de nombres diferente "http://www.w3.org/2006/timezone#". Un axioma de alineación permite que los datos codificados de acuerdo con la versión anterior sean consistentes con la ontología actualizada. @es
history note: In the original 2006 version of OWL-Time, the range of time:timeZone was a TimeZone class in a separate namespace "http://www.w3.org/2006/timezone#". An alignment axiom tzont:TimeZone rdfs:subClassOf time:TimeZone . allows data encoded according to the previous version to be consistent with the updated ontology.
note: IANA maintains a database of timezones. These are well maintained and generally considered authoritative, but individual items are not available at individual URIs, so cannot be used directly in data expressed using OWL-Time. DBPedia provides a set of resources corresponding to the IANA timezones, with a URI for each (e.g. http://dbpedia.org/resource/Australia/Eucla). The World Clock service also provides a list of time zones with the description of each available as an individual webpage with a convenient individual URI (e.g. https://www.timeanddate.com/time/zones/acwst). These or other, similar, resources might be used as a value of the time:timeZone property.
note: IANA mantiene una base de datos de husos horarios. Éstas están bien mantenidas y generalmente se consideran autorizadas, pero los ítems individuales no están disponibles en URIs individuales, por tanto, no se pueden utilizar directamente en datos expresados utilizando OWL-Time. La BDPedia proporciona un conjunto de recursos correspondientes a los husos horarios de IANA, con una URI para cada uno (por ejemplo, http://dbpedia.org/resource/Australia/Eucla). El Servicio de Reloj Mundial también proporciona una lista de husos horarios con la descripción de cada uno de los disponibles como una página Web individual con una URI adecuada individual (por ejemplo, https://www.timeanddate.com/time/zones/acwst). Éstos, y otros recursos similares, se puden usar como un valor de la propiedad 'huso horario'. @es

temporal unit type
type: ObjectProperty
domain: Class
  union of: duración de tiempo
  union of: Generalized date-time description
range: Temporal unit
comment: La unidad de tiempo que proporciona la precisión de un valor fecha-hora o la escala de una extensión temporal. @es
comment: The temporal unit which provides the precision of a date-time value or scale of a temporal extent
label: tipo de unidad temporal @es

acts on property
type: ObjectProperty
inverse of: is acted on by
domain includes: Actuation
range includes: Actuatable Property
comment: Relation between an Actuation and the property of a FeatureOfInterest it is acting upon.
example: In the activity (Actuation) of automatically closing a window if the temperature in a room drops below 20 degrees Celsius, the property on which the Actuator acts upon is the state of the window as it changes from being open to being closed.

has feature of interest
type: ObjectProperty
inverse of: is feature of interest of
domain includes: Actuation
domain includes: Observation
domain includes: Sampling
range includes: Feature Of Interest
range includes: Sample
comment: A relation between an Observation and the entity whose quality was observed, or between an Actuation and the entity whose property was modified, or between an act of Sampling and the entity that was sampled.
example: For example, in an Observation of the weight of a person, the FeatureOfInterest is the person and the property is its weight.

has result
type: ObjectProperty
inverse of: is result of
domain includes: Actuation
domain includes: Observation
domain includes: Sampling
range includes: Result
range includes: Sample
comment: Relation linking an Observation or Actuation or act of Sampling and a Result or Sample.

has sample
type: ObjectProperty
inverse of: is sample of
type: InverseFunctionalProperty
domain includes: Feature Of Interest
range includes: Sample
comment: Relation between a FeatureOfInterest and the Sample used to represent it.

hosts
type: ObjectProperty
inverse of: is hosted by
property chain axiom: in deployment
property chain axiom: deployed system
domain includes: Platform
range includes: Actuator
range includes: Platform
range includes: Sampler
range includes: Sensor
comment: Relation between a Platform and a Sensor, Actuator, Sampler, or Platform, hosted or mounted on it.

is acted on by
type: ObjectProperty
domain includes: Actuatable Property
range includes: Actuation
comment: Relation between an ActuatableProperty of a FeatureOfInterest and an Actuation changing its state.
example: In the activity (Actuation) of automatically closing a window if the temperature in a room drops below 20 degrees Celsius, the property on which the Actuator acts upon is the state of the window as it changes from being open to being closed.

is feature of interest of
type: ObjectProperty
domain includes: Feature Of Interest
domain includes: Sample
range includes: Actuation
range includes: Observation
range includes: Sampling
comment: A relation between a FeatureOfInterest and an Observation about it, an Actuation acting on it, or an act of Sampling that sampled it.

is hosted by
type: ObjectProperty
domain includes: Actuator
domain includes: Platform
domain includes: Sampler
domain includes: Sensor
range includes: Platform
comment: Relation between a Sensor, Actuator, Sampler, or Platform, and the Platform that it is mounted on or hosted by.

is observed by
type: ObjectProperty
inverse of: observes
domain includes: Observable Property
range includes: Sensor
comment: Relation between an ObservableProperty and the Sensor able to observe it.

is result of
type: ObjectProperty
domain includes: Result
domain includes: Sample
range includes: Actuation
range includes: Observation
range includes: Sampling
comment: Relation linking a Result to the Observation or Actuation or act of Sampling that created or caused it.

is sample of
type: ObjectProperty
type: FunctionalProperty
domain includes: Sample
range includes: Feature Of Interest
comment: Relation from a Sample to the FeatureOfInterest that it is intended to be representative of.

made actuation
type: ObjectProperty
inverse of: made by actuator
domain includes: Actuator
range includes: Actuation
comment: Relation between an Actuator and the Actuation it has made.

made by actuator
type: ObjectProperty
domain includes: Actuation
range includes: Actuator
comment: Relation linking an Actuation to the Actuator that made that Actuation.

made by sampler
type: ObjectProperty
inverse of: made sampling
domain includes: Sampling
range includes: Sampler
comment: Relation linking an act of Sampling to the Sampler (sampling device or entity) that made it.

made by sensor
type: ObjectProperty
inverse of: made observation
domain includes: Observation
range includes: Sensor
comment: Relation between an Observation and the Sensor which made the Observation.

made observation
type: ObjectProperty
domain includes: Sensor
range includes: Observation
comment: Relation between a Sensor and an Observation made by the Sensor.

made sampling
type: ObjectProperty
domain includes: Sampler
range includes: Sampling
comment: Relation between a Sampler (sampling device or entity) and the Sampling act it performed.

observed property
type: ObjectProperty
domain includes: Observation
range includes: Observable Property
comment: Relation linking an Observation to the property that was observed. The ObservableProperty should be a property of the FeatureOfInterest (linked by hasFeatureOfInterest) of this Observation.

observes
type: ObjectProperty
sub property of: for property
domain includes: Sensor
range includes: Observable Property
comment: Relation between a Sensor and an ObservableProperty that it is capable of sensing.

phenomenon time
type: ObjectProperty
domain includes: Actuation
domain includes: Observation
domain includes: Sampling
range includes: Temporal entity
comment: The time that the Result of an Observation, Actuation or Sampling applies to the FeatureOfInterest. Not necessarily the same as the resultTime. May be an Interval or an Instant, or some other compound TemporalEntity.

used procedure
type: ObjectProperty
property chain axiom: made by actuator
property chain axiom: implements
property chain axiom: made by sampler
property chain axiom: made by sensor
domain includes: Actuation
domain includes: Observation
domain includes: Sampling
range includes: Procedure
comment: A relation to link to a re-usable Procedure used in making an Observation, an Actuation, or a Sample, typically through a Sensor, Actuator or Sampler.

deployed on platform
type: ObjectProperty
inverse of: in deployment
comment: Relation between a Deployment and the Platform on which the Systems are deployed.

deployed system
type: ObjectProperty
inverse of: has deployment
comment: Relation between a Deployment and a deployed System.

detects
type: ObjectProperty
comment: A relation from a Sensor to the Stimulus that the Sensor detects. The Stimulus itself will be serving as a proxy for some ObservableProperty.

for property
type: ObjectProperty
comment: A relation between some aspect of an entity and a Property.
example: For example, from a Sensor to the properties it can observe; from an Actuator to the properties it can act on; from a Deployment to the properties it was installed to observe or act on; from a SystemCapability to the Property the capability is described for.

has deployment
type: ObjectProperty
comment: Relation between a System and a Deployment, recording that the System is deployed in that Deployment.

has input
type: ObjectProperty
comment: Relation between a Procedure and an Input to it.

has output
type: ObjectProperty
comment: Relation between a Procedure and an Output of it.

has property
type: ObjectProperty
inverse of: is property of
comment: Relation between an entity and a Property of that entity.

has subsystem
type: ObjectProperty
comment: Relation between a System and its component parts.

implemented by
type: ObjectProperty
inverse of: implements
comment: Relation between a Procedure (an algorithm, procedure or method) and an entity that implements that Procedure in some executable way.
example: For example, the relationship between a scientific measuring Procedure and a sensor that senses via that Procedure.

implements
type: ObjectProperty
comment: Relation between an entity that implements a Procedure in some executable way and the Procedure (an algorithm, procedure or method).
example: For example, the relationship between a sensor and the scientific measuring Procedure via which it senses.

in deployment
type: ObjectProperty
comment: Relation between a Platform and a Deployment, meaning that the deployedSystems of the Deployment are hosted on the Platform.
example: For example, a relation between a buoy and a deployment of several Sensors.

is property of
type: ObjectProperty
comment: Relation between a Property and the entity it belongs to.

is proxy for
type: ObjectProperty
comment: A relation from a Stimulus to the Property that the Stimulus is serving as a proxy for.
example: For example, the expansion of quicksilver is a stimulus that serves as a proxy for some temperature property. An increase or decrease in the velocity of spinning cups on a wind sensor is serving as a proxy for the wind speed.

was originated by
type: ObjectProperty
type: FunctionalProperty
comment: Relation between an Observation and the Stimulus that originated it.

has descriptive spatial relation
type: ObjectProperty
sub property of: has spatial relation
comment: This object property, as an spacialization of the object property hasSpatialRelation, generalizes spatial relations defined in the Open Time and Space Core Vocabulary, which are more declarative than those defined in GeoSPARQL.

has spatial relation
type: ObjectProperty
domain: spatial object
range: spatial object
comment: Describes any possible spatial relations between any two given spatial objects. This object properties is used to generalize all the spatial relations defined in GeoSPARQL ontology.

has data value
type: DatatypeProperty
domain: Entity
comment: A datatype property that encodes values from a datatype for an Entity. There are several ways to encode values in DOLCE (Ultralite): 1) Directly assert an xsd:_ value to an Entity by using hasDataValue 2) Assert a Region for an Entity by using hasRegion, and then assert an xsd:_ value to that Region, by using hasRegionDataValue 3) Assert a Quality for an Entity by using hasQuality, then assert a Region for that Quality, and assert an xsd:_ value to that Region, by using hasRegionDataValue 4) When the value is required, but not directly observed, assert a Parameter for an xsd:_ value by using hasParameterDataValue, and then associate the Parameter to an Entity by using isConstraintFor 5) When the value is required, but not directly observed, you can also assert a Parameter for a Region by using parametrizes, and then assert an xsd:_ value to that Region, by using hasRegionDataValue The five approaches obey different requirements. For example, a simple value can be easily asserted by using pattern (1), but if one needs to assert an interval between two values, a Region should be introduced to materialize that interval, as pattern (2) suggests. Furthermore, if one needs to distinguish the individual Quality of a value, e.g. the particular nature of the density of a substance, pattern (3) can be used. Patterns (4) and (5) should be used instead when a constraint or a selection is modeled, independently from the actual observation of values in the real world.
label: ha valore @it

has event date
type: DatatypeProperty
sub property of: has data value
domain: Event
range: dateTime
comment: A datatype property that encodes values from xsd:dateTime for an Event; a same Event can have more than one xsd:dateTime value: begin date, end date, date at which the interval holds, etc.
label: evento ha data @it

has interval date
type: DatatypeProperty
sub property of: has region data value
domain: Time interval
range: dateTime
comment: A datatype property that encodes values from xsd:dateTime for a TimeInterval; a same TimeInterval can have more than one xsd:dateTime value: begin date, end date, date at which the interval holds, etc.
label: intervallo ha data @it

has parameter data value
type: DatatypeProperty
sub property of: has data value
domain: Parameter
comment: 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'.
label: ha valore @it

has region data value
type: DatatypeProperty
sub property of: has data value
domain: Region
comment: A datatype property that encodes values for a Region, e.g. a float for the Region Height.
label: regione ha valore @it

as DGGS
type: DatatypeProperty
sub property of: has serialization
domain: Geometry
range: DGGS Literal
definition: The Discrete Global Grid System (DGGS) serialization of a Geometry
example: C.1.2.4

as GML
type: DatatypeProperty
sub property of: has serialization
domain: Geometry
range: GML Literal
definition: The GML serialization of a Geometry
example: C.1.2.4

as GeoJSON
type: DatatypeProperty
sub property of: has serialization
domain: Geometry
range: GeoJSON Literal
definition: The GeoJSON serialization of a Geometry
example: C.1.2.4

as KML
type: DatatypeProperty
sub property of: has serialization
domain: Geometry
range: KML Literal
definition: The KML serialization of a Geometry
example: C.1.2.4

as WKT
type: DatatypeProperty
sub property of: has serialization
domain: Geometry
range: Well-known Text Literal
definition: The WKT serialization of a Geometry
example: C.1.1.2.2
example: C.1.1.2.3
example: C.1.1.2.4
example: C.1.1.2.5
example: C.1.1.2.6
example: C.1.1.2.8
example: C.1.1.3.1
example: C.1.1.3.2
example: C.1.1.3.3
example: C.1.2.2
example: C.2.1
example: C.2.2.4

coordinate dimension
type: DatatypeProperty
domain: Geometry
range: integer
definition: The number of measurements or axes needed to describe the position of this Geometry in a coordinate system.
example: C.1.2.3

dimension
type: DatatypeProperty
domain: Geometry
range: integer
definition: The topological dimension of this geometric object, which must be less than or equal to the coordinate dimension. In non-homogeneous collections, this will return the largest topological dimension of the contained objects.
example: C.1.2.3

has area in square meters
type: DatatypeProperty
sub property of: has metric size
domain: SpatialObject
range: double
definition: The area of a Spatial Object in square meters.
example: C.1.1.2.3
example: C.1.1.2.9
example: C.1.1.3.3
example: C.1.2.2

has length in meters
type: DatatypeProperty
sub property of: has metric size
domain: SpatialObject
range: double
definition: The length of a Spatial Object in meters.
example: C.1.2.2

has perimeter length in meters
type: DatatypeProperty
sub property of: has metric size
domain: SpatialObject
range: double
definition: The length of the perimeter of a Spatial Object in meters.
example: C.1.1.1.2

has metric size
type: DatatypeProperty
domain: SpatialObject
range: double
definition: Subproperties of this property are used to indicate the size of a Spatial Object, as a measurement or estimate of one or more dimensions of the Spatial Object's spatial presence. Units are always metric (meter, square meter or cubic meter).

has spatial accuracy in meters
type: DatatypeProperty
domain: Geometry
range: double
definition: The positional accuracy of the coordinates of a Geometry in meters.
example: C.1.2.3
note: Spatial accuracy is applicable when a Geometry is used to represent a Feature. It is expressed as a distance that indicates the truthfullness of the positions (coordinates) that define the Geometry. In this case accuracy defines a zone surrounding each coordinate within wich the real positions are known to be. The accuracy value defines this zone as a distance from the coordinate(s) in all directions (e.g. a line, a circle or a sphere, depending on spatial dimension).

has spatial resolution in meters
type: DatatypeProperty
domain: Geometry
range: double
definition: The spatial resolution of a Geometry in meters.
example: C.1.1.2.6
example: C.1.2.2
note: Spatial resolution specifies the level of detail of a Geometry. It the smallest dinstinguishable distance between spatially adjacent coordinates.

has volume in cubic meters
type: DatatypeProperty
sub property of: has metric size
domain: SpatialObject
range: double
definition: The volume of a Spatial Object in cubic meters.
example: C.1.1.2.9
example: C.1.2.2

has serialization
type: DatatypeProperty
domain: Geometry
range: Literal
definition: Connects a Geometry object with its text-based serialization.
example: C.1.2.3

is empty
type: DatatypeProperty
domain: Geometry
range: boolean
definition: (true) if this geometric object is the empty Geometry. If true, then this geometric object represents the empty point set for the coordinate space.
example: C.1.2.3

is simple
type: DatatypeProperty
domain: Geometry
range: boolean
definition: (true) if this geometric object has no anomalous geometric points, such as self intersection or self tangency.
example: C.1.2.3

spatial dimension
type: DatatypeProperty
domain: Geometry
range: integer
definition: The number of measurements or axes needed to describe the spatial position of this Geometry in a coordinate system.
example: C.1.2.3

day
type: DatatypeProperty
domain: Generalized date-time description
comment: Day position in a calendar-clock system. The range of this property is not specified, so can be replaced by any specific representation of a calendar day from any calendar.
comment: Posición de día en un sistema calendario-reloj. @es
label: día @es
definition: Posición de día en un sistema calendario-reloj. El rango de esta propiedad no está especificado, por tanto, se puede reemplazar por una representación específica de un día de calendario de cualquier calendario. @es

day of year
type: DatatypeProperty
domain: Generalized date-time description
range: nonNegativeInteger
comment: El número de día en el año. @es
comment: The number of the day within the year
label: día del año @es

days duration
type: DatatypeProperty
domain: Generalized duration description
range: decimal
comment: Longitud de, o elemento de la longitud de, una extensión temporal expresada en días. @es
comment: length of, or element of the length of, a temporal extent expressed in days
label: duración en días @es

has XSD duration
type: DatatypeProperty
domain: Temporal entity
range: duration
comment: Extensión de una entidad temporal, expresada utilizando xsd:duration. @es
comment: Extent of a temporal entity, expressed using xsd:duration
label: tiene duración XSD @es
editorial note: Característica arriesgada - añadida en la revisión de 2017, y todavía no ampliamente utilizada. @es
editorial note: Feature at risk - added in 2017 revision, and not yet widely used.

hour
type: DatatypeProperty
domain: Generalized date-time description
range: nonNegativeInteger
comment: Hour position in a calendar-clock system.
comment: Posición de hora en un sistema calendario-reloj. @es
label: hora @es

hours duration
type: DatatypeProperty
domain: Generalized duration description
range: decimal
comment: Longitud de, o elemento de la longitud de, una extensión temporal expresada en horas. @es
comment: length of, or element of the length of, a temporal extent expressed in hours
label: duración en horas @es

in XSD date
type: DatatypeProperty
domain: Time instant
range: date
comment: Posición de un instante, expresado utilizando xsd:date. @es
comment: Position of an instant, expressed using xsd:date
label: en fecha XSD @es

in XSD Date-Time
type: DatatypeProperty
domain: Time instant
range: dateTime
comment: Posición de un instante, expresado utilizando xsd:dateTime. @es
comment: Position of an instant, expressed using xsd:dateTime
label: en fecha-tiempo XSD @es
deprecated: true
note: La propiedad 'en fecha-hora XSD' ha sido reemplazada por 'en fecha-sello de tiempo XSD' que hace obligatorio el campo 'huso horario'. @es
note: The property :inXSDDateTime is replaced by :inXSDDateTimeStamp which makes the time-zone field mandatory.

in XSD Date-Time-Stamp
type: DatatypeProperty
domain: Time instant
range: sello de tiempo
comment: Posición de un instante, expresado utilizando xsd:dateTimeStamp. @es
comment: Position of an instant, expressed using xsd:dateTimeStamp
label: en fecha-sello de tiempo XSD @es

in XSD g-Year
type: DatatypeProperty
domain: Time instant
range: gYear
comment: Posición de un instante, expresado utilizando xsd:gYear. @es
comment: Position of an instant, expressed using xsd:gYear
label: en año gregoriano XSD @es

in XSD g-YearMonth
type: DatatypeProperty
domain: Time instant
range: gYearMonth
comment: Posición de un instante, expresado utilizando xsd:gYearMonth. @es
comment: Position of an instant, expressed using xsd:gYearMonth
label: en año-mes gregoriano XSD @es

minute
type: DatatypeProperty
domain: Generalized date-time description
range: nonNegativeInteger
comment: Minute position in a calendar-clock system.
comment: Posición de minuto en un sistema calendario-reloj. @es
label: minuto @es

minutes
type: DatatypeProperty
domain: Generalized duration description
range: decimal
comment: Longitud de, o elemento de la longitud de, una extensión temporal expresada en minutos. @es
comment: length, or element of, a temporal extent expressed in minutes
label: minutos @es

month
type: DatatypeProperty
domain: Generalized date-time description
comment: Month position in a calendar-clock system. The range of this property is not specified, so can be replaced by any specific representation of a calendar month from any calendar.
comment: Posición de mes en un sistema calendario-reloj. El rango de esta propiedad no está especificado, por tanto, se puede reemplazar por cualquier representación específica de un mes de calendario de un calendario cualquiera. @es
label: mes @es

months duration
type: DatatypeProperty
domain: Generalized duration description
range: decimal
comment: Longitud de, o elemento de la longitud de, una extensión temporal expresada en meses. @es
comment: length of, or element of the length of, a temporal extent expressed in months
label: duración en meses @es

Name of temporal position
type: DatatypeProperty
domain: Time position
range: string
comment: El valor (nominal) que indica posición temporal en un sistema de referencia ordinal. @es
comment: The (nominal) value indicating temporal position in an ordinal reference system
label: nombre de posición temporal @es

Numeric value of temporal duration
type: DatatypeProperty
domain: duración de tiempo
range: decimal
comment: Valor de una extensión temporal expresada como un número decimal escalado por una unidad de tiempo. @es
comment: Value of a temporal extent expressed as a decimal number scaled by a temporal unit
label: valor numérico de duración temporal @es

Numeric value of temporal position
type: DatatypeProperty
domain: Time position
range: decimal
comment: El valor (numérico) que indica posición temporal en un sistema de referencia ordinal. @es
comment: The (numeric) value indicating position within a temporal coordinate system
label: valor numérico de posición temporal @es

second
type: DatatypeProperty
domain: Generalized date-time description
range: decimal
comment: Posición de segundo en un sistema calendario-reloj. @es
comment: Second position in a calendar-clock system.
label: segundo @es

seconds duration
type: DatatypeProperty
domain: Generalized duration description
range: decimal
comment: Longitud de, o elemento de la longitud de, una extensión temporal expresada en segundos. @es
comment: length of, or element of the length of, a temporal extent expressed in seconds
label: duración en segundos @es

week
type: DatatypeProperty
domain: Generalized date-time description
range: nonNegativeInteger
comment: Número de semana en el año. @es
comment: Week number within the year.
label: semana @es
note: Weeks are numbered differently depending on the calendar in use and the local language or cultural conventions (locale). ISO-8601 specifies that the first week of the year includes at least four days, and that Monday is the first day of the week. In that system, week 1 is the week that contains the first Thursday in the year.
scope note: Las semanas están numeradas de forma diferente dependiendo del calendario en uso y de las convenciones lingüísticas y culturales locales (locale en inglés). El ISO-8601 especifica que la primera semana del año incluye al menos cuatro días, y que el lunes es el primer día de la semana. En ese sistema, la semana 1 es la semana que contiene el primer jueves del año. @es

weeks duration
type: DatatypeProperty
domain: Generalized duration description
range: decimal
comment: Longitud de, o elemento de la longitud de, una extensión temporal expresada en semanas. @es
comment: length of, or element of the length of, a temporal extent expressed in weeks
label: duración en semanas @es

has XSD date-time
type: DatatypeProperty
domain: Date-time interval
range: dateTime
comment: Valor de 'intervalo de fecha-hora' expresado como un valor compacto. @es
comment: Value of DateTimeInterval expressed as a compact value.
label: tiene fecha-hora XSD @es
deprecated: true
note: Using xsd:dateTime in this place means that the duration of the interval is implicit: it corresponds to the length of the smallest non-zero element of the date-time literal. However, this rule cannot be used for intervals whose duration is more than one rank smaller than the starting time - e.g. the first minute or second of a day, the first hour of a month, or the first day of a year. In these cases the desired interval cannot be distinguished from the interval corresponding to the next rank up. Because of this essential ambiguity, use of this property is not recommended and it is deprecated.
note: Utilizando xsd:dateTime en este lugar significa que la duración del intervalo está implícita: se corresponde con la longitud del elemento más pequeño distinto de cero del literal fecha-hora. Sin embargo, esta regla no se puede utilizar para intervalos cuya duración es mayor que un rango más pequeño que el tiempo de comienzo - p.ej. el primer minuto o segundo del día, la primera hora del mes, o el primer día del año. En estos casos el intervalo deseado no se puede distinguir del intervalo correspondiente al próximo rango más alto. Debido a esta ambigüedad esencial, no se recomienda el uso de esta propiedad y está desaprobada.

year
type: DatatypeProperty
domain: Generalized date-time description
comment: Posición de año en un sistema calendario-reloj. l rango de esta propiedad no está especificado, por tanto, se puede reemplazar por cualquier representación específica de un año de calendario de un calendario cualquiera. @es
comment: Year position in a calendar-clock system. The range of this property is not specified, so can be replaced by any specific representation of a calendar year from any calendar.

years duration
type: DatatypeProperty
domain: Generalized duration description
range: decimal
comment: Longitud de, o elemento de la longitud de, una extensión temporal expresada en años. @es
comment: length of, or element of the length of, a temporal extent expressed in years
label: duración en años @es

has simple result
type: DatatypeProperty
domain includes: Actuation
domain includes: Observation
domain includes: Sampling
comment: The simple value of an Observation or Actuation or act of Sampling.
example: For instance, the values 23 or true.

result time
type: DatatypeProperty
range: dateTime
domain includes: Actuation
domain includes: Observation
domain includes: Sampling
comment: The result time is the instant of time when the Observation, Actuation or Sampling activity was completed.

Vocabulary
type: Class

Abstract
type: Class
subclass of: Entity
disjoint with: Event
disjoint with: Object
disjoint with: Quality
comment: Any Entity that cannot be located in space-time. E.g. mathematical entities: formal semantics elements, regions within dimensional spaces, etc.
label: Astratto @it

Action
type: Class
subclass of: Event
subclass of: Restriction
  on property: has participant
  some values from: Agent
subclass of: Restriction
  on property: executes task
  min cardinality: 1
comment: An Event with at least one Agent that isParticipantIn it, and that executes a Task that typically isDefinedIn a Plan, Workflow, Project, etc.
label: Azione @it

Agent
type: Class
subclass of: Object
comment: 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.
comment: Any agentive Object , either physical (e.g. a whale, a robot, an oak), or social (e.g. a corporation, an institution, a community).
label: Agente @it

Amount
type: Class
subclass of: Region
disjoint with: Physical attribute
disjoint with: Space region
disjoint with: Time interval
comment: A quantity, independently from how it is measured, computed, etc.
label: Quantità @it

Biological object
type: Class
subclass of: Physical body

Chemical object
type: Class
subclass of: Physical body

Classification
type: Class
subclass of: TimeIndexedRelation
subclass of: Restriction
  on property: is setting for
  some values from: Concept
subclass of: Restriction
  on property: is setting for
  some values from: Entity
subclass of: Restriction
  on property: is setting for
  some values from: Time interval
comment: 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.
label: Classificazione @it
label: time-indexed classification

Collection
type: Class
subclass of: Social object
subclass of: Restriction
  on property: has part
  all values from: Collection
comment: 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. A collection is neither an aggregate of its member entities (see e.g. ObjectAggregate class).
label: Collezione @it

Collective
type: Class
subclass of: Collection
subclass of: Restriction
  on property: has member
  all values from: Agent
comment: 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.
label: Collettivo @it

Collective agent
type: Class
subclass of: Social agent
subclass of: Restriction
  on property: acts through
  some values from: Agent
subclass of: Restriction
  on property: is introduced by
  some values from: Description
comment: 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.
label: Agente collettivo @it

Community
type: Class
subclass of: Collective agent
label: Comunità @it

Concept
type: Class
subclass of: Social object
subclass of: Restriction
  on property: is defined in
  some values from: Description
subclass of: Restriction
  on property: has part
  all values from: Concept
disjoint with: Social agent
comment: 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
label: Concetto @it

Configuration
type: Class
subclass of: Collection
comment: 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.
label: Configurazione @it

Contract
type: Class
subclass of: Description
comment: (The content of) an agreement between at least two agents that play a Party Role, about some contract object (a Task to be executed).
label: Contratto @it

Description
type: Class
subclass of: Social object
disjoint with: Social agent
comment: 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. Descriptions 'define' or 'use' concepts, and can be 'satisfied' by situations.
label: Descrizione @it

Design
type: Class
subclass of: Description
comment: 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.

Designed artifact
type: Class
subclass of: Physical artifact
subclass of: Restriction
  on property: is described by
  some values from: Design
comment: 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.
label: Artefatto progettato @it

DesignedSubstance
type: Class
subclass of: Designed artifact
subclass of: Functional substance

Diagnosis
type: Class
subclass of: Description
comment: 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).
label: Diagnosi @it

Entity
type: Class
comment: Anything: real, possible, or imaginary, which some modeller wants to talk about for some purpose.
label: Entità @it

Event
type: Class
subclass of: Entity
subclass of: Restriction
  on property: has participant
  some values from: Object
subclass of: Restriction
  on property: has time interval
  some values from: Time interval
subclass of: Restriction
  on property: has constituent
  all values from: Event
subclass of: Restriction
  on property: has part
  all values from: Event
disjoint with: Object
disjoint with: Quality
comment: 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 suggested 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…
label: Evento @it

Event type
type: Class
subclass of: Concept
subclass of: Restriction
  on property: classifies
  all values from: Event
disjoint with: Parameter
disjoint with: Role
comment: 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)
label: Tipo di evento @it

Formal entity
type: Class
subclass of: Abstract
comment: 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'.
label: Entità formale astratta @it

Functional substance
type: Class
subclass of: Substance

Goal
type: Class
subclass of: Description
comment: The Description of a Situation that is desired by an Agent, and usually associated to a Plan that describes how to actually achieve it
label: Scopo @it

Group
type: Class
subclass of: Collective agent
subclass of: Restriction
  on property: is described by
  some values from: Plan
comment: A CollectiveAgent whose acting agents conceptualize a same SocialRelation .
label: Gruppo @it

InformationEntity
type: Class
subclass of: Entity
comment: A piece of information, be it concretely realized or not. It is a catchall class, intended to bypass the ambiguities of many data or text that could denote either a an expression or a concrete realization of that expression. In a semiotic model, there is no special reason to distinguish between them, however we may want to distinguish between a pure information content (e.g. the 3rd Gymnopedie by Satie), and its possible concrete realizations as a music sheet, a piano execution, the reproduction of the execution, its publishing as a record, etc.).

Information object
type: Class
subclass of: InformationEntity
subclass of: Social object
disjoint with: Social agent
comment: A piece of information, such as a musical composition, a text, a word, a picture, independently from how it is concretely realized.
label: Oggetto informativo @it

Information realization
type: Class
subclass of: InformationEntity
subclass of: Class
  union of: Event
  union of: Physical object
  union of: Quality
subclass of: Restriction
  on property: realizes
  some values from: Information object
subclass of: Restriction
  on property: realizesSelfInformation
  has self: true
comment: A concrete realization of an InformationObject, e.g. the written document (object) containing the text of a law, a poetry reading (event), the dark timbre (quality) of a sound (event) in the execution (event) of a musical composition, realizing a 'misterioso' tempo indication. The realization of an information object also realizes information about itself. This is a special semiotic feature, which allows to avoid a traditonal paradox, by which an information is often supposed to be about itself besides other entities (e.g. the information object 'carpe diem' is about its meaning in Horace's Odes (let alone its fortune in Western culture and beyond), but also about its expression in context: 'dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero', with the sound and emotional relations that it could activate. This is expressed in OWL2 with a local reflexivity axiom of the dul:InformationRealization class.
label: Informazione concreta @it

Local concept
type: Class
subclass of: Concept
comment: 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.

Method
type: Class
subclass of: Description
comment: 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.
label: Metodo @it

Narrative
type: Class
subclass of: Description

Natural person
type: Class
subclass of: Persona {it}
subclass of: Physical agent
comment: A person in the physical commonsense intuition: 'have you seen that person walking down the street?'
label: Persona fisica @it

Norm
type: Class
subclass of: Description
comment: A social norm.
label: Norma @it

Object
type: Class
subclass of: Entity
subclass of: Restriction
  on property: has location
  some values from: Entity
subclass of: Restriction
  on property: is participant in
  some values from: Event
subclass of: Restriction
  on property: has constituent
  all values from: Object
subclass of: Restriction
  on property: has part
  all values from: Object
subclass of: Restriction
  on property: is classified by
  all values from: Role
disjoint with: Quality
comment: 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.
label: Oggetto @it

ObjectAggregate
type: Class
subclass of: Class
  intersection of: Object
  intersection of: Restriction
    on property: has part
    some values from: Class
      intersection of: Object
      intersection of: Restriction
        on property: is member of
        some values from: Collection
creator: Aldo Gangemi
date: 2021-02-21T23:35:02+00:00
comment: An aggregate of distributed objects, members of a same Collection, e.g. the stars in a constellation, the parts of a car, the employees of a company, the entries from an encyclopedia, the concepts expressed in a speech, etc. It cannot be defined by means of an equivalence axiom, because it'd require the same Collection for all members, an axiom that cannot be expressed in OWL.

Organism
type: Class
subclass of: Biological object
subclass of: Physical agent
comment: A physical objects with biological characteristics, typically that organisms can self-reproduce.
label: Organismo @it

Organization
type: Class
subclass of: Social agent
comment: An internally structured, conventionally created SocialAgent, needing a specific Role and Agent that plays it, in order to act.
comment: Un agente sociale strutturato internamente e creato convenzionalmente. Per agire, ha bisogno di ruoli e agenti che li ricoprano. @it
label: Organizzazione @it

Parameter
type: Class
subclass of: Concept
subclass of: Restriction
  on property: classifies
  all values from: Region
subclass of: Restriction
  on property: has part
  all values from: Parameter
disjoint with: Role
comment: 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.
label: Parametro @it

parthood
type: Class
subclass of: TimeIndexedRelation
subclass of: Restriction
  on property: includesPart
  some values from: Entity
subclass of: Restriction
  on property: includesWhole
  some values from: Entity
has key: includesPart
has key: includesWhole
creator: Aldo Gangemi
date: 2021-04-03T13:53:57+00:00
comment: A special kind of Situation that allows to include time indexing for the hasPart relation in situations. For example, if a Situation s 'finally, my bike has a luggage rack' isSettingFor the entity 'my bike' and the TimeIntervals 'now', or more specifically '29March2021', we need to have a time-index the part relation. With Parthood, we use includesWhole and includesPart properties. This can be done similarly for other arguments of parthood, e.g. location, configuration, topology, etc. Concerning the possible property characteristics reused from mereology (transitivity, asymmetry, reflexivity), they need to be implemented by means of rules (or, in a limited way, property chains using the binary hasPart or hasProperPart properties). A key is also added to ensure identification constraints of time-indexed parthood.

Pattern
type: Class
subclass of: Relation
comment: 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

Persona {it}
type: Class
subclass of: Agent
comment: Persons in commonsense intuition, which does not apparently distinguish between either natural or social persons.
label: Person

Personification
type: Class
subclass of: Social agent
comment: 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.

Physical agent
type: Class
subclass of: Agent
subclass of: Physical object
comment: 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
label: Agente fisico @it

Physical artifact
type: Class
subclass of: Physical object
subclass of: Restriction
  on property: is described by
  some values from: Plan
comment: 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.
label: Artefatto fisico @it

Physical attribute
type: Class
subclass of: Region
subclass of: Restriction
  on property: is region for
  all values from: Physical object
disjoint with: Space region
disjoint with: Time interval
comment: Physical value of a physical object, e.g. density, color, etc.
label: Caratteristica fisica @it

Physical body
type: Class
subclass of: Physical object
comment: 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.

Physical object
type: Class
subclass of: Object
subclass of: Restriction
  on property: has part
  all values from: Physical object
disjoint with: Social object
comment: 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).
label: Oggetto fisico @it

Physical place
type: Class
subclass of: Physical object
comment: A physical object that is inherently located; for example, a water area.
label: Luogo fisico @it

Place
type: Class
subclass of: Social object
subclass of: Restriction
  on property: is location of
  min cardinality: 1
comment: Socially or cognitively dependent locations: political geographic entities (Rome, Lesotho), and non-material locations determined by the presence of other entities ("the area close to Rome") or of pivot events or signs ("the area where the helicopter fell"), as well as identified as complements to other entities ("the area under the table"), etc. In this generic sense, a Place is a 'dependent' location. For 'non-dependent' locations, cf. the PhysicalPlace class. For an abstract (dimensional) location, cf. the SpaceRegion class.
label: Luogo @it

Plan
type: Class
subclass of: Description
subclass of: Restriction
  on property: has component
  some values from: Goal
comment: A Description having an explicit Goal, to be achieved by executing the plan
label: Piano @it

Plan execution
type: Class
equivalent class: Restriction
  on property: satisfies
  some values from: Plan
subclass of: Situation
comment: Plan executions are situations that proactively satisfy a plan. Subplan executions are proper parts of the whole plan execution.
label: Esecuzione di piano @it

Process
type: Class
subclass of: Event
comment: 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'.
label: Processo @it

Project
type: Class
subclass of: Plan
subclass of: Restriction
  on property: defines role
  some values from: Role
subclass of: Restriction
  on property: defines task
  some values from: Task
comment: 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.
label: Progetto @it

Quality
type: Class
subclass of: Entity
subclass of: Restriction
  on property: has region
  some values from: Region
subclass of: Restriction
  on property: is quality of
  some values from: Entity
subclass of: Restriction
  on property: has constituent
  all values from: Quality
subclass of: Restriction
  on property: has part
  all values from: Quality
comment: 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'.
label: Qualità @it

Region
type: Class
subclass of: Abstract
subclass of: Restriction
  on property: has constituent
  all values from: Region
subclass of: Restriction
  on property: has part
  all values from: Region
subclass of: Restriction
  on property: overlaps
  all values from: Region
subclass of: Restriction
  on property: precedes
  all values from: Region
comment: 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
label: Regione @it

Relation
type: Class
subclass of: Description
comment: 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.
label: Relazione @it

Right
type: Class
subclass of: Description
subclass of: Restriction
  on property: defines role
  min cardinality: 2
subclass of: Restriction
  on property: defines task
  min cardinality: 1
comment: 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.
label: Diritto @it

Role
type: Class
subclass of: Concept
subclass of: Restriction
  on property: classifies
  all values from: Object
subclass of: Restriction
  on property: has part
  all values from: Role
comment: A Concept that classifies an Object
label: Ruolo @it

Insieme {it}
type: Class
subclass of: Formal entity
label: Set

Situation
type: Class
equivalent class: Restriction
  on property: satisfies
  some values from: Description
subclass of: Entity
comment: 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 adding (some or all) OWL2 keys, corresponding to binary projections of the n-ary, to a subclass of Situation. Otherwise the 'identification constraint' (Calvanese et al., IJCAI 2001) might be violated.
label: Situazione @it

Social agent
type: Class
subclass of: Agent
subclass of: Social object
subclass of: Restriction
  on property: acts through
  some values from: Physical agent
comment: Any individual whose existence is granted simply by its social communicability and capability of action (through some PhysicalAgent).
label: Agente sociale @it

Social object
type: Class
subclass of: Object
subclass of: Restriction
  on property: is expressed by
  some values from: Information object
subclass of: Restriction
  on property: has part
  all values from: Social object
comment: 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 or intepreting existing entities (Description, Concept), or for collecting existing entities (Collection). Being dependent on communication, all social objects need to be expressed by some information object (information objects are self-expressing).
label: Oggetto sociale @it

Social attribute
type: Class
subclass of: Region
subclass of: Restriction
  on property: is region for
  all values from: Social object
comment: 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.
label: Caratteristica sociale @it

Social person
type: Class
subclass of: Persona {it}
subclass of: Social agent
subclass of: Restriction
  on property: acts through
  cardinality: 1
comment: 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).
label: Persona sociale @it
version info: Formerly: Person (changed to avoid confusion with commonsense intuition)

Social relation
type: Class
subclass of: Relation
comment: Any social relationship
label: Relazione sociale @it

Space region
type: Class
subclass of: Region
disjoint with: Time interval
comment: 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.
label: Regione di spazio @it

SpatioTemporalRegion
type: Class
subclass of: Region
subclass of: Restriction
  on property: has constituent
  some values from: Space region
subclass of: Restriction
  on property: has constituent
  some values from: Time interval

Substance
type: Class
subclass of: Physical body
comment: 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).
label: Sostanza @it

Task
type: Class
subclass of: Event type
subclass of: Restriction
  on property: has part
  all values from: Task
subclass of: Restriction
  on property: is executed in
  all values from: Action
subclass of: Restriction
  on property: is task defined in
  all values from: Description
subclass of: Restriction
  on property: is task of
  all values from: Role
comment: 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.

Theory
type: Class
subclass of: Description
subclass of: Restriction
  on property: has component
  some values from: Relation
comment: 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).
label: Teoria @it

TimeIndexedRelation
type: Class
equivalent class: Class
  intersection of: Situation
  intersection of: Restriction
    on property: is setting for
    some values from: Time interval
subclass of: Situation
creator: Aldo Gangemi
date: 2021-02-24T14:24:23+00:00
comment: A Situation that includes a time indexing in its setting, so allowing to order any binary relation (property) with time.

Time interval
type: Class
subclass of: Region
comment: Any Region in a dimensional space that aims at representing time.
label: Intervallo di tempo @it

Transition
type: Class
subclass of: Situation
subclass of: Restriction
  on property: includes event
  some values from: Event
subclass of: Restriction
  on property: includes object
  some values from: Object
subclass of: Restriction
  on property: is setting for
  some values from: Process
subclass of: Restriction
  on property: is setting for
  some values from: Class
    intersection of: Situation
    intersection of: Restriction
      on property: precedes
      some values from: Class
        intersection of: Event
        intersection of: Restriction
subclass of: Restriction
  on property: includes time
  min qualified cardinality: 3
  on class: Time interval
subclass of: Restriction
  on property: is setting for
  min qualified cardinality: 2
  on class: Situation
comment: 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.
label: Transizione @it

Type collection
type: Class
subclass of: Collection
comment: 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.
label: Collezione di un tipo @it

Unit of measure
type: Class
subclass of: Parameter
subclass of: Restriction
  on property: parametrizes
  some values from: Region
comment: Units of measure are conceptualized here as parameters on regions, which can be valued as datatype values.
label: Unità di misura @it

Workflow
type: Class
subclass of: Plan
subclass of: Restriction
  on property: defines role
  some values from: Role
subclass of: Restriction
  on property: defines task
  some values from: Task
comment: A Plan that defines Role(s), Task(s), and a specific structure for tasks to be executed, usually supporting the work of an Organization

Workflow execution
type: Class
equivalent class: Restriction
  on property: satisfies
  some values from: Workflow
subclass of: Situation
label: Esecuzione di workflow @it

Feature
type: Class
subclass of: SpatialObject
disjoint with: Geometry
definition: A discrete spatial phenomenon in a universe of discourse.
example: C.1.1.2.1
example: C.1.1.2.2
example: C.1.1.2.3
example: C.1.1.2.4
example: C.1.1.2.5
example: C.1.1.2.6
example: C.1.1.2.7
example: C.1.1.2.8
example: C.1.1.2.9
example: C.1.1.3.2
example: C.1.1.3.3
example: C.1.2.2
example: C.1.2.3
example: C.1.2.4
note: A Feature represents a uniquely identifiable phenomenon, for example a river or an apple. While such phenomena (and therefore the Features used to represent them) are bounded, their boundaries may be crisp (e.g., the declared boundaries of a state), vague (e.g., the delineation of a valley versus its neighboring mountains), and change with time (e.g., a storm front). While discrete in nature, Features may be created from continuous observations, such as an isochrone that determines the region that can be reached by ambulance within 5 minutes.

FeatureCollection
type: Class
subclass of: SpatialObjectCollection
subclass of: Restriction
  on property: member
  all values from: Feature
definition: A collection of individual Features.
example: C.1.1.6
preferred label: Feature Collection

Geometry
type: Class
subclass of: SpatialObject
definition: A coherent set of direct positions in space. The positions are held within a Spatial Reference System (SRS).
example: C.1.1.2.2
example: C.1.1.2.3
example: C.1.1.2.4
example: C.1.1.2.5
example: C.1.1.2.6
example: C.1.1.2.8
example: C.1.1.3.1
example: C.1.1.3.2
example: C.1.1.3.3
example: C.1.2.2
example: C.1.2.3
example: C.1.2.4
note: Geometry can be used as a representation of the shape, extent or location of a Feature and may exist as a self-contained entity.

GeometryCollection
type: Class
subclass of: SpatialObjectCollection
subclass of: Restriction
  on property: member
  all values from: Geometry
definition: A collection of individual Geometries.
example: C.1.1.7
preferred label: Geometry Collection

SpatialObject
type: Class
definition: Anything spatial (being or having a shape, position or an extent).
example: C.1.1.1.1
example: C.1.1.1.2
note: Subclasses of this class are expected to be used for instance data.
preferred label: Spatial Object

SpatialObjectCollection
type: Class
subclass of: Container
subclass of: Restriction
  on property: member
  all values from: SpatialObject
definition: A collection of individual Spatial Objects.
note: This is the superclass of Feature Collection and Geometry Collection.
preferred label: Spatial Object Collection

Container
type: Class

Thing
type: Class

Date-Time description
type: Class
subclass of: Generalized date-time description
subclass of: Restriction
  on property: Temporal reference system used
  has value: Gregorian
subclass of: Restriction
  on property: day
  all values from: gDay
subclass of: Restriction
  on property: month
  all values from: gMonth
subclass of: Restriction
  on property: year
  all values from: gYear
comment: Descripción de fecha y tiempo estructurada con valores separados para los diferentes elementos de un sistema calendario-reloj. El sistema de referencia temporal está fijado al calendario gregoriano, y el rango de las propiedades año, mes, día restringidas a los correspondientes tipos del XML Schema xsd:gYear, xsd:gMonth y xsd:gDay respectivamente. @es
comment: Description of date and time structured with separate values for the various elements of a calendar-clock system. The temporal reference system is fixed to Gregorian Calendar, and the range of year, month, day properties restricted to corresponding XML Schema types xsd:gYear, xsd:gMonth and xsd:gDay, respectively.
label: descripción de fecha-tiempo @es

Date-time interval
type: Class
subclass of: Proper interval
comment: 'intervalo de fecha-hora' es una subclase de 'intervalo propio', definida utilizando el multi-elemento 'descripción de fecha-hora'. @es
comment: DateTimeInterval is a subclass of ProperInterval, defined using the multi-element DateTimeDescription.
label: intervalo de fecha-hora @es
note: 'intervalo de fecha-hora' se puede utilizar sólo para un intervalo cuyos límites coinciden con un elemento de fecha-hora alineados con el calendario y la zona horaria indicados. Por ejemplo, aunque ambos tienen una duración de un día, el intervalo de 24 horas que empieza en la media noche del comienzo del 8 mayo en Europa Central se puede expresar como un 'intervalo de fecha-hora', el intervalo de 24 horas que empieza a las 1:30pm no. @es
note: :DateTimeInterval can only be used for an interval whose limits coincide with a date-time element aligned to the calendar and timezone indicated. For example, while both have a duration of one day, the 24-hour interval beginning at midnight at the beginning of 8 May in Central Europe can be expressed as a :DateTimeInterval, but the 24-hour interval starting at 1:30pm cannot.

Day of week
type: Class
subclass of: Thing
comment: El día de la semana @es
comment: The day of week
label: día de la semana @es
change note: Remove enumeration from definition, in order to allow other days to be used when required in other calendars. NOTE: existing days are still present as members of the class, but the class membership is now open. In the original OWL-Time the following constraint appeared: owl:oneOf ( time:Monday time:Tuesday time:Wednesday time:Thursday time:Friday time:Saturday time:Sunday ) ;
note: La pertenencia a la clase 'día de la semana' está abierta, para permitir longitudes de semana alternativas y diferentes nombres de días. @es
note: Membership of the class :DayOfWeek is open, to allow for alternative week lengths and different day names.

duración de tiempo
type: Class
subclass of: Temporal duration
subclass of: Restriction
  on property: temporal unit type
  cardinality: 1
subclass of: Restriction
  on property: Numeric value of temporal duration
  cardinality: 1
comment: Duración de una extensión temporal expresada como un número escalado por una unidad temporal. @es
comment: Duration of a temporal extent expressed as a number scaled by a temporal unit
label: Time duration
note: Alternativa a 'descripción de tiempo' para proporcionar descripción soporte a una duración temporal diferente a utilizar un sistema de calendario/reloj. @es
note: Alternative to time:DurationDescription to support description of a temporal duration other than using a calendar/clock system.

Duration description
type: Class
subclass of: Generalized duration description
subclass of: Restriction
  on property: Temporal reference system used
  has value: Gregorian
subclass of: Restriction
  on property: days duration
  all values from: decimal
subclass of: Restriction
  on property: hours duration
  all values from: decimal
subclass of: Restriction
  on property: minutes
  all values from: decimal
subclass of: Restriction
  on property: months duration
  all values from: decimal
subclass of: Restriction
  on property: seconds duration
  all values from: decimal
subclass of: Restriction
  on property: weeks duration
  all values from: decimal
subclass of: Restriction
  on property: years duration
  all values from: decimal
comment: Descripción de extensión temporal estructurada con valores separados para los distintos elementos de un sistema de horario-calendario. El sistema de referencia temporal se fija al calendario gregoriano, y el intervalo de cada una de las propiedades numéricas se restringe a xsd:decimal. @es
comment: Description of temporal extent structured with separate values for the various elements of a calendar-clock system. The temporal reference system is fixed to Gregorian Calendar, and the range of each of the numeric properties is restricted to xsd:decimal
label: descripción de duración @es
note: En el calendario gregoriano la longitud de los meses no es fija. Por lo tanto, un valor como "2,5 meses" no se puede comparar exactamente con una duración similar expresada en términos de semanas o días. @es
note: In the Gregorian calendar the length of the month is not fixed. Therefore, a value like "2.5 months" cannot be exactly compared with a similar duration expressed in terms of weeks or days.

Generalized date-time description
type: Class
subclass of: Temporal position
subclass of: Restriction
  on property: temporal unit type
  cardinality: 1
subclass of: Restriction
  on property: day of week
  max cardinality: 1
subclass of: Restriction
  on property: month of year
  max cardinality: 1
subclass of: Restriction
  on property: in time zone
  max cardinality: 1
subclass of: Restriction
  on property: day
  max cardinality: 1
subclass of: Restriction
  on property: day of year
  max cardinality: 1
subclass of: Restriction
  on property: hour
  max cardinality: 1
subclass of: Restriction
  on property: minute
  max cardinality: 1
subclass of: Restriction
  on property: month
  max cardinality: 1
subclass of: Restriction
  on property: second
  max cardinality: 1
subclass of: Restriction
  on property: week
  max cardinality: 1
subclass of: Restriction
  on property: year
  max cardinality: 1
comment: Descripción de fecha y hora estructurada con valores separados para los distintos elementos de un sistema calendario-reloj.
comment: Description of date and time structured with separate values for the various elements of a calendar-clock system
label: descripción de fecha-hora generalizada @es
note: Algunas combinaciones de propiedades son redundantes - por ejemplo, dentro de un 'año' especificado si se proporciona 'día del año' entonces 'día' y 'mes' se pueden computar, y viceversa. Los valores individuales deberían ser consistentes entre ellos y con el calendario, indicado a través del valor de la propiedad 'tiene TRS'. @es
note: Some combinations of properties are redundant - for example, within a specified :year if :dayOfYear is provided then :day and :month can be computed, and vice versa. Individual values should be consistent with each other and the calendar, indicated through the value of the :hasTRS property.

Generalized duration description
type: Class
subclass of: Temporal duration
subclass of: Restriction
  on property: Temporal reference system used
  cardinality: 1
subclass of: Restriction
  on property: days duration
  max cardinality: 1
subclass of: Restriction
  on property: hours duration
  max cardinality: 1
subclass of: Restriction
  on property: minutes
  max cardinality: 1
subclass of: Restriction
  on property: months duration
  max cardinality: 1
subclass of: Restriction
  on property: seconds duration
  max cardinality: 1
subclass of: Restriction
  on property: weeks duration
  max cardinality: 1
subclass of: Restriction
  on property: years duration
  max cardinality: 1
comment: Descripción de extensión temporal estructurada con valores separados para los distintos elementos de un sistema de horario-calendario. @es
comment: Description of temporal extent structured with separate values for the various elements of a calendar-clock system.
label: descripción de duración generalizada @es
note: La extensión de una duración de tiempo expresada como una 'descripción de duración general' depende del Sistema de Referencia Temporal. En algunos calendarios la longitud de la semana o del mes no es constante a lo largo del año. Por tanto, un valor como "25 meses" puede no ser necesariamente ser comparado con un duración similar expresada en términos de semanas o días. Cuando se consideran calendarios que no están basados en el movimiento de la Tierra, se deben tomar incluso más precauciones en la comparación de duraciones. @es
note: The extent of a time duration expressed as a GeneralDurationDescription depends on the Temporal Reference System. In some calendars the length of the week or month is not constant within the year. Therefore, a value like "2.5 months" may not necessarily be exactly compared with a similar duration expressed in terms of weeks or days. When non-earth-based calendars are considered even more care must be taken in comparing durations.

Time instant
type: Class
subclass of: Temporal entity
disjoint with: Proper interval
comment: A temporal entity with zero extent or duration
comment: Una entidad temporal con una extensión o duración cero. @es
label: instante de tiempo. @es

Time interval
type: Class
subclass of: Temporal entity
comment: A temporal entity with an extent or duration
comment: Una entidad temporal con una extensión o duración. @es
label: intervalo de tiempo @es

January
type: Class
subclass of: Date-Time description
subclass of: Restriction
  on property: temporal unit type
  has value: Month (unit of temporal duration)
subclass of: Restriction
  on property: month
  has value: --01
deprecated: true
history note: This class was present in the 2006 version of OWL-Time. It was presented as an example of how DateTimeDescription could be specialized, but does not belong in the revised ontology.

Month of year
type: Class
subclass of: Date-Time description
subclass of: Restriction
  on property: temporal unit type
  has value: Month (unit of temporal duration)
subclass of: Restriction
  on property: day
  cardinality: 0
subclass of: Restriction
  on property: hour
  cardinality: 0
subclass of: Restriction
  on property: minute
  cardinality: 0
subclass of: Restriction
  on property: month
  cardinality: 1
subclass of: Restriction
  on property: second
  cardinality: 0
subclass of: Restriction
  on property: week
  cardinality: 0
subclass of: Restriction
  on property: year
  cardinality: 0
comment: El mes del año. @es
comment: The month of the year
label: mes del año @es
editorial note: Característica en riesgo - añadida en la revisión de 2017, y no utilizada todavía de forma amplia. @es
editorial note: Feature at risk - added in 2017 revision, and not yet widely used.
note: La pertenencia a la clase 'mes del año' está abierta, a permitir calendarios anuales alternativos y diferentes nombres de meses. @es
note: Membership of the class :MonthOfYear is open, to allow for alternative annual calendars and different month names.

Proper interval
type: Class
subclass of: Time interval
comment: A temporal entity with non-zero extent or duration, i.e. for which the value of the beginning and end are different
comment: Una entidad temporal con extensión o duración distinta de cero, es decir, para la cual los valores de principio y fin del intervalo son diferentes. @es
label: intervalo propio @es

Temporal Reference System
type: Class
comment: A temporal reference system, such as a temporal coordinate system (with an origin, direction, and scale), a calendar-clock combination, or a (possibly hierarchical) ordinal system. This is a stub class, representing the set of all temporal reference systems.
comment: Un sistema de referencia temporal, tal como un sistema de coordenadas temporales (con un origen, una dirección y una escala), una combinación calendario-reloj, o un sistema ordinal (posiblemente jerárquico). Esta clase comodín representa el conjunto de todos los sistemas de referencia temporal. @es
label: sistema de referencia temporal @es
note: A taxonomy of temporal reference systems is provided in ISO 19108:2002 [ISO19108], including (a) calendar + clock systems; (b) temporal coordinate systems (i.e. numeric offset from an epoch); (c) temporal ordinal reference systems (i.e. ordered sequence of named intervals, not necessarily of equal duration).
note: En el ISO 19108:2002 [ISO19108] se proporciona una taxonomía de sistemas de referencia temporal, incluyendo (a) sistemas de calendario + reloj; (b) sistemas de coordenadas temporales (es decir, desplazamiento numérico a partir de una época); (c) sistemas de referencia ordinales temporales (es decir, secuencia ordenada de intervalos nombrados, no necesariamente de igual duración). @es

Temporal duration
type: Class
comment: Extensión de tiempo; duración de un intervalo de tiempo independiente de su posición de inicio particular. @es
comment: Time extent; duration of a time interval separate from its particular start position
label: duración temporal @es

Temporal entity
type: Class
equivalent class: Class
  union of: Time instant
  union of: Time interval
subclass of: Thing
comment: A temporal interval or instant.
comment: Un intervalo temporal o un instante. @es
label: entidad temporal @es

Temporal position
type: Class
subclass of: Restriction
  on property: Temporal reference system used
  cardinality: 1
comment: A position on a time-line
comment: Una posición sobre una línea de tiempo. @es
label: posición temporal @es

Temporal unit
type: Class
subclass of: Temporal duration
comment: A standard duration, which provides a scale factor for a time extent, or the granularity or precision for a time position.
comment: Una duración estándar, que proporciona un factor de escala para una extensión de tiempo, o la granularidad o precisión para una posición de tiempo. @es
label: unidad de tiempo @es
change note: Remove enumeration from definition, in order to allow other units to be used when required in other coordinate systems. NOTE: existing units are still present as members of the class, but the class membership is now open. In the original OWL-Time the following constraint appeared: owl:oneOf ( time:unitSecond time:unitMinute time:unitHour time:unitDay time:unitWeek time:unitMonth time:unitYear ) ;
note: La pertenencia de la clase 'unidad de tiempo' está abierta, para permitir otras unidades de tiempo utilizadas en algunas aplicaciones técnicas (por ejemplo, millones de años o el mes Baha'i). @es
note: Membership of the class TemporalUnit is open, to allow for other temporal units used in some technical applications (e.g. millions of years, Baha'i month).

Time position
type: Class
subclass of: Temporal position
subclass of: Class
  union of: Restriction
    on property: Name of temporal position
    cardinality: 1
  union of: Restriction
    on property: Numeric value of temporal position
    cardinality: 1
comment: A temporal position described using either a (nominal) value from an ordinal reference system, or a (numeric) value in a temporal coordinate system.
comment: Una posición temporal descrita utilizando bien un valor (nominal) de un sistema de referencia ordinal, o un valor (numérico) en un sistema de coordenadas temporales. @es
label: posición de tiempo @es

Time Zone
type: Class
comment: A Time Zone specifies the amount by which the local time is offset from UTC. A time zone is usually denoted geographically (e.g. Australian Eastern Daylight Time), with a constant value in a given region. The region where it applies and the offset from UTC are specified by a locally recognised governing authority.
comment: Un huso horario especifica la cantidad en que la hora local está desplazada con respecto a UTC. Un huso horario normalmente se denota geográficamente (p.ej. el horario de verano del este de Australia), con un valor constante en una región dada. La región donde aplica y el desplazamiento desde UTC las especifica una autoridad gubernamental localmente reconocida. @es
label: huso horario @es
history note: En la versión original de OWL-Time de 2006, se definió, en un espacio de nombres diferente "http://www.w3.org/2006/timezone#", la clase 'huso horario', con varias propiedades específicas correspondientes a un modelo específico de huso horario. En la versión actual hay una clase con el mismo nombre local en el espacio de nombres de OWL-Time, eliminando la dependencia del espacio de nombres externo. Un axioma de alineación permite que los datos codificados de acuerdo con la versión anterior sean consistentes con la ontología actualizada. @es
history note: In the original 2006 version of OWL-Time, the TimeZone class, with several properties corresponding to a specific model of time-zones, was defined in a separate namespace "http://www.w3.org/2006/timezone#". In the current version a class with same local name is put into the main OWL-Time namespace, removing the dependency on the external namespace. An alignment axiom tzont:TimeZone rdfs:subClassOf time:TimeZone . allows data encoded according to the previous version to be consistent with the updated ontology.
note: A designated timezone is associated with a geographic region. However, for a particular region the offset from UTC often varies seasonally, and the dates of the changes may vary from year to year. The timezone designation usually changes for the different seasons (e.g. Australian Eastern Standard Time vs. Australian Eastern Daylight Time). Furthermore, the offset for a timezone may change over longer timescales, though its designation might not. Detailed guidance about working with time zones is given in http://www.w3.org/TR/timezone/ .
note: An ontology for time zone descriptions was described in [owl-time-20060927] and provided as RDF in a separate namespace tzont:. However, that ontology was incomplete in scope, and the example datasets were selective. Furthermore, since the use of a class from an external ontology as the range of an ObjectProperty in OWL-Time creates a dependency, reference to the time zone class has been replaced with the 'stub' class in the normative part of this version of OWL-Time.
note: Un huso horario designado está asociado con una región geográfica. Sin embargo, para una región particular el desplazamiento desde UTC a menudo varía según las estaciones, y las fechas de los cambios pueden variar de un año a otro. La designación de huso horario normalmente cambia de una estación a otra (por ejemplo, el horario estándar frente al horario de verano ambos del este de Australia). Además, del desplazamiento para un huso horario puede cambiar sobre escalas de tiempo mayores, aunque su designación no lo haga. Se puede encontrar una guía detallada sobre el funcionamiento de husos horarios en http://www.w3.org/TR/timezone/."@es , "En [owl-time-20060927] se describió una ontología para descripciones de husos horarios, y se proporcionó en un espacio de nombres separado tzont:. Sin embargo, dicha ontología estaba incompleta en su alcance, y el ejemplo de conjuntos de datos (datasets) era selectivo. Además, puesto que el uso de una clase de una ontología externa como el rango de una propiedad de objeto en OWL-Time crea una dependencia, la referencia a la clase huso horario se ha reemplazado por una clase que viene a ser un "cajón de sastre" en la en la parte normativa de esta versión de OWL-Time. @es
scope note: En esta implementación 'huso horario' no tiene definidas propiedades. Se debería pensar como una superclase "abstracta" de todas las implementaciones de huso horario específicas. @es
scope note: In this implementation TimeZone has no properties defined. It should be thought of as an 'abstract' superclass of all specific timezone implementations.

Year
type: Class
subclass of: Duration description
subclass of: Restriction
  on property: days duration
  cardinality: 0
subclass of: Restriction
  on property: hours duration
  cardinality: 0
subclass of: Restriction
  on property: minutes
  cardinality: 0
subclass of: Restriction
  on property: months duration
  cardinality: 0
subclass of: Restriction
  on property: seconds duration
  cardinality: 0
subclass of: Restriction
  on property: weeks duration
  cardinality: 0
subclass of: Restriction
  on property: years duration
  cardinality: 1
comment: Year duration
deprecated: true
history note: Year was proposed in the 2006 version of OWL-Time as an example of how DurationDescription could be specialized to allow for a duration to be restricted to a number of years. It is deprecated in this edition of OWL-Time.
preferred label: Anno @it
preferred label: Année (calendrier) @fr
preferred label: Ano @pt
preferred label: Año @es
preferred label: Jaar @nl
preferred label: Jahr @de
preferred label: Rok @pl
preferred label: Год @ru
preferred label: سنة @ar
preferred label: 年 @ja

Actuatable Property
type: Class
subclass of: Property
subclass of: Restriction
  on property: is acted on by
  all values from: Actuation
comment: An actuatable quality (property, characteristic) of a FeatureOfInterest.
example: A window actuator acts by changing the state between a frame and a window. The ability of the window to be opened and closed is its ActuatableProperty.

Actuation
type: Class
subclass of: Restriction
  on property: acts on property
  all values from: Actuatable Property
subclass of: Restriction
  on property: has feature of interest
  all values from: Feature Of Interest
subclass of: Restriction
  on property: has result
  all values from: Result
subclass of: Restriction
  on property: made by actuator
  all values from: Actuator
subclass of: Restriction
  on property: used procedure
  all values from: Procedure
subclass of: Restriction
  on property: acts on property
  min cardinality: 1
subclass of: Restriction
  on property: has result
  min cardinality: 1
subclass of: Restriction
  on property: has feature of interest
  cardinality: 1
subclass of: Restriction
  on property: made by actuator
  cardinality: 1
subclass of: Restriction
  on property: result time
  cardinality: 1
comment: An Actuation carries out an (Actuation) Procedure to change the state of the world using an Actuator.
example: The activity of automatically closing a window if the temperature in a room drops below 20 degree Celsius. The activity is the Actuation and the device that closes the window is the Actuator. The Procedure is the rule, plan, or specification that defines the conditions that triggers the Actuation, here a drop in temperature.

Actuator
type: Class
subclass of: System
subclass of: Restriction
  on property: made actuation
  all values from: Actuation
subclass of: Restriction
  on property: for property
  all values from: Actuatable Property
subclass of: Restriction
  on property: implements
  min cardinality: 1
comment: A device that is used by, or implements, an (Actuation) Procedure that changes the state of the world.
example: A window actuator for automatic window control, i.e., opening or closing the window.

Feature Of Interest
type: Class
subclass of: Restriction
  on property: has sample
  all values from: Sample
subclass of: Restriction
  on property: has property
  all values from: Property
subclass of: Restriction
  on property: has property
  min cardinality: 1
comment: The thing whose property is being estimated or calculated in the course of an Observation to arrive at a Result or whose property is being manipulated by an Actuator, or which is being sampled or transformed in an act of Sampling.
example: When measuring the height of a tree, the height is the observed ObservableProperty, 20m may be the Result of the Observation, and the tree is the FeatureOfInterest. A window is a FeatureOfInterest for an automatic window control Actuator.

Observable Property
type: Class
subclass of: Property
subclass of: Restriction
  on property: is observed by
  all values from: Sensor
subclass of: Restriction
  on property:
    inverse of: observed property
  all values from: Observation
subclass of: Restriction
  on property:
    inverse of: is proxy for
  all values from: Stimulus
comment: An observable quality (property, characteristic) of a FeatureOfInterest.
example: The height of a tree, the depth of a water body, or the temperature of a surface are examples of observable properties, while the value of a classic car is not (directly) observable but asserted.

Observation
type: Class
subclass of: Restriction
  on property: has feature of interest
  all values from: Feature Of Interest
subclass of: Restriction
  on property: has result
  all values from: Result
subclass of: Restriction
  on property: made by sensor
  all values from: Sensor
subclass of: Restriction
  on property: observed property
  all values from: Observable Property
subclass of: Restriction
  on property: used procedure
  all values from: Procedure
subclass of: Restriction
  on property: was originated by
  all values from: Stimulus
subclass of: Restriction
  on property: has result
  min cardinality: 1
subclass of: Restriction
  on property: has feature of interest
  cardinality: 1
subclass of: Restriction
  on property: made by sensor
  cardinality: 1
subclass of: Restriction
  on property: observed property
  cardinality: 1
subclass of: Restriction
  on property: phenomenon time
  cardinality: 1
subclass of: Restriction
  on property: was originated by
  cardinality: 1
subclass of: Restriction
  on property: result time
  cardinality: 1
comment: Act of carrying out an (Observation) Procedure to estimate or calculate a value of a property of a FeatureOfInterest. Links to a Sensor to describe what made the Observation and how; links to an ObservableProperty to describe what the result is an estimate of, and to a FeatureOfInterest to detail what that property was associated with.
example: The activity of estimating the intensity of an Earthquake using the Mercalli intensity scale is an Observation as is measuring the moment magnitude, i.e., the energy released by said earthquake.

Platform
type: Class
subclass of: Restriction
  on property: hosts
  all values from: System
subclass of: Restriction
  on property: in deployment
  all values from: Deployment
comment: A Platform is an entity that hosts other entities, particularly Sensors, Actuators, Samplers, and other Platforms.
example: A post, buoy, vehicle, ship, aircraft, satellite, cell-phone, human or animal may act as platforms for (technical or biological) sensors or actuators.

Procedure
type: Class
subclass of: Restriction
  on property: has input
  all values from: Input
subclass of: Restriction
  on property: has output
  all values from: Output
subclass of: Restriction
  on property: implemented by
  all values from: System
comment: A workflow, protocol, plan, algorithm, or computational method specifying how to make an Observation, create a Sample, or make a change to the state of the world (via an Actuator). A Procedure is re-usable, and might be involved in many Observations, Samplings, or Actuations. It explains the steps to be carried out to arrive at reproducible results.
example: The measured wind speed differs depending on the height of the sensor above the surface, e.g., due to friction. Consequently, procedures for measuring wind speed define a standard height for anemometers above ground, typically 10m for meteorological measures and 2m in Agrometeorology. This definition of height, sensor placement, and so forth are defined by the Procedure.
note: Many observations may be created via the same Procedure, the same way as many tables are assembled using the same instructions (as information objects, not their concrete realization).

Result
type: Class
subclass of: Restriction
  on property: is result of
  min cardinality: 1
comment: The Result of an Observation, Actuation, or act of Sampling. To store an observation's simple result value one can use the hasSimpleResult property.
example: The value 20 as the height of a certain tree together with the unit, e.g., Meter.

Sample
type: Class
subclass of: Feature Of Interest
subclass of: Result
subclass of: Restriction
  on property: is result of
  all values from: Sampling
subclass of: Restriction
  on property: is sample of
  all values from: Feature Of Interest
subclass of: Restriction
  on property: is result of
  min cardinality: 1
subclass of: Restriction
  on property: is sample of
  min cardinality: 1
comment: A Sample is the result from an act of Sampling.
comment: Feature which is intended to be representative of a FeatureOfInterest on which Observations may be made.
comment: Physical samples are sometimes known as 'specimens'.
comment: Samples are artifacts of an observational strategy, and have no significant function outside of their role in the observation process. The characteristics of the samples themselves are of little interest, except perhaps to the manager of a sampling campaign. A Sample is intended to sample some FatureOfInterest, so there is an expectation of at least one isSampleOf property. However, in some cases the identity, and even the exact type, of the sampled feature may not be known when observations are made using the sampling features.
example: A 'station' is essentially an identifiable locality where a sensor system or Procedure may be deployed and an observation made. In the context of the observation model, it connotes the 'world in the vicinity of the station', so the observed properties relate to the physical medium at the station, and not to any physical artifact such as a mooring, buoy, benchmark, monument, well, etc.
example: A statistical sample is often designed to be characteristic of an entire population, so that observations can be made regarding the sample that provide a good estimate of the properties of the population.
note: A transient sample, such as a ships-track or flight-line, might be identified and described, but is unlikely to be revisited exactly.

Sampler
type: Class
subclass of: System
subclass of: Restriction
  on property: made sampling
  all values from: Sampling
subclass of: Restriction
  on property: implements
  min cardinality: 1
comment: A device that is used by, or implements, a Sampling Procedure to create or transform one or more samples.
example: A ball mill, diamond drill, hammer, hypodermic syringe and needle, image Sensor or a soil auger can all act as sampling devices (i.e., be Samplers). However, sometimes the distinction between the Sampler and the Sensor is not evident, as they are packaged as a unit. A Sampler need not be a physical device.

Sampling
type: Class
subclass of: Restriction
  on property: has feature of interest
  all values from: Feature Of Interest
subclass of: Restriction
  on property: has result
  all values from: Sample
subclass of: Restriction
  on property: made by sampler
  all values from: Sampler
subclass of: Restriction
  on property: used procedure
  all values from: Procedure
subclass of: Restriction
  on property: has result
  min cardinality: 1
subclass of: Restriction
  on property: has feature of interest
  cardinality: 1
subclass of: Restriction
  on property: made by sampler
  cardinality: 1
subclass of: Restriction
  on property: result time
  cardinality: 1
comment: An act of Sampling carries out a sampling Procedure to create or transform one or more samples.
example: Crushing a rock sample in a ball mill.
example: Digging a pit through a soil sequence.
example: Dividing a field site into quadrants.
example: Drawing blood from a patient.
example: Drilling an observation well.
example: Establishing a station for environmental monitoring.
example: Registering an image of the landscape.
example: Selecting a subset of a population.
example: Sieving a powder to separate the subset finer than 100-mesh.
example: Splitting a piece of drill-core to create two new samples.
example: Taking a diamond-drill core from a rock outcrop.

Sensor
type: Class
subclass of: System
subclass of: Restriction
  on property: made observation
  all values from: Observation
subclass of: Restriction
  on property: observes
  all values from: Observable Property
subclass of: Restriction
  on property: detects
  all values from: Stimulus
subclass of: Restriction
  on property: implements
  min cardinality: 1
comment: Device, agent (including humans), or software (simulation) involved in, or implementing, a Procedure. Sensors respond to a stimulus, e.g., a change in the environment, or input data composed from the results of prior Observations, and generate a Result. Sensors can be hosted by Platforms.
example: Accelerometers, gyroscopes, barometers, magnetometers, and so forth are Sensors that are typically mounted on a modern smart phone (which acts as Platform). Other examples of sensors include the human eyes.

Deployment
type: Class
subclass of: Restriction
  on property: deployed on platform
  all values from: Platform
subclass of: Restriction
  on property: deployed system
  all values from: System
subclass of: Restriction
  on property: for property
  all values from: Property
comment: Describes the Deployment of one or more Systems for a particular purpose. Deployment may be done on a Platform.
example: For example, a temperature Sensor deployed on a wall, or a whole network of Sensors deployed for an Observation campaign.

Input
type: Class
subclass of: Restriction
  on property:
    inverse of: has input
  all values from: Procedure
subclass of: Restriction
  on property:
    inverse of: has input
  min cardinality: 1
comment: Any information that is provided to a Procedure for its use.

Output
type: Class
subclass of: Restriction
  on property:
    inverse of: has output
  all values from: Procedure
subclass of: Restriction
  on property:
    inverse of: has output
  min cardinality: 1
comment: Any information that is reported from a Procedure.

Property
type: Class
subclass of: Restriction
  on property: is property of
  all values from: Feature Of Interest
comment: A quality of an entity. An aspect of an entity that is intrinsic to and cannot exist without the entity.

Stimulus
type: Class
subclass of: Restriction
  on property: is proxy for
  all values from: Observable Property
subclass of: Restriction
  on property:
    inverse of: detects
  all values from: Sensor
subclass of: Restriction
  on property:
    inverse of: was originated by
  all values from: Observation
comment: An event in the real world that 'triggers' the Sensor. The properties associated to the Stimulus may be different to the eventual observed ObservableProperty. It is the event, not the object, that triggers the Sensor.

System
type: Class
subclass of: Restriction
  on property: is hosted by
  all values from: Platform
subclass of: Restriction
  on property: has deployment
  all values from: Deployment
subclass of: Restriction
  on property: has subsystem
  all values from: System
subclass of: Restriction
  on property: implements
  all values from: Procedure
subclass of: Restriction
  on property:
    inverse of: has subsystem
  all values from: System
comment: System is a unit of abstraction for pieces of infrastructure that implement Procedures. A System may have components, its subsystems, which are other systems.

Agent
type: Class

Organization
type: Class

Person
type: Class

complex event
type: Class
subclass of: Describes any type of event that can occur in a smart environment. This representation is able to also define an activity whose recognition is based on realization of its preconditions.
subclass of: Restriction
  on property: has precondition
  some values from: event condition
comment: Describes an event based on its precoditions that can per se involve different events (e.g., "watching tv" happens when "the tv is switched on" and "someone is sitting on the couch").

Describes any type of event that can occur in a smart environment. This representation is able to also define an activity whose recognition is based on realization of its preconditions.
type: Class
subclass of: Event
subclass of: Restriction
  on property: has participant
  some values from: agent
subclass of: Restriction
  on property: is observable at
  some values from: interval
subclass of: Restriction
  on property: has participant
  all values from: Agent
label: event

event condition
type: Class
subclass of: Situation
subclass of: Restriction
  on property: is observable at
  some values from: temporal distance
subclass of: Restriction
  on property: is precondition of
  some values from: complex event
subclass of: Restriction
  on property: is setting for
  some values from: Situation
subclass of: Restriction
  on property: is setting for
  some values from: situation
comment: Describes a precondition for a complex event needed to be recognized within specific temporal distance from the timestamp at which the complex event is recognized.

manifestation
type: Class
subclass of: Describes any type of event that can occur in a smart environment. This representation is able to also define an activity whose recognition is based on realization of its preconditions.
subclass of: Restriction
  on property: is event included in
  some values from: Situation
subclass of: Restriction
  on property: is event included in
  some values from: situation
comment: Describes the occurance/realization of a specific situation of a feature of interest (for its specific property) which can be directly captured from sensor data ("the tv is switched on"),

spatial object
type: Class
subclass of: Feature
subclass of: Restriction
  on property: has geometry
  some values from: Geometry
subclass of: Restriction
  on property: has spatial relation
  some values from: spatial object
comment: Describes any physcical object in a smart environment that has a geometry.

DataReceiverNode
type: Class
subclass of: node
subclass of: Restriction
  on property: receivesDataFrom
  some values from: DataSenderNode
comment: Decsribes a node in a network that receives data from sensors,

DataSenderNode
type: Class
subclass of: node
subclass of: Restriction
  on property: sendsDataTo
  some values from: DataReceiverNode
comment: Decsribes a node as part of a nore station that contributes sending the data read by sensors.

deployment
type: Class
subclass of: Deployment
subclass of: Restriction
  on property: deployed on platform
  some values from: smart environment
subclass of: Restriction
  on property: deployed system
  some values from: network
comment: Describes the deployment of a network in a smart environment.

network
type: Class
subclass of: System
subclass of: Restriction
  on property: has deployment
  some values from: deployment
subclass of: Restriction
  on property: has subsystem
  some values from: node station
comment: A network which is a collection of Nodes

network module
type: Class
subclass of: System
comment: Describes the network modules in the form of node stations and nodes contributing in sending and receiving data within a sensor network in the context of a smart environment.

node
type: Class
subclass of: network module
comment: Decsribes a node in a network that either sends or receives the data read by a sensor.

node station
type: Class
subclass of: network module
subclass of: Restriction
  on property: is hosted by
  some values from: node holder
subclass of: Restriction
  on property: has subsystem
  all values from: node
comment: Decsribes a module in a network that contains nodes, batteries, etc.

ReceiverNodeStation
type: Class
subclass of: node station
subclass of: Restriction
  on property: has subsystem
  all values from: DataReceiverNode
comment: Describes a node station which holds a data receiver node as its part (sub-system)

SenderNodeStation
type: Class
subclass of: node station
subclass of: Restriction
  on property: has subsystem
  some values from: Sensor
subclass of: Restriction
  on property: has subsystem
  some values from: sensor
subclass of: Restriction
  on property: has subsystem
  all values from: DataSenderNode
comment: Describes a node station which is assumed to contain both a data sender node and also sensing devices (sensors)

agent
type: Class
subclass of: Agent
subclass of: mobile object
subclass of: Restriction
  on property: is participant in
  some values from: Describes any type of event that can occur in a smart environment. This representation is able to also define an activity whose recognition is based on realization of its preconditions.
subclass of: Restriction
  on property: is participant in
  all values from: Event
comment: Describes any agent (e.g., human, pet, etc) in a smart environment that can participate in an event or activity.

Location
type: Class
subclass of: Observable Property
subclass of: Restriction
  on property: is property of
  some values from: mobile object

mobile object
type: Class
subclass of: object
subclass of: Restriction
  on property: has property
  some values from: Location
comment: Describes any type of physical object that has the possibility to move in a smart environment.

node holder
type: Class
subclass of: Platform
subclass of: object
subclass of: Restriction
  on property: hosts
  some values from: node station
comment: Describes any object in a smart environment, which is used to host network modules such as nodes or node stations.

object
type: Class
subclass of: Physical object
subclass of: spatial object
subclass of: Restriction
  on property: has location
  some values from: Physical place
subclass of: Restriction
  on property: has location
  some values from: section
comment: Describes any type of physical object in a smart environment.

smart object
type: Class
subclass of: Feature Of Interest
subclass of: object
comment: Describes any physical object in a smart environment which is a feature of interest for an observation process.

section
type: Class
subclass of: Physical place
subclass of: spatial object
subclass of: Restriction
  on property: is location of
  some values from: object
subclass of: Restriction
  on property: is part of
  some values from: smart environment
subclass of: Restriction
  on property: is location of
  all values from: Physical object
comment: Sections belonging to a smart environment (e.g., kitchen, livingroom, etc., in case of a smart home)

smart environment
type: Class
subclass of: Physical place
subclass of: Platform
subclass of: Restriction
  on property: has part
  some values from: section
subclass of: Restriction
  on property: in deployment
  some values from: deployment
comment: Represent a smart environment as a physical place which is also supposed to be a platform for a sensor network deployment.

configuration procedure
type: Class
subclass of: Procedure
subclass of: Restriction
  on property: implemented by
  some values from: sensor
comment: Descibes a procedure required to configure a sensor to be used for an observation process in a smart environment context. This configuration can include both hardware ans software setup related to sensors such as the sampling rate, etc.
example: Descibes a procedure required to configure a sensor to be used for an observation process in a smart environment context. This configuration can include both hardware ans software setup related to sensors such as the sampling rate, etc.

observation
type: Class
subclass of: Observation
subclass of: Restriction
  on property: made by sensor
  some values from: sensor
comment: Using a Sensor it describes the process of observing a property of a feature of interest.

sensor
type: Class
subclass of: Sensor
subclass of: Restriction
  on property: made observation
  some values from: observation
subclass of: Restriction
  on property: implements
  some values from: configuration procedure
comment: Descibes a device that with a specific set of configuration is able to implements an observation process in order to monitor a property of a feature of interest in a smart environment.

situation
type: Class
subclass of: Situation
subclass of: Restriction
  on property: is expressed by
  some values from: Feature Of Interest
subclass of: Restriction
  on property: is expressed by
  some values from: state
subclass of: Restriction
  on property: for property
  some values from: Property
comment: Describes a specific situation in the context of smart environments in the form of a feature of interest, its property and a specific state that express it.
example: e.g., stove-on, tv-on, sofa-used (i.e., the pressure (as the property of the sofa) on the sofa is realized).

state
type: Class
subclass of: Information object
subclass of: Restriction
  on property: expresses
  some values from: situation
comment: Describes a specific state of a feature of interest regardless of how it has been realized.
example: on, off, true, false, etc.

instant
type: Class
subclass of: Time instant
subclass of: temporal entity
subclass of: Restriction
  on property: in XSD Date-Time-Stamp
  qualified cardinality: 1
  on data range: sello de tiempo
comment: Describes a temporal instant specifiying a specific datetimestamp

interval
type: Class
subclass of: Time interval
subclass of: temporal entity
subclass of: Restriction
  on property: has beginning
  qualified cardinality: 1
  on class: instant
subclass of: Restriction
  on property: has duration
  qualified cardinality: 1
  on class: time duration
comment: Describes a temporal entity with an extent or duration with a known starting time.

temporal distance
type: Class
subclass of: temporal entity
subclass of: Restriction
  on property: before
  some values from: instant
subclass of: Restriction
  on property: has duration
  qualified cardinality: 2
  on class: time duration
comment: Describes a temporal distance relatively set to a given time instant. The distance is specified using two separate temporal durations both ending with the given time instant. The object property 'before' indicates that the distance is temporaly behind the time instant as the target time.

temporal entity
type: Class
equivalent class: Class
  union of: instant
  union of: interval
  union of: temporal distance
subclass of: Temporal entity
comment: Describes a temporal entity that can represent a single time instant, a time interval, or a temporal distance.

time duration
type: Class
subclass of: duración de tiempo
comment: Describes time duration in the form of a numeric value indicating its length, and a temporal unit type.

Friday
type: NamedIndividual
type: Day of week
preferred label: Freitag @de
preferred label: Piątek @pl
preferred label: Sexta-feira @pt
preferred label: Vendredi @fr
preferred label: Venerdì @it
preferred label: Viernes @es
preferred label: Vrijdag @nl
preferred label: Пятница @ru
preferred label: الجمعة @ar
preferred label: 星期五 @zh
preferred label: 金曜日 @ja

Monday
type: NamedIndividual
type: Day of week
preferred label: Lundi @fr
preferred label: Lunedì @it
preferred label: Lunes @es
preferred label: Maandag @nl
preferred label: Montag @de
preferred label: Poniedziałek @pl
preferred label: Segunda-feira @pt
preferred label: Понедельник @ru
preferred label: الاثنين @ar
preferred label: 星期一 @zh
preferred label: 月曜日 @ja

Saturday
type: NamedIndividual
type: Day of week
preferred label: Sabato @it
preferred label: Samedi @fr
preferred label: Samstag @de
preferred label: Sobota @pl
preferred label: Sábado @es
preferred label: Zaterdag @nl
preferred label: Суббота @ru
preferred label: السبت @ar
preferred label: 土曜日 @ja
preferred label: 星期六 @zh

Sunday
type: NamedIndividual
type: Day of week
preferred label: Dimanche @fr
preferred label: Domenica @it
preferred label: Domingo @es
preferred label: Niedziela @pl
preferred label: Sonntag @de
preferred label: Zondag @nl
preferred label: Воскресенье @ru
preferred label: الأحد (يوم) @ar
preferred label: 日曜日 @ja
preferred label: 星期日 @zh

Thursday
type: NamedIndividual
type: Day of week
preferred label: Czwartek @pl
preferred label: Donderdag @nl
preferred label: Donnerstag @de
preferred label: Giovedì @it
preferred label: Jeudi @fr
preferred label: Jueves @es
preferred label: Quinta-feira @pt
preferred label: Четверг @ru
preferred label: الخميس @ar
preferred label: 星期四 @zh
preferred label: 木曜日 @ja

Tuesday
type: NamedIndividual
type: Day of week
preferred label: Dienstag @de
preferred label: Dinsdag @nl
preferred label: Mardi @fr
preferred label: Martedì @it
preferred label: Martes @es
preferred label: Terça-feira @pt
preferred label: Wtorek @pl
preferred label: Вторник @ru
preferred label: الثلاثاء @ar
preferred label: 星期二 @zh
preferred label: 火曜日 @ja

Wednesday
type: NamedIndividual
type: Day of week
preferred label: Mercoledì @it
preferred label: Mercredi @fr
preferred label: Mittwoch @de
preferred label: Miércoles @es
preferred label: Quarta-feira @pt
preferred label: Woensdag @nl
preferred label: Środa @pl
preferred label: Среда @ru
preferred label: الأربعاء @ar
preferred label: 星期三 @zh
preferred label: 水曜日 @ja

Day (unit of temporal duration)
type: NamedIndividual
type: Temporal unit
days duration: 1
hours duration: 0
minutes: 0
months duration: 0
seconds duration: 0
weeks duration: 0
years duration: 0
preferred label: Tag @de
preferred label: dag @nl
preferred label: day
preferred label: dia @pt
preferred label: doba @pl
preferred label: día @es
preferred label: giorno @it
preferred label: jour @fr
preferred label: يوماً ما @ar
preferred label: ある日 @jp
preferred label: 一天 @zh
preferred label: 언젠가 @kr

один час"@ru
type: NamedIndividual
type: Temporal unit
days duration: 0
hours duration: 1
minutes: 0
months duration: 0
seconds duration: 0
weeks duration: 0
years duration: 0
label: Hour (unit of temporal duration)
preferred label: Stunde @de
preferred label: godzina @pl
preferred label: heure @fr
preferred label: hora @es
preferred label: hour
preferred label: ora @it
preferred label: uur @nl
preferred label: ساعة واحدة @ar
preferred label: 一小時 @zh
preferred label: 一時間 @jp
preferred label: 한 시간 @kr

Minute (unit of temporal duration)
type: NamedIndividual
type: Temporal unit
days duration: 0
hours duration: 0
minutes: 1
months duration: 0
seconds duration: 0
weeks duration: 0
years duration: 0
preferred label: Minute @de
preferred label: minuta @pl
preferred label: minute
preferred label: minuto @es
preferred label: minuut @nl
preferred label: одна минута @ru
preferred label: دقيقة واحدة @ar
preferred label: 一分 @jp
preferred label: 等一下 @zh
preferred label: 분 @kr

Month (unit of temporal duration)
type: NamedIndividual
type: Temporal unit
days duration: 0
hours duration: 0
minutes: 0
months duration: 1
seconds duration: 0
weeks duration: 0
years duration: 0
preferred label: Monat @de
preferred label: maand @nl
preferred label: mes @es
preferred label: mese @it
preferred label: miesiąc @pl
preferred label: mois @fr
preferred label: month
preferred label: один месяц @ru
preferred label: شهر واحد @ar
preferred label: 一か月 @jp
preferred label: 一個月 @zh
preferred label: 한달 @kr

Second (unit of temporal duration)
type: NamedIndividual
type: Temporal unit
days duration: 0
hours duration: 0
minutes: 0
months duration: 0
seconds duration: 1
weeks duration: 0
years duration: 0
preferred label: Sekunde @de
preferred label: Sekundę @pl
preferred label: second
preferred label: seconde @fr
preferred label: secondo @it
preferred label: segundo @es
preferred label: ثانية واحدة @ar
preferred label: 一秒 @jp
preferred label: 일초 @kr

Week (unit of temporal duration)
type: NamedIndividual
type: Temporal unit
days duration: 0
hours duration: 0
minutes: 0
months duration: 0
seconds duration: 0
weeks duration: 1
years duration: 0
preferred label: Woche @de
preferred label: semaine @fr
preferred label: semana @es
preferred label: settimana @it
preferred label: tydzień @pl
preferred label: week
preferred label: одна неделя @ru
preferred label: سبوع واحد @ar
preferred label: 一周 @zh
preferred label: 一週間 @jp
preferred label: 일주일 @kr

Year (unit of temporal duration)
type: NamedIndividual
type: Temporal unit
days duration: 0
hours duration: 0
minutes: 0
months duration: 0
seconds duration: 0
weeks duration: 0
years duration: 1
preferred label: 1 년 @kr
preferred label: 1年 @jp
preferred label: Jahr @de
preferred label: an @fr
preferred label: anno @it
preferred label: ano @pt
preferred label: jaar @nl
preferred label: rok @pl
preferred label: un año @es
preferred label: year
preferred label: один год @ru
preferred label: سنة واحدة @ar
preferred label: 一年 @zh

Matthew Perry
type: Person
affiliation: Oracle Corporation

John Herring
type: Person
affiliation: Oracle Corporation

Nicholas J. Car
type: Person
affiliation: Australian National University
affiliation: SURROUND Australia Pty Ltd

Joseph Abhayaratna
type: Person
affiliation: Geoscape Australia

Timo Homburg
type: Person
affiliation: Mainz University Of Applied Sciences

Simon J D Cox
type: Person
affiliation: CSIRO Australia

Frans Knibbe
type: Person

Mathias Bonduel
type: Person
affiliation: KU Leuven
affiliation: Neanex Technologies

W3C/OGC Spatial Data on the Web Working Group
type: Agent

W3C/OGC Spatial Data on the Web Working Group
type: Agent

Open Geospatial Consortium
type: Organization

W3C/OGC Spatial Data on the Web Working Group
type: Agent

W3C/OGC Spatial Data on the Web Working Group
type: Agent

pattern: ---(0[1-9]|[1-9][0-9])(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?

qualified cardinality: 2

pattern: --(0[1-9]|1[0-9]|20)(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?

pattern: -?([1-9][0-9]{3,}|0[0-9]{3})(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?

John Herring
type: Person
affiliation: Oracle Corporation

Nicholas J. Car
type: Person
affiliation: Australian National University
affiliation: SURROUND Australia Pty Ltd

Joseph Abhayaratna
type: Person
affiliation: Geoscape Australia

Timo Homburg
type: Person
affiliation: Mainz University Of Applied Sciences

Simon J D Cox
type: Person
affiliation: CSIRO Australia

Frans Knibbe
type: Person

Mathias Bonduel
type: Person
affiliation: KU Leuven
affiliation: Neanex Technologies

W3C/OGC Spatial Data on the Web Working Group
type: Agent

W3C/OGC Spatial Data on the Web Working Group
type: Agent

Open Geospatial Consortium
type: Organization