The Digital Media Project
Source M. Gauvin
Date 2006/07/11
Title
Report on RRD Development with No.
796/Madrid
some new IDP Requirements V.02
Contents
1. Summary....................................................................................................................... 1
2. DMP Creation RRD Model ......................................................................................... 4
2.1. Expressing the IP Value Chain .............................................................................. 5
2.2. Linking the Language of IP with the language of Digital Media .......................... 6
3. RRD Development view of Digital Representation ..................................................... 2
3.1. Objects ................................................................................................................... 2
3.2. Actions ................................................................................................................... 3
3.3. Agents .................................................................................................................... 3
4. Call Requirements ........................................................................................................ 7
1. Summary
Initial development of the RRD Ontology has begun. The approach to satisfying the
Requirements in the call can be summarized as follows:
1) The Creation Model can be formalised in order to express the following digital
files in the context of DMP Creation Model IP Entities:
a.
b.
c.
d.
Work Instance Copy
Adaptation Instance Copy
Work Manifestation Copy (by Work Author)
Adaptation Manifestation Copy (By Adaptation Author)
2) For a complete treatment of the IP Rights in IDP 3 the RRD Ontology Requires
the inclusion of digital and non digital object related Actions:
a. Actions agnostic to whether the relevant IP Entities are represented
digitally or not such as:






Create Adaptations: These authorizations are realized upon
registration of the Adaptation.
First Fixation: In essence the Right to make an Instance
Synchronization: Concurrent performance/display of two distinct
Work or Adaptation Instances each for a different sense e.g. text and
audio or video and song.
Mechanical Reproduction (make copy of Instances)
Public Communication (of Instances and Manifestations):
o Live Performance
o Radio, Televisión, Internet
Distribution: Sale, renting and lending of copies.
1

Private Copy remuneration: Licensing storage media to hold
private non commercial copies.
b. Actions taken on digital objects in their essential nature agnostic to what
they may represent. i.e. copy, delete, modify, store, revoke etc. and all
DMP Value Chain Functions
3) Bringing together the two sets of Actions coherently requires that the IDP
include protected metadata placeholders so that all governed DCI’s can be
recognized using the RRD terms according to their position in the Creation
Model hierarchy. Also it is required that IDP users be able to take on standard
roles as “Agents” on the basis of Actions defined in the RRD. Thus, combining
both sets of Actions plus Agent roles will allow for the determination of generic
default conditions required to invoke different IDP Functions and combinations
thereof.
For example, a user obtains a Work-Manifestation-Copy and chooses the
standard role of Agent type: Adaptor, this then could automatically give rise to
previously determined set of conditions to be fulfilled such as “ To Register DCI
Adaptation of “Great Blue Work” approval certification XYZ is required.”
2. RRD Development view of Digital Representation
2.1. Objects
Object refers to any entity that is represented digitally an example being a Resource or
media file, in this case the object being represented is the actual event (performance,
writing, acting etc.) and its purpose is to convey the event directly to the human senses
i.e. sight, hearing etc.
Resource based representations themselves can be represented as in DMP Content
Information (DCI) a particular instance of the MPEG-21 Digital Item (DI) initially
designed to provide a standard format for securely communicating all the information
pertinent to the use of a Resource such as its location, required tools to render
Resources, Rights Expressions, Metadata etc., so that Resources are never isolated from
the means to use, govern and protect them.
However, other types of representations such as a Work (independently of its physical
manifestations) or any entity for that matter, can be Represented within a single DI or
DCI without necessarily including an actual Resource. Thus, we may produce equally
unique Representations of any entity for any purpose and most particularly for the
purpose of IP rights management.
2
2.2. Actions
Actions are classified in two categories:
1. Actions taken on abstract entities such as the DMP Creation Model IP Entities
these refer to Rights that are given such as the Right of first fixation or of public
communication of a work through a representation such as digital media files.
2. Actions taken on digital files that are in essence agnostic to what the digital files
represent.
2.3. Agents
Agents are defined by the actions that they realize on objects and therefore the
definition of an action implies the corresponding agent to realize the action.
3
3. DMP Creation RRD Model
This section presents an example of how to organize IP objects to be formalized as an
OWL based ontology. The DMP Creation Model extended beyond the IP Entities is
sketched in Figure 1 below.
In the Mind
Work
Independent Work
A
Adaptation
Derivative Work
B of A
Depends on
• Uses
• Produce
Manifestation
B of A
(By Author of C)
Uses
• Produce
• Produce
Work
Instance Copy
• Depends On
• Uses
Uses
• Produce
Instance
Instance
Work
Manifestation Copy
Adaptation
Derivative Work
C of A
• Depends On
• Depends On
Manifestation
(By Author of
A)
Depends on
Adaptation
Manifestation Copy
• Produce
Manifestation
C of A
(By Author of C)
• Uses
Instance
Adaptation
Manifestation Copy
Adaptation
Instance Copy
• Produce
Adaptation
Instance Copy
Physical
Physical
Figure 1. Extended DMP Creation Model
In Figure 1 and between the creator of the Work and the making of Instances, derivation
of IP Entities occurs at two fundamental levels denoted by the verbs: Depend and Use.
Use, always implies the existence of at least one physical Copy therefore allowing
further commercial copies for which rights granting are required. Depend implies a
more un-severable relationship that may not necessarily refer to a physically Manifest
object; for example, the Work here meant to refer to the logical construct and/or idea
expressed in the Work’s physical Manifestations, exists necessarily prior to being so
expressed. Therefore, we say that the Manifestation Depends on the Work rather than
say that it Uses the Work.
Thus, and from the above diagram, the following unequivocal relationships can be
derived:
Work:
 Neither Depends or Uses any other Object
 Has one-to-many relationship to Adaptation,
 Has one-to-many relationship to Manifestation
