22
Alapan Arnab DNA Group Computer Science UCT Extending ODRL to Enable Bi- Directional Communication Alapan Arnab Andrew Hutchison

Extending ODRL to Enable Bi-Directional Communication

  • Upload
    alka

  • View
    63

  • Download
    0

Embed Size (px)

DESCRIPTION

Extending ODRL to Enable Bi-Directional Communication. Alapan Arnab Andrew Hutchison. Agenda. Introduction Design Motivations Extensions Example. Introduction. RELs essentially allow for the expression of contract terms - PowerPoint PPT Presentation

Citation preview

Page 1: Extending ODRL to Enable   Bi-Directional Communication

Alapan ArnabDNA GroupComputer ScienceUCT

Extending ODRL to Enable Bi-Directional Communication

Alapan ArnabAndrew Hutchison

Page 2: Extending ODRL to Enable   Bi-Directional Communication

2

Agenda

Introduction Design Motivations Extensions Example

Page 3: Extending ODRL to Enable   Bi-Directional Communication

3

Introduction

RELs essentially allow for the expression of contract terms

All current RELs have a an uni-directional expression from rights holder to the end user

Thus, this does not allow for the full power that is achieved through a negotiated process

Page 4: Extending ODRL to Enable   Bi-Directional Communication

4

RMS Example

Tom creates a document for Jill and protects it with RMS Can only be read and edited by Jill Time limit of a week

If Jill requires an extension, Tom needs to rewrite the rules Resend the protected document back to Jill

Page 5: Extending ODRL to Enable   Bi-Directional Communication

5

“the assumption of a one-way expression of rights has in part led to the current deficiencies in the REL [XrML]” – Mulligan et al. [2002]

Page 6: Extending ODRL to Enable   Bi-Directional Communication

6

Page 7: Extending ODRL to Enable   Bi-Directional Communication

7

Design Motivations

Need to use external control sets Object separated from license (super distribution)

Use a request – response model

Page 8: Extending ODRL to Enable   Bi-Directional Communication

8

New Functions Breakdown

License Server Functions Keep track of extensions Negotiation algorithms AI for negotiating complex licenses

DRM Controller Functions Keep track of updated use licenses

Page 9: Extending ODRL to Enable   Bi-Directional Communication

9

Three Negotiation Elements

Request (from the user) Deny Request (from the rights holder) Accept Request (from the rights holder)

Page 10: Extending ODRL to Enable   Bi-Directional Communication

10

Three Request Elements

Add Remove Replace

Page 11: Extending ODRL to Enable   Bi-Directional Communication

11

Schema Diagrams

Page 12: Extending ODRL to Enable   Bi-Directional Communication

12

Schema Diagrams Continued

Page 13: Extending ODRL to Enable   Bi-Directional Communication

13

Putting it all together

Chosen to extend the rightsType element

Could have used other element, eg. negType

Our opinion – this is more elegant

Page 14: Extending ODRL to Enable   Bi-Directional Communication

14

Example

Use scenario #2 from the ODRL 1.1 specs Mary Smith (consumer) buys an e-book: “Why Cats Sleep

and We Don’t” Rights:

Single CPU Print 2 times

Suppose Mary Smith is a journalist, and would like to write a thorough review Want to excerpt pictures from various parts of e-book

Example essentially a case of fair use Will also use an extension from an unpublished work

Page 15: Extending ODRL to Enable   Bi-Directional Communication

15

Initial Request

<odrl-ext:rights> <odrl-ext:request> <o-ex:context>

<o-dd:uid>urn:ebook.world/999999/license/1234567890-ABCDEF</o-dd:uid>

</o-ex:context> <odrl-ext:request-add> <o-ex:permission> <o-dd:excerpt> <o-ex:constraint> <o-dd:range> <o-dd:min>3</o-dd:min> <o-dd:max>56</o-dd:max> </o-dd:range> </o-ex:constraint> </o-dd:excerpt> </o-ex:permission> </odrl-ext:request-add>

<o-ex:party> <o-ex:context>

<o-dd:uid>urn:ebook.world/999999/users/msmth-000111</o-dd:uid>

<o-dd:name>Mary Smith</o-dd:name>

</o-ex:context> </o-ex:party> </odrl-ext:request></odrl-ext:rights>

Page 16: Extending ODRL to Enable   Bi-Directional Communication

16

Rejection

<odrl-ext:rights> <odrl-ext:deny-request> <o-ex:context>

<o-dd:uid>urn:ebook.world/999999/license/TRANS-0101</o-dd:uid>

</o-ex:context> <odrl-ext:request-add> <o-ex:permission> <o-dd:excerpt> <o-ex:constraint> <o-dd:range> <o-dd:min>3</o-dd:min> <o-dd:max>56</o-dd:max> </o-dd:range> </o-ex:constraint> </o-dd:excerpt> </o-ex:permission> </odrl-ext:request-add>

<o-ex:party> <o-ex:context>

<o-dd:uid>urn:ebook.world/999999/users/msmth-000111</o-dd:uid>

<o-dd:name>Mary Smith</o-dd:name> </o-ex:context> </o-ex:party> <odrl-ext:description>Excerption is only available with an

