Consider requirements around bundles of direct and indirect interests in a relationship

[kd-ods]

Summary of the bug or issue
At the moment (as of BODS 0.3 and 0.4) there is a lack of clarity about what to do when a person has direct AND indirect interests in an entity. These interests may be bundled together in the Interests array of a single relationship statement. But then, if componentRecordIds is used to lay out which are the intermediaries for some of the indirect interests, it may not be clear which indirect interests are composed of those intermediaries. In such circumstances, should two Relationship statements between the entity and the person be created?

Suggested resolution
With the renaming of Ownership-or-control Statements to Relationship Statements, there is the opportunity to use the clarity of the conceptual model to improve the data model. In particular, it seems natural to talk of an individual having both a direct and an indirect relationship with an entity. So we should consider:

• moving the indirectOrDirect property up a level, to sit at the top level of recordDetails for a relationship
• requiring that where an individual has direct AND indirect interests in an entity the publisher creates two relationship statements: one with indirectOrDirect: 'direct' and one with indirectOrDirect: 'indirect'