Skip to content

Minor clarifications - observation #486

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dr-shorthair wants to merge 9 commits into
base: gh-pages
Choose a base branch
from
Open

Minor clarifications - observation #486

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
595b1cc
Minor clarifications - observation
dr-shorthair Aug 30, 2026
79887d6
sub-class --> subclass etc
dr-shorthair Sep 1, 2026
a80f041
indefinite article
dr-shorthair Sep 1, 2026
dbe4190
Update ssn/chapters/Observation.html
dr-shorthair Sep 2, 2026
3050df6
Update ssn/chapters/Observation.html
dr-shorthair Sep 2, 2026
505f6c5
Update ssn/rdf/ontology/core/sosa-observation.ttl
dr-shorthair Sep 2, 2026
8b23285
pronoun --> demonstrative noun
dr-shorthair Sep 3, 2026
cf6334c
Merge remote-tracking branch 'origin/minor-edits-observation' into mi…
dr-shorthair Sep 3, 2026
483785f
missed one
dr-shorthair Sep 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 14 additions & 13 deletions ssn/chapters/Observation.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ <h4>Overview</h4>
Classes and relationships involved in Observation.
<br>
The result of an observation should be an information item of a type appropriate for the
observed-property (e.g., a number, quantity, category, image, vector, array, geometry etc.).
observed property (e.g., a number, quantity, category, image, vector, array, geometry etc.).
<br>
<em><a href="#Class-diagram">Explanation of the notation used in class diagrams</a></em>.
</figcaption>
Expand Down Expand Up @@ -164,7 +164,7 @@ <h5><dfn>sosa:ObservationCollection</dfn></h5>
[[vocab-dcat-3]].
</p>
<p>
All <a href="#SOSAObservation">Observation</a> properties may appear in an
All <a href="#SOSAObservation">Observation</a> properties may appear in a
<a>sosa:ObservationCollection</a>, including:
<a>sosa:hasFeatureOfInterest</a>,
<a>sosa:hasUltimateFeatureOfInterest</a>,
Expand All @@ -175,7 +175,7 @@ <h5><dfn>sosa:ObservationCollection</dfn></h5>
<a>sosa:resultTime</a>,
<a>sosa:hasResult</a>,
<a>sosa:hasSimpleResult</a>.
If they are present, the value of these properties summarize the values of the matching properties of
If they are present, the values of these properties summarize the values of the matching properties of
the member observations, where membership is either direct or transitive through one or more member
observation collections.
</p>
Expand Down Expand Up @@ -360,7 +360,8 @@ <h5><dfn>sosa:Sensor</dfn></h5>
System that implements an ObservingProcedure to determine the value of an observable Property
</p>
<p>
This may be a device, a piece of infrastructure, an agent (including humans), or a software-based system, including systems performing simulations.
This may be a device, a piece of infrastructure, an agent (including humans), or a software-based system,
including systems performing simulations.
Comment thread
dr-shorthair marked this conversation as resolved.
Outdated
</p>
<p>
A <a href="#SOSASensor">Sensor</a> responds to a <a href="#SOSAStimulus">Stimulus</a>,
Expand All @@ -372,12 +373,12 @@ <h5><dfn>sosa:Sensor</dfn></h5>
See <a href="#ModelLocation">Location and Geometry</a> for patterns to describe this.
</p>
<p class="note">
Specific sensor <em>types</em> may be implemented as <em>sub-classes</em>
of this class or its sub-classes.
Specific sensor <em>types</em> may be implemented as <em>subclasses</em>
of this class or its subclasses.
Their descriptions may capture the properties and characteristics of a whole class of sensors, corresponding
with the information typically found in a spec-sheet or data-sheet.
with the information typically found in a spec-sheet or datasheet.

@ldesousa ldesousa Aug 31, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one I don't get. I suggested before "data sheet".

@TallTed TallTed Sep 2, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Google says correct hyphenation of "a spec-sheet or datasheet" for a formal technical document --

The correct forms are spec sheet and data sheet as two separate words without hyphens, or spec-sheet and data-sheet only when used as compound modifiers directly before a noun.

Suggested change
with the information typically found in a spec-sheet or datasheet.
with the information typically found in a spec sheet or data sheet.

@dr-shorthair dr-shorthair Sep 2, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry guys, we are going round in circles here.
I asked the web and got

image

Since we are working in an engineering context, I chose 'datasheet'.

@TallTed TallTed Sep 3, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough. Inconsistency is the way of the English world. :-)