4



Has one-to-many relationship to Manifestation Copy
Has one-to-many relationship to Instance
Has one-to-many relationship to Instance Copy
Adaptation:
 Depends on a Work
 Uses Manifestation of Work
 Has a one-to-one relationship to Manifestation
 Has one-to-many relationship to Instance
 Has one-to-many relationship to Instance Copy
Manifestation:
 Depends on Work or Adaptation
 Has one-to-one relationship to Adaptation and/or Work
 Has one to many relationship to Instance
 Has one to many relationship to Manifestation Copy
Instance:
 Uses Manifestation of Work
 Has one-to-many relationship to Instance Copy
3.1. Expressing the IP Value Chain
Beginning with the last event of a chain of events, the chaining of Depend, Use and
Produce defines generically what the object is (Work, Manifestation, Instance and
Copy).
Figure 2 below specifies how the Produce, Use and Depend chain of relationships
between objects can be used to determine which actions can be associated with the
corresponding representation of IP Entities.
5
Produce-Use-Use-Depend-Depend => Adaptation Instance Copy
Require Rights for:
 Adaptation of Work
 First fixation of Adaptation
 Copy of Adaptation Instance
Produce-Use-Depend => Work Instance Copy
Require Rights for:
 First fixation of Work
 Copy of Work Instance
Produce-Depend-Depend => Adaptation Manifestation Copy
Require Rights for:
 Adaptation of Work
Produce-Depend => Work Manifestation Copy
No Required Rights
Figure 2. Produce, Use, Depend relationships vs. Actions/Rights.
From the above we begin to distinguish on the basis of the chain of standard defined
relationships i.e. depend-use-produce that a given digital file may require a minimum
set of standard rights attributions. Furthermore, other extensions of rights such as
public communication and performance rights, public dissemination and distribution
and moral rights can then also be appropriately ascribed on the basis of these basic
determinations. With the definition of standard Agent roles, it can be determined which
IP Rights can be ascribed independently or dependently.
Note that the rights quoted above are examples and any variation of them can be
invoked as per different jurisdictions. However, it is the purpose of this approach that
in most if not all jurisdictions the Produce-Use-Depend chains will remain constant.
3.2. DRM as the link between IP and Digital Media Languages
The IP entities above are linked independently of whether those relationships are
represented digitally or otherwise. In the case where objects are represented digitally, as
in the copies illustrated above being digital files, rights over those must be made
subordinate to the rights over the IP Entity or Entities being represented, thus actions to
be taken on digital files representing different IP Entities must be associated with the
hierarchy expressed by the IP Ontology.
6
Since the ability to perform functions on media files are agnostic to what those files
represent, only a DRM system can determine what is being represented and how to
associate that particular representation with the set of actions or functions available. To
achieve this, the metadata used to describe generically the object represented by a DCI
as well as the Resources within it, must be available and coincide with the terms defined
in the IP Ontology. Also, users of Resources will be associated with generic roles such
as Adaptor, Instantiator, End-User etc. when being assigned rights in fully automated IP
licensing of processes.
4. Call Requirements
The following table illustrates how the present development status begins to answer the
call Requirements and shows some new IDP requirements to be considered for IDP-3.
Requirement
Status
Comments & Requirements
Support for DMP
Creation Model
yes
Requirements:
Introduction of new terms to AD 6 and review of existing ones.
 Terms for Actions
o Depend
o Use
o Produce
Support for Functions
and Entities
yes
The design is such that users can determine what objects are in the IP
Entity hierarchy based on Depend, Use and Produce Chains. By
satisfying the requirements below, any set of Value-Chain Functions
can be mapped to the RRD by Users or Groups of Users.
Support for all
Permissions
Demonstrate with DMP
Use Cases
Extendibility
yes
Requirements:
 IDP support for standard default Agent role definitions i.e.
based on Actions. E.g. Instantiator, Adaptor. Review of AD
6 definitions and addition of Producer.
 DCI should support means for recording and concatenating
Depend, Use and Produce.
 Rationalization of Value Chain Functions in terms of scope
vis a vis Agents.
See above
yes
More to come.
yes
The standard Depend, Use, Produce chaining results can be labelled
differently for different IP i.e. Music, Video, Text ect.
Requirements:
Automated OWL
yes
Extend list of IP Entities Actions see summary above.
API to be developed.
7