DOLCE+DnS Ultralite
type: Ontology
comment: 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. sit…
version info: 4.2
version info: Created by Aldo Gangemi as both a simplification and extension of DOLCE and Descriptions and Situations ontologies.
version info: 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 som…

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

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

Agent
type: Class
comment: Additional comment: a computational agent can be considered as a PhysicalAgent that realizes a certain class of algorithms (that can be considered as instances of InformationObject) that allow to obtain some behaviors that are considered typical of agents in general. For an ontology of computational objects based on DOLCE see e.g. http://www.loa-cnr.it/COS/COS.owl, and http://www.loa-cnr.it/KCO/KCO.owl.
comment: Any agentive Object , either physical (e.g. a whale, a robot, an oak), or social (e.g. a corporation, an institution, a community).
label: Agente @it
subclass of: Object

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

Biological object
type: Class
subclass of: Physical body

Chemical object
type: Class
subclass of: Physical body

Classification
type: Class
comment: A special kind of Situation that allows to include time indexing for the classifies relation in situations. For example, if a Situation s 'my old cradle is used in these days as a flower pot' isSettingFor the entity 'my old cradle' and the TimeIntervals '8June2007' and '10June2007', and we know that s satisfies a functional Description for aesthetic objects, which defines the Concepts 'flower pot' and 'flower', then we also need to know what concept classifies 'my old cradle' at what time. In order to solve this issue, we need to create a sub-situation s' for the classification time: 'my old cradle is a flower pot in 8June2007'. Such sub-situation s' isPartOf s.
label: Classificazione @it
label: time-indexed classification
subclass of: TimeIndexedRelation
subclass of: Restriction
  on property: is setting for
  some values from: Concept
subclass of: Restriction
  on property: is setting for
  some values from: Entity
subclass of: Restriction
  on property: is setting for
  some values from: Time interval

Collection
type: Class
comment: Any container for entities that share one or more common properties. E.g. "stone objects", "the nurses", "the Louvre Aegyptian collection", all the elections for the Italian President of the Republic. A collection is not a logical class: a collection is a first-order entity, while a class is second-order. A collection is neither an aggregate of its member entities (see e.g. ObjectAggregate class).
label: Collezione @it
subclass of: Social object
subclass of: Restriction
  all values from: Collection
  on property: has part

Collective
type: Class
comment: A Collection whose members are agents, e.g. "the nurses", "the Italian rockabilly fans". Collectives, facon de parler, can act as agents, although they are not assumed here to be agents (they are even disjoint from the class SocialAgent). This is represented by admitting collectives in the range of the relations having Agent in their domain or range.
label: Collettivo @it
subclass of: Collection
subclass of: Restriction
  all values from: Agent
  on property: has member

Collective agent
type: Class
comment: A SocialAgent that is actedBy agents that are (and act as) members of a Collective. A collective agent can have roles that are also roles of those agents. For example, in sociology, a 'group action' is the situation in which a number of people (that result to be members of a collective) in a given area behave in a coordinated way in order to achieve a (often common) goal. The Agent in such a Situation is not single, but a CollectiveAgent (a Group). This can be generalized to the notion of social movement, which assumes a large Community or even the entire Society as agents. The difference between a CollectiveAgent and an Organization is that a Description that introduces a CollectiveAgent is also one that unifies the corresponding Collective. In practice, this difference makes collective agents 'less stable' than organizations, because they have a dedicated, publicly recognizable Description that is conceived to introduce them.
label: Agente collettivo @it
subclass of: Social agent
subclass of: Restriction
  on property: acts through
  some values from: Agent
subclass of: Restriction
  on property: is introduced by
  some values from: Description

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

Concept
type: Class
comment: A Concept is a SocialObject, and isDefinedIn some Description; once defined, a Concept can be used in other Description(s). If a Concept isDefinedIn exactly one Description, see the LocalConcept class. The classifies relation relates Concept(s) to Entity(s) at some TimeInterval
label: Concetto @it
subclass of: Social object
subclass of: Restriction
  on property: is defined in
  some values from: Description
subclass of: Restriction
  all values from: Concept
  on property: has part
disjoint with: Social agent

Configuration
type: Class
comment: A collection whose members are 'unified', i.e. organized according to a certain schema that can be represented by a Description. Typically, a configuration is the collection that emerges out of a composed entity: an industrial artifact, a plan, a discourse, etc. E.g. a physical book has a configuration provided by the part-whole schema that holds together its cover, pages, ink. That schema, based on the individual relations between the book and its parts, can be represented in a reified way by means of a (structural) description, which is said to 'unify' the book configuration.
label: Configurazione @it
subclass of: Collection

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

Description
type: Class
comment: A Description is a SocialObject that represents a conceptualization. It can be thought also as a 'descriptive context' that uses or defines concepts in order to create a view on a 'relational context' (cf. Situation) out of a set of data or observations. For example, a Plan is a Description of some actions to be executed by agents in a certain way, with certain parameters; a Diagnosis is a Description that provides an interpretation for a set of observed entities, etc. Descriptions 'define' or 'use' concepts, and can be 'satisfied' by situations.
label: Descrizione @it
subclass of: Social object
disjoint with: Social agent

Design
type: Class
comment: A Description of the Situation, in terms of structure and function, held by an Entity for some reason. A design is usually accompanied by the rationales behind the construction of the designed Entity (i.e. of the reasons why a design is claimed to be as such). For example, the actual design (a Situation) of a car or of a law is based on both the specification (a Description) of the structure, and the rationales used to construct cars or laws. While designs typically describe entities to be constructed, they can also be used to describe 'refunctionalized' entities, or to hypothesize unknown functions. For example, a cradle can be refunctionalized as a flowerpot based on a certain home design.
subclass of: Description

Designed artifact
type: Class
comment: A PhysicalArtifact that is also described by a Design. This excludes simple recycling or refunctionalization of natural objects. Most common sense 'artifacts' can be included in this class: cars, lamps, houses, chips, etc.
label: Artefatto progettato @it
subclass of: Physical artifact
subclass of: Restriction
  on property: is described by
  some values from: Design

Diagnosis
type: Class
comment: A Description of the Situation of a system, usually applied in order to control a normal behaviour, or to explain a notable behavior (e.g. a functional breakdown).
label: Diagnosi @it
subclass of: Description

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

