Common use of Workflows Clause in Contracts

Workflows. PANACEA has delivered various workflows that implement the way web services are chained as sequences, with specific input and output (all are at PANACEA myExperiment). For instance, a workflow that consists of a sequence of two "calls" to web services and may take as input a set of URL and identify the language(s) in which they are written and hence give as out a table with pairs (URL, language). It could be chained with one that crawl all URLs that are in a given language. Such work flow could be (identify-languages (list of URLs) + Crawl (URL, Language=Fr). (1) (Input = set of URLs) 🡺 Web services 1: identify languages 🡺 (output (URLs, languages) (2) (input (URLS, Languages) 🡺 Web services 2: Crawl (URLs, Language=Fr) and store 🡺 output (set of XML, HTML, PDF, … pages stored on a given address) It is clear that more sophisticated workflows could be designed, requiring deep analysis and more creativity and hence triggering the application of copyright and other property rights. Some of the workflows are illustrated by the diagrams given below. More details are given in the appendix elaborating on legal issues. The consortium took seriously all aspects related to the ownership of workflows, both to ensure that the exploitation within the consortium is done in a cleared legal framework as well as to ensure that such assets can be licensed to third parties under clean, easy to understand and implementable licensing schema. From a technical point of view, the consortium can easily work out the arguments about the added value of its achievements but it is also crucial that the legal aspects involved behind such a paradigm should not be neglected. When dealing with workflows, data are not only stored on the server of the different web services, but are also “travelling” between web services. To guarantee the privacy of the data transferred from one web service to another, the transfer protocol must be secured so as to avoid any security bridge. Indeed, data going from one server to another (e.g. in the case of a workflow process) or from a client machine to a server (e.g. in the case of a single web service process) should be secure enough so as not to be corrupted or retrieved by a third user. In PANACEA, this process is secured by using SOAP8 (Simple Object Access Protocol), which allows to reach a sufficient level of security since SOAP transports data using both SMTP and HTTP (and although not implemented in the current version, potentially HTTPS). Workflows are, as explained above, original works produced by the partners and that are relying on a LGPL license of TAVERNA. The consortium decided to offer them freely and under a Creative Common license (most existing Workflows are now published with CC_BY_SA 3.0 licenses). ❖ Summary and Plan: 8 ▇▇▇▇://▇▇▇.▇▇.▇▇▇/2002/07/soap-translation/soap12-part0.html It is the plan of the consortium (in particular ▇▇▇▇) to exploit such workflows to design new processing capabilities for potential users. In many cases, users do not care about the tools used to implement some particular processing. But in other cases this may happen, for instance we have seen users requiring some piece of textual corpora to be annotated by several taggers (multiple annotations), followed by the use a web-service executing a "majority-vote" to select the best tag of a given word. In this case, PANACEA workflow engine can be used for this purpose. Several members of the consortium intend to offer services of this kind to the community. The business model behind the exploitation of the platform is part of section 5.