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

Mapping of at-voc:timeperiod to the OWL Time Ontology #681

Open
cristianvasquez opened this issue Aug 14, 2024 · 0 comments
Open

Mapping of at-voc:timeperiod to the OWL Time Ontology #681

cristianvasquez opened this issue Aug 14, 2024 · 0 comments
Milestone

Comments

@cristianvasquez
Copy link
Contributor

Currently, epo:Period and epo:Duration are described using different constructs. Specifically, epo:Period utilizes at-voc:timeperiod, which has a predefined set of values.

Below is a diagram illustrating how epo:Period and epo:Duration are used:

Diagram

As mentioned in Issue #529, the OWL Time Ontology was proposed to describe epo:Period, aligning how time will be represented within the eProcurement Ontology (ePO). To support the analysis and the RDF materialization, we need to explore how at-voc:timeperiod can be represented using the OWL Time Ontology.

Question:

  • Can all elements of at-voc:timeperiod be mapped using the OWL Time Ontology?

This mapping effort will also support ongoing work, such as Issue #40.

Proposed Output:

  • A table mapping at-voc:timeperiod to corresponding representations in the OWL Time Ontology.
  • Alternatively, an extension of at-voc:timeperiod so that its elements are also time:TemporalEntity.

Related Issues:

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

2 participants