Andy Seaborne

While there are a lot of files, it looks to me like the majority are consequences of adding `FOLD` and `UNFOLD` as SPARQL extensions. I've been though the description and...

> Is new SPARQL syntax really required for this? IMO that is a major drawback. Couldn't extension functions suffice? As a GeoSPARQL-like approach? I think @SimonBin's work shows that it...

@hartig - Could you please create an issue at https://github.com/apache/jena/issues for this. I'd prefer that it is the contributor who creates the issue. We can edit descriptions afterwards. Either minimal...

> > It is not an a call-out extension like text query, geo > Precisely because the GeoSPARQL 1.1/1.2 aggregate functions would also greatly benefit from being able to ORDER...

> Done: https://github.com/apache/jena/issues/2518 Thanks - I added an automatic close-issue into the description of this PR.

> @afs I am done with rebasing now. Excellent. If I set to "Rebase and Merge" there is something showing. 148 commits in (commit 9cc5647c3c). Part of the conflict is...

The rebasing has made it a clear which files have changed and that makes reviewing easier - thanks. I haven't managed to do a clean "git rebase" against the current...

ASF now have a Software Grant for this PR. "rebase and merge" and "merge commit" show conflicts. "Squash + merge" is showing as OK. Taking a diff and applying it...

We can't be sure until we have the CDT code combined with the current state of `main`. For now, a separate `CDTAwareParserProfile` is better. This is an internal issue so...

Removed "This closes" from the description. This isn't a PR to the default branch anymore.