e AAP Open Ebook Standards Initiative Recommendations Summary 22.01.2001 Presenter: Robert Bolick, McGraw-Hill Professional [email protected] Table of Contents - Overview AAP Open Ebook Standards Project Overview Numbering -

Download Report

Transcript e AAP Open Ebook Standards Initiative Recommendations Summary 22.01.2001 Presenter: Robert Bolick, McGraw-Hill Professional [email protected] Table of Contents - Overview AAP Open Ebook Standards Project Overview Numbering -

e

AAP Open Ebook Standards Initiative

Recommendations Summary 22.01.2001

Presenter: Robert Bolick, McGraw-Hill Professional [email protected]

Table of Contents - Overview

AAP Open Ebook Standards Project Overview Numbering - A New DOI Based Standard for Ebooks Metadata - Extensions to ONIX, the Existing Standard Digital Rights Management - Publisher Recommendations Ebook Standards Publishers’ Next Steps

1

Over the past year, the AAP has defined a strategy for ebook market success and has now established standards in targeted areas to help build a mass market.

Overall Program Approach

Define Strategy 11/99 – 3/00

Completed

Mobilize Effort 3/00 Develop Standards Establish ongoing standards governance 5/00 – 11/00 Ongoing Today

Begin process of implementing numbering and metadata standards

Utilize DRM recommendations

2

Table of Contents - Numbering

AAP Open Ebook Standards Project Overview Numbering - A New DOI Based Standard for Ebooks Metadata - Extensions to ONIX, the Existing Standard Digital Rights Management - Publisher Recommendations

Ebook Standards - Toward Ongoing, Coordinated Governance

The Road Map for Success: Overview

3

The emergence of electronic content creation and distribution presents new requirements for book numbering systems.

Unique Selected New Requirements for Book Numbering

What Is It?

Why Important?

 Identifies a given digital object uniquely and unambiguously  Required to locate digital content accurately Persistent  Permanent regardless of its location or the information associated with it  Supports distributed information so important to Internet businesses Granular Infinite  Allows identification of objects nested within other objects  Provides for the generation of an unlimited number of identifiers  Enables creation of new products based on combinations of digital objects  Eliminates limitations inherent in earlier numbering systems Extensible  Allows for the addition of new features or uses at a later date  Encourages innovation within the ebook market 4

A DOI-based ebook numbering standard meets these needs and works with the ISBN so that investments for easy coordination with legacy systems are protected.

Prefix 10.9999

Registration Agency Assigned

Digital Object Identifier Structure

Suffix Illustrative

 The DOI

prefix

starts with “10” to distinguish it from other implementations of the Handle System*

9999999999.99

Object Identifier Publisher Assigned (Could be ISBN)

 The “9999” component of the prefix is assigned by a registration agency that ensures unique numbers  The DOI

suffix

can be any alphanumeric string chosen by the registrant (i.e., publisher)  The recommended suffix format will be “Node1.Node2…NodeN” where Node1 = ISBN (or other std. Identifier) Node2 = Component number Node3 = Sub-component number Node4 = Sub-sub-component number

* The Handle System is a comprehensive system for assigning, managing, and resolving persistent identifiers, known as "handles," for digital objects and other resources on the Internet.

5

Numbers can be assigned to portions of an ebook, enabling new book products and business models.

DOI Numbering of Book Elements

Illustrative Prefix 10.9999

Suffix 9999999999.99.9999

Object Identifier 10.1111

1234567890

ebook Intellectual Property Hard cover Paper back Other Manifestations

10.1111

1234567890.12

Chapter 1 Chapter 2 Chapter 3  Before beginning to assign DOIs to ebooks and ebook components each publisher or publishing unit should establish its own policy for setting the syntactic maps for the DOI suffix. Publishers must:  Decide for a given work what the smallest piece of content it is you are likely to want to sell   Understand the structure of the work and translate that into a syntactical map for the DOI suffix. Estimate per node the likely number of saleable components 6

A flexible catalog system will link individual ebook identifiers to content generally located in multiple locations.

DOI Resolution - Illustrative Example

4a

User could be routed to a metadata sheet (or a web site, etc.) which could indicate formats available

5a

User could be enabled to do something else such as select the format desired Title Author … Available in PDF, LIT , RBK The ebook by Scott

.LIT

4b

User could be routed to a digital object rendered in a specific delivery format

Activated DOI

DOI 3

DOI returns location

DOI System DOI

10.1111/0446603589 10.1111/0446603589 10.1111/0446603589

TYPE Location

RBK LIT www.PublisherA.com/…rbk www.PublisherA.com/…lit PDF www.PublisherA.com/…pdf

1

User takes some action (e.g., ‘clicks’) on the DOI

2

DOI System ‘looks up’ where to resolve the request An activated DOI may be displayed in numerous and various locations and ways: online catalog, the copyright page, as part of a reference in another electronic work, behind an icon or the title of the ebook, etc.

 • • •

4b

a Metadata sheet where the user could possibly select a specific format directly to a specific format of an ebook or to any other location (e.g., vendor web site, etc.).

Table of Contents - Metadata AAP Open Ebook Standards Project Overview Numbering - A New DOI Based Standard for Ebooks Metadata - Extensions to ONIX, the Existing Standard Digital Rights Management - Publisher Recommendations Ebook Standards - Toward Ongoing, Coordinated Governance The Road Map for Success: Overview

8

The metadata team has identified three types of metadata: Discovery, Core and Private Metadata that are needed to support the ebook market.

Type Discovery Metadata Core Metadata Private Metadata

Recommended Metadata Types

Characteristics

 Provides the information necessary to help consumers locate and purchase desired titles  Includes information such as: title, author, cover image, ebook description, author bibliography  Located in e-tailer catalogs, and intended for public consumption  “Kernel” data that is part of the ebook package  Enhances consumers’ experience by supporting features such as cataloging and digital libraries  Intended for public consumption by users of ebook reading devices  Private data not intended for public consumption, but necessary to enable the book selling process  Includes rights specification, format information and return metadata 9

Discovery Metadata is based on ONIX, the international standard for metadata. The first release was created for paper books only.

    ONIX Created to provide “rich” product information to online booksellers ONIX provides the ability to define more than 100 distinct types of metadata including title, author, book identification, subject, etc.

ONIX is based on XML Sample Record 1234567890 0816016356 Schur, Norman W A Harvard graduate For more information visit http://www.editeur.org and download ONIX 10

Extending ONIX to support ebooks provides an easy way for information to be transmitted to service providers .

Recommended Ebook Discovery Metadata Fields

Ebook Product

• Filesize • Filesize Unit Code • Approximate Page Count • Distributor • Replaced-By Product Format Code • Audience Code Details • Other Text Type Code • Referring ISBN • Referring ISBN Product Form Code

Ebook Product Components

• Product Form Code • Product Form Source Code • Contained Component Identifier

Ebook Usage Rights

• Usage Rights Code • Usage Rights Code Type • Usage Rights Description • Rights Country

Ebook Format

• Ebook Software • Ebook Software Description • Format Edition Statement •

Ebook Version Information

Version Number • Ebook Software Version Number

For Future ONIX Releases

• Work ID • Copyright Holder • Ancillary Texts 11

Core Metadata, data that is displayed on ebook reading devices for cataloging and digital libraries, is not collected using a standardized format.

Core Metadata Example ABOUT THIS TITLE Title: Coffee Author: ISBN: John Doe 123456789 Description: This book contains everything you need to know about coffee...

Core Metadata 12

We recommend using a subset of ONIX as a guideline for what metadata can be bundled with the ebook content to enhance the user experience with their reading device.

Two Types of Core Metadata Fields

“Strongly Suggested” Fields

Serves to enhance the user experience by enabling features like cataloging and digital libraries:    Product Numbers Series Information Set Information            Title Subtitle Contributor Role Contributor Edition Approximate Pages Publisher Imprint Publishing Dates On Sale Date Approximate Filesize 13

Fields to Use for Further Identification and Description of the Content:

Additional fields that may enhance a reader’s use and experience if provided on the software/device:            Language Illustrations Subject Audience Territorial Rights Other Text Images/Audio/Visual Website Prize Currency Recommended Retail Price ISBN

Private Metadata, however, is not being standardized as requirements are currently too dynamic to recommend a comprehensive, adoptable standard.

Private Metadata Recommendations  Format-specific information and rights specification language are not currently being standardized. In the near term, multiple ebook formats and DRM solutions will exist resulting in multiple requirements.

 Return metadata is not being standardized now. There is a wide variety in the type of metadata and the relationships developed to obtain and share sales information as well as data provided by consumers. What information is collected will be determined by industry participants.

 As interoperability in the eBook market evolves, opportunities to set standards in the above areas should continue to be explored 14

