Christian Bormann
Christian Bormann
One of the quirks of SD-JWT is that the disclosures themselves can be encoded however the issuer deems right. There is no necessity to define rules like always using minified...
This is kind of related to #46: When looking through the example in Aries [RFC 0067](https://github.com/hyperledger/aries-rfcs/blob/main/features/0067-didcomm-diddoc-conventions/README.md), I got a bit confused where the second context (identity.foundation/didcomm-messaging/service-endpoint) in the example DID...
Section 4.2 states: > MUST use the scope parameter to communicate credential type(s) to be issued. The scope value MUST map to a specific Credential type. The scope value may...
Section 7.1. defines supported key resolution mechanisms to validate issued credentials. We do not define a mechanism to validate the status list with currently. Imho, we should re-use the same...
closes the batch endpoint part of #286
The Appendix introduces specific claims for Authorization Details for mdoc and sd-jwt vc type credentials. For both of them a new claim `claims` is introduced as > claims: OPTIONAL. Object...
As discussed in last DCP call, there are some examples in the examples folder of this repository that are currently not referenced in the spec. This is the list of...
Plenum uses a freshness check to make sure the current state of the system has a certain freshness in the audit ledger with default values of ``` UPDATE_STATE_FRESHNESS = True...
The current iteration of the ARF (1.4) uses two different credential formats and it is likely that credential formats and especially proof types will evolve over time. There is already...
Client Metadata is first introduced in Section 5 without referencing the section where it is/should be defined (Section 9). `jwks` and `jwks_uri` are also used without mentioning that section. `client_metadata`...