Action transfer between source nodes and target nodes

Therefore, I suggest adding a sub-element <ActionTransfers> to Relationship Type to cover all cases mentioned above. < ActionTransfers >? < ActionTransfer direction="forward|reverse|bidirectional" targetAction="anyURL" sourceAction="anyURL">+ </ ActionTransfers > The ActionTransfer element has the following properties:  targetAction: This attribute specifies the action of the target instance of a Relationship Template of this Relationship Type.  sourceAction: This attribute specifies the action of the source instance of a Relationship Template of this Relationship Type.  direction: If set to "forward", the targetAction of the target instance is automatically performed when the sourceAction of the source instance is performed. If set to "reverse", the sourceAction of the source instance is automatically performed when the targetAction of the target instance is performed. If set to "bidirectional", one action (either targetAction or sourceAction) is performed, another one is automatically performed. An example is given as follows. <RelationshipTypes> <RelationshipType id="processIntegratedWith" name="process is integrated with" semantics="www.example.com/RelSemantics/processIntegratedWith" > <RelationshipTypeProperties element="ProcessIntegratedWithProperties"/> < ActionTransfers > < ActionTransfer direction="bidirectional" targetAction=" www.example.com/actions/suspend " sourceAction=" www.example.com/actions/suspend "> < ActionTransfer direction="forward" targetAction="www.example.com/actions/deletion" sourceAction="www.example.com/actions/deletion "> </ActionTransfers > </RelationshipType> </RelationshipTypes> In the example, the property cascadingDeletion is described by the second <ActionTransfer> element.