IMO, this reads better and avoids the ambiguity around short space of time. ```suggestion If batch issuance is supported, the Wallet SHOULD use it rather than making consecutive requests for a single Credential of the same Credential Dataset. The Issuer MUST indicate whether batch issuance is supported by including or omitting the `batch_credential_issuance` metadata parameter. The Issuer’s decision may be influenced by various factors, including, but not limited to, trust framework requirements, regulatory constraints, applicable laws or internal policies. ```

As per discussed at https://github.com/openid/OpenID4VC-HAIP/pull/229/files#r2303730339 I'd made a suggestion to clarify what "Wallet MUST support batch issuance" means: ```suggestion The Wallet MUST NOT make multiple single requests for the same credential in a short space of time if the Issuer supports batch issuance. The Issuer MUST indicate whether batch issuance is supported by including or omitting the `batch_credential_issuance` metadata parameter. The Issuer’s decision may be influenced by various factors, including, but not limited to, trust framework requirements, regulatory constraints, applicable laws or internal policies. ``` Kristina said elsewhere that this "makes sense to me"; would be good to get other opinions.

```suggestion The Wallet MUST support batch issuance. The Issuer MUST indicate whether batch issuance is supported by including or omitting the `batch_credential_issuance` metadata parameter. The Issuer’s decision may be influenced by various factors, including, but not limited to, trust framework requirements, regulatory constraints, applicable laws or internal policies. ``` Batch issuance is a server-wide setting, so cannot be done per credential configuration.

Maybe this reads better? ```suggestion Note: See Section 15.4.1 of [@!OIDF.OID4VCI] and Section 15.5 of [@!OIDF.OID4VP] for preventing linkability by colluding Issuer/Verifier, Verifier/Verifier pairs, or by the same Verifier. ```