RDFox provided by graph.build

Federated queries are now supported in accordance with the SPARQL 1.1 Federated Query specification.

The existing GET / and GET /datastores//info REST APIs, which provide information about the whole server or a particular data store respectively, now support the OpenMetrics 1.0 response format, enabling monitoring of RDFox servers using Prometheus or compatible systems (RD-2377). To improve the clarity and consistency of metrics for the newly supported format, the properties returned by these APIs (and by the serverinfo extended shell command and the equivalent JRDFox and C/C++ APIs) have been renamed and their meanings documented (see Section 16.5.7). Java APIs have additionally been updated to include enum types, allowing for further client side calculation/aggregation using these values.

Added a new server parameter http-remotes to enable integration with external HTTP(S) endpoints that require authentication. See Section 4.3.3 for details (RD-2374).

Added an EXPERIMENTAL built-in function, SEMSIM, for semantic similarity search over text embeddings (RD-2437). See Section 9.2.4 for details.

Changes to HTTP request logging (RD-2431 and RD-2421):

Enhanced the endpoint's extended logging format (ELF) to optionally record request start events, configurable via the new elf-logger-recorded-events server parameter.

Added new elf-logger fields: x-timestamp (the timestamp at log creation) and x-request-state (the request state at time of logging, e.g., "request_start", "request_finish", "request_error").

Updated the default value of the elf-logger-fields parameter from date time cs-method cs-uri-stem sc-status sc-bytes time-taken to x-timestamp c-ip cs-method cs-uri-stem cs(RDFox-Request-ID) sc-status sc-bytes time-taken x-protocol-error .

Introduced a new request logging format, elf-json, which records logs in JSON. The fields and events logged by this logger are configured with the same parameters (elf-logger-fields and elf-logger-recorded-events) as the existing elf format.

See documentation for these changes in Section 19.2.

One can now extract and merge statistics for individual queries, enabling troubleshooting of query plans without access to user data (RD-2405).

Added an endpoint parameter, localhost-only to specify whether RDFox should listen on all network interfaces or only on the loopback interface (RD-2406). See Section 19.2 for details.

Deletions and additions in a transaction now cancel out precisely during reasoning (RD-1985).

All APIs now support a way to determine whether an update should be handled using incremental or "from scratch" reasoning (RD-1987).

ODBC and PostgreSQL data source connectors now support connections to databases containing unsupported data types. Such data can then be cast or converted during tuple table construction (RD-2455).

The functionality of the /transaction REST API key was merged into ; moreover, the /transaction key was deprecated and will be removed in future (RD-2353).

The existing allowed-schemes-on-load server parameter has been renamed to allowed-url-schemes-on-import. This parameter is used to control which schemes are allowed when importing data from external sources (RD-2374).

Fixed an issue where numeric (Integer, Decimal and Double) values equal to the lower numeric limit (e.g. Integer -2^63) were wrongly reported as outside the supported range (RD-2388).

Fixed an issue where JRDFox Rule object creation may introduce additional expression nesting, leading to unexpected results when listing or deleting rules (RD-2388).