Thomas Bergwinkl

- define objects immutable without throwing an error

We agreed in the call that Quads and Terms should be immutable but we don't define the behavior for write access. The High Level API may define more details.

Using the datafactory to create `Term` + subclasses and `Quad` is the only official way. And all of them are immutable. > Factory functions (e.g., quad()) or methods (e.g., store.createQuad())...

Not sure how we wanna handle that. I think the interfaces are finished. But at some places we may need more precise descriptions. There is some room for interpretations, which...

I implemented an initial version of the [test suite](https://github.com/bergos/rdf-data-model-test-suite). Most things should be covered, but we need more tests for the `.toCanonical` stuff.

.toCanonical of quads should end with a full stop

I've updated the tests, but also merged them into the [rdf-data-model](https://github.com/rdf-ext/rdf-data-model/). See also #115. If we have enough votes in the other issue, I will move that repository and close...

Example for a resource with many triples and long loading time: https://ld.bs.ch/cube/100128/observation/

@l00mi you can have a look here: https://tbbt.zazukoians.org/data/person/penny Here is the config: https://github.com/zazuko/tbbt.zazukoians.org/blob/ccf7fc338d97cc6cb2a7cd439bae5e9e9a4ebba9/config.yaml

We have two issues for the pagination topic: https://github.com/zazuko/trifid/issues/129 https://github.com/zazuko/trifid/issues/123 @l00mi as we track the pagination in separate issue, can we close this issue?