Submissions:Situation
From Odp
General description
Name: | Situation |
---|---|
Submitted by: | User:ValentinaPresutti |
Also Known As: | |
Intent: | To represent facts, circumstances, observed contexts. |
Domains: | |
Competency Questions: |
|
Solution description: | |
Reusable OWL Building Block: | http://www.ontologydesignpatterns.org/cp/owl/situation.owl (1347) |
Consequences: | This CP allows the designer to model both a certain situation, and the entities that are involved. |
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): | |
Extracted From: | |
Reengineered From: | |
Has Components: | |
Specialization Of: | |
Related CPs: |
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.
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.
Reviews
There is no review about this proposal. This revision (revision ID 1751) takes in account the reviews: none
Other info at evaluation tab