Vous êtes sur la page 1sur 65

Book

Metadata
&ONIX
practicalguidance
andbestpractice

March4&5,2013
Fulldayprofessionaldevelopmenttraining
sponsoredbytheBookIndustryStudyGroup
ATTENDEEPACKET

ONIX: practical guidance


and best practice
Graham Bell
EDItEUR

New York City


4th, 5th March 2013

!
!

EDItEUR, 3941 North Road, London N7 9DP, UK

+44 20 7503 6418

info@editeur.org

www.editeur.org

ONIX: practical guidance


and best practice
Graham Bell
EDItEUR

New York City


4th, 5th March 2013

About me
20 years experience at the point where
publishing and technology meet

formerly senior manager in IT department


for HarperCollins UK

led development of bibliographic, editorial and


digital asset management systems
involved in e-book, e-audio, print-on-demand
and online projects

joined EDItEUR in mid-2010, primarily


responsible for ONIX development

About EDItEUR

not-for-profit membership organisation


develops, supports and promotes metadata
and identification standards for the book,
e-book and serials supply chains

acknowledged centre of expertise on

standards and metadata for the industry

based in London, but a global membership


of publishers, distributors, wholesalers,
subscription agents, retailers, libraries,
system vendors, rights organizations and
trade associations

About EDItEUR

also provides management services to

International ISBN, ISTC, ISNI Agencies

EDItEUR has three full-time staff, two FTE

project staff, plus consultants from both the


book and serials sectors

we also work closely with other standards

organisations, to ensure our standards meet


the needs of their stakeholders too

member participation is vital to ensure that


standards keep pace with evolving business
requirements

EDItEUR members (books)


more than 100 members, from 20 countries

15 new members over last 24 months

distribution, metadata and retail companies


including B&N, Ingram, B&T, Nielsen, Bowker

major publishers including Hachette, Random


House, Pearson, HarperCollins, Macmillan, Wiley

trade organisations including BISG, BIC (UK),


NTCPDSAC (China), JPO ( Japan), IDPF
systems vendors including Publishing Technology,
Klopotek, Virtusales, Giant Chair

represent entire supply chain

EDItEUR family of standards


ONIX descriptive metadata

ONIX for Books

EDItX Sales Reporting etc

ONIX for Identifier Registrations


ONIX for Subscription Products (Serials)
ONIX for Publication Licences

EDItX transactional messages


older EDIFACT and ICEDIS EDI messaging

Identifier services
provide full management service to the

International ISBN Agency, plus secretariat


support for the International ISTC Agency
and International ISNI Agency

Executive Director of the International ISBN


Agency is an EDItEUR employee
EDItEUR works closely with 160 national ISBN
Registration Agencies, and 10 ISTC
Registration Agencies

maintain and promote correct use of identifiers,


onbehalf of the Registration Authorities

Special projects
WIPO Enabling Technologies Framework

encourage publishers to produce more accessible


products for print-impaired readers

EC ARROW Plus

develop shared infrastructure for Books-in-Print


services in smaller EU countries

EC Linked Heritage

develop commercial links to the Europeana online


digital library portal

DCH-RP beginning 2013

About today
the backgound what is ONIX?
ten minute XML
the ONIX data structure
how ONIX data feeds work
tricky parts of the ONIX message

examples and best practice for ONIX 2.1 and 3.0


print and e-books

What is ONIX?

What is ONIX?

the ONIX for Books Product Information

Message is the international XML-based


standard for representing and
communicating book trade information in
electronic form

Typical use cases


a publisher needs to provide information
about its catalogue of products to a
distributor, wholesaler, retailer or other
supply chain partner

includes both current and forthcoming products

scope extends over the full lifecycle for book,


e-book and other products ie includes postpublication updates to price and availability

may cover basic product information and a wide


range of collateral material

Typical use cases


a specialist data aggregator or other

organisation providing data services needs


to collect metadata from many sources, and
redistribute consolidated data about
products to supply chain partners

this may include managing the authority of


data received from multiple data suppliers
can add value to the data, through aggregation,
or input of editorial effort
data conversion on input or output

Typical use cases


a distributor, wholesaler, retailer or library

needs to collect metadata from its suppliers


to populate its internal systems

may include both internal catalogue and


consumer-facing systems such as an online
store
currency and authority is a key concern, to
maintain quality of customer service
supply chains are no longer constrained by
national boundaries needs to work in multinational, multi-language, multi-currency world

database

database

Editorial Planeta

Casa del Libro

Publishers

Retailers

Editorial Planeta

Publishers

Publishers

Publishers

Publishers

Retailers

unsupportable
if data files are
all unique

Retailers

central
agencies
or data
aggregators

Retailers

simpler if
standard
data file

Retailers

export
database

ingest
database

ONIX for Books is a standardised message


specification, not a database

but what you can deliver in your ONIX is


dependent on the design of your
in-house database
ONIX data model often used to guide design of
internal applications

Roots of ONIX
1997 EPICS and BIC Basic
1998 <indecs> project
1998 W3C XML specification
1999 Online Information Exchange initiative
from AAP Digital Issues working party

ONIX developed by EDItEUR, originally in

collaboration with BISG (USA) and BIC (UK)

2000 ONIX v1.0, 1.1 and 1.2 retired


July 2001 ONIX v2.0 retired

Roots of ONIX
1997 EPICS and BIC Basic
1998 <indecs> project
1998 W3C XML specification
1999 Online Information Exchange initiative
from AAP Digital Issues working party

ONIX developed by EDItEUR, originally in

collaboration with BISG (USA) and BIC (UK)

2000 ONIX v1.0, 1.1 and 1.2 retired


July 2001 ONIX v2.0 retired

Roots of ONIX
current status

June 2003 ONIX v2.1 most widely deployed


April 2009 ONIX v3.0 growing in importance

widely used in North America, Western


Europe, Japan, Russia, parts of Eastern
Europe, with early implementations in
China and Egypt

used by small and large organisations

included in many off-the-shelf IT systems, but


also plausible for in-house developers

ONIX governance
no fees payable for use of standard

documentation is available free of charge

membership supports development, and


members help identify new requirements

covered by permissive EDItEUR licence

standard is managed by EDItEUR

all changes discussed by National Groups to


ensure broad international applicability
ratified by an International Steering
Committee to ensure some stability

http://www.editeur.org/files/about/EDItEUR%20
IPR%20licence%20v06%20-%2008-12-09%20%5BFINAL%5D.pdf

Commercial effects
ONIX standards support the business needs
of a wide range of stakeholders

have transparent governance, independent


from particular commercial pressures

encourage competition by levelling the

playing field, promoting interoperability,


reducing vendor lock-in, lowering cost

support choice and change by decoupling


interfaces from applications

http://www.cabinetoffice.gov.uk/sites/default/files/resources/Open-Standards-Principles-FINAL.pdf

Commercial effects
provides an industry lexicon
reduction of technical risks
enables benchmarking against competitors
promotes service quality, lowers customer
service costs

certification can generate brand value


can broaden supplier base
easier entry to international trade

ONIX business benefits


for publishers supply of rich metadata in a
single, standard format, for all downstream
needs

for distributors, retailers efficient, timely


delivery and aggregation of data from
multiple publishers

a shared language
single source of truth about products

ONIX business benefits


for publishers supply of rich metadata in a
ks/

single, standard format, for all downstream


needs

r-Boo

for distributors, retailers efficient, timely

/5/ON
rg.uk
http:/
/www
.bic.o

a shared language
single source of truth about products

IX-fo

delivery and aggregation of data from


multiple publishers

for publishers supply of rich metadata in a

