Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend purpose field for DCQL #391

Open
cre8 opened this issue Jan 22, 2025 · 1 comment
Open

Extend purpose field for DCQL #391

cre8 opened this issue Jan 22, 2025 · 1 comment

Comments

@cre8
Copy link

cre8 commented Jan 22, 2025

This is not something for 1.0, but maybe 1.1 to extend DQCL usage

In the context of OID4VP, the purpose is a string which is fine for multi language support (using the information from the request to insert the correct translation on demand).

In our case we want to include the DCQL inside JWS, where it is static. It would be great to give multiple strings for the purpose to prevent the wallet to translate it by itself (and in the worst case in this happens in the wrong way). One suggestion to extend it in the future would be:

[
    {
        "locale": "en-US",
        "name": "Required for checking the minimum age",
    },
    {
        "locale": "de-DE",
        "name": "Benötigt für die Überprüfung des Mindestalters"
    }
]
  • locale: REQUIRED: String value that identifies the language of this object
    represented as a language tag taken from values defined in BCP47 RFC5646.
    Multiple display objects MAY be included for separate languages. There MUST be
    only one object for each language identifier.
  • name: REQUIRED: String value that defines the purpose.

To not break existing usage, I suggest the type of purpose would be string and this type.

@c2bo
Copy link
Member

c2bo commented Jan 22, 2025

Related issue: #289

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants