Smarthome Place Pattern¶
Source: ODP portal · Published by: ecareathome-ontology.mpi.aass.oru.se · Category: spatial · Domain: iot
To represent a SmartHome as a place (specialization of http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalPlace) which contains a number of sections (other physical places) and is also seen as a platform (e.g. a platform for a sensor network).
What it answers¶
- What are the spatial/directional relations between sections of a smart home?
- Which physical objects are located in a section of a smart environment?
- How many and what sections are there in the SmartHome?
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.
Should you use this one?¶
| Size | 6 classes, 4 properties, 19 axioms |
| Brings in | 2 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 32 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#SmartHomeGeoFeaturehttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#eastOfhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#hasDirectionalRelationhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#hasSpatialRelationhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#northEastOfhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#northOfhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#northWestOfhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#southEastOfhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#southOfhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#southWestOfhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Geometry.owl#westOfhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Place.owl#SmartHomehttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Place.owl#SmartHomeSectionhttp://purl.oclc.org/NET/ssnx/ssn#Deploymenthttp://purl.oclc.org/NET/ssnx/ssn#Platformhttp://purl.oclc.org/NET/ssnx/ssn#inDeploymenthttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalObjecthttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#PhysicalPlacehttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasParthttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isLocationOfhttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isPartOfhttp://www.opengis.net/ont/geosparql#Featurehttp://www.opengis.net/ont/geosparql#Geometryhttp://www.opengis.net/ont/geosparql#hasGeometryhttp://www.opengis.net/ont/geosparql#sfContainshttp://www.opengis.net/ont/geosparql#sfCrosseshttp://www.opengis.net/ont/geosparql#sfDisjointhttp://www.opengis.net/ont/geosparql#sfEqualshttp://www.opengis.net/ont/geosparql#sfIntersectshttp://www.opengis.net/ont/geosparql#sfOverlapshttp://www.opengis.net/ont/geosparql#sfToucheshttp://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.
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.