In CS-02, section 6.1.2 “WU Invocation” currently shows the wallet invocation URI as:
openid4vp://present?request_uri=<URL>
I could not find a normative reference in OpenID4VP or related specifications requiring openid4vp://present specifically, as opposed to the more common/generic form:
openid4vp://?request_uri=
This was also discussed with Nikos Triantafyllou, who suggested opening this issue because the source/reference for making the "present authority" mandatory it's not clear.
Could the spec clarify whether openid4vp://present is intended as a mandatory WE BUILD CS-02 profile requirement or just an example invocation URI?
If it is mandatory, it would be helpful to add an explicit normative statement and rationale/source. If it is only an example, the conformance tests should not reject implementations using other valid OpenID4VP wallet invocation URI forms.
In CS-02, section 6.1.2 “WU Invocation” currently shows the wallet invocation URI as:
openid4vp://present?request_uri=<URL>I could not find a normative reference in OpenID4VP or related specifications requiring openid4vp://present specifically, as opposed to the more common/generic form:
openid4vp://?request_uri=
This was also discussed with Nikos Triantafyllou, who suggested opening this issue because the source/reference for making the "present authority" mandatory it's not clear.
Could the spec clarify whether openid4vp://present is intended as a mandatory WE BUILD CS-02 profile requirement or just an example invocation URI?
If it is mandatory, it would be helpful to add an explicit normative statement and rationale/source. If it is only an example, the conformance tests should not reject implementations using other valid OpenID4VP wallet invocation URI forms.