Standard Licence Expression

1. Standard Licence Expression Sharon Farb, UCLA Daviess Menefee, Elsevier Inc. Christopher McKenzie , John Wiley & Sons Alicia Wise, Publishers Licensing Society April 4, 2006

2. The context • Growth of digital collections in libraries • Variation in licence terms • What are library users permitted to do? • Under what conditions? • Which classes of users are permitted to do what? • What exceptions are there to what they are permitted to do? • e.g. “Can I print this out for the classroom? • How can publishers help libraries comply with licence terms?

3. Intrallect DRM report for JISC:What libraries say they want • Expression of rights • rights expressed in machine readable form • Dissemination of rights • ensuring that whenever a resource is described its rights are also described • Exposure of rights • user sees the rights information associated with a resource

4. The need for precision • e.g. Inter Library Loan (ILL) • ILL clause from one model contract “The Licensee may supply to an Authorised User of another library within the same country as the Licensee a copy of an individual document being part of the Licensed Materials by post, fax or electronic transmission via the Internet or otherwise, for the purposes of research or private study and not for Commercial Use.” i.e. lots of variables – and they do vary!

5. 1-n UseEvent Permits (MAY) Prohibits (MUST NOT) Has Exception Requires (MUST) 0-n UseEvent Has Precondition 0-n Payment Reporting Event etc Terms of a Licence as a group of Events Licensing Event This structure allows for whatever level of flexibility or granularity may be required now or in the future.

6. Structure of ONIX for Licensing Terms message • Definitions • defines and labels the entities that are used in XML expressions elsewhere in the message. • Agent, Place, Resource, Event, Date/Time, State, Period, Usage • SupplyTerms • covers terms relating to the delivery of the licensed materials, eg ftp, physical media etc • UsageTerms • permitted and prohibited uses and related conditions • PaymentTerms • if included • OtherConditions • general terms, included by reference only (e.g. liability, confidentiality or force majeure)

7. ONIX for Licensing Terms • Takes into account the requirements of all stakeholders in the chain • Provides for the full complexity of rights management requirements • Fully extensible • Able to support any future business model • Able to support multimedia rights management • Valuable generic message for publisher use (e.g. Google) • Designed to support interoperability • Can be mapped to other well structured metadata formats (e.g. LOM, IMS)

8. Where are we now? • “Proof of concept” project in UK supported by JISC and PLS (PA / ALPSP / PPA) • Report and sample message from EDItEUR • Two new JISC-funded ONIX for Licensing projects (to be completed by 1 July 2006) • Negotiation and mapping of publisher licence - BIC, John Wiley and Cranfield University • Definition of tools and services to help publishers produce ONIX for LT - BIC, ALPSP, Loughborough University

9. NISO / DLF / EDItEUR / PLS License Expression Working Group • A wide cross-section of stakeholders will • Guide and review the work of EDItEUR consultants. • Participate in pilot testing. • Bring their expertise and awareness of licensing and technology to keep the group's work relevant and complete.

10. Some current issues • Consensus about which parts of licences to prioritise and test. • Encourage system vendors to share their thinking about services on top of messaging. • Joint development of rights data dictionary that can be output in wide array of formats: which? • Governance for the rights data dictionary going forward.

11. http:www.editeur.org/onix_licensing.html http://www.niso.org/committees/License_Expression/LicenseEx_comm.html More information