path in query cannot address array elements

DataElementDef.path is [ + tstr ] in the core CDDL. For SD-JWT VC that means a path can only walk JSON object keys; it cannot select an element of an array claim or "all elements" of one. OpenID4VP's claims path pointer allows strings, null (all elements of the current array) and non-negative integers (a specific index) for this, and SD-JWT VC claim metadata uses the same path syntax, so array claims that are common in SD-JWT VCs (e.g. nationalities, address arrays) are not requestable with the current type.

We could widen the type to [ + (tstr / null / uint) ] and give each format definition the semantics of the non-string elements? (mdoc would continue to only use the two-string form).

Raised while moving the format-specific details into annexes (#21 / #22); the SD-JWT VC annex carries an editor's note pointing at this issue.

Start with DataElementDef.path in the core CDDL and the SD-JWT VC annex, including the editor's note. Compare the OpenID4VP claims path pointer rules for strings, null, and non-negative integers, then determine how each format definition handles the added values while mdoc remains unchanged. Done means the type and format-specific semantics are agreed and the note is resolved.