Ruben Taelman

There's also this directory with (Solid-specific) LDflex webpack configs: https://github.com/LDflex/Query-Solid/tree/master/webpack Given that these exist, does it still make sense to have separate browser builds for LDflex (without query engine)?

For reference: `WeakRef` has just been introduced: https://v8.dev/features/weak-references This would allow scope detection and help simplify batching operations.

Comunica accepts a proxy via [the context](https://comunica.dev/docs/query/advanced/context/#10--enabling-an-http-proxy). LDflex calls Comunica with [a fixed context](https://github.com/LDflex/LDflex-Comunica/blob/master/src/ComunicaEngine.js#L31), so this would have to be changed a bit. It might make sense to extend `execute`...

As an alternative, a generator tool (such as `create-react-app`) might also be an interesting solution. (but I have no strong opinions on this myself)

Just wondering if it might be interesting to use JSON-LD's `@language` keywork on properties to define the language of property values. This could possibly be an additional way of requesting...

> Do you mean something like: fruit.['label@en'] Something more like this: Context: ``` { "label": { "@id": "rdfs:label", "@language": "en" } } ``` LDflex expression: ``` fruit.label ```

> Is it possible to use @language in the root of context? To define the default? Yep, JSON-LD defines that behaviour, so it would make sense if LDflex would inherit...

All of the things you describe _should_ be happening already (with `autoStart: false`). If this is not the case, then there is probably going something wrong somewhere. > In addition...

They can already mostly be generated using the generator tool, so the manual effort should already be minimal. Perhaps a way to regenerate them when changes are made in the...

At first glance, it doesn't appear to be described in the [brTPF paper](https://arxiv.org/pdf/1608.08148.pdf). But perhaps we should investigate the implementation to see if they have any special hypermedia controls.