Skip to content

Unclear from spec how to link/bind a resource with a DID #8

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

Open
wip-abramson opened this issue May 21, 2025 · 2 comments
Open

Unclear from spec how to link/bind a resource with a DID #8

wip-abramson opened this issue May 21, 2025 · 2 comments

Comments

@wip-abramson
Copy link
Contributor

I read through the spec and was unsure:

  1. Where do resources live? What about the resourceMetadata? Is this something that individual DID methods define? Some spec text and examples of this would be useful
  2. How is binding of a resource to a DID enforced and verified. It is not clear to me how binding is achieved, again is this left to the method? Also it seems like this binding is optional, but doesn't that mean I can arbitrarily link resources to any DID within the scope of some method?
  3. I think because of this confusion, I am very unclear how dereferencing of a DID Linked Resource occurs.

For example given the following DID URL:

did:example:entity123/resources/41c0f0fe-cd4e-45aa-aec5-754db4a63865

First I would resolve did:example:entity123 to a resolutionResult including the DID document and metadata.

But then what do I do?

What do I do with the path /resources/41c0f0fe-cd4e-45aa-aec5-754db4a63865?

Where is the resource that I am trying to retrieve and how do I verify it was linked by the DID controller?

@tweeddalex
Copy link
Contributor

Hey @wip-abramson thanks for comments and feedback. Going to discuss with @ankurdotb today and respond to these / start making the spec clearer

@ankurdotb
Copy link
Contributor

This is super useful feedback! Will work through it with Alex

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

3 participants