ODRL Version 2.1 Ontology

This version

http://www.w3.org/ns/odrl/2/ODRL21

Latest version

http://www.w3.org/ns/odrl/2/

Date

2015-03-05

Revision

2.1

Authors

Mo McRoberts (BBC), Víctor Rodríguez Doncel (OEG-UPM)

Contributors

ODRL Community Group

Status of this document

This FINAL specification was published by the W3C ODRL Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Contributor License Agreement (CLA) there is a limited opt-out and other conditions apply. Learn more about W3C Community and Business Groups.

The W3C ODRL Community Group publishes a Final Specification to indicate that the document is believed to be mature and stable for implementation by the wider community. This Draft Specification is not yet endorsed by the W3C ODRL Community Group as appropriate for widespread deployment and that promotes the Community Groups’s mission.

Discussion and feedback of this document takes place on the W3C ODRL Community Group mailing list (see Contributor Archive). Feedback from the public is encouraged and can be send to public-odrl@w3.org (see Public Archive).

Copyright © 2015 the Contributors to the Final Specification, published by the W3C ODRL Community Group under the W3C Community Final Specification Agreement (FSA). A human-readable summary is available.

Namespace URI

The namespace URI for ODRL revision; ?> is http://www.w3.org/ns/odrl/2/.

Alternative serialisations

The ODRL 2 vocabulary is published both in human- and machine-readable forms. A GET request made to the canonical namespace URI will cause HTTP Content Negotiation to occur, which means that the most appropriate variant will be served according to your request. However, if you explicitly wish to retrieve a particular serialisation, you can also do so using the following URLs:

ODRL20.html

HTML (this document)

ODRL21.ttl

RDF (Turtle)

ODRL21.rdf

RDF/XML

ODRL21.nt

RDF (N-Triples)

ODRL21.xsd

XML Schema Definition

ODRL21.json

JSON Schema Definition

Table of Contents

1. 1 Summary of Terms
2. 2 Groups
3. 3 Examples of use
   1. 3.1 Set
   2. 3.2 Offer
   3. 3.3 Agreement
   4. 3.4 Request
   5. 3.5 Ticket
   6. 3.6 Offer and next policy
   7. 3.7 Privacy policy
   8. 3.8 Permission and prohibition
   9. 3.9 Inheritance
   10. 3.10 Social network
   11. 3.11 Multiple assets
4. 4 Classes
5. 5 Properties
6. 6 Concept schemes
7. 7 Concepts
8. 8 Named individuals
9. 9 Acknowledgements
10. 10 References

Summary of Terms

This vocabulary defines 24 classes, 56 properties, one concept scheme, 61 concepts and 18 named individuals.

Classes

Action | Agreement | All | AllConnections | AllGroups | All2ndConnections | Asset | ConflictTerm | Constraint | Duty | Group | Individual | Offer | Operator | Party | Permission | Policy | Privacy | Prohibition | Request | Rule | Set | Ticket | UndefinedTerm

Properties

systemDevice | absolutePosition | absoluteSize | action | assignee | assigner | attributedParty | conflict | consentingParty | constraint | count | dateTime | deliveryChannel | device | duty | elapsedTime | event | fileFormat | function | industry | informedParty | inheritAllowed | inheritFrom | language | media | meteredTime | operator | output | compensatedParty | payAmount | percentage | permission | product | profile | prohibition | proximity | purpose | recipient | relation | relativePosition | relativeSize | resolution | rightOperand | spatial | status | system | target | timeInterval | timedCount | trackingParty | undefined | dataType | version | virtualLocation

Concept schemes

actions

Concepts

acceptTracking | adHocShare | aggregate | annotate | anonymize | append | appendTo | archive | attachPolicy | attachSource | attribute | commercialize | compensate | concurrentUse | copy | delete | derive | digitize | display | distribute | ensureExclusivity | execute | export | extract | extractChar | extractPage | extractWord | give | grantUse | include | index | inform | install | lease | lend | license | modify | move | nextPolicy | obtainConsent | pay | play | present | preview | print | read | reproduce | reviewPolicy | secondaryUse | sell | share | shareAlike | textToSpeech | transfer | transform | translate | uninstall | use | watermark | write | writeTo

