TMO - Task Management Ontology

Namespace: http://www.semanticdesktop.org/ontologies/2008/05/20/tmo#

Authors:

Marco Brunzel

DFKI

Olaf Grebner

SAP

Maintainers:

Marco Brunzel

DFKI

Olaf Grebner

SAP

Contributors:

Leo Sauermann

DFKI

Michael Sintek

DFKI

Ludger van Elst

DFKI

Ansgar Bernardi

DFKI

Uwe Riss

SAP

Abstract

The TMO Ontology can be used to describe personal tasks of individuals, also known as to-do lists. It is based on RDF and NRL, the Nepomuk Representational Language and other Semantic Web ontologies.

Table of Contents

Classes Overview
Properties Overview
TMO Vocabulary Summary
Description of Classes
Description of Properties

Classes Overview

tmo:AbilityCarrier - AbilityCarrier is an abstract class which circumferences all entities which can ...
tmo:AbilityCarrierInvolvement - The class AbilityCarrier_Involvement ties together an AbilityCarrier with an Abi...
tmo:AbilityCarrierRole - Examples instances of AbilityCarrirRoles are e.g. "requested", "required" and "...
tmo:AgentAbilityCarrier -
tmo:AssociationDependency -
tmo:Attachment - By means of attachments, references to other resources can be established. Resou...
tmo:AttachmentRole - AttachmentRoles further specify the type of how an attachment relates to a task....
tmo:Delegability -
tmo:Importance -
tmo:Interdependence -
tmo:PersonInvolvement - PersonInvolvement realizes n-ary associations to Persons which are realtedd to ...
tmo:PersonInvolvementRole - They further specify the type a person was related to an task. Examples instance...
tmo:PredecessorDependency - In a PredecessorDependency the dependencyMemberA is the task which is to be exe...
tmo:PredecessorSuccessorDependency - The PredecessorSuccessorDependency enables a directed relation between task. By ...
tmo:Priority -
tmo:Role - examples: Architect, Developer, ...
tmo:SimilarityDependence -
tmo:Skill - examples are e.g. technologies like Java, XML, ...
tmo:StateTypeRole - StateTypeRole is an abstract class which subsumes various other classes which re...
tmo:SuccessorDependency - In a SuccessorrDependency the dependencyMemberA is the task which is to be execu...
tmo:SuperSubTaskDependency - By means of the SuperSubTaskDependency one can further describe the subtask-supe...
tmo:Task - The tmo:task is the central entitiey of the tmo. Task can range from vague thing...
tmo:TaskContainer -
tmo:TaskDependency - Between the tasks, further dependencies may exist. These dependencies allow for ...
tmo:TaskPrivacyState - Privacy Status serves for the separation between a professional and a private pu...
tmo:TaskState - The task state property allows tracking a task during its lifecycle. Initially t...
tmo:TaskTransmission - On the SSD, tasks are not restricted to one person and may cross from the PTM of...
tmo:TransmissionState - States a task can go through during transmission of an task.
tmo:TransmissionType - By means of the TransmissionType one can distinguish several different types whi...
tmo:UndirectedDependency - A symmetric relations between task.
tmo:Urgency -

Properties Overview

