TIPO DE ESTUDIO

Protection” (IPMP), which is used within the Moving Picture Experts Groups (MPEG) [8].

In spite of its possible cause of confusion, in the following we will use the more common term DRM, but it is important to stress that DRM does not necessarily mean protection. All cases considered in the preceding sections can only be real- ized using some sort of DRM technology. However, while the first and second cases only need management, the third, fourth, and fifth cases would normally require protection. In the digital world, rights enshrined in the 120-year-old Berne Convention [9], such as to have one’s authorship recognized, to object to distortion or mutilation of works, to make quotes from works, and to use works for teaching, can more effectively be supported using DRM technologies, but not necessarily of the protection type.

A value-chain is a special type of communication system linking different users of the value-chain, and DRM is a technology that is added to the system for better management and control of the flow of information through it. As for all communication systems, if the specification of the technology is known and open, anybody can communicate with anybody else, possibly with the payment of a fee to a third party. If the specification is not known or, if it is, is not open, and the communication system is owned by a third party, this party becomes a gatekeeper. For this reason, DRM is a “neutral” technology that can be used to either preserve or break the status quo.

If a value-chain or a portion of it employs a DRM system that is closed or cannot be independently implemented (that from now on will be called “non- interoperable”), it is very easy to preserve the status quo, actually the access barrier gets even higher and the distribution control tighter. But if a value-chain or a portion of it employs a DRM system that is based on open specifications that can be independently implemented (that from now on will be called “interoperable”), the advantages of low access threshold to creators and users demonstrated by such social phenomena as MPEG-1 Audio Layer III (MP3) and DivX can be combined with the possibility to control the use of digital media, a condition that is known to work to preserve the creators’ incentive to continue creating.

3.6 MAKING DRM INTEROPERABLE

There is growing awareness that an interoperable DRM is needed. But how near are we to having one? The answer is very simple: It’s being done by the DMP.

The basic DMP position is that digital technologies are an asset of mankind that should be used so that creators, intermediaries, and end-users all benefit from them. As stated in the DMP statutes [10]:

. . .DMP promotes the development, deployment, and use of digital media that safe- guard the rights of creators to exploit their works, the wish of end-users to fully enjoy

the benefits of digital media and the commercial interests of value-chain players to provide products and services.

The means to achieve this goal is to provide an open DRM specification, i.e., to achieve standardization of appropriate protocols between value-chain users supporting the functions they perform. To remove any doubt about the goals, DMP has provided adefinition of DRM interoperability:

The technical ability of value-chain users to perform functions through interfaces and using protocols of open specification that can be independently implemented and provide predictable results.

Converting the general DMP objectives into a work plan that can be practically implemented is not simple. The first problem is that there is no such thing as a “universal DRM system” to develop a standard for simply because there is no such thing as a “universal way of doing business with media.” We can only think of a range ofimplementationsof DRM systems that satisfy the needs of specific value-chain users.

The second problem is that digital technologies have forced changes on media value-chains and are likely to keep on doing so. Therefore, it is impossible to standardize functions performed in existing value-chains, as we do not know how today’s value-chains will evolve in the future. It is even more difficult to standardize functions that will be performed in future value-chains, as the shape they will take is anybody’s guess.

However, it is possible to standardize protocols for functions at a more atomic level, called primitive functions, which are executed between value-chain users. Examples are offered byidentificationof content and devices,expression of rights

to content,authenticationof devices,accessto content, etc. Functions performed by value-chain users are obtained through combinations of primitive functions.

Standards are useful because they provide interoperability to users, but in devel- oping a standard one must make sure that it will be possible to continuously inject innovation into the system. The ability to combine primitive functions to create new functions ensures that the system remains open to the introduction of both new primitive functions and new roles in the value-chain. The DMP approach ensures that new technologies can be developed and standardized to enable new functions to be performed in an interoperable fashion.

Currently, DMP is developing a harmonized series of toolkit standards. These specify component technologies, called tools, which support the implementation of interoperable primitive functions. Users of the standard can build solutions suiting their requirements by picking the tools to support the functions of their interest.

The benefits of a toolkit standard are manifold. The first is that value-chains are interoperable, and users can still tailor the technologies to their needs instead