further changes to make the PePPOl Qalification Rejection become a "r…

…eal" Qualification Response

guides/transactions/T023/codes/code-list-element.adoc

@@ -9,6 +9,5 @@
 | cbc:AdmissionCode
 | Document location
 | __cac:QualificationResolution/cbc:AdmissionCode__
-| Fixed Value
-|  `false`
+|  `true`, `false`
 |===

guides/transactions/T023/descriptions/index.adoc

@@ -8,12 +8,12 @@ The transaction including business terms, business rules and code lists are base
 
 == Identifier
 
-=== Qualification Rejection Identifier
+=== Qualification Response Identifier
 
 The identifier enables positive referencing the transaction instance for various purposes including referencing between transactions that are part of the same process. Must be expressed as a UUID.
 
 [source,xml,indent=0]
-.Example of qualification rejection document identifier
+.Example of qualification response document identifier
 ....
 include::../files/QualificationResponse.xml[tags=ID]
 ....
@@ -100,12 +100,12 @@ The Qualification Response Resolution is the central part of any Qualification R
 *The Qualification Response Resolution returned with this transaction may be positive or negative*. It is expected to respond every rejection but it is also possible to respond any acceptance. If more than one lot have been aimed to qualify for and need to be responded, one Qualification Response Resolution for each lot is expected.
 
 [source,xml,indent=0]
-.Example of Qualification Rejection Resolution
+.Example of Qualification Response Resolution
 ....
 include::../files/QualificationResponse.xml[tags=QualificationResolution]
 ....
-<.> Gives the qualification result. If the result ist *false*, it states that the Tenderer is not allowed to attend the further Procurement Process. Any qualification rejection is required to be answered with *false*. A positive answer resulting in *true* may also be given, but is not necessarily requested.
-<.> If the decision leading to a Qualification Rejection Resolution can be explained in one or more Reason for Rejection elements. The Qualification Rejection Resolution is expected be te described in plain text. At least one Reason for Rejection element should be provided.
+<.> Gives the qualification result. If the result ist *false*, it states that the Tenderer is not allowed to attend the further Procurement Process and the (generally neutral) qualification response can alo be seen as qualification rejection. Any qualification rejection is required to be answered. A positive answer resulting in *true* may also be given, but is not necessarily requested.
+<.> If the decision leading to a Qualification Rejection, the Reason for Rejection  can be explained in one or more resolution elements. The Qualification Rejection Resolution is expected be te described in plain text. At least one Reason for Rejection element should be provided. A positive answer may be sent without a specific resolution element.
 <.> The Date at which the decision expressed in this Qualification Rejection Resolution was made.
 <.> The ProcurementProjectLot referenced in this Qualification Response
 <.> The ProcurementProjectLot's ID

guides/transactions/T023/files/QualificationResponse.xml

@@ -63,9 +63,7 @@
     </cac:QualificationResolution>
     <!-- end::QualificationResolution[] -->
     <cac:QualificationResolution>
-        <cbc:AdmissionCode>false</cbc:AdmissionCode>
-        <cbc:Resolution>limited turnover</cbc:Resolution>
-        <cbc:Resolution>criminal conviction - money laundering</cbc:Resolution>
+        <cbc:AdmissionCode>true</cbc:AdmissionCode>
         <cbc:ResolutionDate>2023-01-07</cbc:ResolutionDate>
         <cac:ProcurementProjectLot>
             <cbc:ID>765a9937-16d5-4513-92b4-cc9800925951::3</cbc:ID>

rules/peppol-qualification/PEPPOL-T023.sch

@@ -93,14 +93,11 @@
             <assert id="PEPPOL-T023-R039" flag="fatal" test="cbc:AdmissionCode">Element 'cbc:AdmissionCode' MUST be provided.</assert>
             <assert id="PEPPOL-T023-R040" flag="fatal" test="cbc:ResolutionDate">Element 'cbc:ResolutionDate' MUST be provided.</assert>
         </rule>
-        <rule context="ubl:TendererQualificationResponse/cac:QualificationResolution/cbc:AdmissionCode">
-            <assert id="PEPPOL-T023-R041" flag="fatal" test="(not(cbc:AdmissionCode = false()))">AdmissionCode MUST always be "false" in a Qualification Resolution.</assert>
-        </rule>
         <rule context="ubl:TendererQualificationResponse/cac:QualificationResolution/cbc:Resolution">
-            <assert id="PEPPOL-T023-R042" flag="fatal" test="(not(cbc:Resolution))">Each Qualification Response Resolution element has to have one Reason for response.</assert>
+            <assert id="PEPPOL-T023-R042" flag="fatal" test="(../cbc:AdmissionCode = 'false' and not(cbc:Resolution))">Qualification Resolution Element with cbc:AdmissionCode 'false'  has to have at least one Resolution element.</assert>
         </rule>
         <rule context="ubl:TendererQualificationResponse/cac:QualificationResolution/cac:ProcurementProjectLot">
-            <report id="PEPPOL-T023-R044" flag="warning" test="(not(cac:ProcurementProjectLot))">If a Qualification Response Resolution has to be expressed for more than one lot in a procurement, a dedicated reason for response be given per lot and the appropriate lot identifier SHOULD be named.</report>
+            <report id="PEPPOL-T023-R044" flag="warning" test="(not(cac:ProcurementProjectLot))">If a Qualification Response Resolution has to be expressed for more than one lot in a procurement, the appropriate lot identifier SHOULD be named.</report>
         </rule>
     </pattern>
 </schema>