Ruben Taelman

> If we release the beta of asynciterator today I can spend tommorow seeing trying to upgrade comunica - if it's too hard/time consuming then we can just leave it...

> how is code size compared to the state of the art? I'm also interested in this to know whether or not we could/should make graphy's parsers the new defaults...

For reference, an HTML version of the (SWJ) template has been added here: 4b253bc82ff1d78d3936224aa3be6150e7606f29

@csarven Yes, that's what I meant.

I think an HTML variant of the authoring guidelines are still pending: https://github.com/vtex-soft/texsupport.iospress-ds/blob/master/iosart2x.pdf

Hmm, that must be a mistake by me then, as SWJ indeed uses double-column.

I first thought this was caused by [the way the main module is required](https://github.com/rdfjs/N3.js/blob/master/spec/parser.js#L1), but I do the same thing [here](https://github.com/rubensworks/microdata-rdf-streaming-parser.js/blob/master/spec/parser.js#L1), which is running fine on Node 15. So I...

This is really exciting @jeswr, awesome work! So is this implementation N3-specific? Or could it also be generalized to run with the same level of performance over other RDF/JS Sources?

> I expect that the reasoning components I am implementing over in Comunica will be at least 2-3x slower (even after merging all of the optimizations that I have been...

> Indeed - that was the motivation for https://github.com/rdfjs/N3.js/issues/289 as well Oh, interesting, I missed that issue.