Semantics-enabled Web API Organization and Recommendation

Size: px

Start display at page:

Download "Semantics-enabled Web API Organization and Recommendation"

Randolph Quinn
8 years ago
Views:

1 Semantics-enabled Web API Organization and Recommendation Devis Bianchini, Valeria De Antonellis, Michele Melchiori Department of Information Engineering Università di Brescia - Italy 1

2 Fast Web app development: Deployment of situational, short-living Web applications with focus on Web Interface integration of components independently originated from third parties and that are made available through Web APIs 2

Interface integration of components independently

3 Fast Web application development Which open issues? Allowing a Web designer to explore and understand the space of available APIs: dynamicity of this space and large number of available APIs (>4k APIs in ProgrammableWeb.com) heterogeneity in Web API description limited time usually allocated for the development of this kind of Web applications Our contributions: 1. A browsable registry of semantics-enriched Web APIs 2. Semi-automated selection patterns for Web APIs aggregation 3

of available APIs (>4k APIs in ProgrammableWeb.

4 Our vision Focus of this talk We rely on existing technologies and tools See [1] [1] D. Bianchini, V. De Antonellis, M. Melchiori. A semantics-enabled Web API registry, Int. Workshop on Web Semantics,

5 Talk Outline Web API organization in a semantics-enabled registry Web API Selection patterns The prototype tool implementation Conclusions and future work 5

6 Semantic annotation of Web APIs (I) Web APIs are usually described using plain, unstructured HTML semantic annotation of Web APIs is still a difficult task Few efforts have been made to solve these limitations Web Application Description Language (WADL), to propose a counterpart of the WSDL standard for WSDL/SOAP-based Web Services (too complex, not widespread) Combined use of hrests (to structure Web API description) and MicroWSMO (for Web API semantic annotation) 6

Description Language (WADL), to propose a counterpart of the WSDL standard for WSDL/SOAP-based Web Services (too

7 Semantic annotation of Web APIs (II) Web APIs are usually described using plain, unstructured HTML - semantic annotation of Web APIs is still a difficult task Semantic annotation of APIs in our framework is therefore performed according to the steps suggested in the SWEET tool [2]: (a) (b) (c) identification of elements (that is, operations, inputs, outputs) in the unstructured HTML document which represents the API, to produce an hrests description search for ontologies suitable for elements annotation and of taxonomies of categories for API classification annotation and classification of the API according to the MicroWSMO notation [2] M. Maleshkova, C. Pedrinaci, and J. Domingue. Semantic annotation of Web APIs with SWEET. In Proc. of 6th Workshop on Scripting and Development for the Semantic Web,

document which represents the API, to produce an hrests description search for ontologies suitable for elements annotation and of taxonomies of categories for API classification annotation and

8 SWEET-style annotation (I) <div class= service id= svc > <p>description of the <span class= label >ACME Hotels</span> service:</p> <div class= operation id= op1 ><p> The operation <code class= label >gethoteldetails</code> is invoked using the method <span class= method >GET</span> at <code class= address > with <span class= input >the ID of the particular hotel replacing the parameter <code>id</code></span>. It returns <span class= output >the hotel details in an <code>ex:hotelinformation</code> document.</span> </p></div></div> Example hrests description 8

9 SWEET-style annotation (II) <div class= service id= svc > <p>description of the <span class= label rel= model href= ecommerce.owl#hotelreservation >ACME Hotels</span> service:</p> <div class= operation id= op1 ><p> The operation <code class= label >gethoteldetails</code> is invoked using the method <span class= method >GET</span> at <code class= address > with <span class= input >the ID of the particular hotel replacing the parameter <code>id</code></span>. It returns <span class= output >the hotel details in an <code>ex:hotelinformation</code> document.</span> </p></div></div> Insertion of MicroWSMO annotations 9

the method <span class= method >GET</span> at <code class= address >http://example.

10 W i = uri i,cat(w i ),OP(W i ),EV(W i ) op l OP(W i ) op l = method l,addr l,in(op l ),OUT(op l ) ev m EV(W i ) ev m = type m,out ev (ev m ) concept set of concepts set of concepts 10

11 Functional similarity between Web APIs A Web API descriptor W i is functionally similar to another Web API descriptor W j if: 1. The categories of W i and W j are compatible 2. Sim IO (W i, W j ) [0..1] (functional similarity degree) Union of the input sets of all the W j operations Union of the output sets of all the W i operations Concept affinity 11

12 Functional coupling between Web APIs A Web API descriptor W i can be functionally coupled with another Web API descriptor W j if: 1. Coupl IO (W i, W j ) [0..1] (functional coupling degree) Union set of the outputs of the event evi 12

descriptor W j if: 1. Coupl IO (W i, W j ) [0.

13 Web application development scenario (I) Building a Web app from the scratch The Web designer proceeds step by step by selecting a Web API and mapping events with operations 1. The designer specifies a requested Web API in terms of categories, operations and/or inputs/outputs 2. The system suggests APIs that can be coupled with Web APIs already included in the Web app under construction 13

The designer specifies a requested Web API in terms of categories, operations and/or

14 Search selection pattern I need a Web API to find movie theatres 14

15 Search selection pattern I need a Web API to find movie theatres 15

16 Completion selection pattern What functionalities could be added to my Web app? 16

17 Completion selection pattern What functionalities could be added to my Web app? 17

18 Web application development scenario (II) Modifying an existing application The Web designer finds an existing Web app on the Web of Data and desires to replace one of the component Web APIs, since 1. they became unavailable 2. application requirements have been changed 3. the designer needs to improve the QoS of the Web application The system suggests APIs that can substitute Web APIs already included in the Web app under construction 18

they became unavailable 2. application requirements have been changed 3.

19 Substitution selection pattern I need a different Web API to convert coordinates 19

20 Substitution selection pattern I need a different Web API to convert coordinates 20

21 Web API Selection Patterns We define a Selection Pattern as a 4-uple = W,m,, W is the Web API descriptor to be searched for (search pattern), coupled (completion pattern), substituted (substitution pattern) m is the metric used to evaluate the degree of matching (search pattern), of coupling (completion pattern) or similarity (substitution pattern) is the threshold to filter out not relevant Web APIs is a ranking function to present the suggested Web APIs W i W j m (W,W i ) m (W,W j ) 21

Web API Selection Patterns Goal = W Goal, m Goal, Goal, < Goal, Goal = search Goal = completion Goal = substitution Purpose: to provide the designer with APIs matching the request W Goal, So m Goal

22 Web API Selection Patterns Goal = W Goal, m Goal, Goal, < Goal, Goal = search Goal = completion Goal = substitution Purpose: to provide the designer with APIs matching the request W Goal, So m Goal is defined on the basis of Sim IO () Purpose: to provide the designer with APIs having high coupling with the W Goal already in the Web app So m Goal is defined on the basis of Coupl IO () Purpose: to provide the designer with APIs matching the descriptor W Goal, already in the Web app AND having high coupling with descriptors W J connected to W Goal, in the application So m Goal is defined on the basis of both Coupl IO (), Sim IO () 22

23 Prototype: Browsing by coupling 23

24 Conclusions and future work We proposed techniques for fast Web app development based on: Organizing Web API descriptors according to similarity and coupling criteria Exploiting in a semi-automated way this organization by means of selection patterns to support the application design Future work: Additional suggestion metrics (e.g., collective knowledge) Performing experiments on real datasets Developing a complete framework for Web API-based development (e.g., semi-automatic generation of Javascript glue code) 24

25 25

SmartLink: a Web-based editor and search environment for Linked Services

SmartLink: a Web-based editor and search environment for Linked Services Stefan Dietze, Hong Qing Yu, Carlos Pedrinaci, Dong Liu, John Domingue Knowledge Media Institute, The Open University, MK7 6AA,