Hi everyone - I'm looking for a description of the business glossary file format. In particular, I would like to know which relationships types I can specify among business terms. The example yml file provided only contains the relationship elements "contains" and "inherits" (https://github.com/linkedin/datahub/blob/master/metadata-ingestion/examples/bootstrap_data/business_glossary.yml). My goal is to specify e.g. that "Glossary Term A" RELATES TO "Glossary Term B".

@stocky-noon-61140 Currently, these are the only modeled relationships. We can add another relationship type too to the model. Would love to understand the use-case and an example that you had in mind

@loud-island-88694 I cannot find the "inherits" and "contains" relationship in the file you referenced.

They are named "IsA" for inherits and "HasA" for contains

Ah, I just had the impression that I figured out that: hasRelatedTerms = 'Contains', isRelatedTerms = 'Inherits',

So back to your use-case, it looks like we need to add a different relationship type

@stocky-noon-61140 exactly- hasRelatedTerms = Contains, isRelatedTerms = Inherits. Do the current relationship types support your use cases?

@green-football-43791 @loud-island-88694 I don't really see the difference between "has related terms" and "is related". If GLOSSARY TERM A has a related GLOSSARY TERM B; then GLOSSARY TERM A is also a related term of GLOSSARY TERM B and vice versa. So I don't see the distinction between 'contains' and 'inherits'. Also, from a technical perspective, are there any consequences of having contained / inherited glossary terms? To me it appears that linking glossary terms in this way (either by having "contained" or "inherited" glossary terms) has no effect. Looking forward to your feedback!

@stocky-noon-61140 - you are correct- there is no technical effect of these linkings, aside from the related terms appearing in the glossary term's page.