RFC Part 2: Adjust requirements of Package Responses

Requirement 22: /req/deploy-replace-undeploy/package-response-body indicates that the response "SHALL contain the last application package used to deploy the process" (emphasis mine, note the bold). The application package section then proceeds to present the applicable schema.

This definition is misleading because:

1. The package used to deploy can be anything else. This is better described in the Deploy Request Body that lists conditional alternatives (indluding OGC Application Package, CWL, or others). Therefore, if a CWL or others were used directly during deployment, it cannot be directly returned by the package endpoint according to this stricter requirement.

2. Permission 5: /per/ogcapppkg/other-execution-units already indicates that packages can be encoded in other ways.

3. The executionUnit property shows embedded CWL documents, which means negotiating other representations would require mixing application/ogcapppkg+json (to respect Requirement 27: /req/ogcapppkg/package-response-body) with other profiling of application/cwl+json (or others), rather than simply negotiating the application/cwl+json directly.

Therefore, I think Requirement 22 should be reworded to follow the same conditional approach as the deployment, and indicate it is not limited to the application package representation specifically. To make this even clearer, I think a content negotiation Permission statement should be reiterated right under Requirement 22 allowing the endpoint to respond to alternate representations "even if they were not used for deployment", since that goes against what Requirement 22 indicates if followed strictly.

As an extra, the above-mentioned profiling could also be indicated as guidance. Otherwise, the below anyOf representations cannot be negotiated when embedding them in executionUnit with the same Accept: application/ogcapppkg+json content.

https://github.com/opengeospatial/ogcapi-processes/blob/8193f9d5cb976e1b8ca9d0d1bde6cb749fb81e8a/openapi/schemas/processes-dru/executionUnitBase.yaml#L5-L44