Case Sensitivity in translations

Hi everyone

We've had a request in to consider the most appropriate course of action for implementers of translations, when it comes to case sensitivity.

For example with the Spanish Edition, many translations that didn't have legacy commitments to start every description with uppercase, were translated with the initial character using the appropriate case option for the Spanish language. After the English edition changed the case sensitivity for more than 700,000 descriptions (adding a new state for them - see here: https://snomed.atlassian.net/wiki/display/RMT/SNOMED+CT+July+2017+International+Edition+-+SNOMED+International+Release+notes), the editions that didn't use mandatory initial uppercase continued using entire sensitive or entire insensitive for new and modified translations.

So the question for translation implementers is whether or not to now change the initial character to reflect the appropriate case instead of the mandatory one?

As this would add another 700,000 description changes (and therefore a large delta to the Spanish Edition and other translation products), it would be good to first ensure that stakeholders would see value in such a change, in order to align and be consistent across editions?

How would we determine the impact of such a proposed batch change?

If we were to change the initial CAP, would that obviate the need for "cI" (initial character case insensitive) and require a reassignment of the case sensitivity for those concepts, leaving us only with "ci" and "CS" ?

Or is there perhaps a viable alternative to all this that would work better?

Thanks very much!
Andrew