Event
type: Class
comment: Any physical, social, or mental process, event, or state. More theoretically, events can be classified in different ways, possibly based on 'aspect' (e.g. stative, continuous, accomplishement, achievement, etc.), on 'agentivity' (e.g. intentional, natural, etc.), or on 'typical participants' (e.g. human, physical, abstract, food, etc.). Here no special direction is taken, and the following explains why: events are related to observable situations, and they can have different views at a same time. If a position has to be suggested here anyway, the participant-based classification of events seems the most stable and appropriate for many modelling problems. (1) Alternative aspectual views Consider a same event 'rock erosion in the Sinni valley': it can be conceptualized as an accomplishment (what has brought a certain state to occur), as an achievement (the state resulting from a previous accomplishment), as a punctual event (if we collapse the time interval of the erosion into a time point), or as a transition (something that has changed from a state to a different one). In the erosion case, we could therefore have good motivations to shift from one aspect to another: a) causation focus, b) effectual focus, c) historical condensation, d) transition (causality). The different views refer to the same event, but are still different: how to live with this seeming paradox? A typical solution e.g. in linguistics (cf. Levin's aspectual classes) and in DOLCE Full (cf. WonderWeb D18 axiomatization) is to classify events based on aspectual differences. But this solution would create different identities for a same event, where the difference is only based on the modeller's attitude. An alternative solution is suggested here, and exploits the notion of (observable) Situation; a Situation is a view, consistent with a Description, which can be observed of a set of entities. It can also be seen as a 'relational context' created by an observer on the basis of a 'frame'. Therefore, a…
label: Evento @it
subclass of: Entity
subclass of: Restriction
  on property: has participant
  some values from: Object
subclass of: Restriction
  on property: has time interval
  some values from: Time interval
subclass of: Restriction
  all values from: Event
  on property: has constituent
subclass of: Restriction
  all values from: Event
  on property: has part
disjoint with: Object
disjoint with: Quality

Event type
type: Class
comment: A Concept that classifies an Event . An event type describes how an Event should be interpreted, executed, expected, seen, etc., according to the Description that the EventType isDefinedIn (or used in)
label: Tipo di evento @it
subclass of: Concept
subclass of: Restriction
  all values from: Event
  on property: classifies
disjoint with: Parameter
disjoint with: Role

Formal entity
type: Class
comment: Entities that are formally defined and are considered independent from the social context in which they are used. They cannot be localized in space or time. Also called 'Platonic entities'. Mathematical and logical entities are included in this class: sets, categories, tuples, costants, variables, etc. Abstract formal entities are distinguished from information objects, which are supposed to be part of a social context, and are localized in space and time, therefore being (social) objects. For example, the class 'Quark' is an abstract formal entity from the purely set-theoretical perspective, but it is an InformationObject from the viewpoint of ontology design, when e.g. implemented in a logical language like OWL. Abstract formal entities are also distinguished from Concept(s), Collection(s), and Description(s), which are part of a social context, therefore being SocialObject(s) as well. For example, the class 'Quark' is an abstract FormalEntity from the purely set-theoretical perspective, but it is a Concept within history of science and cultural dynamics. These distinctions allow to represent two different notions of 'semantics': the first one is abstract and formal ('formal semantics'), and formallyInterprets symbols that are about entities whatsoever; for example, the term 'Quark' isAbout the Collection of all quarks, and that Collection isFormalGroundingFor the abstract class 'Quark' (in the extensional sense). The second notion is social, localized in space-time ('social semantics'), and can be used to interpret entities in the intensional sense. For example, the Collection of all quarks isCoveredBy the Concept 'Quark', which is also expressed by the term 'Quark'.
label: Entità formale astratta @it
subclass of: Abstract

Functional substance
type: Class
subclass of: Substance

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

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

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

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

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

Local concept
type: Class
comment: A Concept that isDefinedIn exactly 1 Description. For example, the Concept 'coffee' in a 'preparesCoffee' relation can be defined in that relation, and for all other Description(s) that use it, the isConceptUsedIn property should be applied. Notice therefore that not necessarily all Concept(s) isDefinedIn exactly 1 Description.
subclass of: Concept

Method
type: Class
comment: A method is a Description that defines or uses concepts in order to guide carrying out actions aimed at a solution with respect to a problem. It is different from a Plan, because plans could be carried out in order to follow a method, but a method can be followed by executing alternative plans.
label: Metodo @it
subclass of: Description

Narrative
type: Class
subclass of: Description

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

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

Object
type: Class
comment: Any physical, social, or mental object, or a substance. Following DOLCE Full, objects are always participating in some event (at least their own life), and are spatially located.
label: Oggetto @it
subclass of: Entity
subclass of: Restriction
  on property: has location
  some values from: Entity
subclass of: Restriction
  on property: is participant in
  some values from: Event
subclass of: Restriction
  all values from: Object
  on property: has constituent
subclass of: Restriction
  all values from: Object
  on property: has part
subclass of: Restriction
  all values from: Role
  on property: is classified by
disjoint with: Quality

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

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

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

Parameter
type: Class
comment: A Concept that classifies a Region; the difference between a Region and a Parameter is that regions represent sets of observable values, e.g. the height of a given building, while parameters represent constraints or selections on observable values, e.g. 'VeryHigh'. Therefore, parameters can also be used to constrain regions, e.g. VeryHigh on a subset of values of the Region Height applied to buildings, or to add an external selection criterion , such as measurement units, to regions, e.g. Meter on a subset of values from the Region Length applied to the Region Length applied to roads.
label: Parametro @it
subclass of: Concept
subclass of: Restriction
  all values from: Region
  on property: classifies
subclass of: Restriction
  all values from: Parameter
  on property: has part
disjoint with: Role

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

Pattern
type: Class
comment: Any invariance detected from a dataset, or from observation; also, any invariance proposed based on top-down considerations. E.g. patterns detected and abstracted by an organism, by pattern recognition algorithms, by machine learning techniques, etc. An occurrence of a pattern is an 'observable', or detected Situation
subclass of: Relation

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

Personification
type: Class
comment: A social entity with agentive features, but whose status is the result of a cultural transformation from e.g. a PhysicalObject, an Event, an Abstract, another SocialObject, etc. For example: the holy grail, deus ex machina, gods, magic wands, etc.
subclass of: Social agent

Physical agent
type: Class
comment: A PhysicalObject that is capable of self-representing (conceptualizing) a Description in order to plan an Action. A PhysicalAgent is a substrate for (actsFor) a Social Agent
label: Agente fisico @it
subclass of: Agent
subclass of: Physical object

Physical artifact
type: Class
comment: Any PhysicalObject that isDescribedBy a Plan . This axiomatization is weak, but allows to talk of artifacts in a very general sense, i.e. including recycled objects, objects with an intentional functional change, natural objects that are given a certain function, even though they are not modified or structurally designed, etc. PhysicalArtifact(s) are not considered disjoint from PhysicalBody(s), in order to allow a dual classification when needed. E.g., FunctionalSubstance(s) are included here as well. Immaterial (non-physical) artifacts (e.g. texts, ideas, cultural movements, corporations, communities, etc. can be modelled as social objects (see SocialObject), which are all 'artifactual' in the weak sense assumed here.
label: Artefatto fisico @it
subclass of: Physical object
subclass of: Restriction
  on property: is described by
  some values from: Plan

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

Physical body
type: Class
comment: Physical bodies are PhysicalObject(s), for which we tend to neutralize any possible artifactual character. They can have several granularity levels: geological, chemical, physical, biological, etc.
subclass of: Physical object

Physical object
type: Class
comment: Any Object that has a proper space region. The prototypical physical object has also an associated mass, but the nature of its mass can greatly vary based on the epistemological status of the object (scientifically measured, subjectively possible, imaginary).
label: Oggetto fisico @it
subclass of: Object
subclass of: Restriction
  all values from: Physical object
  on property: has part
disjoint with: Social object

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

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

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

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

Process
type: Class
comment: This is a placeholder for events that are considered in their evolution, or anyway not strictly dependent on agents, tasks, and plans. See Event class for some thoughts on classifying events. See also 'Transition'.
label: Processo @it
subclass of: Event

Project
type: Class
comment: A Plan that defines Role(s), Task(s), and a specific structure for tasks to be executed in relation to goals to be achieved, in order to achieve the main goal of the project. In other words, a project is a plan with a subgoal structure and multiple roles and tasks.
label: Progetto @it
subclass of: Plan
subclass of: Restriction
  on property: defines role
  some values from: Role
subclass of: Restriction
  on property: defines task
  some values from: Task

Quality
type: Class
comment: Any aspect of an Entity (but not a part of it), which cannot exist without that Entity. For example, the way the surface of a specific PhysicalObject looks like, or the specific light of a place at a certain time, are examples of Quality, while the encoding of a Quality into e.g. a PhysicalAttribute should be modeled as a Region. From the design viewpoint, the Quality-Region distinction is useful only when individual aspects of an Entity are considered in a domain of discourse. For example, in an automotive context, it would be irrelevant to consider the aspects of car windows for a specific car, unless the factory wants to check a specific window against design parameters (anomaly detection). On the other hand, in an antiques context, the individual aspects for a specific piece of furniture are a major focus of attention, and may constitute the actual added value, because the design parameters for old furniture are often not fixed, and may not be viewed as 'anomalies'.
label: Qualità @it
subclass of: Entity
subclass of: Restriction
  on property: has region
  some values from: Region
subclass of: Restriction
  on property: is quality of
  some values from: Entity
subclass of: Restriction
  all values from: Quality
  on property: has constituent
subclass of: Restriction
  all values from: Quality
  on property: has part

Region
type: Class
comment: Any region in a dimensional space (a dimensional space is a maximal Region), which can be used as a value for a quality of an Entity . For example, TimeInterval, SpaceRegion, PhysicalAttribute, Amount, SocialAttribute are all subclasses of Region. Regions are not data values in the ordinary knowledge representation sense; in order to get patterns for modelling data, see the properties: representsDataValue and hasDataValue
label: Regione @it
subclass of: Abstract
subclass of: Restriction
  all values from: Region
  on property: precedes
subclass of: Restriction
  all values from: Region
  on property: has constituent
subclass of: Restriction
  all values from: Region
  on property: has part
subclass of: Restriction
  all values from: Region
  on property: overlaps

Relation
type: Class
comment: Relations are descriptions that can be considered as the counterpart of formal relations (that are included in the FormalEntity class). For example, 'givingGrantToInstitution(x,y,z)' with three argument types: Provider(x),Grant(y),Recipient(z), can have a Relation counterpart: 'GivingGrantToInstitution', which defines three Concept instances: Provider,Grant,Recipient. Since social objects are not formal entities, Relation includes here any 'relation-like' entity in common sense, including social relations.
label: Relazione @it
subclass of: Description

Right
type: Class
comment: A legal position by which an Agent is entitled to obtain something from another Agent , under specified circumstances, through an enforcement explicited either in a Law, Contract , etc.
label: Diritto @it
subclass of: Description
subclass of: Restriction
  min cardinality: 2
  on property: defines role
subclass of: Restriction
  min cardinality: 1
  on property: defines task

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

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

Situation
type: Class
comment: A view, consistent with ('satisfying') a Description, on a set of entities. It can also be seen as a 'relational context' created by an observer on the basis of a 'frame' (i.e. a Description). For example, a PlanExecution is a context including some actions executed by agents according to certain parameters and expected tasks to be achieved from a Plan; a DiagnosedSituation is a context of observed entities that is interpreted on the basis of a Diagnosis, etc. Situation is also able to represent reified n-ary relations, where isSettingFor is the top-level relation for all binary projections of the n-ary relation. If used in a transformation pattern for n-ary relations, the designer should take care of adding (some or all) OWL2 keys, corresponding to binary projections of the n-ary, to a subclass of Situation. Otherwise the 'identification constraint' (Calvanese et al., IJCAI 2001) might be violated.
label: Situazione @it
subclass of: Entity
equivalent class: Restriction
  on property: satisfies
  some values from: Description

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

Social object
type: Class
comment: Any Object that exists only within some communication Event, in which at least one PhysicalObject participates in. In other words, all objects that have been or are created in the process of social communication: for the sake of communication (InformationObject), for incorporating new individuals (SocialAgent, Place), for contextualizing or intepreting existing entities (Description, Concept), or for collecting existing entities (Collection). Being dependent on communication, all social objects need to be expressed by some information object (information objects are self-expressing).
label: Oggetto sociale @it
subclass of: Object
subclass of: Restriction
  on property: is expressed by
  some values from: Information object
subclass of: Restriction
  all values from: Social object
  on property: has part

Social attribute
type: Class
comment: Any Region in a dimensional space that is used to represent some characteristic of a SocialObject, e.g. judgment values, social scalars, statistical attributes over a collection of entities, etc.
label: Caratteristica sociale @it
subclass of: Region
subclass of: Restriction
  all values from: Social object
  on property: is region for

Social person
type: Class
comment: A SocialAgent that needs the existence of a specific NaturalPerson in order to act (but the lifetime of the NaturalPerson has only to overlap that of the SocialPerson).
label: Persona sociale @it
subclass of: Persona {it}
subclass of: Social agent
subclass of: Restriction
  cardinality: 1
  on property: acts through
version info: Formerly: Person (changed to avoid confusion with commonsense intuition)

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

Space region
type: Class
comment: Any Region in a dimensional space that is used to localize an Entity ; i.e., it is not used to represent some characteristic (e.g. it excludes time intervals, colors, size values, judgment values, etc.). Differently from a Place , a space region has a specific dimensional space.
label: Regione di spazio @it
subclass of: Region
disjoint with: Time interval

Substance
type: Class
comment: Any PhysicalBody that has not necessarily specified (designed) boundaries, e.g. a pile of trash, some sand, etc. In this sense, an artistic object made of trash or a dose of medicine in the form of a pill would be a FunctionalSubstance, and a DesignedArtifact, since its boundaries are specified by a Design; aleatoric objects that are outcomes of an artistic process might be still considered DesignedArtifact(s), and Substance(s).
label: Sostanza @it
subclass of: Physical body

Task
type: Class
comment: An EventType that classifies an Action to be executed. For example, reaching a destination is a task that can be executed by performing certain actions, e.g. driving a car, buying a train ticket, etc. The actions to execute a task can also be organized according to a Plan that is not the same as the one that defines the task (if any). For example, reaching a destination could be defined by a plan to get on holidays, while the plan to execute the task can consist of putting some travels into a sequence.
subclass of: Event type
subclass of: Restriction
  all values from: Task
  on property: has part
subclass of: Restriction
  all values from: Action
  on property: is executed in
subclass of: Restriction
  all values from: Description
  on property: is task defined in
subclass of: Restriction
  all values from: Role
  on property: is task of

Theory
type: Class
comment: A Theory is a Description that represents a set of assumptions for describing something, usually general. Scientific, philosophical, and commonsense theories can be included here. This class can also be used to act as 'naturalized reifications' of logical theories (of course, they will be necessarily incomplete in this case, because second-order entities are represented as first-order ones).
label: Teoria @it
subclass of: Description
subclass of: Restriction
  on property: has component
  some values from: Relation

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

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

Transition
type: Class
comment: A transition is a Situation that creates a context for three TimeInterval(s), two additional different Situation(s), one Event, one Process, and at least one Object: the Event is observed as the cause for the transition, one Situation is the state before the transition, the second Situation is the state after the transition, the Process is the invariance under some different transitions (including the one represented here), in which at least one Object is situated. Finally, the time intervals position the situations and the transitional event in time. This class of situations partly encodes the ontology underlying typical engineering algebras for processes, e.g. Petri Nets. A full representation of the transition ontology is outside the expressivity of OWL, because we would need qualified cardinality restrictions, coreference, property equivalence, and property composition.
label: Transizione @it
subclass of: Situation
subclass of: Restriction
  on property: includes event
  some values from: Event
subclass of: Restriction
  on property: includes object
  some values from: Object
subclass of: Restriction
  on property: is setting for
  some values from: Process
subclass of: Restriction
  on property: is setting for
  some values from: Class
    intersection of: Situation
    intersection of: Restriction
      on property: precedes
      some values from: Class
        intersection of: Event
        intersection of: Restriction
subclass of: Restriction
  min qualified cardinality: 3
  on class: Time interval
  on property: includes time
subclass of: Restriction
  min qualified cardinality: 2
  on class: Situation
  on property: is setting for

Type collection
type: Class
comment: A Collection whose members are the maximal set of individuals that share the same (named) type, e.g. "the gem stones", "the Italians". This class is very useful to apply a variety of the so-called "ClassesAsValues" design pattern, when it is used to talk about the extensional aspect of a class. An alternative variety of the pattern applies to the intensional aspect of a class, and the class Concept should be used instead.
label: Collezione di un tipo @it
subclass of: Collection

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

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

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

acts for
type: ObjectProperty
comment: The relation holding between any Agent, and a SocialAgent. In principle, a SocialAgent requires at least one PhysicalAgent in order to act, but this dependency can be 'delegated'; e.g. a university can be acted for by a department, which on its turm is acted for by physical agents.
domain: Agent
label: agisce per @it
range: Social agent
sub property of: associatedWith
inverse of: acts through

acts through
type: ObjectProperty
comment: The relation holding between a PhysicalAgent and a SocialAgent. In principle, a SocialAgent requires at least one PhysicalAgent in order to act, but this dependency can be 'delegated', e.g. a university can be acted for by a department, which is acted for by physical agents. AKA isActedBy
domain: Social agent
label: agisce mediante @it
range: Agent
sub property of: associatedWith

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

characterizes
type: ObjectProperty
comment: A relation between concepts and collections, where a Concept is said to characterize a Collection; it corresponds to a link between the (reified) intensional and extensional interpretations of a _proper subset of_ a (reified) class. This is different from covers, because it refers to an interpretation the entire reified class. E.g. the collection of vintage saxophones is characterized by the Concept 'manufactured by hand', while it gets covered by the Concept 'Saxophone' with the Parameter 'Vintage'.
domain: Concept
label: caratterizza @it
range: Collection
sub property of: associatedWith
inverse of: is characterized by {@en-us}

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

conceptualizes
type: ObjectProperty
comment: A relation stating that an Agent is internally representing a SocialObject: situations, descriptions, concepts, etc. E.g., 'John believes in the conspiracy theory'; 'Niels Bohr created the solar-system metaphor for the atomic theory'; 'Jacques assumes all swans are white'; 'the task force members share the attack plan'. Conceptualizations can be distinguished into different forms, primarily based on the type of SocialObject that is conceptualized. Descriptions and concepts can be 'assumed', situations can be 'believed' or 'known', plans can be 'adopted', etc. (see ontology: http://www.ontologydesignpatterns.org/ont/dul/Conceptualization.owl.
domain: Agent
label: concettualizza @it
range: Social object
sub property of: associatedWith
inverse of: is conceptualized by

concretely expresses
type: ObjectProperty
comment: A relation between an InformationRealization and a Description, e.g. 'the printout of the Italian Constitution concretelyExpresses the Italian Constitution'. It should be supplied also with a rule stating that the InformationRealization realizes an InformationObject that expresses the Description
domain: Information realization
label: esprime concretamente @it
range: Social object
sub property of: associatedWith
inverse of: is concretely expressed by

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

covers
type: ObjectProperty
comment: A relation between concepts and collections, where a Concept is said to cover a Collection; it corresponds to a link between the (reified) intensional and extensional interpretations of a (reified) class. E.g. the collection of vintage saxophones is covered by the Concept 'Saxophone' with the Parameter 'Vintage'.
domain: Concept
label: ricopre @it
range: Collection
sub property of: associatedWith
inverse of: is covered by

defines
type: ObjectProperty
comment: A relation between a Description and a Concept, e.g. a Workflow for a governmental Organization defines the Role 'officer', or 'the Italian Traffic Law defines the role Vehicle'.
domain: Description
label: definisce @it
range: Concept
sub property of: uses concept
inverse of: is defined in

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

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

describes
type: ObjectProperty
comment: The relation between a Description and an Entity : a Description gives a unity to a Collection of parts (the components), or constituents, by assigning a Role to each of them in the context of a whole Object (the system). A same Entity can be given different descriptions, for example, an old cradle can be given a unifying Description based on the original aesthetic design, the functionality it was built for, or a new aesthetic functionality in which it can be used as a flower pot.
domain: Description
label: descrive @it
range: Entity
sub property of: associatedWith
inverse of: is described by
property chain axiom: defines
property chain axiom: classifies
property chain axiom: uses concept

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

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

executes task
type: ObjectProperty
comment: A relation between an action and a task, e.g. 'putting some water in a pot and putting the pot on a fire until the water starts bubbling' executes the task 'boiling'.
domain: Action
label: esegue il task @it
range: Task
sub property of: is classified by
inverse of: is executed in

expands
type: ObjectProperty
comment: A partial order relation that holds between descriptions. It represents the proper part relation between a description and another description featuring the same properties as the former, with at least one additional one. Descriptions can be expanded either by adding other descriptions as parts, or by refining concepts that are used by them. An 'intention' to expand must be present (unless purely formal theories are considered, but even in this case a criterion of relevance is usually active).
domain: Description
label: espande @it
range: Description
sub property of: is related to description
inverse of: is expanded in

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

expresses concept
type: ObjectProperty
comment: A relation between an InformationObject and a Concept , e.g. the term "dog" expresses the Concept "dog". For expressing a relational meaning, see the more general object property: expresses
domain: Information object
label: esprime il concetto @it
range: Concept
sub property of: expresses
inverse of: is concept expressed by

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

follows
type: ObjectProperty
type: TransitiveProperty
comment: A relation between entities, expressing a 'sequence' schema. E.g. 'year 2000 follows 1999', 'preparing coffee' follows 'deciding what coffee to use', 'II World War follows I World War', etc. It can be used between tasks, processes or time intervals, and subproperties would fit best in order to distinguish the different uses.
domain: Entity
label: segue @it
range: Entity
sub property of: associatedWith
inverse of: precedes

has common boundary
type: ObjectProperty
type: SymmetricProperty
comment: A relation to encode either formal or informal characterizations of 'boundaries' common to two different entities: an Event that ends when another begins, two abstract regions that have a common topological boundary, two objects that are said to be 'in contact' from a commonsense perspective, etc.
domain: Entity
range: Entity
sub property of: associatedWith

has component
type: AsymmetricProperty
type: ObjectProperty
comment: The hasProperPart relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the Object.
domain: Entity
label: ha componente @it
range: Entity
sub property of: has proper part
inverse of: is component of

has constituent
type: ObjectProperty
comment: 'Constituency' depends on some layering of the world described by the ontology. For example, scientific granularities (e.g. body-organ-tissue-cell) or ontological 'strata' (e.g. social-mental-biological-physical) are typical layerings. Intuitively, a constituent is a part belonging to a lower layer. Since layering is actually a partition of the world described by the ontology, constituents are not properly classified as parts, although this kinship can be intuitive for common sense. A desirable advantage of this distinction is that we are able to talk e.g. of physical constituents of non-physical objects (e.g. systems), while this is not possible in terms of parts. Example of are the persons constituting a social system, the molecules constituting a person, the atoms constituting a river, etc. In all these examples, we notice a typical discontinuity between the constituted and the constituent object: e.g. a social system is conceptualized at a different layer from the persons that constitute it, a person is conceptualized at a different layer from the molecules that constitute them, and a river is conceptualized at a different layer from the atoms that constitute it.
domain: Entity
label: ha costituente @it
range: Entity
sub property of: associatedWith
inverse of: is constituent of

has constraint
type: ObjectProperty
comment: A relation between parameters and entities. It allows to assert generic constraints (encoded as parameters), e.g. MinimumAgeForDriving isConstraintFor John (where John is a legal subject under the TrafficLaw). The intended semantics (not expressible in OWL) is that a Parameter isParameterFor a Concept that classifies an Entity; moreover, it entails that a Parameter parametrizes a Region that isRegionFor that Entity.
domain: Entity
label: ha vincolo @it
range: Parameter
sub property of: is classified by
inverse of: is constraint for

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

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

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

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

has location
type: ObjectProperty
comment: A generic, relative spatial location, holding between any entities. E.g. 'the cat is on the mat', 'Omar is in Samarcanda', 'the wound is close to the femural artery'. For 'absolute' locations, see SpaceRegion
domain: Entity
label: ha localizzazione @it
range: Entity
sub property of: associatedWith
inverse of: is location of

has member
type: ObjectProperty
comment: A relation between collections and entities, e.g. 'my collection of saxophones includes an old Adolphe Sax original alto' (i.e. my collection has member an Adolphe Sax alto).
domain: Collection
label: ha membro @it
range: Entity
sub property of: associatedWith
inverse of: is member of

has parameter
type: ObjectProperty
comment: A Concept can have a Parameter that constrains the attributes that a classified Entity can have in a certain Situation, e.g. a 4WheelDriver Role definedIn the ItalianTrafficLaw has a MinimumAge parameter on the Amount 16.
domain: Concept
label: ha parametro @it
range: Parameter
sub property of: is related to concept
inverse of: is parameter for

has parameter data value
type: DatatypeProperty
comment: Parametrizes values from a datatype. For example, a Parameter MinimumAgeForDriving hasParameterDataValue 18 on datatype xsd:int, in the Italian traffic code. In this example, MinimumAgeForDriving isDefinedIn the Norm ItalianTrafficCodeAgeDriving. More complex parametrization requires workarounds. E.g. AgeRangeForDrugUsage could parametrize data value: 14 to 50 on the datatype: xsd:int. Since complex datatypes are not allowed in OWL1.0, a solution to this can only work by creating two 'sub-parameters': MinimumAgeForDrugUsage (that hasParameterDataValue 14) and MaximumAgeForDrugUsage (that hasParameterDataValue 50), which are components of (cf. hasComponent) the main Parameter AgeRangeForDrugUsage. Ordering on subparameters can be created by using or specializing the object property 'precedes'.
domain: Parameter
label: ha valore @it
sub property of: has data value

has part
type: ObjectProperty
type: ReflexiveProperty
type: TransitiveProperty
comment: A schematic relation between any entities, e.g. 'the human body has a brain as part', '20th century contains year 1923', 'World War II includes the Pearl Harbour event'. Parthood should assume the basic properties of mereology: transitivity, antisymmetry, and reflexivity (propert Parthood of course misses reflexivity). However, antisymmetry is not supported in OWL2 explicitly, therefore DUL has to adopt one of two patterns: 1) dropping asymmetry axioms, while granting reflexivity: this means that symmetry is not enforced, but permitted for the case of reflexivity. Of course, in this way we cannot prevent symmetric usages of hasPart; 2) dropping the reflexivity axiom, and enforce asymmetry: in this case, we would prevent all symmetric usages, but we loose the possibility of enforcing reflexivity, which is commonsensical in parthood. In DUL, we adopt pattern #1 for partOf, and pattern #2 for properPartOf, which seems a good approximation: due to the lack of inheritance of property characteristics, each asymmetric hasPropertPart assertion would also be a reflexive hasPart assertion (reflexive reduction design pattern). Subproperties and restrictions can be used to specialize hasPart for objects, events, etc.
domain: Entity
label: ha parte @it
range: Entity
sub property of: associatedWith
inverse of: is part of
property chain axiom:
  inverse of: includesWhole
property chain axiom: includesPart

has participant
type: ObjectProperty
comment: A relation between an object and a process, e.g. 'John took part in the discussion', 'a large mass of snow fell during the avalanche', or 'a cook, some sugar, flour, etc. are all present in the cooking of a cake'.
domain: Event
label: ha come partecipante @it
range: Object
sub property of: associatedWith
inverse of: is participant in

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

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

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

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

has region
type: ObjectProperty
comment: A relation between entities and regions, e.g. 'the number of wheels of that truck is 12', 'the time of the experiment is August 9th, 2004', 'the whale has been localized at 34 degrees E, 20 degrees S'.
domain: Entity
label: ha attributo @it
range: Region
sub property of: associatedWith
inverse of: is region for

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

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

has setting
type: ObjectProperty
comment: A relation between entities and situations, e.g. 'this morning I've prepared my coffee with a new fantastic Arabica', i.e.: (an amount of) a new fantastic Arabica hasSetting the preparation of my coffee this morning.
domain: Entity
label: è nel contesto di @it
range: Situation
sub property of: associatedWith
inverse of: is setting for

has task
type: ObjectProperty
comment: A relation between roles and tasks, e.g. 'students have the duty of giving exams' (i.e. the Role 'student' hasTask the Task 'giving exams').
domain: Role
label: ha come obiettivo @it
range: Task
sub property of: is related to concept
inverse of: is task of

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

includes action
type: ObjectProperty
comment: A relation between situations and actions, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: the preparation of my coffee this morning included a burning of my fingers).
domain: Situation
label: include azione @it
range: Action
sub property of: includes event
inverse of: is action included in

