Osma Suominen

Ah, that makes sense. Then perhaps the response for the whole batch could contain both results and errors like you say, and the errors could be represented as Problem JSON...

Yes, using the order would work too. I'm OK with that as well - just want to get rid of the arbitrary keys. Newline delimited JSON (known as NDJSON or...

That's a valid concern @wetneb. As you say, an OpenAPI spec is generally specific to a particular instance living at a particular server URL. My understanding of OpenAPI/Swagger is also...

What's the reason for having such dynamic URLs? Is it really a necessary feature? One possible way around this would be to have separate OpenAPI specs for each service/path. Each...

Thanks @wetneb for the clarification, I understand the rationale for multiple endpoints, which implies some level of dynamic URLs. > One alternative to these dynamic URLs would be to do...

I'm all for improving the API, but...if we did big changes like this in the spec, could we except OpenRefine to implement support for the modernized API soon-ish? I'm thinking...

Thanks @stefanw for your input, it's very valuable to have actual, recent implementation experience! > I would have gladly used any kind of library that could have made the implementation...

Yes, we are struggling with this, as we want to be able to replicate most changes in YSA and Allärs to YSO. But YSO is maintained using TopBraid Composer (TBC)...

This sounds like a good feature and something I've also thought about in the past. However, it's quite a challenge to do all of this and also ensure data consistency....

> (We could also consider switching to another translation platform - Symfony [supports](https://symfony.com/doc/current/translation.html#translation-providers) Crowdin, Loco and Localise - but that's beyond the scope of this issue). I opened a separate...