From 59bb2a3522716ba0241a0883acae5ac41008481a Mon Sep 17 00:00:00 2001
From: Alex Tweeddale <alex.tweeddale@gmail.com>
Date: Tue, 18 Jun 2024 10:13:42 +0000
Subject: [PATCH] chore(rebuild): Fixed all formatting issues

I went and fixed all the bikeshed formatting issues, converting markdown to HTML where necessary

SHA: 85018787f8d0f494155edacfbb3215df47e722f7
Reason: push, by @Tweeddalex

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
---
 index.html | 369 ++++++++++++++++++++++++++++++++---------------------
 1 file changed, 225 insertions(+), 144 deletions(-)

diff --git a/index.html b/index.html
index 9a5996e..ee2f33b 100644
--- a/index.html
+++ b/index.html
@@ -8,7 +8,7 @@
   <meta content="Bikeshed version 82ce88815, updated Thu Sep 7 16:33:55 2023 -0700" name="generator">
   <link href="https://w3c-ccg.github.io/did-linked-resources" rel="canonical">
   <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
-  <meta content="5ee1d513badae8de296aae655c3eb7b913b5d09c" name="document-revision">
+  <meta content="85018787f8d0f494155edacfbb3215df47e722f7" name="document-revision">
 <style>/* Boilerplate: style-autolinks */
 .css.css, .property.property, .descriptor.descriptor {
     color: var(--a-normal-text);
@@ -599,9 +599,9 @@ <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
       <li>
        <a href="#rules-and-logic-for-handling-ambiguous-queries"><span class="secno">10.4</span> <span class="content">Rules and logic for handling ambiguous queries</span></a>
        <ol class="toc">
-        <li><a href="#ambiguity-generally-throws-an-error"><span class="secno">10.4.1</span> <span class="content">**Ambiguity generally throws an error** ###</span></a>
-        <li><a href="#multiple-versions-of-the-same-resource"><span class="secno">10.4.2</span> <span class="content">**Multiple versions of the same resource** ###</span></a>
-        <li><a href="#ambiguity--resourcemetadatatrue"><span class="secno">10.4.3</span> <span class="content">**Ambiguity + resourceMetadata=true** ###</span></a>
+        <li><a href="#ambiguity-generally-throws-an-error"><span class="secno">10.4.1</span> <span class="content">Ambiguity generally throws an error</span></a>
+        <li><a href="#multiple-versions-of-the-same-resource"><span class="secno">10.4.2</span> <span class="content">Multiple versions of the same resource</span></a>
+        <li><a href="#ambiguity--resourcemetadatatrue"><span class="secno">10.4.3</span> <span class="content">Ambiguity + resourceMetadata=true</span></a>
        </ol>
      </ol>
     <li>
@@ -650,8 +650,9 @@ <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
   <main>
    <h2 class="heading settled" data-level="1" id="intro"><span class="secno">1. </span><span class="content">Introduction</span><a class="self-link" href="#intro"></a></h2>
    <p>DID-Linked Resources are digital files that can be retrieved and referenced using a persistent and unique DID URL.</p>
-   <p>This specification defines common requirements, algorithms including their request formats and response formats, architectural options, and various considerations for how DID-Linked Resources SHOULD act as persistent identifiers for referencing and retrieving digital Resources (such as data schemas, status lists, trust registries, governance documents, or policy definitions). This specification complements the [DID Resolution Specification](https://w3c-ccg.github.io/did-resolution/), including its patterns and algorithms for DID URL resolution and dereferencing. By using DID URLs which remain conformant with W3C Decentralized Identifiers (DIDs) v1.0 Recommendation <a data-link-type="biblio" href="#biblio-did-core" title="Decentralized Identifiers (DIDs) v1.0">[DID-CORE]</a> and the [DID Resolution Specification](https://w3c-ccg.github.io/did-resolution/), existing DID Resolvers will be able to dereference these DID URLs to retrieve the identified resources using the DID URL query syntax in this specification.</p>
-   <p>_**Note:** While this specification defines some base-level functionality for DID URL dereferencing, the actual steps required to communicate with a DID’s verifiable data registry are defined by the applicable DID method specification.</p>
+   <p>This specification defines common requirements, algorithms including their request formats and response formats, architectural options, and various considerations for how DID-Linked Resources SHOULD act as persistent identifiers for referencing and retrieving digital Resources (such as data schemas, status lists, trust registries, governance documents, or policy definitions). This specification complements the <a href="https://w3c-ccg.github.io/did-resolution/">DID Resolution Specification</a>, including its patterns and algorithms for DID URL resolution and dereferencing.</p>
+   <p>By using DID URLs which remain conformant with W3C Decentralized Identifiers (DIDs) v1.0 Recommendation <a data-link-type="biblio" href="#biblio-did-core" title="Decentralized Identifiers (DIDs) v1.0">[DID-CORE]</a> and the <a href="https://w3c-ccg.github.io/did-resolution/">DID Resolution Specification</a>, existing DID Resolvers will be able to dereference these DID URLs to retrieve the identified resources using the DID URL query syntax in this specification.</p>
+   <p><b>Note:</b> while this specification defines some base-level functionality for DID URL dereferencing, the actual steps required to communicate with a DID’s verifiable data registry are defined by the applicable DID method specification.</p>
    <h3 class="heading settled" data-level="1.1" id="conformance"><span class="secno">1.1. </span><span class="content">Conformance</span><a class="self-link" href="#conformance"></a></h3>
    <p>In addition to sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
 The key words MAY, MUST, MUST NOT, OPTIONAL, and SHOULD in this document are to be interpreted as described in BCP 14 <a data-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a> <a data-link-type="biblio" href="#biblio-rfc8174" title="Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words">[RFC8174]</a> when, and only when, they appear in all capitals, as shown here.</p>
@@ -664,20 +665,20 @@ <h2 class="heading settled" data-level="2" id="terminology"><span class="secno">
    <p><dfn data-dfn-type="dfn" data-noexport id="resource-collection">Resource Collection<a class="self-link" href="#resource-collection"></a></dfn>: An organized and structured set of digital resources, collectively and individually identifiable using persistent and unique DID URLs.</p>
    <p><dfn data-dfn-type="dfn" data-noexport id="resource-id">Resource ID<a class="self-link" href="#resource-id"></a></dfn>: A unique identifier for a specified DID-Linked Resource.</p>
    <h2 class="heading settled" data-level="3" id="resources"><span class="secno">3. </span><span class="content">DID-Linked Resources</span><a class="self-link" href="#resources"></a></h2>
+   <p>This section explains the context for building DID-Linked Resources, as well as their fundamental components for construction.</p>
    <h3 class="heading settled" data-level="3.1" id="context"><span class="secno">3.1. </span><span class="content">DID-Linked Resources context</span><a class="self-link" href="#context"></a></h3>
-   <p>The [[DID Core]] specification defines an interoperable standard for DID documents and associated core properties, however it does not currently have a standardized way to specify properties of Resources associated with DIDs, nor how to consistently reference nor retrieve them.</p>
-   <p>Digital Resources are _generally_ stored on traditional centralized-storage endpoints, but this comes with certain drawbacks:</p>
+   <p>The <a data-link-type="biblio" href="#biblio-did-core" title="Decentralized Identifiers (DIDs) v1.0">[DID-CORE]</a> specification defines an interoperable standard for DID documents and associated core properties, however it does not currently have a standardized way to specify properties of Resources associated with DIDs, nor how to consistently reference nor retrieve them.</p>
+   <p>Digital Resources are generally stored on traditional centralized-storage endpoints, but this comes with certain drawbacks:</p>
    <ol>
     <li data-md>
-     <p>**Digital Resources could be tampered with by compromising the hosting provider**: Digital Resources stored at a centralized web endpoint can be compromised and replaced by malicious actors.</p>
+     <p><b>Digital Resources could be tampered with by compromising the hosting provider</b>: Digital Resources stored at a centralized web endpoint can be compromised and replaced by malicious actors.</p>
     <li data-md>
-     <p>**Hosting providers could unilaterally cease to host particular clients**: Hosting providers could terminate accounts due to factors such as non-payment of fees, violation of Terms of Service, etc.</p>
+     <p><b>Hosting providers could unilaterally cease to host particular clients</b>: Hosting providers could terminate accounts due to factors such as non-payment of fees, violation of Terms of Service, etc.</p>
     <li data-md>
-     <p>**[Single point of failure (SPOF)](https://dbpedia.org/resource/Single_point_of_failure) in resiliency**: Even with highly-trusted and sophisticated hosting providers who may not present a risk of infrastructure being compromised, a service outage at the hosting provider can make a Resource anchored on their systems inaccessible.</p>
+     <p><b><a href="https://dbpedia.org/resource/Single_point_of_failure">Single point of failure (SPOF)</a></b>: Even with highly-trusted and sophisticated hosting providers who may not present a risk of infrastructure being compromised, a service outage at the hosting provider can make a Resource anchored on their systems inaccessible.</p>
    </ol>
-   <p>Despite these issues, many decentralized identity or Digital Credential implementations, _even ones that use ledgers or other distributed systems for DIDs_, often utilize centralized storage. From the [W3C Verifiable Credential Implementation Guide](https://w3c.github.io/vc-imp-guide/#creating-new-credential-types):</p>
-   <blockquote>
-    <p>Example schema.org address with full URLs:</p>
+   <p>Despite these issues, many decentralized identity or Digital Credential implementations, even ones that use ledgers or other distributed systems for DIDs, often utilize centralized storage. From the <a href="https://w3c.github.io/vc-imp-guide/#creating-new-credential-types">W3C Verifiable Credential Implementation Guide</a>.</p>
+   <p>Example schema.org address with full URLs:</p>
 <pre class="language-json highlight"><c- p>{</c->
   <c- f>"@type"</c-><c- p>:</c-> <c- u>"http://schema.org/Person"</c-><c- p>,</c->
   <c- f>"http://schema.org/address"</c-><c- p>:</c-> <c- p>{</c->
@@ -690,22 +691,25 @@ <h3 class="heading settled" data-level="3.1" id="context"><span class="secno">3.
   <c- p>}</c->
 <c- p>}</c->
 </pre>
-   </blockquote>
    <p>Using traditional web endpoints to store digital resources that are critical for a Verifiable Credential to function, detracts from the proper functioning and utility that persistently-accessible Decentralized Identifiers offer. This has also resulted in inconsistent and unstandardized approaches to storing, referencing, and retrieving digital resources such as schemas, trusted issuer lists and status lists.</p>
    <h3 class="heading settled" data-level="3.2" id="contruction"><span class="secno">3.2. </span><span class="content">DID-Linked Resources construction</span><a class="self-link" href="#contruction"></a></h3>
    <p>"Resources" SHOULD be identifiable using a Decentralized Identifier (DID) and a Universally Unique Identifier (UUID) that acts as a permanently-accessible identifier to fetch the Resource from a Verifiable Data Registry or other storage endpoint. We refer to this UUID as the "Resource ID".</p>
    <p>Using UUIDs ensures a high level of confidence that no two identical Resource IDs will ever be created. This is important for ensuring the integrity and unambiguity of each individual DID-Linked Resource.</p>
    <p>The following path-based syntax is an example of how a DID Method may construct a DID URL to point to a DID-Linked Resource:</p>
-   <p>`did:example:<unique-identifier>/resources/<universally-unique-identifier>`</universally-unique-identifier></unique-identifier></p>
-   <p>_**Note:** The above path-based syntax would be an implementation-specific way of referencing a resource._</p>
+<pre class="language-json highlight">did<c- p>:</c->example<c- p>:</c->&lt;u<c- kc>n</c->ique<c- mi>-</c->ide<c- kc>nt</c->i<c- kc>f</c->ier>/resources/&lt;u<c- kc>n</c->iversally<c- mi>-</c->u<c- kc>n</c->ique<c- mi>-</c->ide<c- kc>nt</c->i<c- kc>f</c->ier>
+</pre>
+   <p><b>Note:</b> The above path-based syntax would be an implementation-specific way of referencing a resource.</p>
    <h3 class="heading settled" data-level="3.3" id="collections"><span class="secno">3.3. </span><span class="content">DID-Linked Resource Collections</span><a class="self-link" href="#collections"></a></h3>
    <p>Resources are organized into groups or sets called "Collections". Each DID may have an associated Collection, and the Collection ID is derived from the unique identifier of the DID.</p>
    <p>The most important concept used in this design is that each Collection is identified using a DID and is described using a DID document.</p>
    <p>The DID document acts as metadata, providing information about the Collection, such as who is able to update it, when it was created, and what are the latest and/or deprecated versions of Resources within the Collection.
 For example, the following DID:</p>
-   <p>`did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d`</p>
-   <p>will derive the Collection ID: `0a5b94d0-a417-48ed-a6f5-4abc9e95888d`</p>
-   <p>_**Note:** The Collection ID may take the syntactical form of the DID method that the DID-Linked Resource is associated with._</p>
+<pre class="language-json highlight">did<c- p>:</c->example<c- p>:</c-><c- mi>0</c->a<c- mi>5</c->b<c- mi>94</c->d<c- mi>0-</c->a<c- mf>417-48e</c->d<c- mi>-</c->a<c- mi>6</c-><c- kc>f</c-><c- mi>5-4</c->abc<c- mf>9e95888</c->d
+</pre>
+   <p>will derive the Collection ID:</p>
+<pre class="language-json highlight"><c- mi>0</c->a<c- mi>5</c->b<c- mi>94</c->d<c- mi>0-</c->a<c- mf>417-48e</c->d<c- mi>-</c->a<c- mi>6</c-><c- kc>f</c-><c- mi>5-4</c->abc<c- mf>9e95888</c->d
+</pre>
+   <p><b>Note:</b> The Collection ID may take the syntactical form of the DID method that the DID-Linked Resource is associated with.</p>
    <h2 class="heading settled" data-level="4" id="algorithm"><span class="secno">4. </span><span class="content">DID-Linked Resources Algorithm</span><a class="self-link" href="#algorithm"></a></h2>
    <p>To create a "DID-Linked Resource", you MUST first create a "parent" DID, from which the Collection ID can be derived, and under which the associated Resources will be linked.</p>
    <p>Next, to create a digital Resource associated with the "parent" DID, you MUST provide the following Request inputs:</p>
@@ -724,77 +728,74 @@ <h2 class="heading settled" data-level="4" id="algorithm"><span class="secno">4.
      <p>Sign the transaction using the same Verification Method keys as those within the parent DID Document.</p>
    </ol>
    <p>As a response, the DID Document SHOULD append metadata about the DID-Linked Resource into the existing DID Document Metadata.</p>
-   <blockquote>
 <pre class="language-json highlight"><c- p>{</c->
-<c- f>"@context"</c-><c- p>:</c-> <c- u>"https://w3id.org/did-resolution/v1"</c-><c- p>,</c->
-<c- f>"didResolutionMetadata"</c-><c- p>:</c-> <c- p>{</c->
-<c- f>"contentType"</c-><c- p>:</c-> <c- u>"application/did+ld+json"</c-><c- p>,</c->
-<c- f>"retrieved"</c-><c- p>:</c-> <c- u>"2023-06-23T11:21:20Z"</c-><c- p>,</c->
-<c- f>"did"</c-><c- p>:</c-> <c- p>{</c->
-<c- f>"didString"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c-><c- p>,</c->
-<c- f>"methodSpecificId"</c-><c- p>:</c-> <c- u>"0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c-><c- p>,</c->
-<c- f>"method"</c-><c- p>:</c-> <c- u>"example"</c->
-<c- p>}</c->
-<c- p>},</c->
-<c- f>"didDocument"</c-><c- p>:</c-> <c- p>{</c->
-<c- f>"@context"</c-><c- p>:</c-> <c- p>[</c->
-<c- u>"https://www.w3.org/ns/did/v1"</c-><c- p>,</c->
-<c- u>"https://w3id.org/security/suites/ed25519-2020/v1"</c->
-<c- p>],</c->
-<c- f>"id"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c-><c- p>,</c->
-<c- f>"controller"</c-><c- p>:</c-> <c- p>[</c->
-<c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c->
-<c- p>],</c->
-<c- f>"verificationMethod"</c-><c- p>:</c-> <c- p>[</c->
-<c- p>{</c->
-<c- f>"id"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d#key-1"</c-><c- p>,</c->
-<c- f>"type"</c-><c- p>:</c-> <c- u>"Ed25519VerificationKey2020"</c-><c- p>,</c->
-<c- f>"controller"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c-><c- p>,</c->
-<c- f>"publicKeyMultibase"</c-><c- p>:</c-> <c- u>"z6Mkphkdz97NJXYSbj7eGDkWR242kP58LEEkVrSseTtAzbWE"</c->
-<c- p>}</c->
-<c- p>],</c->
-<c- f>"authentication"</c-><c- p>:</c-> <c- p>[</c->
-<c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d#key-1"</c->
-<c- p>],</c->
-<c- f>"service"</c-><c- p>:</c-> <c- p>[</c->
-<c- p>{</c->
-<c- f>"id"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d#website"</c-><c- p>,</c->
-<c- f>"type"</c-><c- p>:</c-> <c- u>"LinkedDomains"</c-><c- p>,</c->
-<c- f>"serviceEndpoint"</c-><c- p>:</c-> <c- p>[</c->
-<c- u>"https://foo.com"</c->
-<c- p>]</c->
-<c- p>}</c->
-<c- p>]</c->
-<c- p>},</c->
-<c- f>"didDocumentMetadata"</c-><c- p>:</c-> <c- p>{</c->
-<c- f>"created"</c-><c- p>:</c-> <c- u>"2023-03-22T07:19:47Z"</c-><c- p>,</c->
-<c- f>"versionId"</c-><c- p>:</c-> <c- u>"15be3e0f-12e9-4c26-9b60-a02bf5746313"</c-><c- p>,</c->
-<c- f>"linkedResourceMetadata"</c-><c- p>:</c-> <c- p>[</c->
-<c- p>{</c->
-<c- f>"resourceURI"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d/resources/4e1104f9-2ee9-4bde-adc2-ab8ba72b124a"</c-><c- p>,</c->
-<c- f>"resourceCollectionId"</c-><c- p>:</c-> <c- u>"0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c-><c- p>,</c->
-<c- f>"resourceId"</c-><c- p>:</c-> <c- u>"4e1104f9-2ee9-4bde-adc2-ab8ba72b124a"</c-><c- p>,</c->
-<c- f>"resourceName"</c-><c- p>:</c-> <c- u>"ExampleResource"</c-><c- p>,</c->
-<c- f>"resourceType"</c-><c- p>:</c-> <c- u>"StatusList2021Revocation"</c-><c- p>,</c->
-<c- f>"mediaType"</c-><c- p>:</c-> <c- u>"application/json"</c-><c- p>,</c->
-<c- f>"resourceVersion"</c-><c- p>:</c-> <c- u>""</c-><c- p>,</c->
-<c- f>"created"</c-><c- p>:</c-> <c- u>"2023-03-24T12:13:45Z"</c-><c- p>,</c->
-<c- f>"checksum"</c-><c- p>:</c-> <c- u>"6819aaecd4073173b159fedf8077c38e14939d03d58e7f4e2a0ddfe034eb2ed4"</c-><c- p>,</c->
-<c- f>"previousVersionId"</c-><c- p>:</c-> <c- kc>null</c-><c- p>,</c->
-<c- f>"nextVersionId"</c-><c- p>:</c-> <c- kc>null</c->
-<c- p>}</c->
-<c- p>]</c->
-<c- p>}</c->
+  <c- f>"@context"</c-><c- p>:</c-> <c- u>"https://w3id.org/did-resolution/v1"</c-><c- p>,</c->
+  <c- f>"didResolutionMetadata"</c-><c- p>:</c-> <c- p>{</c->
+    <c- f>"contentType"</c-><c- p>:</c-> <c- u>"application/did+ld+json"</c-><c- p>,</c->
+    <c- f>"retrieved"</c-><c- p>:</c-> <c- u>"2023-06-23T11:21:20Z"</c-><c- p>,</c->
+    <c- f>"did"</c-><c- p>:</c-> <c- p>{</c->
+      <c- f>"didString"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c-><c- p>,</c->
+      <c- f>"methodSpecificId"</c-><c- p>:</c-> <c- u>"0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c-><c- p>,</c->
+      <c- f>"method"</c-><c- p>:</c-> <c- u>"example"</c->
+    <c- p>}</c->
+  <c- p>},</c->
+  <c- f>"didDocument"</c-><c- p>:</c-> <c- p>{</c->
+    <c- f>"@context"</c-><c- p>:</c-> <c- p>[</c->
+      <c- u>"https://www.w3.org/ns/did/v1"</c-><c- p>,</c->
+      <c- u>"https://w3id.org/security/suites/ed25519-2020/v1"</c->
+    <c- p>],</c->
+    <c- f>"id"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c-><c- p>,</c->
+    <c- f>"controller"</c-><c- p>:</c-> <c- p>[</c->
+      <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c->
+    <c- p>],</c->
+    <c- f>"verificationMethod"</c-><c- p>:</c-> <c- p>[</c->
+      <c- p>{</c->
+        <c- f>"id"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d#key-1"</c-><c- p>,</c->
+        <c- f>"type"</c-><c- p>:</c-> <c- u>"Ed25519VerificationKey2020"</c-><c- p>,</c->
+        <c- f>"controller"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c-><c- p>,</c->
+        <c- f>"publicKeyMultibase"</c-><c- p>:</c-> <c- u>"z6Mkphkdz97NJXYSbj7eGDkWR242kP58LEEkVrSseTtAzbWE"</c->
+      <c- p>}</c->
+    <c- p>],</c->
+    <c- f>"authentication"</c-><c- p>:</c-> <c- p>[</c->
+      <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d#key-1"</c->
+    <c- p>],</c->
+    <c- f>"service"</c-><c- p>:</c-> <c- p>[</c->
+      <c- p>{</c->
+        <c- f>"id"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d#website"</c-><c- p>,</c->
+        <c- f>"type"</c-><c- p>:</c-> <c- u>"LinkedDomains"</c-><c- p>,</c->
+        <c- f>"serviceEndpoint"</c-><c- p>:</c-> <c- p>[</c->
+          <c- u>"https://foo.com"</c->
+        <c- p>]</c->
+      <c- p>}</c->
+    <c- p>]</c->
+  <c- p>},</c->
+  <c- f>"didDocumentMetadata"</c-><c- p>:</c-> <c- p>{</c->
+    <c- f>"created"</c-><c- p>:</c-> <c- u>"2023-03-22T07:19:47Z"</c-><c- p>,</c->
+    <c- f>"versionId"</c-><c- p>:</c-> <c- u>"15be3e0f-12e9-4c26-9b60-a02bf5746313"</c-><c- p>,</c->
+    <c- f>"linkedResourceMetadata"</c-><c- p>:</c-> <c- p>[</c->
+      <c- p>{</c->
+        <c- f>"resourceURI"</c-><c- p>:</c-> <c- u>"did:example:0a5b94d0-a417-48ed-a6f5-4abc9e95888d/resources/4e1104f9-2ee9-4bde-adc2-ab8ba72b124a"</c-><c- p>,</c->
+        <c- f>"resourceCollectionId"</c-><c- p>:</c-> <c- u>"0a5b94d0-a417-48ed-a6f5-4abc9e95888d"</c-><c- p>,</c->
+        <c- f>"resourceId"</c-><c- p>:</c-> <c- u>"4e1104f9-2ee9-4bde-adc2-ab8ba72b124a"</c-><c- p>,</c->
+        <c- f>"resourceName"</c-><c- p>:</c-> <c- u>"ExampleResource"</c-><c- p>,</c->
+        <c- f>"resourceType"</c-><c- p>:</c-> <c- u>"StatusList2021Revocation"</c-><c- p>,</c->
+        <c- f>"mediaType"</c-><c- p>:</c-> <c- u>"application/json"</c-><c- p>,</c->
+        <c- f>"resourceVersion"</c-><c- p>:</c-> <c- u>""</c-><c- p>,</c->
+        <c- f>"created"</c-><c- p>:</c-> <c- u>"2023-03-24T12:13:45Z"</c-><c- p>,</c->
+        <c- f>"checksum"</c-><c- p>:</c-> <c- u>"6819aaecd4073173b159fedf8077c38e14939d03d58e7f4e2a0ddfe034eb2ed4"</c-><c- p>,</c->
+        <c- f>"previousVersionId"</c-><c- p>:</c-> <c- kc>null</c-><c- p>,</c->
+        <c- f>"nextVersionId"</c-><c- p>:</c-> <c- kc>null</c->
+      <c- p>}</c->
+    <c- p>]</c->
+  <c- p>}</c->
 <c- p>}</c->
 </pre>
-   </blockquote>
    <h2 class="heading settled" data-level="5" id="linkage"><span class="secno">5. </span><span class="content">Linking DIDs to Resources and Collections</span><a class="self-link" href="#linkage"></a></h2>
    <p>Multiple Resources can be stored within a Collection and linked to the same DID; for example, this could be new versions of the same Resource over a period of time, or entirely different resources. This enables unique resources to be stored directly on a Verifiable Data Registry (VDR) and be retrievable through DID resolution and DID URL dereferencing.</p>
    <p>Once you have created a resource, the DID document will automatically reference the resource and the collection within the `didDocumentMetadata` in a newly defined section called `linkedResourceMetadata`.</p>
-   <p>This relationship is shown in the diagram below:</p>
-   <p><img alt="Relationship between DIDs and DID-Linked Resources" src="DID-Linked-Resources-Relationship"></p>
    <h2 class="heading settled" data-level="6" id="archoverview"><span class="secno">6. </span><span class="content">Architecture Overview</span><a class="self-link" href="#archoverview"></a></h2>
-   <p><img alt="DID-Linked Resources Architecture Overview" src="DID-Linked-Resources-Relationship"></p>
+   <p>The relationship between DIDs, Resource Collections and Resources is shown in the diagram below:</p>
+   <p><img alt="DID-Linked Resources Architecture Overview" src="DID-Linked-Resources-Relationship.png"></p>
    <h2 class="heading settled" data-level="7" id="principles"><span class="secno">7. </span><span class="content">Design principles</span><a class="self-link" href="#principles"></a></h2>
    <p>The following design principles should be taken into consideration. DID-Linked Resources SHOULD:</p>
    <ol>
@@ -811,31 +812,86 @@ <h2 class="heading settled" data-level="7" id="principles"><span class="secno">7
    </ol>
    <h2 class="heading settled" data-level="8" id="request"><span class="secno">8. </span><span class="content">Resource Request Parameters</span><a class="self-link" href="#request"></a></h2>
    <p>The following list defines which specific parameters are required and are optional for a request to create a resource:</p>
-   <p>| Parameter                 | Type                                                          | Required?    |
-| ------------------------- | ------------------------------------------------------------- | ----------- | 
-| `"resourceCollectionId"`  | A [String](https://infra.spec.whatwg.org/#string) that conforms to a unique identifier format for an associated DID method         | Yes    |
-| `"resourceId"`            | A [String](https://infra.spec.whatwg.org/#string), such as a UUID, that uniquely identifies the resource              | Yes    |
-| `"resourceName"`          | A [String](https://infra.spec.whatwg.org/#string) that names and identifies a resource. This property, along with the `resourceType` below, can be used to track version changes within a resource              | Yes    |
-| `"resourceType"`          | A [String](https://infra.spec.whatwg.org/#string), such as a UUID, that uniquely identifies the resource              | Yes    |
-| `"resourceVersion"`       | A [String](https://infra.spec.whatwg.org/#string) identifies the type of resource. This property, along with the `resourceName` above, can be used to track version changes within a resource               | No    |
-| `"alsoKnownAs"`           | An [array](https://infra.spec.whatwg.org/#array) that describes alternative URIs for the resource                    | No    |</p>
+   <table>
+    <thead>
+     <tr>
+      <th>Parameter
+      <th>Type
+      <th>Required?
+    <tbody>
+     <tr>
+      <td><code>"resourceCollectionId"</code>
+      <td>A <a href="https://infra.spec.whatwg.org/#string">String</a> that conforms to a unique identifier format for an associated DID method
+      <td>Yes
+     <tr>
+      <td><code>"resourceId"</code>
+      <td>A <a href="https://infra.spec.whatwg.org/#string">String</a>, such as a UUID, that uniquely identifies the resource
+      <td>Yes
+     <tr>
+      <td><code>"resourceName"</code>
+      <td>A <a href="https://infra.spec.whatwg.org/#string">String</a> that names and identifies a resource. This property, along with the <code>resourceType</code> below, can be used to track version changes within a resource
+      <td>Yes
+     <tr>
+      <td><code>"resourceType"</code>
+      <td>A <a href="https://infra.spec.whatwg.org/#string">String</a> that uniquely identifies the type of resource
+      <td>Yes
+     <tr>
+      <td><code>"resourceVersion"</code>
+      <td>A <a href="https://infra.spec.whatwg.org/#string">String</a> that identifies the version of the resource. This property, along with the <code>resourceName</code> above, can be used to track version changes within a resource
+      <td>No
+     <tr>
+      <td><code>"alsoKnownAs"</code>
+      <td>An <a href="https://infra.spec.whatwg.org/#array">array</a> that describes alternative URIs for the resource
+      <td>No
+   </table>
    <h2 class="heading settled" data-level="9" id="response"><span class="secno">9. </span><span class="content">Resource Response Parameters</span><a class="self-link" href="#response"></a></h2>
    <p>The following list defines which specific parameters are required and which are optional for a response, following the creation of a Resource:</p>
-   <p>| Parameter | Description |
-| :--- | :--- |
-| **`resourceUri`** | A string or a map that conforms to the rules of <a data-link-type="biblio" href="#biblio-rfc3986" title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</a> URIs which SHOULD directly lead to a location where the resource can be accessed. For example: `did:example:46e2af9a-2ea0-4815-999d-730a6778227c/resources/0f964a80-5d18-4867-83e3-b47f5a756f02`.   |
-| **`resourceCollectionId`** | A string that conforms to a method-specific supported unique identifier format. For example, a UUID: `46e2af9a-2ea0-4815-999d-730a6778227c`.  |
-| **`resourceId`** | A string that uniquely identifies the resource. For example, a UUID: `0f964a80-5d18-4867-83e3-b47f5a756f02`. |
-| **`resourceName`** | A string that uniquely names and identifies a resource. This property, along with the `resourceType` below, can be used to track version changes within a resource. |
-| **`resourceType`** | A string that identifies the type of resource. This property, along with the `resourceName` above, can be used to track version changes within a resource. Not to be confused with `mediaType`. |
-| **`resourceVersion`** | (Optional) A string that identifies the version of the resource. This property is provided by the client and can be any value. |
-| **`alsoKnownAs`** | (Optional) An array that describes alternative URIs for the  resource. |
-| **`mediaType`** | A string that identifies the IANA-media type of the resource. |
-| **`created`** | A string that identifies the time the resource was created, as an XML date-time. |
-| **`updated`** | (Optional) A string that identifies the time the resource was updated, as an XML date-time. |
-| **`checksum`** | A string that may be used to prove that the resource has not been tampered with. |
-| **`previousVersionId`** | (Optional) A string that identifies the previous version of the resource. |
-| **`nextVersionId`** | (Optional) A string that identifies the next version of the resource. |</p>
+   <table>
+    <thead>
+     <tr>
+      <th>Parameter
+      <th>Description
+    <tbody>
+     <tr>
+      <td><strong><code>resourceUri</code></strong>
+      <td>A string or a map that conforms to the rules of <a href="https://tools.ietf.org/html/rfc3986" target="_blank">RFC3986</a> URIs which SHOULD directly lead to a location where the resource can be accessed. For example: <code>did:example:46e2af9a-2ea0-4815-999d-730a6778227c/resources/0f964a80-5d18-4867-83e3-b47f5a756f02</code>.
+     <tr>
+      <td><strong><code>resourceCollectionId</code></strong>
+      <td>A string that conforms to a method-specific supported unique identifier format. For example, a UUID: <code>46e2af9a-2ea0-4815-999d-730a6778227c</code>.
+     <tr>
+      <td><strong><code>resourceId</code></strong>
+      <td>A string that uniquely identifies the resource. For example, a UUID: <code>0f964a80-5d18-4867-83e3-b47f5a756f02</code>.
+     <tr>
+      <td><strong><code>resourceName</code></strong>
+      <td>A string that uniquely names and identifies a resource. This property, along with the <code>resourceType</code> below, can be used to track version changes within a resource.
+     <tr>
+      <td><strong><code>resourceType</code></strong>
+      <td>A string that identifies the type of resource. This property, along with the <code>resourceName</code> above, can be used to track version changes within a resource. Not to be confused with <code>mediaType</code>.
+     <tr>
+      <td><strong><code>resourceVersion</code></strong>
+      <td>(Optional) A string that identifies the version of the resource. This property is provided by the client and can be any value.
+     <tr>
+      <td><strong><code>alsoKnownAs</code></strong>
+      <td>(Optional) An array that describes alternative URIs for the resource.
+     <tr>
+      <td><strong><code>mediaType</code></strong>
+      <td>A string that identifies the IANA-media type of the resource.
+     <tr>
+      <td><strong><code>created</code></strong>
+      <td>A string that identifies the time the resource was created, as an XML date-time.
+     <tr>
+      <td><strong><code>updated</code></strong>
+      <td>(Optional) A string that identifies the time the resource was updated, as an XML date-time.
+     <tr>
+      <td><strong><code>checksum</code></strong>
+      <td>A string that may be used to prove that the resource has not been tampered with.
+     <tr>
+      <td><strong><code>previousVersionId</code></strong>
+      <td>(Optional) A string that identifies the previous version of the resource.
+     <tr>
+      <td><strong><code>nextVersionId</code></strong>
+      <td>(Optional) A string that identifies the next version of the resource.
+   </table>
    <h3 class="heading settled" data-level="9.1" id="discoverability"><span class="secno">9.1. </span><span class="content">Discoverability via DIDDoc Metadata</span><a class="self-link" href="#discoverability"></a></h3>
    <p>Once a Resource has been created under a Resource Collection, the parent DID document will automatically have an updated `didDocumentMetadata` section, including `linkedResourceMetadata`.</p>
    <p>The syntax of the linked Resource metadata is as follows:</p>
@@ -876,7 +932,7 @@ <h3 class="heading settled" data-level="9.1" id="discoverability"><span class="s
       <c- p>]</c->
     <c- p>}</c->
 </pre>
-   <p>Importantly, we decided not to populate the `didDocumentMetadata` with the actual resource data, but instead, populate what we refer to as a _Resource Preview_ which contains all the metadata about the associated resources.</p>
+   <p>Importantly, we decided not to populate the `didDocumentMetadata` with the actual resource data, but instead, populate what we refer to as a <b>Resource Preview</b> which contains all the metadata about the associated resources.</p>
    <h3 class="heading settled" data-level="9.2" id="preview"><span class="secno">9.2. </span><span class="content">Composition of Resource Preview</span><a class="self-link" href="#preview"></a></h3>
    <p>Resource previews will appear within DID document metadata. These do not include the actual core data of the resource and only reference the metadata:</p>
    <ul>
@@ -936,35 +992,62 @@ <h3 class="heading settled" data-level="10.2" id="dereferencing"><span class="se
     <li data-md>
      <p>A DID is resolved to a DID Document;</p>
     <li data-md>
-     <p>A resource within / associated with the DID Document is identified, based on the portion of the DID URL that follows the DID (path, query, fragment as defined by the ABNF in section 3.2 of the DID 1.0 specification.).</p>
+     <p>A resource within / associated with the DID Document is identified, based on the portion of the DID URL that follows the DID (path, query, fragment as defined by the ABNF in section 3.2 of the <a data-link-type="biblio" href="#biblio-did-core" title="Decentralized Identifiers (DIDs) v1.0">[DID-CORE]</a> specification.).</p>
    </ol>
    <p>Requests to fetch Resources are considered as a DID URL Dereferencing scenario it uses [DID URL paths](https://w3c.github.io/did-core/#path) to lead to a Resource object, rather than a DIDDoc.</p>
-   <p>On the other hand, Resources _metadata_ requests are handled like DID URL Resolution since the result is a subsection of `didDocumentMetadata` specific to that resource.</p>
+   <p>On the other hand, Resources metadata requests are handled like DID URL Resolution since the result is a subsection of `didDocumentMetadata` specific to that resource.</p>
    <h3 class="heading settled" data-level="10.3" id="resource-resolution-and-dereferencing-parameters"><span class="secno">10.3. </span><span class="content">Resource resolution and dereferencing parameters</span><a class="self-link" href="#resource-resolution-and-dereferencing-parameters"></a></h3>
    <p>Here we have an ability to specify different parameters to filter to particular DID-Linked Resources.</p>
-   <p>| Parameter              | Type                                                                                                                                                                                                                  | Description                                                                                     |
-| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
-| `resourceId`           | A [string](https://infra.spec.whatwg.org/#string) that conforms to a method specific unique identifier format.                                                                                                        | The unique identifier of a particular DID-Linked Resource                                       |
-| `resourceCollectionId` | A [string](https://infra.spec.whatwg.org/#string) that conforms to a method specific unique identifier format.                                                                                                        | Can be used to query all resources associated with a DID if combined with resourceMetadata=true |
-| `resourceName`         | A [string](https://infra.spec.whatwg.org/#string)                                                                                                                                                                     | The specific name of a DID-Linked Resource                                                      |
-| `resourceType`         | A [string](https://infra.spec.whatwg.org/#string)                                                                                                                                                                     | The specific type of a DID-Linked Resource                                                      |
-| `resourceVersionTime`  | A [JSON String](https://www.rfc-editor.org/rfc/rfc8259#section-7) serialized as an [XML Datetime](https://www.w3.org/TR/xmlschema11-2/#dateTime) normalized to UTC 00:00:00 and without sub-second decimal precision. | Used to fetch a version of a resource at a specific point in time                               |
-| `checksum`             | A [string](https://infra.spec.whatwg.org/#string)                                                                                                                                                                     | Used to specify a particular resource checksum to demonstrate it is untampered                  |
-| `resourceMetadata`     | [Boolean](https://infra.spec.whatwg.org/#booleans)                                                                                                                                                                    | Used to fetch metadata related to a specific resource or group of resources                     |</p>
+   <table>
+    <thead>
+     <tr>
+      <th>Parameter
+      <th>Type
+      <th>Description
+    <tbody>
+     <tr>
+      <td><code>resourceId</code>
+      <td>A <a href="https://infra.spec.whatwg.org/#string">string</a> that conforms to a method specific unique identifier format.
+      <td>The unique identifier of a particular DID-Linked Resource.
+     <tr>
+      <td><code>resourceCollectionId</code>
+      <td>A <a href="https://infra.spec.whatwg.org/#string">string</a> that conforms to a method specific unique identifier format.
+      <td>Can be used to query all resources associated with a DID if combined with <code>resourceMetadata=true</code>.
+     <tr>
+      <td><code>resourceName</code>
+      <td>A <a href="https://infra.spec.whatwg.org/#string">string</a>.
+      <td>The specific name of a DID-Linked Resource.
+     <tr>
+      <td><code>resourceType</code>
+      <td>A <a href="https://infra.spec.whatwg.org/#string">string</a>.
+      <td>The specific type of a DID-Linked Resource.
+     <tr>
+      <td><code>resourceVersionTime</code>
+      <td>A <a href="https://www.rfc-editor.org/rfc/rfc8259#section-7">JSON String</a> serialized as an <a href="https://www.w3.org/TR/xmlschema11-2/#dateTime">XML Datetime</a> normalized to UTC 00:00:00 and without sub-second decimal precision.
+      <td>Used to fetch a version of a resource at a specific point in time.
+     <tr>
+      <td><code>checksum</code>
+      <td>A <a href="https://infra.spec.whatwg.org/#string">string</a>.
+      <td>Used to specify a particular resource checksum to demonstrate it is untampered.
+     <tr>
+      <td><code>resourceMetadata</code>
+      <td><a href="https://infra.spec.whatwg.org/#booleans">Boolean</a>.
+      <td>Used to fetch metadata related to a specific resource or group of resources.
+   </table>
    <p>Like with DIDDoc query parameters, these can all be chained together to create complex requests for specific DID-Linked Resources at particular points in time or associated with particular DIDDoc versions. </p>
    <h3 class="heading settled" data-level="10.4" id="rules-and-logic-for-handling-ambiguous-queries"><span class="secno">10.4. </span><span class="content">Rules and logic for handling ambiguous queries</span><a class="self-link" href="#rules-and-logic-for-handling-ambiguous-queries"></a></h3>
    <p>It is important to understand how our resolver logically handles more complex dereferencing requests. We have set some baseline defaults and rules to ensure a logical and consistent experience for clients who use our resolver.</p>
-   <h4 class="heading settled" data-level="10.4.1" id="ambiguity-generally-throws-an-error"><span class="secno">10.4.1. </span><span class="content">**Ambiguity generally throws an error** ###</span><a class="self-link" href="#ambiguity-generally-throws-an-error"></a></h4>
-   <p>If the request specifies a parameter where there are multiple potential results, such as where the DID has two resources of the same `resourceType` (<a class="property css" data-link-type="property">String</a>) but `resourceName` is not the same,  an error will be thrown because there is not enough information to discern which resource is being requested.</p>
-   <h4 class="heading settled" data-level="10.4.2" id="multiple-versions-of-the-same-resource"><span class="secno">10.4.2. </span><span class="content">**Multiple versions of the same resource** ###</span><a class="self-link" href="#multiple-versions-of-the-same-resource"></a></h4>
-   <p>If there are multiple resources with the same `resourceType` and `resourceName` but with different `versionIds,` and there is no parameter specified to fetch a particular version, **the resolver will fetch the latest resource by default**.</p>
+   <h4 class="heading settled" data-level="10.4.1" id="ambiguity-generally-throws-an-error"><span class="secno">10.4.1. </span><span class="content">Ambiguity generally throws an error</span><a class="self-link" href="#ambiguity-generally-throws-an-error"></a></h4>
+   <p>If the request specifies a parameter where there are multiple potential results, such as where the DID has two resources of the same `resourceType` but `resourceName` is not the same,  an error will be thrown because there is not enough information to discern which resource is being requested.</p>
+   <h4 class="heading settled" data-level="10.4.2" id="multiple-versions-of-the-same-resource"><span class="secno">10.4.2. </span><span class="content">Multiple versions of the same resource</span><a class="self-link" href="#multiple-versions-of-the-same-resource"></a></h4>
+   <p>If there are multiple resources with the same `resourceType` and `resourceName` but with different `versionIds,` and there is no parameter specified to fetch a particular version, <b>the resolver will fetch the latest resource by default</b>.</p>
    <p>This is because the query is not ambiguous in terms of discerning which set of resources to dereference to, but is only ambiguous in terms of which version of that resource to fetch. </p>
-   <h4 class="heading settled" data-level="10.4.3" id="ambiguity--resourcemetadatatrue"><span class="secno">10.4.3. </span><span class="content">**Ambiguity + resourceMetadata=true** ###</span><a class="self-link" href="#ambiguity--resourcemetadatatrue"></a></h4>
+   <h4 class="heading settled" data-level="10.4.3" id="ambiguity--resourcemetadatatrue"><span class="secno">10.4.3. </span><span class="content">Ambiguity + resourceMetadata=true</span><a class="self-link" href="#ambiguity--resourcemetadatatrue"></a></h4>
    <p>If there is an ambiguous query, such as where there are two resources with the same name but different types, AND there is a resourceMetadata=true parameter, resource data pertaining to all the resources which could potentially be seen as being ambiguous will be returned. </p>
    <p>For example, in the below example, there are multiple resources with the `resourceType= string`, but with different `resourceName` parameters:</p>
    <details>
     <summary>Request format</summary>
-<pre>1.0/identifiers/did:example:c1685ca0-1f5b-439c-8eb8-5c0e85ab7cd0?resourceType=String&amp;resourceMetadata=true
+<pre class="language-json highlight">did<c- p>:</c->example<c- p>:</c->c<c- mi>1685</c->ca<c- mi>0-1</c-><c- kc>f</c-><c- mi>5</c->b<c- mi>-439</c->c<c- mf>-8e</c->b<c- mi>8-5</c->c<c- mf>0e85</c->ab<c- mi>7</c->cd<c- mi>0</c->?resourceType=S<c- kc>tr</c->i<c- kc>n</c->g&amp;resourceMe<c- kc>ta</c->da<c- kc>ta</c->=<c- kc>true</c->
 </pre>
    </details>
    <details>
@@ -1019,10 +1102,10 @@ <h4 class="heading settled" data-level="10.4.3" id="ambiguity--resourcemetadatat
    <h2 class="heading settled" data-level="11" id="examples"><span class="secno">11. </span><span class="content">Resolution and Dereferecing examples</span><a class="self-link" href="#examples"></a></h2>
    <h3 class="heading settled" data-level="11.1" id="resourceid"><span class="secno">11.1. </span><span class="content">ResourceId</span><a class="self-link" href="#resourceid"></a></h3>
    <p>`ResourceId` parameter can be used for filtering a particular resource version by specifically identifying its unique ID.</p>
-   <p>**Example**:</p>
+   <p>For example:</p>
    <details>
     <summary>Request format</summary>
-<pre>1.0/identifiers/did:example:b5d70adf-31ca-4662-aa10-d3a54cd8f06c?resourceId=5e16a3f9-7c6e-4b6b-8e28-20f56780ee25
+<pre class="language-json highlight">did<c- p>:</c->example<c- p>:</c->b<c- mi>5</c->d<c- mi>70</c->ad<c- kc>f</c-><c- mi>-31</c->ca<c- mi>-4662-</c->aa<c- mi>10-</c->d<c- mi>3</c->a<c- mi>54</c->cd<c- mi>8</c-><c- kc>f</c-><c- mi>06</c->c?resourceId=<c- mf>5e16</c->a<c- mi>3</c-><c- kc>f</c-><c- mi>9-7</c->c<c- mf>6e-4</c->b<c- mi>6</c->b<c- mf>-8e28-20</c-><c- kc>f</c-><c- mf>56780ee25</c->
 </pre>
    </details>
    <details>
@@ -1046,10 +1129,10 @@ <h3 class="heading settled" data-level="11.1" id="resourceid"><span class="secno
    </details>
    <h3 class="heading settled" data-level="11.2" id="resourcecollectionid"><span class="secno">11.2. </span><span class="content">ResourceCollectionId</span><a class="self-link" href="#resourcecollectionid"></a></h3>
    <p>`resourceCollectionId` parameter filters all the resource by `collectionId` field. By default cause we are asking for resources for a particular DID it already includes all the resource with the same `collectionId` and this parameter can used mostly as sanity check. Without `resourceMetadata=true` parameter will return the latest created resource if there is only one resource or an unambiguous resource.</p>
-   <p>**Example**:</p>
+   <p>For example:</p>
    <details>
     <summary>Request format</summary>
-<pre>1.0/identifiers/did:example:d8ac0372-0d4b-413e-8ef5-8e8f07822b2c?resourceCollectionId=d8ac0372-0d4b-413e-8ef5-8e8f07822b2c
+<pre class="language-json highlight">did<c- p>:</c->example<c- p>:</c->d<c- mi>8</c->ac<c- mi>0372-0</c->d<c- mi>4</c->b<c- mf>-413e-8e</c-><c- kc>f</c-><c- mf>5-8e8</c-><c- kc>f</c-><c- mi>07822</c->b<c- mi>2</c->c?resourceCollec<c- kc>t</c->io<c- kc>n</c->Id=d<c- mi>8</c->ac<c- mi>0372-0</c->d<c- mi>4</c->b<c- mf>-413e-8e</c-><c- kc>f</c-><c- mf>5-8e8</c-><c- kc>f</c-><c- mi>07822</c->b<c- mi>2</c->c
 </pre>
    </details>
    <details>
@@ -1073,10 +1156,10 @@ <h3 class="heading settled" data-level="11.2" id="resourcecollectionid"><span cl
    </details>
    <h3 class="heading settled" data-level="11.3" id="resourcetype"><span class="secno">11.3. </span><span class="content">ResourceType</span><a class="self-link" href="#resourcetype"></a></h3>
    <p>This parameter is also just a filter by `Type` field through resources. But there is a corner case if the user asks about exact resource (exact data). If after applying all the parameters in request several resources are left with the same `Name` - the latest one will be responded. Otherwise - error `NotFoundError` will be raised.</p>
-   <p>**Example**:</p>
+   <p>For example:</p>
    <details>
     <summary>Request format</summary>
-<pre>1.0/identifiers/did:example:d8ac0372-0d4b-413e-8ef5-8e8f07822b2c?resourceType=exampleResourceType
+<pre class="language-json highlight">did<c- p>:</c->example<c- p>:</c->d<c- mi>8</c->ac<c- mi>0372-0</c->d<c- mi>4</c->b<c- mf>-413e-8e</c-><c- kc>f</c-><c- mf>5-8e8</c-><c- kc>f</c-><c- mi>07822</c->b<c- mi>2</c->c?resourceType=exampleResourceType
 </pre>
    </details>
    <details>
@@ -1100,10 +1183,10 @@ <h3 class="heading settled" data-level="11.3" id="resourcetype"><span class="sec
    </details>
    <h3 class="heading settled" data-level="11.4" id="resourcename"><span class="secno">11.4. </span><span class="content">ResourceName</span><a class="self-link" href="#resourcename"></a></h3>
    <p>Behavior of this parameter is similar with [resourceType](adr-005-did-resolution-and-did-url-dereferencing.md#resourcetype) one. If there is no ambiguous resource, it will be fetched. Otherwise greater specifity is required. </p>
-   <p>**Example**:</p>
+   <p>For example:</p>
    <details>
     <summary>Request format</summary>
-<pre>1.0/identifiers/did:example:d8ac0372-0d4b-413e-8ef5-8e8f07822b2c?resourceName=exampleResourceName
+<pre class="language-json highlight">did<c- p>:</c->example<c- p>:</c->d<c- mi>8</c->ac<c- mi>0372-0</c->d<c- mi>4</c->b<c- mf>-413e-8e</c-><c- kc>f</c-><c- mf>5-8e8</c-><c- kc>f</c-><c- mi>07822</c->b<c- mi>2</c->c?resourceName=exampleResourceName
 </pre>
    </details>
    <details>
@@ -1127,10 +1210,10 @@ <h3 class="heading settled" data-level="11.4" id="resourcename"><span class="sec
    </details>
    <h3 class="heading settled" data-level="11.5" id="resourceversion"><span class="secno">11.5. </span><span class="content">ResourceVersion</span><a class="self-link" href="#resourceversion"></a></h3>
    <p>This parameter filters by `Version` field. We introduced it with latest network upgrade and can be optionally set to identify a version of a resource with a particular string.</p>
-   <p>**Example**:</p>
+   <p>For example:</p>
    <details>
     <summary>Request format</summary>
-<pre>1.0/identifiers/did:example:d8ac0372-0d4b-413e-8ef5-8e8f07822b2c?resourceVersion=b9029cf7-c40b-4850-b9a1-9bfad46a68d7
+<pre class="language-json highlight">did<c- p>:</c->example<c- p>:</c->d<c- mi>8</c->ac<c- mi>0372-0</c->d<c- mi>4</c->b<c- mf>-413e-8e</c-><c- kc>f</c-><c- mf>5-8e8</c-><c- kc>f</c-><c- mi>07822</c->b<c- mi>2</c->c?resourceVersio<c- kc>n</c->=b<c- mi>9029</c->c<c- kc>f</c-><c- mi>7-</c->c<c- mi>40</c->b<c- mi>-4850-</c->b<c- mi>9</c->a<c- mi>1-9</c->b<c- kc>fa</c->d<c- mi>46</c->a<c- mi>68</c->d<c- mi>7</c->
 </pre>
    </details>
    <details>
@@ -1153,12 +1236,12 @@ <h3 class="heading settled" data-level="11.5" id="resourceversion"><span class="
 </pre>
    </details>
    <h3 class="heading settled" data-level="11.6" id="resourceversiontime"><span class="secno">11.6. </span><span class="content">ResourceVersionTime</span><a class="self-link" href="#resourceversiontime"></a></h3>
-   <p>**Important:** This parameter must always be accompanied by another resource query qualifier.</p>
+   <p><b>Important:</b> This parameter must always be accompanied by another resource query qualifier.</p>
    <p>The main goal here is to get the nearest resource for `resourceVersionTime` value. "Nearest" means that if we are asking for time between `resource1` and `resource2` were created - `resource1` will be returned. In case if requested `resourceVersionTime` is before the first resource created - `NotFoundError` will be returned. The most useful use-case here is checking that some "Credential" (driver’s license) was active at `resourceVersionTime` (was not revoked from Revocation Registry for example).</p>
-   <p>**Example**:</p>
+   <p>For example:</p>
    <details>
     <summary>Request format</summary>
-<pre>1.0/identifiers/did:example:d8ac0372-0d4b-413e-8ef5-8e8f07822b2c?resourceVersionTime=2023-02-22T06:58:18.61Z&amp;resourceVersion=1.14.41
+<pre class="language-json highlight">did<c- p>:</c->example<c- p>:</c->d<c- mi>8</c->ac<c- mi>0372-0</c->d<c- mi>4</c->b<c- mf>-413e-8e</c-><c- kc>f</c-><c- mf>5-8e8</c-><c- kc>f</c-><c- mi>07822</c->b<c- mi>2</c->c?resourceVersio<c- kc>n</c->Time=<c- mi>2023-02-22</c->T<c- mi>06</c-><c- p>:</c-><c- mi>58</c-><c- p>:</c-><c- mf>18.61</c->Z&amp;resourceVersio<c- kc>n</c->=<c- mf>1.14.41</c->
 </pre>
    </details>
    <details>
@@ -1183,10 +1266,10 @@ <h3 class="heading settled" data-level="11.6" id="resourceversiontime"><span cla
    </details>
    <h3 class="heading settled" data-level="11.7" id="checksum"><span class="secno">11.7. </span><span class="content">Checksum</span><a class="self-link" href="#checksum"></a></h3>
    <p>It just checks that `checksum` is the same as resource’s metadata and also can used as a sanity check. For example, if the user knows what is exact checksum then it may be checked before actual downloading.</p>
-   <p>**Example**:</p>
+   <p>For example:</p>
    <details>
     <summary>Request format</summary>
-<pre>1.0/identifiers/did:example:d8ac0372-0d4b-413e-8ef5-8e8f07822b2c?checksum=27ad51a49f079a6634b18bbc3ac08dd2d91f13fabf72ea8e5d83692fe4820058
+<pre class="language-json highlight">did<c- p>:</c->example<c- p>:</c->d<c- mi>8</c->ac<c- mi>0372-0</c->d<c- mi>4</c->b<c- mf>-413e-8e</c-><c- kc>f</c-><c- mf>5-8e8</c-><c- kc>f</c-><c- mi>07822</c->b<c- mi>2</c->c?checksum=<c- mi>27</c->ad<c- mi>51</c->a<c- mi>49</c-><c- kc>f</c-><c- mi>079</c->a<c- mi>6634</c->b<c- mi>18</c->bbc<c- mi>3</c->ac<c- mi>08</c->dd<c- mi>2</c->d<c- mi>91</c-><c- kc>f</c-><c- mi>13</c-><c- kc>fa</c->b<c- kc>f</c-><c- mf>72e</c->a<c- mf>8e5</c->d<c- mi>83692</c-><c- kc>fe</c-><c- mi>4820058</c->
 </pre>
    </details>
    <details>
@@ -1219,10 +1302,10 @@ <h3 class="heading settled" data-level="11.8" id="resourcemetadata"><span class=
     <li data-md>
      <p>Unused</p>
    </ul>
-   <p>**Example**:</p>
+   <p>For example:</p>
    <details>
     <summary>Request format</summary>
-<pre>1.0/identifiers/did:example:d8ac0372-0d4b-413e-8ef5-8e8f07822b2c?resourceType=exampleSchema&amp;resourceMetadata=true
+<pre class="language-json highlight">did<c- p>:</c->example<c- p>:</c->d<c- mi>8</c->ac<c- mi>0372-0</c->d<c- mi>4</c->b<c- mf>-413e-8e</c-><c- kc>f</c-><c- mf>5-8e8</c-><c- kc>f</c-><c- mi>07822</c->b<c- mi>2</c->c?resourceType=exampleSchema&amp;resourceMe<c- kc>ta</c->da<c- kc>ta</c->=<c- kc>true</c->
 </pre>
    </details>
    <details>
@@ -1359,8 +1442,6 @@ <h3 class="no-num no-ref heading settled" id="informative"><span class="content"
   <dl>
    <dt id="biblio-did-core">[DID-CORE]
    <dd>Manu Sporny; et al. <a href="https://w3c.github.io/did-core/"><cite>Decentralized Identifiers (DIDs) v1.0</cite></a>. URL: <a href="https://w3c.github.io/did-core/">https://w3c.github.io/did-core/</a>
-   <dt id="biblio-rfc3986">[RFC3986]
-   <dd>T. Berners-Lee; R. Fielding; L. Masinter. <a href="https://www.rfc-editor.org/rfc/rfc3986"><cite>Uniform Resource Identifier (URI): Generic Syntax</cite></a>. January 2005. Internet Standard. URL: <a href="https://www.rfc-editor.org/rfc/rfc3986">https://www.rfc-editor.org/rfc/rfc3986</a>
    <dt id="biblio-rfc8174">[RFC8174]
    <dd>B. Leiba. <a href="https://www.rfc-editor.org/rfc/rfc8174"><cite>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</cite></a>. May 2017. Best Current Practice. URL: <a href="https://www.rfc-editor.org/rfc/rfc8174">https://www.rfc-editor.org/rfc/rfc8174</a>
   </dl>
\ No newline at end of file