includes agent
type: ObjectProperty
comment: A relation between situations and persons, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: the preparation of my coffee this morning included me).
domain: Situation
label: include l'agente @it
range: Agent
sub property of: includes object
inverse of: is agent included in

includes event
type: ObjectProperty
comment: A relation between situations and events, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: the preparation of my coffee this morning included a burning of my fingers).
domain: Situation
label: include l'evento @it
range: Event
sub property of: is setting for
inverse of: is event included in

includes object
type: ObjectProperty
comment: A relation between situations and objects, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: the preparation of my coffee this morning included me).
domain: Situation
label: include l'oggetto @it
range: Object
sub property of: is setting for
inverse of: is object included in

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

includes time
type: ObjectProperty
comment: A relation between situations and time intervals, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: preparing my coffee was held this morning). A data value attached to the time interval typically complements this modelling pattern.
domain: Situation
label: include tempo @it
range: Time interval
sub property of: is setting for
inverse of: is time included in

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

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

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

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

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

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

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

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

is classified by
type: ObjectProperty
comment: A relation between a Concept and an Entity, e.g. 'John is considered a typical rude man'; your last concert constitutes the achievement of a lifetime; '20-year-old means she's mature enough'.
domain: Entity
label: è classificato da @it
range: Concept
sub property of: associatedWith

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

is concept expressed by
type: ObjectProperty
comment: A relation between an InformationObject and a Concept , e.g. the term "dog" expresses the Concept "dog". For expressing a relational meaning, see the more general object property: expresses
domain: Concept
label: è un concetto espresso da @it
range: Information object
sub property of: is expressed by

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

is conceptualized by
type: ObjectProperty
comment: A relation stating that an Agent is internally representing a Description . E.g., 'John believes in the conspiracy theory'; 'Niels Bohr created a solar-system metaphor for his atomic theory'; 'Jacques assumes all swans are white'; 'the task force shares the attack plan'.
domain: Social object
label: è concettualizzato da @it
range: Agent
sub property of: associatedWith

is concretely expressed by
type: ObjectProperty
comment: A relation between an InformationRealization and a Description, e.g. 'the printout of the Italian Constitution concretelyExpresses the Italian Constitution'. It should be supplied also with a rule stating that the InformationRealization realizes an InformationObject that expresses the Description
domain: Social object
label: è espresso concretamente da @it
range: Information realization
sub property of: associatedWith

is constituent of
type: ObjectProperty
comment: 'Constituency' depends on some layering of the world described by the ontology. For example, scientific granularities (e.g. body-organ-tissue-cell) or ontological 'strata' (e.g. social-mental-biological-physical) are typical layerings. Intuitively, a constituent is a part belonging to a lower layer. Since layering is actually a partition of the world described by the ontology, constituents are not properly classified as parts, although this kinship can be intuitive for common sense. A desirable advantage of this distinction is that we are able to talk e.g. of physical constituents of non-physical objects (e.g. systems), while this is not possible in terms of parts. Example of are the persons constituting a social system, the molecules constituting a person, the atoms constituting a river, etc. In all these examples, we notice a typical discontinuity between the constituted and the constituent object: e.g. a social system is conceptualized at a different layer from the persons that constitute it, a person is conceptualized at a different layer from the molecules that constitute them, and a river is conceptualized at a different layer from the atoms that constitute it.
domain: Entity
label: è costituente di @it
range: Entity
sub property of: associatedWith