tmo:abilityCarrier -
tmo:abilityCarrierInvolvement -
tmo:abilityCarrierRole -
tmo:abilityCarrierTask -
tmo:actualCompletion -
tmo:actualEndTime -
tmo:actualStartTime -
tmo:actualTime -
tmo:attachment - connects a Task with an Attachment object. Attachments are associations of Thing...
tmo:attachmentReference -
tmo:attachmentRole -
tmo:attachmentTask - Inverse of attachment, connects an Attachment Association to the associated Task...
tmo:containsTask -
tmo:contextTask -
tmo:contextThread -
tmo:createdBy -
tmo:dateTime - dateTime subsumes various properties with Range XMLSchema:dateTime. If possible ...
tmo:delegability -
tmo:dependency -
tmo:dependencyDescription - Endusers can clarify why they created a depedency.
tmo:dependencyMemberA - The semantic of this relation is defined in the sublclass of undirected Dependen...
tmo:dependencyMemberB - The semantic of this relation is defined in the sublclass of undirected Dependen...
tmo:dependencyOrderNumber -
tmo:dependencyType -
tmo:dueDate -
tmo:endTime -
tmo:importance -
tmo:indexPosition -
tmo:involvedPerson -
tmo:involvedPersonRole -
tmo:involvedPersonTask -
tmo:involvedPersons -
tmo:lastReviewDate -
tmo:logEntry -
tmo:nextReviewIntervall -
tmo:priority -
tmo:progress -
tmo:receiveDateTime -
tmo:sendDateTime -
tmo:startTime -
tmo:stateTypeRole -
tmo:subTask -
tmo:subTaskOrdering - Ordering of the subtasks listed in the tmo:subTasks property of this Task. This ...
tmo:superTask -
tmo:targetCompletion -
tmo:targetEndTime -
tmo:targetStartTime -
tmo:targetTime -
tmo:taskDescription - The task description helps users to understand the goal and the proceeding of a ...
tmo:taskGoal -
tmo:taskId - The Task Identifier allows a unique identification of a task object within the r...
tmo:taskName - The Task Name helps the user to identify a task in a list. It should be expressi...
tmo:taskPrivacyState - For the separation between professional and private purpose of a task, this attr...
tmo:taskReference -
tmo:taskSource - here can be stated from which sources a task was derived. e.g from another task ...
tmo:taskState - The task state describes the current state of the task as described in Section 5...
tmo:taskStateChangesFrom -
tmo:taskStateChangesTo -
tmo:taskTransmission -
tmo:timemanagement -
tmo:transmissionFrom -
tmo:transmissionState -
tmo:transmissionStateChangesFrom -
tmo:transmissionStateChangesTo -
tmo:transmissionTask -
tmo:transmissionTo -
tmo:transmissionType -
tmo:urgency -

TMO Vocabulary Summary

Description of Classes

tmo:AbilityCarrier

LabelAbilityCarrier
DescriptionAbilityCarrier is an abstract class which circumferences all entities which can take action or which are somehow involved in tasks. This is in other task conceptualizations rather named "actor". But here it is named AbilityCarrier because it is not neccessarily "active". The execution of a task relies on certain abilities. The abstract concept of Abilitiy_Carriers circumference all those more concrete concepts of which one can think of while working on tasks. Using this abstract class enables to substitute such Ability Carrier's in the process of generating patterns from task instances and vice versa in the process of instantiating task instances from patterns without violating the schema. With this attribute, a series of ability carrying entities (Person, Role, Skill, OrganizationalUnit, InformalDescribedAbility) and the role of involvement (required, request, used) is enabled. The role hereby allows specifying how the ability carrying entity is or was involved.
Super-classes 
Sub-classestmo:AgentAbilityCarrier, tmo:Skill, tmo:Role
In domain of 
In range oftmo:abilityCarrier

tmo:AbilityCarrierInvolvement

LabelAbilityCarrierInvolvement
DescriptionThe class AbilityCarrier_Involvement ties together an AbilityCarrier with an AbilityCarrier_Role. This is a role based modelling approach. An n-ary relation is realized.
Super-classespimo:ClassOrThingOrPropertyOrAssociation, pimo:Association
Sub-classes 
In domain oftmo:abilityCarrier, tmo:abilityCarrierTask, tmo:abilityCarrierRole
In range oftmo:abilityCarrierInvolvement

tmo:AbilityCarrierRole

LabelAbilityCarrierRole
DescriptionExamples instances of AbilityCarrirRoles are e.g. "requested", "required" and "used" which further specify the type a person was involved in.
Super-classestmo:StateTypeRole
Sub-classes 
In domain of 
In range oftmo:abilityCarrierRole

tmo:AgentAbilityCarrier

LabelAgentAbilityCarrier
Description
Super-classestmo:AbilityCarrier
Sub-classes 
In domain of 
In range of 

tmo:AssociationDependency

LabelAssociationDependency
Description
Super-classestmo:UndirectedDependency, pimo:ClassOrThingOrPropertyOrAssociation, pimo:Association, tmo:TaskDependency
Sub-classes 
In domain of 
In range of 

tmo:Attachment

LabelAttachment
DescriptionBy means of attachments, references to other resources can be established. Resources are information objects. Every Thing, which can be referenced, on the SSD is an information object. In contrast to the usual SSD references/associations, here additionally information can be specified. Further metadata about the role an attachment plays can be stated by means of instances of AttachmentRole. It can be expressed what the Role of attachment is e.g., regarding "desired/requested" or "required" or "potentially useful / somehow related" or "used/produced/achieved". The reference property models the actual link to the attached piece of information.
Super-classespimo:ClassOrThingOrPropertyOrAssociation, pimo:Association
Sub-classes 
In domain oftmo:createdBy, tmo:attachmentTask, tmo:attachmentReference, tmo:attachmentRole
In range oftmo:attachment

