The document outlines standards goals and updates for 2023. It discusses the introduction of ONIX 3.1, which is not fully backwards compatible with 3.0. It provides examples of deprecated elements in ONIX 3.1 and guidance on updating documentation and code to reflect changes. The document also seeks input on how often standards bodies should manage changes to deprecations and outlines new elements added in ONIX 3.1.

1. Standards Goals for 2023
Tom Richardson
May 25, 2023
Standards and Certification

2. Land Acknowledgement

3. What’s with BiblioShare and ONIX 3.0?
Mea culpa

4. Retail
Database
ONIX
Record

5. ONIX 2.1
Record
ONIX 2.1
BiblioShare
API Output

6. ONIX 3.1
Record
ONIX 3.1
BiblioShare
API Output
ONIX 2.1
Record
ONIX 2.1
BiblioShare
API Output

7. ONIX 3.1
Record
ONIX 3.1
BiblioShare
API Output

8. BISG Statement
on
Misuse of the title and subtitle fields
https://www.bisg.org/statement-on-misuse-of-the-title-and-subtitle-fields
Released May 2023

9. Not following the definitions provided in
a standard defeats the purpose of having the
standard.
Senders need to create metadata before retail
use can happen
Retailers need to use the data they are sent –
following its named purpose

10. We have to admit that standards will change
and agree on how to communicate about that
so that implementation actually occurs in
a timely manner.

11. Introducing ONIX 3.1
&
Why it isn’t ONIX 3.0.9

12. It’s ONIX 3.1 because it is no longer
fully backwards compatible with 3.0
A full list of all deprecated elements can be found in an
appendix in the Specification:
A.4 List of elements removed from Release 3.1

13. It’s not a problem
because there’s almost no use of what’s
been removed. Mostly, just be sure you
update your documentation
AND

14. stop or don’t use anything that’s labeled
as
“Deprecated”
in the new documentation.
That is how
upcoming removals to ONIX
are marked.

15. ONIX for Books
version 3
is considered stable enough that it has
to support changes that affect version compatibility.
ONIX data senders and receivers need a stable
standard
– it’s cheaper – but in addition to supporting new
data with each version update they should consider
the need to plan for change
based on the standard’s requirements
if they want to remain within it.

16. EDItEUR is seeking input
about removing deprecations:
If 12 years is clearly too long
and
if version updates that are around
every second year seems too short:
How often and how should they manage this
kind of change?

17. The most common use of newly removed data in
BiblioShare’s ONIX 3.0 archive is “dual data” providing
the deprecated and expected presentation
<AudienceCode>03</AudienceCode>
<Audience>
<AudienceCodeType>01</AudienceCodeType>
<AudienceCodeValue>03</AudienceCodeValue>
</Audience>
The bit in red is the deprecated AudienceCode
Deprecated tags and composites

18. Example date composite – this is a birth year coded to
show the “date format” is atypical:
<ContributorDate>
<ContributorDateRole>50</ContributorDateRole>
<DateFormat>05</DateFormat>
<Date>1935</Date>
</ContributorDate>
What’s in red above is deprecated and should appear as
an attribute in the <Date> tag:
<ContributorDate>
<ContributorDateRole>50</ContributorDateRole>
<Date dateformat=“05”>1935</Date>
</ContributorDate>
Deprecated tags and composites

19. PromotionContact (k166) use <ProductContact>
Gender (x524) in the Contributor composite has been
removed and has no equivalent in release 3.1
Removed Conference & Reissue & their elements
Duplicated support removed for
-- Sales Restrictions only available within Sales Rights
-- P.7.47 Unnamed Persons (b249) use P.7.20a
Deprecated tags and composites

20. ALL default values in the Header
composite
• H.17 Default language of text
• H.18 Default price type
• H.19 Default currency
Newly deprecated in ONIX 3.1

21. P.5.10 / P.6.5 TitleText (b203)
Use TitleWithoutPrefix in all entries
<NoPrefix/>
<TitleWithoutPrefix>Book Title</TitleWithoutPrefix>
<TitlePrefix>The</TitlePrefix>
<TitleWithoutPrefix>Book Title</TitleWithoutPrefix>
Newly deprecated in ONIX 3.1

