Latest revision as of 13:53, 8 March 2010

Warning!

This is an old revision. Go to current revision

Last modified date is: 2010-03-08

Graphical representation

Diagram

General description

Name:	Situation
Submitted by:	AldoGangemi
Also Known As:	situation
Intent:	To represent contexts or situations, and the things that are contextualized.
Domains:	General
Competency Questions:	What is the context or situation of something? What are the things present in this context or situation?
Solution description:	-
Reusable OWL Building Block:	1 (770)
Consequences:	We can contextualize things that have something in common, or are associated: a same place, time, view, causal link, systemic dependence, etc. We can also reify n-ary relations as situations.
Scenarios:	The lecture was held in January 1921 by Bela Fleck, with some physicians in the audience making questions, in a very relaxed athmosphere.
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:	http://www.ontologydesignpatterns.org/ont/dul/DUL.owl
Reengineered From:
Has Components:
Specialization Of:
Related CPs:

Elements

The Situation Content OP locally defines the following ontology elements:

hasSetting (owl:ObjectProperty) 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).

hasSetting page

isSettingFor (owl:ObjectProperty)

isSettingFor page

Situation (owl:Class) A view on a set of entities. It can be seen as a 'relational context', reifying a relation.

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 situation for each instance of an n-ary relation, otherwise the 'identification constraint' (Calvanese et al., IJCAI 2001) could be violated

- adding an 'exact cardinality' restriction corresponding to the arity of the n-ary relation, otherwise the designer would actually represent a polymorphic relation.

Situation page

Additional information

(type): http://www.w3.org/2002/07/owl#Ontology

(versionInfo): Created by Aldo Gangemi and Valentina Presutti

(imports): http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl

Scenarios

Scenarios about Situation

No scenario is added to this Content OP.

Reviews

Reviews about Situation

There is no review about this proposal.

Some subquery has no valid condition.

This revision (revision ID 9122) takes in account the reviews: none

Other info at evaluation tab

Modeling issues

Modeling issues about Situation

There is no Modeling issue related to this proposal.