Named individuals

eq | gt | gteq | hasPart | ignore | invalid | isA | isAllOf | isAnyOf | isNoneOf | isPartOf | lt | lteq | neq | perm | policyUsage | prohibit | support

Groups

Some terms can be organised into logical groups, as shown below:

Examples of use

The examples in this section are RDF expressions of the scenarios provided by the ODRL Version 2.0 Core Model.

Set

The following shows an instance of a set policy. The set shows a policy expression, stating that the asset, http://example.com/asset:9898, is the target of the permission to reproduce and the prohibition to modify.

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .

<http://example.com/policy:0099>
	a odrl:Set;
	odrl:permission [
		a odrl:Permission ;
		odrl:target <http://example.com/asset:9898> ;
		odrl:action odrl:reproduce
	] ;
	odrl:prohibition [
		a odrl:Prohibition ;
		odrl:target <http://example.com/asset:9898> ;
		odrl:action odrl:modify
	] .

Download this example as Turtle, RDF/XML, or N-Triples.

Because all of the rules associated with this policy have the same target, and do not have any constraints or duties (requirements), one may abbreviate the expression of the policy and use the Dublin Core rights or license predicates to associate the asset with that policy:

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .
@prefix dct: <http://purl.org/dc/terms/> .

<http://example.com/asset:9898> dct:license <http://example.com/policy:0099> .

<http://example.com/policy:0099>
	a odrl:Set;
	odrl:permission odrl:reproduce ;
	odrl:prohibition odrl:modify .

Download this example as Turtle, RDF/XML, or N-Triples.

Offer

The following shows the instance of an offer policy. The offer contains the music file http://example.com/music:4545 that is offered by the party http://example.com/sony:10 with the permissions to play and copy the file. The permission to copy is only granted once. The two permissions are offered in exchange for a payment of AUD$0.50.

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .

<http://example.com/policy:0231>
	a odrl:Offer ;
	odrl:permission [
		a odrl:Permission ;
		odrl:target <http://example.com/music:4545> ;
		odrl:assigner <http://example.com/sony:10> ;
		odrl:action odrl:play ;
		odrl:duty _:requirements
	] ;
	odrl:permission [
		a odrl:Permission ;
		odrl:target <http://example.com/music:4545> ;
		odrl:assigner <http://example.com/sony:10> ;
		odrl:action odrl:copy ;
		odrl:duty _:requirements ;
		odrl:constraint [
			a odrl:Constraint ;
			odrl:count 1 ;
			odrl:operator odrl:lteq
		]
	] .

_:requirements
	a odrl:Duty ;
	odrl:action odrl:pay ;
	odrl:constraint [
		a odrl:Constraint ;
		odrl:payAmount 50.00 ;
		odrl:operator odrl:eq ;
		odrl:unit <http://cvx.iptc.org/iso4217a:AUD>
	] .

<http://example.com/sony:10> a odrl:Party .

Download this example as Turtle, RDF/XML, or N-Triples.

Agreement

The following shows the instance of an agreement policy. The agreement contains all entities shown in the offer scenario above. A new party, http://example.com/billie:888 has been added. This party accepted the previous offer and thus is now the buyer of the permission play and copy: i.e. they are now linked as assignee of the permissions and duty entities.

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .

<http://example.com/policy:9001>
	a odrl:Agreement ;
	odrl:permission [
		a odrl:Permission ;
		odrl:target <http://example.com/music:4545> ;
		odrl:assigner <http://example.com/sony:10> ;
		odrl:assignee <http://example.com/billie:888> ;
		odrl:action odrl:play ;
		odrl:duty _:requirements
	] ;
	odrl:permission [
		odrl:target <http://example.com/music:4545> ;
		odrl:assigner <http://example.com/sony:10> ;
		odrl:assignee <http://example.com/billie:888> ;
		odrl:action odrl:copy ;
		odrl:duty _:requirements ;
		odrl:constraint [
			a odrl:Constraint ;
			odrl:count 1 ;
			odrl:operator odrl:lteq
		]
	] .

