DCQL queries in production: 7 real verifier scenarios

DCQL (Digital Credentials Query Language) is the part of OpenID4VP that decides "what does the verifier ask for, and how flexibly?" The spec examples are great but skinny — what does it look like when you wire it to real use cases?

We documented seven we run end-to-end:

• Basic query with trusted authority — https://docs.igrant.io/docs/dcql-basic-credential-query-with-trusted-authority/

• Age verification (claim set) — https://docs.igrant.io/docs/dcql-2-4-2-claim-set-age-verification

• Identity proof alternatives (credential set) — https://docs.igrant.io/docs/dcql-2-4-3-credential-set-proof-of-identity-alternatives/

• KYC with photo ID + address proof — https://docs.igrant.io/docs/dcql-2-4-4-kyc-request-photo-id-address-proof/

• Student transport pass — https://docs.igrant.io/docs/dcql-2-4-5-student-transport-pass/

• Loan application with multiple bank statements — https://docs.igrant.io/docs/dcql-2-4-6-loan-application-multiple-bank-statements/

• Delivery service with restricted postal codes — https://docs.igrant.io/docs/dcql-2-4-7-delivery-service-restricted-postal-codes/

What DCQL patterns are you running into that aren't covered? The spec is still maturing — would love to hear what's awkward.