Decentralized Identifiers v1.0
The Decentralized Identifiers specification editors and implementers spent some time at Rebooting the Web of Trust 6 processing the remaining issues in the issue tracker.
This document summarizes the proposed resolutions that the group has put forward to resolve all of the DID specification issues that were submitted before 2018-03-05.
DID Specification RWoT6 Resolutions
- Describe how guardianship and delegation is provided for by Object Capabilities
- Use 'proof' instead of 'signature'
- DID Documents MUST be fully formed (not in intermediate form)
- DID Documents MUST contain an 'id' property
- Cryptographic keys MUST contain an 'owner' property
- Service endpoints will be defined per DID Reconciliation Draft
- DIDs MUST start with 'did:'
- References to JOSE/JWS/JWK will be made in Linked Data Proof/Signature/Suite specs, not DID spec See #38 See #39
- DID Documents do not require an encapsulating signature
- Authorization best practices will request that developers follow the Object Capability pattern
- Add crypto material search algorithm to spec
- Allow use of publicKeyAddress instead of URL for Ethereum Use Cases
- Spec will explain graph data model approach
- Cryptographic Suites will be non-normative, but explained in examples
- Biometrics will be pseudonymous and no material will be on blockchain
- Revoked keys will be allowed in DID Document
The group expects that work will continue during the W3C Credentials Community Group meetings over the next several months, with a plan to take the specification on the W3C Standards track by Q4 2018. The following work items will be needed to progress onto the W3C Standards track:
- DID Primer for W3C Members
- W3C DID Working Group Charter Proposal
- DID Use Cases (focus on 3-5 use cases)
- DID Specification
- Test Suite for DID Specification