Submissions:TaskExecution
From Odp
Current revision (14:01, 8 March 2010) (view source) m |
|||
| (7 intermediate revisions not shown.) | |||
| Line 1: | Line 1: | ||
{{Content_OP_Proposal_toolbar}} | {{Content_OP_Proposal_toolbar}} | ||
| - | {{ | + | {{Graphical representation header}} |
| - | |ImageName= | + | {{Graphical representation |
| + | |ImageName=Taskexecution.jpg | ||
}} | }} | ||
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
| - | |||
|SubmittedBy=AldoGangemi | |SubmittedBy=AldoGangemi | ||
| - | | | + | |Name=TaskExecution |
| - | | | + | |Intent=To represent actions through which tasks are executed. |
| - | + | |Domain=Organization,Management,Scheduling,Workflow | |
| - | | | + | |
| - | + | ||
|CompetencyQuestion=which task is executed through this action? | |CompetencyQuestion=which task is executed through this action? | ||
what actions can done in order to execute that task? | what actions can done in order to execute that task? | ||
| - | | | + | |ContentODPDescription=---- |
| + | |ReusableOWLBuildingBlock=http://www.ontologydesignpatterns.org/cp/owl/taskexecution.owl | ||
| + | |Consequences=This CP allows designers to make assertions on roles played by agents without involving the agents that play that roles, and vice versa. It allows to express neither the context type in which tasks are defined, not the particular context in which the action is carried out. Moreover, it does not allow to express the time at which the task is executed through the action (for actions that do not solely execute that certain task). | ||
| + | |Scenario=She smiled at us, so obtaining the effect of making us feeling positive. | ||
| + | |ExtractedFrom=http://www.loa-cnr./ontologies/DUL.owl | ||
| + | |HasComponent=Submissions:AgentRole | ||
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
| Line 25: | Line 28: | ||
|HasElement=isExecutedIn | |HasElement=isExecutedIn | ||
}} | }} | ||
| - | + | {{Additional information header}} | |
| - | {{ | + | |
| - | + | ||
| - | + | ||
(type): http://www.w3.org/2002/07/owl#Ontology | (type): http://www.w3.org/2002/07/owl#Ontology | ||
| Line 43: | Line 43: | ||
(versionInfo): Created by Aldo Gangemi | (versionInfo): Created by Aldo Gangemi | ||
| + | |||
| + | |||
| + | [[Category:Waiting for review]] | ||
| + | {{Scenarios about me}} | ||
| + | {{Reviews about me}} | ||
| + | {{Modeling issues about me}} | ||
| + | {{My references}} | ||
Current revision
| If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 9131 |
Graphical representation
Diagram
General description
| Name: | TaskExecution |
|---|---|
| Submitted by: | AldoGangemi |
| Also Known As: | |
| Intent: | To represent actions through which tasks are executed. |
| Domains: | |
| Competency Questions: |
what actions can done in order to execute that task? |
| Solution description: | ---- |
| Reusable OWL Building Block: | http://www.ontologydesignpatterns.org/cp/owl/taskexecution.owl (896) |
| Consequences: | This CP allows designers to make assertions on roles played by agents without involving the agents that play that roles, and vice versa. It allows to express neither the context type in which tasks are defined, not the particular context in which the action is carried out. Moreover, it does not allow to express the time at which the task is executed through the action (for actions that do not solely execute that certain task). |
| Scenarios: | She smiled at us, so obtaining the effect of making us feeling positive. |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
Elements
The TaskExecution Content OP locally defines the following ontology elements:
Action (owl:Class) An Event with at least one Agent that isParticipantIn it, and that executes a Task that typically isDefinedIn a Plan, Workflow, Project, etc.
Action page
executesTask (owl:ObjectProperty) A relation between an action and a task, e.g. 'putting some water in a pot and putting the pot on a fire until the water starts bubbling' executes the task 'boiling'.
executesTask page isExecutedIn (owl:ObjectProperty) A relation between an action and a task, e.g. 'putting some water in a pot and putting the pot on a fire until the water starts bubbling' executes the task 'boiling'.
isExecutedIn pageAdditional information
(type): http://www.w3.org/2002/07/owl#Ontology
(relatedCPs): The Nary Classification CP available at http://www.ontologydesignpatterns.org/cp/owl/naryclassification.owl allows to represent temporariness of concepts that classify objects. By specializing naryclassification, it is possible to create a temporally-indexed version of taskexecution. Its imported component taskrole.owl allows to express also the dependence between tasks and roles.
(imports): http://www.ontologydesignpatterns.org/cp/owl/taskrole.owl
(imports): http://www.ontologydesignpatterns.org/cp/owl/participation.owl
(scenarios): She smiled at us, so obtaining the effect of making us feeling positive.
(imports): http://www.ontologydesignpatterns.org/cp/owl/agentrole.owl
(versionInfo): Created by Aldo Gangemi
Scenarios
No scenario is added to this Content OP.
Reviews
There is no review about this proposal. This revision (revision ID 9131) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
There is no Modeling issue related to this proposal.
References
