# Submissions:RecurrentEventSeries

(Difference between revisions)
 Revision as of 17:31, 27 June 2019 (view source) (New page: {{Content_OP_Proposal_toolbar}} {{Graphical representation header}} {{Graphical representation}} {{Content OP Proposal Template |SubmittedBy=ValentinaAnitaCarriero |Name=RecurrentEventSeri...)← Previous diff Current revision (13:55, 28 June 2019) (view source) Line 1: Line 1: {{Content_OP_Proposal_toolbar}} {{Content_OP_Proposal_toolbar}} {{Graphical representation header}} {{Graphical representation header}} - {{Graphical representation}} + {{Graphical representation + |ImageName=Recurrent-event-series.jpg + }} {{Content OP Proposal Template {{Content OP Proposal Template |SubmittedBy=ValentinaAnitaCarriero |SubmittedBy=ValentinaAnitaCarriero

## Current revision

 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: In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 13662

Diagram

# General description

 Name: RecurrentEventSeries ValentinaAnitaCarriero To represent recurrent event series as situations and collections of consecutive events, with a regular time period between events and unifying factors. What are the events of a recurrent event series? Which is the time period elapsing between two events of a recurrent event series? When is the next event of a recurrent event series scheduled? What are the unifying criteria shared by all the events in a recurrent event series? Which is the (immediate) next event in a recurrent event series? Which is the (immediate) previous event in a recurrent event series? 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. http://www.ontologydesignpatterns.org/cp/owl/recurrenteventseries.owl (97) A series of recurrent events, its unifying factors and the recurrent time period can be modelled. 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.

# Elements

The RecurrentEventSeries Content OP locally defines the following ontology elements:

# Scenarios

No scenario is added to this Content OP.

# Reviews

There is no review about this proposal. This revision (revision ID 13662) takes in account the reviews: none

Other info at evaluation tab

# Modeling issues

There is no Modeling issue related to this proposal.