OWL-Time alignment possibly incorrectly assumes prov:Activity a subclass of time:ProperInterval

[ajnelson-nist]

It appears that it is possible for prov:Activitys to be "Instantaneous" in some cases.

• Seeing PROV-CONSTRAINTS Constraint 30, the constraints on an activity's start and end instants are that the start "precedes" the end.
• PROV-CONSTRAINTS defines "precedes" between two instants as an instant whose time-value is less than or equal to another instant.
• "Strictly precedes" would be used for strictly-less-than.
  • Within PROV-CONSTRAINTS, only Constraint 42 appears to refer to strict instance precedence.

So, it is possible the correct alignment is:

prov:Activty rdfs:subClassOf time:Interval .

This might also have some nontrivial effects on relating prov:Start to prov:Generation, prov:Invalidation, etc.

[ajnelson-nist]

Further work on UCO's core:Event proposal and w3c/sdw Issue 1430 suggest this is, for now, the proper alignment to assume between TIME and PROV:

prov:Activity rdfs:subClassOf time:TemporalEntity .

UCO might benefit from defining time predicates uco-time:precedes and uco-time:follows as extensions over predicates available in OWL-Time.

[ajnelson-nist]

After further looking into w3c/sdw Issue 1430, I now think uco-time:precedes and uco-time:before (likewise follows/after) should be defined as a pair (quartet) of properties, alongside uco-time:equals. precedes would be a parent property of before and equals. before would implement strict-inequality. precedes permits equality.

While implementing various profiles along the way to UCO Issue 651, I no longer think statements in case-prov would be good to do directly between prov:Activity and time:TemporalEntity, as there are reasons to try treating them with is-a and has-a relationships. This project will avoid inducing commitments by the choice it makes.

case-prov will treat them as has-a via the InvestigationAction mapping:

case-investigation:InvestigativeAction
    rdfs:subClassOf
        prov:Activity ,
        [
            a owl:Restriction ;
            owl:onProperty time:hasTime ;
            owl:allValuesFrom time:Interval ;
        ]
        ;
    .