e AAP Open Ebook Standards Initiative Recommendations Summary 22.01.2001 Presenter: Robert Bolick, McGraw-Hill Professional bob_bolick@mcgraw-hill.com 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 Mobilize Effort 3/00 Establish ongoing standards governance Develop Standards 5/00 – 11/00 Ongoing Today Begin process of implementing numbering and metadata standards Utilize DRM recommendations Completed 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. Selected New Requirements for Book Numbering What Is It? Why Important? Unique 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 Allows identification of objects nested within other objects Enables creation of new products based on combinations of digital objects Infinite Provides for the generation of an unlimited number of identifiers 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. Digital Object Identifier Structure The DOI prefix starts with “10” to distinguish it from other implementations of the Handle System* Prefix Suffix 10.9999 9999999999.99 Registration Agency Assigned Object Identifier Illustrative 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) Publisher Assigned (Could be ISBN) 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 Prefix 10.9999 Suffix Intellectual Property 9999999999.99.9999 Object Identifier ebook 10.1111 10.1111 Hard cover 1234567890 Chapter 1 Illustrative Chapter 2 Paper back Other Manifestations Chapter 3 1234567890.12 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 5a 4a User could be routed to a metadata sheet (or a web site, etc.) which could indicate formats available Activated DOI User could be enabled to do something else such as select the format desired 4b The ebook Title Author … Available in PDF, LIT, RBK by Scott .LIT 3 DOI User could be routed to a digital object rendered in a specific delivery format DOI returns location DOI System 1 User takes some action (e.g., ‘clicks’) on the DOI 2 DOI TYPE Location 10.1111/0446603589 RBK www.PublisherA.com/…rbk 10.1111/0446603589 LIT www.PublisherA.com/…lit 10.1111/0446603589 PDF www.PublisherA.com/…pdf 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. There are Resolution options. The publisher may choose to have the user resolve to: • • • 4a 4b 5a 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.). This is enabled by a set of parameters which would be included with the string that is passed to the resolution system 7 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. Recommended Metadata Types Type Characteristics Discovery Metadata 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 Core Metadata “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 Metadata 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 <Product> <RecordReference>1234567890</RecordReference> <ISBN>0816016356</ISBN> <Contributor> <PersonNameInverted>Schur, Norman W</PersonNameInverted> <BiographicalNote>A Harvard graduate </BiographicalNote> </Contributor> <Product> 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 Format • Ebook Software • Ebook Software Description • Format Edition Statement 11 Ebook Usage Rights • Usage Rights Code • Usage Rights Code Type • Usage Rights Description • Rights Country Ebook Version Information • Version Number • Ebook Software Version Number For Future ONIX Releases • Work ID • Copyright Holder • Ancillary Texts 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: John Doe ISBN: 123456789 Description: This book contains everything you need to know about coffee... 12 Core Metadata 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 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: 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 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 Legislation Compliance Investigation Enforcement Legal Rights specification Encryption Authentication Packaging Accessibility Social Business Value Proposition New Business Models 18 Expectations Mores Education 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 bn.com Glassbook IBM Adobe Open eBook Forum Working Groups/ Reciprocal PREVIEW SYSTEMS EBX Working Group OverDrive NuvoMedia * Representative sampling of some industry participants consulted NetLibrary 19 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 Publishing Step OEB PDF LIT RB Other • Ebooks are distributed to the selling step in multiple formats Selling Step • Consumer acquires the eBook in the format and DRM appropriate for her reading device DRM A DRM B DRM C DRM D DRM E RB PDF • Publishers create ebooks in multiple formats either using in-house capabilities or a service bureau1 LIT 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 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 20 The eBook by Scott With simulated DRM interoperability, consumers can experience content without being hampered by the formats used. Today’s Multiple DRM Scenario Consumer 1 eBook Source “.XYZ” format Rdr A Multiple DRM systems required Multiple file formats supported DRM “A” Complex support requirements Key DRM “B” Increased costs “.123” format Rdr B 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? Why Important? Rights Vocabulary for expressing ebook Specification rights permissions Language Electronic Package Control File Formats Enables ebook business models under DRM protection Encryption and packaging technology Provides secure ebook content to support the DRM system storage and transmission Specifications for storing ebook content and rendering it on a reading device Key element to enable interoperability between reading ebook devices Protocols and interfaces that allow Inter-DRM communication Trust one DRM system to establish “trusted” reduced implementation costs for Infrastructure communications with another 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 Reading Authenticate View or Play Print Copy Changing Delete Extract Sharing Lend Specification Options Export Edit Transfer Install Multiple distribution models Imbed 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. The Ebook Electronic Package Electronic Package Content <Table of Contents> <Text> <Graphics> <Audio> <Video> Trust Infrastructure Metadata Number(s) Usage Rights Marketing Info Other Data 24 Content “logically” separate from metadata to increase flexibility Multiple content types and file formats supported Core Metadata located with package, other metadata can be located elsewhere Standardized encryption used to secure both content and metadata in package Interoperable file formats will improve publishers’ efficiency in creating and maintaining ebooks. Ebook File Formats Today and Tomorrow Today, there are requirements to support multiple formats Adobe “PDF” Microsoft “LIT” Tomorrow,increased interoperability of file formats means less cost and complexity Microsoft “DOC” Standard Format “A” Rocket Book “RBF” Adobe “PSC” Internet “HTM” Reciprocal “NFF” Palm Pilot “PRC” 25 Standard Format “B” Internet “XML” MS-DOS “RTF” Lower technical support Less editing / proofing Simpler computer systems Fewer process errors Standardized elements of DRM systems will allow them to intercommunicate, enabling true interoperability. Tomorrow’s Standard Scenario Industry standard DRM elements Consumer 1 Ebook Source DRM Standards Industry standard file format (.ISF) Rdr A Enhanced interoperability achieved “.ISF” format Consumer support simplified Rdr B Reduced costs Consumer 2 26 Simulate DRM interoperability in the near term while working with AAP and the open ebook standards organization to develop DRM standards facilitating true interoperability. Key DRM Recommendations Adopt a balanced approach to DRM that includes technical, social and legal dimensions Determine new ways to add value to publisher-sourced content so that it is more valuable than unauthorized versions In the near-term, simulate interoperability by simultaneously supporting the DRM and file formats needed to meet market needs Over the longer-term work with AAP and the open ebook standards group to develop DRM standards needed for true interoperability - Participate in AAP’s Enabling Technologies Committee to refine publisher-specific DRM recommendations - Actively contribute to the open ebook standards organization working groups focused on DRM 27 Table of Contents - Publishers’ Next Steps 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 28 The AAP Enabling Technologies Committee will coordinate the development of publisher-specific standards related to ebooks. AAP Enabling Technologies Committee Design aap Preliminary AAP-led committee continues development of publisher-specific standards recommendations and requirements Enabling Tech. Comm. • “Voice of the publisher” Committee is staffed by volunteers from AAP membership • Develops publisher-specific standards and requirements Committee oversees publisher-specific working group projects, and a subcommittee will participate in the open ebook standards group • Staffed by 1 AAP and several publisher volunteers Publisher-Specific Working Group Projects Working groups meet at AAP or publisher locations at frequency determined by the teams and AAP Committee will meet with other industry participants to discuss issues 29 Publishers can take next steps with guidance from the AAP work just completed. Immediate Next Steps Review the AAP recommendations for ebook standards and make plans to implement http://www.publishers.org/home/ebookstudy.htm Assign individual(s) to work with AAP’s Enabling Technologies Committee to develop publisher-specific ebook technology requirements Contact Open Ebook Forum regarding participation in standards development http://www.openebook.org Launch initiatives to select technology for pilot programs 30 Thanks. For further information: emccoyd@publishers.org bob_bolick@mcgraw-hill.com Table of Contents 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 35 In May, the AAP and seven sponsoring publishers came together to create open ebook standards that benefit all industry participants. AAP Ebook Standards Project Project Leadership Sponsoring Publishers HarperCollins Holtzbrinck Houghton Mifflin McGraw-Hill Pearson Random House Thomson Learning Peter Jovanovich Chair Bob Bolick Larry Klein Richard Sarnoff Accenture Support Metadata Team Liisa McCloy-Kelley - Random House Accenture Support Numbering Team Bob Bolick - McGraw-Hill DRM Team Larry Klein - Pearson Accenture Support Accenture Support Communications Team Kathryn Blough - AAP Accenture Support 36 Ed / Professional Team Nettie Douglas - Thomson Accenture Support The project deliverables will help create an environment that works for all consumers. Ebook Usability Goals Finding ebooks will be enjoyable and efficient Buying ebooks will be secure and private Reading ebooks will be comfortable and enjoyable Storing ebooks will be safe and convenient Disposing of ebooks will include flexible options 37 These standards help create an environment where it is easier and more comfortable for publishers and authors to get into the market. Benefits to Publishers and Authors Common language for describing content (metadata standard) enables fast and reliable exchange of marketing data among rights holders, distributors, sellers and readers Flexible numbering system that easily identifies granular content but links to legacy systems such as ISBN Coordination of publisher-specific recommendations to guide development of DRM technology that works for all industry participants AAP leadership of publisher-specific recommendations through the AAP Enabling Technologies Committee Coordinated development of future standards in open ebook standards group with publishers positioned to provide direction in critical areas 38 This work is widely regarded as laying the groundwork for a vibrant ebook market. Ebook Project Messages Publishers have come together to make it easier for consumers to find and use ebooks We are laying the groundwork for making more ebooks available by making it easier and more comfortable for publishers and authors to get into the market. Our work encourages reading and experiencing content in new ways; anytime, anywhere, and on any device. ‘Experiencing’ content refers to using additional features such as audio, video, links, and interactivity. 39 Publishers can act now to implement a new digital object numbering standard for all ebooks. Key Numbering Recommendations Implement a new numbering standard based on DOIs for all ebooks Use the DOI in conjunction with the ISBN (or EAN, UPC, ISSN) for legacy purposes. Assign and register one ISBN and one DOI to cover all renderings of an ebook Include the ISBN and DOI in the ONIX metadata Indicate the ebook’s available rendering (e.g., PDF, LIT, etc.) in the ONIX metadata Establish a policy for setting the syntactic maps for the DOI suffix Resolve the user to a metadata sheet or use parameter passing to support resolution to specific renderings Assign DOIs to saleable pieces of ebooks by extending the ebook DOI via the use of nodes 40 Each publisher or publishing unit should establish its policy for setting the syntactic maps for the DOI suffix.* Numbering ‘Next Steps’ Determine, for a given work, the smallest subcomponent to be offered to the reader, estimate the number of them in the work, and work up from this to the syntactic map for the DOI suffix. Decide on the approach to handling format identification: a) the AAP/Accenture primary recommendation of parameter passing or b) the AAP/Accenture alternate recommendation for assigning a DOI and ISBN to every rendering of every saleable component. Decide to what the DOI is expected to resolve and ensure that the metadata records are prepared accordingly. As each piece goes into the digital asset management (DAM) system or Production, assign a DOI to it and note, if necessary, that component's place in the work's sequential structure. As each piece goes into the DAM system or Production and the DOI is assigned, create the core ONIX metadata record for that piece. That core metadata record is the same record one will need when the DOI is registered with a Registration Agency. Each publisher will have to determine their parameter set for each ebook, and register with a DOI Registration Agency, including how the resolution system would handle each type specific resolution request (e.g., URL addresses). This will require that product databases include all the ONIX-compliant codes so that info about different formats, different distributors, usage rights, etc., are communicated to DOI Registration Agency when registered. * These are intended to be 'preliminary' guidelines with which to get started, but your Editorial, Production, and Systems staffs can contact the AAP's Enabling Technologies Committee to ensure that they obtain the latest guidance. 41 It may be helpful to walk through some basic examples. General Illustrative Examples (ISBN Prefix 10.9999 Registration Agency Assigned = 1234567890) Suffix 10.1111/ISBN - This reflects the simplest situation: a whole ebook, intended to be sold only as the whole. 9999999999.99 Object Identifier 10.1111/ISBN.1 - This reflects one of the simplest situations: one saleable chapter in a 10chapter book (0-9), where the publisher does not intend to sell any element smaller than a chapter. Publisher Assigned (Could be ISBN) 10.1111/ISBN.01 - This reflects an ebook with as many as 100 individually saleable chapters (0099). 42 Questions? 43 Metadata, descriptive information about a book’s content and characteristics, is created and used throughout the life of a book. It helps readers find and learn about ebooks, as well as organize their own libraries of ebooks. Ebook Market Process Model Create and Publish Market and Distribute Metadata created and used to catalog ebook information Metadata used to help market to booksellers and distributors Sell to Consumer Metadata helps consumers find and evaluate potential purchases 44 Consume Content Metadata provides additional text to augment reading experience Support Consumer Publishers’ ability to manage metadata and consumers’ ability to enjoy ebooks is enhanced through the metadata standards. Potential Metadata Benefits The process by which metadata is collected and distributed is simplified Requirements for inefficient “one-to-one” arrangements between publisher and metadata receiver (e.g., e-tailer) are reduced Ebook metadata accuracy is improved, reducing consumer confusion Ability to search metadata is enhanced, supporting consumers’ ability to find ebooks Ebook device features such as “cataloging” and “digital libraries” are enabled, enhancing the consumer experience The metadata can help communicate information about new ebook products and services that are created, such as selling book sections and superdistribution 45 To promote the adoption of metadata standards, the following next steps should be followed when utilizing ONIX for Discovery Metadata. Discovery Metadata Next Steps Identify resources to understand the ONIX International Standard Determine what metadata fields in ONIX to complete (Note: Core Metadata should be the minimum set of information defined) Map ONIX to existing systems • Include “translation tables” to store code mappings to internal systems • Determine how to use new ONIX Ebook extensions Select an option to implement ONIX: • Modification of current systems to be ONIX compliant • On Site translation of current in-house data Into an ONIX record • Off Site (3rd party) translation of current in-house data Into an ONIX record Coordinate “ONIX Readiness” schedules with each vendor to confirm date when ONIX will be accepted Test ONIX feed with vendors Supply ONIX feed for both paper and electronic books 46 Questions? 47 In addition, the following next steps should be followed when utilizing ONIX for Core Metadata. Core Metadata Next Steps Use Core Metadata as the minimum amount of metadata that should be captured for an ebook. Adopt Core Metadata for use with all service providers in the creation of an ebook. Create the Core Metadata feed • Extract Core Metadata from Discovery Metadata feed for use by service providers • Send the entire Discovery Metadata feed for service providers Note: Core Metadata should never be modified once it is linked to the content. 48 Individual publisher plans should be derived from strategies to create new content offerings enabled by DRM technology. DRM Roadmap DRM Strategy Market Entry Approach Business models Competitive opportunities Value propositions Service offerings Required DRM features Sourcing Plan Implementation Plan Partnership options In-house options Economic dynamics of each option Required sourcing Experimentation Evolutionary ebook program Revolutionary ebook transformation Required investment levels Impact to existing production systems Prerequisite changes Integration Testing Training Planning contingencies File Formats Market penetration by device Device format support Interoperability Execute Plans Pilot programs “Friends and family” program Full roll out Monitor results Evaluate market penetration and customer satisfaction 49 Interoperability needs at consumer, publisher and bookseller Options Necessary Interoperability features Technology Develop Standards Participate in AAP technology initiatives Contribute to standards development through open ebook standards organization Current product features and benefits Enabling technologies Standards compliance Iterate Iterate through this roadmap as market conditions change Questions? 50 Many standards initiatives are underway within industry and trade organizations, but these efforts should be focused toward common goals. Current and Desired Standards Landscape Open eBook Forum AAP Technolog y Group ONIX XrML User Group Open Ebook Standards Electronic Book Exchange OPIMA Int’l. DOI Foundation Open DRM Book Industry Study Group 51 An effective governance process is needed for ongoing stewardship of the new standards and to create needed standards for DRM interoperability. Recommended Governance Process Standards Requirements DRM Infrastructure Working Group DRM Rights Language Specification Working Group AAP Metadata Standards Ongoing Metadata Standards Working Group(s) AAP Numbering Standards Ongoing Numbering Standards Working Group(s) AAP DRM Recommendations A standards council, including publishers and other industry participants, approves standards development AAP DRM recommendations are an input and drive DRM working groups AAP numbering and metadata standards are the basis for ongoing evolution of standards Publishers actively participate in various working groups, along with other industry participants Publishers have opportunity to veto inappropriate standards proposals Harmonized, publisher-endorsed standards result from the process Standards Integration Harmonized, Integrated Standards 52 Preliminary AAP will encourage publisher participation in standards setting through the Enabling Technologies Committee and an open standards organization. Recommended Governance Framework …and collaborates with open ebook standards group on broader standards issues. AAP-led, publisher-sponsored working group develops publisherspecific standards recommendations and requirements... Enabling Tech. Comm. • “Voice of the publisher” • Develops publisherspecific standards and requirements • Staffed by 1 AAP and several publisher volunteers Preliminary AAP Standards Committee Other Industry Participants Standards Groups Liaison • Staffed by 1 AAP who links with industry standards groups • Members of Enabling Tech. Comm. will participate in the work of the standards group Libraries Book Distributors Publisher-Specific Working Group Projects Publishers Open Ebook Standards Group • Sets unified ebook standards Other Standards Bodies Other Rights Holders Technology Providers Book Sellers Service Providers Notes AAP working group leader who also sits on the Global eBook Standards Council Publisher volunteer who participates in AAP working group and may also sit on Global eBook Standards Council 53 Non-AAP members representing other standards groups and industry participants, invited to participate in AAP committee discussions AAP will work with an open standards organization to coordinate development of standards across a broad group of industry participants. Recommended Standards Governance Coordination aap Standards Groups Liaison • Staffed by 1 AAP who links with industry standards groups • Members of Enabling Tech. Comm. will participate in the work of the standards group Other Industry Participants Libraries Book Distributors Liaison between AAP Enabling Technologies Committee and Open Ebook Standards Group coordinates activities Publishers Open Ebook Standards Group • Sets unified ebook standards Other Standards Bodies Other Rights Holders Technology Providers Book Sellers Service Providers Open ebook standards group membership reflects broad base of industry participants on a global basis; including significant rights holder participation Voting rights are determined based on participation in open ebook standards group activities and sponsorship of the standards body 54 Preliminary Liaison participates in standards group governance and encourages participation of publishers Publishers have ability to “veto” inappropriate standards, proposals, or recommendations Voting process protections guard against arbitrary interference with needed actions Open ebook standards group membership includes representation from multiple industry participants, including significant rights holder involvement Open ebook standards group administers desired governance process and working groups AAP standards oversight committee will establish coordinated approval of standards by publishers. Recommended Standards Oversight Committee Preliminary Standards committee directs ongoing standards work by publishers AAP Standards Committee Committee members participate in the working groups of the Open Ebook Standards Group 55