You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
Currently,
epo:Period
andepo: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
andepo:Duration
are used: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 howat-voc:timeperiod
can be represented using the OWL Time Ontology.Question:
at-voc:timeperiod
be mapped using the OWL Time Ontology?This mapping effort will also support ongoing work, such as Issue #40.
Proposed Output:
at-voc:timeperiod
to corresponding representations in the OWL Time Ontology.at-voc:timeperiod
so that its elements are alsotime:TemporalEntity
.Related Issues:
The text was updated successfully, but these errors were encountered: