---
# System prepended metadata

title: 'DID method (:web + others) Lit Review'

---

** idea. what if combined did:web with .well-known service endpoint discovery?


- did:web https://w3c-ccg.github.io/did-method-web/

- did:web2.0 https://github.com/WebOfTrustInfo/rwot12-cologne/blob/main/advance-readings/did-web-2.0.md


- did:webplus https://github.com/LedgerDomain/did-webplus

> - Each DID document is self-signed, having fields "selfSignature" and "selfSignatureVerifier" which define the signature and the public key that verifies the self-signature. The process for verifying a self-signature is explained in the selfsign crate readme.
> - Each DID document has a "versionId" field, which starts at 0 upon DID creation and increases by 1 with each update.
> - Each DID document has a "validFrom" field, defining the timestamp at which the DID document becomes current.


- did:webS https://trustoverip.github.io/tswg-did-method-webs-specification
    - did:web + KERI AID
    - keri complexity?
    - nice benefit: Any did:webs can be expressed as a did:web but the inverse is not true–a did:webs MUST include an AID.
        - possibility of using it where did:web is accepted increases adoption, can simply ignore the last qualifier, or some detail.
    - The did:web version of the DIDs are the same (minus the s) and point to the same did.json file, but have no knowledge of the did.keri file.
    -  “walk the KEL” -> not realistc for keys that are constantly rotated...
    -  interesting idea::
        -  https://trustoverip.github.io/tswg-did-method-webs-specification/#the-whois-folder


- did:peer https://identity.foundation/peer-did-method-spec/#method-name


- DID:github https://github.com/decentralized-identity/github-did
- DID:gitN https://github.com/dhuseby/did-git-spec/blob/master/did-git-spec.md
- Well Known DID: https://identity.foundation/.well-known/resources/did-configuration/
- did:key https://w3c-ccg.github.io/did-method-key/
- did:jwk https://github.com/quartzjer/did-jwk/blob/main/spec.md