is constraint for
type: ObjectProperty
comment: A relation between parameters and entities. It allows to assert generic constraints (encoded as parameters), e.g. MinimumAgeForDriving isConstraintFor John (where John is a legal subject under the TrafficLaw). The intended semantics (not expressible in OWL) is that a Parameter isConstraintFor and Entity if the Parameter isParameterFor a Concept that classifies that Entity; moreover, it entails that a Parameter parametrizes a Region that isRegionFor that Entity. The use in OWL is therefore a shortcut to annotate what Parameter constrains what Entity
domain: Parameter
label: è un vincolo per @it
range: Entity
sub property of: classifies

is covered by
type: ObjectProperty
comment: A relation between concepts and collections, where a Concept is said to cover a Collection; it corresponds to a link between the (reified) intensional and extensional interpretations of a (reified) class. E.g. the collection of vintage saxophones is covered by the Concept 'Saxophone' with the Parameter 'Vintage'.
domain: Collection
label: è ricoperto da @it
range: Concept
sub property of: associatedWith

is defined in
type: ObjectProperty
comment: A relation between a Description and a Concept, e.g. a Workflow for a governmental Organization defines the Role 'officer', or 'the Italian Traffic Law defines the role Vehicle'.
domain: Concept
label: è definito in @it
range: Description
sub property of: is concept used in

