Report on Reuters Response to MPEG-21 CfR
This presentation is the property of its rightful owner.
Sponsored Links
1 / 19

David Parrott Reuters/ Chief Technology Office 18 July 2001 PowerPoint PPT Presentation


  • 124 Views
  • Uploaded on
  • Presentation posted in: General

Report on Reuters Response to MPEG-21 CfR Report to XACML Committee Face-to-Face Meeting. David Parrott Reuters/ Chief Technology Office 18 July 2001.

Download Presentation

David Parrott Reuters/ Chief Technology Office 18 July 2001

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


David parrott reuters chief technology office 18 july 2001

Report on Reuters Response to MPEG-21 CfRReport to XACML Committee Face-to-Face Meeting

David Parrott

Reuters/Chief Technology Office18July 2001

This presentation is a report of a meeting between Dr David Parrott of the Reuters Chief Technology Office and the XACML Committee which took place on 18 July 2001. The contents of this presentation relate to a fuller paper submitted as Reuters response to the MPEG-21 call for requirements (ISO/IEC JTC1/SC29/WG11 N4044: "Reissue of the Call for Requirements for a Rights Data Dictionary and a Rights Expression Language" dated March 2001) on 1 June 2001. The full MPEG submission contains greater detail of the issues, and the context in which the statements contained in the presentation are made. The full response submitted by Reuters on 1 June 2001 can be found at http://www.oasis-open.org/committees/xacml/docs/response-v1.0-public.doc. This presentation and the statements contained within it do not necessarily reflect Reuters current or future policy, position or plans in relation to the topics discussed, nor does it purport to cover all the relevant topics in this area. Reuters accepts no responsibility for the consequences of any reliance placed on the contents of this presentation.


David parrott reuters chief technology office 18 july 2001

The Permissioning Problem

Reuters Today

  • Private networks give tight access control

  • Reuters client-site components allow fine-grained permissions

  • Control is reduced on satellite feeds

  • Many data types, all with different permissioning models and implementations

  • Heavyweight subscription contracts.


David parrott reuters chief technology office 18 july 2001

Digital Rights Management (DRM)

  • Managing:

    • Rights (IPRs, Permissions, Access Controls, Usage, etc)…

    • Obligations…

    • Audit trails…

    • … across the entire value chain (of IPR creators, publishers, distributors, consumers…)

  • Electronic, machine-readable contracts

  • In equal measures:

    • Legal Infrastructure

    • Business Infrastructure

    • Technology Infrastructure.


David parrott reuters chief technology office 18 july 2001

Many Approaches to DRM

  • Standardised Markup for Expressing Rights and Obligations

  • Detection of IPR Infringement

    • Watermarking

    • Fingerprinting/Traitor Tracing

    • Tracking/Searching

  • Rights and Obligations Enforcement

    • Permissioning and Access Control (encryption technologies if appropriate)

    • Licensing and contracts

    • Sandboxes (protected environments).


David parrott reuters chief technology office 18 july 2001

Why are we Interested in Digital Rights Management?

Reuters needs to permission its data and protect its IPR…

  • Data is inherently valuable

  • Unified approach across “Slice and dice” service offerings

  • Unified approach across flexible and varied distribution channels

    • e.g., proprietary networks, satellite broadcast, public Internet

  • Broadcast mode delivery is required in many cases for scalability

    • permissioning restricts access to just those parts paid for

  • Third party content comes with complex and exacting distribution rules

    • plus regulatory requirements

  • Data flows are multi-directional and include contribution rights.


David parrott reuters chief technology office 18 july 2001

DRM

Rules &

Consequences

Content

Encryption

What Digital Rights Management is NOT

(i) It is not just enforcement by locking up content in a layer of encryption

  • Restricted Actions:

  • View, Print, Save, …

  • No “fair use”

  • B2C dominated

  • Security/Trust Problems:

  • Software inherently unsafe

  • Trusted applications restrictive

  • Vulnerable to systematic attack

  • Proprietary Implementations:

  • Lacking interoperability

  • Closed user-base

  • Risk backing the wrong player


David parrott reuters chief technology office 18 july 2001

.

.

.

.

.

.

Service

Provision

Reuters

Channel

Partner

(Schwab)

Value

Add

Data feed

Processing

Real-Time

Customer

(Banks)

News feed

Customer

(Yahoo!)

Custom

Analytics

Auto

Trading

Risk

Mgmt

.

.

.

.

.

.

What Digital Rights Management is NOT

