You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
The text was updated successfully, but these errors were encountered:
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..
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.)The text was updated successfully, but these errors were encountered: