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
We are using DID URLs (paths) to reference files, and the /whois path to reference a Linked-VP because they align so easily with a web-based DID. However, it is my understanding that in DID Methods that don't have such an obvious/simple mechanism, DID Linked Resources are used for more or less the same purpose -- to resolve a resources related to (or perhaps "published by") the DID Controller.
This issue is to look at DID Linked Resources from the perspective of did:tdw and if it would be a good idea to reference the DID Linked Resources spec in the did:tdw spec.
The text was updated successfully, but these errors were encountered:
One question is how much of this should be in the W3C DID Resolution spec itself (which currently doesn't say much about how to handle paths in DID URLs), how much of this should be method-specific, and how much can be re-used across different DID methods.
We are using DID URLs (paths) to reference files, and the
/whois
path to reference a Linked-VP because they align so easily with a web-based DID. However, it is my understanding that in DID Methods that don't have such an obvious/simple mechanism, DID Linked Resources are used for more or less the same purpose -- to resolve a resources related to (or perhaps "published by") the DID Controller.This issue is to look at DID Linked Resources from the perspective of
did:tdw
and if it would be a good idea to reference the DID Linked Resources spec in thedid:tdw
spec.The text was updated successfully, but these errors were encountered: