The Digital Media Project

Interoperable Digital Rights Management Platform

Technical Specification, version 3.0

20 July 2007

NOTICE

Use of the technologies described in this DMP Approved Document may infringe patents, copyrights or intellectual property rights of DMP Members or non-members. Under no circumstance shall DMP be held responsible for identifying any or all such rights.

Neither DMP nor any of its Members accept any responsibility whatsoever arising out of or in connection with the use of this DMP Approved Document, the information contained herein and any related Information Technology expression for damages or liability, direct or consequential.

This DMP Approved Document supersedes all previous versions and is subject to change without notice.

DMP is a non profit organisation registered in accordance to the laws of Switzerland.

Foreword

The Digital Media Project

The Digital Media Project (DMP) is a non-profit Association registered in Geneva, Switzerland. Its mission is “to promote the successful development, deployment and use of digital media that respect the rights of creators and rights holders to exploit their works, the wish of end users to fully enjoy the benefits of digital media and the interests of value-chain players to provide products and services, according to the principles laid down in the Digital Media Manifesto” [10].

Membership in DMP is open to any corporation and individual firm, partnership, governmental body or international organisation. DMP does not restrict Membership on the basis of race, colour, sex, religion or national origin. By joining DMP each Member agrees, both individually and collectively, to adhere to open competition in the development of digital media technologies, products or services. DMP Members are not restricted in any way from designing, developing, marketing or procuring digital media technologies, hardware, software, systems or services. Members are not bound to implement or use specific digital media standards, recommendations and specifications by virtue of their participation in DMP.

The goals of DMP are realised by developing Technical Specifications, Technical References and Recommended Practices enabling businesses that support new or improved end-user experiences and Recommended Actions to appropriate entities to act on removal of barriers holding up exploitation of digital media. Technical Specifications, Technical References, Recommended Practices and Recommended Actions are collectively called "DMP Approved Documents" (AD).

DMP operates on the basis of open international collaboration of all interested parties: corporations and individual firms, partnerships, governmental bodies or international organisations, supporting the DMP mission and the means to achieve its goals. DMP ADs are developed according to the DMP Procedures of Work [11]. DMP seeks the involvement of creators and end users of Digital Media through appropriate mechanisms.

