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

Prepare for CR Transition #833

Merged
merged 5 commits into from
Sep 8, 2022
Merged

Prepare for CR Transition #833

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5245b47
make SOLID ref informative
mmccool Sep 8, 2022
6926ce1
add explicit section links to para starting at 4203
mmccool Sep 8, 2022
4ea7812
remove lines 4614-4616, avoid mention of nosec
mmccool Sep 8, 2022
abbd535
fix all HTMLtidy errors, generate static version
mmccool Sep 8, 2022
22e6f50
export, then tidy
mmccool Sep 8, 2022
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
41 changes: 20 additions & 21 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,13 +19,13 @@
shortName: "wot-architecture11",
copyrightStart: 2017,
wgPublicList: "public-wot-wg",
implementationReportURI: "https://w3c.github.io/wot-architecture/testing/report.html",
implementationReportURI: "https://w3c.github.io/wot-architecture/testing/report11.html",
github: {
repoURL: "https://github.com/w3c/wot-architecture",
branch: "master"
branch: "main"
},
previousPublishDate: "2020-11-24",
previousMaturity: "FPWD",
previousPublishDate: "2022-09-07",
previousMaturity: "WD",
editors: [
{
name: "Michael Lagally",
Expand Down Expand Up @@ -307,7 +307,7 @@
may be instantiated when devices and services that implement the Thing and Consumer
roles interact in different network topologies.</li>
<li>Section 10 <a href="#sec-security-considerations">Security Considerations</a> and
<li>Section 11 <a href="#sec-privacy-considerations">Privacy Considerations</a>
Section 11 <a href="#sec-privacy-considerations">Privacy Considerations</a>
are normative; they summarize some general issues and provide guidelines to help preserve
the security and privacy of concrete WoT implementations.</li>
</ul>
Expand Down Expand Up @@ -661,7 +661,6 @@ <h1>Terminology</h1>
Orchestration is combining individual things with rules or services
into a new service or virtual <a>Thing</a>.
</dd>
</dt>
<dt>
<dfn>Partial TD</dfn>
</dt>
Expand Down Expand Up @@ -975,28 +974,24 @@ <h2>Device Categories</h2>
<td>Small embedded devices such as M2M communication nodes, smart meters, sensor nodes and other embedded appliances,
home appliances, low-end TV set-top boxes, and point of sale terminals are some examples.</td>
<!-- could just call this an "advanced node" or just a "node" if above is "basic node" -->
</tr>
</tr><tr>
<td>Class-3, C3</td>
<td>~ 64-256 KiB</td>
<td>~ 256 KiB - several MBs</td>
<td>ISP gateway</td>
<td>Small home and industrial gateways</td>
</tr>
</tr><tr>
<td>Class-4, C4</td>
<td>~ 256 KiB - several MB</td>
<td>~ 1 MB - several MB</td>
<td>gateway/hub</td>
<td>Large home and industrial gateways</td>
</tr>
</tr><tr>
<td>Class-5, C5</td>
<td>~ 1 GB</td>
<td>~ 1 GB</td>
<td>edge</td>
<td>Powerful edge servers</td>
</tr>
</tr><tr>
<td>Class-6, C6</td>
<td>~ several GB</td>
Expand Down Expand Up @@ -1277,7 +1272,7 @@ <h1>Common Deployment Patterns</h1>
illustrate how devices/things interact with controllers,
other devices, agents and servers.
In this section, we use the term <em>client role</em> as an
initiator of a transport protocol, and the term </em>server role</em>
initiator of a transport protocol, and the term <em>server role</em>
as a passive component of a transport protocol.
This does not imply prescribing a specific role on any system component.
A device can be in a <em>client</em> and <em>server</em> role simultaneously.
Expand Down Expand Up @@ -1741,12 +1736,12 @@ <h2>Fundamental Concepts</h2>
<h3>Metadata</h3>
<p>
The WoT architecture provides metadata formats to describe both specific <em>instances</em>
of </a>Things</a> and <em>classes</em> of <a>Things</a>. The metadata format for <em>instances</em> is called
of <a>Things</a> and <em>classes</em> of <a>Things</a>. The metadata format for <em>instances</em> is called
<a>Thing Description</a> while that for <em>classes</em> is called <a>Thing Model</a>.
</p>
<section id="metadata-thing-descriptions">
<h3>Thing Descriptions</h3>
<p>A <a>Thing</a> instance is described by standardized metadata.</a>
<p>A <a>Thing</a> instance is described by standardized metadata.
<span class="rfc2119-assertion" id="arch-td-metadata">
In W3C WoT, the description metadata for a <a>Thing</a> instance
MUST be available as a <a>WoT Thing Description</a> (TD) [[?WOT-THING-DESCRIPTION]].</span>
Expand Down Expand Up @@ -1811,8 +1806,8 @@ <h3>Thing Models</h3>
<li> simulation of devices/<a>Things</a> that have not yet been developed.</li>
<li> developing common applications across devices from different manufacturers that share a common <a>Thing model</a>.
</li>
<li> combining multiple models into a <a>Thing</a>.
<li> implementation support of a concrete <a>Thing</a>.
<li> combining multiple models into a <a>Thing</a>.</li>
<li> implementation support of a concrete <a>Thing</a>.</li>
</ul>
<p>
The <a>Thing Model</a> is a logical description of the interface and possible interaction with <a>Thing</a>'s
Expand Down Expand Up @@ -3123,7 +3118,7 @@ <h3>Exploration Mechanisms</h3>
Suitable best-practice security mechanisms for authentication and authorization for
different circumstances are discussed in [[WOT-SECURITY]].
Suitable mechanisms for managing access controls and keys are also discussed
in [[SOLID]].
in [[?SOLID]].
</p><p>
<a>TDDs</a> are not just a convenience feature but are essential in several
WoT use cases.
Expand Down Expand Up @@ -4200,8 +4195,10 @@ <h5>Cross-Script Security Risk</h5>
In practice, isolation of scripts and runtime instances from each other
can be accomplished by running all instances
in a "sandboxed" environment that controls its access to the rest of the environment.
For more information see Sections "WoT Servient Single-Tenant" and "WoT Servient
Multi-Tenant" of the <em>WoT Security and Privacy Guidelines</em> specification [[?WOT-SECURITY]].
For more information see Sections
<a href="https://www.w3.org/TR/wot-security/#wot-servient-single-tenant">WoT Servient Single-Tenant</a>
and <a href="https://www.w3.org/TR/wot-security/#wot-servient-multi-tenant">WoT Servient Multi-Tenant</a>
of the <em>WoT Security and Privacy Guidelines</em> specification [[?WOT-SECURITY]].
</dd>
</dl>
</section>
Expand Down Expand Up @@ -4421,7 +4418,7 @@ <h2>Secure Transport</h2>
id="arch-security-consideration-tls-optional-on-lan">
Private networks such as a LAN, protected by a firewall, MAY use the
<a href="#sec-security-consideration-trusted-environment-risks">Trusted
Environment</a> approach of depending on network security only</a>.</span>
Environment</a> approach of depending on network security only.</span>
This is not generally recommended but may be necessary for practical
reasons. Please see the referenced security consideration for
additional risks and mitigations with this approach.
Expand Down Expand Up @@ -4611,9 +4608,11 @@ <h2>Access to Personally Identifiable Information</h2>
returning Thing Descriptions, the following also applies:
<span class="rfc2119-assertion" id="arch-privacy-consideration-id-access-control-mandatory-immutable">
Services returning Thing Descriptions with immutable IDs SHOULD use some form of access control.</span>
<!--
Specifically, in both of these situations, the <code>nosec</code> security
scheme described in [[WOT-THING-DESCRIPTION]] should not be used,
as it provides no access control.
-->
Following the principle that Thing Descriptions describing
Things associated with specific persons should be treated as
PII, even if they do not explictly contain it, this implies
Expand Down Expand Up @@ -4683,9 +4682,9 @@ <h2 id="changes-in-fpwd-1.1-from-recommendation-1.0">Changes in the FPWD from th
<li>System Integration</li>
<li>Abstract WoT System Architecture</li>
</ul>
<li>Various editors notes with placeholders for planned contributions.</li>
<li> References to github repositories for use cases and requirements.</li>
</li>
<li>Various editors notes with placeholders for planned contributions.</li>
<li> References to github repositories for use cases and requirements.</li>
<li>Requirement chapter was moved to the <em>WoT Use Cases and Requirements</em> document [[WOT-USE-CASES-REQUIREMENTS]].</li>
</ul>

Expand Down
Loading