w3c
Horizontal Review: Internationalization self test
This short review is for the following spec: DID Resolution 1.0.
-
[ ] If the spec (or its implementation) contains any natural language text that will be read by a human (this includes error messages or other UI text, JSON strings, etc, etc), ensure that there’s metadata about and support for basic things such as language and text direction. Also check the detailed guidance for Language and Text direction.
Comments_go_here.
- [ ] Not applicable
-
[ ] If the spec (or its implementation) allows content authors to produce typographically appealing text, either in its own right, or in association with graphics. take into account the different typographic styles used around the world (for things such as line-breaking, text justification, emphasis or other text decorations, text selection and units, etc.) Also check the detailed guidance for Typographic support.
Comments_go_here.
- [x] Not applicable
-
[ ] If the spec (or its implementation) allows the user to point into text, creates text fragments, concatenates text, allows the user to select or step through text (using a cursor or other methods), etc. make allowances for the ways different scripts handle units of text. Also check the detailed guidance for Text-processing.
Comments_go_here.
- [x] Not applicable
-
[ ] If the spec (or its implementation) allows searching or matching of text, including syntax and identifiers understand the implications of normalisation, case folding, etc. Also check the detailed guidance for Text-processing.
Comments_go_here
- [x] Not applicable
-
[ ] If the spec (or its implementation) sorts text ensure that it does so in locally relevant ways. Also check the detailed guidance for Text-processing.
Comments go here.
- [x] Not applicable
-
[ ] If the spec (or its implementation) captures user input ensure that it also captures metadata about language and text direction, and that it accommodates locale-specific input methods.
Comments go here.
- [x] Not applicable
-
[x] If the spec (or its implementation) deals with time in any way that will be read by humans and/or crosses time zone boundaries ensure that it will represent time as expected in locales around the world, and manage the relationship between local and global/absolute time. Also check the detailed guidance for Local dates, times and formats.
There is a versionTime parameter that can be passed into DID resolution. The spec requires that this DateTime value be normalized to UTC 00:00:00
- [ ] Not applicable
-
[ ] If the spec (or its implementation) allows any character encoding other than UTF-8. make sure you have a convincing argument as to why, and then ensure that the character encoding model is correct. Also check the detailed guidance for Characters.
Comments go here.
- [x] Not applicable
-
[ ] If the spec (or its implementation) defines markup ensure support for internationalization features and avoid putting human-readable text in attribute values or plain-text elements. Also check the detailed guidance for Markup & syntax.
Comments go here.
- [x] Not applicable
-
[ ] If the spec (or its implementation) deals with names, addresses, time & date formats, etc ensure that the model is flexible enough to cope with wide variations in format, levels of data, etc. Also check the detailed guidance for Local dates, times and formats.
Comments go here.
- [x] Not applicable
-
[ ] If the spec (or its implementation) describes a format or data that is likely to need localization. ensure that there’s an approach in place which allows effective storage and labelling of, and access to localised alternatives for strings, text, images, etc.
Comments go here.
- [x] Not applicable
-
[ ] If the spec (or its implementation) makes any reference to or relies on any cultural norms ensure that it can be adapted to suit different cultural norms around the world (ranging from depictions of people or gestures, to expectations about gender roles, to approaches to work and life, etc).
Comments go here.
- [x] Not applicable
Short i18n review checklist is here
@peacekeeper the only question I wasn't sure about was number 1. The DID resolution spec does have error messages.
Do we ensure that there’s metadata about and support for basic things such as language and text direction?
This was discussed during the #did meeting on 31 July 2025.
View the transcript
w3c/did-resolution#144
Wip: This is the internationalization self-test that I did a bit ago.
Wip: What happens at this point?
manu: Yes we should just leave this issue open until the horizontal review happens....
manu: we can close it after they complete their review...
ivan: Maybe it's worth putting text in issue that says that this spec doesn't deal w/ human readable text, it's for machine-to-machine communication. I18N is not really relevant for this specification... but making that clear for i18n is helpful.
Wip: That's my sense, most of the questions were not applicable.
ivan: The same applies for a11y as well.
