DUL_ssn.owl (extract of DUL.owl)

DO NOT EDIT - This is a semi-automatically generated documentation automatically derived from the subset of http://www.loa-cnr.it/ontologies/DUL.owl which is reused in the SSN ontology. It includes the classes and properties which are directly used by the SSN ontology and the associated classes and properties which are required to have a standalone module.

Version

3.25 (a.k.a. DUL 2.2)

The URI for the complete version of this ontology is http://www.loa-cnr.it/ontologies/DUL.owl#

When used in XML documents the suggested prefix is DUL

Table of Contents

Section	Module	Classes	Properties
DUL	DUL	Abstract, Agent, Collection, Concept, Description, Design, DesignedArtifact, Entity, Event, Goal, InformationEntity, InformationObject, InformationRealization, LocalConcept, Method, Object, PhysicalAgent, PhysicalArtifact, PhysicalObject, Place, Plan, PlanExecution, Process, Quality, Region, Role, Situation, SocialAgent, SocialObject	actsFor, actsThrough, classifies, conceptualizes, concretelyExpresses, defines, describes, expresses, follows, hasComponent, hasConstituent, hasLocation, hasPart, hasParticipant, hasQuality, hasRegion, hasSetting, includesEvent, includesObject, isClassifiedBy, isComponentOf, isConceptUsedIn, isConceptualizedBy, isConcretelyExpressedBy, isConstituentOf, isDefinedIn, isDescribedBy, isEventIncludedIn, isExpressedBy, isLocationOf, isObjectIncludedIn, isPartOf, isParticipantIn, isQualityOf, isRealizedBy, isRegionFor, isSatisfiedBy, isSettingFor, overlaps, precedes, realizes, satisfies, usesConcept

Section DUL

Introduction DUL

This part of the ontology defines 29 classes and 43 properties .

Module	Term Name	Type	Definition
DUL	Abstract	class	Any Entity that cannot be located in space-time [...]
DUL	Agent	class	Any agentive Object , either physical [...]
DUL	Collection	class	Any container for entities that share one or more common properties [...]
DUL	Concept	class	A Concept is a SocialObject, and isDefinedIn some Description [...]
DUL	Description	class	A Description is a SocialObject that represents a conceptualization [...]
DUL	Design	class	A Description of the Situation, in terms of structure and function, held by an Entity for some reason [...]
DUL	DesignedArtifact	class	A PhysicalArtifact that is also described by a Design [...]
DUL	Entity	class	Anything: real, possible, or imaginary, which some modeller wants to talk about for some purpose.
DUL	Event	class	Any physical, social, or mental process, event, or state [...]
DUL	Goal	class	The Description of a Situation that is desired by an Agent, and usually associated to a Plan that describes how to actually achieve it
DUL	InformationEntity	class	A piece of information, be it concretely realized or not.
DUL	InformationObject	class	A piece of information, such as a musical composition, a text, a word, a picture, independently from how it is concretely realized.
DUL	InformationRealization	class	A concrete realization of an InformationObject [...]
DUL	LocalConcept	class	A Concept that isDefinedIn exactly 1 Description [...]
DUL	Method	class	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 [...]
DUL	Object	class	Any physical, social, or mental object, or a substance
DUL	PhysicalAgent	class	A PhysicalObject that is capable of self-representing (conceptualizing) a Description in order to plan an Action [...]
DUL	PhysicalArtifact	class	Any PhysicalObject that isDescribedBy a Plan [...]
DUL	PhysicalObject	class	Any Object that has a proper space region [...]
DUL	Place	class	A location, in a very generic sense [...]
DUL	Plan	class	A Description having an explicit Goal, to be achieved by executing the plan
DUL	PlanExecution	class	Plan executions are situations that proactively satisfy a plan [...]
DUL	Process	class	This is a placeholder for events that are considered in their evolution, or anyway not strictly dependent on agents, tasks, and plans [...]
DUL	Quality	class	Any aspect of an Entity (but not a part of it), which cannot exist without that Entity [...]
DUL	Region	class	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 [...]
DUL	Role	class	A Concept that classifies an Object
DUL	Situation	class	A view, consistent with ('satisfying') a Description, on a set of entities [...]
DUL	SocialAgent	class	Any individual whose existence is granted simply by its social communicability and capability of action (through some PhysicalAgent).
DUL	SocialObject	class	Any Object that exists only within some communication Event, in which at least one PhysicalObject participates in [...]
DUL	actsFor	property	The relation holding between any Agent, and a SocialAgent [...]
DUL	actsThrough	property	The relation holding between a PhysicalAgent and a SocialAgent [...]
DUL	classifies	property	A relation between a Concept and an Entity [...]
DUL	conceptualizes	property	A relation stating that an Agent is internally representing a SocialObject: situations, descriptions, concepts, etc. [...]
DUL	concretelyExpresses	property	A relation between an InformationRealization and a Description [...]
DUL	defines	property	A relation between a Description and a Concept [...]
DUL	describes	property	The relation between a Description and an Entity [...]
DUL	expresses	property	A relation between an InformationObject and a 'meaning', generalized here as a 'SocialObject' [...]
DUL	follows	property	A relation between entities, expressing a 'sequence' schema [...]
DUL	hasComponent	property	The hasPart relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the Object.
DUL	hasConstituent	property	'Constituency' depends on some layering of the world described by the ontology [...]
DUL	hasLocation	property	A generic, relative localization, holding between any entities [...]
DUL	hasPart	property	A schematic relation between any entities [...]
DUL	hasParticipant	property	A relation between an object and a process [...]
DUL	hasQuality	property	A relation between entities and qualities [...]
DUL	hasRegion	property	A relation between entities and regions [...]
DUL	hasSetting	property	A relation between entities and situations [...]
DUL	includesEvent	property	A relation between situations and events [...]
DUL	includesObject	property	A relation between situations and objects [...]
DUL	isClassifiedBy	property	A relation between a Concept and an Entity [...]
DUL	isComponentOf	property	The hasPart relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the Object.
DUL	isConceptUsedIn	property	A more generic relation holding between a Description and a Concept [...]
DUL	isConceptualizedBy	property	A relation stating that an Agent is internally representing a Description [...]
DUL	isConcretelyExpressedBy	property	A relation between an InformationRealization and a Description [...]
DUL	isConstituentOf	property	'Constituency' depends on some layering of the world described by the ontology [...]
DUL	isDefinedIn	property	A relation between a Description and a Concept [...]
DUL	isDescribedBy	property	The relation between an Entity and a Description [...]
DUL	isEventIncludedIn	property
DUL	isExpressedBy	property	A relation between a dul:SocialObject (the 'meaning') and a dul:InformationObject (the 'expression') [...]
DUL	isLocationOf	property	A generic, relative localization, holding between any entities [...]
DUL	isObjectIncludedIn	property
DUL	isPartOf	property	A relation between any entities [...]
DUL	isParticipantIn	property	A relation between an object and a process [...]
DUL	isQualityOf	property	A relation between entities and qualities [...]
DUL	isRealizedBy	property	A relation between an information realization and an information object [...]
DUL	isRegionFor	property	A relation between entities and regions [...]
DUL	isSatisfiedBy	property	A relation between a Situation and a Description [...]
DUL	isSettingFor	property	A relation between situations and entities [...]
DUL	overlaps	property	A schematic relation between any entities [...]
DUL	precedes	property	A relation between entities, expressing a 'sequence' schema [...]
DUL	realizes	property	A relation between an information realization and an information object [...]
DUL	satisfies	property	A relation between a Situation and a Description [...]
DUL	usesConcept	property	A generic relation holding between a Description and a Concept [...]

Module DUL

Abstract

Any Entity that cannot be located in space-time. E.g. mathematical entities: formal semantics elements, regions within dimensional spaces, etc.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Abstract
Label:	Abstract
Subclass of	DUL:Entity
Disjoint with	DUL:Event, DUL:Object and DUL:Quality
Paraphrase (experimental)	A DUL:Abstract is something that is a DUL:Entity A DUL:Abstract is not a DUL:Event and is not a DUL:Object and is not a DUL:Quality

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Abstract">
<rdfs:label xml:lang="en">Abstract</rdfs:label>
<rdfs:label xml:lang="it">Astratto</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Event"/>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Quality"/>
<rdfs:comment>
Any Entity that cannot be located in space-time. E.g. mathematical 
entities: formal semantics elements, regions within dimensional spaces, 
etc.
</rdfs:comment>
</owl:Class>

Agent

Any agentive Object , either physical (e.g. a whale, a robot, an oak), or social (e.g. a corporation, an institution, a community).

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.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Agent
Label:	Agent
Subclass of	DUL:Object
Equivalent to	Union of : DUL:PhysicalAgent and DUL:SocialAgent
Paraphrase (experimental)	A DUL:Agent is something that is a DUL:Object A DUL:Agent is something that must be a DUL:PhysicalAgent or DUL:SocialAgent

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Agent">
<rdfs:label xml:lang="en">Agent</rdfs:label>
<rdfs:label xml:lang="it">Agente</rdfs:label>
<owl:equivalentClass>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalAgent"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#SocialAgent"/>
</owl:unionOf>
</owl:Class>
</owl:equivalentClass>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
Any agentive Object , either physical (e.g. a whale, a robot, an oak), 
or social (e.g. a corporation, an institution, a community).
</rdfs:comment>
<rdfs: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.
</rdfs:comment>
</owl:Class>

Collection

Any container for entities that share one or more common properties. E.g. "stone objects", "the nurses", "the Louvre Aegyptian collection", all the elections for the Italian President of the Republic. A collection is not a logical class: a collection is a first-order entity, while a class is second-order.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Collection
Label:	Collection
Subclass of	DUL:SocialObject and things that have a DUL:hasPart property who must be a DUL:Collection
Paraphrase (experimental)	A DUL:Collection is something that is a DUL:SocialObject and has a DUL:hasPart property who must be a DUL:Collection

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Collection">
<rdfs:label xml:lang="en">Collection</rdfs:label>
<rdfs:label xml:lang="it">Collezione</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Collection"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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.
</rdfs:comment>
</owl:Class>

Concept

A Concept is a SocialObject, and isDefinedIn some Description; once defined, a Concept can be used in other Description(s). If a Concept isDefinedIn exactly one Description, see the LocalConcept class. The classifies relation relates Concept(s) to Entity(s) at some TimeInterval

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Concept
Label:	Concept
Subclass of	DUL:SocialObject, things that have a DUL:hasPart property who must be a DUL:Concept and things that have a DUL:isDefinedIn property who may be a DUL:Description
Disjoint with	DUL:Description, DUL:InformationObject, DUL:Situation and DUL:SocialAgent
Paraphrase (experimental)	A DUL:Concept is something that is a DUL:SocialObject and has a DUL:hasPart property who must be a DUL:Concept and has a DUL:isDefinedIn property who may be a DUL:Description A DUL:Concept is not a DUL:Description and is not a DUL:InformationObject and is not a DUL:Situation and is not a DUL:SocialAgent

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Concept">
<rdfs:label xml:lang="en">Concept</rdfs:label>
<rdfs:label xml:lang="it">Concetto</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Concept"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isDefinedIn"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
</owl:Restriction>
</rdfs:subClassOf>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject"/>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialAgent"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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
</rdfs:comment>
</owl:Class>

Description

A Description is a SocialObject that represents a conceptualization. It can be thought also as a 'descriptive context' that uses or defines concepts in order to create a view on a 'relational context' (cf. Situation) out of a set of data or observations. For example, a Plan is a Description of some actions to be executed by agents in a certain way, with certain parameters; a Diagnosis is a Description that provides an interpretation for a set of observed entities, etc.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Description
Label:	Description
Subclass of	DUL:SocialObject
Disjoint with	DUL:InformationObject, DUL:Situation and DUL:SocialAgent
Paraphrase (experimental)	A DUL:Description is something that is a DUL:SocialObject A DUL:Description is not a DUL:InformationObject and is not a DUL:Situation and is not a DUL:SocialAgent

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Description">
<rdfs:label xml:lang="en">Description</rdfs:label>
<rdfs:label xml:lang="it">Descrizione</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject"/>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialAgent"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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.
</rdfs:comment>
</owl:Class>

Design

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

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Design
Label:	Design
Subclass of	DUL:Description
Paraphrase (experimental)	A DUL:Design is something that is a DUL:Description

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Design">
<rdfs:label xml:lang="en">Design</rdfs:label>
<rdfs:label xml:lang="it">Design</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<rdfs: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 a specific law. While designs typically describe 
entities to be constructed, they can also be used to describe 
'refunctionalized' entities, or to hypothesize unknown functions.
</rdfs:comment>
</owl:Class>

DesignedArtifact

A PhysicalArtifact that is also described by a Design. This excludes simple recycling or refunctionalization of natural objects. Most common sense 'artifacts' can be included in this class: cars, lamps, houses, chips, etc.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#DesignedArtifact
Label:	Designed artifact
Subclass of	DUL:PhysicalArtifact and things that have a DUL:isDescribedBy property who may be a DUL:Design
Paraphrase (experimental)	A DUL:DesignedArtifact is something that is a DUL:PhysicalArtifact and has a DUL:isDescribedBy property who may be a DUL:Design

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#DesignedArtifact">
<rdfs:label xml:lang="en">Designed artifact</rdfs:label>
<rdfs:label xml:lang="it">Artefatto progettato</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalArtifact"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isDescribedBy"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Design"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs: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.
</rdfs:comment>
</owl:Class>

Entity

Anything: real, possible, or imaginary, which some modeller wants to talk about for some purpose.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Entity
Label:	Entity
Equivalent to	Union of : DUL:Abstract , DUL:Event , DUL:Object , DUL:Quality and DUL:Region
Paraphrase (experimental)	A DUL:Entity is something that must be a DUL:Abstract, DUL:Event, DUL:Object, DUL:Quality or DUL:Region

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Entity">
<rdfs:label xml:lang="en">Entity</rdfs:label>
<rdfs:label xml:lang="it">Entità</rdfs:label>
<owl:equivalentClass>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Abstract"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Event"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Quality"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Region"/>
</owl:unionOf>
</owl:Class>
</owl:equivalentClass>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
Anything: real, possible, or imaginary, which some modeller wants to 
talk about for some purpose.
</rdfs:comment>
</owl:Class>

Event

Any physical, social, or mental process, event, or state. More theoretically, events can be classified in different ways, possibly based on 'aspect' (e.g. stative, continuous, accomplishement, achievement, etc.), on 'agentivity' (e.g. intentional, natural, etc.), or on 'typical participants' (e.g. human, physical, abstract, food, etc.). Here no special direction is taken, and the following explains why: events are related to observable situations, and they can have different views at a same time. If a position has to be suggested here anyway, the participant-based classification of events seems the most stable and appropriate for many modelling problems. (1) Alternative aspectual views Consider a same event 'rock erosion in the Sinni valley': it can be conceptualized as an accomplishment (what has brought a certain state to occur), as an achievement (the state resulting from a previous accomplishment), as a punctual event (if we collapse the time interval of the erosion into a time point), or as a transition (something that has changed a state to a different one). In the erosion case, we could therefore have good motivations to shift from one aspect to another: a) causation focus, b) effectual focus, c) historical condensation d) transition (causality). The different views refer to the same event, but are still different: how to live with this seeming paradox? A typical solution e.g. in linguistics (cf. Levin's aspectual classes) and in DOLCE Full (cf. WonderWeb D18 axiomatization) is to classify events based on aspectual differences. But this solution would create different identities for a same event, where the difference is only based on the modeller's attitude. An alternative solution is applied here, and exploits the notion of (observable) Situation; a Situation is a view, consistent with a Description, which can be observed of a set of entities. It can also be seen as a 'relational context' created by an observer on the basis of a 'frame'. Therefore, a Situation allows to create a context where each particular view can have a proper identity, while the Event preserves its own identity. For example, ErosionAsAccomplishment is a Situation where rock erosion is observed as a process leading to a certain achievement: the conditions (roles, parameters) that suggest such view are stated in a Description, which acts as a 'theory of accomplishments'. Similarly, ErosionAsTransition is a Situation where rock erosion is observed as an event that has changed a state to another: the conditions for such interpretation are stated in a different Description, which acts as a 'theory of state transitions'. Consider that in no case the Event is changed or enriched in parts by the aspectual view. (2) Alternative intentionality views Similarly to aspectual views, several intentionality views can be provided for a same Event. For example, one can investigate if an avalanche has been caused by immediate natural forces, or if there is any hint of an intentional effort to activate those natural forces. Also in this case, the Event as such has not different identities, while the causal analysis generates situations with different identities, according to what Description is taken for interpreting the Event. On the other hand, if the possible actions of an Agent causing the starting of an avalanche are taken as parts of the Event, then this makes its identity change, because we are adding a part to it. Therefore, if intentionality is a criterion to classify events or not depends on if an ontology designer wants to consider causality as a relevant dimension for events' identity. (3) Alternative participant views A slightly different case is when we consider the basic participants to an Event. In this case, the identity of the Event is affected by the participating objects, because it depends on them. For example, if snow, mountain slopes, wind, waves, etc. are considered as an avalanche basic participants, or if we also want to add water, human agents, etc., makes the identity of an avalanche change. Anyway, this approach to event classification is based on the designer's choices, and more accurately mirrors lexical or commonsense classifications (see. e.g. WordNet 'supersenses' for verb synsets). Ultimately, this discussion has no end, because realists will keep defending the idea that events in reality are not changed by the way we describe them, while constructivists will keep defending the idea that, whatever 'true reality' is about, it can't be modelled without the theoretical burden of how we observe and describe it. Both positions are in principle valid, but, if taken too radically, they focus on issues that are only partly relevant to the aim of computational ontologies, which only attempt to assist domain experts in representing what they want to conceptualize about a certain portion of reality according to their own ideas. For this reason, in this ontology both events and situations are allowed, together with descriptions, in order to encode the modelling needs independently from the position (if any) chosen by the designer.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Event
Label:	Event
Subclass of	DUL:Entity, things that have a DUL:hasPart property who must be a DUL:Event, things that have a DUL:hasParticipant property who may be a DUL:Object and things that have a DUL:hasConstituent property who must be a DUL:Event
Disjoint with	DUL:Object and DUL:Quality
Paraphrase (experimental)	A DUL:Event is something that is a DUL:Entity and has a DUL:hasPart property who must be a DUL:Event and has a DUL:hasParticipant property who may be a DUL:Object and has a DUL:hasConstituent property who must be a DUL:Event A DUL:Event is not a DUL:Object and is not a DUL:Quality

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Event">
<rdfs:label xml:lang="en">Event</rdfs:label>
<rdfs:label xml:lang="it">Evento</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Event"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasParticipant"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasConstituent"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Event"/>
</owl:Restriction>
</rdfs:subClassOf>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Quality"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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 a state to a different one). In the erosion 
case, we could therefore have good motivations to shift from one aspect 
to another: a) causation focus, b) effectual focus, c) historical 
condensation d) transition (causality). The different views refer to the 
same event, but are still different: how to live with this seeming 
paradox? A typical solution e.g. in linguistics (cf. Levin's aspectual 
classes) and in DOLCE Full (cf. WonderWeb D18 axiomatization) is to 
classify events based on aspectual differences. But this solution would 
create different identities for a same event, where the difference is 
only based on the modeller's attitude. An alternative solution is 
applied here, and exploits the notion of (observable) Situation; a 
Situation is a view, consistent with a Description, which can be 
observed of a set of entities. It can also be seen as a 'relational 
context' created by an observer on the basis of a 'frame'. Therefore, a 
Situation allows to create a context where each particular view can have 
a proper identity, while the Event preserves its own identity. For 
example, ErosionAsAccomplishment is a Situation where rock erosion is 
observed as a process leading to a certain achievement: the conditions 
(roles, parameters) that suggest such view are stated in a Description, 
which acts as a 'theory of accomplishments'. Similarly, 
ErosionAsTransition is a Situation where rock erosion is observed as an 
event that has changed a state to another: the conditions for such 
interpretation are stated in a different Description, which acts as a 
'theory of state transitions'. Consider that in no case the Event is 
changed or enriched in parts by the aspectual view. (2) Alternative 
intentionality views Similarly to aspectual views, several 
intentionality views can be provided for a same Event. For example, one 
can investigate if an avalanche has been caused by immediate natural 
forces, or if there is any hint of an intentional effort to activate 
those natural forces. Also in this case, the Event as such has not 
different identities, while the causal analysis generates situations 
with different identities, according to what Description is taken for 
interpreting the Event. On the other hand, if the possible actions of an 
Agent causing the starting of an avalanche are taken as parts of the 
Event, then this makes its identity change, because we are adding a part 
to it. Therefore, if intentionality is a criterion to classify events or 
not depends on if an ontology designer wants to consider causality as a 
relevant dimension for events' identity. (3) Alternative participant 
views A slightly different case is when we consider the basic 
participants to an Event. In this case, the identity of the Event is 
affected by the participating objects, because it depends on them. For 
example, if snow, mountain slopes, wind, waves, etc. are considered as 
an avalanche basic participants, or if we also want to add water, human 
agents, etc., makes the identity of an avalanche change. Anyway, this 
approach to event classification is based on the designer's choices, and 
more accurately mirrors lexical or commonsense classifications (see. 
e.g. WordNet 'supersenses' for verb synsets). Ultimately, this 
discussion has no end, because realists will keep defending the idea 
that events in reality are not changed by the way we describe them, 
while constructivists will keep defending the idea that, whatever 'true 
reality' is about, it can't be modelled without the theoretical burden 
of how we observe and describe it. Both positions are in principle 
valid, but, if taken too radically, they focus on issues that are only 
partly relevant to the aim of computational ontologies, which only 
attempt to assist domain experts in representing what they want to 
conceptualize about a certain portion of reality according to their own 
ideas. For this reason, in this ontology both events and situations are 
allowed, together with descriptions, in order to encode the modelling 
needs independently from the position (if any) chosen by the designer.
</rdfs:comment>
</owl:Class>

Goal

The Description of a Situation that is desired by an Agent, and usually associated to a Plan that describes how to actually achieve it

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Goal
Label:	Goal
Subclass of	DUL:Description
Paraphrase (experimental)	A DUL:Goal is something that is a DUL:Description

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Goal">
<rdfs:label xml:lang="en">Goal</rdfs:label>
<rdfs:label xml:lang="it">Scopo</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<rdfs: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
</rdfs:comment>
</owl:Class>

InformationEntity

A piece of information, be it concretely realized or not.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#InformationEntity
Subclass of	DUL:Entity
Equivalent to	Union of : DUL:InformationObject and DUL:InformationRealization
Paraphrase (experimental)	A DUL:InformationEntity is something that is a DUL:Entity A DUL:InformationEntity is something that must be a DUL:InformationObject or DUL:InformationRealization

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#InformationEntity">
<owl:equivalentClass>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#InformationRealization"/>
</owl:unionOf>
</owl:Class>
</owl:equivalentClass>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:comment>A piece of information, be it concretely realized or not.</rdfs:comment>
</owl:Class>

InformationObject

A piece of information, such as a musical composition, a text, a word, a picture, independently from how it is concretely realized.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject
Label:	Information object
Subclass of	DUL:InformationEntity, DUL:SocialObject, things that have at least 1 DUL:expresses property and things that have a DUL:isRealizedBy property who may be a DUL:InformationRealization
Disjoint with	DUL:Situation and DUL:SocialAgent
Paraphrase (experimental)	A DUL:InformationObject is something that is a DUL:InformationEntity and is a DUL:SocialObject and has at least 1 DUL:expresses property and has a DUL:isRealizedBy property who may be a DUL:InformationRealization A DUL:InformationObject is not a DUL:Situation and is not a DUL:SocialAgent

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject">
<rdfs:label xml:lang="en">Information object</rdfs:label>
<rdfs:label xml:lang="it">Oggetto informativo</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationEntity"/>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#expresses"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">
1</owl:minCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isRealizedBy"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationRealization"/>
</owl:Restriction>
</rdfs:subClassOf>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialAgent"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
A piece of information, such as a musical composition, a text, a word, a 
picture, independently from how it is concretely realized.
</rdfs:comment>
</owl:Class>

InformationRealization

A concrete realization of an InformationObject, e.g. the written document containing the text of a law.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#InformationRealization
Label:	Information realization
Subclass of	DUL:InformationEntity, things that have a DUL:concretelyExpresses property who may be a DUL:SocialObject and things that have a DUL:realizes property who may be a DUL:InformationObject
Equivalent to	(composite term, see schema)
Paraphrase (experimental)	A DUL:InformationRealization is something that is a DUL:InformationEntity and has a DUL:concretelyExpresses property who may be a DUL:SocialObject and has a DUL:realizes property who may be a DUL:InformationObject A DUL:InformationRealization is something that must be a (composite term, see schema)

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#InformationRealization">
<rdfs:label xml:lang="en">Information realization</rdfs:label>
<rdfs:label xml:lang="it">Informazione concreta</rdfs:label>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalObject"/>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Event"/>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasParticipant"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalObject"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:unionOf>
</owl:Class>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#realizes"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationEntity"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#concretelyExpresses"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#realizes"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
A concrete realization of an InformationObject, e.g. the written 
document containing the text of a law.
</rdfs:comment>
</owl:Class>

LocalConcept

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

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#LocalConcept
Label:	Local concept
Subclass of	DUL:Concept
Equivalent to	(composite term, see schema)
Paraphrase (experimental)	A DUL:LocalConcept is something that is a DUL:Concept A DUL:LocalConcept is something that must be a (composite term, see schema)

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#LocalConcept">
<rdfs:label xml:lang="en">Local concept</rdfs:label>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Concept"/>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isDefinedIn"/>
<owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">
1</owl:cardinality>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Concept"/>
<rdfs: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.
</rdfs:comment>
</owl:Class>

Method

A method is a Description that defines or uses concepts in order to guide carrying out actions aimed at a solution with respect to a problem. It is different from a Plan, because plans could be carried out in order to follow a method, but a method can be followed by executing alternative plans.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Method
Label:	Method
Subclass of	DUL:Description
Paraphrase (experimental)	A DUL:Method is something that is a DUL:Description

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Method">
<rdfs:label xml:lang="en">Method</rdfs:label>
<rdfs:label xml:lang="it">Metodo</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<rdfs: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.
</rdfs:comment>
</owl:Class>

Object

Any physical, social, or mental object, or a substance

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Object
Label:	Object
Subclass of	DUL:Entity, things that have a DUL:isClassifiedBy property who must be a DUL:Role, things that have a DUL:isParticipantIn property who may be a DUL:Event, things that have a DUL:hasConstituent property who must be a DUL:Object and things that have a DUL:hasPart property who must be a DUL:Object
Equivalent to	Union of : DUL:PhysicalObject and DUL:SocialObject
Disjoint with	DUL:Quality
Paraphrase (experimental)	A DUL:Object is something that is a DUL:Entity and has a DUL:isClassifiedBy property who must be a DUL:Role and has a DUL:isParticipantIn property who may be a DUL:Event and has a DUL:hasConstituent property who must be a DUL:Object and has a DUL:hasPart property who must be a DUL:Object A DUL:Object is something that must be a DUL:PhysicalObject or DUL:SocialObject A DUL:Object is not a DUL:Quality

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Object">
<rdfs:label xml:lang="en">Object</rdfs:label>
<rdfs:label xml:lang="it">Oggetto</rdfs:label>
<owl:equivalentClass>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalObject"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
</owl:unionOf>
</owl:Class>
</owl:equivalentClass>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isClassifiedBy"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Role"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isParticipantIn"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Event"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasConstituent"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
</owl:Restriction>
</rdfs:subClassOf>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Quality"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
Any physical, social, or mental object, or a substance</rdfs:comment>
</owl:Class>

PhysicalAgent

A PhysicalObject that is capable of self-representing (conceptualizing) a Description in order to plan an Action. A PhysicalAgent is a substrate for (actsFor) a Social Agent

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalAgent
Label:	Physical agent
Subclass of	DUL:Agent, DUL:PhysicalObject and things that have a DUL:conceptualizes property who may be a DUL:Plan
Paraphrase (experimental)	A DUL:PhysicalAgent is something that is a DUL:Agent and is a DUL:PhysicalObject and has a DUL:conceptualizes property who may be a DUL:Plan

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalAgent">
<rdfs:label xml:lang="en">Physical agent</rdfs:label>
<rdfs:label xml:lang="it">Agente fisico</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Agent"/>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalObject"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#conceptualizes"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Plan"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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
</rdfs:comment>
</owl:Class>

PhysicalArtifact

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

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalArtifact
Label:	Physical artifact
Subclass of	DUL:PhysicalObject and things that have a DUL:isDescribedBy property who may be a DUL:Plan
Paraphrase (experimental)	A DUL:PhysicalArtifact is something that is a DUL:PhysicalObject and has a DUL:isDescribedBy property who may be a DUL:Plan

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalArtifact">
<rdfs:label xml:lang="en">Physical artifact</rdfs:label>
<rdfs:label xml:lang="it">Artefatto fisico</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalObject"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isDescribedBy"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Plan"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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.
</rdfs:comment>
</owl:Class>

PhysicalObject

Any Object that has a proper space region. The prototypical physical object has also an associated mass, but the nature of its mass can greatly vary based on the epistemological status of the object (scientifically measured, subjectively possible, imaginary).

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalObject
Label:	Physical object
Subclass of	DUL:Object and things that have a DUL:hasPart property who must be a DUL:PhysicalObject
Disjoint with	DUL:SocialObject
Paraphrase (experimental)	A DUL:PhysicalObject is something that is a DUL:Object and has a DUL:hasPart property who must be a DUL:PhysicalObject A DUL:PhysicalObject is not a DUL:SocialObject

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalObject">
<rdfs:label xml:lang="en">Physical object</rdfs:label>
<rdfs:label xml:lang="it">Oggetto fisico</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalObject"/>
</owl:Restriction>
</rdfs:subClassOf>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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).
</rdfs:comment>
</owl:Class>

Place

