Question about DELETE and nested sub-resources

[EricLo-417]

Hello OGC Connected System People,

I am currently making an implementation of the api and I have a question about what do per spec when deleting parents of sub-resources.
So for example, lets say I have a deployment that has a subdeployment which then has a subdeployment.
So
P -> C -> NestedChild

What is the intended chain?

NestedChild moves up a level?

P -> NestedChild

or

NestedChild becomes a top-level deployment
P
NestedChild

Looking under the CREATE/REPLACE/DELETE section, it only talks about CREATE for subdeployments but nothing for DELETE

And then the deployments section also does not mention what to do if deployment was a parent

[SpeckiJ]

This indeed looks like an oversight in the spec - for systems the behaviour of sub-resources is clearly defined (i.e. reject by default if there are sub-resources, cascade deletion if cascade parameter is given), but for deployments this was missed.

For the sake of consistency I would handle the deletion of deployments and their sub-resources the same way,

1. Reject the DELETE if there are subdeployments (this forces the user to first update them - deciding whether they should be deleted, moved to top-level, or moved to be someone else's child)
2. Allow deletion if the (currently non-spec) cascade parameter is set, and cascade deletion to the children.

[alexrobin]

@SpeckiJ I agree that we should do this the same way we do it for Systems