is described by
type: ObjectProperty
comment: The relation between an Entity and a Description: a Description gives a unity to a Collection of parts (the components), or constituents, by assigning a Role to each of them in the context of a whole Object (the system). A same Entity can be given different descriptions, for example, an old cradle can be given a unifying Description based on the original aesthetic design, the functionality it was built for, or a new aesthetic functionality in which it can be used as a flower pot.
domain: Entity
label: è descritto da @it
range: Description
sub property of: associatedWith

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

is executed in
type: ObjectProperty
comment: A relation between an action and a task, e.g. 'putting some water in a pot and putting the pot on a fire until the water starts bubbling' executes the task 'boiling'.
domain: Task
label: è eseguito mediante @it
range: Action
sub property of: classifies

is expanded in
type: ObjectProperty
comment: A partial order relation that holds between descriptions. It represents the proper part relation between a description and another description featuring the same properties as the former, with at least one additional one. Descriptions can be expanded either by adding other descriptions as parts, or by refining concepts that are used by them. An 'intention' to expand must be present (unless purely formal theories are considered, but even in this case a criterion of relevance is usually active).
domain: Description
label: è espansa in @it
range: Description
sub property of: is related to description

is expressed by
type: ObjectProperty
comment: A relation between a dul:SocialObject (the 'meaning') and a dul:InformationObject (the 'expression'). For example: 'A Beehive is a structure in which bees are kept, typically in the form of a dome or box.' (Oxford dictionary)'; 'the term Beehive expresses the concept Beehive in my apiculture ontology'. The intuition for 'meaning' is intended to be very broad. A separate, large comment is included in the encoding of 'expresses', for those who want to investigate more on what kind of meaning can be represented in what form.
domain: Social object
label: è espresso da @it
range: Information object
sub property of: associatedWith

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

