support haip:// instead for openid4vp:// scheme for use cases that fall under the haip profile

[endimion]

https://openid.net/specs/openid4vc-high-assurance-interoperability-profile-sd-jwt-vc-1_0.html

4.1. Credential Offer

As a way to invoke the Wallet, at least a custom URL scheme haip:// MUST be supported. Implementations MAY support other ways to invoke the wallets as agreed by trust frameworks/ecosystems/jurisdictions, not limited to using other custom URL schemes

[lalc]

Does this have an impact on rfc001/rfc002?

If no, could we capture these into the itb RFC?

[endimion]

If I understand the spec correctly, yes we should actually add it explicitly to RFC002, since its part of the VP spec when using HAIP. @georgepadayatti what do you think?