Skip to content

Recurrentsituationseries Pattern

Source: ODP portal  ·  Published by: ontologydesignpatterns.org  ·  Category: structural  ·  Domain: music

To represent recurrent situation series as situations and collections of consecutive situations, with a regular time period between situations and unifying factors.

What it answers

  • What are the situations of a recurrent situation series?, Which is the time period elapsing between two situations of a recurrent situation series?, When is the next situation of a recurrent situation series scheduled?, What are the unifying criteria shared by all the situations in a recurrent situation series?, Which are the unifying situations shared by a (subset of) the situations member of a recurrent situation series?, When is a unifying situation valid?, Which is the (immediate) next situation in a recurrent situation series?, Which is the (immediate) previous situation in a recurrent situation series?

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.

Download the pattern

Should you use this one?
Size 9 classes, 31 properties, 220 axioms
Brings in 1 imported ontology, so adopting it adopts that too
Reasoning HermiT finds this pattern consistent, with no unsatisfiable class, and its worked example consistent with the pattern.

A situation it was written for. Umbria Jazz is a collection of situations, which all take place in July and in the Italian region of Umbria, and has the musical genre jazz as a topic. Its situations recur at regular time periods, i.e. annually.

Check it yourself: the published pattern  ·  an archived copy  ·  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 40 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/recurrentsituationseries.owl#RecurrentSituationSeries
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#Situation
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#TimePeriod
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#UnifyingSituation
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#hasEstimatedTimePeriod
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#hasImmediateNextSituation
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#hasImmediatePreviousSituation
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#hasMeasuredTimePeriod
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#hasMemberSituation
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#hasNextSituation
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#hasPreviousSituation
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#hasTimePeriod
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#hasTimePeriodBeforeNextSituation
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#hasUnifyingFactor
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#hasUnifyingSituation
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#involvesUnifyingFactor
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#isEstimatedTimePeriodOf
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#isInvolvedInUnifyingSituation
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#isLocallyInconsistentWith
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#isMeasuredTimePeriodOf
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#isSituationMemberOf
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#isTheLastSituation
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#isTimePeriodBeforeNextSituationOf
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#isTimePeriodOf
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#isUnifyingFactorOf
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#isUnifyingSituationOf
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#isValidIn
  • http://www.ontologydesignpatterns.org/cp/owl/recurrentsituationseries.owl#situationNumber
  • http://www.ontologydesignpatterns.org/ont/d0.owl#Eventuality
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Collection
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Concept
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Description
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#TimeInterval
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#classifies
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#follows
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasMember
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isClassifiedBy
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isMemberOf
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#precedes
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#satisfies

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.

Download the example

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.