Skip to content
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

Clarifying FAIR principles for WPS #114

Open
huard opened this issue Jul 17, 2020 · 1 comment
Open

Clarifying FAIR principles for WPS #114

huard opened this issue Jul 17, 2020 · 1 comment

Comments

@huard
Copy link

huard commented Jul 17, 2020

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)

@jerstlouis
Copy link
Member

jerstlouis commented Nov 4, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants