Tomasz Pluskiewicz

The same goes for unescaped spaces in and URI

In fact I was not and yes, the parsing is fixed when a baseIRI is passed to the constructor. Would still be nice to add a parameter to `import` though

Not a bad idea, at least for `baseIRI` to be standardised like the ctor parameter. On the other hand, since we're talking about JS, any superfluous parameters are also not...

This is not an issue with the project but a limitation of TypeScript. You need to name the class and return that instead: ``` function VisuElement(base: B) { class Mixin...

Does this also intend to fix a looping case like ```turtle _:list rdf:first "foo" ; rdf:rest _:list ; . ```

Ok, maybe I was misled by the word "loop" in the test case name

This is just a workaround, because it returns an array of clownface with single context The real deal should return a single object with distinct `terms`/`values`

Hello @martinwebrant. Sorry for late reply. In code where I needed a specific graph, in the current version I would create a new pointer object like: ```ts let pointer: GraphPointer...

I support this effort, albeit I have not looked closely yet. That said, the motivation does not give it justice. What you describe can simply be done as ```diff -bob.outE(ns.ex.exoticProperty).out(ns.ex.label).value...

We are running v16.11