Groups of properties
This XSD diagram shows the sub-components of a group of criteria:
Figure 36. cac:TenderingCriterionPropertyGroup - XSD Schema, global view
One group of properties may include one or more 'sub-groups' of properties (class cac:SubsidiaryTenderingCriterionGroup).
Notice that: One sub-group of properties 'is a' group of criteria:
Figure 37. cac:SubsidiaryTenderingCriterionGroup- XSD Schema
Expected elements
Table 22. Groups of properties, expected elements
Class name: |
cac:TenderingCriterionPropertyGroup |
Definition: |
The first level group of properties and sub-groups of properties in the structure of a criterion. |
Business rule(s): |
Common (BR-TC-07, BR-TC-16) |
File: |
ubl-2.3/xsdrt/common/UBL-CommonAggregateComponents-2.3.xsd |
Path: |
/QualificationApplicationRequest/cac:TenderingCriterion/cac:TenderingCriterionPropertyGroup |
| Components | Type | Card | Description | Requirements |
|---|---|---|---|---|
cbc:ID |
Identifier |
1 |
Identifies a group of requirements uniquely. |
Information Requirement: tbr070-013. Rule: Compulsory use of the UUIDs supplied by e-Certis. See also the spreadsheet ESPD-criterion. Rule scope: Common (BR-TC-12, BR-OTH-02, BR-OTH-02#01) |
cbc:PropertyGroupTypeCode |
Code |
1 |
Code addressed to control the behavior of the group of criteria. |
Information Requirement: tbr070-013. Rule: Compulsory use of the Code List PropertyGroupType. See sections below about the 'criteria data structures' and the XML examples on exclusion and selection criteria to understand the use of this code. Beware that the first element inside a group of properties (after the group ID) is always a cac:TenderingCriterionProperty. In some occasions this might entail the use of an empty CAPTION element, for instance, to produce groups of subgroups where no property does really makes sense in the first group. See also the sub-section The ONTRUE/ONFALSE codes for GROUP and SUBGROUP control Rule scope: Common (BR-TC-14, BR-TC-15, BR-OTH-01, BR-OTH-01#11, BR-OTH-03) |
cac:TenderingCriterionProperty |
Class |
1..n |
Caption (i.e. a 'label'), specific MS or buyer requirement (e.g. 'Number of references expected: 5' or a question addressed to the economic operator (e.g. 'Your average yearly turnover for the past three years?'. |
Information Requirement: tbr070-013. Rule: See the rules for the class in the tables below to see the rules related to criterion properties. See also the XML examples provided in sections about exclusion and selection criteria. |
cac:SubsidiaryTenderingCriterionPropertyGroup |
Class |
0..n |
A second, third or n-level group inside a first level group of properties. |
Information Requirement: tbr070-013. Rule: subsidiary property groups 'are' property groups (i.e. it is the same component but qualified as 'subsidary'). Therefore all the rules applicable to property groups are also applicable to sub-groups: Compulsory use of the Code List PropertyGroupType. See sections below about the 'criteria data structures' and the XML examples on exclusion and selection criteria to understand the use of this code. Beware that the first element inside a group of properties (after the group ID) is always a cac:TenderingCriterionProperty. In some occasions this might entail the use of an empty CAPTION element, for instance, to produce groups of subgroups where no property does really makes sense in the first group. |
XML Examples
-
See examples in sections about exclusion and selection criteria. Study:
-
How GROUPS (cac:TenderingCriterionPropertyGroup) and SUB-GROUPs (cac:cac:SubsidiaryTenderingCriterionPropertyGroup) are organised, and
-
How the codes ON*, ONTRUE and ONFALSE are used.
-
-
You will notice in the examples that the elements cbc:Name and cbc:Description of groups and subgroups of properties are never used. As a common practice the ESPD documents use instead a first cac:TenderingCriterionProperty of type CAPTION (i.e. an informative property that act as a 'label').
