Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable other DID doc content types #15

Open
rhiaro opened this issue Oct 19, 2020 · 1 comment
Open

Enable other DID doc content types #15

rhiaro opened this issue Oct 19, 2020 · 1 comment

Comments

@rhiaro
Copy link
Member

rhiaro commented Oct 19, 2020

A hardcoded file called did.json is not very flexible, and excludes other representations. We should update the spec to use Accept headers on Read. It'd also be better if the requester for Read just fetches the DID as it stands without adding fixed strings or filenames on the end.

@dmitrizagidulin
Copy link
Collaborator

Hmmm, yeah, maybe we can design a mechanism that allows for elegant DIDs without filenames, but also allows for filenames with extensions optionally. (Although there aren't really other representations to exclude, in this method (it defines only the JSON/JSON-LD representation).

-1 to using Accept headers. (Many many web servers aren't able to do content negotiation.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants