decentralized-identity / decentralized-identity/did-registration

Define a way to polyfill method specific driver in to a browser API

Open
#19 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
HTML
Stars
11
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Thinking about where I see this going, I think one of the clear places I could see this getting implemented would be as a Browser API since DIDs have been standardized at W3C. However, one thing that's certain is that browser vendors won't want to support every did method under the sun so I'm thinking it would be useful for us to define a method to polyfill a method into the browser so that the standard interface APIs could be used by them. Then browser vendors would only need to implement 1 or 2 did methods by default with the additional option that a new method can be added into the browser very easily while also converging their usage in a meaninful way like this spec does.

What's your thoughts on adding a addMethodDriver operation in a way that would allow for the create API to call those methods using the polyfill?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.