| ||
 |
D-Lib Magazine
|
|
Stephen Mooney |
|
IntroductionSeveral years ago, in a copyright context, I came across a cartoon modeled on the Oracle at Delphi, the seat of ancient world prophecy. A disheveled and filthy traveler crawled toward the feet of a most contented-looking Oracle. The traveler had apparently come quite a distance, in all likelihood by foot, and while the Oracle appeared willing to listen, his interest in the traveler was reluctant, mild at best. Still, the traveler wanted the world�s wisdom, at least as much as one can gain in a copyright context, and forcing what appeared to be his last breath begged of the Oracle to know, "What is Fair Use?" Since the cartoon was unfortunately of the one-frame variety, I personally never received the answer. Such a cartoon could well be drawn about Digital Rights Management (DRM) in the emerging eBook environment. Here, however, our traveler friend would surely ask, "What is Interoperability?" The creator of our imagined cartoon would do well to ensure that this second cartoon were also of the one-frame variety so as to avoid having to answer that particular question. Such avoidance would place the Cartoon Creator in excellent company in the eBook world, and were I to offer a definitive answer here, the astute reader might conclude that I had rushed in where Oracles and Cartoon Creators fear to tread. Still, such questions must at least be approached if we are to gain an understanding of DRM in the emerging eBook environment. To that end, I address four initiatives that have, or soon must, grapple with such questions and issues: the Electronic Book Exchange Working Group (EBX) [1], the Open eBook Forum (OeBF), Digital Object Identifiers for eBooks (DOI-EB), and the recently published eBook Standards of the Association of American Publishers (AAP) [2]. Before proceeding, we need to keep two important points in mind. Firstly, although the term "eBook" serves an immediate marketing need in that it handily identifies something that many seem to understand, the very term "eBook" may be a misnomer. As the marketing focus shifts from the initial sale of an eBook to secondary uses and licenses involving more detailed rights transactions, it is very possible that the term "eBook" may be much less useful than it appears to be at the moment. Thus, we may come to speak of "ePublications." Secondly, what one considers to be "selling" an eBook may, in certain cases, be licensing. I have explored these points in greater depth elsewhere [3]. For our immediate purposes, we must remember that eBooks are not yet fully fixed in commerce, or indeed in our minds, to anywhere near the extent that paper books are. Ironically, the very DRM technologies and processes that gave rise to notions of what eBooks are could begin to rob us of a definitive sense of what eBooks will come to be. The AAP eBook ReportSeveral publishers and other interested parties contributed to the AAP eBook Report, and I would heartily recommend a review of that report for those interested in eBooks. The AAP eBook Report is actually three separate reports, and I comment on each throughout this article. They are: These documents represent hundreds of hours of work by a variety of people in the publishing industry and are an excellent basis from which to address commercial and other needs of eBook environments. AAP eBook Report: DRM for eBooks"Digital Rights Management (DRM), the technologies, tools and process that protect intellectual property during digital content commerce," according to AAP�s DRM for eBooks, "is a vital building block of the emerging electronic book (eBook) market. DRM creates an essential foundation of trust between authors and consumers that is a prerequisite for a robust market." [7] I do not take "robust market" in a solely or strictly commercial way, and although there is much focus on individual consumers, a "robust market" necessarily encompasses libraries, certainly digital libraries. The "DRM Core Concepts" section of the AAP Report is an excellent primer, and the "Publisher DRM Requirements" provides extraordinarily helpful guidelines to those building eBook standards or commercial eBook solutions. Let us dwell briefly on the section of the AAP DRM eBook Report entitled "DRM Interoperability". AAP�s DRM for eBooks: InteroperabilityAAP defines Interoperability as "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." [8] AAP acknowledges that eBook interoperability is not likely for some time [9, 10] and that consumers who expect eBooks to provide interoperability similar to paper books (which may be readily given, lent, or copied) may be "unpleasantly surprised" [11] to discover that various formats and reading devices are incompatible. Among the reasons AAP cites for these conditions are technology providers who "may be reluctant to adopt a different, standardized technology approach if this is viewed as weakening their patent protections." [12] AAP is not the first to observe the effect of patents on DRM standards making efforts [13, 14]. Within the eBook world, EBX was among the first to recognize the implications of patent rights on eBook DRM interoperability [15]. EBX sought to craft a DRM eBook Specification that ensured consumers could "read any book, from any publisher on any device." [16] In fact, EBX specified that it would "�allow 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." [17] The EBX specification further asserted, "It is critical that the distribution and transfer protocols and the format of Vouchers and Credentials be standardized to ensure interoperability between [sic] publishers, distributors, booksellers, libraries, and consumers. [18] DRM eBook interoperability, while a stated goal of EBX, meant different things to different EBX members at different points in time. A colleague commented within an EBX context that "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?" [19] To the extent we focused on DRM interoperability within EBX, we were unable to offer a compelling response to perfectly legitimate concerns about patent rights, issues that AAP aptly observes have been a factor in preventing DRM eBook interoperability. For now, such interoperability does not exist, and according to the AAP eBook Report, we are: �in an environment clouded by multiple, incompatible technologies�Given (this) turbulence in the DRM technology market, it doesn�t seem prudent to bet that any one DRM technology format [20] will emerge from the pack today and garner a commanding market share in the near term. A more reasonable approach, in the near term, is to diversify -- support all current DRM and content file formats and new ones as they appear. This approach is called "DRM pseudo-interoperability" (DPI)�(which) can maximize market opportunity size (because all reading devices become the market) and sidestep DRM interoperability issues. [21] Kindly permit a brief digression having to do with the italics above: DRM technology format. DRM technology and format may be viewed distinctly, as they are two very different things. I sometimes hear it asserted that DRM Interoperability will be addressed by the Open eBook Publication Structure. However, this is not true, nor is it an objective of the OeBF Publication Structure Working Group. Rather, the Open eBook Publication Structure (available for public comment through 14 January 2001) addresses a different problem, that is: allowing publishers to provide their content without having to reformat it for each reading system. The OeBF Publication Structure ensures that content can be viewed on any reading system which is OeB-compliant, so long as the owner of the reading system has the right to read the content on that reading system. [22] The Publication Structure does not, and was not intended to address DRM interoperability. As noted on the OeBF web site, "DRM is an important issue for publishers and must be addressed by individual solution providers and by the industry in general. However, DRM is orthogonal to the creation of an open rich content encoding scheme, which is what the (OeBF Publication Structure) Specification is all about." [23] My colleague makes another interesting observation for which I cannot take credit: "The OeBF Publication Structure is widely acceptable because it does not threaten any single vendor�s value proposition." [24] My colleague�s observation causes me to wonder whether EBX�s attempt, or indeed any attempt, to create full-fledged DRM eBook interoperability is, for now at least, a bridge too far. In attempting to craft some sort of DRM eBook interoperability, the approach of OeBF�s Publication Structure might well be a useful guide. 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? Two immediate possibilities come to mind. The first, noted in the AAP DRM eBook Report, and quite familiar to participants in EBX, is a common rights language for eBooks. There appear to be two candidates at the moment: eXtensible Rights Markup Language (XrML) [25]. and Open Digital Rights Language (ODRL) [26] AAP notes that "a common DRM language will make it easier for content providers to supply content for any DRM system. " My colleague again provides guidance when he suggests that "even with different DRM implementations, technology providers can also cooperate -- they can agree to rights messaging standards." [27] The second possibility for a solution to facilitate eBook requirements is interoperability -- not of DRM or of content -- but of metadata. Before suggesting how interoperability of data bears on DRM in the emerging eBook environment, permit me briefly to review two additional topics addressed by the AAP eBook report -- metadata and numbering. EBook Metadata and Numbering"The publishing industry is built from a collection of disparate databases, many of which contain very similar data but few of which can directly interoperate with each other," according to John Erickson [28, 29] . AAP notes that "without (metadata) standards, in order to track, find, and sell or purchase an eBook, (parties) bear the cost of inefficient mechanisms of entering and communicating metadata�." [30] AAP states as an assumption that the existing ONIX International Standard (ONIX) [31] "will be the baseline for all Metadata standards recommendations." [32] AAP defines metadata as "data about data" [33] and also provides a second worthwhile description of metadata as "factual information that identifies or describes Content and includes all such information except the content itself." [34] Metadata accompanying an eBook enables us more completely to understand an eBook for commercial and other purposes. Most of the information on the title page of a book, for example, is metadata. The AAP Metadata Report makes particularly cogent arguments for the need to standardize certain eBook metadata (e.g., for discovery purposes) while ensuring that other metadata can remain private and unseen by the unauthorized. Ensuring that all participants in the eBook value chain have a common understanding of eBook metadata is essential if eBook content is to be described efficiently and effectively, as is the AAP�s stated goal. Such standardized metadata, however, could also be the foundation for an eBook system of interoperable metadata that need not, and in all likelihood would not, threaten "any single vendor�s value proposition." Such interoperability of metadata could well begin to address the concerns AAP outlines with regard to the dearth of DRM interoperability, perhaps providing a step beyond the DRM pseudo-interoperability (DPI) AAP describes, or, at the very least, facilitating it. Concepts of such interoperability of metadata will be familiar to those acquainted with the intellectual rigor of Indecs [35], developed through the efforts of Mark Bide and Godfrey Rust, who have made clear that "electronic trading depends to a far greater extent than traditional commerce on the way in which things are identified (whether they are people, stuff or deals) and the terms in which they are described, that is, metadata." [36] Indecs, of course, did not focus on eBooks, but it might provide guidance to those involved in eBook undertakings who would like to see some kind of interoperability develop. AAP�s eBook Numbering Report recommends "that publishers implement a new number standard based on Digital Object Identifiers (DOIs) for all eBooks (and) use the DOI in conjunction with the ISBN (or EAN, U.P.C. ISSN) for legacy purposes." [37] The International DOI Foundation (IDF) developed the DOI, an identification system for intellectual property in the digital environment. [38] Metadata associated with a DOI "can express relationships; and it can work with other metadata from other sources to construct services and transactions (by conforming to a standard way of using metadata -- e.g., by expressing the context in which a piece of intellectual property is being used). This enables the construction of predictable, automated transactions." [39] Toward eBook Interoperability of a Sort [40]Two complimentary initiatives, one within the Open eBook Forum and a second within the International DOI Foundation, could well provide the eBook world with the beginnings of interoperability of eBook metadata, and thus provide an avenue toward the DRM interoperability sought by the authors of the AAP eBook Report. Within OeBF, working groups for metadata and identifiers are in the process of outlining detailed requirements as a foundation, perhaps, to developing eBook standards. OeBF is not attempting to reinvent metadata and identifier systems already in place. The requirements developed by such undertakings will inform not only possible standards development within, or adoption by, OeBF but could also inform the second important initiative now under way. As noted in the AAP eBook Report, DOI provides a framework for managing intellectual content, for linking customers with content suppliers, for facilitating electronic commerce, and enabling automated copyright management for all types of media. (The DOI is an implementation of the CNRI Handle System® in which the term "DOI" is used to describe the identifiers [41].) The IDF recently established Digital Object Identifier for e-Books (DOI-EB), one of the purposes of which is to develop technical demonstrations and prototypes for the use of DOI with eBooks based on publisher requirements, many of which appear in all three sections of the AAP eBook report. Might the combination of requirements established within OeBF and elsewhere, combined with the prototype work DOI-EB begins in the first quarter of 2001, provide a foundation for interoperability of eBook metadata? Perhaps so. Persistent readers might recall the imagined cartoon about Digital Rights Management (DRM) in the emerging eBook environment and my admonition that the creator of such a cartoon would do well to avoid answering, "What is Interoperability?" The eBook interoperability envisioned here -- that of eBook metadata based on DOI -- is not the same as the DRM interoperability described in the AAP eBook Report. For the most part, such DRM interoperability does not exist among technology solutions providers. However, interoperability of eBook metadata based on DOI is a possible practical step toward DRM interoperability in that it will not "threaten any single vendor�s value proposition." The elements of this approach are to be found within the recommendations of the AAP eBook Report itself, namely standardized metadata and use of DOI. To bring such interoperability of eBook metadata to fruition, eBook requirements and, perhaps, ultimately eBook standards developed by OeBF as well as the prototypes based on such requirements to be developed by DOI-EB might well cause a future cartoon creator to add a second frame to our imagined cartoon and tentatively, at least, offer an answer to "What is Interoperability?" This time, the Oracle might well point to standardized eBook metadata and unique identifiers as our best practical guide to DRM interoperability in the emerging eBook environment. Notes and ReferencesTo see the entire list of notes and references, see <http://www.dlib.org/dlib/january01/mooney/mooney-notes.html> Copyright© 2001 Stephen Mooney |
|
|
|
Top
| Contents |
|
|
|
D-Lib Magazine Access Terms and Conditions DOI: 10.1045/january2001-mooney
|