<br>
Individual sensor <em>instances</em> are <em>members</em> of this class or its sub-classes.
Individual sensor <em>instances</em> are <em>members</em> of this class or its subclasses.
<br>
See <a href="#ModelSystemType">Systems Types and Individuals</a> for patterns to describe this.
</p>
Expand Down Expand Up @@ -446,7 +447,7 @@ <h5><dfn>sosa:Stimulus</dfn></h5>
event in the real world that triggers a Sensor
</p>
<p>
The properties associated to the Stimulus may be different to the eventual observed Property.
The properties associated with the Stimulus may be different to the eventual observed Property.
Comment thread
dr-shorthair marked this conversation as resolved.
Outdated
It is the event, not the object, that triggers the Sensor.
</p>
<dl>
Expand Down Expand Up @@ -532,7 +533,7 @@ <h5><dfn>sosa:hasProxy</dfn></h5>
<dl>
<dt>Examples</dt>
<dd>
For example, the expansion of mercury is a
The expansion of mercury is a
<a href="#SOSAStimulus">Stimulus</a> that serves as a
proxy for some temperature
<a href="#SOSAProperty">Property</a>.
Expand Down Expand Up @@ -574,7 +575,7 @@ <h5><dfn>sosa:isDetectedBy</dfn></h5>
</p>
<p>
<em>is detected by</em> &mdash;
relation from a Stimulus to a Sensor that may detect it
relation from a Stimulus to a Sensor that may detect the Stimulus
Comment thread
dr-shorthair marked this conversation as resolved.
Outdated
</p>
<p>
The Stimulus itself will be serving as a proxy (<a>sosa:isProxyFor</a>) for some Property.
Expand Down Expand Up @@ -932,7 +933,7 @@ <h5><dfn>sosa:originated</dfn></h5>
</p>
<p>
<em>originated</em> &mdash;
relation from a Stimulus to an Observation that was originated by it
relation from a Stimulus to an Observation that was originated by the Stimulus
Comment thread
dr-shorthair marked this conversation as resolved.
Outdated
</p>
<dl>
<dt>Domain Includes</dt>
Expand Down Expand Up @@ -1147,7 +1148,7 @@ <h5><dfn>sosa:wasOriginatedBy</dfn></h5>
</p>
<p>
<em>was originated by</em> &mdash;
relation from an Observation to the Stimulus that originated it
relation from an Observation to the Stimulus that originated the Observation
Comment thread
dr-shorthair marked this conversation as resolved.
Outdated
</p>
<dl>
<dt>Domain Includes</dt>
Expand Down
12 changes: 6 additions & 6 deletions ssn/rdf/ontology/core/sosa-observation.ttl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ sosa:ObservationCollection

All Observation properties may appear in an Observation Collection, including:
hasFeatureOfInterest , hasUltimateFeatureOfInterest , usedProcedure , madeBySensor , observedProperty , phenomenonTime , startTime, resultTime , hasResult , hasSimpleResult :
If they are present, the value of these properties summarize the values of the matching properties of the member observations, where membership is either direct or transitive through one or more member observation collections.
If they are present, the values of these properties summarize the values of the matching properties of the member observations, where membership is either direct or transitive through one or more member observation collections.
The following consistency rules apply with respect to the Observation properties listed above:

1. Where an individual Observation Collection omits a property, a member Observation (direct or transitive) MAY have any value for that property.
Expand Down Expand Up @@ -113,7 +113,7 @@ sosa:Stimulus
skos:definition """
event in the real world that triggers a Sensor
"""@en ;
skos:note """The properties associated to the Stimulus may be different to the eventual observed Property. It is the event, not the object, that triggers the Sensor."""@en ;
skos:note """The properties associated with the Stimulus may be different to the eventual observed Property. It is the event, not the object, that triggers the Sensor."""@en ;
Comment thread
dr-shorthair marked this conversation as resolved.
Outdated
rdfs:isDefinedBy sosa-obs: .

sosa:detects
Expand All @@ -136,7 +136,7 @@ sosa:hasProxy
relation from a Property to a Stimulus that serves as its proxy
"""@en ;
skos:example """
For example, the expansion of mercury is a Stimulus that serves as a proxy for some temperature Property.
The expansion of mercury is a Stimulus that serves as a proxy for some temperature Property.
An increase or decrease in the velocity of spinning cups on a wind Sensor is serving as a proxy for the wind speed.
"""@en ;
schema:domainIncludes sosa:Property ;
Expand All @@ -148,7 +148,7 @@ sosa:isDetectedBy
a owl:ObjectProperty ;
rdfs:label "is detected by"@en ;
skos:definition """
relation from a Stimulus to a Sensor that may detect it
relation from a Stimulus to a Sensor that may detect the Stimulus
Comment thread
dr-shorthair marked this conversation as resolved.
Outdated

The Stimulus itself will be serving as a proxy for some Property.
"""@en ;
Expand Down Expand Up @@ -251,7 +251,7 @@ sosa:originated
a owl:ObjectProperty ;
rdfs:label "originated"@en ;
skos:definition """
relation from a Stimulus to an Observation that was originated by it
relation from a Stimulus to an Observation that was originated by the Stimulus
Comment thread
dr-shorthair marked this conversation as resolved.
Outdated
"""@en ;
schema:domainIncludes sosa:Stimulus ;
schema:rangeIncludes sosa:Observation ;
Expand Down Expand Up @@ -317,7 +317,7 @@ sosa:wasOriginatedBy
a owl:ObjectProperty ;
rdfs:label "was originated by"@en ;
skos:definition """
relation from an Observation to the Stimulus that originated it
relation from an Observation to the Stimulus that originated the Observation
Comment thread
dr-shorthair marked this conversation as resolved.
Outdated
"""@en ;
schema:domainIncludes sosa:Observation ;
schema:domainIncludes sosa:ObservationCollection ;
Expand Down
Loading