Fix dcqal-mso-mdoc-aamva-namespace - #29
grahamallen-1 wants to merge 3 commits into
Conversation
Update spruce opencred with latest from stateofca
Fix dcqal-mso-mdoc-aamva-namespace
|
Thanks for the fix. Digital Bazaar's active development happens in the canonical |
@djscruggs Do you know of a timeline for OpenCred to support mso_mdoc + W3C VC credentials in a single DCQL? Our understanding is that this is currently not supported. |
Build a single mso_mdoc credential whose claims span every requested namespace instead of one credential per namespace. A query that spanned both the base ISO namespace (org.iso.18013.5.1) and its AAMVA sub-namespace (org.iso.18013.5.1.aamva) previously emitted two credentials sharing a duplicate id: '0' and a bogus doctype_value (org.iso.18013.5.1.aamva.mDL) that wallets reject. All mso_mdoc namespaces belong to the same mDL doctype, so buildMsoMdocCredentials now flattens claims across namespaces and derives doctype_value from the base (shortest) namespace, independent of namespace order. The downstream intent_to_retain stamping is unchanged. Ported from #29 by grahamallen-1 and adapted to the current _buildDcqlQueryForMdoc pipeline.
Fix DCQL
mso_mdoccredential query generation when a query spans both the base ISO namespace (org.iso.18013.5.1) and its AAMVA sub-namespace (org.iso.18013.5.1.aamva). Today this produces an invalid query that wallets reject.