The Digital Media Project  

• identify a piece of
  • Content Data
  • Content Data Element
  • Use Data
• refer to the identification.

• identify
  • Work and its constituent parts
• refer to the Work identification.

• identify
  • Work and its constituent parts
• refer to the Work identification.

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.

• Unambiguous identification of a Work
• Unambiguous identification of a Work Use License and Data

• Identify Work within an organisation (#3 in PAV?)
• Avoid duplication of Work Identifiers over time (#4 in PAV?)

• Unambiguous identification of a Work and its parts

• 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.

• Content should be identified by different VCUs to enable tracing the origin of content when licensed to other VCUs

• 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.

• Permit tracking of a Work throughout copy generations and variations.

• 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

• 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.

• The following types of Domain shall be supported
  • Device-based
  • User-based
  • By enumeration
  • By reference to a legally established class of special users
  • Location-based

• Hierarchy of Domains shall be supported

To enable

• Content Access and Use of Content and Services
• Payment systems to operate

• Being usable for the purpose of User authentication
• Ability to accommodate a variety of models for human interaction with Devices e.g.:
  • Allow a single User to use multiple Devices,
  • Allow multiple Users to share a single Device,
  • 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.

• Supports identification of identity of user to which content was licensed

• Works
• Users
• Devices
• Platforms
• Etc.

• To support the association of a piece of Governed Content with a Device
• To support Trust management

• To support the association of the Use of a Work with a Device

• 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.

• Ability to obtain Device capability information from the Device Identifier
• Playback of a set of books can be restricted to a specific set of machines (devices). (requires clarification by proponent)

• 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.

• How to identify Content formats

• Relevant parameters in a content format
  • Compression algorithm used
  • Video resolution
  • Bitrate used for encoding
  • Audio sampling frequency
  • Number of channels
  • Key management
  • Encryption methos
  • Watermarking
  • Etc.

• 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

• To support Rights "packaging"

• 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

• To identify Device capabilities, e.g.
  • capability to process (e.g. Render) certain Resource types;
  • capability to process certain Content formats
  • capability to process certain Rights Expressions
  • etc.

• Verify origin of Work for which Identifier is requested
• Verify that the requester qualifies as Author of Work

• Verify that the requester represents a qualified Author of Work (agency)

• Form trusted relationships and give all Users confidence in the Work, Resource or Device.
• Verify that any entity that can be identified is justly and correctly identified.

• To include the following mandatory fields
  • Author
  • Title
  • Genre of Authorship
  • Date of Creation of Work …

• Persistent Association of Identifiers and Metadata to Resources
• Ability to include encrypted and unencrypted Data
• Ability to apply Rights Expressions to Composite Content components
• Ability to Use Content Data Elements from Governed Content
• Ability to associate Composite Content Elements stored at locations remote from each other
• Ability to support association of Composite Content Elements
• Ability to support Element unavailability, both temporary and permanent.

• Standard format for Work-related information

• Compatibility of Resource Descriptors with existing standards
• Organize and associate (i.e. multiplex) Rights Expressions and Content for carriage in broadcast and streaming
• Efficient communication of Rights Expressions
• An End-User should not have to wait for a long time before Using Content
• Organize and associate (i.e. multiplex) Metadata and Content for carriage in broadcast and streaming
• Efficient communication of Metadata
• An End-User should not have to wait for a long time before Using Metadata

• Content shall be represented in a Delivery-System agnostic format

• Different Uses of the same Content (e.g. Resource selection)
• Executing sets of Functions on Content that serve for orientation, navigation and judgement (e.g. searching/filtering content)

• License Different Uses of the same Work  (e.g. Work based Resource selection)
• Ability to apply Work based Author and CMS issued Rights Expressions and Licenses to Composite Content components containing various types of Works/Resources (Audio, Video, Graphic etc.).
• Ability to find out which Works are employed in a piece of Content

• Ability to identify Use Data
• Ability to support protection of Use Data
• Ability to convert Use Data to a human readable form
• Ability to represent a wide range of Content Uses e.g. time of Use, Composite Content, Domains, Superdistribution Uses

• Ability to identify Use Data pertaining to a Work
• Ability to support protection of Work Use Data
• Ability to represent a wide range of Work Uses e.g. time of Use, Composite Content, Domains, Super-distribution Uses

• The Solution shall represent different subsets of Rights
• The Solution shall represent new Rights when the need occurs
•  The Solution shall unambiguously identify
  • the User granting the Right
  • the User, Device or Domains obtaining the Right
  • the piece(s) of Content to which the Rights Expression refers
  •  the Right that is granted in such a way that there is no ambiguity in the semantics of the Rights Expression
• The Solution shall support the following Functions:
  • Copy
  • Move
  • Backup/Restore
  • Export
  • Import
  • Transfer to an external rendering device
•  The Rights Expression shall support at least the following:
  • To assign one Rights Expression to many pieces of Governed Content
  • To assign many Rights Expressions each referring to a different component of a Composite Content
• In particular a piece of Content can have no Rights Expression (to be checked whether it should be a “do everything” type of Rights Expression)
• To specify Content Uses e.g.
  • Period of time (e.g. play as long as the play time is less than a specified period) and based on time/date
  • User identity-based
  • Count based (play up to the specified number of time)
• To specify Resource Uses e.g.
  • Audio
  • Video
  • Executables (e.g. applet)
•  To allow streaming
•  To process metadata
• Presentation of Metadata
•  To allow trick modes

• The solution shall represent varying subsets of Author/CMS Rights
• The Solution shall unambiguously identify
  • the Work(s) to which the Rights Expression refers
  • the Right in the context of a given License or Licenses
• The Solution shall support the following Functions:
  • Edit
  • Adapt
  • Associate (e.g. we may want to maintain an association between audio and video)
  • Stream
  • Download
• Digital Rights Expressions shall support at least the following:
  • To assign Rights Expressions to Works
  • To assign one Rights Expression to many Works and/or pieces of Governed Content
  • To assign Rights Expressions with Context Use limitations, e.g. age of End-User
  • To assign many Rights Expressions each referring to a component of a Composite Content containing any combination of Works
  • To resolve conflicts between Rights Expressions for Work Use and Rights Expressions for Governed Content Use in which the Works are contained
  • To specify Work Uses e.g.
    • Period of time (e.g. play as long as the play time is less than a specified period) and based on time/date
    • User identity-based
    • Count based (play up to the specified number of time)

• The Solution shall support the following Functions:
  • Store
• Rights Expression should enable
  • Store received Content
  • Move/Copy within Authorised Domain
  • Move/Copy within Footprint (e.g. applications may be required to determine the geographic region in which the device running the application is found, parcticularly when on-line)
  • Export to a movable media
  • Signal no Copy/Move outside Footprint
  • Inhibit Encryption of cleartext Content
• Rights Expressions should be able to make reference to a Footprint (already supported by “Identify Domain”)
• Rights Expressions should
  • Not require a return channel
  • Have low payload
  • Be processable by a wide array of Device sophistication

• Rights Expressions should support
  • Conditional expiry (i.e. SMP loses Rights to sheet music if Stored for longer than determined period without Use)
  • Multiple grantors of the same Work
  • Rights to segments of Work and Content

• Rights Expressions should support Quote

• Rights Expressions shall support
  • Use of Content Stored in a Device-based Domain by the User of that Domain through a Device that does not belong to that Domain
  • Store
  • Time-shifted Use

• Rights Expressions shall support
• Use of Governed Content within geographical domains

• Rights Expressions shall support Rights restrictions when Exporting

• Rights Expression shall support Device-based Licenses

• Rights Expression shall support conversion between different resource encoding (e.g. MP3 to AAC)

• Rights Expression shall support annotate / modify content for personal use

• The Rights Expression shall support at least the following types of media: audio, video, images, text and executables, group/bundles thereof and composite content thereof

• The Rights Expression shall support the addition of new metadata

• The Rights Expression shall support the expression of time within which content can be Accessed

• The Rights Expression shall support Access of Content based on User identity and Rating (e.g. suitability for age)

• The Rights Expression shall support a User acquiring a License for another User

BT

• Shall support multiple protocols for the authentication of Users

• Certificates must be removable by the user, e.g for the purpose of services the device

• Supports national and international interlibrary loan (requires clarification by proponent)

• Playback of a set of books can be restricted to a specific set of users. (is on a book-by-book basis not enough?)

DC

• Protocol for the authentication of the Device

• Correct delivery of Content, Use Data and Executables.

• Correct delivery of a Work
• Guarantee that correct Work and Author are associated within content.

• Ability to detect that there is corruption or loss of part of the Content, Use Data and Executables
• Support error recovery in the case where Content, Use Data and Executables are delivered over an imperfect Delivery System.
• Compatibility with data protection and privacy aspects (e.g. to limit the compilation of user profiles by third parties)

• Ability to cross-reference Work and Author identification with license data (this is a question of verifying Metadata Intergrity)

• Detect miss-match of Content or Content Data and their associated Identifiers.

• Ability to detect that there is corruption of the Device software

• A protocol to certify Content in reference to a Work

• A mechanism to certify Users

• A protocol to certify Authors

• A mechanism to certify Devices

• To support multiple key exchange protocols without loss of interoperability
  • One key to one or to many piece(s) of Governed Content
  • One key to one or to many Users
  • One key to one or to many Devices
• To support identification of authorised key management systems
• Technology to protect keys
• For any pieces of Content used within Composite Content, it shall be possible to choose not to encrypt that piece of Content and it shall also be possible to encrypt that piece of Content using individual keys.
• The ability to support superdistribution of Governed Content when each instance of such Governed Content is encrypted with a different key.
• The Solution should lend itself easily to key management implementations that do not interfere with an enjoyable User experience.
• Key management solutions should not be completely destroyed by a single failure and if defeated, should have adequate recovery plans in place to restore key management security.

• Setting up a Domain, including the ability to distribute Rights Expressions that can only be used by Devices in the Domain
• Joining a Domain
• Authorising entry to a Domain
• Leaving a Domain
• Directing to leave a Domain, including the ability to exclude a Device so that it cannot process Rights Expressions associated with the Domain after the time of exclusion
• Users with an authorised entitlement shall be able to fully control Domain membership and Content distribution.
• Users without an authorised entitlement shall not be able to obtain confidential information related to the Domain
• A Domain shall be configurable to permit a variety of distribution options between Devices belonging to the Domain, e.g. superdistribution of Content and Composite Content to Devices belonging to a sub-Domain within the Domain (e.g., specialized interest groups).

• Protocol to ascertain that a device is a Device
• Protocol to determine the Device’s Rights Expression interpretation capabilities
• Protocol to determine the Device’s Use capabilities
• A Device shall be able to identify another Device before distributing (or refusing to distribute) Content or Rights Expressions to that Device, however configurations for anonymity and/or confidentiality should be optional
• Content shall include relevant Metadata identifying the characteristics of that Content and the Device capabilities required to process that Content
• A Device shall be able to request and receive information identifying relevant capabilites of another Device before distributing (or refusing to distribute) requested Content or its associated Rights Expression to that Device
• A Device shall be able to request and receive information identifying characteristics of Content before receiving (or refusing to receive) the Content or its Rights Expression
• If a Device has received Content, the Device shall be able to determine whether it is able to process the Content before requesting the Rights Expression associated with it; the same shall apply if a Device has received the Rights Expression but has not received the Content
• The solution shall provide sufficient flexibility to respect Users' wishes for anonymous use and confidentiality of information not necessary for the purpose of discovery of Device capabilities.

• Mechanism for protection of Use Data
• Ability to decide the utilisation of Use Data

• Use of broadcast Governed Content in a Footprint must support Use Privacy

• Navigation aids can be downloaded and executed on a Common Open API

• Access to authenticated Work and Author Descriptors

• Access Content via multicast

• It shall be possible to make Access License Transparent to User

• Suitably flexible for a wide variety of Content Data
• Efficiently implementable on a wide range of Devices
• Based on Encryption Algorithms that are:
  • publicly disclosed
  • subject to constant scrutiny and evaluation by the worldwide cryptographic community
  • supporting stream and bulk ciphers
  • considered as secure
  • in broad use
• The appropriate consideration of export restrictions.

• Content may be governed but resources may not ne encrypted
• Scalable encryption methods  (requires clarification by proponent)
• Support
  • Facilitate efficient prefetch and decryption of child resources.
  • Efficient random access to content blocks for all linear content types.
• Must not require player to extract content from aggregated files. (requires clarification by proponent)

• A protocol to communicate with another Device to accomplish the function required by the definitions of Copy/Move, including the point-to-multipoint case
• The protocol should lend itself to secure implementations
• The protocol should lend itself to efficient implementations on a wide variety of devices.

To be able to make room for Governed Content in a Device without losing permanently the Governed Content that is removed from the Device.

• A protocol to communicate with a non-DMP DRM system. This includes, as a minimum, a means to identify non-DMP DRM systems

A Rights Holder has the ability to extend the range of use of their Content to other governed environments.

• A protocol to communicate with a non-DMP DRM system. This includes, as a minimum, a means to identify non-DMP DRM systems  

Enables Environments to be populated with governed content from sources outside of DMP.

• Time-shifted Play should be supported
• Immediacy of Playing Content (without the need of complex username/password)

• Governed content should be playable without negative effects on player performance. Media quality, etc.

• Implementable in open-source players. (requires clarification by proponent)

• Required features must be implementable on all current DTB reading systems. (make explicit which are the features of the current DTB reading systems for support in DMP)

• Must allow rendering compatible with existing assistive technologies (screen readers, refreshable braille displays). (make explicit which are the existing assistive technologies for support in DMP

• Can't ""hide"" text from other applications (e.g., screen-readers).

• Players must inform the user of authorization failures

• Protected books must fail gracefully when played in a legacy player

DC

• A protocol to communicate with the external rendering device. This includes
  • a means to identify external rendering devices
• Ability to work with standards already in place or in development for the networked home.

• License must be disclosed to human user in a usable form (education about rights, restrictions, penalties).
• Content should be rendered without markup.

• The ability to Associate Persistently Work related information to all copies of Content containing that Work and all child copies and variations thereof that retain the Work and/or variation.

In the case of persistent association the ability to Distribute Data that are tightly bound to other Data

• The ability to support multiple payment methods and mechanisms

#  

Value-chain User

Acr.

Definition

1.       

Author

AUT

A User who creates Works

2.       

Performer

PRF

A User who Uses Works to make Content

3.       

Collective Management Society

CMS

A User who provides collective representation to its member, e.g. Authors, Performers, Publishers etc.

4.       

Producer

PRD

A User who produces Content

5.       

Publisher

PBL

A User who makes Content available to the public

6.       

Syndicator

SND

A User who manages and provides Content to Retailers using a variety of  purchase options

7.       

Metadata Service provider

MTP

A User who recognises, assigns, delivers and processes structured metadata

8.       

Mediation Service provider

MDP

A User who provides mediator/agent Services to broker “closed” information such as actor identity

9.       

Resolution Service provider

RSP

A User who provides the Service of mapping disparate sets of Metadata

10.   

Repository

RPS

A User who offers Services to name, describe, locate, access, manage, and secure information about Content

11.   

Monitoring Service provider

MNP

A User who provides Use Data information in aggregated form

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, indexing and promoting Services typically to Retailers

14.   

Retailer

RTL

A User who sells or Licenses Content to an End-user

15.   

Technology licensing provider

TLP

A User who provides Device Manufacturers and Platform providers with a license to utilise patented technology to make Devices and Platforms

16.   

Device Manufacturer

DVM

A User who manufactures or assembles hardware and/or software components to make Devices

17.   

Connectivity provider

CNP

A User who provides point-to-point or point-to-multipoint connectivity between Users

18.   

Network Service provider

NTP

A User who provides IP (or equivalent) services and typically various other services above it, e.g. guarantee of quality of service

19.   

Platform Service provider

PLP

A User who provides services on (parts of) the technology infrastructure of a Value-chain

20.   

Security provider

SCP

A User who provides technologies and services related to the security technologies and all levels of relevant computer and network security solutions

21.   

Certificate Authority

CRA

A User who issues digital certificates used to create digital signatures and public-private key pair

22.   

Conformance certification provider

CCP

A User who provides conformance, robustness and encoding rules along with certification of satisfying same.

23.   

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

24.   

Financial Service provider

FSP

A User who provides the infrastructure for financial transactions, and accept deposits and channel the money into lending activities

25.   

End-user

ENU

The last User in a Value-chain

26.   

Reseller

27.   

Public Authority

PBA

A User who provides rules relating to the Use of Content and taxation on transactions related to Content.