22. EDItEUR is seeking input
about removing deprecations:
If 12 years is clearly too long
and
if version updates that are around
every second year seems too short:
How often and how should they manage this
kind of change?

23. • Version changes are when new composites
and elements are added to support new data
and functionality
– Typically happens every 1 ½ to 2 years
– The current version is ONIX 3.1
• Issue Changes are when new codes are added
to existing code lists
– Typically happens 4 times a year
– The current issue is Issue 61

24. • Update your ONIX Specifications at least yearly
– It has minor corrections and tweaks made regularly
– Always update it after a version change
– Absolutely update it when there are newly
deprecated data points
• Understand how your software updates code
list issue changes
– Ensure that staff using the code lists has access to
“full” versions that include the explanatory Notes.

25. Use version updates to review ONIX for metadata that
might benefit your business
• ONIX 3 has had 9 version updates since 2009 and they
are summarized in the Specification’s Introduction
• Ask BookNet for help if you’re unsure:
– If any potential targets have use in BiblioShare,
– You’re unsure how to implement them,
– You’re unsure of the purpose of any metadata
structure or code,
– Your business has something to say, a
communication need and metadata might help.

26. Tell your trading partners (and BookNet) if you
add or need additional metadata support.
Don’t rely on them finding your changes.

27. • Added <SequenceNumber> to allow explicit
prioritization of Block 2 Collateral material
• Added <AwardingBody> within <Prize>
• Added <MarketReference> to enable market-
specific partial (‘Block’) updates
What’s New in ONIX 3.1

28. • Added <CollectionFrequency> to carry
frequency of publication of products in a
collection
• Added <CollectionElementLevel> to enable
linking of Collection identifiers to specific
collection title elements
What’s New in ONIX 3.1 for Collections

29. • Added a <AffiliationIdentifier> composite
within <ProfessionalAffiliation>
• Added <EpubUsageConstraint>, extended
<EpubLicense>, <Publisher> and
<CopyrightStatement> within Block 3
<ContentItem> to support hybrid open
access (ie per-chapter licensing)
What’s New in ONIX 3.1

30. Other additions and changes
• <EpubLicenseDate> in <EpubLicense> within
<DescriptiveDetail> (but not within <Price>), to
enable future licensing changes
• <Website> within <NewSupplier>
• Added <FaxNumber> within <ProductContact> &
<SupplyContact> and removed deprecation from
contact details within <PublisherRepresentative> &
<Supplier>, to improve consistency of various
composites
What’s New in ONIX 3.1

31. Newly added in 2023 for
the Issue 61 code list update
List 153 Text Type Code 37 “Cover line”
• (US) Reading line – line of usually explanatory copy
on cover, somewhat like a subtitle but not on the
title page and added by the publisher, eg ‘with 125
illustrated recipes’

32. Added in 2009 for the Issue 10 code list update
and supported by both ONIX 2.1 and 3.1
List 153 Text Type Code 10
“Promotional Headline”
• A promotional phrase which is intended to
headline a description of the product

33. Transparency by all players

34. Standards BNC is involved in
• EDI
• Subject Schemes
– BISAC
– Thema
• Identifiers
– ISBN/GTIN/ISNI
• Others...
– ISO/W3C
GDSN/SAN
• BISG (US)
– Metadata
– Subjects
– Supply-chain (EDI)
– Identifiers & Workflow
• EDItEUR
– ONIX Int Steering
Committee
– Thema Int Steering
Committee
• BTLF (Quebec)

35. BNC Bibliographic Committee
Canadian English Language
– National Group for ONIX
– National Group for Thema

36. Diversity Equity Inclusion
Identity Indigeneity & Justice
for book subjects & author promotion
A place for participation
Both BISAC and Thema are adding values to help buyers find books
that include various diversity related values.
Getting it right is hard as evidenced by the rapid decline in use of “own
voices” after it was found the association lead to potentially unsafe and
uncomfortable situations for book authors.
As much as we want a button that will make it easy to create a timely
list bird books by black authors, or just to promote well vetted list for
use during Indigenous or Black History months, getting it right takes
well thought out positions and choices.
Big problems are solved by participation
and sharing of information.

37. Thank you
trichardson@booknetcanada.ca
booknetcanada.ca/newsletter-sign-up

38. Slide Title
• slide text
– bullets
• lot of text
– more bullets