From d0160205d8475e4a819a905446185c6bb81b8f9c Mon Sep 17 00:00:00 2001
From: ottomorac <16960403+ottomorac@users.noreply.github.com>
Date: Fri, 12 Sep 2025 17:50:36 -0400
Subject: [PATCH 1/3] add http get and post binding options

---
 index.html | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/index.html b/index.html
index 828a9f1..7fb10dd 100644
--- a/index.html
+++ b/index.html
@@ -2208,6 +2208,12 @@ <h2>HTTP(S) Binding</h2>
 		<p>This binding is generally considered a <a>remote binding</a>, but could
 			also be a <a>local binding</a> if the HTTP(S) endpoint is run in a local environment, such as on <code>localhost</code>.</p>
 
+		<p>All conformant <a>DID resolvers</a> MUST implement an HTTP(S) binding using GET as described in the algorithm below.
+			In addition, <a>DID resolvers</a> MAY support an alternative HTTP(S) binding using POST.
+			Allowing clients to send POST request to the resolver endpoint may be useful in order to avoid URL length limitations,
+			and it also allows the DID (or DID URL) and resolution options to be kept out of the invoked URL 
+			(protecting them from exposure in logs, proxies, or monitoring).</p>
+
 		<p>Using this binding, the <a>DID resolution</a> function (see
 			<a href="#resolving"></a>) and/or <a>DID URL dereferencing</a> function (see <a href="#dereferencing"></a>)
 			can be executed as follows:</p>

From 019696616eaeb519333e31b86ceffbc673c9c1aa Mon Sep 17 00:00:00 2001
From: Otto Mora <16960403+ottomorac@users.noreply.github.com>
Date: Wed, 24 Sep 2025 12:14:20 -0400
Subject: [PATCH 2/3] Update index.html

Co-authored-by: Markus Sabadello <markus@danubetech.com>
---
 index.html | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 7fb10dd..2b49d37 100644
--- a/index.html
+++ b/index.html
@@ -2212,7 +2212,10 @@ <h2>HTTP(S) Binding</h2>
 			In addition, <a>DID resolvers</a> MAY support an alternative HTTP(S) binding using POST.
 			Allowing clients to send POST request to the resolver endpoint may be useful in order to avoid URL length limitations,
 			and it also allows the DID (or DID URL) and resolution options to be kept out of the invoked URL 
-			(protecting them from exposure in logs, proxies, or monitoring).</p>
+			(protecting them from exposure in logs, proxies, or monitoring).
+			Finally, using POST also has the advantage that all data types of a <a href="#metadata-structure">metadata structure</a>
+			are fully supported, including <a data-cite="INFRA#maps">maps</a>, <a
+			data-cite="INFRA#list">lists</a>, and <a data-cite="INFRA#ordered-set">sets</a>.</p>
 
 		<p>Using this binding, the <a>DID resolution</a> function (see
 			<a href="#resolving"></a>) and/or <a>DID URL dereferencing</a> function (see <a href="#dereferencing"></a>)

From 598c0d3d4a1992f1a4a4d2dd2644074c049a57fa Mon Sep 17 00:00:00 2001
From: Otto Mora <16960403+ottomorac@users.noreply.github.com>
Date: Tue, 30 Sep 2025 23:15:19 -0400
Subject: [PATCH 3/3] Update index.html

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 2b49d37..63a9d67 100644
--- a/index.html
+++ b/index.html
@@ -2213,7 +2213,8 @@ <h2>HTTP(S) Binding</h2>
 			Allowing clients to send POST request to the resolver endpoint may be useful in order to avoid URL length limitations,
 			and it also allows the DID (or DID URL) and resolution options to be kept out of the invoked URL 
 			(protecting them from exposure in logs, proxies, or monitoring).
-			Finally, using POST also has the advantage that all data types of a <a href="#metadata-structure">metadata structure</a>
+			Finally, using POST has the advantage that all data types in 
+			DID <a href="#metadata-structure">metadata structures</a>
 			are fully supported, including <a data-cite="INFRA#maps">maps</a>, <a
 			data-cite="INFRA#list">lists</a>, and <a data-cite="INFRA#ordered-set">sets</a>.</p>