Benjamin Geer

I have no memory of this. You could look for the PR in which this happened; there might be an explanation there. If it doesn’t make sense, please fix it.

CIDOC has transitive properties. I'm trying to think of how we can deal with this, given the [Knora FAQ about transitive properties](https://docs.knora.org/paradox/faq.html#can-a-user-created-property-be-an-owl-transitiveproperty-).

Looking at the [Erlangen CRM](http://erlangen-crm.org/), which is an OWL encoding of the CIDOC CRM, they use `owl:TransitiveProperty`. I think we could use this encoding and handle the transitive properties like...

Interesting quotes from the spec: > Implementations may lead to solutions where elements and links between relevant elements of our conceptualizations are no longer explicit in a database or other...

There are also different [versions of the CIDOC CRM](http://www.cidoc-crm.org/versions-of-the-cidoc-crm) to be aware of. There's an "official" version corresponding to [ISO 21127:2014](https://www.iso.org/standard/57832.html), as well as more recent versions under development. The...

Can you paste the rest of the stack trace so I can see where in the Knora code this happens?

It would also help a lot to have the Gravsearch query that triggers this.

It's validated and reformatted: https://github.com/dhlab-basel/Knora/blob/develop/webapi/src/main/scala/org/knora/webapi/responders/v2/ResourcesResponderV2.scala#L512 `PermissionUtilADM.validatePermissions()` does some validation, converts the string to a `Set[PermissionADM]`, then calls `PermissionUtilADM.formatPermissionADMs()` to reformat the permissions for consistency. To be honest, I've always had...

@tobiasschweizer @SepidehAlassi To make a large text containing lots of markup, could we combine a lot of BEOL texts into one text? How hard do you think that would be?

> We could just copy and paste an existing text several times I think that for a realistic performance test, it would be better not to repeat the same content.