Author DCQL queries

A DCQL query tells a wallet which credentials and claims the verifier needs. Queries are tenant resources with an immutable version history; verifier bindings and verification templates reference them by id and pinned version, and trust attachments by id.

Complete first: Set up the verifier.

Steps and why they come in this order

Step	Why here
1. Review existing queries	Queries are shared by templates and attachments. Reuse or version an existing query rather than creating a near duplicate.
2. Create and edit a query	The query must exist before a template or attachment can reference it.
3. Derive a query from semantic-model channels	When credentials are governed in the semantic model, derive the query mechanically instead of hand-writing claim paths.
4. Manage query versions	Templates can pin a version. Read the history before pinning and restore when a change must be undone.

Format-specific claim paths

Credential	DCQL format	Type match	Claim paths
SD-JWT VC	dc+sd-jwt	meta.vct_values	JSON claim names such as family_name
ISO mdoc	mso_mdoc	meta.doctype_value	Namespace and element such as org.iso.18013.5.1/family_name
W3C VCDM 1.1 JWT	jwt_vc_json	VCDM 1.1 context and types	Paths below the VCDM 1.1 credential
W3C VCDM 2.0 JWT	jwt_vc_json-ld	VCDM 2.0 context and types	Paths for the VCDM 2.0 credential

Do not reuse an SD-JWT claim path for mdoc or a VCDM 1.1 query for a VCDM 2.0 credential.

Deeper reference

DCQL REST API, DCQL Store and DCQL Authoring describe the store, PUT versus PATCH semantics and the channel projection. The Postman folder 3. Tenant APIs > Verify credentials creates a DCQL query and binds it to the verifier.

Next journey

Continue with Build trust domains and anchors.