Submissions:Situation Revision as of 17:28, 26 October 2008 by ValentinaPresutti (Talk | contribs) (Article is waiting for review.) (diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Warning!

This is an old revision. Go to current revision

This pattern has been certified.

Related submission, with evaluation history, can be found here

Last modified date is: 2008-10-26

General description

Name:	Situation
Submitted by:	User:ValentinaPresutti
Also Known As:
Intent:	To represent facts, circumstances, observed contexts.
Domains:
Competency Questions:	What entities are in the seeting of a certain situation?
Solution description:
Reusable OWL Building Block:	1 (770)
Consequences:	This CP allows the designer to model both a certain situation, and the entities that are involved. It provides designers with a vocabulary for representing n-ary relations.
Scenarios:	I prepared a coffee with my heater, 300 ml of water, and an Arabica coffee mix.
Known Uses:
Web References:
Other References:
Examples (OWL files):	http://www.ontologydesignpatterns.org/cp/examples/situation/coffee.owl
Extracted From:	http://www.loa-cnr.it/ontologies/DUL.owl
Reengineered From:
Has Components:
Specialization Of:
Related CPs:	Submissions:Submissions:Description

Elements

The Situation Content OP locally defines the following ontology elements:

Entity (owl:Class) Anything: real, possible, or imaginary, which some modeller wants to talk about for some purpose.

Entity 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

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

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 3050) takes in account the reviews: none

Other info at evaluation tab