w3c
Model accept as the HTTP accept header
Just wondering... would it be possible, for the sake of conceptual compatibility, to model the accept properties (both of DID and for DID URL) after the HTTP Accept header syntax (see, e.g., MDN). I.e., the caller may accept several media types, possibly with priorities. (My reading of the current text is that, at the moment, a single media type can be used.)
You're right, at the moment the accept option can only contain a single media type, but I don't remember why we made it like this. I think what you suggest makes sense to me, happy to support this change..
This was discussed during the #did meeting on 10 July 2025.
View the transcript
Model accept as the HTTP accept header #116
<ottomorac> w3c/
ottomorac: The was a suggestion from Ivan to model the “accept” properties (both of DID and for DID URL) after the HTTP Accept header syntax. The suggestion was positively received by Markus. What would be the next steps here?
markus_sabadello: background was - when you invoke a resolver, you can pass the Accept header
… maybe the significance of this has changed a bit after we moved away from Abstract Data Model. but still has the same overall function as in HTTP
… even if at the moment we allow only a single mime type
… but in DID URL Dereferencing, we might have many different media types
<Zakim> manu, you wanted to agree, model after HTTP Accept.
manu: +1 to what Markus said, and what Ivan was suggesting
… lets not reinvent the wheel and just model it after the HTTP accept header
ottomorac: ok, consensus is to model it after HTTP Header, change the DID resolution algorithm.
… do we just label the issue as Ready for PR?
markus_sabadello: yes
This was discussed during the #did meeting on 04 September 2025.
View the transcript
Model accept as the HTTP accept header w3c/did-resolution#116
manu: so, we want to avoid that, so lets keep discussing
<ottomorac> w3c/
<ottomorac> There was agreement to model it after the HTTP Accept Header, there is change required in the DID resolution algorithm. We need someone to volunteer to create the PR.
ottomorac: looking for a volunteer for this PR
markus_sabadello: I can take this one
This was discussed during the #did meeting on 11 November 2025.
View the transcript
w3c/did-resolution#116
@wip: we talk model accept headers we take that on we are ready for model accept headers.
markus_sabadello: I already assigned