...
Examples
NOTE: The first two sets of examples in this section are based on the verification metadata formats defined by the did:webvh and did:webs methods, both of which have the constraint of being valid did:web DID. By contrast, a did:scid is not a valid did:web DID because are web-based DID methods. While did:scid supports storing verification metadata on a web server, it is not strictly a web-based DID method because: a) it does not include any web location information in the DID itself (the location information is only in a did:scid URL parameter), and b) did:scid supports storing verification metadata in other locations, including blockchains, DHTs, and local storage in peer-to-peer usages. |
did:scid Webvh Example
Examples in this section are based on the current specification for the did:webvh method.
IMPORTANT: Although the Webvh method is the underlying basis, these examples are based on a (currently hypothetical) did:scid:vh method specification. This would be a separate specification (or perhaps an appendix to the did:webvh method specification) that specifies how the Webvh method is adapted to become a did:scid:vh method. At a minimum it this did:scid:vh method specification would cover: How the did:scid:vh method-specific-id is generated; How the Webvh DID documents and verifiable history file is portable.
|
...
This example uses a hypothetical modified version of the cheqd DID method that would specifyspecifies: 1) using how the did:scid
DID could be used as the namespace
component of a did:cheqd
DID, and 2) how to retrieve the did:scid
DID verification metadata from the cheqd blockchain.
...
The final example shows how a did:scid:ke
DID could store its verification metadata on the cheqd blockchain (again, assuming a modified version of the cheqd DID method that supports did:scid
DIDs as described above):
did:scid:ke:3:EKYGGh-FtAphGmSZbsuBs_t4qpsjYJ2ZqvMKluq9OxmP?src=did:cheqd
...