1. Nathan D.M. Robertson nrobertson@law.umaryland.edu License Term Encoding and License Expression ICOLC Spring Meeting Montréal, Canada 25 April 2007

2. Licenses Unencoded What staff can and can’t do What users can and can’t do

3. Licenses Encoded: Inform Users ERM System !!?! ? Oh, good! I can use this for ILL! I’m not supposed to e-mail it to my friends? ( whatever, I’ll do it anyway...)

4. Licenses Encoded: Assist Licensing ERM System It has always been our policy never to agree to indemnify in any contract. Oh, did I mention our upcoming financial and legal audit? How many days (and paper cuts) is it worth to you? I know the answer, but... Uh oh. Do we have any current licenses with indemnification clauses? I can tell you in minutes !

5. Purpose of License Encoding  Two distinct functions: 1. Inform staff and patrons of rights, responsibilities and restrictions. 2. Facilitate license management through sophisticated reporting and ERM system triggers.

6. ERMI Encoding Options  Permitted (explicit)  Prohibited (explicit)  Permitted (interpreted)  Prohibited (interpreted)  Silent (no interpretation)  Not applicable 1. Inform Users 2. Facilitate Mgmt. Way too complicated! Just tell me Yes or No! Please. Not nearly sophisticated enough.

7. ERMI License Term Fields  Governing Jurisdiction  Confidentiality of Agreement Note  Clickwrap Modification Clause Indicator  Termination Requirements  Completeness of Content Clause Indicator  Print Copy  Digital Copy  Scholarly Sharing  Electronic Link Term Note 1. Inform Users 2. Facilitate Mgmt.  Database Protection Override Clause Indicator  Perpetual Access Right  Concurrency with Print Version Clause Indicator  Applicable Copyright Law Good, good….  Content Warranty Aaugh! No! I don’t care about any of this!  Indemnification by Licensee Clause Indicator  Applicable Copyright Law  UCITA Override Clause Indicator  Cure Period for Breach Unit of Measure  Performance Warranty Uptime Guarantee Oh, is that all? A good start, but insufficient.

8. License Interpretation is Hard Work Can the library use the resource to fulfill Interlibrary Loan requests? LICENSE AGREEMENT …. 5.2.3. Blah. blah blah blah... 5.2.4. Interlibrary Loan. Institution may not use Electronic Titles for purpose of interlibrary loans. 5.2.4. More Blah. blah blah blah. LICENSE AGREEMENT …. 4. PROHIBITED USES. Licensee may not: a) blah blah… b) sell, supply or otherwise distribute data retrieved from the Licensed Resource to third parties; c) blah blah blah….. LICENSE AGREEMENT 1. License: i) blah blah… ii) …you will not re-distribute the materials retrieved from the products to other libraries or third parties… blah blah blah….. v) Notwithstanding the above restrictions, this license shall not restrict your rights to use of the materials under the copyright law of the United States and the doctrine of “fair use.” LICENSE AGREEMENT 1)blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah … 2)blah blah blah blah blah blah blah blah blah blah blah blah blah blah… !!?! ?

9. Questions  Is the “License Management” benefit worth the cost?  Time and effort to interpret and encode  Staff confusion  ERM System development efforts  Is “interpreted” vs. “explicit” useful to staff, or only to licensing managers? … and what if you don’t have to do all the work yourself?

10. XML License Expression Standard ERM System ONIX-PL Encoding interpret silence and confirm interpretations ? ? ? ONIX PL

11. Consortium XML License Expression Standard ERM System ERM System ERM System ONIX PL

12. ONIX Publications License  First manifestation of planned “ONIX for Licensing Terms” family of messages.  One of EDItEUR’s ONIX suite of XML messages.  Flexible “modular” constructions to express concepts. Usages, Agents, Resources….  Ability to encode and express an entire license. 1. Inform Users 2. Facilitate Mgmt. An entire license? Are you insane? Hush.

13. Rights Supply Chain selected rights transferred all rights transferred My patrons need X and Y rights. I can only transfer rights I have. selected rights all rights selected rights all rights I have (not all rights!) selected rights the remaining rights selected rights My patrons need X and Y rights. Hooray! A product I can license. You have got to be kidding.

14. ONIX-PL  ?  ERMI Encodings  Create an ERMI “dialect” of ONIX-PL.  Require message suppliers to choose from array of expression “modules” that map to ERMI values.  Some additional constraints on usages can map automatically to ERMI note fields.  ERM systems will communicate with each other using the dialect.  Imperfect metadata crosswalk.  Many concepts expressible in ONIX-PL inexpressible in ERMI dialect.  Precision lost in conversion of encoded values to notes.

15. Consortium ERM System ERM System Data and Work Flow ERM System “ERMIAN” ONIX-PL with explicit expressions only “ERMIAN” ONIX-PL with interpretations interpret silence and confirm interpretations

16. Discussion…  Which concepts are worth encoding?  Would automatic load of some data change the cost/benefit analysis?  How much granularity is desirable?  Can you accept upstream interpretations?  Do you need to know that interpretations occurred?  Interpretation might include override of explicit expressions—do you need to know?  What if downstream library prefers more values and more granularity than upstream interpreter?