mathib / cto-ontology Goto Github PK

an owl:DatatypeProperty representing the due date for a task should be added (if such metadata is to be modelled in the dataset instead as "context" defined at dataset level)

modeling of supertask for smaller task is possible using cto:hasTaskContext since both classes cto:Task and cto:TaskContext are not disjoint

• add additional human description to property
• add schema:rangeIncludes cto:Task to property

it should be possible to indicate, in the planning phase, the craft (type of contractor) that is related to the individual task.

This can happen by defining types of contractors as:

• SKOS "individuals" (with possible interrelations)
• OWL classes

connected using respectively a

• owl:ObjectProperty cto:relatedCraft
• owl:AnnotationProperty cto:relatedCraft >> owl:ObjectProperty with OWL punning

an owl:ObjectProperty can be added for task status such as "done", "inProcess", "planned", etc. (if such metadata is to be modelled in the dataset instead as "context" defined at dataset level)