Submissions:TimeInterval
From Odp
| If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 9136 |
Graphical representation
Diagram
General description
| Name: | time interval |
|---|---|
| Submitted by: | ValentinaPresutti |
| Also Known As: | |
| Intent: | To represent time intervals. |
| Domains: | |
| Competency Questions: |
|
| Solution description: | -- |
| Reusable OWL Building Block: | http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl (1158) |
| Consequences: | The dates of the time interval are not part of the domain of discourse, they are datatype values. If there is the need of reasoning about dates this Content OP should be used in composition with the region Content OP. |
| Scenarios: | The time interval “January 2008” starts at 2008−01−01 and ends at and ends at 2008−01−31. |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
Elements
The TimeInterval Content OP locally defines the following ontology elements:
has interval date (owl:DatatypeProperty) A datatype property that encodes values from xsd:date for a time interval; a
same time interval can have more than one xsd:date value: begin date, end date, date at which the interval holds, as well as dates expressed in different formats: xsd:gYear, xsd:dateTime, etc.
hasIntervalDate page has interval start date (owl:DatatypeProperty) The start date of a time interval.
hasIntervalStartDate page has interval end date (owl:DatatypeProperty) The end date of a time interval.
hasIntervalEndDate pageAdditional information
This Content OP can be composed with other Content OPs when temporal aspects need to be represented.
Scenarios
No scenario is added to this Content OP.
Reviews
There is no review about this proposal. This revision (revision ID 9136) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
There is no Modeling issue related to this proposal.
References