A location, in a very generic sense: a political geographic entity (Roma, Lesotho), a non-material location determined by the presence of other entities ("the area close to Roma"), pivot events or signs ("the area where the helicopter fell"), complements of other entities ("the area under the table"), etc. In this generic sense, a Place is an "approximate" location. For an "absolute" location, see the class SpaceRegion

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Place
Label:	Place
Subclass of	DUL:SocialObject and things that have at least 1 DUL:isLocationOf property
Paraphrase (experimental)	A DUL:Place is something that is a DUL:SocialObject and has at least 1 DUL:isLocationOf property

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Place">
<rdfs:label xml:lang="en">Place</rdfs:label>
<rdfs:label xml:lang="it">Luogo</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isLocationOf"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">
1</owl:minCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment>
A location, in a very generic sense: a political geographic entity 
(Roma, Lesotho), a non-material location determined by the presence of 
other entities ("the area close to Roma"), pivot events or signs ("the 
area where the helicopter fell"), complements of other entities ("the 
area under the table"), etc. In this generic sense, a Place is an 
"approximate" location. For an "absolute" location, see the class 
SpaceRegion
</rdfs:comment>
</owl:Class>

Plan

A Description having an explicit Goal, to be achieved by executing the plan

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Plan
Label:	Plan
Subclass of	DUL:Description and things that have a DUL:hasComponent property who may be a DUL:Goal
Paraphrase (experimental)	A DUL:Plan is something that is a DUL:Description and has a DUL:hasComponent property who may be a DUL:Goal

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Plan">
<rdfs:label xml:lang="en">Plan</rdfs:label>
<rdfs:label xml:lang="it">Piano</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasComponent"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Goal"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment>
A Description having an explicit Goal, to be achieved by executing the 
plan
</rdfs:comment>
</owl:Class>

PlanExecution

Plan executions are situations that proactively satisfy a plan. Subplan executions are proper parts of the whole plan execution.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#PlanExecution
Label:	Plan execution
Subclass of	DUL:Situation
Equivalent to	(composite term, see schema)
Paraphrase (experimental)	A DUL:PlanExecution is something that is a DUL:Situation A DUL:PlanExecution is something that must be a (composite term, see schema)

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#PlanExecution">
<rdfs:label xml:lang="en">Plan execution</rdfs:label>
<rdfs:label xml:lang="it">Esecuzione di piano</rdfs:label>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#satisfies"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Plan"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<rdfs:comment>
Plan executions are situations that proactively satisfy a plan. Subplan 
executions are proper parts of the whole plan execution.
</rdfs:comment>
</owl:Class>

Process

This is a placeholder for events that are considered in their evolution, or anyway not strictly dependent on agents, tasks, and plans. See Event class for some thoughts on classifying events. See also 'Transition'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Process
Label:	Process
Subclass of	DUL:Event
Paraphrase (experimental)	A DUL:Process is something that is a DUL:Event

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Process">
<rdfs:label xml:lang="en">Process</rdfs:label>
<rdfs:label xml:lang="it">Processo</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Event"/>
<rdfs: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'.
</rdfs:comment>
</owl:Class>

Quality

Any aspect of an Entity (but not a part of it), which cannot exist without that Entity. For example, the way the surface of a specific PhysicalObject looks like is a Quality, while the encoding of that 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'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Quality
Label:	Quality
Subclass of	DUL:Entity, things that have a DUL:hasConstituent property who must be a DUL:Quality, things that have a DUL:hasPart property who must be a DUL:Quality and things that have a DUL:isQualityOf property who may be a DUL:Entity
Paraphrase (experimental)	A DUL:Quality is something that is a DUL:Entity and has a DUL:hasConstituent property who must be a DUL:Quality and has a DUL:hasPart property who must be a DUL:Quality and has a DUL:isQualityOf property who may be a DUL:Entity

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Quality">
<rdfs:label xml:lang="en">Quality</rdfs:label>
<rdfs:label xml:lang="it">Qualità</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasConstituent"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Quality"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Quality"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isQualityOf"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs: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 is a Quality, while the encoding of that 
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'.
</rdfs:comment>
</owl:Class>

Region

Any region in a dimensional space (a dimensional space is a maximal Region), which can be used as a value for a quality of an Entity . For example, TimeInterval, SpaceRegion, PhysicalAttribute, Amount, SocialAttribute are all subclasses of Region. Regions are not data values in the ordinary knowledge representation sense; in order to get patterns for modelling data, see the properties: representsDataValue and hasDataValue

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Region
Label:	Region
Subclass of	DUL:Abstract, things that have a DUL:precedes property who must be a DUL:Region, things that have a DUL:hasPart property who must be a DUL:Region, things that have a DUL:overlaps property who must be a DUL:Region and things that have a DUL:hasConstituent property who must be a DUL:Region
Paraphrase (experimental)	A DUL:Region is something that is a DUL:Abstract and has a DUL:precedes property who must be a DUL:Region and has a DUL:hasPart property who must be a DUL:Region and has a DUL:overlaps property who must be a DUL:Region and has a DUL:hasConstituent property who must be a DUL:Region

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Region">
<rdfs:label xml:lang="en">Region</rdfs:label>
<rdfs:label xml:lang="it">Regione</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Abstract"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#precedes"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Region"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Region"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#overlaps"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Region"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasConstituent"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Region"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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
</rdfs:comment>
</owl:Class>

Role

A Concept that classifies an Object

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Role
Label:	Role
Subclass of	DUL:Concept, things that have a DUL:classifies property who must be a DUL:Object and things that have a DUL:hasPart property who must be a DUL:Role
Paraphrase (experimental)	A DUL:Role is something that is a DUL:Concept and has a DUL:classifies property who must be a DUL:Object and has a DUL:hasPart property who must be a DUL:Role

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Role">
<rdfs:label xml:lang="en">Role</rdfs:label>
<rdfs:label xml:lang="it">Ruolo</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Concept"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#classifies"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Role"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
A Concept that classifies an Object</rdfs:comment>
</owl:Class>

Situation

A view, consistent with ('satisfying') a Description, on a set of entities. It can also be seen as a 'relational context' created by an observer on the basis of a 'frame' (i.e. a Description). For example, a PlanExecution is a context including some actions executed by agents according to certain parameters and expected tasks to be achieved from a Plan; a DiagnosedSituation is a context of observed entities that is interpreted on the basis of a Diagnosis, etc. Situation is also able to represent reified n-ary relations, where isSettingFor is the top-level relation for all binary projections of the n-ary relation. If used in a transformation pattern for n-ary relations, the designer should take care of creating only one subclass of Situation for each n-ary relation, otherwise the 'identification constraint' (Calvanese et al., IJCAI 2001) could be violated.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#Situation
Label:	Situation
Subclass of	DUL:SocialObject and things that have a DUL:satisfies property who may be a DUL:Description
Disjoint with	DUL:SocialAgent
Paraphrase (experimental)	A DUL:Situation is something that is a DUL:SocialObject and has a DUL:satisfies property who may be a DUL:Description A DUL:Situation is not a DUL:SocialAgent

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Situation">
<rdfs:label xml:lang="en">Situation</rdfs:label>
<rdfs:label xml:lang="it">Situazione</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#satisfies"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
</owl:Restriction>
</rdfs:subClassOf>
<owl:disjointWith rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialAgent"/>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
A view, consistent with ('satisfying') a Description, on a set of 
entities. It can also be seen as a 'relational context' created by an 
observer on the basis of a 'frame' (i.e. a Description). For example, a 
PlanExecution is a context including some actions executed by agents 
according to certain parameters and expected tasks to be achieved from a 
Plan; a DiagnosedSituation is a context of observed entities that is 
interpreted on the basis of a Diagnosis, etc. Situation is also able to 
represent reified n-ary relations, where isSettingFor is the top-level 
relation for all binary projections of the n-ary relation. If used in a 
transformation pattern for n-ary relations, the designer should take 
care of creating only one subclass of Situation for each n-ary relation, 
otherwise the 'identification constraint' (Calvanese et al., IJCAI 2001) 
could be violated.
</rdfs:comment>
</owl:Class>

SocialAgent

Any individual whose existence is granted simply by its social communicability and capability of action (through some PhysicalAgent).

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#SocialAgent
Label:	Social agent
Subclass of	DUL:Agent, DUL:SocialObject and things that have a DUL:actsThrough property who may be a DUL:PhysicalAgent
Paraphrase (experimental)	A DUL:SocialAgent is something that is a DUL:Agent and is a DUL:SocialObject and has a DUL:actsThrough property who may be a DUL:PhysicalAgent

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#SocialAgent">
<rdfs:label xml:lang="en">Social agent</rdfs:label>
<rdfs:label xml:lang="it">Agente sociale</rdfs:label>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Agent"/>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#actsThrough"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#PhysicalAgent"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
Any individual whose existence is granted simply by its social 
communicability and capability of action (through some PhysicalAgent).
</rdfs:comment>
</owl:Class>

SocialObject

Any Object that exists only within some communication Event, in which at least one PhysicalObject participates in. In other words, all objects that have been or are created in the process of social communication: for the sake of communication (InformationObject), for incorporating new individuals (SocialAgent, Place), for contextualizing existing entities (Situation), for collecting existing entities (Collection), or for describing existing entities (Description, Concept). Being dependent on communication, all social objects need to be expressed by some information object (information object are self-expressing).

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject
Label:	Social object
Subclass of	DUL:Object, things that have a DUL:isExpressedBy property who may be a DUL:InformationObject and things that have a DUL:hasPart property who must be a DUL:SocialObject
Equivalent to	Union of : DUL:Collection , DUL:Concept , DUL:Description , DUL:InformationObject , DUL:Place , DUL:Situation and DUL:SocialAgent
Paraphrase (experimental)	A DUL:SocialObject is something that is a DUL:Object and has a DUL:isExpressedBy property who may be a DUL:InformationObject and has a DUL:hasPart property who must be a DUL:SocialObject A DUL:SocialObject is something that must be a DUL:Collection, DUL:Concept, DUL:Description, DUL:InformationObject, DUL:Place, DUL:Situation or DUL:SocialAgent

Schema:

<owl:Class rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject">
<rdfs:label xml:lang="en">Social object</rdfs:label>
<rdfs:label xml:lang="it">Oggetto sociale</rdfs:label>
<owl:equivalentClass>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Collection"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Concept"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Place"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<rdf:Description rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#SocialAgent"/>
</owl:unionOf>
</owl:Class>
</owl:equivalentClass>
<rdfs:subClassOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isExpressedBy"/>
<owl:someValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction><owl:onProperty rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart"/>
<owl:allValuesFrom rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
Any Object that exists only within some communication Event, in which at 
least one PhysicalObject participates in. In other words, all objects 
that have been or are created in the process of social communication: 
for the sake of communication (InformationObject), for incorporating new 
individuals (SocialAgent, Place), for contextualizing existing entities 
(Situation), for collecting existing entities (Collection), or for 
describing existing entities (Description, Concept). Being dependent on 
communication, all social objects need to be expressed by some 
information object (information object are self-expressing).
</rdfs:comment>
</owl:Class>

actsFor

The relation holding between any Agent, and a SocialAgent. In principle, a SocialAgent requires at least one PhysicalAgent in order to act, but this dependency can be 'delegated'; e.g. a university can be acted for by a department, which on its turm is acted for by physical agents.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#actsFor
Label:	acts for
Domain	DUL:Agent
Range	DUL:SocialAgent
Inverse of	DUL:actsThrough
Paraphrase (experimental)	Having a DUL:actsFor implies being something that is a DUL:Agent
Paraphrase (experimental)	Being the DUL:actsFor of something, implies being something that is a DUL:SocialAgent

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#actsFor">
<rdfs:label xml:lang="en">acts for</rdfs:label>
<rdfs:label xml:lang="it">agisce per</rdfs:label>
<rdfs: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.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Agent"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialAgent"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#actsThrough"/>
</owl:ObjectProperty>

actsThrough

The relation holding between a PhysicalAgent and a SocialAgent. In principle, a SocialAgent requires at least one PhysicalAgent in order to act, but this dependency can be 'delegated', e.g. a university can be acted for by a department, which is acted for by physical agents. AKA isActedBy

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#actsThrough
Label:	acts through
Domain	DUL:SocialAgent
Range	DUL:Agent
Paraphrase (experimental)	Having a DUL:actsThrough implies being something that is a DUL:SocialAgent
Paraphrase (experimental)	Being the DUL:actsThrough of something, implies being something that is a DUL:Agent

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#actsThrough">
<rdfs:label xml:lang="en">acts through</rdfs:label>
<rdfs:label xml:lang="it">agisce mediante</rdfs:label>
<rdfs: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
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Agent"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialAgent"/>
</owl:ObjectProperty>

classifies

A relation between a Concept and an Entity, e.g. the Role 'student' classifies a Person 'John'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#classifies
Label:	classifies
Domain	DUL:Concept
Range	DUL:Entity
Paraphrase (experimental)	Having a DUL:classifies implies being something that is a DUL:Concept
Paraphrase (experimental)	Being the DUL:classifies of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#classifies">
<rdfs:label xml:lang="en">classifies</rdfs:label>
<rdfs:label xml:lang="it">classifica</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
A relation between a Concept and an Entity, e.g. the Role 'student' 
classifies a Person 'John'.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Concept"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
</owl:ObjectProperty>

conceptualizes

A relation stating that an Agent is internally representing a SocialObject: situations, descriptions, concepts, etc. E.g., 'John believes in the conspiracy theory'; 'Niels Bohr created the solar-system metaphor for the atomic theory'; 'Jacques assumes all swans are white'; 'the task force members share the attack plan'. Conceptualizations can be distinguished into different forms, primarily based on the type of SocialObject that is conceptualized. Descriptions and concepts can be 'assumed', situations can be 'believed' or 'known', plans can be 'adopted', etc. (see ontology: http://www.loa-cnr.it/ontologies/Conceptualization.owl.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#conceptualizes
Label:	conceptualizes
Domain	DUL:Agent
Range	DUL:SocialObject
Inverse of	DUL:isConceptualizedBy
Paraphrase (experimental)	Having a DUL:conceptualizes implies being something that is a DUL:Agent
Paraphrase (experimental)	Being the DUL:conceptualizes of something, implies being something that is a DUL:SocialObject

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#conceptualizes">
<rdfs:label xml:lang="en">conceptualizes</rdfs:label>
<rdfs:label xml:lang="it">concettualizza</rdfs:label>
<rdfs: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.loa-cnr.it/ontologies/Conceptualization.owl.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Agent"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isConceptualizedBy"/>
</owl:ObjectProperty>

concretelyExpresses

A relation between an InformationRealization and a Description, e.g. 'the printout of the Italian Constitution concretelyExpresses the Italian Constitution'. It should be supplied also with a rule stating that the InformationRealization realizes an InformationObject that expresses the Description

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#concretelyExpresses
Label:	concretely expresses
Domain	DUL:InformationRealization
Range	DUL:SocialObject
Inverse of	DUL:isConcretelyExpressedBy
Paraphrase (experimental)	Having a DUL:concretelyExpresses implies being something that is a DUL:InformationRealization
Paraphrase (experimental)	Being the DUL:concretelyExpresses of something, implies being something that is a DUL:SocialObject

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#concretelyExpresses">
<rdfs:label xml:lang="en">concretely expresses</rdfs:label>
<rdfs:label xml:lang="it">esprime concretamente</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationRealization"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isConcretelyExpressedBy"/>
</owl:ObjectProperty>

defines

A relation between a Description and a Concept, e.g. a Workflow for a governmental Organization defines the Role 'officer', or 'the Italian Traffic Law defines the role Vehicle'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#defines
Label:	defines
Domain	DUL:Description
Range	DUL:Concept
Subproperty of	DUL:usesConcept
Inverse of	DUL:isDefinedIn
Paraphrase (experimental)	Having a DUL:defines implies being something that is a DUL:Description
Paraphrase (experimental)	Being the DUL:defines of something, implies being something that is a DUL:Concept

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#defines">
<rdfs:label xml:lang="en">defines</rdfs:label>
<rdfs:label xml:lang="it">definisce</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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'.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Concept"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isDefinedIn"/>
<rdfs:subPropertyOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#usesConcept"/>
</owl:ObjectProperty>

describes

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

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#describes
Label:	describes
Domain	DUL:Description
Range	DUL:Entity
Paraphrase (experimental)	Having a DUL:describes implies being something that is a DUL:Description
Paraphrase (experimental)	Being the DUL:describes of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#describes">
<rdfs:label xml:lang="en">describes</rdfs:label>
<rdfs:label xml:lang="it">descrive</rdfs:label>
<rdfs: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.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
</owl:ObjectProperty>

expresses

A relation between an InformationObject and a 'meaning', generalized here as a 'SocialObject'. For example: 'A Beehive is a structure in which bees are kept, typically in the form of a dome or box.' (Oxford dictionary)'; 'the term Beehive expresses the concept Beehive in my apiculture ontology'. The intuition for 'meaning' is intended to be very broad. A separate, large comment is included for those who want to investigate more on what kind of meaning can be represented in what form.

This is a large comment field for those who want to investigate the different uses of the 'expresses' relation for modeling different approaches to meaning characterization and modeling. For example, in all these cases, some aspect of meaning is involved: - Beehive means "a structure in which bees are kept, typically in the form of a dome or box." (Oxford dictionary) - 'Beehive' is a synonym in noun synset 09218159 "beehive|hive" (WordNet) - 'the term Beehive can be interpreted as the fact of 'being a beehive', i.e. a relation that holds for concepts such as Bee, Honey, Hosting, etc.' - 'the text of Italian apiculture regulation expresses a rule by which beehives should be kept at least one kilometer away from inhabited areas' - 'the term Beehive expresses the concept Beehive' - Beehive' for apiculturists does not express the same meaning as for, say, fishermen' - 'Your meaning of 'Beautiful' does not seem to fit mine' - Beehive' is formally interpreted as the set of all beehives' - 'from the term 'Beehive', we can build a vector space of statistically significant cooccurring terms in the documents that contain it' - the lexeme 'Belly' expresses the role 'Body_Part' in the frame 'ObservableBodyParts' (FrameNet) As the examples suggest, the 'meaning of meaning' is dependent on the background approach/theory that one assumes. One can hardly make a summary of the too many approaches and theories of meaning, therefore this relation is maybe the most controversial and difficult to explain; normally, in such cases it would be better to give up formalizing. However, the usefulness of having a 'semantic abstraction' in modeling information objects is so high (e.g. for the semantic web, interoperability, reengineering, etc.), that we accept this challenging task, although without taking any particular position in the debate. We provide here some examples, which we want to generalize upon when using the 'expresses' relation to model semantic aspects of social reality. In the most common approach, lexicographers that write dictionaries, glossaries, etc. assume that the meaning of a term is a paraphrase (or 'gloss', or 'definition'). Another approach is provided by concept schemes like thesauri and lexicons, which assume that the meaning of a term is a 'concept', encoded as a 'lemma', 'synset', or 'descriptor'. Still another approach is that of psychologists and cognitive scientists, which often assume that the meaning of an information object is a concept encoded in the mind or cognitive system of an agent. A radically different approach is taken by social scientists and semioticians, who usually assume that meanings of an information object are spread across the communication practices in which members of a community use that object. Another approach that tackles the distributed nature of meaning is assumed by geometrical models of semantics, which assume that the meaning of an InformationObject (e.g. a word) results from the set of informational contexts (e.g. within texts) in which that object is used similarly. The logical approach to meaning is still different, since it assumes that the meaning of e.g. a term is equivalent to the set of individuals that the term can be applied to; for example, the meaning of 'Ali' is e.g. an individual person called Ali, the meaning of 'Airplane' is e.g. the set of airplanes, etc. Finally, an approach taken by structuralist linguistics and frame semantics is that a meaning is the relational context in which an information object can be applied; for example, a meaning of 'Airplane' is situated e.g. in the context ('frame') of passenger airline flights. These different approaches are not necessarily conflicting, and they mostly talk about different aspects of so-called 'semantics'. They can be summarized and modelled within DOLCE-Ultralite as follows (notice that such list is far from exhaustive): (1) Informal meaning (as for linguistic or commonsense semantics: a distinction is assumed between (informal) meaning and reference; see isAbout for an alternative pattern on reference) - Paraphrase meaning (as for lexicographic semantics). Here it is modelled as the expresses relation between instances of InformationObject and different instances of InformationObject that act as 'paraphrases' - Conceptual meaning (as for 'concept scheme' semantics). Here it is modelled as the expresses relation between instances of InformationObject and instances of Concept - Relational meaning (as for frame semantics). Here it is modelled as the expresses relation between instances of InformationObject and instances of Description - Cognitive meaning (as for 'psychological' semantics). Here it is modelled as the expresses relation between any instance of InformationObject and any different instance of InformationObject that isRealizedBy a mental, cognitive or neural state (depending on which theory of mind is assumed). Such states can be considered here as instances of Process (occurring in the mind, cognitive system, or neural system of an agent) - Cultural meaning (as for 'social science' semantics). Here it is modelled as the expresses relation between instances of InformationObject and instances of SocialObject (institutions, cultural paradigms, norms, social practices, etc.) - Distributional meaning (as for geometrical models of meaning). Here it is modelled as the expresses relation between any instance of InformationObject and any different instance of InformationObject that isFormallyRepresentedIn some (geometrical) Region (e.g. a vector space) (2) Formal meaning (as for logic and formal semantics: no distinction is assumed between informal meaning and reference, therefore between 'expresses' and 'isAbout', which can be used interchangeably) - Object-level formal meaning (as in the traditional first-order logic semantics). Here it is modelled as the expresses relation between an instance of InformationObject and an instance of Collection that isGroundingFor (in most cases) a Set; isGroundingFor is defined in the ontology: http://www.loa-cnr.it/ontologies/IOLite.owl - Modal formal meaning (as in possible-world semantics). Here it is modelled as the expresses relation between an instance of InformationObject and an instance of Collection that isGroundingFor a Set, and which isPartOf some different instance of Collection that isGroundingFor a PossibleWorld This is only a first step to provide a framework, in which one can model different aspects of meaning. A more developed ontology should approach the problem of integrating the different uses of 'expresses', so that different theories, resources, methods can interoperate.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#expresses
Label:	expresses
Domain	DUL:InformationObject
Range	DUL:SocialObject
Paraphrase (experimental)	Having a DUL:expresses implies being something that is a DUL:InformationObject
Paraphrase (experimental)	Being the DUL:expresses of something, implies being something that is a DUL:SocialObject

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#expresses">
<rdfs:label xml:lang="en">expresses</rdfs:label>
<rdfs:label xml:lang="it">esprime</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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.
</rdfs:comment>
<rdfs: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 
the most common approach, lexicographers that write dictionaries, 
glossaries, etc. assume that the meaning of a term is a paraphrase (or 
'gloss', or 'definition'). Another approach is provided by concept 
schemes like thesauri and lexicons, which assume that the meaning of a 
term is a 'concept', encoded as a 'lemma', 'synset', or 'descriptor'. 
Still another approach is that of psychologists and cognitive 
scientists, which often assume that the meaning of an information object 
is a concept encoded in the mind or cognitive system of an agent. A 
radically different approach is taken by social scientists and 
semioticians, who usually assume that meanings of an information object 
are spread across the communication practices in which members of a 
community use that object. Another approach that tackles the distributed 
nature of meaning is assumed by geometrical models of semantics, which 
assume that the meaning of an InformationObject (e.g. a word) results 
from the set of informational contexts (e.g. within texts) in which that 
object is used similarly. The logical approach to meaning is still 
different, since it assumes that the meaning of e.g. a term is 
equivalent to the set of individuals that the term can be applied to; 
for example, the meaning of 'Ali' is e.g. an individual person called 
Ali, the meaning of 'Airplane' is e.g. the set of airplanes, etc. 
Finally, an approach taken by structuralist linguistics and frame 
semantics is that a meaning is the relational context in which an 
information object can be applied; for example, a meaning of 'Airplane' 
is situated e.g. in the context ('frame') of passenger airline flights. 
These different approaches are not necessarily conflicting, and they 
mostly talk about different aspects of so-called 'semantics'. They can 
be summarized and modelled within DOLCE-Ultralite as follows (notice 
that such list is far from exhaustive): (1) Informal meaning (as for 
linguistic or commonsense semantics: a distinction is assumed between 
(informal) meaning and reference; see isAbout for an alternative pattern 
on reference) - Paraphrase meaning (as for lexicographic semantics). 
Here it is modelled as the expresses relation between instances of 
InformationObject and different instances of InformationObject that act 
as 'paraphrases' - Conceptual meaning (as for 'concept scheme' 
semantics). Here it is modelled as the expresses relation between 
instances of InformationObject and instances of Concept - Relational 
meaning (as for frame semantics). Here it is modelled as the expresses 
relation between instances of InformationObject and instances of 
Description - Cognitive meaning (as for 'psychological' semantics). Here 
it is modelled as the expresses relation between any instance of 
InformationObject and any different instance of InformationObject that 
isRealizedBy a mental, cognitive or neural state (depending on which 
theory of mind is assumed). Such states can be considered here as 
instances of Process (occurring in the mind, cognitive system, or neural 
system of an agent) - Cultural meaning (as for 'social science' 
semantics). Here it is modelled as the expresses relation between 
instances of InformationObject and instances of SocialObject 
(institutions, cultural paradigms, norms, social practices, etc.) - 
Distributional meaning (as for geometrical models of meaning). Here it 
is modelled as the expresses relation between any instance of 
InformationObject and any different instance of InformationObject that 
isFormallyRepresentedIn some (geometrical) Region (e.g. a vector space) 
(2) Formal meaning (as for logic and formal semantics: no distinction is 
assumed between informal meaning and reference, therefore between 
'expresses' and 'isAbout', which can be used interchangeably) - 
Object-level formal meaning (as in the traditional first-order logic 
semantics). Here it is modelled as the expresses relation between an 
instance of InformationObject and an instance of Collection that 
isGroundingFor (in most cases) a Set; isGroundingFor is defined in the 
ontology: http://www.loa-cnr.it/ontologies/IOLite.owl - Modal formal 
meaning (as in possible-world semantics). Here it is modelled as the 
expresses relation between an instance of InformationObject and an 
instance of Collection that isGroundingFor a Set, and which isPartOf 
some different instance of Collection that isGroundingFor a 
PossibleWorld This is only a first step to provide a framework, in which 
one can model different aspects of meaning. A more developed ontology 
should approach the problem of integrating the different uses of 
'expresses', so that different theories, resources, methods can 
interoperate.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
</owl:ObjectProperty>

follows

A relation between entities, expressing a 'sequence' schema. E.g. 'year 2000 follows 1999', 'preparing coffee' follows 'deciding what coffee to use', 'II World War follows I World War', etc. It can be used between tasks, processes or time intervals, and subproperties would fit best in order to distinguish the different uses.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#follows
Label:	follows
Type of property:	Transitive Property
Domain	DUL:Entity
Range	DUL:Entity
Paraphrase (experimental)	Having a DUL:follows implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:follows of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#follows">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
<rdfs:label xml:lang="en">follows</rdfs:label>
<rdfs:label xml:lang="it">segue</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
</owl:ObjectProperty>

hasComponent

The hasPart relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the Object.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#hasComponent
Label:	has component
Domain	DUL:Object
Range	DUL:Object
Subproperty of	DUL:hasPart
Inverse of	DUL:isComponentOf
Paraphrase (experimental)	Having a DUL:hasComponent implies being something that is a DUL:Object
Paraphrase (experimental)	Being the DUL:hasComponent of something, implies being something that is a DUL:Object

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#hasComponent">
<rdfs:label xml:lang="en">has component</rdfs:label>
<rdfs:label xml:lang="it">ha componente</rdfs:label>
<rdfs:comment>
The hasPart relation without transitivity, holding between an Object 
(the system) and another (the component), and assuming a Design that 
structures the Object.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<rdfs:subPropertyOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isComponentOf"/>
</owl:ObjectProperty>

hasConstituent

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

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#hasConstituent
Label:	has constituent
Domain	DUL:Entity
Range	DUL:Entity
Paraphrase (experimental)	Having a DUL:hasConstituent implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:hasConstituent of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#hasConstituent">
<rdfs:label xml:lang="en">has constituent</rdfs:label>
<rdfs:label xml:lang="it">ha costituente</rdfs:label>
<rdfs: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.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
</owl:ObjectProperty>

hasLocation

A generic, relative localization, 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

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#hasLocation
Label:	has location
Domain	DUL:Entity
Range	DUL:Entity
Paraphrase (experimental)	Having a DUL:hasLocation implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:hasLocation of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#hasLocation">
<rdfs:label xml:lang="en">has location</rdfs:label>
<rdfs:label xml:lang="it">ha localizzazione</rdfs:label>
<rdfs:comment>
A generic, relative localization, 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
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
</owl:ObjectProperty>

hasPart

A schematic relation between any entities, e.g. 'the human body has a brain as part', '20th century contains year 1923', 'World War II includes the Pearl Harbour event'. Subproperties and restrictions can be used to specialize hasPart for objects, events, etc.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#hasPart
Label:	has part
Type of property:	Transitive Property
Domain	DUL:Entity
Range	DUL:Entity
Paraphrase (experimental)	Having a DUL:hasPart implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:hasPart of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
<rdfs:label xml:lang="en">has part</rdfs:label>
<rdfs:label xml:lang="it">ha parte</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
A schematic relation between any entities, e.g. 'the human body has a 
brain as part', '20th century contains year 1923', 'World War II 
includes the Pearl Harbour event'. Subproperties and restrictions can be 
used to specialize hasPart for objects, events, etc.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
</owl:ObjectProperty>

hasParticipant

A relation between an object and a process, e.g. 'John took part in the discussion', 'a large mass of snow fell during the avalanche', or 'a cook, some sugar, flour, etc. are all present in the cooking of a cake'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#hasParticipant
Label:	has participant
Domain	DUL:Event
Range	DUL:Object
Inverse of	DUL:isParticipantIn
Paraphrase (experimental)	Having a DUL:hasParticipant implies being something that is a DUL:Event
Paraphrase (experimental)	Being the DUL:hasParticipant of something, implies being something that is a DUL:Object

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#hasParticipant">
<rdfs:label xml:lang="en">has participant</rdfs:label>
<rdfs:label xml:lang="it">ha come partecipante</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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'.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Event"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isParticipantIn"/>
</owl:ObjectProperty>

hasQuality

A relation between entities and qualities, e.g. 'Dmitri's skin is yellowish'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#hasQuality
Label:	has quality
Domain	DUL:Entity
Range	DUL:Quality
Paraphrase (experimental)	Having a DUL:hasQuality implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:hasQuality of something, implies being something that is a DUL:Quality

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#hasQuality">
<rdfs:label xml:lang="en">has quality</rdfs:label>
<rdfs:label xml:lang="it">ha qualità</rdfs:label>
<rdfs:comment>
A relation between entities and qualities, e.g. 'Dmitri's skin is 
yellowish'.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Quality"/>
</owl:ObjectProperty>

hasRegion

A relation between entities and regions, e.g. 'the number of wheels of that truck is 12', 'the time of the experiment is August 9th, 2004', 'the whale has been localized at 34 degrees E, 20 degrees S'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#hasRegion
Label:	has region
Domain	DUL:Entity
Range	DUL:Region
Inverse of	DUL:isRegionFor
Paraphrase (experimental)	Having a DUL:hasRegion implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:hasRegion of something, implies being something that is a DUL:Region

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#hasRegion">
<rdfs:label xml:lang="en">has region</rdfs:label>
<rdfs:label xml:lang="it">ha attributo</rdfs:label>
<rdfs: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'.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Region"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isRegionFor"/>
</owl:ObjectProperty>

hasSetting

A relation between entities and situations, e.g. 'this morning I've prepared my coffee with a new fantastic Arabica', i.e.: (an amount of) a new fantastic Arabica hasSetting the preparation of my coffee this morning.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#hasSetting
Label:	has setting
Domain	DUL:Entity
Range	DUL:Situation
Inverse of	DUL:isSettingFor
Paraphrase (experimental)	Having a DUL:hasSetting implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:hasSetting of something, implies being something that is a DUL:Situation

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#hasSetting">
<rdfs:label xml:lang="en">has setting</rdfs:label>
<rdfs:label xml:lang="it">è nel contesto di</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isSettingFor"/>
</owl:ObjectProperty>

includesEvent

A relation between situations and events, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: the preparation of my coffee this morning included a burning of my fingers).

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#includesEvent
Label:	includes event
Domain	DUL:Situation
Range	DUL:Event
Subproperty of	DUL:isSettingFor
Paraphrase (experimental)	Having a DUL:includesEvent implies being something that is a DUL:Situation
Paraphrase (experimental)	Being the DUL:includesEvent of something, implies being something that is a DUL:Event

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#includesEvent">
<rdfs:label xml:lang="en">includes event</rdfs:label>
<rdfs:label xml:lang="it">include l'evento</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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).
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Event"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<rdfs:subPropertyOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isSettingFor"/>
</owl:ObjectProperty>

includesObject

A relation between situations and objects, e.g. 'this morning I've prepared my coffee and had my fingers burnt' (i.e.: the preparation of my coffee this morning included me).

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#includesObject
Label:	includes object
Domain	DUL:Situation
Range	DUL:Object
Subproperty of	DUL:isSettingFor
Paraphrase (experimental)	Having a DUL:includesObject implies being something that is a DUL:Situation
Paraphrase (experimental)	Being the DUL:includesObject of something, implies being something that is a DUL:Object

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#includesObject">
<rdfs:label xml:lang="en">includes object</rdfs:label>
<rdfs:label xml:lang="it">include l'oggetto</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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).
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<rdfs:subPropertyOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isSettingFor"/>
</owl:ObjectProperty>

isClassifiedBy

A relation between a Concept and an Entity, e.g. 'John is considered a typical rude man'; your last concert constitutes the achievement of a lifetime; '20-year-old means she's mature enough'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isClassifiedBy
Label:	is classified by
Domain	DUL:Entity
Range	DUL:Concept
Inverse of	DUL:classifies
Paraphrase (experimental)	Having a DUL:isClassifiedBy implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:isClassifiedBy of something, implies being something that is a DUL:Concept

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isClassifiedBy">
<rdfs:label xml:lang="en">is classified by</rdfs:label>
<rdfs:label xml:lang="it">è classificato da</rdfs:label>
<rdfs: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'.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Concept"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#classifies"/>
</owl:ObjectProperty>

isComponentOf

The hasPart relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the Object.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isComponentOf
Label:	is component of
Domain	DUL:Object
Range	DUL:Object
Subproperty of	DUL:isPartOf
Paraphrase (experimental)	Having a DUL:isComponentOf implies being something that is a DUL:Object
Paraphrase (experimental)	Being the DUL:isComponentOf of something, implies being something that is a DUL:Object

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isComponentOf">
<rdfs:label xml:lang="en">is component of</rdfs:label>
<rdfs:label xml:lang="it">è componente di</rdfs:label>
<rdfs:comment>
The hasPart relation without transitivity, holding between an Object 
(the system) and another (the component), and assuming a Design that 
structures the Object.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<rdfs:subPropertyOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isPartOf"/>
</owl:ObjectProperty>

isConceptUsedIn

A more generic relation holding between a Description and a Concept. In order to be used, a Concept must be previously definedIn another Description

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isConceptUsedIn
Label:	is concept used in
Domain	DUL:Concept
Range	DUL:Description
Paraphrase (experimental)	Having a DUL:isConceptUsedIn implies being something that is a DUL:Concept
Paraphrase (experimental)	Being the DUL:isConceptUsedIn of something, implies being something that is a DUL:Description

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isConceptUsedIn">
<rdfs:label xml:lang="en">is concept used in</rdfs:label>
<rdfs:label xml:lang="it">è un concetto usato in</rdfs:label>
<rdfs: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
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Concept"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
</owl:ObjectProperty>

isConceptualizedBy

A relation stating that an Agent is internally representing a Description . E.g., 'John believes in the conspiracy theory'; 'Niels Bohr created a solar-system metaphor for his atomic theory'; 'Jacques assumes all swans are white'; 'the task force shares the attack plan'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isConceptualizedBy
Label:	is conceptualized by
Domain	DUL:SocialObject
Range	DUL:Agent
Paraphrase (experimental)	Having a DUL:isConceptualizedBy implies being something that is a DUL:SocialObject
Paraphrase (experimental)	Being the DUL:isConceptualizedBy of something, implies being something that is a DUL:Agent

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isConceptualizedBy">
<rdfs:label xml:lang="en">is conceptualized by</rdfs:label>
<rdfs:label xml:lang="it">è concettualizzato da</rdfs:label>
<rdfs: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'.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Agent"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
</owl:ObjectProperty>

isConcretelyExpressedBy

A relation between an InformationRealization and a Description, e.g. 'the printout of the Italian Constitution concretelyExpresses the Italian Constitution'. It should be supplied also with a rule stating that the InformationRealization realizes an InformationObject that expresses the Description

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isConcretelyExpressedBy
Label:	is concretely expressed by
Domain	DUL:SocialObject
Range	DUL:InformationRealization
Paraphrase (experimental)	Having a DUL:isConcretelyExpressedBy implies being something that is a DUL:SocialObject
Paraphrase (experimental)	Being the DUL:isConcretelyExpressedBy of something, implies being something that is a DUL:InformationRealization

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isConcretelyExpressedBy">
<rdfs:label xml:lang="en">is concretely expressed by</rdfs:label>
<rdfs:label xml:lang="it">è espresso concretamente da</rdfs:label>
<rdfs: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
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationRealization"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
</owl:ObjectProperty>

isConstituentOf

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

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isConstituentOf
Label:	is constituent of
Domain	DUL:Entity
Range	DUL:Entity
Inverse of	DUL:hasConstituent
Paraphrase (experimental)	Having a DUL:isConstituentOf implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:isConstituentOf of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isConstituentOf">
<rdfs:label xml:lang="en">is constituent of</rdfs:label>
<rdfs:label xml:lang="it">è costituente di</rdfs:label>
<rdfs: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.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasConstituent"/>
</owl:ObjectProperty>

isDefinedIn

A relation between a Description and a Concept, e.g. a Workflow for a governmental Organization defines the Role 'officer', or 'the Italian Traffic Law defines the role Vehicle'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isDefinedIn
Label:	is defined in
Domain	DUL:Concept
Range	DUL:Description
Subproperty of	DUL:isConceptUsedIn
Paraphrase (experimental)	Having a DUL:isDefinedIn implies being something that is a DUL:Concept
Paraphrase (experimental)	Being the DUL:isDefinedIn of something, implies being something that is a DUL:Description

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isDefinedIn">
<rdfs:label xml:lang="en">is defined in</rdfs:label>
<rdfs:label xml:lang="it">è definito in</rdfs:label>
<rdfs: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'.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Concept"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<rdfs:subPropertyOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isConceptUsedIn"/>
</owl:ObjectProperty>

isDescribedBy

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

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isDescribedBy
Label:	is described by
Domain	DUL:Entity
Range	DUL:Description
Inverse of	DUL:describes
Paraphrase (experimental)	Having a DUL:isDescribedBy implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:isDescribedBy of something, implies being something that is a DUL:Description

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isDescribedBy">
<rdfs:label xml:lang="en">is described by</rdfs:label>
<rdfs:label xml:lang="it">è descritto da</rdfs:label>
<rdfs: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.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#describes"/>
</owl:ObjectProperty>

isEventIncludedIn

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isEventIncludedIn
Label:	is event included in
Domain	DUL:Event
Range	DUL:Situation
Subproperty of	DUL:hasSetting
Inverse of	DUL:includesEvent
Paraphrase (experimental)	Having a DUL:isEventIncludedIn implies being something that is a DUL:Event
Paraphrase (experimental)	Being the DUL:isEventIncludedIn of something, implies being something that is a DUL:Situation

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isEventIncludedIn">
<rdfs:label xml:lang="en">is event included in</rdfs:label>
<rdfs:label xml:lang="it">è un evento nel contesto di</rdfs:label>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Event"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<rdfs:subPropertyOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasSetting"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#includesEvent"/>
</owl:ObjectProperty>

isExpressedBy

A relation between a dul:SocialObject (the 'meaning') and a dul:InformationObject (the 'expression'). For example: 'A Beehive is a structure in which bees are kept, typically in the form of a dome or box.' (Oxford dictionary)'; 'the term Beehive expresses the concept Beehive in my apiculture ontology'. The intuition for 'meaning' is intended to be very broad. A separate, large comment is included in the encoding of 'expresses', for those who want to investigate more on what kind of meaning can be represented in what form.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isExpressedBy
Label:	is expressed by
Domain	DUL:SocialObject
Range	DUL:InformationObject
Inverse of	DUL:expresses
Paraphrase (experimental)	Having a DUL:isExpressedBy implies being something that is a DUL:SocialObject
Paraphrase (experimental)	Being the DUL:isExpressedBy of something, implies being something that is a DUL:InformationObject

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isExpressedBy">
<rdfs:label xml:lang="en">is expressed by</rdfs:label>
<rdfs:label xml:lang="it">è espresso da</rdfs:label>
<rdfs: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.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#SocialObject"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#expresses"/>
</owl:ObjectProperty>

isLocationOf

A generic, relative localization, holding between any entities. E.g. 'Rome is the seat of the Pope', 'the liver is the location of the tumor'. For 'absolute' locations, see SpaceRegion

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isLocationOf
Label:	is location of
Domain	DUL:Entity
Range	DUL:Entity
Inverse of	DUL:hasLocation
Paraphrase (experimental)	Having a DUL:isLocationOf implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:isLocationOf of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isLocationOf">
<rdfs:label xml:lang="en">is location of</rdfs:label>
<rdfs:label xml:lang="it">è una localizzazione di</rdfs:label>
<rdfs: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
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasLocation"/>
</owl:ObjectProperty>

isObjectIncludedIn

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isObjectIncludedIn
Label:	is object included in
Domain	DUL:Object
Range	DUL:Situation
Subproperty of	DUL:hasSetting
Inverse of	DUL:includesObject
Paraphrase (experimental)	Having a DUL:isObjectIncludedIn implies being something that is a DUL:Object
Paraphrase (experimental)	Being the DUL:isObjectIncludedIn of something, implies being something that is a DUL:Situation

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isObjectIncludedIn">
<rdfs:label xml:lang="en">is object included in</rdfs:label>
<rdfs:label xml:lang="it">è un oggetto nel contesto di</rdfs:label>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<rdfs:subPropertyOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasSetting"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#includesObject"/>
</owl:ObjectProperty>

isPartOf

A relation between any entities, e.g.'brain is a part of the human body'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isPartOf
Label:	is part of
Type of property:	Transitive Property
Domain	DUL:Entity
Range	DUL:Entity
Inverse of	DUL:hasPart
Paraphrase (experimental)	Having a DUL:isPartOf implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:isPartOf of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isPartOf">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
<rdfs:label xml:lang="en">is part of</rdfs:label>
<rdfs:label xml:lang="it">è parte di</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
A relation between any entities, e.g.'brain is a part of the human body'.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasPart"/>
</owl:ObjectProperty>

isParticipantIn

A relation between an object and a process, e.g. 'John took part in the discussion', 'a large mass of snow fell during the avalanche', or 'a cook, some sugar, flour, etc. are all present in the cooking of a cake'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isParticipantIn
Label:	is participant in
Domain	DUL:Object
Range	DUL:Event
Paraphrase (experimental)	Having a DUL:isParticipantIn implies being something that is a DUL:Object
Paraphrase (experimental)	Being the DUL:isParticipantIn of something, implies being something that is a DUL:Event

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isParticipantIn">
<rdfs:label xml:lang="en">is participant in</rdfs:label>
<rdfs:label xml:lang="it">è un partecipante a</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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'.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Event"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Object"/>
</owl:ObjectProperty>

isQualityOf

A relation between entities and qualities, e.g. 'Dmitri's skin is yellowish'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isQualityOf
Label:	is quality of
Domain	DUL:Quality
Range	DUL:Entity
Inverse of	DUL:hasQuality
Paraphrase (experimental)	Having a DUL:isQualityOf implies being something that is a DUL:Quality
Paraphrase (experimental)	Being the DUL:isQualityOf of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isQualityOf">
<rdfs:label xml:lang="en">is quality of</rdfs:label>
<rdfs:label xml:lang="it">è una qualità di</rdfs:label>
<rdfs:comment>
A relation between entities and qualities, e.g. 'Dmitri's skin is 
yellowish'.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Quality"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#hasQuality"/>
</owl:ObjectProperty>

isRealizedBy

A relation between an information realization and an information object, e.g. the paper copy of the Italian Constitution realizes the text of the Constitution.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isRealizedBy
Label:	is realized by
Domain	DUL:InformationObject
Range	DUL:InformationRealization
Paraphrase (experimental)	Having a DUL:isRealizedBy implies being something that is a DUL:InformationObject
Paraphrase (experimental)	Being the DUL:isRealizedBy of something, implies being something that is a DUL:InformationRealization

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isRealizedBy">
<rdfs:label xml:lang="en">is realized by</rdfs:label>
<rdfs:label xml:lang="it">è realizzato da</rdfs:label>
<rdfs: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.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationRealization"/>
</owl:ObjectProperty>

isRegionFor

A relation between entities and regions, e.g. 'the color of my car is red'.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isRegionFor
Label:	is region for
Domain	DUL:Region
Range	DUL:Entity
Paraphrase (experimental)	Having a DUL:isRegionFor implies being something that is a DUL:Region
Paraphrase (experimental)	Being the DUL:isRegionFor of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isRegionFor">
<rdfs:label xml:lang="en">is region for</rdfs:label>
<rdfs:label xml:lang="it">è una regione di</rdfs:label>
<rdfs:comment>
A relation between entities and regions, e.g. 'the color of my car is 
red'.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Region"/>
</owl:ObjectProperty>

isSatisfiedBy

A relation between a Situation and a Description, e.g. the execution of a Plan satisfies that plan.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isSatisfiedBy
Label:	is satisfied by
Domain	DUL:Description
Range	DUL:Situation
Inverse of	DUL:satisfies
Paraphrase (experimental)	Having a DUL:isSatisfiedBy implies being something that is a DUL:Description
Paraphrase (experimental)	Being the DUL:isSatisfiedBy of something, implies being something that is a DUL:Situation

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isSatisfiedBy">
<rdfs:label xml:lang="en">is satisfied by</rdfs:label>
<rdfs:label xml:lang="it">è soddisfatta da</rdfs:label>
<rdfs:comment>
A relation between a Situation and a Description, e.g. the execution of 
a Plan satisfies that plan.
</rdfs:comment>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#satisfies"/>
</owl:ObjectProperty>

isSettingFor

A relation between situations and entities, e.g. 'this morning I've prepared my coffee with a new fantastic Arabica', i.e.: the preparation of my coffee this morning is the setting for (an amount of) a new fantastic Arabica.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#isSettingFor
Label:	is setting for
Domain	DUL:Situation
Range	DUL:Entity
Paraphrase (experimental)	Having a DUL:isSettingFor implies being something that is a DUL:Situation
Paraphrase (experimental)	Being the DUL:isSettingFor of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#isSettingFor">
<rdfs:label xml:lang="en">is setting for</rdfs:label>
<rdfs:label xml:lang="it">include</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
</owl:ObjectProperty>

overlaps

A schematic relation between any entities, e.g. 'the chest region overlaps with the abdomen region', 'my spoken words overlap with hers', 'the time of my leave overlaps with the time of your arrival', 'fibromyalgia overlaps with other conditions'. Subproperties and restrictions can be used to specialize overlaps for objects, events, time intervals, etc.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#overlaps
Label:	overlaps
Type of property:	Symmetric property
Domain	DUL:Entity
Range	DUL:Entity
Inverse of	DUL:overlaps
Paraphrase (experimental)	Having a DUL:overlaps implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:overlaps of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#overlaps">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#SymmetricProperty"/>
<rdfs:label xml:lang="en">overlaps</rdfs:label>
<rdfs:label xml:lang="it">sovrapposto a</rdfs:label>
<rdfs: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.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#overlaps"/>
</owl:ObjectProperty>

precedes

A relation between entities, expressing a 'sequence' schema. E.g. 'year 1999 precedes 2000', 'deciding what coffee to use' precedes 'preparing coffee', 'World War II follows World War I', 'in the Milan to Rome autoroute, Bologna precedes Florence', etc. It can then be used between tasks, processes, time intervals, spatially locate objects, situations, etc. Subproperties can be defined in order to distinguish the different uses.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#precedes
Label:	precedes
Type of property:	Transitive Property
Domain	DUL:Entity
Range	DUL:Entity
Inverse of	DUL:follows
Paraphrase (experimental)	Having a DUL:precedes implies being something that is a DUL:Entity
Paraphrase (experimental)	Being the DUL:precedes of something, implies being something that is a DUL:Entity

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#precedes">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#TransitiveProperty"/>
<rdfs:label xml:lang="en">precedes</rdfs:label>
<rdfs:label xml:lang="it">precede</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Entity"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#follows"/>
</owl:ObjectProperty>

realizes

A relation between an information realization and an information object, e.g. the paper copy of the Italian Constitution realizes the text of the Constitution.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#realizes
Label:	realizes
Domain	DUL:InformationRealization
Range	DUL:InformationObject
Inverse of	DUL:isRealizedBy
Paraphrase (experimental)	Having a DUL:realizes implies being something that is a DUL:InformationRealization
Paraphrase (experimental)	Being the DUL:realizes of something, implies being something that is a DUL:InformationObject

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#realizes">
<rdfs:label xml:lang="en">realizes</rdfs:label>
<rdfs:label xml:lang="it">realizza</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
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.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#InformationRealization"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isRealizedBy"/>
</owl:ObjectProperty>

satisfies

A relation between a Situation and a Description, e.g. the execution of a Plan satisfies that plan.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#satisfies
Label:	satisfies
Domain	DUL:Situation
Range	DUL:Description
Paraphrase (experimental)	Having a DUL:satisfies implies being something that is a DUL:Situation
Paraphrase (experimental)	Being the DUL:satisfies of something, implies being something that is a DUL:Description

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#satisfies">
<rdfs:label xml:lang="en">satisfies</rdfs:label>
<rdfs:label xml:lang="it">soddisfa</rdfs:label>
<rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
A relation between a Situation and a Description, e.g. the execution of 
a Plan satisfies that plan.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Situation"/>
</owl:ObjectProperty>

usesConcept

A generic relation holding between a Description and a Concept. In order to be used, a Concept must be previously definedIn another Description. This last condition cannot be encoded for object properties in OWL.

URI:	http://www.loa-cnr.it/ontologies/DUL.owl#usesConcept
Label:	uses concept
Domain	DUL:Description
Range	DUL:Concept
Inverse of	DUL:isConceptUsedIn
Paraphrase (experimental)	Having a DUL:usesConcept implies being something that is a DUL:Description
Paraphrase (experimental)	Being the DUL:usesConcept of something, implies being something that is a DUL:Concept

Schema:

<owl:ObjectProperty rdf:about="http://www.loa-cnr.it/ontologies/DUL.owl#usesConcept">
<rdfs:label xml:lang="en">uses concept</rdfs:label>
<rdfs:label xml:lang="it">usa il concetto</rdfs:label>
<rdfs: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.
</rdfs:comment>
<rdfs:range rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Concept"/>
<rdfs:domain rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#Description"/>
<owl:inverseOf rdf:resource="http://www.loa-cnr.it/ontologies/DUL.owl#isConceptUsedIn"/>
</owl:ObjectProperty>

Documentation generated using a generation tool derived from the vocab.org toolchain.