_:requirements
	a odrl:Duty ;
	odrl:action odrl:pay ;
	odrl:constraint [
		a odrl:Constraint ;
		odrl:payAmount 50.00 ;
		odrl:operator odrl:eq ;
		odrl:unit <http://cvx.iptc.org/iso4217a:AUD>
	] .

<http://example.com/sony:10> a odrl:Party .
<http://example.com/billie:888> a odrl:Party .

Download this example as Turtle, RDF/XML, or N-Triples.

Request

The following shows the instance of a request policy. The party http://example.com/guest:0589 has requested the permission to display the target asset, http://example.com/news:0099.

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .

<http://example.com/policy:04311>
	a odrl:Request ;
	odrl:permission [
		a odrl:Permission ;
		odrl:action odrl:display ;
		odrl:assignee <http://example.com/guest:0589> ;
		odrl:target <http://example.com/news:0099>
	] .

<http://example.com/guest:0589> a odrl:Party .

Download this example as Turtle, RDF/XML, or N-Triples.

Ticket

The following shows the instance of a ticket policy. The ticket expresses the play permission for the target asset, http://example.com/game:4589. The ticket is valid until the end of the year 2010. Any valid holder of this ticket may exercise this permission.

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<http://example.com/policy:0811>
	a odrl:Ticket ;
	odrl:permission [
		a odrl:Permission ;
		odrl:action odrl:play ;
		odrl:target <http://example.com/game:4589> ;
		odrl:constraint [
			a odrl:Constraint ;
			odrl:operator odrl:lteq ;
			odrl:dateTime "2010-12-31"^^xsd:date
		]
	] .

Download this example as Turtle, RDF/XML, or N-Triples.

Offer and next policy

The following shows the instance of an offer policy showing the next-policy structure.

The party http://example.com/sony:99 assigns the permission distribute directly to the potential buyer of the permission who will pay €1,000. The distribute permission is also constrained to the country Italy. The potential assignee may then distribute the target asset according to the next-policy target asset linked directly from this duty. In this case, the next policy asset stipulates that the potential assignee may only offer the display permission to downstream consumers.

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .

<http://example.com/policy:5531>
	a odrl:Offer ;
	odrl:permission [
		a odrl:Permission ;
		odrl:action odrl:distribute ;
		odrl:target <http://example.com/wallpaper:2321> ;
		odrl:assigner <http://example.com/sony:99> ;
		odrl:constraint [
			a odrl:Constraint ;
			odrl:operator odrl:eq ;
			odrl:spatial <http://ontologi.es/place/IT>
		] ;
		odrl:duty <http://example.com/duty:01>, <http://example.com/duty:02>
	] .

<http://example.com/duty:01>
	a odrl:Duty ;
	odrl:action odrl:pay ;
	odrl:constraint [
		a odrl:Constraint ;
		odrl:payAmount 1000.00 ;
		odrl:operator odrl:eq ;
		odrl:unit <http://cvx.iptc.org/iso4217a:EUR>
	] .

<http://example.com/duty:02>
	a odrl:Duty ;
	odrl:action odrl:nextPolicy ;
	odrl:target <http://example.com/policy:7777> .

<http://example.com/policy:7777>
	a odrl:Set ;
	odrl:permission [
		a odrl:Permission ;
		odrl:action odrl:display ;
		odrl:target <http://example.com/wallpaper:2321>
	] .

<http://example.com/sony:99> a odrl:Party .

Download this example as Turtle, RDF/XML, or N-Triples.

Privacy policy

The following shows the instance of a privacy policy.

The target asset is personal data and the assignee is allowed to distribute the asset only for the purpose of contacting the subject of the personal data. The purpose value is taken from the P3P privacy purpose vocabulary.

