Accomplishment
type: Class
subclass of: ActivityExecuted
adapted from: DOLCE-Lite, Accomplishment

Achievement
type: Class
subclass of: ActivityExecuted
adapted from: DOLCE-Lite, Achievement
comment: Executed Activities by an Agent are called achievements if they are atomic

Action
type: Class
subclass of: ActivityOccurence
comment: An Activity with at least one Agent that isParticipantIn it, and that executes a Task that typically isDefinedIn a Plan, Workflow, Project, etc.

Activity
type: Class
adapted from: Prov-O, Activity
adapted from: iCity, Activity
comment: An Activity describes something that occurs in the domain. 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.

ActivityExecuted
type: Class
subclass of: Activity
adapted from: Prov-O, Activity. Used for Provenance. Capturing What Happended

ActivityOccurence
type: Class
subclass of: Activity
adapted from: iCity, ActivityOccurence
comment: An occurrence of some Activity that occurs at some point in time and space

ActivityTrace
type: Class
subclass of: ActivityExecuted
adapted from: Prov-O, Activity. Used for Provenance. Capturing What Happended
comment: A Completed Activity. Used to capture What Happened.

Agent
type: Class
adapted from: W3 prov:Agent

Aims
type: Class
subclass of: Purpose
comment: Broad statements of intent or overarching aspirations. Targets and Milestones. Realization, Detailed and Concrete. Measurable.

AssociationTrace
type: Class
subclass of: AgentInfluenceTrace
adapted from: W3 prov:Association

Behavior
type: Class
comment: Refers to the actions, reactions, or conduct of a person or organization in response to internal or external stimuli

Collection
type: Class
adapted from: W3 prov:Activity

CommunicationSpec
type: Class
subclass of: Specification
adapted from: https://w3id.org/ep-plan CommunicationSpec
comment: A specification of how communication/exchange of variables between two steps should be performed.

Entity
type: Class
adapted from: W3 prov:Entity

Geometry
type: Class
adapted from: geom:geometry

Habit
type: Class
subclass of: Behavior
comment: A specific type of behavior that is repeated regularly and tends to occur automatically in response to certain cues or triggers.

InferredIntent
type: Class
subclass of: Insight
comment: determination or estimation of the underlying purpose or goal behind a particular action, behavior, or communication

InstantaneousEvent
type: Class
adapted from: W3 prov:Activity
comment: An instantaneous event, or event for short, happens in the world and marks a change in the world, in its activities and in its entities. The term 'event' is commonly used in process algebra with a similar meaning. Events represent communications or interactions; they are assumed to be atomic and instantaneous.

Membership
type: Class
subclass of: Situation
subclass of: Thing
adapted from: W3 org:Membership
comment: Relation between an Agent, an Organization and Role

MembershipRole
type: Class
subclass of: Role
comment: Indicaes the Role the Agent plays in a Membership relationship with an Organzation

Mission
type: Class
subclass of: Purpose
comment: How we get there

Organization
type: Class
subclass of: Agent
adapted from: W3 org:Organization
adapted from: W3 prov:Organization
adapted from: foaf:Organization
comment: Has identity and definining purpose

Person
type: Class
subclass of: Agent
adapted from: W3 org:Person
adapted from: W3 prov:Person
adapted from: foaf:Person

Plan
type: Class
subclass of: ProcessSpec
adapted from: http://purl.org/net/p-plan
adapted from: https://w3id.org/ep-plan Plan

Planning
type: Class
comment: An ACTIVITY whose major EFFECT is to produce a Plan

Point
type: Class
adapted from: wgs:Point

Post
type: Class
adapted from: W3 org:Post
comment: A Post represents some position within an organization that exists independently of the person or persons filling it. Posts may be used to represent situations where a person is a member of an organization ex officio (for example the Secretary of State for Scotland is part of UK Cabinet by virtue of being Secretary of State for Scotland, not as an individual person). A post can be held by multiple people and hence can be treated as a organization in its own right.

Process
type: Class
subclass of: Activity
subclass of: Thing
adapted from: BFO:process
comment: A squence of Activities. An occurrent that has temporal proper parts and for some time t, p s-depends_on some material entity at t. 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;

ProcessSpec
type: Class
subclass of: ActivitySpec
subclass of: Specification
adapted from: Academic Event Ontology (AEON)
comment: Specification of Occurrent that has temporal proper parts

Purpose
type: Class
comment: Why do we do what we do? We believe ....

Role
type: Class
adapted from: W3 prov:Role
adapted from: skos:Concept

Site
type: Class
adapted from: W3 org:Site
comment: An office or other premise at which the organization is located

State
type: Class
subclass of: Thing
comment: A state refers to a class of manifestations. It may be a precondition or effect of some Activity, or more generally it may enabled or be caused by some Activity. If a state is complex, it may refer to some combination of classes of manifestations. A note on complex states: Say that a shopping activity, Activity-Shop, requires both the VehicleW30LGas state, but also some state wherein the mall is open, OpenMall. Each state would first be defined separately. Then, we can simply state: precondition(VehicleW30LGas,Activity-Shop) AND precondition(OpenMall,Activity-Shop) were the preconditions required disjunctively, we could state: precondition(VehicleW30LGas,Activity-Shop) OR precondition(OpenMall,Activity-Shop) However, in large and complex domains, there will be cases in which the above approach is undesirable. In particular, due to the complexity of the description that results as the state being described becomes more detailed. In many cases it will be more natural and convenient to be able to refer to a single, aggregate state. We therefore extend the representation of States to capture aggregation, as approached in the concept of state trees introduced by TOVE as a construct for the activity cluster. A State may be either non-terminal or terminal. A terminal state has no child states, and therefore refers directly to a class of manifestations, whereas a non-terminal state has child states, which may define some classes of manifestations, or further define some other complex states. NonTerminalState(x) v TerminalState(x) = State(x) A state cannot be both non-terminal and terminal. TerminalState disjointWith NonTerminalState

StateOfAffair
type: Class
comment: refers to the existing situation or condition of a particular matter or issue at a specific point in time (past, current or future time). It encapsulates the overall circumstances, events, or conditions that characterize a given situation or context.

StrategicPlan
type: Class
subclass of: Plan
comment: Strategic plan outlines the specific steps, initiatives, and objectives necessary to implement a chosen strategy

Strategy
type: Class
subclass of: Approach
comment: Strategy refers to the overarching approach or direction chosen to achieve specific goals or objectives.

Task
type: Class
subclass of: PlannedActivity
adapted from: https://w3id.org/semanticarts/ontology/gistCore Task
comment: Something that could potentially be executed, which is merely described but not proposed in any specific way, such as a business process for onboarding a new employee, or the steps in a recipe for making polyethylene from ethylene, is not a task but rather a task specification.

TimeInstant
type: Class
subclass of: TemporalEntity
adapted from: w3.org/2006/time, Time instant

TimeInterval
type: Class
subclass of: TemporalEntity
adapted from: w3.org/2006/time, Time interval

Vision
type: Class
subclass of: Purpose
comment: What your trying to achieve?