# Feedback requested: Versioning for ROR schema and API

**URL:** <https://community.crossref.org/t/feedback-requested-versioning-for-ror-schema-and-api/3107>\
**Category:** Questions from Crossref\
**Tags:** ror\
**Created:** [9 November 2022 22:32 UTC](https://community.crossref.org/t/feedback-requested-versioning-for-ror-schema-and-api/3107 "2022-11-09T22:32:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![amandafrench](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/amandafrench/32/710_2.png) [@amandafrench](https://community.crossref.org/u/amandafrench)\
**Post date:** [9 November 2022 22:32 UTC](https://community.crossref.org/t/feedback-requested-versioning-for-ror-schema-and-api/3107/1 "2022-11-09T22:32:04Z")

</div>

We know that the ROR [metadata schema](https://ror.readme.io/docs/ror-data-structure) and [API](https://api.ror.org/organizations) will need to change in the future, and therefore they need to be versioned. **We’re proposing to version the API and the schema together,** so that when a new major schema version is introduced, the API will also be versioned so that users can unambiguously request a response in a specific schema version.

What do you think? Comment on the [proposal for handling schema and API versioning in ROR](https://docs.google.com/document/d/1882i-nUt8rqhd1bLqMJ3hF-wq5i8HYktUYmN_gUR1xM/edit?usp=sharing) by **November 20**.

Note that we do already have [versioning for the registry itself](https://github.com/ror-community/ror-updates/releases), the data, so this proposal only applies to the API and to the metadata schema.

We rely on your help! As always we’re especially interested in hearing from current and potential ROR adopters, but anyone with strong opinions on the subject is also more than welcome to comment.