Rinke Hoekstra

I have a similar issue with scoped contexts and IRI expansion using scoped `@base` or `@vocab` definitions. Only the first scope context is used, the other is ignored. Adding this...

We are capturing data ownership information as part of a catalog, and have a need to store the ownership information with the data, as this may be distributed across multiple...

I can confirm that excluding the `manifest.jsonld` explicitly will make the tests run (though very many of them fail).

@ansell ok, did my best :-) The tests now run with a copy of the W3C test suite for JSON-LD 1.1 As the comments in the code already said, ideally...

I'd like to bump this as it fixes major issues we're facing internally, with slow framing on large JSON-LD files. I will try to generate some artificial data (large amount...

I support this. Without this we’d have to resort to reification of alternate names to indicate that they are abbreviations.

Adding to this, why does the [JSON-LD version of the ontology](https://github.com/w3c/web-annotation/blob/gh-pages/vocab/wd/ontology/oa.jsonld) not use the [anno.jsonld](https://github.com/w3c/web-annotation/blob/gh-pages/jsonld/anno.jsonld) context?

I'm hitting the same problem. What is the best way to work around this?

This updating in BlankNode appears to be the culprit: https://github.com/linkeddata/rdflib.js/blob/c14dfd57d5159ad5ac1ee2523cc7924968e24f53/src/blank-node.ts#L35 I think that the abstract `nextId` counter is not synchronised across class instances when data is loaded asynchronously?

This is rather problematic for any system that uses rdflib.js to parse JSON-LD. Any chance this can get prioritized?