Warning:
This wiki has been archived and is now read-only.
SSN Base
Contents
Data
Data module
The two figures below shows two examples where the SSN ontology is used in conjunction with the DUL ontology to manage data.
Figure 5.21 shows how a ssn:ObservationValue which is a sub-class of DUL:Region is attached to a ssn:SensorOutput.
Figure 5.21 - Using ssn:hasValue for observation results
Data example (OWL)
- See uni-deploy for more info.
- See University deployment for more info.
Figure 5.22 shows how an example of how data value can be attached to a ssn:Property (here a ssn:OperatingPowerRange).
This example uses DUL:Amount, a subclass of DUL:Region which is the DUL class to handle a quantity value. The DUL:UnitOfMeasure can also be defined. In DUL, Units of measure are conceptualized as parameters on regions and defined as a subclass of DUL:Parameter.
Figure 5.22 - Using ssn:hasValue to add data to a operational restriction property
ConstraintBlock (Condition)
ConstraintBlock module
- Condition and inCondition
ssn:Condition is used to specify ranges for qualities that act as conditions on a system/sensor's operation. For example, wind speed of 10-60m/s is expressed as a condition linking a quality, wind speed, a unit of measurement, metres per second, and a set of values, 10-60, and may be used as the condition on a MeasurementProperty, for example, to state that a sensor has a particular accuracy in that condition.
ssn:inCondition describes the prevailing environmental conditions for Measurement Capabilites, Operating Conditions and Survival Ranges. Used for example to say that a sensor has a particular accuracy in particular conditions (see also the MeasuringCapability module documentation).
Figure 5.23 - Classes using ssn:Condition in the SSN Ontology
ConstraintBlock example (OWL)
- Snippet from : WM30
- See Wind sensor for more info.
This is called 'Storage temperature' on the WM30 data sheet. The intention is likely to be the same as SurvivalRange: i.e. if the device is stored outside this temperature range it no longer works as specified.
In any case, for the purposes of the example it shows the use of ssn:Condition to specify a SurvivalRange.
<owl:Ontology rdf:about="http://purl.oclc.org/NET/ssnx/meteo/WM30">
...
<owl:Class rdf:about="http://purl.oclc.org/NET/ssnx/meteo/WM30#WM30_SurvivalRange">
<rdfs:subClassOf rdf:resource="http://purl.oclc.org/NET/ssnx/ssn#SurvivalRange"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="http://purl.oclc.org/NET/ssnx/ssn#inCondition"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<owl:Class>
<owl:oneOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://purl.oclc.org/NET/ssnx/qu/dim/Temperature"/>
</owl:oneOf>
</owl:Class>
<owl:Restriction>
<owl:onProperty rdf:resource="http://purl.oclc.org/NET/ssnx/ssn#hasValue"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://purl.oclc.org/NET/ssnx/meteo/WM30#ValueRange"/>
<owl:Restriction>
<owl:onProperty rdf:resource="http://purl.oclc.org/NET/ssnx/meteo/WM30#unitOfMeasure"/>
<owl:someValuesFrom>
<owl:Class>
<owl:oneOf rdf:parseType="Collection">
<rdf:Description rdf:about="http://purl.oclc.org/NET/ssnx/qu/unit/degreeCelsius"/>
</owl:oneOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="http://purl.oclc.org/NET/ssnx/meteo/WM30#hasRangeMaxValueInclusive"/>
<owl:hasValue rdf:datatype="&xsd;float">65.0</owl:hasValue>
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="http://purl.oclc.org/NET/ssnx/meteo/WM30#hasRangeMinValueInclusive"/>
<owl:hasValue rdf:datatype="&xsd;float">-60.0</owl:hasValue>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
Figure 5.24 - ssn:Condition