Mismatch Between CAS JSON Implementation and Documentation on `rank` Field Data Type

[ubyndr]

Hi @dosumis,

We noticed an inconsistency between our existing CAS JSON files and the documentation for the cell annotation schema in BICAN_schema.md.

In our current CAS JSON files, we have been using string values for the rank field. However, according to the documentation:

• rank (integer): A number indicating relative granularity with 0 being the most specific. This is intended for cases where a single dataset has multiple keys used consistently to record annotations at different granularity levels.

Given this, should we:

1. Update the existing CAS files to store rank as an integer, aligning with the documentation?
2. Adjust the documentation to reflect our current usage of string values in CAS JSON files?

Your guidance on this would be greatly appreciated. cc @hkir-dev

Thank you!

[hkir-dev]

Cas instances should align with the schema, value should be int.

I remember that we solved this issue in the cas-tools. However, some of the older taxonomies may still have this. Cas-tools should be able to read both versions to support older cas files, but it should write int.