Andy Seaborne
Andy Seaborne
Latest changed to 4.9.0 ... so it is always valid in the future :-)
Blank nodes are concrete. "concrete" covers the RDF terms that can go in an RDF graph and be printed. The test "triple.concrete" isn't appropriate (from reading the code).
The blocker is the WAR file which shares `jena-fuseki-core`. It locks to specific versions of Apache Tomcat (Tomcat 10 being the first Jakarka based Tomcat). There are also the Spring...
Seeking information: [email to users@ asking about tomcat usage](https://lists.apache.org/thread/go9wxd05zcpj2g4hmnvvb7jvf4p81r6g).
@rzo1, presumably this works in reverse as well -- convert `jakarta.*` to `javax.*` (providing no new capabilities of the various specs are used). There is likely to be a long...
We plan to switch to jakarka.* at Jena5 (which wil also require Java17). Conversion to jakarka.* has been tried - it was pretty uneventful.
+1 to listing the graph without counts.
Merge would be one option - some people might read it as "validate each one separately".
`--data` has multiple possible expectations. One way to resolve this would be allow `--data` to be stdin and then use `riot` to parse/merge files.
Hi @Afler - no concrete progress but it's getting nearer. @Afler, @benjaminaaron -- a few refinement questions -- There are several areas within the UI: query, data loading, endpoint stats...