Jesse Wright

> If treating {} as true, as proposed by @josd, is possible without drawbacks, I would support that solution. I'm deferring this decision to the N3 group. If we see...

I agree with Ruben that (2) is the only ~semantically correct~** and non-breaking solution. It is why I chose to implement it that way in N3.js > So > :p...

Thanks for the input @joachimvh and @phochste. I also agree that my proposal above is insufficient for N3 reasoning, and had built it only with basic RDFs style rules in...

@phocste - with the map for quantifiers above, I'm assuming the key is the term that you with to quantify. Why is the object an RDF.Variable considering this appears to...

> I agree with @phochste that it would probably be better to first define the scope of what this interface intends to cover. IMO the interface should be able to...

@ignazio1977 - I've been looking into the OWLApi definitions for [OwlAxiom](https://github.com/owlcs/owlapi/blob/version5/api/src/main/java/org/semanticweb/owlapi/model/OWLAxiom.java) and [Reasoners](https://github.com/owlcs/owlapi/blob/version5/api/src/main/java/org/semanticweb/owlapi/reasoner/OWLReasoner.java) to see if it would provide a good basis for this; especially given that it has different...

True, and this is not a major issue - it would just be cleaner to go with the suggested class and describe as much data as possible in RDF rather...

Attempted in https://github.com/eyereasoner/eye-js/pull/1210, benchmark shows no performance improvement compared to main.

> I'd use NodeNext instead In Comunica, I am trying to set up dual packaging of CJS and ESM. It appears that when `NodeNext` is set, it is required that...

> So yea, are you sure you want a dual package in the first place? Looking around, many libraries are now ESM-only, finally :) I'll direct that question towards @rubensworks...