Time Interval Pattern¶
Source: ODP portal · Published by: ontologydesignpatterns.org · Category: structural · Domain: temporal
Represents a time interval with a start and end point. Used for temporal modeling.
What it answers¶
- When does this interval start? When does this interval end?
The pattern¶
The graph is the axioms the pattern asserts; nothing here is inferred. Drag to rearrange, scroll to zoom, and use the graph's own search box to find a term inside it.
Opens at level of detail 3: classes, individuals, properties and restrictions, without the literals. Raise it with the LOD control in the graph's own toolbar to see annotation values and anything a reasoner adds.
Should you use this one?¶
| Size | 1 classes, 2 properties, 8 axioms |
| Brings in | nothing - it stands on its own |
| Reasoning | HermiT finds this pattern consistent, with no unsatisfiable class, and its worked example consistent with the pattern. |
A situation it was written for. A project runs from January to June. A lecture is scheduled from 10:00 to 11:30.
Check it yourself: the published pattern · an archived copy · its reference · the ontology itself.
If a link does not open
ontologydesignpatterns.org, which publishes most of this library, does
not currently answer over HTTPS, and its wiki redirects submission pages
to its front page. The archived copy is there for exactly that reason.
The ontology files themselves are still served over plain HTTP.
Terms it declares¶
The 3 classes and properties this pattern models, as the recommender scores them. Annotation properties and built-ins are excluded, because an annotation property is not modelling.
http://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#TimeIntervalhttp://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#hasIntervalEndDatehttp://www.ontologydesignpatterns.org/cp/owl/timeinterval.owl#hasIntervalStartDate
An example of it in use¶
The pattern says what may be asserted; this says it. The graph below is a small set of individuals that instantiate the classes above and are connected by its properties, so the shape the pattern describes is visible as data rather than as a schema.
Import this pattern into your own ontology from inside Protégé: OntoBoard → Reuse → Pattern library…, which hands it to Import terms… and writes the term list, the module, the import and the catalog entry the way ODK expects. See Working with ODK.
Something wrong with this pattern, its example or this page? Report a problem with this pattern - the form opens with the pattern filled in, and a title and a sentence are all it needs.