TMO_Instance_PersonInvolvementRole_Creator
type: PersonInvolvementRole

abilityCarrierRole
type: Property
domain: AbilityCarrierInvolvement
range: AbilityCarrierRole
sub property of: stateTypeRole
max cardinality: 1
min cardinality: 1

AbilityCarrierInvolvement
type: Class
comment: The class AbilityCarrier_Involvement ties together an AbilityCarrier with an AbilityCarrier_Role. This is a role based modelling approach. An n-ary relation is realized.
subclass of: Resource
subclass of: Association

AbilityCarrierRole
type: Class
comment: Examples instances of AbilityCarrirRoles are e.g. "requested", "required" and "used" which further specify the type a person was involved in.
subclass of: StateTypeRole

stateTypeRole
type: Property
range: Resource
max cardinality: 1

PersonInvolvement
type: Class
comment: PersonInvolvement realizes n-ary associations to Persons which are realtedd to an task. The involvement is further characterized by an PersonTaskRole.
subclass of: Resource
subclass of: Association

TMO_Instance_TaskState_Running
type: TaskState

SimilarityDependence
type: Class
subclass of: UndirectedDependency

UndirectedDependency
type: Class
comment: A symmetric relations between task.
subclass of: TaskDependency

PredecessorDependency
type: Class
comment: In a PredecessorDependency the dependencyMemberA is the task which is to be executed before dependencyMemberB.
subclass of: PredecessorSuccessorDependency

PredecessorSuccessorDependency
type: Class
comment: The 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.
subclass of: TaskDependency
role: abstract

TMO_Instance_TaskContainer_outbox
type: TaskContainer

dueDate
type: Property
domain: Task
range: dateTime
sub property of: taskDueTime
sub property of: dateTime
max cardinality: 1

Task
type: Class
comment: The tmo:task is the central entitiey of the tmo. Task can range from vague things to be possibly done in e distant future to concrete things to be done in a precise forseeable manner. It is not unrealisitc to assume that knowledge worker have hundred or more tasks a day.
subclass of: Task

dateTime
type: Property
comment: dateTime subsumes various properties with Range XMLSchema:dateTime. If possible they are further grouped by "abstract" properties.
range: dateTime
max cardinality: 1

TMO_Instance_Urgency_04
type: Urgency

actualCompletion
type: Property
domain: Task
range: Literal
sub property of: progress
max cardinality: 1

progress
type: Property
range: Literal
max cardinality: 1

TMO_Instance_PersonInvolvementRole_Co-worker
type: PersonInvolvementRole

urgency
type: Property
domain: Task
range: Urgency
sub property of: timemanagement
max cardinality: 1

Urgency
type: Class
subclass of: StateTypeRole

timemanagement
type: Property
range: Literal
max cardinality: 1

TMO_Instance_TaskContainer_archive
type: TaskContainer

dependency
type: Property
domain: Task
range: TaskDependency

TaskDependency
type: Class
comment: Between 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.
subclass of: Resource
subclass of: Association
role: abstract

TMO_Instance_Importance_10
type: Importance

targetStartTime
type: Property
domain: Task
range: dateTime
sub property of: targetTime
sub property of: startTime
max cardinality: 1

targetTime
type: Property
range: dateTime
sub property of: dateTime
max cardinality: 1

startTime
type: Property
range: dateTime
sub property of: dateTime
max cardinality: 1

dependencyDescription
type: Property
comment: Endusers can clarify why they created a depedency.
domain: TaskDependency
sub property of: description
max cardinality: 1

TMO_Instance_Importance_09
type: Importance

transmissionState
type: Property
domain: TaskTransmission
range: TransmissionState
sub property of: stateTypeRole
max cardinality: 1
min cardinality: 1

TaskTransmission
type: Class
comment: On 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.
subclass of: Resource

TransmissionState
type: Class
comment: States a task can go through during transmission of an task.
subclass of: StateTypeRole

TMO_Instance_TaskState_Finalized
type: TaskState

abilityCarrier
type: Property
domain: AbilityCarrierInvolvement
range: AbilityCarrier
sub property of: associationMember
max cardinality: 1
min cardinality: 1

AbilityCarrier
type: Class
comment: AbilityCarrier 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.
subclass of: Resource
role: abstract

TMO_Instance_TransmissionState_Rejected_Transmitted
type: TransmissionState

TMO_Instance_Delegability_High
type: Delegability

