ONIX Codelist 68 released

Codelist Issue 68 for ONIX 3.0 has been released.* Complete listings of the ONIX codelists can be downloaded from the EDItEUR website.

• Issue 68 stand-alone codelist documentation as a readable PDF or HTML file (open and read it in your web browser)

• Issue 68 TXT, CSV, XML, JSON files for loading into your data management applications

• Issue 68 XSD, RNG, DTD schema modules for use with existing XML schema files (but note that it's better to download the latest 3.1 schemas since they incorporate a couple of small improvements as well as the new Block 8)

• The ‘strict’ XSD 1.1 with Issue 68 (the strict XSD must be updated each time there is a new issue of the codelists, as it includes some codelists within the XSD itself)

• The online browser for the ONIX code lists at ns.editeur.org/onix has been updated to issue 68

Need help finding and using the documentation? Read this.

It should go without saying that everyone should review the document summarizing the changes and update their systems, but we've highlighted some changes of particular note for you below. This is a weighty list and we encourage you to read the whole document, not just the following highlights.

List 17 – Contributor role

New code B35 has been added to reflect the role of “image descriptions by,” which EDItEUR defines as the “creator of alternative image descriptions for accessibility purposes.”

List 18 – Person / organization name type

If you work in publishing, you will have a healthy love/hate relationship with acronyms, and the addition of new code 08 to list 18 is unlikely to surprise. Use code 08 to reflect acronyms, initials, and short abbreviations for the full name. Use only within <AlternativeName> with a corporate name.

List 73 – Website role

New code 52 has been added, to reflect a type of website for “publisher’s or third party contact form,” for which EDItEUR gives an example of “a web page providing an interactive contact form for safety-related issues.” Publishers and data senders interested in supporting the EU’s General Product Safety Regulation (GPSR) will find value in this new code addition.

List 74 – Language

Continuing the expansion of this list with codelist 63’s numerous additions to include several publishing languages used by First Nations, Inuit, and Métis people in the lands now called Canada, List 74 now includes code “oka” for the Nsyilxcən language.

List 79 – Product form feature type

Continuing its effort to address all requirements of the forthcoming European Union Deforestation Regulation (EUDR), EDItEUR has introduced new code 54 to allow data senders to share an “EUDR stock present attestation. It confirms ALL stock provided to suppliers in the EU predates the publisher’s appropriate EUDR deadline.** This replaces the need for a Due Diligence Statement (DDS) but not the obligation to provide documentation if requested.

Any subsequent stock would require submission of a DDS which would include an equivalent statement making this code redundant. It’s a good practice to remove this value when DDS information is added.

** December 30, 2025 or June 30, 2026 for micro- and small enterprises as defined here.

List 262 – Carbon/GHG emissions certification scheme

The new addition to this list has a Canadian connection! It follows the launch of two free-to-use Sustainable Publishing Tools, carbon calculators designed specifically for publishing industry professionals, that emerged from a collaboration between New Society Publishers and ECW Press, with funding from the Canada Council for the Arts through the Digital Greenhouse grant.

To reflect per book carbon calculations measured through the Sustainable Publishing Tools, data senders should use code 202.

Interested in learning how to use the Sustainable Publishing Tools? Attend a free webinar on Thursday, February 13, 2025: learn more about the webinar here or reserve your spot.

French translations of the tools are coming soon, courtesy of BTLF (La Société de gestion de la banque de titres de langue française).

*A note to ONIX 2.1 users

ONIX 2.1 users should note that codelist updates no longer apply to ONIX 2.1 and users should continue to use Issue 36. ONIX 3.0 code lists and schema modules no longer contain codes or lists unique to ONIX 2.1. You can still obtain the correct ONIX 2.1 schema and codelists from the Archived Previous Releases page.

BookNet Canada still recommends that you use and periodically update your copy of EDItEUR's best practices guide. It’s an essential ONIX 3.1 guide, but much of the information in it applies equally to ONIX 2.1.