change occurance of bindings registry (#2130)

Author: egekorkan

index.html

@@ -150,11 +150,11 @@
             publisher: "W3C",
             date: "July 2021"
           },
-          "WOT-BINDINGS-REGISTRY": {
-            title: "Web of Things (WoT) Bindings Registry",
-            //, href: "https://www.w3.org/TR/wot-bindings-registry/"
-            href: "https://w3c.github.io/wot-bindings-registry/",
-            authors: ["TODO"], //TODO: sync authors
+          "WOT-BINDING-REGISTRY": {
+            title: "Web of Things (WoT) Binding Registry",
+            //, href: "https://www.w3.org/TR/wot-binding-registry/"
+            href: "https://w3c.github.io/wot-binding-registry/",
+            authors: ["Ege Korkan"],
             publisher: "W3C",
             date: "TODO" //TODO: Add publication date
           },
@@ -789,7 +789,7 @@ <h2>Terminology</h2>
         <dt><dfn id="dfn-binding-specification">Binding Specification</dfn></dt>
         <dd>
           A binding specification is a document that specifies a binding for a protocol, a payload format, or both. All
-          bindings follow the rules of the WoT Bindings Registry [[WOT-BINDINGS-REGISTRY]].
+          bindings follow the rules of the WoT Binding Registry [[WOT-BINDING-REGISTRY]].
         </dd>
         <dt><dfn id="dfn-binding-instance">Binding Instance</dfn></dt>
         <dd>
@@ -1513,8 +1513,8 @@ <h2>Data Schema Vocabulary Definitions</h2>
           <p>
             In a TD, concrete data formats are specified in Forms (see <a href="#form"></a>) using content types. When
             the value of a content type in an instance of the Form is <code>application/json</code>, the data schema can
-            be processed directly by JSON Schema processors. Otherwise, entries in Web of Things (WoT) Bindings Registry
-            [[?WOT-BINDINGS-REGISTRY]] define available mappings from data schemas to other content types such as XML
+            be processed directly by JSON Schema processors. Otherwise, entries in Web of Things (WoT) Binding Registry
+            [[?WOT-BINDING-REGISTRY]] define available mappings from data schemas to other content types such as XML
             [[?xml]]. If the content type in an instance of the Form is not <code>application/json</code> and if no
             mapping is defined for the content type, specifying a data schema does not make sense for the content type.
           </p>
@@ -5475,7 +5475,7 @@ <h3>Adding Bindings</h3>
 
         <p>
           With the <a>TD Context Extensions</a> in a Thing Description, the communication metadata can be supplemented
-          via <a>Binding Specifications</a> from the WoT Bindings Registry [[WOT-BINDINGS-REGISTRY]], which are added
+          via <a>Binding Specifications</a> from the WoT Binding Registry [[WOT-BINDING-REGISTRY]], which are added
           through additional <a>Vocabulary Terms</a> serialized into JSON objects representing a
           <code>Form</code> instance. Please see <a href="#bindings"></a> for further information.
         </p>
@@ -5596,7 +5596,7 @@ <h2>Bindings</h2>
         In summary, Bindings enable a Thing Description to be adapted to a specific protocol, data payload formats or
         both in specific ways. This is done through URI Schemes, additional descriptive vocabularies, Thing Models and
         examples that aim to guide the implementors of Things and Consumers alike. This section explains the overall
-        mechanism and gives basic guidance on creating new Bindings. The [[WOT-BINDINGS-REGISTRY]] contains a registry
+        mechanism and gives basic guidance on creating new Bindings. The [[WOT-BINDING-REGISTRY]] contains a registry
         (list) of existing Bindings as well the requirements to follow to register new entries to the registry.
       </p>
 
@@ -5751,7 +5751,7 @@ <h5>Protocol Bindings</h5>
 
           <p>
             In some cases, header options or other parameters of the protocols need to be included. Given that these are
-            highly protocol dependent, please refer to the bindings listed in [[[WOT-BINDINGS-REGISTRY]]]. Additionally,
+            highly protocol dependent, please refer to the bindings listed in [[[WOT-BINDING-REGISTRY]]]. Additionally,
             protocols may have defined Subprotocols that can be used for some interaction types. For example, to receive
             asynchronous notifications using HTTP, some servers may support long polling (<code>longpoll</code>), WebSub
             [[WebSub]] (<code>websub</code>) and Server-Sent Events [[eventsource]] (<code>sse</code>).

index.template.html

@@ -150,11 +150,11 @@
             publisher: "W3C",
             date: "July 2021"
           },
-          "WOT-BINDINGS-REGISTRY": {
-            title: "Web of Things (WoT) Bindings Registry",
-            //, href: "https://www.w3.org/TR/wot-bindings-registry/"
-            href: "https://w3c.github.io/wot-bindings-registry/",
-            authors: ["TODO"], //TODO: sync authors
+          "WOT-BINDING-REGISTRY": {
+            title: "Web of Things (WoT) Binding Registry",
+            //, href: "https://www.w3.org/TR/wot-binding-registry/"
+            href: "https://w3c.github.io/wot-binding-registry/",
+            authors: ["Ege Korkan"],
             publisher: "W3C",
             date: "TODO" //TODO: Add publication date
           },
@@ -789,7 +789,7 @@ <h2>Terminology</h2>
         <dt><dfn id="dfn-binding-specification">Binding Specification</dfn></dt>
         <dd>
           A binding specification is a document that specifies a binding for a protocol, a payload format, or both. All
-          bindings follow the rules of the WoT Bindings Registry [[WOT-BINDINGS-REGISTRY]].
+          bindings follow the rules of the WoT Binding Registry [[WOT-BINDING-REGISTRY]].
         </dd>
         <dt><dfn id="dfn-binding-instance">Binding Instance</dfn></dt>
         <dd>
@@ -1157,8 +1157,8 @@ <h2>Data Schema Vocabulary Definitions</h2>
           <p>
             In a TD, concrete data formats are specified in Forms (see <a href="#form"></a>) using content types. When
             the value of a content type in an instance of the Form is <code>application/json</code>, the data schema can
-            be processed directly by JSON Schema processors. Otherwise, entries in Web of Things (WoT) Bindings Registry
-            [[?WOT-BINDINGS-REGISTRY]] define available mappings from data schemas to other content types such as XML
+            be processed directly by JSON Schema processors. Otherwise, entries in Web of Things (WoT) Binding Registry
+            [[?WOT-BINDING-REGISTRY]] define available mappings from data schemas to other content types such as XML
             [[?xml]]. If the content type in an instance of the Form is not <code>application/json</code> and if no
             mapping is defined for the content type, specifying a data schema does not make sense for the content type.
           </p>
@@ -4169,7 +4169,7 @@ <h3>Adding Bindings</h3>
 
         <p>
           With the <a>TD Context Extensions</a> in a Thing Description, the communication metadata can be supplemented
-          via <a>Binding Specifications</a> from the WoT Bindings Registry [[WOT-BINDINGS-REGISTRY]], which are added
+          via <a>Binding Specifications</a> from the WoT Binding Registry [[WOT-BINDING-REGISTRY]], which are added
           through additional <a>Vocabulary Terms</a> serialized into JSON objects representing a
           <code>Form</code> instance. Please see <a href="#bindings"></a> for further information.
         </p>
@@ -4290,7 +4290,7 @@ <h2>Bindings</h2>
         In summary, Bindings enable a Thing Description to be adapted to a specific protocol, data payload formats or
         both in specific ways. This is done through URI Schemes, additional descriptive vocabularies, Thing Models and
         examples that aim to guide the implementors of Things and Consumers alike. This section explains the overall
-        mechanism and gives basic guidance on creating new Bindings. The [[WOT-BINDINGS-REGISTRY]] contains a registry
+        mechanism and gives basic guidance on creating new Bindings. The [[WOT-BINDING-REGISTRY]] contains a registry
         (list) of existing Bindings as well the requirements to follow to register new entries to the registry.
       </p>
 
@@ -4445,7 +4445,7 @@ <h5>Protocol Bindings</h5>
 
           <p>
             In some cases, header options or other parameters of the protocols need to be included. Given that these are
-            highly protocol dependent, please refer to the bindings listed in [[[WOT-BINDINGS-REGISTRY]]]. Additionally,
+            highly protocol dependent, please refer to the bindings listed in [[[WOT-BINDING-REGISTRY]]]. Additionally,
             protocols may have defined Subprotocols that can be used for some interaction types. For example, to receive
             asynchronous notifications using HTTP, some servers may support long polling (<code>longpoll</code>), WebSub
             [[WebSub]] (<code>websub</code>) and Server-Sent Events [[eventsource]] (<code>sse</code>).