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

Add test vectors that use i18n strings #218

Closed
msporny opened this issue Oct 21, 2023 · 1 comment
Closed

Add test vectors that use i18n strings #218

msporny opened this issue Oct 21, 2023 · 1 comment
Assignees
Labels
CR1 This item was processed during the first Candidate Recommendation phase. editorial This issue or PR constitutes an editorial change.

Comments

@msporny
Copy link
Member

msporny commented Oct 21, 2023

The test vectors use human-readable strings and the i18n group requested that we express them using the appropriate @language/@direction values across vc-data-integrity, vc-di-eddsa, and vc-di-ecdsa. This is a tracking issue to make sure we update the test vectors to conform to i18n guidance.

@msporny msporny added the CR1 This item was processed during the first Candidate Recommendation phase. label Oct 21, 2023
@msporny msporny added the editorial This issue or PR constitutes an editorial change. label Feb 25, 2024
@msporny msporny assigned msporny and unassigned Wind4Greg Jun 28, 2024
@msporny msporny changed the title Update examples to use i18n strings where pertinent Add test vectors that use i18n strings Jul 21, 2024
@msporny
Copy link
Member Author

msporny commented Jul 21, 2024

Transferring this issue to w3c-ccg/data-integrity-test-suite-assertion#83 since it's the best way that we can enforce what the I18N group would like to see.

@msporny msporny closed this as completed Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CR1 This item was processed during the first Candidate Recommendation phase. editorial This issue or PR constitutes an editorial change.
Projects
None yet
Development

No branches or pull requests

2 participants