Once you've loaded your data into a SQLite database and put Datasette in front of it, your audience can get the data out in any shape that they like.

Consider the museum data in my https://www.niche-museums.com/ website.

Using a SQL query, I can get it out as an array of objects with name, url, address, latitude, longitude: https://www.niche-museums.com/browse.json?sql=select+name%2C...

Or maybe I want to get back the name as "title" and the latitude longitude as lat / lng. I can do that with a different SQL query:

    select name as title, latitude as lat, longitude as lng from museums limit 10

Let's say I want it as an Atom feed. Datasette plugins can add different output renderers, so I can get back an Atom feed like this:

https://www.niche-museums.com/browse.atom?sql=SELECT%0D%0A++...

That's using a convoluted SQL query to define exactly what I want back in that feed.

The point is: if you have a sufficiently flexible API gateway in front of your data, the people consuming your data can define the "standard" that they want to retrieve it in at runtime.

I think that's a really interesting characteristic. It's made me less excited about boil-the-ocean attempts at defining a single standard and getting everyone to support it at once.

[ This thread may not be the best place to raise this idea, since the Python Data API Standards project isn't really in the same realm as the web API formats I'm talking about here ]