|
Last modified date is: 2019-06-27 |
Diagram (this article has no graphical representation)
| Name: | RecurrentEventSeries |
|---|---|
| Submitted by: | ValentinaAnitaCarriero |
| Also Known As: | |
| Intent: | To represent recurrent event series as situations and collections of consecutive events, with a regular time period between events and unifying factors. |
| Domains: | |
| Competency Questions: |
|
| Solution description: | A recurrent event series is modelled as an intersection of a collection and a situation. Indeed, a recurrent event is seen as a collection, since it contains entities that share one or more common properties and are unified conceptually (unifying factors). These entities are member of the collection, and are all consecutive events. At the same time, a recurrent event is a situation, intended as a relational context in which the contextualised things are based on a frame: a recurrent event is similar to a plan that defines how the things involved in that plan (i.e. the specific events) shall be carried out, e.g. where the events shall be located, in which time of the year, etc. |
| Reusable OWL Building Block: | 1 (146) |
| Consequences: | A series of recurrent events, its unifying factors and the recurrent time period can be modelled. |
| Scenarios: | Umbria Jazz is a collection of events, which all take place in July and in the Italian region of Umbria, and has the musical genre jazz as a topic. Its events recur at regular time periods, i.e. annually. |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The RecurrentEventSeries Content OP locally defines the following ontology elements:
No scenario is added to this Content OP.
This revision (revision ID 13657) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
