Update context links for the signature suites

[kdenhartog]

I noticed some of the signature suites still point at the did-core context rather than the split out ones. This is an issue to track those and get them updated.

[OR13]

We have addressed this issue, it should be closed, and its not actionable.

[OR13]

Look we have done this like this: https://w3c.github.io/did-spec-registries/#jsonwebkey2020

https://w3c-ccg.github.io/lds-jws2020/

[iherman]

The issue was discussed in a meeting on 2021-10-19

• no resolutions were taken

View the transcript

5.1. Update context links for the signature suites (issue did-spec-registries#310)

See github issue did-spec-registries#310.

Michael Prorock: +1 close

Orie Steele: this one is stale, seems closeable

Daniel Burnett: sidebar: fine to proceed a little faster with an "any objections?"

Manu Sporny: a link to a PR that closed this issue would be nice

Manu Sporny: +1 to close.

[kdenhartog]

Uh not sure what you mean? the context link points at this:
https://www.w3.org/ns/did/v1

not this: http://w3id.org/security/suites/jws-2020/v1

All of the signature suites that point at the did-core context are incorrect now that the did-core context doesn't include suites so anyone relying on the did-core context to get their suite definitions will be inadvertently dropping public keys in their did documents when using the JSON-LD representation. I think this should remain open until that's fixed.