Feature request: move to RDF4J

[LorenzBuehmann]

Hi,

not sure if anybody knows about this, but it look like the SPARQL plugin still depends on an older version of Sesame which has already been moved to RDF4J ~ 2 years ago. I guess many bugs have been solved since then, performance maybe increased and features added.

I came across this "issue" by this Stackoverflow post and the outcome was that some functions of SPARQL, especially the casting of literals, are not available in the SPARQL plugin of Protege.

For example

SELECT (xsd:integer(str(?o)) as ?o_casted)

will fail although this is part of SPARQL 1.1 standard.

To be honest, I always thought Protege is already using RDF4J and not Sesame, but it's not case given the dependency in the pom.xml.

I found a fix in the RDF4J repository, thus, I assume it will never make the way to Sesame, so there is no simple way to make the SPARQL plugin feature complete and even get rid of possible bugs without moving to RDF4J.

Cheers,
Lorenz

[LorenzBuehmann]

Another reason to upgrade: https://stackoverflow.com/questions/53299218/sparql-support-protege-5

[abrokenjester]

FYI there is a fairly up-to-date Sesame-to-Rdf4j migration guide that documents what changes need to happen to move the codebase across.