In current version of tapi there is a min-elements constraint (eq 2) for list of SIPs.
This makes perfect sense at conceptual level - to create any connectivity service this is minimal value.
However it is impractical from development perspective - e.g. while system is starting and doing discovery gradually you are not able to add first SIP independently of others.
I suggest to remove this constraint from the model
In current version of tapi there is a min-elements constraint (eq 2) for list of SIPs. This makes perfect sense at conceptual level - to create any connectivity service this is minimal value. However it is impractical from development perspective - e.g. while system is starting and doing discovery gradually you are not able to add first SIP independently of others. I suggest to remove this constraint from the model