add did:dsr method

[iamstd-zch]

Instructions for Pull Requests

Please read these instructions thoroughly in order to ensure that your pull request is processed in a timely manner. This document contains detailed instructions for registering a DID Method. If your pull request concerns some other change to the repository, you may delete all of the text in this text box and write up a more relevant description.

There is a DID Method Registration form below that MUST be included in a DID Method Registration Request. The form includes check boxes that you are expected to fill out when you submit your request.

Once you submit your request, your pull request will be reviewed by the registry editors. Changes regarding the required criteria may be requested. If there are no objections or changes requested, your DID method will be registered after a minimum of 7 days.

DID Method Registration Process

In order to register a new DID method, you must add a JSON file to the ./methods directory.

Here is an example registration entry:

{
  // These fields are required
  "name": "example",
  "status": "registered",
  "specification": "https://w3c-ccg.github.io/did-spec/",
  // These fields are optional
  "contactName": "W3C Credentials Community Group",
  "contactEmail": "",
  "contactWebsite": "",
  "verifiableDataRegistry": "DID Specification"
}

Your Pull Request will be automatically validated, please ensure that all of the automated tests pass (no errors reported) or your submission will not be reviewed. Common reasons for failed validation includes invalidly formatted JSON files and missing mandatory fields.

----- DID METHOD REGISTRATION FORM: DELETE EVERYTHING ABOVE THIS LINE ------

DID Method Registration

As a DID method registrant, I have ensured that my DID method registration complies with the following statements:

• The DID Method specification defines the DID Method Syntax.
• The DID Method specification defines the Create, Read, Update, and Deactivate DID Method Operations.
• The DID Method specification contains a Security Considerations section.
• The DID Method specification contains a Privacy Considerations section.
• The JSON file I am submitting has passed all automated validation tests below.
• The JSON file contains a contactEmail address [OPTIONAL].
• The JSON file contains a verifiableDataRegistry entry [OPTIONAL].

[MizukiSonoko]

There is insufficient explanation about DID Method Specific Identifier.
Could you add examples and logic.
Regards

[iamstd-zch]

There is insufficient explanation about DID Method Specific Identifier. Could you add examples and logic. Regards
i have add examples and create logic progress as following,
dsr-did = "did:dsr:" dsr-specific-idstring
dsr-specific-idstring = subnamespace ":"
namestring = 16128(base58char)
subnamespace = *ALPHA *(ALPHA / DIGIT / "_" / "-")
base58char = "1" / "2" / "3" / "4" / "5" / "6" / "7" / "8" / "9" / "A" / "B" / "C"
/ "D" / "E" / "F" / "G" / "H" / "J" / "K" / "L" / "M" / "N" / "P" / "Q"
/ "R" / "S" / "T" / "U" / "V" / "W" / "X" / "Y" / "Z" / "a" / "b" / "c"
/ "d" / "e" / "f" / "g" / "h" / "i" / "j" / "k" / "m" / "n" / "o" / "p"
/ "q" / "r" / "s" / "t" / "u" / "v" / "w" / "x" / "y" / "z"

dsr-did example as following: did:dsr:123456789abcdef123456789abcdef123456789abc

you can see detail here: https://github.com/iamstd-zch/dsr-did/blob/main/dsr-did-specification.md

thank your advice

[w3cbot]

pchampin marked as non substantive for IPR from ash-nazg.

[msporny]

The DID Method specification does not contain enough information in the CRUD or Security/Privacy Considerations sections to implement. No work seems to have been done on the DID Method in the last six months.

Please add more implementation details to each section so that we might understand how this DID Method is intended to work. At a minimum, more effort will need to be put into the Security Considerations and Privacy Considerations sections.

[swcurran]

I agree that there is insufficient information to determine if this is a DID Method or not. There is no explanation of the binding between the UUID DID specific identifier and a related Ethereum address.