|
The Digital Media Project |
|||
|
Source |
GA04 |
Date: |
2004/10/29 |
|
Title |
Interoperable DRM Platform Functions and Requirements |
No. |
0239/Barcelona |
Interoperable DRM Platform Functions and Requirements
The Digital Media Project (DMP) is a not-for-profit organisation with the mission to “promote continuing 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 various value-chain players to provide products and services, according to the principles laid down in the Digital Media Manifesto”.
DMP has identified “Interoperable Digital Rights Management (DRM)” as the technology whose deployment can further the goals stated in its Mission and has developed a work plan whose current version foresees, inter alia, the development and publication of:
1. Technical Specifications for Portable Audio and Video (PAV) Devices in April 2005
2. Technical Specifications for Interoperable DRM Platform (IDP) and Interoperable End-user Devices (IED) in October 2005
3. Recommended Practices for End-to-End Conformance (EEC) in July 2006.
In July 2004 the DMP issued a Call for Proposals (CfP) on “Portable Audio and Video (PAV) Devices”, relevant to point 1. above. It is planning to issue another CfP for both “Interoperable DRM Platform (IDP)” and “Interoperable End-User Devices (IED)” relevant to point 2. above. The latter specifications will extend the functionalities of the PAV specification.
As done for the PAV CfP, the IDP/IED CfP will make reference to “IDP/IED Requirements”. The DMP is currently busy collecting said requirements from a variety of sources. So far requirements from representatives of the following Value-Chain Users have been contributed:
1. Collective Management Societies
2. Producers
3. Public Service Broadcasters
4. Sheet Music Publishers
5. Device Manufacturers in the development of PAV requirements.
A list of Value-Chain Users identified so far DMP, and whose requirements the DMP expects to include is given in Annex A.
This document contains in an organised fashion the IDP/IED requirements as developed so far. It is based on the PAV requirements document but new information submitted by some Value-Chain Users representing their requirements (so far DMP0171, DMP0169 and DMP0175 in addition to those already received for the PAV CfP) has been added. Value-Chain Users are encouraged to provide additional requirements that satisfy their needs or to comment on the existing ones. They will be incorporated in this document after review by DMP. Contributors will have ample opportunity to review the document before final publication as an attachment to the IDP/IED CfP.
An effort has been made to apportion the requirements provided by an organisation to different Value-Chain Users when that organisation clearly represents more than one Value-Chain User.
This document is made public for the purpose of offering an opportunity to concerned entities to express their requirements and to comment on the requirements collected and organised so far. Currently the document is planned for final publication on 2004/10/29 and therefore represents work in progress.
This document should be read bearing in mind that words beginning with a capital letter have the meaning specified in the DMP Terminology. Please note that this document, too, is work in progress.
Readers should note that the right column of each of the tables below contains a reference to the source of the entry:
|
Acronym |
Name |
|
CMS |
Collective Management Societies |
|
PRD |
Producers |
|
PBB |
Public Service Broadcasters |
|
SMP |
Sheet Music Publishers |
|
PAV |
Portable Audio and Video Device Requirements |
|
AHG3 |
Ad hoc group established by DMP General Assembly |
The requirements below should be read bearing in mind the following general requirements (the list below is work in progress):
1. 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. E.g. a Producer Using a Work to produce a piece of Content can only grant a conditional subset of those Rights to that Content that have been granted him by the Author of said Work
2. DMP specifications aim at a unique form for Resources, Metadata, Rights Expressions and Licenses that is agnostic of Delivery Systems.
3. DMP specifications do not aim to support specific business models to the detriment of other business models
4. DMP aims at developing “tool-kit” specifications, i.e. Users wishing to set up Value-Chains supporting specific business models will have the possibility to do so in a scalable way and retaining interoperability with other Value-Chains.
Those wishing to comment on or contribute requirements to this document should forward their submissions to Marc Gauvin (mgauvin@sdae.net). Submissions will be discussed by the Ad hoc Group on Requirements for Interoperable DRM Platform (IDP) and Interoperable End-user Devices (IED). To subscribe to the ad hoc group reflector follow the instructions.
Ed. Comment Need to add a section dedicated to interoperability ETRI.
Table of Contents
|
Category |
Function |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Represent Resources |
|
|
Represent Metadata |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Authenticate Domain |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Access |
|
|
|
License |
|
|
Content |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Detailed description of Requirements |
Source |
|
Definition |
The means to uniquely and unambiguosly · identify a piece of o Content Data o Content Data Element o Use Data · refer to the identification. |
PAV |
|
|
The means to uniquely and unambiguously · identify o Work · refer to the Work identification. |
CMS |
|
|
The means to uniquely and unambiguously · identify o Work and its constituent parts · refer to the Work identification. |
SMP |
|
Objective |
To support the association of Resources, Metadata, Rights Expressions, Licences and/or Use Data with a piece of Data that may be remote from such Resources, Metadata, Rights Expressions, Licenses and/or Function that generated the Use Data. |
PAV |
|
|
To support the association of Work, Resources, Metadata, Rights Expressions, Licences and/or Use Data with a piece of Data that may be remote from such Work, Resources, Metadata, Rights Expressions, Licenses and/or Function that generated the Use Data. |
CMS |
|
|
To support the Use of a Work and/or its parts |
SMP |
|
Requirements |
1. Unambiguous identification of a piece of Content Data and Content Data Element 2. Unambiguous identification of Use Data 3. Ability to work in conjunction with multiple, existing industry schemes for Content Data identification. 4. Ability to extend the total number of identifiers that can be assigned in such a manner that previously assigned identifiers do not become obsolete. |
PAV |
|
|
· Unambiguous identification of a Work · Unambiguous identification of a Work Use License and Data |
CMS |
|
|
· Identify Work within an organisation (#3 in PAV?) · Avoid duplication of Work Identifiers over time (#4 in PAV?) |
PBB (PRD) |
|
|
· Unambiguous identification of a Work and its parts |
SMP |
|
|
Answer to Sony queries. In the PAV Requirements we refer to Content Identification required for particular PAV implementations and not all identification schemes. But at the IDP level we include any standard identification scheme provided by VCUs. |
DVM |
|
Benefits |
· Flexible distribution schemes where different Content Data Elements may be supplied from different sources. · A given Content Data Element may be referenced by a multiplicity of Composing Content without duplication. · Fine granularity of Rights Expressions. |
PAV |
|
|
· Permit tracking of a Work throughout copy generations and variations. |
CMS |
Identify License
|
Definition |
The means to identify the appropriate License of Work contained in Governed Content in a particular instance of Use |
CMS |
|
Objective |
· To support the association of the use of a Work (e.g. Use Context) within a piece of Governed Content with the appropriate License or License identifier · To support Trust Management |
CMS |
|
Requirements |
· Compatible with administration of Domains for Work Use, i.e. that a Work can only be Used in a specific Domain (e.g. a Broadcast Footprint, a company) · Ability to associate a given set of Rights Expressions with the appropriate License and Use Context · Ability to work in conjunction with existing industry schemes to deliver specific Licensed 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. |
CMS |
|
Benefits |
Guarantee appropriate Licensed Uses of Works |
CMS |
|
|
|
DMV |
|
Definition |
The means to identify Use domains |
AHG3 |
|
Objective |
To identify groupings of Users and/or Devices. For the time being only End-Users are considered |
AHG3 |
|
Requirements |
· The following types of Domain shall be supported o Device-based o User-based o Location-based |
AHG3 |
|
|
· Hierarchy of Domains shall be supported |
PM |
|
Benefits |
Enable more Uses of Content by identifying groupings of Users and/or Devices instead of just Users or Devices |
AHG3 |
|
Definition |
The means to identify the device that represents the (human, corporate etc.) User in a particular instance of Use |
PAV |
|
Objective |
To enable · Content Access and Use of Content and Services · Payment systems to operate |
PAV |
|
Requirements |
· Being usable for the purpose of User authentication · 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, · Ability to extend the total number of identifiers that can be assigned in such a manner that previously assigned identifiers do not become obsolete. |
PAV |
|
Benefits |
Depending on a given device's design, allows one User to employ multiple devices or allows multiple Users to use a single device. Useful in the event of disaster recovery scenarios when a device or storage medium is destroyed |
PAV |
|
Definition |
The means to identify the Device employed in a particular instance of Use |
PAV |
|
Objective |
· To support the association of a piece of Governed Content with a Device · To support Trust management |
PAV |
|
|
· To support the association of the Use of a Work with a Device |
CMS |
|
Requirements |
· Compatible with administration of Domain models for Use. · 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. |
PAV |
|
Benefits |
· Allows reliable administration of Device-based Uses. · Compatible with succession 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. |
PAV |
|
Definition |
Identification of Content formats |
PAV |
|
Objective |
To provide the means to identify Content formats |
PAV |
|
Requirements |
· How to identify Content formats |
PAV |
|
|
· Relevant parameters in a content format o Compression algorithm used o Video resolution o Bitrate used for encoding o Audio sampling frequency o Number of channels o Etc. |
AHG3 |
|
Benefits |
The ability to acquire Content that is suitable for the Device |
PAV |
|
|
The ability to acquire a Work that is suitable for the Device as per Rights Expressions and Licenses issued by Authors and CMSs |
CMS |
|
Definition |
The means to identify that the Context of Use of a Work is in accord with License stipulated by the Author/CMS and according to the Author’s moral rights. These limits would relate to identifiable associations of a Work with the presence of another Work, Logo, Name (i.e. names of commercial entity, political or religious entities), Domains, IP or geographic region etc. Example is content released under a “free use” License that shall not be used for political purposes |
CMS |
|
Objective |
· To support associating a Work or only associating a Work with an identifiable pre-determined Context or Contexts in accord with the intended limits of associating a Work as stipulated by the Author · To support Trust management |
CMS |
|
|
· To support Rights "packaging" |
PM |
|
Requirements |
· Compatible with administration of Domain for Work Use. · Ability to work in conjunction with existing industry schemes to administer specific Work Uses. · Ability to identify other Works and objects associated within an identifiable digital unit such as a Web object or Digital Item |
CMS |
|
Benefits |
Allows reliable administration of intended Work Uses |
CMS |
|
Definition |
Identification of capabilities of a Device to handle Data or perform Functions |
PAV |
|
Objective |
To provide the means to identify the functionality of a Device |
PAV |
|
Requirements |
· To identify Device capabilities, e.g. o capability to process (e.g. Render) certain Resource types; o capability to process certain Content formats o capability to process certain Rights Expressions o etc. |
AHG3 |
|
Benefits |
The ability to acquire Content that is suitable for the Device |
PAV |
|
|
The ability to acquire a Work that is suitable for the Device as per Rights Expressions and Licenses |
CMS |