Tools to help publishers and libraries produce OLT licencesDesign for an ONIX-PL license drafting systemFrancis CaveONIX-PL license drafting scenarios Starting point will generally be an existing paper license Licensors (e.g. publishers) creating ONIX-PL expressions for their own licenses Licensees (e.g. libraries) creating ONIX-PL interpretations of publisher licenses Licensees creating ONIX-PL expressions for their own preferred usage policies and other termsONIX-PL license drafting scenarios Starting point for creating an ONIX-PL license expression will always be a license template (public or private) To encourage the adoption of standard forms of license expression To promote interoperability To simplify the use of ONIX-PL licenses by recipient licenseesONIX-PL license drafting scenarios But where do the templates come from? Specialist function required for the creation of templates and optional clauses Public templates and clauses will need to be created and maintained for use by all Private templates and clauses will need to be created and maintained by individual license developers / ownersONIX-PL license drafting scenarios Different types of involvement in the creation of ONIX-PL license expressions Creation and modification of templates and optional clauses Selection of the right template Selection of optional clauses, if relevant “Filling-in the blanks” in the template Final steps and sign-offONIX-PL license drafting scenarios Drafting ONIX-PL expressions will be an iterative process Need to compare drafts Need to exchange drafts between licensor and licensee Need to express the status of a draft in the ONIX-PL format new functionality to be added in next revision of ONIX-PLUser roles Template and clause developer License expression / interpretation creator Template selector Optional clause selector Form-filler License expression reviewer / approverFunctional requirements (1) Template development Selection of “built-in” basic templates Pallet of building-block clauses that may be added to a basic template Added clauses may be defined to be required or optional for use with specific templates Choices constrained by ONIX-PL schema and associated business rules that define valid combinations of clauses in a templateFunctional requirements (2) Drafting of expressions / interpretations for specific licenses Selection of appropriate template Public or private template Selection of appropriate optional clauses within that template Add new clauses Remove existing clauses where not required Completion of clauses that contain editable fields Free text fields for names, addresses, etc Selection of single or multiple options from controlled value listsFunctional requirements (3) Revision of existing license expressions Extension of initial drafting process Add or remove optional clauses Change contents of editable fields ONIX-PL format will support revision management and version control new functionality to be added in next revision of ONIX-PLFunctional requirements (4) Review / approve draft license expression Two views of a draft license expression: Page view, for general review on screen (web browser) or on paper, and for easier comparison with the original paper license Form view, for final editing steps and approval / sign-off Side-by-side comparison of different drafts Limited editing of draft e.g. selection of some specific options that remain undecided Approval of drafts for communication with other parties Final sign-off of agreed expressionsFunctional requirements (5) Communication of license expressions ONIX-PL XML format for machine-to-machine communication Page view for general review purposes can be saved in various XML-based formats XHTML for web review Microsoft Office XML (Word, Excel,.) OpenOffice XML .Drafting system design principles System must support all the ONIX-PL license drafting scenarios System must meet the functional requirements for each user role System must encourage the use of public templates System must be intuitive to use for persons with adequate knowledge and experience of the drafting of licensesDrafting system architecture Web-based, client-server architecture Web server can deliver appropriate functionality to different types of user employing standard web browser technology Limits requirement for system development to server-side generation of user form and page views and associated functionality back-end expression validation and communication functions Network-based or stand-aloneDrafting system architectureONIX-PL License Expression ServerWeb ServerPrivate Template storeLicense storeWeb BrowserOther ONIX-PL License Expression ServersPublic Template ServerPublic Template storeLocal printingInternetDrafting systemUser interface design (1) Forms view Different