The Digital Media Project1 Leonardo Chiariglione 2005/05/05.

The Digital Media Project 1

The Digital Media Project

Leonardo Chiariglione2005/05/05


Content media

• Content media have always played an important role in society

• Waves of technologies have been deployed to create, publish, distribute and use content media

• Hosts of middlemen set up business to manage an increasingly complex infrastructure

• Public Authorities have played a double role: – tight control in some cases (public service) – hands off in other cases

• 20 years ago the Compact Disc introduced ditial technologies– little more than “better” music on “better” disc


…until ten years ago

• An explosive mix was made– Digital Signal Processing– Digital Networks– Personal Computers

• People’s attitude vis-à-vis content has changed• The foundations of the business of many value

chains have been upset• Digital technologies have transformed the

business of content– From management of scarcity– To management of abundance


Abundance notwithstanding, content has value

• Creating content is still an art – in search of remuneration

• Packaging and distributing content may have to be done differently, but is still needed

• To deliver and consume content we still need networks and devices

• We must preserve the value of content if we want to preserve a means to remunerate those who create


Digital Rights Management

• DRM is commonly touted as the technology that can restore the value of content

• A definition of DRM (NIST): – DRM is a system of IT components and services along

with corresponding law, policies and business models which strive to distribute and control IP and its rights

• A DRM system is a form of communication management

• Without standards a communication system reduces the world to a set of non-communicating islands


Standards for DRM

• There is no universal DRM system, only implementations of DRM systems that satisfy the needs of specific value chain users

• It is impossible to standardise Functions performed in– Existing value-chains (we do not know how today’s value-

chains will evolve)– Future value-chains (we do not know what they will be)

• It is possible to standardise protocols for lower-level functions (Primitive Functions) between value-chain players – Existing Functions are implemented as a combination of

Primitive Functions– Future Functions can be combinations of existing and new

Primitive Functions• This approach supports the possibility to inject continuous

innovation in the system


How to develop a DRM standard

• Many initiatives exist around specific interest groups targeting– Points in the value chain– Specific industries

• There are many corporate agendas– Protect traditional roles– Expand traditional roles– Create new roles

• And one common approach to further them– Proprietary technologies to protect/expand/create value-chains

roles• Many end-users don’t buy it because they lose

– The possibility of accessing all content (aka interoperability)– The many little liberties they used to take with content


The Digital Media Project

• Launched as Digital Media Manifesto in Jul 2003 • Manifesto published in Sep 2003

– http://manifesto.chiariglione.org/

• Digital Media Project established in Dec 2003– http://www.digital-media-project.org/

• The basic DMP position– Digital technologies are an asset of mankind – Creators, intermediaries and end-users should all benefit

from them– This is achieved by standardising appropriate Protocols

between value-chain users supporting the Functions they execute


What happened in these 1.5 years?

• Primitive Functions identified • Requirements developed• Call for Proposals for Portable Audio and Video

(PAV) Devices issued in July 2004• First set of Phase I specifications (for PAVs)

approved in April 2005• Call for Proposals for Stationary Audio and

Video (SAV) Devices issued in January 2004• First set of Phase II working drafts approved

in April 2005• Call for Contributions on Mapping of Traditional

Rights and Usages (TRU) to the Digital Space issued in April 2004


The DMP Phase I Approved Documents

AD Title Type

#1 Use Cases Technical Reference

#2 Architecture Technical Reference

#3 Interoperable DRM Platform

Technical Specification

#4 Value Chains Technical Specification

#5 Registration Authorities Technical Specification

#6 Terminology Technical Reference


AD #1 – Use Cases

• Six Use Cases have been identified– Use Case No. 1 – Open Release– Use Case No. 2 – Open Search– Use Case No. 3 – Home Distribution #1– Use Case No. 4 – Home Distribution #2– Use Case No. 5 – Internet Distribution– Use Case No. 6 – Smart Retailer


Open Release

• Let’s imagine a User who – Owns Rights to a piece of Content– Is interested to Release in a way that other Users can

freely Access it but – Does not want to make it public domain

• Examples:– Publicity material– Trailers– A garage band’s song – Amateur video on a blog– BBC’s Creative Archive project– Lawrence Lessig’s Creative Commons

• An Open Release is “free” now but may not be Released in the same way in the future


An Open Release example

• Leonardo has been invited to give a presentation at a conference

• Now he can no longer attend• As a substitute Leonardo decides

– To send some AV material to the conference organisers

– Structured as Governed Content for controlled distribution

• So he performs the following steps …


Open Release walkthrough/1

1. Create a PowerPoint Resource file2. Create a set of Metadata related to the PowerPoint file

containing:3. Create an audio and video of himself while he makes the

presentation4. Create an audio-visual Resource file e.g. by compressing

audio and video5. Create a set of Metadata related to the audio-visual

Resource containing:6. Obtain Resource and Metadata Identifiers from the