is location of
type: ObjectProperty
comment: A generic, relative localization, holding between any entities. E.g. 'Rome is the seat of the Pope', 'the liver is the location of the tumor'. For 'absolute' locations, see SpaceRegion
domain: Entity
label: è una localizzazione di @it
range: Entity
sub property of: associatedWith

is member of
type: ObjectProperty
comment: A relation between collections and entities, e.g. 'the Night Watch by Rembrandt is in the Rijksmuseum collection'; 'Davide is member of the Pen Club', 'Igor is one the subjects chosen for the experiment'.
domain: Entity
label: è membro di @it
range: Collection
sub property of: associatedWith

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

is observable at
type: ObjectProperty
comment: A relation to represent a (past, present or future) TimeInterval at which an Entity is observable. In order to encode a specific time, a data value should be related to the TimeInterval. An alternative way of representing time is the datatype property: hasIntervalDate
domain: Entity
label: è osservabile a @it
range: Time interval
sub property of: has region
inverse of: is time of observation of

is parameter for
type: ObjectProperty
comment: A Concept can have a Parameter that constrains the attributes that a classified Entity can have in a certain Situation, e.g. a 4WheelDriver Role definedIn the ItalianTrafficLaw has a MinimumAge parameter on the Amount 16.
domain: Parameter
label: è un parametro per @it
range: Concept
sub property of: is related to concept

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

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

