Given the late reply, you may have already resolved this. SID recommends the following for recording the communication interaction means...
Note that the OpenAPI is a simplified version of SID and hence you would need to extend the current version of the API to introduce this sub-resource.
I'm not sure that the word "Simplified" is necessarily appropriate, Dan. I would rather express it that the SID is a conceptual information model, whereas the Open API payload model is adapted from the SID to make it easier to use as (well) payloads in API operations.
It's certainly true that the structure is simpler in the Open API, with far less deep inheritance structures. But the Open API entities have far richer properties/attributes. And because the Open APIs are exercised in real-life, they are being enhanced as vendors and CSPs bring their experience back into the API model.
Specifically for the matter at hand. the InteractionItem in TMF includes a Channel (which is an open-ended entity that can be used to describe any communication channel). Not sure that it needs to be specifically subclassed, but that's an implementation decision.
Thanks for the reply Jonathan.
Are there any plans to introduce a sales channel management Open API? I noticed it being referred to in your v5 Product Catalog API.
I am not aware of such, Rochana. It could be added in the future, for now in v5 we just have the opaque ChannelRef.