Updating IDs with PUT #245
Description
Currently, the PUT request to update elements seems to allow updating the ID, e.g. by doing a HTTP PUT .../submodels/{id} and providing a new ID in the payload.
In general, this is ok, i.e. normal behavior of REST APIs. However, things start to get less clear when looking at some details.
For example, what is the expected behavior when calling /shells/{aasIdentifier}/submodels/{submodelIdentifier} and updating an ID?
Is it expected that the submodel-refs in the AAS are also updated accordingly?
What about the following scenario: There are two AASs (AAS_1 and AAS_2) both having a reference to the same submodel (Submodel_1). What is the overall state after calling PUT /shells/AAS_1/submodels/Submodel_1 and changing the ID of the submodel to Submodel_1_new? By "default" behavior, both AAS would still point to Submodel_1 which no longer exists. However, this is unexpected as the call to update the submodel happend "in the context of AAS_1" (as it is part of the URL). This is counter-intuitive.
- I have signed the required Developer Certificate of Origin (DCO) already.