Skip to content

Actuation Actuator Effect Pattern

Source: ODP portal  ·  Published by: irit.fr  ·  Category: structural  ·  Domain: iot

Ontology design pattern for modeling actuation actuator effect relationships and concepts.

What it answers

  • Which physical quantity does a given device change, and what effect does it have on its surroundings?
  • Which commands has a device received, what value did each command carry, and when was it issued?
  • How quickly does a device react after a command arrives, and what range of commands can it accept without damaging itself?

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 36 classes, 25 properties, 216 axioms
Brings in nothing - it stands on its own
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 61 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://delicias.dia.fi.upm.es/ontologies/ObjectWithStates.owl#Object
  • http://purl.oclc.org/NET/ssnx/ssn#Device
  • http://purl.oclc.org/NET/ssnx/ssn#FeatureOfInterest
  • http://purl.oclc.org/NET/ssnx/ssn#Input
  • http://purl.oclc.org/NET/ssnx/ssn#Process
  • http://purl.oclc.org/NET/ssnx/ssn#Property
  • http://purl.oclc.org/NET/ssnx/ssn#forProperty
  • http://purl.oclc.org/NET/ssnx/ssn#hasProperty
  • http://purl.oclc.org/NET/ssnx/ssn#hasValue
  • http://purl.oclc.org/NET/ssnx/ssn#implements
  • http://purl.oclc.org/NET/ssnx/ssn#isPropertyOf
  • http://purl.org/vocommons/voaf#Vocabulary
  • http://qudt.org/schema/qudt#QuantityKind
  • http://qudt.org/schema/qudt#Unit
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#Acting
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#ActuatingCapability
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#ActuatingDevice
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#ActuatingProperty
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#ActuatingRange
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#ActuatingTime
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#Actuation
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#ActuationValue
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#Actuator
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#ActuatorInput
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#ActuatorOutput
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#Effect
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#Situation
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#actsOn
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#actuationMethodUsed
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#actuationResults
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#consumes
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#controlledBy
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#hasActuatingCapability
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#hasActuatingProperty
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#hasDateTime
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#hasEffect
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#impactedProperty
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#impacts
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#isActedUponBy
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#isConsumedBy
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#isController
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#receivedActuation
  • http://www.irit.fr/recherches/MELODI/ontologies/SAN#wasActuationSent
  • http://www.linkedmodel.org/schema/vaem#date
  • http://www.ontologydesignpatterns.org/cp/owl/situation.owl#Situation
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Agent
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Amount
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Entity
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Event
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#InformationObject
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Method
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Object
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalObject
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Process
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Quality
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Region
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#UnitOfMeasure
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#includesEvent
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isParametrizedBy
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isSettingFor
  • http://www.w3.org/2006/time#Instant

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.