-
We have conducted a self-review of our spec [Verifiable Credentials Data Model v2.0](https://www.w3.org/TR/vc-data-model-2.0/), and the results can be found at https://github.com/w3c/vc-data-model/iss…
-
## Expected Behavior
A response with appropriate error code should be send to verifier when an exception occurs while decrypting request.
According to document ISO 18013-5, section 9.1.1.4 Table 2…
-
I think we should use short JWT-style names for the type and status list claims in order to show that these claims are at the core of the JWT (just like `exp`, `iss`, etc.). I therefore propose that w…
-
Currently we use Hardware-Backed Android KeyStore for `CredentialKey` and `DeviceKey` which means that the private part of those keys never leave Secure Hardware. Concretely the Secure Hardware is whe…
-
Here are some suggestions on how section "[5.8 Zero-Knowledge Proofs](https://www.w3.org/TR/vc-data-model/#zero-knowledge-proofs)" in the W3C VC Data Model v1.1 could be improved.
The title may be …
-
## Expected Behavior
During NFC engagement HRM with AC (alternative carriers) records are generated by the reader and parsed by mdoc holder to form HSM single AC selected.
In the case reader include…
-
It seems to me that we can definitively say that the flow proposed in this PR is not compliant to:
[oauth-attestation-based-client-authentication](https://vcstuff.github.io/draft-looker-oauth-attes…
-
## Expected Behavior
As per ISO 18013-5(8.3.3.1.1.3) Standard
Device retrieval mdoc response should contain an error code 0 for the missed item that are requested from the verifier.
## Actual Beh…
-
In order to prevent the number of digests leaking any information, ISO-18013-5 suggests adding additional digests that do not correlate to any of the hidden elements. The recently suggested format of …
-
We've recently been toying around with the idea of how to enable verifiable credential validation when it's not possible to retrieve arbitrary context files. One of the ways we've looked to get around…