W3C/OGC Spatial Data on the Web Working Group
An RDF/OWL vocabulary for representing spatial information
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.
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.
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/
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.
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.
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.
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).
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.
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/).
Copyright © 2006-2017 W3C, OGC. W3C and OGC liability, trademark and document use rules apply.
OGC GeoSPARQL - A Geographic Query Language for RDF Data OGC 11-052r5
Semantic Sensor Network Ontology
Sensor, Observation, Sample, and Actuator (SOSA) Ontology
Smart Environment Event Ontology Pattern
Smart Environment Geometry Ontology Pattern
Smart Environment Network Ontology Pattern
Smart Environment Object Ontology Pattern
Smart Environment Place Ontology Pattern
Smart Environment Sensing Ontology Pattern
Smart Environment Situation Ontology Pattern
Smart Environment Time Ontology Pattern
se-event
se-geometry
se-network
se-sensing
se-situ
se-time
How many and what sections are there in a smart environment?
What are node holders, in other words, which objects are used as the holder of sensors in a smart environment?
What are smart objects, in other words, which objects are the interest of an observation process?
What are the feature of interests considered within an observation proces?
What are the possible states of the feature of interests (objects under the observation process) in a smart environment?
What are the preconditions of a complex event? And what is the temporal distance between a complex event and its preconditions?
What are the spatial relations among objects or sections in a smart environment?
What are the spatial/directional relations between sections or between sections and objects in an environment?
What is the confuguration (e.g.,, sampling rate) set for a given sensor?
What is the node receiving the data from a giveb sensor?
What is the output (result) of a sensing process?
What is the temporal distance between two specific time steps?
What is the time interval between two specific timestamps in the form of dates?
What sensors make a sensing (observation) process?
When does an Event occur? (Dul:TimeInterval)
Where are the locations of objects in an environment?
Which property of an object (i.e, feature of interest) is used to conceptualize a situation?
Which situation (including a feature of interest; its property and its state) has been captured in the form of a manifestation event?
Which types of nodes are available in a network?
Who has participated in a given event? (Dul:Agent)
We can quantitavely represent temporal distances through an observation process for different purposes . These purposes include definition of an event in terms of its preconditions whose occurance timestamp is within a specific temporal distance with that of the event.
The ontology pattern Time represents temporal entities in the form of Instant, Interval and Temporal Distance (for example the relative temporal relations between an event and its preconditions.) in the context of smart environments.
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.
This pattern is used to represent events in the context of smart environments. An event in this pattern is represented in the form of either a Manifestation or a Complex Event, where a manifestation represents the occurance of a specific situation of an object which can be directly captured from sensor data ("the tv is switched on"), whereas a complex event is defined based on its precoditions that can involve different events (e.g., "watching tv" happens when "the tv is switched on" and "someone is sitting on the couch"). The precondition of a complex event is represented in the form of a situation (DUL:Situation) which indicates proper temporal distances between a complex event and, the events involved in its definition.
To represent a SmartHome as a place (specialization of http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalPlace) which contains a number of sections (other physical places) and is also seen as a platform (e.g. a platform for a sensor network).
Please report any errors to the W3C Spatial Data on the Web Working Group via the SDW WG Public List public-sdw-wg@w3.org
The DOLCE+DnS Ultralite ontology. It is a simplification of some parts of the DOLCE Lite-Plus library (cf. http://www.ontologydesignpatterns.org/ont/dul/DLP397.owl). Main aspects in which DOLCE+DnS Ultralite departs from DOLCE Lite-Plus are the following: - The names of classes and relations have been made more intuitive - The DnS-related part is closer to the newer 'constructive DnS' ontology (http://www.ontologydesignpatterns.org/ont/dul/cDnS.owl). - Temporal and spatial relations are simplified - Qualities and regions are more relaxed than in DOLCE-Full: they can be used as attributes of any entity; an axiom states that each quality has a region - Axiomatization makes use of simpler constructs than DOLCE Lite-Plus - The architecture of the ontology is pattern-based, which means that DOLCE+DnS Ultralite is also available in modules, called 'content ontology design patterns', which can be applied independently in the design of domain ontologies (cf. http://www.ontologydesignpatterns.org). If many modules are needed in a same ontology project, it is anyway useful to use this integrated version. The final result is a lightweight, easy-to-apply foundational ontology for modeling either physical or social contexts. Several extensions of DOLCE+DnS Ultralite have been designed: - Information objects: http://www.ontologydesignpatterns.org/ont/dul/IOLite.owl - Systems: http://www.ontologydesignpatterns.org/ont/dul/SystemsLite.owl - Plans: http://www.ontologydesignpatterns.org/ont/dul/PlansLite.owl - Legal domain: http://www.ontologydesignpatterns.org/ont/dul/CLO/CoreLegal.owl - Lexical and semiotic domains: http://www.ontologydesignpatterns.org/ont/lmm/LMM_L2.owl - DOLCE-Zero: http://www.ontologydesignpatterns.org/ont/d0.owl is a commonsense-oriented generalisation of some top-level classes, which allows to use DOLCE with tolerance against ambiguities like abstract vs. concrete information, locations vs. physical artifacts, event occurrences vs. event types, events vs. situations, qualities vs. regions, etc.; etc.
This pattern relies on both the SSN ontology and DUL in order to represent an object in the context of a smart environment. Using this model we categorize the objects in to two groups of Smart Object and NodeHolder. Due to usual difficulties to install sensors in a smart environment it is common that some other objects (i.e. NodeHolder) are used to hosts sensors so as to observe the situation of other objects (i.e. SmartObject). Using this pattern we are able to diffrentiate between these two types of objects.
This pattern relies on the SSN ontology and represents sensors and the other modules needed to deploy a network in a smart environment.
This pattern represents the spatial structure of the smart environment in terms of its sections (e.g., rooms in case of a smart home) and also the location of pgysical objects. This pattern uses the Smart Environment Geometry pattern, DULCE and SSN ontologies.
OWL-Time
Tiempo en OWL
Created by Aldo Gangemi as both a simplification and extension of DOLCE and Descriptions and Situations ontologies.
In 3.2, the links between instances of Region or Parameter, and datatypes have been revised and made more powerful, in order to support efficient design patterns for data value modelling in OWL1.0. Also, the names of the related properties have been changed in order to make them more intuitive. Furthermore, a large comment field has been added to the 'expresses' object property, in order to clarify some issues about the many interpretations. In 3.3, the relation between regions, parameters, and datatypes has been still improved. In 3.5, the person-related classes have been refactored: Person in 3.4 is now SocialPerson, to avoid confusion with commonsense intuition; Person is now the union of social persons and humans, therefore being a subclass of Agent. In 3.6, other fixes on universal restriction involving expresses. Also added the property 'isConstraintFor' between parameters and entities. Moved the properties: 'assumes' and 'adopts' to the new module: http://www.ontologydesignpatterns.org/ont/dul/Conceptualization.owl. In 3.7, some fixes on the names of classes and properties related to FormalEntity; created a new separate module for general universal restrictions (DULGCI.owl). In 3.8, more fixes on the interface to formal entities and links to IOLite.owl. In 3.9, some naming and comment fixes. In 3.10, removed cardinality restriction from hasPart and isPartOf restrictions (changed to hasComponent and isComponentOf), for OWL(DL) compatibility. Also enlarged the range of includesAgent to contain both social and physical agents, and of conceptualizes universal restriction on agents, to include all social objects. In 3.11, some more subproperty axioms have been introduced, and all elements have got English labels. In 3.12, added some classes to map some old DolceLitePlus classes that were used to align OntoWordNet. In 3.13, added the LocalConcept class to express a Concept that cannot be used in a Description different from the one that defines it. Also updated some comments. In 3.14, added some comments. In 3.15, removed some owl:disjointWith axioms relating Collection to InformationObject, Description, Situation, and SocialAgent. The rationale for doing that is to allow less strict constraints on domain relations involving collections that can be also conceived as descriptions, situations, social agents, or information objects; for example: a collection of sentences from a text (an information object) that are ranked with a relevance criterion can be still considered a text. In 3.16, name of isActedBy changed to actsThrough, which is clearer. Also added SpatioTemporalRegion as constituted by a SpaceRegion and a TimeInterval. In 3.17, removed redundant universal axioms from Entity and other top classes. Fixed restrictions on FunctionalSubstance class, and comments in Design and Substance classes. In 3.18, removed subClassOf axiom from FunctionalSubstance to DesignedArtifact, created a new subclass of FunctionalSubstance, called DesignedSubstance, and created a subClassOf axiom from DesignedSubstance to DesignedArtifact. In 3.19, removed disjointness axiom between Concept and Collection (the same rationale applies as in 3.15 version. In 3.20, revised the comment for Quality, added InformationEntity as the superclass for InformationObject and InformationRealization (represented as the union of those classes). This is needed in many domain ontologies that do not need to distinguish between abstract and concrete aspects of information entities. One possible revision (not implemented here) would be to introduce the relations: expresses and isAbout with a broader domain:InformationEntity, and two more specific properties: abstractlyExpresses and isAbstractlyAbout. This last revision has not been implemented yet, since a large revision procedure should be carried out in order to check the impact of the revision on the existing DOLCE-DnS-Ultralite plugins. In 3.21, added comment to InformationEntity, and optimized representation of equivalence for InformationRealization. In 3.22, added comment to Personification. In 3.23, added associatedWith object property, and put all object properties as subproperties of it. In 3.24, removed hasProxy datatype property. In 3.25, generalized domain and range of hasComponent and isComponentOf. In 3.26, updated some comments in order to clarify or exemplify the concepts. In 3.27, added rdfs:isDefinedBy annotations for Linked Data browsers. In 3.28, broadened the universe of pre-/post-conditions to give room to events and states. In 3.29, added some properties to support DBpedia alignment: sameSettingAs (situational analogous to coparticipation), including relations originating e.g. from sharing kinship, ownership, or roleplaying situations. In 3.30, completed some domains and ranges (formerly owl:Thing, now dul:Entity), and added axiom: Organism subClassOf PhysicalAgent. In 3.31, added a restriction to Quality and one to Region in order to ensure the original DOLCE constraint of qualities being always associated with a region, and vice versa. These axioms do not however exclude a direct applicability of qualities or regions to any other entity. In 3.32, removed redundant union axioms and some restrictions, which spot a negative trade-off between expressivity and complexity. In 3.33, added the ObjectAggregate class, added two property chains for coparticipation and same situation setting, updated some comments, added an axiom to Transition. In 3.34, extended mereological support for parthood, introducing hasPropertPart (transitive) as a middle property between hasPart (transitive and reflexive) and hasComponent (asymmetric). This solution uses then "reflexive reduction" and "transitive reduction" design patterns (they allow to grant property characteristics through the superproperties, but not in the subproperties). Technically, mereology axioms would require that also hasProperPart be asymmetric, however a direct subproperty of an OWL non-simple property (hasPart) cannot be also asymmetric, hence the approximation. Added a n-ary parthood class in order to suggest an alternative pattern for time- (and space-)indexed part relations. In order to ensure that property characteristics hold also with parthood n-ary, a property chain is introduced which infers a direct dul:partOf property for each parthood individual. Added a dul:realizesSelfInformation propery in order to enable local reflexivity ('Self') axioms for all information realizations. In 4.0, some foundational changes are introduced. - Firstly, the temporally indexed versions of some properties are introduced as subclasses of Situation (following the n-ary relation pattern), so covering relations from DOLCE that were skipped because of their larger arity. - - Secondly, D&S's Situation class is extracted from DOLCE top-level distinctions (it used to be a subclass of SocialObject), put as a primitive class under Entity, and not disjoint from any other class. Since we are relaxing the semantics of Situation, this change is fully compatible with previous versions of DUL. The reason for the change is that it may sound counterintuitive (as many have noticed) to assume a descriptive commitment for situations, but not for events or states. In fact, D&S provides an epistemological commitment to an ontology, independently from its foundational distinctions. A situation operationalizes that epistemology, and it is better not to put it under any foundational distinction (event, object, fluent, etc.), leaving to the designer whether to use descriptions as epistemological lenses, and so generating a situation, or not. A consequence is that any entity, when 'framed' by (satisfying) a description, becomes a situation. We can still model entities as being in a situation's setting, and classified by a concept defined in a description. In 4.1, also the disjointness between Description and Concept has been dropped, in order to unify the projections of an intensional relation with its mereological dependencies. Until now, when a description d1 is part of another description d, we cannot model d1 as a concept defined or used by d, even though it is totally reasonable to consider it as such, i.e., playing a role in d. The impediment is due to the disjointness between being Description and Concept. By dropping that axiom, we can operate on descriptions and concepts more flexibly. A compositional property, hasInScope, is introduced to link situations that are 'diagonally' modelled through a description, e.g., when a situation s1 involves a description d1 (diagonal meta-level), which is satisfied by a situation s2, s1 hasInScope s2. Legal reasoning is a relevant example: a case in point (s2) may satisfy two legal norms (d1 and d2) that are conflicting according to a meta-norm d; d3 can be satisfied by a situation s that 'interprets' (involves) both d1 and d2 against s2. hence, s hasInScope s2. This may also happen wehen the two conflicting descriptions are satisfied by alternative situations sharing important elements, as in perspectival reasoning: the meta-description in this case has in scope both alternative situations. In 4.2, the disjointness between Information Object and either Description or Concept has been dropped because of the full dependence of non-agentive social objects from information artifacts.
New modular version of the SSN ontology. This ontology was originally developed in 2009-2011 by the W3C Semantic Sensor Networks Incubator Group (SSN-XG). For more information on the group's activities see: http://www.w3.org/2005/Incubator/ssn/. The ontology was revised and modularized in 2015-2017 by the W3C/OGC Spatial Data on the Web Working Group, see: https://www.w3.org/2015/spatial/wiki/Semantic_Sensor_Network_Ontology. In particular, (a) the scope is extended to include actuation and sampling; (b) the core concepts and properties are factored out into the SOSA ontology. The SSN ontology imports SOSA and adds formal axiomatization consistent with the text definitions in SOSA, and adds classes and properties to accommodate the scope of the original SSN ontology.
2016-06-15 - initial update of OWL-Time - modified to support arbitrary temporal reference systems.
2016-12-20 - adjust range of time:timeZone to time:TimeZone, moved up from the tzont ontology.
2016-12-20 - restore time:Year and time:January which were present in the 2006 version of the ontology, but now marked "deprecated".
2017-02 - intervalIn, intervalDisjoint, monthOfYear added; TemporalUnit subclass of TemporalDuration
2017-04-06 - hasTime, hasXSDDuration added; Number removed; all duration elements changed to xsd:decimal
Update of OWL-Time ontology, extended to support general temporal reference systems. Ontology engineering by Simon J D Cox
A textual serialization of a Discrete Global Grid (DGGS) Geometry object.
"<https://w3id.org/dggs/auspix> OrdinateList (R3234)"^^<http://www.opengis.net/ont/geosparql#dggsLiteral>
DGGS Literal
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
A GeoJSON serialization of a Geometry object.
GeoJSON Literal
A GML serialization of a Geometry object.
GML Literal
A KML serialization of a Geometry object.
KML Literal
A Well-known Text serialization of a Geometry object.
Well-known Text Literal
sello de tiempo
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.
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.
Día generalizado
Generalized day
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.
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.
Generalized month
Mes generalizado
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.
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.
Año generalizado
Generalized year
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.
acts for
agisce per
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
acts through
agisce mediante
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.
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'.
caratterizza
characterizes
A relation between a Concept and an Entity, e.g. the Role 'student' classifies a Person 'John'.
classifica
classifies
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.
conceptualizes
concettualizza
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
concretely expresses
esprime concretamente
A relation between two objects participating in a same Event; e.g., 'Vitas and Jimmy are playing tennis'.
co-participates with
copartecipa con
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'.
covers
ricopre
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'.
defines
definisce
A relation between a description and a role, e.g. the recipe for a cake defines the role 'ingredient'.
defines role
definisce il ruolo
A relation between a description and a task, e.g. the recipe for a cake defines the task 'boil'.
defines task
definisce il task
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.
describes
descrive
The intransitive follows relation. For example, Wednesday directly precedes Thursday. Directness of precedence depends on the designer conceptualization.
directly follows
segue direttamente
The intransitive precedes relation. For example, Monday directly precedes Tuesday. Directness of precedence depends on the designer conceptualization.
directly precedes
precede direttamente
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'.
esegue il task
executes task
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).
espande
expands
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.
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 the most common approach, lexicographers that write dictionaries, glossaries, etc. assume that the meaning of a term is a paraphrase (or 'gloss', or 'definition'). Another approach is provided by concept schemes like thesauri and lexicons, which assume that the meaning of a term is a 'concept', encoded as a 'lemma', 'synset', or 'descriptor'. Still another approach is that of psychologists and cognitive scientists, which often assume that the meaning of an information object is a concept encoded in the mind or cognitive system of an agent. A radically different approach is taken by social scientists and semioticians, who usually assume that meanings of an information object are spread across the communication practices in which members of a community use that object. Another approach that tackles the distributed nature of meaning is assumed by geometrical models of semantics, which assume that the meaning of an InformationObject (e.g. a word) results from the set of informational contexts (e.g. within texts) in which that object is used similarly. The logical approach to meaning is still different, since it assumes that the meaning of e.g. a term is equivalent to the set of individuals that the term can be applied to; for example, the meaning of 'Ali' is e.g. an individual person called Ali, the meaning of 'Airplane' is e.g. the set of airplanes, etc. Finally, an approach taken by structuralist linguistics and frame semantics is that a meaning is the relational context in which an information object can be applied; for example, a meaning of 'Airplane' is situated e.g. in the context ('frame') of passenger airline flights. These different approaches are not necessarily conflicting, and they mostly talk about different aspects of so-called 'semantics'. They can be summarized and modelled within DOLCE-Ultralite as follows (notice that such list is far from exhaustive): (1) Informal meaning (as for linguistic or commonsense semantics: a distinction is assumed between (informal) meaning and reference; see isAbout for an alternative pattern on reference) - Paraphrase meaning (as for lexicographic semantics). Here it is modelled as the expresses relation between instances of InformationObject and different instances of InformationObject that act as 'paraphrases' - Conceptual meaning (as for 'concept scheme' semantics). Here it is modelled as the expresses relation between instances of InformationObject and instances of Concept - Relational meaning (as for frame semantics). Here it is modelled as the expresses relation between instances of InformationObject and instances of Description - Cognitive meaning (as for 'psychological' semantics). Here it is modelled as the expresses relation between any instance of InformationObject and any different instance of InformationObject that isRealizedBy a mental, cognitive or neural state (depending on which theory of mind is assumed). Such states can be considered here as instances of Process (occurring in the mind, cognitive system, or neural system of an agent) - Cultural meaning (as for 'social science' semantics). Here it is modelled as the expresses relation between instances of InformationObject and instances of SocialObject (institutions, cultural paradigms, norms, social practices, etc.) - Distributional meaning (as for geometrical models of meaning). Here it is modelled as the expresses relation between any instance of InformationObject and any different instance of InformationObject that isFormallyRepresentedIn some (geometrical) Region (e.g. a vector space) (2) Formal meaning (as for logic and formal semantics: no distinction is assumed between informal meaning and reference, therefore between 'expresses' and 'isAbout', which can be used interchangeably) - Object-level formal meaning (as in the traditional first-order logic semantics). Here it is modelled as the expresses relation between an instance of InformationObject and an instance of Collection that isGroundingFor (in most cases) a Set; isGroundingFor is defined in the ontology: http://www.ontologydesignpatterns.org/ont/dul/IOLite.owl - Modal formal meaning (as in possible-world semantics). Here it is modelled as the expresses relation between an instance of InformationObject and an instance of Collection that isGroundingFor a Set, and which isPartOf some different instance of Collection that isGroundingFor a PossibleWorld This is only a first step to provide a framework, in which one can model different aspects of meaning. A more developed ontology should approach the problem of integrating the different uses of 'expresses', so that different theories, resources, methods can interoperate.
esprime
expresses
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
esprime il concetto
expresses concept
Generic distance relation between any Entity(s). E.g. Rome is far from Beijing, astronomy is far from necromancy.
far from
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.
follows
segue
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 common boundary
The hasProperPart relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the Object.
ha componente
has component
'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.
ha costituente
has constituent
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.
ha vincolo
has constraint
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
ha localizzazione
has location
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).
ha membro
has member
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.
ha parametro
has parameter
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.
ha parte
has part
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'.
ha come partecipante
has participant
Direct succession applied to situations. E.g., 'A postcondition of our Plan is to have things settled'.
ha postcondizione
has postcondition
Direct precedence applied to situations. E.g., 'A precondition to declare war against a foreign country is claiming to find nuclear weapons in it'.
ha precondizione
has precondition
Asymmetric (so including irreflexive) parthood.
has proper part
A relation between entities and qualities, e.g. 'Dmitri's skin is yellowish'.
ha qualità
has quality
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'.
ha attributo
has region
A relation between an object and a role, e.g. the person 'John' has role 'student'.
ha ruolo
has role
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.
has setting
è nel contesto di
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').
ha come obiettivo
has task
The generic relation between events and time intervals.
ha intervallo temporale
has time interval
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).
include azione
includes action
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).
include l'agente
includes agent
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).
include l'evento
includes event
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).
include l'oggetto
includes object
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.
include tempo
includes time
A relation between a Description and a SocialAgent, e.g. a Constitutional Charter introduces the SocialAgent 'PresidentOfRepublic'.
introduce
introduces
coinvolge agente
involves agent
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.
is about
si riferisce a
is action included in
è un'azione nel contesto di
is agent included in
è un agente nel contesto di
is agent involved in
è un agente coinvolto in
is characterized by
è caratterizzato da
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'.
is classified by
è classificato da
The asymmetric isProperPartOf relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the Object.
is component of
è componente di
is concept expressed by
è un concetto espresso da
A more generic relation holding between a Description and a Concept. In order to be used, a Concept must be previously definedIn another Description
is concept used in
è un concetto usato in
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'.
is conceptualized by
è concettualizzato da
is concretely expressed by
è espresso concretamente da
is constituent of
è costituente di
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
is constraint for
è un vincolo per
is covered by
è ricoperto da
is defined in
è definito in
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.
is described by
è descritto da
is event included in
è un evento nel contesto di
is executed in
è eseguito mediante
is expanded in
è espansa in
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.
is expressed by
è espresso da
is introduced by
è introdotto da
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
is location of
è una localizzazione di
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'.
is member of
è membro di
is object included in
è un oggetto nel contesto di
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
is observable at
è osservabile a
is parameter for
è un parametro per
The relation between a Parameter, e.g. 'MajorAge', and a Region, e.g. '>17 year'.
is parametrized by
è parametrizzato da
A relation between any entities, e.g. 'brain is a part of the human body'. See dul:hasPart for additional documentation.
is part of
è parte di
is participant in
è un partecipante a
Direct succession applied to situations. E.g., 'Taking some rest is a postcondition of my search for a hotel'.
is postcondition of
è postcondizione di
Direct precedence applied to situations. E.g., 'claiming to find nuclear weapons in a foreign country is a precondition to declare war against it'.
is precondition of
è precondizione di
See dul:hasProperPart for additional documentation.
is propert part of
is quality of
è una qualità di
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.
is realized by
è realizzato da
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.
is reference of
è il riferimento di
The relation between entities and information realizations, e.g. between Italy and a paper copy of the text of the Italian Constitution.
is reference of information realized by
è riferimento dell'informazione realizzata da
A relation between entities and regions, e.g. 'the color of my car is red'.
is region for
è una regione di
Any relation between concepts, e.g. superordinated, conceptual parthood, having a parameter, having a task, superordination, etc.
is related to concept
è associato al concetto
is related to description
è associata alla descrizione
A relation between a description and a role, e.g. the role 'Ingredient' is defined in the recipe for a cake.
is role defined in
è un ruolo definito in
A relation between an object and a role, e.g. 'student' is the role of 'John'.
is role of
è un ruolo di
A relation between a Situation and a Description, e.g. the execution of a Plan satisfies that plan.
is satisfied by
è soddisfatta da
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.
include
is setting for
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
is specialized by
è specializzato da
Direct succession applied to concepts. E.g. the role 'Officer' is subordinated to 'Director'.
is subordinated to
è subordinato a
Direct precedence applied to concepts. E.g. the role 'Executive' is superordinated to 'DepartmentManager'.
is superordinated to
è superordinato a
A relation between a description and a task, e.g. the task 'boil' is defined in a recipe for a cake.
is task defined in
è un task definito in
is task of
è un obiettivo per
is time included in
è un tempo nel contesto di
The generic relation between time intervals and events.
intervallo temporale di
is time interval of
is time of observation of
è il tempo di osservazione di
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.
is unified by
è unificato da
Generic distance relation between any Entity(s). E.g. Rome is near to Florence, astronomy is near to physics.
near to
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.
overlaps
sovrapposto a
The relation between a Parameter, e.g. 'MajorAgeLimit', and a Region, e.g. '18_year'. For a more data-oriented relation, see hasDataValue
parametrizes
parametrizza
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.
precede
precedes
realizes
realizza
realizes information about
realizza informazione che si riferisce a
This relation is a workaround to enable local reflexivity axioms (Self) working with non-simple properties; in this case, dul:realizesInformation About.
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).
is in the same setting as
è nella stessa situazione di
satisfies
soddisfa
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.
specializes
specializza
unifica
unifies
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.
usa il concetto
uses concept
The default Geometry to be used in spatial calculations. It is usually the most detailed Geometry.
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.
default geometry
States that the subject SpatialObject spatially contains the object SpatialObject. DE-9IM: T*TFF*FF*
contains
States that the subject SpatialObject is spatially covered by the object SpatialObject. DE-9IM: TFF*TFT**
covered by
States that the subject SpatialObject spatially covers the object SpatialObject. DE-9IM: T*TFT*FF*
States that the subject SpatialObject is spatially disjoint from the object SpatialObject. DE-9IM: FF*FF****
disjoint
States that the subject SpatialObject spatially equals the object SpatialObject. DE-9IM: TFFFTFFFT
equals
States that the subject SpatialObject is spatially inside the object SpatialObject. DE-9IM: TFF*FFT**
inside
States that the subject SpatialObject spatially meets the object SpatialObject. DE-9IM: FT******* ^ F**T***** ^ F***T****
meet
States that the subject SpatialObject spatially overlaps the object SpatialObject. DE-9IM: T*T***T**
overlap
The area of a Spatial Object.
has area
The minimum or smallest bounding or enclosing box of a given Feature.
has bounding box
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.
The arithmetic mean position of all the Geometry points of a given Feature.
has centroid
The target Geometry shall describe a point, for example an instance of http://www.opengis.net/ont/sf#Point.
has default geometry
A spatial representation for a given Feature.
has geometry
The length of a Spatial Object.
has length
The length of the perimeter of a Spatial Object.
has perimeter length
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.
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 size
The positional accuracy of the coordinates of a Geometry.
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 accuracy
The spatial resolution of a Geometry.
Spatial resolution specifies the level of detail of a Geometry. It the smallest distinguishable distance between spatially adjacent coordinates.
has spatial resolution
The volume of a three-dimensional Spatial Object.
has volume
States that the subject SpatialObject is spatially disjoint from the object SpatialObject. DE-9IM: FFTFFTTTT
disconnected
States that the subject SpatialObject spatially meets the object SpatialObject. DE-9IM: FFTFTTTTT
externally connected
States that the subject SpatialObject is spatially inside the object SpatialObject. DE-9IM: TFFTFFTTT
non-tangential proper part
States that the subject SpatialObject spatially contains the object SpatialObject. DE-9IM: TTTFFTFFT
non-tangential proper part inverse
States that the subject SpatialObject spatially overlaps the object SpatialObject. DE-9IM: TTTTTTTTT
partially overlapping
States that the subject SpatialObject is spatially covered by the object SpatialObject. DE-9IM: TFFTTFTTT
tangential proper part
States that the subject SpatialObject spatially covers the object SpatialObject. DE-9IM: TTTFTTFFT
tangential proper part inverse
States that the subject SpatialObject spatially contains the object SpatialObject. DE-9IM: T*****FF*
States that the subject SpatialObject spatially crosses the object SpatialObject. DE-9IM: T*T******
crosses
States that the subject SpatialObject is not spatially disjoint from the object SpatialObject. DE-9IM: T******** ^ *T******* ^ ***T***** ^ ****T****
intersects
States that the subject SpatialObject spatially touches the object SpatialObject. DE-9IM: FT******* ^ F**T***** ^ F***T****
touches
States that the subject SpatialObject is spatially within the object SpatialObject. DE-9IM: T*F**F***
within
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.
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.
after
después
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.
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.
antes
before
El día de la semana, cuyo valor es un miembro de la clase 'día de la semana'.
The day of week, whose value is a member of the class time:DayOfWeek
day of week
día de la semana
Beginning of a temporal entity
Comienzo de una entidad temporal.
has beginning
tiene principio
Beginning of a temporal entity.
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.
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.
has Date-Time description
tiene descripción fecha-hora
Duración de una entidad temporal, expresada como un valor escalado o un valor nominal.
Duration of a temporal entity, expressed as a scaled value or nominal value
has duration
tiene duración
Duración de una entidad temporal, evento o actividad, o cosa, expresada como un valor escalado.
Duration of a temporal entity, event or activity, or thing, expressed as a scaled value
Duración de una entidad temporal, expresada utilizando una descripción estructurada.
Duration of a temporal entity, expressed using a structured description
has duration description
tiene descripción de duración
End of a temporal entity.
Final de una entidad temporal.
has end
tiene fin
El sistema de referencia temporal utilizado por una posición temporal o descripción de extensión.
The temporal reference system used by a temporal position or extent description.
Temporal reference system used
sistema de referencia temporal utilizado
Duración de una entidad temporal.
Duration of a temporal entity.
has temporal duration
tiene duración temporal
Proporciona soporte a la asociación de una entidad temporal (instante o intervalo) a cualquier cosa.
Supports the association of a temporal entity (instant or interval) to any thing
has time
tiene tiempo
Característica arriesgada -añadida en la revisión del 2017 que no ha sido todavía utilizada de forma amplia.
Feature at risk - added in 2017 revision, and not yet widely used.
Posición de un instante, expresada utilizando una descripción estructurada.
Position of an instant, expressed using a structured description
en descripción de fecha-hora
in date-time description
Posición de un instante de tiempo.
Position of a time instant
Temporal position
posición temporal
Posición de un instante, expresada como una coordenada temporal o un valor nominal.
Position of an instant, expressed as a temporal coordinate or nominal value
Time position
posición de tiempo
Position of a time instant expressed as a TimePosition
An instant that falls inside the interval. It is not intended to include beginnings and ends of intervals.
Un instante que cae dentro del intervalo. Se asume que no es ni el principio ni el final de ningún intervalo.
has time instant inside
tiene instante de tiempo dentro
If a proper interval T1 is intervalAfter another proper interval T2, then the beginning of T1 is after the end of T2.
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.
interval after
intervalo posterior
If a proper interval T1 is intervalBefore another proper interval T2, then the end of T1 is before the beginning of T2.
Si un intervalo propio T1 está antes que otro intervalo propio T2, entonces el final de T1 está antes que el principio de T2.
interval before
intervalo anterior
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.
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.
interval contains
intervalo contiene
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.
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.
interval disjoint
intervalo disjunto
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.
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
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.
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.
interval during
intervalo durante
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.
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.
interval equals
intervalo igual
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.
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.
interval finished by
intervalo terminado por
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.
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.
interval finishes
intervalo termina
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.
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.
interval in
intervalo interior
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.
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
If a proper interval T1 is intervalMeets another proper interval T2, then the end of T1 is coincident with the beginning of T2.
Si un intervalo propio T1 se encuentra con otro intervalo propio T2, entonces el final de T1 coincide con el principio de T2.
interval meets
intervalo se encuentra
If a proper interval T1 is intervalMetBy another proper interval T2, then the beginning of T1 is coincident with the end of T2.
Si un intervalo propio T1 es 'intervalo encontrado por' otro intervalo propio T2, entonces el principio de T1 coincide con el final de T2.
interval met by
intervalo encontrado por
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.
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.
interval overlapped by
intervalo solapado por
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.
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.
interval overlaps
intervalo se solapa
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.
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.
interval started by
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.
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.
interval starts
intervalo empieza
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.
El mes del año, cuyo valor es un miembro de la clase 'mes del año'.
The month of the year, whose value is a member of the class time:MonthOfYear
mes del año
month of year
Característica arriesgada - añadida en la revisión de 2017, y todavía no ampliamente utilizada.
The time zone for clock elements in the temporal position
en huso horario
in time zone
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.
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.
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.
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'.
La unidad de tiempo que proporciona la precisión de un valor fecha-hora o la escala de una extensión temporal.
The temporal unit which provides the precision of a date-time value or scale of a temporal extent
temporal unit type
tipo de unidad temporal
Relation between an Actuation and the property of a FeatureOfInterest it is acting upon.
acts on property
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.
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.
has feature of interest
For example, in an Observation of the weight of a person, the FeatureOfInterest is the person and the property is its weight.
Relation linking an Observation or Actuation or act of Sampling and a Result or Sample.
has result
Relation between a FeatureOfInterest and the Sample used to represent it.
has sample
Relation between a Platform and a Sensor, Actuator, Sampler, or Platform, hosted or mounted on it.
hosts
Relation between an ActuatableProperty of a FeatureOfInterest and an Actuation changing its state.
is acted on by
A relation between a FeatureOfInterest and an Observation about it, an Actuation acting on it, or an act of Sampling that sampled it.
is feature of interest of
Relation between a Sensor, Actuator, Sampler, or Platform, and the Platform that it is mounted on or hosted by.
is hosted by
Relation between an ObservableProperty and the Sensor able to observe it.
is observed by
Relation linking a Result to the Observation or Actuation or act of Sampling that created or caused it.
is result of
Relation from a Sample to the FeatureOfInterest that it is intended to be representative of.
is sample of
Relation between an Actuator and the Actuation it has made.
made actuation
Relation linking an Actuation to the Actuator that made that Actuation.
made by actuator
Relation linking an act of Sampling to the Sampler (sampling device or entity) that made it.
made by sampler
Relation between an Observation and the Sensor which made the Observation.
made by sensor
Relation between a Sensor and an Observation made by the Sensor.
made observation
Relation between a Sampler (sampling device or entity) and the Sampling act it performed.
made sampling
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.
observed property
Relation between a Sensor and an ObservableProperty that it is capable of sensing.
observes
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.
phenomenon time
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.
used procedure
Relation between a Deployment and the Platform on which the Systems are deployed.
deployed on platform
Relation between a Deployment and a deployed System.
deployed system
A relation from a Sensor to the Stimulus that the Sensor detects. The Stimulus itself will be serving as a proxy for some ObservableProperty.
detects
A relation between some aspect of an entity and a Property.
for property
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.
Relation between a System and a Deployment, recording that the System is deployed in that Deployment.
has deployment
Relation between a Procedure and an Input to it.
has input
Relation between a Procedure and an Output of it.
has output
Relation between an entity and a Property of that entity.
has property
Relation between a System and its component parts.
has subsystem
Relation between a Procedure (an algorithm, procedure or method) and an entity that implements that Procedure in some executable way.
implemented by
For example, the relationship between a scientific measuring Procedure and a sensor that senses via that Procedure.
Relation between an entity that implements a Procedure in some executable way and the Procedure (an algorithm, procedure or method).
implements
For example, the relationship between a sensor and the scientific measuring Procedure via which it senses.
Relation between a Platform and a Deployment, meaning that the deployedSystems of the Deployment are hosted on the Platform.
in deployment
For example, a relation between a buoy and a deployment of several Sensors.
Relation between a Property and the entity it belongs to.
is property of
A relation from a Stimulus to the Property that the Stimulus is serving as a proxy for.
is proxy for
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.
Relation between an Observation and the Stimulus that originated it.
was originated by
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 descriptive spatial relation
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 spatial relation
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.
ha valore
has data value
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.
evento ha data
has event date
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.
has interval date
intervallo ha data
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'.
has parameter data value
A datatype property that encodes values for a Region, e.g. a float for the Region Height.
has region data value
regione ha valore
The Discrete Global Grid System (DGGS) serialization of a Geometry
as DGGS
The GML serialization of a Geometry
as GML
The GeoJSON serialization of a Geometry
as GeoJSON
The KML serialization of a Geometry
as KML
The WKT serialization of a Geometry
as WKT
The number of measurements or axes needed to describe the position of this Geometry in a coordinate system.
coordinate dimension
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.
dimension
The area of a Spatial Object in square meters.
has area in square meters
The length of a Spatial Object in meters.
has length in meters
The length of the perimeter of a Spatial Object in meters.
has perimeter length in meters
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 metric size
The positional accuracy of the coordinates of a Geometry in meters.
has spatial accuracy in meters
The spatial resolution of a Geometry in meters.
Spatial resolution specifies the level of detail of a Geometry. It the smallest dinstinguishable distance between spatially adjacent coordinates.
has spatial resolution in meters
The volume of a Spatial Object in cubic meters.
has volume in cubic meters
Connects a Geometry object with its text-based serialization.
has serialization
(true) if this geometric object is the empty Geometry. If true, then this geometric object represents the empty point set for the coordinate space.
is empty
(true) if this geometric object has no anomalous geometric points, such as self intersection or self tangency.
is simple
The number of measurements or axes needed to describe the spatial position of this Geometry in a coordinate system.
spatial dimension
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.
Posición de día en un sistema calendario-reloj.
day
día
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.
El número de día en el año.
The number of the day within the year
day of year
día del año
Longitud de, o elemento de la longitud de, una extensión temporal expresada en días.
length of, or element of the length of, a temporal extent expressed in days
days duration
duración en días
Extensión de una entidad temporal, expresada utilizando xsd:duration.
Extent of a temporal entity, expressed using xsd:duration
has XSD duration
tiene duración XSD
Hour position in a calendar-clock system.
Posición de hora en un sistema calendario-reloj.
hora
hour
Longitud de, o elemento de la longitud de, una extensión temporal expresada en horas.
length of, or element of the length of, a temporal extent expressed in hours
duración en horas
hours duration
Posición de un instante, expresado utilizando xsd:date.
Position of an instant, expressed using xsd:date
en fecha XSD
in XSD date
Posición de un instante, expresado utilizando xsd:dateTime.
Position of an instant, expressed using xsd:dateTime
en fecha-tiempo XSD
in XSD Date-Time
La propiedad 'en fecha-hora XSD' ha sido reemplazada por 'en fecha-sello de tiempo XSD' que hace obligatorio el campo 'huso horario'.
The property :inXSDDateTime is replaced by :inXSDDateTimeStamp which makes the time-zone field mandatory.
Posición de un instante, expresado utilizando xsd:dateTimeStamp.
Position of an instant, expressed using xsd:dateTimeStamp
en fecha-sello de tiempo XSD
in XSD Date-Time-Stamp
Posición de un instante, expresado utilizando xsd:gYear.
Position of an instant, expressed using xsd:gYear
en año gregoriano XSD
in XSD g-Year
Posición de un instante, expresado utilizando xsd:gYearMonth.
Position of an instant, expressed using xsd:gYearMonth
en año-mes gregoriano XSD
in XSD g-YearMonth
Minute position in a calendar-clock system.
Posición de minuto en un sistema calendario-reloj.
minute
minuto
Longitud de, o elemento de la longitud de, una extensión temporal expresada en minutos.
length, or element of, a temporal extent expressed in minutes
minutes
minutos
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.
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.
mes
month
Longitud de, o elemento de la longitud de, una extensión temporal expresada en meses.
length of, or element of the length of, a temporal extent expressed in months
duración en meses
months duration
El valor (nominal) que indica posición temporal en un sistema de referencia ordinal.
The (nominal) value indicating temporal position in an ordinal reference system
Name of temporal position
nombre de posición temporal
Valor de una extensión temporal expresada como un número decimal escalado por una unidad de tiempo.
Value of a temporal extent expressed as a decimal number scaled by a temporal unit
Numeric value of temporal duration
valor numérico de duración temporal
El valor (numérico) que indica posición temporal en un sistema de referencia ordinal.
The (numeric) value indicating position within a temporal coordinate system
Numeric value of temporal position
valor numérico de posición temporal
Posición de segundo en un sistema calendario-reloj.
Second position in a calendar-clock system.
second
segundo
Longitud de, o elemento de la longitud de, una extensión temporal expresada en segundos.
length of, or element of the length of, a temporal extent expressed in seconds
duración en segundos
seconds duration
Número de semana en el año.
Week number within the year.
semana
week
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.
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.
Longitud de, o elemento de la longitud de, una extensión temporal expresada en semanas.
length of, or element of the length of, a temporal extent expressed in weeks
duración en semanas
weeks duration
Valor de 'intervalo de fecha-hora' expresado como un valor compacto.
Value of DateTimeInterval expressed as a compact value.
has XSD date-time
tiene fecha-hora XSD
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.
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.
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.
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.
year
Longitud de, o elemento de la longitud de, una extensión temporal expresada en años.
length of, or element of the length of, a temporal extent expressed in years
duración en años
years duration
The simple value of an Observation or Actuation or act of Sampling.
has simple result
For instance, the values 23 or true.
The result time is the instant of time when the Observation, Actuation or Sampling activity was completed.
result time
Any Entity that cannot be located in space-time. E.g. mathematical entities: formal semantics elements, regions within dimensional spaces, etc.
Abstract
Astratto
An Event with at least one Agent that isParticipantIn it, and that executes a Task that typically isDefinedIn a Plan, Workflow, Project, etc.
Action
Azione
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.
Any agentive Object , either physical (e.g. a whale, a robot, an oak), or social (e.g. a corporation, an institution, a community).
Agent
Agente
A quantity, independently from how it is measured, computed, etc.
Amount
Quantità
Biological object
Chemical object
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.
Classification
Classificazione
time-indexed classification
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).
Collection
Collezione
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.
Collective
Collettivo
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.
Agente collettivo
Collective agent
Community
Comunità
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
Concept
Concetto
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.
Configuration
Configurazione
(The content of) an agreement between at least two agents that play a Party Role, about some contract object (a Task to be executed).
Contract
Contratto
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.
Description
Descrizione
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.
Design
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.
Artefatto progettato
Designed artifact
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).
Diagnosi
Diagnosis
Anything: real, possible, or imaginary, which some modeller wants to talk about for some purpose.
Entity
Entità
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 Situation allows to create a context where each particular view can have a proper identity, while the Event preserves its own identity. For example, ErosionAsAccomplishment is a Situation where rock erosion is observed as a process leading to a certain achievement: the conditions (roles, parameters) that suggest such view are stated in a Description, which acts as a 'theory of accomplishments'. Similarly, ErosionAsTransition is a Situation where rock erosion is observed as an event that has changed a state to another: the conditions for such interpretation are stated in a different Description, which acts as a 'theory of state transitions'. Consider that in no case the actual event is changed or enriched in parts by the aspectual view. (2) Alternative intentionality views Similarly to aspectual views, several intentionality views can be provided for a same Event. For example, one can investigate if an avalanche has been caused by immediate natural forces, or if there is any hint of an intentional effort to activate those natural forces. Also in this case, the Event as such has not different identities, while the causal analysis generates situations with different identities, according to what Description is taken for interpreting the Event. On the other hand, if the possible actions of an Agent causing the starting of an avalanche are taken as parts of the Event, then this makes its identity change, because we are adding a part to it. Therefore, if intentionality is a criterion to classify events or not, this depends on if an ontology designer wants to consider causality as a relevant dimension for events' identity. (3) Alternative participant views A slightly different case is when we consider the basic participants to an Event. In this case, the identity of the Event is affected by the participating objects, because it depends on them. For example, if snow, mountain slopes, wind, waves, etc. are considered as an avalanche basic participants, or if we also want to add water, human agents, etc., that makes the identity of an avalanche change. Anyway, this approach to event classification is based on the designer's choices, and more accurately mirrors lexical or commonsense classifications (see. e.g. WordNet 'supersenses' for verb synsets). Ultimately, this discussion has no end, because realists will keep defending the idea that events in reality are not changed by the way we describe them, while constructivists will keep defending the idea that, whatever 'true reality' is about, it can't be modelled without the theoretical burden of how we observe and describe it. Both positions are in principle valid, but, if taken too radically, they focus on issues that are only partly relevant to the aim of computational ontologies, which assist domain experts in representing a certain portion of reality according to their own assumptions and requirements. For this reason, in this ontology version of DOLCE, both events and situations are allowed, together with descriptions (the reason for the inclusion of the D&S framewrok in DOLCE), in order to encode the modelling needs, independently from the position (if any) chosen by the model designer.
Event
Evento
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)
Event type
Tipo di evento
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'.
Entità formale astratta
Formal entity
Functional substance
The Description of a Situation that is desired by an Agent, and usually associated to a Plan that describes how to actually achieve it
Goal
Scopo
A CollectiveAgent whose acting agents conceptualize a same SocialRelation .
Group
Gruppo
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.).
A piece of information, such as a musical composition, a text, a word, a picture, independently from how it is concretely realized.
Information object
Oggetto informativo
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.
Information realization
Informazione concreta
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.
Local concept
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.
Method
Metodo
Narrative
A person in the physical commonsense intuition: 'have you seen that person walking down the street?'
Natural person
Persona fisica
Norm
Norma
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.
Object
Oggetto
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.
A physical objects with biological characteristics, typically that organisms can self-reproduce.
Organism
Organismo
An internally structured, conventionally created SocialAgent, needing a specific Role and Agent that plays it, in order to act.
Un agente sociale strutturato internamente e creato convenzionalmente. Per agire, ha bisogno di ruoli e agenti che li ricoprano.
Organization
Organizzazione
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.
Parameter
Parametro
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.
parthood
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
Pattern
Persons in commonsense intuition, which does not apparently distinguish between either natural or social persons.
Person
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.
Personification
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
Agente fisico
Physical agent
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.
Artefatto fisico
Physical artifact
Physical value of a physical object, e.g. density, color, etc.
Caratteristica fisica
Physical attribute
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 body
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).
Oggetto fisico
Physical object
A physical object that is inherently located; for example, a water area.
Luogo fisico
Physical place
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.
Luogo
Place
A Description having an explicit Goal, to be achieved by executing the plan
Piano
Plan
Plan executions are situations that proactively satisfy a plan. Subplan executions are proper parts of the whole plan execution.
Esecuzione di piano
Plan execution
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'.
Process
Processo
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.
Progetto
Project
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'.
Quality
Qualità
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
Region
Regione
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.
Relation
Relazione
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.
Diritto
Right
Role
Ruolo
Set
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.
Situation
Situazione
Any individual whose existence is granted simply by its social communicability and capability of action (through some PhysicalAgent).
Agente sociale
Social agent
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).
Oggetto sociale
Social object
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.
Caratteristica sociale
Social attribute
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).
Persona sociale
Social person
Formerly: Person (changed to avoid confusion with commonsense intuition)
Relazione sociale
Social relation
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.
Regione di spazio
Space region
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).
Sostanza
Substance
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.
Task
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).
Teoria
Theory
A Situation that includes a time indexing in its setting, so allowing to order any binary relation (property) with time.
Any Region in a dimensional space that aims at representing time.
Intervallo di tempo
Time interval
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.
Transition
Transizione
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.
Collezione di un tipo
Type collection
Units of measure are conceptualized here as parameters on regions, which can be valued as datatype values.
Unit of measure
Unità di misura
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
Esecuzione di workflow
Workflow execution
A discrete spatial phenomenon in a universe of discourse.
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.
Feature
A collection of individual Features.
Feature Collection
A coherent set of direct positions in space. The positions are held within a Spatial Reference System (SRS).
Geometry can be used as a representation of the shape, extent or location of a Feature and may exist as a self-contained entity.
Geometry
A collection of individual Geometries.
Geometry Collection
Anything spatial (being or having a shape, position or an extent).
Subclasses of this class are expected to be used for instance data.
Spatial Object
A collection of individual Spatial Objects.
This is the superclass of Feature Collection and Geometry Collection.
Spatial Object Collection
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.
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.
Date-Time description
descripción de fecha-tiempo
'intervalo de fecha-hora' es una subclase de 'intervalo propio', definida utilizando el multi-elemento 'descripción de fecha-hora'.
DateTimeInterval is a subclass of ProperInterval, defined using the multi-element DateTimeDescription.
Date-time interval
intervalo de fecha-hora
'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.
: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.
El día de la semana
The day of week
Day of week
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 ) ;
La pertenencia a la clase 'día de la semana' está abierta, para permitir longitudes de semana alternativas y diferentes nombres de días.
Membership of the class :DayOfWeek is open, to allow for alternative week lengths and different day names.
Duración de una extensión temporal expresada como un número escalado por una unidad temporal.
Duration of a temporal extent expressed as a number scaled by a temporal unit
Time duration
Alternativa a 'descripción de tiempo' para proporcionar descripción soporte a una duración temporal diferente a utilizar un sistema de calendario/reloj.
Alternative to time:DurationDescription to support description of a temporal duration other than using a calendar/clock system.
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.
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
Duration description
descripción de duración
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.
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.
Descripción de fecha y hora estructurada con valores separados para los distintos elementos de un sistema calendario-reloj.
Description of date and time structured with separate values for the various elements of a calendar-clock system
Generalized date-time description
descripción de fecha-hora generalizada
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'.
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.
Descripción de extensión temporal estructurada con valores separados para los distintos elementos de un sistema de horario-calendario.
Description of temporal extent structured with separate values for the various elements of a calendar-clock system.
Generalized duration description
descripción de duración generalizada
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.
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.
A temporal entity with zero extent or duration
Una entidad temporal con una extensión o duración cero.
Time instant
instante de tiempo.
A temporal entity with an extent or duration
Una entidad temporal con una extensión o duración.
intervalo de tiempo
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.
El mes del año.
The month of the year
Month of year
Característica en riesgo - añadida en la revisión de 2017, y no utilizada todavía de forma amplia.
La pertenencia a la clase 'mes del año' está abierta, a permitir calendarios anuales alternativos y diferentes nombres de meses.
Membership of the class :MonthOfYear is open, to allow for alternative annual calendars and different month names.
A temporal entity with non-zero extent or duration, i.e. for which the value of the beginning and end are different
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.
Proper interval
intervalo propio
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.
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.
Temporal Reference System
sistema de referencia temporal
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).
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).
Extensión de tiempo; duración de un intervalo de tiempo independiente de su posición de inicio particular.
Time extent; duration of a time interval separate from its particular start position
Temporal duration
duración temporal
A temporal interval or instant.
Un intervalo temporal o un instante.
Temporal entity
entidad temporal
A position on a time-line
Una posición sobre una línea de tiempo.
A standard duration, which provides a scale factor for a time extent, or the granularity or precision for a time position.
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.
Temporal unit
unidad de tiempo
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 ) ;
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).
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).
A temporal position described using either a (nominal) value from an ordinal reference system, or a (numeric) value in a temporal coordinate system.
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.
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.
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.
Time Zone
huso horario
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.
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.
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/ .
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.
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.
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.
In this implementation TimeZone has no properties defined. It should be thought of as an 'abstract' superclass of all specific timezone implementations.
Year
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.
Anno
Année (calendrier)
Ano
Año
Jaar
Jahr
Rok
Год
سنة
An actuatable quality (property, characteristic) of a FeatureOfInterest.
Actuatable Property
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.
An Actuation carries out an (Actuation) Procedure to change the state of the world using an Actuator.
Actuation
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.
A device that is used by, or implements, an (Actuation) Procedure that changes the state of the world.
Actuator
A window actuator for automatic window control, i.e., opening or closing the window.
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.
Feature Of Interest
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.
An observable quality (property, characteristic) of a FeatureOfInterest.
Observable Property
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.
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.
Observation
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.
A Platform is an entity that hosts other entities, particularly Sensors, Actuators, Samplers, and other Platforms.
Platform
A post, buoy, vehicle, ship, aircraft, satellite, cell-phone, human or animal may act as platforms for (technical or biological) sensors or actuators.
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.
Procedure
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.
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).
The Result of an Observation, Actuation, or act of Sampling. To store an observation's simple result value one can use the hasSimpleResult property.
Result
The value 20 as the height of a certain tree together with the unit, e.g., Meter.
A Sample is the result from an act of Sampling.
Feature which is intended to be representative of a FeatureOfInterest on which Observations may be made.
Physical samples are sometimes known as 'specimens'.
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.
Sample
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.
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.
A transient sample, such as a ships-track or flight-line, might be identified and described, but is unlikely to be revisited exactly.
A device that is used by, or implements, a Sampling Procedure to create or transform one or more samples.
Sampler
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.
An act of Sampling carries out a sampling Procedure to create or transform one or more samples.
Sampling
Crushing a rock sample in a ball mill.
Digging a pit through a soil sequence.
Dividing a field site into quadrants.
Drawing blood from a patient.
Drilling an observation well.
Establishing a station for environmental monitoring.
Registering an image of the landscape.
Selecting a subset of a population.
Sieving a powder to separate the subset finer than 100-mesh.
Splitting a piece of drill-core to create two new samples.
Taking a diamond-drill core from a rock outcrop.
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.
Sensor
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.
Describes the Deployment of one or more Systems for a particular purpose. Deployment may be done on a Platform.
Deployment
For example, a temperature Sensor deployed on a wall, or a whole network of Sensors deployed for an Observation campaign.
Any information that is provided to a Procedure for its use.
Input
Any information that is reported from a Procedure.
Output
A quality of an entity. An aspect of an entity that is intrinsic to and cannot exist without the entity.
Property
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.
Stimulus
System is a unit of abstraction for pieces of infrastructure that implement Procedures. A System may have components, its subsystems, which are other systems.
System
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").
complex event
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.
event
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.
event condition
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"),
manifestation
Describes any physcical object in a smart environment that has a geometry.
spatial object
Decsribes a node in a network that receives data from sensors,
Decsribes a node as part of a nore station that contributes sending the data read by sensors.
Describes the deployment of a network in a smart environment.
deployment
A network which is a collection of Nodes
network
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.
network module
Decsribes a node in a network that either sends or receives the data read by a sensor.
node
Decsribes a module in a network that contains nodes, batteries, etc.
node station
Describes a node station which holds a data receiver node as its part (sub-system)
Describes a node station which is assumed to contain both a data sender node and also sensing devices (sensors)
Describes any agent (e.g., human, pet, etc) in a smart environment that can participate in an event or activity.
agent
Describes any type of physical object that has the possibility to move in a smart environment.
mobile object
Describes any object in a smart environment, which is used to host network modules such as nodes or node stations.
node holder
Describes any type of physical object in a smart environment.
object
Describes any physical object in a smart environment which is a feature of interest for an observation process.
smart object
Sections belonging to a smart environment (e.g., kitchen, livingroom, etc., in case of a smart home)
section
Represent a smart environment as a physical place which is also supposed to be a platform for a sensor network deployment.
smart environment
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.
configuration procedure
Using a Sensor it describes the process of observing a property of a feature of interest.
observation
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.
sensor
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.
situation
e.g., stove-on, tv-on, sofa-used (i.e., the pressure (as the property of the sofa) on the sofa is realized).
Describes a specific state of a feature of interest regardless of how it has been realized.
state
on, off, true, false, etc.
Describes a temporal instant specifiying a specific datetimestamp
instant
Describes a temporal entity with an extent or duration with a known starting time.
interval
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 distance
Describes a temporal entity that can represent a single time instant, a time interval, or a temporal distance.
temporal entity
Describes time duration in the form of a numeric value indicating its length, and a temporal unit type.
time duration
Friday
Freitag
Piątek
Sexta-feira
Vendredi
Venerdì
Viernes
Vrijdag
Пятница
الجمعة
星期五
金曜日
Monday
Lundi
Lunedì
Lunes
Maandag
Montag
Poniedziałek
Segunda-feira
Понедельник
الاثنين
星期一
月曜日
Saturday
Sabato
Samedi
Samstag
Sobota
Sábado
Zaterdag
Суббота
السبت
土曜日
星期六
Sunday
Dimanche
Domenica
Domingo
Niedziela
Sonntag
Zondag
Воскресенье
الأحد (يوم)
日曜日
星期日
Thursday
Czwartek
Donderdag
Donnerstag
Giovedì
Jeudi
Jueves
Quinta-feira
Четверг
الخميس
星期四
木曜日
Tuesday
Dienstag
Dinsdag
Mardi
Martedì
Martes
Terça-feira
Wtorek
Вторник
الثلاثاء
星期二
火曜日
Wednesday
Mercoledì
Mercredi
Mittwoch
Miércoles
Quarta-feira
Woensdag
Środa
Среда
الأربعاء
星期三
水曜日
Day (unit of temporal duration)
Tag
dag
dia
doba
giorno
jour
يوماً ما
ある日
一天
언젠가
Hour (unit of temporal duration)
Stunde
godzina
heure
ora
uur
ساعة واحدة
一小時
一時間
한 시간
Minute (unit of temporal duration)
Minute
minuta
minuut
одна минута
دقيقة واحدة
一分
等一下
Month (unit of temporal duration)
Monat
maand
mese
miesiąc
mois
один месяц
شهر واحد
一か月
一個月
한달
Second (unit of temporal duration)
Sekunde
Sekundę
seconde
secondo
ثانية واحدة
一秒
일초
Week (unit of temporal duration)
Woche
semaine
settimana
tydzień
одна неделя
سبوع واحد
一周
一週間
일주일
Year (unit of temporal duration)
1 년
1年
anno
ano
jaar
rok
un año
один год
سنة واحدة
一年