delivery and aggregation of data from


multiple publishers

a shared language
single source of truth about products

/5/ON
IX-fo
r-Boo

for distributors, retailers efficient, timely

ks/

single, standard format, for all downstream


needs

http:/
/www
.bic.o
rg.uk

http://www.bisg.org/what-we-do-21-15-onix-for-books.php

ONIX business benefits

Showing 1324 of 841,539 results

Here, the average sales across all records with incomplete BIC Basic elements are 1,113 copies per title, with the complete records
seeing an 98% increase in average sales.
We can further break this down to compare the effect seen for online sales with those seen through physical book shops, which we
will refer to as offline sales. Figure 1.3 shows the change experienced across these two channelsiii.

Titles that meet the BIC


Basic standard see average
sales 98% higher than those
that dont meet the standard.
fig. 1.3 Average sales per ISBN for records with complete or incomplete BIC Basic data and an image in offline and online book retailers
We see here that there is a more marked difference in average sales for offline retailers than online retailers, where we might have
expected the opposite to be true. The offline retail channel sees sales rising 124% for titles meeting the BIC basic standard, whereas
online retail sales see growth of 48%.
Looking at the effect of supplying this basic level of metadata by genre shows differences in the degree to which average sales are
affected, but in all cases the records with more complete metadata have average sales significantly higher than those with
incomplete data. Figure 1.4 shows this across the four broadest genres used in Nielsen BookScan information.

fig. 1.4 Average sales for records with complete or incomplete BIC Basic data across different genres

based on a study of the top-selling 100,000

Fiction titles see the most dramatic improvement in average sales for records with complete BIC Basic data and an image. Records
with incomplete data have average sales of 1,326 but this grows by 173% for titles with complete BIC Basic data and an image,
which have average sales of 3,624. Specialist Non-Fiction titles show the smallest increase but even so see average sales rise by
33% for titles with complete data and an image. Trade Non-Fiction average sales per ISBN grow by 97% when all BIC Basic
elements are present, and Childrens titles see average sales rise by 52%.

ISBNs in the UK in 2011

Overall, we can see a clear relationship between the completeness of basic metadata and sales.

Nielsen - Metadata White Paper

Page 4

[For online sales, products]


with progressively increasing
amounts of enhanced
metadata see progressively
increasing average sales.
http://www.nielsenbookdata.co.uk/controller.php?page=1129

Research has proven that the


more information customers
have about a book, the more
likely they are to buy it.

ONIX provides a way to transmit


this information in a clean and
seamless way across multiple
trading partner relationships.

http://www.bisg.org/what-we-do-21-15-onix-for-books.php

Didnt we used to have


a sales team.

Metadata is all youve got


(in the growing part
of the market)

ONIX in detail

Versions of ONIX
ONIX 2.1

stable since 2004 (and compatible with 2.0)

growing number of implementations

Nielsen able to accept ONIX 3.0

most widely deployed at present

ONIX 3.0

reflects significant developments in e-book


market, internationalisation etc

reference name and short tag flavours

ONIX 2.1 vs ONIX 3.0


two quite different messages

block-level updates

10 years
accumulated
experience

digital products
sets and series
sales rights
marketing collateral
parallel multi-lingual data

global
best practice
guide

related works
international markets

ONIX 2.1 documentation


Specification

PDF, several separate documents

readable PDF, HTML, plus CSV, TSV, XML for


integration into applications, regularly updated

new HTML version, single document

codelists

schemas and tools

DTD, XSD
XSLT tools eg tag converter

ONIX 2.1 documentation


Specification

PDF, several separate documents

readable PDF, HTML, plus CSV, TSV, XML for


integration into applications, regularly updated

new HTML version, single document

codelists

schemas and tools

DTD, XSD
XSLT tools eg tag converter

ONIX 2.1 documentation


Specification

PDF, several separate documents

readable PDF, HTML, plus CSV, TSV, XML for


integration into applications, regularly updated

new HTML version, single document

codelists

schemas and tools

DTD, XSD
XSLT tools eg tag converter

ONIX 2.1 documentation


Specification

PDF, several separate documents

readable PDF, HTML, plus CSV, TSV, XML for


integration into applications, regularly updated

new HTML version, single document

codelists

schemas and tools

DTD, XSD
XSLT tools eg tag converter

ONIX 3.0 documentation


Specification

PDF, HTML

HTML only, regularly updated

set of codelist files shared with ONIX 2.1

XSD, RNG, DTD, and new Schematron

Implementation and Best Practice Guide


codelists

schemas and tools

XSLT tools, UML class diagrams

ONIX 3.0 documentation


Specification

PDF, HTML

HTML only, regularly updated

set of codelist files shared with ONIX 2.1

XSD, RNG, DTD, and new Schematron

Implementation and Best Practice Guide


codelists

schemas and tools

XSLT tools, UML class diagrams

Internationalisation
standards like ONIX need to cope with

multiple languages (German, French, Greek)

a generalised data model, supporting the use of


shared standard identifiers like ISBN and ISTC

multiple scripts (Latin, Arabic, Cyrillic, Kanji)


multiple cultures and business environments

ONIX is not just an XML message

controlled vocabularies
global implementation guidelines

ONIX is built using XML syntax


so well take a few minutes to learn XML

XML
structured data format
generally used for communication rather than
for storage

W3C standard neutral and non-proprietary


technology, supported by lots of software
tools

syntax based on <tag>data</tag>

so its just text you can open it in Windows


Notepad, Mac TextEdit, or a web browser

XML
structured data format
generally used for communication rather than
for storage

but you
W3C standard neutral and non-proprietary
create your

technology,
supported by lots ofown
software
looks like
tags
tools familiar
HTML

syntax based on <tag>data</tag>

and all
tags must
be closed

so its just text you can open it in Windows


Notepad, Mac TextEdit, or a web browser

<tag>data</tag>

tags can
be nested

<author>
<firstname>Mary</firstname>
<lastname>OConnor</lastname>
</author>
data
should be
granular

short
empty tag
syntax

<author/>

<retailer>Marks &amp; Spencer</retailer>


& and <
not
allowed

<!-- you can include comments -->

attributes
for data
format

<date format="yyyymmdd">20120116</date>
<date format="mmddyyyy">01162012</date>

<author>

</author>

Unicode

<author>!"#$%&# '()</author>
<author> </author>

XML
file must
start

<?xml version="1.0" encoding="UTF-8"?>


character
encoding
for data

<title>Stockholm AZ</title>

named
character
entity

<title>Stockholm A&ndash;Z</title>

<title>Stockholm A&#8211;Z</title>
<title>Stockholm A&#x2013;Z</title>
numerical
character
reference

<?xml version="1.0" encoding="UTF-8"?>


<ONIXmessage>
single
root

element
</ONIXmessage>

<?xml version="1.0" encoding="UTF-8"?>


<ONIXMessage>

</ONIXMessage>
XML is
case
sensitive

<?xml version="1.0" encoding="UTF-8"?>


<!DOCTYPE ONIXMessage SYSTEM
"http://www.editeur.org/onix/2.1/
reference/onix-international.dtd">
refers to
<ONIXMessage>
schema or

DTD
</ONIXMessage>

XML schemas
a schema or DTD defines what tags and
attributes can be used

their sequence and nesting


cardinality, eg optional and repeatable (0n)

schema (but not DTD) additionally defines


what data content each tag may contain

number, date, text etc


enumeration (controlled vocabulary or codelist)

XML validation
XML files can be well-formed or valid

well-formed if all the <tags> match </tags>

validating with a schema is better than


validating with a DTD, because it can check
certain rules about content, not just tagging

validation is process of checking XML data file


against a particular DTD or schema

you need some specific XML software for


validation

<text><![CDATA[ unparsed ]]></text>

the get-out clause


completely ignored by XML parsers

the unparsed data bypasses the content


restrictions of the DTD or schema
only sensible use of CDATA is to embed HTML
inside an ONIX data element
but its much better to use XHTML (which can
be checked with the normal ONIX schema)

Validation limitations
an ONIX file is not simply a file that

validates. The Specification includes other


rules and requirements

limitations on XSD or RNG validation

cannot define co-occurrence constraints


or verify check digits
or provide warnings about bad practice
these need to be controlled at application level

advanced validation with Schematron

XML is just syntax.


You also need semantics

Contracts

Works
ISTCs

Editions
ABR

2nd

Manifestations
ISBNs HB

EB

PB

CD

Impressions
1

(Reprints)

Relational vs denormalised data

database

database

ONIX is denormalised (flattened) because

every source database has a different entity


relationship structure

its optimised for communication, not data


management

<Product>
<RecordReference>com.globalbookinfo.onix.01734529</RecordReference>
<NotificationType>03</NotificationType>
<RecordSourceType>04</RecordSourceType>
<RecordSourceIdentifier>
<RecordSourceIDType>06</RecordSourceIDType>
<IDValue>0614141800001</IDValue>
</RecordSourceIdentifier>
<RecordSourceName>Global Bookinfo</RecordSourceName>
<ProductIdentifier>
<ProductIDType>03</ProductIDType>
<IDValue>9780007232833</IDValue>
</ProductIdentifier>
<ProductIdentifier>
<ProductIDType>15</ProductIDType>
<IDValue>9780007232833</IDValue>
</ProductIdentifier>
<DescriptiveDetail>
<ProductComposition>00</ProductComposition>
<ProductForm>BC</ProductForm>
<ProductFormDetail>B102</ProductFormDetail>
<Measure>
<MeasureType>01</MeasureType>
<Measurement>8.5</Measurement>
<MeasureUnitCode>in</MeasureUnitCode>
</Measure>

who supplied
this info?

the ISBN

its a paperback
height

ONIX high-level data structure


<ONIXMessage>
<Header>
<SenderName>

</Header>
<Product>

</Product>
<Product>

</Product>
</ONIXMessage>

<ONIXmessage>
<header>
<x298>

</header>
<product>

</product>
<product>

</product>
</ONIXmessage>

ONIX high-level data structure

NameIdentifierRelator
nameIdType : Token (List 44)
iDTypeName : String [0..1]

SimplePersonalName
-namesBeforeKey : String [0..1]
-keyNames : String
-namesAfterKey : String [0..1]

PersonalName
/ personName : String
/ personNameInverted : String

0..1

Name
nameType : Token [0..1] (List 18)

identifies
0..n

NameIdentifier
idValue : String

{xor}
{xor}

StructuredPersonalName
titlesBeforeNames : String [0..1]
namesBeforeKey : String [0..1]
prefixToKey : String [0..1]
keyNames : String
suffixToKey : String [0..1]
namesAfterKey : String [0..1]
lettersAfterNames : String [0..1]
titlesAfterNames : String [0..1]

Most NameIdentifiers are in fact


'persona' identifiers. One Name
can have many NameIdentifiers,
and a NameIdentifier can be
linked to several name variants

0..1
CorporateName
-namesBeforeKey : String [0..1]
-keyNames : String
-namesAfterKey : String [0..1]
/ corporateName : String
/ corporateNameInverted : String

0..n
ContributorPlaceRelator
contributorPlaceRelator : Token (List 151)

ProfessionalAffiliation
professionalPosition : String [0..1]

AlternativeName

0..n
Place

Contributor

countryCode : Token [0..1] (List 91)0..n


regionCode : Token [0..1] (List 49)

NamedContributor

biographicalNote : Xstring [0..n]


contributorDescription : Xstring [0..n]
{xor}

Date
date : Date

UnnamedContributor

NamedContributor is a
'persona', with (potentially)
multiple names (personalitites)

unnamedPersons: Token (List 19)

0..n

0..n
DateRelator
contributorDateRole : Token (List 177)

Contributor
sequenceNumber : Integer [0..1]
contributorRole : Token [1..n] (List 17)
fromLanguage : Token [0..1] (List 74)
tolanguage : Token [0..1] (List 74)

WebsiteRelator
websiteRole : Token [0..1] (List 73)

0..n

Website
websiteLink : URL
websiteDescription : Xstring [0..n]

DescriptiveDetail

author
is too
specific

<author>
<firstname>Mary Therese</firstname>
<lastname>OConnor</lastname>
</author>

<contributor>
<givenname>Maria</givenname>
<familyname>Garca del Ro Prez</familyname>
</contributor>
sorting vs.
display

prefixes
like van
de

<contributor>
<givenname>Xiaohua</givenname>
<familyname>Li</familyname>
<order>east</order>
</contributor>

<contributor>
<givenname>Guy</givenname>
<familyprefix>de</familyprefix>
<familyname>Maupassant</familyname>
<order>west</order>
</contributor>

functional

<Contributor>
granularity
<TitlesBeforeNames> eg Prof.
<NamesBeforeKey> eg Mary Therese
<PrefixToKey> eg de
<KeyNames> eg Balzac
<NamesAfterKey> eg Xiaohua
<SuffixToKey> eg Jr.
<LettersAfterNames> eg PhD.
<TitlesAfterNames> eg Prince of Wales careful
</Contributor>
analysis is
needed

simple
option as
well

<PersonName>Dr. Mary Therese OConnor,


MEP</PersonName>
<PersonNameInverted>OConnor, Dr. Mary
Therese, MEP</PersonNameInverted>

Contributor names in ONIX


sort these into alphabetical order, by author

Mary OConnor (but Mire Conchobhair)


Henriette dAngeville
Maria Garca del Ro Prez
Petfi Sndor
His Holiness the Dalai Lama

metadata
complexity
reflects the level
of real-world
complexity

*+,-# ./$/ !0123:


!01234-# 567-# 869#+:; <=>1?

Codelists in ONIX List 150


BA Book

Book detail unspecified

BB Hardback

Hardback or cased book

BC Paperback
BD Loose-leaf
BE Spiral bound
BF Pamphlet
BG Fine binding

Paperback or other softback


book
one row
= one
Loose-leaf book
concept
Spiral, comb or coil bound
book
Pamphlet or brochure, stapled;
German geheftet
Leather bound or other fine
binding

Codelists in ONIX List 150


BA Book

Book detail unspecified

BB Hardback

Hardback or cased book

BC Paperback

Paperback or other softback


book

BD Loose-leaf

Loose-leaf book

BE Spiral bound
codes
BF Pamphlet
appear in
data
BG Fine the
binding

Spiral, comb or coil bound


book
Pamphlet or brochure, stapled;
German geheftet
Leather bound or other fine
binding

Codelists in ONIX List 150


BA Book

Book detail unspecified

BB Hardback

Hardback or cased book

BC Paperback

Paperback or other softback


book

BD Loose-leaf

Loose-leaf book

BE Spiral bound
BF Pamphlet
BG Fine binding

Spiral, comb or coil bound


book
labels in
Pamphlet
or brochure, stapled;
any
German
geheftet
language
Leather bound or other fine
binding

Codelists in ONIX List


150
language
BA Book

independence
Book detail unspecified

BB Hardback

Hardback or cased book

BC Paperback

Paperback or other softback


book

BD Loose-leaf

Loose-leaf book

