[Nepomuk] relationship between pimo:project and pimo:task

[Christian Mollekopf]

On Sunday, August 21, 2011 07:53:37 AM swair shah wrote:
> Hi,
>
Hey swair,
 
> Does having Pimo:Tasks as optional subsets of Pimo:project make sense? This
> is is reference to a 'project management tool'.
> Treating Tasks in a similar way websites, persons, files and notes with
> respect to a Pimo:Project does not make sense.
>
Why doesn't that make sense?
The only difference I can see is that the pimo:partOf relation seems a little 
stronger than the pimo:isRelated relation.
I think it depends on each case which one is more correct, so either option 
seems valid.

Currently I'm using pimo:isRelated in MindMirror to relate the tasks to either 
Topics or Projects ,but that could be changed. The only requirement is that I 
can relate a Task with multiple Projects/Topics at the same time, but that 
seems to work for both properties too.

So for consistency's sake I would just use the same property as used to relate 
files, notes, etc.

> This is what i propose: To have a pimo:project has:part pimo:Tasks, instead
> of isRelatedTo. Make a pimoProjectModel, which has projects as nodes and
> tasks as children. With Tasks having TMO:States but keeping the states
> limited to just 3 for better usability: states, Completed, Running, Not
> Completed (New).
> 

I'd suggest using 4:
tmo:TMO_Instance_TaskState_New : New Items, not yet specified
tmo:TMO_Instance_TaskState_Running : Something you're working on right now.
tmo:TMO_Instance_TaskState_Suspended : Something you want to keep for later
tmo:TMO_Instance_TaskState_Completed : Completed tasks/Aborted tasks

> Of course a project can exist without having no task as a part of it. And
> task can exist without being a part of a project and These tasks won't be
> handled by project manager.
> 
> When a task is chosen as a working context, if it is pimo:partOf a project
> then that project is also a working context, meaning, 'things' which are
> related to the task also get associated with the project. I don't really see
> a use case for the last one, but having task as a part of a project would
> certainly help.

Cheers,

Christian

> 
> thanks,
> swair.