RE: JW3: What if search arbiter is in a query scope

> I would recommend not putting search arbiters in
> the scope of a query, and would expect that to be the
> normal case.

I anticipate many servers making each collection a search arbiter, and hence
a search arbiter would likely end up in the scope of many queries.

> If someone implements that, then that search arbiter would obviously have
to
> respond like any other resource in the scope of a query responds.

But, I do find myself agreeing with this.  If a search arbiter is not a new
resource type, as I now favor, then the behavior under search is no
different than if the same resource didn't support the SEARCH method.

If there is agreement that a search arbiter isn't a new resource type, this
issue can also be closed.

- Jim