Table of Contents - Digital Rights Management

AAP Open Ebook Standards Project Overview Numbering - A New DOI Based Standard for Ebooks Metadata - Extensions to ONIX, the Existing Standard Digital Rights Management - Publisher Recommendations Ebook Standards - Toward Ongoing, Coordinated Governance The Road Map for Success: Overview

15

Digital rights management (DRM), the tools and techniques that secure digital content, provides a foundation of trust between author and consumer.

The eBook Market Model

Can I trust that I will be properly compensated for the content I create?

Can I trust that this content is authentic and that my privacy will be protected?

Information Flows eBooks Compensation

(Financial & Information)

16

The trust foundation provides a number of key benefits to both content providers and consumers.

Key DRM Benefits  Identification of parties to the transaction and source(s) of the content  Secure ebook distribution  Controlled content access  Verification of authenticity  Appropriate collection/protection of consumer data 17

DRM consists of a number of technical elements which should be balanced with initiatives in other areas to increase the protection DRM provides.

DRM Domains

Technical

Rights specification

Encryption

Authentication

Packaging

Accessibility

Legislation

Compliance

Investigation

Enforcement Legal Social

Expectations

Mores

Education Business

Value Proposition

New Business Models

18

While there are many companies and organizations focused on DRM, at this early stage of the market, there are no generally accepted standards for DRM.

DRM Industry Participant* Input Adobe bn.com

Glassbook Reciprocal

PREVIEW SYSTEMS Open eBook Forum Working Groups/ EBX Working Group

OverDrive

NuvoMedia

* Representative sampling of some industry participants consulted 19 NetLibrary

IBM

Intertrust

Lightning Source

Magex

Despite the lack of standards, publishers can use “simulated interoperability” to simultaneously support multiple DRM and content file formats.

Near-Term DRM Scenario The eBook by Scott • Consumer acquires the eBook in the format and DRM appropriate for her reading device Publishing Step OEB PDF LIT RB Other • Publishers create ebooks in multiple formats either using in-house capabilities or a service bureau 1 • Ebooks are distributed to the selling step in multiple formats Selling Step DRM A DRM B DRM C DRM D DRM E

RB PDF LIT

1 • • Distribution file formats may be different than retail file formats Publishers may choose to limit distribution formats to reduce production costs while supporting multiple retail formats to maximize available markets Exchange Step DRM A DRM B DRM C DRM D DRM E • Consumer can transport the eBook to a new reading device or give/lend the book • Exchange step either translates the eBook format or enables DRM-controlled key exchange as appropriate The eBook by Scott 20

With simulated DRM interoperability, consumers can experience content without being hampered by the formats used.

eBook Source “.XYZ” format

Today’s Multiple DRM Scenario Consumer 1  Multiple DRM systems required

Rdr A

 Multiple file formats supported

DRM “A” Key

 Complex support requirements

DRM “B”

 Increased costs

Rdr B “.123” format

 Limited user interoperability Consumer 2 21

Ultimately, elements of DRM can be standardized to achieve increased interoperability which benefits consumers.

DRM Standardization Framework

What Is It?

Rights Specification Language  Vocabulary for expressing ebook rights permissions Electronic Package Control  Encryption and packaging technology to support the DRM system 

Why Important?

Enables ebook business models under DRM protection  Provides secure ebook content storage and transmission File Formats  Specifications for storing ebook content and rendering it on a reading device  Key element to enable interoperability between reading ebook devices Trust Infrastructure  Protocols and interfaces that allow one DRM system to establish “trusted” communications with another  Inter-DRM communication reduced implementation costs for industry participants 22

A standardized rights specification language will allow industry participants to pursue a variety of new business models under DRM security.

Desirable Rights Management Features

Specification Options

Multiple distribution models Reading Authenticate View or Play Copy Print Changing Extract Edit Delete Imbed Lend Sharing Export Transfer Install Keeping Backup Uninstall Restore

XML-based tagging

DRM program interface

23

Standardized electronic package controls will enable a variety of devices to unwrap and open ebooks regardless of the original formats.

Trust Infrastructure

The Ebook Electronic Package

Electronic Package Content