BE Spiral bound
BF Pamphlet
BG Fine binding

Spiral, comb or coil bound


book
Pamphlet or brochure, stapled;
German geheftet
Leather bound or other fine
binding

Codelists in ONIX
256 pages

Codelist 23 code 11
means content page count

<Extent>
<ExtentType>11</ExtentType>
<ExtentValue>256</ExtentValue>
<ExtentUnit>03</ExtentUnit>
</Extent>
Codelist 24 code 03
means pages

Codelists in ONIX
256 minutes

Codelist 23 code 09
means duration

<Extent>
<ExtentType>09</ExtentType>
<ExtentValue>256</ExtentValue>
<ExtentUnit>05</ExtentUnit>
</Extent>
Codelist 24 code 05
means minutes

Codelists in ONIX
256 minutes

Codelist 23 code 09
clarity
means duration

and
<Extent>
precision
<ExtentType>09</ExtentType>
<ExtentValue>256</ExtentValue>
<ExtentUnit>05</ExtentUnit>
</Extent>
Codelist 24 code 05
means minutes

Codelists in ONIX
256 minutes

Codelist 23 code 09
means duration

<Extent>
<ExtentType>09</ExtentType>
<ExtentValue>256</ExtentValue>
<ExtentUnit>05</ExtentUnit>
</Extent>
semantic
Codelist 24 code
05
intermeans minutes

operability

Codelists in ONIX
256 minutes
<extent>
<b218>09</b218>
<b219>256</b219>
<b220>05</b220>
</extent>

short tag
equivalent

ONIX 3.0 data elements

message details
identity and authority

record details
product identifiers

1. descriptive details

product form
special features
packaging
physical size
usage constraints

trade classification
product parts
collection titles
titles
contributors
conference
edition
language
extent
subject
audience

ONIX 3.0 data elements

2. collateral details

cited material
supporting resources
prizes

3. content detail
4. publishing details

supporting text

imprint and publisher


lifecycle dates
territorial rights

5. related material

related works
related products

6. supply details

markets
market publishing details
suppliers
discounts
prices and tax
reissue details

ONIX data elements


data elements come from all parts of the
organisation editorial, production,
marketing, sales, even design

not all data is available on day one


need to integrate data from all departments

dont just collect it all manually at the end


make the data functional part of the process
greater exposure ensures greater accuracy

metadata develops as the book develops

ONIX data elements


editorial
design
production
marketing
sales

database

ONIX data elements


aim is to provide a kit of parts for your
supply chain partners

every data element they require


as fine-grained as they need
confidence in the datas meaning
timely and correct

for cataloguing, trading in, merchandising,


promoting, selling

internally and in customer-facing applications

After syntax and semantics,


you need an operating model
this is where the ONIX 3.0 Implementation
and Best Practice Guide comes in

ONIX data feeds

database

database

need to agree arrangements with recipient

ONIX data feeds


full feed or delta updates

provide full record for every product, every time


or provide full record, but only for products
that have changed since last time

block updates ONIX 3.0 only

like delta updates, but

always provide identity and authority, plus any


of Blocks 16 that have changed

provide only the parts of records that have


changed since last time

ONIX data feeds


scope of feed

all products? all active products? all products


the data recipient may order?
pre-pub only, or include post-pub P&A?
how often?
method of file collection or delivery?

often but not always possible to create a

http://www.editeur.org/93/Release-3.0-Downloads/#Best practice

single data feed for all partners

ONIX data feeds

timing

ONIX data feeds

initial supply around 6 months prior to pub


all details complete and correct at least four
months prior to pub
updated throughout life-cycle

(but P&A updates often not done via ONIX)

service level agreement

BIC / BISG best practices for data senders and


for data recipients

http://www.bisg.org/docs/RecipientBestPracticesV1.0FINAL.pdf

certification schemes

timing

ONIX data feeds

initial supply around 6 months prior to pub


all details complete and correct at least four
months prior to pub
updated throughout life-cycle

(but P&A updates often not done via ONIX)

service level agreement

BIC / BISG best practices for data senders and


for data recipients

certification schemes

http://www.bic.org.uk/files/pdfs/110721recipients%20best%20practice%20final.pdf

timing

ONIX data feeds

initial supply around 6 months prior to pub


all details complete and correct at least four
months prior to pub
updated throughout life-cycle

(but P&A updates often not done via ONIX)

service level agreement

BIC / BISG best practices for data senders and


for data recipients

certification schemes

Service level expectations

clear information on data flow within the


recipient organisation
provide receipt acknowledgements
comply with territorial sales rights, public
announcement dates, sales embargo dates,
remove deleted records, hide withdrawn or
postponed indefinitely products
recipients should process P&A updates within
two working days wherever possible, and
provide a mechanism for emergency updates

ONIX data feeds


ONIX 2.1, plus ongoing P&A updates via

ONIX Supply Update message or

ONIX 3.0 block 6 update or

EDItX

(EDItEUR XML format)

EDIFACT

(European EDI format)

Tradacoms (UK EDI format)


X.12

ONIX 3.0

(US EDI format)

EDItX, EDIFACT, Tradacoms, X.12

ONIX data feeds

database

database

for digital products, sales reports need to


flow back from retailer to publisher

EDItX Sales Report format

Record reference

<RecordReference>uk.co.harpercollins.036036
</RecordReference>
<NotificationType>03</NotificationType>
<RecordSourceType>01</RecordSourceType>
<RecordSourceName>HarperCollins
Publishers Ltd.</RecordSourceName>

Product identifier

<ProductIdentifier>
<ProductIDType>03</ProductIDType>
<IDValue>9780007232833</IDValue>
</ProductIdentifier>
<ProductIdentifier>
<ProductIDType>15</ProductIDType>
<IDValue>9780007232833</IDValue>
</ProductIdentifier>
<ProductIdentifier>
<ProductIDType>02</ProductIDType>
<IDValue>0007232837</IDValue>
</ProductIdentifier>

Contributor

2.1

<Contributor>
<SequenceNumber>1</SequenceNumber>
<ContributorRole>A01</ContributorRole>
<PersonNameInverted>Sj&ouml;wall, Maj
</PersonNameInverted>
<PersonNameIdentifier>
<PersonNameIDType>01</PersonNameIDType>
<IDTypeName>HCP Author ID</IDTypeName>
<IDValue>7421</IDValue>
</PersonNameIdentifier>
<BiographicalNote textformat="05"><p>Maj
Sj&ouml;wall is a poet. She lives in Sweden.</p>
</BiographicalNote>
</Contributor>

3.0

<Contributor>
<SequenceNumber>1</SequenceNumber>
<ContributorRole>A01</ContributorRole>
<NameIdentifier>
<NameIDType>01</NameIDType>
<IDTypeName>HCP Author ID</IDTypeName>
<IDValue>7421</IDValue>
</NameIdentifier>
<PersonNameInverted>Sjwall, Maj
</PersonNameInverted>
<BiographicalNote textformat="05"><p>Maj
Sjwall is a poet. She lives in Sweden.</p>
</BiographicalNote>
</Contributor>

<Contributor>
<SequenceNumber>1</SequenceNumber>
<ContributorRole>A01</ContributorRole>
<NameIdentifier>
<NameIDType>16</NameIDType>
<IDValue>0000000121479135</IDValue>
</NameIdentifier>
<PersonNameInverted>Sjwall, Maj
</PersonNameInverted>
<BiographicalNote textformat="05"><p>Maj
Sjwall is a poet. She lives in Sweden.</p>
</BiographicalNote>
</Contributor>

3.0

http://isni.org/search

<BiographicalNote>Umberto Eco, professor of


