Our approach is fully implemented and has been tested with live Web services. We propose two demonstration scenarios that are designed to illustrate the approach.

 

Scenario 1 - Mapping New WS

Path Alignment

In the screen shot above is presenting the procedure of adding a new Web Service method. The user should give the url of the web service then she should specify the type of the input value that the web service expects. If the input type is not an actual value like a name of a person or a title of a book but it is e.g. an identifier, the user may select the "Undefined" option. If there is a suffix for the url of the WS the user can add it in the box next to the input value menu. After that the user has to give a name for the new Web Service method. A query over the Knowledge Base is generated and presented in the text area below. When the user preses the button "Get Input Values!" the query is executed and the values are retrieved from the KB. If the user wants to inspect the retrieved input values she can do it by using the menu bellow. By pushing the "Next!" button the user can continue with the procedure of the Paths Alignment.

 

 

Path Alignment

Above, there is the interface that presents the paths alignment for a Web Service. The user determines the API and the Web Service and then the path pairs are showing in the table. In the first column are presenting the paths from the xml documents that are exported from the WS and in the right column the rdf properties from the KB. If the user wants to go deeper into the actual values she should select a path pair in the table and then push "Inspect Value!". After that will be able to select the input value that wants to inspect. In the table bellow are showing the actual values that exist in the xml document and in the KB under the specific paths. Moreover, by pushing the button "Show Exceptions!" the user would be able to inspect the input values where the path pairs do not match, like in the screenshot above.

 

 

 

Path Alignment

After that the user can observe the classes and relations alignment between the KB and the WS, producing by our system. The API and the Web Service have to be determined and the results are presenting in the area below.

 

 

Scenario 2 - Discovering IO Dependencies

 

Path Alignment

In the above interface is presenting the Input-Output dependencies between the WSs. The User select an API and the WS that she prefers and the result is a graph with the WS that are depending to the given WS. The arrows connect the given WS with the WSs that can take as input a value under a specific path of the xml file outputted by the first WS.