>>>>> Andy Seaborne <[email protected]>:
> Hopefully, Fuseki2 is compatible with Fuseki1 configurations - it's > supposed to be anyway. > At some point (no plans), Fuseki1 is end-of-life. Currently, it's > only getting maintenance. > Fuseki2 runs as a service much better. Ok, thanks! Compared with what you said inline, Fuseki2 it is! One point I forgot to mention was that we want SPARQL query results as JSON-LD and that's possibly Fuseki2 only...? (If so, this definitely means going for Fuseki2). One minor comment/question below: >> - Directory layout compatibility? (I know this is different) > It does have it's own "run" area. That's part of being more > OS-service oriented. As far as I can tell from the existing code, it operates with a TDB directory with the dataset embedded, while Fuseki2 seems to use the structure run/databases/<dataset-name> Ie. one separate TDB database per dataset...? Or is it just that the existing code creates a single dataset and names the directory it resides in "TDB" rather than using the dataset name...? (The existing code that wraps Fuseki1 _does_ seem to ensure that the a single dataset is always present and creates it if it isn't)
