Ruben Taelman

> Let's make it two weeks to give people some time. Two weeks can be a very long time in some cases though. E.g. when devs discover a bug in...

Both suggestions sound good to me, no preference for either one on my end. This is also something we can tweak afterwards if we notice that things are not working...

I also don't think splitting is needed. A single typings package should be fine. Regarding changelogs, I don't have a big preference, as long as it doesn't put too much...

This approach looks good to me, should be straightforward to implement into Capability Proxy. > A better solution would be to include an original target specifier to getCapability I agree...

I just ran into this PR. Without having looked into it in detail, feel free to take inspiration from the Ingredient Components API that I've been working with for several...

The readme contains instructions on how to build this project and how to use it from the command line: https://github.com/rdfostrich/ostrich?tab=readme-ov-file#ostrich There are also bindings to use it in Node.js, which...

Hi @c-martinez 👋 AFAIK, there are no abstraction layers on top of this library directly, but there are several for [Comunica](https://comunica.dev/) (which can do everything this library can, and more),...

Note to self: We'll probably need some new optimize actor that enforces the use of the bind join when SERVICE with variable is found. We can use this enforcement mechanism...

Thanks for reporting!

Hmm, since I don't have time to fix this problem this week, I'll just pull the releases from CF and MR.