Exclusion Ground (xml structure and rule BR-BT-00067-0104

[rkottmann]

We found two interrelated issues w.r.t. to exclusion (maybe it also applies to selection-criteria):

The following structure throws BR-BT-00067-0104 as an error:

<cac:TenderingTerms>
        <cac:ProcurementLegislationDocumentReference>
            <cbc:ID>vgv</cbc:ID>
        </cac:ProcurementLegislationDocumentReference>
        <cac:TendererQualificationRequest>
            <cac:SpecificTendererRequirement>
                <!--BT-806-Procedure (Order: 03)-->
                <cbc:TendererRequirementTypeCode listName="exclusion-grounds-source">epo-notice</cbc:TendererRequirementTypeCode>
            </cac:SpecificTendererRequirement>
            <cac:SpecificTendererRequirement>
                <!--BT-67(a)-Procedure (Order: 03)-->
                <cbc:TendererRequirementTypeCode listName="exclusion-ground">exg-natl-bre-nat-law</cbc:TendererRequirementTypeCode>
                <!--BT-67(b)-Procedure (Order: 04)-->
                <cbc:Description languageID="DEU">Gemäß § 123, 124 GWB, § 57, 42 Abs. 1 VgV und § 16 VOB/A</cbc:Description>
            </cac:SpecificTendererRequirement>
        </cac:TendererQualificationRequest>
    </cac:TenderingTerms>

The way the rule context is defined it matches cac:TendererQualificationRequest two times, although it should only exactly match the TendererRequirementTypeCode once. The reason for matching also the other is that the context logically says "please test TendererRequirementTypeCode if there is a TendererQualificationRequest having at least one cac:SpecificTendererRequirement/cbc:TendererRequirementTypeCode/@listName='exclusion-ground' which is true also for the BT-806:

<!-- codelist omitted for brevity -->
<rule context="/*/cac:TenderingTerms/cac:TendererQualificationRequest[cac:SpecificTendererRequirement/cbc:TendererRequirementTypeCode/@listName='exclusion-ground']/cac:SpecificTendererRequirement/cbc:TendererRequirementTypeCode">

  <assert id="BR-BT-00067-0104" role="ERROR" test="normalize-space(.) = ('exg-crim-corrpt', ...)">rule|text|BR-BT-00067-0104</assert>

  <assert id="BT-67_a_-Procedure-List_MA" role="ERROR" test="count(@listName) > 0">rule|text|BT-67_a_-Procedure-List_MA</assert>
  <assert id="BT-67_a_-Procedure_WS" role="ERROR" test="normalize-space(.) eq .">rule|text|BT-67_a_-Procedure_WS</assert>
</rule>
 

The second issue might be (depending on the specification, we are not sure about) that you DO NOT expect to have both SpecificTendererRequirement for exclusion ground and for exclusion grounds source inside the same TendererQualificationRequest. Most probably you require them to be separated, like this:

  <cac:TenderingTerms>
        <cac:ProcurementLegislationDocumentReference>
            <cbc:ID>vgv</cbc:ID>
        </cac:ProcurementLegislationDocumentReference>
        <cac:TendererQualificationRequest>
            <cac:SpecificTendererRequirement>
                <!--BT-806-Procedure (Order: 03)-->
                <cbc:TendererRequirementTypeCode listName="exclusion-grounds-source">epo-notice</cbc:TendererRequirementTypeCode>
            </cac:SpecificTendererRequirement>
        </cac:TendererQualificationRequest>
        <cac:TendererQualificationRequest>
            <cac:SpecificTendererRequirement>
                <!--BT-67(a)-Procedure (Order: 03)-->
                <cbc:TendererRequirementTypeCode listName="exclusion-ground">exg-natl-bre-nat-law</cbc:TendererRequirementTypeCode>
                <!--BT-67(b)-Procedure (Order: 04)-->
                <cbc:Description languageID="DEU">Gemäß § 123, 124 GWB, § 57, 42 Abs. 1 VgV und § 16 VOB/A</cbc:Description>
            </cac:SpecificTendererRequirement>
        </cac:TendererQualificationRequest>
    </cac:TenderingTerms>

In case our assumption is correct, then the additional bug is that you do not have a rule to enforce this structure.

Note: the problem is only present since eforms-sdk-1.12, because rule context was different in eforms-sdk-1.10:

<!-- codelist omitted for brevity -->
<rule context="/*/cac:TenderingTerms/cac:TendererQualificationRequest/cac:SpecificTendererRequirement/cbc:TendererRequirementTypeCode[@listName='exclusion-ground']">

  <assert id="BR-BT-00067-0104" role="ERROR" test="normalize-space(.) = ('bankr-nat', ....)">rule|text|BR-BT-00067-0104</assert>

</rule>

[YvesJo]

Hi,

Field BT-806-Procedure has:
full XPATH /*/cac:TenderingTerms/cac:TendererQualificationRequest[cac:SpecificTendererRequirement/cbc:TendererRequirementTypeCode/@listName='exclusion-grounds-source']/cac:SpecificTendererRequirement/cbc:TendererRequirementTypeCode
Parent node: ND-ExclusionGroundsSource
Grandparent node: ND-TendererQualificationRequestSources

BT-67(a)-Procedure and BT-67(b)-Procedure have:
Full XPATHS /*/cac:TenderingTerms/cac:TendererQualificationRequest[cac:SpecificTendererRequirement/cbc:TendererRequirementTypeCode/@listName='exclusion-ground']/cac:SpecificTendererRequirement/cbc:TendererRequirementTypeCode
and /*/cac:TenderingTerms/cac:TendererQualificationRequest[cac:SpecificTendererRequirement/cbc:TendererRequirementTypeCode/@listName='exclusion-ground']/cac:SpecificTendererRequirement/cbc:Description

Parent node ND-ExclusionGrounds
Grandparent node ND-TendererQualificationRequest

Grandparent nodes differ for both cases.

KR

[YvesJo]

Issue converted to a discussion as this is not a Bug