Resource and Metadata Registration Agency7. Create a human-readable license8. Obtain a license identifier from license registration agency


Open Release walkthrough/2

9. Create a machine-readable License corresponding to the human-readable license

10. Obtain License Identifier from License Registration Agency

11. Create a Content Item with Resources, Metadata, human-readable license and License

12. Obtain a Content Identifier from Content Registration Agency

13. Include Content Identifier in the Content Item14. Create a Content file from the Content Item15. Release the Content file to the conference

organisers


Open Internet Distribution

• Interest in Internet distribution– Consumers want to use the Internet to play content on a

variety of devices, e.g. portable devices – Rights holders can benefit from Internet distribution

• The problem of interoperability– So far this has been done using technologies that do not

provide interoperability– The lack of interoperability is a serious obstacle to the

acceptance of governed content distribution mechanisms

• The use case is about the Great Red Band (GRB) garage band that wants to distribute its catalogue using the web


The walkthrough

1. Create an MP3 file and other Resource types2. Create a set of Metadata for all Resources in each

recording 3. Obtain Resource and Metadata Identifiers from a

Registration Agency4. Create a human-readable License5. Create the corresponding machine-readable License6. Store the License in a License server7. Obtain a License Identifier from a Registration Agency8. Encrypt Resources9. Create a Content Item with Encrypted Resources,

Metadata, human-readable License and License 10. Create a Content file11. Post the Content file on GRB’s web site


Home Distribution #1

• A record company offers families a large number of songs at interesting prices

• Family members can choose independently the songs for their Devices

• Family members can play only one song at a time taken from their set any time they want on any of their Devices

• A song can be Used by Devices belonging to more than one family member when the corresponding family members have selected that song.


AD #2 – Architecture/1

• A Work is generated by a Creator in the form of a Manifestation

• Creators, Producers and Instantiators obtain unique Identification of their IP objects from Registration Agencies

• Resources are combined with Metadata as a single entity called Content

• Content is Represented in a form called DMP Content Information (DCI) for the purpose of Using Content on Devices

• Content, too, is uniquely Identified by Registration Agencies• DCI and its referenced Resources need to be Packaged in

order to deliver Content between Users • The DCI is wrapped in a file format called DMP Content

Format (DCF) for the purpose of delivering Content between Users



• A User can deliver a Content Item to another User in two ways– For free Use (un-Governed Content)– With attached conditions to Use a Content Item (Governed

Content)• The latter is done by means of a License which Grants

Rights to a User to Use a Content Item• A language to Represent Rights Expressions is required so

that a Device can interpret Rights• The License of the Governed Content Item can be:

– Bundled within the Governed Content– Not Bundled within the Governed Content

• A User can Access a Content Item with a License that is Bundled within the Content


The End-User Device Model (Phase I)

Content or

License Provider

eXternalDevice

PAVDevice

DCF

Access Content

Access License

License

DCF

Transfer Content



• An external device (XD) (e.g. a PC) Accesses the Content Item and transfers it to the PAV Device

• If the Content Item does not have a Bundled License the XD will need a Tool to Access a License

• XD creates a DCF of the Content Item with a Bundled License and transfer it to the PAV Device

• Both Tools require the establishment of Trust between Devices, which requires the ability to Identify and Authenticate Devices

• Content can be Licensed to groups of Devices called Domains

• To Use a Governed Content Item the PAV Device will Parse the DCF to obtain the License and Parse the License to obtain the Resource Decryption Keys

• Keys are employed to Decrypt Resources that will be Used according to the Rights Granted in the License


AD #3 – Interoperable DRM PlatformTechnologies

• Represent– Content– Keys – Rights Expressions

• Identify– Content– License– Device– Domain

• Package– Content

• Authenticate– Device

• Manage– Domains

• Access– Content– License– Update/Upgrade License

• Process– Binarise XML– Copy– Encrypt/Decrypt– Move– Parse– Play– Print– Render– Store


AD #4 Value Chains

• This shows how technologies from IDP-1 can be utilised to implement the Use Cases of AD #1

• AD #4 is normative in the sense that if a Use Cases is implemented with the Tools selected by AD #4 Value Chain Users can expect to be able to interoperate


AD #5 – Registration Authorities

• Value-Chains handling Governed Content need to be able to reliably and unambiguously Identify such Entities as Content, Devices and Domains

• This task cannot be carried just by anybody and not by a single organisation

• DMP has the role to appoint the “root” element – called Registration Authority – for any type of Entity for which Identification is required

• The Registration Authority will appoint Registration Agencies based on agreed rules

• Registration Authorities are responsible for allocating namespaces to Registration Agencies


AD #6 – Terminology

• A collection of definitions for terms used across the six Approved Documents (terms used with initial capital letter)


Specifications are not enough

• DMP is developing two more Approved Documents– Reference Software– End-to-End Conformance

• Reference software for IDP-1 is being developed as an open movement targeting source code that can be used with a license as close as possible to Open Source


Conformance

