How will KPs handle qualifier_constraints?

[edeutsch]

With new PR #327 KPs may receive QEdge.qualifier_constraints. How will they handle them?

Proposals:

A) (heart emoji) If a KP receives non-empty QEdge.qualifier_constraints, it MUST only return edges that satisfy the entire set of qualifier_constraints. If a KP does not yet support QEdge.qualifier_constraints, it MUST return an empty response because no matches are found.

B) (rocket emoji) If a KP receives non-empty QEdge.qualifier_constraints, it MUST only return edges that satisfy the entire set of qualifier_constraints. If a KP does not yet support QEdge.qualifier_constraints, it MUST return an ERROR condition to indicate that qualifier_constraints are not supported.

C) (eyes emoji) If a KP receives non-empty QEdge.qualifier_constraints, it MAY return edges that satisfy the unqualified edge.

Please comment and/or vote on this comment with an emoji as listed above. Feel free to describe a different proposal.

[brettasmi]

I vote C, at least for now--I feel like it might be better to push this down the line until we're all implementing qualifiers and have a better sense of how that's working.

[edeutsch]

addressed in PR #364