I have found that a major flaw with the Relationship Service Spec is that it doesn't recognize the semantics of the relationships
and therefore, doesn't enable the management of the relationship data, which cannot exist independently of the object data.

Please forward my proposed remedy, available at the following link, to the contributors
http://www.geocities.com/unifiedmodel/ManagingRelationships.htm

Summary: RelationshipHandle seems to have no purpose, unless it is being used for lazy instantiation of the Relationship.

The declaration of CosRelationships::RelationshipFactory::create does not
mention the DuplicateRoleName exception in its raises clause. The
specification (formal/00-06-24) states that Role names must be unique within
each relationship type. Is this an error in the IDL?

CosGraphs::Node interface provides a function add_role() which helps in adding a new role to the related
object the Node is representing. The specifications suggests to raise an exception DuplicateRoleType
if the new role is same, subtype, supertype of one of the role of the Node object.

What if the user of function calls add_role() with a role for an object which is not represented by this node.
Definitely we cannot add the new role to the Node. Only thing we can do here is return out of function.
But user will not be aware that the function has failed, since the return type is void.

Summary: DuplicateRoleName exception is defined in CosRelationships but is left out in the declaration of the create()
method of the RelationshipFactory interface !!!!
In the spec for the Relationships Services, DuplicateRoleName is thrown in the create() method of the
relationships factory.
Is this a typo, an error, a modification or what ????
Where do we report these things?

Summary: If Role requires the Related Object to be a Node (e.g. CocContainment), must Node return itself as related_object attribute or can there be a different related Object

Summary: CosGraphs::Role cannot obtain a knowledge of its node. Therefore, CosGraphs::Role::get_edges() cannot be fully supported, nor can the Traversal interface.