Exporting and interactively querying Web service-accessed sources

Abstract

The CLIDE System assists the owners of sources that participate in Web service-based data publishing systems to publish a restricted set of parameterized queries over the schema of their sources and package them as WSDL services. The sources may be relational databases, which naturally have a schema, or ad hoc information/application systems whereas the owner publishes a virtual schema. CLIDE allows information clients to pose queries over the published schema and utilizes prior work on answering queries using views to answer queries that can be processed by combining and processing the results of one or more Web service calls. These queries are called feasible. Contrary to prior work, where infeasible queries are rejected without an explanatory feedback, leading the user into a frustrating trial-and-error cycle, CLIDE features a query formulation interface, which extends the QBE-like query builder of Microsoft's SQL Server with a color scheme that guides the user toward formulating feasible queries. CLIDE guarantees that the suggested query edit actions are complete (i.e., each feasible query can be built by following only suggestions), rapidly convergent (the suggestions are tuned to lead to the closest feasible completions of the query), and suitably summarized (at each interaction step, only a minimal number of actions needed to preserve completeness are suggested). We present the algorithms, implementation, and performance evaluation showing that CLIDE is a viable on-line tool. ACM Reference Format:Petropoulos, M., Deutsch, A., Papakonstantinou, Y., and Katsis, Y. 2007. Exporting and interactively querying web service-accessed sources: The CLIDE system.

Data services

“…For a schema-based external model, recent work proposed tools to help users author only answerable queries, for example, CLIDE. 41 These tools utilize the schemas and restrictions of the service-enabled data sources as a basis for query formulation, rather than just the externally visible data service metadata, to guide the users toward formulating answerable queries. More work is needed here to handle broader classes of queries.…”

Optimizing DaaS Web Service Based Data Mashups

“…In our system, DaaS Web services are modeled as RDF views over domain ontologies where primary key constraints are defined explicitly by the concepts' skolem functions, thus the discussed Primary key based optimizations are included by default in our query processing model. The CLIDE System [12] addresses the problem of semi-automatic interactive data mashup query formulation over a set of data services. The system helps mashup creators formulate feasible queries over data services by proposing a set of actions with which the query remains answerable.…”

On a proposal to integrate web sources using semantic-web technologies

“…Building and maintaining mappings automatically is appealing insofar this reduces integration costs and relieves users from the burden of writing them, checking whether they work as expected or not, making changes if necessary, and restarting this cycle [5], [49]. Mappings can be of various types but, in the bibliography, approaches that generate them automatically focus on two, namely: correspondences and executable mappings.…”

“…Furthermore, Parreiras et al [47] transforms handcrafted OCL-like executable mappings into SPARQL executable mappings. Note that this approach is usually not appealing since handcrafted executable mappings increase integration costs [5], [49]. • They interpret correspondences in isolation, such as Mocan and Cimpian [42], which transform each correspondence into an executable mapping in isolation; however, correspondences are inherently ambiguous and they need to be interpreted as a whole to perform the data translation task [6], [50].…”

“…One of the most important challenges is to make these software applications interoperate with each other to keep their data synchronised or to create new functionality [22], [27]. This interoperation is usually handcrafted, which is difficult to build and maintain, so integration costs are highly increased [49], [63].…”