academic, scholar or journalist credential. Furthermore, a maximum of 10% of the total protected work can be excerpted

</odrl-ext:description></odrl-ext:deny-request></odrl-ext:rights>

Page 17: Extending ODRL to Enable   Bi-Directional Communication

17

Counter Offer

<odrl-ext:rights> <odrl-ext:grant-request> <o-ex:context>

<o-dd:uid>urn:ebook.world/999999/license/1234567890-ABCDEF</o-dd:uid>

</o-ex:context> <o-ex:context>

<o-dd:uid>urn:ebook.world/999999/license/1234567890-ABCDEF-01</o-dd:uid>

</o-ex:context> <odrl-ext:request-add> <o-ex:permission> <o-dd:excerpt> <o-ex:constraint> <o-dd:range> <o-dd:min>3</o-dd:min> <o-dd:max>13</o-dd:max> </o-dd:range>

<o-dd-ext:credential> <o-dd-ext:OrList> <o-dd-ext:CredentialsType>Journalist</o-

dd-ext:CredentialsType> <o-dd-ext:CredentialsType>Academic</o-

dd-ext:CredentialsType> <o-dd-ext:CredentialsType>Scholar</o-

dd-ext:CredentialsType> </o-dd-ext:OrList> </o-dd-ext:credential> </o-ex:constraint> </o-dd:excerpt> </o-ex:permission> </odrl-ext:request-add> <o-ex:party> <o-ex:context>

<o-dd:uid>urn:ebook.world/999999/users/msmth-000111</o-dd:uid>

<o-dd:name>Mary Smith</o-dd:name> </o-ex:context> </o-ex:party> </odrl-ext:request></odrl-ext:rights>

Page 18: Extending ODRL to Enable   Bi-Directional Communication

18

Refined Request<odrl-ext:rights> <odrl-ext:grant-request> <o-ex:context> <o-dd:uid>

urn:ebook.world/999999/license/1234567890-ABCDEF-01</o-dd:uid>

</o-ex:context> <odrl-ext:request-add> <o-ex:permission> <o-dd:excerpt> <o-ex:constraint> <o-dd:range> <o-dd:min>3</o-dd:min> <o-dd:max>4</o-dd:max> </o-dd:range> <o-dd:range> <o-dd:min>16</o-dd:min> <o-dd:max>18</o-dd:max> </o-dd:range> <o-dd:range> <o-dd:min>56</o-dd:min> <o-dd:max>57</o-dd:max> </o-dd:range>

<o-dd-ext:credential> <o-dd-ext:CredentialsType> Journalist

</o-dd-ext:CredentialsType> </o-dd-ext:credential> </o-ex:constraint> </o-dd:excerpt> </o-ex:permission> </odrl-ext:request-add> <o-ex:party> <o-ex:context> <o-dd:uid>

urn:ebook.world/999999/users/msmth-00111

</o-dd:uid> <o-dd:name>Mary Smith</o-dd:name> </o-ex:context> </o-ex:party> </odrl-ext:request></odrl-ext:rights>

Page 19: Extending ODRL to Enable   Bi-Directional Communication

19

Request Accepted<odrl-ext:rights> <odrl-ext:grant-request> <o-ex:context> <o-dd:uid>urn:ebook.world/999999/license/1234567890-ABCDEF</o-dd:uid> </o-ex:context> <o-ex:context> <o-dd:uid>urn:ebook.world/999999/license/1234567890-ABCDEF-01</o-dd:uid> </o-ex:context> <odrl-ext:request-add> <o-ex:permission> <o-dd:excerpt> <o-ex:constraint> <o-dd:range> <o-dd:min>3</o-dd:min> <o-dd:max>4</o-dd:max> </o-dd:range> <o-dd:range> <o-dd:min>16</o-dd:min> <o-dd:max>18</o-dd:max> </o-dd:range> <o-dd:range> <o-dd:min>56</o-dd:min> <o-dd:max>57</o-dd:max> </o-dd:range>

<o-dd-ext:credential> <o-dd-ext:CredentialsType> Journalist </o-dd-ext:CredentialsType> </o-dd-ext:credential> </o-ex:constraint> </o-dd:excerpt> </o-ex:permission> </odrl-ext:request-add> <o-ex:party> <o-ex:context> <o-dd:uid> urn:ebook.world/999999/users/msmth-000111 </o-dd:uid> <o-dd:name>Mary Smith </o-dd:name> </o-ex:context> </o-ex:party> </odrl-ext:request></odrl-ext:rights>

Page 20: Extending ODRL to Enable   Bi-Directional Communication

20

Future Work/Work in Progress Aim to create a working prototype by end of

September Part of a smaller sub-project

Not yet too sure on AI aspect

Page 21: Extending ODRL to Enable   Bi-Directional Communication

21

Conclusions

Presented extensions to ODRL 1.1 for bi-directional support Enables negotiation between user and license server Allows for the negotiation of any part of an ODRL license

Our opinion, this makes ODRL more complete Would like to see these extensions (or similar

structures) in ODRL 2.0 Extensions can also be done in other RELs like

XrML (which we have also done)

Page 22: Extending ODRL to Enable   Bi-Directional Communication

22

Questions

? Email: [email protected]