Copyright ODRL Initiative 2005-2009. All Rights Reserved.
Note: This document has been renamed "Common Vocabulary" from the previous "Core Metadata" to better reflect its objective.
This document contains the ODRL Version 2.0 Common Vocabulary Specification. The Common Vocabulary provides basic vocabulary and its semantics for the ODRL rights expression language. Any or all of the vocabulary terms can be used by communities to form their own profiles to meet their particular requirements. The consistent reuse of these terms will lead to greater interoperability across communities.
This is the third public Working Draft of the ODRL V2.0 Common Vocabulary Specification document produced by the ODRL Version 2.0 Working Group.
The ODRL Initiative publishes a Working Draft for review by working group members and other interested parties. The ODRL Version 2.0 Working Group expects to advance this document to a Draft Specification once the Working Group is satisfied the vocabulary has broad consensus and demonstrated at least two interoperable implementations.
Comments on this document should be sent to editors and discussion of this document takes place on the public working group mailing list odrl-version2@odrl.net archived at http://odrl.net/pipermail/odrl-version2_odrl.net/.
This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than "work in progress". Publication as a Working Draft does not imply endorsement by the ODRL Initiative.
1. Overview
2. ODRL Common Vocabulary
3. Profiles (Informative)
Acknowledgements
References
The ODRL rights expression language (REL) has benefited from a robust underlying information model that has captured its semantics and provided extensibility paths for various communities. The Common Vocabulary Profile specifies the terms (vocabulary) used by the Core Model for common rights expression needs. (This was called the "data dictionary" in the previous version.)[ODRL11]
The following documents are planned and being developed for ODRL Version 2.0:
The new profile includes additional semantics and meets requirements gathered from the DRM community, the latest research on security, access control, obligation management as well as the past experiences in implementations and research of ODRL. The requirements for Version 2.0 are documented [ODRL-REQ] and will be directly referenced in this document to ensure that they have been adequately addressed (where applicable).
The model shall be formally specified using UML notation [UML] [ODRL-REQ#6] and shall utilise the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in accordance to [RFC2119].
The table below outlines the comprehensive version 2.0 ODRL Common Vocabulary. The Common Vocabulary offers a wide range of vocabulary terms for the expression of Permissions, Prohibitions, Constraints, and Duties over assets. Additional and/or different semantics can be defined in ODRL Extension Profiles (see also Section 3 Profiles ) for particular ODRL application areas, such as service level agreements, contracts, or certain industry sectors. All terms of the Common Vocabulary are related to specific entities of the Core Model [ODRL-Model]., e.g. Asset, Party, Permission, Action, Duty, etc. and MUST only be used for that particular entity.
Vocabulary terms in this section may be used as the "name" of the Action Entity.
Name | Identifier | Semantics | ODRL Entity | Comment/Example |
---|---|---|---|---|
The act of rendering the asset onto paper or hard copy form | Permission, Prohibition | Creating a permanent, fixed (static), and directly perceivable representation of the asset | ||
Play | play | The act of rendering the asset into audio and/or video form | Permission, Prohibition | Playing a movie file |
Display | display | The act of making a transient visible rendering of the asset | Permission, Prohibition | Displaying an image on a screen |
Execute | execute | The act of executing the asset | Permission, Prohibition, Duty | Machine executable code or Java such as a game or application |
Export | export | The act of converting the asset into a new form | Permission, Prohibition, Duty | Typically used to convert the asset into a different format for consumption on a third-party system and may also include the conversion of the rights license |
Install | install | The act of loading an asset onto storage device ready for operation | Permission | |
Uninstall | uninstall | The act of unloading an asset from storage device | Permission, Prohibition | The asset is not longer useable |
Sell | sell | The act of allowing the asset to be sold (ownership transfer) in exchange of value | Permission, Prohibition | |
Copy | copy | The act of making an exact copy of an asset. | Permission, Prohibition | |
Move | move | The act of moving an asset | Permission, Prohibition | After the asset has been moved, the original copy must to be deleted |
Modify | modify | The act of changing parts (or all) of the asset | Permission, Prohibition | A new asset is created |
Extract | extract | The act of extracting (replicating) unchanged parts (or all) of the asset for reuse into another asset | Permission, Prohibition | |
Annotate | annotate | The act of adding notations/commentaries to the asset | Duty | A new asset is created |
Aggregate | aggregate | The act of using an asset (or parts of it) as part of a composite collection | Permission, Prohibition | |
Tracked | tracked | The act of recording information on the use of the asset | Duty | The collected information MAY be sent to the asset owner |
Give | give | The act of allowing the asset to be given away (ownership transfer) in perpetuity without exchange of value | Permission, Prohibition, Duty | The original asset MUST be deleted |
Pay | pay | The act of paying a financial amount to a party | Duty | Both the amount and parties need to be specified. The Payer is the Assignee and the Payee is the Assigner. |
Commercialize | commercialize | The act of exploiting the asset in a commercial environment | Permission, Prohibition | |
Share | share | The act of the non-commercial reproduction and distribution of the asset to other parties. | Permission, Prohibition | This action can be used to express Creative Commons [CC] Sharing semantics |
Ad-hoc Share | adhocShare | The act of sharing an asset to parties in close proximity to the owner | Permission, Prohibition | This action can be used to express OMA [OMA] Sharing semantics |
Lend | lend | The act of allowing the asset to be made available for temporary use then returned (without exchange of value) | Permission, Prohibition | During this period, the asset is only available to the lendee. Temporal constraints may be used. |
Lease | lease | The act of allowing the asset to be made available for a fixed period of time then returned (for exchange of value) | Permission, Prohibition | During this period, the asset is only available to the lendee. Temporal constraints may be used. |
Translate | translate | The act of translating the asset into a different language | Permission, Prohibition; | A new asset is created |
Archive | archive | The act of archiving the asset for long-term preservation | Permission, Prohibition | |
Digitize | digitize | The act of digitizing the asset from its original (analogue) format. | Permission, Prohibition | |
Attribution | attribute | The act of showing attribution to the asset owners. | Duty | This action can be used to express Creative Commons [CC] Attribution semantics. |
Reproduce | reproduce | The act of reproducing an asset | Permission | This action can be used to express Creative Commons [CC] Reproduction semantics. |
Distribute | distribute | The act of distributing, display publicly, and publicly perform the asset | Permission | This action can be used to express Creative Commons [CC] Distribution semantics. |
Derive | derive | The act of creating a derivative asset. | Permission | A new asset is created. This action can be used to express Creative Commons [CC] Derivative works semantics. |
Notice | notice | The act of keeping all license notices with the asset | Duty | This action can be used to express Creative Commons [CC] Sharing semantics. |
Share-a-like | shareAlike | The act of licensing any derivative asset under the same terms as the original asset. | Duty | This action can be used to express Creative Commons [CC] Share-a-like semantics. |
Source Code | sourceCode | The act of requiring that source code must be provided for the asset and derivative asset. | Duty | This action can be used to express Creative Commons [CC] Source Code semantics. |
Vocabulary terms in this section may be used as the field "name" of the Constraint Entity.
The Constraint entity as three attributes; name, operator and rightOperand, For example, to express that a Print Permission is constraint by 10 times, create a Constraint entity where:
In the field "rightOperand" of the Constraint Entity, standard data types such as Integer, Real, Sting, etc. may be used
Name | Identifier | Semantics | Comment/Example |
---|---|---|---|
Count | count | A numeric count (positive integer) indicating the number of times the corresponding entity may be exercised. | |
Spatial | spatial | A code representing a geospatial area | The code value and code source MUST be represented |
Date Time | dateTime | The date and optional time representing a point in time | Date and Time value must conform to [ISO8601]. |
Timed | timed | The number of seconds after which timed metering use of the asset begins | The default value is 0 seconds. This can be used to express OMA [OMA] Timed-Count semantics |
Accumulated | accumulated | The maximum period of metered usage time | Value must conform to [ISO8601]. For example "P30H" indicates a 30 hour period. |
Interval | interval | Recurring period of time in which the rights can be exercised | Interval value must conform to [ISO8601]. For example "P7D" indicates a 7 day period. |
Water Mark | watermark | Specification of watermarking constraint for the asset. | |
Purpose | purpose | Specification of a defined purpose to which the usage is constrained | E.g. educational use |
Industry | industry | Specification of a defined industry to which the usage is constrained | E.g. media |
CPU | cpu | A computing system with an identifiable central processing unit (CPU). | |
System | system | An identifiable computing system | |
Proximity | proximity | An identifiable proximity detection method name | This can be used to express OMA [OMA] Proximity semantics |
High Income Nation | highIncomeNation | The given rights must NOT be exercised in nations defined as high-income economies by the World Bank. | This can be used to express Creative Commons [CC] Sharing Non High Income Nation Use semantics. |
Terms in this section may be used as attribute in the field "operator" of the Constraint Entity.
Name | Identifier | Semantics | Comment/Example |
---|---|---|---|
Greater Than | gt | An operator indicating that a given value is greater than the rightOperand of the Constraint. | |
Less Than | lt | An operator indicating that a given value is less than the rightOperand of the Constraint. | |
Equals | eq | An operator indicating that a given value equals the rightOperand of the Constraint. | |
Not Equal To | neq | An operator indicating that a given value is not equal to the rightOperand of the Constraint. | |
Less Than or Equal To | lteg | An operator indicating that a given value is less than or equal to the rightOperand of the Constraint. | |
Greater Than or Equal to | gteg | An operator indicating that a given value is greater than or equal to the rightOperand of the Constraint. | |
Is Part Of | isPartOf | An operator indicating that a given value is part of the defined set defined by the rightOperand of the Constraint. |
Terms in this section may be used as attribute in the field "measure" of the Object Entity.
The applicable value being measured is then expressed in the field "value" of the Object Entity. For example, to express that a Pay Duty has 10 Euros:
In the field "value" of the Object Entity, standard data types such as Integer, Real, Sting, etc. may be used
Name | Identifier | Semantics | Comment/Example |
---|---|---|---|
Currency | currency | The 3-letter currency code as specified in ISO 4217 [ISO4217] | The number given in the 'value' field of the Object Entity represents an amount in the respective currency (e.g. EUR, USD, GBP). |
Advert | advert | The number of adverts the party must view | For example, with a value = 3, represents that three advertisements must be viewed by the party. |
The ODRL Core Model and Common Vocabulary represent the basic needs for rights expressibility. As a result, different communities will require less or more terms from the Common Vocabulary. Community Profiles that extend the ODRL Core Model or Common Vocabulary are expected to be developed that adequately document these changes in respect to the Common Vocabulary. Some requirements of this process include:
The editors gratefully acknowledge feedback and contributions to this document from:
[ODRL11] | R. Iannella (ed). Open Digital Rights Language (ODRL), Version 1.1.
Technical Specification, ODRL Initiative, 8 August 2002. http://odrl.net/1.1/ODRL-11.pdf |
[ODRL-REQ] | S. Guth & R. Iannella (eds). Open Digital Rights Language (ODRL)
Version 2.0 Requirements (Working Draft), ODRL Initiative, http://odrl.net/2.0/v2req.html,
24 November 2004. |
[RFC2119] | Key words for use in RFCs to Indicate Requirement Levels, S. Bradner.
The Internet Society, March 1997. ftp://ftp.rfc-editor.org/in-notes/rfc2119.txt |
[vC] | F. Dawson & T. Howes, vCard MIME Directory Profile, IETF, RFC 2426,September 1998. http://www.ietf.org/rfc/rfc2426.txt |
[DC] | The Dublin Core Metadata Intitiative http://dublincore.org |
[UML] | Unified Modeling Language (UML), Management Group, 2003. http://www.omg.org/technology/documents/formal/uml.htm |