...
Unfortunately, this endpoint does not align with REST conventions and does not prepare for future changes. Then, redesigning the endpoint for improvement is considered:
- POST - /cps/api/v1/dataspaces (or /cps/api/v2/dataspaces ?)
with all payload information for the dataspace to be created provided in the HTTP request body ("dataspace-name" being mandatory and "data-updated-notification-indicator" optional):
...
Dataspace modification requires a new endpoint:
- PUT /cps/api/v1/dataspaces?dataspace-name=<name> (or /cps/api/v2/dataspaces?dataspace-name=<name> ?)
with all payload information for the dataspace to be created provided in the HTTP request body ("dataspace-name" being mandatory, consistent with the query parameter and "data-updated-notification-indicator" optional):
...