-
As pointed out by @kdenhartog [on X](https://x.com/PryvitKyle/status/1849895350783603085) the current DID draft doesn't include the right context to verify default signing keys.
The `type` key in t…
-
Hi,
it might be out of the scope of this spec, it's not a microservice, but asynchronous issuing is crucial in order to enable:
* an approval process - a process that might involve collecting addi…
-
Reading through #116 it helped me to understand some things. My way of getting my thoughts in order was to try to map what I read to the [security vocabulary](https://w3c.github.io/vc-data-integrity/v…
-
> I generally see risk in statically defining formats this query language works against. I would rather see us leverage a registry with associated guidance on how to plug into the general query langua…
-
_Originally posted by @aljones15 in https://github.com/w3c/vc-di-bbs-test-suite/pull/33#discussion_r1664035031_
> @TallTed as this PR is part of a chain with other tests in it perhaps we should mer…
-
The Verifiable Credentials Working Group is requesting a review of Controller Documents by the end of summer 2024 (ideally, sooner). Controller Documents are a generalization of DID Documents and some…
-
Current draft lacks a clear specification for verifiable presentations using BBS signatures. The specification should clarify whether the verifiable presentation BBS proof value can only be signed, on…
-
As per https://w3c.github.io/vc-jose-cose/
-
- name of spec to be reviewed: BBS Cryptosuite v2023 Securing Verifiable Credentials with Selective Disclosure
using BBS Signatures
- URL of spec: https://www.w3.org/TR/vc-di-bbs/
- Does your doc…
-
A credential issuance endpoint can be posted to multiple times with initially an unsigned credential and then later a signed credential which will have a new proof added to the VC which could use the …