semiotics at the University of Bologna, and
author of The Name Of The Rose and
Foucaults Pendulum, is one of the worlds
bestselling novelists.
As well as novels, he also writes childrens
books and academic works.</BiographicalNote>

<BiographicalNote><![CDATA[Umberto Eco,
professor of semiotics at the University of
Bologna, and author of The Name Of The
Rose and Foucaults Pendulum, is one of the
worlds bestselling novelists.
As well as novels, he also writes childrens
books and academic works.]]>
</BiographicalNote>

<BiographicalNote textformat="05"><p>Umberto
Eco, professor of semiotics at the University of
Bologna, and author of <em>The Name Of The
Rose</em> and <em>Foucaults Pendulum
</em>, is one of the worlds bestselling
novelists.</p><p>As well as novels, he also
writes childrens books and academic works.
</p></BiographicalNote>

<BiographicalNote language="ita"
textformat="05"><p>Umberto Eco, professore di
semiotica allUniversit di Bologna e autore di
<em>Il nome della rosa</em> e <em>Il pendolo
di Foucault</em>, uno dei romanzieri pi
venduto al mondo.</p></BiographicalNote>
<BiographicalNote language= "eng"
textformat="05"><p>Umberto Eco, professor of
semiotics at the University of Bologna, and
author of <em>The Name Of The Rose</em>
and <em>Foucaults Pendulum</em>, is one of
the worlds bestselling novelists.</p>
</BiographicalNote>

Titles

3.0.1

Titles
covers titles, subtitles

and in 3.0, also covers some set or series titles

original title of translation

useful alternative titles

former title (eg with film tie-ins)


distributors title (often abbreviated to fit fixedlength field in legacy IT system)

2.1

<NoSeries/>
<Title>
<TitleType>01</TitleType>
<TitleText textcase="01">The man on the
balcony</TitleText>
<TitlePrefix textcase="01">The</TitlePrefix>
<TitleWithoutPrefix textcase="01">man on
the balcony</TitleWithoutPrefix>
</Title>

3.0

<NoCollection/>
<TitleDetail>
<TitleType>01</TitleType>
<TitleElement>
<TitleElementLevel>01</TitleElementLevel>
<TitlePrefix>The</TitlePrefix>
<TitleWithoutPrefix textcase="02">Man on
the Balcony</TitleWithoutPrefix>
</TitleElement>
</TitleDetail>

3.0

<NoCollection/>
<TitleDetail>
<TitleType>01</TitleType>
<TitleElement>
<TitleElementLevel>01</TitleElementLevel>
<TitleText textcase="01">Mannen p
balcongen</TitleText>
</TitleElement>
</TitleDetail>

<TitleDetail>
<TitleType>01</TitleType>
<TitleElement>
<TitleElementLevel>02</TitleElementLevel>
<TitleText textcase="01">Martin Beck
</TitleText>
</TitleElement>
<TitleElement>
<TitleElementLevel>01</TitleElementLevel>
<TitleText textcase="01">Mannen p
balcongen</TitleText>
</TitleElement>
</TitleDetail>

3.0

Sets, series, collections

Sets and series

<Set> or <Series> in ONIX 2.1


<Collection> in ONIX 3.0

publisher collections
ascribed collections

2.1

<Series>
<Title>
<TitleType>01</TitleType>
<TitleText textcase="02">Martin Beck</TitleText>
</Title>
<NumberWithinSeries>3</NumberWithinSeries>
</Series>

3.0

<Collection>
<CollectionType>10</CollectionType>
<TitleDetail>
<TitleType>01</TitleType>
<TitleElement>
<TitleElementLevel>02</TitleElementLevel>
<TitleText textcase="01">Martin Beck</TitleText>
</TitleElement>
<TitleElement>
<TitleElementLevel>01</TitleElementLevel>
<PartNumber>3</PartNumber>
</TitleElement>
</TitleDetail>
</Collection>

3.0.1

<CollectionSequence>
<CollectionSequenceType>02
</CollectionSequenceType>
<CollectionSequenceNumber>3.2
</CollectionSequenceNumber>
</CollectionSequence>

Publication order

Narrative order

The Lion, the Witch


and the Wardrobe

The Magicians Nephew

Prince Caspian

The Lion, the Witch


and the Wardrobe

The Voyage of the


Dawn Treader

The Horse and His Boy

The Silver Chair

Prince Caspian

The Horse and His Boy

The Voyage of the


Dawn Treader

The Magicians Nephew

The Silver Chair

The Last Battle

The Last Battle

two ways to provide collection details in


ONIX 3.0

as just another title element within


<TitleDetail>, or
as a title element in <TitleDetail> within
<Collection>

not always a simple choice


depends on whether collection title is an

integral part of the identity of the product, or


whether the product has an identity separate
from the collection

Multi-item products

Contained items
<ContainedItem> in ONIX 2.1
<ProductPart> in ONIX 3.0

book and CD, book and toy


multiple books in a pack
trade multipacks

Subject

Subject
BISAC subject classification
BIC subject classification
library-specific schemes LCSH, Dewey,
UDC but rarely provided by publishers

keywords
CBMC codes

2.1

<MainSubject>
<MainSubjectSchemeIdentifier>10
</MainSubjectSchemeIdentifier>
<SubjectSchemeVersion>2010
</SubjectSchemeVersion>
<SubjectCode>FIC022020</SubjectCode>
<SubjectHeadingText>FICTION /
Mystery & Detective / Police Procedural
</SubjectHeadingText>
</MainSubject>

3.0

<Subject>
<MainSubject/>
<SubjectSchemeIdentifier>10
</SubjectSchemeIdentifier>
<SubjectSchemeVersion>2012
</SubjectSchemeVersion>
<SubjectCode>FIC022020</SubjectCode>
<SubjectHeadingText>FICTION /
Mystery & Detective / Police Procedural
</SubjectHeadingText>
</Subject>

not available due to licensing issues

http://editeur.dyndns.org

<Subject>
<SubjectSchemeIdentifier>20
</SubjectSchemeIdentifier>
<SubjectHeadingText>Martin Beck;
police procedural; Lake Vttern;
Wallander</SubjectHeadingText>
</Subject>

Descriptive text

Descriptive text
short description
long description
review snippets
combined contributor biography
table of contents

probably the most underused collateral type

2.1

<OtherText>
<TextTypeCode>08</TextTypeCode>
<Text>&lsquo;Their mysteries don&rsquo;t
just read well; they reread even better.
Witness, wife, petty cop or crook &ndash;
they&rsquo;re all real characters even if
they get just afew sentences. The plots
hold, because they&rsquo;re ingenious
but never inhuman.&rsquo;
New York Times</Text>
</OtherText>

2.1

<OtherText>
<TextTypeCode>08</TextTypeCode>
<Text textformat="05"><p>&lsquo;Their
mysteries don&rsquo;t just read well;
they reread even better. Witness, wife,
petty cop or crook &ndash; they&rsquo;re
all real characters even if they get just a
few sentences. The plots hold, because
they&rsquo;re ingenious but never
inhuman.&rsquo;<br />New York Times
</p></Text>
</OtherText>

3.0

<TextContent>
<TextType>06</TextType>
<ContentAudience>00</ContentAudience>
<Text textformat="05"><p>Their mysteries
dont just read well; they reread even
better. Witness, wife, petty cop or crook
theyre all real characters even if they
get just a few sentences. The plots hold,
because theyre ingenious but never
inhuman.</p></Text>
<SourceTitle>New York Times</SourceTitle>
</TextContent>

<TextContent>
<TextType>06</TextType>
<ContentAudience>00</ContentAudience>
<Text textformat="02"><![CDATA[<p>Their
mysteries dont just read well; they
reread evenbetter. Witness, wife, petty
cop or crook &hellip;theyre all real
characters even if theyget just a few
sentences. The plots hold,because
theyre ingenious but neverinhuman.]]>
</Text>
<SourceTitle>New York Times</SourceTitle>
</TextContent>

3.0

Gyldendal Norsk Forlag

Collateral material

http://www.guardian.co.uk/
books/2009/nov/22/crimethriller-maj-sjowall-sweden

Collateral material
cover images
author portrait images

might require a photo credit

need to agree on naming, or provide


unambiguous name in ONIX

sample spreads
deliver via URL in ONIX, or deliver separately
ONIX 3 goes further

cited material

Imprint and publisher

Imprint and publisher


imprint is a brand name
publisher is an organisation name

even though they often appear the same

Amazon demands an imprint identifier as

well (without actually saying what kind of ID


that would be)

<Imprint>
<ImprintName>Harper Perennial</ImprintName>
</Imprint>
2.1
<Imprint>
<NameCodeType>02</NameCodeType>
<NameCodeTypeName>HCP List ID
</NameCodeTypeName>
<NameCodeValue>HCUKPERF</NameCodeValue>
<ImprintName>Harper Perennial</ImprintName>
</Imprint>

<Imprint>
<ImprintName>Harper Perennial</ImprintName>
</Imprint>
3.0
<Imprint>
<ImprintIdentifier>
<ImprintIDType>01</ImprintIDType>
<IDTypeName>HCP List ID</IDTypeName>
<IDValue>HCUKPERF</IDValue>
</ImprintIdentifier>
<ImprintName>Harper Perennial</ImprintName>
</Imprint>

Territorial rights

Territorial rights
these are sales rights

publishing rights where a publisher can


exploit a work or sell a product
sales rights where a publisher chooses to sell a
product

critical to distributors, wholesalers and


retailers

dont just supply positive details include


countries where the product is not for sale
and provide an alternative if possible

pub rights database at work level


contracts

editorial
ONIX recipient
sales order processing / distribution
cust serv

2.1

<SalesRights>
<SalesRightsType>01</SalesRightsType>
<RightsCountry>AG AI AU BB BD BM BN BS BW
BZ CM CY DM EG FJ FK GB GD GH GI GM
GY HK IE IL IN IO JM JO KE KI KN KW KY
LC LK LS MT MU MV MW MY MZ NA NG
NR NZ PG PK PN SB SC SD SG SH SL SO SZ
TC TO TT TV TZ UG VC VG VU WS YE RS ME
ZA ZM ZW</RightsCountry>
</SalesRights>

2.1

<SalesRights>
<SalesRightsType>03</SalesRightsType>
<RightsCountry>AS CA GU MP PH PR
US VI</RightsCountry>
</SalesRights>

3.0

<SalesRights>
<SalesRightsType>01</SalesRightsType>
<Territory>
<CountriesIncluded>US</CountriesIncluded>
<RegionsExcluded>US-HI US-AL
</RegionsExcluded>
</Territory>
</SalesRights>
<ROWSalesRightsType>03</ROWSalesRightsType>

Related works and products

2.1

<WorkIdentifier>
<WorkIDType>11</WorkIDType>
<IDValue>A0220090000154FA</IDValue>
</WorkIdentifier>

Contracts

Works
ISTCs

Editions
ABR

2nd

Manifestations
ISBNs HB

EB

PB

CD

Impressions
1

(Reprints)

swedish

english

abridged

ISTC

work

work

work

ISBN

product

product

product

hardback

e-book

paperback

3.0

<RelatedWork>
<WorkRelationCode>01</WorkRelationCode>
<WorkIdentifier>
<WorkIDType>11</WorkIDType>
<IDValue>A0220090000154FA</IDValue>
</WorkIdentifier>
</RelatedWork>

3.0
many
<RelatedProduct>
different
<ProductRelationCode>06</ProductRelationCode>
product
<ProductRelationCode>27</ProductRelationCode>
relators
<ProductIdentifier>
<ProductIDType>03</ProductIDType>
<IDValue>9780007324378</IDValue>
</ProductIdentifier>
<ProductIdentifier>
<ProductIDType>15</ProductIDType>
<IDValue>9780007324378</IDValue>
</ProductIdentifier>
</RelatedProduct>

product

first

second

third

work

work

work

product

product

product

product

product

product

product

product replaces
related product

Availability

Availability
distinguish between decisions made by the
publisher (cancelled, forthcoming, active,
out of print)

<PublishingStatus>

and statuses reported by a supplier


(expected, in stock, out of stock)

<ProductAvailability>
some supplier statuses simply repeat what the
publisher says, others reflect local stock status

<PublishingStatus>

product

Suppliers Product availability

code

Cancelled

01

Not yet available

02

Available

20

Temporarily unavailable

30

No longer supplied by us

43

Not available, publisher indicates OP

51

Supply details

Supply details
carries details of your distributor

territories they supply to

should be a subset of your <SalesRights> !

prices they charge


tax included in those prices (at least in some
countries)

ONIX 2.1 has a dedicated P&A update format


standard block update in ONIX 3.0

<Price>
<PriceTypeCode>02</PriceTypeCode>
<DiscountCoded>
<DiscountCodeType>01</DiscountCodeType>
<DiscountCode>AHACP029</DiscountCode>
</DiscountCoded>
<PriceAmount>7.99</PriceAmount>
<CurrencyCode>GBP</CurrencyCode>
<CountryCode>GB</CountryCode>
<TaxRateCode1>Z</TaxRateCode1>
<TaxRatePercent1>0</TaxRatePercent1>
<TaxableAmount1>7.99</TaxableAmount1>
<TaxAmount1>0.00</TaxAmount1>
</Price>

2.1

2.1

<Price>
<PriceTypeCode>01</PriceTypeCode>
<DiscountCoded>
<DiscountCodeType>01</DiscountCodeType>
<DiscountCodeTypeName>FolklorePub
</DiscountCodeTypeName>
<DiscountCode>029</DiscountCode>
</DiscountCoded>
<PriceAmount>9.95</PriceAmount>
<CurrencyCode>USD</CurrencyCode>
<CountryCode>US</CountryCode>
<CountryCode>PR</CountryCode>
</Price>

2.1

<Price>
<PriceTypeCode>07</PriceTypeCode>
<PriceAmount>49.00</PriceAmount>
<CurrencyCode>SEK</CurrencyCode>
<CountryCode>SE</CountryCode>
<TaxRateCode1>R</TaxRateCode1>
<TaxRatePercent1>6</TaxRatePercent1>
<TaxableAmount1>46.25</TaxableAmount1>
<TaxAmount1>2.75</TaxAmount1>
</Price>

<Price>
<PriceType>01</PriceType>
<DiscountCoded> </DiscountCoded>
<PriceAmount>7.99</PriceAmount>
<CurrencyCode>EUR</CurrencyCode>
<Territory>
<CountriesIncluded>AT BE CY FI FR DE ES
GR IE IT LU MT NL PT SI SK AD MC ME
SM VA</CountriesIncluded>
</Territory>
<PriceDate>
<PriceDateRole>15</PriceDateRole>
<Date>20130225</Date>
</PriceDate>
</Price>

3.0

E-books

E-books
what do people ask about?

e-book formats, digital originals, enhanced


editions, DRM, apps, international pricing
role of intermediaries
direct supply of data to retailers
what about data aggregators?
sales reports
how can I supply the data I need in ONIX 2.1?

oh, and how many ISBNs do I need?

How%20
to...
nloads/
#
http://w

ww.edite

ur.org/9
3/

Release
-3

.0-Dow

http://www.bisg.org/docs/EBooksONIX_FAQ.pdf

E-book identifiers
lack of accepted standard practice, most
particularly among publishers in USA

growing problems for intermediaries, resellers

http://www.isbn-international.org/faqs/view/17

http://www.bisg.org/docs/BISG_Policy_1101.pdf

IIA and BISG commissioned studies in 2010


IIA FAQ published late 2010
BISG policy published late 2011

E-book identifiers
lack of accepted standard practice, most
particularly among publishers in USA

growing problems for intermediaries, resellers

IIA FAQ published late 2010

IIA and BISG commissioned studies in 2010

http://www.isbn-international.org/faqs/view/17

http://www.bisg.org/docs/BISG_Policy_1101.pdf

BISG policy published late 2011

E-book identifiers
lack of accepted standard practice, most
particularly among publishers in USA

growing problems for intermediaries, resellers

http://www.isbn-international.org/faqs/view/17

http://www.bisg.org/docs/BISG_Policy_1101.pdf

IIA and BISG commissioned studies in 2010


IIA FAQ published late 2010
BISG policy published late 2011

E-book identifiers
ISBN is the primary supply chain identifier
for e-books just as it is for physical

there is no magic identifier called an e-ISBN


change of file format means new ISBN
change of content means new ISBN
major change in usage rights means its a
new product, and needs a new ISBN

this is difficult, primarily because of


limitations in legacy IT systems

E-book identifiers

if an intermediary changes the file format of


an e-book (eg EPUB to Kindle), the modified
version may need a new ISBN or at the
very least the old ISBN should be removed

if publisher does not assign the new ISBN,


thenthe intermediary can do so (and should
inform the publisher and other supply chain
partners)
theres no good process when two
intermediaries convert into the same format
if the converted version is then sold direct to
consumers, it may not need a new ISBN at all

E-book identifiers
there remains some disagreement about

whether different DRMs on the same file


format (eg EPUB+Apple DRM and EPUB
+Adobe DRM) should have separate ISBNs

for the reader, differences of DRM are as


important as differences of file format
needs different hardware or software to read
DRMs are linked to different accounts at
different retailers

Describing e-books in ONIX

product identifiers
product form
product form detail
product form feature
usage restrictions
extent
edition

pub dates

ONIX 2.1
and 3.0 differ
significantly

territorial rights
sales restrictions
related products
supplier
agency/tiered pricing
accessibility

<ProductIdentifier>
<ProductIDType>03</ProductIDType>
<IDValue>9780007232833</IDValue>
</ProductIdentifier>
<ProductIdentifier>
<ProductIDType>15</ProductIDType>
<IDValue>9780007232833</IDValue>
</ProductIdentifier>
<ProductIdentifier>
<ProductIDType>01</ProductIDType>
<IDTypeName>XYZ SKU</IDTypeName>
<IDValue>BP036036</IDValue>
</ProductIdentifier>

Product form and detail


ONIX 2.1 has just electronic book text,

ONIX3.0 has downloadable or online


anda separate licence product type

ONIX 3.0 deals with file format via

<ProductFormDetail>, whereas ONIX 2.1


uses <EpubType>

both can include EPUB, PDF, Kindle, apps

specific hardware and software requirements


(eg needs EPUB 3 capable reader, needs
iOS 5.1) in <ProductFormFeature>

<ProductForm>DG</ProductForm>
<ProductFormDetail>E201</ProductFormDetail>
<ProductFormDetail>E202</ProductFormDetail>
<ProductContentType>10</ProductContentType>
<ProductContentType>06</ProductContentType>
<ProductContentType>13</ProductContentType>
<ProductFormFeature>
<ProductFormFeatureType>06
</ProductFormFeatureType>
<ProductFormFeatureValue>03
</ProductFormFeatureValue>
<ProductFormFeatureDescription>iOS 5.1
</ProductFormFeatureDescription>
</ProductFormFeature>
<EpubType>029</EpubType>
<ProductComposition>00</ProductComposition>
<ProductForm>ED</ProductForm>
<ProductFormDetail>E101</ProductFormDetail>
<ProductFormDetail>E201</ProductFormDetail>
<ProductFormDetail>E202</ProductFormDetail>
<ProductFormFeature>
<ProductFormFeatureType>06
</ProductFormFeatureType>
<ProductFormFeatureValue>03
</ProductFormFeatureValue>
<ProductFormFeatureDescription>iOS 5.1
</ProductFormFeatureDescription>
</ProductFormFeature>
<PrimaryContentType>10</PrimaryContentType>
<ProductContentType>06</ProductContentType>
<ProductContentType>13</ProductContentType>

2.1

3.0

Usage restrictions
ONIX 3.0 only <EpubTechnicalProtection>
and <EpubUsageConstraint>

limits on print, cut and paste, concurrent use,


TTS, lending
can specify which DRM framework is used
(watermarking or some technical enforcement)

important for retailers to make constraints


clear to purchasers

and so publishers need to be clear to retailers

<EpubTechnicalProtection>03
</EpubTechnicalProtection>
<EpubUsageConstraint>
<EpubUsageType>05</EpubUsageType>
<EpubUsageStatus>01</EpubUsageStatus>
</EpubUsageConstraint>
<EpubUsageConstraint>
<EpubUsageType>03</EpubUsageType>
<EpubUsageStatus>02</EpubUsageStatus>
<EpubUsageLimit>
<Quantity>10</Quantity>
<EpubUsageUnit>05</EpubUsageUnit>
</EpubUsageLimit>
</EpubUsageConstraint>

Extents
can provide multiple extents, via <Extent>

content page count, absolute page count


notional page count
page count of print counterpart
word count, file size can also be specified

content types text, images, audio, video,

maps, animation for enhanced e-books in


<PrimaryContent> and <ProductContent>

<Extent>
<ExtentType>22</ExtentType>
<ExtentValue>1.4</ExtentValue>
<ExtentUnit>19</ExtentUnit>
</Extent>
<Extent>
<ExtentType>02</ExtentType>
<ExtentValue>142000</ExtentValue>
<ExtentUnit>02</ExtentUnit>
</Extent>
<Extent>
<ExtentType>08</ExtentType>
<ExtentValue>320</ExtentValue>
<ExtentUnit>03</ExtentUnit>
</Extent>

3.0

Edition types
<EditionType> copes with

digital originals
<EditionType>DGO</EditionType>
enhanced editions
<EditionType>ENH</EditionType>

Publication dates
ONIX 3.0 can provide multiple dates using
<PublishingDate>

date of first publication (of original work)

nominal date of publication of e-book

date of publication of print counterpart


(source physical book)
embargo date

ONIX 2.1 is limited to delivering pub date of


the e-book, date of first publication of the
work, and the sales embargo date

3.0

<PublishingDate>
<PublishingDateRole>11</PublishingDateRole>
<Date dateformat="05">1811</Date>
</PublishingDate>
<PublishingDate>
<PublishingDateRole>19</PublishingDateRole>
<Date dateformat="01">198510</Date>
</PublishingDate>
<PublishingDate>
<PublishingDateRole>02</PublishingDateRole>
<Date dateformat="00">20110428</Date>
</PublishingDate>

2.1

<PublicationDate>20110428</PublicationDate>
<YearFirstPublished>1811</YearFirstPublished>

Territorial rights
same as printed books
but perceived as being complex because of
the reality of global selling suddenly it
matters!

and the fact that many e-book products are


retailer-exclusives

<SalesRights> and <SalesRestriction>

a real premium value on delivery of accurate


and comprehensive sales rights

3.0

<SalesRights>
<SalesRightsType>07</SalesRightsType>
<Territory>
<RegionsIncluded>WORLD</RegionsIncluded>
</Territory>
</SalesRights>
<SalesRestriction>
<SalesRestrictionType>05</SalesRestrictionType>
<SalesOutlet>
<SalesOutletName>Fnac</SalesOutletName>
</SalesOutlet>
</SalesRestriction>

2.1

<SalesRights>
<SalesRightsType>01</SalesRightsType>
<RightsCountry>GB AT BE BG CY CZ DE DK EE
ES FI FR GR HU IE IT LT LU LV MT NL PL PT
RO SE SI SK CH IS LI NO</RightsCountry>
</SalesRights>
<SalesRestriction>
<SalesRestrictionType>04</SalesRestrictionType>
<SalesOutlet>
<SalesOutletName>Tesco</SalesOutletName>
</SalesOutlet>
</SalesRestriction>

Related works and products


value of work identifiers (either proprietary
or standard, like ISTC) is growing due to
larger number of manifestations per work

again, same as for physical product


some retailers demand source ISBN as a
first among equals related product

2.1

<WorkIdentifier>
<WorkIDType>11</WorkIDType>
<IDValue>A0220090000154FA</IDValue>
</WorkIdentifier>
<WorkIdentifier>
<WorkIDType>01</WorkIDType>
<IDTypeName>KPbiblioWID</IDTypeName>
<IDValue>2283</IDValue>
</WorkIdentifier>

3.0

<RelatedWork>
<WorkRelationCode>01</WorkRelationCode>
<WorkIdentifier>
<WorkIDType>11</WorkIDType>
<IDValue>A0220090000154FA</IDValue>
</WorkIdentifier>
<WorkIdentifier>
<WorkIDType>01</WorkIDType>
<IDTypeName>KPbiblioWID</IDTypeName>
<IDValue>2283</IDValue>
</WorkIdentifier>
</RelatedWork>

3.0

<RelatedProduct>
<ProductRelationCode>13</ProductRelationCode>
<ProductRelationCode>06</ProductRelationCode>
<ProductIdentifier>
<ProductIDType>03</ProductIDType>
<IDValue>9780007120765</IDValue>
</ProductIdentifier>
<ProductIdentifier>
<ProductIDType>15</ProductIDType>
<IDValue>9780007120765</IDValue>
</ProductIdentifier>
<ProductForm>BC</ProductForm>
</RelatedProduct>

Supplier
<Supplier> in ONIX is usually a physical

book distributor or wholesaler from whom a


retailer can order copies

for e-books, the supplier may be a digital


intermediary or a retailer

<SupplierRole> specifies the suppliers role in


the supply chain

n to es
sio ted su
us i is
sc lim al
di be nic
t ch
us te
m ely
r
pu

E-book prices

ONIX caters for multiple business


models via <PriceType>

retail price less discount


wholesale price
agency price with commission

prices in multiple currencies


tiered/coded prices using <PriceCoded>
price of print counterpart using
<ComparisonProductPrice>

<Price>
<PriceType>41</PriceType>
<DiscountCoded>
<DiscountCodeType>05</DiscountCodeType>
<DiscountCodeTypeName>XYZ Agency Rate
List</DiscountCodeTypeName>
<DiscountCode>B</DiscountCode>
</DiscountCoded>
<PriceAmount>49.95</PriceAmount>
<CurrencyCode>SEK</CurrencyCode>
</Price>

3.0

<PriceCoded>
<PriceCodeType>01</PriceCodeType>
<PriceCodeTypeName>EbookVendor.com Tier
</PriceCodeTypeName>
<PriceCode>7a</PriceCode>
</PriceCoded>

E-book accessibility

E-book accessibility
accessibility goes beyond the features of the
e-book reading system accessible content

ensuring your products are suitable for

print-impaired readers can mean a 1015%


growth in the total addressable market
more as population ages

EDItEUR works with WIPO, IDPF, DAISY


Consortium and global advocacy groups

E-book accessibility
ONIX has always been able to describe
Braille, large print, DAISY products

EPUB 3 is the new delivery system for DAISY


EPUB 3 can be accessible but its not
automatically suitable for print-impaired
readers just because its an EPUB 3

must let prospective readers know how

accessible your publication is via metadata

E-book accessibility
high-level EDItEUR / WIPO advice

http://www.editeur.org/109/EnablingTechnologies-Framework/

detailed, practical advice in OReilly booklet

http://shop.oreilly.com/product/
0636920025283.do (available free of charge)

publishers should incorporate testing for

accessibility into their QA procedures, and


feed the results into their metadata records

ONIX codelist 196 to describe accessibility

Accessibility features

you can use all the


accessibility features
of the reading device
navigation via TOC
navigation via Index
logical reading order

alt text

full alternative
descriptive text

visualised data also


available as text
accessible maths
accessible chemistry
print-equivalent page
numbering
synchronised prerecorded audio
compatibility notes

<ProductFormFeature>
<ProductFormFeatureType>09</ProductFormFeatureType>
<ProductFormFeatureValue>10</ProductFormFeatureValue>
</ProductFormFeature>
<ProductFormFeature>
<ProductFormFeatureType>09</ProductFormFeatureType>
<ProductFormFeatureValue>13</ProductFormFeatureValue>
</ProductFormFeature>
<ProductFormFeature>
<ProductFormFeatureType>09</ProductFormFeatureType>
<ProductFormFeatureValue>15</ProductFormFeatureValue>
</ProductFormFeature>

Codelist 196
codelist is granular, and carefully specified
each print-impaired reader can characterise
their requirements in terms of the various
features in List 196

each publisher and retailer can characterise

the features provided by a particular product


in terms of the features in List 196

buyer can match the two profiles

Summary

Minimum set of ONIX tags


no-one needs to supply every element
the ONIX DTD and schemas make very few
data elements mandatory

technical minimum is completely useless

true minimum set is the set of tags that


meets your business requirements

minimum sets described in Best practices

documentation are helpful in that the


encapsulate common business requirements

EDItEUR ONIX 3.0 Specification, Global

implementation and best practice guidelines


and tools

http://www.editeur.org/93/Release-3.0Downloads/

EDItEUR ONIX 2.1 Specifications and tools

http://www.editeur.org/15/Previous-Releases/

http://www.editeur.org/14/Code-Lists/
#Code lists issue latest

Codelists are a vital part of the framework

BISG best practices

http://www.bisg.org/docs/
Best_Practices_Document.pdf
http://www.bisg.org/docs/
Recipient_Best_Practices.pdf

BookNet Canada ONIX best practices

https://booknetcanada.onconfluence.com/
display/UserDocs/ONIX

BIC/Nielsen UK ONIX 2.1 best practice

http://www.nielsenbookdata.co.uk/uploads/
BookData ONIX Guidelines V3_2.pdf

BISAC Subject codes 2012

http://www.bisg.org/what-we-do-0-136-bisacsubject-headings-list-major-subjects.php
(note annual licensing requirement)

BIC Subject codes 2.1

http://www.bic.org.uk/files/pdfs/101201 bic2.1
complete rev.pdf
http://editeur.dyndns.org/bic_categories
(interactive version)

look out for the new, international THEMA


subject scheme in 2013

International Standard Text Code (ISTC)

http://www.istc-international.org

http://www.isbn-international.org

International Standard Book Number (ISBN)

International Standard Name Identifier (ISNI)

http://www.isni.org

graham@editeur.org
http://www.editeur.org