Licences of the standard

  • The specification, the JSON Schemas, the code lists and the examples are licensed under the Creative Commons Attribution 4.0 licence (CC BY 4.0): free to use, share and adapt, also commercially, with attribution.
  • Code and tools, such as the validator, are licensed under the Apache License 2.0, which includes a patent licence from every contributor of code.

Contributions

Contributions are proposals, comments, text, schema changes, examples and code given to the organisation – in working groups, through the feedback form, by email or in a repository.

  • Contributions are licensed under the same licence as the part of the standard they are made for: CC BY 4.0 for the specification, schemas and examples, Apache 2.0 for code.
  • Whoever contributes confirms that they have the right to do so – for example because the contribution is their own work or because their employer agrees.
  • Contributors keep their copyright. They do not transfer it to the organisation.
  • Contributions must not contain confidential information of the contributor or of third parties.

Patents

The standard is meant to be implemented royalty-free. Members who take part in a working group commit to the following for the parts of the specification that the group produces while they take part:

  • Royalty-free licence. For patent claims that are necessarily infringed by implementing the specification (essential claims), they grant every implementer a worldwide, non-exclusive, royalty-free licence. The licence covers implementing the specification only.
  • Defensive suspension. The licence may be suspended towards an implementer who asserts its own essential claims against the member for implementing the specification.
  • Disclosure. Participants disclose patents and patent applications they know of that could contain essential claims, as early as possible, regardless of who holds them.
  • Alternatives. If a patent is not available under royalty-free terms, the working group looks for a solution that does not need it.

The name and the logo

The name “OpenJuvenile” and the logo identify the standard. They will be held by the organisation once it is founded. Using the name to refer to the standard is welcome – for example: “Exports product records in the OpenJuvenile format, version 0.2.”

  • The name is not used in a way that suggests endorsement by the organisation, membership or certification that does not exist.
  • The name is not used as part of a product, company or service name.
  • The logo is not changed and only used for the standard itself.
  • Statements about certification are only made as described in the certification programme.

Standards and identifiers of others

The standard refers to standards, identifiers and code lists of other organisations, such as GS1 identifiers, EN standards and EU legislation. Their rights stay with their owners. To use a GTIN, for example, a company needs a GS1 company prefix; European standards are available from the national standards bodies. This policy does not grant any rights to them.

Questions and disclosures

Questions and patent disclosures: hello@openjuvenile.org.

Last updated: October 2026