Skip to content

Minor clarifications - property definition pattern #497

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 3 commits into
base: gh-pages
Choose a base branch
from
Open

Minor clarifications - property definition pattern #497

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
43d9713
Minor clarifications - property definition pattern
dr-shorthair Aug 30, 2026
6635552
sub-class --> subclass etc
dr-shorthair Sep 1, 2026
cb7d472
indefinite article
dr-shorthair Sep 1, 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
4 changes: 2 additions & 2 deletions ssn/chapters/ModelPropertyDefinition.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ <h4>New property definitions</h4>
<pre class="example turtle" data-include="./rdf/examples/Temperature-i-adopt.ttl" data-include-format="text"></pre>
<p>
The key point is that an individual property, whether taken from a catalogue or defined using a specialist
vocabaulary, is denoted by a URI.
vocabulary, is denoted by a URI.
This URI can then be used as the value of the
<a>sosa:actsOnProperty</a> or
<a>sosa:observedProperty</a> of an Execution.
Expand All @@ -47,7 +47,7 @@ <h4>Feature-specific properties</h4>
features of interest (e.g., `ex:Temperature`, `ex:Concentration`, or `ex:OnOffStatus`).
These <em>shared</em> properties are then used across executions. For instance, thousands of observations about CO<sub>2</sub> concentrations
all share the same `ex:Concentration` property, thereby ensuring scalability, indexing, interoperability, reuse,
and a concise semantics. Similarly, one could define `ex:CO2Concentration` as a sub-property of
and a concise semantics. Similarly, one could define `ex:CO2Concentration` as a subproperty of
`ex:Concentration` using a single axiom. This new property (and resulting hierarchy) can then be used to distinguish
CO<sub>2</sub> concentration observations from more general concentration observations without giving up on their commonality
with other types of concentration observations. This improves structure and retrieval. The catalogs listed above support this usage.
Expand Down
Loading