Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
ajnelson-nist opened this issue Jun 26, 2023 · 1 comment

Comments

@ajnelson-nist
Copy link
Member

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
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant