George Svarovsky

Linking to #60 for reference

> OK but then we should probably have collaborative editing as an issue/use case. I've just done a scrape of related use-cases from Solid and w3, and written it up...

`@where` can take an array (at least, for json-rql --> SPARQL), e.g. [sparql-10-1b](https://github.com/gsvarovsky/json-rql/blob/2fb11f9f91f6e5f437f2ec457a23d48abfc04342/test/data/sparql-10-1b.json) More test cases needed.

Thanks @jeswr Since this will be addressed by your rewrite, but in the meantime can cause hangs in tests and (theoretically) apps, I'm going to release a patch of m-ld...

Schema available at https://json-rql.org/schema.json. It's rather permissive, so leaving this ticket open for future improvements.

Hi @zg009 thanks so much for your interest! This is certainly a reasonable place to start, yes. However it might be a bit different than I thought... 1. JournalConfig is...

The primary brake here is that we use a customised [typedoc theme](https://github.com/m-ld/typedoc-theme). The template for the theme changed extensively for typedoc 0.20. - https://github.com/m-ld/m-ld-js/issues/79 - https://github.com/m-ld/m-ld-js/pull/126 The `readmeToc` thing is...

**Suggestion**: using a customised theme is going to cause this kind of problem repeatedly. Let's switch to generating markdown docs using [typedoc-plugin-markdown](https://www.npmjs.com/package/typedoc-plugin-markdown), then compose the final website using eleventy, via...

> Do I see it correct that I could propagate list changes in m-ld specific format, but keep them in my own dataset as a rdf list? It would work...

Note https://www.w3.org/2014/data-shapes/wiki/Rdf:List_Stresstest