Line 26: | Line 26: | ||
{{Has Element Template | {{Has Element Template | ||
|HasElement=hasSetting | |HasElement=hasSetting | ||
+ | }} | ||
+ | {{Has Element Template | ||
+ | |HasElement=Element x | ||
}} | }} |
Name: | Situation |
---|---|
Submitted by: | |
Also Known As: | |
Intent: | To represent facts, circumstances, observed contexts. |
Domains: | |
Competency Questions: | |
Solution description: | |
Reusable OWL Building Block: | 1 (85) |
Consequences: | This CP allows the designer to model both a certain situation, and the entities that are involved. |
Scenarios: | Scenario 1, Scenario 2, Scenario 3 |
Known Uses: | ... |
Web References: | www.site1.org, www.site2.org |
Other References: | Reference 1, reference2 |
Examples (OWL files): | |
Extracted From: | |
Reengineered From: | |
Has Components: | |
Specialization Of: | |
Related CPs: |
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.