Hi Andrii
From a business perspective, I have trouble to imagine an order without any party related (but perhaps there are some UC that did not require it) - that why " Create Product Order API demands RelatedParty as mandatory".
But because, as you noted, relatedParty could be described at product order level or product level, I will be unconfortable with a cardinality 1..* at any level. It will limit flexibility to describe party at product order level only or at product level only in API implementations.
Best regards
------------------------------
Ludovic Robert
Orange
------------------------------
Original Message:
Sent: Jun 06, 2019 04:29
From: Andrii Teslenko
Subject: TMF622 - cardinality of RelatedParty seems to be wrong on resource diagram
Hi all
Please advise how to read TMF622 Open API resource model. Particularly for RelatedPartyRef, it's located under Product Order and Product and for both has cardinality like 0..*, however Create Product Order API demands RelatedParty as mandatory -- at least one RelatedParty to be created.
My question is -- Do we need it mandatory for both either Product or Product Order? I think so, thus imho cardinality should be fixed as 1..* for RelatedParty
------------------------------
Andrii Teslenko
Netcracker Technology
------------------------------