tmo:AttachmentRole

LabelAttachmentRole
DescriptionAttachmentRoles further specify the type of how an attachment relates to a task. Example instances of AttachmentRoles are e.g. "desired_request", "required" and "used".
Super-classestmo:StateTypeRole
Sub-classes 
In domain of 
In range oftmo:attachmentRole

tmo:Delegability

LabelDelegability
Description
Super-classestmo:StateTypeRole
Sub-classes 
In domain of 
In range oftmo:delegability

tmo:Importance

LabelImportance
Description
Super-classestmo:StateTypeRole
Sub-classes 
In domain of 
In range oftmo:importance

tmo:Interdependence

LabelInterdependence
Description
Super-classestmo:UndirectedDependency, pimo:ClassOrThingOrPropertyOrAssociation, pimo:Association, tmo:TaskDependency
Sub-classes 
In domain of 
In range of 

tmo:PersonInvolvement

LabelPersonInvolvement
DescriptionPersonInvolvement realizes n-ary associations to Persons which are realtedd to an task. The involvement is further characterized by an PersonTaskRole.
Super-classespimo:ClassOrThingOrPropertyOrAssociation, pimo:Association
Sub-classes 
In domain oftmo:involvedPersonTask, tmo:involvedPersonRole, tmo:involvedPerson
In range oftmo:involvedPersons

tmo:PersonInvolvementRole

LabelPersonInvolvementRole
DescriptionThey further specify the type a person was related to an task. Examples instances of AttachmentRoles are e.g.
Super-classestmo:StateTypeRole
Sub-classes 
In domain of 
In range oftmo:involvedPersonRole

tmo:PredecessorDependency

LabelPredecessorDependency
DescriptionIn a PredecessorDependency the dependencyMemberA is the task which is to be executed before dependencyMemberB.
Super-classestmo:PredecessorSuccessorDependency, pimo:ClassOrThingOrPropertyOrAssociation, pimo:Association, tmo:TaskDependency
Sub-classes 
In domain of 
In range of 

tmo:PredecessorSuccessorDependency

LabelPredecessorSuccessorDependency
DescriptionThe PredecessorSuccessorDependency enables a directed relation between task. By means of the concrete sublcasses one can further distinguish from which point of view this relation is created.
Super-classestmo:TaskDependency, pimo:Association, pimo:ClassOrThingOrPropertyOrAssociation
Sub-classestmo:SuccessorDependency, tmo:PredecessorDependency
In domain of 
In range of 

tmo:Priority

LabelPriority
Description
Super-classestmo:StateTypeRole
Sub-classes 
In domain of 
In range oftmo:priority

tmo:Role

LabelRole
Descriptionexamples: Architect, Developer, ...
Super-classestmo:AbilityCarrier
Sub-classes 
In domain of 
In range of 

tmo:SimilarityDependence

LabelSimilarityDependence
Description
Super-classestmo:UndirectedDependency, pimo:ClassOrThingOrPropertyOrAssociation, pimo:Association, tmo:TaskDependency
Sub-classes 
In domain of 
In range of 

tmo:Skill

LabelSkill
Descriptionexamples are e.g. technologies like Java, XML, ...
Super-classestmo:AbilityCarrier
Sub-classes 
In domain of 
In range of 

tmo:StateTypeRole

LabelStateTypeRole
DescriptionStateTypeRole is an abstract class which subsumes various other classes which represent "states" or roles e.g. in role based modelling conpetualisations.
Super-classes 
Sub-classestmo:AbilityCarrierRole, tmo:TaskPrivacyState, tmo:Urgency, tmo:TransmissionType, tmo:TransmissionState, tmo:TaskState, tmo:Importance, tmo:Delegability, tmo:Priority, tmo:AttachmentRole, tmo:PersonInvolvementRole
In domain of 
In range of 

tmo:SuccessorDependency

LabelSuccessorDependency
DescriptionIn a SuccessorrDependency the dependencyMemberA is the task which is to be executed after dependencyMemberB.
Super-classestmo:PredecessorSuccessorDependency, pimo:ClassOrThingOrPropertyOrAssociation, pimo:Association, tmo:TaskDependency
Sub-classes 
In domain of 
In range of 

