Relationship between controller
property and DID controller
#326
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #122 has a lot of back-and-forth about the relationship between the
controller
property and the actual DID controller, aka the entity that can edit the DID document.The original issue was about whether we can assume the DID subject (aka an entity that can authenticate itself with verification material contained in the DID doc.. I think?) is default controller in the absence of a
controller
property. (Short answer to that being 'no'.)I'm not sure there's consensus, so I've added a NOTE presenting one set of perspectives from that thread, which is basically that the
controller
property is indicative but ultimately who/what can or cannot edit a DID doc, and under what circumstances, is up to the DID method,controller
property or no.I'm not sure if there's normative language to be developed from this, happy to iterate.