TMO_Instance_Urgency_10
type: Urgency

taskId
type: Property
comment: The 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).
domain: Task
range: Literal
max cardinality: 1
min cardinality: 1

TMO_Instance_Importance_01
type: Importance

TMO_Instance_TransmissionType_Transfer
type: TransmissionType

priority
type: Property
domain: Task
range: Priority
sub property of: timemanagement
max cardinality: 1

Priority
type: Class
subclass of: StateTypeRole

StateTypeRole
type: Class
comment: StateTypeRole is an abstract class which subsumes various other classes which represent "states" or roles e.g. in role based modelling conpetualisations.
subclass of: Resource

TMO_Instance_Urgency_03
type: Urgency

involvedPersons
type: Property
domain: Task
range: PersonInvolvement
inverse property: involvedPersonTask

involvedPersonTask
type: Property
domain: PersonInvolvement
range: Task
sub property of: associationMember
inverse property: involvedPersons
max cardinality: 1

involvedPerson
type: Property
domain: PersonInvolvement
range: Person
sub property of: associationMember
max cardinality: 1
min cardinality: 1

containsTask
type: Property
domain: TaskContainer
range: Task
sub property of: hasPart

TaskContainer
type: Class
subclass of: Collection

TMO_Instance_PersonInvolvementRole_Suggested
type: PersonInvolvementRole

TMO_Instance_TaskState_Archived
type: TaskState

indexPosition
type: Property
domain: Task
range: Literal
max cardinality: 1

dependencyType
type: Property
range: Resource
max cardinality: 1
min cardinality: 1

targetEndTime
type: Property
domain: Task
range: dateTime
sub property of: targetTime
sub property of: endTime
max cardinality: 1

endTime
type: Property
range: dateTime
sub property of: dateTime
max cardinality: 1

TMO_Instance_Importance_08
type: Importance

attachmentReference
type: Property
domain: Attachment
range: Resource
sub property of: associationMember
max cardinality: 1
min cardinality: 1

Attachment
type: Class
comment: By 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.
subclass of: Resource
subclass of: Association

TMO_Instance_Delegability_Never
type: Delegability

superTask
type: Property
domain: Task
range: Task
sub property of: partOf
sub property of: taskReference
inverse property: subTask
max cardinality: 1

taskReference
type: Property
domain: Task
range: Task
max cardinality: 1

subTask
type: Property
domain: Task
range: Task
sub property of: hasPart
inverse property: superTask

taskDescription
type: Property
comment: The 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.
domain: Task
sub property of: description
max cardinality: 1

SuperSubTaskDependency
type: Class
comment: By 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.
subclass of: TaskDependency

contextTask
type: Property
range: Task
inverse property: contextThread
max cardinality: 1

contextThread
type: Property
domain: Task
range: MediumTermContextThread
inverse property: contextTask
max cardinality: 1

SuccessorDependency
type: Class
comment: In a SuccessorrDependency the dependencyMemberA is the task which is to be executed after dependencyMemberB.
subclass of: PredecessorSuccessorDependency

TMO_Instance_TransmissionState_NotTransmitted
type: TransmissionState

TMO_Instance_Urgency_06
type: Urgency

abilityCarrierInvolvement
type: Property
domain: Task
range: AbilityCarrierInvolvement
inverse property: abilityCarrierTask

abilityCarrierTask
type: Property
domain: AbilityCarrierInvolvement
range: Task
sub property of: associationMember
inverse property: abilityCarrierInvolvement
max cardinality: 1

TMO_Instance_AbilityCarrierRole_Required
type: AbilityCarrierRole

actualStartTime
type: Property
domain: Task
range: dateTime
sub property of: actualTime
sub property of: startTime
max cardinality: 1

actualTime
type: Property
range: dateTime
sub property of: dateTime
max cardinality: 1

transmissionType
type: Property
domain: TaskTransmission
range: TransmissionType
sub property of: stateTypeRole
max cardinality: 1
min cardinality: 1

TransmissionType
type: Class
comment: By 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.
subclass of: StateTypeRole

taskTransmission
type: Property
domain: Task
range: TaskTransmission
inverse property: transmissionTask

transmissionTask
type: Property
domain: TaskTransmission
range: Task
sub property of: taskReference
inverse property: taskTransmission
max cardinality: 1
min cardinality: 1

TMO_Instance_PersonInvolvementRole_Executor
type: PersonInvolvementRole

