Parameterized requests to data resources

[clange]

trafficstars

In applications of the IDS (concretely: https://www.mobility-data-space.de/) the requirement is coming up to re-introduce a parameterization of datasets as we had it in previous infomodel versions but, back then, without any alignment with standards and without any backing by use cases. Here, the use case is a dataset with mobility-related information, e.g., road construction sites, which can be filtered by region. We should consider OpenAPI.

[jlangkau]

For shure, A totaly different way to solve a problem to execute a function... but our solutions will follow this idea:

https://fno.io/spec/

Here someone can see, how we bring to service (but this example is a little bit buggy, and a starting point only):

https://github.com/nicosResearchAndDevelopment/nrd-GAIAboX/blob/master/gbx.P/BO/time/P.BO.time.before.md

...and: „yes, not IDS flavoured so far“, but openAPI is a flavour, too...

[rob-metalinkage]

The OGC is already building a set of canonical API profiles for spatial features based on OpenAPI - the OGC API. This is in active development, so testing it against your need and providing feedback if it falls short would be preferable to re-inventing this wheel. see https://ogcapi.ogc.org/

[ghobona]

@clange

Based on the use case described above, I would encourage you and @International-Data-Spaces-Association to look into implementing a solution based on the OGC API - Features standard.

Developer-friendly OpenAPI definitions are available , as well as a tutorial.