-
|
BT-10-Procedure-Buyer and BT-610-Procedure-Buyer are both mandatory for SubType 5 and 8. BT-610-Procedure-Buyer: {
"noticeTypes" : [ "3", "6", "9", "13", "14", "18", "19", "21", "26", "27", "28", "31", "32", "34", "35", "E1", "E2", "E3", "E4", "E5" ],
"condition" : "{ND-ContractingParty} ${BT-11-Procedure-Buyer not in ('pub-undert','pub-undert-cga','pub-undert-la','pub-undert-ra','spec-rights-entity')}",
"value" : true,
"severity" : "ERROR"
}BT-10-Procedure-Buyer: {
"noticeTypes" : [ "2", "3", "5", "6", "8", "9", "11", "12", "13", "14", "15", "17", "18", "19", "20", "21", "24", "25", "26", "27", "28", "30", "31", "32", "33", "34", "35", "37", "E1", "E2", "E3", "E4", "E5", "T01", "T02" ],
"condition" : "{ND-ContractingParty} ${BT-11-Procedure-Buyer not in ('body-pl','body-pl-cga','body-pl-la','body-pl-ra','cga','def-cont','eu-ins-bod-ag','grp-p-aut','int-org','la','org-sub','org-sub-cga','org-sub-la','org-sub-ra','ra')}",
"value" : true,
"severity" : "ERROR"
}This is fine by schema and schematron, but we see no reason why both fields should be required, as it makes no sense for most cases. What is the intended behaviour for subtypes 5 and 8? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
Hi,
As this is not an SDK issue, I'm converting this into a discussion.
For form 5, 8 and some others under Directive 25, BT-610 (Acivity Entity) is mandatory while BT-10 (Activity Authority) is conditionally mandatory (cf. Regulation Annex).
These forms are normally for Contracting Entities (hence BT-610 mandatory) and is also used by Contracting Authorities acting as Contracting Entities (in which case BT-10 and BT-610 are expected).
Regarding the rule that applies on form 5, 8 for BT-10, its presence requirement (forbidden or mandatory) is determined based on the value of the Buyer Legal Type associated to the Buyer. As long as the Buyer and its legal type have not been identified, app…