Internationalization Issues

Registry TC,

Here is another issue from our CC Review work (in addition to the
earlier Slots issue) that I would like to raise up to our TC for
handling. It references the fact that not all RIM attributes are
I18N-capable. This has been identified as an issue within our CC Review
work, as we are making extensive use of Slots. Here is the issue in more
detail:

ISSUE:
Internationalization is missing in certain places. For example, although
Dictionary Entry Names and Definitions can be defined in different
languages for CC/BIEs (according to CCTS spec), Business Terms cannot.
This makes it hard to use the synonym feature in searches.

Currently only RegistryObject.name and RegistryObject.description are
I18N aware. If we start storing I18N-capable strings in Slots, it means
that Slot values must support Internationalization. 

Thanks,
Joe