(This is a sample challenge for the GovTech Hackathon)

Goal

DCAT vs OData, REST vs RDF, Frictionless Data vs GraphQL? Developers and data publishers have a hard time making sense of the Babel's Tower of standards when it comes to metadata exchange and, after decades of evolution and competition - API technologies. With experience and hindsight, we know that some standards fit certain use cases more conditions, have various learning curves, and have slightly different conditions of reuse.

An inspiration for this from our colleagues in the Internet of Things area is the BetterIoT Assessment Tool, which helps early stage hardware startups make a strategy:

Designs

The idea would be to have a "data standards chooser" for publishers and developers, similar to the helpful License Chooser tool from Creative Commons:

Or the even simpler choose a license web page from GitHub:

References

• REST API Industry debate (Medium post)
• SOAP REST OData - What Technology When (WEM)
• Understanding gRPC OpenAPI and REST (Google Blog)
• Data Sharing Principles (GEO, screenshot below)