ICD for AIP draft version can be downloaded from this link: CAP-TN-037-BE_ICD_for_LTA-1.0-RC1.docx
Functionality | Operation(s) | Current ICD | Future ICD | Justification | Alternatives |
---|---|---|---|---|---|
Returns real priority calculated for requested order | productOrder batchOrder | priority field is returned | priority field is not returned in response | OGC API standard don't allow to specify additional fields in jobStatus response | none |
Returns estimatedDate information for requested order | productOrder batchOrder | estimatedDate field is returned in order response. Mandatory for productOrder | estimatedDate field is not returned in response | OGC API standard don't allow to specify additional fields in jobStatus response | Use the "finished" property of Job status. Use the specific STAC property order:date. It requires the |
Automatic creation of Batch Orders | bulkCreate | Batch orders processes are created in advance in the bulkCreate step but not triggered. The client has to trigger each of them for execution. | Batch Orders processes are not automatically created. The client has to execute a new process called "batchOrder" | No concept of "process triggering" in OGC API; It doesn't change anything in terms of number of | |
Setting of FilterParam query parameter | bulkCreate | FilterParam property is a string with the complete criteria | FilterParam property becomes a array of objects. Each object is a criterion for product filtering | Less complexity on client side to define STAC query. The query is built by the service and is compliant | keeping a string |
BatchOrder query sub-step | bulkCreate | The bulkCreate step don't return the list of Batch Orders but the client needs to send another query to get them. | Job result of bulkCreate process contains the list of batchOrders as an output parameter | simplification of workflow | |
Notification about process completion | productOrder batchOrder bulkCreate | ||||
Notification on Subscriptions | The LTA service posts a HTTP query to a predefined callback URL | The notification is sent asynchronously through a AMPQ message broler | More robust, especially if client's URL is irresponsive. However, this requires a overwork on client side. |
Id. | Author | Section/Page number | Title | Status (Open / Fixed / Closed) | Initial Comment | Discussion |
---|---|---|---|---|---|---|
1 |
Question: can BulkCreate be synchronous : NO because potential time to execute "Bulk Create request" can be long (several mn)
Decision: stick to asynchonous process
Question: Are each batch order created when Bulk create : yes and persisted in a DB
Note on sequence diagrams: generated with https://plantuml.online/uml