-
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…
-
The W3C V1.0 Data Model has little focus on the role of the holder, despite it's inclusion in Figure 1 of the spec. There is little normative text about the holder, and the data item "holder" is only …
-
There are many different ways of implementing selective disclosure. Some send the whole credential with blinded property names and values, others send atomic credentials, others send assertions and pr…
-
- bstr / [ 2*certs: bstr ] is referenced
- X.509 header must be placed in the unprotected bucket
-
The example https://www.w3.org/TR/vc-data-model/#identifiers gives the following description for id:
>The value of the id property MUST be a single URI. It is RECOMMENDED that the URI in the id b…
-
# New Work Item Proposal
## Include Link to Abstract or Draft
The purpose of this work item is to demonstrate a path to interoperability between the ISO-18013-5 Mobile Driver's License data mod…
-
The following is proposed as a way of categorizing PEMC requirements based on the type of actor that is participating in mobile credential transactions. Using abstract use cases enables PEMC requireme…