Align asynchronous response with CloudEvents format to ensure compliance with Commonalities r3.3

[albertoramosmonagas]

Problem description

The current asynchronous response mechanism in PredictiveConnectivityData does not follow the CloudEvents delivery format as required by CAMARA Commonalities r3.3. Instead, it uses a custom JSON structure (application/json), which creates inconsistency with the agreed CAMARA standard for event notifications and asynchronous responses.

This could lead to fragmentation across APIs, since API consumers integrating multiple CAMARA APIs would need to support different delivery models.

Expected behavior

• The asynchronous response should use CloudEvents format (application/cloudevents+json) as the delivery mechanism.
• The payload of the asynchronous response should be wrapped inside the data field of a CloudEvent.
• Required CloudEvent attributes (e.g. id, source, specversion, type, datacontenttype, time) should be present.
• Event type should follow the CAMARA naming conventions, e.g. org.camaraproject.predictive-connectivity-data-v0.connectivity-data-async.

Alternative solution

At this stage, no alternative solution is proposed. The alignment with CloudEvents is mandatory per Commonalities, but not blocking for the Fall25

Additional context

• This issue was raised during the review of the Release Candidate for Fall’25
• Agreement in the WG and with Release Management is to keep the current RC stable for Fall’25.
• This correction will be addressed post-Fall25, and released as v0.2.0, following the dual-phase model.
• A similar issue will be raised in the Population Density Data repository to ensure both APIs are aligned consistently.

[albertoramosmonagas]

An issue is open in Commonalities to deal with this point see camaraproject/Commonalities#533

[albertoramosmonagas]

The fix has been uploaded to commonalities: #575. It explains that an asynchronous response is not really an event. And that although it is recommended to use sink and sinkCredential, the cloudevents model should not be used. Telefónica will propose a PR with the new changes.