Define HTTP POST binding

[peacekeeper]

This defines an HTTP POST binding in addition to the HTTP GET binding. This also adds some examples, and updates the OpenAPI definition.

Addresses #161. Related to #192.

---

Preview | Diff

[w3cbot]

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

View the transcript

w3c/did-resolution#196

markus_sabadello: I try to define of how the POST interface would work:
… how you construct the URL, what to put in the headers, in the body.

Wip: review wanted on these PRs.
… Also the OpenAPI YAML needs to be updated.

markus_sabadello: yes

---

[w3cbot]

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

View the transcript

Define HTTP POST binding #196

<ottomorac> w3c/did-resolution#196

ottomorac: Will has provided approval, but it would be great if other folks also reviewed

<Wip> w3c/did-resolution#183

Wip: this isn't about this PR, but just briefly -
… maybe this 'no cache allowed' is a 'feature not supported'?

manu: wait, I'm confused

<Wip> w3c/did-resolution#183

Wip: sorry, this is about PR 183

ottomorac: I think Will was saying that instead of having a 'No-cache disallowed' error, we make it more generic, use the 'feature not supported' error instead

manu: yeah, I think that would be fine
… as long as we have a description of what the missing feature is

---

[peacekeeper]

Merging after approvals, suggestions applied, conflicts resolved.