mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-12-27 08:09:27 -05:00
95 lines
2.8 KiB
Markdown
95 lines
2.8 KiB
Markdown
---
|
||
published: false
|
||
---
|
||
|
||
# Web Standards
|
||
|
||
### IBC
|
||
|
||
https://github.com/cosmos/ibc/
|
||
|
||
## List
|
||
- aggregate well-known-did-1-of-a 1 of a (intermediate)
|
||
- aggregate did-spec-registries-1-of-a Signature Implementations 1 of many (intermediate)
|
||
- aggregate did-spec-registries-1-of-b did-method 1 of many (intermediate)
|
||
|
||
|
||
### W3C
|
||
|
||
Decentralized Identifier ✓
|
||
- Explainer ✓
|
||
- Literature +
|
||
- Methods ✓
|
||
- Tools \ Services
|
||
- Critique ✓
|
||
|
||
Verifiable Credential
|
||
- Explainer ✓
|
||
- Comparisons ✓
|
||
- Varieties
|
||
- JSON-LD
|
||
- JSON-LD ZKP BBS+
|
||
- JSON-JWT
|
||
- ZKP-CL - [IIA] Indy Aries AnnonCreds
|
||
- JWP
|
||
|
||
JSON-LD
|
||
- [Complementary] JSON-LD ✓ (W3C)
|
||
|
||
### Credentials Community Group
|
||
|
||
- [Exchange] CHAPI ✓ (CCG)
|
||
- [Complementary] Cryptography > BBS ✓ (CCG)
|
||
- [Authorization] oCap/zCap ✓ (CCG)
|
||
|
||
### IETF
|
||
|
||
- [Complementary] (IETF)
|
||
- [Authorization] GNAP ✓ (IETF)
|
||
- [Authorization] OAuth ✓ (IETF)
|
||
- [ID-Non-SSI] OAuth (IETF)
|
||
- [ID-Non-SSI] SCIM (IETF)
|
||
|
||
### OASIS
|
||
|
||
- [ID-Non-SSI] SAML (OASIS)
|
||
- [ID-Non-SSI] KMIP (OASIS)
|
||
- [ID-Non-SSI] Secure QR Code (OASIS)
|
||
|
||
### ISO/IEC
|
||
- mDL 18013-5 ✓ (ISO)
|
||
- 22030 ?
|
||
- Working Group 3 - Travel Documents
|
||
|
||
### OpenID Foundation
|
||
- [Exchange] OIDC ✓ (OpenID)
|
||
- [ID-Non-SSI] OpenID (OpenID)
|
||
|
||
### ISO
|
||
- [Exchange] mDL ✓ (ISO)
|
||
- [Blockchain] ISOTC 307 ✓ (ISO)
|
||
|
||
### CEN/CENTLIC
|
||
- [Blockchain] CEN/CENTLIC ✓ (CEN)
|
||
- [Blockchain] ERC 725 (ERC-EIP)
|
||
|
||
### FIDO
|
||
- [ID-Non-SSI] FIDO (FIDO)
|
||
|
||
## VC
|
||
|
||
* [New search engine, mobile wallet, verifiable credentials and delivery technologies.](https://twitter.com/HUMBLPay/status/1574454647384813568) via Twitter ([ANN](https://www.globenewswire.com/en/news-release/2022/04/13/2421969/0/en/HUMBL-Selected-To-Pilot-Digital-Wallet-Program-On-Behalf-of-The-County-of-Santa-Cruz-California.html) 2022-04-13 HUMBL @HUMBLPay
|
||
*using verifiable credentials in their wallet.*
|
||
> #HUMBL x GF2GO - San Diego, CA - [Pilot Program](https://www.youtube.com/watch?v=H_HAFEzmkWU)
|
||
|
||
## DIDs
|
||
W3C Press Release - [Decentralized Identifiers (DIDs) v1.0 becomes a W3C Recommendation](https://www.w3.org/2022/07/pressrelease-did-rec) worth reading to see who contributed comments (and notice who didn’t)
|
||
|
||
For individuals in particular, DIDs can put them back in control of their personal data and consent, and also enable more respectful bi-directional trust relationships where forgery is prevented, privacy is honored, and usability is enhanced.
|
||
|
||
## DID Auth
|
||
|
||
* [SSI Interaction Patterns](https://www.windley.com/archives/2021/06/ssi_interaction_patterns.shtml)
|
||
> While the DID Authn pattern is simple, it is not as flexible as we need in some situations. For more complicated scenarios, we can use verifiable credentials. The first scenario we’ll consider is where the same organization is issuing and verifying the credential.
|
||
> 
|