|
The Digital Media Project |
|||
|
Source |
L. Chiariglione |
Date |
2005/01/25 |
|
Title |
Revised description of “Open Release” Use Case |
No. |
0314/AHG04 |
Revised description of “Open Release” Use Case
There are many cases where some Users (companies or even individuals) own Rights to a piece of Content, have an interest in Releasing it in such a way that other Users can freely Access it but do not want to make it public domain. In other words those Users want to Release a piece of Content that is Governed, even though in a “light-weight” form. In this document this type of Release is called “Open Release”.
Examples of Open Release Content are publicity material and teasers. An important set of major potential applications is represented by the BBC’s Creative Archive project.
Leonardo has just finished preparing a PowerPoint presentation. This was intended to be used at a conference that he can no longer attend. So he makes a video of himself while he makes the presentation.
As the conference has an international exposure and he would like to have his presentation accessible by Users in different countries, Leonardo creates:
1. A set of human-readable Creative Commons-like Rights Expressions for a selected range of jurisdictions (of course including the jurisdiction of the place where the conference is held)
2. The corresponding machine-readable Rights Expressions written in the appropriate languages
Leonardo then performs the following steps:
· He gets a License Identifier from an agency
· He creates a DCI containing
o The audio-video file
o The PowerPoint file
o The human-readable License
o The machine-readable License
· He binarises the Rights Expression
· He binarises the DCI
· He gets a DCI Identifier from an agency
Leonardo knows that the Released DCI will not deter people from doing what he does not what them to do. However, if he or one of his robots will find Resources taken from the DCI on some web site he will have the option of suing the infringers. Also, if his presentation will become a “best seller”, he will have the option to License it at other terms to other Users. These other Users may well decide to Release the same Content, possibly enriched with other elements, is a protected form.
To support this Use Case a set of Primitive Functions are needed.
The reference software for Open Release could be made available in the following form:
· An authoring tool with the following functionality
o Create DCI
o Create License
o Obtain License Identifier
o Obtain DCI Identifier
o Create DCF file format
· A browsing tool with the following functionality
o Extract DCI
o Interpret License
o Browse Resources
The following issues have been identified that are important for the successful deployment of Open Release:
· License Identification and DCI Identification agencies. DMP must establish the DMP Naming Authority and agencies must be appointed so that Users can get Identifiers. It is realised that there is a number of legal issues that must be resolved to shield agencies from the responsibilities arising from them Assigning Identifiers to Content for which the Use Requesting the Identifiers may not have Rights.
· Cost of Identifiers. The success of Open Release depends on making DCI Identifiers available at (virtually) no cost
· Cost of technologies. There should be no cost involved in the use of the IPR required to implement Open Release.
It is clear that Open Release would “create the market”. All efforts should be made by all affected parties to make this possible by creatively resolving the 3 issues identified above.