localization (number, date, etc)

[willfarrell]

I've been thinking a lot around creating data standards, defined by JSON Schema - data stored in csv, that are used by multiple locales. Creating multiple schema with different patterns and external code to transform values into en-US or ISO to be validated against the schema is the current approach, but would be nice if the spec was more inclusive. Just want to start the discussion around what it could look like in the spec, if this is best handled at the implementation layer, and/or what are best practices people are using.

Intl.NumberFormat

Currently type:"number" accepts 1234.56 and if coercion is supported, "1234.56"

Numbers can also be written like "1,234.56", "1 234.56", "1.234,56", "1 234,56", depending on the locale. Could there be a new format to support validating these number formats based on a locale, passed in as an option or as part of the spec?

Ref: ajv-validator/ajv#2099

Intl.DateTimeFormat

Same as Intl.NumberFormat, but for dates. In this case the ISO standard is used, and not en-US which I think is the right approach, but should be considered for consistency.

locale modifier

Ability to choose a what sub-schema to enforce based on the locale of the data. An example would be enum lists in different languages.

{
  // similar to `not`?
  "locale:fr-CA": {
    ...
  }
}

For context, my locale is en-CA.

[gregsdennis]

The numeric format is specified by JSON, which is not something that we can alter. Further (and discussed elsewhere), numbers as strings is not something that we currently support.

In regard to the rest, for numerous reasons, we're recommending against using and/or expanding format. It's touched on in that issue I linked above. Essentially, these would best be supported as a vocabulary.

Lastly, there are many other issues/discussions that relate to the topic of localization:

• Proposal: Standardize validation error and introduce new keyword messages json-schema-spec#1241
• Add "messages" property json-schema-spec#148
• Localization, Multilingual annotations (including enum), localized schema $id and their relation to $ref and $merge preprocessing json-schema-spec#278
• v6 annotation: custom error messages while validating json-schema-spec#62
• i18n support via new keywords "defaultLocale", "locales", and "locale… json-schema-spec#12

[willfarrell]

Thanks so much for the resources, looks like I have some reading to do. Didn't think to look at the historical issues, sorry about the re-post.