-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to register new verification method type? #404
Comments
Examples:
I also maintain a list here as well: https://ns.did.ai/ For example: Can I move this issue to the did spec registries? |
I edited your submission to make it more readable for future searchers. |
Thank you a lot!
From: Orie Steele ***@***.***>
Reply to: w3c/did-core ***@***.***>
Date: Tuesday, 11 January 2022 at 18:32
To: w3c/did-core ***@***.***>
Cc: Jaroslav Saxa ***@***.***>, Mention ***@***.***>
Subject: [External] Re: [w3c/did-core] How to register new verification method type? (Issue w3c/did-core#814)
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.
…________________________________
I edited your submission to make it more readable for future searchers.
—
Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_did-2Dcore_issues_814-23issuecomment-2D1010197933&d=DwMCaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=wh8nBKo6jtXpe7b7SRASSfVwiLjyDDX8VYF1jnhokS0&m=YGCPyD2kEDPRykhb_ggdiCPfStzJ06PMRnA5Sbc70rJZdEAMQOvmyZATOkTQ1KrM&s=Nu1mI45EcEs4uI66Qq-Skdx--26CRfdhR7I_edbeRO8&e=>, or unsubscribe<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMWAB2ABIDK4Z7JLW2MXZ2LUVRSUHANCNFSM5LW4ERDA&d=DwMCaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=wh8nBKo6jtXpe7b7SRASSfVwiLjyDDX8VYF1jnhokS0&m=YGCPyD2kEDPRykhb_ggdiCPfStzJ06PMRnA5Sbc70rJZdEAMQOvmyZATOkTQ1KrM&s=sCRGAAY9Qc8enRZ2oApeuXtNitWzfjWPPJFwNjAgS8w&e=>.
Triage notifications on the go with GitHub Mobile for iOS<https://urldefense.proofpoint.com/v2/url?u=https-3A__apps.apple.com_app_apple-2Dstore_id1477376905-3Fct-3Dnotification-2Demail-26mt-3D8-26pt-3D524675&d=DwMCaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=wh8nBKo6jtXpe7b7SRASSfVwiLjyDDX8VYF1jnhokS0&m=YGCPyD2kEDPRykhb_ggdiCPfStzJ06PMRnA5Sbc70rJZdEAMQOvmyZATOkTQ1KrM&s=cFV4f2voXJgu4bkONxFDp5AlbFakQW69lCqXuST8IKY&e=> or Android<https://urldefense.proofpoint.com/v2/url?u=https-3A__play.google.com_store_apps_details-3Fid-3Dcom.github.android-26referrer-3Dutm-5Fcampaign-253Dnotification-2Demail-2526utm-5Fmedium-253Demail-2526utm-5Fsource-253Dgithub&d=DwMCaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=wh8nBKo6jtXpe7b7SRASSfVwiLjyDDX8VYF1jnhokS0&m=YGCPyD2kEDPRykhb_ggdiCPfStzJ06PMRnA5Sbc70rJZdEAMQOvmyZATOkTQ1KrM&s=bWITFYYseHS17-ji9kRwNcT1DJforz0R0ywEV6ggAd0&e=>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________
www.accenture.com
|
@jaroslavsaxa I have transferred the issue, please feel free to link any work in progress here, and I am happy to review. |
Ah. Thanks. I was afraid to ask. I have an incoming PR that I don't really think should be immediately approved, but also isn't silly. |
<not an issue, but request for help> - We should like to register new verification method type key/signature. Can you please navigate how this can be done in did-spec-registry?
The text was updated successfully, but these errors were encountered: