11. Release Notes¶
11.1. Experimental features¶
From time to time, RDFox releases may include experimental features not intended for use in production. In these cases, the affected APIs will clearly be labeled “EXPERIMENTAL” meaning that they may change or disappear entirely without notice in later versions. Further, Oxford Semantic Technologies offers no support for any API labeled in this way.
If you have feedback or questions regarding any feature of RDFox, whether experimental or not, we would be grateful to hear it via any of the normal channels.
Fix bug where RDFox fails to start with a file in use error on Windows.
Fix bug that causes RDFox to end if the terminal window is resized or a screen session is reconnected during login prompt.
Fix bug where data store snapshot files are not deleted when data stores are deleted.
Fix bug that caused RDFox to hang or crash if an attempt is made to import invalid data.
Allow Ctrl+C to interrupt import operations.
Allow Ctrl+C to interrupt loading of persisted data stores during restart.
The term ‘user’ is replaced by the term ‘role’ in all JRDFox APIs related to authentication. For example
tech.oxfordsemantic.jrdfox.client.DataStoreConnection.getUserName()is replaced by
When creating server connections for the first time via JRDFox APIs, the default role name and password are now “guest” and “guest”.
All references to the namespace
org.semanticweb.owlapihave been removed from the JRDFox code base and the owlapi-*.jar file is no longer included in the RDFox distribution. Consequently the following features are no longer available:
the overload of
tech.oxfordsemantic.jrdfox.client.DataStoreConnection.importDatathat accepted an
the command line facility to generate a Datalog program from an OWL ontology
Correct the behavior of
owl-in-rdf-support is no longer EXPERIMENTAL.
The JRDFox features that make use of owlapi-*.jar (one of the DataStoreConnection importData methods, and the GetRules utility) are now deprecated. This dependency will be removed in a future release of RDFox. Import of OWL documents (in Functional Style and Turtle syntaxes) will continue to be supported by the remaining importData methods.
Fix bug where a crash may occur when the Java or REST interfaces are used to import large data sets (RD-531).
The MIME types for the RDFox-proprietary SPARQL answer formats have been consolidated to us the
New proprietary SPARQL answer formats have been added that abbreviate IRI prefixes in the result
The binary answer format has been changed
Renamed the parameters for obtaining diagnostic information in the REST API
Added calls to all APIs for retrieving server-level diagnostic information
Removed the query domain parameter in all APIs for exporting data and added the ability to pass in arbitrary key-value pairs
Adapted the syntax of the
exportcommand to support the change from the previous item
Optimized the shell interface by not requiring file names to be enclosed in quotes
Embedded an experimental HTML application which is served from
/consolewhen the endpoint is running
Only add the
Access-Control-Allow-Originheader to HTTP responses if the user has configured the allowed origin
Added support for importing from files containing axioms represented in OWL 2 functional-style syntax.
Added experimental support for OWL 2 axioms translated from imported RDF data.
SPARQL query evaluation has been reworked to improve performance and eliminate errors in the returned solution for a small number of query types.
RDFox and JRDFox now require a license file
Improved support for
RESTful API supports the HTTP X-HTTP-Method-Override request parameter to allow HTTP PATCH requests to be made from client code that does not directly support PATCH (e.g. Java HttpURLConnection)
Improved support for
xsd:decimalon macOS and Linux
Added support for the following SPARQL 1.1 functions:
RDFox now retains the data types of literals in the input — that is,
xsd:intis no longer normalized to
xsd:integer, and similarly for other derived data types (RD-194)
Added initial support for
Performance improvements in the evaluation of most builtin functions (RD-196)
convert-unknown-datatypes-to-stringswere replaced with options
import.invalid-literal-policydescribed in Section 6.2.2
Shell variables containing backslash characters are now correctly expanded on the command line (RD-219)
There is no restriction on the number of files that can be imported on a single line in the shell (RD-89)
SSL/TLS for the RESTful API using openSSL (Windows, macOS, Linux) and Secure Transport (macOS only)
Fixed a bug where sending
DELETErequests was incorrectly detected as having a body
Extracted the data store statistics into separate data structures that can be administered using the various APIs (RD-27); thus, there is now a way to update the statistics using the REST API
statsshell command to manage statistics, and deprecated the
updatestatscommand in favor of
infoshell command that merges the functionality of the old
rulestatscommand, and the
ruleplancommand; added the option to print summary of the information about a data store; removed the
Fixed a bug where tuple tables imported from a data source could have repeated column names
Extended the OWL translator to support data types and data type restrictions according to the OWL 2 RL specification (RD-53)
Improved handling of out-of-memory exceptions (RD-50)
Improved handling of situations when the capacity of a data store is exceeded (RD-90)
Fixed a bug where parallel import of Turtle files would sometimes slow down or even crash after loading some number of files
Improved the performance of importing large numbers of
Fixed the bug where incrementally added rules sometimes were not handled correctly (RD-120)
LIMITcan not occur in a SPARQL query in an arbitrary order
The RDFox command line supports common line editing functions including arrow-key navigation and command history on platforms where this was previously unavailable (macOS and Linux)
Commands used when starting RDFox have been revised (now
daemon) and options have been added to enable logging of API calls and to set a maximum allowable memory size.
Added support for cryptographic hash functions MD5, SHA1, SHA256, SHA384 and SHA512 in rules and queries
LCASE()functions are Unicode aware and use the unconditional case mappings as defined by the Unicode Standard 11.0 (RD-8)
REPLACE()SPARQL 1.1 functions (RD-5)