1 / 28

Machine readable licences An Introduction to ONIX-PL

Machine readable licences An Introduction to ONIX-PL. JIBS-Eduserv Seminar, Wednesday 16 June 2010 Mark Bide – Executive Director, EDItEUR. About EDItEUR. London-based global trade standards organization for books and serials supply chains Established 1991

kmatos
Télécharger la présentation

Machine readable licences An Introduction to ONIX-PL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Machine readable licencesAn Introduction to ONIX-PL JIBS-Eduserv Seminar, Wednesday 16 June 2010 Mark Bide – Executive Director, EDItEUR

  2. About EDItEUR • London-based global trade standards organization for books and serials supply chains • Established 1991 • Not-for-profit membership organization • ONIX family of communications standards • ONIX for Books • ONIX for Serials (online subscription products including ebooks) • ONIX for Licensing Terms • EDI • RFID • Manage the International ISBN Agency

  3. ONIX family principles • XML • Common approach to encoding, validation • Designed for global application • Permissive, open structures • Able to cover a wide range of use cases and to be adaptable to local use without compromising the core structures • Encourage localised and appropriate profiling for specific applications • Reuse of key structures and semantics within and between message families • Common composites • Shared code values • Separate message structure from code values • Easy update of code lists while maintaining backwards compatibility • Only when absolutely necessary (new “major release” like ONIX for Books 3.0) is backwards compatibility lost

  4. ONIX-PL

  5. ONIX-PL: the problem • …there is a desire on the part of users of resources…to be compliant with terms established by rightsholders…the need for users to know what permissions attach to the access and use of any particular resource becomes increasingly pressing due to considerable differentiation between license terms…It is difficult or impossible for users to discover for themselves the terms that apply to a particular resource… • With licenses typically available only on paper (or its digital equivalent), reference to license terms is labour intensive and slow • ERMS only part of the solution – how do you populate the data?

  6. ONIX-PL: the solution? • …lies in the establishment of mechanisms by which key elements of licenses can be made available so that a user can be provided with the most significant elements of license information at the point of use – those that relate to permitted access and use. This needs to happen without additional human intervention; those significant license terms must be machine interpretable.

  7. ONIX-PL: the headlines • ONIX for Publications Licences (ONIX-PL) a message for expressing publisher-library licences in XML using an extensible dictionary of terms • v1.0 published on the EDItEUR website • A second issue of the Code Lists will be published when needed • ERM systems will allow users to link from e-resources to user-friendly understandable usage terms • Librarians can view complete licence and interpret terms • OPLE – an open source authoring/editing tool, jointly funded by JISC and PLS to help publishers map their licences to ONIX-PL and libraries to add interpretation or map licenses • RELI Project – a pilot project to demonstrate the function of a licence registry • Although semantics specific to the publisher/library supply chain, the conceptual framework should be applicable to any licence

  8. RELI – ONIX-PL in action “Registry of Electronic Licences”A JISC funded project led by the University of Loughborough

  9. RELI: identifying user requirements • Making license terms available to end-users is important • Some form of symbolic representation of what is permitted and what is forbidden, but that only key usage terms • Interpreting licenses presents many problems, particularly if the meaning of clauses is obscure. In these cases most librarians tend to err on the side of caution and do not allow users to make any use of a resource if they are not completely clear about its legitimacy. • Librarians can find it difficult to present the clauses within the license in a meaningful way without expert unpicking of the “legal jargon”. • Librarians indicated that integrating a license registry with existing library management systems would be desirable, but that it should function without relying on other library management systems. • Publishers would like to be able to offer one broad general license, but this was not possible due to differing conditions on the sale of journals. Publishers, however, did indicate that they would be willing to create machine-readable licenses when it can be shown that there is a demand for them.

  10. RELI: user requirements – the detail Bide, M., Dhiensa, R., Look, H., Oppenheim, C. and Probets, S.G., ''Requirements for a registry of electronic licences'', The Electronic Library, 27(1), February 2009, 43-57, ISSN: 0264-0473

  11. The challenge of identity – license to resource

  12. The challenge of identity – license to resource to user

  13. High level overview of process

  14. The user view of RELI

  15. The user view of RELI

  16. RELI Conclusions • The “chicken and egg” conundrum • The requirement is real – but only libraries can create the demand • Expressing licenses in XML is a considerable discipline for publishers and everyone else in the chain • There is a steep learning curve for everyone • Expressing licenses in XML does not overcome licensing disagreements • Indeed, in the short term, the opposite may be true • There are substantial challenges in identification • Of resource, licenses and users • A license registry can be useful to an institution in a number of ways, as well as providing permissions data for users • Storing all licenses in one place for access by library staff • Enabling comparisons of licenses

  17. Issues identified but ruled out of scope • Overlapping licences for the same resources • Repository architecture • Distributed vs centralized • Governance and trust issues

  18. ONIX-PL and EDUSERV

  19. EDItEUR Project for Eduserv • Commissioned in September 2009 • ONIX-PL expression of Eduserv licence terms • Report outlining issues that arose in creating the expression • Project completed November 2009 • Deliverables: http://www.eduserv.org.uk/research/studies/onixpl2009 • Required some modest addition of terms to the ONIX vocabulary • New “user” types • New “usage purposes” • New “general term types”

  20. ONIX-PL: 2010

  21. Developments that we expect to see this year • Approved JISC project: JISC Collections Licence Comparison and Analysis Tool • Create ONIX PL expressions of about 80 of the most licensed resources in the JISC Collections portfolio • Make licence expressions available to UK academic institutions for loading into ERMS • Create a web interface to allow view of individual licences, multiple licences at the same time, or to compare the terms of specific licences • Active interest from SURFDienst in pilot project(s) • Associated with management of rights in “complex objects” in repositories

  22. Thank you mark@editeur.org

More Related