Line 8: Line 8:
 
|Name=Activity Pattern
 
|Name=Activity Pattern
 
|Intent=To incorporate the general two perspectives of activities: a workflow perspective, which are often observed in planning-related applications, and a spatiotemporal perspective, which are often found in geographic activity analysis.
 
|Intent=To incorporate the general two perspectives of activities: a workflow perspective, which are often observed in planning-related applications, and a spatiotemporal perspective, which are often found in geographic activity analysis.
|Domain=Workflow
+
|Domain=Workflow,General
 
|CompetencyQuestion=What are the requirements to complete an activity?
 
|CompetencyQuestion=What are the requirements to complete an activity?
 
Which places are involved in the activity?
 
Which places are involved in the activity?

Revision as of 01:33, 16 September 2014

Warning.gif

Warning!

This is an old revision. Go to current revision

Certified.png
This pattern has been certified.

Related submission, with evaluation history, can be found here

Working.gif Last modified date is: 2014-09-16

Graphical representation

Diagram

Activity3 small.png

General description

Name: Activity Pattern
Submitted by: YingjieHu
Also Known As:
Intent: To incorporate the general two perspectives of activities: a workflow perspective, which are often observed in planning-related applications, and a spatiotemporal perspective, which are often found in geographic activity analysis.
Domains:

Workflow, General

Competency Questions:
  • What are the requirements to complete an activity?

Which places are involved in the activity? Can other planned activities/tasks be combined with this activity? Which chained activities are necessary to achieve this activity? Which activities are afforded by specific places? Where and when to acquire an activity-relevant object?

Solution description: Activity is an important concept in many fields, and a number of

activity-related ontologies have been developed. While suitable for their designated use cases, these ontologies cannot be easily generalized to other applications. This work aims at providing a generic ontology design pattern to model the common core of activities in different domains. Such a pattern can be used as a building block to construct more specific activity ontologies.

Reusable OWL Building Block: 1 (512)
Consequences: Only two perspectives for activities are included in this pattern. While these two perspectives are commonly observed in existing work, other views toward activities may also need to be supported in future work.
Scenarios: Activity or task planning. Help find out which activities should be completed before other activities.Activity decomposition. Find out what are the sub-activities that constitute the super activity.Spatiotemporal queries. Find out the activities that happen at particular locations and time.
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:



Elements

The An Ontology Design Pattern for Activity Reasoning Content OP locally defines the following ontology elements:

ObjectProperty hasDependent (owl:ObjectProperty)
ArrowRight.gif hasDependent page
ObjectProperty hasOutcome (owl:ObjectProperty)
ArrowRight.gif hasOutcome page
ObjectProperty hasPart (owl:ObjectProperty)
ArrowRight.gif hasPart page
ObjectProperty hasParticipant (owl:ObjectProperty)
ArrowRight.gif hasParticipant page
ObjectProperty hasRequirement (owl:ObjectProperty)
ArrowRight.gif hasRequirement page
ObjectProperty isDependentOf (owl:ObjectProperty)
ArrowRight.gif isDependentOf page
ObjectProperty isPartOf (owl:ObjectProperty)
ArrowRight.gif isPartOf page
ObjectProperty isPrecededBy (owl:ObjectProperty)
ArrowRight.gif isPrecededBy page
ObjectProperty isRequirementOf (owl:ObjectProperty)
ArrowRight.gif isRequirementOf page
ObjectProperty precedes (owl:ObjectProperty)
ArrowRight.gif precedes page
ObjectProperty produces (owl:ObjectProperty)
ArrowRight.gif produces page
ObjectProperty supports (owl:ObjectProperty)
ArrowRight.gif supports page
ObjectProperty takesPlaceAt (owl:ObjectProperty)
ArrowRight.gif takesPlaceAt page
DatatypeProperty hasDuration (owl:DatatypeProperty)
ArrowRight.gif hasDuration page
DatatypeProperty hasEnd (owl:DatatypeProperty)
ArrowRight.gif hasEnd page
DatatypeProperty hasStart (owl:DatatypeProperty)
ArrowRight.gif hasStart page
Class Activity (owl:Class)
ArrowRight.gif Activity page
Class FixedActivity (owl:Class)
ArrowRight.gif FixedActivity page
Class FlexibleActivity (owl:Class)
ArrowRight.gif FlexibleActivity page
Class Outcome (owl:Class)
ArrowRight.gif Outcome page
Class Place (owl:Class)
ArrowRight.gif Place page
Class Requirement (owl:Class)
ArrowRight.gif Requirement page

Additional information

While this pattern so far focuses on human activities, the agents that are involved in this pattern may also be other autonomous agents, such as animals.

Scenarios

Scenarios about An Ontology Design Pattern for Activity Reasoning

No scenario is added to this Content OP.

Reviews

Reviews about An Ontology Design Pattern for Activity Reasoning
There is no review about this proposal.
Some subquery has no valid condition.

This revision (revision ID 11997) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about An Ontology Design Pattern for Activity Reasoning
There is no Modeling issue related to this proposal.
Some subquery has no valid condition.


References

Add a reference


The page [[Bootstrap:Footer]] was not found.