Introduction to theMedia Value Chain Ontology

November 12-14th, 20085th General Meeting, Barcelona, Spain

Víctor Rodríguez DoncelUniversitat Politècnica de Catalunya

Intellectual Property Representation Non-digital:

Written contracts Text licenses in software (“license.txt”)

“Semi-digital” CreativeCommons

Digital Metadata annotation (ex: dc:creator) Rights Expression Languages (REL)

Its role in a complete DRM system MPEG-21 REL, ODRL, OMA DRM v2.0, others

Semantic Representation

2

The need of defining an ontology

Lack of standard representation of basic concepts regarding content use throughout the Value Chain creates confusion Although homogeneous principles are enacted everywhere (WIPO 163

countries) Since all users have access to Resource creation and distribution there is

the need for any user to play any value chain role. Each User and content case will require the ability for a user to take on a different Role than in other cases.

Formalizing a model into a formal system: Allows computer to perform reasoning: make inferences, classify

concepts etc. Having an explicit model interoperability is granted Computer applications rely on a common paradigm

3

MPEG-21 Context In process of standardization: MPEG-21 Part 10,

Committee Draft (CD) under balloting MPEG-21 Parts:

4

Part 1: Vision, Technologies and StrategyPart 2: Digital Item DeclarationPart 3: Digital Item IdentificationPart 4: Intellectual Property Management and Protection ComponentsPart 5: Rights Expression LanguagePart 6: Rights Data DictionaryPart 7: Digital Item AdaptationPart 8: Reference SoftwarePart 9: File FormatPart 10: Digital Item ProcessingPart 11: Evaluation Tools for Persistent Association Technologies

Part 12: TestBed for MPEG-21 Resource DeliveryPart 14: Conformance TestingPart 15: Event ReportingPart 16: Binary FormatPart 17: Fragment Identification of MPEG ResourcesPart 18: Digital Item StreamingPart 19: Media Value Chain Ontology

The Media Value Chain Premises

IP requires that there be an origin giving way to the concept of Original Work

A Work’s author is its rights holder All IP Entities are derived from other IP Entities except in

the case of Work Rights can be transferred along the Value Chain

5

...

Ontology Elements

6

CreatorCreatorEndUserEndUser

etc.etc.Usuarios

Entidades PI

Acciones

WorkManifestation

CreateWorkCreateWorkDistributeDistribute

MakeInstance...MakeInstance...

Permisos

MVCO elements (I): Types of IP Entities Intellectual Property entities

Work Adaptation Manifestation (based on a Work or Adaptation)

Instance (coming from a WorkManif. or AdaptationManif.)

Copy (coming from a Manifestation or from an Instance)

Product Use data

7

MVCO elements (II): Users User roles

Creator Adaptor Instantiator Producer Distributor EndUser

Kind of users: (ContentHandler,Collective)

8

MVCO elements (III): Actions Creation Model (Transformation of IP Entities along the value chain)

CreateWork MakeAdaptation MakeManifestation (either from Work or from Adaptation) MakeInstance (either from WM or from WA) MakeCopy (either from Manifestation or from Instance) MakeProduct

Distribution Model Distribute PublicCommunication

Consumption EndUserAction (Users can play any Role and none are locked

into a Role e.g. End-User Role)9

MVCO elements (IV): Permissions

Authorisation model Permissions are given in a chain. Additional Creator permissions for certain actions

Permissions can include requirements as both positive and negative propositions

Exceptional permissions can be made automatically The invoker must satisfy certain requirements to invoke

the CopyrightException

10

Relations (I)

11

IP Entity IP EntityAction

resultsInexecutedOver

resultedFromhasSuffered

User

executedBy hasExecuted

Relations (II)

12

IP Entity Action

executedOver

hasSuffered

Permission

Fact

permitsAction

hasRequired

hasRightsOwner

User issuedBy

rightGivenBy

Model Formalisation

Web Ontology Language (OWL) and the Semantic Web XML RDF RDFS OWL SWRL OWL DL chosen to grant decidability OWL to be published with unfettered access IP Management using their class individuals Expressed:

Defining classes, object properties, datatype properties, individuals etc.

Giving domain and range to the relations Imposing restrictions to the classes (existential, universal,

cardinality, disjunction etc.) No SWRL rules have been given

13

Classes in the hierarchy tree (I)

14

Classes in the hierarchy tree (II)

15

Classes in the hierarchy tree (III)

16

Relations

17

Relation Domain Range P InverseexecutedOver Action IPEntity hasSufferedresultsIn Action IPEntity F resultedFromexecutedBy Action User F hasExecutedhasRequired Permission Fact isRequiredInimpliesHaving Action ActionrightGivenBy Action UserpermitsAction Permission ActiononBehalfOf Content

HandlerUser T

issuedBy Permission UserhasRightsOwner IPEntity User FmadeUpOf IPEntity IPEntitytakesPartIn User Collective T

MVCO based Applications

Java API in two levels Level 1: simple datatypes, non object-oriented calls Level 2: a class set to handle all the details (Ad-hoc APIs

vs Automatically generated APIs)

18

MVCO

MVCO

API level 1 functionalities

19

API Level 2 sample class

20

Introduction to theMedia Value Chain Ontology

November 12-14th, 20085th General Meeting, Barcelona, Spain

Víctor Rodríguez DoncelUniversitat Politècnica de Catalunya

Thanks for your attention