tmo:SuperSubTaskDependency

LabelSuperSubTaskDependency
DescriptionBy means of the SuperSubTaskDependency one can further describe the subtask-supertask relation .e.g by an descriptin. This enables an n-ary relation between subtask and supertask.
Super-classestmo:TaskDependency, pimo:Association, pimo:ClassOrThingOrPropertyOrAssociation
Sub-classes 
In domain of 
In range of 

tmo:TaskContainer

LabelTaskContainer
Description
Super-classespimo:Thing, pimo:ClassOrThingOrPropertyOrAssociation, pimo:Collection, pimo:ClassOrThing
Sub-classes 
In domain oftmo:containsTask
In range of 

tmo:TaskDependency

LabelTaskDependency
DescriptionBetween the tasks, further dependencies may exist. These dependencies allow for a graph network structure. For ease of use, dependencies should not be too frequent, otherwise the primarily character of a hierarchy would be diminished and a consequent graph representation would become considerable. However, such a graph representation has other drawbacks, the user is likely to loose oversight, tree structures are more helpful in structuring the work. A dependency relation is characterized by the type of the relation and by an additional description. There are different possibilities for dependency relations between tasks.
Super-classespimo:ClassOrThingOrPropertyOrAssociation, pimo:Association
Sub-classestmo:SuccessorDependency, tmo:PredecessorDependency, tmo:PredecessorSuccessorDependency, tmo:AssociationDependency, tmo:UndirectedDependency, tmo:Interdependence, tmo:SuperSubTaskDependency, tmo:SimilarityDependence
In domain oftmo:dependencyMemberA, tmo:dependencyMemberB, tmo:dependencyOrderNumber, tmo:dependencyDescription
In range oftmo:dependency

tmo:TaskPrivacyState

LabelTaskPrivacyState
DescriptionPrivacy Status serves for the separation between a professional and a private purpose of a task. This attribute provides with the values "professional/private" a high-level separation of privacy in terms of setting distribution and access rights to other users for the task. This separation may arise as a general Nepomuk issue and may therefore be handled in conjunction with a privacy preserving SSD architecture.
Super-classestmo:StateTypeRole
Sub-classes 
In domain of 
In range oftmo:taskPrivacyState

tmo:TaskState

LabelTaskState
DescriptionThe task state property allows tracking a task during its lifecycle. Initially the state is just "created". The TaskState class was modeled so that for each state can be set which the typical prior and posterior states are. This has the advantage that e.g. a UI can retrieve the allowed states at runtime from the ontology; rather can having this potentially changing knowledge hard coded. But the prior and posterior states are only defaults; the human user is always free to change the state.
Super-classestmo:StateTypeRole
Sub-classes 
In domain oftmo:taskStateChangesFrom, tmo:taskStateChangesTo
In range oftmo:taskState, tmo:taskStateChangesFrom, tmo:taskStateChangesTo

tmo:TaskTransmission

LabelTaskTransmission
DescriptionOn the SSD, tasks are not restricted to one person and may cross from the PTM of one person to the PTM of another. With transmission, we refer to the process of sending a task – from one person (sender) to one or more other persons (receiver(s)) (see Section 5.2.1.3 Task Transmission). Task delegation and task transfer are two special kinds of task transmission which are described at the end of this section. In addition, the collaborative task is realized by task transmission. For the process of sending a task, some information is required. This information is also modelled in the task ontology. This information is still useful after the process of sending a task was completed. Task Delegation is a process where the sender of the task restricts the access rights of the receiver. This includes the right to distribute further this task and additionally the obligation to give feedback to the sender. The person that receives a task by delegation usually has not the full control about the task. The attributes described in the following section have the purpose to enable such "access rights". The receiver will also probably have obligations regarding what to report to whom at which time. In contrast, the simplest case is that all rights are granted to the receiver and there is no feedback desired by the sender. What to do with the task may be apparent by the organization context, or it may be left to the receiver. This is like sending an email – but with the advantage that the information is transferred in the "task space" of the participating persons.
Super-classes 
Sub-classes 
In domain oftmo:transmissionState, tmo:transmissionTo, tmo:receiveDateTime, tmo:sendDateTime, tmo:transmissionTask, tmo:transmissionFrom, tmo:transmissionType
In range oftmo:taskTransmission

