Presentation is loading. Please wait.

Presentation is loading. Please wait.

R EUTERS 150 Y EARS David Parrott Reuters/Chief Technology Office 18 July 2001 Report on Reuters Response to MPEG-21 CfR Report to XACML Committee Face-to-Face.

Similar presentations


Presentation on theme: "R EUTERS 150 Y EARS David Parrott Reuters/Chief Technology Office 18 July 2001 Report on Reuters Response to MPEG-21 CfR Report to XACML Committee Face-to-Face."— Presentation transcript:

1 R EUTERS 150 Y EARS David Parrott Reuters/Chief Technology Office 18 July 2001 Report on Reuters Response to MPEG-21 CfR Report to XACML Committee Face-to-Face Meeting 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.http://www.oasis-open.org/committees/xacml/docs/response- v1.0-public.doc

2 R EUTERS 150 Y EARS 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. The Permissioning Problem Reuters Today

3 R EUTERS 150 Y EARS 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.

4 R EUTERS 150 Y EARS 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). Many Approaches to DRM

5 R EUTERS 150 Y EARS 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.

6 R EUTERS 150 Y EARS What Digital Rights Management is NOT DRM Encryption Content Rules & Consequences Security/Trust Problems: Software inherently unsafe Trusted applications restrictive Vulnerable to systematic attack Restricted Actions: View, Print, Save, … No “fair use” B2C dominated Proprietary Implementations: Lacking interoperability Closed user-base Risk backing the wrong player (i) It is not just enforcement by locking up content in a layer of encryption

7 R EUTERS 150 Y EARS What Digital Rights Management is NOT (ii) It is NOT the exclusive domain of “Eyes and Ears” B2C data delivery Vs Reuters Channel Partner (Schwab) News feed Customer (Yahoo!) Real-Time Customer (Banks) Custom Analytics Risk Mgmt Auto Trading Data feed Processing Service Provision Value Add........................

8 R EUTERS 150 Y EARS Content, Permissions, Obligations, and Trust Permissions The most you can do with content Obligations The least you must do in order to gain access TRUSTTRUST TRUSTTRUST

9 R EUTERS 150 Y EARS Intellectual Property Management and Protection Financial Management User Privacy Resource Abstraction Event Reporting Content –Creation and Production –Distribution –Consumption and Usage –Packaging –Identification and Description –Representation MPEG-21

10 R EUTERS 150 Y EARS ContributorsReuters Systems And Products DistributorsNetwork Service Providers Customers Rights Expressions Everywhere

11 R EUTERS 150 Y EARS ContributorsReuters Systems And Products DistributorsNetwork Service Providers Customers “Straight-Through” Rules Processing Rules

12 R EUTERS 150 Y EARS ContributorsReuters Systems And Products DistributorsNetwork Service Providers Customers Unified Rules Definitions Relational Database E-commerce Admin (Directories) Microsoft Exchange Policies and Rules Web Access Real-Time Permissioning Billing

13 R EUTERS 150 Y EARS Requirements for Rights Data Dictionary & Rights Expression Language 3.1.1Division of the Standard into an Extensible Core and Standard Prelude 3.1.2Inclusivity 3.1 REQUIREMENTS FOR THE STRUCTURE OF THE STANDARD

14 R EUTERS 150 Y EARS Requirements for Rights Data Dictionary & Rights Expression Language 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 3.2 REQUIREMENTS FOR RIGHTS STRUCTURE AND MANAGEMENT

15 R EUTERS 150 Y EARS Requirements for Rights Data Dictionary & Rights Expression Language 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 3.3 REQUIREMENTS FOR RIGHTS AND OBLIGATIONS DEFINITIONS

16 R EUTERS 150 Y EARS Requirements for Rights Data Dictionary & Rights Expression Language 3.4.1Temporal 3.4.2Geographic 3.4.3Environmental 3.4 ATTRIBUTES ON WHICH RIGHTS AND OBLIGATIONS ARE PREDICATED

17 R EUTERS 150 Y EARS Requirements for Rights Data Dictionary & Rights Expression Language 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 3.5 REQUIREMENTS PERTAINING TO TRUST

18 R EUTERS 150 Y EARS Requirements for Rights Data Dictionary & Rights Expression Language 3.6.1Specialised Support for Business to Business (B2B) Commerce 3.6.2Machine Processing of Digital Objects 3.6 ADDITIONAL FUNCTIONAL REQUIREMENTS

19 R EUTERS 150 Y EARS Requirements for Rights Data Dictionary & Rights Expression Language 4.1CHANNEL DEFINITION 4.2OBJECT MODELS 4.3WORKFLOW 4 OTHER AREAS FOR CONSIDERATION IN BUILDING THE STANDARD


Download ppt "R EUTERS 150 Y EARS David Parrott Reuters/Chief Technology Office 18 July 2001 Report on Reuters Response to MPEG-21 CfR Report to XACML Committee Face-to-Face."

Similar presentations


Ads by Google