-
Notifications
You must be signed in to change notification settings - Fork 81
/
errata.html
187 lines (170 loc) · 16 KB
/
errata.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
<!DOCTYPE HTML>
<html xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Errata for Semantic Sensor Network Ontology</title>
<link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/2016/W3C-REC.css">
<style type="text/css">
dl dt { margin-top: 1em; }
dl dd { margin-top: 0; margin-bottom: 0; }
li { margin-top: 0; margin-bottom: 0; }
</style>
</head>
<body>
<section>
<h1>Errata for Semantic Sensor Network Ontology</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>08 January 2019</h2>
<p class="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2019 <a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="https://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>). W3C <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
<hr/>
<section>
<h2 name="abstract" id="abstract">Abstract</h2>
<p>This document records known errata for the <a href="https://www.w3.org/TR/vocab-ssn/">Semantic Sensor Network Ontology</a> W3C Recommendation, published on 19 October 2017 (and updated in-place to fix link errors on 08 December 2017).</p>
<p>Entries are listed in chronological order of their date of publication. Each entry has the following information:</p>
<ul>
<li>A unique entry number</li>
<li>The date it was added to the errata page.</li>
<li>The type of erratum (editorial or substantive)</li>
<li>The section(s) referred to</li>
<li>A description of the problem and correction if applicable</li>
<li>A rationale for making the change (not required for editorial errata)</li>
</ul>
</section>
<section>
<h2 id="known-errors">Known errata in the Semantic Sensor Network Ontology</h2>
<p>No substantive errata have been identified so far. Known editorial errata are:</p>
<ol>
<li><a href="#entry-1">Syntax error in Seismographs example</a></li>
<li><a href="#entry-2">Syntax errors in DHT Deployment example</a></li>
<li><a href="#entry-3">"Specifically" misspelled as "secifically"</a></li>
<li><a href="#entry-4">Wrong domain/range for <code>actsOnProperty</code> and <code>isActedOnBy</code> in Actuation diagrams</a></li>
<li><a href="#entry-5">Inexistent <code>sosa:actuationMadeBy</code> property used in apartment 134 example</a></li>
<li><a href="#entry-6">Unsatisfiable classes in SSNX alignment module</a></li>
<li><a href="#entry-7">Unsatisfiable classes in DUL and SSNX alignment modules</a></li>
<li><a href="#entry-8">Use of <code>qudt-1-1:numericalValue</code> instead of <code>qudt-1-1:numericValue</code> in Examples 12 and 13</a></li>
<li><a href="#entry-9">Syntax error in apartment 134 examples</a></li>
<li><a href="#entry-10">Link error in IP68 Smart Sensor example</a></li>
</ol>
<p>Entries are detailed below:</p>
<dl>
<dt><a id="entry-1">1. Syntax error in Seismographs example</a></dt>
<dd>Added: 08 December 2017</dd>
<dd>Type: Editorial</dd>
<dd>Refers to: <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#seismograph">B.5 Seismographs</a></dd>
<dd>Description: The Turtle example ends with a "<code>;</code>".</dd>
<dd>Correction: Replace the final "<code>;</code>" with a "<code>.</code>".</dd>
<dd>Note: the RDF file containing a <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/integrated/examples/seismograph.ttl">graph corresponding to this example</a> correctly ends with a "<code>.</code>".</dd>
<dt><a id="entry-2">2. Syntax errors in DHT Deployment example</a></dt>
<dd>Added: 08 December 2017</dd>
<dd>Type: Editorial</dd>
<dd>Refers to: <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#dht22-deployment">B.10 DHT22 Deployment</a></dd>
<dd>Description: The objects of the <code>sosa:hosts</code> and <code>ssn:hasSubSystem</code> properties for <code><PCBBoard2></code> (resp. <code><PCBBoard3></code>) target <code><DHT22/4578></code> instead of <code><DHT22/4579></code> (resp. <code><DHT22/4580></code>).</dd>
<dd>Correction: the definitions of <code><PCBBoard2></code> and <code><PCBBoard3></code> should rather read:
<br/>
<div class="example">
<pre><code><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 <b><DHT22/4579></b> ;
ssn:hasSubSystem <b><DHT22/4579></b> .
<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 <b><DHT22/4580></b> ;
ssn:hasSubSystem <b><DHT22/4580></b> .
<DHT22/4580> a ssn:System ;
rdfs:label "DHT22 sensor #4580."@en ;
sosa:isHostedBy <PCBBoard3> .
</code></pre>
</div>
</dd>
<dd>Note: the same errors exist in the file containing a <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/integrated/examples/dht22-deployment.ttl">graph corresponding to this example</a>.</dd>
<dt><a id="entry-3">3. "Specifically" misspelled as "secifically"</a></dt>
<dd>Added: 08 December 2017</dd>
<dd>Type: Editorial</dd>
<dd>Refers to: sections <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#Actuations-overview">4.4.1</a>, <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#Sampling-overview">4.5.1</a>, <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#Features-of-Interest-and-Properties-overview">4.6.1</a>, <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#Results-overview">4.7.1</a>, <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#Procedures-overview">4.8.1</a>, <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#Systems-and-their-Deployment-overview">4.9.1</a></dd>
<dd>Description: The "p" is missing in occurrences of "specifically" in the referred sections.</dd>
<dd>Correction: Add the missing "p".</dd>
<dt><a id="entry-4">4. Wrong domain/range for <code>actsOnProperty</code> and <code>isActedOnBy</code> in Actuation diagrams</a></dt>
<dd>Added: 16 January 2018</dd>
<dd>Type: Editorial</dd>
<dd>Refers to: <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#Actuations-overview">4.4.1 Overview and examples</a></dd>
<dd>Description: Figures <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/images/SOSA-Actuation.png">11</a> and <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/images/SSN-Actuation.png">12</a> incorrectly connect the <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#SOSAactsOnProperty"><code>sosa:actsOnProperty</code></a> and the <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#SOSAisActedOnBy"><code>sosa:isActedOnBy</code></a> property links with the <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#SOSAActuator"><code>sosa:Actuator</code></a> class instead of with the <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#SOSAActuation"><code>sosa:Actuation</code></a> class.</dd>
<dd>Correction: Update the figures to connect the <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#SOSAactsOnProperty"><code>sosa:actsOnProperty</code></a> and <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#SOSAisActedOnBy"><code>sosa:isActedOnBy</code></a> property links with the <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#SOSAActuation"><code>sosa:Actuation</code></a> class.</dd>
<dd>Note: the normative definitions of these classes and properties are correct.</dd>
<dt><a id="entry-5">5. Inexistent <code>sosa:actuationMadeBy</code> property used in apartment 134 example</a></dt>
<dd>Added: 16 January 2018</dd>
<dd>Type: Editorial</dd>
<dd>Refers to: <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#apartment-134">B.3 apartment 134</a></dd>
<dd>Description: The <code>sosa:actuationMadeBy</code> property, which used to exist in previous versions of the specification, was renamed into <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#SOSAmadeByActuator"><code>sosa:madeByActuator</code></a>. The apartment 134 still uses the old property name.</dd>
<dd>Correction: Replace the occurrence of <code>sosa:actuationMadeBy</code> by <code>sosa:madeByActuator</code> in the example.</dd>
<dd>Note: the same error exists in the file containing a <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/integrated/examples/apartment-134-sosa.ttl">graph corresponding to this example</a>.</dd>
<dt><a id="entry-6">6. Unsatisfiable classes in SSNX alignment module</a></dt>
<dd>Added: 26 February 2018</dd>
<dd>Type: Editorial</dd>
<dd>Refers to: <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#SSNX_Alignment">6.2 SSNX Alignment Module</a></dd>
<dd>Description: Unsatisfiability of some classes due to axioms (1) and (2) being too strict:
<pre>sosa:hasResult ≡ oldssn:hasValue (1)
sosa:hasResult ≡ oldssn:observationResult (2)</pre>
<ul>
<li>Axiom (1) is causing the following problem: <code>oldssn:hasValue</code> is a sub-property of <code>dul:hasRegion</code>, whose range in DUL has <code>dul:Abstract</code> as a super-class. Yet, a <code>sosa:Sampling</code> procedure has only <code>sosa:Sample</code> as a result, and <code>sosa:Sample</code> is a sub-class of <code>( dul:Event or dul:Object or dul:Quality )</code></li>
<li>Axiom (2) is causing problems in combination to both:
<ul>
<li>disjunction between <code>dul:SocialObject</code> and <code>dul:PhysicalObject</code> , and</li>
<li>disjunctions between <code>dul:Event</code> and <code>dul:Object</code> .</li>
</ul>
</li>
</ul>
</dd>
<dd>Correction: Axioms (1) and (2) are relaxed to (1') and (2')
<pre>oldssn:hasValue ⊑ sosa:hasResult (1')
oldssn:observationResult ⊑ sosa:hasResult (2')</pre>
</dd>
<dd>Note: <code>≡</code> means <em>equivalent class</em>, <code>⊑</code> means <em>subclass of</em></dd>
<dd>Note: the change is made both in the specification and in the file containing <a href="http://www.w3.org/2017/01/ssn-ssnx/">SSN-SSNX</a>.</dd>
<dt><a id="entry-7">7. Unsatisfiable classes in DUL and SSNX alignment modules</a></dt>
<dd>Added: 26 February 2018</dd>
<dd>Type: Editorial</dd>
<dd>Refers to: <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#DUL_Alignment">6.1 Dolce-Ultralite Alignment Module</a> and <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#SSNX_Alignment">6.2 SSNX Alignment Module</a></dd>
<dd>Description: Unsatisfiability of some classes, ex. Survival classes:
<ul>
<li>class <code>ssn-system:SurvivalProperty</code> is a sub-class of <code>ssn:Property</code>, and has for <code>inverseof( ssn-system:hasSurvivalProperty )</code> only (and at least one) <code>ssn-system:SurvivalRange</code>, that is a sub-class of <code>ssn:Property</code></li>
<li><code>inverseof( ssn-system:hasSurvivalProperty )</code> is a sub-property of <code>ssn:isPropertyOf</code><br>
<code>ssn:Property</code> has for <code>ssn:isPropertyOf</code> only <code>sosa:FeatureOfInterest</code></li>
</ul>
So some instance of <code>ssn-system:SurvivalRange</code> would be both a <code>ssn:Property</code> and a <code>sosa:FeatureOfInterest</code>, which is forbidden.
</dd>
<dd>Correction: A feature of interest can also be a quality, so axioms (1) and (2) are relaxed to (1') and (2')
<pre>sosa:FeatureOfInterest rdfs:subClassOf [ owl:unionOf ( dul:Event dul:Object dul:InformationEntity ) ] (1)
oldssn:FeatureOfInterest owl:equivalentClass sosa:FeatureOfInterest (2)</pre>
<pre>sosa:FeatureOfInterest rdfs:subClassOf dul:Entity (1')
oldssn:FeatureOfInterest rdfs:subClassOf sosa:FeatureOfInterest (2')</pre>
<dd>Note: the change is made both in the specification and in the files containing <a href="http://www.w3.org/ns/ssn/dul">the DUL alignment</a> and <a href="http://www.w3.org/2017/01/ssn-ssnx/">SSN-SSNX</a>.</dd>
<dt><a id="entry-8">8. Use of <code>qudt-1-1:numericalValue</code> instead of <code>qudt-1-1:numericValue</code> in Examples 12 and 13</a></dt>
<dd>Added: 15 March 2018</dd>
<dd>Type: Editorial</dd>
<dd>Refers to: Example <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#tree-height">B.4 Tree height measurement</a></dd>
<dd>Description: Use of <code>qudt-1-1:numericalValue</code> instead of <code>qudt-1-1:numericValue</code> in the referred examples.</dd>
<dd>Correction: change <code>qudt-1-1:numericalValue</code> to <code>qudt-1-1:numericValue</code>.</dd>
<dd>Note: the same syntax error exists in the specification and in the RDF files containing a <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/integrated/examples/tree-height.ttl">graph corresponding to Example 12</a> and a <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/integrated/examples/tree-height-sosa.ttl">graph corresponding to Example 11</a>.</dd>
<dt><a id="entry-9">9. Syntax error in apartment 134 examples</a></dt>
<dd>Added: 15 March 2018</dd>
<dd>Type: Editorial</dd>
<dd>Refers to: <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#apartment-134">B.3 apartment 134</a></dd>
<dd>Description: The examples reference a non-existing <code>sosa:hasSimplResult</code> predicate.</dd>
<dd>Correction: Replace <code>sosa:hasSimplResult</code> with <code>sosa:hasSimpleResult</code> in Example 10 and Example 11.</dd>
<dd>Note: the same syntax error exists in the specification and in the RDF files containing a <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/integrated/examples/seismograph.ttl">graph corresponding to Example 10</a> and a <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/integrated/examples/apartment-134-sosa.ttl">graph corresponding to Example 11</a>.</dd>
<dt><a id="entry-10">10. Link error in IP68 Smart Sensor example</a></dt>
<dd>Added: 08 January 2019</dd>
<dd>Type: Editorial</dd>
<dd>Refers to: <a href="https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/#ip68-smart-sensor">B.11 IP68 Smart Sensor</a></dd>
<dd>Description: The link to the graph corresponding to the example goes to the wrong file.</dd>
<dd>Correction: Fix the link to target the correct <a href="https://www.w3.org/TR/vocab-ssn/integrated/examples/ip68.ttl">IP68 Smart Sensor graph file</a>.</dd>
</dl>
</section>
</section>
</body>
</html>