jerstlouis
commented
3 years ago In the Modular OGC API Workflows project, we are trying to make process (or workflow) execution-requests Re-usable by leaving the negotiation of APIs, Area of Interest, resolution, formats up to the two end-points of any hop alongside the chain, outside of the definition of the workflow itself.
The approach also attempts to improve Interoperability in the same way, in that these nodes could find common ground based on their supported capabilities. The extension also allows to trigger processing via simple OGC API data delivery services request (e.g. Features, Tiles, Coverages, Maps), making processing a lot easier to leverage in simple client applications.
A map could also share the workflow document generating it, which allows to easily reproduce the results, and re-use it with additional or different data or processes.
The idea is also to be able to bring together any data or processes that you can Find (e.g. using OGC API - Common or Records, or simply the greater ease with which APIs implementing them can be found in a web search), and allowing any process to Access them using this simple chaining mechanism.
See also #115
There is a general agreement for the implementation of FAIR principles regarding data, and ongoing discussions about what this means for services. I think WPS could be the backbone of FAIR services but it would be useful to clarify expectations and conduct a gap analysis of what might be missing from the WPS standard and current implementations to make this a reality.
References
Internet of FAIR Data & Services (IFDS)