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

[swair shah]

Hi,

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.

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).

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.

thanks,
swair.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20110821/983e4ef4/attachment.html>