Smarthome Network 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 sensors and other techniqually needed objects to deploy a network in a smart home environment. The concept of Network is modeled in this pattern as a System (http://purl.oclc.org/NET/ssnx/ssn#System) whose constituents are NodeStations (subclass of Node which is in turn subsumed by the class http://purl.oclc.org/NET/ssnx/ssn#Device). Another subsumee of the Device class is the class Node describing more details about the content of each node station. Depending on their roles, nodes of a network are devided into types of node senders (whcih observe a phenomenon and send the data) and receivers (which receive the observation data).
What it answers¶
- What are the nodes that are sending data to a given receiver?
- What is the receiving node of the given set of sending nodes?
- Which types of nodes are available in a network?
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 | 13 classes, 10 properties, 55 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 23 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_Network.owl#DataReceiverNodehttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Network.owl#DataSenderNodehttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Network.owl#Networkhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Network.owl#Nodehttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Network.owl#NodeStationhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Network.owl#ReceiverNodeStationhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Network.owl#SenderNodeStationhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Network.owl#SmartHomeDeploymenthttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Network.owl#receivesDataFromhttp://ecareathome-ontology.mpi.aass.oru.se/patterns/SmartHome_Network.owl#sendsDataTohttp://purl.oclc.org/NET/ssnx/ssn#Deploymenthttp://purl.oclc.org/NET/ssnx/ssn#Devicehttp://purl.oclc.org/NET/ssnx/ssn#Platformhttp://purl.oclc.org/NET/ssnx/ssn#SensingDevicehttp://purl.oclc.org/NET/ssnx/ssn#Systemhttp://purl.oclc.org/NET/ssnx/ssn#deployedOnPlatformhttp://purl.oclc.org/NET/ssnx/ssn#deployedSystemhttp://purl.oclc.org/NET/ssnx/ssn#hasDeploymenthttp://purl.oclc.org/NET/ssnx/ssn#onPlatformhttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasConstituenthttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#hasParthttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isConstituentOfhttp://www.ontologydesignpatterns.org/ont/dul/DUL.owl#isPartOf
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.