Skip to content
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

geo location metadata #961

Merged
merged 4 commits into from
Sep 21, 2020
Merged

geo location metadata #961

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d19bf78
geo location metadata
sebastiankb Sep 15, 2020
753ee6f
update examples based on feedback
sebastiankb Sep 17, 2020
ca56de7
update context
sebastiankb Sep 17, 2020
e497147
fix in example
sebastiankb Sep 18, 2020
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
111 changes: 110 additions & 1 deletion index.template.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3173,7 +3173,14 @@ <h3>Semantic Annotations</h3>
</p>

<p>
As an example, the TD snippet given below extends the version information container
Next subsections shows some sample usage of different kind of ontologies in Thing Descriptions.
</p>

<section id="semantic-annotations-example-version-units">
<h3>Example I: Version and Unit Annotations</h3>

<p>
The TD snippet given below extends the version information container
by adding version numbers for the hardware and firmware of the <a>Thing</a>, and uses
values from external <a>Vocabularies</a> for the <a>Thing</a> and for the
data schema unit: <a href="https://w3id.org/saref">SAREF</a>,
Expand Down Expand Up @@ -3215,6 +3222,10 @@ <h3>Semantic Annotations</h3>
}
</pre>

</section>
<section id="semantic-annotations-example-state">
<h3>Example II: State Annotations</h3>

<p>
In many cases, <a>TD Context Extensions</a> may be used to annotate pieces of a data schema,
to be able to semantically process the state information of the physical world object,
Expand Down Expand Up @@ -3282,6 +3293,104 @@ <h3>Semantic Annotations</h3>
of the lamp.
</p>

</section>
<section id="semantic-annotations-example-geoloc">
<h3>Example III: Geolocation Annotations</h3>

<p>
For many use cases like in building, agraculture, or smart city location based data is required. This
information can be provided in the Thing Description in different ways and can be relyed on
different kind of location ontologies (e.g.,[[WGS84]], [[schema.org]) depending on purpose (e.g., indoor, outdoor).
Also see [[sdw-bp]].
</p>

<p>
The TD snippet below uses <code>lat</code> and <code>long</code> from the [[WGS84]] ontology to
provide static latitude and longitude metadata at Thing's top level.
</p>

<pre class="example" id="saref-state-annotation-example">
{
"@context": [
"https://www.w3.org/2019/wot/td/v1",
{
"geo": "http://www.w3.org/2003/01/geo/wgs84_pos#"
}
],
"@type": "Thing",
"geo:lat" : "26.58",
"geo:long" : "297.83",
...
"properties": {
...

}
</pre>


<p>
In some use cases location based metadata have to be provided at the interaction level, e.g.,
as provided as a <a>Property</a> that returns the latest <code>longitude</code>, <code>latitude</code>, abd <code>elevation</code> values
based on [[schema.org]]:
</p>

<pre class="example" id="saref-state-annotation-example">
{
"@context": [
"https://www.w3.org/2019/wot/td/v1",
{
"schema": "http://schema.org#"
}
],
...
"properties": {
"position": {
"type": "object",
"@type" : "schema:GeoCoordinates",
"properties": {
"longitude": { "type": "number" },
"latitude": { "type": "number" },
"elevation": { "type": "number" }
},
"forms": [{"href": "https://robot.example.com/position"}]
},
...
},
...
}
</pre>

<p>
In the case it is desired to have a different name for, e.g., <code>longitude</code>, <code>latitude</code>,
and <code>elevation</code>in the data model, <code>jsonld:context</code> can be used to link
terms to specific vocabulary from a ontology (also see [[json-schema]], Section 3.3 Defining a JSON-LD context for data instances):
</p>

<pre class="example" id="saref-state-annotation-example">
{
"@context": "https://www.w3.org/2019/wot/td/v1",
...
"properties": {
"position": {
"jsonld:context": {
"schema": "http://schema.org/"
"long": "schema:longitude",
"lat": "schema:latitude",
"height": "schema:elevation"
},
"type": "object",
"properties": {
"long": { "type": "number" },
"lat": { "type": "number" },
"height": { "type": "number" }
}
}
},
...
}
</pre>


</section>

<section>
Expand Down