The following realization proposal builds on adding an abstract class as an intermediate layer. Consider the following descibed steps, shown also graphically in the image attached. In addition a sample implementation is available in the attached package.

Sample Realisation of Solution 1: as attachment to this post


a) Abstract class is introduced to define all attributes necessary for the sub-class.
b) E has aRx and bR‘y, so it can be modelled. As bRy is semantically not the same as bR‘y, queries need to consider both (e.g. a union of bRy and bR‘y)

Liitteet:

CIDOC_MultipleInheritance_Implementation-1_FINAL.zip (214,9k), MultipleInheritancec_Implementation1.png (55,5k)

The following realization proposal builds on pointers as relations. Consider the following descibed steps, shown also graphically in the image attached. In addition a sample implementation is available in the attached package.

Sample Realisation of solution 2b - Version 1: as attachment to this post
Sample Realisation of solution 2b - Version 2: as attachment to this post

a) Abstract class is introduced to define all attributes necessary for the sub-class.
b) New additional pointer is introduced.
c) E has aPx, bPy and ePy, so it can be modelled as pointer and can be queried by pointer name. For visual represenation of the pointer, additional drawing of generic relation is necessary. As pointers are instance attributes, the search needs to consider the query of instance attributes.

Liitteet:

CIDOC_MultipleInheritance_Implementation-2b_1.1_FINAL.zip (223,8k), CIDOC_MultipleInheritance_Implementation-2b_FINAL.zip (221,7k), MultipleInheritancec_Implementation2b__.png (106,9k)

The following realization proposal builds on a script-based resolution approach. Consider thesample implementation as available in the attached package.

Sample Realisation of Solution 4: as attachment to this post

Liitteet:

CIDOC_MultipleInheritance_Implementation-4_FINAL.zip (231,2k), MultipleInheritancec_Implementation4_.png (103,3k)