qualify service5 with a feature for variable service locations

[lisp]

as the semantics for variable service locations is not well defined, it is not appropriate to require its unqualified implementation in order to demonstrate performance.
either add a distinct feature for their support or define an alternative to sd:BasicFederatedQuery to indicate the extended implementation.

[afs]

The tests should be labelled in the manifest); IIRC that was going to be done but seems to have not happened. The "labelling the manifest" approach is used elsewhere in the tests. A separate issue is whether endpoints that have a query processor that has this feature. Modifications to the service description vocabulary are out side testing. Maybe send a comment to the comments list for any future WG to consider.

[lisp]

there is a label in the manifest, but it is the same as for a test with a constant location.
if we need to extend the service description in order to adequately describe tests, do we have to start our own vocabulary?

this question is relevant beyond the federation tests, as there are other aspects, where the features are not sufficient to distinguish among variations in what should be conformant behavior.

[gkellogg]

It may be that forward-compatible updates the the test vocabularies are in-bounds, it needs checking with the powers-that-be. @ericprud, can you comment?

Of course, another alternative would be to simply define required vocabulary terms directly in the test manifest itself.