Objection: Disconnect between what a description/specification of a DID Method is vs. the description/specification of a specific DID Method Implementation

[mwherman2000]

...and hence, the expected Purpose, Intended Audience, and Objectives for a DID Method specification document is muddy/unclear.

...and hence, inconsistent assessment criteria and banter has resulted for newly submitted DID Method Registry pull requests.

Desired Resolution: The expectations for DID Method specification document's Purpose and Scope, Intended Audience and Objectives requirements need to be clarified and made explicit. Anything related to an Implementation should be moved to beneath an Implementation Guidance and/or Reference Implementation level 2, non-normative section.

I will be withdrawing #383 and resubmitting a new pull request for a refactored version 1.5 of the "DID Object" Method specification with the above considerations in mind.