Fix Version/s: Nader te bepalen
The BgZ consists of many endpoints. A server may choose which it supports with a certain minimum (20).
When it does not support an endpoint, the specification is unnecessarily unclear about what to expect. This means that both an empty Bundle and a Bundle with an OperationOutcome would be valid. In that case a client cannot see the difference between "no data" and "not supported". This seems relevant to know.
The qualification testing currently also allows both variants. The first vendor implemented an HTTP 200 (OK) + OperationOutcome with severity information and issue code not-supported.
I would like to see that behavior as the way to handle not-supported:
<div xmlns="http://www.w3.org/1999/xhtml"> Feature not yet implemented. </div>