Charles E. Lehner
Charles E. Lehner
This adds a definition to the namespace document for the following term: as specified in the following specification draft. Specification draft: https://w3id.org/security/suites/eip712sig-2021 Source: https://github.com/w3c-ccg/ethereum-eip712-signature-2021-spec Issue about suite registration: https://github.com/w3c-ccg/ethereum-eip712-signature-2021-spec/issues/37 Cryptosuite...
The security context references https://w3id.org/security#. But https://w3id.org/security redirects to https://w3id.org/security/, which redirects to https://w3c-ccg.github.io/security-vocab/, which does not return JSON-LD - even if the HTTP Accept header is set to `application/ld+json`...
In `lib/NQuads.js`, string literals are escaped. But IRIs are not. [RDF 1.1 N-Quads](https://www.w3.org/TR/n-quads/#terminals) includes this production: ```ebnf [10] IRIREF::='' ``` Here is a test showing a statement with a IRI...
Currently this specification draft says the verification method type must be `EcdsaSecp256k1VerificationKey2019` or `EcdsaSecp256k1RecoveryMethod2020`. However, there are other verification method types that can be used to verify Secp256k1 signatures. e.g.:...
- [x] Add context file: https://github.com/w3c-ccg/ethereum-eip712-signature-2021-spec/pull/22 - [x] Register context under w3id.org: https://github.com/perma-id/w3id.org/pull/2298 (URI: https://w3id.org/security/suites/eip712sig-2021/v1) - [x] Update specification text to describe JSON-LD context: https://github.com/w3c-ccg/ethereum-eip712-signature-2021-spec/pull/31 - [x] Mention security limitations...
From https://github.com/w3c/spec-prod/blob/main/docs/examples.md#deploy-to-github-pages - Build and test on pull-request - Deploy to `gh-pages` branch on push to `main` Deploying the built version enables the spec to work better in browsers without...
- [ ] https://w3c-ccg.github.io/security-vocab/#EthereumEip712Signature2021: https://github.com/w3c-ccg/security-vocab/pull/129 - [x] ~~https://www.w3.org/TR/did-spec-registries/~~ - not needed - no new verification method - [ ] https://w3c-ccg.github.io/ld-cryptosuite-registry/#signature-suites: https://github.com/w3c-ccg/ld-cryptosuite-registry/pull/39 - [ ] https://w3c-ccg.github.io/vc-extension-registry/#proof-methods
Test vector proposed by @haardikk21 in #26, but I haven't been able to verify it: https://github.com/w3c-ccg/ethereum-eip712-signature-2021-spec/pull/26/files#r799759138
Continue editing from #20 and #26, applying minor changes in sections 5 and 6. - Improve case (capitalization) consistency - Fix typos - Reduce use of normative-sounding language - Attempt...
The example (https://w3c-ccg.github.io/did-resolution/#example-11) is inconsistent with the algorithm (https://w3c-ccg.github.io/did-resolution/#algorithm). The example says: > Given the following input service endpoint URL: > > `https://example.com/messages/8377464` > > And given the following input...