• Value-chains are the result of business agreements made by value-chain users that are supported by a set of technologies

• As the IDP is an open specification value-chain users can get solutions from multiple sources

• To be in business each party in an agreement must have the means to make sure that the other parties employ conforming products

• DMP will develop Recommended Practices for End-to-End Conformance to be published in January 2006

• Value-chain users can reference the document in their business agreements


Benefits of DMP specifications

• DMP ADs offer a non-application-specific DRM “tool-kit”

• Value Chains (AD #4) are application specific, but implemented with the same “tools”

• Different business models can be implemented by properly assembling IDP “tools” supplied by an ecosystem of competing providers to set up value chains

• The functionalities of an existing IDP-enabled value-chain can be augmented in a scalable way by adding more “tools”

• Interoperability between value-chains is enhanced by the use of common “tools”


DMP Phase II

• Phase II (started in April) adds DRM technologies to support Devices with network or broadcast access

• This is done by – Re-using the Phase I technologies– Extending the Phase I technologies– Adding new technologies

• Phase II will provide standard technologies to enable interoperable access to Governed Content via broadcast channel and Internet


Technologies for Phase II/1

• Represent– Represent Metadata– Represent Rights Expressions– Represent Tool Pack

• Identify– Identify User– Identify Tool– Identify Tool Pack

• Package– Package Content as Stream– Package Tool Pack as Stream


Technologies for Phase II/2

• Authenticate– Authenticate User– Authenticate Tool Pack

• Manage– Manage Domain– Manage Tool Pack

• Access– Access Tool– Access Tool Pack– Access Tool Pack Data


Interoperability is important but more is needed

• For DMP interoperability of DRM is a must but…• Any DRM has the potential to substantially alter

the analogue-world balance between Users, in particular when one of them is the End-User– The set of Rights acquired by a given Value-Chain User

is subject to the set of Rights that was available to the Value-Chain User granting the Rights

• If the imbalance is not remedied the scope of Traditional Rights and Usages (TRU) of users of media will be reduced

• This may lead to the outright rejection of DRM by some Users, in particular End-Users


Disclaimer

• DMP does not claim that an established TRU necessarily implies a right of a User to a particular Use of digital media

• DMP only claims that, if Users have found a particular Use advantageous in the analogue domain they are probably interested to continue exercising that Use in the digital domain as well– Not necessarily for free

• Leveraging on this interest may offer opportunities for new “Digital Media Business Models” that are – Attractive to Users – Respectful of the rights of those who have created Works

and invested in making Content


Overcoming the TRU obstacle/1

• DMP intends to publish a “Recommended Action on Mapping of Traditional Rights and Usages to the Digital Space”

• The “TRU Recommended Action” will contain scenarios of TRU support made possible by specific technical and legal choices

• Individual jurisdictions may wish to use the “TRU Recommended Action” to determine – TRUs mandatorily supported by the IDPs operating under

their purview– TRUs that can be left to private negotiations between

Users


Overcoming the TRU obstacle/2

• During 2004 a large number of Traditional Rights and Usages have been collected/analysed– See http://www.dmpf.org/open/dmp0270.zip

• A Call for Contributions has been published in Apr 2005– See http://www.dmpf.org/open/dmp0409.doc

• Responses are due by 15 July 2005• TRU Recommended Action is expected to

be published in Jan 2006


TRUs considered in the Call for Contributions

• TRU #1 to quote• TRU #2 to make personal copy• TRU # 3 to space shift content• TRU # 4 to time shift content• TRU #5 to make playback device• TRU #6 to choose playback device• TRU #7 to use content whose copyright has expired• TRU #14 to edit for personal use• TRU 18 to apply a rating to a piece of content• TRU #19 of continued access• TRU #30 to freedom from monitoring• TRU #55 to access content in libraries• TRU #67 to make content creation device• TRU #69 to access content of one's choice


An example: TRU #55 to access content in libraries/1

• Nature of TRU– A user can draw a book from a public library

at nominal or no cost and read it at will for a short, possibly renewable, period of time.

• Digital support – Scenario 1: Digital support of copyright exceptions for libraries– Repositories can “lend” Governed Content by

using copy-controlled check-out and check-in mechanisms for the borrowed Contents Items.


An example: TRU #55 to access content in libraries/2

• Digital support – Scenario 2: Focussed on-line access to Content– A Repository offers the following services

• Content search services not driven by commercial criteria• Pointers to (Governed) Content offered by other (possibly

commercial) sources • Governed Content When no other source is availableWhen

copyright has expired (see TRU #7)• When the Repositories hold the copyright.

• User roles & benefits– Public Authorities:

• enact appropriate legislation to enhance the social role of public libraries in the digital media era.


Read more at

http://mpeg.chiariglione.org/

http://digital-media-project.org/

The Digital Media Project1 Leonardo Chiariglione 2005/05/05.

Documents

Transcript of The Digital Media Project1 Leonardo Chiariglione 2005/05/05.