Cardinality restriction of `epo:hasMainActivity` causes SHACL shape violation

[csnyulas]

As described in issue https://github.com/OP-TED/eForms-SDK/issues/1186, we have encountered many notices where both the "Activity Authority" (field BT-10-Procedure-Buyer) and the "Activity Entity" (field BT-610-Procedure-Buyer) is specified. I assume that this is wrong, but given the prevalence of this situation, I wonder whether this is really a potentially valid way of describing the buyer activity type, and would make sense to either

• relax the cardinality restriction of the epo:hasMainActivity property, OR
• provide multiple properties (perhaps sub-properties of epo:hasMainActivity) to differentiate between the main activity of the "entities" vs. "authorities".

If the ePO model is left like it is now, the notices that have both "Activity Authority" and the "Activity Entity" specified (several examples of which are listed in issue https://github.com/OP-TED/eForms-SDK/issues/1186) will result in SHACL constraint violation.

[andreea-pasare]

As of ePO 5.0.0, the cardinality for epo:hasMainActivity is modified from [0..1] to [0..*]:

Also, for a comprehensive explanation on the topic, see discussion: https://github.com/OP-TED/eForms-SDK/discussions/729#discussioncomment-7312576