Ruben Taelman

That seems problematic. But the weird thing is that it only seems to occur in that run. Locally it works fine, and also in the other runs it seems.

> it seems that 156/156 of the spec tests are consistently passing. Yay 😅 > I suspect the best solution will be to create a PR for [rdf-test-suite](https://github.com/rubensworks/rdf-test-suite.js/) which has...

For people running into this issue with Webpack 5, in the meantime you can use: https://www.npmjs.com/package/node-polyfill-webpack-plugin

This might be a good replacement for stream: https://www.npmjs.com/package/readable-stream

So it looks like `stream` is the biggest one to tackle. Given [this issue](https://github.com/nodejs/readable-stream/issues/448), I suspect that `readable-stream` works out-of-the-box in Webpack. However, the [readme indicates otherwise](https://www.npmjs.com/package/readable-stream#user-content-usage-in-browsers). So we will...

> Even if it would work out of the box, our dependencies depend on readable-stream v1, v2 and v3 but not v4. So we would still have to migrate them...

`POST` to append to RDF resources may indeed be a very valuable simplification for developers. I'm however not too sure about defining the semantics of `POST` for `text/plain` though, as...

> The fourth component is the request URI identifying each resource. Such an interpretation definitely makes sense IMO. The only problem with it (summarizing my [previous comment](https://github.com/solid/specification/issues/125#issuecomment-872211665)) is that it...

> So, this is now 4 separate GET requests, but it encodes exactly the same graph as the original example, right? It depends on the interpretation of the `graph` component....

Currently, LDflex can also produce `WHERE` clauses for insertions and deletions. Several examples can be seen in the [unit tests](https://github.com/LDflex/LDflex/blob/master/test/integration/sparql-test.js#L163-L172). I do however think that it may be possible to...