Submissions:RecurrentEventSeries

From Odp

(Difference between revisions)
Jump to: navigation, search

ValentinaAnitaCarriero (Talk | contribs)
(New page: {{Content_OP_Proposal_toolbar}} {{Graphical representation header}} {{Graphical representation}} {{Content OP Proposal Template |SubmittedBy=ValentinaAnitaCarriero |Name=RecurrentEventSeri...)
Next diff →

Revision as of 17:31, 27 June 2019


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

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: 13657

Graphical representation

Diagram (this article has no graphical representation)

General description

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:
  • 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?
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: http://www.ontologydesignpatterns.org/cp/owl/recurrenteventseries.owl (484)
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:


Elements

The RecurrentEventSeries Content OP locally defines the following ontology elements:

Additional information

Scenarios

Scenarios about RecurrentEventSeries

No scenario is added to this Content OP.

Reviews

Reviews about RecurrentEventSeries

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

Other info at evaluation tab


Modeling issues

Modeling issues about RecurrentEventSeries

There is no Modeling issue related to this proposal.


References

Add a reference


Personal tools
Quality Committee
Content OP publishers