Difference between revisions of "ISO5087-1:Activity"

From City Data Model Project Collaboratory
Jump to navigation Jump to search
m (Text replacement - "Value=Activity" to "Value=5087-1:Activity")
m (Megankatsumi moved page Iso5087-1:Activity to ISO5087-1:Activity: Text replacement - "Iso5087-1:Activity" to "ISO5087-1:Activity")
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{Class Definition
 
{{Class Definition
−
|Pattern=Ptest3
+
|Pattern=Pattern:Activity Pattern, Pattern:City Service Pattern, Pattern:Recurring Event Pattern, Pattern:Resource Pattern
 
|Description=An Activity describes something that occurs in the domain. It has the following set of core properties:  
 
|Description=An Activity describes something that occurs in the domain. It has the following set of core properties:  
 
* hasSubactivity: identifies a more granular activity that the activity may be decomposed into.  
 
* hasSubactivity: identifies a more granular activity that the activity may be decomposed into.  
Line 25: Line 25:
  
 
Figure 2 illustrates the use of the Activity Ontology to describe a class of objects that should be identified as “Drive to Work” activities, where the effect of such an activity is a Conjunctive state. The conjunctive state is decomposed into two terminal states, meaning that it should be interpreted as a state where both sub-states (DriverAtWork and CarAtWork) are true.
 
Figure 2 illustrates the use of the Activity Ontology to describe a class of objects that should be identified as “Drive to Work” activities, where the effect of such an activity is a Conjunctive state. The conjunctive state is decomposed into two terminal states, meaning that it should be interpreted as a state where both sub-states (DriverAtWork and CarAtWork) are true.
 +
|Interface Specification References=ISO 5087-1 City data model — Part 1: Foundation level concepts
 
|Definition Status=Pending Approval
 
|Definition Status=Pending Approval
 
}}
 
}}
Line 88: Line 89:
 
|Property=Prov:wasAssociatedWith
 
|Property=Prov:wasAssociatedWith
 
|Restriction=only
 
|Restriction=only
−
|Value=Agent
+
|Value=ISO5087-1:Agent
 
}}
 
}}
 
}}
 
}}

Latest revision as of 05:17, 16 December 2022


Pattern

This class has been associated with the following pattern: Pattern:Activity Pattern, Pattern:City Service Pattern, Pattern:Recurring Event Pattern, Pattern:Resource Pattern Pattern:Activity Pattern, Pattern:City Service Pattern, Pattern:Provenance Pattern, Pattern:Recurring Event Pattern, Pattern:Resource Pattern, Ptest3

Subclass Of

Description

An English description of the definition (what distinguishes this sense of the term?).

An Activity describes something that occurs in the domain. It has the following set of core properties:

  • hasSubactivity: identifies a more granular activity that the activity may be decomposed into.
  • hasStatus: identifies an ActivityStatus. This specifies the status of the activity at some point or interval in time. For example, the activity may be “scheduled, “executing” or “completed”.
  • hasPrecondition: identifies a State that must be realized in order for the activity to occur.
  • hasEffect: identifies a State that is realized once the activity has occurred.
  • occursAt: identifies a time Interval over which the activity occurs. o hasLocation: identifies a location (a spatial Feature) where the activity occurs.
  • scheduledFor: identifies the time Interval that an activity was scheduled to be performed/occur at.
  • occursBefore: identifies an activity that the activity occurred before.

An Activity may also be described with the following, supplemental properties:

  • enabledBy: identifies a State that in some (indirect) way enabled the activity to occur. An activity is enabled by a state if the state is a precondition for the activity or if the state is a precondition of some subactivity of the activity. The enabledBy property is a generalization (super-property) of the hasPrecondition property.
  • causes: identifies a State that in some (indirect) way was caused by the occurrence of the activity. An activity is caused by a state if the state is an effect of the activity or if the state is an effect of some subactivity of the activity. The causes property is a generalization (super-property) of the hasEffect property.
  • occursDirectlyBefore: identifies an activity that occurred immediately prior to the activity. The occursDirectlyBefore property is a sub-property of the occursBefore property.
  • beginOf: identifies the time Instant that the activity occurs at.
  • endOf: identifies the time Instant that the activity ends at.

In Provenance Pattern, an Activity is something that acts on Entities (such as consuming or transforming them). An Activity has the following core properties:

  • used: the used property identifies an Entity(s) that was used by a particular Activity. For example, if some set of data was generated by the activity of running a predictive simulation model, then the input dataset(s) would be identified as used by the simulation model prediction activity.
  • wasAssociatedWith: the wasAssociatedWith property identifies an Agent(s) that is in some way responsible for the activity taking place.


An Activity may be further defined by (decomposed into) Subactivities. An Activity may have precondition and/or effect State. An Activity may be enabled by or cause some State. An enabling of causing state is a generalization of a precondition/effect; an Activity is enabled by or causes some State if it has a subactivity with a precondition or effect (respectively) of that State. In other words, the state may not be required directly before, or cause directly after the activity, but by some more specialized sub-activity. An Activity occurs at some point in time and space. An Activity takes place during some interval, and so has some duration. An Activity may have some Manifestations that participate in it. An Activity is something that acts on Entities (such as consuming or transforming them).

Class Diagram Description

An activity cluster provides a basic structure for representing activity specifications. Illustrated in Figure 1, it consists of an activity connected to an enabling and caused state, each of which may be a state tree that defines complex states via decomposition into conjunctions and disjunctions of states.

Figure 2 illustrates the use of the Activity Ontology to describe a class of objects that should be identified as “Drive to Work” activities, where the effect of such an activity is a Conjunctive state. The conjunctive state is decomposed into two terminal states, meaning that it should be interpreted as a state where both sub-states (DriverAtWork and CarAtWork) are true.

Required by Use Case(s)

(why is this specialized definition needed?)

Finding, Reserving, and Paying for Parking

CDM References

What other classes or properties reference this term?

Interface Specification References

This class has been associated with the following interface specification items: ISO 5087-1 City data model — Part 1: Foundation level concepts

Sources

Sources considered when developing the class:


Status

Pending Approval

Has Subclass(es)



Annotations

Annotation Value


Manchester Syntax Specification

Property Restriction Value
HasStatus exactly 1 5087-1:ActivityStatus
HasSubactivity only 5087-1:Activity
HasPrecondition only State
EnabledBy only State
HasEffect only State
Causes only State
ScheduledFor exactly 1 Time:Interval
occursAt some Time:Interval
BeginOf some Time:Instant
EndOf some Time:Instant
OccursBefore only 5087-1:Activity
OccursDirectlyBefore only 5087-1:Activity
HasLocation only Loc:Feature
Prov:used only Entity
Prov:wasAssociatedWith only ISO5087-1:Agent


Supplementary Figures

Figure Caption
Act-1.png
Figure 1: A generic activity cluster.
Act-2.png
Figure 2: Example use of the Activity Ontology.
Prov1.png
Figure 3: The Provenance Ontology main classes and properties
Retrieved from "http://citydatastandard.org/index.php?title=ISO5087-1:Activity&oldid=31723"