3.0.0

RDF4J 3.0 is a major new release of the Eclipse RDF4J framework. Some highlights:

• Major improvements to the SHACL Sail
• Cleanup of core APIs (removing deprecated and obsolete code)
• Preparing RDF4J for Java 11/12 compatibility
• RDF4J Server / Workbench upgrade to Servlet API 3.1

For a complete overview, see all issues fixed in 3.0.

Upgrade notes

RDF4J 3.0 contains several backward incompatible changes. We distinguish changes that affect users of the RDF4J tools (Console, Workbench, Server), changes that affect users of the RDF4J APIs and libraries, and changes that affect third party Sail / Repository implementations. See the linked issues for further details.

RDF4J tools users

• Due to an up upgrade to Spring 5.1, RDF4J Server and RDF4J Workbench now require a servlet container that supports Servlet API 3.1. For Apache Tomcat, that means Tomcat 8 or better. For Eclipse Jetty, it means Jetty 9 or better.
• The RDFS inferencer has changed its default behavior for inferred triples.

rdf4j API/library users

• The deprecated Graph API has been removed. Any code that still uses Graph, GraphImpl, or GraphUtil will need to be rewritten to use corresponding features in the Model API.
• Deprecated methods have been removed from the Model API. Any existing code that uses the deprecated methods will need to be rewritten to use the recommend new methods.
• The deprecated package org.eclipse.rdf4j.model.util.language has been removed.
• The SHACL Sail shape persistence directory has been moved.

third-party sail / repository implementors

• invoking init() (or initialize()) on a Repository or Sail object is no longer mandatory.
• we allow injection of optimizers into a Sail object.
• as part of a massive restructure of our code repositories and the way in which the project is tested, testsuites and compliance tests have been moved and refactored. If you were depending on a particular testsuite and can no longer find it, contact us.

Table of Contents