Draft 0.2 – open for comment. Changes are expected.

Give feedback

Introduction

Purpose, scope and structure of the specification, and how to read its requirement levels.

Purpose

OpenJuvenile defines a shared format for the product data of juvenile and toy products. A brand describes a product once, in one record, and every shop, product information management (PIM) system and marketplace can read the same record – including the safety information that EU law requires in online offers.

The format builds on what exists: GTIN and GS1 Digital Link for identification, JSON Schema for the definition of fields, and the standards for the EU Digital Product Passport. It adds the fields that generic standards do not know, such as height ranges of car seats, folded dimensions of strollers, adapter compatibility, test evidence against EN standards and 3D/AR assets.

Scope

Version 0.2 covers:

  • the core of a product record, which applies to every juvenile or toy product,
  • the blocks compliance, media and compatibility,
  • the category profiles for strollers and car seats.

Further category profiles are planned: nursery furniture and mattresses, carriers, feeding, textiles, safety products and toys.

The specification describes data. It is not software, not a marketplace and not a standard of a standardisation body such as CEN or DIN. Nothing in it is legal advice.

Structure of a record

A record is a JSON document that describes one product variant, identified by its GTIN. Core fields sit at the top level, including recordInfo with the publisher and the time of the last change. The blocks compliance, media and compatibility are objects with their own schema, and category profiles sit under profiles:

{
  "specVersion": "0.2",
  "recordInfo": { "publisher": { "…": "…" }, "lastModified": "2026-09-15T09:30:00Z" },
  "gtin": "9521234567899",
  "brand": { "name": "Example Brand" },
  "modelName": "Pebble Travel Stroller",
  "category": { "code": "stroller" },
  "profiles": { "stroller": { "…": "…" } },
  "compliance": { "…": "…" },
  "media": { "…": "…" },
  "compatibility": { "…": "…" }
}

Every block has a fixed tone and pattern that is used throughout this site:

  • Core Identity, brand, manufacturer, dimensions, weights, multilingual texts and lifecycle status.
  • Category profiles Required and recommended fields for one product category, such as strollers or car seats.
  • Compliance Applied regulations, standards with version, test reports, warnings per language, manufacturer and EU responsible person, link to the Digital Product Passport.
  • Media Image roles, documents and 3D/AR assets with real-world scale and variant assignment.
  • Compatibility Which seat fits which stroller, with which adapter, from which model year.

Requirement levels

The key words MUST, SHOULD and MAY are used as described in RFC 2119.

  • MUST – a record is only valid with this field.
  • SHOULD – recommended. A missing field does not make a record invalid, but lowers its completeness.
  • MAY – optional.
  • MUST if – required when the stated condition applies, for example the EU responsible person when the manufacturer is established outside the EU.

The level of a nested field applies when its parent object is present.

Conformance

A record conforms to version 0.2 when it is valid against the JSON Schemas of this version. The schemas are the normative part of the specification. The field tables in these chapters are generated from them.

Roles

  • Data supplier – a brand, manufacturer, importer or distributor that creates and maintains records. The publisher of a record is named in recordInfo.publisher.
  • Data recipient – a shop, retailer, marketplace, PIM system or other platform that reads records.
  • Solution provider – a company that builds software or services that write or read records.

Exchanging records

Version 0.2 defines the record. How records are exchanged between companies – transport, batches and notifications of changes – is not yet specified. recordInfo.lastModified and recordInfo.revision already let data recipients detect changes.

Status of this document

This is draft 0.2, published for public comment. Changes are expected. Comments can be sent through the feedback form; until the association and its working groups are set up, they are read by the contact person for the draft. How the standard changes after version 1.0 is described under Governance.