Download JAR files tagged by service with all dependencies

iServe Integrated Engine provides a complete an integrated local version of iServe to be used within Java Applications. This module provides integrated programmatic access for the deployment and interaction with iServe engines. iServe is what we refer to as service warehouse which unifies service publication, analysis, and discovery through the use of lightweight semantics as well as advanced discovery and analytic capabilities. iServe provides the typical features of service registries and additional functionality that exploits service descriptions, service annotations and further data gathered and derived from the analysis of these descriptions, data crawled from the Web, periodic monitoring and user activities.

iServe is what we refer to as service warehouse which unifies service publication, analysis, and discovery through the use of lightweight semantics as well as advanced discovery and analytic capabilities. iServe provides the typical features of service registries and additional functionality that exploits service descriptions, service annotations and further data gathered and derived from the analysis of these descriptions, data crawled from the Web, periodic monitoring and user activities. iServe builds upon lessons learnt from research and development on the Web and on service discovery algorithms to provide a generic semantic service registry able to support advanced discovery over both Web APIs and WSDL services described using heterogeneous formalisms.

The Virtuoso server module (ks-server-virtuoso) provides an implementation of the Triple Store server-side component (API in ks-triplestore) on top of the OpenLink Virtuoso triple store, a scalable native code triple store that is accessed as an external service. The Virtuoso Sesame driver, which builds on the Virtuoso JDBC driver, is used to remotely access the Virtuoso server for writing data and performing SPARQL queries. For performance reasons, data modification is performed in a non-transactional way, with the module managing possible failures in a way that trigger the external repopulation of the Virtuoso triple store starting from the master copy of data stored in the Data Store component.

This is the main aggregator for all implementation code shared between modules. Each module contains one or more service interfaces, exposed statically using "X_" prefixed classes. Core modules will define their API interfaces, their static accessor, and often a "plain-jre" default implementation which can be replaced by injection override. There must be zero external dependencies in any core modules. A low-performance, low-feature default is preferred over thick, dependency-ridden shared inherits.