EDItEUR Releases ONIX 3.1.3 — Four Targeted Changes for a More International Metadata Standard
EDItEUR, the international organisation that maintains the ONIX book metadata standard, has released ONIX 3.1.3, a targeted update introducing four changes: a new structured TextSource element for clearer attribution of reviews and descriptive content; added contextual detail about people or entities featured in a book; adjustments to publisher and imprint name ordering to improve multilingual sorting; and support for transliteration across different writing systems, including a new textscript attribute enabling the same text to be represented in both native script and romanised form. EDItEUR recommends all ONIX 3.1 users migrate to version 3.1.3.
Analysis
ONIX updates rarely make headlines outside the metadata community, but ONIX 3.1.3 deserves attention from anyone who cares about the discoverability of books in languages and scripts that have historically been underserved by the global publishing data infrastructure.
The four changes in this revision are modest in scope but significant in their direction. The TextSource element — which replaces the deprecated TextAuthor, TextSourceCorporate, and TextSourceDescription elements — is primarily a housekeeping improvement, giving publishers a cleaner, more structured way to attribute reviews and endorsements. The addition of contextual detail about featured people or entities addresses a genuine gap in how non-fiction and biography metadata is currently handled.
The two changes that matter most for international publishing are the multilingual sorting improvements and the transliteration support. The sorting fix addresses a problem that anyone who has worked with Latin-language publisher names will immediately recognise: when a publisher's name begins with "Editora," "Editorial," or "Éditions," alphabetical sorting by the first word produces a meaningless cluster that obscures the actual name. The ability to specify an alternative sort order — so that "Editora Companhia das Letras" sorts under "C" rather than "E" — is a small change with a large practical impact on catalogue usability across the Spanish, Portuguese, and French-speaking markets.
The transliteration support is even more consequential. The new textscript attribute allows the same metadata field to carry both a native-script version and a romanised transliteration — so a Hindi title can be represented in Devanagari for Hindi-speaking markets and in Latin script for international distribution systems that cannot handle non-Roman characters. This is not a solved problem in global publishing metadata, and even a targeted improvement in the standard's ability to handle it represents meaningful progress. As EDItEUR's own documentation notes, the previous XSD schema had a bug that made multilingual metadata appear to validate correctly even when it violated the specification — a problem that 3.1.3 also fixes. The recommendation to migrate is well-founded.