Additionally, the assigner (the party who the personal data is about) has stipulated that the assignee must delete the asset after a 30 day period (retention policy).

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .
@prefix p3p: <http://www.w3.org/2002/01/p3prdfv1#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<http://example.com/policy:1111>
	a odrl:Privacy ;
	odrl:permission [
		a odrl:Permission ;
		odrl:action odrl:distribute ;
		odrl:target <http://example.com/billie:888:personal-data> ;
		odrl:assigner <http://example.com/billie:888> ;
		odrl:assignee <http://example.com/gov:health:au> ;
		odrl:duty [
			a odrl:Duty ;
			odrl:action odrl:delete ;
			odrl:constraint [
				a odrl:Constraint ;
				odrl:operator odrl:eq ;
				odrl:dateTime "P30D"^^xsd:dateTime 
			]
		] ;
		odrl:constraint [
			a odrl:Constraint ;
			odrl:operator odrl:eq ;
			odrl:purpose p3p:contact
		]
	] .

<http://example.com/billie:888> a odrl:Party .
<http://example.com/gov:health:au> a odrl:Party .

Download this example as Turtle, RDF/XML, or N-Triples.

Permission and prohibition

The following shows the instance of an agreement policy with both a permission and a prohibition. The party http://example.com/sony:10 assigns the permission play to the party http://example.com/billie:888 at the same time they are prohibited from utilising the target asset as a mobile:ringtone. Additionally, in case of any conflict, the conflict attribute is set to perm indicating that the permission entity will take precedence.

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .
@prefix mobile: <http://example.com/mobile#> .

<http://example.com/policy:3433>
	a odrl:Agreement ;
	odrl:conflict odrl:perm ;
	odrl:permission [
		a odrl:Permission ;
		odrl:action odrl:play ;
		odrl:assignee <http://example.com/billie:888> ;
		odrl:assigner <http://example.com/sony:10> ;
		odrl:target <http://example.com/music:1234908>
	] ;
	odrl:prohibition [
		a odrl:Prohibition ; 
		odrl:action mobile:ringtone ;
		odrl:assignee </http://example.combillie:888> ;
		odrl:assigner <http://example.com/sony:10> ;
		odrl:target <http://example.com/music:1234908>
	] .

<http://example.com/billie:888> a odrl:Party .
<http://example.com/sony:10> a odrl:Party .

Download this example as Turtle, RDF/XML, or N-Triples.

Inheritance

The following shows the instance of a (child) policy http://example.com/policy:9999 inheriting from another (parent) policy http://example.com/policy:5531. The inherit-from attribute of the (child) policy has the same identifier as the (parent) policy's own identifier.

In this inheritance example, the parent policy allows the party http://example.com/billie:888 to print the parent’s target asset. The child policy allows the party http://example.com/class:IT01 (a group of people) to display the child’s target asset. Since the child policy also inherits from the parent policy, then the party http://example.com/class:IT01 can also print the parent’s target asset.

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .

<http://example.com/policy:5531>
	a odrl:Agreement ;
	odrl:permission [
		a odrl:Permission ;
		odrl:action odrl:print ;
		odrl:target <http://example.com/report:2321> ;
		odrl:assigner <http://example.com/pub:88> ;
		odrl:assignee <http://example.com/billie:888> ;		
	] .
	
<http://example.com/policy:9999>
	a odrl:Agreement ;
	odrl:inheritFrom <http://example.com/policy:5531> ;
	odrl:permission [
		a odrl:Permission ;
		odrl:action odrl:display ;
		odrl:target <http://example.com/report:2333> ;
		odrl:assigner <http://example.com/pub:88> ;
		odrl:assignee <http://example.com/class:IT01>
	] .

<http://example.com/pub:88> a odrl:Party .
<http://example.com/billie:888> a odrl:Party .
<http://example.com/class:IT01> a odrl:Group .

Download this example as Turtle, RDF/XML, or N-Triples.

Social network

The following shows the instance of an agreement policy for a social network scenario.

The target asset are photos posted to a social network site and the assigner is the owner of the photos. The assignee is a group and represents the football network members on the social network, who are each allowed to display the photos.

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .

<http://example.com/policy:5109>
	a odrl:Agreement ;
	odrl:permission [
		a odrl:Permission ;
		odrl:action odrl:display ;
		odrl:target <http://example.com/myPlace:billie:photos:football2010> ;
		odrl:assigner <http://example.com/myPlace:billie> ;
		odrl:assignee <http://example.com/myPlace:network:football>
	] .

<http://example.com/myPlace:billie> a odrl:Party .
<http://example.com/myPlace:network:football> a odrl:Group .

Download this example as Turtle, RDF/XML, or N-Triples.

Multiple assets

The following shows an instance of a set policy utilising multiple asset entities.

The index permission is granted to the target asset. Additionally, the x:collection asset specifies which database the index outcome should be stored in.

@prefix odrl: <http://www.w3.org/ns/odrl/2/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix x: <http://example.com/x#> .

<http://example.com/policy:881212>
	a odrl:Set ;
	odrl:permission [
		a odrl:Permission ;
		odrl:action odrl:index ;
		odrl:target <http://example.com/archive/2010> ;
		x:collection <http://example.com/x/database>
	] .

x:collection 
	rdfs:subPropertyOf odrl:relation .

Download this example as Turtle, RDF/XML, or N-Triples.

Classes

Asset

Party

Policy

ConflictTerm

UndefinedTerm

Rule

Permission

Prohibition

Duty

Action

Constraint

Operator

Agreement

Offer

Privacy

Request

Set

Ticket

All

All2ndConnections

AllConnections

AllGroups

Group

Individual

Properties

conflict

undefined

permission

prohibition

inheritAllowed

inheritFrom

profile

relation

output

target

function

action

constraint

duty

unit

dataType

operator

rightOperand

status

absolutePosition

absoluteSize

count

dateTime

deliveryChannel

device

systemDevice

elapsedTime

event

fileFormat

industry

language

media

meteredTime

payAmount

percentage

product

purpose

recipient

relativePosition

relativeSize

resolution

spatial

system

timeInterval

version

virtualLocation

assignee

assigner

attributedParty

consentingParty

informedParty

payeeParty

compensatedParty

trackingParty

proximity

timedCount

Concept schemes

actions

Concepts

use

grantUse

compensate

acceptTracking

aggregate

annotate

anonymize

append

appendTo

archive

attribute

concurrentUse

copy

delete

derive

digitize

display

distribute

ensureExclusivity

execute

export

extract

give

include

index

inform

install

lease

license

lend

modify

move

nextPolicy

obtainConsent

pay

play

present

preview

print

read

reproduce

reviewPolicy

secondaryUse

sell

textToSpeech

transfer

transform

translate

uninstall

watermark

write

writeTo

adHocShare

extractChar

extractPage

extractWord

attachPolicy

attachSource

shareAlike

commercialize

share

Named individuals

perm

prohibit

ignore

invalid

support

eq

gt

gteq

hasPart

isA

isAllOf

isAnyOf

isNoneOf

isPartOf

lt

lteq

neq

policyUsage

Acknowledgements

The authors gratefully acknowledge feedback and contributions to this document from members of the W3C ODRL Community Group.

This document was generated using phpspecgen written by Nicholas J. Humfrey and modified by Yves Raimond, and subsequently modified by Mo McRoberts.

References

[ODRL-MODEL]

R. Iannella, S. Guth, D. Paehler & A. Kasten (eds.) Open Digital Rights Language (ODRL) Version 2.0 - Core Model. Final Specification, W3C ODRL Community Group, 24 April 2012. http://www.w3.org/community/odrl/two/model/

[ODRL-VOCAB]

S. Guth & R. Iannella (eds). Open Digital Rights Language (ODRL) Version 2.0 – Common Vocabulary. Final Specification, W3C ODRL Community Group, 19 April 2012. http://www.w3.org/community/odrl/two/vocab/

[ODRL-XML]

R. Iannella (ed.). Open Digital Rights Language (ODRL) Version 2.0 – XML Encoding. Final Specification, W3C ODRL Community Group, 19 April 2012. http://www.w3.org/community/odrl/two/xml/

[RDF-PRIMER]

E. Manola & E. Miller (eds.). RDF Primer. W3C Recommendation, 10 February 2004. http://www.w3.org/TR/2004/REC-rdf-primer-20040210/

[TURTLE]

D. Beckett, T. Berners-Lee. Turtle - Terse RDF Triple Language. W3C Team Submission, 28 March 2011. http://www.w3.org/TeamSubmission/turtle/