linked-data

Description

Is your feature request related to a problem? Please describe.
CSV files produced in different locales have different default separators, a comma-separated file (",") is but one type of CSV.

In Sweden we usually use a semicolon (";") as separator and many CSV files use a tab as separator ("\t"). Importing CSVs requires reformatting them before import, and causes inoperability issues and f

Triples within a TriplesBlock are list elements. E.g.:

expr = Builtin_NOTEXISTS(
                graph = GroupGraphPatternSub(
                    part = [TriplesBlock_{'triples': [[rdflib.term.Variable('a'), rdflib.term.URIRef('https://github.com/GreenfishK/DataCitation/citing/valid_from'), rdflib.term.Variable('valid_from')]], '_vars': set()}]
                    _vars = set()
        

Debug logging for lifecycle methods like initialization and when data has to be re-inferred (eg. when something is deleted).

Trace logging would be per statement to log what gets inferred.

The server has a couple of regular expressions that re-appear.
We might want to expose them as constants.

It should be rather trivial to replace most of the legacy jQuery-based code in jquery.js with an IXSL (Saxon-JS) implementation.

We need to keep the fetchDispatchXML function though.

Hi, Is it possible to add in readme more information about support?

• What are the feature necessary for LDflex to work?
• Is Node supported?
• Are browsers supported? Which ones?
• Can polyfills help?

Currently we are just catching (thanks @c-martinez ) errors when we fail to parse query metadata. These are situations in which the parsing will most probably fail:

• Empty line at the beginning of the metadata section
• More than one empty line at the end of the metadata section
• Inconsistent indenting
• Etc.
  At the moment the backend fails silently, and simply no OpenAPI spec is rendered f