targetCompletion
type: Property
domain: Task
range: Literal
sub property of: progress
max cardinality: 1

TMO_Instance_Delegability_Medium
type: Delegability

AgentAbilityCarrier
type: Class
subclass of: AbilityCarrier
role: abstract

TMO_Instance_TaskPrivacy_Private
type: TaskPrivacyState

TMO_Instance_Importance_07
type: Importance

AssociationDependency
type: Class
subclass of: UndirectedDependency

nextReviewIntervall
type: Property
domain: Task
range: integer
max cardinality: 1

transmissionFrom
type: Property
domain: TaskTransmission
range: Person
max cardinality: 1
min cardinality: 1

taskState
type: Property
comment: The task state describes the current state of the task as described in Section 5.2.7.
domain: Task
range: TaskState
sub property of: stateTypeRole
max cardinality: 1
min cardinality: 1

TaskState
type: Class
comment: The 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.
subclass of: StateTypeRole

delegability
type: Property
domain: Task
range: Delegability
sub property of: timemanagement
max cardinality: 1

Delegability
type: Class
subclass of: StateTypeRole

TMO_Instance_PersonInvolvementRole_Related
type: PersonInvolvementRole

TMO_Instance_TaskContainer_inbox
type: TaskContainer

TMO_Instance_AttachmentRole_Required
type: AttachmentRole

taskPrivacyState
type: Property
comment: For 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.
domain: Task
range: TaskPrivacyState
sub property of: stateTypeRole
max cardinality: 1

TaskPrivacyState
type: Class
comment: Privacy 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.
subclass of: StateTypeRole

taskName
type: Property
comment: The 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.
domain: Task
range: Literal
sub property of: prefLabel
max cardinality: 1

TMO_Instance_AbilityCarrierRole_Requested
type: AbilityCarrierRole

TMO_Instance_PersonInvolvementRole_Controller
type: PersonInvolvementRole

TMO_Instance_PersonInvolvementRole_Delegate
type: PersonInvolvementRole

transmissionStateChangesFrom
type: Property
domain: TransmissionState
range: TransmissionState
sub property of: stateTypeRole
max cardinality: 1

transmissionStateChangesTo
type: Property
domain: TransmissionState
range: TransmissionState
sub property of: stateTypeRole
max cardinality: 1

TMO_Instance_PersonInvolvementRole_ExternalObserver
type: PersonInvolvementRole

TMO_Instance_Urgency_05
type: Urgency

TMO_Instance_TaskState_Completed
type: TaskState

TMO_Instance_Importance_06
type: Importance

attachmentRole
type: Property
domain: Attachment
range: AttachmentRole
sub property of: stateTypeRole
max cardinality: 1

AttachmentRole
type: Class
comment: AttachmentRoles further specify the type of how an attachment relates to a task. Example instances of AttachmentRoles are e.g. "desired_request", "required" and "used".
subclass of: StateTypeRole

TMO_Instance_TaskPrivacy_Professional
type: TaskPrivacyState

TMO_Instance_TaskState_Terminated
type: TaskState

TMO_Instance_PersonInvolvementRole_Owner
type: PersonInvolvementRole

TMO_Instance_AttachmentRole_Desired_Requested
type: AttachmentRole

TMO_Instance_TransmissionState_Accepted_NotTransmitted
type: TransmissionState

TMO_Instance_PersonInvolvementRole_Analyst
type: PersonInvolvementRole

logEntry
type: Property
domain: Task
range: Resource

transmissionTo
type: Property
domain: TaskTransmission
range: Person
max cardinality: 1
min cardinality: 1

TMO_Instance_TransmissionType_Join
type: TransmissionType

lastReviewDate
type: Property
domain: Task
range: dateTime
sub property of: dateTime
max cardinality: 1

Role
type: Class
comment: examples: Architect, Developer, ...
subclass of: AbilityCarrier

taskGoal
type: Property
domain: Task
range: Resource

dependencyMemberA
type: Property
comment: The 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)
domain: TaskDependency
range: Task
sub property of: taskReference
sub property of: associationMember
max cardinality: 1
min cardinality: 1

TMO_Instance_Urgency_08
type: Urgency

taskStateChangesFrom
type: Property
domain: TaskState
range: TaskState
sub property of: stateTypeRole
max cardinality: 1

receiveDateTime
type: Property
domain: TaskTransmission
range: dateTime
sub property of: dateTime
max cardinality: 1

