Behaviour when multiple is used with transaction data

[TimoGlastra]

When the new multiple query field from DCQL is used, what is the intended behaviour for transaction data?

Should all credentials include the transaction data hash, or only the first one? I think a small clarification on intended behaviour might help.

I could find anything in the spec or #398

[c2bo]

Imho multiple and transaction_data should be mutually exclusive. multiple has some level of ambiguity to it by design, whereas transaction_data should only be used when you know exactly what credential you want.

[Sakurann]

+1 to what Christian said

(sorry, did not mean to close)

[TimoGlastra]

Makes sense, we should probably add something to spec for that? It would make the implementation simpler by not having to deal with it

[c2bo]

Yeah, We should add a sentence that transaction_data MUST NOT be used in combination with multiple. I can do a quick PR fixing that if people are fine with a PR clarifying in that direction.