Closed christophenoel closed 4 years ago
Work on a Transactions extension has started at https://github.com/opengeospatial/wps-rest-binding/tree/master/extensions/transactions/standard
Some change requests and ideas:
Similarly to various specification standards, I think that the spec should request a tailoring for each deployment profile, and define the information required in such tailoring. For example for "git repository of a Docker container" profile, a tailoring document should specify the specific application package schema, and detail how the information is used to generate the process description and to run the application.
I hope it helps :)
For anyone interested or for inspiration, I got advanced schema definitions of the whole Deploy going all the way down to the lowest type
field of CWL definition for the Application Package:
https://pavics-weaver.readthedocs.io/en/schema-xmlexamples/api.html#tag/Processes/paths/~1processes/post in the request body: executionUnit -> unit (CWL) schemas: json
XML attribute definitions are also included in those schemas.
I have added the schemas for the transactional operation deploy / undeploy https://github.com/opengeospatial/wps-rest-binding/commit/7bdee9df5652ad3a7ad13075c535b84f9b264d0b