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
The revision of OWL Time subtly changed the semantics of how we model temporal extents.
We also rely on some custom data properties that make it difficult to apply temporal reasoning rules designed for use with OWL Time.
It would also be worthwhile to make it clear how PeriodO temporal extents relate to the fuzzy-bounded E2 Temporal Entity of the CIDOC CRM.
Finally, it might be nice to be able to express PeriodO temporal extents using EDTF via the EDTF Ontology.
For all these reasons we need to revisit the way temporal extents are modeled in PeriodO. Ideally any changes would
@context
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The revision of OWL Time subtly changed the semantics of how we model temporal extents.
We also rely on some custom data properties that make it difficult to apply temporal reasoning rules designed for use with OWL Time.
It would also be worthwhile to make it clear how PeriodO temporal extents relate to the fuzzy-bounded E2 Temporal Entity of the CIDOC CRM.
Finally, it might be nice to be able to express PeriodO temporal extents using EDTF via the EDTF Ontology.
For all these reasons we need to revisit the way temporal extents are modeled in PeriodO. Ideally any changes would
@context
would change accordingly), andThe text was updated successfully, but these errors were encountered: