Bug description

The property observable:creationTime is used in the class observable:WindowsThreadFacet. This property has no relevant documentation rdfs:comment string.

Everywhere else a creation timestamp is mentioned, the property is observable:observableCreatedTime. This has been the case since UCO 0.6.0, when observable:createdTime was disambiguated from core:createdTime.

Should the property in use be deprecated and replaced with observable:observableCreatedTime? On assumption the answer is yes, this Issue proposes deprecating and removing the property.

Requirements

Requirement 1

UCO should consolidate creation time properties that do not distinguish in purpose between one another.

Risk / Benefit analysis

Benefits

Removes ambiguity for UCO producers and consumers in how to represent observable creation times.

Risks

observable:creationTime would be deprecated, and removed in UCO 2.0.0. UCO has not yet, at the time of this writing, deprecated a property, though a plan has been laid out to do so in Issue 493.

Competencies demonstrated

Competency 1

A user wishes to transcribe a creation timestamp from some observable object in their data model.

Competency Question 1.1

What is the creation timestamp to use within the observable namespace?

Result 1.1

The general observable:observableCreatedTime, defined in UCO 0.6.0.

Solution suggestion

Assign observable:creationTime the additional type owl:DeprecatedProperty.
Add a shape to warn against the property's usage, from UCO 1.2.0 to UCO 2.0.0:

observable:creationTime-deprecation-shape
    a sh:NodeShape ;
    sh:property [
        a sh:PropertyShape ;
        sh:maxCount 0 ;
        sh:message "observable:creationTime is deprecated, and will be an error to use in UCO 2.0.0.  observable:observableCreatedTime should be used instead."@en ;
        sh:severity sh:Warning ;
        sh:path observable:creationTime ;
    ] ;
    sh:targetSubjectsOf observable:creationTime ;
    .

Remove the sh:severity sh:Warning statement in UCO 2.0.0.
Add a shape duplicating the current observable:creationTime PropertyShape on observable:WindowsThreadFacet, except substituting observable:observableCreatedTime.
Retain the observable:creationTime PropertyShape on observable:WindowsThreadFacet, as-is, for now. Delete in 2.0.0.

Coordination

Tracking in Jira ticket OC-284
[x] Administrative review completed, proposal announced to Ontology Committees (OCs) on 2022-11-29
[x] Requirements to be discussed in OC meeting, 2022-12-08
[x] Requirements Review vote occurred, passing, on 2022-02-08
[x] Requirements development phase completed.
[x] Solution announced to OCs on 2023-01-17
[x] Solutions Approval to be discussed in OC meeting, 2023-01-26
[x] Solutions Approval vote occurred, passing, on 2023-01-26
[x] Solutions development phase completed.
[x] Backwards-compatible implementation merged into develop for the next release
[x] develop state with backwards-compatible implementation merged into develop-2.0.0
[x] Backwards-incompatible implementation merged into develop-2.0.0
[x] Milestone linked
[x] Documentation logged in pending release pages

ucoProject / UCO

observable:creationTime is ambiguous, possibly redundant, with observable:observableCreatedTime #508