(No) integration of CCO Time Ontology

[carstenhoyerklick]

Description of the issue

I have looked at the Time Ontology Module of CCO. I creates a number of new classes at ...>occurent>temporal region > onedimensional region.

These are different intervals as Multy-Day, Multi.Hour, Multi-Minute, Mulit Month, Multi-Second, Multi-Week, Multi year.

It also creates ...>temporal region > one-dimensional region > temporal interval a number of new classes as Afternoon, Axial Rotation Period, Day, Calendar Day, Greogrian Day, Julian Day, Decade, Evening, Hour, Minute, Month, Calendar Month, Morning, Night, Second, Week, Calendar Week, Year, Calendar Year

It further created at
zero-dimensional region > temporal instant a number of classes
Reference Time, Time of Day, Julian Date, Modified Julian Date, Unix temporal instant.

As far as I would see we need none of these for the annotation of our data.

Also the object properties define a number of term which can be used to describe causality, things that happen before and after. These may be useful to describe a flow diagram of processes, which is I think also not our use case.

For my impression we do not need to import the TimeOntology Module, unless we find a use case for it.

Ideas of solution

Do not import the TimeOntology from the CCO.

Workflow checklist

• I am aware of the workflow in CONTRIBUTING.md

[delzar]

I think all of us need the unix timestamp to stamp experiment data, do we need the CCO time ontology for that or is that solved in some other way.
We at MS also need process flow diagrams for process (modeling workflows of many tasks, some of them are just sequential, some are loops and so on).