Skip to content

Minor clarifications - plan pattern #492

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

Minor clarifications - plan pattern #492

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 8 additions & 6 deletions ssn/chapters/ModelPlan.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ <h3>Planning executions and collections</h3>
Sampling) at some future time.
Collections of Samples or Executions can be described ahead of their completion, to indicate the intention
to make collections with the given properties at a future date.
Here we describe patterns that may be used in this way.
Patterns that may be used in this way are described here.
</p>

<section id="ModelPlan-Deployment">
Expand Down Expand Up @@ -44,7 +44,8 @@ <h4>Planned Collection using generic system</h4>
<p>
More generically, a Collection (i.e., <a>sosa:ActuationCollection</a>, <a>sosa:ObservationCollection</a>,
<a>sosa:SamplingCollection</a>, or <a>sosa:SampleCollection</a>) can be described which is made by a potential
deployment, where the actual system is only specified in terms of the Procedure implemented.
deployment.
In this case the actual system is only specified in terms of the Procedure implemented.
</p>
<p>
For example, <a href="#Fig-PlannedSampleCollection"></a> describes a potential set of samples (`ex:SC-LaJ2`) of
Expand All @@ -70,10 +71,11 @@ <h4>Planned Collection using generic system</h4>
(`ex:ObsColpH`),
packaged in a <a>sosa:ObservationCollection</a>, whose (proximate) feature of interest is the set of Samples
described above (`ex:SC-LaJ2`).
Each member of the <a>sosa:ObservationCollection</a>must be consistent with the
<a href="#SOSAObservationCollection">requirements for membership of an ObservationCollection</a> - i.e., be
sampled on the specified <a>sosa:Platform</a> using the nominated <a>sosa:ObservingProcedure</a> (`ex:pH-A56`),
and whose <a>sosa:hasFeatureOfInterest</a> must be a member of the set of Samples (`ex:SC-LaJ2`).
Each member of the <a>sosa:ObservationCollection</a> must be consistent with the
<a href="#SOSAObservationCollection">requirements for membership of an ObservationCollection</a>.
It must use the nominated <a>sosa:ObservingProcedure</a> (`ex:pH-A56`),
and its <a>sosa:hasFeatureOfInterest</a> must be a member of the set of Samples (`ex:SC-LaJ2`),
from the same Platform (`ex:LOIRE_A_JARGEAU_WQ_Station`).
Again, the actual System (<a>sosa:Sensor</a>) is not specified, only that it must implement the nominated
ObservingProcedure.
</p>
Expand Down
Loading