SemanticWebImport

From Gephi:Wiki

SemanticWebImport Template:SemanticWebImport Implemented Template:SemanticWebImport Import

Contents 1 Licensing 2 Videos 3 Description 4 General Description of the GUI 5 Use 6 BBC Preset Examples 7 Using Local Files 8 Access with REST 9 Access with SOAP

Licensing

This plugin is developped inside Inria, by the Wimmics research team, with the support of the Dream team.

This plugin is made available through the CeCILL-B licence.

Videos

The main page for the following videos can found at SemanticWebImport Plugin Videos.

• Installation of the plugin
• Overview of the parts of the plugin
• Access to local RDF data

Description

The SemanticWebImport plugin is intended to allow the import of semantic data into Gephi. The imported data are obtained by processing a SPARQL request on the semantic data. The data can be accessed following three manners:

1. by accessing local rdf, rdfs, rul files and using the embedded Corese engine to apply the SPARQL request;
2. by accessing a remote REST SPARQL endpoint. In that case, the SPARQL request is applied remotely and the graph is built locally by analyzing the result sent by the REST endpoint;
3. by accessing a remote SOAP SPARQL endpoint. As for the REST endpoint, the resulting graph is built from the result returned by the endpoint.

We begin by showing how to make run the preset examples which come with the plugin. Then we detail the three drivers allowing to import semantic data.

In all the following cases, it is required there is a currently opened project, otherwise the graph can not be built.

General Description of the GUI

The SemanticWebImport plugin is made of the following parts:

1. The selector for the SPARQL driver to be used, i.e. how the semantic data can be accessed. Currently, the choice can be made between (i) access to local data through the Corese engine; (ii) access to a remote REST SPARQL endpoint; (iii) access to a remote SOAP SPARQL enpoint.

2. The parameters associated which each driver; See the description of each driver below.

3. The SPARQL editor to enter a SPARQL request that extract the data used to build the graph. It is mandatory to be a construct request.

4. The selector for preset examples and the load button to activate them;

5. A log window to obtain hints about what is happening;

6. The start button and a checkbox to select whether the current workspace must be cleaned before starting to build the graph from the result of the SPARQL request.

Use

To use the plugin, follow these steps:

1. choose a driver between the three available (part 1);
2. parameterize the driver (part 2, and see the following sections for more details);
3. enter the SPARQL request, making sure it is a construct SPARQL request. All the relations "?x ?r ?y" in the construct part are creating nodes ?x and ?y and an edge to connect both;
4. In part 6, choose if the workspace has to be reset;
5. In part 6, launch the processing (part 6) by clicking on the start button.

BBC Preset Examples

To obtain the BBC example, foolow the following steps:

1. Create a new empty project;
2. Select in the Load Examples/Configurations (i.e. the part 4 in previous image) the "BBC" example;
3. Click on load. The GUI should be similar to
   

   

   View of the SemanticWebPlugin after loading the BBC example
   .
4. Launch the SPARQL driver by clicking on the start button (part 5). The BBC example connects to a SOAP SPARQL endpoint, and the SPARQL request is processed remotely, then the result is returned to the plugin. The graph obtained should be similar to
   

   

   View of the SemanticWebPlugin after processing the BBC example
   .

Using Local Files

The Corese driver allows to process locally a SPARQL request on RDF files. The RDF files can be provided as:

1. local files.
2. internet files, i.e. beginning with http://. For example, http://dbpedia.org/data/The_Beatles.rdf can be added and used as an input.
3. resource files (i.e. RDF files coming from a jar file run by gephi). The file must begin with /. Three such files are coming embedded inside the plugin, /fr/inria/edelweis/examples/human_2007_09_11.rdf, /fr/inria/edelweis/examples/human_2007_09_11.rdfs, /fr/inria/edelweis/examples/human_2007_09_11.rul.

The CoreseDriver is made of three parts:

1. buttons allowing to add a local file (+) or remove a resource (-);
2. the list of resources;
3. a text field and a button to add external resources, i.e. rdf files on the internet.

Access with REST

The REST SPARQL driver allows to make process a SPARQL request on a remote SPARQL endpoint with REST interface.

The Rest panel is made of the following parts:

1. the URL for the endpoint;
2. the name given to the query tag. Most often it is "query"; some endpoints use "q".
3. some parameters to be added the request. For example "debug=on" can be provided by:
   1. Writing "debug" instead of "REST name" in the part 3.
   2. Writing "on" instead of "REST value" in the part 3.
   3. Clicking on +.

Access with SOAP

The SOAP SPARQL driver has a single parameter, the URL of the endpoint.