-
Key: COMMONS11-3
-
Status: closed
-
Source: Thematix Partners LLC ( Mrs. Elisa F. Kendall)
-
Summary:
Currently we have an explicit date period, but not explicit time period, which is needed for PPMN, among other processes. This is also required for Robotics.
-
Reported: COMMONS 1.0b2 — Fri, 14 Jul 2023 18:05 GMT
-
Disposition: Resolved — $issue.fixedSpecification.name
-
Disposition Summary:
Added a number of properties to the Dates and Times ontology related to start and end time
The resolution to this issue adds two classes to the ontology: TimePeriod and ExplicitTimePeriod, and a number of properties, including a general purpose hasTime property as well as hasDateOfIssuance, hasEnd, hasEndTime, hasStart, hasStartTime, and hasTimePeriod, per request of two task forces, Robotics Service Ontology (RoSO) and Pedigree and Provenance Metamodel and Notation (PPMN).
Note: in the text revisions, under item 5, there are no sections labeled i and n because solitaire turned them into odd emojis.
-
Updated: Wed, 20 Dec 2023 15:27 GMT
-
Attachments:
- DatesAndTimes.mdzip 311 kB ()
- DatesAndTimes.rdf 30 kB (application/rdf+xml)
- DatesAndTimesClassHierarchy.png 27 kB (image/png)
- DatesAndTimesClassHierarchy.svg 628 kB (image/svg+xml)
COMMONS11 — Need to add start and end time and explicit time period in Commons
- Key: COMMONS11-3
- OMG Task Force: Commons Ontology Library (Commons) 1.1 RTF