|
53 | 53 | ],
|
54 | 54 | xref: ["web-platform", "HTML", "INFRA", "URL", "WEBIDL", "DOM", "FETCH",
|
55 | 55 | "ecmascript", "streams",
|
56 |
| - "wot-architecture", "wot-thing-description", "wot-binding-templates"], |
| 56 | + "wot-architecture11", "wot-thing-description", "wot-binding-templates"], |
57 | 57 | localBiblio: {
|
58 |
| - "WOT-ARCHITECTURE" : { |
59 |
| - href:"https://www.w3.org/TR/2023/CR-wot-architecture11-20230119/", |
60 |
| - title: "Web of Things (WoT) Architecture 1.1", |
61 |
| - publisher: "W3C", |
62 |
| - date: "19 January 2023" |
63 |
| - }, |
64 | 58 | "WOT-TD" : {
|
65 | 59 | href:"https://www.w3.org/TR/2023/CR-wot-thing-description11-20230119/",
|
66 | 60 | title: "Web of Things (WoT) Thing Description 1.1",
|
|
173 | 167 | The Web of Things is made of entities (<a>Thing</a>s) that can describe their capabilities in a machine-interpretable <a>Thing Description</a> (TD) and expose these capabilities through the <a>WoT Interface</a>, that is, network interactions modeled as <a>Properties</a> (for reading and writing values), <a>Action</a>s (to execute remote procedures with or without return values) and <a>Event</a>s (for signaling notifications).
|
174 | 168 | </p>
|
175 | 169 | <p>
|
176 |
| - The main <a>Web of Things</a> (WoT) concepts are described in the [[[WOT-ARCHITECTURE]]] specification. |
| 170 | + The main <a>Web of Things</a> (WoT) concepts are described in the [[[wot-architecture11]]] specification. |
177 | 171 | </p>
|
178 | 172 | <p>
|
179 | 173 | Scripting is an optional building block in WoT and it is typically used in gateways or browsers that are able to run a <a>WoT Runtime</a> and
|
|
204 | 198 | <section id="introduction"> <h2>Introduction</h2>
|
205 | 199 | <p>
|
206 | 200 | WoT provides layered interoperability based on how <a>Thing</a>s are used:
|
207 |
| - "consumed" and "exposed", as defined in the [[[WOT-ARCHITECTURE]]] terminology. |
| 201 | + "consumed" and "exposed", as defined in the [[[wot-architecture11]]] terminology. |
208 | 202 | </p>
|
209 | 203 | <p>
|
210 | 204 | By <a>consuming a TD</a>, a client <a>Thing</a> creates a local runtime resource model that allows accessing the <a>Properties</a>, <a>Actions</a> and <a>Events</a> exposed by the server <a>Thing</a> on a remote device.
|
|
385 | 379 |
|
386 | 380 | <section> <h2>Terminology and conventions</h2>
|
387 | 381 | <p>
|
388 |
| - The generic WoT terminology is defined in [[!WOT-ARCHITECTURE]]: <dfn data-lt="Things">Thing</dfn>, <dfn data-lt="Thing Descriptions">Thing Description</dfn> (in short <dfn>TD</dfn>), <dfn>Partial TD</dfn>, <dfn>Web of Things</dfn> (in short <b><i>WoT</i></b>), <dfn>WoT Interface</dfn>, <dfn>Protocol Bindings</dfn>, <dfn>WoT Runtime</dfn>, <dfn data-lt="consume|consume a TD|consuming a TD">Consuming a Thing Description</dfn>, <dfn>TD Directory</dfn>, <dfn data-lt="Properties">Property</dfn>, <dfn data-lt="Actions">Action</dfn>, <dfn data-lt="Events|WoT-Event">Event</dfn>, |
| 382 | + The generic WoT terminology is defined in [[!wot-architecture11]]: <dfn data-lt="Things">Thing</dfn>, <dfn data-lt="Thing Descriptions">Thing Description</dfn> (in short <dfn>TD</dfn>), <dfn>Partial TD</dfn>, <dfn>Web of Things</dfn> (in short <b><i>WoT</i></b>), <dfn>WoT Interface</dfn>, <dfn>Protocol Bindings</dfn>, <dfn>WoT Runtime</dfn>, <dfn data-lt="consume|consume a TD|consuming a TD">Consuming a Thing Description</dfn>, <dfn>TD Directory</dfn>, <dfn data-lt="Properties">Property</dfn>, <dfn data-lt="Actions">Action</dfn>, <dfn data-lt="Events|WoT-Event">Event</dfn>, |
389 | 383 | <a data-cite="WOT-TD#dataschema">
|
390 | 384 | <dfn>DataSchema</dfn></a>, <a data-cite="WOT-TD#form"><dfn data-lt="Forms">Form</dfn></a>,
|
391 | 385 | <a data-cite="WOT-TD#securityscheme"><dfn>SecurityScheme</dfn></a>, <a data-cite="WOT-TD#nosecurityscheme"><dfn>NoSecurityScheme</dfn></a> etc.
|
392 | 386 | </p>
|
393 | 387 | <p>
|
394 |
| - <dfn data-plurals="WoT Interactions">WoT Interaction</dfn> is a synonym for <a data-cite="WOT-ARCHITECTURE#dfn-interaction-affordance"><dfn>Interaction Affordance</dfn></a>. |
| 388 | + <dfn data-plurals="WoT Interactions">WoT Interaction</dfn> is a synonym for <a data-cite="wot-architecture11#dfn-interaction-affordance"><dfn>Interaction Affordance</dfn></a>. |
395 | 389 | An <a>Interaction Affordance</a> (or shortly, affordance) is the term used in [[!WOT-TD]]
|
396 | 390 | when referring to <a>Thing</a> capabilities, as explained in
|
397 | 391 | <a href="https://github.com/w3c/wot-thing-description/issues/282">TD issue 282</a>.
|
@@ -601,7 +595,7 @@ <h2>The <dfn>WOT</dfn> namespace</dfn></h2>
|
601 | 595 | that resolves with an {{ExposedThing}} object that extends {{ConsumedThing}} with a server interface,
|
602 | 596 | i.e. the ability to define request handlers. The |init:ExposedThingInit| object is an instance of the <a>ExposedThingInit</a> type.
|
603 | 597 | Specifically, an <a>ExposedThingInit</a> value is a dictionary used for the initialization of an <a>ExposedThing</a> and
|
604 |
| - it represents a <a>Partial TD</a> as described in the [[!WOT-ARCHITECTURE]]. As such, it has the same |
| 598 | + it represents a <a>Partial TD</a> as described in the [[!wot-architecture11]]. As such, it has the same |
605 | 599 | structure of a <a>Thing Description</a> but it may omit some information.
|
606 | 600 | The method MUST run the following steps:
|
607 | 601 | <ol>
|
@@ -4114,7 +4108,7 @@ <h3>Discovery Examples</h3>
|
4114 | 4108 | <ul>
|
4115 | 4109 | <li>
|
4116 | 4110 | Implementors of WoT Runtimes that do not implement a Scripting Runtime.
|
4117 |
| - The [[!WOT-ARCHITECTURE]] document provides generic security guidelines |
| 4111 | + The [[!wot-architecture11]] document provides generic security guidelines |
4118 | 4112 | for this group.
|
4119 | 4113 | </li>
|
4120 | 4114 | <li>
|
|
0 commit comments