New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename "id" to "process" and use full URI to process #123
Comments
If going with the suggestion in #124 where the client can POST to |
Clarifications we discussed in the 2021-02-21 SWG meeting:
|
@jerstlouis If I understand correctly, the first bullet is proposing to support a request and payload structure such as: URL: http://localhost:8080/processes/EchoProcess {
"inputs": {
"complexInputId": {
"format": {
"mediaType": "application/xml"
},
"value": "<test/>"
},
"complexInputsId": [
{
"format": {
"mediaType": "text/plain",
"encoding": "UTF-8"
},
"value": "test"
},
{
"format": {
"mediaType": "text/plain",
"encoding": "UTF-8"
},
"href": "https://test.data/test.txt"
}
],
"literalInputId": {
"dataType": {
"name": "double"
},
"value": "0.05"
},
"boundingboxInputId": {
"bbox": [
51.9,
7,
52,
7.1
],
"crs": "EPSG:4326"
}
},
"outputs": {
"literalOutputId": {
"transmissionMode": "value"
},
"boundingboxOutput": {
"transmissionMode": "value"
},
"complexOutputId": {
"format": {
"mediaType": "application/xml"
},
"transmissionMode": "value"
},
"complexOutputsId": {
"format": {
"mediaType": "text/plain"
},
"transmissionMode": "reference"
}
},
"response": "document",
"mode": "async"
} Note that the example above removes the 'id' property from the current Execute example. @jerstlouis Could you please confirm that the example above reflects what you are proposing? |
@ghobona In general the proposal would be for such an execute requests to include
but the first bullet of the clarifications means that for the top-level process (i.e. excluding workflows nested processes) this A reason for including the process in the execute request would be to share it as something meant to always be executed for that particular end-point (e.g. drag & drop it in QGIS and it knows where to POST it to). |
@jerstlouis Thanks for the clarification. |
|
This facilitates sharing process execution as a client will know where to POST the execution request to.
It also allows nested processes as inputs for the chained workflows extension.
The text was updated successfully, but these errors were encountered: