[UPDATE: The most recent version of the ONIX codelists may be found here.]
ONIX Code lists Issue 38 for ONIX 3.0 has been released.* In addition to the code lists, EDItEUR has also issued new specifications and an implementation and best practices guide.
It should go without saying that everyone should review the changes document and update their systems, but we've highlighted some changes of particular note for you below.
All products
New support for linked products — a List 168 price condition value allows users to set a price for when multiple products are bought from a list. For example, two for one deals or similar offers.
Microsoft has a List 139 retail sales outlet ID, and a code value for LP records has been added as a List 150 audio product form.
Physical products
Three new measure codes cover the situation when the product sold by retailers has packaging that will be removed by consumers. The familiar codes for height, width and thickness are used to describe what you ship to retailers (and that's normally the same as what consumers get) but the new codes allow you to provide the size of the product actually used by consumers in the event that is meaningfully different.**
Digital products
A new List 81 content type code for scripting can be used when an e-publication contains microprogramming within it (e.g. JavaScript). There are also new dates in supply date role List 166 to control products supply and availability after the product has been withdrawn from sale. (Withdrawal ends sales to new customers but existing product owners maintain access to downloads and DRM support. These new codes allow communication about ending that access.)
There are many more changes and updates in Issue 38, please reference the full list for details.
EDItEUR supports ONIX code lists in multiple formats:
ONIX Code list Issue 38 Changes in release
Standalone documents (PDF & HTML)
Files for loading into data systems
Schema modules (XSD, RNG, DTD)
*A note to ONIX 2.1 users
ONIX 2.1 users should note that code list 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 code lists from the Archived Previous Releases page.
BookNet still recommends that you use and periodically update your copy of EDItEUR's best practices guide. It is an essential ONIX 3.0 guide, but much of the information in it applies equally to ONIX 2.1.
BookNet would like to pause, catch it's breath, and note to ONIX 2.1 users that there is now a full decade — 10 years — of new development available to users in ONIX 3.0. You should be considering what your systems need to support. ONIX 3.0 is easier to develop than you think, and it supports greater accuracy and detail in all aspects of data trading.
**Updated Aug. 9, 2017. Previous version had an inaccurate explanation of these new codes.