feature: support GetContainmentTree and GetDescriptor or stop offering a ContainmentTreeService.

[ben-Draeger]

Is there an existing issue for this?

• [X] I have searched the existing issues

Feature idea

Currently, the sdc11073 ReferenceTest-Device offers a ContainmentTreeService, but answers GetContainmentTree Requests with a SOAPFault: Receiver: not implemented.

This was observed when running SDCcc (7.0.1) against sdc11073 (version: b370b79d609f87fb24d9b425a0c1c7fd444bf96f, should be 1.1.25 I think).

NOTE: The same behaviour can be observed for GetDescriptor Requests.

While offering a ContainmentTreeService is optional (Biceps:R0119), a device offering a ContainmentTreeService must respond to GetContainmentTree- and GetDescriptor-Requests in a way conformant with the Requirements (f.i. Biceps:R5030, R5031, R5032, R5033, R5034, and R5035).

Alternatives

I would suggest to resolve this situation by either not offering a ContainmentTreeService or by implementing GetContainmentTree and GetDescriptor.

Implementation idea

No response

Participation

• [ ] I am willing to submit a pull request to implement this feature.

Link to the idea discussion

No response