https://github.com/ezsystems/ezpublish-kernel/pull/1243 made Location Search using REST content views possible, by allowing a "type" attribute on the Query node in the ViewInput, specifying that the Query is a Location one.

It turns out that this approach has a few issues when you think about stored views, since you would not know what is being returned (Content, or Location).

We could change ViewInput to be a Content ViewInput (either deprecate, or document it as such), and introduce a new LocationViewInput. Similarly, the Response would be either a View (Content View), or a LocationView.