Tools to help publishers and libraries produce OLT licences

1、Tools to help publishers and libraries produce OLT licencesDesign for an ONIX-PL license drafting system,Francis Cave,ONIX-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 Licensee

2、s (e.g. libraries) creating ONIX-PL interpretations of publisher licenses Licensees creating ONIX-PL expressions for their own preferred usage policies and other terms,ONIX-PL license drafting scenarios,Starting point for creating an ONIX-PL license expression will always be a license template (publ

3、ic 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 licensees,ONIX-PL license drafting scenarios,But where do the templates come from? Specialist function required for the creation of templa

4、tes 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 / owners,ONIX-PL license drafting scenarios,Different types of involvement in the creation

5、 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-off,ONIX-PL license drafting scenarios,Drafting ONIX-PL expressions will

6、 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-PL,User roles,Template and clause developer License expression / interpretation cre

7、ator Template selector Optional clause selector Form-filler License expression reviewer / approver,Functional 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 requir

8、ed 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 template,Functional requirements (2),Drafting of expressions / interpretations for specific licenses Selection of appropriate template Pub

9、lic 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 valu

10、e lists,Functional 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 O

11、NIX-PL,Functional 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-of

12、f 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 expressions,Functional requirements (5),Communication of license expressions ONIX-PL X

13、ML 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 S

14、ystem 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 licenses,Drafting system architecture,Web-based, client-server architecture Web serve

15、r 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

16、-based or stand-alone,Drafting system architecture,ONIX-PL LicenseExpressionServer,WebServer,PrivateTemplatestore,Licensestore,Public TemplateServer,PublicTemplatestore,Localprinting,Internet,User interface design (1),Forms view Different kinds of clause grouped into overlapping sheets selectable by

17、 sheet tabs avoid scrolling as far as possible Editable fields using standard user interface control objects text boxes, drop-downs, check-boxes, radio buttons, action buttons Pop-ups for help and for adding annotations,User interface design (2),Page view Default format will be HTML viewable in same web browser application as Forms view Option to choose alternative formats for prettier printing for sharing with users who dont have access to the license expression server.,User interface design (3),Templ