Closed 617640999 closed 4 months ago
In method-specific-identifier section I'd like a little more explanation about
method-specific-id
. Of course, we can know SM3 format by reading SM3 specification, but I'd like some information on length, etc.Example
method-specific-id = <hexdigit>{64} hexdigit = [0-9A-F]
I have modified the explanation about method-specific-id
in https://github.com/617640999/ctid-did-register/commit/e44aa3d50cf199726122edadd7431d0fc918c1fb, please check again whether it meets the registration requirements. Thanks!
Is it possible to clearly dissociate the security aspects from the privacy considerations in the last section? Please, try to clearly point out in the security part as present in the document at https://w3c.github.io/did-core/#security-requirements
Thanks for your review, I have updated my registration request to split security and privacy considerations into two points. Please help review again. link to this registration
Could you please review it for me? @msporny @MizukiSonoko @gatemezing @ajile-in @genaris @KDean-Dolphin @apuchitnis @adam-burns @stenreijers @Steffytan @rajivrajani
Please add more to the security and privacy considerations sections. For an example look at DID Core:
* https://www.w3.org/TR/did-core/#security-considerations * https://www.w3.org/TR/did-core/#privacy-considerations
Thank a lot for your review. I have revised it. Please review it again. here is the link
My registration has been approved twice. Could you please help me merge this PR ? @msporny
DID Method Registration
As a DID method registrant, I have ensured that my DID method registration complies with the following statements:
contactEmail
address [OPTIONAL].verifiableDataRegistry
entry [OPTIONAL].