Skip to content

Commit

Permalink
chore: cleanup list of traits decentralized-identity#4
Browse files Browse the repository at this point in the history
  • Loading branch information
@jceb
jceb committed Sep 3, 2024
1 parent faa5a16 commit 4bda96a
Show file tree
Hide file tree
Showing 2 changed files with 92 additions and 62 deletions.
113 changes: 69 additions & 44 deletions schemas/traits.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,85 +16,110 @@
"description": "DID Specification URL.",
"format": "uri"
},
"modifiable": {
"type": "boolean",
"title": "Modifiable",
"description": "DID Documents can be modified."
},
"service_endpoints": {
"type": "boolean",
"title": "Service Endpoints",
"description": "Service endpoints can be added to DID Documents."
},
"deactivatable": {
"type": "boolean",
"title": "Deactivatable",
"description": "DID Documents can be deactivated / deleted."
"description": "DID Documents can be deactivated."
},
"enumerable": {
"deletable": {
"type": "boolean",
"title": "Enumerable",
"description": "All DIDs of this method can be enumerated, i.e. a public registry like a DLT exists that references all existing DIDs."
"title": "Deletable",
"description": "DID Documents can be deleted."
},
"globally": {
"fees": {
"type": "boolean",
"title": "Globally resolvable",
"description": "DIDs can be resolved globally, i.e. the current DID document can be resolved globally from every point as opposed to a DID that just exists in a local context."
"title": "Explicit Fees",
"description": "Creation, modification or deletion of identifiers require a transaction fee, e.g. blockchain-based DID methods often require transaction fees."
},
"history": {
"self-certifying": {
"type": "boolean",
"title": "History available",
"description": "Previous versions of DID document are available and can be looked up."
"title": "Self-Certifying",
"description": "DID and the initial DID Document are cryptographically bound to one another, e.g. `did:key`."
},
"immutable": {
"rotatable_keys": {
"type": "boolean",
"title": "Immutable History",
"description": "Changes to DID Documents are persisted in an immutable data structure, e.g. a DLT."
"title": "Rotatable Keys",
"description": "The DID method supports rotation of keys to control the DID."
},
"pre-rotatable_keys": {
"type": "boolean",
"title": "Pre-Rotatable Keys",
"description": "Cryptographic keys can be pre-rotated to combat key loss and attacks by quantum computers. - Comment by Juan: one thing working with the KERI WG at DIF taught me was that there are like 10 different capabilities/flows that people refer to when they mean rotation. rotation in case of key exfiltration? manual rotation by controller? regular/automated rotation NOT requiring manual controller intervention?"
},
"modifiable_multi-sig": {
"type": "boolean",
"title": "Multi-Signature Modifiable",
"description": "The method supports multiple DID controllers, with multiple key signatures required to update or deactivate the DID. - Comment by Juan: threshold versus multisig goes all the way back to christopher allan's BTC pre-DID research and some of the oldest did-wg megathreads, worth picking carefully a definition. joe andreiu probably has something detailed written up about this somewhere.."
},
"human-readable": {
"type": "boolean",
"title": "Human-readable",
"description": "DID can be read and remembered by humans, e.g. `did:web:example.com:me`."
"description": "DIDs are human-readable, e.g. `did:web:example.com:me`."
},
"pre-rotation": {
"enumerable": {
"type": "boolean",
"title": "Key Pre-Rotation",
"description": "Cryptographic keys can be pre-rotated to combat key loss and attacks by quantum computers."
"title": "Enumerable",
"description": "All DIDs of this method can be enumerated, i.e. a public registry like a DLT exists that references all existing DIDs."
},
"modifiable": {
"locally_resolvable": {
"type": "boolean",
"title": "Modifiable",
"description": "DID Documents can be modified."
"title": "Locally Resolvable",
"description": "DID documents can be resolved in an ephameral local context, e.g. `did:peer`."
},
"self-certification": {
"globally_resolvable": {
"type": "boolean",
"title": "Self-Certification",
"description": "The initial DID Document is securely derived from the DID itself, e.g. `did:key`."
"title": "Globally Resolvable",
"description": "DID documents can be resolved globally."
},
"self-creation": {
"documents": {
"type": "boolean",
"title": "Self-Creation",
"description": "DID Document is generative / derived from the DID without having to access any external system, e.g. any `did:key` DID can be derived from the initial public key."
"title": "Documents Hosting",
"description": "Additional documents can be hosted with the DID Document and dereferenced via DID paths."
},
"fees": {
"history": {
"type": "boolean",
"title": "Explicit Fees",
"description": "Creation, modification or deletion of identifiers trigger transaction fees, e.g. blockchain-based DID methods often require transaction fees."
"title": "DID Document History",
"description": "Previous versions of DID documents are available and can be dereferenced."
},
"history_immutable": {
"type": "boolean",
"title": "Immutable DID Document History",
"description": "Changes to DID Documents are persisted in an immutable data structure, e.g. a DLT."
},
"hosting": {
"not_hosted": {
"type": "boolean",
"title": "Hosting",
"description": "What kind of hosting is require? None, centralized, decentralized.."
"title": "Not Hosted",
"description": "No hosting of DID Document required, e.g. ephameral `did:key` documents."
},
"rotatable": {
"centrally_hosted": {
"type": "boolean",
"title": "Rotatable",
"description": "The DID method supports rotation of the keys to control the DID (worth calling this out, in addition to pre-rotation, as many methods do not support) - Comment by Juan: one thing working with the KERI WG at DIF taught me was that there are like 10 different capabilities/flows that people refer to when they mean rotation. rotation in case of key exfiltration? manual rotation by controller? regular/automated rotation NOT requiring manual controller intervention?."
"title": "Centrally Hosted",
"description": "Hosted on a centralized service, e.g. a web server."
},
"multi-sig": {
"decentrally_hosted": {
"type": "boolean",
"title": "Multi-sig",
"description": "The method supports multiple DID controllers, with multiple key signatures required to update or deactivate the DID - Comment by Juan: same-- threshold versus multisig goes all the way back to christopher allan's BTC pre-DID research and some of the oldest did-wg megathreads, worth picking carefully a definition. joe andreiu probably has something detailed written up about this somewhere.."
"title": "Decentrally Hosted",
"description": "Hosted on a decentralized service, e.g. a DLT."
},
"globally_dereferenceable": {
"universal_resolver": {
"type": "boolean",
"title": "Globally dereferenceable",
"description": "The DID method supports extensible DID URLs to external resources or to specific versions of the DID Document. - Comment by Juan: split into 3 diff ones: service-specific DID URL support, ?versionTime= support, and ?versionId= support . a surprising number of methods support 1 or 2 but not all 3!."
"title": "Universal Resolver Driver",
"description": "DID method has a functional Universal Resolver driver."
},
"publicly_accessible": {
"universal_registrar": {
"type": "boolean",
"title": "Publicly Accessible",
"description": "The DID method has a functional Universal Resolver AND Universal Registrar driver - Comment by Juan: should there be some kind of maintenance requirement or stalebot caveat?."
"title": "Universal Registrar Driver",
"description": "DID method has a functional Universal Registrar driver. - Comment by Juan: should there be some kind of maintenance requirement or stalebot caveat?"
}
},
"required": [
Expand Down
Loading

0 comments on commit 4bda96a

Please sign in to comment.