Closed anthonycamilleri closed 1 month ago
By my reading of the section 10.1, this approach seems to be supported, but the current language makes it a bit unclear if only examples described in the VC standard are supported, or whether any internationalisation approach supported by the JSON-LD standard is supported.
Language maps are supported. Any i18n mechanism supported by JSON-LD is supported by VCDM.
That said, there were multiple organizations that objected to using advanced JSON-LD features. So, the best we could do in the specification is to try and find a middle ground. That resulted in this section:
https://w3c.github.io/vc-data-model/#type-specific-credential-processing
as well as the general section on JSON-LD usage:
https://w3c.github.io/vc-data-model/#json-ld
At present, I don't think we'll be able to get consensus to recommend language maps. They are already allowed per the specification, perhaps we can say more about them being allowed since you read the spec and it wasn't clear to you.
Given the above, what sort of language would you like to see in the specification around this topic?
I believe the right pointer is https://w3c.github.io/vc-data-model/#language-and-base-direction and not what @msporny put into his comments
The issue was discussed in a meeting on 2024-05-01
The issue was discussed in a meeting on 2024-05-29
The issue was discussed in a meeting on 2024-06-12
The issue was discussed in a meeting on 2024-06-19
The issue was discussed in a meeting on 2024-06-26
The issue was discussed in a meeting on 2024-07-03
The issue was discussed in a meeting on 2024-07-17
PR #1532 was merged to address this PR, closing.
The issue was discussed in a meeting on 2024-07-31
In the European context, multilingual credentials are commonplace. The typical use case is to have approx. 30 languages which may be used for a credential-type, with any individual credential being typically expressed in 2-3 languages. For this kind of use case, it makes sense for us to use JSON-LD language indexing, as specified here https://www.w3.org/TR/json-ld11/#example-71-language-map-expressing-a-property-in-three-languages. This approach is the one currently adopted in the European Digital Credentials scheme.
By my reading of the section 10.1, this approach seems to be supported, but the current language makes it a bit unclear if only examples described in the VC standard are supported, or whether any internationalisation approach supported by the JSON-LD standard is supported.
The suggestion would be to explicitly mention language-maps as a supported approach, and possibly include a language map as an example.