CRUD Interface

Access to the CRUD interface is obtained by means of iServeEngine facade. Therein you will get access to the main data managers in charge of services, documents, and ontologies. For convenience iServeEngine provides methods that take care of automatically transforming services prior to importing them, keeping all data managers synchronized, and when necessary, obtaining remote ontologies referred to by the imported services.

iServeEngine engine = iServeEngineFactory.createEngine();

// Get Registry Manager
RegistryManager manager = engine.getRegistryManager();

InputStream in;
List<URI> servicesUris;
for (File ttlFile : msmTtlTcFiles) {
    in = new FileInputStream(ttlFile);
    servicesUris = manager.importServices(in, MediaType.TEXT_TURTLE.getMediaType());
}

List<URI> services = manager.getServiceManager().listServices();

URI svcUri = new URI("http://iserve.installation.org/services/id/1");
Service service = manager.getServiceManager().getService(svcUri);

The Matching Interface

iServe provides a Matching API that can be used programmatically from Java. Although, work is ongoing to provide a more advanced and richer API, you can already work with it within your applications. Should you wish to obtain a Matcher, you can simply do so by means of the uk.ac.open.kmi.iserve.api.MatchersFactory. This factory takes care of locating Matcher implementations by means of a plugin mechanism, and will automatically create the plugin of your choice at runtime. Currently, the code only provides a ConceptMatcher allowing you to find matches between concepts loaded in the server by relying directly on SPARQL queries. Further matches are under development and will be released incrementally.

Below you have an example on how you can create a Matcher.

ConceptMatcher matcher = MatchersFactory.createConceptMatcher(SparqlLogicConceptMatcher.class.getName());

Notifications

In order to enable applications and extensions to react upon changes to the registry, iServe implements a simple notification mechanism based on Guava's EventBus. Applications can register for notifications simply by doing:

manager.registerAsObserver(this);

This will ensure than any change on the Services, Documents or Knowledge Base Managers get automatically reported. Processing the events is simply ensured by implementing a method that takes the event we are interested in as sole argument. The method should be annotated with @Subscribe. See package uk.ac.open.kmi.iserve.sal.events for the list of events supported.

An example on how such a subscription method should be implemented is listed next.

@Subscribe
public void handleOntologyCreatedEvent(OntologyCreatedEvent event) {
    // Code handling the event...
}