Skip to main content
. Author manuscript; available in PMC: 2015 Mar 1.
Published in final edited form as: IEEE Comput Graph Appl. 2014 Mar-Apr;34(2):26–37. doi: 10.1109/MCG.2014.27

Figure 2.

Figure 2

Example mapping of a datanode ontology from a third-party .NET assembly. The left side of the figure shows a generic .NET class hierarchy containing interfaces, class inheritance, and member fields, properties and methods. The right side of the figure shows the automatically-generated datanode ontology replicating the strongly typed objects and relationships from the .NET assembly. Instance-specific data are maintained on the subclass datanode object (i.e. data are not stored in superclass datanodes) and the fields, properties and methods of the original .NET object are accessible through the DIVE datanodes by virtual properties.