ALMAS13 — Receiver Hierarchy Error Conditions

Receiver Kind Type should be unique
Parent should have it's own Receiver Kind definition
Parent of a Receiver Kind should not introduce a circularity

Place additional restrictions on Receiver Hierarchy configuration schema

Receiver Kind Type uniqueness should be enforced using an xs:unique element within Receiver_Hierarchy_T acting on //Receiver_Kind/Type and scoped to itself (i.e. the hierarchy content).
Parents should be declared as Receiver_Kind elements containing the elements of which they are parents (their 'children'). This avoids circular dependencies as each name is then only used once and the relationships are structural.
'Parent-Child' isn't a great abstraction for this use case. Having inverted the relationships, 'priority receiver' would be better terminology. Therefore have each Receiver_Kind contain a Priority_Receivers element each with zero-or-more Receiver_Kind elements. Update the description for the file accordingly at the start of section section 7.3
Parent should have it's own Receiver Kind definition
Parent of a Receiver Kind should not introduce a circularity