Merge branch 'main' into author-editor-affiliation

Author: acoburn

lws10-core/Discovery.html

@@ -12,28 +12,28 @@ <h4>Data Model</h4>
 
     <ul>
       <li>
-        <dfn>id</dfn> - the <code>id</code> property is REQUIRED. Its value MUST be a URI that identifies the storage.
+        <strong>`id`</strong> - the <code>id</code> property is REQUIRED. Its value MUST be a URI that identifies the storage.
       </li>
       <li>
-        <dfn>type</dfn> - the <code>type</code> property is REQUIRED. Its value MUST be a string that equals
+        <strong>`type`</strong> - the <code>type</code> property is REQUIRED. Its value MUST be a string that equals
         <code>Storage</code> or a set of strings that contains an item equal to <code>Storage</code> (case-sensitive).
       </li>
       <li>
-        <dfn>capability</dfn> - the <code>capability</code> property is OPTIONAL. Its value MUST be a set of
+        <strong>`capability`</strong> - the <code>capability</code> property is OPTIONAL. Its value MUST be a set of
         capabilities, where each capability is described by a map containing the following properties.
         Additional properties MAY be present.
         <ul>
-          <li><dfn>id</dfn> - the <code>id</code> property is OPTIONAL. If present, its value MUST be a URI.</li>
-          <li><dfn>type</dfn> - the <code>type</code> property is REQUIRED. Its value MUST be a string or a set of strings.</li>
+          <li><strong>`id`</strong> - the <code>id</code> property is OPTIONAL. If present, its value MUST be a URI.</li>
+          <li><strong>`type`</strong> - the <code>type</code> property is REQUIRED. Its value MUST be a string or a set of strings.</li>
         </ul>
       </li>
       <li>
-        <dfn>service</dfn> - the <code>service</code> property is REQUIRED. Its value MUST be a set of services,
+        <strong>`service`</strong> - the <code>service</code> property is REQUIRED. Its value MUST be a set of services,
         where each service is described by a map containing the following properties. Additional properties MAY be present.
         <ul>
-          <li><dfn>id</dfn> - the <code>id</code> property is OPTIONAL. If present, its value MUST be a URI.</li>
-          <li><dfn>type</dfn> - the <code>type</code> property is REQUIRED. Its value MUST be a string or a set of strings.</li>
-          <li><dfn>serviceEndpoint</dfn> - the <code>serviceEndpoint</code> property is REQUIRED. Its value MUST be a URI.</li>
+          <li><strong>`id`</strong> - the <code>id</code> property is OPTIONAL. If present, its value MUST be a URI.</li>
+          <li><strong>`type`</strong> - the <code>type</code> property is REQUIRED. Its value MUST be a string or a set of strings.</li>
+          <li><strong>`serviceEndpoint`</strong> - the <code>serviceEndpoint</code> property is REQUIRED. Its value MUST be a URI.</li>
         </ul>
       </li>
     </ul>

lws10-core/Operations/create-resource.md

@@ -14,7 +14,7 @@ The **create resource** operation adds a new [served resource](#dfn-served-resou
 
 **Possible Responses:**
 
-* **Created:** The operation succeeded. The server returns the final identifier of the newly created resource.
+* <strong id="dfn-created">Created:</strong> The operation succeeded. The server returns the final identifier of the newly created resource.
 * **Target Not Found:** The specified target container does not exist.
 * **Not Permitted:** The client's identity is known, but they do not have permission to create resources in this container.
 * **Unknown Requester:** The server does not recognize the client's identity and requires authentication.

lws10-core/Operations/restbinding.md

@@ -1,3 +1,3 @@
 For each core operation (create, read, update, delete), we describe the HTTP method(s) to use, required headers or special considerations (including concurrency controls via ETags, content negotiation, and pagination for container listings), and what the server should do and return. Standard HTTP status codes are used to indicate outcomes with additional mappings for scenarios such as quota exceeded (507 Insufficient Storage) or precondition failures (412 Precondition Failed). The binding tries to adhere to HTTP/1.1 and relevant RFCs (such as [[!RFC7231]] for HTTP semantics, [[!RFC7233]] for range requests, [[!RFC5789]] for PATCH, [[!RFC8288]] for Web Linking, and [[!RFC9264]] for Link Sets) so that it integrates naturally with web standards. Discoverability is emphasized through mechanisms like Link headers and WWW-Authenticate headers on 401 responses, avoiding hardcoded URI locations. Metadata integration is required across operations, ensuring atomicity and use of Link Sets for server-managed and user-managed properties.
 
-**Note:** As all examples in this specifications, examples given in this section (HTTP request and response snippets) are **non-normative**, meant to illustrate typical usage. The actual requirements are stated in the descriptive text and tables. Also, while this binding covers HTTP (as the initial target protocol), the LWS operations could in principle be bound to other protocols in the future. Servers MUST support content negotiation for `application/lws+json`, `application/ld+json`, and `application/json` for container representations (see [Container Media Type](#container-media-type)). Servers MAY additionally support formats like Turtle.
+**Note:** As all examples in this specifications, examples given in this section (HTTP request and response snippets) are **non-normative**, meant to illustrate typical usage. The actual requirements are stated in the descriptive text and tables. Also, while this binding covers HTTP (as the initial target protocol), the LWS operations could in principle be bound to other protocols in the future. Servers MUST support content negotiation for `application/lws+json`, `application/ld+json`, and `application/json` for container representations (see [](#lws-media-type)). Servers MAY additionally support formats like Turtle.