tmo:TransmissionState

LabelTransmissionState
DescriptionStates a task can go through during transmission of an task.
Super-classestmo:StateTypeRole
Sub-classes 
In domain oftmo:transmissionStateChangesFrom, tmo:transmissionStateChangesTo
In range oftmo:transmissionState, tmo:transmissionStateChangesFrom, tmo:transmissionStateChangesTo

tmo:TransmissionType

LabelTransmissionType
DescriptionBy means of the TransmissionType one can distinguish several different types which might imply a different business logic. e.g. delegation can mean that the results of the task fulfillment care to be reported back to the sender of the task.
Super-classestmo:StateTypeRole
Sub-classes 
In domain of 
In range oftmo:transmissionType

tmo:UndirectedDependency

LabelUndirectedDependency
DescriptionA symmetric relations between task.
Super-classestmo:TaskDependency, pimo:Association, pimo:ClassOrThingOrPropertyOrAssociation
Sub-classestmo:AssociationDependency, tmo:Interdependence, tmo:SimilarityDependence
In domain of 
In range of 

tmo:Urgency

LabelUrgency
Description
Super-classestmo:StateTypeRole
Sub-classes 
In domain of 
In range oftmo:urgency

Description of Properties

tmo:abilityCarrier

LabelabilityCarrier
Description
Domaintmo:AbilityCarrierInvolvement
Rangetmo:AbilityCarrier
Minimum Cardinality1
Maximum Cardinality1
Super-propertiespimo:associationMember
Sub-properties 

tmo:abilityCarrierInvolvement

LabelabilityCarrierInvolvement
Description
Domaintmo:Task
Rangetmo:AbilityCarrierInvolvement
Super-properties 
Sub-properties 

tmo:abilityCarrierRole

LabelabilityCarrierRole
Description
Domaintmo:AbilityCarrierInvolvement
Rangetmo:AbilityCarrierRole
Minimum Cardinality1
Maximum Cardinality1
Super-propertiestmo:stateTypeRole
Sub-properties 

tmo:abilityCarrierTask

LabelabilityCarrierTask
Description
Domaintmo:AbilityCarrierInvolvement
Rangetmo:Task
Maximum Cardinality1
Super-propertiespimo:associationMember
Sub-properties 

tmo:actualCompletion

LabelactualCompletion
Description
Domaintmo:Task
Rangerdfs:Literal
Maximum Cardinality1
Super-propertiestmo:progress
Sub-properties 

tmo:actualEndTime

LabelactualEndTime
Description
Domaintmo:Task
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiestmo:actualTime, tmo:endTime, tmo:dateTime
Sub-properties 

tmo:actualStartTime

LabelactualStartTime
Description
Domaintmo:Task
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiestmo:actualTime, tmo:startTime, tmo:dateTime
Sub-properties 

tmo:actualTime

LabelactualTime
Description
Domain 
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiestmo:dateTime
Sub-propertiestmo:actualStartTime, tmo:actualEndTime

tmo:attachment

Labelattachment
Descriptionconnects a Task with an Attachment object. Attachments are associations of Things.
Domaintmo:Task
Rangetmo:Attachment
Super-properties 
Sub-properties 

tmo:attachmentReference

LabelattachmentReference
Description
Domaintmo:Attachment
Rangerdfs:Resource
Minimum Cardinality1
Maximum Cardinality1
Super-propertiespimo:associationMember
Sub-properties 

tmo:attachmentRole

LabelattachmentRole
Description
Domaintmo:Attachment
Rangetmo:AttachmentRole
Maximum Cardinality1
Super-propertiestmo:stateTypeRole
Sub-properties 

tmo:attachmentTask

LabelattachmentTask
DescriptionInverse of attachment, connects an Attachment Association to the associated Task. Is required for every instance of Attachment.
Domaintmo:Attachment
Rangetmo:Task
Maximum Cardinality1
Super-propertiespimo:associationMember
Sub-properties 

tmo:containsTask

LabelcontainsTask
Description
Domaintmo:TaskContainer
Rangetmo:Task
Super-propertiespimo:objectProperty, pimo:hasPart
Sub-properties 

tmo:contextTask

LabelcontextTask
Description
Domain 
Rangetmo:Task
Maximum Cardinality1
Super-properties 
Sub-properties 

