Maybe first it would be great to idenfity two revisions to compare as we do already. Then we'd however have a textarea query field to execute a query in order to find a specific subtree in a resource. Ideally the output should somehow be a single nodeKey as input to the serializer on the server GET https://example.org/database/resource/diff?first-revision=3&second-revision=7&startNodeKey=${resultNodeKeyFromQuery} for instance .