Skip to content

Support CredentialQuery with empty elements_dict #48

Open

Description

@GarethCOliver

Currently, Credential Queries must include at least one requested element. There exist a number of niche cases where it may be useful to request no elements. Semantically, this is proving you are in possession of a document of a particular type.

  • This can be used as a 'proof-of-human' signal, as it's a strong proof that this is a user.
  • This can be used with TransactionData in a case where you want something signed, but you don't care about the identity of the user
  • (SD-JWT-VC Specific) You can get back mandatory claims (minorly efficient)

These are pretty niche, but limiting it in-spec doesn't seem particularly desirable, but we can discuss.

Raised by Martijn, this is does then require showing sensible UI for this, which is challenging.

Activity

  1. jogu commented on Sep 7, 2026

    @jogu
    Contributor

    Discussed on today's WG call:

    Should allow it in the spec. SD-JWT VC might have claims that are always disclosed, and in that context requesting no extra claims also makes sense. No obvious reason not to support it for mdocs.

    Should it be mandatory for wallets to support though, given the UX difficulties? Could be let to ecosystem profiles etc.

    OID4VP appears to require wallets to support this (though we're not sure the WG ever explicitly discussed it), and Joseph shared that there is conformance test that sends such a request and expects a credential with no selectively disclosable changes returned.

    18013-5 namespaces in IssuerSigned structure is optional in response, suggesting it's legal to return an mdoc without any claims. An 18013-5 request must request at least one claim.

    Further checking of the spec needed.

  2. andrewhughes3000 commented on Sep 19, 2026

    @andrewhughes3000
    Member

    I thought that for mdoc DeviceRequest, a list of specific data elements to be returned must be provided. And then the mdoc/holder can only respond with those requested data elements (I'm trying to say: "no wildcard requests").
    If an empty CredentialQuery is expected to result in mandatory claims returned if SD-JWT-VC but no claims returned for mdoc, is this a problem? Am I understanding this correctly?

  3. jogu commented on Oct 5, 2026

    @jogu
    Contributor

    Discussed on today's WG call:

    Make this a credential format specific rule.

    Question about whether this can be made optional for wallets to implement as it might not be easy to design UI for the case where there are no claims. It's believed to be mandatory for openid4vp. Making it optional may mean verifiers can't use it in practice.

  4. awoie commented on Oct 15, 2026

    @awoie
    Contributor

    What is the rational of making this a credential format-specific rule?

  5. andrewhughes3000 commented on Oct 15, 2026

    @andrewhughes3000
    Member

    WG discussion:

    • Need to put the rationale to put the rules in the credential format
    • Suggestion to describe what it means to have an empty query for each credential type
    • Discussion back and forth about whether the meaning of the claims is generalizable across credential formats or per-credential type.
    • suggestion to avoid making this feature mandatory for all credential types
    • Existing document types may not define this today - this gap should be fixed there
    • Conclusion: at the protocol level this feature should exist; the author of a "doctype" should be able to declare whether or not this feature is allowed
    • Gareth to create a draft PR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions