Last Updated: 24 July 2008

The microODRL specification descrbes a profile of the complete ODRL language for use as microformats in marking up standard HTML web pages.

These note indicate the extend of the microODRL profile and all other features of ODRL not mentioned are not supported.

Identifying ODRL microformats
  • The root class name is “odrl” and the id attribute indicates that this is version 1.1 of ODRL semantics
  • Example: <div class="odrl" id="11">
  • An element with a class name of "odrl" is itself called an “microODRL Policy”
  • If there are no other identifiers (see Asset) then the microODRL Policy applies to the current web page
  • You may have multiple microODRL Policies in a web page

Identifying assets
  • You can explicitly identity the Asset URI with the asset class and uid class
  • Example: <span class="asset">contents of <abbr class="uid" title="http://odrl.net">this web site</span></span>

Identifying parties
  • You can specify parties related to the ODRL policy with the party and name class
  • Example: <span class="party">The illustrator is <span class="name">Billie Jay</span></span>

Terms to Support - Overview
  • Can only have one level of elements within each of the Permission, Constraint, and Requirements elements.
  • This means that all Constraints apply to all Permissions as well as all Requirements

Terms to Support - Permissions
  • Any of the terms for Permissions (See Section 3.1 "Permissions Elements" in the ODRL V1.1 Specification)
  • All Permissions must be within elements with the permission class
  • Example: <span class="permission"> ... </span>
  • Individual terms must use the corresponding class name (within the Permission class)
  • Example: You may <span class="play">play the audio</span>
  • Also supported are the ODRL/CC Profile Permissions: Reproduction, Distribution, DerivativeWorks, Sharing

Terms to Support - Constaints
  • All Constriants must be within elements with the constraint class
  • Individual terms must use the corresponding class name (within the Constraint class)
  • Example: You can use this for <span class="purpose">educational use</span> only
  • However, if the constraint has a sub-element and a technical value, then the class and title must be used for the constraint value including both the constaint name and subelement seperated with a “dash”.
  • Example: no more than <abbr class="count" title="10">ten times</abbr>
  • Example: you can only do this in <abbr class="spatial" title="AU">Australia</abbr>
  • Example: until the <abbr class="datetime-end" title="2008-12-31T23:59:59">end of 2008</abbr>
  • Also supported are the ODRL/CC Profile Constraints: NonCommercialUse, NonHighIncomeNationUse

Terms to Support - Requirements
  • Any of the terms for Requirements (See Section 3.3 "Requirement Elements" in the ODRL V1.1 Specification)
  • All Reqirements must be within elements with the requirement class
  • Individual terms must use the corresponding class name (within the Requirement class)
  • Example: You should <span class="attribution">Attribute the source</span>
  • However, to support the payment requirements, then a class for the payment type in one element must be used together with another element with the class and title (tax subelements are not supported and the currency should be part of the title):
  • Example: you need <span class="payment-prepay">pay up front</span> the amount of <abbr class="amount" title="AUD10.00">ten australian dollars</abbr>
  • Also supported are the ODRL/CC Profile Requirements: Notice, ShareAlike, SourceCode