provision of new contents (e.g. when a human content provider delegates the CUbRIK platform), or to express derivative works. Licenses information are described by the LicenseInformation class, which stores information extracted from the provided licenses, which includes: LicenseType: a unique identifier for the type of the license, e.g. “cc-by”, a Creative Commons License type which allows to share, remix and make commercial use of a work under the condition of attribution of the original author • LicenseInfoURL: a URL pointing to information about the license, e.g. http://creativecommons.org/licenses/by/2.0/de/ • LicenseText: a human-readable license text • MorePermissionsURL: a contact point for getting information / negotiating further usage of the work or details beyond the described license (e.g. request for commercial use for a CC license that is only allows non-commercial use) • MachineReadableText: a machine readable version of the license, e.g. in XML format An important part of the provision process is the Approval of the content, i.e. the verification of the content with respect to the claimed ownership and copyrights. The status of approval for a ContentObject can be tracked using Approval entities, which store the approval Level (e.g. “1.0” for fully approved or “0.0” for not approved); thanks to the possibility to define several Approval objects, and to the presence of a date attribute, it is also possible to track the evolutions of a ContentObject approval status. To provide an example of provenance and rights management in CUbRIK, Figure 1-10 describes the following scenario: •
There is a well-known ContentProvider (“Jamendo”), thus having reached the highest possible trust level (“1.0”). • The ContentProvider uploads 2 different ContentObjects (the AudioObject and the VideoObject). • The ContentProvider also provides licenses for the ContentObjects, which contain information about the Creators of the ContentObjects as well as information that is used by system to derive and set actual UsagePermissions. In the given example the system only “knows” two possible UsagePermissions: “transcode” and “view”. Based on the provided licenses (in both cases CC BY) the system associates the existing UsagePermissions with the ContentObjects. • Based on the given License Information of the VideoObject, the system finds a derivation between the VideoObject and the AudioObject, thus establishing a relationship between the ContentObjects. • The Creator of the “Audio Object” is also a registered CUbRIKEndUser, thus the system is able to establish a relationship between the Creator and the system user. • An additional ContentObject (“Transcoded”) is derived from the AudioObject by a SystemComponent (the “Transcoder”). The “Transcoder” has a “transcode” permission (per definition). • Based on the ContentProvenance and License information of the AudioObject, the system derives a new LicenseInformation instance for the Transcoded object. Moreover, there is a CUbRIKEndUser “John Doe” which has the permission to view ContentObjects (per definition). •
CUbRIK Metadata Models
Page 17
D2.1 Version 1.0