ROSO — Relationships between classes when referring to other ontologies such as Commons and CORA to be described.

Consider describing the relationship between classes using EquivalentClass, DisjointClass, etc. For example, Robot and Person seem to disjoint parts of Agent. References to Commons or CORA classes may use EquivalentClass.
IEEE RAS, however, does not provide CORA-owl officially. Is it possible to refer them in OWL?

Relationships between classes when referring to other ontologies such as Commons and CORA to be described.

Definitions in Commons 1.1 are imported to the model (though it is ancillary), and then Figures are replaced with those using ODM prototypes.
Figures 3, 4, and 5 in beta 1.0, which represented classes, are replaced and renumbered to Figures 3, 5, and 7, respectively.
Figures 4 and 6 added to illustrate the hierarchy of properties. (Figure 7 contains both classes and properties.)

• The disjoint relationship between Robot and Person is defined as a class axiom of Robot.
• The domain of isLocatedAt is defined as a union of Point, Region, and Site with ODM stereotypes.
• The domain of hasRole is defined as a union of Agent and AgentGroup. (typo: \cap replaced with \cup)
• Incompatibility between figures and texts revised mostly about range and domain of property (missing axioms added as texts).
• The range and domain of actedOn is inverted.
• Removed AgentGroup from range or domain of properties in RoboticServiceInteractionOntology.

No particular relationship between RoSO and IEEE CORA is represented since RoSO is defined as independent from CORA.