search

w3c-ccg / lds-ecdsa-secp256k1-2019

Linked Data Cryptographic Suite for ECDSA Secp256k1 2019
https://w3c-ccg.github.io/lds-ecdsa-secp256k1-2019/
Other
0 stars 5 forks source link

Terms missing from the w3id.org/security/v1 context (but used in the examples) #8

Open jandrieu opened 2 years ago

jandrieu commented 2 years ago

I'm not sure if the intention is to add that term to the JSON-LD context, but both publicKeyJwk and EcdsaSecp256k1VerificationKey2019 are missing today.

Here in example 2 (just because it is shorter) https://w3c-ccg.github.io/lds-ecdsa-secp256k1-2019/#example-2

{
  "@context": ["https://w3id.org/security/v1"],
  "id": "did:example:123456789abcdefghi#keys-1",
  "type": "EcdsaSecp256k1VerificationKey2019",
  "controller": "did:example:123456789abcdefghi",
  "expires": "2017-02-08T16:02:20Z",
  "publicKeyHex" : "034ee0f670fc96bb75e8b89c068a1665007a41c98513d6a911b6137e2d16f1d300"
}

People are using this in the field in exactly the manner used here, which fails to resolve the string to a fully qualified URI since it is not found in the listed context. As such, it is a potentially ambiguous term.

We should either update the context at w3id.org/security or define the term inline something like this:

"@context": [
    "https://www.w3.org/ns/did/v1",
    {
      "EcdsaSecp256k1VerificationKey2019": "https://w3id.org/security#EcdsaSecp256k1VerificationKey2019
",
      "publicKeyJwk": {
        "@id": "https://w3id.org/security#publicKeyJwk",
        "@type": "@json"
      }
    }