Skip to content

Eventprocessing Pattern

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

To model event objects (in the context of complex event processing), their attributes, and their relations actual events, and sensor readings producing the events. Different types of event objects, such as complex, composite, and simple events are modelled, preoperties for expressing relations between event objects, such as constituency and componency are expressed, and attributes of event objects, such as timestamps and other data values. This pattern is aligned both to the SSN (Semantic Sensor Network) ontology, and the Event-F model, which in turn both use DUL as an upper layer.

What it answers

  • What event objects are this complex event object and abstraction of?
  • What is the header/body of this event object?
  • What are the parts of this composite event object?
  • What is the timestamp of this event object?
  • By what sensor was this event object recorded?
  • What actual event does this event object document?
  • What are the attribute values of this event object?

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 17 classes, 35 properties, 199 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.

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 52 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://events.semantic-multimedia.org/ontology/2009/4/15/model.owl#EventDocumentationDescription
  • http://events.semantic-multimedia.org/ontology/2009/4/15/model.owl#EventDocumentationSituation
  • http://events.semantic-multimedia.org/ontology/2009/4/15/model.owl#EventInterpretationDescription
  • http://purl.oclc.org/NET/ssnx/ssn#SensorOutput
  • http://www.loa-cnr.it/ontologies/DUL.owl#Event
  • http://www.loa-cnr.it/ontologies/DUL.owl#InformationObject
  • http://www.loa-cnr.it/ontologies/DUL.owl#Region
  • http://www.loa-cnr.it/ontologies/DUL.owl#SpaceRegion
  • http://www.loa-cnr.it/ontologies/DUL.owl#TimeInterval
  • http://www.loa-cnr.it/ontologies/DUL.owl#hasComponent
  • http://www.loa-cnr.it/ontologies/DUL.owl#hasConstituent
  • http://www.loa-cnr.it/ontologies/DUL.owl#hasDataValue
  • http://www.loa-cnr.it/ontologies/DUL.owl#hasPart
  • http://www.loa-cnr.it/ontologies/DUL.owl#hasRegion
  • http://www.loa-cnr.it/ontologies/DUL.owl#isAbout
  • http://www.loa-cnr.it/ontologies/DUL.owl#isComponentOf
  • http://www.loa-cnr.it/ontologies/DUL.owl#isConstituentOf
  • http://www.loa-cnr.it/ontologies/DUL.owl#isEventIncludedIn
  • http://www.loa-cnr.it/ontologies/DUL.owl#isPartOf
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#ComplexEventObject
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#CompositeEventObject
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#EventObject
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#EventObjectBody
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#EventObjectHeader
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#EventObjectPart
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#SensorOutput
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#SimpleEventObject
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasDirectSubEventObject
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventDuration
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventLocation
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventObjectApplicationTime
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventObjectAttributeDataValue
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventObjectAttributeValue
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventObjectBody
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventObjectComponent
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventObjectExpirationTime
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventObjectHeader
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventObjectPart
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventObjectSamplingTime
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventObjectSystemTime
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasEventObjectTime
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasSensorReadingValue
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#hasSubEventObject
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#informationAboutEvent
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#isDirectSubEventObjectOf
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#isEventObjectBodyOf
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#isEventObjectComponentOf
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#isEventObjectHeaderOf
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#isEventObjectPartOf
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#isSubEventObjectOf
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#refersToEventObjectComponent
  • http://www.ontologydesignpatterns.org/cp/owl/eventprocessing.owl#refersToEventObjectConstituent

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.