We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It appears that it is possible for prov:Activitys to be "Instantaneous" in some cases.
prov:Activity
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.
prov:Start
prov:Generation
prov:Invalidation
The text was updated successfully, but these errors were encountered:
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:
core:Event
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.
uco-time:precedes
uco-time:follows
Sorry, something went wrong.
No branches or pull requests
It appears that it is possible for
prov:Activity
s to be "Instantaneous" in some cases.So, it is possible the correct alignment is:
This might also have some nontrivial effects on relating
prov:Start
toprov:Generation
,prov:Invalidation
, etc.The text was updated successfully, but these errors were encountered: