Align use of CAMARA common schemas

Problem description
The API defines its own schemas for several ones defined by CAMARA_common.yaml

Possible evolution
Adopte the schemas from Common.yaml and extend these where necessary:

use common geographical location schemas; replace ellipse by polygon or extend common schema with ellipse if required.
use common PhoneNumber
use DateTime rather than inline definition
check for other applicable common schemas

Alternative solution
Continue with local variants with slightly higher maintenance cost.

Additional context
This can be done in the next rc or at anytime before v1.0.0

This should also cover CAMARA_event_common.yaml for webrtc-events-subscriptions. The local copies differ from it:

SinkCredential lacks PRIVATE_KEY_JWT (and the related 422 code).
maxLength values differ for accessToken, sink and terminationDescription.
SubscriptionAsync.id is not required.
The subscription list is a bare array instead of the template's list with pagination.

Navigation Menu