Submissions:ActivitySpecification

From Odp

Jump to: navigation, search


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 13639

Graphical representation

Diagram

Image:Activityspec op.png

General description

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:

Event Processing, General

Competency Questions:
  • What are the preconditions (effects) of a given activity?
  • Is/are the precondition(s) true at some time t?
  • Is/are the effect(s) true at some time t?
  • If we observe some state
  • what activity may have caused it?
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: http://ontology.eil.utoronto.ca/icity/ActivitySpecification (21)
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:


Elements

The ActivitySpecification Content OP locally defines the following ontology elements:

Additional information

Scenarios

Scenarios about ActivitySpecification

No scenario is added to this Content OP.

Reviews

Reviews about ActivitySpecification

There is no review about this proposal. This revision (revision ID 13639) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about ActivitySpecification

There is no Modeling issue related to this proposal.


References

Add a reference


Personal tools
Quality Committee
Content OP publishers