createdBy
type: Property
domain: Attachment
range: Person
max cardinality: 1

TMO_Instance_AbilityCarrierRole_Used
type: AbilityCarrierRole

TMO_Instance_Importance_05
type: Importance

TMO_Instance_TaskContainer_activetasks
type: TaskContainer

sendDateTime
type: Property
domain: TaskTransmission
range: dateTime
sub property of: dateTime
max cardinality: 1

TMO_Instance_PersonInvolvementRole_Collaborator
type: PersonInvolvementRole

TMO_Instance_TaskState_Suspended
type: TaskState

dependencyMemberB
type: Property
comment: The 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)
domain: TaskDependency
range: Task
sub property of: taskReference
sub property of: associationMember
max cardinality: 1
min cardinality: 1

TMO_Instance_Priority_High
type: Priority

TMO_Instance_PersonInvolvementRole_Observer
type: PersonInvolvementRole

TMO_Instance_Delegability_Unrestricted
type: Delegability

TMO_Instance_Priority_Medium
type: Priority

TMO_Instance_Delegability_Low
type: Delegability

Interdependence
type: Class
subclass of: UndirectedDependency

involvedPersonRole
type: Property
domain: PersonInvolvement
range: PersonInvolvementRole
sub property of: stateTypeRole
max cardinality: 1
min cardinality: 1

PersonInvolvementRole
type: Class
comment: They further specify the type a person was related to an task. Examples instances of AttachmentRoles are e.g.
subclass of: StateTypeRole

TMO_Instance_Urgency_07
type: Urgency

TMO_Instance_PersonInvolvementRole_Reviewer
type: PersonInvolvementRole

actualEndTime
type: Property
domain: Task
range: dateTime
sub property of: endTime
sub property of: actualTime
max cardinality: 1

TMO_Instance_TransmissionType_Delegation
type: TransmissionType

TMO_Instance_Importance_04
type: Importance

taskSource
type: Property
comment: here can be stated from which sources a task was derived. e.g from another task or from an task pattern
domain: Task
range: Resource
sub property of: taskReference
max cardinality: 1

TMO_Instance_Urgency_02
type: Urgency

TMO_Instance_TransmissionState_Accepted_Transmitted
type: TransmissionState

TMO_Instance_TaskState_New
type: TaskState

TMO_Instance_TaskContainer_trashtasks
type: TaskContainer

TMO_Instance_AttachmentRole_Used
type: AttachmentRole

TMO_Instance_TransmissionState_Rejected_NotTransmitted
type: TransmissionState

TMO_Instance_Priority_Low
type: Priority

TMO_Instance_TransmissionState_Transmitted
type: TransmissionState

TMO_Instance_Importance_03
type: Importance

TMO_Instance_AttachmentRole_Related
type: AttachmentRole

TMO_Instance_PersonInvolvementRole_Involved
type: PersonInvolvementRole

importance
type: Property
domain: Task
range: Importance
sub property of: timemanagement
max cardinality: 1

Importance
type: Class
subclass of: StateTypeRole

subTaskOrdering
type: Property
comment: Ordering 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.
domain: Task
range: List
max cardinality: 1

TMO_Instance_Urgency_01
type: Urgency

dependencyOrderNumber
type: Property
domain: TaskDependency
range: int
max cardinality: 1
min cardinality: 1

TMO_Instance_PersonInvolvementRole_Initiator
type: PersonInvolvementRole

attachment
type: Property
comment: connects a Task with an Attachment object. Attachments are associations of Things.
domain: Task
range: Attachment
inverse property: attachmentTask

attachmentTask
type: Property
comment: Inverse of attachment, connects an Attachment Association to the associated Task. Is required for every instance of Attachment.
domain: Attachment
range: Task
sub property of: associationMember
inverse property: attachment
max cardinality: 1

TMO_Instance_PersonInvolvementRole_Receiver
type: PersonInvolvementRole

TMO_Instance_TaskState_Deleted
type: TaskState

taskStateChangesTo
type: Property
domain: TaskState
range: TaskState
sub property of: stateTypeRole
max cardinality: 1

TMO_Instance_Urgency_09
type: Urgency

TMO_Instance_Importance_02
type: Importance

TMO_Instance_PersonInvolvementRole_InternalObserver
type: PersonInvolvementRole

Skill
type: Class
comment: examples are e.g. technologies like Java, XML, ...
subclass of: AbilityCarrier