Closed rhiaro closed 5 years ago
Per discussion in 2019-05-09 DID Spec and DID Resolution Spec meeting, @jandrieu will review and potentially propose changes.
Ping @jandrieu: We discussed this on last Thursday's call; do you have any further feedback on this? Otherwise I think we'll merge it soon.
Per discussion in 2019-05-30 DID Spec and DID Resolution Spec meeting, this will be merged in 3 days from now unless there is any additional feedback.
A starting point; I expect people will have lots of opinions about what goes in here.
The Unique DID Method Names section tries to strike a balance between explaining why the DID Method Registry is useful, without implying it's authoritative or required, and without being too defensive about its existence at all.
@talltree's original proposal was to call it "Governance of DID Method Namespaces" but I thought "governance" implied a bit more authority or even just process than perhaps we want to associate with the DID Method Registry.
Also there might be a better place in the spec for this section.
I also added a very short section in Security Considerations because if I understand correctly potential non-unique DID method names could be an attack vector. This might warrant expanding on in the future, but I kept it brief for now.
Preview | Diff