eForms-SDK icon indicating copy to clipboard operation
eForms-SDK copied to clipboard

BR-BT-00052-0022 rule - incorrect translation?

Open tompeeszter opened this issue 11 months ago • 2 comments

We have noticed the following issue according to the rule: BR-BT-00052-0022 (validation-stage-4-16.sch ).

The rule:

<assert id="BR-BT-00052-0022" role="ERROR" diagnostics="BT-52-Lot" test="
	count(cbc:CandidateReductionConstraintIndicator) &gt; 0 
		or 
	not(../../cac:TenderingProcess/cbc:ProcedureCode/normalize-space(text()) = ('comp-dial','innovation','neg-w-call'))">rule|text|BR-BT-00052-0022
</assert>

The official translation of the rule:

English: The procedure will take place in successive stages. At each stage, some participants may be eliminated' (BT-52-Lot) is mandatory when: 'Type of procedure' (BT-105) must not be either 'Competitive dialogue', 'Innovation partnership'; 'Negotiated with prior publication of a call for competition / competitive with negotiation' (in '16 – Contract notice – general directive, standard regime')

Hungarian: Ez az eljárás több szakaszból áll. Minden szakaszban kiesik néhány résztvevő' (BT-52-Lot) kötelező, amikor: 'Az eljárás típusa' (BT-105) nem lehet 'Versenypárbeszéd', 'Innovációs partnerség'; 'Eljárást megindító felhívás előzetes közzétételével járó tárgyalásos / tárgyalásos' ('16 – Eljárást megindító hirdetmény – általános irányelv, klasszikus ajánlatkérőkre vonatkozó szabályok')

According to the schematron rule BT-52-Lot is mandatory in '16 – Contract notice – general directive, standard regime' if BT-105-Procedure ='comp-dial' or 'innovation' or 'neg-w-call'. Despite this, the translation states that BT-52-Lot is mandatory in '16 – Contract notice – general directive, standard regime' if BT-105-Procedure !='comp-dial' or 'innovation' or 'neg-w-call'. ('must not be' / 'nem lehet').

Could you please investigate this issue?

Thanks in advance!

tompeeszter avatar Jan 23 '25 14:01 tompeeszter

Hi, Indeed the label is stating the contrary of what is expected. This should get fixed with SDK 1.14

YvesJo avatar Jan 23 '25 15:01 YvesJo

Thanks a lot!

tompeeszter avatar Jan 23 '25 15:01 tompeeszter

Addressing multistage procedure has been moved out of SDK 1.14 scope and this will get fixed with SDK 1.15

YvesJo avatar Dec 02 '25 14:12 YvesJo