clarification of the subjects of the requirements and recommendations

[hdfrk]

Most of the requirements and recommendations in this document clearly states the subjects, such as Issuer, Wallet, and Verifier. However, there are several requirement and recommendation texts where the subjects are missing, which would make the readers who are not fully familiar with the specifications confused to implement.
It would be better to examine each requirements and recommendations to check missing subjects in the texts before the publication.

For example, the first two requirements in the subsection 5.2 do not state the subjects, but the latter two state the subjects.

5.2. OpenID for Verifiable Presentations via W3C Digital Credentials API

The following requirements apply to OpenID for Verifiable Presentations via the W3C Digital Credentials API:

• Wallet Invocation is done via the W3C Digital Credentials API or an equivalent platform API. Any other mechanism, including Custom URL schemes, MUST NOT be used.
• The Response Mode MUST be dc_api.jwt.
• The Verifier and Wallet MUST use Annex A in [OIDF.OID4VP] that defines how to use OpenID4VP over the W3C Digital Credentials API.
• The Wallet MUST support both signed and unsigned requests as defined in Annex A.3.1 and A.3.2 of [OIDF.OID4VP]. The Verifier MAY support signed requests, unsigned requests, or both.

[tlodderstedt]

proposal "The Wallet MUST support Wallet Invocation ivia the W3C Digital Credentials API or an equivalent platform API. The Verifier MUST use it. Any other mechanism, including Custom URL schemes, MUST NOT be used. ".
proposal "The verifier MUST set the Response Mode MUST to dc_api.jwt and the wallet must support that Response Mode".
@fkj please do a RP.