Open APIs

Hi,

The current TMF681 specification requires that the whole content of the customer notification needs to be passed from the API client.  However that often leads to inconsistent communication going to the customers from different channels in a large CSP like Jio.  Hence we had to templatize the communication, and for different notifications we have thousands of templates for various business needs.  The templates typically have the template id, the static content, and the variables which need to be provided by the consuming applications.  The API consuming applications do provide the template id and the variable values.  TMF681 API doesn't provide any field to provide the template id and the variable values.  We see three options to tackle the same: -

1. Option A: Extend the data model to have a new entity "CommunicationTemplate", and refer to it in the CommunicationMessage_Create.

2. Option B: Send the template id and variable values in CommunicationMessage_Create Characteristics. 

3. Option C: Include ID field in the CommunicationMessage_Create also, which can carry the template id in the request.  This however does not look to be much viable. 

Please let us know if any thought has been given in this regard, and if not, what would be your guidance?