Slowly getting there.

  An important fix for TDB2 compaction is now in the codebase.

  The SHACL listener code is merged.

  The GeoSPARQL gml fix has just been merged (this will require users
  to fix any GML data they have and reload).

  UI code is going well.

    Andy

On 05/07/2022 15:27, Andy Seaborne wrote:
The 4.5.0 release was 2022-05-01 so end July, early August would be the next release. It would be good to release so that substantial upcoming features integrate at the beginning of a cycle.


== In this release:

JENA-2333 : A change to sorting un-alike language tags.
https://lists.apache.org/thread/o9j1pd8psm3okc9kyc7ttc3wr460oxkd

This is a fix - Java sort can throw IllegalArgumentException if it detects sorting problems. It is not a guarantee - most time, the bad comparator just causes silent variations of sort order.

GH-1292: https://github.com/apache/jena/issues/1292
Add support for authentication with a bearer token

GH-1387 : https://github.com/apache/jena/issues/1387
Improve SERVICE extensibility (Claus Stadler)


Nearly ready:
https://issues.apache.org/jira/browse/JENA-2320
PR: https://github.com/apache/jena/pull/1256
SHACL listener (Florian Kleedorfer)

GH-1390: https://github.com/apache/jena/pull/1390
Missing implementations for RDFLinkAdapter  (Claus Stadler)

and two which are Context related and positively affected by a fix to context handling in queries.
GH-1374, 1375


There are many improvements and fixes from people using the code.


Issues closed:

Github:
https://github.com/apache/jena/issues?q=is%3Aissue+closed%3A%3E2022-05-01

JIRA:
http://s.apache.org/jena-4.6.0-jira

There are several GeoSPARQL issues outstanding -
https://github.com/apache/jena/pulls?q=is%3Apr+is%3Aopen+label%3Ageosparql

== GeoSPARQL

GeoSPARQL is sufficiently complicated that the direction of the subsystem and implications of some these changes need more consideration from GeoSPARQL users and contributors.

== Beyond 4.6.0

One reason to do 4.6.0 now is to create a released base for significant new work coming up:

A new in-memory graph (amongst other things, better use of memory and a lot more maintainable).

A new subsystem for SERVICE caching and processing.

     Andy

Reply via email to