Skip to content

Smarthome Object Pattern

Source: ODP portal  ·  Published by: ecareathome-ontology.mpi.aass.oru.se  ·  Category: structural  ·  Domain: iot

This pattern relies on both the SSN ontology and DUL in order to represent an object in the context of Smart Home. Using this model we categorize the objects in to two groups of Smart Objects and NodeHolder based on the reason behind their existance in a smart home. Due to usual difficulties to install sensors in a smart home environment it is common that some other objects (i.e. NodeHolder) are used to attache sensors on so as to observe the situation of other objects (i.e. SmartObject) specifically for the configuration planner. Using this pattern we are able to diffrentiate between these two types of objects. This pattern also allows us to extend the definition of an object's properties in the context of smart home. The properties of a SmartObject which are the interest of the sensing process can be defined as either a subclass of the class http://purl.oclc.org/NET/ssnx/ssn#Property (e.g. the temperature of a stove) or as part of the smart object (e.g. the door of a friedge)

What it answers

  • Where is the location of a given object?
  • Which objects are used as the holder of sensors in the smart home environment?
  • Which devices (e.g. sensors) are attached to a NodeHolder?
  • Which objects are there in a smart home environment?
  • Which objects are the interest of the observation process?

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 15 classes, 5 properties, 38 axioms
Brings in 3 imported ontologies, so adopting it adopts those 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 46 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://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#SmartHomeGeoFeature
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#eastOf
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#hasDirectionalRelation
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#hasSpatialRelation
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#northEastOf
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#northOf
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#northWestOf
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#southEastOf
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#southOf
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#southWestOf
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#westOf
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Object.owl#Location
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Object.owl#MobileObject
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Object.owl#NodeHolder
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Object.owl#NonMobileObject
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Object.owl#SmartHomeAgent
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Object.owl#SmartHomeObject
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Object.owl#SmartObject
  • http://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Property.owl#SmartHomeProperty
  • http://purl.oclc.org/NET/ssnx/ssn#Device
  • http://purl.oclc.org/NET/ssnx/ssn#Platform
  • http://purl.oclc.org/NET/ssnx/ssn#Property
  • http://purl.oclc.org/NET/ssnx/ssn#attachedSystem
  • http://purl.oclc.org/NET/ssnx/ssn#hasProperty
  • http://purl.oclc.org/NET/ssnx/ssn#isPropertyOf
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Agent
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Event
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#NaturalPerson
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalObject
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalPlace
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Situation
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasConstituent
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasLocation
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isObjectIncludedIn
  • http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isParticipantIn
  • http://www.opengis.net/ont/geosparql#Feature
  • http://www.opengis.net/ont/geosparql#Geometry
  • http://www.opengis.net/ont/geosparql#hasGeometry
  • http://www.opengis.net/ont/geosparql#sfContains
  • http://www.opengis.net/ont/geosparql#sfCrosses
  • http://www.opengis.net/ont/geosparql#sfDisjoint
  • http://www.opengis.net/ont/geosparql#sfEquals
  • http://www.opengis.net/ont/geosparql#sfIntersects
  • http://www.opengis.net/ont/geosparql#sfOverlaps
  • http://www.opengis.net/ont/geosparql#sfTouches
  • http://www.opengis.net/ont/geosparql#sfWithin

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.