add did-method-plc registration

w3c / did-spec-registries

DID Spec Registry (Note)

https://w3c.github.io/did-spec-registries/

Other

117 stars 193 forks source link

add did-method-plc registration #515

Closed bnewbold closed 1 year ago

bnewbold commented 1 year ago

DID Method Registration

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

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

(the auto-validation tests require repo maintainer approval before they run, I think)

cc: @dholms

bnewbold commented 1 year ago

Gentle ping to reviewers: @msporny @OR13 @mprorock

OR13 commented 1 year ago

I noticed https://w3id.org/security/suites/ecdsa-2019/v1 is 404, I assume you are not actually doing any JSON-LD processing.

You might have meant to use https://w3id.org/security/suites/secp256k1-2020/v1

You probably didn't mean to use these:

https://w3c.github.io/vc-di-ecdsa/

https://w3id.org/security/data-integrity/v1

But you should be aware of them if you intend to support NIST Curves and JSON-LD in the future, while also using multibase.

bnewbold commented 1 year ago

Thanks for the catch @OR13! Created a follow-up issue for us to track. We do indeed not use JSON-LD validation actively, but should ensure we aren't pushing broken DID documents. In the context of our registry and did:plc semantics, this should be a pretty straight-forward thing to fix.

https://github.com/bluesky-social/did-method-plc/issues/32

bnewbold commented 1 year ago

Pushed a tiny change to update our contact email.

Just to clarify the current state of this PR/registry: while we will address the @context URLs in our DID documents soon, we assume that this registration isn't blocking on that.

OR13 commented 1 year ago

@bnewbold correct, JSON-LD issues do not block registration here, there are 2 media types for DIDs which were requested, but afaik, neither has been registered with IANA.

application/did+json and application/did+ld+json.

The first does not require @context, the second does, but regardless of the presence of the member, it won't be used for anything other that schema checks, until you do some JSON-LD process on the document.