Draft 0.2 – open for comment. Changes are expected.

Give feedback

Conventions

Naming, units, ranges, codes, dates, multilingual texts and extension fields used in every block.

File format

A record is a JSON document in UTF-8. Each record describes one product variant with one GTIN. A record MAY contain a $schema property with the URL of the core schema, so that editors can validate it while it is written.

Field names

Field names use camelCase, for example modelName or childHeightCm. Fields that hold a measured value carry the unit at the end of the name: Cm, Kg, Px, Months.

Ranges are objects with min and max, both inclusive. The unit is part of the name of the range: "childWeightKg": { "min": 9, "max": 18 }.

Code values – the allowed values of a field – are written in lower case with words separated by hyphens, for example car-seat or one-hand.

Units

  • Length and dimensions in centimetres (cm).
  • Weight in kilograms (kg).
  • Age in months.
  • Coordinates of 3D models in metres (m).

Numbers are JSON numbers, not strings, and use a decimal point: 6.9, not "6,9".

Identifiers

The primary identifier of a record is the GTIN (Global Trade Item Number) of the variant. GTINs have 8, 12, 13 or 14 digits and a valid GS1 check digit. They are stored as strings so that leading zeros are kept. In GS1 Digital Link URIs, the GTIN is written with 14 digits, padded with leading zeros.

Language codes

Languages are identified by BCP 47 language tags: en, de, de-AT, zh-Hans.

Country codes

Countries are identified by ISO 3166-1 alpha-2 codes in upper case: AT, DE, GB. In the list of markets, EU stands for the whole European Union.

Dates

Dates are ISO 8601 calendar dates: YYYY-MM-DD, for example 2026-02-01. Points in time, such as recordInfo.lastModified, are ISO 8601 date-times with a time zone: 2026-09-15T09:30:00Z.

Localized strings

Texts that consumers read are localized strings: an object with a language tag as key and the text as value.

{ "en": "Never leave your child unattended.", "de": "Lassen Sie Ihr Kind niemals unbeaufsichtigt." }

A localized string has at least one language. Data recipients use the languages they need.

Requirement levels in the schemas

  • A field listed in required of its parent is MUST.
  • Every other field carries the annotation x-openjuvenile-level with should, may or conditional.
  • Conditional fields describe their condition in x-openjuvenile-condition. Where the condition can be checked, the schema enforces it with if/then.

Extension fields

Fields whose names start with x- are allowed at the top level of a record and of every module, for example x-erp-id. Data recipients that do not know an extension field ignore it. Extension fields are not part of the standard. Extension fields MUST NOT carry prices or commercial terms.

No prices or commercial terms

Records describe products. They contain no prices, discounts or other commercial terms, and such data is never part of the data shared under this standard.