Benjamin Geer

> In practice I hope you, as soon as possible, will provide a Typescript lib to deal with the Knora API I'm working on it right now. :)

Have you read https://discuss.dasch.swiss/t/large-texts-and-xml-databases/134 ? You have two options: 1. Break your text into smaller pieces, instead of storing a huge text in a single `TextValue`. 2. Wait until Knora...

I suggested the same thing to you last April: https://github.com/dasch-swiss/knora-api/issues/1293#issuecomment-480269479

> the save process is also very slow If you can split the text into smaller pieces, both saving and loading will be faster.

> However, artificially splitting long editions that users can easily deal with with other tools (existDB) is not an acceptable solution (this is already the feedback we have from another...

> What do you consider will be "a lot of markup"? In the test I did, nearly every word had a tag. The more markup you have, the more triples...

> Just have a look to their job : http://lumieres.unil.ch/fiches/trans/1088/ That text has chapters. Why not store one chapter per resource? That would also make navigation and editing a lot...

I don't think it's possible to for us to use the variable in the input query, because it could exist only in one block (an `OPTIONAL`). What if the user...

OK, so I think this isn't a bug.

Also update the discussion about "owner" in the docs: https://github.com/dhlab-basel/Knora/blob/develop/docs/src/paradox/05-internals/design/api-admin/administration.md