FBEF — Revise the CorporateControl ontology to eliminate potential reasoning issues related to hasRole

Testing with various reasoners and test data shows that reasoning over the hasRole relationship in some circumstances returns incorrect results. Replacing the hasRole property with isPlayedBy corrects this issue.

A handful of minor discrepancies in annotations that were missed via corrections for mechanical / syntax changes to the CorporateControl ontology should also be addressed. These include a number of missing labels, particularly on properties, as well as missing datatypes for some annotations.

There is also a bug in the VOM model with respect to duplicate proxy classes for IncorporatedCompany, one in the main model folder and one in the Proxies folder. These should be reconciled to eliminate the MagicDraw null pointer exception that arises when one attempts to find related information when clicking on one or the other proxy class.

Note that there are also missing definitions for properties and classes in this ontology that should be addressed under a separate issue.

Revise the CorporateControl ontology to eliminate potential reasoning issues related to hasRole

Testing with various reasoners and test data shows that reasoning over the hasRole relationship in some circumstances returns incorrect results. Replacing the hasRole property with isPlayedBy corrects this issue.

A handful of minor discrepancies in annotations that were missed via corrections for mechanical / syntax changes to the CorporateControl ontology should also be addressed. These include a number of missing labels, particularly on properties, as well as missing datatypes for some annotations.

There is also a bug in the VOM model with respect to duplicate proxy classes for IncorporatedCompany, one in the main model folder and one in the Proxies folder. These should be reconciled to eliminate the MagicDraw null pointer exception that arises when one attempts to find related information when clicking on one or the other proxy class.

Note that there are also missing definitions for properties and classes in this ontology that should be addressed under a separate issue.