-
Notifications
You must be signed in to change notification settings - Fork 1
New Component Integration
The integration of new components in the generator depends on the interfaces offered by the component:
- REST-based APIs. The most straight forward integration consisting of a stand alone component application that provides services. For integrating a REST-based application, it is required to develop a GUI within the Workbench.
- Web applications. The component provides all its functionality within an application and has it own user interface. Some communication between the component and the integration application has to be defined, and the user experience is compromised because users have to deal with different interfaces.
- Libraries. If the component is available as a library (e.g. jar), a component interface is required, and in some cases adaptation of communication and data processing is also necessary.
In any case, in order to integrate components it is required some front-end development. For adding a new component in the workbench follow next steps:
-
Describe the component to the configuration file: The components are described using a vocabulary developed within the Linked Data Stack team. The Linked Data Integration Schema, provides the vocabulary to describe the services offered by a component, its version, the required data for using it (i.e. user, password, working directories, etc). And a classification within the Linked Data Lifecycle. Thus, the developer has to add into the system-components.ttl the description of the service of the new component to integrate. Therein, the developer can see the different descriptions of existing components and can use one of those as an example.
-
Create the GUI
-
Add the Routes to the GUI
-
Activate the component
#Home
- Dashboard
- Import RDF
- Sparqlify
- TripleGeo-Sercvice
- Virtuoso SPARQL Endpoint
- Mapify
- Facete
- OntoWiki
- LIMES
- FAGI-gis
- DEER
- Public-Private Data Coevolution