(ii) It is NOT the exclusive domain of “Eyes and Ears” B2C data delivery

Vs


David parrott reuters chief technology office 18 july 2001

T

R

U

S

T

T

R

U

S

T

Content, Permissions, Obligations, and Trust

Permissions

The most you can do with content

Obligations

The least you must do in order to gain access


David parrott reuters chief technology office 18 july 2001

MPEG-21

  • Content

    • Creation and Production

    • Distribution

    • Consumption and Usage

    • Packaging

    • Identification and Description

    • Representation

  • Intellectual Property Management and Protection

  • Financial Management

  • User Privacy

  • Resource Abstraction

  • Event Reporting


David parrott reuters chief technology office 18 july 2001

Rights Expressions Everywhere

Contributors

Reuters

Systems

And

Products

Distributors

Network

Service

Providers

Customers


David parrott reuters chief technology office 18 july 2001

Rules

Rules

Rules

“Straight-Through” Rules Processing

Contributors

Reuters

Systems

And

Products

Distributors

Network

Service

Providers

Customers

Rules


David parrott reuters chief technology office 18 july 2001

Relational

Database

Web

Access

E-commerce

Admin

(Directories)

Billing

Real-Time

Permissioning

Microsoft

Exchange

Unified Rules Definitions

Contributors

Reuters

Systems

And

Products

Distributors

Network

Service

Providers

Customers

Policies and Rules


Requirements f or rights data dictionary rights expression language

Requirements for Rights Data Dictionary & Rights Expression Language

3.1REQUIREMENTS FOR THE STRUCTURE OF THE STANDARD

3.1.1Division of the Standard into an Extensible Core and Standard Prelude

3.1.2Inclusivity


Requirements f or rights data dictionary rights expression language1

Requirements for Rights Data Dictionary & Rights Expression Language

3.2REQUIREMENTS FOR RIGHTS STRUCTURE AND MANAGEMENT

3.2.1The Relationships between Rights and Obligations

3.2.2Rights and Obligations Transfer (Inheritance)

3.2.3Rights and Content Independence

3.2.4The Types of Content over which Rights and Obligations Apply

3.2.5Matching Rights and Obligations to Digital Objects

3.2.6Matching Rights to Contexts

3.2.7Location, Form, and Access Control of Data Dictionaries

3.2.8Management of Issued Rights and Obligations

3.2.9Fail-Over and Behaviour Modification

3.2.10Privacy of Terms Expressed in the Language and Data Dictionary

3.2.11Expression Evaluation


Requirements f or rights data dictionary rights expression language2

Requirements for Rights Data Dictionary & Rights Expression Language

3.3REQUIREMENTS FOR RIGHTS AND OBLIGATIONS DEFINITIONS

3.3.1Operational Specifications

3.3.2Reporting

3.3.3Acknowledgement of Source

3.3.4Rights and Obligations for Real-Time Data

3.3.5Rights and Obligations for a Stream of Digital Objects

3.3.6Rights and Obligations for Transactional Data

3.3.7Rights and Obligations for Database or Server Access

3.3.8Usage Rights

3.3.9Managing Communities

3.3.10Contract Management

3.3.11Business Models


Requirements f or rights data dictionary rights expression language3

Requirements for Rights Data Dictionary & Rights Expression Language

3.4ATTRIBUTES ON WHICH RIGHTS AND OBLIGATIONS ARE PREDICATED

3.4.1Temporal

3.4.2Geographic

3.4.3Environmental


Requirements f or rights data dictionary rights expression language4

Requirements for Rights Data Dictionary & Rights Expression Language

3.5REQUIREMENTS PERTAINING TO TRUST

3.5.1Identification of Trusted Entities

3.5.2Trusted Time Services

3.5.3Trusted Applications and Environments

3.5.4Certifiable Audit Trails

3.5.5Agent Authentication

3.5.6Data Integrity

3.5.7Agent Mandated Privacy

3.5.8Confidentiality


Requirements f or rights data dictionary rights expression language5

Requirements for Rights Data Dictionary & Rights Expression Language

3.6ADDITIONAL FUNCTIONAL REQUIREMENTS

3.6.1Specialised Support for Business to Business (B2B) Commerce

3.6.2Machine Processing of Digital Objects


Requirements f or rights data dictionary rights expression language6

Requirements for Rights Data Dictionary & Rights Expression Language

4OTHER AREAS FOR CONSIDERATION IN BUILDING THE STANDARD

4.1CHANNEL DEFINITION

4.2OBJECT MODELS

4.3WORKFLOW


  • Login