tmo:contextThread

LabelcontextThread
Description
Domaintmo:Task
Rangehttp://ontologies.opendfki.de/repos/ontologies/wcon/workcontext#MediumTermContextThread
Maximum Cardinality1
Super-properties 
Sub-properties 

tmo:createdBy

LabelcreatedBy
Description
Domaintmo:Attachment
Rangepimo:Person
Maximum Cardinality1
Super-properties 
Sub-properties 

tmo:dateTime

LabeldateTime
DescriptiondateTime subsumes various properties with Range XMLSchema:dateTime. If possible they are further grouped by "abstract" properties.
Domain 
Rangexsd:dateTime
Maximum Cardinality1
Super-properties 
Sub-propertiestmo:actualTime, tmo:dueDate, tmo:lastReviewDate, tmo:endTime, tmo:actualStartTime, tmo:startTime, tmo:sendDateTime, tmo:targetEndTime, tmo:targetTime, tmo:actualEndTime, tmo:receiveDateTime, tmo:targetStartTime

tmo:delegability

Labeldelegability
Description
Domaintmo:Task
Rangetmo:Delegability
Maximum Cardinality1
Super-propertiestmo:timemanagement
Sub-properties 

tmo:dependency

Labeldependency
Description
Domaintmo:Task
Rangetmo:TaskDependency
Super-properties 
Sub-properties 

tmo:dependencyDescription

LabeldependencyDescription
DescriptionEndusers can clarify why they created a depedency.
Domaintmo:TaskDependency
Range 
Maximum Cardinality1
Super-propertiesnao:annotation, nao:description
Sub-properties 

tmo:dependencyMemberA

LabeldependencyMemberA
DescriptionThe semantic of this relation is defined in the sublclass of undirected Dependency on which this property is stated. (The subject of the statment where this property is expressed)
Domaintmo:TaskDependency
Rangetmo:Task
Minimum Cardinality1
Maximum Cardinality1
Super-propertiespimo:associationMember, tmo:taskReference
Sub-properties 

tmo:dependencyMemberB

LabeldependencyMemberB
DescriptionThe semantic of this relation is defined in the sublclass of undirected Dependency on which this property is stated. (The subject of the statment where this property is expressed)
Domaintmo:TaskDependency
Rangetmo:Task
Minimum Cardinality1
Maximum Cardinality1
Super-propertiespimo:associationMember, tmo:taskReference
Sub-properties 

tmo:dependencyOrderNumber

LabeldependencyOrderNumber
Description
Domaintmo:TaskDependency
Rangexsd:int
Minimum Cardinality1
Maximum Cardinality1
Super-properties 
Sub-properties 

tmo:dependencyType

LabeldependencyType
Description
Domain 
Rangerdfs:Resource
Minimum Cardinality1
Maximum Cardinality1
Super-properties 
Sub-properties 

tmo:dueDate

LabeldueDate
Description
Domaintmo:Task
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiespimo:datatypeProperty, pimo:taskDueTime, tmo:dateTime
Sub-properties 

tmo:endTime

LabelendTime
Description
Domain 
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiestmo:dateTime
Sub-propertiestmo:actualEndTime, tmo:targetEndTime

tmo:importance

Labelimportance
Description
Domaintmo:Task
Rangetmo:Importance
Maximum Cardinality1
Super-propertiestmo:timemanagement
Sub-properties 

tmo:indexPosition

LabelindexPosition
Description
Domaintmo:Task
Rangerdfs:Literal
Maximum Cardinality1
Super-properties 
Sub-properties 

tmo:involvedPerson

LabelinvolvedPerson
Description
Domaintmo:PersonInvolvement
Rangepimo:Person
Minimum Cardinality1
Maximum Cardinality1
Super-propertiespimo:associationMember
Sub-properties 

tmo:involvedPersonRole

LabelinvolvedPersonRole
Description
Domaintmo:PersonInvolvement
Rangetmo:PersonInvolvementRole
Minimum Cardinality1
Maximum Cardinality1
Super-propertiestmo:stateTypeRole
Sub-properties 

tmo:involvedPersonTask

LabelinvolvedPersonTask
Description
Domaintmo:PersonInvolvement
Rangetmo:Task
Maximum Cardinality1
Super-propertiespimo:associationMember
Sub-properties 

tmo:involvedPersons

