|
3 | 3 | <head> |
4 | 4 | <meta charset="utf-8" /> |
5 | 5 | <meta name="color-scheme" content="light dark" /> |
6 | | - <title>Web of Things (WoT) Bindings Registry</title> |
| 6 | + <title>Web of Things (WoT) Binding Registry</title> |
7 | 7 | <script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script> |
8 | 8 | <script class="remove"> |
9 | 9 | var respecConfig = { |
10 | | - shortName: "wot-bindings-registry", |
| 10 | + shortName: "wot-binding-registry", |
11 | 11 | specStatus: "ED", |
12 | 12 | copyrightStart: 2025, |
13 | 13 | noLegacyStyle: true, |
|
16 | 16 | group: "wg/wot", |
17 | 17 | charterDisclosureURI: "https://www.w3.org/2004/01/pp-impl/95969/status", |
18 | 18 | wgPublicList: "public-wot-wg", |
19 | | - edDraftURI: "https://w3c.github.io/wot-bindings-registry/", |
20 | | - github: "https://github.com/w3c/wot-bindings-registry", |
21 | | - issueBase: "https://www.github.com/w3c/wot-bindings-registry/issues", |
| 19 | + edDraftURI: "https://w3c.github.io/wot-binding-registry/", |
| 20 | + github: "https://github.com/w3c/wot-binding-registry", |
| 21 | + issueBase: "https://www.github.com/w3c/wot-binding-registry/issues", |
22 | 22 | editors: [ |
23 | 23 | { |
24 | 24 | name: "Ege Korkan", |
|
34 | 34 | data: [ |
35 | 35 | { |
36 | 36 | value: "In the GitHub repository", |
37 | | - href: "https://github.com/w3c/wot-bindings-registry/graphs/contributors" |
| 37 | + href: "https://github.com/w3c/wot-binding-registry/graphs/contributors" |
38 | 38 | } |
39 | 39 | ] |
40 | 40 | }, |
|
43 | 43 | data: [ |
44 | 44 | { |
45 | 45 | value: "We are on GitHub", |
46 | | - href: "https://github.com/w3c/wot-bindings-registry/" |
| 46 | + href: "https://github.com/w3c/wot-binding-registry/" |
47 | 47 | }, |
48 | 48 | { |
49 | 49 | value: "File a bug", |
50 | | - href: "https://github.com/w3c/wot-bindings-registry/issues" |
| 50 | + href: "https://github.com/w3c/wot-binding-registry/issues" |
51 | 51 | } |
52 | 52 | ] |
53 | 53 | } |
@@ -97,7 +97,7 @@ <h2>Introduction</h2> |
97 | 97 | </p> |
98 | 98 |
|
99 | 99 | <p> |
100 | | - As the number of such protocols and media types is vast and tends to change over time, this document defines a flexible mechanism called a Bindings Registry. |
| 100 | + As the number of such protocols and media types is vast and tends to change over time, this document defines a flexible mechanism called a Binding Registry. |
101 | 101 | This document relies on the registry track mechanism of the <a href="https://www.w3.org/policies/process/#registries">W3C Process</a> and extends it to be specific and fit to the purposes of WoT bindings. |
102 | 102 | </p> |
103 | 103 |
|
@@ -150,19 +150,19 @@ <h2>Terminology</h2> |
150 | 150 | A form element in a TD or TM that contains the concrete mapping of the operation to a binding. Thus it is a machine-readable description of how to activate an affordance. |
151 | 151 | </dd> |
152 | 152 | <dt> |
153 | | - <dfn id="dfn-wot-bindings-registry">WoT Bindings Registry</dfn> |
| 153 | + <dfn id="dfn-wot-binding-registry">WoT Binding Registry</dfn> |
154 | 154 | </dt> |
155 | 155 | <dd> |
156 | | - A W3C Registry Track document that contains the <a>WoT Bindings Registry Table</a>, its requirements and possibly other information. See <a href="https://www.w3.org/policies/process/#registry">registry</a> for more information on the definition. |
| 156 | + A W3C Registry Track document that contains the <a>WoT Binding Registry Table</a>, its requirements and possibly other information. See <a href="https://www.w3.org/policies/process/#registry">registry</a> for more information on the definition. |
157 | 157 | </dd> |
158 | 158 | <dt> |
159 | | - <dfn id="dfn-wot-bindings-registry-table">WoT Bindings Registry Table</dfn> |
| 159 | + <dfn id="dfn-wot-binding-registry-table">WoT Binding Registry Table</dfn> |
160 | 160 | </dt> |
161 | 161 | <dd> |
162 | 162 | A list of bindings that are usable in the context of WoT. See <a href="https://www.w3.org/policies/process/#registry-table">registry table</a> for more information. |
163 | 163 | </dd> |
164 | 164 | <dt> |
165 | | - <dfn id="dfn-wot-bindings-registry-definition">WoT Bindings Registry Definition</dfn> |
| 165 | + <dfn id="dfn-wot-binding-registry-definition">WoT Binding Registry Definition</dfn> |
166 | 166 | </dt> |
167 | 167 | <dd> |
168 | 168 | A set of requirements that explain how the registry table is structured and maintained. See <a href="https://www.w3.org/policies/process/#registry-definition">registry definition</a> for more information. |
@@ -299,7 +299,7 @@ <h2>Content of Registry Definition</h2> |
299 | 299 | This pilot exists to test the process and the rules defined in this section. |
300 | 300 | </p> |
301 | 301 |
|
302 | | - <p>A <a href="#dfn-wot-bindings-registry-definition">set of rules</a> extending the <a href="https://www.w3.org/2023/Process-20230612/#reg-def">Registry Definitions from the W3C Process Document</a> can be found below and is structured as follows.</p> |
| 302 | + <p>A <a href="#dfn-wot-binding-registry-definition">set of rules</a> extending the <a href="https://www.w3.org/2023/Process-20230612/#reg-def">Registry Definitions from the W3C Process Document</a> can be found below and is structured as follows.</p> |
303 | 303 |
|
304 | 304 | <ul> |
305 | 305 | <li><a href="#entry-format"></a> |
@@ -355,7 +355,7 @@ <h2>Entry format</h2> |
355 | 355 |
|
356 | 356 | <!-- |
357 | 357 | TODO: These assertions should be moved to the registry definition. |
358 | | - see https://github.com/w3c/wot-bindings-registry/pull/17#discussion_r2267069020 |
| 358 | + see https://github.com/w3c/wot-binding-registry/pull/17#discussion_r2267069020 |
359 | 359 | --> |
360 | 360 | <!-- <ul> |
361 | 361 | <li>In a TD, a binding SHOULD be identifiable by the terms in a form such as <code>href</code>, <code>contentType</code>, <code>subprotocol</code>, or connection information found in the root of the TD.<ul> |
@@ -588,7 +588,7 @@ <h3>Transition</h3> |
588 | 588 | </ul> |
589 | 589 | </li> |
590 | 590 | <li><span class="rfc2119-assertion" id="submission-requirements-test-report-current-state">For the binding to transition to the "Current" state, a <em>Test Report</em> MUST exist.</span> <span class="rfc2119-assertion" id="submission-requirements-test-report-implementation">The <em>Test Report</em> MUST contain at least one implementation of a Consumer</span> (capable of understanding and performing all the operations described in the binding) and one Exposer (capable of handling all the operations and features described in the binding and optionally be able to create a valid TD). Additional implementations can be added even after the transition to the Current.</li> |
591 | | - <li>The exact contents of the Test Report is not decided yet. See <a href="https://github.com/w3c/wot-bindings-registry/issues/3">https://github.com/w3c/wot-bindings-registry/issues/3</a></li> |
| 591 | + <li>The exact contents of the Test Report is not decided yet. See <a href="https://github.com/w3c/wot-binding-registry/issues/3">https://github.com/w3c/wot-binding-registry/issues/3</a></li> |
592 | 592 | <li><span class="rfc2119-assertion" id="submission-requirements-test-report-transition">Submitters MAY call for transition but the custodian can also automatically trigger the process once it is verified that the condition above is reached.</span></li> |
593 | 593 | <li><span class="rfc2119-assertion" id="submission-requirements-test-report-published"><em>Test Reports</em> and related resources SHOULD be published in a git repository.</span> <span class="rfc2119-assertion" id="submission-requirements-test-report-public">The repository SHOULD be public and it MUST be accessible to the reviewers and the custodian.</span></li> |
594 | 594 | <li>Collaboration between the custodian, reviewers, and submitters is highly encouraged, ideally through a Plugfest or another structured testing session where different implementations can be evaluated collectively.</li> |
@@ -650,7 +650,7 @@ <h3>Dependency</h3> |
650 | 650 | <section id="registry"> |
651 | 651 | <h2>Registry</h2> |
652 | 652 |
|
653 | | - <p>The following table defines the <a>WoT Bindings Registry</a> where each entry is a binding. Entries are ordered alphabetically according to their name.</p> |
| 653 | + <p>The following table defines the <a>WoT Binding Registry</a> where each entry is a binding. Entries are ordered alphabetically according to their name.</p> |
654 | 654 |
|
655 | 655 | <p class="note"> |
656 | 656 | The first entry is a placeholder example. It will be deleted once the first real entry is added. You can find the list of bindings that predate the registry mechanism at <a href="https://github.com/w3c/wot-binding-templates/?tab=readme-ov-file#publications">this Readme file</a>. |
|
0 commit comments