Diagram
Name: | ActivitySpecification |
---|---|
Submitted by: | MeganKatsumi |
Also Known As: | Activity Specification OP |
Intent: | This work is concerned with supporting a correct and meaningful representation of activities on the Semantic Web, with the potential to support tasks such as activity recognition and reasoning about causation. This requires an ontology capable of more than simply documenting and annotating individual activity occurrences; definitions of activity specifications are required.
Current representations of activities in OWL do not meet the basic requirements for activity specifications. Detailed definitions of an activity's preconditions and effects are lacking, in particular with respect to a consideration of change over time. This pattern leverages existing work to fill this void with an ontology design pattern for activity specifications in OWL. |
Domains: | |
Competency Questions: | |
Solution description: | The proposed solution adopts a view of causality similar to the Event Calculus [Kowalski, 1986], employing the concept of manifestations to describe the states (fluents). |
Reusable OWL Building Block: | 1 (245) |
Consequences: | (-) Requires a temporal representation of the domain -- specifically using the Logical OP for change -- which results in a larger, more complex representation.
(+) However, given that the concepts are preconditions and effects of an activity, they should be subject to change and so the resulting representation is (though larger) more appropriate and more accurate. |
Scenarios: | This pattern is applicable for a wide range of scenarios. In essence, for the formalization of any activity precondition/effect. For example: -My car must have gas (an manifestation of a specific vehicle should have gas) before I can drive to work (the manifestation should exist at some time before the drive to work activity occurs) -An effect of my driving to work is that I am at work and so is my car. |
Known Uses: | http://ontology.eil.utoronto.ca/icity/UrbanSystem |
Web References: | |
Other References: | |
Examples (OWL files): | |
Extracted From: | |
Reengineered From: | |
Has Components: | |
Specialization Of: | |
Related CPs: |
The ActivitySpecification Content OP locally defines the following ontology elements:
No scenario is added to this Content OP.
This revision (revision ID 13639) takes in account the reviews: none
Other info at evaluation tab