How to best treat multiple parent classes in original schema

TypeDB
1

Hi all,

We wanted to migrate from our old ontology to TypeDB but faced the problem of a couple of classes being defined with several parent classes. I know that ideally, one resolves this by making a very new schema design, where these semantics are rather captured with role plays. Assuming one would like to get the most literal conversion of OWL to TypeDB, what would be your best approach in handling multiple parent classes? E.g., inheriting from one and defining the inherited attributes (data props) and role plays (object props) from the other parent class as additional features?

Many thanks in advance!

2

I think this is the cleanest way. I can’t really think of other ways to do it, especially not for a general schema

1 Like
3

Thank you! Do you have any recommendations on guidelines on what to define as entity, attribute, or relation respectively? So assuming one has a bunch of relevant concepts (e.g., the owl classes and object properties). How would you approach the questions of what should become an entity or a relation?

Many thanks again!