Errata for Semantic Sensor Network Ontology

08 January 2019

Abstract

This document records known errata for the Semantic Sensor Network Ontology W3C Recommendation, published on 19 October 2017 (and updated in-place to fix link errors on 08 December 2017).

Entries are listed in chronological order of their date of publication. Each entry has the following information:

A unique entry number
The date it was added to the errata page.
The type of erratum (editorial or substantive)
The section(s) referred to
A description of the problem and correction if applicable
A rationale for making the change (not required for editorial errata)

Known errata in the Semantic Sensor Network Ontology

No substantive errata have been identified so far. Known editorial errata are:

Syntax error in Seismographs example
Syntax errors in DHT Deployment example
"Specifically" misspelled as "secifically"
Wrong domain/range for actsOnProperty and isActedOnBy in Actuation diagrams
Inexistent sosa:actuationMadeBy property used in apartment 134 example
Unsatisfiable classes in SSNX alignment module
Unsatisfiable classes in DUL and SSNX alignment modules
Use of qudt-1-1:numericalValue instead of qudt-1-1:numericValue in Examples 12 and 13
Syntax error in apartment 134 examples
Link error in IP68 Smart Sensor example

Entries are detailed below:

1. Syntax error in Seismographs example

Added: 08 December 2017

Type: Editorial

Refers to: B.5 Seismographs

Description: The Turtle example ends with a ";".

Correction: Replace the final ";" with a ".".

Note: the RDF file containing a graph corresponding to this example correctly ends with a ".".

2. Syntax errors in DHT Deployment example

Added: 08 December 2017

Type: Editorial

Refers to: B.10 DHT22 Deployment

Description: The objects of the sosa:hosts and ssn:hasSubSystem properties for <PCBBoard2> (resp. <PCBBoard3>) target <DHT22/4578> instead of <DHT22/4579> (resp. <DHT22/4580>).

Correction: the definitions of <PCBBoard2> and <PCBBoard3> should rather read:

<PCBBoard2> a ssn:System , sosa:Platform ;
  rdfs:label "PCB Board 2"@en ;
  rdfs:comment "PCB Board 2 hosts DHT22 temperature and humidity sensor #4579 permanently, one can say it has it as one of its subsystems."@en ;
  sosa:hosts <DHT22/4579> ;
  ssn:hasSubSystem <DHT22/4579> .

  <DHT22/4579> a ssn:System ;
    rdfs:label "DHT22 sensor #4579."@en ;
    sosa:isHostedBy <PCBBoard2> .


<PCBBoard3> a ssn:System , sosa:Platform ;
  rdfs:label "PCB Board 3"@en ;
  rdfs:comment "PCB Board 3 hosts DHT22 temperature and humidity sensor #4580 permanently, one can say it has it as one of its subsystems."@en ;
  sosa:hosts <DHT22/4580> ;
  ssn:hasSubSystem <DHT22/4580> .

  <DHT22/4580> a ssn:System ;
    rdfs:label "DHT22 sensor #4580."@en ;
    sosa:isHostedBy <PCBBoard3> .

Note: the same errors exist in the file containing a graph corresponding to this example.

3. "Specifically" misspelled as "secifically"

Added: 08 December 2017

Type: Editorial

Refers to: sections 4.4.1, 4.5.1, 4.6.1, 4.7.1, 4.8.1, 4.9.1

Description: The "p" is missing in occurrences of "specifically" in the referred sections.

Correction: Add the missing "p".

4. Wrong domain/range for actsOnProperty and isActedOnBy in Actuation diagrams

Added: 16 January 2018

Type: Editorial

Refers to: 4.4.1 Overview and examples

Description: Figures 11 and 12 incorrectly connect the sosa:actsOnProperty and the sosa:isActedOnBy property links with the sosa:Actuator class instead of with the sosa:Actuation class.

Correction: Update the figures to connect the sosa:actsOnProperty and sosa:isActedOnBy property links with the sosa:Actuation class.

Note: the normative definitions of these classes and properties are correct.

5. Inexistent sosa:actuationMadeBy property used in apartment 134 example

Added: 16 January 2018

Type: Editorial

Refers to: B.3 apartment 134

