Require HTTP GET binding and allow HTTP POST

[ottomorac]

This PR attempts to address #161 by adding a statement requiring that DID resolvers implement HTTP GET bindings and allowing an alternative HTTP POST binding to be used when desired.

---

Preview | Diff

[ottomorac]

@peacekeeper I have initially opted to just add the normative statement requiring GET and allowing POST. I thought the HTTP binding section would be appropriate location for the change but if you think we should make the change in the DID Resolution and Dereferencing Sections directly let me know.

Also not sure yet if I need to go into the detailed steps of how the binding can be done with either GET or POST in steps 2 and 4 and how that might affect things like encoding of query params etc. I think let's align on the normative statement first, and perhaps discuss if we need to add the detailed steps as well once we figure that out.

[w3cbot]

This was discussed during the #did meeting on 18 September 2025.

View the transcript

w3c/did-resolution#192

Wip: another one from Otto, also about binding.

markus_sabadello: it is about adding a POST binding, which we don't have right now.
… I think it is fine.
… It goes together with PR w3c/did-resolution#196 which I submitted.

---