Jan Niestadt

The current default on the dev branch (and for upcoming BlackLab 4.0), API v4, is transitional: - 98% compatible with v3 - adds new `/corpora/NAME` endpoints There's also the experimental...

e.g. if your config shows you're trying to index relations, but you're using VTD instead of Saxon, give an error message explaining the problem.

The following queries should have identical results: ``` n:_ -case-> v1:_; -case-> v2:_ :: start(v1) < start(n) & start(n) < start(v2) n:_ -case-> v1:_; -case-> v2:_ :: start(v2) < start(n)...

Add tests for relations features.

1

A lot from plan-relations.md can be reused for the final documentation.

BlackLab should trim values while indexing by default, otherwise an XML structure like this will index a word ending in a newline: ```xml ende ```

We currently only CI test JSON responses, but we rely on certain XML responses as well in corpus-frontend. We should at least test these XML responses to ensure they don't...

`IntArrays.parallelQuickSort()` really sped up sorting terms while writing them to disk or while reconstructing the global terms list. Sorting hits by a `HitProperty` seems to still be done single-threaded in...

The indexing system has grown complex over the years, and some features aren't very useful, or aren't needed anymore if you use Saxon with XPath 3 support. We should deprecate...

In chn-intern, running the TermSerialization tool finds terms that don't correctly "round-trip" (i.e. get the id for the term, then get the term for that id again), although not too...