representing synonyms in transport metadata

[grispin]

With all the discussion around synonyms at the Sprint 2024 conference, should we consider representing the synonyms that are in-use for an implementation in the transport metadata?
This was brought up in a few side discussions so I wanted to capture it here for a wider discussion.

The use-cases that were mentioned that I do remember from the conversations were:

• During migration of field names to communicate to clients the renaming. This could allow the client to know about the rename and not need to resync to align their data set
• Communicating localized synonyms that are not part of the RESO standard synonyms
• Data aggregators that re-structuring the upstream data to a standardized model. Allows the downstream consumer to know what the field name was in the originating system when a transform as occurred

If anyone has a good or counter use-case please add it.