is participant in
type: ObjectProperty
comment: A relation between an object and a process, e.g. 'John took part in the discussion', 'a large mass of snow fell during the avalanche', or 'a cook, some sugar, flour, etc. are all present in the cooking of a cake'.
domain: Object
label: è un partecipante a @it
range: Event
sub property of: associatedWith

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

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

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

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

is realized by
type: ObjectProperty
comment: A relation between an information realization and an information object, e.g. the paper copy of the Italian Constitution realizes the text of the Constitution.
domain: Information object
label: è realizzato da @it
range: Information realization
sub property of: associatedWith
inverse of: realizes

is reference of
type: ObjectProperty
comment: A relation between information objects and any Entity (including information objects). It can be used to talk about e.g. entities are references of proper nouns: the proper noun 'Leonardo da Vinci' isAbout the Person Leonardo da Vinci; as well as to talk about sets of entities that can be described by a common noun: the common noun 'person' isAbout the set of all persons in a domain of discourse, which can be represented in DOLCE-Ultralite as an individual of the class: Collection . The isReferenceOf relation is irreflexive, differently from its inverse isAbout.
domain: Entity
label: è il riferimento di @it
range: Information object
sub property of: associatedWith

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

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

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

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

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

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

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

is setting for
type: ObjectProperty
comment: A relation between situations and entities, e.g. 'this morning I've prepared my coffee with a new fantastic Arabica', i.e.: the preparation of my coffee this morning is the setting for (an amount of) a new fantastic Arabica.
domain: Situation
label: include @it
range: Entity
sub property of: associatedWith

is specialized by
type: ObjectProperty
type: TransitiveProperty
comment: A partial order relation that holds between social objects. It represents the subsumption relation between e.g. a Concept and another Concept that is broader in extensional interpretation, but narrowe in intensional interpretation. E.g. PhDStudent Role specializes Student Role
domain: Social object
label: è specializzato da @it
range: Social object
sub property of: associatedWith
inverse of: specializes

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

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

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

is task of
type: ObjectProperty
comment: A relation between roles and tasks, e.g. 'students have the duty of giving exams' (i.e. the Role 'student' hasTask the Task 'giving exams').
domain: Task
label: è un obiettivo per @it
range: Role
sub property of: is related to concept

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

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

is time of observation of
type: ObjectProperty
comment: A relation to represent a (past, present or future) TimeInterval at which an Entity is observable. In order to encode a specific time, a data value should be related to the TimeInterval. An alternative way of representing time is the datatype property: hasIntervalDate
domain: Time interval
label: è il tempo di osservazione di @it
range: Entity
sub property of: is region for

is unified by
type: ObjectProperty
comment: A Collection has a unification criterion, provided by a Description; for example, a community of practice can be unified by a shared theory or interest, e.g. the community that makes research on mirror neurons shares some core knowledge about mirror neurons, which can be represented as a Description MirrorNeuronTheory that unifies the community. There can be several unifying descriptions.
domain: Collection
label: è unificato da @it
range: Description
sub property of: associatedWith
inverse of: unifies

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

overlaps
type: ObjectProperty
type: SymmetricProperty
comment: A schematic relation between any entities, e.g. 'the chest region overlaps with the abdomen region', 'my spoken words overlap with hers', 'the time of my leave overlaps with the time of your arrival', 'fibromyalgia overlaps with other conditions'. Subproperties and restrictions can be used to specialize overlaps for objects, events, time intervals, etc.
domain: Entity
label: sovrapposto a @it
range: Entity
sub property of: associatedWith

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

precedes
type: ObjectProperty
type: TransitiveProperty
comment: A relation between entities, expressing a 'sequence' schema. E.g. 'year 1999 precedes 2000', 'deciding what coffee to use' precedes 'preparing coffee', 'World War II follows World War I', 'in the Milan to Rome autoroute, Bologna precedes Florence', etc. It can then be used between tasks, processes, time intervals, spatially locate objects, situations, etc. Subproperties can be defined in order to distinguish the different uses.
domain: Entity
label: precede @it
range: Entity
sub property of: associatedWith

realizes
type: ObjectProperty
comment: A relation between an information realization and an information object, e.g. the paper copy of the Italian Constitution realizes the text of the Constitution.
domain: Information realization
label: realizza @it
range: Information object
sub property of: associatedWith

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

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

is in the same setting as
type: ObjectProperty
type: SymmetricProperty
comment: A relation between two entities participating in a same Situation; e.g., 'Our company provides an antivenom service' (the situation is the service, the two entities are the company and the antivenom). @it
domain: Entity
label: è nella stessa situazione di @it
range: Entity
sub property of: associatedWith
property chain axiom: has setting
property chain axiom: is setting for

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

specializes
type: ObjectProperty
type: TransitiveProperty
comment: A partial order relation that holds between social objects. It mainly represents the subsumption relation between e.g. a Concept or Description and another Concept (resp. Description) that is broader in extensional interpretation, but narrower in intensional interpretation. For example, the role PhDStudent specializes the role Student. Another possible use is between a Collection that isCoveredBy a Concept A, and another Collection that isCoveredBy a Concept B that on its turm specializes A. For example, the 70,000 series Selmer Mark VI saxophone Collection specializes the Selmer Mark VI saxophone Collection.
domain: Social object
label: specializza @it
range: Social object
sub property of: associatedWith

unifies
type: ObjectProperty
comment: A Collection has a unification criterion, provided by a Description; for example, a community of practice can be unified by a shared theory or interest, e.g. the community that makes research on mirror neurons shares some core knowledge about mirror neurons, which can be represented as a Description MirrorNeuronTheory that unifies the community. There can be several unifying descriptions.
domain: Description
label: unifica @it
range: Collection
sub property of: associatedWith

uses concept
type: ObjectProperty
comment: A generic relation holding between a Description and a Concept. In order to be used, a Concept must be previously definedIn another Description. This last condition cannot be encoded for object properties in OWL.
domain: Description
label: usa il concetto @it
range: Concept
sub property of: associatedWith