Description: The sosa:actuationMadeBy property, which used to exist in previous versions of the specification, was renamed into sosa:madeByActuator. The apartment 134 still uses the old property name.

Correction: Replace the occurrence of sosa:actuationMadeBy by sosa:madeByActuator in the example.

Note: the same error exists in the file containing a graph corresponding to this example.

6. Unsatisfiable classes in SSNX alignment module

Added: 26 February 2018

Type: Editorial

Refers to: 6.2 SSNX Alignment Module

Description: Unsatisfiability of some classes due to axioms (1) and (2) being too strict:

sosa:hasResult ≡ oldssn:hasValue (1)
sosa:hasResult ≡ oldssn:observationResult (2)

Axiom (1) is causing the following problem: oldssn:hasValue is a sub-property of dul:hasRegion, whose range in DUL has dul:Abstract as a super-class. Yet, a sosa:Sampling procedure has only sosa:Sample as a result, and sosa:Sample is a sub-class of ( dul:Event or dul:Object or dul:Quality )
Axiom (2) is causing problems in combination to both:
- disjunction between dul:SocialObject and dul:PhysicalObject , and
- disjunctions between dul:Event and dul:Object .

Correction: Axioms (1) and (2) are relaxed to (1') and (2')

oldssn:hasValue ⊑ sosa:hasResult (1')
oldssn:observationResult ⊑ sosa:hasResult (2')

Note: ≡ means equivalent class, ⊑ means subclass of

Note: the change is made both in the specification and in the file containing SSN-SSNX.

7. Unsatisfiable classes in DUL and SSNX alignment modules

Added: 26 February 2018

Type: Editorial

Refers to: 6.1 Dolce-Ultralite Alignment Module and 6.2 SSNX Alignment Module

Description: Unsatisfiability of some classes, ex. Survival classes:

class ssn-system:SurvivalProperty is a sub-class of ssn:Property, and has for inverseof( ssn-system:hasSurvivalProperty ) only (and at least one) ssn-system:SurvivalRange, that is a sub-class of ssn:Property
inverseof( ssn-system:hasSurvivalProperty ) is a sub-property of ssn:isPropertyOf
ssn:Property has for ssn:isPropertyOf only sosa:FeatureOfInterest

So some instance of ssn-system:SurvivalRange would be both a ssn:Property and a sosa:FeatureOfInterest, which is forbidden.

Correction: A feature of interest can also be a quality, so axioms (1) and (2) are relaxed to (1') and (2')

sosa:FeatureOfInterest rdfs:subClassOf [ owl:unionOf ( dul:Event dul:Object dul:InformationEntity ) ] (1)
oldssn:FeatureOfInterest owl:equivalentClass sosa:FeatureOfInterest (2)

sosa:FeatureOfInterest rdfs:subClassOf dul:Entity (1')
oldssn:FeatureOfInterest rdfs:subClassOf sosa:FeatureOfInterest (2')

Note: the change is made both in the specification and in the files containing the DUL alignment and SSN-SSNX.

8. Use of qudt-1-1:numericalValue instead of qudt-1-1:numericValue in Examples 12 and 13

Added: 15 March 2018

Type: Editorial

Refers to: Example B.4 Tree height measurement

Description: Use of qudt-1-1:numericalValue instead of qudt-1-1:numericValue in the referred examples.

Correction: change qudt-1-1:numericalValue to qudt-1-1:numericValue.

Note: the same syntax error exists in the specification and in the RDF files containing a graph corresponding to Example 12 and a graph corresponding to Example 11.

9. Syntax error in apartment 134 examples

Added: 15 March 2018

Type: Editorial

Refers to: B.3 apartment 134

Description: The examples reference a non-existing sosa:hasSimplResult predicate.

Correction: Replace sosa:hasSimplResult with sosa:hasSimpleResult in Example 10 and Example 11.

Note: the same syntax error exists in the specification and in the RDF files containing a graph corresponding to Example 10 and a graph corresponding to Example 11.

10. Link error in IP68 Smart Sensor example

Added: 08 January 2019

Type: Editorial

Refers to: B.11 IP68 Smart Sensor

Description: The link to the graph corresponding to the example goes to the wrong file.

Correction: Fix the link to target the correct IP68 Smart Sensor graph file.