d0.owl
type: Ontology
imports: DUL.owl
comment: A supplementary ontology used as a generalization of DOLCE+DnS Ultralite (DUL), in order to deal with the systematic polysemy of many lexical items, whose senses create problems when used as OWL classes. For example, it's customary to find lexical items that carry both a sense of physical or abstract location, of event or event type, etc.
version info: 1.2 - added Eventuality, and subclass axioms to close all classes under dul:Entity 1.3 - removed disjoint axioms that could be hardly sustainable (Concept-IO, Concept-Description, Description-Situation, Description-IO) 1.4 - updated several obsolete comments, added CollectiveEntity class, deprecated the d0:Event class 1.5 - updated the Topic class as Domain (as a system of subjects), added Subject as anything thatis the focus of an InformationEntity

has focus
type: ObjectProperty
sub property of: isAbout
inverse of: is focus of
creator: Aldo Gangemi
date: 2021-09-16T16:18:05Z
comment: The aboutness relation when an information entity is summarised, as in the case of subjects, topics, domains, etc.

is focus of
type: ObjectProperty
sub property of: isReferenceOf
creator: Aldo Gangemi
date: 2021-09-16T16:14:30Z
comment: The aboutness relation when an information entity is summarised, as in the case of subjects, topics, domains, etc.

activity
type: Class
equivalent class: Class
  union of: Action
  union of: Task
comment: Any action or task planned or executed by an agent intentionally causing and participating in it. E.g. swimming, shopping, knowledge sharing, etc. This is a catch all class to make sense of ambiguous data that cannot be made more precise, e.g. at the lexical level.

characteristic
type: Class
equivalent class: Class
  union of: Parameter
  union of: Quality
  union of: Region
comment: An aspect, quality, attribute, or dimensional value of a thing. E.g. radial symmetry, poker face, alkalinity, attractiveness, darkness, geographical coordinates, etc. This is a catch all class to make sense of ambiguous data that cannot be made more precise, e.g. at the lexical level.

cognitive entity
type: Class
subclass of: Class
  union of: Event
  union of: Object
  union of: Quality
subclass of: Restriction
  on property: hasLocation
  some values from: PhysicalAgent
comment: Attitudes, cognitive abilities, ideologies, psychological phenomena, mind, etc. E.g. discernment, homophobia, precognition, etc. Since cognitive entities can be categorized as objects (e.g. a memorised image), events (e.g. an experience of astonishment), or qualities (e.g. a bias in judgment), this is a catch-all class, aimed at making sense of ambiguous data or words, when they cannot be disambiguated in a particular context. In addition, cognitive entities such as emotions can be (jointly) considered at different levels, including the biological or neural substrate for experiencing them, their cognitive state, their bodily expression, or as (an instance of) public notions, e.g. 'sadness'.

CollectiveEntity
type: Class
equivalent class: Class
  union of: Collection
  union of: ObjectAggregate
creator: Aldo Gangemi
date: 2021-02-21T23:30:55Z
comment: Either collections (as socially constructed entities) or aggregates (as distributed physical objects whose parts are member of a same collection). This is a catch all class to make sense of ambiguous data that cannot be made more precise, e.g. at the lexical level.

domain
type: Class
subclass of: subject
subclass of: Class
  intersection of: system
  intersection of: Restriction
    on property: hasComponent
    min qualified cardinality: 2
    on class: SocialObject
comment: A domain is defined here as a discipline, field, branch of knowledge, standard topic area. E.g. algebra, avionics, ballet, theology, engineering, etc. A domain could be named, or generated by a clustering function. A domain is an intensional notion, which 'synthesizes' social objects, so creating an (evolving, fuzzy) cultural System. Topics can include information objects, concepts, relations, etc.

event
type: Class
equivalent class: Class
  union of: Event
  union of: EventType
subclass of: Thing
comment: Any event or event type, independently of its possible causes. E.g. avalanches, earthquakes, brainwaves, bonfires, tasks, steps, phases, etc. This is a catch all class to make sense of ambiguous data that cannot be made more precise, e.g. at the lexical level. (This is a deprecated class).
deprecated: This class used to be important in order to make sense of ambiguous terms denoting either events or event types. Later, the Eventuality class has been introduced, which extends the tolerance to situations as well. The term 'Event' is DOLCE-Zero is also identical to the restricted Event in DOLCE, hence the reason for deprecation.

eventuality
type: Class
equivalent class: Class
  union of: Event
  union of: EventType
  union of: Situation
comment: Any event, situation, activity, event type, etc. Used to abstract from formal criteria that distinguish between event occurrences, their types, and constructed objects (situations, tropes, qua-entities) that provide a setting for multiple entities. This is a catch all class to make sense of ambiguous data that cannot be made more precise, e.g. at the lexical level.
label: accadimento @it

location
type: Class
equivalent class: Class
  union of: PhysicalPlace
  union of: Place
  union of: SpaceRegion
comment: A location, in a very generic sense e.g. geo-political entities, physical object that are inherently located, spatial coordinates, etc. E.g. Oslo, Australia, Inner Mongolia, resort area, intergalactic space, tundra, tunnel, etc. This is a catch all class to make sense of ambiguous data that cannot be made more precise, e.g. at the lexical level.

subject
type: Class
equivalent class: Restriction
  on property: is focus of
  some values from: InformationEntity
creator: Aldo Gangemi
date: 2021-09-22T17:06:09Z
comment: Any theme, matter, topic, etc. For subjects that become institutionalised or standard, i.e., they get a systematic structure, see Domain. A subject could be named, or generated by a clustering function. A subject can be anything that one considers the focus of a discourse, visual representation, or other communication modalities (i.e., information entities).

system
type: Class
subclass of: Class
  intersection of: ObjectAggregate
  intersection of: Restriction
    on property: hasComponent
    min qualified cardinality: 2
    on class: Object
comment: Physical, social, or abstract systems. E.g. viticulture, non-linear systems, democracy, water distribution, etc. Systems are characterized by components with interdependencies, spatio-temporal patterns, reference situations, equilibria, etc. System components can be physical, social, or a mixture of them. As such, System could be considered as (a special kind of) an ObjectAggregate. However, systems have an internal structure (a Configuration) that is not required for object aggregates in general, whose parts only need the membership to a same collection.