Friday, April 14, 2017

Documenting Sesame and RDF4j

 Sesame 4.1.2 became RDF4J 2.0. Documentation for rdf4j is here: .
An older version of Sesame, 2.7, is documented here:

Sesame also provided a JDBC like interface:

In PowerAquaOpenSource there is a jar:

openrdf-sesame-2.3-pr1-onejar in ./PowerAquaOpenSource/myLib/sesame2/

In PowerAquaLinked there is a jar:

a-openrdf-sesame-2.3-pr1-onejar.jar in ./poweraqualinked/WEB-INF/lib/

The jar files in PowerAqua contain all of the relevant Sesame libraries for programming applications.

On source-forge I was able to download: openrdf-sesame-4.1.2-sdk.tar.gz. This contains complete binaries in jar files.


Now I can play with the downloaded binaries for sesame-4.1.2:

Looking at:

I note that I can store the repositories on the file system, or on a sesame server.

When I chose ./openrdf-sesame-4.1.2/bin/".sh I get SYSTEM for the command "show repositories."

I get no server for "connect http://localhost:8080/openrdf-sesame."

Either I have no server, or it is not running on port 8080. port 8080 is the default.
(Documentation on setting up a server: ,
A server is not needed if sesame is strictly used a library to program against.

I look at the code for the Sesame2Plugin:

and I notice that for ./Sesame2Plugin/ there is:

import org.openrdf.repository.Repository;
import org.openrdf.repository.RepositoryConnection;
import org.openrdf.repository.http.HTTPRepository;


public static void createDBFromURI(String sesameServerPath, String repositoryName, String filePath, String format)

System.out.println("Uploading into repository " + sesameServerPath + repositoryName);
Repository myRepository = new HTTPRepository(sesameServerPath, repositoryName);
RepositoryConnection con = myRepository.getConnection();

Comparing this to  " Accessing a remote repository" in tells me that connects to an existing sesame repository.

In the other file in ./Sesame2Plugin/

looks like it is accessing a preexisting sesame server...

Thus for PowerAqua-decompiled/

No comments:

Post a Comment