New normative document proposal: Supporting Multiple Languages in JSON

[BigBlueHat]

I've begun work on extracting the Value Object shape used in the JSON-LD Syntax v1.1 specification. It provides a foundation for consistent handling of multiple languages, but because it only exists in the JSON-LD Syntax specification many people overlook it or believe more is required for parsing it.

This new standalone specification would extract details on the Value Object syntax to be used for the primary purpose of encoding multi language strings in a fashion that has previously been approved during I18N reviews of the v1.1 specifications.

The specification would specifically describe this style of object construction following the limitations defined in Value Object:

{
  "occupation": {
    "@value": "Scientist",
    "@language": "en",
    "@direction": "ltr"
  }
}

This specification would not specify Language Maps nor the setting of any language defaults for an entire JSON document.

This specific specification would be targeted at only the Value Object syntax, parsing, and processing.

[gkellogg]

Discussed on the 2024-05-29 CG meeting. Feeling was that this should be a WG Note.

[pchampin]

Propose to close after the merge of #4.