Hello,we are debating currently on the completeness of the "relationship space" in the CUSTOMER TMF 629 API area. Concretely:Most of the Customer's properties are "relationships/references" to foreign domains like "Payment Method", "Account", etc.However, these mostly process-oriented domains, have their own (direct) relationships to "Customer" (aka "relatedParty") , so the reverse relationships in the Customer area are simply for bidirectional navigation, should this be needed.We state/observe however, that the number of direct navigation paths is greater than the number of reverse paths, with one of the most important missing relationship being that to "Product" (Product Inventory). The Product inventory is used by us to design/map customer agreements for private customers (deployed/installed product/service base).Question: How should we understand TMF completeness concern with respect to the Customer relationship space ?
Thanks in advance,
Adrian Ciornei,Deutsche Telekom