Benjamin Geer

Understood. How about a limit of 150 for now?

If I remember correctly, the compound resource idea would just be an optimisation to make it more efficient to query a tree of resources (e.g. in Gravsearch). It wouldn't create...

> limiting a resource's number of properties can only increase the graph depth... there's no magic :( But generally you don't need to get a whole tree at once. You...

> simplify the data access, instead of making several http v2/resources requests, we could have all data in one request We want the client to make several requests in order...

@mrivoal OK!

@tobiasschweizer would like to implement the querying of compound resources in https://github.com/dhlab-basel/knora-api-js-lib.

Is the resource very large? If so, it could be that the SPARQL query result is truncated. @tobiasschweizer would you have time to look at this?

It's still there in the scripts in `src/webapi/scripts`: ``` owlim:query-limit-results "50000"; ```

Relevant discussion with @mrivoal here: https://github.com/dasch-swiss/knora-api/issues/1320#issuecomment-494300576

> In the past I have spotted problems when GraphDB couldn't serialize a response because it was too large. This could also be problem with fewer properties that have large...