Ruben Taelman

> I've just run some benchmarks (running https://github.com/comunica/comunica-feature-reasoning/tree/chore/benchmark-forward-chaining/packages/actor-rdf-reason-forward-chaining/perf) in Comunica with some of the Asynciterator and N3.js optimisations included and it is 2-3 orders of magnitude slower than the results...

> The results are about 2-3x slower than the internal implementation on N3.js. That gets us a lot closer already! (and may be in the acceptable range even) > @josd...

A big 👍 from me on this. Would be crucial for things like https://github.com/comunica/comunica/issues/873. An alternative approach could be to store this `id` value within the RDF/JS `Term`, but not...

> My main concern with this approach would be having to handle conflicting ID's if there are multiple sources. Indeed, we'll need a way of detecting distinct sources if we'd...

FYI, this tool may also be valuable: https://github.com/rubensworks/rdf-literal.js#converting-a-date

@jeswr Yeah, definitely makes sense to also include this in the Comunica framework. Instead of encypting/decrypting server-side (for the issues raised by @joachimvh), it might indeed also make sense to...

Let me also ping @skirrane, she might also be interested in this.

While `ValueOverrider` definitely makes sense to me, it seems to be designed with the assumption that Components.js must remain unchanged. However, since there definitely is a need for [value overriding...

There are use cases where HTTPS is not required, and HTTP is sufficient (e.g. https://github.com/rubensworks/ldbc-snb-decentralized.js). So I wouldn't make it mandatory. But it would make sense to make it the...

AFAIK this is intended behaviour. Making a statement about something does not necessarily imply that statement. (Ruben says that cows are blue =\> cows are blue)