-
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 …
-
- bstr / [ 2*certs: bstr ] is referenced
- X.509 header must be placed in the unprotected bucket
-
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…
-
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…
-
Can we support the localisation for schema attributes and value?
To achieve this do we need to implement this functionality on react-native app side or on Aries agent side by implementing the below…
-
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…
-
Why was ISO/IEC JTC 1/SC 17/WG 10 removed from the external organizations? It was in the vc-data-model 1.0 charter.
-
For the purposes of privacy-enhancing mobile credentials, I propose that the PEMC WG use the following as an operational definition of privacy for the recommendation. I came up with this starting from…
-
@awoie commented, in relation to references:
>add ISO 18013-5 ? NFC -> BLE/Wifi-Direct, QR Code -> BLE/Wifi-Direct