How can a provider inform the ASP/aggregator about not implemented features in advance of the API call

[pendula95]

I see there is a discussion in minutes regarding this topic but following the next meetings minutes I don't see any activity. https://github.com/camaraproject/DeviceStatus/blob/main/documentation/MeetingMinutes/MoM-2023-09-13.md#aob

Example:
Let's say API implementation of Device connectivity status /connectivity is only based on AAA as a datasource and contains information if subscriber has data connectivity or not. So in this case the API can be implemented as:

1. Return only CONNECTED_DATA or NOT_CONNECTED.
   Without the caller knowing that this API implementation only supports CONNECTED_DATA and NOT_CONNECTED I might get a false assumption that any subscriber that gets NOT_CONNECTED also has no capability of CONNECTED_SMS.

[bigludo7]

Hello @pendula95
This is a fair question and I did not see how we can handle this with current API Design.

One way to do this is, perhaps, to add a fourth value in the enum: NOT_DATA_CONNECTED
With this value we indicate that the mobile is not reachable by data but 'we do not know for SMS"

This is not very elegant design but if this UC is common perhaps we can think about it..

[rartych]

Regarding the general question in the title, I think this API proposal addresses it: camaraproject/APIBacklog#22
Here we can think how to tackle specific cases regarding connectivity status information.