Kristina

> we should split the current verification algorithm in two, where one algorithm covers validation of the base SD-JWT properties (issuer JWT valid, all disclosures accounted for), and the other...

not sure why is would be an RDF description and not an entity statement as defined in OpenID Federation specification?

+1 to "adopting the [OpenID Connect Federation](https://openid.net/specs/openid-connect-federation-1_0.html) definition of an [Entity Identifier](https://openid.net/specs/openid-connect-federation-1_0.html#name-entity-statement) and [Automatic Registration](https://openid.net/specs/openid-connect-federation-1_0.html#name-automatic-registration). I think it is one of the best approaches out there right now that meets...

Issue #95 seems to be referencing the Federation draft too

Below is the definition of the VP Token from OID4VP. I think it's pretty clear VP Token != W3C VP? > VP Token: An artifact defined in this specification that...

VP Token is not a JWT in itself (it's a VP itself it or an array of VPs) so no 'typ'. Do you mean PR in this repo or in...

[here](https://openid.bitbucket.io/connect/openid-4-verifiable-presentations-1_0.html#section-6.1-2.2) is definition of VP Token fromt the spec: > JSON String or JSON object that MUST contain a single Verifiable Presentation or an array of JSON Strings and JSON...

resolved by #96, which also removed section 7.2.7 and 7.2.8 from -00 from HAIP and refers to VCI.

as I said in https://github.com/openid/oid4vc-haip-sd-jwt-vc/issues/103#issuecomment-2129806601, the intention of HAIP was that the issuer has to issue using two key resolution mechanisms - web-based key resolution (.well-known/jwt_vc_issuer with or without openid...

yes, `a trust model and a trust mechanism needs to be built on top HAIP`. the HAIP intends to be silent on this exact question: "How does a credential issuer...