LabelinvolvedPersons
Description
Domaintmo:Task
Rangetmo:PersonInvolvement
Super-properties 
Sub-properties 

tmo:lastReviewDate

LabellastReviewDate
Description
Domaintmo:Task
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiestmo:dateTime
Sub-properties 

tmo:logEntry

LabellogEntry
Description
Domaintmo:Task
Rangerdfs:Resource
Super-properties 
Sub-properties 

tmo:nextReviewIntervall

LabelnextReviewIntervall
Description
Domaintmo:Task
Rangexsd:integer
Maximum Cardinality1
Super-properties 
Sub-properties 

tmo:priority

Labelpriority
Description
Domaintmo:Task
Rangetmo:Priority
Maximum Cardinality1
Super-propertiestmo:timemanagement
Sub-properties 

tmo:progress

Labelprogress
Description
Domain 
Rangerdfs:Literal
Maximum Cardinality1
Super-properties 
Sub-propertiestmo:targetCompletion, tmo:actualCompletion

tmo:receiveDateTime

LabelreceiveDateTime
Description
Domaintmo:TaskTransmission
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiestmo:dateTime
Sub-properties 

tmo:sendDateTime

LabelsendDateTime
Description
Domaintmo:TaskTransmission
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiestmo:dateTime
Sub-properties 

tmo:startTime

LabelstartTime
Description
Domain 
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiestmo:dateTime
Sub-propertiestmo:actualStartTime, tmo:targetStartTime

tmo:subTask

LabelsubTask
Description
Domaintmo:Task
Rangetmo:Task
Super-propertiespimo:objectProperty, pimo:hasPart
Sub-properties 

tmo:subTaskOrdering

LabelsubTaskOrdering
DescriptionOrdering of the subtasks listed in the tmo:subTasks property of this Task. This is only for ordering/sorting in GUIs, the semantic relation is defined in subTasks, and if this and subTasks differ, subTasks is the correct list.
Domaintmo:Task
Rangerdf:List
Maximum Cardinality1
Super-properties 
Sub-properties 

tmo:superTask

LabelsuperTask
Description
Domaintmo:Task
Rangetmo:Task
Maximum Cardinality1
Super-propertiespimo:objectProperty, tmo:taskReference, pimo:partOf
Sub-properties 

tmo:targetCompletion

LabeltargetCompletion
Description
Domaintmo:Task
Rangerdfs:Literal
Maximum Cardinality1
Super-propertiestmo:progress
Sub-properties 

tmo:targetEndTime

LabeltargetEndTime
Description
Domaintmo:Task
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiestmo:targetTime, tmo:endTime, tmo:dateTime
Sub-properties 

tmo:targetStartTime

LabeltargetStartTime
Description
Domaintmo:Task
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiestmo:targetTime, tmo:startTime, tmo:dateTime
Sub-properties 

tmo:targetTime

LabeltargetTime
Description
Domain 
Rangexsd:dateTime
Maximum Cardinality1
Super-propertiestmo:dateTime
Sub-propertiestmo:targetStartTime, tmo:targetEndTime

tmo:taskDescription

LabeltaskDescription
DescriptionThe task description helps users to understand the goal and the proceeding of a task. It can also describe the context of a task. The task description is composed at minimum of a summary of what is done to reach the goal. The task description is the main source for identifying related information, e.g., suitable patterns. A Task Description can be either an informal, described textual content (?TextualDescription) or it can be a more formally structured representation (āFormalDescription). Technology considerations: Informal descriptions allow for text similarity processing, a formal description allows for applying case based similarity measures.
Domaintmo:Task
Range 
Maximum Cardinality1
Super-propertiesnao:annotation, nao:description
Sub-properties 

tmo:taskGoal

LabeltaskGoal
Description
Domaintmo:Task
Rangerdfs:Resource
Super-properties 
Sub-properties 

tmo:taskId

LabeltaskId
DescriptionThe Task Identifier allows a unique identification of a task object within the range of all Nepomuk objects. The Task Identifier is automatically generated during the creation of a task. The generation of identifiers (IDs) is a Nepomuk architecture issue (Wp2000/WP6000).
Domaintmo:Task
Rangerdfs:Literal
Minimum Cardinality1
Maximum Cardinality1
Super-properties 
Sub-properties 

tmo:taskName

