There are terms missing to describe important dates of project lifetimes
Description of the issue
We are missing terms to describe things like decomissioning date, commissioning date, construction start, construction end, decomissioning start, decomissioning end ... etc.
Ideas of solution
I suspect all of these could be subclasses of zero-dimensional temporal region, my experience is that these concepts are often not easy to define so we may be discussing these for a while.
Workflow checklist
- [ ] I discussed the issue with someone else than me before working on a solution
- [ ] I already read the latest version of the workflow for this repository
- [ ] The goal of this ontology is clear to me
I am aware that
- [ ] every entry in the ontology should have a definition
- [ ] classes should arise from concepts rather than from words
I went quickly through other ontologies without success. I was expecting these definitions to appear in some construction project ontology but was not the case. There is this data property: commissioningDate in the dbpedia ontology
We already have:
-
construction time: A construction time is a time span that measures the time that is needed to construct an artificial object. -
decommissioning time: A decommissioning time is a time span that measures the time that is needed to decommission an artificial object. -
ending time: An ending time is a zero-dimensional temporal region that indicates the end of a one-dimensional temporal region. -
start time: A start time is a zero-dimensional temporal region that indicates the beginning of a one-dimensional temporal region.
So what about:
-
commissioning start: A commissioning start is a start time that indicates the beginning of a commissioning time. -
commissioning end: A commissioning end is an end time that indicates the beginning of a commissioning time. -
decommissioning start: A decommissioning start is a start time that indicates the beginning of a decommissioning time. -
decommissioning end: A decommissioning end is an end time that indicates the beginning of a decommissioning time.
The terms commissioning date and decommissioning date are a bit more tricky. I would assume that commissioning date is the same as commissioning end and decommissioning date the same as decommissioning start.
I think this is related, how do we deal with associating a status to the units based on their lifetime status?
From SEDOS meeting 09.05.2023:
Missing vocabulary for definitions of portafolio status (pre-construction, approved, planned, announced)
Missing vocabulary for definitions of portafolio status (pre-construction, approved, planned, announced)
This might be a bit tricky as these are states of objects which not even exist.
Any feedback on my proposals above?
We already have:
construction time: A construction time is a time span that measures the time that is needed to construct an artificial object.decommissioning time: A decommissioning time is a time span that measures the time that is needed to decommission an artificial object.ending time: An ending time is a zero-dimensional temporal region that indicates the end of a one-dimensional temporal region.start time: A start time is a zero-dimensional temporal region that indicates the beginning of a one-dimensional temporal region.So what about:
commissioning start: A commissioning start is a start time that indicates the beginning of a commissioning time.commissioning end: A commissioning end is an end time that indicates the beginning of a commissioning time.decommissioning start: A decommissioning start is a start time that indicates the beginning of a decommissioning time.decommissioning end: A decommissioning end is an end time that indicates the beginning of a decommissioning time.The terms
commissioning dateanddecommissioning dateare a bit more tricky. I would assume thatcommissioning dateis the same ascommissioning endanddecommissioning datethe same asdecommissioning start.
I think these are good, can end/start have a timestamp as data property?
I think these are good, can end/start have a timestamp as data property?
Currently, time stamp only mentions and is axiomated by time step . But from my perspective, it should also be relatable to 0-dim-temporal regions like start/ending time.
EDIT: I think it is also rather an information content entity instead of 0-dim-temporal region.
This issue is open for almost a year, although good proposals were made.
We should further make time stamp a subclass of data descriptor and add is about some 0-dim-temporal region.
Any objections against implementation?
If time stamp would be a subclass of data descriptor, then a quantity value could have a time stamp as property, similar to aggregation type or unit? If this is correct, I would appreciate this implementation. In combination with time span and time stamp alignment I could create a time stamped measurement datum with a time and a value.
Yes, that would be possible.