11111

The In4mium Components Part 1: Input Modules

The In4mium components

As mentioned in previous blogs In4mium has developed a series of modules that allow your business to take advantage of semantic technology wherever and however you wish to apply it.
The In4mium modules give you the ability to create services, ETL workflows, ESB containers and much more injecting semantic technology where you need it whilst allowing you to use your existing architecture and platforms for deployment. What’s more you don’t have to write a single line of code or learn complex APIs or buy into an expensive platform to take advantage of any of it. You can even mix and match with traditional technology modules allowing you to gain the best from all worlds.

The In4mium Palette
In4mium has extended the Talend palette with a series of modules that allow you to utilise semantic technologies as you need them. These modules have been categorised under the concepts of Data Management, Input, Output and Manipulators
Palette
In this first blog we will introduce to the In4mium input modules highlighting what you can achieve with them.

Input Modules
We have developed a series of modules that can retrieve RDF data and place it in the workflow from a variety of common sources.
In short the In4mium input modules allow RDF data to be brought into a Talend workflow.

Palette2

RDF Files
The simplest of these reads RDF data from files. A variety of formats is supported so you don’t have to worry about file conversions.

Triple Stores.
RDF data can be brought into a workflow directly from a variety triple stores. Think of these modules as database connectors for semantic technologies. Currently we support the use of TDB, SDB and Allegrograph. Our range can be expanded very quickly and easily so if you have a favourite triple store don’t worry.
The triple store connectors allow the use of SPARQL select or construct queries for the data retrieval.

Sparql Endpoints
The In4mium modules for SparqlEndpoints allow you to connect and query any SparqlEndpoint. Since many triples stores expose SparqlEndpoints you can access your RDF data regardless of the underlying technology utilised.

Miscellaneous Modules.
In4mium also has a couple of miscellaneous modules for bringing RDF data onto a workflow.
The first of which is the OPSRestClient that allows you to connect with Open PHACTS service. This is a beta module that currently allows the retrieval of chemical information. Whilst anyone can call the Open PHACTS service directly our module enables a simple configuration for the user to select what it is they require. It’s that simple. No need to know the actual API call itself… we handle all that for you.
It’s a great way to utilise the Open PHACTS service that allows you to combine its data with anything else.
Our second module allows the creation of a D2RQ connection to a relational database allowing RDF data to be retrieved using a SPARQL query. Whilst D2RQ can be hosted as an endpoint in its own right we find this module extremely useful in a workflow without having to rely on other systems and technology implementations. Of course if you already have a D2RQ Sparql endpoint hosted you can simply use out SPARQL endpoint modules to query it.

We don’t dictate how you want to setup your system we enable to achieve goals quickly and simply and in a sustainable extensible manner.

In future blogs we will detail the use of the In4mium modules in workflows demonstrating how easy it is to create sophisticated sustainable systems with them.

This entry was posted in Components, Modules, RDF, Semantic Technology, Semantic Web, Talend, Uncategorized. Bookmark the permalink.