Closed kimdhamilton closed 5 years ago
I think we should actually allow defining methods as an option.
In particular, I'm sensitive to the pushback we've had around method namespace collisions. There may be a solution using a meta-method that, by necessity, needs to be standardized.
I'm not sure that's the right answer or even a good one, but I don't want to preclude the DIDWG from considering it. This is especially relevant since the CCG as the namespace czar (because of the did method registry) is not quite a complete solution.
Merge conflicts, rebase, please.
"DID method implementation" or "DID method specification"? (The latter is the term currently used in the DID spec.)
I assume both specifying DID methods AND implementing them is out of scope?
Merge conflict fixed
Clarify that publishing a specific DID method implementation is out of scope, and that the DID specification is modeled after the URI spec (RFC 3986)
Addresses #21.