Disclaimer: I'm new here 馃槈
It looks like to add EcdsaKoblitzSignature2016 (coming soon once https://github.com/w3c-dvcg/lds-koblitz2016/pull/4 is merged) to https://web-payments.org/contexts/security-v1.jsonld we would add a line to that context like this:
"GraphSignature2012": "sec:GraphSignature2012",
"LinkedDataSignature2015": "sec:LinkedDataSignature2015",
"LinkedDataSignature2016": "sec:LinkedDataSignature2016",
+ "EcdsaKoblitzSignature2016": "sec:EcdsaKoblitzSignature2016",
"CryptographicKey": "sec:Key",
And then add a new section for EcdsaKoblitzSignature2016, linked to by https://web-payments.org/vocabs/security#EcdsaKoblitzSignature2016, directly after the existing LinkedDataSignature2016 section.
Sound about right?
Tagging @msporny 馃啒
Disclaimer: I'm new here 馃槈
It looks like to add EcdsaKoblitzSignature2016 (coming soon once https://github.com/w3c-dvcg/lds-koblitz2016/pull/4 is merged) to https://web-payments.org/contexts/security-v1.jsonld we would add a line to that context like this:
"GraphSignature2012": "sec:GraphSignature2012", "LinkedDataSignature2015": "sec:LinkedDataSignature2015", "LinkedDataSignature2016": "sec:LinkedDataSignature2016", + "EcdsaKoblitzSignature2016": "sec:EcdsaKoblitzSignature2016", "CryptographicKey": "sec:Key",And then add a new section for EcdsaKoblitzSignature2016, linked to by https://web-payments.org/vocabs/security#EcdsaKoblitzSignature2016, directly after the existing LinkedDataSignature2016 section.
Sound about right?
Tagging @msporny 馃啒