Building the content tree from PlatformUI requires something like n*3 REST queries, where n is the number of displayed nodes.

Study how this could be improved. Possible solutions are:

• custom media type, maybe applied to the location search endpoint, that adds the extra information so that no extra requests are needed
• custom REST endpoint, that only contains what's required by the tree

Prototype: return ContentInfo in addition to Location when executing a Location Query (POST /content/views).