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

Add relative-ref DID URL parameter #349

Closed
peacekeeper opened this issue Jul 15, 2020 · 1 comment · Fixed by #357
Closed

Add relative-ref DID URL parameter #349

peacekeeper opened this issue Jul 15, 2020 · 1 comment · Fixed by #357
Assignees
Labels
pr exists There is an open PR to address this issue

Comments

@peacekeeper
Copy link
Contributor

Since matrix parameters were removed from the DID URL syntax, one consequence is that an extra DID URL parameter is needed that can contain an encoded service endpoint path and query string. This has been originally mentioned by @dlongley in #159 (comment) and used again in an example use case described by @OR13 in #327. This DID URL parameter would always be used in conjunction with the service parameter which is already in the spec.

Example

did:ex:123?service=files&relative-ref=%2Fmyresume%2Fdoc%3Fversion%3Dlatest%23intro

@peacekeeper peacekeeper self-assigned this Jul 15, 2020
@msporny
Copy link
Member

msporny commented Jul 21, 2020

Yes, we need to add this to the DID Core specification. We need to discuss service and possible parameters during a special topic call.

@msporny msporny added needs special call Needs a special topic call to make progress and removed needs special call Needs a special topic call to make progress labels Jul 21, 2020
@peacekeeper peacekeeper added the pr exists There is an open PR to address this issue label Jul 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr exists There is an open PR to address this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants