Hi Community, The previous posts about the business glossary dealt about applying more term types (attribute and entity terms), and how they get context by adding relationship types. This time I want to discuss options to add multilingualism to the glossary. I don’t mean the One Web interface itself, but the content. When your company operates in an international environment, having term names and definitions in just one language may not suffice (although many people understand English, the level of understanding may vary, so translations will contribute to a better understanding of the glossary content). So suppose the glossary contains content in English and, like in my situation, also Dutch translations are required for the term’s name and definition. The most simple solution would be to add properties like nameDutch and businessDefinitionDutch to entity term. And when German translations are required as well, add properties nameGerman and businessDefinitionGerman and so on. The pro
