Tata AIG General Insurance Company - Insurer Innovation Award 2024
The Functional Units
1. The Functional Units: Abstractions for Web Service Annotation Paolo Missier Katy Wolstencroft Franck Tanoh Peter Li Sean Bechhofer Khalid Belhajjame Steve Pettifer Carole Goble School of Computer Science, University of Manchester (UK) SWF 2010
To clearly annotate web service we need another layer of abstraction independent to the technology used. In this presentation a number of example to define the FU The work presented here stems from the observation that current annotation models force users to think in term of service interface rather than high level functionality FU: the elementary units of information used to describe a service. Using widely used web service in Life Science we define the FU as configurations and compositions of underlying service operations. FU is limited to the set of operations that are part of the same service.
How many web services are there? What are the API submission statistics for 2008 Is there a graph showing an increase? o 3 million/month accesses to various WS APIs (MSD, BioModels, ES-compute jobs, etc). o 1 million/month compute jobs of which more than 50% are over WS (mostly by systematic users). o 20K unique IPs/month for the whole. Of these Ca. 5K are systematic users and account for the vast majority of job submissions. o User agents covering every single LS programming language have been detected (perl, python, C/C++, C#, Java, Ruby, PHP, etc). o A guess for LSWS: >500 - < 1000 worldwide but growing as specialisation and segregation of methods from monolithic servers offering more than 20 methods takes place. This only includes SOAP (rpc &doclit). REST, JAX-WS and DAS are not included in this estimate. If you count DAS as a type of REST WS, you can say >700 - <1000. I'm being conservative.
Web service providers usually think about themselves first when building web service
Despite a wealth of research over the past few years, service annotations still reflect a interface oriented view rather than a functional view of the service. WSMO Ontologies : Terminology used by other elements Goals : service functionality Web services: the services provided. Mediators: for interoperability between WSMO elements OWL-S Service: web services declaration Service profile: functionality and non-functional properties Service model: service functionality Service grounding: technical aspect of the service SAWSDL W3C recommendation since 2007 Maps WSDL document to a domain ontology
Annotation apply to the entire service or individual operations, they follow the WSDL structure. For the purpose of discovery in registry such as BioCatalogue , this level of abstraction in not always suitable because the set of operations exposed by a service are not always functional tasks.
A means to pool metadata about services in the wild A means to discover and reuse those services A means to curate services A platform for service monitoring and analytics A generic service annotation model for community annotation
Service in the wild worse than we think…we’ve come across these different type of service. Multiple operation->1 task: by annotating these services on individual operation, a gap remains between the users perspective of service operations as tasks with a well-defined function and service providers’ technological view. We argue that this gap can be filled by choosing to annotate at a higher level of abstraction => that’s what we name the FU KEGG: Kyoto Encyclopedia of Genes and Genomes
ChEBI (meaning either Chemical Entities of Biological Interest or Chemistry at the EBI) is a database of molecular entities focused on 'small' chemical compounds. ... The SABIO-RK ( S ystem for the A nalysis of Bio chemical Pathways - R eaction K inetics) is a web-based application based on the SABIO relational database that contains information about biochemical reactions, their kinetic equations with their parameters, and the experimental conditions under which these parameters were measured. This is a concrete example of FU…
Notes: useful for finding alternative services and configuring services
To elicit the FU we can extract sub workflow of tried and testing workflow from workflow repository such as myExperiment…. A single workflow may define multiple FU. Identify FU by parsing the workflow definition from myexperiment Elicitation of FU: Identify the operations and the way they are combined Annotation of FU: annotating inputs and outputs by relating them to concepts from a domain ontology… this can be automated using existing tools such as QuASAR, Meteor-S, Assam. QuASAR ( Quality Assurance of Semantic Annotations for Services) : aims to provide a toolkit to assist in the cost-effective creation and evolution of reliable semantic annotations Web services. Can be used to infer new semantic annotation or verify the quality of existing annotation ASSAM: A Tool for Semi-automatically Annotating Semantic Web Services
![Functional Unit (FU) ,[object Object],[object Object],[object Object],[object Object],SOAP REST DAS OTHERS SERVICE FUNCTIONAL UNIT](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)