Tools to help publishers and libraries produce OLT licencesONIX-PL license drafting scenariosStarting point will generally be an existing paper licenseLicensors (e.g. publishers) creating ONIX-PL expressions for their own licensesLicensees (e.g. libraries) creating ONIX-PL interpretations of publisher licensesLicensees creating ONIX-PL expressions for their own preferred usage policies and other termsONIX-PL license drafting scenariosStarting 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 expressionTo promote interoperabilityTo simplify the use of ONIX-PL licenses by recipient licenseesONIX-PL license drafting scenariosBut where do the templates come from?Specialist function required for the creation of templates and optional clausesPublic templates and clauses will need to be created and maintained for use by allPrivate templates and clauses will need to be created and maintained by individual license developers / ownersONIX-PL license drafting scenariosDifferent types of involvement in the creation of ONIX-PL license expressionsCreation and modification of templates and optional clausesSelection of the right templateSelection of optional clauses, if relevant“Filling-in the blanks” in the templateFinal steps and sign-offONIX-PL license drafting scenariosDrafting ONIX-PL expressions will be an iterative processNeed to compare draftsNeed to exchange drafts between licensor and licenseeNeed to express the status of a draft in the ONIX-PL formatnew functionality to be added in next revision of ONIX-PLUser rolesTemplate and clause developerLicense expression / interpretation creatorTemplate selectorOptional clause selectorForm-fillerLicense expression reviewer / approverFunctional requirements (1)Template developmentSelection of “built-in” basic templatesPallet of building-block clauses that may be added to a basic templateAdded clauses may be defined to be required or optional for use with specific templatesChoices 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 licensesSelection of appropriate templatePublic or private templateSelection of appropriate optional clauses within that templateAdd new clausesRemove existing clauses where not requiredCompletion of clauses that contain editable fieldsFree text fields for names, addresses, etcSelection of single or multiple options from controlled value listsFunctional requirements (3)Revision of existing license expressionsExtension of initial drafting processAdd or remove optional clausesChange contents of editable fieldsONIX-PL format will support revision management and version controlnew functionality to be added in next revision of ONIX-PLFunctional requirements (4)Review / approve draft license expressionTwo 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 licenseForm view, for final editing steps and approval / sign-offSide-by-side comparison of different draftsLimited editing of drafte.g. selection of some specific options that remain undecidedApproval of drafts for communication with other partiesFinal sign-off of agreed expressionsFunctional requirements (5)Communication of license expressionsONIX-PL XML format for machine-to-machine communicationPage view for general review purposes can be saved in various XML-based formatsXHTML for web reviewMicrosoft Office XML (Word, Excel,.)OpenOffice XML.Drafting system design principlesSystem must support all the ONIX-PL license drafting scenariosSystem must meet the functional requirements for each user roleSystem must encourage the use of public templatesSystem must be intuitive to usefor persons with adequate knowledge and experience of the drafting of licensesDrafting system architectureWeb-based, client-server architectureWeb server can deliver appropriate functionality to different types of user employing standard web browser technologyLimits requirement for system development to server-sidegeneration of user form and page views and associated functionalityback-end expression validation and communication functionsNetwork-based or stand-aloneDrafting system architectureONIX-PLLicenseExpressionServerWebServerPrivateTemplatestoreLicensestoreWebBrowserOtherONIX-PLLicenseExpressionServersPublicTemplateServerPublicTemplatestoreLocalprintingInternetDrafting systemUser interface design (1)Forms viewDifferent kinds of clause grouped into overlapping sheetsselectable by sheet tabsavoid scrolling as far as possibleEditable fields using standard user interface control objectstext boxes, drop-downs, check-boxes, radio buttons, action buttonsPop-ups for help and for adding annotationsUser interface design (2)Page viewDefault format will be HTMLviewable in same web browser application as Forms viewOption to choose alternative formatsfor prettier printingfor sharing with users who dont have access to the license expression server.User interface design (3)Template design viewSelection of clauses to include in templateDrag and drop approach?Tick-box approach?Unlikely to get it right first time!TimetableCompletion of system design specification by mid-July 2006First implementation, subject to funding, during last quarter of 2006