LabeltaskName
DescriptionThe Task Name helps the user to identify a task in a list. It should be expressive enough to give a meaningful recognition. Details should be written in the description attribute instead. A name attribute is not allowed to contain line breaks.
Domaintmo:Task
Rangerdfs:Literal
Maximum Cardinality1
Super-propertiesnao:prefLabel
Sub-properties 

tmo:taskPrivacyState

LabeltaskPrivacyState
DescriptionFor the separation between professional and private purpose of a task, this attribute provides with the values "professional/private" a high level separation of privacy in terms of setting distribution rights to other users for the task. This separation may arise as a general Nepomuk issue and may therefore be handled in conjunction with a privacy preserving SSD architecture.
Domaintmo:Task
Rangetmo:TaskPrivacyState
Maximum Cardinality1
Super-propertiestmo:stateTypeRole
Sub-properties 

tmo:taskReference

LabeltaskReference
Description
Domaintmo:Task
Rangetmo:Task
Maximum Cardinality1
Super-properties 
Sub-propertiestmo:superTask, tmo:dependencyMemberA, tmo:dependencyMemberB, tmo:transmissionTask, tmo:taskSource

tmo:taskSource

LabeltaskSource
Descriptionhere can be stated from which sources a task was derived. e.g from another task or from an task pattern
Domaintmo:Task
Rangerdfs:Resource
Maximum Cardinality1
Super-propertiestmo:taskReference
Sub-properties 

tmo:taskState

LabeltaskState
DescriptionThe task state describes the current state of the task as described in Section 5.2.7.
Domaintmo:Task
Rangetmo:TaskState
Minimum Cardinality1
Maximum Cardinality1
Super-propertiestmo:stateTypeRole
Sub-properties 

tmo:taskStateChangesFrom

LabeltaskStateChangesFrom
Description
Domaintmo:TaskState
Rangetmo:TaskState
Maximum Cardinality1
Super-propertiestmo:stateTypeRole
Sub-properties 

tmo:taskStateChangesTo

LabeltaskStateChangesTo
Description
Domaintmo:TaskState
Rangetmo:TaskState
Maximum Cardinality1
Super-propertiestmo:stateTypeRole
Sub-properties 

tmo:taskTransmission

LabeltaskTransmission
Description
Domaintmo:Task
Rangetmo:TaskTransmission
Super-properties 
Sub-properties 

tmo:timemanagement

Labeltimemanagement
Description
Domain 
Rangerdfs:Literal
Maximum Cardinality1
Super-properties 
Sub-propertiestmo:delegability, tmo:priority, tmo:importance, tmo:urgency

tmo:transmissionFrom

LabeltransmissionFrom
Description
Domaintmo:TaskTransmission
Rangepimo:Person
Minimum Cardinality1
Maximum Cardinality1
Super-properties 
Sub-properties 

tmo:transmissionState

LabeltransmissionState
Description
Domaintmo:TaskTransmission
Rangetmo:TransmissionState
Minimum Cardinality1
Maximum Cardinality1
Super-propertiestmo:stateTypeRole
Sub-properties 

tmo:transmissionStateChangesFrom

LabeltransmissionStateChangesFrom
Description
Domaintmo:TransmissionState
Rangetmo:TransmissionState
Maximum Cardinality1
Super-propertiestmo:stateTypeRole
Sub-properties 

tmo:transmissionStateChangesTo

LabeltransmissionStateChangesTo
Description
Domaintmo:TransmissionState
Rangetmo:TransmissionState
Maximum Cardinality1
Super-propertiestmo:stateTypeRole
Sub-properties 

tmo:transmissionTask

LabeltransmissionTask
Description
Domaintmo:TaskTransmission
Rangetmo:Task
Minimum Cardinality1
Maximum Cardinality1
Super-propertiestmo:taskReference
Sub-properties 

tmo:transmissionTo

LabeltransmissionTo
Description
Domaintmo:TaskTransmission
Rangepimo:Person
Minimum Cardinality1
Maximum Cardinality1
Super-properties 
Sub-properties 

tmo:transmissionType

LabeltransmissionType
Description
Domaintmo:TaskTransmission
Rangetmo:TransmissionType
Minimum Cardinality1
Maximum Cardinality1
Super-propertiestmo:stateTypeRole
Sub-properties 

tmo:urgency

Labelurgency
Description
Domaintmo:Task
Rangetmo:Urgency
Maximum Cardinality1
Super-propertiestmo:timemanagement
Sub-properties