DOI for eBooks: What are we identifying? Steve Mooney Sophia-Antipolis, France 22 JAN 01

Download Report

Transcript DOI for eBooks: What are we identifying? Steve Mooney Sophia-Antipolis, France 22 JAN 01

DOI for eBooks:
What are we identifying?
Steve Mooney
Sophia-Antipolis, France
22 JAN 01
1
DOI-EB





International DOI Foundation (IDF)
Determine requirements with respect to the
application of unique identifiers to eBooks
Develop proofs-of-concept for the use of
DOIs with eBooks
Develop technical demonstrations, possibly
including a prototype eBook registration
agency/commercial implementations.
February Meeting
2
What is an ebook?


A misnomer
A marketing term
3
EBX: What is an ebook?

“…a digital object that is an electronic
representation of a book. While an eBook can consist of a single page, it is
normally thought of as an electronic
analog of a multi-page hardcover or
paperback book. An eBook may exist in
a variety of formats…”
4
OeBF: What is an ebook?

“…short for electronic book. 1. A Literary
Work in the form of a Digital Object,
consisting of one or more standard Unique
Identifiers, metadata, and a Monographic
body of content, intended to be published
and accessed electronically. 2. May also
refer to the hardware device created for the
purpose of reading eBooks (RocketBook,
SoftBook, Franklin e-bookman),”
5
Selling vs. Licensing




Encryption
Migration
Taking a Portion
What does it mean “to sell” an ebook?
6
Digital Rights Management
7
AAP DRM Report


Big Cost to AAP
Points about DRM





“enables digital commerce”
“protection of digital content”
“secure ebook distribution”
“ensures content authenticity”
“participant identification”
8
DRM Interoperability



“the condition achieved when two or more
technical systems can exchange information
directly in a way that is satisfactory to the
users of the systems.”
Acknowledges that eBook interoperability is
not likely for some time
Consumers who expect eBooks to provide
interoperability similar to paper books (may
be “unpleasantly surprised”)
9
Reluctant Technology
Providers?


“may be reluctant to adopt a different,
standardized technology approach if this is
viewed as weakening their patent
protections.”
AAP is not the first to observe the effect of
patents on DRM standards making efforts.


MPEG
EBX
10
Interoperability Requirement


AAP SAYS: “DRM standards will need
to enable interoperability that will drive
robust market growth.
Who else set such an ambitious goal?
11
EBX



“…read any book, from any publisher on any
device.”
“…interoperability among different EBX client
and server implementations, so that a server
implemented by one vendor can authenticate
a client implemented by a second vendor.”
“…critical that the distribution and transfer
protocols and the format of Vouchers and
Credentials be standardized to ensure
interoperability….”
12
What Is Interoperability?


meant different things to different EBX
members at different points in time.
“Most technology providers fail to see
value in the interoperability proposed by
EBX. Why should a technology
provider push for DRM interoperability
when it could mean that other
technology providers might benefit?”
13
A Bridge Too Far?

Was EBX’s attempt, or indeed any
attempt, to create full-fledged DRM
eBook interoperability, for now at least,
a bridge too far?
14
A Type of Interoperability?

Is there a type of interoperability that
can facilitate DRM requirements along
the eBook value chain while also not
threatening, or even appearing to
threaten, perfectly legitimate patent
rights, other intellectual property rights
and corresponding commercial
interests?
15
Two requirements


Common Rights Language
Interoperability


not of DRM or of content
but of metadata. <indecs>
16
Interoperability


DRM interoperability does not exist among
technology solutions providers.
Interoperability of eBook metadata based on
DOI is a possible practical step


will not “threaten any single vendor’s value
proposition.”
elements of this approach are to be found within
the recommendations of the AAP eBook Report
itself, namely standardized metadata and use of
DOI.
17
Questions for DOI-EB






Why would one use an identifier?
What metadata is mandatory?
What entities within the entire eBook value
chain must be identified?
Identifying Parties and privacy?
How will DOIs fit into eBook workflow? What
are the components?
May one sell pieces of an ebook? What are
the “saleable” pieces? How are they
identified?
18
DOI-EB Process





Business Requirements
Commercial aspects should be
considered.
DOI-EB Technical Prototypes
February Meeting
Complimentary with OeBF initiatives
19
Conclusions

Developing Understandings


Avoid DRM Overreach


ebook/epublication? DRM? What does is
mean to sell ePublications?
“unpleasantly surprised”
Metadata interoperability based on
unique identification of IP entities
20
Thank You
21