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

Jump to bottom

use proper Architecture 1.1 reference #1727

Merged
merged 1 commit into from
Oct 19, 2022
Merged

use proper Architecture 1.1 reference #1727

Show file tree
Hide file tree
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
12 changes: 6 additions & 6 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -463,7 +463,7 @@ <h2>Thing Description</h2>
Events (<a href="#eventaffordance"><code>EventAffordance</code></a> class) are used
for the push model of communication where notifications,
discrete events, or streams of values are sent asynchronously to the receiver.
See [[?WOT-ARCHITECTURE]] for details.
See [[wot-architecture11]] for details.
</p>
<p>
In general, the TD provides metadata for different <a>Protocol Bindings</a>
Expand Down Expand Up @@ -724,7 +724,7 @@ <h2>Terminology</h2>
<dfn>WoT Interface</dfn>, and
<dfn>WoT Runtime</dfn>
are defined in <a href="https://www.w3.org/TR/wot-architecture/#terminology">Section 3</a>
of the WoT Architecture specification [[?WOT-ARCHITECTURE]].
of the WoT Architecture specification [[wot-architecture11]].
</p>

<p>
Expand Down Expand Up @@ -914,7 +914,7 @@ <h2>Overview</h2>
<li>
the <em>core</em> TD <a>Vocabulary</a>, which reflects the
<a>Interaction Model</a> with the <a>Properties</a>, <a>Actions</a>, and <a>Events</a>
<a>Interaction Affordances</a> [[?WOT-ARCHITECTURE]]
<a>Interaction Affordances</a> [[wot-architecture11]]
</li>
<li>
the <em>Data Schema</em> <a>Vocabulary</a>, including (a subset of)
Expand Down Expand Up @@ -2257,8 +2257,8 @@ <h2>Hypermedia Controls Vocabulary Definitions</h2>
includes the well-known types necessary to implement the
WoT interaction model described in [<cite><a class=
"bibref" data-link-type="biblio" href=
"#bib-wot-architecture" title=
"Web of Things (WoT) Architecture">WOT-ARCHITECTURE</a></cite>].
"#bib-wot-architecture11" title=
"Web of Things (WoT) Architecture 1.1">wot-architecture11</a></cite>].
Future versions of the standard may extend this list but
<span class="rfc2119-assertion" id=
"well-known-operation-types-only">operations types
Expand Down Expand Up @@ -5511,7 +5511,7 @@ <h3>Protocol Bindings</h3>

<p>
Every form in a WoT Thing Description needs to have a submission target, given by the <code>href</code> member, as indicated in <a href="#form">Form</a>.
The URI scheme [[!RFC3986]] of this submission target indicates what <a>Protocol Binding</a> the <a>Thing</a> implements [[?WOT-ARCHITECTURE]].
The URI scheme [[!RFC3986]] of this submission target indicates what <a>Protocol Binding</a> the <a>Thing</a> implements [[wot-architecture11]].
For instance, if the target starts with <code>http</code> or
<code>https</code>, a <a>Consumer</a> can then infer the <a>Thing</a> implements the
<a>Protocol Binding</a> based on HTTP and it should expect HTTP-specific terms in the
Expand Down
8 changes: 4 additions & 4 deletions index.template.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -463,7 +463,7 @@ <h2>Thing Description</h2>
Events (<a href="#eventaffordance"><code>EventAffordance</code></a> class) are used
for the push model of communication where notifications,
discrete events, or streams of values are sent asynchronously to the receiver.
See [[?WOT-ARCHITECTURE]] for details.
See [[wot-architecture11]] for details.
</p>
<p>
In general, the TD provides metadata for different <a>Protocol Bindings</a>
Expand Down Expand Up @@ -724,7 +724,7 @@ <h2>Terminology</h2>
<dfn>WoT Interface</dfn>, and
<dfn>WoT Runtime</dfn>
are defined in <a href="https://www.w3.org/TR/wot-architecture/#terminology">Section 3</a>
of the WoT Architecture specification [[?WOT-ARCHITECTURE]].
of the WoT Architecture specification [[wot-architecture11]].
</p>

<p>
Expand Down Expand Up @@ -914,7 +914,7 @@ <h2>Overview</h2>
<li>
the <em>core</em> TD <a>Vocabulary</a>, which reflects the
<a>Interaction Model</a> with the <a>Properties</a>, <a>Actions</a>, and <a>Events</a>
<a>Interaction Affordances</a> [[?WOT-ARCHITECTURE]]
<a>Interaction Affordances</a> [[wot-architecture11]]
</li>
<li>
the <em>Data Schema</em> <a>Vocabulary</a>, including (a subset of)
Expand Down Expand Up @@ -4235,7 +4235,7 @@ <h3>Protocol Bindings</h3>

<p>
Every form in a WoT Thing Description needs to have a submission target, given by the <code>href</code> member, as indicated in <a href="#form">Form</a>.
The URI scheme [[!RFC3986]] of this submission target indicates what <a>Protocol Binding</a> the <a>Thing</a> implements [[?WOT-ARCHITECTURE]].
The URI scheme [[!RFC3986]] of this submission target indicates what <a>Protocol Binding</a> the <a>Thing</a> implements [[wot-architecture11]].
For instance, if the target starts with <code>http</code> or
<code>https</code>, a <a>Consumer</a> can then infer the <a>Thing</a> implements the
<a>Protocol Binding</a> based on HTTP and it should expect HTTP-specific terms in the
Expand Down
4 changes: 2 additions & 2 deletions validation/td-validation.ttl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -762,8 +762,8 @@
includes the well-known types necessary to implement the
WoT interaction model described in [<cite><a class=
"bibref" data-link-type="biblio" href=
"#bib-wot-architecture" title=
"Web of Things (WoT) Architecture">WOT-ARCHITECTURE</a></cite>].
"#bib-wot-architecture11" title=
"Web of Things (WoT) Architecture 1.1">wot-architecture11</a></cite>].
Future versions of the standard may extend this list but
<span class="rfc2119-assertion" id=
"well-known-operation-types-only">operations types
Expand Down