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

Revisit the way temporal extents are modeled #97

Open
rybesh opened this issue Sep 3, 2021 · 0 comments
Open

Revisit the way temporal extents are modeled #97

rybesh opened this issue Sep 3, 2021 · 0 comments

Comments

@rybesh
Copy link
Member

rybesh commented Sep 3, 2021

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

  1. not affect the JSON representation of the dataset (since the @context would change accordingly), and
  2. be backward-compatible with earlier RDF versions of the dataset.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant