DID Method Proposal Template: a couple thoughts

[mwherman2000]

Around 50 minutes into this week's call, the conversation revolved around how the DID Method Proposal Template might evolve over time as we learn more about what we're trying to do. Here's a couple thoughts:

1. Think of the DID Method Proposal Template as a introductory stub document for an eventual specification document. That is, as we learn more about that we want a specification document to look like, we can add more of those sections to the Proposal Template. Anyone making a submission for the DID Method, can fill in as many of the sections as they are able but at a minimum, they would need to complete the sections (we currently have) in the Introduction.
2. By extension, it is possible anyone is able to complete a fully documented DID Method Specification for vetting by the WG. i.e. not everyone has to start with the minimum required Introduction section. i.e. they don't have to complete 2 separate documents.

Thoughts?
@peacekeeper

[peacekeeper]

+1 that we can add more sections to the template as we learn more...

And I think we definitely want to encourage selecting DID methods that already have some existing specs or other materials, rather than starting from zero. But in this case, I think still everyone who wants to propose a DID method should fill out the template.

[mwherman2000]

The idea is for each "template" to beocome a living document that "grows up" into a specification (through the addition of additional mandatory and optional sections).

[peacekeeper]

living document that "grows up" into a specification

Actually I think it would be better to keep that separate. The proposal should just be a short document that we use in the beginning of the process, whereas the specifications are much more formal and have to include specific sections that are mandated by DID Core... Also, I expect that this group will probably pick DID methods that already have advanced specifications, rather starting from zero.