# Scheduling breaking changes we have on our radar

**URL:** <https://forum.openrefine.org/t/scheduling-breaking-changes-we-have-on-our-radar/1410>\
**Category:** Development & Design\
**Created:** [March 25, 2024, 9:27am UTC](https://forum.openrefine.org/t/scheduling-breaking-changes-we-have-on-our-radar/1410 "2024-03-25T09:27:28Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![DaxServer](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/daxserver/32/1082_2.png) [@DaxServer](https://forum.openrefine.org/u/DaxServer)\
**Post date:** [June 4, 2024, 6:37am UTC](https://forum.openrefine.org/t/scheduling-breaking-changes-we-have-on-our-radar/1410/12 "2024-06-04T06:37:51Z")

</div>

> - REST API protocol review/update, versioning and documenting as a public API (could be broken into two or items)

I would suggest adopting the OpenAPI Specification. This enables a standardized API development and fast tracks API consumers alleviating the need to develop an API client themselves as [OpenAPI Client Generators](https://openapi-generator.tech/) do them with a single command. In fact, the Server Generators support Java may be used to generate server-side code. With this spec also comes the ability for a [Swagger UI](https://swagger.io/tools/swagger-ui/) and Documentation Generators.

---

_[View the full topic](https://forum.openrefine.org/t/scheduling-breaking-changes-we-have-on-our-radar/1410)._