DMP ADs are publicly available documents whose copyright is retained by DMP. DMP has the policy to contribute the results of its activities to appropriate formal standards bodies and other appropriate entities whenever this is instrumental to achieve the general DMP goals. Electronic copies of DMP ADs can be obtained free of charge from the DMP web site (http://www.dmpf.org/) or from the DMP Secretariat (secretariat@dmpf.org).

DMP has the intention to make ADs available in a form such that users can implement them either freely, or on a royalty-free basis or on fair and reasonable terms and non discriminatory (RAND) conditions following the IEC/ISO/ITU policy on IPR in international standards. When issuing Calls for Proposals DMP explicitly advises Respondents to the Calls of this policy. If DMP references an external standard or specification in a DMP AD, DMP expects that the same IPR policy, or a comparable one, has been adopted by the entity that produced the standard or specification.

However, it must be noted that DMP is not in a position to make any expressed or implied guarantee that licensing of any of the technologies relevant to any or all of its ADs can indeed be obtained either royalty free, or at RAND terms.

Media and Digital Technologies

Media content has always played an important role in all societies and manifold technologies have been invented and deployed to provide means to store, distribute and consume it. The complexity of these technologies and the stimulus to provide ever-enhanced end-user experiences have created very complex media content value-chains populated by an increasing number of interacting intermediaries, each providing increasingly sophisticated services to the two extremes of the value-chains – creators and end users – as well as to the various intermediaries in between. Note that in DMP all players in the value chain – Creators, intermediaries and End-Users – are generically called Value-Chain Users or, simply, Users. Note that terms beginning with a capital letter are defined in the DMP Terminology [6].

Media value-chain technologies have been designed with two main purposes in mind: the first to provide or augment the end-user experience, and the second to provide or augment the capability to distribute media content. The latest round of technologies – the digital technologies – has augmented the end-user experience, e.g. by providing very high quality audio and video that does not deteriorate with time and use. Further digital networks have also dramatically increased the distribution potential of media content.

As a result, some of the traditional means to manage the value of media content along the value-chain are rapidly losing their established meaning. This is the source of various difficulties and is the major cause of the poor exploitation of the potential of digital media technologies. Digital Rights Management (DRM) has been advocated by many as the set of technologies that can overcome these difficulties because Users are given the possibility to manage Content while it moves along the Value-Chain. The reader is alerted to the fact that the DMP defines DRM as follows: Information Technology components and services which strive to distribute and control content and its rights.

The DMP agrees that DRM has the potential to combine the benefit of digital technologies with the need for a virtuous circle that motivates Creators to continue creating because remuneration is facilitated by DRM technologies. However, DMP sees serious problems in the introduction of DRM technologies that are lacking Interoperability.

A DRM system can be described as a particular form of communication designed to provide controlled communication between two or more Users. Therefore the implementation of a DRM system may require a broad range of communication technologies. Unless these are designed in such a way as to enable communication of Content between two different implementations, DRM becomes an obstacle that prevent Users from having the seamless and rewarding communication that digital media technologies can enable. This has particularly serious consequences in the case of the End-User because the lack of Interoperability detracts from the End-User experience and thus may seriously impede the take off of services designed to provide appropriate remuneration to relevant value-chain users.

Standards can bring benefits to the very special type of communication systems called DRM. However, the application of DRM standards obeys different rules because DRM is tightly connected to business practices that typically need different combinations of DRM technologies. As the introduction of digital technologies is currently forcing changes in the way value-chain users conduct their business, it is hard to define today what kinds of standards are required, much less to forecast what kinds of standard will be needed in the future.

The DMP approaches the problem of DRM Interoperability by specifying individual technologies – that DMP calls Tools – required to implement what DMP calls “Primitive Functions”. These are “smaller” functions obtained when the functions value-chain users perform when they do business between themselves are broken down into more atomic elements. It is expected that, while functions may undergo substantial changes as a consequence of the evolution of the media business in the value-chain, Primitive Functions will generally remain more stable and may just need to be augmented with new technologies.

Therefore the DMP is not developing a universal “DRM standard” capable of providing interoperability between every variety of different Users in arbitrary Value-Chains or across different Value-Chains. The DMP provides specifications of Tools enabling Primitive Functions along with examples of how Value-Chains serving specific goals can be set up using the standard Tools. The DMP specifications are developed in phases, so as to achieve gradual development of standards technologies.

The DMP approach to DRM standardisation is based on the following process

1. For each phase Use Cases deemed to be significant are identified and documented;

2. Primitive Functions required to implement the selected Use Cases are singled out;

3. Requirements for Primitive Functions are developed through inputs from relevant Users;

4. Tools serving the needs represented by the Use Cases are standardised;

5. Calls for Proposals for Tools with the identified requirements are issued;

6. The Tools are selected and documented through an open process. DMP favours Tools that have already been developed, standardised or adopted by other bodies, possibly adapting them to DMP needs;

7. Specifications of how Tools can be assembled to implement the selected Use Cases are developed;

8. In subsequent phases, Calls for Proposals for additional Tools needed to support new Primitive Functions or additional functionalities of existing Tools are issued.

The DMP calls the ensemble of all standardised DRM Tools “Interoperable DRM Platform (IDP)”. The IDP provides several major advantages:

1. The specifications are industry agnostic, i.e. Users are free to build a great variety of Value-Chains that suit their business models by combining just the Tools that are appropriate for them;

2. The capabilities of a Value-Chain or new Value-Chains can be extended by adding more Tools, possibly through additional standardisation;

3. The cost to access standardised Tools may be reduce because in general Tools have multiple usages and may be provided by multiple suppliers;

4. Full interoperability can be achieved within a Value-Chain;

5. An enhanced degree of interoperability can be achieved between different Value-Chains;

6. Innovation can be continuously fed in the system.

DRM requires more than technology

In spite of the value the DMP attaches to Interoperable DRM as the main digital media-enabling technology, the DMP has noted that DRM has the potential to substantially alter the balance that has been in existence in the analogue world between different Users of Content, in particular when one of them is the End-User. If not appropriately remedied, this imbalance may lead to a significant reduction of the scope of Traditional Rights and Usages (TRU) of Users. A possible outcome is the outright rejection of the new technology on the part of some Users, in particular End-Users who will perceive the media experience in a DRM environment as inferior.

The DMP is not claiming that an established TRU necessarily implies a right of a User to a particular Use of digital media but simply that, if Users have found a particular Use advantageous in the analogue domain, they are probably interested in continuing to exercise that Use in the digital domain as well. Leveraging upon this interest may provide multiple opportunities for new “Digital Media Business Models” that are attractive to Users but respectful of Rights Holders.

Therefore the DMP intends to add technologies to its specifications to make the exercise of a broad range of TRUs technically possible. However, even a summary analysis shows that many TRUs have a legislative/regulatory impact that needs to be addressed by proper authorities. This can only be done within individual jurisdictions by determining which TRUs shall be mandated in Interoperable DRM Platforms operating under their jurisdiction and which TRUs can be left to private deals between Users. This is a challenging task because it requires blending knowledge encompassing the legal, social and economic fields with in-depth knowledge of the highly sophisticated and unusual DRM technologies.

The suite of DMP Approved Documents

DMP has produced the following ADs:

1. Approved Document No. 1 – Value Chain Functions and Requirements [1]: a collection of Primitive Functions derived from today’s media value-chains with corresponding Requirements.

2. Approved Document No. 2 - Architecture [2]: a general architecture that describes some of the digital extensions of today’s media value-chains and collects the basic assumptions and technologies underlying the establishment of IDP-enabled Value-Chains.

3. Approved Document No. 3 – Interoperable DRM Platform [3]: a collection of technical specifications of basic Tools that are needed to implement Primitive Functions.

4. Approved Document No. 4 – Use Cases and Value Chains [4]: a collection of Use Cases along with normative specifications of examples of (portions of) Value-Chains implementing the Use Cases using the Tools drawn from the IDP Toolkit.

5. Approved Document No. 5 – Certification and Registration Authorities [5]: a set of operational rules for Certification Authorities established to Certify Devices and DRM Tools, and Registration Authorities established to Assign Identifiers to Content, DRM Tools, Devices, Users and Domains.

6. Approved Document No. 6 – Terminology [6]: a set of terms and corresponding definitions that are used throughout DMP ADs providedto overcome the problem of DRM being a field that impacts many existing fields with their own established and sometimes conflicting terminologies.

7. Approved Document No. 7 – Reference Software [7]: a software implementation of IDP Tools distributed, whenever possible, under the Mozilla Public Licence. When this is not possible DMP provides the reference software with a “modify, use and distribute” license.

8. Approved Document No. 8 – End-to-End Conformance [8]: a set of Recommended Practices that Value-Chain Users can reference to ascertain that the Tools employed by other parties conform to DMP Technical Specifications and Technical References.

9. Approved Document No. 9 – Mapping of Traditional Rights and Usages to the Digital Space [9]: a set of example support of TRUs using DMP Tools possibly complemented by recommendations to appropriate authorities to enable the benefit of TRUs in a DMP-enabled world of digital media.

1 Value Chain Functions and Requirements

1.1 Introduction

DMP is developing a series of specifications for Interoperable DRM called Interoperable DRM Platform (IDP) where each phase of the IDP specifications is indicated by a sequential number. The open IDP specifications enable Users to technically execute Functions using standard Protocols through standard Interfaces with predictable results.

Because there is such a broad variety of value-chains there can hardly be a “universal DRM system” to develop specifications for. Therefore it is expected that there will be a range of “implementations” of DRM systems designed to satisfy the needs of specific value-chain users. The DMP specifications can be used to realise the digital equivalent of the media value-chains that exist today, but also to make value-chains that have no obvious equivalent with today’s value-chains.

This unpredictable environment requires a different type of standardisation than used for other standardisation efforts, e.g. video coding, that typically apply to well-defined environments. The DMP approach is based on protocols for lower-level functions (called Primitive Functions) between value-chain users. If Primitive Functions are well defined existing and possibly new Functions can be built as combinations of Primitive Functions. In the future new Functions could also be built using existing and new Primitive Functions.

This document documents the requirements upon which the Interoperable DRM specification has been developed. To achieve this, the following process – open to any party – has been invoked:

1. Ask a broad range of value-chain users to state their needs

2. Derive Functions from the stated needs

3. Develop requirements for implementing Functions

4. Identify prominent use cases used to focus the development of specifications

5. Issue Call for Proposals for technologies to implement Functions.

All documents produced at each of these steps have been made publicly available for comments on the DMP web site at http://www.digital-media-project.org/.

So far representatives of the following value-chain users have contributed to the process:

1. Civil Rights Associations

2. Association of People with Special Needs

3. Collective Management Societies

4. Device Manufacturers

5. Individuals

6. Producers

7. Public Service Broadcasters

8. Sheet Music Publishers

9. Telecommunication operators.

This document is work in progress as it is the starting point for the series of interoperable DRM specifications that DMP plans to develop. Those wishing to comment on or contribute to future versions of this Approved Document No. 1 are requested to forward their submissions to Marc Gauvin (mgauvin@sdae.net). Submissions are typically discussed within the Ad hoc Group on Requirements for Interoperable DRM Platform, whose email reflector is idp-ied-rq@dmpf.org. To subscribe to the email reflector follow the instructions.

This Approved Document No. 1 contains

1. The list of Value-Chain Users identified so far by DMP, and whose requirements the DMP expects to support (Chapter 2)

2. The list of General Requirements underpinning the DMP process (Chapter 3)

3. The table a Primitive Functions identified with indication of which IDP Phase supports the given Primitive Function (Chapter 4)

4. The full list of Functional Requirements of Primitive Functions (Chapter 5).

1.2 Value-Chain Users

#	Value-Chain User	Acr.	Definition
1.	Creator	CRE	A User who creates a Work and generates its first Manifestation
2.	Performer	PRF	A User who interprets a Manifestation of a Work making an Instance
3.	Registration Authority	RAU	A User managing Identifier name spaces, and appointing and overseeing Registration Agencies
4.	Registration Agency	RAG	A User appointed by a Registration Authority to Assign Identifiers
5.	Collective Management Society	CMS	A User who provides collective representation to its members, e.g. Authors, Performers, Publishers etc.
6.	Producer	PRD	A User who produces Content
7.	Publisher	PBL	A User who selects Content and makes it available to other Users
8.	Syndicator	SND	A User who manages and places Content to Retailers using a variety of purchasing options
9.	Metadata Resolution provider	MRP	A User who resolves, i.e. maps between disparate sets of Metadata
10.	Repository	RPS	A User who offers Services to long-term Store, Identify, describe, locate, Access, manage, and Validate Content and its Metadata
11.	Monitoring Service provider	MNP	A User who processes Use Data to provide information
12.	Marketer	MKT	A User who provides promotional, sale enhancement, brand enhancement and merchandising Services
13.	Aggregator	AGG	A User who provides procuring, packaging, presenting, cataloguing, archiving and indexing Services typically to Retailers
14.	Retailer	RTL	A User who sells or Licenses Content to an End-user
15.	Technology provider	TCP	A User who provides technology to make Devices
16.	Technology licensing provider	TLP	A User who provides Device Manufacturers with a license to utilise patented technology to make Devices
17.	Device Manufacturer	DVM	A User who manufactures or assembles hardware and/or software components to make Devices
18.	Connectivity provider	CNP	A User who provides point-to-point or point-to-multipoint connectivity between Users
19.	Network Service provider	NTP	A User who provides Internet Protocol (or equivalent) services and typically various other services above it, e.g. quality of service
20.	Tool provider	TOP	A User who sells or Licenses Tools to Users
21.	Certificate Authority	CRA	A User who issues digital Certificates used to create digital Signatures and public-private Keys
22.	Certification Authority	CAU	A User appointing and overseeing Certification Agencies
23.	Certification Agency	CAG	A User appointed by a Certification Authority to Certify Devices or DRM Tools
24.	Clearing House	CLH	A User who collects Value Expressions from other Users to distribute to Right Holders for the purchase of Use Rights over a given instance of Content
25.	Payment Service provider	PSP	A User who provides the infrastructure for financial transactions
26.	End-User	ENU	The last User in a Value-Chain
27.	Reseller	RSL	A User who possesses the Right to control the disposition and transfer of Content from End-users to different End-users
28.	Public Authority	PBA	A User who provides rules relating to the Use of Content and taxation on transactions related to Content.

1.3 General requirements

1.	The IDP shall be a “tool-kit” specification
2.	The IDP shall evolve in phases, each phase introducing new Tools keeping compatibility with the Tools of preceding phases
3.	The IDP shall be open to support all legitimate needs by · Value-Chain Users · Associations of People with Special Needs
4.	The IDP shall support Rights inheritance, i.e. that 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
5.	The IDP shall support the ability of a given Value-Chain User to mask the Value-Chain Users supplying Services to it in support of the Services that it provides to its clients
6.	Licensing of technologies required to implement IDP tools shall be RAND and preferably royalty-free
7.	The IDP shall be designed in such a way that its use shall have a minimal impact on Users, ideally that its use should be transparent
8.	The IDP Tools must satisfy the relevant requirements expressed in this document
9.	All Entities must be capable of being uniquely and unambiguously Identified
10.	Information about Devices and Domains shall be restricted to the minimum required for these to operate in the DMP Environment
11.	The IDP shall specify technologies that are native to it (e.g. the Rights Expression Language) and supported by implementations claiming conformance with IDP. DMP recognises that there may be implementations that replace the native IDP technologies with others that have the same functionality. However, no support for conformance testing to such implementations will be provided by DMP.

1.4 Primitive Functions

The following table provides the current list of Primitive Functions grouped in categories. For each Primitive Function a cross in any of the last two right columns indicates whether or not it is currently specified and if so in which version of the Interoperable DRM Platform (AD #3). An X in both columns means that technology is provided by IDP-2 that adds to the technology already provided by IDP-1.

Table 1 – Primitive Functions

Category	Primitive Function	IDP#1	IDP#2	V.2.1	V.3.0
Represent
	Represent Identifier of Content	X
	Represent Identifier of Device	X
	Represent Identifier of User		X
	Represent Identifier of Domain	X
	Represent Identifier of DRM Tool		X
	Represent Identifier of Footprint
	Represent Identifier of Class of Users
	Represent Identifier of Territory
	Represent Identifier of Jurisdiction
	Represent Content	X	X
	Represent Resource		X
	Represent Metadata		X
	Represent DRM information		X
	Represent DRM Tool Body		X
	Represent DRM Tool		X
	Represent Rights Expression	X	X
	Represent Rights Data			X
	Represent Key Body		X
	Represent Key	X	X
	Represent Device Information		X		X
	Represent Domain Information		X
	Represent Use Data	X
	Represent Value Chain
	Represent Resource Format
	Represent Binarised XML	X
Identify
	Identify Content			X
	Identify IP Class			X
	Identify Metadata
	Identify Device	X
	Identify Domain		X
	Identify Role
	Identify User
Recognize
	Recognize Items			X
	Recognize Roles			X
Revoke
	Revoke Content
	Revoke Content Element
	Revoke Device
	Revoke Domain
	Revoke User
Authenticate
	Authenticate Content			X
	Authenticate Device	X
	Authenticate DRM Tool		X
	Authenticate User
Verify
	Verify Content
	Verify Device
Negotiate
	Negotiate Licence
	Negotiate Use Data
	Negotiate Licence and Use Data
Report
	Report Use Data				X
Deliver
	Store				X
	Copy
	Move
	Backup
	Export
	Access	X	X
	Restore
	Import
	Update
	Inter-Device communication				X
Manage
	Manage Domain	X	X
	Manage DRM Tool		X
Package
	Package as File	X
	Package as Broadcast		X
	Package as Streaming		X
Process
	Encrypt/Decrypt	X
Transact
Test Conformance
	Test Conformance of Rights Expressions
	Test Conformance of Enforcing Rights Expressions
	Test Conformance of Tamper resistance
Certify
	Certify Content
	Certify Device
	Certify User

	Detailed description of Requirements
Definition	The syntax of the information used to describe the identity of Content so that it can be Processed by a Device
Objective	To enable accurate Governance of a Content Item
Requirements	1. Ability to provide unique and unambiguous identification of a Content Item 2. Ability to support versioning 3. Ability to extend the total number of Identifiers that can be Assigned in such a manner that previously Assigned Identifiers do not become obsolete 4. Ability to Identify Content by different Users to enable tracing the origin of Content when Licensed to other Users 5. Ability to Identify a Content Item for Use only within a specific Device or a Domain (e.g. a Broadcast Footprint, a company, a home)
Benefits	1. Flexible distribution schemes where different Content Elements may be supplied by different Providers 2. A given Content Element may be referenced in multiple parts of a Content Item 3. Multiple Content Items can refer to the same Content Element 4. Fine granularity of Rights Expressions.

1.5.1.2 Represent Identifier of Device

	Detailed description of Requirements
Definition	The syntax of the information used to describe the identity of a Device employed in a particular instance of Use so that it can be Processed by a Device
Objective	To enable various Device-related Functions such as · To support the association of a piece of Governed Content with a Device · To support Trust management
Requirements	· Ability to work in conjunction with existing industry schemes to administer customer/device-specific uses · Ability to extend the total number of Identifiers that can be Assigned in such a manner that previously Assigned Identifiers do not become obsolete · Ability to obtain Device capability information by reading the Device Identifier · Ability to support requirements for Domain Management
Benefits	· Allows reliable administration of Device-based Uses · Compatible with replacement strategies in cases where a Device is destroyed or otherwise replaced, or else used only for a period of time after which a different Device will be used.

1.5.1.3 Represent Identifier of User

	Detailed description of Requirements
Definition	The syntax of the information used to describe the identity of a User in a particular instance of Use so that it can be Processed by a Device
Objective	To enable various User-related Functions such as License Content to an Identified User
Requirements	· Ability to support User Authentication · Ability to support Identification of any Value-Chain User · Ability to accommodate a variety of models for human interaction with Devices e.g.: o Allow a single User to use multiple Devices, o Allow multiple Users to share a single Device, o Allow the use of a confidential identity (e.g. prepaid card) · Ability to extend the total number of Identifiers that can be Assigned in such a manner that previously Assigned Identifiers do not become obsolete · Ability to access information related to the User that may be legally required for the provision of Content
Benefits	Depending on a given device's design, allows one User to employ multiple devices or allows multiple Users to use a single device

1.5.1.4 Represent Identifier of Domain

	Detailed description of Requirements
Definition	The syntax of the information used to describe the identity of Domain so that it can be Processed by a Device
Objective	To enable Value-Chain Users to License Content to Identified groupings of Users and/or Devices
Requirements	· Ability to support the following types of Domains o Device-based o User-based o Location-based (e.g. DHCP) o Mixed Device, User and Location-based o Context-based § By reference to a legally established class of special users (e.g. students, people with special needs) · Ability to support a hierarchy of Domains
Benefits	Enable more Uses of Content by Identifying groupings of Users and/or Devices instead of just individual Users or Devices

1.5.1.5 Represent Identifier of DRM Tool

	Detailed description of Requirements
Definition	The syntax of the information used to describe the identity of executable code or hardware device that implements one or more DRM Functions on a Device so that it can be Processed by a Device
Objective	To facilitate Authentication of DRM Tools
Requirements	Ability to Identify individual DRM Tools Ability to Identify groups of DRM Tools as an Entity (Tool Group) Ability to Identify complete DRM Systems (Tool Packs)
Benefits	· To obtain and classify DRM Tools · To Authenticate DRM Tools

1.5.1.6 Represent Identifier of Footprint

	Detailed description of Requirements
Definition	The syntax of the information used to describe the identity of a primary broadcast distribution area so that it can be Processed by a Device
Objective	To enable Devices to Use Content intended for a particular Footprint
Requirements	Unique and unambiguous identification of a particular Footprint
Benefits	Enable Usage of Content within a particular Footprint

1.5.1.7 Represent Identifier of Class of Users

	Detailed description of Requirements
Definition	The syntax of the information used to describe the identity of a particular class of Users so that it can be Processed by a Device
Objective	To enable Devices to Use Content intended for a particular class of Users
Requirements	Unique and unambiguous identification of a particular class of Users
Benefits	Enable Usage of Content within a particular class of Users

1.5.1.8 Represent Identifier of Territory

	Detailed description of Requirements
Definition	The syntax of the information used to describe the identity of a particular geographical area so that it can be Processed by a Device
Objective	To enable Devices to Use Content intended for a particular Territory
Requirements	Unique and unambiguous identification of a particular Territory
Benefits	Enable Usage of Content within a particular Territory

1.5.1.9 Represent Identifier of Jurisdiction

	Detailed description of Requirements
Definition	The syntax of the information used to describe the identity of a particular Jurisdiction so that it can be Processed by a Device
Objective	To enable Devices to Use Content intended for a particular Jurisdiction
Requirements	Unique and unambiguous identification of a particular Jurisdiction
Benefits	Enable Usage of Content within a particular Jurisdiction

1.5.1.10 Represent Content

	Detailed description of Requirements
Definition	The syntax of the information used to describe the organisation and association of Content and Content Elements so that it can be Processed by a Device
Objective	To enable a predictable processing of Content and Content Elements according to the purposes of the Content Item design, i.e. to Represent the Governed Use of Work, Manifestation, Instance, Production, DRM Tool etc.
Requirements	· Ability to provide persistent association of Identifiers to Content and Content Elements · Ability to include Clear-text and Encrypted Identifiers, Content and Content Elements in a Content Item · Ability to apply Licenses to different Content Elements in a Content Item · Ability to Use individual Content Elements in a Content Item · Ability to associate to a Content Item Content Elements Stored at locations remote from each other · Ability to support temporary and permanent unavailability of Content Elements · Ability to Represent Content in a Delivery-System agnostic format · Ability to convey information related to § Key management § Encryption methods § Watermarking § Etc. · Ability of a Content Item to contain another Content Item
Benefits	· Standard format to securely communicate Resources and Governance information for Use · Multiple Uses of the same Resources (e.g. possibility to create multiple play lists) · Different Licenses for the same Content and/or Content Elements · Easy navigation · Easy repurposing

1.5.1.11 Represent Resource

	Detailed description of Requirements
Definition	The syntax of the information used to describe the format of a Resource so that it can be Processed by a Device
Objective	To enable a Device to interpret the Representation so that the Resource can be Used
Requirements	· To be as simple as possible · To be as expressive as required
Benefits	Use of Resources by Devices

1.5.1.12 Represent Metadata

	Detailed description of Requirements
Definition	The syntax of the information used to describe features and attributes associated with Content and Content Elements or Devices so that it can be Processed by a Device
Objective	· Facilitate interaction between Users for a plurality of purposes, e.g. o Classification o Description o Search and retrieval o Presentation o Etc. · Enable best Use of Content on Devices
Requirements	· Ability to support existing Metadata standards · Ability to signal the standard in use · Ability to employ a minimal Metadata standard set for End Users · Ability to describe Device features and capabilities
Benefits	Allow for an effective interchange of Content between Users and optimal Use of Content and Devices

1.5.1.13 Represent DRM Information

	Detailed description of Requirements
Definition	The syntax of the information used to describe Governance of Content so that it can be Processed by a Device
Objective	To enable a Device to interpret the information so that Content can be Used as determined by its Governance
Requirements	Ability to represent · DRM Tools required to Access Content · Initialisation and configuration data for DRM Tools · Decryption Keys · Information related to DRM Tool Management · Placeholders for Licenses
Benefits	Enable Content Governance by Devices

1.5.1.14 Represent DRM Tool Body

	Detailed description of Requirements
Definition	The syntax of the specific information used to describe DRM Tool embodiments used so that they can be Processed by a Device
Objective	To enable a Device to execute DRM Functions specific of a given Content Item
Requirements	· Ability to Represent a single Tool Body · Ability to Represent a Tool Pack Body
Benefits	Extend the number and scope of DRM Functions that a Device can execute

1.5.1.15 Represent DRM Tool

	Detailed description of Requirements
Definition	The syntax of the specific information used to describe the environment in which DRM Tools will operate so that they can be Processed by a Device
Objective	To provide the Device with the means to perform the required DRM functionality
Requirements	The Representation shall include: · Tool ID · DRM Processor type, including o Vendor o Model o Serial number · Target OS including o Vendor o Model o Serial number o Version o Virtual machine · CPU o Vendor o Model o Speed · Memory o Vendor o Model o Speed o Size · Auxiliary hardware o Smart card o Hard Key · Network · Downloading · RPC mechanism · Firmware · Tool API configuration o Instantiation API ID o Messaging API ID · Target HW · Format e.g. zip · Tool source · Authentication parameters · Update schedule info · Tool Validation info · License info · Others
Benefits	Upgradeable Device capable of executing multiple DRM functionalities

1.5.1.16 Represent Rights Expression

	Detailed description of Requirements
Definition	The syntax of the information used to describe Permissions and Conditions so that it can be Processed by a Device
Objective	To allow conditional Use of Content, based on the Conditions being satisfied or fulfilled
Requirements	· Ability to interpret a Rights Expression o Without a return channel o With low payload o On a wide array of Device sophistication · Ability to unambiguously Identify o The User granting the Permission o The Device, User or Domain obtaining the Permission o The Content and Content Elements to which the Rights Expression refers · Ability to utilise (Rights data dictionary) o A User selectable Rights data dictionary o A minimal default Rights data dictionary · Ability to Represent (Permission sets) o Different subsets of Permissions o New Permissions when the need occurs · Ability to Represent (specific Permissions to Content) o Conditional expiry (e.g. Content may no longer be Used if Stored for longer than a determined period without Use) o One Rights Expression to many Content Elements o Many Rights Expressions each referring to a different Content Element § In particular a Content Item can have no Rights Expression (i.e. a Device can Use the Content without limits) o Content Uses e.g. § Period of time (e.g. play as long as the play time is greater than specified time and less than a specified time) and based on time/date § Count based (play up to a specified number of times) § User based § Device based § Domain based § Location based o Rights Expressions with Context Use limitations, e.g. age of End-User · Ability to support Delivery by: o Streaming o Broadcast o File download o Physical media · Ability to support (Conditions) o Territories o Jurisdictions o Footprints o Domains o Devices o Users o IP Entities · Ability to support (Functions) o Not to Encrypt clear-text Resources o Quote o Time-shifted Use o Annotation o Trick modes o Move/Copy § Between Devices § Within Domain § Within Footprint o Export to a movable media · Ability to support (Content types) o Reference to different IP Entities o Addition of Metadata o Use of the following types of Resources: audio, video, images, text and executables and groups/bundles thereof o Access of Content based on Rating (e.g. suitability for age) o Rights to segments of Content o Many Rights Expressions each referring to particular Content Elements of a Content Item · Ability to support (Rights of Users) o Ability to represent the sets of Rights pertaining to all Users e.g. Authors, Performers, Producers, Aggregators, Distributors, etc. o The Right of a User to License another User o Restriction to a class of Users o Multiple Licensors · Ability to support dynamic creation of Rights Expressions as a result of interaction between Users · Ability to support Creative Commons licenses
Benefits	Potentially allow the full range of human contractual agreements to be embodied in the digital domain, especially including automatic processing of agreements that are stated in rigorous forms

1.5.1.17 Represent Rights Data

	Detailed description of Requirements
Definition	The semantics of the data used in Permission and Conditions so that they can be interpreted by a Device in a predictable way
Objective	To enable a device to perform the Functions in an agreed and predictable way
Requirements	· The RRD will maintain a basic core set of terms for o IP Entities o Actions o Rights o Roles · The RRD will support a number of extensions created as the need arises · The RRD extension will be consistent with the core · To support the following IP Entities o Work o Adaptation o Manifestation o Instance o Work Instance o Adaptation Instance o Work Manifestation Copy o Work Instance Copy o Adaptation Manifestation Copy o Adaptation Instance Copy o Product · To support the following Actions o Create Work o Make Manifestation o Make Work Manifestation o Make Adaptation Manifestation o Make Instance o Make Work Instance o Make Adaptation Instance o Make Copy o Make Adaptation Instance Copy o Make Adaptation Manifestation Copy o Make Work Instance Copy o Make Work Manifestation Copy o Play o Copy · To support a subset (to be defined) of the following REL Rights: o Adapt o Delete o Delist o Diminish o Embed o Enhance o Enlarge o Enlist o Execute o Export o GovernedAdapt o GovernedCopy o GovernedMove o Install o Modify o Move o Play o Print o Reduce o Uninstall · To support the following Roles o Creator o Adaptor o Instantiator o Producer o Distrubutor o End User · RRD shall support the execution of Functions, some of which may be derived from the terms in the list above or be included as new terms o Adapt (Resource) § Conversion of compression method § Video resolution § Sampling frequency o Backup o Copy o Edit o Encrypt o Export o Import o Move o Quote o Restore o Space-shifted Use o Store o Synchronise o Time-shifted Use o Transfer to an external rendering device o Etc. · It must be machine readable · It must convey a strict correspondence between machine and human based interpretation and understanding · It must be represent a wide array of Users through adoption of one or more Roles · It must describe a complete array of Actions that Users can perform on or with IP Entities. · It must be capable of discerning between Roles on the basis of different combinations of Actions and IP Entity relationships · It must be capable of associating Rights with Actions and Roles. · It must be capable of describing the transfer of Rights throughout the Value Chain · It must be able to associate which IP Entities are required by Actions and which if any are produced by Actions.
Benefits	· Users have assurance that Devices behave predictably. · Essential input for conformance testing.

1.5.1.18 Represent Key

	Detailed description of Requirements
Definition	The syntax of the information used to describe Keys and associated parameters so that it can be Processed by a Device
Objective	To provide a Device with the necessary information to utilize a Key
Requirements	· Ability to represent o Time dependent/independent Keys o Association of Keys to particular time segment of a Resource o Key type and related data (e.g. Authentication, Certificates, etc.) o Set of Key types
Benefits	The ability to use multiple Keys and Key Management schemes

1.5.1.19 Represent Device Information

	Detailed description of Requirements
Definition	The syntax of the information used to describe the capabilities of a Device to perform Functions so that it can be Processed by a Device
Objective	To describe the capability of a Device
Requirements	· To identify Device capabilities, e.g. o Capability to Process (e.g. Render) certain Resource Types o Capability to determine the applicability of certain Rights Expressions o etc.
Benefits	The ability to Access Content that is suitable for the Device

1.5.1.20 Represent Domain Information

	Detailed description of Requirements
Definition	The syntax of the information used to describe the attributes of a Domain so that it can be Processed by a Device
Objective	To describe the minimum set of attributes of a Domain that is required to License Content for that Domain
Requirements	· The Representation shall include o Information about when the Domain was created o Domain Identifier o Domain Public and Private Keys o Domain Administrator’s name and password o List of Devices/Users in the Domain o Maximum number of Devices/Users o List of Revoked Devices/Users o Expiration date of Domain · The Representation may optionally include o Type of Devices o Maximum frequency of Devices/Users leaving and joining
Benefits	· For the Content Provider the ability to determine proper Licensing of its Content · For the End-User the ability to obtain Content for Use within his Domain

1.5.1.21 Represent Use Data

	Detailed description of Requirements
Definition	The syntax of the information used to describe the elements making up one or more instance of Use of Content, Device or User so that it can be Processed by a Device
Objective	To enable processing of Use Data in a predictable fashion
Requirements	· Ability to Identify Use Data · Ability to support protection of Use Data · Ability to convert Use Data to a human readable form · Ability to not Identify User or Device associated with Use Data · Ability to Represent a wide range of Content Uses e.g. time of Use, combinations of Content Items, Domains, Superdistribution Uses
Benefits	Provide a machine-processable record of Uses

1.5.1.22 Represent Value Chains

	Detailed description of Requirements
Definition	The syntax of the information used to describe Value Chains
Objective	To digitally represent Value Chains
Requirements	· Ability to represent the actions of the Users · Ability to represent the relationships of the Users
Benefits	To enable the unambiguous replication of Value Chains

1.5.1.23 Represent Resource Format

	Detailed description of Requirements
Definition	The syntax of the information used to describe the format of Resources so that it can be Processed by a Device
Objective	To provide the means to Access Content containing suitable Resources for the Device
Requirements	· The ability to express relevant parameters in a Resource format o Compression algorithm used o Video resolution o Bitrate used for encoding o Audio sampling frequency o Number of channels o Etc.
Benefits	To facilitate Access to Content To be able to Access Content that is suitable for the Device

1.5.1.24 Represent Binarised XML

	Detailed description of Requirements
Definition	The efficient Representation of XML data
Objective	To save memory, transmission and processing capabilities when handling XML documents
Requirements	· To reduce the amount of information required to express an XML structure to a minimum · To allow for a lossless conversion between an XML structure its binary representation and the reconverted XML structure · To make processing of a binarised XML structure at least as easy to process as the original XML structure
Benefits	Better use of computing and transmission resources

1.5.2 Identify

1.5.2.1 Identify Content

	Detailed description of Requirements
Definition	The Function resulting from a request by a User and the consequent Assignment of an Identifier to Content Entities
Objective	To associate data, e.g. a number, to Entities in a unique and unambiguous fashion
Requirements	To Assign Identifiers according to the rules laid down by the Registration Authority as implemented by the Registration Agency so that there exists a unique, unambiguous, persistent and trusted correspondence between the Identifier and the Entity it Identifies · The Registration Agency shall provide unique Identifiers · The Registration Agency shall Assign the Identifiers unambiguously · The Registration Agency shall be able to Authenticate a Content Item without the need to Access the entire Content Item
Benefits	Form trusted relationships (i.e. Authenticate) by providing Users with the ability to Identify Content Entities

1.5.2.2 Identify IP Class

	Detailed description of Requirements
Definition	The Function by which a User Assigns an IP Class to a Content Item
Objective	To enable Recognition of the Content Item
Requirements	· There must be a determined set of IP Classes
Benefits	There are more possibilities to Use Content Items

1.5.2.3 Identify Metadata

	Detailed description of Requirements
Definition	The Function performed by a User when describing Entities within a DCI
Objective	To facilitate search for and Use of Content Entities
Requirements	· Ability to support the need of different Users to Assign Metadata that have mandatory descriptive fields, e.g.: o Author o Title o Genre of Authorship o Date of Creation of Work o … · Ability to facilitate cataloguing of Content for distribution to professional Users
Benefits	Secondary means to identify Entities

1.5.2.4 Identify Device

	Detailed description of Requirements
Definition	The Function resulting from a request by a User and the consequent Assignment of an Identifier to Devices
Objective	To enable Device Authentication
Requirements	To Assign Identifiers according to the rules laid down by the Registration Authority as implemented by the Registration Agency so that there exists a unique, unambiguous, persistent and trusted correspondence between the Identifier and the Device it Identifies · The Registration Agency shall provide unique Identifiers · The Registration Agency shall Assign the Identifiers unambiguously
Benefits	Form trusted relationships (i.e. Authenticate) by providing Users with the ability to Identify Devices

1.5.2.5 Identify Domain

	Detailed description of Requirements
Definition	The Function resulting from a request by a User and the consequent Assignment of an Identifier to Domain
Objective	To enable Identification of a Domain so that Content can be Licensed to it
Requirements	· The Registration Agency shall provide unique Identifiers, at least for the Domain life cycle · The Registration Agency shall Assign the Identifiers unambiguously
Benefits	Content can be Licensed to Domains

1.5.2.6 Identify Role

	Detailed description of Requirements
Definition	The Function by which a User is Assigned a Role
Objective	To enable Recognition of a Role
Requirements	· There must be a determined set of Roles
Benefits	It is possible to simplify licensing

1.5.2.7 Identify User

(Currently outside of DMP)

	Detailed description of Requirements
Definition
Objective
Requirements	·
Benefits

1.5.3 Recognize

1.5.3.1 Recognize Items

	Detailed description of Requirements
Definition	The Function that matches a given Content Item with corresponding IP Entities in the RRD
Objective	To classify Content Items with the IP that they represent
Requirements	· The ability to interface with the RRD
Benefits	Users have the means to recognize the full set of Conditions for any Role required to interact with a given Content Item

1.5.3.2 Recognize Roles

	Detailed description of Requirements
Definition	The Function that matches the Role Assigned to a User with a corresponding Role in the RRD
Objective	To classify a User’s Role with a given Content Item in terms of the RRD
Requirements	· The ability to interface with the RRD
Benefits	Users have the means to recognize the full set of Conditions for any Role required to interact with a given Content Item

1.5.4 Revoke

1.5.4.1 Revoke Content

	Detailed description of Requirements
Definition	The Function by which a User ceases to recognise a Content Item
Objective	To prevent the further Use of a Content Item
Requirements	· Content must be Identified
Benefits	To discontinue Use of a Content Item, e.g. when the Content Item has been found unsuitable for distribution

1.5.4.2 Revoke Content Element

	Detailed description of Requirements
Definition	The Function by which a User ceases to recognise a Content Element
Objective	To prevent the further Use of a Content Element
Requirements	· Content Element must be Identified
Benefits	To discontinue Use of a Content Element, e.g. when the Content Element is faulty

1.5.4.3 Revoke Device

	Detailed description of Requirements
Definition	The Function by which a User ceases to recognise a device as a Device
Objective	To prevent the further Use of the Device
Requirements	· Device must be Identified
Benefits	To discontinue Use of a Device, e.g. when the Device has been compromised

1.5.4.4 Revoke Domain

	Detailed description of Requirements
Definition	The Function by which a Domain Manager ceases to recognise a Domain
Objective	To prevent the further operation of the Domain
Requirements	· Domain must be Identified · Devices or Users belonging to the Domain must be Identified
Benefits	To discontinue operation of a Domain, e.g. the Devices have been compromised

1.5.4.5 Revoke User

	Detailed description of Requirements
Definition	The Function by which a User ceases to recognise a device as a User
Objective	To prevent the further Use of Devices or Content by a User
Requirements	· User must be Identified
Benefits	To discontinue Use of Devices by a User, e.g. when the device representing the User has been compromised

1.5.5 Authenticate

1.5.5.1 Authenticate Content

	Detailed description of Requirements
Definition	The Function of proving the identity of a Content Item to a Device
Objective	To make sure that a Device Accesses the intended Content Item
Requirements	· Content must be Identified · Content must be Signed or Hashed · Ability to compare a given Content Item with the Registered Content Item · Ability to compare the hash of a given Content Item with the Registered hash and ID of the Content Item
Benefits	To enable a Device to Use the intended Content

1.5.5.2 Authenticate Device

	Detailed description of Requirements
Definition	The Function of proving the identity of a Device to another Device a User or Domain. E.g. · A LPD Authenticates a DMD
Objective	To make sure that Content is Used by the intended Device
Requirements	· Device must be Identified · Ability to support different levels of Authentication
Benefits	To enable Content Uses on identified Devices

1.5.5.3 Authenticate DRM Tool

	Detailed description of Requirements
Definition	The Function of proving the identity of a DRM Tool to a Device
Objective	To make sure that the Content is processed by the intended DRM Tool
Requirements	· DRM Tool must be Identified
Benefits	Correct handling of Content Management and Protection

The Digital Media Project

Table of Contents

1 Value Chain Functions and Requirements