+
+
+
+
+
+ + + This page has moved to a /en/extensions/additionalContactPoint/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/awardCriteria/master/extension.json b/en/extensions/awardCriteria/master/extension.json
new file mode 100644
index 000000000..951f22f14
--- /dev/null
+++ b/en/extensions/awardCriteria/master/extension.json
@@ -0,0 +1,32 @@
+{
+ "name": {
+ "en": "Award criteria breakdown",
+ "es": "Desglose de los criterios de adjudicaci\u00f3n"
+ },
+ "description": {
+ "en": "Adds an award criteria array to the lot object, to break down award criteria by price, cost and quality.",
+ "es": "Agrega una matriz de criterios de adjudicaci\u00f3n al objeto lote, para desglosar los criterios de adjudicaci\u00f3n por precio, costo y calidad."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/awardCriteria/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "awardCriterionType.csv",
+ "awardCriterionFixed.csv",
+ "criterionWeight.csv",
+ "criterionThreshold.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/en/extensions/awardCriteria/master/index.html b/en/extensions/awardCriteria/master/index.html
new file mode 100644
index 000000000..428ff1763
--- /dev/null
+++ b/en/extensions/awardCriteria/master/index.html
@@ -0,0 +1,422 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Award criteria breakdown +
+ ++ Adds an award criteria array to the lot object, to break down award criteria by price, cost and quality. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ awardCriterionFixed.csv +
+ +
+ You can download the awardCriterionFixed.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ total
+
+ |
+ + Fixed (total) + | +
+ The number is the fixed price or fixed cost for the bid. For example: "The price of a bid must be $100,000." + + |
+
+
+ unit
+
+ |
+ + Fixed (per unit) + | +
+ The number is the fixed price or fixed cost for a unit. For example: "The price of each widget must be $100." + + |
+
+ awardCriterionType.csv +
+ +
+ You can download the awardCriterionType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ price
+
+ |
+ + Price + | +
+ The criterion concerns the acquisition price of the bid. + + |
+
+
+ cost
+
+ |
+ + Cost + | +
+ The criterion concerns any other non-price monetary attribute of the bid. + + |
+
+
+ quality
+
+ |
+ + Quality + | +
+ The criterion concerns a non-price, non-cost attribute of the bid. + + |
+
+ criterionThreshold.csv +
+ +
+ You can download the criterionThreshold.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ minimumScore
+
+ |
+ + Minimum score + | +
+ The number is a minimum score that bids or requests to participate need to receive for the criterion. For example: "A bid must receive 20 points or more for criterion X." + + |
+
+
+ maximumBids
+
+ |
+ + Maximum number of passing bids + | +
+ The number is the maximum number of bids or requests to participate that can pass the criterion. For example: "A bid must receive one of the highest 3 scores for criterion X." + + |
+
+ criterionWeight.csv +
+ +
+ You can download the criterionWeight.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ percentageExact
+
+ |
+ + Weight (percentage, exact) + | +
+ The number is an exact percentage. The numbers must add up to 100. + + |
+
+
+ percentageRangeMiddle
+
+ |
+ + Weight (percentage, middle of a range) + | +
+ The weighting is expressed as a range of percentages. The sum of the minima must be less than or equal to 100. The sum of the maxima must be equal to or greater than 100. + + |
+
+
+ decimalExact
+
+ |
+ + Weight (decimal, exact) + | +
+ The number is an exact finite decimal proper fraction. The numbers must add up to 1. + + |
+
+
+ decimalRangeMiddle
+
+ |
+ + Weight (decimal, middle of a range) + | +
+ The weighting is expressed as a range of finite decimal proper fractions. The sum of the minima must be less than or equal to 1. The sum of the maxima must be equal to or greater than 1. + + |
+
+
+ pointsExact
+
+ |
+ + Weight (points, exact) + | +
+ The weighting is expressed as an exact number of points. + + |
+
+
+ pointsRangeMiddle
+
+ |
+ + Weight (points, middle of a range) + | +
+ The weighting is expressed as a range of numbers of points. + + |
+
+
+ order
+
+ |
+ + Order of importance + | +
+ The number indicates an order of importance. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/awardCriteria/master/release-schema.json b/en/extensions/awardCriteria/master/release-schema.json
new file mode 100644
index 000000000..b797a7c0d
--- /dev/null
+++ b/en/extensions/awardCriteria/master/release-schema.json
@@ -0,0 +1,193 @@
+{
+ "definitions": {
+ "Lot": {
+ "properties": {
+ "awardCriteria": {
+ "title": "Award criteria",
+ "description": "Information about the award criteria for the lot.",
+ "$ref": "#/definitions/AwardCriteria"
+ }
+ },
+ "extension_explorer:source": {
+ "identifier": "awardCriteria",
+ "version": "master"
+ }
+ },
+ "LotGroup": {
+ "properties": {
+ "awardCriteria": {
+ "title": "Award criteria",
+ "description": "Information about the award criteria for the lot.",
+ "$ref": "#/definitions/AwardCriteria"
+ }
+ },
+ "extension_explorer:source": {
+ "identifier": "awardCriteria",
+ "version": "master"
+ }
+ },
+ "AwardCriteria": {
+ "title": "Award criteria",
+ "description": "Information about the award criteria.",
+ "type": "object",
+ "properties": {
+ "weightingDescription": {
+ "title": "Complicated weighting description",
+ "description": "When the weighting cannot be expressed per criterion, the mathematical equation (or other description) that expresses the complicated (e.g. non-linear) weighting.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "orderRationale": {
+ "title": "Justification for order of importance",
+ "description": "The justification for only indicating the award criteria's order of importance, not their weighting.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "criteria": {
+ "title": "Award criteria",
+ "description": "The award criteria.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/AwardCriterion"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "awardCriteria",
+ "version": "master"
+ }
+ },
+ "AwardCriterion": {
+ "title": "Award criterion",
+ "description": "Information about the award criterion.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Type",
+ "description": "The aspect of the bid that the criterion concerns.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "awardCriterionType.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "name": {
+ "title": "Name",
+ "description": "The name of the criterion.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "The description of the criterion.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "numbers": {
+ "title": "Numbers",
+ "description": "Numbers linked to the criterion.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/CriterionNumber"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "awardCriteria",
+ "version": "master"
+ }
+ },
+ "CriterionNumber": {
+ "title": "Criterion number",
+ "description": "Information about a number linked to a criterion.",
+ "type": "object",
+ "properties": {
+ "number": {
+ "title": "Number",
+ "description": "The number.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "weight": {
+ "title": "Weight",
+ "description": "Whether the number is a type of weight.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "criterionWeight.csv",
+ "openCodelist": false,
+ "enum": [
+ "percentageExact",
+ "percentageRangeMiddle",
+ "decimalExact",
+ "decimalRangeMiddle",
+ "pointsExact",
+ "pointsRangeMiddle",
+ "order",
+ null
+ ]
+ },
+ "fixed": {
+ "title": "Fixed",
+ "description": "Whether the number is a fixed value.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "awardCriterionFixed.csv",
+ "openCodelist": false,
+ "enum": [
+ "total",
+ "unit",
+ null
+ ]
+ },
+ "threshold": {
+ "title": "Threshold",
+ "description": "Whether the number is a type of threshold.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "criterionThreshold.csv",
+ "openCodelist": false,
+ "enum": [
+ "minimumScore",
+ "maximumBids",
+ null
+ ]
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "awardCriteria",
+ "version": "master"
+ }
+ }
+ }
+}
diff --git a/en/extensions/awardCriteria/master/schema/index.html b/en/extensions/awardCriteria/master/schema/index.html
new file mode 100644
index 000000000..51860808c
--- /dev/null
+++ b/en/extensions/awardCriteria/master/schema/index.html
@@ -0,0 +1,576 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Award criteria breakdown +
+ ++ Adds an award criteria array to the lot object, to break down award criteria by price, cost and quality. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an award criteria array to the Lot and LotGroup objects, to break down award criteria by price, cost and quality.
Legal context
+In the European Union, this extension's fields correspond to eForms BG-707 (Award Criteria).For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Directive 2014/24/EU Article 67(5) describes weightings and orders of importance.
+Examples
+Lots
+Weight
+The award criteria for the lot are 50% service quality and 50% price.
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "awardCriteria": {
+ "criteria": [
+ {
+ "type": "quality",
+ "name": "Service quality",
+ "numbers": [
+ {
+ "number": 50,
+ "weight": "percentageExact"
+ }
+ ]
+ },
+ {
+ "type": "price",
+ "name": "Price",
+ "numbers": [
+ {
+ "number": 50,
+ "weight": "percentageExact"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Fixed
+The price of the lot is fixed at $100,000, such that tenderers compete on quality only.
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "awardCriteria": {
+ "criteria": [
+ {
+ "type": "price",
+ "name": "Fixed price",
+ "numbers": [
+ {
+ "number": 100000,
+ "fixed": "total"
+ },
+ {
+ "number": 0,
+ "weight": "decimalExact"
+ }
+ ]
+ },
+ {
+ "type": "quality",
+ "name": "Service quality",
+ "numbers": [
+ {
+ "number": 1,
+ "weight": "decimalExact"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Lot group
+The award criteria for the lot group is 100% price.
+{
+ "tender": {
+ "lotGroups": [
+ {
+ "id": "1",
+ "awardCriteria": {
+ "criteria": [
+ {
+ "type": "price",
+ "name": "Price",
+ "numbers": [
+ {
+ "number": 100,
+ "weight": "percentageExact"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2022-04-25
+-
+
- Add requests to participate to
criterionThreshold.csvcode descriptions.
+ - Generalize AwardCriterionNumber to
CriterionNumberfor reuse in other extensions.
+
2022-02-27
+-
+
- Add
LotGroup.awardCriteriafield.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This model was discussed in https://github.com/eForms/eForms/issues/119, https://github.com/eprocurementontology/eprocurementontology/issues/157 and https://github.com/eprocurementontology/eprocurementontology/issues/203. This extension was originally discussed as part of the OCDS for EU profile, in pull requests and in https://github.com/open-contracting/standard/issues/443.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/beneficialOwners/index.html b/en/extensions/beneficialOwners/index.html
new file mode 100644
index 000000000..ead8d8ee1
--- /dev/null
+++ b/en/extensions/beneficialOwners/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Award criteria breakdown +
+ ++ Adds an award criteria array to the lot object, to break down award criteria by price, cost and quality. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ awardCriteria
+
+ |
+ + Award criteria + | +
+ Information about the award criteria for the lot. + + |
+ + AwardCriteria object + | +
+ LotGroup +
+ +
+ The extension defines these fields in the LotGroup object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ awardCriteria
+
+ |
+ + Award criteria + | +
+ Information about the award criteria for the lot. + + |
+ + AwardCriteria object + | +
+ AwardCriteria +
+ +
+ The extension defines a new AwardCriteria object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ weightingDescription
+
+ |
+ + Complicated weighting description + | +
+ When the weighting cannot be expressed per criterion, the mathematical equation (or other description) that expresses the complicated (e.g. non-linear) weighting. + + |
+ + string + | +
+
+ orderRationale
+
+ |
+ + Justification for order of importance + | +
+ The justification for only indicating the award criteria's order of importance, not their weighting. + + |
+ + string + | +
+
+ criteria
+
+ |
+ + Award criteria + | +
+ The award criteria. + + |
+ + array of AwardCriterion objects + | +
+ AwardCriterion +
+ +
+ The extension defines a new AwardCriterion object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Type + | +
+ The aspect of the bid that the criterion concerns. + + |
+ + string from open awardCriterionType codelist + | +
+
+ name
+
+ |
+ + Name + | +
+ The name of the criterion. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ The description of the criterion. + + |
+ + string + | +
+
+ numbers
+
+ |
+ + Numbers + | +
+ Numbers linked to the criterion. + + |
+ + array of CriterionNumber objects + | +
+ CriterionNumber +
+ +
+ The extension defines a new CriterionNumber object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ number
+
+ |
+ + Number + | +
+ The number. + + |
+ + number + | +
+
+ weight
+
+ |
+ + Weight + | +
+ Whether the number is a type of weight. + + |
+ + string from closed criterionWeight codelist + | +
+
+ fixed
+
+ |
+ + Fixed + | +
+ Whether the number is a fixed value. + + |
+ + string from closed awardCriterionFixed codelist + | +
+
+ threshold
+
+ |
+ + Threshold + | +
+ Whether the number is a type of threshold. + + |
+ + string from closed criterionThreshold codelist + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/beneficialOwners/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/beneficialOwners/master/extension.json b/en/extensions/beneficialOwners/master/extension.json
new file mode 100644
index 000000000..ea20eb9c8
--- /dev/null
+++ b/en/extensions/beneficialOwners/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Beneficial owners",
+ "es": "Beneficiarios finales"
+ },
+ "description": {
+ "en": "Adds a beneficialOwners array to the organization object to indicate the beneficial owners of an organization.",
+ "es": "Agregue una lista de beneficialOwners al objeto organizaci\u00f3n para indicar los beneficiarios finales de una organizaci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/beneficialOwners/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "country.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/beneficialOwners/master/index.html b/en/extensions/beneficialOwners/master/index.html
new file mode 100644
index 000000000..ecc3f802e
--- /dev/null
+++ b/en/extensions/beneficialOwners/master/index.html
@@ -0,0 +1,378 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Beneficial owners +
+ ++ Adds a beneficialOwners array to the organization object to indicate the beneficial owners of an organization. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ country.csv +
+ +
+ You can download the country.csv file in English.
+
| + Code + | ++ Title + | +
|---|---|
+
+ AD
+
+ |
+ + Andorra + | +
+
+ AE
+
+ |
+ + United Arab Emirates + | +
+
+ AF
+
+ |
+ + Afghanistan + | +
+
+ AG
+
+ |
+ + Antigua and Barbuda + | +
+
+ AI
+
+ |
+ + Anguilla + | +
+
+ AL
+
+ |
+ + Albania + | +
+
+ AM
+
+ |
+ + Armenia + | +
+
+ AO
+
+ |
+ + Angola + | +
+
+ AQ
+
+ |
+ + Antarctica + | +
+
+ AR
+
+ |
+ + Argentina + | +
+
+ AS
+
+ |
+ + American Samoa + | +
+
+ AT
+
+ |
+ + Austria + | +
+
+ AU
+
+ |
+ + Australia + | +
+
+ AW
+
+ |
+ + Aruba + | +
+
+ AX
+
+ |
+ + Åland Islands + | +
+
+ AZ
+
+ |
+ + Azerbaijan + | +
+
+ BA
+
+ |
+ + Bosnia and Herzegovina + | +
+
+ BB
+
+ |
+ + Barbados + | +
+
+ BD
+
+ |
+ + Bangladesh + | +
+
+ BE
+
+ |
+ + Belgium + | +
+
+ BF
+
+ |
+ + Burkina Faso + | +
+
+ BG
+
+ |
+ + Bulgaria + | +
+
+ BH
+
+ |
+ + Bahrain + | +
+
+ BI
+
+ |
+ + Burundi + | +
+
+ BJ
+
+ |
+ + Benin + | +
+
+ BL
+
+ |
+ + Saint Barthélemy + | +
+
+ BM
+
+ |
+ + Bermuda + | +
+
+ BN
+
+ |
+ + Brunei Darussalam + | +
+
+ BO
+
+ |
+ + Bolivia (Plurinational State of) + | +
+
+ BQ
+
+ |
+ + Bonaire, Sint Eustatius and Saba + | +
+
+ BR
+
+ |
+ + Brazil + | +
+
+ BS
+
+ |
+ + Bahamas + | +
+
+ BT
+
+ |
+ + Bhutan + | +
+
+ BV
+
+ |
+ + Bouvet Island + | +
+
+ BW
+
+ |
+ + Botswana + | +
+
+ BY
+
+ |
+ + Belarus + | +
+
+ BZ
+
+ |
+ + Belize + | +
+
+ CA
+
+ |
+ + Canada + | +
+
+ CC
+
+ |
+ + Cocos (Keeling) Islands + | +
+
+ CD
+
+ |
+ + Congo (the Democratic Republic of the) + | +
+
+ CF
+
+ |
+ + Central African Republic + | +
+
+ CG
+
+ |
+ + Congo + | +
+
+ CH
+
+ |
+ + Switzerland + | +
+
+ CI
+
+ |
+ + Côte d'Ivoire + | +
+
+ CK
+
+ |
+ + Cook Islands + | +
+
+ CL
+
+ |
+ + Chile + | +
+
+ CM
+
+ |
+ + Cameroon + | +
+
+ CN
+
+ |
+ + China + | +
+
+ CO
+
+ |
+ + Colombia + | +
+
+ CR
+
+ |
+ + Costa Rica + | +
+
+ CU
+
+ |
+ + Cuba + | +
+
+ CV
+
+ |
+ + Cabo Verde + | +
+
+ CW
+
+ |
+ + Curaçao + | +
+
+ CX
+
+ |
+ + Christmas Island + | +
+
+ CY
+
+ |
+ + Cyprus + | +
+
+ CZ
+
+ |
+ + Czechia + | +
+
+ DE
+
+ |
+ + Germany + | +
+
+ DJ
+
+ |
+ + Djibouti + | +
+
+ DK
+
+ |
+ + Denmark + | +
+
+ DM
+
+ |
+ + Dominica + | +
+
+ DO
+
+ |
+ + Dominican Republic + | +
+
+ DZ
+
+ |
+ + Algeria + | +
+
+ EC
+
+ |
+ + Ecuador + | +
+
+ EE
+
+ |
+ + Estonia + | +
+
+ EG
+
+ |
+ + Egypt + | +
+
+ EH
+
+ |
+ + Western Sahara + | +
+
+ ER
+
+ |
+ + Eritrea + | +
+
+ ES
+
+ |
+ + Spain + | +
+
+ ET
+
+ |
+ + Ethiopia + | +
+
+ FI
+
+ |
+ + Finland + | +
+
+ FJ
+
+ |
+ + Fiji + | +
+
+ FK
+
+ |
+ + Falkland Islands [Malvinas] + | +
+
+ FM
+
+ |
+ + Micronesia (Federated States of) + | +
+
+ FO
+
+ |
+ + Faroe Islands + | +
+
+ FR
+
+ |
+ + France + | +
+
+ GA
+
+ |
+ + Gabon + | +
+
+ GB
+
+ |
+ + United Kingdom of Great Britain and Northern Ireland + | +
+
+ GD
+
+ |
+ + Grenada + | +
+
+ GE
+
+ |
+ + Georgia + | +
+
+ GF
+
+ |
+ + French Guiana + | +
+
+ GG
+
+ |
+ + Guernsey + | +
+
+ GH
+
+ |
+ + Ghana + | +
+
+ GI
+
+ |
+ + Gibraltar + | +
+
+ GL
+
+ |
+ + Greenland + | +
+
+ GM
+
+ |
+ + Gambia + | +
+
+ GN
+
+ |
+ + Guinea + | +
+
+ GP
+
+ |
+ + Guadeloupe + | +
+
+ GQ
+
+ |
+ + Equatorial Guinea + | +
+
+ GR
+
+ |
+ + Greece + | +
+
+ GS
+
+ |
+ + South Georgia and the South Sandwich Islands + | +
+
+ GT
+
+ |
+ + Guatemala + | +
+
+ GU
+
+ |
+ + Guam + | +
+
+ GW
+
+ |
+ + Guinea-Bissau + | +
+
+ GY
+
+ |
+ + Guyana + | +
+
+ HK
+
+ |
+ + Hong Kong + | +
+
+ HM
+
+ |
+ + Heard Island and McDonald Islands + | +
+
+ HN
+
+ |
+ + Honduras + | +
+
+ HR
+
+ |
+ + Croatia + | +
+
+ HT
+
+ |
+ + Haiti + | +
+
+ HU
+
+ |
+ + Hungary + | +
+
+ ID
+
+ |
+ + Indonesia + | +
+
+ IE
+
+ |
+ + Ireland + | +
+
+ IL
+
+ |
+ + Israel + | +
+
+ IM
+
+ |
+ + Isle of Man + | +
+
+ IN
+
+ |
+ + India + | +
+
+ IO
+
+ |
+ + British Indian Ocean Territory + | +
+
+ IQ
+
+ |
+ + Iraq + | +
+
+ IR
+
+ |
+ + Iran (Islamic Republic of) + | +
+
+ IS
+
+ |
+ + Iceland + | +
+
+ IT
+
+ |
+ + Italy + | +
+
+ JE
+
+ |
+ + Jersey + | +
+
+ JM
+
+ |
+ + Jamaica + | +
+
+ JO
+
+ |
+ + Jordan + | +
+
+ JP
+
+ |
+ + Japan + | +
+
+ KE
+
+ |
+ + Kenya + | +
+
+ KG
+
+ |
+ + Kyrgyzstan + | +
+
+ KH
+
+ |
+ + Cambodia + | +
+
+ KI
+
+ |
+ + Kiribati + | +
+
+ KM
+
+ |
+ + Comoros + | +
+
+ KN
+
+ |
+ + Saint Kitts and Nevis + | +
+
+ KP
+
+ |
+ + Korea (the Democratic People's Republic of) + | +
+
+ KR
+
+ |
+ + Korea (the Republic of) + | +
+
+ KW
+
+ |
+ + Kuwait + | +
+
+ KY
+
+ |
+ + Cayman Islands + | +
+
+ KZ
+
+ |
+ + Kazakhstan + | +
+
+ LA
+
+ |
+ + Lao People's Democratic Republic + | +
+
+ LB
+
+ |
+ + Lebanon + | +
+
+ LC
+
+ |
+ + Saint Lucia + | +
+
+ LI
+
+ |
+ + Liechtenstein + | +
+
+ LK
+
+ |
+ + Sri Lanka + | +
+
+ LR
+
+ |
+ + Liberia + | +
+
+ LS
+
+ |
+ + Lesotho + | +
+
+ LT
+
+ |
+ + Lithuania + | +
+
+ LU
+
+ |
+ + Luxembourg + | +
+
+ LV
+
+ |
+ + Latvia + | +
+
+ LY
+
+ |
+ + Libya + | +
+
+ MA
+
+ |
+ + Morocco + | +
+
+ MC
+
+ |
+ + Monaco + | +
+
+ MD
+
+ |
+ + Moldova (the Republic of) + | +
+
+ ME
+
+ |
+ + Montenegro + | +
+
+ MF
+
+ |
+ + Saint Martin (French part) + | +
+
+ MG
+
+ |
+ + Madagascar + | +
+
+ MH
+
+ |
+ + Marshall Islands + | +
+
+ MK
+
+ |
+ + North Macedonia + | +
+
+ ML
+
+ |
+ + Mali + | +
+
+ MM
+
+ |
+ + Myanmar + | +
+
+ MN
+
+ |
+ + Mongolia + | +
+
+ MO
+
+ |
+ + Macao + | +
+
+ MP
+
+ |
+ + Northern Mariana Islands + | +
+
+ MQ
+
+ |
+ + Martinique + | +
+
+ MR
+
+ |
+ + Mauritania + | +
+
+ MS
+
+ |
+ + Montserrat + | +
+
+ MT
+
+ |
+ + Malta + | +
+
+ MU
+
+ |
+ + Mauritius + | +
+
+ MV
+
+ |
+ + Maldives + | +
+
+ MW
+
+ |
+ + Malawi + | +
+
+ MX
+
+ |
+ + Mexico + | +
+
+ MY
+
+ |
+ + Malaysia + | +
+
+ MZ
+
+ |
+ + Mozambique + | +
+
+ NA
+
+ |
+ + Namibia + | +
+
+ NC
+
+ |
+ + New Caledonia + | +
+
+ NE
+
+ |
+ + Niger + | +
+
+ NF
+
+ |
+ + Norfolk Island + | +
+
+ NG
+
+ |
+ + Nigeria + | +
+
+ NI
+
+ |
+ + Nicaragua + | +
+
+ NL
+
+ |
+ + Netherlands + | +
+
+ NO
+
+ |
+ + Norway + | +
+
+ NP
+
+ |
+ + Nepal + | +
+
+ NR
+
+ |
+ + Nauru + | +
+
+ NU
+
+ |
+ + Niue + | +
+
+ NZ
+
+ |
+ + New Zealand + | +
+
+ OM
+
+ |
+ + Oman + | +
+
+ PA
+
+ |
+ + Panama + | +
+
+ PE
+
+ |
+ + Peru + | +
+
+ PF
+
+ |
+ + French Polynesia + | +
+
+ PG
+
+ |
+ + Papua New Guinea + | +
+
+ PH
+
+ |
+ + Philippines + | +
+
+ PK
+
+ |
+ + Pakistan + | +
+
+ PL
+
+ |
+ + Poland + | +
+
+ PM
+
+ |
+ + Saint Pierre and Miquelon + | +
+
+ PN
+
+ |
+ + Pitcairn + | +
+
+ PR
+
+ |
+ + Puerto Rico + | +
+
+ PS
+
+ |
+ + Palestine, State of + | +
+
+ PT
+
+ |
+ + Portugal + | +
+
+ PW
+
+ |
+ + Palau + | +
+
+ PY
+
+ |
+ + Paraguay + | +
+
+ QA
+
+ |
+ + Qatar + | +
+
+ RE
+
+ |
+ + Réunion + | +
+
+ RO
+
+ |
+ + Romania + | +
+
+ RS
+
+ |
+ + Serbia + | +
+
+ RU
+
+ |
+ + Russian Federation + | +
+
+ RW
+
+ |
+ + Rwanda + | +
+
+ SA
+
+ |
+ + Saudi Arabia + | +
+
+ SB
+
+ |
+ + Solomon Islands + | +
+
+ SC
+
+ |
+ + Seychelles + | +
+
+ SD
+
+ |
+ + Sudan + | +
+
+ SE
+
+ |
+ + Sweden + | +
+
+ SG
+
+ |
+ + Singapore + | +
+
+ SH
+
+ |
+ + Saint Helena, Ascension and Tristan da Cunha + | +
+
+ SI
+
+ |
+ + Slovenia + | +
+
+ SJ
+
+ |
+ + Svalbard and Jan Mayen + | +
+
+ SK
+
+ |
+ + Slovakia + | +
+
+ SL
+
+ |
+ + Sierra Leone + | +
+
+ SM
+
+ |
+ + San Marino + | +
+
+ SN
+
+ |
+ + Senegal + | +
+
+ SO
+
+ |
+ + Somalia + | +
+
+ SR
+
+ |
+ + Suriname + | +
+
+ SS
+
+ |
+ + South Sudan + | +
+
+ ST
+
+ |
+ + Sao Tome and Principe + | +
+
+ SV
+
+ |
+ + El Salvador + | +
+
+ SX
+
+ |
+ + Sint Maarten (Dutch part) + | +
+
+ SY
+
+ |
+ + Syrian Arab Republic + | +
+
+ SZ
+
+ |
+ + Eswatini + | +
+
+ TC
+
+ |
+ + Turks and Caicos Islands + | +
+
+ TD
+
+ |
+ + Chad + | +
+
+ TF
+
+ |
+ + French Southern Territories + | +
+
+ TG
+
+ |
+ + Togo + | +
+
+ TH
+
+ |
+ + Thailand + | +
+
+ TJ
+
+ |
+ + Tajikistan + | +
+
+ TK
+
+ |
+ + Tokelau + | +
+
+ TL
+
+ |
+ + Timor-Leste + | +
+
+ TM
+
+ |
+ + Turkmenistan + | +
+
+ TN
+
+ |
+ + Tunisia + | +
+
+ TO
+
+ |
+ + Tonga + | +
+
+ TR
+
+ |
+ + Turkey + | +
+
+ TT
+
+ |
+ + Trinidad and Tobago + | +
+
+ TV
+
+ |
+ + Tuvalu + | +
+
+ TW
+
+ |
+ + Taiwan (Province of China) + | +
+
+ TZ
+
+ |
+ + Tanzania, the United Republic of + | +
+
+ UA
+
+ |
+ + Ukraine + | +
+
+ UG
+
+ |
+ + Uganda + | +
+
+ UM
+
+ |
+ + United States Minor Outlying Islands + | +
+
+ US
+
+ |
+ + United States of America + | +
+
+ UY
+
+ |
+ + Uruguay + | +
+
+ UZ
+
+ |
+ + Uzbekistan + | +
+
+ VA
+
+ |
+ + Holy See + | +
+
+ VC
+
+ |
+ + Saint Vincent and the Grenadines + | +
+
+ VE
+
+ |
+ + Venezuela (Bolivarian Republic of) + | +
+
+ VG
+
+ |
+ + Virgin Islands (British) + | +
+
+ VI
+
+ |
+ + Virgin Islands (U.S.) + | +
+
+ VN
+
+ |
+ + Viet Nam + | +
+
+ VU
+
+ |
+ + Vanuatu + | +
+
+ WF
+
+ |
+ + Wallis and Futuna + | +
+
+ WS
+
+ |
+ + Samoa + | +
+
+ XK
+
+ |
+ + Kosovo + | +
+
+ YE
+
+ |
+ + Yemen + | +
+
+ YT
+
+ |
+ + Mayotte + | +
+
+ ZA
+
+ |
+ + South Africa + | +
+
+ ZM
+
+ |
+ + Zambia + | +
+
+ ZW
+
+ |
+ + Zimbabwe + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/beneficialOwners/master/release-schema.json b/en/extensions/beneficialOwners/master/release-schema.json
new file mode 100644
index 000000000..2777e54f4
--- /dev/null
+++ b/en/extensions/beneficialOwners/master/release-schema.json
@@ -0,0 +1,361 @@
+{
+ "definitions": {
+ "Organization": {
+ "properties": {
+ "beneficialOwners": {
+ "title": "Beneficial owners",
+ "description": "The beneficial owners of the organization.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Person"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "details": {
+ "properties": {
+ "listedOnRegulatedMarket": {
+ "title": "Listed on regulated market",
+ "description": "Whether the organization is listed on a regulated market (e.g. a stock exchange) that ensures adequate transparency in line with anti-money laundering legislation.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+ },
+ "Person": {
+ "title": "Person",
+ "description": "A natural person.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "A local identifier for the person.",
+ "type": "string",
+ "minLength": 1
+ },
+ "name": {
+ "title": "Name",
+ "description": "The full name of the person.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "identifier": {
+ "title": "Identifier",
+ "description": "An official identifier for the person. The scheme should follow the pattern {JURISDICTION}-{TYPE}, where JURISDICTION is a three-letter, uppercase ISO 3166-1 alpha-3 country code, and TYPE is one of \"PASSPORT\", \"TAXID\" or \"IDCARD\".",
+ "$ref": "#/definitions/Identifier"
+ },
+ "nationalities": {
+ "title": "Nationalities",
+ "description": "The nationalities of the person, from the closed country codelist.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "AD",
+ "AE",
+ "AF",
+ "AG",
+ "AI",
+ "AL",
+ "AM",
+ "AO",
+ "AQ",
+ "AR",
+ "AS",
+ "AT",
+ "AU",
+ "AW",
+ "AX",
+ "AZ",
+ "BA",
+ "BB",
+ "BD",
+ "BE",
+ "BF",
+ "BG",
+ "BH",
+ "BI",
+ "BJ",
+ "BL",
+ "BM",
+ "BN",
+ "BO",
+ "BQ",
+ "BR",
+ "BS",
+ "BT",
+ "BV",
+ "BW",
+ "BY",
+ "BZ",
+ "CA",
+ "CC",
+ "CD",
+ "CF",
+ "CG",
+ "CH",
+ "CI",
+ "CK",
+ "CL",
+ "CM",
+ "CN",
+ "CO",
+ "CR",
+ "CU",
+ "CV",
+ "CW",
+ "CX",
+ "CY",
+ "CZ",
+ "DE",
+ "DJ",
+ "DK",
+ "DM",
+ "DO",
+ "DZ",
+ "EC",
+ "EE",
+ "EG",
+ "EH",
+ "ER",
+ "ES",
+ "ET",
+ "FI",
+ "FJ",
+ "FK",
+ "FM",
+ "FO",
+ "FR",
+ "GA",
+ "GB",
+ "GD",
+ "GE",
+ "GF",
+ "GG",
+ "GH",
+ "GI",
+ "GL",
+ "GM",
+ "GN",
+ "GP",
+ "GQ",
+ "GR",
+ "GS",
+ "GT",
+ "GU",
+ "GW",
+ "GY",
+ "HK",
+ "HM",
+ "HN",
+ "HR",
+ "HT",
+ "HU",
+ "ID",
+ "IE",
+ "IL",
+ "IM",
+ "IN",
+ "IO",
+ "IQ",
+ "IR",
+ "IS",
+ "IT",
+ "JE",
+ "JM",
+ "JO",
+ "JP",
+ "KE",
+ "KG",
+ "KH",
+ "KI",
+ "KM",
+ "KN",
+ "KP",
+ "KR",
+ "KW",
+ "KY",
+ "KZ",
+ "LA",
+ "LB",
+ "LC",
+ "LI",
+ "LK",
+ "LR",
+ "LS",
+ "LT",
+ "LU",
+ "LV",
+ "LY",
+ "MA",
+ "MC",
+ "MD",
+ "ME",
+ "MF",
+ "MG",
+ "MH",
+ "MK",
+ "ML",
+ "MM",
+ "MN",
+ "MO",
+ "MP",
+ "MQ",
+ "MR",
+ "MS",
+ "MT",
+ "MU",
+ "MV",
+ "MW",
+ "MX",
+ "MY",
+ "MZ",
+ "NA",
+ "NC",
+ "NE",
+ "NF",
+ "NG",
+ "NI",
+ "NL",
+ "NO",
+ "NP",
+ "NR",
+ "NU",
+ "NZ",
+ "OM",
+ "PA",
+ "PE",
+ "PF",
+ "PG",
+ "PH",
+ "PK",
+ "PL",
+ "PM",
+ "PN",
+ "PR",
+ "PS",
+ "PT",
+ "PW",
+ "PY",
+ "QA",
+ "RE",
+ "RO",
+ "RS",
+ "RU",
+ "RW",
+ "SA",
+ "SB",
+ "SC",
+ "SD",
+ "SE",
+ "SG",
+ "SH",
+ "SI",
+ "SJ",
+ "SK",
+ "SL",
+ "SM",
+ "SN",
+ "SO",
+ "SR",
+ "SS",
+ "ST",
+ "SV",
+ "SX",
+ "SY",
+ "SZ",
+ "TC",
+ "TD",
+ "TF",
+ "TG",
+ "TH",
+ "TJ",
+ "TK",
+ "TL",
+ "TM",
+ "TN",
+ "TO",
+ "TR",
+ "TT",
+ "TV",
+ "TW",
+ "TZ",
+ "UA",
+ "UG",
+ "UM",
+ "US",
+ "UY",
+ "UZ",
+ "VA",
+ "VC",
+ "VE",
+ "VG",
+ "VI",
+ "VN",
+ "VU",
+ "WF",
+ "WS",
+ "XK",
+ "YE",
+ "YT",
+ "ZA",
+ "ZM",
+ "ZW"
+ ]
+ },
+ "codelist": "country.csv",
+ "openCodelist": false,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "address": {
+ "title": "Address",
+ "description": "The address of the person.",
+ "$ref": "#/definitions/Address"
+ },
+ "email": {
+ "title": "Email",
+ "description": "The e-mail address of the person.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "email",
+ "minLength": 1
+ },
+ "faxNumber": {
+ "title": "Fax number",
+ "description": "The fax number of the person. This must include the international dialing code.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "telephone": {
+ "title": "Telephone",
+ "description": "The telephone number of the person. This must include the international dialing code.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/beneficialOwners/master/schema/index.html b/en/extensions/beneficialOwners/master/schema/index.html
new file mode 100644
index 000000000..514dc2044
--- /dev/null
+++ b/en/extensions/beneficialOwners/master/schema/index.html
@@ -0,0 +1,442 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Beneficial owners +
+ ++ Adds a beneficialOwners array to the organization object to indicate the beneficial owners of an organization. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a beneficial owners array to the organization object to indicate the beneficial owners of an organization.
+If beneficial ownership (BO) information is collected via contracting processes, then this extension is appropriate: for example, if tenderers are obligated to disclose their beneficial owners within their bid submission. Similarly, to use this extension, the laws in your jurisdiction must permit the publication of personal identifiers.
+You can find the complete guidance on publishing personal identifiers in the Beneficial Ownership Data Standard documentation
+On the other hand, if BO information is collected in a central register via other means, then it is recommended to publish that information as a separate dataset. The BO dataset and the OCDS dataset should identify organizations in the same way, so that users can cross-reference the datasets. The BO dataset can follow the Beneficial Ownership Data Standard.
+Example
+With nationality
+The beneficial owner's nationality is disclosed.
+{
+ "parties": [
+ {
+ "id": "AHL",
+ "name": "Alpha Holdings Ltd",
+ "beneficialOwners": [
+ {
+ "id": "1",
+ "name": "Juan Perez",
+ "identifier": {
+ "scheme": "PRY-IDCARD",
+ "id": "12345"
+ },
+ "nationalities": [
+ "PY"
+ ],
+ "address": {
+ "streetAddress": "Avenida Eusebio Ayala 1347",
+ "locality": "Asunción",
+ "region": "Gran Asunción",
+ "postalCode": "1001",
+ "countryName": "Paraguay"
+ },
+ "email": "jperez@example.com",
+ "faxNumber": "+595210000001",
+ "telephone": "+595210000000"
+ }
+ ]
+ }
+ ]
+}
+Without nationality
+The beneficial owner's nationality is not disclosed because the organization is listed on a regulated market (e.g. a stock exchange) that ensures adequate transparency in line with anti-money laundering legislation.
+{
+ "parties": [
+ {
+ "id": "AHL",
+ "name": "Alpha Holdings Ltd",
+ "beneficialOwners": [
+ {
+ "id": "1",
+ "name": "Juan Perez",
+ "identifier": {
+ "scheme": "PRY-IDCARD",
+ "id": "12345"
+ },
+ "address": {
+ "streetAddress": "Avenida Eusebio Ayala 1347",
+ "locality": "Asunción",
+ "region": "Gran Asunción",
+ "postalCode": "1001",
+ "countryName": "Paraguay"
+ },
+ "email": "jperez@example.com",
+ "faxNumber": "+595210000001",
+ "telephone": "+595210000000"
+ }
+ ],
+ "details": {
+ "listedOnRegulatedMarket": true
+ }
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-08-04
+-
+
- Convert nationality field to
nationalitiesarray.
+
2023-06-07
+-
+
- Add
country.csvcodelist for nationality field.
+
2023-02-27
+-
+
- Add fields:
+
-
+
Person.address
+Person.email
+Person.faxNumber
+Person.telephone
+Organization.details.listedOnRegulatedMarket
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/bidOpening/index.html b/en/extensions/bidOpening/index.html
new file mode 100644
index 000000000..cb14198fc
--- /dev/null
+++ b/en/extensions/bidOpening/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Beneficial owners +
+ ++ Adds a beneficialOwners array to the organization object to indicate the beneficial owners of an organization. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ beneficialOwners
+
+ |
+ + Beneficial owners + | +
+ The beneficial owners of the organization. + + |
+ + array of Person objects + | +
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + Listed on regulated market + | +
+ Whether the organization is listed on a regulated market (e.g. a stock exchange) that ensures adequate transparency in line with anti-money laundering legislation. + + |
+ + boolean + | +
+ Person +
+ +
+ The extension defines a new Person object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ A local identifier for the person. + + |
+ + string + | +
+
+ name
+
+ |
+ + Name + | +
+ The full name of the person. + + |
+ + string + | +
+
+ identifier
+
+ |
+ + Identifier + | +
+ An official identifier for the person. The scheme should follow the pattern {JURISDICTION}-{TYPE}, where JURISDICTION is a three-letter, uppercase ISO 3166-1 alpha-3 country code, and TYPE is one of "PASSPORT", "TAXID" or "IDCARD". + + |
+ + Identifier object + | +
+
+ nationalities
+
+ |
+ + Nationalities + | +
+ The nationalities of the person, from the closed country codelist. + + |
+ + array of strings from closed country codelist + | +
+
+ address
+
+ |
+ + Address + | +
+ The address of the person. + + |
+ + Address object + | +
+
+ email
+
+ |
+ + Email + | +
+ The e-mail address of the person. + + |
+ + string + | +
+
+ faxNumber
+
+ |
+ + Fax number + | +
+ The fax number of the person. This must include the international dialing code. + + |
+ + string + | +
+
+ telephone
+
+ |
+ + Telephone + | +
+ The telephone number of the person. This must include the international dialing code. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/bidOpening/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/bidOpening/master/release-schema.json b/en/extensions/bidOpening/master/release-schema.json
new file mode 100644
index 000000000..6dd6724ff
--- /dev/null
+++ b/en/extensions/bidOpening/master/release-schema.json
@@ -0,0 +1,58 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "bidOpening": {
+ "title": "Bid opening",
+ "description": "The date, time, place and other details of the public bid opening.",
+ "$ref": "#/definitions/BidOpening"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "bidOpening": {
+ "title": "Bid opening",
+ "description": "The date, time, place and other details of the public bid opening.",
+ "$ref": "#/definitions/BidOpening"
+ }
+ }
+ },
+ "BidOpening": {
+ "title": "Bid opening",
+ "description": "The date, time, place and other details of the public bid opening.",
+ "type": "object",
+ "properties": {
+ "date": {
+ "title": "Date and time",
+ "description": "The date and time of the bid opening.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "location": {
+ "title": "Location",
+ "description": "The place where the bid opening occurs.",
+ "$ref": "#/definitions/Location"
+ },
+ "address": {
+ "title": "Address",
+ "description": "The address of the place where the bid opening occurs.",
+ "$ref": "#/definitions/Address"
+ },
+ "description": {
+ "title": "Details",
+ "description": "Any other details about the bid opening (who can participate, whether authorization is needed, etc.).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/bidOpening/master/schema/index.html b/en/extensions/bidOpening/master/schema/index.html
new file mode 100644
index 000000000..81e96e4b8
--- /dev/null
+++ b/en/extensions/bidOpening/master/schema/index.html
@@ -0,0 +1,384 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Bid opening +
+ ++ Adds an object to describe the date, time, place and other details of the bid opening. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an object to describe the date, time, place and other details of the public bid opening.
+This extension must be used with the Location extension.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Legal context
+In the European Union, this extension's fields correspond to eForms BT-132 (Public Opening Date), BT-133 (Public Opening Place), BT-134 (Public Opening Description). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+Tender
+{
+ "tender": {
+ "bidOpening": {
+ "date": "2019-10-16T15:00:00+01:00",
+ "address": {
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford",
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom"
+ },
+ "location": {
+ "description": "Central Oxford",
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 51.751944,
+ -1.257778
+ ]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2640729"
+ ]
+ },
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "description": "We recommend that people who wish to attend the opening register on this page: https://wwww.example.org/register"
+ }
+ }
+}
+Lots
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "bidOpening": {
+ "date": "2019-10-16T15:00:00+01:00",
+ "address": {
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford",
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom"
+ },
+ "location": {
+ "description": "Central Oxford",
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 51.751944,
+ -1.257778
+ ]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2640729"
+ ]
+ },
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "description": "We recommend that people who wish to attend the opening register on this page: https://wwww.example.org/register"
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-06-07
+-
+
- Clarify that the extension is for bid openings that are public events. +
2023-02-13
+-
+
- Add
Lot.bidOpeningfield.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile, in pull requests and in https://github.com/open-contracting/standard/issues/749.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/bids/index.html b/en/extensions/bids/index.html
new file mode 100644
index 000000000..54a0cdd9a
--- /dev/null
+++ b/en/extensions/bids/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Bid opening +
+ ++ Adds an object to describe the date, time, place and other details of the bid opening. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ bidOpening
+
+ |
+ + Bid opening + | +
+ The date, time, place and other details of the public bid opening. + + |
+ + BidOpening object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ bidOpening
+
+ |
+ + Bid opening + | +
+ The date, time, place and other details of the public bid opening. + + |
+ + BidOpening object + | +
+ BidOpening +
+ +
+ The extension defines a new BidOpening object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ date
+
+ |
+ + Date and time + | +
+ The date and time of the bid opening. + + |
+ + string + | +
+
+ location
+
+ |
+ + Location + | +
+ The place where the bid opening occurs. + + |
+ + Location object + | +
+
+ address
+
+ |
+ + Address + | +
+ The address of the place where the bid opening occurs. + + |
+ + Address object + | +
+
+ description
+
+ |
+ + Details + | +
+ Any other details about the bid opening (who can participate, whether authorization is needed, etc.). + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/bids/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/bids/master/codelists/statistic.csv b/en/extensions/bids/master/codelists/statistic.csv
new file mode 100644
index 000000000..1766d1468
--- /dev/null
+++ b/en/extensions/bids/master/codelists/statistic.csv
@@ -0,0 +1,19 @@
+Category,Code,Title,Description
+bids,requests,Requests to participate,The total number of unique requests to participate received
+bids,bids,Bids,The total number of unique bids received (prior to any being discounted for not meeting essential criteria).
+bids,validBids,Valid bids,"The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids are considered during the tender evaluation stage."
+EU,disqualifiedBids,Disqualified bids,"The number of bids that were found inadmissible. A bid is found inadmissible where it has been verified that it has been submitted by a tenderer who has been excluded or who did not meet the selection criteria, or when it is not in conformity with the technical specifications, or is irregular (e.g. it was received late, having an abnormally low price or cost), unacceptable or unsuitable."
+bids,lowestValidBidValue,Lowest valid bid value,The value of the lowest valid bid.
+bids,highestValidBidValue,Highest valid bid value,The value of the highest valid bid.
+bidders,bidders,Bidders,The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria).
+bidders,qualifiedBidders,Qualified bidders,The total number of unique organizations or consortia passing the qualification stage of the evaluation process.
+bidders,disqualifiedBidders,Disqualified bidders,The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process.
+EU,electronicBids,Electronic bids,The number of bids received by electronic means.
+EU,microBids,Bids from micro companies,The number of bids received from micro enterprises.
+EU,smeBids,Bids from SMEs,The number of bids received from small and medium enterprises.
+EU,smallBids,Bids from small companies,The number of bids received from small enterprises.
+EU,mediumBids,Bids from medium companies,The number of bids received from medium enterprises.
+EU,foreignBids,Bids from foreign firms,The number of bids received from bidders from outside the country where the tender is issued.
+EU,foreignBidsFromEU,Bids from firms in other European Economic Area countries,The number of bids received from tenderers from other European Economic Area countries.
+EU,foreignBidsFromNonEU,Bids from firms in non-European Economic Area countries,The number of bids received from tenderers from non-European Economic Area countries.
+EU,tendersAbnormallyLow,Tenders excluded because they were abnormally low,"The number of tenders excluded because they were abnormally low. Note that in some EU datasets this might have been converted from a boolean, such that a value of 1 would indicate ""1 or more"" tenders were excluded. Users need to evaluate and interpret data accordingly."
diff --git a/en/extensions/bids/master/extension.json b/en/extensions/bids/master/extension.json
new file mode 100644
index 000000000..35155b927
--- /dev/null
+++ b/en/extensions/bids/master/extension.json
@@ -0,0 +1,28 @@
+{
+ "name": {
+ "en": "Bid statistics and details",
+ "es": "Estad\u00edsticas y detalles de las ofertas"
+ },
+ "description": {
+ "en": "Allowing bid statistics, and detailed bid information to be represented.",
+ "es": "Permite que se muestren las estad\u00edsticas de ofertas y la informaci\u00f3n detallada de las ofertas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/bids/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "statistic.csv",
+ "bidStatus.csv",
+ "country.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/bids/master/index.html b/en/extensions/bids/master/index.html
new file mode 100644
index 000000000..1dc2a98d4
--- /dev/null
+++ b/en/extensions/bids/master/index.html
@@ -0,0 +1,493 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Bid statistics and details +
+ ++ Allowing bid statistics, and detailed bid information to be represented. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ bidStatus.csv +
+ +
+ You can download the bidStatus.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ invited
+
+ |
+ + Invited + | +
+ A bid has been invited from the listed tenderer(s). + + |
+
+
+ pending
+
+ |
+ + Pending + | +
+ A bid has been submitted but not yet evaluated. + + |
+
+
+ valid
+
+ |
+ + Valid + | +
+ The submitted bid met the qualification requirements in order to be evaluated. + + |
+
+
+ disqualified
+
+ |
+ + Disqualified + | +
+ The submitted bid did not meet the qualification requirements in order to be evaluated. + + |
+
+
+ withdrawn
+
+ |
+ + Withdrawn + | +
+ The submitted bid was withdrawn by the tenderer(s). + + |
+
+ country.csv +
+ +
+ You can download the country.csv file in English.
+
| + Code + | ++ Title + | +
|---|---|
+
+ AD
+
+ |
+ + Andorra + | +
+
+ AE
+
+ |
+ + United Arab Emirates + | +
+
+ AF
+
+ |
+ + Afghanistan + | +
+
+ AG
+
+ |
+ + Antigua and Barbuda + | +
+
+ AI
+
+ |
+ + Anguilla + | +
+
+ AL
+
+ |
+ + Albania + | +
+
+ AM
+
+ |
+ + Armenia + | +
+
+ AO
+
+ |
+ + Angola + | +
+
+ AQ
+
+ |
+ + Antarctica + | +
+
+ AR
+
+ |
+ + Argentina + | +
+
+ AS
+
+ |
+ + American Samoa + | +
+
+ AT
+
+ |
+ + Austria + | +
+
+ AU
+
+ |
+ + Australia + | +
+
+ AW
+
+ |
+ + Aruba + | +
+
+ AX
+
+ |
+ + Åland Islands + | +
+
+ AZ
+
+ |
+ + Azerbaijan + | +
+
+ BA
+
+ |
+ + Bosnia and Herzegovina + | +
+
+ BB
+
+ |
+ + Barbados + | +
+
+ BD
+
+ |
+ + Bangladesh + | +
+
+ BE
+
+ |
+ + Belgium + | +
+
+ BF
+
+ |
+ + Burkina Faso + | +
+
+ BG
+
+ |
+ + Bulgaria + | +
+
+ BH
+
+ |
+ + Bahrain + | +
+
+ BI
+
+ |
+ + Burundi + | +
+
+ BJ
+
+ |
+ + Benin + | +
+
+ BL
+
+ |
+ + Saint Barthélemy + | +
+
+ BM
+
+ |
+ + Bermuda + | +
+
+ BN
+
+ |
+ + Brunei Darussalam + | +
+
+ BO
+
+ |
+ + Bolivia (Plurinational State of) + | +
+
+ BQ
+
+ |
+ + Bonaire, Sint Eustatius and Saba + | +
+
+ BR
+
+ |
+ + Brazil + | +
+
+ BS
+
+ |
+ + Bahamas + | +
+
+ BT
+
+ |
+ + Bhutan + | +
+
+ BV
+
+ |
+ + Bouvet Island + | +
+
+ BW
+
+ |
+ + Botswana + | +
+
+ BY
+
+ |
+ + Belarus + | +
+
+ BZ
+
+ |
+ + Belize + | +
+
+ CA
+
+ |
+ + Canada + | +
+
+ CC
+
+ |
+ + Cocos (Keeling) Islands + | +
+
+ CD
+
+ |
+ + Congo (the Democratic Republic of the) + | +
+
+ CF
+
+ |
+ + Central African Republic + | +
+
+ CG
+
+ |
+ + Congo + | +
+
+ CH
+
+ |
+ + Switzerland + | +
+
+ CI
+
+ |
+ + Côte d'Ivoire + | +
+
+ CK
+
+ |
+ + Cook Islands + | +
+
+ CL
+
+ |
+ + Chile + | +
+
+ CM
+
+ |
+ + Cameroon + | +
+
+ CN
+
+ |
+ + China + | +
+
+ CO
+
+ |
+ + Colombia + | +
+
+ CR
+
+ |
+ + Costa Rica + | +
+
+ CU
+
+ |
+ + Cuba + | +
+
+ CV
+
+ |
+ + Cabo Verde + | +
+
+ CW
+
+ |
+ + Curaçao + | +
+
+ CX
+
+ |
+ + Christmas Island + | +
+
+ CY
+
+ |
+ + Cyprus + | +
+
+ CZ
+
+ |
+ + Czechia + | +
+
+ DE
+
+ |
+ + Germany + | +
+
+ DJ
+
+ |
+ + Djibouti + | +
+
+ DK
+
+ |
+ + Denmark + | +
+
+ DM
+
+ |
+ + Dominica + | +
+
+ DO
+
+ |
+ + Dominican Republic + | +
+
+ DZ
+
+ |
+ + Algeria + | +
+
+ EC
+
+ |
+ + Ecuador + | +
+
+ EE
+
+ |
+ + Estonia + | +
+
+ EG
+
+ |
+ + Egypt + | +
+
+ EH
+
+ |
+ + Western Sahara + | +
+
+ ER
+
+ |
+ + Eritrea + | +
+
+ ES
+
+ |
+ + Spain + | +
+
+ ET
+
+ |
+ + Ethiopia + | +
+
+ FI
+
+ |
+ + Finland + | +
+
+ FJ
+
+ |
+ + Fiji + | +
+
+ FK
+
+ |
+ + Falkland Islands [Malvinas] + | +
+
+ FM
+
+ |
+ + Micronesia (Federated States of) + | +
+
+ FO
+
+ |
+ + Faroe Islands + | +
+
+ FR
+
+ |
+ + France + | +
+
+ GA
+
+ |
+ + Gabon + | +
+
+ GB
+
+ |
+ + United Kingdom of Great Britain and Northern Ireland + | +
+
+ GD
+
+ |
+ + Grenada + | +
+
+ GE
+
+ |
+ + Georgia + | +
+
+ GF
+
+ |
+ + French Guiana + | +
+
+ GG
+
+ |
+ + Guernsey + | +
+
+ GH
+
+ |
+ + Ghana + | +
+
+ GI
+
+ |
+ + Gibraltar + | +
+
+ GL
+
+ |
+ + Greenland + | +
+
+ GM
+
+ |
+ + Gambia + | +
+
+ GN
+
+ |
+ + Guinea + | +
+
+ GP
+
+ |
+ + Guadeloupe + | +
+
+ GQ
+
+ |
+ + Equatorial Guinea + | +
+
+ GR
+
+ |
+ + Greece + | +
+
+ GS
+
+ |
+ + South Georgia and the South Sandwich Islands + | +
+
+ GT
+
+ |
+ + Guatemala + | +
+
+ GU
+
+ |
+ + Guam + | +
+
+ GW
+
+ |
+ + Guinea-Bissau + | +
+
+ GY
+
+ |
+ + Guyana + | +
+
+ HK
+
+ |
+ + Hong Kong + | +
+
+ HM
+
+ |
+ + Heard Island and McDonald Islands + | +
+
+ HN
+
+ |
+ + Honduras + | +
+
+ HR
+
+ |
+ + Croatia + | +
+
+ HT
+
+ |
+ + Haiti + | +
+
+ HU
+
+ |
+ + Hungary + | +
+
+ ID
+
+ |
+ + Indonesia + | +
+
+ IE
+
+ |
+ + Ireland + | +
+
+ IL
+
+ |
+ + Israel + | +
+
+ IM
+
+ |
+ + Isle of Man + | +
+
+ IN
+
+ |
+ + India + | +
+
+ IO
+
+ |
+ + British Indian Ocean Territory + | +
+
+ IQ
+
+ |
+ + Iraq + | +
+
+ IR
+
+ |
+ + Iran (Islamic Republic of) + | +
+
+ IS
+
+ |
+ + Iceland + | +
+
+ IT
+
+ |
+ + Italy + | +
+
+ JE
+
+ |
+ + Jersey + | +
+
+ JM
+
+ |
+ + Jamaica + | +
+
+ JO
+
+ |
+ + Jordan + | +
+
+ JP
+
+ |
+ + Japan + | +
+
+ KE
+
+ |
+ + Kenya + | +
+
+ KG
+
+ |
+ + Kyrgyzstan + | +
+
+ KH
+
+ |
+ + Cambodia + | +
+
+ KI
+
+ |
+ + Kiribati + | +
+
+ KM
+
+ |
+ + Comoros + | +
+
+ KN
+
+ |
+ + Saint Kitts and Nevis + | +
+
+ KP
+
+ |
+ + Korea (the Democratic People's Republic of) + | +
+
+ KR
+
+ |
+ + Korea (the Republic of) + | +
+
+ KW
+
+ |
+ + Kuwait + | +
+
+ KY
+
+ |
+ + Cayman Islands + | +
+
+ KZ
+
+ |
+ + Kazakhstan + | +
+
+ LA
+
+ |
+ + Lao People's Democratic Republic + | +
+
+ LB
+
+ |
+ + Lebanon + | +
+
+ LC
+
+ |
+ + Saint Lucia + | +
+
+ LI
+
+ |
+ + Liechtenstein + | +
+
+ LK
+
+ |
+ + Sri Lanka + | +
+
+ LR
+
+ |
+ + Liberia + | +
+
+ LS
+
+ |
+ + Lesotho + | +
+
+ LT
+
+ |
+ + Lithuania + | +
+
+ LU
+
+ |
+ + Luxembourg + | +
+
+ LV
+
+ |
+ + Latvia + | +
+
+ LY
+
+ |
+ + Libya + | +
+
+ MA
+
+ |
+ + Morocco + | +
+
+ MC
+
+ |
+ + Monaco + | +
+
+ MD
+
+ |
+ + Moldova (the Republic of) + | +
+
+ ME
+
+ |
+ + Montenegro + | +
+
+ MF
+
+ |
+ + Saint Martin (French part) + | +
+
+ MG
+
+ |
+ + Madagascar + | +
+
+ MH
+
+ |
+ + Marshall Islands + | +
+
+ MK
+
+ |
+ + North Macedonia + | +
+
+ ML
+
+ |
+ + Mali + | +
+
+ MM
+
+ |
+ + Myanmar + | +
+
+ MN
+
+ |
+ + Mongolia + | +
+
+ MO
+
+ |
+ + Macao + | +
+
+ MP
+
+ |
+ + Northern Mariana Islands + | +
+
+ MQ
+
+ |
+ + Martinique + | +
+
+ MR
+
+ |
+ + Mauritania + | +
+
+ MS
+
+ |
+ + Montserrat + | +
+
+ MT
+
+ |
+ + Malta + | +
+
+ MU
+
+ |
+ + Mauritius + | +
+
+ MV
+
+ |
+ + Maldives + | +
+
+ MW
+
+ |
+ + Malawi + | +
+
+ MX
+
+ |
+ + Mexico + | +
+
+ MY
+
+ |
+ + Malaysia + | +
+
+ MZ
+
+ |
+ + Mozambique + | +
+
+ NA
+
+ |
+ + Namibia + | +
+
+ NC
+
+ |
+ + New Caledonia + | +
+
+ NE
+
+ |
+ + Niger + | +
+
+ NF
+
+ |
+ + Norfolk Island + | +
+
+ NG
+
+ |
+ + Nigeria + | +
+
+ NI
+
+ |
+ + Nicaragua + | +
+
+ NL
+
+ |
+ + Netherlands + | +
+
+ NO
+
+ |
+ + Norway + | +
+
+ NP
+
+ |
+ + Nepal + | +
+
+ NR
+
+ |
+ + Nauru + | +
+
+ NU
+
+ |
+ + Niue + | +
+
+ NZ
+
+ |
+ + New Zealand + | +
+
+ OM
+
+ |
+ + Oman + | +
+
+ PA
+
+ |
+ + Panama + | +
+
+ PE
+
+ |
+ + Peru + | +
+
+ PF
+
+ |
+ + French Polynesia + | +
+
+ PG
+
+ |
+ + Papua New Guinea + | +
+
+ PH
+
+ |
+ + Philippines + | +
+
+ PK
+
+ |
+ + Pakistan + | +
+
+ PL
+
+ |
+ + Poland + | +
+
+ PM
+
+ |
+ + Saint Pierre and Miquelon + | +
+
+ PN
+
+ |
+ + Pitcairn + | +
+
+ PR
+
+ |
+ + Puerto Rico + | +
+
+ PS
+
+ |
+ + Palestine, State of + | +
+
+ PT
+
+ |
+ + Portugal + | +
+
+ PW
+
+ |
+ + Palau + | +
+
+ PY
+
+ |
+ + Paraguay + | +
+
+ QA
+
+ |
+ + Qatar + | +
+
+ RE
+
+ |
+ + Réunion + | +
+
+ RO
+
+ |
+ + Romania + | +
+
+ RS
+
+ |
+ + Serbia + | +
+
+ RU
+
+ |
+ + Russian Federation + | +
+
+ RW
+
+ |
+ + Rwanda + | +
+
+ SA
+
+ |
+ + Saudi Arabia + | +
+
+ SB
+
+ |
+ + Solomon Islands + | +
+
+ SC
+
+ |
+ + Seychelles + | +
+
+ SD
+
+ |
+ + Sudan + | +
+
+ SE
+
+ |
+ + Sweden + | +
+
+ SG
+
+ |
+ + Singapore + | +
+
+ SH
+
+ |
+ + Saint Helena, Ascension and Tristan da Cunha + | +
+
+ SI
+
+ |
+ + Slovenia + | +
+
+ SJ
+
+ |
+ + Svalbard and Jan Mayen + | +
+
+ SK
+
+ |
+ + Slovakia + | +
+
+ SL
+
+ |
+ + Sierra Leone + | +
+
+ SM
+
+ |
+ + San Marino + | +
+
+ SN
+
+ |
+ + Senegal + | +
+
+ SO
+
+ |
+ + Somalia + | +
+
+ SR
+
+ |
+ + Suriname + | +
+
+ SS
+
+ |
+ + South Sudan + | +
+
+ ST
+
+ |
+ + Sao Tome and Principe + | +
+
+ SV
+
+ |
+ + El Salvador + | +
+
+ SX
+
+ |
+ + Sint Maarten (Dutch part) + | +
+
+ SY
+
+ |
+ + Syrian Arab Republic + | +
+
+ SZ
+
+ |
+ + Eswatini + | +
+
+ TC
+
+ |
+ + Turks and Caicos Islands + | +
+
+ TD
+
+ |
+ + Chad + | +
+
+ TF
+
+ |
+ + French Southern Territories + | +
+
+ TG
+
+ |
+ + Togo + | +
+
+ TH
+
+ |
+ + Thailand + | +
+
+ TJ
+
+ |
+ + Tajikistan + | +
+
+ TK
+
+ |
+ + Tokelau + | +
+
+ TL
+
+ |
+ + Timor-Leste + | +
+
+ TM
+
+ |
+ + Turkmenistan + | +
+
+ TN
+
+ |
+ + Tunisia + | +
+
+ TO
+
+ |
+ + Tonga + | +
+
+ TR
+
+ |
+ + Turkey + | +
+
+ TT
+
+ |
+ + Trinidad and Tobago + | +
+
+ TV
+
+ |
+ + Tuvalu + | +
+
+ TW
+
+ |
+ + Taiwan (Province of China) + | +
+
+ TZ
+
+ |
+ + Tanzania, the United Republic of + | +
+
+ UA
+
+ |
+ + Ukraine + | +
+
+ UG
+
+ |
+ + Uganda + | +
+
+ UM
+
+ |
+ + United States Minor Outlying Islands + | +
+
+ US
+
+ |
+ + United States of America + | +
+
+ UY
+
+ |
+ + Uruguay + | +
+
+ UZ
+
+ |
+ + Uzbekistan + | +
+
+ VA
+
+ |
+ + Holy See + | +
+
+ VC
+
+ |
+ + Saint Vincent and the Grenadines + | +
+
+ VE
+
+ |
+ + Venezuela (Bolivarian Republic of) + | +
+
+ VG
+
+ |
+ + Virgin Islands (British) + | +
+
+ VI
+
+ |
+ + Virgin Islands (U.S.) + | +
+
+ VN
+
+ |
+ + Viet Nam + | +
+
+ VU
+
+ |
+ + Vanuatu + | +
+
+ WF
+
+ |
+ + Wallis and Futuna + | +
+
+ WS
+
+ |
+ + Samoa + | +
+
+ XK
+
+ |
+ + Kosovo + | +
+
+ YE
+
+ |
+ + Yemen + | +
+
+ YT
+
+ |
+ + Mayotte + | +
+
+ ZA
+
+ |
+ + South Africa + | +
+
+ ZM
+
+ |
+ + Zambia + | +
+
+ ZW
+
+ |
+ + Zimbabwe + | +
+ statistic.csv +
+ +
+ You can download the statistic.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ requests
+
+ |
+ + Requests to participate + | +
+ The total number of unique requests to participate received + +
|
+
+
+ bids
+
+ |
+ + Bids + | +
+ The total number of unique bids received (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ validBids
+
+ |
+ + Valid bids + | +
+ The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids are considered during the tender evaluation stage. + +
|
+
+
+ disqualifiedBids
+
+ |
+ + Disqualified bids + | +
+ The number of bids that were found inadmissible. A bid is found inadmissible where it has been verified that it has been submitted by a tenderer who has been excluded or who did not meet the selection criteria, or when it is not in conformity with the technical specifications, or is irregular (e.g. it was received late, having an abnormally low price or cost), unacceptable or unsuitable. + +
|
+
+
+ lowestValidBidValue
+
+ |
+ + Lowest valid bid value + | +
+ The value of the lowest valid bid. + +
|
+
+
+ highestValidBidValue
+
+ |
+ + Highest valid bid value + | +
+ The value of the highest valid bid. + +
|
+
+
+ bidders
+
+ |
+ + Bidders + | +
+ The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ qualifiedBidders
+
+ |
+ + Qualified bidders + | +
+ The total number of unique organizations or consortia passing the qualification stage of the evaluation process. + +
|
+
+
+ disqualifiedBidders
+
+ |
+ + Disqualified bidders + | +
+ The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process. + +
|
+
+
+ electronicBids
+
+ |
+ + Electronic bids + | +
+ The number of bids received by electronic means. + +
|
+
+
+ microBids
+
+ |
+ + Bids from micro companies + | +
+ The number of bids received from micro enterprises. + +
|
+
+
+ smeBids
+
+ |
+ + Bids from SMEs + | +
+ The number of bids received from small and medium enterprises. + +
|
+
+
+ smallBids
+
+ |
+ + Bids from small companies + | +
+ The number of bids received from small enterprises. + +
|
+
+
+ mediumBids
+
+ |
+ + Bids from medium companies + | +
+ The number of bids received from medium enterprises. + +
|
+
+
+ foreignBids
+
+ |
+ + Bids from foreign firms + | +
+ The number of bids received from bidders from outside the country where the tender is issued. + +
|
+
+
+ foreignBidsFromEU
+
+ |
+ + Bids from firms in other European Economic Area countries + | +
+ The number of bids received from tenderers from other European Economic Area countries. + +
|
+
+
+ foreignBidsFromNonEU
+
+ |
+ + Bids from firms in non-European Economic Area countries + | +
+ The number of bids received from tenderers from non-European Economic Area countries. + +
|
+
+
+ tendersAbnormallyLow
+
+ |
+ + Tenders excluded because they were abnormally low + | +
+ The number of tenders excluded because they were abnormally low. Note that in some EU datasets this might have been converted from a boolean, such that a value of 1 would indicate "1 or more" tenders were excluded. Users need to evaluate and interpret data accordingly. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/bids/master/release-schema.json b/en/extensions/bids/master/release-schema.json
new file mode 100644
index 000000000..252b15e48
--- /dev/null
+++ b/en/extensions/bids/master/release-schema.json
@@ -0,0 +1,894 @@
+{
+ "properties": {
+ "bids": {
+ "title": "Bids",
+ "description": "The bid section is used to publish summary statistics, and where applicable, individual bid information.",
+ "$ref": "#/definitions/Bids"
+ }
+ },
+ "definitions": {
+ "Award": {
+ "properties": {
+ "relatedBid": {
+ "title": "Related bid",
+ "description": "Where bid details are used, a cross reference to the entry in the bids array to which this award relates. Provide the bid identifier here.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "deprecated": {
+ "description": "This field is deprecated in favor of `relatedBids`, to allow an award to combine multiple bids.",
+ "deprecatedVersion": "1.2"
+ }
+ },
+ "relatedBids": {
+ "title": "Related bids",
+ "description": "Where bid details are used, a cross reference to the entries in the bids array to which this award relates. Provide the bid identifiers here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "relatedBids": {
+ "title": "Related bids",
+ "description": "Where bid details are used, a cross reference to the entries in the bids array to which this contract relates. Provide the bid identifiers here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Statistic": {
+ "title": "Statistic",
+ "description": "For reporting aggregate statistics related to a tender. Where lots are in use, statistics can be broken down by lot.",
+ "type": "object",
+ "required": [
+ "id",
+ "measure",
+ "value"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "An internal identifier for this statistic.",
+ "type": "string"
+ },
+ "measure": {
+ "title": "Measure",
+ "description": "The statistic reported in the value.",
+ "type": "string",
+ "codelist": "statistic.csv",
+ "openCodelist": true
+ },
+ "date": {
+ "title": "Date",
+ "description": "The date when this statistic was last updated. This is often the closing date of the tender process. This field may be omitted unless either (a) the same statistic is provided from multiple points in time, or (b) there is a specific local requirement for the date when statistics were calculated to be provided.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "value": {
+ "title": "Value",
+ "description": "The value for the measure in question. Total counts should be provided as an integer. Percentages should be provided as a proportion of 1 (e.g. 10% = 0.1)",
+ "type": "number"
+ },
+ "valueGross": {
+ "title": "Gross value",
+ "description": "The monetary value for the measure in question, including all taxes.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "currency": {
+ "title": "Currency",
+ "description": "The currency of the amount in the `value` field, if the statistic has a monetary value.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "currency.csv",
+ "openCodelist": false,
+ "enum": [
+ "ADP",
+ "AED",
+ "AFA",
+ "AFN",
+ "ALK",
+ "ALL",
+ "AMD",
+ "ANG",
+ "AOA",
+ "AOK",
+ "AON",
+ "AOR",
+ "ARA",
+ "ARP",
+ "ARS",
+ "ARY",
+ "ATS",
+ "AUD",
+ "AWG",
+ "AYM",
+ "AZM",
+ "AZN",
+ "BAD",
+ "BAM",
+ "BBD",
+ "BDT",
+ "BEC",
+ "BEF",
+ "BEL",
+ "BGJ",
+ "BGK",
+ "BGL",
+ "BGN",
+ "BHD",
+ "BIF",
+ "BMD",
+ "BND",
+ "BOB",
+ "BOP",
+ "BOV",
+ "BRB",
+ "BRC",
+ "BRE",
+ "BRL",
+ "BRN",
+ "BRR",
+ "BSD",
+ "BTN",
+ "BUK",
+ "BWP",
+ "BYB",
+ "BYN",
+ "BYR",
+ "BZD",
+ "CAD",
+ "CDF",
+ "CHC",
+ "CHE",
+ "CHF",
+ "CHW",
+ "CLF",
+ "CLP",
+ "CNY",
+ "COP",
+ "COU",
+ "CRC",
+ "CSD",
+ "CSJ",
+ "CSK",
+ "CUC",
+ "CUP",
+ "CVE",
+ "CYP",
+ "CZK",
+ "DDM",
+ "DEM",
+ "DJF",
+ "DKK",
+ "DOP",
+ "DZD",
+ "ECS",
+ "ECV",
+ "EEK",
+ "EGP",
+ "ERN",
+ "ESA",
+ "ESB",
+ "ESP",
+ "ETB",
+ "EUR",
+ "FIM",
+ "FJD",
+ "FKP",
+ "FRF",
+ "GBP",
+ "GEK",
+ "GEL",
+ "GHC",
+ "GHP",
+ "GHS",
+ "GIP",
+ "GMD",
+ "GNE",
+ "GNF",
+ "GNS",
+ "GQE",
+ "GRD",
+ "GTQ",
+ "GWE",
+ "GWP",
+ "GYD",
+ "HKD",
+ "HNL",
+ "HRD",
+ "HRK",
+ "HTG",
+ "HUF",
+ "IDR",
+ "IEP",
+ "ILP",
+ "ILR",
+ "ILS",
+ "INR",
+ "IQD",
+ "IRR",
+ "ISJ",
+ "ISK",
+ "ITL",
+ "JMD",
+ "JOD",
+ "JPY",
+ "KES",
+ "KGS",
+ "KHR",
+ "KMF",
+ "KPW",
+ "KRW",
+ "KWD",
+ "KYD",
+ "KZT",
+ "LAJ",
+ "LAK",
+ "LBP",
+ "LKR",
+ "LRD",
+ "LSL",
+ "LSM",
+ "LTL",
+ "LTT",
+ "LUC",
+ "LUF",
+ "LUL",
+ "LVL",
+ "LVR",
+ "LYD",
+ "MAD",
+ "MDL",
+ "MGA",
+ "MGF",
+ "MKD",
+ "MLF",
+ "MMK",
+ "MNT",
+ "MOP",
+ "MRO",
+ "MRU",
+ "MTL",
+ "MTP",
+ "MUR",
+ "MVQ",
+ "MVR",
+ "MWK",
+ "MXN",
+ "MXP",
+ "MXV",
+ "MYR",
+ "MZE",
+ "MZM",
+ "MZN",
+ "NAD",
+ "NGN",
+ "NIC",
+ "NIO",
+ "NLG",
+ "NOK",
+ "NPR",
+ "NZD",
+ "OMR",
+ "PAB",
+ "PEH",
+ "PEI",
+ "PEN",
+ "PES",
+ "PGK",
+ "PHP",
+ "PKR",
+ "PLN",
+ "PLZ",
+ "PTE",
+ "PYG",
+ "QAR",
+ "RHD",
+ "ROK",
+ "ROL",
+ "RON",
+ "RSD",
+ "RUB",
+ "RUR",
+ "RWF",
+ "SAR",
+ "SBD",
+ "SCR",
+ "SDD",
+ "SDG",
+ "SDP",
+ "SEK",
+ "SGD",
+ "SHP",
+ "SIT",
+ "SKK",
+ "SLL",
+ "SOS",
+ "SRD",
+ "SRG",
+ "SSP",
+ "STD",
+ "STN",
+ "SUR",
+ "SVC",
+ "SYP",
+ "SZL",
+ "THB",
+ "TJR",
+ "TJS",
+ "TMM",
+ "TMT",
+ "TND",
+ "TOP",
+ "TPE",
+ "TRL",
+ "TRY",
+ "TTD",
+ "TWD",
+ "TZS",
+ "UAH",
+ "UAK",
+ "UGS",
+ "UGW",
+ "UGX",
+ "USD",
+ "USN",
+ "USS",
+ "UYI",
+ "UYN",
+ "UYP",
+ "UYU",
+ "UYW",
+ "UZS",
+ "VEB",
+ "VEF",
+ "VES",
+ "VNC",
+ "VND",
+ "VUV",
+ "WST",
+ "XAF",
+ "XAG",
+ "XAU",
+ "XBA",
+ "XBB",
+ "XBC",
+ "XBD",
+ "XCD",
+ "XDR",
+ "XEU",
+ "XFO",
+ "XFU",
+ "XOF",
+ "XPD",
+ "XPF",
+ "XPT",
+ "XRE",
+ "XSU",
+ "XTS",
+ "XUA",
+ "XXX",
+ "YDD",
+ "YER",
+ "YUD",
+ "YUM",
+ "YUN",
+ "ZAL",
+ "ZAR",
+ "ZMK",
+ "ZMW",
+ "ZRN",
+ "ZRZ",
+ "ZWC",
+ "ZWD",
+ "ZWL",
+ "ZWN",
+ "ZWR",
+ null
+ ]
+ },
+ "notes": {
+ "title": "Notes",
+ "description": "Any notes needed to understand or interpret the given statistic.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Related Lot",
+ "description": "Where lots are in use, if this statistic relates to a particular lot, provide the lot identifier here. If left blank, the statistic will be interpreted as applying to the whole tender.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "extension_explorer:source": {
+ "identifier": "bids",
+ "version": "master"
+ }
+ },
+ "Bids": {
+ "title": "Bids",
+ "description": "Summary and detailed information about bids received and evaluated as part of this contracting process.",
+ "type": "object",
+ "properties": {
+ "statistics": {
+ "title": "Statistics",
+ "description": "Summary statistics on the number and nature of bids received. Where information is provided on individual bids, these statistics should match those that can be calculated from the bid details array.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Statistic"
+ }
+ },
+ "details": {
+ "title": "Bid details",
+ "description": "An array of bids, providing information on the bidders, and where applicable, bid status, bid values and related documents. The extent to which this information can be disclosed varies from jurisdiction to jurisdiction.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Bid"
+ }
+ }
+ },
+ "extension_explorer:source": {
+ "identifier": "bids",
+ "version": "master"
+ }
+ },
+ "Bid": {
+ "title": "Bid",
+ "description": "For representing a bid or quote in response to the tender or qualification stage in this contracting process.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "A local identifier for this bid",
+ "type": "string"
+ },
+ "identifiers": {
+ "title": "Identifiers",
+ "description": "Identifiers for this bid. This field can be used to provide internal identifiers for the bid, such as identifiers from a buyer's document management system or procurement system.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/SimpleIdentifier"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "date": {
+ "title": "Date",
+ "description": "The date when this bid was received.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "description": {
+ "title": "Description",
+ "description": "A description of this bid. The description field may be used to describe the terms and conditions for the bid.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "title": "Status",
+ "description": "The status of the bid.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "bidStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "invited",
+ "pending",
+ "valid",
+ "disqualified",
+ "withdrawn",
+ null
+ ]
+ },
+ "items": {
+ "title": "Items offered by the tenderer(s)",
+ "description": "The goods, works or services offered by the tenderer(s), broken into line items wherever possible. Items should not be duplicated, but the quantity specified instead.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Item"
+ },
+ "uniqueItems": true
+ },
+ "tenderers": {
+ "title": "Tenderer",
+ "description": "The organization(s) responsible for this bid.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "value": {
+ "title": "Value",
+ "description": "The total value of the bid.",
+ "$ref": "#/definitions/Value"
+ },
+ "validityPeriod": {
+ "title": "Validity period",
+ "description": "The period for which this bid is valid.",
+ "$ref": "#/definitions/Period"
+ },
+ "documents": {
+ "title": "Documents",
+ "description": "All documents and attachments related to the bid and its evaluation.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Document"
+ },
+ "uniqueItems": true
+ },
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "The identifiers of the lots to which this bid relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "countriesOfOrigin": {
+ "title": "Countries of origin",
+ "description": "The countries of origin of the items in this bid, from the closed country codelist. If a country is missing, [create an issue](https://github.com/open-contracting/standard/issues) to discuss the addition of a user-assigned code to the country codelist.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "AD",
+ "AE",
+ "AF",
+ "AG",
+ "AI",
+ "AL",
+ "AM",
+ "AO",
+ "AQ",
+ "AR",
+ "AS",
+ "AT",
+ "AU",
+ "AW",
+ "AX",
+ "AZ",
+ "BA",
+ "BB",
+ "BD",
+ "BE",
+ "BF",
+ "BG",
+ "BH",
+ "BI",
+ "BJ",
+ "BL",
+ "BM",
+ "BN",
+ "BO",
+ "BQ",
+ "BR",
+ "BS",
+ "BT",
+ "BV",
+ "BW",
+ "BY",
+ "BZ",
+ "CA",
+ "CC",
+ "CD",
+ "CF",
+ "CG",
+ "CH",
+ "CI",
+ "CK",
+ "CL",
+ "CM",
+ "CN",
+ "CO",
+ "CR",
+ "CU",
+ "CV",
+ "CW",
+ "CX",
+ "CY",
+ "CZ",
+ "DE",
+ "DJ",
+ "DK",
+ "DM",
+ "DO",
+ "DZ",
+ "EC",
+ "EE",
+ "EG",
+ "EH",
+ "ER",
+ "ES",
+ "ET",
+ "FI",
+ "FJ",
+ "FK",
+ "FM",
+ "FO",
+ "FR",
+ "GA",
+ "GB",
+ "GD",
+ "GE",
+ "GF",
+ "GG",
+ "GH",
+ "GI",
+ "GL",
+ "GM",
+ "GN",
+ "GP",
+ "GQ",
+ "GR",
+ "GS",
+ "GT",
+ "GU",
+ "GW",
+ "GY",
+ "HK",
+ "HM",
+ "HN",
+ "HR",
+ "HT",
+ "HU",
+ "ID",
+ "IE",
+ "IL",
+ "IM",
+ "IN",
+ "IO",
+ "IQ",
+ "IR",
+ "IS",
+ "IT",
+ "JE",
+ "JM",
+ "JO",
+ "JP",
+ "KE",
+ "KG",
+ "KH",
+ "KI",
+ "KM",
+ "KN",
+ "KP",
+ "KR",
+ "KW",
+ "KY",
+ "KZ",
+ "LA",
+ "LB",
+ "LC",
+ "LI",
+ "LK",
+ "LR",
+ "LS",
+ "LT",
+ "LU",
+ "LV",
+ "LY",
+ "MA",
+ "MC",
+ "MD",
+ "ME",
+ "MF",
+ "MG",
+ "MH",
+ "MK",
+ "ML",
+ "MM",
+ "MN",
+ "MO",
+ "MP",
+ "MQ",
+ "MR",
+ "MS",
+ "MT",
+ "MU",
+ "MV",
+ "MW",
+ "MX",
+ "MY",
+ "MZ",
+ "NA",
+ "NC",
+ "NE",
+ "NF",
+ "NG",
+ "NI",
+ "NL",
+ "NO",
+ "NP",
+ "NR",
+ "NU",
+ "NZ",
+ "OM",
+ "PA",
+ "PE",
+ "PF",
+ "PG",
+ "PH",
+ "PK",
+ "PL",
+ "PM",
+ "PN",
+ "PR",
+ "PS",
+ "PT",
+ "PW",
+ "PY",
+ "QA",
+ "RE",
+ "RO",
+ "RS",
+ "RU",
+ "RW",
+ "SA",
+ "SB",
+ "SC",
+ "SD",
+ "SE",
+ "SG",
+ "SH",
+ "SI",
+ "SJ",
+ "SK",
+ "SL",
+ "SM",
+ "SN",
+ "SO",
+ "SR",
+ "SS",
+ "ST",
+ "SV",
+ "SX",
+ "SY",
+ "SZ",
+ "TC",
+ "TD",
+ "TF",
+ "TG",
+ "TH",
+ "TJ",
+ "TK",
+ "TL",
+ "TM",
+ "TN",
+ "TO",
+ "TR",
+ "TT",
+ "TV",
+ "TW",
+ "TZ",
+ "UA",
+ "UG",
+ "UM",
+ "US",
+ "UY",
+ "UZ",
+ "VA",
+ "VC",
+ "VE",
+ "VG",
+ "VI",
+ "VN",
+ "VU",
+ "WF",
+ "WS",
+ "XK",
+ "YE",
+ "YT",
+ "ZA",
+ "ZM",
+ "ZW"
+ ]
+ },
+ "codelist": "country.csv",
+ "openCodelist": false,
+ "minItems": 1
+ },
+ "hasRank": {
+ "title": "Has rank",
+ "description": "Whether this bid is ranked.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "rank": {
+ "title": "Rank",
+ "description": "The position of this bid (i.e. whether the bid is ranked first, second, third, etc.) in a design contest, a framework agreement with multiple winners (e.g. cascades), an innovation partnership, a competitive dialogue, or another procedure.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "variant": {
+ "title": "Is variant",
+ "description": "Whether the bid is a variant. A variant is a bid that fulfills the buyer's needs differently than as proposed in the procurement documents.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ },
+ "extension_explorer:source": {
+ "identifier": "bids",
+ "version": "master"
+ }
+ },
+ "SimpleIdentifier": {
+ "title": "Simple identifier",
+ "description": "An unambiguous reference to a resource within a given context.",
+ "type": "object",
+ "properties": {
+ "scheme": {
+ "title": "Scheme",
+ "description": "The list, register or system from which the identifier is taken.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "The identifier taken from the scheme.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "versionId": true,
+ "minLength": 1
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "bids",
+ "version": "master"
+ }
+ }
+ }
+}
diff --git a/en/extensions/bids/master/schema/index.html b/en/extensions/bids/master/schema/index.html
new file mode 100644
index 000000000..fd5cff7d5
--- /dev/null
+++ b/en/extensions/bids/master/schema/index.html
@@ -0,0 +1,965 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Bid statistics and details +
+ ++ Allowing bid statistics, and detailed bid information to be represented. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Information on bids submitted as part of a contracting process is important for many forms of analysis, including:
+-
+
- Market analysis for understanding the competitiveness of a given marketplace; +
- Red flag analysis for understanding potential corruption risks; and +
- Value for money analysis; +
Regulatory regimes vary on the extent to which they allow information on bidding to be proactively published, and at what point in the procurement process. In some systems and processes, a list of invited bidders is published at the start of tendering, and full details and documents on the bids received are disclosed when evaluation is complete. In other systems, only summary statistics on the number of bids received is made public.
+The OCDS bid extension introduces a new, flexible, top-level section to each contracting process to capture bidding information. Implementers will need to assess which fields are applicable to their local regulatory regime, and to local use-cases.
+This extension can also be used to publish data on quotes.
+Schema
+The bids.details array is used to provide one or more Bid objects, each representing a unique bid received.
The bids.statistics array is used to represent key statistical information about the number of bids and bidders. Each entry in the array is a Statistic object containing at least:
-
+
- An identifier +
- A measure, from the
statistic.csvcodelist
+ - A value for that measure +
The statistic.csv codelist is an open codelist. Publishers can add their own codes to this list. When doing so, publishers are encouraged to engage with the open contracting community to agree upon definitions of each code.
For example, publishers may wish to add statistics on minority or women-owned businesses, or bids that meet certain environmental standards and targets.
+The codelist's Category column indicates whether the statistic applies to bids or bidders or whether it is specified or required by a particular regulatory context (e.g. EU).
+Guidance
+Correcting a bid's value
+Buyers and procuring entities – and, in some jurisdictions, bidders – can correct a bid's value after the bid is submitted: for example, to correct an arithmetical error or a misplaced decimal mark.
+In OCDS, the bid's value is disclosed via the bids.details.value field. If a bid's value is corrected, the value of the bids.details.value field is overwritten. As such, the originally submitted value is only available via the contracting process' change history.
As a publisher, to make both the original and corrected values available to users, publish at least two releases for the contracting process: one release containing the bid's originally submitted value and another containing its corrected value.
+Example
+Below is an example of a bids extension:
+{
+ "bids": {
+ "statistics": [
+ {
+ "id": "1",
+ "measure": "validBids",
+ "value": 1,
+ "date": "2016-12-09T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were considered valid against relevant criteria."
+ },
+ {
+ "id": "2",
+ "measure": "highestValidBidValue",
+ "value": 1000,
+ "valueGross": 1200,
+ "currency": "USD"
+ },
+ {
+ "id": "3",
+ "measure": "lowestValidBidValue",
+ "value": 1000,
+ "valueGross": 1200,
+ "currency": "USD"
+ }
+ ],
+ "details": [
+ {
+ "id": "1",
+ "date": "2016-12-09T01:00:00+01:00",
+ "status": "valid",
+ "identifiers": [
+ {
+ "id": "bid-123-456",
+ "scheme": "internal"
+ }
+ ],
+ "items": [
+ {
+ "id": "1",
+ "description": "Installation and operation of the Shared Public Telecommunications Network",
+ "classification": {
+ "scheme": "CPV",
+ "id": "32412100",
+ "description": "Telecommunications network",
+ "uri": "http://purl.org/cpv/2008/code-32412100"
+ },
+ "quantity": 1
+ }
+ ],
+ "value": {
+ "amount": 1000,
+ "currency": "USD"
+ },
+ "tenderers": [
+ {
+ "id": "MEGA",
+ "name": "Mega Consortium"
+ }
+ ],
+ "countriesOfOrigin": [
+ "MX"
+ ],
+ "hasRank": true,
+ "rank": 1,
+ "variant": true
+ },
+ {
+ "id": "2",
+ "date": "2016-12-10T01:00:00+01:00",
+ "status": "disqualified",
+ "value": {
+ "amount": 1500,
+ "currency": "USD"
+ },
+ "tenderers": [
+ {
+ "id": "BETA",
+ "name": "Beta Consortium"
+ }
+ ],
+ "hasRank": true,
+ "rank": 2
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "1",
+ "title": "Example PPP contract award",
+ "description": "Award of Example PPP contract to Mega Consortium",
+ "status": "active",
+ "date": "2016-12-17T10:00:00-06:00",
+ "relatedBids": [
+ "1"
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "relatedBids": [
+ "1"
+ ]
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+Unreleased
+-
+
- Add fields:
+
-
+
Bid.identifiers
+Bid.description
+Bid.items
+Bid.countriesOfOrigin
+Bid.hasRank
+Bid.rank
+Bid.relatedLots(moved from the Lots extension)
+Bid.validityPeriod
+Bid.variant
+BidsStatistic.valueGross
+Award.relatedBids
+Contract.relatedBids
+
+ - Deprecate the
Award.relatedBidfield
+ - Add guidance on correcting bid values +
- Rename the
BidStatisticdefinition toStatistic, and remove bid-specific language from its fields' descriptions
+ - Rename the
bidStatistics.csvcodelist tostatistic.csv
+ - Add codes to
statistic.csv: +-
+
- 'microBids' +
- 'smallBids' +
- 'mediumBids' +
- 'disqualifiedBids' +
+
v1.1.5
+-
+
- Add
BidsStatistic.currencyfield
+ - Add 'lowestValidBidValue' and 'highestValidBidValue' codes to
bidStatistics.csv
+ - Remove type information from field descriptions +
- Review normative and non-normative words +
v1.1.4
+-
+
- Fix the title and description of the 'foreignBidsFromEU' code to refer to the European Economic Area (EEA). Previously, its title referred to the European Single Market, but its description listed the members of the EEA. +
- Add a 'foreignBidsFromNonEU' code to
bidStatistics.csv
+ - Remove invalid
requiredproperty on array fieldBids.details
+ - Fix the merge behavior of
Bids.statisticsandBid.tenderersto use identifier merge strategy
+ - Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow required fields
BidsStatistic.id,BidsStatistic.measure,BidsStatistic.valuefrom being null
+ - Disallow
Bids.statisticsfrom having null in its array of objects
+ - Allow
Bids.statisticsto be null
+ - Add enum to
Bid.status
+ - Move
BidsStatistic.requirementResponsesto requirements extension
+ - Add descriptions to bidStatus.csv +
- List codelists in extension.json +
- Add example to documentation +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/bids/v1.1.4/README.md b/en/extensions/bids/v1.1.4/README.md
new file mode 100644
index 000000000..849ee46cf
--- /dev/null
+++ b/en/extensions/bids/v1.1.4/README.md
@@ -0,0 +1,134 @@
+# Bid statistics and details
+
+Information on bids submitted as part of a contracting process is important for many forms of analysis, including:
+
+- Market analysis for understanding the competitiveness of a given marketplace;
+- Red flag analysis for understanding potential corruption risks; and
+- Value for money analysis;
+
+Regulatory regimes vary on the extent to which they allow information on bidding to be proactively published, and at what point in the procurement process. In some systems and processes, a list of invited bidders will be published at the start of tendering, and full details and documents on the bids received may be disclosed when evaluation is complete. In other systems, only summary statistics on the number of bids received may be made public.
+
+The OCDS bid extension introduces a new, flexible, top-level section to each contracting process to capture bidding information. Implementers will need to assess which fields are applicable to their local regulatory regime, and to local use-cases.
+
+## Schema
+
+The `bids/details` array is used to provide one or more `Bid` objects, each representing a unique bid received.
+
+The `bids/statistics` array is used to represent key statistical information about the number of bids and bidders. Each entry in the array is a `BidsStatistic` object containing at least:
+
+- An identifier
+- A measure, from the `bidStatistics.csv` codelist
+- A value for that measure
+
+The `bidStatistics.csv` codelist is an **open** codelist. Publishers can add their own codes to this list. When doing so, publishers are encouraged to engage with the open contracting community to agree upon definitions of each code.
+
+For example, publishers may wish to add statistics on minority or women-owned businesses, or bids that meet certain environmental standards and targets.
+
+The codelist's Category column indicates whether the statistic applies to bids or bidders or whether it is specified or required by a particular regulatory context (e.g. EU).
+
+## Example
+
+Below is an example of a bids extension:
+
+```json
+{
+ "bids": {
+ "statistics": [{
+ "id": "1.0",
+ "measure": "validBids",
+ "value": 1,
+ "date": "2016-12-09T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were considered valid against relevant criteria."
+ }, {
+ "id": "2.0",
+ "measure": "disqualifiedBids",
+ "value": 1,
+ "date": "2016-12-10T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were disqualified."
+ }],
+ "details": [{
+ "id": "1.0",
+ "date": "2016-12-09T01:00:00+01:00",
+ "status": "valid",
+ "value": {
+ "amount": 1000,
+ "currency": "USD"
+ },
+ "documents": [{
+ "id": "1.0",
+ "documentType": "evaluationReports",
+ "title": "Mega Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Mega Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_megaConsortium.pdf",
+ "datePublished": "2016-11-17T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en",
+ "author": "Ministry of Communications"
+ }],
+ "tenderers": [{
+ "id": "MEGA",
+ "name": "Mega Consortium"
+ }]
+ }, {
+ "id": "2.0",
+ "date": "2016-12-10T01:00:00+01:00",
+ "status": "disqualified",
+ "value": {
+ "amount": 1500,
+ "currency": "USD"
+ },
+ "documents": [{
+ "id": "1.0",
+ "documentType": "evaluationReports",
+ "title": "Beta Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Beta Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_betaConsortium.pdf",
+ "datePublished": "2016-11-18T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en",
+ "author": "Ministry of Communications"
+ }],
+ "tenderers": [{
+ "id": "BETA",
+ "name": "Beta Consortium"
+ }]
+ }]
+
+ },
+ "awards": [{
+ "id": "111",
+ "title": "Example PPP contract award",
+ "description": "Award of Example PPP contract to Mega Consortium",
+ "status": "active",
+ "date": "2016-12-17T10:00:00-06:00",
+ "relatedBid": "1.0"
+ }]
+}
+```
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.4
+
+- Fix the title and description of the 'foreignBidsFromEU' code to refer to the European Economic Area (EEA). Previously, its title referred to the European Single Market, but its description listed the members of the EEA.
+- Add a 'foreignBidsFromNonEU' code to `bidStatistics.csv`
+- Remove invalid `required` property on array field `Bids.details`
+- Fix the merge behavior of `Bids.statistics` and `Bid.tenderers` to use identifier merge strategy
+- Remove Sphinx directives from readme
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Disallow required fields `BidsStatistic.id`, `BidsStatistic.measure`, `BidsStatistic.value` from being null
+- Disallow `Bids.statistics` from having null in its array of objects
+- Allow `Bids.statistics` to be null
+- Add enum to `BidsStatistic.status`
+- Move `BidsStatistic.requirementResponses` to requirements extension
+- Add descriptions to bidStatus.csv
+- List codelists in extension.json
+- Add example to documentation
+- Add tests and tidy code
diff --git a/en/extensions/bids/v1.1.4/codelists/bidStatistics.csv b/en/extensions/bids/v1.1.4/codelists/bidStatistics.csv
new file mode 100644
index 000000000..602341d60
--- /dev/null
+++ b/en/extensions/bids/v1.1.4/codelists/bidStatistics.csv
@@ -0,0 +1,13 @@
+Category,Code,Title,Description
+bids,requests,Requests to participate,The total number of unique requests to participate received
+bids,bids,Bids,The total number of unique bids received (prior to any being discounted for not meeting essential criteria).
+bids,validBids,Valid bids,"The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids should be considered during the tender evaluation stage."
+bidders,bidders,Bidders,The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria).
+bidders,qualifiedBidders,Qualified bidders,The total number of unique organizations or consortia passing the qualification stage of the evaluation process.
+bidders,disqualifiedBidders,Disqualified bidders,The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process.
+EU,electronicBids,Electronic bids,The number of bids received by electronic means.
+EU,smeBids,Bids from SMEs,The number of bids received from small and medium-sized enterprises.
+EU,foreignBids,Bids from foreign firms,The number of bids received from bidders from outside the country where the tender is issued.
+EU,foreignBidsFromEU,Bids from firms in other European Economic Area countries,The number of bids received from tenderers from other European Economic Area countries.
+EU,foreignBidsFromNonEU,Bids from firms in non-European Economic Area countries,The number of bids received from tenderers from non-European Economic Area countries.
+EU,tendersAbnormallyLow,Tenders excluded because they were abnormally low,"The number of tenders excluded because they were abnormally low. Note that in some EU datasets this may have been converted from a boolean, such that a value of 1 would indicate '1 or more' tenders were excluded. Users should evaluate and interpret data accordingly."
diff --git a/en/extensions/bids/v1.1.4/codelists/bidStatus.csv b/en/extensions/bids/v1.1.4/codelists/bidStatus.csv
new file mode 100644
index 000000000..fc2071691
--- /dev/null
+++ b/en/extensions/bids/v1.1.4/codelists/bidStatus.csv
@@ -0,0 +1,6 @@
+Code,Title,Description
+invited,Invited,A bid has been invited from the listed tenderer(s).
+pending,Pending,A bid has been submitted but not yet evaluated.
+valid,Valid,The submitted bid met the qualification requirements in order to be evaluated.
+disqualified,Disqualified,The submitted bid did not meet the qualification requirements in order to be evaluated.
+withdrawn,Withdrawn,The submitted bid was withdrawn by the tenderer(s).
diff --git a/en/extensions/bids/v1.1.4/codelists/index.html b/en/extensions/bids/v1.1.4/codelists/index.html
new file mode 100644
index 000000000..b9f86392c
--- /dev/null
+++ b/en/extensions/bids/v1.1.4/codelists/index.html
@@ -0,0 +1,587 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Bid statistics and details +
+ ++ Allowing bid statistics, and detailed bid information to be represented. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ bids
+
+ |
+ + Bids + | +
+ The bid section is used to publish summary statistics, and where applicable, individual bid information. + + |
+ + Bids object + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedBid
+
+ |
+ + Related bid + | +
+ Where bid details are used, a cross reference to the entry in the bids array to which this award relates. Provide the bid identifier here. + ++ + Deprecated in OCDS 1.2: + + This field is deprecated in favor of `relatedBids`, to allow an award to combine multiple bids. + + |
+ + string + | +
+
+ relatedBids
+
+ |
+ + Related bids + | +
+ Where bid details are used, a cross reference to the entries in the bids array to which this award relates. Provide the bid identifiers here. + + |
+ + array of strings + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedBids
+
+ |
+ + Related bids + | +
+ Where bid details are used, a cross reference to the entries in the bids array to which this contract relates. Provide the bid identifiers here. + + |
+ + array of strings + | +
+ Statistic +
+ +
+ The extension defines a new Statistic object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ An internal identifier for this statistic. + + |
+ + string + | +
+
+ measure
+
+ |
+ + Measure + | +
+ The statistic reported in the value. + + |
+ + string from open statistic codelist + | +
+
+ date
+
+ |
+ + Date + | +
+ The date when this statistic was last updated. This is often the closing date of the tender process. This field may be omitted unless either (a) the same statistic is provided from multiple points in time, or (b) there is a specific local requirement for the date when statistics were calculated to be provided. + + |
+ + string + | +
+
+ value
+
+ |
+ + Value + | +
+ The value for the measure in question. Total counts should be provided as an integer. Percentages should be provided as a proportion of 1 (e.g. 10% = 0.1) + + |
+ + number + | +
+
+ valueGross
+
+ |
+ + Gross value + | +
+ The monetary value for the measure in question, including all taxes. + + |
+ + number + | +
+
+ currency
+
+ |
+ + Currency + | +
+ The currency of the amount in the |
+ + string from closed currency codelist + | +
+
+ notes
+
+ |
+ + Notes + | +
+ Any notes needed to understand or interpret the given statistic. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Related Lot + | +
+ Where lots are in use, if this statistic relates to a particular lot, provide the lot identifier here. If left blank, the statistic will be interpreted as applying to the whole tender. + + |
+ + string + | +
+ Bids +
+ +
+ The extension defines a new Bids object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statistics
+
+ |
+ + Statistics + | +
+ Summary statistics on the number and nature of bids received. Where information is provided on individual bids, these statistics should match those that can be calculated from the bid details array. + + |
+ + array of Statistic objects + | +
+
+ details
+
+ |
+ + Bid details + | +
+ An array of bids, providing information on the bidders, and where applicable, bid status, bid values and related documents. The extent to which this information can be disclosed varies from jurisdiction to jurisdiction. + + |
+ + array of Bid objects + | +
+ Bid +
+ +
+ The extension defines a new Bid object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ A local identifier for this bid + + |
+ + string + | +
+
+ identifiers
+
+ |
+ + Identifiers + | +
+ Identifiers for this bid. This field can be used to provide internal identifiers for the bid, such as identifiers from a buyer's document management system or procurement system. + + |
+ + array of SimpleIdentifier objects + | +
+
+ date
+
+ |
+ + Date + | +
+ The date when this bid was received. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A description of this bid. The description field may be used to describe the terms and conditions for the bid. + + |
+ + string + | +
+
+ status
+
+ |
+ + Status + | +
+ The status of the bid. + + |
+ + string from closed bidStatus codelist + | +
+
+ items
+
+ |
+ + Items offered by the tenderer(s) + | +
+ The goods, works or services offered by the tenderer(s), broken into line items wherever possible. Items should not be duplicated, but the quantity specified instead. + + |
+ + array of Item objects + | +
+
+ tenderers
+
+ |
+ + Tenderer + | +
+ The organization(s) responsible for this bid. + + |
+ + array of OrganizationReference objects + | +
+
+ value
+
+ |
+ + Value + | +
+ The total value of the bid. + + |
+ + Value object + | +
+
+ validityPeriod
+
+ |
+ + Validity period + | +
+ The period for which this bid is valid. + + |
+ + Period object + | +
+
+ documents
+
+ |
+ + Documents + | +
+ All documents and attachments related to the bid and its evaluation. + + |
+ + array of Document objects + | +
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ The identifiers of the lots to which this bid relates. + + |
+ + array of strings + | +
+
+ countriesOfOrigin
+
+ |
+ + Countries of origin + | +
+ The countries of origin of the items in this bid, from the closed country codelist. If a country is missing, create an issue to discuss the addition of a user-assigned code to the country codelist. + + |
+ + array of strings from closed country codelist + | +
+
+ hasRank
+
+ |
+ + Has rank + | +
+ Whether this bid is ranked. + + |
+ + boolean + | +
+
+ rank
+
+ |
+ + Rank + | +
+ The position of this bid (i.e. whether the bid is ranked first, second, third, etc.) in a design contest, a framework agreement with multiple winners (e.g. cascades), an innovation partnership, a competitive dialogue, or another procedure. + + |
+ + integer + | +
+
+ variant
+
+ |
+ + Is variant + | +
+ Whether the bid is a variant. A variant is a bid that fulfills the buyer's needs differently than as proposed in the procurement documents. + + |
+ + boolean + | +
+ SimpleIdentifier +
+ +
+ The extension defines a new SimpleIdentifier object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ scheme
+
+ |
+ + Scheme + | +
+ The list, register or system from which the identifier is taken. + + |
+ + string + | +
+
+ id
+
+ |
+ + ID + | +
+ The identifier taken from the scheme. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/bids/v1.1.4/extension.json b/en/extensions/bids/v1.1.4/extension.json
new file mode 100644
index 000000000..cbe6a6fe9
--- /dev/null
+++ b/en/extensions/bids/v1.1.4/extension.json
@@ -0,0 +1,23 @@
+{
+ "name": {
+ "en": "Bid statistics and details",
+ "es": "Estad\u00edsticas y detalles de las ofertas"
+ },
+ "description": {
+ "en": "Allowing bid statistics, and detailed bid information to be represented.",
+ "es": "Permite que se muestren las estad\u00edsticas de ofertas y la informaci\u00f3n detallada de las ofertas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/bids/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "bidStatistics.csv",
+ "bidStatus.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/en/extensions/bids/v1.1.4/index.html b/en/extensions/bids/v1.1.4/index.html
new file mode 100644
index 000000000..6e34b6d44
--- /dev/null
+++ b/en/extensions/bids/v1.1.4/index.html
@@ -0,0 +1,405 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Bid statistics and details +
+ ++ Allowing bid statistics, and detailed bid information to be represented. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ bidStatistics.csv +
+ +
+ You can download the bidStatistics.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ requests
+
+ |
+ + Requests to participate + | +
+ The total number of unique requests to participate received + +
|
+
+
+ bids
+
+ |
+ + Bids + | +
+ The total number of unique bids received (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ validBids
+
+ |
+ + Valid bids + | +
+ The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids should be considered during the tender evaluation stage. + +
|
+
+
+ bidders
+
+ |
+ + Bidders + | +
+ The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ qualifiedBidders
+
+ |
+ + Qualified bidders + | +
+ The total number of unique organizations or consortia passing the qualification stage of the evaluation process. + +
|
+
+
+ disqualifiedBidders
+
+ |
+ + Disqualified bidders + | +
+ The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process. + +
|
+
+
+ electronicBids
+
+ |
+ + Electronic bids + | +
+ The number of bids received by electronic means. + +
|
+
+
+ smeBids
+
+ |
+ + Bids from SMEs + | +
+ The number of bids received from small and medium-sized enterprises. + +
|
+
+
+ foreignBids
+
+ |
+ + Bids from foreign firms + | +
+ The number of bids received from bidders from outside the country where the tender is issued. + +
|
+
+
+ foreignBidsFromEU
+
+ |
+ + Bids from firms in other European Economic Area countries + | +
+ The number of bids received from tenderers from other European Economic Area countries. + +
|
+
+
+ foreignBidsFromNonEU
+
+ |
+ + Bids from firms in non-European Economic Area countries + | +
+ The number of bids received from tenderers from non-European Economic Area countries. + +
|
+
+
+ tendersAbnormallyLow
+
+ |
+ + Tenders excluded because they were abnormally low + | +
+ The number of tenders excluded because they were abnormally low. Note that in some EU datasets this may have been converted from a boolean, such that a value of 1 would indicate '1 or more' tenders were excluded. Users should evaluate and interpret data accordingly. + +
|
+
+ bidStatus.csv +
+ +
+ You can download the bidStatus.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ invited
+
+ |
+ + Invited + | +
+ A bid has been invited from the listed tenderer(s). + + |
+
+
+ pending
+
+ |
+ + Pending + | +
+ A bid has been submitted but not yet evaluated. + + |
+
+
+ valid
+
+ |
+ + Valid + | +
+ The submitted bid met the qualification requirements in order to be evaluated. + + |
+
+
+ disqualified
+
+ |
+ + Disqualified + | +
+ The submitted bid did not meet the qualification requirements in order to be evaluated. + + |
+
+
+ withdrawn
+
+ |
+ + Withdrawn + | +
+ The submitted bid was withdrawn by the tenderer(s). + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/bids/v1.1.4/release-schema.json b/en/extensions/bids/v1.1.4/release-schema.json
new file mode 100644
index 000000000..ec32a8032
--- /dev/null
+++ b/en/extensions/bids/v1.1.4/release-schema.json
@@ -0,0 +1,166 @@
+{
+ "properties": {
+ "bids": {
+ "title": "Bids",
+ "description": "The bid section is used to publish summary statistics, and where applicable, individual bid information.",
+ "$ref": "#/definitions/Bids"
+ }
+ },
+ "definitions": {
+ "Award": {
+ "properties": {
+ "relatedBid": {
+ "title": "Related bid",
+ "description": "Where bid details are used, a cross reference to the entry in the bids array to which this award relates. Provide the bid identifier here.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "BidsStatistic": {
+ "title": "Bid Statistic",
+ "description": "For reporting aggregate statistics about the bids related to a tender. Where lots are in use, statistics may optionally be broken down by lot.",
+ "type": "object",
+ "required": [
+ "id",
+ "measure",
+ "value"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "An internal identifier for this statistical item.",
+ "type": "string"
+ },
+ "measure": {
+ "title": "Measure",
+ "description": "An item from the bidStatistics codelist for the statistic reported in value. This is an open codelist, and other statistics may also be included.",
+ "type": "string",
+ "codelist": "bidStatistics.csv",
+ "openCodelist": true
+ },
+ "date": {
+ "title": "Date",
+ "description": "The date when this statistic was last updated. This is often the closing date of the tender process. This field can be left blank unless either (a) the same statistic is provided from multiple points in time, or (b) there is a specific local requirement for the date when statistics were calculated to be provided.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "value": {
+ "title": "Value",
+ "description": "The value for the measure in question. Total counts should be provided as an integer. Percentages should be presented as a proportion of 1 (e.g. 10% = 0.1)",
+ "type": "number"
+ },
+ "notes": {
+ "title": "Notes",
+ "description": "Any notes required to understand or interpret the given statistic.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Related Lot",
+ "description": "Where lots are in use, if this statistic relates to bids on a particular lot, provide the lot identifier here. If left blank, the statistic will be interpreted as applying to the whole tender.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Bids": {
+ "title": "Bids",
+ "description": "Summary and detailed information about bids received and evaluated as part of this contracting process.",
+ "type": "object",
+ "properties": {
+ "statistics": {
+ "title": "Statistics",
+ "description": "Summary statistics on the number and nature of bids received. Where information is provided on individual bids, these statistics should match those that can be calculated from the bid details array.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/BidsStatistic"
+ }
+ },
+ "details": {
+ "title": "Bid details",
+ "description": "An array of bids, providing information on the bidders, and where applicable, bid status, bid values and related documents. The extent to which this information can be disclosed varies from jurisdiction to jurisdiction.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Bid"
+ }
+ }
+ }
+ },
+ "Bid": {
+ "title": "Bid",
+ "description": "For representing a bid in response to the tender or qualification stage in this contracting process.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "A local identifier for this bid",
+ "type": [
+ "string"
+ ]
+ },
+ "date": {
+ "title": "Date",
+ "description": "The date when this bid was received.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "status": {
+ "title": "Status",
+ "description": "The status of the bid, drawn from the bidStatus codelist",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "bidStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "invited",
+ "pending",
+ "valid",
+ "disqualified",
+ "withdrawn",
+ null
+ ]
+ },
+ "tenderers": {
+ "title": "Tenderer",
+ "description": "The party, or parties, responsible for this bid. This should provide a name and identifier, cross-referenced to an entry in the parties array at the top level of the release.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "value": {
+ "title": "Value",
+ "description": "The total value of the bid.",
+ "$ref": "#/definitions/Value"
+ },
+ "documents": {
+ "title": "Documents",
+ "description": "All documents and attachments related to the bid and its evaluation.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Document"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/bids/v1.1.4/schema/index.html b/en/extensions/bids/v1.1.4/schema/index.html
new file mode 100644
index 000000000..39af1cd0a
--- /dev/null
+++ b/en/extensions/bids/v1.1.4/schema/index.html
@@ -0,0 +1,636 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Bid statistics and details +
+ ++ Allowing bid statistics, and detailed bid information to be represented. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Information on bids submitted as part of a contracting process is important for many forms of analysis, including:
+-
+
- Market analysis for understanding the competitiveness of a given marketplace; +
- Red flag analysis for understanding potential corruption risks; and +
- Value for money analysis; +
Regulatory regimes vary on the extent to which they allow information on bidding to be proactively published, and at what point in the procurement process. In some systems and processes, a list of invited bidders will be published at the start of tendering, and full details and documents on the bids received may be disclosed when evaluation is complete. In other systems, only summary statistics on the number of bids received may be made public.
+The OCDS bid extension introduces a new, flexible, top-level section to each contracting process to capture bidding information. Implementers will need to assess which fields are applicable to their local regulatory regime, and to local use-cases.
+Schema
+The bids/details array is used to provide one or more Bid objects, each representing a unique bid received.
The bids/statistics array is used to represent key statistical information about the number of bids and bidders. Each entry in the array is a BidsStatistic object containing at least:
-
+
- An identifier +
- A measure, from the
bidStatistics.csvcodelist
+ - A value for that measure +
The bidStatistics.csv codelist is an open codelist. Publishers can add their own codes to this list. When doing so, publishers are encouraged to engage with the open contracting community to agree upon definitions of each code.
For example, publishers may wish to add statistics on minority or women-owned businesses, or bids that meet certain environmental standards and targets.
+The codelist's Category column indicates whether the statistic applies to bids or bidders or whether it is specified or required by a particular regulatory context (e.g. EU).
+Example
+Below is an example of a bids extension:
+{
+ "bids": {
+ "statistics": [{
+ "id": "1.0",
+ "measure": "validBids",
+ "value": 1,
+ "date": "2016-12-09T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were considered valid against relevant criteria."
+ }, {
+ "id": "2.0",
+ "measure": "disqualifiedBids",
+ "value": 1,
+ "date": "2016-12-10T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were disqualified."
+ }],
+ "details": [{
+ "id": "1.0",
+ "date": "2016-12-09T01:00:00+01:00",
+ "status": "valid",
+ "value": {
+ "amount": 1000,
+ "currency": "USD"
+ },
+ "documents": [{
+ "id": "1.0",
+ "documentType": "evaluationReports",
+ "title": "Mega Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Mega Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_megaConsortium.pdf",
+ "datePublished": "2016-11-17T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en",
+ "author": "Ministry of Communications"
+ }],
+ "tenderers": [{
+ "id": "MEGA",
+ "name": "Mega Consortium"
+ }]
+ }, {
+ "id": "2.0",
+ "date": "2016-12-10T01:00:00+01:00",
+ "status": "disqualified",
+ "value": {
+ "amount": 1500,
+ "currency": "USD"
+ },
+ "documents": [{
+ "id": "1.0",
+ "documentType": "evaluationReports",
+ "title": "Beta Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Beta Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_betaConsortium.pdf",
+ "datePublished": "2016-11-18T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en",
+ "author": "Ministry of Communications"
+ }],
+ "tenderers": [{
+ "id": "BETA",
+ "name": "Beta Consortium"
+ }]
+ }]
+
+ },
+ "awards": [{
+ "id": "111",
+ "title": "Example PPP contract award",
+ "description": "Award of Example PPP contract to Mega Consortium",
+ "status": "active",
+ "date": "2016-12-17T10:00:00-06:00",
+ "relatedBid": "1.0"
+ }]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.4
+-
+
- Fix the title and description of the 'foreignBidsFromEU' code to refer to the European Economic Area (EEA). Previously, its title referred to the European Single Market, but its description listed the members of the EEA. +
- Add a 'foreignBidsFromNonEU' code to
bidStatistics.csv
+ - Remove invalid
requiredproperty on array fieldBids.details
+ - Fix the merge behavior of
Bids.statisticsandBid.tenderersto use identifier merge strategy
+ - Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow required fields
BidsStatistic.id,BidsStatistic.measure,BidsStatistic.valuefrom being null
+ - Disallow
Bids.statisticsfrom having null in its array of objects
+ - Allow
Bids.statisticsto be null
+ - Add enum to
BidsStatistic.status
+ - Move
BidsStatistic.requirementResponsesto requirements extension
+ - Add descriptions to bidStatus.csv +
- List codelists in extension.json +
- Add example to documentation +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/bids/v1.1.5/README.md b/en/extensions/bids/v1.1.5/README.md
new file mode 100644
index 000000000..dc307df1c
--- /dev/null
+++ b/en/extensions/bids/v1.1.5/README.md
@@ -0,0 +1,166 @@
+# Bid statistics and details
+
+Information on bids submitted as part of a contracting process is important for many forms of analysis, including:
+
+- Market analysis for understanding the competitiveness of a given marketplace;
+- Red flag analysis for understanding potential corruption risks; and
+- Value for money analysis;
+
+Regulatory regimes vary on the extent to which they allow information on bidding to be proactively published, and at what point in the procurement process. In some systems and processes, a list of invited bidders is published at the start of tendering, and full details and documents on the bids received are disclosed when evaluation is complete. In other systems, only summary statistics on the number of bids received is made public.
+
+The OCDS bid extension introduces a new, flexible, top-level section to each contracting process to capture bidding information. Implementers will need to assess which fields are applicable to their local regulatory regime, and to local use-cases.
+
+## Schema
+
+The `bids.details` array is used to provide one or more `Bid` objects, each representing a unique bid received.
+
+The `bids.statistics` array is used to represent key statistical information about the number of bids and bidders. Each entry in the array is a `BidsStatistic` object containing at least:
+
+- An identifier
+- A measure, from the `bidStatistics.csv` codelist
+- A value for that measure
+
+The `bidStatistics.csv` codelist is an **open** codelist. Publishers can add their own codes to this list. When doing so, publishers are encouraged to engage with the open contracting community to agree upon definitions of each code.
+
+For example, publishers may wish to add statistics on minority or women-owned businesses, or bids that meet certain environmental standards and targets.
+
+The codelist's Category column indicates whether the statistic applies to bids or bidders or whether it is specified or required by a particular regulatory context (e.g. EU).
+
+## Example
+
+Below is an example of a bids extension:
+
+```json
+{
+ "bids": {
+ "statistics": [
+ {
+ "id": "1",
+ "measure": "validBids",
+ "value": 1,
+ "date": "2016-12-09T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were considered valid against relevant criteria."
+ },
+ {
+ "id": "2",
+ "measure": "disqualifiedBids",
+ "value": 1,
+ "date": "2016-12-10T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were disqualified."
+ },
+ {
+ "id": "3",
+ "measure": "highestValidBidValue",
+ "value": 1000,
+ "currency": "USD"
+ },
+ {
+ "id": "4",
+ "measure": "lowestValidBidValue",
+ "value": 1000,
+ "currency": "USD"
+ }
+ ],
+ "details": [
+ {
+ "id": "1",
+ "date": "2016-12-09T01:00:00+01:00",
+ "status": "valid",
+ "value": {
+ "amount": 1000,
+ "currency": "USD"
+ },
+ "documents": [
+ {
+ "id": "1",
+ "documentType": "evaluationReports",
+ "title": "Mega Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Mega Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_megaConsortium.pdf",
+ "datePublished": "2016-11-17T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en"
+ }
+ ],
+ "tenderers": [
+ {
+ "id": "MEGA",
+ "name": "Mega Consortium"
+ }
+ ]
+ },
+ {
+ "id": "2",
+ "date": "2016-12-10T01:00:00+01:00",
+ "status": "disqualified",
+ "value": {
+ "amount": 1500,
+ "currency": "USD"
+ },
+ "documents": [
+ {
+ "id": "1",
+ "documentType": "evaluationReports",
+ "title": "Beta Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Beta Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_betaConsortium.pdf",
+ "datePublished": "2016-11-18T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en"
+ }
+ ],
+ "tenderers": [
+ {
+ "id": "BETA",
+ "name": "Beta Consortium"
+ }
+ ]
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "111",
+ "title": "Example PPP contract award",
+ "description": "Award of Example PPP contract to Mega Consortium",
+ "status": "active",
+ "date": "2016-12-17T10:00:00-06:00",
+ "relatedBid": "1"
+ }
+ ]
+}
+```
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.5
+
+- Add `BidsStatistic.currency` field
+- Add 'lowestValidBidValue' and 'highestValidBidValue' codes to `bidStatistics.csv`
+- Remove type information from field descriptions
+- Review normative and non-normative words
+
+### v1.1.4
+
+- Fix the title and description of the 'foreignBidsFromEU' code to refer to the European Economic Area (EEA). Previously, its title referred to the European Single Market, but its description listed the members of the EEA.
+- Add a 'foreignBidsFromNonEU' code to `bidStatistics.csv`
+- Remove invalid `required` property on array field `Bids.details`
+- Fix the merge behavior of `Bids.statistics` and `Bid.tenderers` to use identifier merge strategy
+- Remove Sphinx directives from readme
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Disallow required fields `BidsStatistic.id`, `BidsStatistic.measure`, `BidsStatistic.value` from being null
+- Disallow `Bids.statistics` from having null in its array of objects
+- Allow `Bids.statistics` to be null
+- Add enum to `Bid.status`
+- Move `BidsStatistic.requirementResponses` to requirements extension
+- Add descriptions to bidStatus.csv
+- List codelists in extension.json
+- Add example to documentation
+- Add tests and tidy code
diff --git a/en/extensions/bids/v1.1.5/codelists/bidStatistics.csv b/en/extensions/bids/v1.1.5/codelists/bidStatistics.csv
new file mode 100644
index 000000000..6098ed2d5
--- /dev/null
+++ b/en/extensions/bids/v1.1.5/codelists/bidStatistics.csv
@@ -0,0 +1,15 @@
+Category,Code,Title,Description
+bids,requests,Requests to participate,The total number of unique requests to participate received
+bids,bids,Bids,The total number of unique bids received (prior to any being discounted for not meeting essential criteria).
+bids,validBids,Valid bids,"The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids are considered during the tender evaluation stage."
+bids,lowestValidBidValue,Lowest valid bid value,The value of the lowest valid bid.
+bids,highestValidBidValue,Highest valid bid value,The value of the highest valid bid.
+bidders,bidders,Bidders,The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria).
+bidders,qualifiedBidders,Qualified bidders,The total number of unique organizations or consortia passing the qualification stage of the evaluation process.
+bidders,disqualifiedBidders,Disqualified bidders,The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process.
+EU,electronicBids,Electronic bids,The number of bids received by electronic means.
+EU,smeBids,Bids from SMEs,The number of bids received from small and medium-sized enterprises.
+EU,foreignBids,Bids from foreign firms,The number of bids received from bidders from outside the country where the tender is issued.
+EU,foreignBidsFromEU,Bids from firms in other European Economic Area countries,The number of bids received from tenderers from other European Economic Area countries.
+EU,foreignBidsFromNonEU,Bids from firms in non-European Economic Area countries,The number of bids received from tenderers from non-European Economic Area countries.
+EU,tendersAbnormallyLow,Tenders excluded because they were abnormally low,"The number of tenders excluded because they were abnormally low. Note that in some EU datasets this might have been converted from a boolean, such that a value of 1 would indicate ""1 or more"" tenders were excluded. Users need to evaluate and interpret data accordingly."
diff --git a/en/extensions/bids/v1.1.5/codelists/bidStatus.csv b/en/extensions/bids/v1.1.5/codelists/bidStatus.csv
new file mode 100644
index 000000000..fc2071691
--- /dev/null
+++ b/en/extensions/bids/v1.1.5/codelists/bidStatus.csv
@@ -0,0 +1,6 @@
+Code,Title,Description
+invited,Invited,A bid has been invited from the listed tenderer(s).
+pending,Pending,A bid has been submitted but not yet evaluated.
+valid,Valid,The submitted bid met the qualification requirements in order to be evaluated.
+disqualified,Disqualified,The submitted bid did not meet the qualification requirements in order to be evaluated.
+withdrawn,Withdrawn,The submitted bid was withdrawn by the tenderer(s).
diff --git a/en/extensions/bids/v1.1.5/codelists/index.html b/en/extensions/bids/v1.1.5/codelists/index.html
new file mode 100644
index 000000000..b593bcb43
--- /dev/null
+++ b/en/extensions/bids/v1.1.5/codelists/index.html
@@ -0,0 +1,631 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Bid statistics and details +
+ ++ Allowing bid statistics, and detailed bid information to be represented. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ bids
+
+ |
+ + Bids + | +
+ The bid section is used to publish summary statistics, and where applicable, individual bid information. + + |
+ + Bids object + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedBid
+
+ |
+ + Related bid + | +
+ Where bid details are used, a cross reference to the entry in the bids array to which this award relates. Provide the bid identifier here. + + |
+ + string + | +
+ BidsStatistic +
+ +
+ The extension defines a new BidsStatistic object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ An internal identifier for this statistical item. + + |
+ + string + | +
+
+ measure
+
+ |
+ + Measure + | +
+ An item from the bidStatistics codelist for the statistic reported in value. This is an open codelist, and other statistics may also be included. + + |
+ + string from open bidStatistics codelist + | +
+
+ date
+
+ |
+ + Date + | +
+ The date when this statistic was last updated. This is often the closing date of the tender process. This field can be left blank unless either (a) the same statistic is provided from multiple points in time, or (b) there is a specific local requirement for the date when statistics were calculated to be provided. + + |
+ + string + | +
+
+ value
+
+ |
+ + Value + | +
+ The value for the measure in question. Total counts should be provided as an integer. Percentages should be presented as a proportion of 1 (e.g. 10% = 0.1) + + |
+ + number + | +
+
+ notes
+
+ |
+ + Notes + | +
+ Any notes required to understand or interpret the given statistic. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Related Lot + | +
+ Where lots are in use, if this statistic relates to bids on a particular lot, provide the lot identifier here. If left blank, the statistic will be interpreted as applying to the whole tender. + + |
+ + string + | +
+ Bids +
+ +
+ The extension defines a new Bids object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statistics
+
+ |
+ + Statistics + | +
+ Summary statistics on the number and nature of bids received. Where information is provided on individual bids, these statistics should match those that can be calculated from the bid details array. + + |
+ + array of BidsStatistic objects + | +
+
+ details
+
+ |
+ + Bid details + | +
+ An array of bids, providing information on the bidders, and where applicable, bid status, bid values and related documents. The extent to which this information can be disclosed varies from jurisdiction to jurisdiction. + + |
+ + array of Bid objects + | +
+ Bid +
+ +
+ The extension defines a new Bid object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ A local identifier for this bid + + |
+ + string + | +
+
+ date
+
+ |
+ + Date + | +
+ The date when this bid was received. + + |
+ + string + | +
+
+ status
+
+ |
+ + Status + | +
+ The status of the bid, drawn from the bidStatus codelist + + |
+ + string from closed bidStatus codelist + | +
+
+ tenderers
+
+ |
+ + Tenderer + | +
+ The party, or parties, responsible for this bid. This should provide a name and identifier, cross-referenced to an entry in the parties array at the top level of the release. + + |
+ + array of OrganizationReference objects + | +
+
+ value
+
+ |
+ + Value + | +
+ The total value of the bid. + + |
+ + Value object + | +
+
+ documents
+
+ |
+ + Documents + | +
+ All documents and attachments related to the bid and its evaluation. + + |
+ + array of Document objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/bids/v1.1.5/extension.json b/en/extensions/bids/v1.1.5/extension.json
new file mode 100644
index 000000000..b57fc1497
--- /dev/null
+++ b/en/extensions/bids/v1.1.5/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Bid statistics and details",
+ "es": "Estad\u00edsticas y detalles de las ofertas"
+ },
+ "description": {
+ "en": "Allowing bid statistics, and detailed bid information to be represented.",
+ "es": "Permite que se muestren las estad\u00edsticas de ofertas y la informaci\u00f3n detallada de las ofertas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/bids/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "bidStatistics.csv",
+ "bidStatus.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/bids/v1.1.5/index.html b/en/extensions/bids/v1.1.5/index.html
new file mode 100644
index 000000000..c12288f19
--- /dev/null
+++ b/en/extensions/bids/v1.1.5/index.html
@@ -0,0 +1,437 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Bid statistics and details +
+ ++ Allowing bid statistics, and detailed bid information to be represented. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ bidStatistics.csv +
+ +
+ You can download the bidStatistics.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ requests
+
+ |
+ + Requests to participate + | +
+ The total number of unique requests to participate received + +
|
+
+
+ bids
+
+ |
+ + Bids + | +
+ The total number of unique bids received (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ validBids
+
+ |
+ + Valid bids + | +
+ The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids are considered during the tender evaluation stage. + +
|
+
+
+ lowestValidBidValue
+
+ |
+ + Lowest valid bid value + | +
+ The value of the lowest valid bid. + +
|
+
+
+ highestValidBidValue
+
+ |
+ + Highest valid bid value + | +
+ The value of the highest valid bid. + +
|
+
+
+ bidders
+
+ |
+ + Bidders + | +
+ The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ qualifiedBidders
+
+ |
+ + Qualified bidders + | +
+ The total number of unique organizations or consortia passing the qualification stage of the evaluation process. + +
|
+
+
+ disqualifiedBidders
+
+ |
+ + Disqualified bidders + | +
+ The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process. + +
|
+
+
+ electronicBids
+
+ |
+ + Electronic bids + | +
+ The number of bids received by electronic means. + +
|
+
+
+ smeBids
+
+ |
+ + Bids from SMEs + | +
+ The number of bids received from small and medium-sized enterprises. + +
|
+
+
+ foreignBids
+
+ |
+ + Bids from foreign firms + | +
+ The number of bids received from bidders from outside the country where the tender is issued. + +
|
+
+
+ foreignBidsFromEU
+
+ |
+ + Bids from firms in other European Economic Area countries + | +
+ The number of bids received from tenderers from other European Economic Area countries. + +
|
+
+
+ foreignBidsFromNonEU
+
+ |
+ + Bids from firms in non-European Economic Area countries + | +
+ The number of bids received from tenderers from non-European Economic Area countries. + +
|
+
+
+ tendersAbnormallyLow
+
+ |
+ + Tenders excluded because they were abnormally low + | +
+ The number of tenders excluded because they were abnormally low. Note that in some EU datasets this might have been converted from a boolean, such that a value of 1 would indicate "1 or more" tenders were excluded. Users need to evaluate and interpret data accordingly. + +
|
+
+ bidStatus.csv +
+ +
+ You can download the bidStatus.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ invited
+
+ |
+ + Invited + | +
+ A bid has been invited from the listed tenderer(s). + + |
+
+
+ pending
+
+ |
+ + Pending + | +
+ A bid has been submitted but not yet evaluated. + + |
+
+
+ valid
+
+ |
+ + Valid + | +
+ The submitted bid met the qualification requirements in order to be evaluated. + + |
+
+
+ disqualified
+
+ |
+ + Disqualified + | +
+ The submitted bid did not meet the qualification requirements in order to be evaluated. + + |
+
+
+ withdrawn
+
+ |
+ + Withdrawn + | +
+ The submitted bid was withdrawn by the tenderer(s). + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/bids/v1.1.5/release-schema.json b/en/extensions/bids/v1.1.5/release-schema.json
new file mode 100644
index 000000000..48fbd1ae0
--- /dev/null
+++ b/en/extensions/bids/v1.1.5/release-schema.json
@@ -0,0 +1,481 @@
+{
+ "properties": {
+ "bids": {
+ "title": "Bids",
+ "description": "The bid section is used to publish summary statistics, and where applicable, individual bid information.",
+ "$ref": "#/definitions/Bids"
+ }
+ },
+ "definitions": {
+ "Award": {
+ "properties": {
+ "relatedBid": {
+ "title": "Related bid",
+ "description": "Where bid details are used, a cross reference to the entry in the bids array to which this award relates. Provide the bid identifier here.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "BidsStatistic": {
+ "title": "Bid Statistic",
+ "description": "For reporting aggregate statistics about the bids related to a tender. Where lots are in use, statistics can be broken down by lot.",
+ "type": "object",
+ "required": [
+ "id",
+ "measure",
+ "value"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "An internal identifier for this statistic.",
+ "type": "string"
+ },
+ "measure": {
+ "title": "Measure",
+ "description": "The statistic reported in the value.",
+ "type": "string",
+ "codelist": "bidStatistics.csv",
+ "openCodelist": true
+ },
+ "date": {
+ "title": "Date",
+ "description": "The date when this statistic was last updated. This is often the closing date of the tender process. This field may be omitted unless either (a) the same statistic is provided from multiple points in time, or (b) there is a specific local requirement for the date when statistics were calculated to be provided.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "value": {
+ "title": "Value",
+ "description": "The value for the measure in question. Total counts should be provided as an integer. Percentages should be provided as a proportion of 1 (e.g. 10% = 0.1)",
+ "type": "number"
+ },
+ "currency": {
+ "title": "Currency",
+ "description": "The currency of the amount in the `value` field, if the statistic has a monetary value.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "currency.csv",
+ "openCodelist": false,
+ "enum": [
+ "ADP",
+ "AED",
+ "AFA",
+ "AFN",
+ "ALK",
+ "ALL",
+ "AMD",
+ "ANG",
+ "AOA",
+ "AOK",
+ "AON",
+ "AOR",
+ "ARA",
+ "ARP",
+ "ARS",
+ "ARY",
+ "ATS",
+ "AUD",
+ "AWG",
+ "AYM",
+ "AZM",
+ "AZN",
+ "BAD",
+ "BAM",
+ "BBD",
+ "BDT",
+ "BEC",
+ "BEF",
+ "BEL",
+ "BGJ",
+ "BGK",
+ "BGL",
+ "BGN",
+ "BHD",
+ "BIF",
+ "BMD",
+ "BND",
+ "BOB",
+ "BOP",
+ "BOV",
+ "BRB",
+ "BRC",
+ "BRE",
+ "BRL",
+ "BRN",
+ "BRR",
+ "BSD",
+ "BTN",
+ "BUK",
+ "BWP",
+ "BYB",
+ "BYN",
+ "BYR",
+ "BZD",
+ "CAD",
+ "CDF",
+ "CHC",
+ "CHE",
+ "CHF",
+ "CHW",
+ "CLF",
+ "CLP",
+ "CNY",
+ "COP",
+ "COU",
+ "CRC",
+ "CSD",
+ "CSJ",
+ "CSK",
+ "CUC",
+ "CUP",
+ "CVE",
+ "CYP",
+ "CZK",
+ "DDM",
+ "DEM",
+ "DJF",
+ "DKK",
+ "DOP",
+ "DZD",
+ "ECS",
+ "ECV",
+ "EEK",
+ "EGP",
+ "ERN",
+ "ESA",
+ "ESB",
+ "ESP",
+ "ETB",
+ "EUR",
+ "FIM",
+ "FJD",
+ "FKP",
+ "FRF",
+ "GBP",
+ "GEK",
+ "GEL",
+ "GHC",
+ "GHP",
+ "GHS",
+ "GIP",
+ "GMD",
+ "GNE",
+ "GNF",
+ "GNS",
+ "GQE",
+ "GRD",
+ "GTQ",
+ "GWE",
+ "GWP",
+ "GYD",
+ "HKD",
+ "HNL",
+ "HRD",
+ "HRK",
+ "HTG",
+ "HUF",
+ "IDR",
+ "IEP",
+ "ILP",
+ "ILR",
+ "ILS",
+ "INR",
+ "IQD",
+ "IRR",
+ "ISJ",
+ "ISK",
+ "ITL",
+ "JMD",
+ "JOD",
+ "JPY",
+ "KES",
+ "KGS",
+ "KHR",
+ "KMF",
+ "KPW",
+ "KRW",
+ "KWD",
+ "KYD",
+ "KZT",
+ "LAJ",
+ "LAK",
+ "LBP",
+ "LKR",
+ "LRD",
+ "LSL",
+ "LSM",
+ "LTL",
+ "LTT",
+ "LUC",
+ "LUF",
+ "LUL",
+ "LVL",
+ "LVR",
+ "LYD",
+ "MAD",
+ "MDL",
+ "MGA",
+ "MGF",
+ "MKD",
+ "MLF",
+ "MMK",
+ "MNT",
+ "MOP",
+ "MRO",
+ "MRU",
+ "MTL",
+ "MTP",
+ "MUR",
+ "MVQ",
+ "MVR",
+ "MWK",
+ "MXN",
+ "MXP",
+ "MXV",
+ "MYR",
+ "MZE",
+ "MZM",
+ "MZN",
+ "NAD",
+ "NGN",
+ "NIC",
+ "NIO",
+ "NLG",
+ "NOK",
+ "NPR",
+ "NZD",
+ "OMR",
+ "PAB",
+ "PEH",
+ "PEI",
+ "PEN",
+ "PES",
+ "PGK",
+ "PHP",
+ "PKR",
+ "PLN",
+ "PLZ",
+ "PTE",
+ "PYG",
+ "QAR",
+ "RHD",
+ "ROK",
+ "ROL",
+ "RON",
+ "RSD",
+ "RUB",
+ "RUR",
+ "RWF",
+ "SAR",
+ "SBD",
+ "SCR",
+ "SDD",
+ "SDG",
+ "SDP",
+ "SEK",
+ "SGD",
+ "SHP",
+ "SIT",
+ "SKK",
+ "SLL",
+ "SOS",
+ "SRD",
+ "SRG",
+ "SSP",
+ "STD",
+ "STN",
+ "SUR",
+ "SVC",
+ "SYP",
+ "SZL",
+ "THB",
+ "TJR",
+ "TJS",
+ "TMM",
+ "TMT",
+ "TND",
+ "TOP",
+ "TPE",
+ "TRL",
+ "TRY",
+ "TTD",
+ "TWD",
+ "TZS",
+ "UAH",
+ "UAK",
+ "UGS",
+ "UGW",
+ "UGX",
+ "USD",
+ "USN",
+ "USS",
+ "UYI",
+ "UYN",
+ "UYP",
+ "UYU",
+ "UYW",
+ "UZS",
+ "VEB",
+ "VEF",
+ "VES",
+ "VNC",
+ "VND",
+ "VUV",
+ "WST",
+ "XAF",
+ "XAG",
+ "XAU",
+ "XBA",
+ "XBB",
+ "XBC",
+ "XBD",
+ "XCD",
+ "XDR",
+ "XEU",
+ "XFO",
+ "XFU",
+ "XOF",
+ "XPD",
+ "XPF",
+ "XPT",
+ "XRE",
+ "XSU",
+ "XTS",
+ "XUA",
+ "XXX",
+ "YDD",
+ "YER",
+ "YUD",
+ "YUM",
+ "YUN",
+ "ZAL",
+ "ZAR",
+ "ZMK",
+ "ZMW",
+ "ZRN",
+ "ZRZ",
+ "ZWC",
+ "ZWD",
+ "ZWL",
+ "ZWN",
+ "ZWR",
+ null
+ ]
+ },
+ "notes": {
+ "title": "Notes",
+ "description": "Any notes needed to understand or interpret the given statistic.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Related Lot",
+ "description": "Where lots are in use, if this statistic relates to bids on a particular lot, provide the lot identifier here. If left blank, the statistic will be interpreted as applying to the whole tender.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Bids": {
+ "title": "Bids",
+ "description": "Summary and detailed information about bids received and evaluated as part of this contracting process.",
+ "type": "object",
+ "properties": {
+ "statistics": {
+ "title": "Statistics",
+ "description": "Summary statistics on the number and nature of bids received. Where information is provided on individual bids, these statistics should match those that can be calculated from the bid details array.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/BidsStatistic"
+ }
+ },
+ "details": {
+ "title": "Bid details",
+ "description": "An array of bids, providing information on the bidders, and where applicable, bid status, bid values and related documents. The extent to which this information can be disclosed varies from jurisdiction to jurisdiction.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Bid"
+ }
+ }
+ }
+ },
+ "Bid": {
+ "title": "Bid",
+ "description": "For representing a bid in response to the tender or qualification stage in this contracting process.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "A local identifier for this bid",
+ "type": [
+ "string"
+ ]
+ },
+ "date": {
+ "title": "Date",
+ "description": "The date when this bid was received.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "status": {
+ "title": "Status",
+ "description": "The status of the bid.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "bidStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "invited",
+ "pending",
+ "valid",
+ "disqualified",
+ "withdrawn",
+ null
+ ]
+ },
+ "tenderers": {
+ "title": "Tenderer",
+ "description": "The party, or parties, responsible for this bid.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "value": {
+ "title": "Value",
+ "description": "The total value of the bid.",
+ "$ref": "#/definitions/Value"
+ },
+ "documents": {
+ "title": "Documents",
+ "description": "All documents and attachments related to the bid and its evaluation.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Document"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/bids/v1.1.5/schema/index.html b/en/extensions/bids/v1.1.5/schema/index.html
new file mode 100644
index 000000000..e875a7c7b
--- /dev/null
+++ b/en/extensions/bids/v1.1.5/schema/index.html
@@ -0,0 +1,653 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Bid statistics and details +
+ ++ Allowing bid statistics, and detailed bid information to be represented. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Information on bids submitted as part of a contracting process is important for many forms of analysis, including:
+-
+
- Market analysis for understanding the competitiveness of a given marketplace; +
- Red flag analysis for understanding potential corruption risks; and +
- Value for money analysis; +
Regulatory regimes vary on the extent to which they allow information on bidding to be proactively published, and at what point in the procurement process. In some systems and processes, a list of invited bidders is published at the start of tendering, and full details and documents on the bids received are disclosed when evaluation is complete. In other systems, only summary statistics on the number of bids received is made public.
+The OCDS bid extension introduces a new, flexible, top-level section to each contracting process to capture bidding information. Implementers will need to assess which fields are applicable to their local regulatory regime, and to local use-cases.
+Schema
+The bids.details array is used to provide one or more Bid objects, each representing a unique bid received.
The bids.statistics array is used to represent key statistical information about the number of bids and bidders. Each entry in the array is a BidsStatistic object containing at least:
-
+
- An identifier +
- A measure, from the
bidStatistics.csvcodelist
+ - A value for that measure +
The bidStatistics.csv codelist is an open codelist. Publishers can add their own codes to this list. When doing so, publishers are encouraged to engage with the open contracting community to agree upon definitions of each code.
For example, publishers may wish to add statistics on minority or women-owned businesses, or bids that meet certain environmental standards and targets.
+The codelist's Category column indicates whether the statistic applies to bids or bidders or whether it is specified or required by a particular regulatory context (e.g. EU).
+Example
+Below is an example of a bids extension:
+{
+ "bids": {
+ "statistics": [
+ {
+ "id": "1",
+ "measure": "validBids",
+ "value": 1,
+ "date": "2016-12-09T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were considered valid against relevant criteria."
+ },
+ {
+ "id": "2",
+ "measure": "disqualifiedBids",
+ "value": 1,
+ "date": "2016-12-10T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were disqualified."
+ },
+ {
+ "id": "3",
+ "measure": "highestValidBidValue",
+ "value": 1000,
+ "currency": "USD"
+ },
+ {
+ "id": "4",
+ "measure": "lowestValidBidValue",
+ "value": 1000,
+ "currency": "USD"
+ }
+ ],
+ "details": [
+ {
+ "id": "1",
+ "date": "2016-12-09T01:00:00+01:00",
+ "status": "valid",
+ "value": {
+ "amount": 1000,
+ "currency": "USD"
+ },
+ "documents": [
+ {
+ "id": "1",
+ "documentType": "evaluationReports",
+ "title": "Mega Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Mega Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_megaConsortium.pdf",
+ "datePublished": "2016-11-17T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en"
+ }
+ ],
+ "tenderers": [
+ {
+ "id": "MEGA",
+ "name": "Mega Consortium"
+ }
+ ]
+ },
+ {
+ "id": "2",
+ "date": "2016-12-10T01:00:00+01:00",
+ "status": "disqualified",
+ "value": {
+ "amount": 1500,
+ "currency": "USD"
+ },
+ "documents": [
+ {
+ "id": "1",
+ "documentType": "evaluationReports",
+ "title": "Beta Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Beta Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_betaConsortium.pdf",
+ "datePublished": "2016-11-18T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en"
+ }
+ ],
+ "tenderers": [
+ {
+ "id": "BETA",
+ "name": "Beta Consortium"
+ }
+ ]
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "111",
+ "title": "Example PPP contract award",
+ "description": "Award of Example PPP contract to Mega Consortium",
+ "status": "active",
+ "date": "2016-12-17T10:00:00-06:00",
+ "relatedBid": "1"
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.5
+-
+
- Add
BidsStatistic.currencyfield
+ - Add 'lowestValidBidValue' and 'highestValidBidValue' codes to
bidStatistics.csv
+ - Remove type information from field descriptions +
- Review normative and non-normative words +
v1.1.4
+-
+
- Fix the title and description of the 'foreignBidsFromEU' code to refer to the European Economic Area (EEA). Previously, its title referred to the European Single Market, but its description listed the members of the EEA. +
- Add a 'foreignBidsFromNonEU' code to
bidStatistics.csv
+ - Remove invalid
requiredproperty on array fieldBids.details
+ - Fix the merge behavior of
Bids.statisticsandBid.tenderersto use identifier merge strategy
+ - Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow required fields
BidsStatistic.id,BidsStatistic.measure,BidsStatistic.valuefrom being null
+ - Disallow
Bids.statisticsfrom having null in its array of objects
+ - Allow
Bids.statisticsto be null
+ - Add enum to
Bid.status
+ - Move
BidsStatistic.requirementResponsesto requirements extension
+ - Add descriptions to bidStatus.csv +
- List codelists in extension.json +
- Add example to documentation +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/budget/index.html b/en/extensions/budget/index.html
new file mode 100644
index 000000000..03f457ed6
--- /dev/null
+++ b/en/extensions/budget/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Bid statistics and details +
+ ++ Allowing bid statistics, and detailed bid information to be represented. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ bids
+
+ |
+ + Bids + | +
+ The bid section is used to publish summary statistics, and where applicable, individual bid information. + + |
+ + Bids object + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedBid
+
+ |
+ + Related bid + | +
+ Where bid details are used, a cross reference to the entry in the bids array to which this award relates. Provide the bid identifier here. + + |
+ + string + | +
+ BidsStatistic +
+ +
+ The extension defines a new BidsStatistic object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ An internal identifier for this statistic. + + |
+ + string + | +
+
+ measure
+
+ |
+ + Measure + | +
+ The statistic reported in the value. + + |
+ + string from open bidStatistics codelist + | +
+
+ date
+
+ |
+ + Date + | +
+ The date when this statistic was last updated. This is often the closing date of the tender process. This field may be omitted unless either (a) the same statistic is provided from multiple points in time, or (b) there is a specific local requirement for the date when statistics were calculated to be provided. + + |
+ + string + | +
+
+ value
+
+ |
+ + Value + | +
+ The value for the measure in question. Total counts should be provided as an integer. Percentages should be provided as a proportion of 1 (e.g. 10% = 0.1) + + |
+ + number + | +
+
+ currency
+
+ |
+ + Currency + | +
+ The currency of the amount in the |
+ + string from closed currency codelist + | +
+
+ notes
+
+ |
+ + Notes + | +
+ Any notes needed to understand or interpret the given statistic. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Related Lot + | +
+ Where lots are in use, if this statistic relates to bids on a particular lot, provide the lot identifier here. If left blank, the statistic will be interpreted as applying to the whole tender. + + |
+ + string + | +
+ Bids +
+ +
+ The extension defines a new Bids object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statistics
+
+ |
+ + Statistics + | +
+ Summary statistics on the number and nature of bids received. Where information is provided on individual bids, these statistics should match those that can be calculated from the bid details array. + + |
+ + array of BidsStatistic objects + | +
+
+ details
+
+ |
+ + Bid details + | +
+ An array of bids, providing information on the bidders, and where applicable, bid status, bid values and related documents. The extent to which this information can be disclosed varies from jurisdiction to jurisdiction. + + |
+ + array of Bid objects + | +
+ Bid +
+ +
+ The extension defines a new Bid object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ A local identifier for this bid + + |
+ + string + | +
+
+ date
+
+ |
+ + Date + | +
+ The date when this bid was received. + + |
+ + string + | +
+
+ status
+
+ |
+ + Status + | +
+ The status of the bid. + + |
+ + string from closed bidStatus codelist + | +
+
+ tenderers
+
+ |
+ + Tenderer + | +
+ The party, or parties, responsible for this bid. + + |
+ + array of OrganizationReference objects + | +
+
+ value
+
+ |
+ + Value + | +
+ The total value of the bid. + + |
+ + Value object + | +
+
+ documents
+
+ |
+ + Documents + | +
+ All documents and attachments related to the bid and its evaluation. + + |
+ + array of Document objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/budget/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/budget/master/extension.json b/en/extensions/budget/master/extension.json
new file mode 100644
index 000000000..742a26c06
--- /dev/null
+++ b/en/extensions/budget/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Budget Breakdown",
+ "es": "Desglose del presupuesto"
+ },
+ "description": {
+ "en": "Adds a budget breakdown array to the budget object to break down a budget by source and period.",
+ "es": "Agrega una lista de desglose de presupuesto al objeto de presupuesto para desglosar un presupuesto por fuente y per\u00edodo."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/budget/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "+partyRole.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/budget/master/index.html b/en/extensions/budget/master/index.html
new file mode 100644
index 000000000..21aaf4128
--- /dev/null
+++ b/en/extensions/budget/master/index.html
@@ -0,0 +1,411 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Budget Breakdown +
+ ++ Adds a budget breakdown array to the budget object to break down a budget by source and period. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ sourceParty
+
+ |
+ + Source organization + | +
+ The organization providing the funds for a budget entry. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/budget/master/release-schema.json b/en/extensions/budget/master/release-schema.json
new file mode 100644
index 000000000..43e1ae53d
--- /dev/null
+++ b/en/extensions/budget/master/release-schema.json
@@ -0,0 +1,75 @@
+{
+ "definitions": {
+ "BudgetBreakdown": {
+ "title": "Detailed budget breakdown",
+ "description": "This section allows a detailed budget breakdown to be expressed, covering multiple budget sources and multiple periods",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "An identifier for this particular budget entry.",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "A short free text description of this budget entry.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "amount": {
+ "title": "Amount",
+ "description": "The value of the budget line item. A positive amount means the source organization funds the contracting process. A negative amount means the contracting process pays the source organization.",
+ "$ref": "#/definitions/Value"
+ },
+ "uri": {
+ "title": "Linked budget information",
+ "description": "A URI pointing directly to a machine-readable information about this budget entry.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "period": {
+ "title": "Budget period",
+ "description": "The period covered by this budget entry.",
+ "$ref": "#/definitions/Period"
+ },
+ "sourceParty": {
+ "title": "Source organization",
+ "description": "The organization providing the funds for this budget entry. The corresponding entry in the `parties` array must have 'sourceParty' in its `roles` array.",
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "budget",
+ "version": "master"
+ }
+ },
+ "Budget": {
+ "properties": {
+ "budgetBreakdown": {
+ "title": "Budget breakdown",
+ "description": "A detailed breakdown of the budget by period and/or participating funders.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/BudgetBreakdown"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/budget/master/schema/index.html b/en/extensions/budget/master/schema/index.html
new file mode 100644
index 000000000..480e1c02d
--- /dev/null
+++ b/en/extensions/budget/master/schema/index.html
@@ -0,0 +1,372 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Budget Breakdown +
+ ++ Adds a budget breakdown array to the budget object to break down a budget by source and period. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+OCDS' planning.budget object can be used to describe the budget from which funds are drawn. It includes a single budget.amount field to capture the total value of the budget for the contracting process.
This extension provides a way to describe the budget in greater detail, including multi-year budgets or budgets sourced from multiple organizations. In the case of PPPs, budgets may be sourced from the private sector or from multi-lateral development banks.
+Disclosing structured data on multi-source budgets allows users to understand how much of the funds for a project come from government or from a specific department, whilst structured data on multi-year budgets allows users to understand the expected spend profile of a contract.
+Guidance
+In the core planning.budget block, budget.amount should be used to capture the total value of the budget for the contracting process.
Where budget.budgetBreakdown is used to express a multi-source budget but the organization details are not known for one or more parts of the budget, for example in a PPP where part of the budget will be provided by the successful private sector bidder, the sourceParty.name field should be used to provide a free text explanation of the source of the budget, e.g. "Private sector investment from successful bidder".
Examples
+Multi-source budgets
+The following JSON snippet models a single year multi-source budget:
+{
+ "planning": {
+ "budget": {
+ "amount": {
+ "amount": 300000,
+ "currency": "GBP"
+ },
+ "budgetBreakdown": [
+ {
+ "id": "1",
+ "description": "Budget contribution from the local government",
+ "sourceParty": {
+ "id": "GB-LAC-E09000003-557",
+ "name": "London Borough of Barnet - Transport Services"
+ },
+ "amount": {
+ "amount": 150000,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "2",
+ "description": "Budget contribution from the national government",
+ "sourceParty": {
+ "id": "GB-GOV-23",
+ "name": "Department for Transport"
+ },
+ "amount": {
+ "amount": 150000,
+ "currency": "GBP"
+ }
+ }
+ ]
+ }
+ },
+ "parties": [
+ {
+ "id": "GB-GOV-23",
+ "name": "Department for Transport",
+ "roles": [
+ "funder"
+ ]
+ },
+ {
+ "id": "GB-LAC-E09000003-557",
+ "name": "London Borough of Barnet - Transport Services",
+ "roles": [
+ "funder"
+ ]
+ }
+ ]
+}
+Multi-year budgets
+The following JSON snippet models a multi-year single source budget:
+{
+ "planning": {
+ "budget": {
+ "amount": {
+ "amount": 70000,
+ "currency": "GBP"
+ },
+ "budgetBreakdown": [
+ {
+ "id": "1",
+ "description": "2021/2022",
+ "period": {
+ "startDate": "2021-04-01T00:00:00Z",
+ "endDate": "2022-03-31T23:59:59Z"
+ },
+ "amount": {
+ "amount": 20000,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "2",
+ "description": "2022/2023",
+ "period": {
+ "startDate": "2022-04-01T00:00:00Z",
+ "endDate": "2023-03-31T23:59:59Z"
+ },
+ "amount": {
+ "amount": 50000,
+ "currency": "GBP"
+ }
+ }
+ ]
+ }
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-06-07
+-
+
- Add 'sourceParty' code to the
+partyRole.csvcodelist, because the 'funder' code is deprecated in OCDS 1.2.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2019-03-20
+-
+
- Set
"uniqueItems": trueon array fields, and add"minLength": 1on required string fields.
+
2019-01-30
+-
+
- Remove obsolete
mergeStrategyproperties
+
2018-05-08
+-
+
- Make
BudgetBreakdown.idrequired and non-nullable to support revision tracking and list merging
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/budget_and_spend/index.html b/en/extensions/budget_and_spend/index.html
new file mode 100644
index 000000000..eb6dac0a9
--- /dev/null
+++ b/en/extensions/budget_and_spend/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Budget Breakdown +
+ ++ Adds a budget breakdown array to the budget object to break down a budget by source and period. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ BudgetBreakdown +
+ +
+ The extension defines a new BudgetBreakdown object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ An identifier for this particular budget entry. + + |
+ + string or integer + | +
+
+ description
+
+ |
+ + Description + | +
+ A short free text description of this budget entry. + + |
+ + string + | +
+
+ amount
+
+ |
+ + Amount + | +
+ The value of the budget line item. A positive amount means the source organization funds the contracting process. A negative amount means the contracting process pays the source organization. + + |
+ + Value object + | +
+
+ uri
+
+ |
+ + Linked budget information + | +
+ A URI pointing directly to a machine-readable information about this budget entry. + + |
+ + string + | +
+
+ period
+
+ |
+ + Budget period + | +
+ The period covered by this budget entry. + + |
+ + Period object + | +
+
+ sourceParty
+
+ |
+ + Source organization + | +
+ The organization providing the funds for this budget entry. The corresponding entry in the |
+ + OrganizationReference object + | +
+ Budget +
+ +
+ The extension defines these fields in the Budget object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ budgetBreakdown
+
+ |
+ + Budget breakdown + | +
+ A detailed breakdown of the budget by period and/or participating funders. + + |
+ + array of BudgetBreakdown objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/budget_and_spend/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/budget_and_spend/master/release-schema.json b/en/extensions/budget_and_spend/master/release-schema.json
new file mode 100644
index 000000000..934d6aed6
--- /dev/null
+++ b/en/extensions/budget_and_spend/master/release-schema.json
@@ -0,0 +1,155 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "financialProgress": {
+ "title": "Financial progress",
+ "description": "The financial progress section allows high-level and detailed information on amounts committed or spent to date for this particular contract. This may be used alongside the transactions section, which allows for details of each individual payment to be recorded.",
+ "type": "object",
+ "properties": {
+ "totalSpend": {
+ "title": "Total spend",
+ "description": "The total spend on this contract at the date of last update. Note that the exact fiscal measure this number represents may vary between data publishers (e.g. amount invoiced vs. amount transferred to the bank account of the supplier).",
+ "$ref": "#/definitions/Value"
+ },
+ "measures": {
+ "title": "Measures",
+ "description": "This measures section reports aggregated financial progress figures for this contract (i.e. without breakdown by budget classifications). Measures must be provided as a set of key-value pairs, where the key should be the name of the measure used within a related Fiscal Data Package dataset or other budget and spending dataset. The value is the value of this measure when last updated, and must be provided as a number in the same default currency as any aggregate reported budget or spending figures.",
+ "type": "object",
+ "patternProperties": {
+ "[A-Za-z0-9._-]": {
+ "type": [
+ "number",
+ "null"
+ ]
+ }
+ },
+ "minProperties": 1
+ },
+ "breakdown": {
+ "title": "Financial progress breakdown",
+ "description": "This section contains a breakdown of financial progress, allowing various measures (amount invoiced, amount accrued, amount paid etc.) to be disaggregated by source, period and budget classification",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/FinancialProgressBreakdown"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+ },
+ "FinancialProgressBreakdown": {
+ "title": "Financial progress breakdown",
+ "description": "This section allows a detailed breakdown of financial progress to be provided, each covering a particular periods, or allocating financial progress against particular funding sources and fiscal classifications.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "An identifier for this particular financial progress breakdown entry.",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "A short free text description of this financial progress breakdown. This may be displayed in user interfaces to help users interpret this entry. This may be automatically generated from structured data or may be manually entered.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "period": {
+ "title": "Budget period",
+ "description": "The period covered by this financial progress breakdown entry. This information may also be duplicated using classifications where relevant.",
+ "$ref": "#/definitions/Period"
+ },
+ "classifications": {
+ "title": "Budget classifications",
+ "description": "Budget classifications must be provided as a set of key-value pairs, where the key is a dimension (or the label of a dimension) used in budget classification, and the value is the value of that dimension for this contracting process or specific contract (depending on the point within an OCDS file at which the classification is provided).",
+ "type": "object",
+ "patternProperties": {
+ "[A-Za-z0-9._-]": {
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "measures": {
+ "title": "measures",
+ "description": "Measures must be provided as a set of key-value pairs, where the key should be the name of the measure used within a related Fiscal Data Package dataset or other budget and spending dataset. The value is the value of this measure when last updated, and must be provided as a number in the same default currency as any aggregate reported budget or spending figures.",
+ "type": "object",
+ "patternProperties": {
+ "[A-Za-z0-9._-]": {
+ "type": [
+ "number",
+ "null"
+ ]
+ }
+ },
+ "minProperties": 1
+ },
+ "fiscalBreakdownFieldMapping": {
+ "$ref": "#/definitions/FiscalBreakdownFieldMapping"
+ }
+ },
+ "minProperties": 1
+ },
+ "BudgetBreakdown": {
+ "properties": {
+ "classifications": {
+ "title": "Budget classifications",
+ "description": "Budget classifications must be provided as a set of key-value pairs, where the key is a dimension (or the label of a dimension) used in budget classification, and the value is the value of that dimension for this contracting process or specific contract (depending on the point within an OCDS file at which the classification is provided).",
+ "type": "object",
+ "patternProperties": {
+ "[A-Za-z0-9._-]": {
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "measures": {
+ "title": "measures",
+ "description": "Measures must be provided as a set of key-value pairs, where the key should be the name of the measure used within a related Fiscal Data Package dataset or other budget and spending dataset. The value is the value of this measure when last updated, and must be provided as a number in the same default currency as any aggregate reported budget or spending figures.",
+ "type": "object",
+ "patternProperties": {
+ "[A-Za-z0-9._-]": {
+ "type": [
+ "number",
+ "null"
+ ]
+ }
+ },
+ "minProperties": 1
+ },
+ "fiscalBreakdownFieldMapping": {
+ "$ref": "#/definitions/FiscalBreakdownFieldMapping"
+ }
+ }
+ },
+ "FiscalBreakdownFieldMapping": {
+ "title": "Fiscal Breakdown Field Mapping",
+ "description": "OCDS defers to the Fiscal Data Package to provide detailed definitions of budget classifications and measures, including providing labels for each property and describing the relationship between each classification or measure and established fiscal concepts. A Fiscal Data Package may also contain budget and spend data, using the same classifications and measures as the OCDS file, and thereby allowing comparison between 'contract level' budget allocations and spend, and allocations and spending at the level of a particular budget line. When used, the fiscalBreakdownFieldMapping field must contain a dereferenceable URI pointing to a [Fiscal Data Package (FDP)](https://frictionlessdata.io/specs/fiscal-data-package/) datapackage.json file (version 1.0 or above), or a file that, when decompressed, contains a datapackage.json file. The URI should include a fragment identifier with the `name` value of a particular resource within that file in order to identify the particular budget or spending data file to which contract level budget allocations and spending measures can be compared, and the particular column definitions to use. The referenced resource should contain `field` or `extraField` properties with their `name` property matching each of the budget/financial progress breakdown `classification` or `measure` fields in the OCDS data, and at minimum providing labels for these.",
+ "type": "string",
+ "format": "uri"
+ }
+ }
+}
diff --git a/en/extensions/budget_and_spend/master/schema/index.html b/en/extensions/budget_and_spend/master/schema/index.html
new file mode 100644
index 000000000..c5026fb37
--- /dev/null
+++ b/en/extensions/budget_and_spend/master/schema/index.html
@@ -0,0 +1,581 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Budget and spending classification +
+ ++ Extends budget breakdown and contract implementation to allow publication of detailed budget allocations and execution for a contracting process, using classifications that can be mapped to separately published budget and spend data. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The Budgets and Spend extension extends budget breakdown and the contract implementation section to allow the publication of detailed budget allocations and execution for a contracting process.
+A discussion paper providing background approach taken is available here.
+This repository is under active development, and currently contains a worked example of how this extension can be used to record yearly financial commitments to a contracting process and individual contracts.
+In summary
+This extension introduces three new features that build on the budget breakdown extension:
+-
+
classifications- allowing functional, economic and administrative classifications to be provided for each budget breakdown item;
+measures- allowing different budget measures (planned, committed, executed etc.) to be expressed at the contracting process level for each set of budget classifications;
+fiscalBreakdownFieldMapping- providing an approach to link to a Fiscal Data Package datapackage.json file that defines the meaning of each classification and measure, and that provides access to related budget-level data.
+
In addition, it introduces the financialProgress object into contracts.implementation, allowing a detailed breakdown of the financial execution of each contract to be expressed, using the same classifications, measures and fiscalBreakdownFieldMapping features as for budgetBreakdown.
Getting started
+The best way to understand this extension is by looking at worked examples.
+-
+
- The coordination example illustrates how to express data on budget allocation and execution that may be drawn from different data systems (e.g. finance systems and procurement systems). +
- The integration example illustrates how references to a Fiscal Data Package can support display of data to users, and comparison between contracting process level and budget level data. +
- The flat data example illustrates how the structured data published using this extension can be analyzed using spreadsheet tools. +
Key concepts
+This extension provides the tools to create data that links budgets, contracting processes and spending
+Drawing on definitions from the Global Initiative for Fiscal Transparency (GIFT):
+A budget is a forward-looking statements of how an organization proposes to raise revenues, spend resources, and finance its operations. The National Government budget should cover all the activities of a state. Detailed budgets may also exist at the level of agencies and projects. In public contracting, the funding for a contracting process may come from a particular section of the National budget, or from an organizational budget. It may also come wholly or partially from an external funders budget (e.g. an International Development Bank), either directly, or passing through government systems.
+Budget lines are constructed from a set of classifications (often described in terms of Functional, Administrative and Economic classifications), and measures (such as the original amount committed to a particular set of classifications, or the modified, or executed, amounts).
+Fiscal reports are records of [an organization's] actual (historical) revenues, spending and financing. They may report the fiscal activities of the central government, state governments, or local governments, or of all levels of government in a country (referred to as the general government). Reports may cover a whole government in aggregate as an organization, and/or individual government units, e.g. ministries, departments or agencies. They may be on a cash or accruals basis (full or partial). As payments are made during the execution of a contract, these may be allocated against one or more sections of the budget. In some cases, this may allow the creation of fiscal reporting at the level of individual contracts.
+The Open Contracting Data Standard is used to share information about contracting processes. A contracting process may go through a number of stages over time, including planning, tender, award, contract signature and implementation.
+Relating budget, contracting and spend
+
The image above presents a schematic representation of how budget, contracting and spend datasets may interact.
+Note that:
+-
+
- This does not represent a linear sequence of events. Data may become available at different points in time, such as when budgeting takes place on an annual cycle, but contracts are signed to cover multiple years. In such cases, the budget information in the
planningsection of an OCDS contracting process may be updated after contracts are awarded and being implemented.
+ - Budget and spend data may be provided at varying levels of granularity, from a single budget line that funds multiple contracting processes, to the fiscal classification of individual items of spend against a particular contract. Data publishers will vary as to the level of detail that can be extracted reliably from their systems. +
- Budget execution data may exist at the transactional level, or may exist at a more aggregated level. This extension currently covers budget execution, but does not cover detailed classification of transactions. +
The image below shows a mapping between the stages of a transaction and the stages of a contracting process. The stages of a transaction are generally common across different jurisdictions and reflect those described by the Fiscal Data Package; however, some jurisdictions might not record all stages, some might use different terminology, and some might have more stages.
+
The joined-up data covered by this extension is typically sourced from procurement systems and Financial Management Information Systems (FMIS). Examples of how such systems can be integrated include:
+-
+
- Before beginning a tender, the procurement system checks that funds are available for the contracting process through the FMIS, and creates a reservation in the FMIS. +
- When a contract is signed, the procurement system creates a commitment in the FMIS for the value of the contract. +
- When a milestone or deliverable of a contract is completed, the procurement system creates a verification or accrual ("devengado" in Spanish) in the FMIS. +
Joined up data standards: connections with the fiscal data package
+The Fiscal Data Package, developed by Open Knowledge with the support of GIFT, provides "a lightweight and user-oriented format for publishing and consuming fiscal data". Unlike OCDS, which requires data to be converted to a set JSON structure before publication, a Fiscal Data Package consists of:
+-
+
- A data package definition (datapackage.json) which describes the 'logical model' to apply to existing data files. This defines columns, their relationship to fiscal concepts, and how they should be transformed by consuming applications in order to create normalized data. +
- Data files, which provide the 'physical model' for budget or spending dataset, and may be the direct exports from existing systems. +
Considerable research and user-testing has taken place to develop the Fiscal Data Package, establishing that, instead of seeking agreement on some global set of fiscal concepts, it is important, given the diversity of budget and spending systems around the world, to allow publishers to provide data using their existing fiscal concepts, and to then annotate these with additional data that can progressively support comparison and analysis across datasets.
+To avoid duplication of effort by data publishers and consumers, this extension defers to the Fiscal Data Package model with respect to the definition of fiscal concepts, and follows FDP's approach of allowing use of existing data column names. Whilst FDP makes no direct distinction between "classifications" and "measures", considering both to be instances of "fiscal concepts", in this extension we do draw a distinction to allow measures to be validated as numerical, whilst classifications can take string or number values.
+Background
+A full exploration of the approach taken in this extension can be found in the background discussion paper.
+User stories & requirements
+This extension was designed around a set of user stories.
+-
+
- U1: As a journalist I want to see the budget source of a particular contracting process in order to understand whether funding has come from domestic resources, loans or other international revenue +
- U2: As a journalist I want to find all the contracts funded through a particular budget source in order to analyze the extent to which the budget is spent via contracting or other means +
- U3: As a civil society organization focused on infrastructure I want to find all the contracting processes related to a given infrastructure programme or project so that I can carry out a review of compliance with infrastructure project transparency requirements. +
- U4: As a journalist I want to track (suspicious) contracts in order to identify potential connections between the recipients and the officials and politicians in control of the budgeting and award processes. +
Identifying and confirming budget allocations:
+-
+
- U5: As a potential supplier I want to see when budget availability is confirmed for a given contracting process so that I can plan a pipeline of potential bidding opportunities. +
- U6: As a civil society monitoring organization I want to identify projects without confirmed budget so that I can analyze the funding gap for planned procurement +
- U7: As a treasury official I want to share information on the status of budget allocations and spending for any given contract so that I can demonstrate to the public that the budget is being spent in accordance with approved plans +
- U8: As a procurement monitor I want to see how much of the spend on an infrastructure project has come from the capital budget vs the revenue budget so that I can monitor over or underspend +
- U9: As a civil society organization I want to identify how far particular budget lines have spend allocated against them, and the status of that spend over time so that I can report on areas of over or under spending. +
Tracking the payment process:
+-
+
- U10: As an academic I want to identify the gap between invoice date and payment date so that I can analyze how prices are affected by payment timelines +
- U11: As an auditor I want to see full details of the billing and payment process so that I can identify potential red flags and investigate particular processes +
These user stories were used to identify a set of requirements that the extension should meet. The list below outlines the extent to which the current extension meets the requirements that were identified.
+-
+
- R1: Uniquely identify each relevant budget line
+
-
+
- Requirement met?: Yes. BudgetBreakdown is extended with a flexible
classificationsobject that can include any number of classification fields, mirroring the terms and column names used within budget datasets.
+
+ - Requirement met?: Yes. BudgetBreakdown is extended with a flexible
- R2: Uniquely identify the projects providing funding to a contracting process
+
-
+
- Requirement met?: Partially. No changes are currently introduced to meet this use case. The core budget object already includes a
projectIDfield.
+
+ - Requirement met?: Partially. No changes are currently introduced to meet this use case. The core budget object already includes a
- R3: Provide amounts for different budget phases including confirmed budget allocations
+
-
+
- Requirement met?: Yes. BudgetBreakdown is extended with a flexible
measuresobject that can include any number of measure fields, mirroring the terms and column names used within existing budget and spending datasets.
+
+ - Requirement met?: Yes. BudgetBreakdown is extended with a flexible
- R4: Classify transactions against budget lines
+
-
+
- Requirement met?: No. Disaggregated financial progress information can be classified against budget lines in the contract implementation
financialProgress.breakdownsection, but the extension does not currently modify thetransactionsblock to allow classification at the individual transaction level.
+
+ - Requirement met?: No. Disaggregated financial progress information can be classified against budget lines in the contract implementation
- R5: Provide information on the transaction process, from invoice to payment
+
-
+
- Requirement met?: Partial. The
measuresinfinancialProgress.breakdownfor each contract can be used to describe different moments of payment processing. However, this only provides a full history of the timing of payment processes when used with a detailed version history of releases. An alternative approach of adding details oftransactionsto represent different moments such as requests for payment and payment approvals has not been included in this extension, but may be developed separately in future.
+
+ - Requirement met?: Partial. The
- R6: Allow individual amount allocations of budget to contract within OCDS to be checked against overall budget line allocations in a budget dataset
+
-
+
- Requirement met?: Yes. Through use of a link to the Fiscal Data Package it is possible to compare the contract-level financial information in OCDS with similarly classified information in an FDP. +
+ - R7: Provide front end interfaces with the information needed to display budget information to users
+
-
+
- Requirement met?: Yes. When used in conjunction with a Fiscal Data Package, applications can lookup labels and meta-data for each
classificationsandmeasuresin order to display information clearly to users.
+
+ - Requirement met?: Yes. When used in conjunction with a Fiscal Data Package, applications can lookup labels and meta-data for each
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-06-04
+-
+
- Review normative and non-normative words +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2019-03-20
+-
+
- Set
"uniqueItems": trueon array fields, and add"minLength": 1on required string fields.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/charges/index.html b/en/extensions/charges/index.html
new file mode 100644
index 000000000..c150e11a1
--- /dev/null
+++ b/en/extensions/charges/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Budget and spending classification +
+ ++ Extends budget breakdown and contract implementation to allow publication of detailed budget allocations and execution for a contracting process, using classifications that can be mapped to separately published budget and spend data. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ financialProgress
+
+ |
+ + Financial progress + | +
+ The financial progress section allows high-level and detailed information on amounts committed or spent to date for this particular contract. This may be used alongside the transactions section, which allows for details of each individual payment to be recorded. + + |
+ + object + | +
+
+ financialProgress.
+ |
+ + Total spend + | +
+ The total spend on this contract at the date of last update. Note that the exact fiscal measure this number represents may vary between data publishers (e.g. amount invoiced vs. amount transferred to the bank account of the supplier). + + |
+ + Value object + | +
+
+ financialProgress.
+ |
+ + Measures + | +
+ This measures section reports aggregated financial progress figures for this contract (i.e. without breakdown by budget classifications). Measures must be provided as a set of key-value pairs, where the key should be the name of the measure used within a related Fiscal Data Package dataset or other budget and spending dataset. The value is the value of this measure when last updated, and must be provided as a number in the same default currency as any aggregate reported budget or spending figures. + + |
+ + object + | +
+
+ financialProgress.
+ |
+ + + | ++ + | ++ number + | +
+
+ financialProgress.
+ |
+ + Financial progress breakdown + | +
+ This section contains a breakdown of financial progress, allowing various measures (amount invoiced, amount accrued, amount paid etc.) to be disaggregated by source, period and budget classification + + |
+ + array of FinancialProgressBreakdown objects + | +
+ FinancialProgressBreakdown +
+ +
+ The extension defines a new FinancialProgressBreakdown object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ An identifier for this particular financial progress breakdown entry. + + |
+ + string or integer + | +
+
+ description
+
+ |
+ + Description + | +
+ A short free text description of this financial progress breakdown. This may be displayed in user interfaces to help users interpret this entry. This may be automatically generated from structured data or may be manually entered. + + |
+ + string + | +
+
+ period
+
+ |
+ + Budget period + | +
+ The period covered by this financial progress breakdown entry. This information may also be duplicated using classifications where relevant. + + |
+ + Period object + | +
+
+ classifications
+
+ |
+ + Budget classifications + | +
+ Budget classifications must be provided as a set of key-value pairs, where the key is a dimension (or the label of a dimension) used in budget classification, and the value is the value of that dimension for this contracting process or specific contract (depending on the point within an OCDS file at which the classification is provided). + + |
+ + object + | +
+
+ classifications.
+ |
+ + + | ++ + | ++ string or number + | +
+
+ measures
+
+ |
+ + measures + | +
+ Measures must be provided as a set of key-value pairs, where the key should be the name of the measure used within a related Fiscal Data Package dataset or other budget and spending dataset. The value is the value of this measure when last updated, and must be provided as a number in the same default currency as any aggregate reported budget or spending figures. + + |
+ + object + | +
+
+ measures.
+ |
+ + + | ++ + | ++ number + | +
+
+ fiscalBreakdownFieldMapping
+
+ |
+ + + | ++ + | ++ FiscalBreakdownFieldMapping object + | +
+ BudgetBreakdown +
+ +
+ The extension defines these fields in the BudgetBreakdown object from the Budget Breakdown extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ classifications
+
+ |
+ + Budget classifications + | +
+ Budget classifications must be provided as a set of key-value pairs, where the key is a dimension (or the label of a dimension) used in budget classification, and the value is the value of that dimension for this contracting process or specific contract (depending on the point within an OCDS file at which the classification is provided). + + |
+ + object + | +
+
+ classifications.
+ |
+ + + | ++ + | ++ string or number + | +
+
+ measures
+
+ |
+ + measures + | +
+ Measures must be provided as a set of key-value pairs, where the key should be the name of the measure used within a related Fiscal Data Package dataset or other budget and spending dataset. The value is the value of this measure when last updated, and must be provided as a number in the same default currency as any aggregate reported budget or spending figures. + + |
+ + object + | +
+
+ measures.
+ |
+ + + | ++ + | ++ number + | +
+
+ fiscalBreakdownFieldMapping
+
+ |
+ + + | ++ + | ++ FiscalBreakdownFieldMapping object + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/charges/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/charges/master/extension.json b/en/extensions/charges/master/extension.json
new file mode 100644
index 000000000..a72aaab12
--- /dev/null
+++ b/en/extensions/charges/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Charges",
+ "es": "Cargos"
+ },
+ "description": {
+ "en": "Adds a charges array to the implementation object to disclose the charges to be incurred by users or government in a given period of a contract.",
+ "es": "Agrega una matriz de cargos al objeto de implementaci\u00f3n para publicar los cargos en que incurrir\u00e1n los usuarios o el gobierno en un per\u00edodo determinado de un contrato."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/charges/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "chargePaidBy.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/charges/master/index.html b/en/extensions/charges/master/index.html
new file mode 100644
index 000000000..4578e39db
--- /dev/null
+++ b/en/extensions/charges/master/index.html
@@ -0,0 +1,336 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Charges +
+ ++ Adds a charges array to the implementation object to disclose the charges to be incurred by users or government in a given period of a contract. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ chargePaidBy.csv +
+ +
+ You can download the chargePaidBy.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ government
+
+ |
+ + Government + | +
+ The charge is paid by the government + + |
+
+
+ user
+
+ |
+ + User + | +
+ The charge is paid by businesses or citizens using the facilities provided by the contract + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/charges/master/release-schema.json b/en/extensions/charges/master/release-schema.json
new file mode 100644
index 000000000..513ae226e
--- /dev/null
+++ b/en/extensions/charges/master/release-schema.json
@@ -0,0 +1,83 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "charges": {
+ "title": "Charges",
+ "description": "Information on the revenue to be raised through charges, as set out in the contract or as subsequently revised during the life of the project.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Charge"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Charge": {
+ "title": "Charge",
+ "description": "A charge to be incurred by users or government over the course of the contract. Charge information can be broken down by period. Information on the unit prices upon which total values are based can be provided in the tariffs section.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Charge identifier",
+ "description": "A local identifier for this specific charge. This field is used to keep track of revisions of a charge across multiple OCDS releases.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "Charge title",
+ "description": "A descriptive title for this charge.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "paidBy": {
+ "title": "Paid by",
+ "description": "Is this a user charge (paid by businesses or citizens using the facilities provided by the contract), or a charge paid by the government?",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "chargePaidBy.csv",
+ "openCodelist": false,
+ "enum": [
+ "government",
+ "user",
+ null
+ ]
+ },
+ "period": {
+ "title": "Period",
+ "description": "The period to which this charge applies.",
+ "$ref": "#/definitions/Period"
+ },
+ "estimatedValue": {
+ "title": "Estimated value",
+ "description": "What is the estimated total value to be raised from this charge during this period.",
+ "$ref": "#/definitions/Value"
+ },
+ "actualValue": {
+ "title": "Actual value",
+ "description": "In the implementation section, this field may be updated with the total revenue raised from this charge during this period.",
+ "$ref": "#/definitions/Value"
+ },
+ "notes": {
+ "title": "Notes",
+ "description": "Any notes on this charge. This may include clarifying information.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/charges/master/schema/index.html b/en/extensions/charges/master/schema/index.html
new file mode 100644
index 000000000..e37c3d952
--- /dev/null
+++ b/en/extensions/charges/master/schema/index.html
@@ -0,0 +1,393 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Charges +
+ ++ Adds a charges array to the implementation object to disclose the charges to be incurred by users or government in a given period of a contract. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The charges extension is used to record details of the total charges that are estimated or applied to users or government during the operation of a Public Private Partnership contract.
+This can be used to provide a breakdown of government support to a project, on a period-by-period basis.
+The charges extension introduces a charges array to the contracts.implementation object.
Example
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "title": "Public Private Partnership Agreement",
+ "description": "Public-Private Partnership agreement entered into by and between telecoms promoter, together with national fibre infrastructure and the special purpose vehicle Mega Consortium Ltd",
+ "implementation": {
+ "charges": [
+ {
+ "id": "2025-user",
+ "title": "User charges for calendar year 2025 resulting from 4G, 3G, voice and SMS tariffs",
+ "estimatedValue": {
+ "amount": 1019100000,
+ "currency": "USD"
+ },
+ "paidBy": "user",
+ "period": {
+ "startDate": "2025-01-01T00:00:00Z",
+ "endDate": "2025-12-31T23:59:59Z"
+ }
+ },
+ {
+ "id": "2026-user",
+ "title": "User charges for calendar year 2026 resulting from 4G, 3G, voice and SMS tariffs",
+ "estimatedValue": {
+ "amount": 1129206411.9632988,
+ "currency": "USD"
+ },
+ "paidBy": "user",
+ "period": {
+ "startDate": "2026-01-01T00:00:00Z",
+ "endDate": "2026-12-31T23:59:59Z"
+ }
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2019-03-20
+-
+
- Set
"uniqueItems": trueon array fields, and add"minLength": 1on required string fields.
+
2018-05-08
+-
+
- Make
Charge.idrequired to support revision tracking and list merging
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/charges/v1.1/README.md b/en/extensions/charges/v1.1/README.md
new file mode 100644
index 000000000..546e2affb
--- /dev/null
+++ b/en/extensions/charges/v1.1/README.md
@@ -0,0 +1,18 @@
+# Charges
+
+The charges extension is used to record details of the **total** charges that are estimated or applied to users or government during the operation of a Public Private Partnership contract.
+
+This can be used to provide a breakdown of **government support** to a project, on a period-by-period basis.
+
+## Overview
+
+The Charges extension introduces a `charges` property to both `Contract` and `Contract/Implementation`.
+
+This contains an array of `Charge` objects with properties for:
+
+- `title` - a descriptive title of the charge;
+- `paidBy` - either 'government' or 'user';
+- `period` - the start and end-date of the period covered by the charge;
+- `estimatedValue` - the predicated total value of this charge during the period;
+- `actualValue` - the actual value (updated after the period has ended) of the charge during the period;
+- `notes` - further information on the charge;
diff --git a/en/extensions/charges/v1.1/codelists/index.html b/en/extensions/charges/v1.1/codelists/index.html
new file mode 100644
index 000000000..affacdf57
--- /dev/null
+++ b/en/extensions/charges/v1.1/codelists/index.html
@@ -0,0 +1,5 @@
+
+
+
+
+
+
+
+ + Charges +
+ ++ Adds a charges array to the implementation object to disclose the charges to be incurred by users or government in a given period of a contract. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ charges
+
+ |
+ + Charges + | +
+ Information on the revenue to be raised through charges, as set out in the contract or as subsequently revised during the life of the project. + + |
+ + array of Charge objects + | +
+ Charge +
+ +
+ The extension defines a new Charge object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Charge identifier + | +
+ A local identifier for this specific charge. This field is used to keep track of revisions of a charge across multiple OCDS releases. + + |
+ + string + | +
+
+ title
+
+ |
+ + Charge title + | +
+ A descriptive title for this charge. + + |
+ + string + | +
+
+ paidBy
+
+ |
+ + Paid by + | +
+ Is this a user charge (paid by businesses or citizens using the facilities provided by the contract), or a charge paid by the government? + + |
+ + string from closed chargePaidBy codelist + | +
+
+ period
+
+ |
+ + Period + | +
+ The period to which this charge applies. + + |
+ + Period object + | +
+
+ estimatedValue
+
+ |
+ + Estimated value + | +
+ What is the estimated total value to be raised from this charge during this period. + + |
+ + Value object + | +
+
+ actualValue
+
+ |
+ + Actual value + | +
+ In the implementation section, this field may be updated with the total revenue raised from this charge during this period. + + |
+ + Value object + | +
+
+ notes
+
+ |
+ + Notes + | +
+ Any notes on this charge. This may include clarifying information. + + |
+ + string + | +
Not Found
+The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
diff --git a/en/extensions/charges/v1.1/extension.json b/en/extensions/charges/v1.1/extension.json new file mode 100644 index 000000000..6c298817c --- /dev/null +++ b/en/extensions/charges/v1.1/extension.json @@ -0,0 +1,15 @@ +{ + "name": { + "en": "Charges", + "es": "Cargos" + }, + "description": { + "en": "The charges extension is used to record details of the **total** charges that are estimated or applied to users or government during the operation of a Public Private Partnership contract.", + "es": "La extensi\u00f3n de cargos se utiliza para registrar detalles de los **cargos totales** estimados o aplicados a los usuarios o al gobierno durante la operaci\u00f3n de un contrato de Asociaci\u00f3n P\u00fablico Privada." + }, + "compatibility": [ + "1.1" + ], + "dependencies": [], + "documentationUrl": {} +} diff --git a/en/extensions/charges/v1.1/index.html b/en/extensions/charges/v1.1/index.html new file mode 100644 index 000000000..b37540443 --- /dev/null +++ b/en/extensions/charges/v1.1/index.html @@ -0,0 +1,274 @@ + + + + + + + + + +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/charges/v1.1/release-schema.json b/en/extensions/charges/v1.1/release-schema.json
new file mode 100644
index 000000000..8d250e8fa
--- /dev/null
+++ b/en/extensions/charges/v1.1/release-schema.json
@@ -0,0 +1,71 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "charges": {
+ "type": "array",
+ "title": "Charges",
+ "description": "Information on the revenue to be raised through charges, as set out in the contract or as subsequently revised during the life of the project.",
+ "items": {
+ "$ref": "#/definitions/Charge"
+ }
+ }
+ }
+ },
+ "Charge": {
+ "type": "object",
+ "title": "Charge",
+ "description": "A charge to be incurred by users or government over the course of the contract. Charge information can be broken down by period. Information on the unit prices upon which total values are based can be provided in the tariffs section.",
+ "properties": {
+ "id": {
+ "title": "Charge identifier",
+ "description": "A local identifier for this specific charge. This field is used to keep track of revisions of a charge across multiple OCDS releases.",
+ "type": "string"
+ },
+ "title": {
+ "title": "Charge title",
+ "description": "A descriptive title for this charge.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "paidBy": {
+ "title": "Paid by",
+ "description": "Is this a user charge (paid by businesses or citizens using the facilities provided by the contract), or a charge paid by the government?",
+ "type": [
+ "string",
+ "null"
+ ],
+ "enum": [
+ "government",
+ "user"
+ ]
+ },
+ "period": {
+ "title": "Period",
+ "description": "The period to which this charge applies.",
+ "$ref": "#/definitions/Period"
+ },
+ "estimatedValue": {
+ "title": "Estimated value",
+ "description": "What is the estimated total value to be raised from this charge during this period.",
+ "$ref": "#/definitions/Value"
+ },
+ "actualValue": {
+ "title": "Actual value",
+ "description": "In the implementation section, this field may be updated with the total revenue raised from this charge during this period.",
+ "$ref": "#/definitions/Value"
+ },
+ "notes": {
+ "title": "Notes",
+ "description": "Any notes on this charge. This may include clarifying information.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/charges/v1.1/schema/index.html b/en/extensions/charges/v1.1/schema/index.html
new file mode 100644
index 000000000..c535e6e1a
--- /dev/null
+++ b/en/extensions/charges/v1.1/schema/index.html
@@ -0,0 +1,388 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Charges +
+ ++ Adds a charges array to the implementation object to disclose the charges to be incurred by users or government in a given period of a contract. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The charges extension is used to record details of the total charges that are estimated or applied to users or government during the operation of a Public Private Partnership contract.
+This can be used to provide a breakdown of government support to a project, on a period-by-period basis.
+Overview
+The Charges extension introduces a charges property to both Contract and Contract/Implementation.
This contains an array of Charge objects with properties for:
-
+
title- a descriptive title of the charge;
+paidBy- either 'government' or 'user';
+period- the start and end-date of the period covered by the charge;
+estimatedValue- the predicated total value of this charge during the period;
+actualValue- the actual value (updated after the period has ended) of the charge during the period;
+notes- further information on the charge;
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/communication/index.html b/en/extensions/communication/index.html
new file mode 100644
index 000000000..41f020165
--- /dev/null
+++ b/en/extensions/communication/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Charges +
+ ++ Adds a charges array to the implementation object to disclose the charges to be incurred by users or government in a given period of a contract. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ charges
+
+ |
+ + Charges + | +
+ Information on the revenue to be raised through charges, as set out in the contract or as subsequently revised during the life of the project. + + |
+ + array of Charge objects + | +
+ Charge +
+ +
+ The extension defines a new Charge object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Charge identifier + | +
+ A local identifier for this specific charge. This field is used to keep track of revisions of a charge across multiple OCDS releases. + + |
+ + string + | +
+
+ title
+
+ |
+ + Charge title + | +
+ A descriptive title for this charge. + + |
+ + string + | +
+
+ paidBy
+
+ |
+ + Paid by + | +
+ Is this a user charge (paid by businesses or citizens using the facilities provided by the contract), or a charge paid by the government? + + |
+ + string + | +
+
+ period
+
+ |
+ + Period + | +
+ The period to which this charge applies. + + |
+ + Period object + | +
+
+ estimatedValue
+
+ |
+ + Estimated value + | +
+ What is the estimated total value to be raised from this charge during this period. + + |
+ + Value object + | +
+
+ actualValue
+
+ |
+ + Actual value + | +
+ In the implementation section, this field may be updated with the total revenue raised from this charge during this period. + + |
+ + Value object + | +
+
+ notes
+
+ |
+ + Notes + | +
+ Any notes on this charge. This may include clarifying information. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/communication/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/communication/master/release-schema.json b/en/extensions/communication/master/release-schema.json
new file mode 100644
index 000000000..f7644278b
--- /dev/null
+++ b/en/extensions/communication/master/release-schema.json
@@ -0,0 +1,80 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "communication": {
+ "title": "Communication",
+ "description": "Modalities of communication about key events.",
+ "$ref": "#/definitions/Communication"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "communication": {
+ "title": "Communication",
+ "description": "Modalities of communication about key events for this lot.",
+ "$ref": "#/definitions/Communication"
+ }
+ }
+ },
+ "Communication": {
+ "title": "Communication",
+ "description": "Modalities of communication about key events.",
+ "type": "object",
+ "properties": {
+ "atypicalToolName": {
+ "title": "Atypical tool name",
+ "description": "The name of the tools and devices that are not generally available and that are required to communicate electronically with the buyer.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "atypicalToolUrl": {
+ "title": "Atypical tool URL",
+ "description": "The URL of the tools and devices that are not generally available and that are required to communicate electronically with the buyer.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "noticePreferredPublicationDate": {
+ "title": "Notice preferred publication date",
+ "description": "The buyer's preferred date of publication of the notice (e.g. to avoid publication during a national holiday).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "futureNoticeDate": {
+ "title": "Future notice date",
+ "description": "The estimated date of publication of the next sequential notice. For example, the next sequential notice for a planning notice might be a competition notice.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "invitationToConfirmInterestDispatchDate": {
+ "title": "Invitation to confirm interest dispatch date",
+ "description": "The estimated date of dispatch from the buyer to potential suppliers of the invitations to confirm interest. For example, when a planning notice is used as a call for competition, the buyer might simultaneously invite the potential suppliers that have expressed their interest to confirm their continuing interest.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "documentAvailabilityPeriod": {
+ "title": "Document availability period",
+ "description": "The period during which documents can be accessed, or during which requests for access to documents can be submitted.",
+ "$ref": "#/definitions/Period"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/communication/master/schema/index.html b/en/extensions/communication/master/schema/index.html
new file mode 100644
index 000000000..12d092b0c
--- /dev/null
+++ b/en/extensions/communication/master/schema/index.html
@@ -0,0 +1,418 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Communication +
+ ++ Adds a communication object to the tender to describe the modalities of communication about key events. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a communication object to the tender and lot objects, to describe the modalities of communication about key events.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Legal context
+In the European Union, this extension's fields correspond to eForms BT-124, BT-127, BT-631, BT-632 and BT-738.For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+Tender
+An example of a planning notice from which a competition notice will follow.
+{
+ "tender": {
+ "communication": {
+ "atypicalToolName": "ACertainTool",
+ "atypicalToolUrl": "https://ecomm-procurement.example.net",
+ "futureNoticeDate": "2020-06-17T00:00:00+01:00",
+ "noticePreferredPublicationDate": "2020-03-15T00:00:00+01:00",
+ "documentAvailabilityPeriod": {
+ "startDate": "2020-06-15T00:00:00+01:00",
+ "endDate": "2020-07-10T00:00:00+01:00"
+ }
+ }
+ }
+}
+Lot
+An example of a planning notice that is used as a call for competition and that is divided into lots.
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "communication": {
+ "atypicalToolName": "ACertainTool",
+ "atypicalToolUrl": "https://ecomm-procurement.example.net",
+ "noticePreferredPublicationDate": "2020-03-15T00:00:00+01:00",
+ "documentAvailabilityPeriod": {
+ "startDate": "2020-06-15T00:00:00+01:00",
+ "endDate": "2020-07-10T00:00:00+01:00"
+ },
+ "invitationToConfirmInterestDispatchDate": "2020-11-15T09:00:00+01:00"
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-03-09
+-
+
- Add fields:
+
-
+
Communication.atypicalToolName
+Communication.invitationToConfirmInterestDispatchDate
+Communication.noticePreferredPublicationDate
+Lot.communication
+
+
2021-01-19
+-
+
- Add
tender.communication.documentAvailabilityPeriodfield
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/contractTerms/index.html b/en/extensions/contractTerms/index.html
new file mode 100644
index 000000000..928e24ae3
--- /dev/null
+++ b/en/extensions/contractTerms/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Communication +
+ ++ Adds a communication object to the tender to describe the modalities of communication about key events. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ communication
+
+ |
+ + Communication + | +
+ Modalities of communication about key events. + + |
+ + Communication object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ communication
+
+ |
+ + Communication + | +
+ Modalities of communication about key events for this lot. + + |
+ + Communication object + | +
+ Communication +
+ +
+ The extension defines a new Communication object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ atypicalToolName
+
+ |
+ + Atypical tool name + | +
+ The name of the tools and devices that are not generally available and that are required to communicate electronically with the buyer. + + |
+ + string + | +
+
+ atypicalToolUrl
+
+ |
+ + Atypical tool URL + | +
+ The URL of the tools and devices that are not generally available and that are required to communicate electronically with the buyer. + + |
+ + string + | +
+
+ noticePreferredPublicationDate
+
+ |
+ + Notice preferred publication date + | +
+ The buyer's preferred date of publication of the notice (e.g. to avoid publication during a national holiday). + + |
+ + string + | +
+
+ futureNoticeDate
+
+ |
+ + Future notice date + | +
+ The estimated date of publication of the next sequential notice. For example, the next sequential notice for a planning notice might be a competition notice. + + |
+ + string + | +
+
+ invitationToConfirmInterestDispatchDate
+
+ |
+ + Invitation to confirm interest dispatch date + | +
+ The estimated date of dispatch from the buyer to potential suppliers of the invitations to confirm interest. For example, when a planning notice is used as a call for competition, the buyer might simultaneously invite the potential suppliers that have expressed their interest to confirm their continuing interest. + + |
+ + string + | +
+
+ documentAvailabilityPeriod
+
+ |
+ + Document availability period + | +
+ The period during which documents can be accessed, or during which requests for access to documents can be submitted. + + |
+ + Period object + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/contractTerms/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/contractTerms/master/codelists/permission.csv b/en/extensions/contractTerms/master/codelists/permission.csv
new file mode 100644
index 000000000..e72d40d7a
--- /dev/null
+++ b/en/extensions/contractTerms/master/codelists/permission.csv
@@ -0,0 +1,4 @@
+Code,Title,Description
+required,Required,The activity is required.
+allowed,Allowed,The activity is allowed.
+notAllowed,Not allowed,The activity is not allowed.
diff --git a/en/extensions/contractTerms/master/extension.json b/en/extensions/contractTerms/master/extension.json
new file mode 100644
index 000000000..de01f54f9
--- /dev/null
+++ b/en/extensions/contractTerms/master/extension.json
@@ -0,0 +1,29 @@
+{
+ "name": {
+ "en": "Contract terms",
+ "es": "T\u00e9rminos del contrato"
+ },
+ "description": {
+ "en": "Adds a contract terms object to the tender and lot objects, to describe the terms governing the future contract.",
+ "es": "Agrega un objeto t\u00e9rminos del contrato a los objetos de la licitaci\u00f3n y del lote, para describir los t\u00e9rminos que rigen al futuro contrato."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/contractTerms/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "permission.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/en/extensions/contractTerms/master/index.html b/en/extensions/contractTerms/master/index.html
new file mode 100644
index 000000000..34214973d
--- /dev/null
+++ b/en/extensions/contractTerms/master/index.html
@@ -0,0 +1,369 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Contract terms +
+ ++ Adds a contract terms object to the tender and lot objects, to describe the terms governing the future contract. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ permission.csv +
+ +
+ You can download the permission.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ required
+
+ |
+ + Required + | +
+ The activity is required. + + |
+
+
+ allowed
+
+ |
+ + Allowed + | +
+ The activity is allowed. + + |
+
+
+ notAllowed
+
+ |
+ + Not allowed + | +
+ The activity is not allowed. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/contractTerms/master/release-schema.json b/en/extensions/contractTerms/master/release-schema.json
new file mode 100644
index 000000000..f0e99c219
--- /dev/null
+++ b/en/extensions/contractTerms/master/release-schema.json
@@ -0,0 +1,214 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "contractTerms": {
+ "title": "Contract terms",
+ "description": "Information about the terms governing the future contracts from the procedure.",
+ "$ref": "#/definitions/ContractTerms"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "contractTerms": {
+ "title": "Contract terms",
+ "description": "Information about the terms governing the future contracts for the lot.",
+ "$ref": "#/definitions/ContractTerms"
+ }
+ }
+ },
+ "ContractTerms": {
+ "title": "Contract terms",
+ "description": "Information about the terms governing the future contracts.",
+ "type": "object",
+ "properties": {
+ "hasElectronicPayment": {
+ "title": "Electronic payment used",
+ "description": "Whether electronic payment is used.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "hasElectronicOrdering": {
+ "title": "Electronic ordering used",
+ "description": "Whether electronic ordering is used.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "electronicInvoicingPolicy": {
+ "title": "Electronic invoicing policy",
+ "description": "Whether the buyer will require, allow or not allow electronic invoices.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "permission.csv",
+ "openCodelist": false,
+ "enum": [
+ "required",
+ "allowed",
+ "notAllowed",
+ null
+ ]
+ },
+ "reservedExecution": {
+ "title": "Reserved execution",
+ "description": "Whether the execution of the contract is restricted to the framework of sheltered employment programmes.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "performanceTerms": {
+ "title": "Terms performance",
+ "description": "The main information about the performance of the contract (e.g. intermediary deliverables, compensation for damages, intellectual property rights).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "financialTerms": {
+ "title": "Financial terms",
+ "description": "The main information about financing and payment and/or reference to any provisions that govern them.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "tendererLegalForm": {
+ "title": "Tenderer legal form",
+ "description": "A certain legal form that must be taken by a group of tenderers that is awarded a contract.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "hasExclusiveRights": {
+ "title": "Has exclusive rights",
+ "description": "A right entitling a public service operator to operate certain public passenger transport services on a particular route or network or in a particular area, to the exclusion of any other such operator.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "exclusiveRights": {
+ "title": "Exclusive rights",
+ "description": "The nature and extent of the exclusive rights granted by the procuring entity to the supplier.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "operatorRevenueShare": {
+ "title": "Operator revenue share",
+ "description": "The percentage of revenue from the sale of tickets allocated to the supplier.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0
+ },
+ "otherTerms": {
+ "title": "Other terms",
+ "description": "Other contract terms that do not fit the semantics of any other OCDS field.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "rewardsAndPenalties": {
+ "title": "Rewards and penalties",
+ "description": "Information about rewards and penalties relating to quality targets.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "socialStandards": {
+ "title": "Social standards",
+ "description": "The required social standards, for example: detail of the contractual rights of the staff concerned, and conditions under which employees are considered to be linked to the services.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "hasNonDisclosureAgreement": {
+ "title": "Has non-disclosure agreement",
+ "description": "Whether contract execution requires a non-disclosure agreement.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "nonDisclosureAgreement": {
+ "title": "Non-disclosure agreement",
+ "description": "A description of the non-disclosure agreement required for contract execution.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "customerServices": {
+ "title": "Customer services",
+ "description": "Information about customer service requirements.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/CustomerService"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "CustomerService": {
+ "title": "Customer service",
+ "description": "A customer service requirement.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Type",
+ "description": "The type of this customer service requirement.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "name": {
+ "title": "Name",
+ "description": "A name for this customer service requirement.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "A description of this customer service requirement.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/contractTerms/master/schema/index.html b/en/extensions/contractTerms/master/schema/index.html
new file mode 100644
index 000000000..4aa23db13
--- /dev/null
+++ b/en/extensions/contractTerms/master/schema/index.html
@@ -0,0 +1,678 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Contract terms +
+ ++ Adds a contract terms object to the tender and lot objects, to describe the terms governing the future contract. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a contract terms object to the tender and lot objects, to describe the terms governing the future contract.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Legal context
+In the European Union, this extension's fields correspond to eForms BG-711 (Contract Terms), BT-801 (Non Disclosure Agreement), BT-802 (Non Disclosure Agreement Description), OPT-071 (Quality Target Code) and OPT-072 (Quality Target Description). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+Tender
+{
+ "tender": {
+ "contractTerms": {
+ "hasElectronicPayment": true,
+ "hasElectronicOrdering": false,
+ "electronicInvoicingPolicy": "required",
+ "reservedExecution": true,
+ "performanceTerms": "A set of KPIs will be developed for this contract and the successful tenderer will be measured against these for the duration of the contract. Please refer to briefing document for further details.",
+ "financialTerms": "In the event that a work referred to in § 2.6 of the Agreement is created as part of the implementation of the Subject Matter of the Agreement, the Contractor shall indicate on the invoice what proportion of the remuneration for implementation.",
+ "tendererLegalForm": "Contractors may jointly apply for the contract.",
+ "hasExclusiveRights": false,
+ "operatorRevenueShare": 0.25,
+ "socialStandards": "The supplier maintains the social, collective bargaining and labor law obligations according to Union law, national law or collective agreements. 4 paragraph 4a Regulation 13707/2007.",
+ "hasNonDisclosureAgreement": true,
+ "nonDisclosureAgreement": "A non-disclosure agreement is required in order to...",
+ "customerServices": [
+ {
+ "type": "clean",
+ "name": "Cleanliness of rolling stock and station facilities",
+ "description": "Rolling stock and station facilities must be kept at a minimum standard of cleanliness."
+ }
+ ]
+ }
+ }
+}
+Lot
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "contractTerms": {
+ "hasElectronicPayment": true,
+ "hasElectronicOrdering": false,
+ "electronicInvoicingPolicy": "required",
+ "reservedExecution": true,
+ "performanceTerms": "A set of KPIs will be developed for this contract and the successful tenderer will be measured against these for the duration of the contract. Please refer to briefing document for further details.",
+ "financialTerms": "In the event that a work referred to in § 2.6 of the Agreement is created as part of the implementation of the Subject Matter of the Agreement, the Contractor shall indicate on the invoice what proportion of the remuneration for implementation.",
+ "tendererLegalForm": "Contractors may jointly apply for the contract.",
+ "hasExclusiveRights": false,
+ "operatorRevenueShare": 0.25,
+ "socialStandards": "The supplier maintains the social, collective bargaining and labor law obligations according to Union law, national law or collective agreements. 4 paragraph 4a Regulation 13707/2007.",
+ "hasNonDisclosureAgreement": true,
+ "nonDisclosureAgreement": "A non-disclosure agreement is required in order to...",
+ "customerServices": [
+ {
+ "type": "clean",
+ "name": "Cleanliness of rolling stock and station facilities",
+ "description": "Rolling stock and station facilities must be kept at a minimum standard of cleanliness."
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-03-10
+-
+
- Add
hasNonDisclosureAgreement,nonDisclosureAgreementandcustomerServicesfields.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/contract_buyer/index.html b/en/extensions/contract_buyer/index.html
new file mode 100644
index 000000000..ff0a46e15
--- /dev/null
+++ b/en/extensions/contract_buyer/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Contract terms +
+ ++ Adds a contract terms object to the tender and lot objects, to describe the terms governing the future contract. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ contractTerms
+
+ |
+ + Contract terms + | +
+ Information about the terms governing the future contracts from the procedure. + + |
+ + ContractTerms object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ contractTerms
+
+ |
+ + Contract terms + | +
+ Information about the terms governing the future contracts for the lot. + + |
+ + ContractTerms object + | +
+ ContractTerms +
+ +
+ The extension defines a new ContractTerms object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasElectronicPayment
+
+ |
+ + Electronic payment used + | +
+ Whether electronic payment is used. + + |
+ + boolean + | +
+
+ hasElectronicOrdering
+
+ |
+ + Electronic ordering used + | +
+ Whether electronic ordering is used. + + |
+ + boolean + | +
+
+ electronicInvoicingPolicy
+
+ |
+ + Electronic invoicing policy + | +
+ Whether the buyer will require, allow or not allow electronic invoices. + + |
+ + string from closed permission codelist + | +
+
+ reservedExecution
+
+ |
+ + Reserved execution + | +
+ Whether the execution of the contract is restricted to the framework of sheltered employment programmes. + + |
+ + boolean + | +
+
+ performanceTerms
+
+ |
+ + Terms performance + | +
+ The main information about the performance of the contract (e.g. intermediary deliverables, compensation for damages, intellectual property rights). + + |
+ + string + | +
+
+ financialTerms
+
+ |
+ + Financial terms + | +
+ The main information about financing and payment and/or reference to any provisions that govern them. + + |
+ + string + | +
+
+ tendererLegalForm
+
+ |
+ + Tenderer legal form + | +
+ A certain legal form that must be taken by a group of tenderers that is awarded a contract. + + |
+ + string + | +
+
+ hasExclusiveRights
+
+ |
+ + Has exclusive rights + | +
+ A right entitling a public service operator to operate certain public passenger transport services on a particular route or network or in a particular area, to the exclusion of any other such operator. + + |
+ + boolean + | +
+
+ exclusiveRights
+
+ |
+ + Exclusive rights + | +
+ The nature and extent of the exclusive rights granted by the procuring entity to the supplier. + + |
+ + string + | +
+
+ operatorRevenueShare
+
+ |
+ + Operator revenue share + | +
+ The percentage of revenue from the sale of tickets allocated to the supplier. + + |
+ + number + | +
+
+ otherTerms
+
+ |
+ + Other terms + | +
+ Other contract terms that do not fit the semantics of any other OCDS field. + + |
+ + string + | +
+
+ rewardsAndPenalties
+
+ |
+ + Rewards and penalties + | +
+ Information about rewards and penalties relating to quality targets. + + |
+ + string + | +
+
+ socialStandards
+
+ |
+ + Social standards + | +
+ The required social standards, for example: detail of the contractual rights of the staff concerned, and conditions under which employees are considered to be linked to the services. + + |
+ + string + | +
+
+ hasNonDisclosureAgreement
+
+ |
+ + Has non-disclosure agreement + | +
+ Whether contract execution requires a non-disclosure agreement. + + |
+ + boolean + | +
+
+ nonDisclosureAgreement
+
+ |
+ + Non-disclosure agreement + | +
+ A description of the non-disclosure agreement required for contract execution. + + |
+ + string + | +
+
+ customerServices
+
+ |
+ + Customer services + | +
+ Information about customer service requirements. + + |
+ + array of CustomerService objects + | +
+ CustomerService +
+ +
+ The extension defines a new CustomerService object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Type + | +
+ The type of this customer service requirement. + + |
+ + string + | +
+
+ name
+
+ |
+ + Name + | +
+ A name for this customer service requirement. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A description of this customer service requirement. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/contract_buyer/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/contract_buyer/master/release-schema.json b/en/extensions/contract_buyer/master/release-schema.json
new file mode 100644
index 000000000..0e45e6d50
--- /dev/null
+++ b/en/extensions/contract_buyer/master/release-schema.json
@@ -0,0 +1,27 @@
+{
+ "definitions": {
+ "Award": {
+ "properties": {
+ "buyers": {
+ "title": "Buyers",
+ "description": "The organizations aiming to conclude a contract with the suppliers or to use the goods, services or works resulting from the contract, if not identical to the buyers for the contracting process.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "buyer": {
+ "title": "Buyer",
+ "description": "The organization aiming to conclude a contract with the suppliers or to use the goods, services or works resulting from the contract, if not identical to the buyer for the contracting process.",
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/contract_buyer/master/schema/index.html b/en/extensions/contract_buyer/master/schema/index.html
new file mode 100644
index 000000000..3c10695fa
--- /dev/null
+++ b/en/extensions/contract_buyer/master/schema/index.html
@@ -0,0 +1,282 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Buyer per award or contract +
+ ++ Adds buyer fields to the award and contract objects to indicate the buyer(s) for an individual award or contract, if different from the buyer(s) involved in the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds buyer fields to the award and contract objects to indicate the buyer(s) for an individual award or contract, if different from the buyer(s) involved in the contracting process as a whole.
+OCDS indicates the (lead) buyer in a contracting process with the buyer field. If a contracting process involves multiple buyers, each buyer can be added to the parties array with a 'buyer' role.
However, in some cases, for a given award, a subset of the buyers decide on the supplier and sign the contract. Only use this extension in such cases.
+Legal context
+In the European Union, this extension's fields correspond to eForms OPT-300-Contract-Signatory. For correspondences to eForms fields, see OCDS for eForms.
+Example
+Contracts
+Two contracts are issued with a different buyer for each.
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "buyer": {
+ "name": "Example Department of Transport",
+ "id": "GB-GOV-00000000"
+ }
+ },
+ {
+ "id": "2",
+ "awardID": "2",
+ "buyer": {
+ "name": "Example Department of Education",
+ "id": "GB-GOV-12345678"
+ }
+ }
+ ]
+}
+Awards
+One award is issued with two buyers.
+{
+ "awards": [
+ {
+ "id": "1",
+ "buyers": [
+ {
+ "name": "Example Department of Education",
+ "id": "GB-GOV-12345678"
+ },
+ {
+ "name": "Example Department of Transport",
+ "id": "GB-GOV-00000000"
+ }
+ ]
+ }
+ ]
+}
+Changelog
+2023-04-12
+-
+
- Add
awards.buyersfield.
+
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/contract_completion/index.html b/en/extensions/contract_completion/index.html
new file mode 100644
index 000000000..504e68a5d
--- /dev/null
+++ b/en/extensions/contract_completion/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Buyer per award or contract +
+ ++ Adds buyer fields to the award and contract objects to indicate the buyer(s) for an individual award or contract, if different from the buyer(s) involved in the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ buyers
+
+ |
+ + Buyers + | +
+ The organizations aiming to conclude a contract with the suppliers or to use the goods, services or works resulting from the contract, if not identical to the buyers for the contracting process. + + |
+ + array of OrganizationReference objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ buyer
+
+ |
+ + Buyer + | +
+ The organization aiming to conclude a contract with the suppliers or to use the goods, services or works resulting from the contract, if not identical to the buyer for the contracting process. + + |
+ + OrganizationReference object + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/contract_completion/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/contract_completion/master/release-schema.json b/en/extensions/contract_completion/master/release-schema.json
new file mode 100644
index 000000000..0eb38ffc1
--- /dev/null
+++ b/en/extensions/contract_completion/master/release-schema.json
@@ -0,0 +1,40 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "endDate": {
+ "title": "End date",
+ "description": "The actual date when contract implementation ended. Where `implementation/endDate` varies from the anticipated `contract/period/endDate` an explanation of the variance should be provided in `implementation/endDateDetails`.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "endDateDetails": {
+ "title": "End date details",
+ "description": "Details related to the endDate. This may be a justification for the contract's completion date being different than in the original contract.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "finalValue": {
+ "title": "Final value",
+ "description": "The actual total value of all payments for a completed contract. If `implementation/transactions` are used for this contract, this field should equal the sum of the `transaction/value/amount` fields. Where `finalValue/amount` varies from `contract/value/amount` an explanation of the variance should be provided in `finalValueDetails`.",
+ "$ref": "#/definitions/Value"
+ },
+ "finalValueDetails": {
+ "title": "Final value details",
+ "description": "Details related to the final value. This may be a justification for the completed contract's value being different than in the original contract.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/contract_completion/master/schema/index.html b/en/extensions/contract_completion/master/schema/index.html
new file mode 100644
index 000000000..5b6856554
--- /dev/null
+++ b/en/extensions/contract_completion/master/schema/index.html
@@ -0,0 +1,282 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Contract Completion +
+ ++ Adds fields to the contract implementation section to detail the end date, and final value of a contract. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The Open Contracting Data Standard can be used to provide information on all stages of a contracting process, from planning through to implementation.
+This extension introduces four fields that can be used at the end of a contracting process to provide details of the final date and value of the contract, and, where there is variation, to provide a justification of this.
+Using existing OCDS fields within a contracts register
+OCDS contains many existing fields that can be used as part of a Contracts Register. These are documented in the schema reference. This extension does not modify any of these fields. However, the following list is provided for convenience of those considering the design of a contracts register:
+-
+
- Supplier details should be recorded within the
awardssection, linked viacontracts.awardID(even if you are only releasing information at the contract stage, you may provide information in the tender and award sections).
+ - Contract documents can be linked to under
contracts.documents.
+ - Performance reports can be provided under
contracts.implementation.documents.
+ - Details of payments can be provided under
contracts.implementation.transactions.
+ - Progress details can be provided using
contracts.implementation.milestones.
+ - Amendments can be described using the
contracts.amendmentsarray, and with past values provided using the OCDS releases model as described here.
+
Using milestones to show contract completion
+Milestones may have a status of 'scheduled', 'met', 'notMet' or 'partiallyMet'. By providing at least one milestone for a contract, and then ensuring milestones.status is updated when implementation.endDate you can indicate whether a contract ended with successful delivery of all milestones and deliverables.
Example
+Note the difference between the contract period and value (as agreed in the contract, or amended contract), and the implementation finalValue and endDate, along with the explanation provided of this variance.
{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "title": "Contract to build new cycle lanes in the centre of town.",
+ "period": {
+ "startDate": "2010-07-01T00:00:00Z",
+ "endDate": "2012-01-01T23:59:00Z",
+ "maxExtentDate": "2012-01-31T23:59:00Z"
+ },
+ "value": {
+ "amount": 11500000,
+ "currency": "GBP"
+ },
+ "implementation": {
+ "endDate": "2012-02-01T00:00:00Z",
+ "endDateDetails": "Project was completed one day beyond the extended deadline.",
+ "finalValue": {
+ "amount": 11800000,
+ "currency": "GBP"
+ },
+ "finalValueDetails": "The final payment to the supplier included a compensation payment triggered by the local authority failure to provide work permits on schedule."
+ }
+ }
+ ]
+}
+The examples directory contains a full worked example with:
+-
+
- A release that provides details of a contract; +
- A release that includes an amendment to the contract to increase the total value, as well as initial payment transactions; +
- A release that contains a confirmed end date, final value, and the explanation of variation in these. +
This is also provided as an OCDS record and as an Excel file.
+In the Excel file, it is possible to see three releases describing the three key moments from the same contracting process.
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-06-04
+-
+
- Review normative and non-normative words +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed in https://github.com/open-contracting/standard/issues/703.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/contract_suppliers/index.html b/en/extensions/contract_suppliers/index.html
new file mode 100644
index 000000000..9257e33bc
--- /dev/null
+++ b/en/extensions/contract_suppliers/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Contract Completion +
+ ++ Adds fields to the contract implementation section to detail the end date, and final value of a contract. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ endDate
+
+ |
+ + End date + | +
+ The actual date when contract implementation ended. Where |
+ + string + | +
+
+ endDateDetails
+
+ |
+ + End date details + | +
+ Details related to the endDate. This may be a justification for the contract's completion date being different than in the original contract. + + |
+ + string + | +
+
+ finalValue
+
+ |
+ + Final value + | +
+ The actual total value of all payments for a completed contract. If |
+ + Value object + | +
+
+ finalValueDetails
+
+ |
+ + Final value details + | +
+ Details related to the final value. This may be a justification for the completed contract's value being different than in the original contract. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/contract_suppliers/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/contract_suppliers/master/release-schema.json b/en/extensions/contract_suppliers/master/release-schema.json
new file mode 100644
index 000000000..d557c9353
--- /dev/null
+++ b/en/extensions/contract_suppliers/master/release-schema.json
@@ -0,0 +1,18 @@
+{
+ "definitions": {
+ "Contract": {
+ "properties": {
+ "suppliers": {
+ "title": "Suppliers",
+ "description": "The suppliers explicitly named in this contract.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/contract_suppliers/master/schema/index.html b/en/extensions/contract_suppliers/master/schema/index.html
new file mode 100644
index 000000000..230fad4c9
--- /dev/null
+++ b/en/extensions/contract_suppliers/master/schema/index.html
@@ -0,0 +1,231 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Contract suppliers +
+ ++ To allow explicit declaration of suppliers within the contracts block. Used when a single award to multiple suppliers results in multiple contracts to a sub-set of those awarded suppliers. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+OCDS is designed around a contracting model in which:
+-
+
- One or more awards are made naming the selected suppliers; +
- One contract is signed for each award made, referring back to the related award; +
For this reason, the core Contract block does not include information on suppliers. These can be located by looking at the related Award using the awardID cross-reference.
However, there are some contracting processes in which a single award to multiple suppliers, results in multiple contracts, each to a single supplier. In these instances, it is important to specify suppliers at the contract level.
+The Contract Suppliers extension introduces a contracts.suppliers array for this purpose.
Example
+An award is made to a consortium with multiple suppliers. Then, a contract is signed with each of them separately. When this extension is used, you should fill contracts.items and contracts.value with the awarded items and value for each supplier.
{
+ "awards": [
+ {
+ "id": "ocds-213czf-000-00001-award-01",
+ "value": {
+ "amount": 100000,
+ "currency": "GBP"
+ },
+ "items": [
+ {
+ "id": "0001",
+ "description": "Construction work for highways",
+ "quantity": 10,
+ "unit": {
+ "name": "Miles",
+ "value": {
+ "amount": 10000,
+ "currency": "GBP"
+ }
+ }
+ }
+ ],
+ "suppliers": [
+ {
+ "id": "GB-COH-1234567844",
+ "name": "AnyCorp Cycle Provision"
+ },
+ {
+ "id": "GB-COH-789456123",
+ "name": "OtherCorp"
+ }
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "ocds-213czf-000-00001-contract-01",
+ "awardID": "ocds-213czf-000-00001-award-01",
+ "value": {
+ "amount": 70000,
+ "currency": "GBP"
+ },
+ "suppliers": [
+ {
+ "id": "GB-COH-1234567844",
+ "name": "AnyCorp Cycle Provision"
+ }
+ ],
+ "items": [
+ {
+ "id": "0001",
+ "description": "Construction work for highways",
+ "quantity": 7,
+ "unit": {
+ "name": "Miles",
+ "value": {
+ "amount": 10000,
+ "currency": "GBP"
+ }
+ }
+ }
+ ]
+ },
+ {
+ "id": "ocds-213czf-000-00001-contract-02",
+ "awardID": "ocds-213czf-000-00001-award-01",
+ "value": {
+ "amount": 30000,
+ "currency": "GBP"
+ },
+ "suppliers": [
+ {
+ "id": "GB-COH-789456123",
+ "name": "OtherCorp"
+ }
+ ],
+ "items": [
+ {
+ "id": "0001",
+ "description": "Construction work for highways",
+ "quantity": 3,
+ "unit": {
+ "name": "Miles",
+ "value": {
+ "amount": 10000,
+ "currency": "GBP"
+ }
+ }
+ }
+ ]
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/countryCode/index.html b/en/extensions/countryCode/index.html
new file mode 100644
index 000000000..b1613addc
--- /dev/null
+++ b/en/extensions/countryCode/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Contract suppliers +
+ ++ To allow explicit declaration of suppliers within the contracts block. Used when a single award to multiple suppliers results in multiple contracts to a sub-set of those awarded suppliers. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ suppliers
+
+ |
+ + Suppliers + | +
+ The suppliers explicitly named in this contract. + + |
+ + array of OrganizationReference objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/countryCode/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/countryCode/master/extension.json b/en/extensions/countryCode/master/extension.json
new file mode 100644
index 000000000..7e48beda6
--- /dev/null
+++ b/en/extensions/countryCode/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Country code",
+ "es": "C\u00f3digo de pa\u00eds"
+ },
+ "description": {
+ "en": "Adds a country code field to the address object.",
+ "es": "Agregar un campo c\u00f3digo de pa\u00eds al objeto de direcci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/countryCode/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "country.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/countryCode/master/index.html b/en/extensions/countryCode/master/index.html
new file mode 100644
index 000000000..c94344371
--- /dev/null
+++ b/en/extensions/countryCode/master/index.html
@@ -0,0 +1,307 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Country code +
+ ++ Adds a country code field to the address object. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ country.csv +
+ +
+ You can download the country.csv file in English.
+
| + Code + | ++ Title + | +
|---|---|
+
+ AD
+
+ |
+ + Andorra + | +
+
+ AE
+
+ |
+ + United Arab Emirates + | +
+
+ AF
+
+ |
+ + Afghanistan + | +
+
+ AG
+
+ |
+ + Antigua and Barbuda + | +
+
+ AI
+
+ |
+ + Anguilla + | +
+
+ AL
+
+ |
+ + Albania + | +
+
+ AM
+
+ |
+ + Armenia + | +
+
+ AO
+
+ |
+ + Angola + | +
+
+ AQ
+
+ |
+ + Antarctica + | +
+
+ AR
+
+ |
+ + Argentina + | +
+
+ AS
+
+ |
+ + American Samoa + | +
+
+ AT
+
+ |
+ + Austria + | +
+
+ AU
+
+ |
+ + Australia + | +
+
+ AW
+
+ |
+ + Aruba + | +
+
+ AX
+
+ |
+ + Åland Islands + | +
+
+ AZ
+
+ |
+ + Azerbaijan + | +
+
+ BA
+
+ |
+ + Bosnia and Herzegovina + | +
+
+ BB
+
+ |
+ + Barbados + | +
+
+ BD
+
+ |
+ + Bangladesh + | +
+
+ BE
+
+ |
+ + Belgium + | +
+
+ BF
+
+ |
+ + Burkina Faso + | +
+
+ BG
+
+ |
+ + Bulgaria + | +
+
+ BH
+
+ |
+ + Bahrain + | +
+
+ BI
+
+ |
+ + Burundi + | +
+
+ BJ
+
+ |
+ + Benin + | +
+
+ BL
+
+ |
+ + Saint Barthélemy + | +
+
+ BM
+
+ |
+ + Bermuda + | +
+
+ BN
+
+ |
+ + Brunei Darussalam + | +
+
+ BO
+
+ |
+ + Bolivia (Plurinational State of) + | +
+
+ BQ
+
+ |
+ + Bonaire, Sint Eustatius and Saba + | +
+
+ BR
+
+ |
+ + Brazil + | +
+
+ BS
+
+ |
+ + Bahamas + | +
+
+ BT
+
+ |
+ + Bhutan + | +
+
+ BV
+
+ |
+ + Bouvet Island + | +
+
+ BW
+
+ |
+ + Botswana + | +
+
+ BY
+
+ |
+ + Belarus + | +
+
+ BZ
+
+ |
+ + Belize + | +
+
+ CA
+
+ |
+ + Canada + | +
+
+ CC
+
+ |
+ + Cocos (Keeling) Islands + | +
+
+ CD
+
+ |
+ + Congo (the Democratic Republic of the) + | +
+
+ CF
+
+ |
+ + Central African Republic + | +
+
+ CG
+
+ |
+ + Congo + | +
+
+ CH
+
+ |
+ + Switzerland + | +
+
+ CI
+
+ |
+ + Côte d'Ivoire + | +
+
+ CK
+
+ |
+ + Cook Islands + | +
+
+ CL
+
+ |
+ + Chile + | +
+
+ CM
+
+ |
+ + Cameroon + | +
+
+ CN
+
+ |
+ + China + | +
+
+ CO
+
+ |
+ + Colombia + | +
+
+ CR
+
+ |
+ + Costa Rica + | +
+
+ CU
+
+ |
+ + Cuba + | +
+
+ CV
+
+ |
+ + Cabo Verde + | +
+
+ CW
+
+ |
+ + Curaçao + | +
+
+ CX
+
+ |
+ + Christmas Island + | +
+
+ CY
+
+ |
+ + Cyprus + | +
+
+ CZ
+
+ |
+ + Czechia + | +
+
+ DE
+
+ |
+ + Germany + | +
+
+ DJ
+
+ |
+ + Djibouti + | +
+
+ DK
+
+ |
+ + Denmark + | +
+
+ DM
+
+ |
+ + Dominica + | +
+
+ DO
+
+ |
+ + Dominican Republic + | +
+
+ DZ
+
+ |
+ + Algeria + | +
+
+ EC
+
+ |
+ + Ecuador + | +
+
+ EE
+
+ |
+ + Estonia + | +
+
+ EG
+
+ |
+ + Egypt + | +
+
+ EH
+
+ |
+ + Western Sahara + | +
+
+ ER
+
+ |
+ + Eritrea + | +
+
+ ES
+
+ |
+ + Spain + | +
+
+ ET
+
+ |
+ + Ethiopia + | +
+
+ FI
+
+ |
+ + Finland + | +
+
+ FJ
+
+ |
+ + Fiji + | +
+
+ FK
+
+ |
+ + Falkland Islands [Malvinas] + | +
+
+ FM
+
+ |
+ + Micronesia (Federated States of) + | +
+
+ FO
+
+ |
+ + Faroe Islands + | +
+
+ FR
+
+ |
+ + France + | +
+
+ GA
+
+ |
+ + Gabon + | +
+
+ GB
+
+ |
+ + United Kingdom of Great Britain and Northern Ireland + | +
+
+ GD
+
+ |
+ + Grenada + | +
+
+ GE
+
+ |
+ + Georgia + | +
+
+ GF
+
+ |
+ + French Guiana + | +
+
+ GG
+
+ |
+ + Guernsey + | +
+
+ GH
+
+ |
+ + Ghana + | +
+
+ GI
+
+ |
+ + Gibraltar + | +
+
+ GL
+
+ |
+ + Greenland + | +
+
+ GM
+
+ |
+ + Gambia + | +
+
+ GN
+
+ |
+ + Guinea + | +
+
+ GP
+
+ |
+ + Guadeloupe + | +
+
+ GQ
+
+ |
+ + Equatorial Guinea + | +
+
+ GR
+
+ |
+ + Greece + | +
+
+ GS
+
+ |
+ + South Georgia and the South Sandwich Islands + | +
+
+ GT
+
+ |
+ + Guatemala + | +
+
+ GU
+
+ |
+ + Guam + | +
+
+ GW
+
+ |
+ + Guinea-Bissau + | +
+
+ GY
+
+ |
+ + Guyana + | +
+
+ HK
+
+ |
+ + Hong Kong + | +
+
+ HM
+
+ |
+ + Heard Island and McDonald Islands + | +
+
+ HN
+
+ |
+ + Honduras + | +
+
+ HR
+
+ |
+ + Croatia + | +
+
+ HT
+
+ |
+ + Haiti + | +
+
+ HU
+
+ |
+ + Hungary + | +
+
+ ID
+
+ |
+ + Indonesia + | +
+
+ IE
+
+ |
+ + Ireland + | +
+
+ IL
+
+ |
+ + Israel + | +
+
+ IM
+
+ |
+ + Isle of Man + | +
+
+ IN
+
+ |
+ + India + | +
+
+ IO
+
+ |
+ + British Indian Ocean Territory + | +
+
+ IQ
+
+ |
+ + Iraq + | +
+
+ IR
+
+ |
+ + Iran (Islamic Republic of) + | +
+
+ IS
+
+ |
+ + Iceland + | +
+
+ IT
+
+ |
+ + Italy + | +
+
+ JE
+
+ |
+ + Jersey + | +
+
+ JM
+
+ |
+ + Jamaica + | +
+
+ JO
+
+ |
+ + Jordan + | +
+
+ JP
+
+ |
+ + Japan + | +
+
+ KE
+
+ |
+ + Kenya + | +
+
+ KG
+
+ |
+ + Kyrgyzstan + | +
+
+ KH
+
+ |
+ + Cambodia + | +
+
+ KI
+
+ |
+ + Kiribati + | +
+
+ KM
+
+ |
+ + Comoros + | +
+
+ KN
+
+ |
+ + Saint Kitts and Nevis + | +
+
+ KP
+
+ |
+ + Korea (the Democratic People's Republic of) + | +
+
+ KR
+
+ |
+ + Korea (the Republic of) + | +
+
+ KW
+
+ |
+ + Kuwait + | +
+
+ KY
+
+ |
+ + Cayman Islands + | +
+
+ KZ
+
+ |
+ + Kazakhstan + | +
+
+ LA
+
+ |
+ + Lao People's Democratic Republic + | +
+
+ LB
+
+ |
+ + Lebanon + | +
+
+ LC
+
+ |
+ + Saint Lucia + | +
+
+ LI
+
+ |
+ + Liechtenstein + | +
+
+ LK
+
+ |
+ + Sri Lanka + | +
+
+ LR
+
+ |
+ + Liberia + | +
+
+ LS
+
+ |
+ + Lesotho + | +
+
+ LT
+
+ |
+ + Lithuania + | +
+
+ LU
+
+ |
+ + Luxembourg + | +
+
+ LV
+
+ |
+ + Latvia + | +
+
+ LY
+
+ |
+ + Libya + | +
+
+ MA
+
+ |
+ + Morocco + | +
+
+ MC
+
+ |
+ + Monaco + | +
+
+ MD
+
+ |
+ + Moldova (the Republic of) + | +
+
+ ME
+
+ |
+ + Montenegro + | +
+
+ MF
+
+ |
+ + Saint Martin (French part) + | +
+
+ MG
+
+ |
+ + Madagascar + | +
+
+ MH
+
+ |
+ + Marshall Islands + | +
+
+ MK
+
+ |
+ + North Macedonia + | +
+
+ ML
+
+ |
+ + Mali + | +
+
+ MM
+
+ |
+ + Myanmar + | +
+
+ MN
+
+ |
+ + Mongolia + | +
+
+ MO
+
+ |
+ + Macao + | +
+
+ MP
+
+ |
+ + Northern Mariana Islands + | +
+
+ MQ
+
+ |
+ + Martinique + | +
+
+ MR
+
+ |
+ + Mauritania + | +
+
+ MS
+
+ |
+ + Montserrat + | +
+
+ MT
+
+ |
+ + Malta + | +
+
+ MU
+
+ |
+ + Mauritius + | +
+
+ MV
+
+ |
+ + Maldives + | +
+
+ MW
+
+ |
+ + Malawi + | +
+
+ MX
+
+ |
+ + Mexico + | +
+
+ MY
+
+ |
+ + Malaysia + | +
+
+ MZ
+
+ |
+ + Mozambique + | +
+
+ NA
+
+ |
+ + Namibia + | +
+
+ NC
+
+ |
+ + New Caledonia + | +
+
+ NE
+
+ |
+ + Niger + | +
+
+ NF
+
+ |
+ + Norfolk Island + | +
+
+ NG
+
+ |
+ + Nigeria + | +
+
+ NI
+
+ |
+ + Nicaragua + | +
+
+ NL
+
+ |
+ + Netherlands + | +
+
+ NO
+
+ |
+ + Norway + | +
+
+ NP
+
+ |
+ + Nepal + | +
+
+ NR
+
+ |
+ + Nauru + | +
+
+ NU
+
+ |
+ + Niue + | +
+
+ NZ
+
+ |
+ + New Zealand + | +
+
+ OM
+
+ |
+ + Oman + | +
+
+ PA
+
+ |
+ + Panama + | +
+
+ PE
+
+ |
+ + Peru + | +
+
+ PF
+
+ |
+ + French Polynesia + | +
+
+ PG
+
+ |
+ + Papua New Guinea + | +
+
+ PH
+
+ |
+ + Philippines + | +
+
+ PK
+
+ |
+ + Pakistan + | +
+
+ PL
+
+ |
+ + Poland + | +
+
+ PM
+
+ |
+ + Saint Pierre and Miquelon + | +
+
+ PN
+
+ |
+ + Pitcairn + | +
+
+ PR
+
+ |
+ + Puerto Rico + | +
+
+ PS
+
+ |
+ + Palestine, State of + | +
+
+ PT
+
+ |
+ + Portugal + | +
+
+ PW
+
+ |
+ + Palau + | +
+
+ PY
+
+ |
+ + Paraguay + | +
+
+ QA
+
+ |
+ + Qatar + | +
+
+ RE
+
+ |
+ + Réunion + | +
+
+ RO
+
+ |
+ + Romania + | +
+
+ RS
+
+ |
+ + Serbia + | +
+
+ RU
+
+ |
+ + Russian Federation + | +
+
+ RW
+
+ |
+ + Rwanda + | +
+
+ SA
+
+ |
+ + Saudi Arabia + | +
+
+ SB
+
+ |
+ + Solomon Islands + | +
+
+ SC
+
+ |
+ + Seychelles + | +
+
+ SD
+
+ |
+ + Sudan + | +
+
+ SE
+
+ |
+ + Sweden + | +
+
+ SG
+
+ |
+ + Singapore + | +
+
+ SH
+
+ |
+ + Saint Helena, Ascension and Tristan da Cunha + | +
+
+ SI
+
+ |
+ + Slovenia + | +
+
+ SJ
+
+ |
+ + Svalbard and Jan Mayen + | +
+
+ SK
+
+ |
+ + Slovakia + | +
+
+ SL
+
+ |
+ + Sierra Leone + | +
+
+ SM
+
+ |
+ + San Marino + | +
+
+ SN
+
+ |
+ + Senegal + | +
+
+ SO
+
+ |
+ + Somalia + | +
+
+ SR
+
+ |
+ + Suriname + | +
+
+ SS
+
+ |
+ + South Sudan + | +
+
+ ST
+
+ |
+ + Sao Tome and Principe + | +
+
+ SV
+
+ |
+ + El Salvador + | +
+
+ SX
+
+ |
+ + Sint Maarten (Dutch part) + | +
+
+ SY
+
+ |
+ + Syrian Arab Republic + | +
+
+ SZ
+
+ |
+ + Eswatini + | +
+
+ TC
+
+ |
+ + Turks and Caicos Islands + | +
+
+ TD
+
+ |
+ + Chad + | +
+
+ TF
+
+ |
+ + French Southern Territories + | +
+
+ TG
+
+ |
+ + Togo + | +
+
+ TH
+
+ |
+ + Thailand + | +
+
+ TJ
+
+ |
+ + Tajikistan + | +
+
+ TK
+
+ |
+ + Tokelau + | +
+
+ TL
+
+ |
+ + Timor-Leste + | +
+
+ TM
+
+ |
+ + Turkmenistan + | +
+
+ TN
+
+ |
+ + Tunisia + | +
+
+ TO
+
+ |
+ + Tonga + | +
+
+ TR
+
+ |
+ + Turkey + | +
+
+ TT
+
+ |
+ + Trinidad and Tobago + | +
+
+ TV
+
+ |
+ + Tuvalu + | +
+
+ TW
+
+ |
+ + Taiwan (Province of China) + | +
+
+ TZ
+
+ |
+ + Tanzania, the United Republic of + | +
+
+ UA
+
+ |
+ + Ukraine + | +
+
+ UG
+
+ |
+ + Uganda + | +
+
+ UM
+
+ |
+ + United States Minor Outlying Islands + | +
+
+ US
+
+ |
+ + United States of America + | +
+
+ UY
+
+ |
+ + Uruguay + | +
+
+ UZ
+
+ |
+ + Uzbekistan + | +
+
+ VA
+
+ |
+ + Holy See + | +
+
+ VC
+
+ |
+ + Saint Vincent and the Grenadines + | +
+
+ VE
+
+ |
+ + Venezuela (Bolivarian Republic of) + | +
+
+ VG
+
+ |
+ + Virgin Islands (British) + | +
+
+ VI
+
+ |
+ + Virgin Islands (U.S.) + | +
+
+ VN
+
+ |
+ + Viet Nam + | +
+
+ VU
+
+ |
+ + Vanuatu + | +
+
+ WF
+
+ |
+ + Wallis and Futuna + | +
+
+ WS
+
+ |
+ + Samoa + | +
+
+ XK
+
+ |
+ + Kosovo + | +
+
+ YE
+
+ |
+ + Yemen + | +
+
+ YT
+
+ |
+ + Mayotte + | +
+
+ ZA
+
+ |
+ + South Africa + | +
+
+ ZM
+
+ |
+ + Zambia + | +
+
+ ZW
+
+ |
+ + Zimbabwe + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/countryCode/master/release-schema.json b/en/extensions/countryCode/master/release-schema.json
new file mode 100644
index 000000000..00ceca881
--- /dev/null
+++ b/en/extensions/countryCode/master/release-schema.json
@@ -0,0 +1,271 @@
+{
+ "definitions": {
+ "Address": {
+ "properties": {
+ "country": {
+ "title": "Country code",
+ "description": "The country, from the closed country codelist. If a country is missing, [create an issue](https://github.com/open-contracting/standard/issues) to discuss the addition of a user-assigned code to the country codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "country.csv",
+ "openCodelist": false,
+ "enum": [
+ "AD",
+ "AE",
+ "AF",
+ "AG",
+ "AI",
+ "AL",
+ "AM",
+ "AO",
+ "AQ",
+ "AR",
+ "AS",
+ "AT",
+ "AU",
+ "AW",
+ "AX",
+ "AZ",
+ "BA",
+ "BB",
+ "BD",
+ "BE",
+ "BF",
+ "BG",
+ "BH",
+ "BI",
+ "BJ",
+ "BL",
+ "BM",
+ "BN",
+ "BO",
+ "BQ",
+ "BR",
+ "BS",
+ "BT",
+ "BV",
+ "BW",
+ "BY",
+ "BZ",
+ "CA",
+ "CC",
+ "CD",
+ "CF",
+ "CG",
+ "CH",
+ "CI",
+ "CK",
+ "CL",
+ "CM",
+ "CN",
+ "CO",
+ "CR",
+ "CU",
+ "CV",
+ "CW",
+ "CX",
+ "CY",
+ "CZ",
+ "DE",
+ "DJ",
+ "DK",
+ "DM",
+ "DO",
+ "DZ",
+ "EC",
+ "EE",
+ "EG",
+ "EH",
+ "ER",
+ "ES",
+ "ET",
+ "FI",
+ "FJ",
+ "FK",
+ "FM",
+ "FO",
+ "FR",
+ "GA",
+ "GB",
+ "GD",
+ "GE",
+ "GF",
+ "GG",
+ "GH",
+ "GI",
+ "GL",
+ "GM",
+ "GN",
+ "GP",
+ "GQ",
+ "GR",
+ "GS",
+ "GT",
+ "GU",
+ "GW",
+ "GY",
+ "HK",
+ "HM",
+ "HN",
+ "HR",
+ "HT",
+ "HU",
+ "ID",
+ "IE",
+ "IL",
+ "IM",
+ "IN",
+ "IO",
+ "IQ",
+ "IR",
+ "IS",
+ "IT",
+ "JE",
+ "JM",
+ "JO",
+ "JP",
+ "KE",
+ "KG",
+ "KH",
+ "KI",
+ "KM",
+ "KN",
+ "KP",
+ "KR",
+ "KW",
+ "KY",
+ "KZ",
+ "LA",
+ "LB",
+ "LC",
+ "LI",
+ "LK",
+ "LR",
+ "LS",
+ "LT",
+ "LU",
+ "LV",
+ "LY",
+ "MA",
+ "MC",
+ "MD",
+ "ME",
+ "MF",
+ "MG",
+ "MH",
+ "MK",
+ "ML",
+ "MM",
+ "MN",
+ "MO",
+ "MP",
+ "MQ",
+ "MR",
+ "MS",
+ "MT",
+ "MU",
+ "MV",
+ "MW",
+ "MX",
+ "MY",
+ "MZ",
+ "NA",
+ "NC",
+ "NE",
+ "NF",
+ "NG",
+ "NI",
+ "NL",
+ "NO",
+ "NP",
+ "NR",
+ "NU",
+ "NZ",
+ "OM",
+ "PA",
+ "PE",
+ "PF",
+ "PG",
+ "PH",
+ "PK",
+ "PL",
+ "PM",
+ "PN",
+ "PR",
+ "PS",
+ "PT",
+ "PW",
+ "PY",
+ "QA",
+ "RE",
+ "RO",
+ "RS",
+ "RU",
+ "RW",
+ "SA",
+ "SB",
+ "SC",
+ "SD",
+ "SE",
+ "SG",
+ "SH",
+ "SI",
+ "SJ",
+ "SK",
+ "SL",
+ "SM",
+ "SN",
+ "SO",
+ "SR",
+ "SS",
+ "ST",
+ "SV",
+ "SX",
+ "SY",
+ "SZ",
+ "TC",
+ "TD",
+ "TF",
+ "TG",
+ "TH",
+ "TJ",
+ "TK",
+ "TL",
+ "TM",
+ "TN",
+ "TO",
+ "TR",
+ "TT",
+ "TV",
+ "TW",
+ "TZ",
+ "UA",
+ "UG",
+ "UM",
+ "US",
+ "UY",
+ "UZ",
+ "VA",
+ "VC",
+ "VE",
+ "VG",
+ "VI",
+ "VN",
+ "VU",
+ "WF",
+ "WS",
+ "XK",
+ "YE",
+ "YT",
+ "ZA",
+ "ZM",
+ "ZW",
+ null
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/countryCode/master/schema/index.html b/en/extensions/countryCode/master/schema/index.html
new file mode 100644
index 000000000..b868259f8
--- /dev/null
+++ b/en/extensions/countryCode/master/schema/index.html
@@ -0,0 +1,236 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Country code +
+ ++ Adds a country code field to the address object. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a country code field to the address object.
+Legal context
+In the European Union, this extension's fields correspond to eForms BT-514 (Organisation Country Code), BT-5141 (Place Country Code). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+{
+ "parties": [
+ {
+ "id": "GB-LAC-E09000003",
+ "name": "London Borough of Barnet",
+ "address": {
+ "streetAddress": "4, North London Business Park, Oakleigh Rd S",
+ "locality": "London",
+ "region": "London",
+ "postalCode": "N11 1NP",
+ "countryName": "United Kingdom",
+ "country": "GB"
+ }
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+If you need to use a user-assigned code, create an issue to discuss its addition to the codelist.
+Changelog
+2023-02-07
+-
+
- Rename
countryCodetocountryto match OCDS 1.2.
+
This extension was originally discussed as part of the OCDS for EU profile, in pull requests and in https://github.com/open-contracting/standard/issues/524.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/coveredBy/index.html b/en/extensions/coveredBy/index.html
new file mode 100644
index 000000000..f6969b2a4
--- /dev/null
+++ b/en/extensions/coveredBy/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Country code +
+ ++ Adds a country code field to the address object. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Address +
+ +
+ The extension defines these fields in the Address object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ country
+
+ |
+ + Country code + | +
+ The country, from the closed country codelist. If a country is missing, create an issue to discuss the addition of a user-assigned code to the country codelist. + + |
+ + string from closed country codelist + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/coveredBy/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/coveredBy/master/extension.json b/en/extensions/coveredBy/master/extension.json
new file mode 100644
index 000000000..d3ff1b08a
--- /dev/null
+++ b/en/extensions/coveredBy/master/extension.json
@@ -0,0 +1,29 @@
+{
+ "name": {
+ "en": "Covered By",
+ "es": "Cubierto por"
+ },
+ "description": {
+ "en": "Adds a field to indicate the treaties that the contracting process is covered by.",
+ "es": "Agregar un campo para indicar los tratados que cubre el proceso de contrataci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/coveredBy/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "coveredBy.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/en/extensions/coveredBy/master/index.html b/en/extensions/coveredBy/master/index.html
new file mode 100644
index 000000000..45b09ca60
--- /dev/null
+++ b/en/extensions/coveredBy/master/index.html
@@ -0,0 +1,349 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Covered By +
+ ++ Adds a field to indicate the treaties that the contracting process is covered by. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ coveredBy.csv +
+ +
+ You can download the coveredBy.csv file in English.
+
| + Code + | ++ Title + | +
|---|---|
+
+ GPA
+
+ |
+ + Agreement on Government Procurement + | +
+
+ EU-CVD
+
+ |
+ + European Parliament and Council 2009/33/EC (Clean Vehicles Directive) + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/coveredBy/master/release-schema.json b/en/extensions/coveredBy/master/release-schema.json
new file mode 100644
index 000000000..40836d00b
--- /dev/null
+++ b/en/extensions/coveredBy/master/release-schema.json
@@ -0,0 +1,44 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "coveredBy": {
+ "title": "Covered by",
+ "description": "The international legal instruments that the contracting process is covered by.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "coveredBy.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "coveredBy": {
+ "title": "Covered by",
+ "description": "The international legal instruments that the lot is covered by.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "coveredBy.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/coveredBy/master/schema/index.html b/en/extensions/coveredBy/master/schema/index.html
new file mode 100644
index 000000000..d01f94951
--- /dev/null
+++ b/en/extensions/coveredBy/master/schema/index.html
@@ -0,0 +1,287 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Covered By +
+ ++ Adds a field to indicate the treaties that the contracting process is covered by. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds a field to indicate the international legal instruments that the contracting process is covered by.
+For example, the Agreement on Government Procurement (GPA) is a treaty that requires members to indicate whether a contracting process is covered by it. The Clean Vehicles Directive is a legal act that provides for member states of the European Union to indicate associated information in procurement notices. The coveredBy field should be used to meet such requirements.
To disclose the laws or regulations that govern the contracting process and that grant legal authority to the procuring entity, use the legalBasis extension instead.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
If you need to refer to a treaty that is not in the coveredBy codelist:
-
+
- If the treaty has a national or subnational scope, pick a relevant ISO 3166-1 alpha-2 country code (e.g "CA" for Canada). +
- If the treaty has a subnational scope, pick a relevant ISO 3166-2 region code (e.g "NT" for Northern Territories, a province of Canada). +
- Concatenate the code(s) to the acronym of the treaty, separating each part with a dash (e.g "CA-NT-BIP"). +
- Add this code to the
coveredByarray.
+ - Document the new code (see Extending open codelists). +
Legal context
+The Revised Agreement on Government Procurement (GPA) includes: "each notice of intended procurement shall include … l. an indication that the procurement is covered by this Agreement."
+The European Union is a party to the GPA, and as such its Directive 2014/24/EU (Public contracts — setting out clear ground rules) includes: "Part C: Information to be included in contract notices … 29. Indication whether the contract is covered by the GPA."
+Example
+The coveredBy field is an array of strings, whose values are selected from the coveredBy.csv open codelist.
Tender
+{
+ "tender": {
+ "coveredBy": [
+ "GPA"
+ ]
+ }
+}
+Lot
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "coveredBy": [
+ "EU-CVD"
+ ]
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-03-02
+-
+
- Add 'EU-CVD' to the
coveredBycodelist.
+ - Add
coveredByto theLotobject.
+
2020-11-04
+-
+
- Add guidance on the creation of new codes for the
coveredBycodelist.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/designContest/index.html b/en/extensions/designContest/index.html
new file mode 100644
index 000000000..f18358b52
--- /dev/null
+++ b/en/extensions/designContest/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Covered By +
+ ++ Adds a field to indicate the treaties that the contracting process is covered by. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ coveredBy
+
+ |
+ + Covered by + | +
+ The international legal instruments that the contracting process is covered by. + + |
+ + array of strings from open coveredBy codelist + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ coveredBy
+
+ |
+ + Covered by + | +
+ The international legal instruments that the lot is covered by. + + |
+ + array of strings from open coveredBy codelist + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/designContest/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/designContest/master/release-schema.json b/en/extensions/designContest/master/release-schema.json
new file mode 100644
index 000000000..853ab6299
--- /dev/null
+++ b/en/extensions/designContest/master/release-schema.json
@@ -0,0 +1,167 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "designContest": {
+ "title": "Design contest",
+ "description": "Information about the organization of a design contest.",
+ "$ref": "#/definitions/DesignContest"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "designContest": {
+ "title": "Design contest",
+ "description": "Information about the organization of a design contest.",
+ "$ref": "#/definitions/DesignContest"
+ }
+ }
+ },
+ "DesignContest": {
+ "title": "Design contest",
+ "description": "Information about the organization of a design contest.",
+ "type": "object",
+ "properties": {
+ "selectedParticipants": {
+ "title": "Selected participants",
+ "description": "The organizations that have already been selected to participate in the design contest.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "hasPrizes": {
+ "title": "Has prizes",
+ "description": "Whether prizes will be awarded in the design contest.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "prizes": {
+ "title": "Prizes",
+ "description": "Information about the prizes awarded in the design contest.",
+ "$ref": "#/definitions/Prizes"
+ },
+ "rewardsDetails": {
+ "title": "Rewards details",
+ "description": "The details and conditions of the payments to be made to the participants.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "followUpContracts": {
+ "title": "Follow-up contracts",
+ "description": "Whether any contracts following the design contest will be awarded to the winner or winners of the design contest.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "bindingJuryDecision": {
+ "title": "Binding jury decision",
+ "description": "Whether the jury\u2019s decision is binding on the procuring entity.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "juryMembers": {
+ "title": "Jury members",
+ "description": "The members of the jury.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/JuryMember"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "JuryMember": {
+ "title": "Jury member",
+ "description": "Member of the jury.",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Name",
+ "description": "The name of the jury member.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Prizes": {
+ "title": "Prizes",
+ "description": "Information about the prizes awarded in a design contest.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "The description of the prizes.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "details": {
+ "title": "Details",
+ "description": "Information about the individual prizes.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Prize"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Prize": {
+ "title": "Prize",
+ "description": "Information about an individual prize awarded in a design contest.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "The locally unique identifier for the prize.",
+ "type": [
+ "string"
+ ],
+ "versionId": true,
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "The description of the prize.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "value": {
+ "title": "Value",
+ "description": "The value of the prize.",
+ "$ref": "#/definitions/Value"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/designContest/master/schema/index.html b/en/extensions/designContest/master/schema/index.html
new file mode 100644
index 000000000..1821f6759
--- /dev/null
+++ b/en/extensions/designContest/master/schema/index.html
@@ -0,0 +1,639 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Design contest +
+ ++ Adds an object to the tender object to describe a design contest. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an object to the tender and lot objects to describe a design contest.
+Legal context
+In the European Union, this extension's fields correspond to eForms BG-704 (Reward and Jury) and BG-44 (Prize) and Title III, Chapter II of Directive 2014/24/EU. For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Examples
+A contracting process with a single prize.
+{
+ "tender": {
+ "designContest": {
+ "selectedParticipants": [
+ {
+ "id": "1",
+ "name": "Brigitte Hermon"
+ },
+ {
+ "id": "2",
+ "name": "Paolo Travino"
+ }
+ ],
+ "hasPrizes": true,
+ "prizes": {
+ "description": "The winner(s) will receive a prize of EUR 3,000.00 (VAT free).",
+ "details": [
+ {
+ "id": "1",
+ "value": {
+ "amount": 3000,
+ "currency": "EUR"
+ }
+ }
+ ]
+ },
+ "rewardsDetails": "The payment is made by administrative mandate within 30 days in accordance with the regulations in force.",
+ "followUpContracts": true,
+ "bindingJuryDecision": true,
+ "juryMembers": [
+ {
+ "name": "Karla Schaffer"
+ },
+ {
+ "name": "Bulat Kazinsky"
+ },
+ {
+ "name": "Alexandra Martinez"
+ },
+ {
+ "name": "Scott MacDougall"
+ }
+ ]
+ }
+ }
+}
+Lot
+A lot with multiple prizes.
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "designContest": {
+ "selectedParticipants": [
+ {
+ "id": "1",
+ "name": "Brigitte Hermon"
+ },
+ {
+ "id": "2",
+ "name": "Paolo Travino"
+ }
+ ],
+ "hasPrizes": true,
+ "prizes": {
+ "details": [
+ {
+ "id": "1",
+ "description": "A lump sum indemnity of an amount identical to that paid to unsuccessful competitors will be paid to the winning team in the form of an advance on the project management contract at the end of the competition; this sum being credited to the amount of fees to be collected subsequently under the project management contract.",
+ "value": {
+ "amount": 3000,
+ "currency": "EUR"
+ }
+ },
+ {
+ "id": "2",
+ "description": "The two competitors (candidates admitted to compete) will receive a maximum fixed compensation of 10,000 EUR excluding tax. For the services provided, subject to the admissibility of their services with regard to the rules of the competition and compliance with the program. Compensation is fixed, in accordance with the provisions of article R. 2172-4 of the public procurement code, the buyer, on the proposal of the jury, reserves the right, in the case of a project that he deems incomplete or whose performances do not comply with the competition rules and/or the programme, to totally or partially cancel the indemnity.",
+ "value": {
+ "amount": 10000,
+ "currency": "EUR"
+ }
+ }
+ ]
+ },
+ "rewardsDetails": "The payment is made by administrative mandate within 30 days in accordance with the regulations in force.",
+ "followUpContracts": true,
+ "bindingJuryDecision": true,
+ "juryMembers": [
+ {
+ "name": "Karla Schaffer"
+ },
+ {
+ "name": "Bulat Kazinsky"
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-03-10
+-
+
- Add
lots.designContestobject.
+ - Add
detailsarray toDesignContest.prizesarray, to describe theid,descriptionandvalueof each prize.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/document_publisher/index.html b/en/extensions/document_publisher/index.html
new file mode 100644
index 000000000..420a26bce
--- /dev/null
+++ b/en/extensions/document_publisher/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Design contest +
+ ++ Adds an object to the tender object to describe a design contest. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ designContest
+
+ |
+ + Design contest + | +
+ Information about the organization of a design contest. + + |
+ + DesignContest object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ designContest
+
+ |
+ + Design contest + | +
+ Information about the organization of a design contest. + + |
+ + DesignContest object + | +
+ DesignContest +
+ +
+ The extension defines a new DesignContest object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ selectedParticipants
+
+ |
+ + Selected participants + | +
+ The organizations that have already been selected to participate in the design contest. + + |
+ + array of OrganizationReference objects + | +
+
+ hasPrizes
+
+ |
+ + Has prizes + | +
+ Whether prizes will be awarded in the design contest. + + |
+ + boolean + | +
+
+ prizes
+
+ |
+ + Prizes + | +
+ Information about the prizes awarded in the design contest. + + |
+ + Prizes object + | +
+
+ rewardsDetails
+
+ |
+ + Rewards details + | +
+ The details and conditions of the payments to be made to the participants. + + |
+ + string + | +
+
+ followUpContracts
+
+ |
+ + Follow-up contracts + | +
+ Whether any contracts following the design contest will be awarded to the winner or winners of the design contest. + + |
+ + boolean + | +
+
+ bindingJuryDecision
+
+ |
+ + Binding jury decision + | +
+ Whether the jury’s decision is binding on the procuring entity. + + |
+ + boolean + | +
+
+ juryMembers
+
+ |
+ + Jury members + | +
+ The members of the jury. + + |
+ + array of JuryMember objects + | +
+ JuryMember +
+ +
+ The extension defines a new JuryMember object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ name
+
+ |
+ + Name + | +
+ The name of the jury member. + + |
+ + string + | +
+ Prizes +
+ +
+ The extension defines a new Prizes object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ The description of the prizes. + + |
+ + string + | +
+
+ details
+
+ |
+ + Details + | +
+ Information about the individual prizes. + + |
+ + array of Prize objects + | +
+ Prize +
+ +
+ The extension defines a new Prize object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ The locally unique identifier for the prize. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ The description of the prize. + + |
+ + string + | +
+
+ value
+
+ |
+ + Value + | +
+ The value of the prize. + + |
+ + Value object + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/document_publisher/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/document_publisher/master/extension.json b/en/extensions/document_publisher/master/extension.json
new file mode 100644
index 000000000..78a87174c
--- /dev/null
+++ b/en/extensions/document_publisher/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Document publisher",
+ "es": "Document publisher"
+ },
+ "description": {
+ "en": "Adds a publisher field to the document object.",
+ "es": "Adds a publisher field to the document object."
+ },
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting-extensions/ocds_document_publisher_extension"
+ },
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+partyRole.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/document_publisher/master/index.html b/en/extensions/document_publisher/master/index.html
new file mode 100644
index 000000000..667dc0581
--- /dev/null
+++ b/en/extensions/document_publisher/master/index.html
@@ -0,0 +1,307 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Document publisher +
+ ++ Adds a publisher field to the document object. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ informationService
+
+ |
+ + Information service + | +
+ An organization that can provide information regarding specific aspects of the contracting process. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/document_publisher/master/release-schema.json b/en/extensions/document_publisher/master/release-schema.json
new file mode 100644
index 000000000..fe549fb2c
--- /dev/null
+++ b/en/extensions/document_publisher/master/release-schema.json
@@ -0,0 +1,13 @@
+{
+ "definitions": {
+ "Document": {
+ "properties": {
+ "publisher": {
+ "title": "Publisher",
+ "description": "The organization responsible for making the document available.",
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/document_publisher/master/schema/index.html b/en/extensions/document_publisher/master/schema/index.html
new file mode 100644
index 000000000..1d8ed0fcb
--- /dev/null
+++ b/en/extensions/document_publisher/master/schema/index.html
@@ -0,0 +1,236 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Document publisher +
+ ++ Adds a publisher field to the document object. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a publisher field to the document object and an 'informationService' role to indicate the organization responsible for making the document available.
+Usage
+For each organization referenced by a Document.publisher field, add the 'informationService' code to its roles array.
Legal context
+In the European Union, this extension's fields correspond to eForms OPT-301 (Party ID reference). For correspondences to eForms fields, see OCDS for eForms.
+Example
+{
+ "parties": [
+ {
+ "id": "ORG-0001",
+ "roles": [
+ "informationService"
+ ]
+ }
+ ],
+ "tender": {
+ "id": "1",
+ "documents": [
+ {
+ "id": "1",
+ "publisher": {
+ "id": "ORG-0001"
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/documentation_details/index.html b/en/extensions/documentation_details/index.html
new file mode 100644
index 000000000..aebcfabf1
--- /dev/null
+++ b/en/extensions/documentation_details/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Document publisher +
+ ++ Adds a publisher field to the document object. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Document +
+ +
+ The extension defines these fields in the Document object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ publisher
+
+ |
+ + Publisher + | +
+ The organization responsible for making the document available. + + |
+ + OrganizationReference object + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/documentation_details/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/documentation_details/master/codelists/language.csv b/en/extensions/documentation_details/master/codelists/language.csv
new file mode 100644
index 000000000..5749f4af7
--- /dev/null
+++ b/en/extensions/documentation_details/master/codelists/language.csv
@@ -0,0 +1,185 @@
+Code,Title
+aa,Afar
+ab,Abkhazian
+ae,Avestan
+af,Afrikaans
+ak,Akan
+am,Amharic
+an,Aragonese
+ar,Arabic
+as,Assamese
+av,Avaric
+ay,Aymara
+az,Azerbaijani
+ba,Bashkir
+be,Belarusian
+bg,Bulgarian
+bh,Bihari languages
+bi,Bislama
+bm,Bambara
+bn,Bengali
+bo,Tibetan
+br,Breton
+bs,Bosnian
+ca,"Catalan, Valencian"
+ce,Chechen
+ch,Chamorro
+co,Corsican
+cr,Cree
+cs,Czech
+cu,"Church Slavic, Old Slavonic, Church Slavonic, Old Bulgarian, Old Church Slavonic"
+cv,Chuvash
+cy,Welsh
+da,Danish
+de,German
+dv,"Divehi, Dhivehi, Maldivian"
+dz,Dzongkha
+ee,Ewe
+el,Modern Greek
+en,English
+eo,Esperanto
+es,"Spanish, Castilian"
+et,Estonian
+eu,Basque
+fa,Persian
+ff,Fulah
+fi,Finnish
+fj,Fijian
+fo,Faroese
+fr,French
+fy,Western Frisian
+ga,Irish
+gd,"Gaelic, Scottish Gaelic"
+gl,Galician
+gn,Guarani
+gu,Gujarati
+gv,Manx
+ha,Hausa
+he,Hebrew
+hi,Hindi
+ho,Hiri Motu
+hr,Croatian
+ht,"Haitian, Haitian Creole"
+hu,Hungarian
+hy,Armenian
+hz,Herero
+ia,Interlingua
+id,Indonesian
+ie,"Interlingue, Occidental"
+ig,Igbo
+ii,"Sichuan Yi, Nuosu"
+ik,Inupiaq
+io,Ido
+is,Icelandic
+it,Italian
+iu,Inuktitut
+ja,Japanese
+jv,Javanese
+ka,Georgian
+kg,Kongo
+ki,"Kikuyu, Gikuyu"
+kj,"Kuanyama, Kwanyama"
+kk,Kazakh
+kl,"Kalaallisut, Greenlandic"
+km,Central Khmer
+kn,Kannada
+ko,Korean
+kr,Kanuri
+ks,Kashmiri
+ku,Kurdish
+kv,Komi
+kw,Cornish
+ky,"Kirghiz, Kyrgyz"
+la,Latin
+lb,"Luxembourgish, Letzeburgesch"
+lg,Ganda
+li,"Limburgan, Limburger, Limburgish"
+ln,Lingala
+lo,Lao
+lt,Lithuanian
+lu,Luba-Katanga
+lv,Latvian
+mg,Malagasy
+mh,Marshallese
+mi,Maori
+mk,Macedonian
+ml,Malayalam
+mn,Mongolian
+mr,Marathi
+ms,Malay
+mt,Maltese
+my,Burmese
+na,Nauru
+nb,Norwegian Bokmål
+nd,North Ndebele
+ne,Nepali
+ng,Ndonga
+nl,"Dutch, Flemish"
+nn,Norwegian Nynorsk
+no,Norwegian
+nr,South Ndebele
+nv,"Navajo, Navaho"
+ny,"Chichewa, Chewa, Nyanja"
+oc,Occitan
+oj,Ojibwa
+om,Oromo
+or,Oriya
+os,"Ossetian, Ossetic"
+pa,"Panjabi, Punjabi"
+pi,Pali
+pl,Polish
+ps,"Pushto, Pashto"
+pt,Portuguese
+qu,Quechua
+rm,Romansh
+rn,Rundi
+ro,"Romanian, Moldavian, Moldovan"
+ru,Russian
+rw,Kinyarwanda
+sa,Sanskrit
+sc,Sardinian
+sd,Sindhi
+se,Northern Sami
+sg,Sango
+si,"Sinhala, Sinhalese"
+sk,Slovak
+sl,Slovenian
+sm,Samoan
+sn,Shona
+so,Somali
+sq,Albanian
+sr,Serbian
+ss,Swati
+st,Southern Sotho
+su,Sundanese
+sv,Swedish
+sw,Swahili
+ta,Tamil
+te,Telugu
+tg,Tajik
+th,Thai
+ti,Tigrinya
+tk,Turkmen
+tl,Tagalog
+tn,Tswana
+to,Tonga
+tr,Turkish
+ts,Tsonga
+tt,Tatar
+tw,Twi
+ty,Tahitian
+ug,"Uighur, Uyghur"
+uk,Ukrainian
+ur,Urdu
+uz,Uzbek
+ve,Venda
+vi,Vietnamese
+vo,Volapük
+wa,Walloon
+wo,Wolof
+xh,Xhosa
+yi,Yiddish
+yo,Yoruba
+za,"Zhuang, Chuang"
+zh,Chinese
+zu,Zulu
diff --git a/en/extensions/documentation_details/master/extension.json b/en/extensions/documentation_details/master/extension.json
new file mode 100644
index 000000000..fac7335b0
--- /dev/null
+++ b/en/extensions/documentation_details/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Document Details",
+ "es": "Detalles de Documentos"
+ },
+ "description": {
+ "en": "Adds fields to the document object for page references, access details and author information.",
+ "es": "Agrega campos al objeto document para referencias a p\u00e1ginas, acceso a detalles e informaci\u00f3n del autor."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/documentation_details/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "language.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/documentation_details/master/index.html b/en/extensions/documentation_details/master/index.html
new file mode 100644
index 000000000..6f97a00a5
--- /dev/null
+++ b/en/extensions/documentation_details/master/index.html
@@ -0,0 +1,333 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Document Details +
+ ++ Adds fields to the document object for page references, access details and author information. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ language.csv +
+ +
+ You can download the language.csv file in English.
+
| + Code + | ++ Title + | +
|---|---|
+
+ aa
+
+ |
+ + Afar + | +
+
+ ab
+
+ |
+ + Abkhazian + | +
+
+ ae
+
+ |
+ + Avestan + | +
+
+ af
+
+ |
+ + Afrikaans + | +
+
+ ak
+
+ |
+ + Akan + | +
+
+ am
+
+ |
+ + Amharic + | +
+
+ an
+
+ |
+ + Aragonese + | +
+
+ ar
+
+ |
+ + Arabic + | +
+
+ as
+
+ |
+ + Assamese + | +
+
+ av
+
+ |
+ + Avaric + | +
+
+ ay
+
+ |
+ + Aymara + | +
+
+ az
+
+ |
+ + Azerbaijani + | +
+
+ ba
+
+ |
+ + Bashkir + | +
+
+ be
+
+ |
+ + Belarusian + | +
+
+ bg
+
+ |
+ + Bulgarian + | +
+
+ bh
+
+ |
+ + Bihari languages + | +
+
+ bi
+
+ |
+ + Bislama + | +
+
+ bm
+
+ |
+ + Bambara + | +
+
+ bn
+
+ |
+ + Bengali + | +
+
+ bo
+
+ |
+ + Tibetan + | +
+
+ br
+
+ |
+ + Breton + | +
+
+ bs
+
+ |
+ + Bosnian + | +
+
+ ca
+
+ |
+ + Catalan, Valencian + | +
+
+ ce
+
+ |
+ + Chechen + | +
+
+ ch
+
+ |
+ + Chamorro + | +
+
+ co
+
+ |
+ + Corsican + | +
+
+ cr
+
+ |
+ + Cree + | +
+
+ cs
+
+ |
+ + Czech + | +
+
+ cu
+
+ |
+ + Church Slavic, Old Slavonic, Church Slavonic, Old Bulgarian, Old Church Slavonic + | +
+
+ cv
+
+ |
+ + Chuvash + | +
+
+ cy
+
+ |
+ + Welsh + | +
+
+ da
+
+ |
+ + Danish + | +
+
+ de
+
+ |
+ + German + | +
+
+ dv
+
+ |
+ + Divehi, Dhivehi, Maldivian + | +
+
+ dz
+
+ |
+ + Dzongkha + | +
+
+ ee
+
+ |
+ + Ewe + | +
+
+ el
+
+ |
+ + Modern Greek + | +
+
+ en
+
+ |
+ + English + | +
+
+ eo
+
+ |
+ + Esperanto + | +
+
+ es
+
+ |
+ + Spanish, Castilian + | +
+
+ et
+
+ |
+ + Estonian + | +
+
+ eu
+
+ |
+ + Basque + | +
+
+ fa
+
+ |
+ + Persian + | +
+
+ ff
+
+ |
+ + Fulah + | +
+
+ fi
+
+ |
+ + Finnish + | +
+
+ fj
+
+ |
+ + Fijian + | +
+
+ fo
+
+ |
+ + Faroese + | +
+
+ fr
+
+ |
+ + French + | +
+
+ fy
+
+ |
+ + Western Frisian + | +
+
+ ga
+
+ |
+ + Irish + | +
+
+ gd
+
+ |
+ + Gaelic, Scottish Gaelic + | +
+
+ gl
+
+ |
+ + Galician + | +
+
+ gn
+
+ |
+ + Guarani + | +
+
+ gu
+
+ |
+ + Gujarati + | +
+
+ gv
+
+ |
+ + Manx + | +
+
+ ha
+
+ |
+ + Hausa + | +
+
+ he
+
+ |
+ + Hebrew + | +
+
+ hi
+
+ |
+ + Hindi + | +
+
+ ho
+
+ |
+ + Hiri Motu + | +
+
+ hr
+
+ |
+ + Croatian + | +
+
+ ht
+
+ |
+ + Haitian, Haitian Creole + | +
+
+ hu
+
+ |
+ + Hungarian + | +
+
+ hy
+
+ |
+ + Armenian + | +
+
+ hz
+
+ |
+ + Herero + | +
+
+ ia
+
+ |
+ + Interlingua + | +
+
+ id
+
+ |
+ + Indonesian + | +
+
+ ie
+
+ |
+ + Interlingue, Occidental + | +
+
+ ig
+
+ |
+ + Igbo + | +
+
+ ii
+
+ |
+ + Sichuan Yi, Nuosu + | +
+
+ ik
+
+ |
+ + Inupiaq + | +
+
+ io
+
+ |
+ + Ido + | +
+
+ is
+
+ |
+ + Icelandic + | +
+
+ it
+
+ |
+ + Italian + | +
+
+ iu
+
+ |
+ + Inuktitut + | +
+
+ ja
+
+ |
+ + Japanese + | +
+
+ jv
+
+ |
+ + Javanese + | +
+
+ ka
+
+ |
+ + Georgian + | +
+
+ kg
+
+ |
+ + Kongo + | +
+
+ ki
+
+ |
+ + Kikuyu, Gikuyu + | +
+
+ kj
+
+ |
+ + Kuanyama, Kwanyama + | +
+
+ kk
+
+ |
+ + Kazakh + | +
+
+ kl
+
+ |
+ + Kalaallisut, Greenlandic + | +
+
+ km
+
+ |
+ + Central Khmer + | +
+
+ kn
+
+ |
+ + Kannada + | +
+
+ ko
+
+ |
+ + Korean + | +
+
+ kr
+
+ |
+ + Kanuri + | +
+
+ ks
+
+ |
+ + Kashmiri + | +
+
+ ku
+
+ |
+ + Kurdish + | +
+
+ kv
+
+ |
+ + Komi + | +
+
+ kw
+
+ |
+ + Cornish + | +
+
+ ky
+
+ |
+ + Kirghiz, Kyrgyz + | +
+
+ la
+
+ |
+ + Latin + | +
+
+ lb
+
+ |
+ + Luxembourgish, Letzeburgesch + | +
+
+ lg
+
+ |
+ + Ganda + | +
+
+ li
+
+ |
+ + Limburgan, Limburger, Limburgish + | +
+
+ ln
+
+ |
+ + Lingala + | +
+
+ lo
+
+ |
+ + Lao + | +
+
+ lt
+
+ |
+ + Lithuanian + | +
+
+ lu
+
+ |
+ + Luba-Katanga + | +
+
+ lv
+
+ |
+ + Latvian + | +
+
+ mg
+
+ |
+ + Malagasy + | +
+
+ mh
+
+ |
+ + Marshallese + | +
+
+ mi
+
+ |
+ + Maori + | +
+
+ mk
+
+ |
+ + Macedonian + | +
+
+ ml
+
+ |
+ + Malayalam + | +
+
+ mn
+
+ |
+ + Mongolian + | +
+
+ mr
+
+ |
+ + Marathi + | +
+
+ ms
+
+ |
+ + Malay + | +
+
+ mt
+
+ |
+ + Maltese + | +
+
+ my
+
+ |
+ + Burmese + | +
+
+ na
+
+ |
+ + Nauru + | +
+
+ nb
+
+ |
+ + Norwegian Bokmål + | +
+
+ nd
+
+ |
+ + North Ndebele + | +
+
+ ne
+
+ |
+ + Nepali + | +
+
+ ng
+
+ |
+ + Ndonga + | +
+
+ nl
+
+ |
+ + Dutch, Flemish + | +
+
+ nn
+
+ |
+ + Norwegian Nynorsk + | +
+
+ no
+
+ |
+ + Norwegian + | +
+
+ nr
+
+ |
+ + South Ndebele + | +
+
+ nv
+
+ |
+ + Navajo, Navaho + | +
+
+ ny
+
+ |
+ + Chichewa, Chewa, Nyanja + | +
+
+ oc
+
+ |
+ + Occitan + | +
+
+ oj
+
+ |
+ + Ojibwa + | +
+
+ om
+
+ |
+ + Oromo + | +
+
+ or
+
+ |
+ + Oriya + | +
+
+ os
+
+ |
+ + Ossetian, Ossetic + | +
+
+ pa
+
+ |
+ + Panjabi, Punjabi + | +
+
+ pi
+
+ |
+ + Pali + | +
+
+ pl
+
+ |
+ + Polish + | +
+
+ ps
+
+ |
+ + Pushto, Pashto + | +
+
+ pt
+
+ |
+ + Portuguese + | +
+
+ qu
+
+ |
+ + Quechua + | +
+
+ rm
+
+ |
+ + Romansh + | +
+
+ rn
+
+ |
+ + Rundi + | +
+
+ ro
+
+ |
+ + Romanian, Moldavian, Moldovan + | +
+
+ ru
+
+ |
+ + Russian + | +
+
+ rw
+
+ |
+ + Kinyarwanda + | +
+
+ sa
+
+ |
+ + Sanskrit + | +
+
+ sc
+
+ |
+ + Sardinian + | +
+
+ sd
+
+ |
+ + Sindhi + | +
+
+ se
+
+ |
+ + Northern Sami + | +
+
+ sg
+
+ |
+ + Sango + | +
+
+ si
+
+ |
+ + Sinhala, Sinhalese + | +
+
+ sk
+
+ |
+ + Slovak + | +
+
+ sl
+
+ |
+ + Slovenian + | +
+
+ sm
+
+ |
+ + Samoan + | +
+
+ sn
+
+ |
+ + Shona + | +
+
+ so
+
+ |
+ + Somali + | +
+
+ sq
+
+ |
+ + Albanian + | +
+
+ sr
+
+ |
+ + Serbian + | +
+
+ ss
+
+ |
+ + Swati + | +
+
+ st
+
+ |
+ + Southern Sotho + | +
+
+ su
+
+ |
+ + Sundanese + | +
+
+ sv
+
+ |
+ + Swedish + | +
+
+ sw
+
+ |
+ + Swahili + | +
+
+ ta
+
+ |
+ + Tamil + | +
+
+ te
+
+ |
+ + Telugu + | +
+
+ tg
+
+ |
+ + Tajik + | +
+
+ th
+
+ |
+ + Thai + | +
+
+ ti
+
+ |
+ + Tigrinya + | +
+
+ tk
+
+ |
+ + Turkmen + | +
+
+ tl
+
+ |
+ + Tagalog + | +
+
+ tn
+
+ |
+ + Tswana + | +
+
+ to
+
+ |
+ + Tonga + | +
+
+ tr
+
+ |
+ + Turkish + | +
+
+ ts
+
+ |
+ + Tsonga + | +
+
+ tt
+
+ |
+ + Tatar + | +
+
+ tw
+
+ |
+ + Twi + | +
+
+ ty
+
+ |
+ + Tahitian + | +
+
+ ug
+
+ |
+ + Uighur, Uyghur + | +
+
+ uk
+
+ |
+ + Ukrainian + | +
+
+ ur
+
+ |
+ + Urdu + | +
+
+ uz
+
+ |
+ + Uzbek + | +
+
+ ve
+
+ |
+ + Venda + | +
+
+ vi
+
+ |
+ + Vietnamese + | +
+
+ vo
+
+ |
+ + Volapük + | +
+
+ wa
+
+ |
+ + Walloon + | +
+
+ wo
+
+ |
+ + Wolof + | +
+
+ xh
+
+ |
+ + Xhosa + | +
+
+ yi
+
+ |
+ + Yiddish + | +
+
+ yo
+
+ |
+ + Yoruba + | +
+
+ za
+
+ |
+ + Zhuang, Chuang + | +
+
+ zh
+
+ |
+ + Chinese + | +
+
+ zu
+
+ |
+ + Zulu + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/documentation_details/master/release-schema.json b/en/extensions/documentation_details/master/release-schema.json
new file mode 100644
index 000000000..3e1f33531
--- /dev/null
+++ b/en/extensions/documentation_details/master/release-schema.json
@@ -0,0 +1,69 @@
+{
+ "definitions": {
+ "Document": {
+ "properties": {
+ "pageStart": {
+ "title": "Page start",
+ "description": "When the information referenced exists within a large document, indicate the first page on which it can be found. This should refer to the printed page number, not the page number reported by software applications.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "pageEnd": {
+ "title": "Page end",
+ "description": "When the information referenced exists within a large document, indicate the last page on which it can be found. This should refer to the printed page number, not the page number reported by software applications.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "accessDetails": {
+ "title": "Access details",
+ "description": "A description of any special arrangements needed to access this document, for example: registering for access, paying a fee, or visiting a location to inspect the document.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "accessDetailsURL": {
+ "title": "Access details URL",
+ "description": "A web address for information on any special arrangements needed to access the document.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "author": {
+ "title": "Author",
+ "description": "The names of the authors of the document.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "unofficialTranslations": {
+ "title": "Unofficial translations",
+ "description": "The languages in which unofficial translations of the document are available, from the open [language](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#language) codelist. A [BCP47 language tag](https://www.w3.org/International/articles/language-tags/) is allowed, if there is a user need for the additional information.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "language.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/documentation_details/master/schema/index.html b/en/extensions/documentation_details/master/schema/index.html
new file mode 100644
index 000000000..07a581ad5
--- /dev/null
+++ b/en/extensions/documentation_details/master/schema/index.html
@@ -0,0 +1,321 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Document Details +
+ ++ Adds fields to the document object for page references, access details and author information. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Document objects are used to describe and link to documents. This extension adds fields to document objects to:
+-
+
- Indicate the page numbers at which relevant information can be found within a large document +
- Describe any special arrangements needed to access the document +
- Name the author of the document (not to be confused with its publisher) +
- Indicate the languages in which unofficial translations of the document are available +
Use cases include:
+-
+
- Accessing the document and locating the information within it +
- Checking whether authors are involved in other ways in the contracting process, e.g. as bidders +
- Measuring the accessibility of documents +
Example
+{
+ "tender": {
+ "documents": [
+ {
+ "id": "1",
+ "documentType": "equityTransferCaps",
+ "title": "Equity transfer cap terms",
+ "description": "No equity transfer is permitted until construction is completed. See document for more details.",
+ "url": "http://example.com/ppp_unit/documents/contracts/4g_network_signed_contract.pdf",
+ "language": "en",
+ "unofficialTranslations": [
+ "it"
+ ],
+ "pageStart": "334",
+ "pageEnd": "336",
+ "accessDetails": "This document can only be accessed by visiting the PPP unit office by appointment. Please see the PPP unit website for further details.",
+ "accessDetailsURL": "http://example.com/ppp_unit/registration/",
+ "author": "Contract department, PPP unit"
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-08-04
+-
+
- Change unofficialTranslation field to
unofficialTranslationsarray of languages.
+
2023-04-05
+-
+
- Add
accessDetailsURLand unofficialTranslation fields.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2020-04-15
+-
+
- Improve documentation +
- Use non-normative keywords where appropriate +
2019-01-30
+-
+
- Remove obsolete
mergeStrategyproperties
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/enquiries/index.html b/en/extensions/enquiries/index.html
new file mode 100644
index 000000000..0bcd3772e
--- /dev/null
+++ b/en/extensions/enquiries/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Document Details +
+ ++ Adds fields to the document object for page references, access details and author information. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Document +
+ +
+ The extension defines these fields in the Document object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ pageStart
+
+ |
+ + Page start + | +
+ When the information referenced exists within a large document, indicate the first page on which it can be found. This should refer to the printed page number, not the page number reported by software applications. + + |
+ + string + | +
+
+ pageEnd
+
+ |
+ + Page end + | +
+ When the information referenced exists within a large document, indicate the last page on which it can be found. This should refer to the printed page number, not the page number reported by software applications. + + |
+ + string + | +
+
+ accessDetails
+
+ |
+ + Access details + | +
+ A description of any special arrangements needed to access this document, for example: registering for access, paying a fee, or visiting a location to inspect the document. + + |
+ + string + | +
+
+ accessDetailsURL
+
+ |
+ + Access details URL + | +
+ A web address for information on any special arrangements needed to access the document. + + |
+ + string + | +
+
+ author
+
+ |
+ + Author + | +
+ The names of the authors of the document. + + |
+ + string + | +
+
+ unofficialTranslations
+
+ |
+ + Unofficial translations + | +
+ The languages in which unofficial translations of the document are available, from the open language codelist. A BCP47 language tag is allowed, if there is a user need for the additional information. + + |
+ + array of strings from open language codelist + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/enquiries/master/ +
+Not Found
+The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
diff --git a/en/extensions/enquiries/master/extension.json b/en/extensions/enquiries/master/extension.json new file mode 100644 index 000000000..0588b98e1 --- /dev/null +++ b/en/extensions/enquiries/master/extension.json @@ -0,0 +1,23 @@ +{ + "name": { + "en": "Enquiries", + "es": "Consultas" + }, + "description": { + "en": "The enquiries extension can be used to record questions raised during a contracting process, and the answers provided.", + "es": "La extensi\u00f3n sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contrataci\u00f3n y las respuestas proporcionadas." + }, + "documentationUrl": { + "en": "https://extensions.open-contracting.org/en/extensions/enquiries/" + }, + "compatibility": [ + "1.1" + ], + "schemas": [ + "release-schema.json" + ], + "contactPoint": { + "name": "Open Contracting Partnership", + "email": "data@open-contracting.org" + } +} diff --git a/en/extensions/enquiries/master/index.html b/en/extensions/enquiries/master/index.html new file mode 100644 index 000000000..9f6007b75 --- /dev/null +++ b/en/extensions/enquiries/master/index.html @@ -0,0 +1,347 @@ + + + + + + + + + +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/enquiries/master/release-schema.json b/en/extensions/enquiries/master/release-schema.json
new file mode 100644
index 000000000..ff73e0b38
--- /dev/null
+++ b/en/extensions/enquiries/master/release-schema.json
@@ -0,0 +1,103 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "enquiries": {
+ "title": "Enquiries",
+ "description": "Questions sent to the procuring entity, and the answers given",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Enquiry"
+ },
+ "uniqueItems": true
+ }
+ }
+ },
+ "Enquiry": {
+ "title": "Enquiry",
+ "description": "A question related to this contracting process, generally sent during the enquiry period.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "A unique identifier for the enquiry.",
+ "type": "string"
+ },
+ "date": {
+ "title": "Date",
+ "description": "The date the enquiry was received or processed.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "author": {
+ "title": "Question author",
+ "description": "The organization asking this question. The corresponding entry in the `parties` array should have 'enquirer' in its `roles` array.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "title": {
+ "title": "Question title",
+ "description": "The subject line of the question.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Description",
+ "description": "The body of the question.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "answer": {
+ "title": "Answer",
+ "description": "The answer to this question, when available.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "dateAnswered": {
+ "title": "Date answered",
+ "description": "The date the answer to the question was provided.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "relatedItem": {
+ "title": "Related item",
+ "description": "If this question relates to a specific line-item, this field contains the line-item identifier.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Related lot",
+ "description": "Where lots are used, if this question relates to a specific lot, this field contains the lot identifier.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "threadID": {
+ "title": "Thread identifier",
+ "description": "If this question and answer forms part of a discussion thread (e.g. the question is a follow-up to a previous answer) a thread identifier can be used to associate multiple enquiries.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/enquiries/master/schema/index.html b/en/extensions/enquiries/master/schema/index.html
new file mode 100644
index 000000000..735854ea3
--- /dev/null
+++ b/en/extensions/enquiries/master/schema/index.html
@@ -0,0 +1,444 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Enquiries +
+ ++ The enquiries extension can be used to record questions raised during a contracting process, and the answers provided. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The enquiries extension can be used to record questions raised during a contracting process, and the answers provided.
+Structure
+The extension adds an enquiries array to tender, consisting of one or more enquiry objects, each with fields for a question, and an answer.
Example:
+{
+ "tender": {
+ "enquiries": [
+ {
+ "id": "Q1",
+ "date": "2017-01-22T14:55:00Z",
+ "author": {
+ "name": "Open Data Services Co-op",
+ "id": "GB-COH-09506232"
+ },
+ "title": "Variations of timeline accepted?",
+ "description": "The tender specifies delivery of Item 1 by end of March 2017. Will alternative proposals for the timeline be considered?",
+ "dateAnswered": "2017-02-05T09:00:00Z",
+ "answer": "There is a hard deadline of 15th April 2017. All proposals must be for delivery of Item 1 by this date.",
+ "relatedItem": "1",
+ "threadID": "1"
+ }
+ ]
+ }
+}
+Supporting documents with clarifications, or a full document containing answers to questions can be included in the tender.documents array with a documentType of 'clarifications'.
Where the answers to a question are only available in attached documents, an answer value such as 'Consult section N of "%document name%" in the documents section' may be entered to allow analysts of the data to identify that an answer to this question has been provided.
When a system allows a discussion format, where each answer can be followed by a further clarification question, the threadID field can be used to link together multiple entries in the enquiries array.
Guidance
+Implementations may vary on the amount of enquiry information they provide, and when it is provided.
+Some publishers may omit the identity of the question author to protect confidentiality of enquirers, or may anonymize this information (e.g. simply putting the author name as 'Organization 1' or 'Organization 2' so that it is possible to see questions from the same organization, but not to know the identity of that organization.)
+The relatedItem and relatedLot fields are available for use when questions can be asked in relation to a specific lot or item.
Where possible, the recommended approach is to:
+-
+
- Make release with a 'tenderUpdate' release tag for every new question or batch of questions received, providing an enquiries array with each of the questions in; +
- Make a release with a 'tenderUpdate' release tag when the answers to the questions are provided, updating the earlier enquiries array so each entry now contains both a question and an answer; +
This approach will enable third-party applications to watch for releases that provide answers to questions, and will support procurement monitors in reviewing the way in which questions are being answered.
+We recommend that publishers provide question answers as plain text, or with minimal HTML markup (paragraphs and line-breaks), and that consuming applications parse text appropriately to format it for readability (e.g. replace line-breaks with paragraph breaks in HTML).
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+Unreleased
+-
+
- Remove the
+partyRole.csvcodelist, whose codes already exist in OCDS 1.1
+ - Make
Enquiry.idrequired so that enquiries are merged by identifier
+ - Make
Tender.enquiriesnon-nullable
+
v1.1.5
+-
+
- Review normative and non-normative words +
v1.1.4
+-
+
- Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Use
OrganizationReferenceinstead ofOrganizationforEnquiry.author
+ - Correct name of +partyRole.csv codelist (was +partyRoles.csv) +
- Allow
Enquiry.dateto be null
+ - List codelists in extension.json +
- Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/enquiries/v1.1.4/README.md b/en/extensions/enquiries/v1.1.4/README.md
new file mode 100644
index 000000000..c365bdead
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.4/README.md
@@ -0,0 +1,75 @@
+# Enquiries
+
+The enquiries extension can be used to record questions raised during a contracting process, and the answers provided.
+
+## Structure
+
+The extension adds an `enquiries` array to tender, consisting of one or more enquiry objects, each with fields for a question, and an answer.
+
+Example:
+
+```json
+{
+ "tender": {
+ "enquiries": [
+ {
+ "id": "Q1",
+ "date": "2017-01-22T14:55:00Z",
+ "author": {
+ "name": "Open Data Services Co-op",
+ "id": "GB-COH-09506232"
+ },
+ "title": "Variations of timeline accepted?",
+ "description": "The tender specifies delivery of Item 1 by end of March 2017. Will alternative proposals for the timeline be considered?",
+ "dateAnswered": "2017-02-05T09:00:00Z",
+ "answer": "There is a hard deadline of 15th April 2017. All proposals must be for delivery of Item 1 by this date.",
+ "relatedItem": "1",
+ "threadID": "1"
+ }
+ ]
+ }
+}
+```
+
+Supporting documents with clarifications, or a full document containing answers to questions can be included in the `tender/documents` array with a `documentType` of 'clarifications'.
+
+Where the answers to a question are only available in attached documents, an `answer` value such as 'Consult section N of "%document name%" in the documents section' may be entered to allow analysts of the data to identify that an answer to this question has been provided.
+
+When a system allows a discussion format, where each answer can be followed by a further clarification question, the `threadID` property can be used to link together multiple entries in the `enquiries` array.
+
+## Usage guidance
+
+Implementations may vary on the amount of enquiry information they provide, and when it is provided.
+
+Some publishers may omit the identity of the question author to protect confidentiality of enquirers, or may anonymize this information (e.g. simply putting the author name as 'Organization 1' or 'Organization 2' so that it is possible to see questions from the same organization, but not to know the identity of that organization.)
+
+The `relatedItem` and `relatedLot` properties are available for use when questions can be asked in relation to a specific lot or item.
+
+Where possible, the recommended approach is to:
+
+- Make release with a `tenderUpdate` release tag for every new question or batch of questions received, providing an enquiries array with each of the questions in;
+- Make a release with a `tenderUpdate` release tag when the answers to the questions are provided, updating the earlier enquiries array so each entry now contains both a question and an answer;
+
+This approach will enable third-party applications to watch for releases that provide answers to questions, and will support procurement monitors in reviewing the way in which questions are being answered.
+
+We recommend that publishers provide question answers as plain text, or with minimal HTML markup (paragraphs and line-breaks), and that consuming applications parse text appropriately to format it for readability (e.g. replace line-breaks with paragraph breaks in HTML).
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.4
+
+- Remove Sphinx directives from readme
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Use `OrganizationReference` instead of `Organization` for `Enquiry.author`
+- Correct name of +partyRole.csv codelist (was +partyRoles.csv)
+- Allow `Enquiry.date` to be null
+- List codelists in extension.json
+- Use Apache 2.0 License
+- Add tests and tidy code
diff --git a/en/extensions/enquiries/v1.1.4/codelists/+partyRole.csv b/en/extensions/enquiries/v1.1.4/codelists/+partyRole.csv
new file mode 100644
index 000000000..cc186f654
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.4/codelists/+partyRole.csv
@@ -0,0 +1,2 @@
+Code,Title,Description
+enquirer,Enquirer,A party who has made an enquiry during the enquiry phase of a contracting process
diff --git a/en/extensions/enquiries/v1.1.4/codelists/index.html b/en/extensions/enquiries/v1.1.4/codelists/index.html
new file mode 100644
index 000000000..2ee78b613
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.4/codelists/index.html
@@ -0,0 +1,238 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Enquiries +
+ ++ The enquiries extension can be used to record questions raised during a contracting process, and the answers provided. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ enquiries
+
+ |
+ + Enquiries + | +
+ Questions sent to the procuring entity, and the answers given + + |
+ + array of Enquiry objects + | +
+ Enquiry +
+ +
+ The extension defines a new Enquiry object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ A unique identifier for the enquiry. + + |
+ + string + | +
+
+ date
+
+ |
+ + Date + | +
+ The date the enquiry was received or processed. + + |
+ + string + | +
+
+ author
+
+ |
+ + Question author + | +
+ The organization asking this question. The corresponding entry in the |
+ + OrganizationReference object + | +
+
+ title
+
+ |
+ + Question title + | +
+ The subject line of the question. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ The body of the question. + + |
+ + string + | +
+
+ answer
+
+ |
+ + Answer + | +
+ The answer to this question, when available. + + |
+ + string + | +
+
+ dateAnswered
+
+ |
+ + Date answered + | +
+ The date the answer to the question was provided. + + |
+ + string + | +
+
+ relatedItem
+
+ |
+ + Related item + | +
+ If this question relates to a specific line-item, this field contains the line-item identifier. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Related lot + | +
+ Where lots are used, if this question relates to a specific lot, this field contains the lot identifier. + + |
+ + string + | +
+
+ threadID
+
+ |
+ + Thread identifier + | +
+ If this question and answer forms part of a discussion thread (e.g. the question is a follow-up to a previous answer) a thread identifier can be used to associate multiple enquiries. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/enquiries/v1.1.4/extension.json b/en/extensions/enquiries/v1.1.4/extension.json
new file mode 100644
index 000000000..1d4becafe
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.4/extension.json
@@ -0,0 +1,22 @@
+{
+ "name": {
+ "en": "Enquiries",
+ "es": "Consultas"
+ },
+ "description": {
+ "en": "The enquiries extension can be used to record questions raised during a contracting process, and the answers provided.",
+ "es": "La extensi\u00f3n sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contrataci\u00f3n y las respuestas proporcionadas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/enquiries/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "+partyRole.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/en/extensions/enquiries/v1.1.4/index.html b/en/extensions/enquiries/v1.1.4/index.html
new file mode 100644
index 000000000..a4aa49134
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.4/index.html
@@ -0,0 +1,342 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Enquiries +
+ ++ The enquiries extension can be used to record questions raised during a contracting process, and the answers provided. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ enquirer
+
+ |
+ + Enquirer + | +
+ A party who has made an enquiry during the enquiry phase of a contracting process + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/enquiries/v1.1.4/release-schema.json b/en/extensions/enquiries/v1.1.4/release-schema.json
new file mode 100644
index 000000000..0afb7fee4
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.4/release-schema.json
@@ -0,0 +1,105 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "enquiries": {
+ "title": "Enquiries",
+ "type": [
+ "array",
+ "null"
+ ],
+ "description": "Questions sent to the procuring entity, and the answers given",
+ "items": {
+ "$ref": "#/definitions/Enquiry"
+ }
+ }
+ }
+ },
+ "Enquiry": {
+ "type": "object",
+ "title": "Enquiry",
+ "description": "A question related to this contracting process, generally sent during the enquiry period.",
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "A unique identifier for the enquiry.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "date": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "title": "Date",
+ "description": "The date the enquiry was received or processed.",
+ "format": "date-time"
+ },
+ "author": {
+ "title": "Question author",
+ "description": "The identifier and name of the party asking this question. Questioners may be listed in the parties array with a role of 'enquirer'. Procurement policies vary on whether or not the identity of those asking questions should be disclosed, or at which stage this information may be disclosed. When the identity of the questioner cannot be disclosed leave the author section blank. Display systems should interpret this as an anonymous question.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "title": {
+ "title": "Question title",
+ "description": "The subject line of the question.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Description",
+ "description": "The body of the question.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "answer": {
+ "title": "Answer",
+ "description": "The answer to this question, when available.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "dateAnswered": {
+ "title": "Date answered",
+ "description": "The date the answer to the question was provided.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "relatedItem": {
+ "title": "Related item",
+ "description": "If this question relates to a specific line-item, this field contains the line-item identifier.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Related lot",
+ "description": "Where lots are used, if this question relates to a specific lot, this field contains the lot identifier.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "threadID": {
+ "title": "Thread identifier",
+ "description": "If this question and answer forms part of a discussion thread (e.g. the question is a follow up to a previous answer) an optional thread identifier can be used to associate together multiple enquiries.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/enquiries/v1.1.4/schema/index.html b/en/extensions/enquiries/v1.1.4/schema/index.html
new file mode 100644
index 000000000..5a1cfc4d4
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.4/schema/index.html
@@ -0,0 +1,449 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Enquiries +
+ ++ The enquiries extension can be used to record questions raised during a contracting process, and the answers provided. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The enquiries extension can be used to record questions raised during a contracting process, and the answers provided.
+Structure
+The extension adds an enquiries array to tender, consisting of one or more enquiry objects, each with fields for a question, and an answer.
Example:
+{
+ "tender": {
+ "enquiries": [
+ {
+ "id": "Q1",
+ "date": "2017-01-22T14:55:00Z",
+ "author": {
+ "name": "Open Data Services Co-op",
+ "id": "GB-COH-09506232"
+ },
+ "title": "Variations of timeline accepted?",
+ "description": "The tender specifies delivery of Item 1 by end of March 2017. Will alternative proposals for the timeline be considered?",
+ "dateAnswered": "2017-02-05T09:00:00Z",
+ "answer": "There is a hard deadline of 15th April 2017. All proposals must be for delivery of Item 1 by this date.",
+ "relatedItem": "1",
+ "threadID": "1"
+ }
+ ]
+ }
+}
+Supporting documents with clarifications, or a full document containing answers to questions can be included in the tender/documents array with a documentType of 'clarifications'.
Where the answers to a question are only available in attached documents, an answer value such as 'Consult section N of "%document name%" in the documents section' may be entered to allow analysts of the data to identify that an answer to this question has been provided.
When a system allows a discussion format, where each answer can be followed by a further clarification question, the threadID property can be used to link together multiple entries in the enquiries array.
Usage guidance
+Implementations may vary on the amount of enquiry information they provide, and when it is provided.
+Some publishers may omit the identity of the question author to protect confidentiality of enquirers, or may anonymize this information (e.g. simply putting the author name as 'Organization 1' or 'Organization 2' so that it is possible to see questions from the same organization, but not to know the identity of that organization.)
+The relatedItem and relatedLot properties are available for use when questions can be asked in relation to a specific lot or item.
Where possible, the recommended approach is to:
+-
+
- Make release with a
tenderUpdaterelease tag for every new question or batch of questions received, providing an enquiries array with each of the questions in;
+ - Make a release with a
tenderUpdaterelease tag when the answers to the questions are provided, updating the earlier enquiries array so each entry now contains both a question and an answer;
+
This approach will enable third-party applications to watch for releases that provide answers to questions, and will support procurement monitors in reviewing the way in which questions are being answered.
+We recommend that publishers provide question answers as plain text, or with minimal HTML markup (paragraphs and line-breaks), and that consuming applications parse text appropriately to format it for readability (e.g. replace line-breaks with paragraph breaks in HTML).
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.4
+-
+
- Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Use
OrganizationReferenceinstead ofOrganizationforEnquiry.author
+ - Correct name of +partyRole.csv codelist (was +partyRoles.csv) +
- Allow
Enquiry.dateto be null
+ - List codelists in extension.json +
- Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/enquiries/v1.1.5/README.md b/en/extensions/enquiries/v1.1.5/README.md
new file mode 100644
index 000000000..209dc78ea
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.5/README.md
@@ -0,0 +1,79 @@
+# Enquiries
+
+The enquiries extension can be used to record questions raised during a contracting process, and the answers provided.
+
+## Structure
+
+The extension adds an `enquiries` array to tender, consisting of one or more enquiry objects, each with fields for a question, and an answer.
+
+Example:
+
+```json
+{
+ "tender": {
+ "enquiries": [
+ {
+ "id": "Q1",
+ "date": "2017-01-22T14:55:00Z",
+ "author": {
+ "name": "Open Data Services Co-op",
+ "id": "GB-COH-09506232"
+ },
+ "title": "Variations of timeline accepted?",
+ "description": "The tender specifies delivery of Item 1 by end of March 2017. Will alternative proposals for the timeline be considered?",
+ "dateAnswered": "2017-02-05T09:00:00Z",
+ "answer": "There is a hard deadline of 15th April 2017. All proposals must be for delivery of Item 1 by this date.",
+ "relatedItem": "1",
+ "threadID": "1"
+ }
+ ]
+ }
+}
+```
+
+Supporting documents with clarifications, or a full document containing answers to questions can be included in the `tender.documents` array with a `documentType` of 'clarifications'.
+
+Where the answers to a question are only available in attached documents, an `answer` value such as 'Consult section N of "%document name%" in the documents section' may be entered to allow analysts of the data to identify that an answer to this question has been provided.
+
+When a system allows a discussion format, where each answer can be followed by a further clarification question, the `threadID` property can be used to link together multiple entries in the `enquiries` array.
+
+## Usage guidance
+
+Implementations may vary on the amount of enquiry information they provide, and when it is provided.
+
+Some publishers may omit the identity of the question author to protect confidentiality of enquirers, or may anonymize this information (e.g. simply putting the author name as 'Organization 1' or 'Organization 2' so that it is possible to see questions from the same organization, but not to know the identity of that organization.)
+
+The `relatedItem` and `relatedLot` properties are available for use when questions can be asked in relation to a specific lot or item.
+
+Where possible, the recommended approach is to:
+
+- Make release with a 'tenderUpdate' release tag for every new question or batch of questions received, providing an enquiries array with each of the questions in;
+- Make a release with a 'tenderUpdate' release tag when the answers to the questions are provided, updating the earlier enquiries array so each entry now contains both a question and an answer;
+
+This approach will enable third-party applications to watch for releases that provide answers to questions, and will support procurement monitors in reviewing the way in which questions are being answered.
+
+We recommend that publishers provide question answers as plain text, or with minimal HTML markup (paragraphs and line-breaks), and that consuming applications parse text appropriately to format it for readability (e.g. replace line-breaks with paragraph breaks in HTML).
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.5
+
+- Review normative and non-normative words
+
+### v1.1.4
+
+- Remove Sphinx directives from readme
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Use `OrganizationReference` instead of `Organization` for `Enquiry.author`
+- Correct name of +partyRole.csv codelist (was +partyRoles.csv)
+- Allow `Enquiry.date` to be null
+- List codelists in extension.json
+- Use Apache 2.0 License
+- Add tests and tidy code
diff --git a/en/extensions/enquiries/v1.1.5/codelists/+partyRole.csv b/en/extensions/enquiries/v1.1.5/codelists/+partyRole.csv
new file mode 100644
index 000000000..cc186f654
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.5/codelists/+partyRole.csv
@@ -0,0 +1,2 @@
+Code,Title,Description
+enquirer,Enquirer,A party who has made an enquiry during the enquiry phase of a contracting process
diff --git a/en/extensions/enquiries/v1.1.5/codelists/index.html b/en/extensions/enquiries/v1.1.5/codelists/index.html
new file mode 100644
index 000000000..738d8a7cd
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.5/codelists/index.html
@@ -0,0 +1,238 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Enquiries +
+ ++ The enquiries extension can be used to record questions raised during a contracting process, and the answers provided. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ enquiries
+
+ |
+ + Enquiries + | +
+ Questions sent to the procuring entity, and the answers given + + |
+ + array of Enquiry objects + | +
+ Enquiry +
+ +
+ The extension defines a new Enquiry object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ A unique identifier for the enquiry. + + |
+ + string + | +
+
+ date
+
+ |
+ + Date + | +
+ The date the enquiry was received or processed. + + |
+ + string + | +
+
+ author
+
+ |
+ + Question author + | +
+ The identifier and name of the party asking this question. Questioners may be listed in the parties array with a role of 'enquirer'. Procurement policies vary on whether or not the identity of those asking questions should be disclosed, or at which stage this information may be disclosed. When the identity of the questioner cannot be disclosed leave the author section blank. Display systems should interpret this as an anonymous question. + + |
+ + OrganizationReference object + | +
+
+ title
+
+ |
+ + Question title + | +
+ The subject line of the question. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ The body of the question. + + |
+ + string + | +
+
+ answer
+
+ |
+ + Answer + | +
+ The answer to this question, when available. + + |
+ + string + | +
+
+ dateAnswered
+
+ |
+ + Date answered + | +
+ The date the answer to the question was provided. + + |
+ + string + | +
+
+ relatedItem
+
+ |
+ + Related item + | +
+ If this question relates to a specific line-item, this field contains the line-item identifier. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Related lot + | +
+ Where lots are used, if this question relates to a specific lot, this field contains the lot identifier. + + |
+ + string + | +
+
+ threadID
+
+ |
+ + Thread identifier + | +
+ If this question and answer forms part of a discussion thread (e.g. the question is a follow up to a previous answer) an optional thread identifier can be used to associate together multiple enquiries. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/enquiries/v1.1.5/extension.json b/en/extensions/enquiries/v1.1.5/extension.json
new file mode 100644
index 000000000..288c8b201
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.5/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Enquiries",
+ "es": "Consultas"
+ },
+ "description": {
+ "en": "The enquiries extension can be used to record questions raised during a contracting process, and the answers provided.",
+ "es": "La extensi\u00f3n sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contrataci\u00f3n y las respuestas proporcionadas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/enquiries/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "+partyRole.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/enquiries/v1.1.5/index.html b/en/extensions/enquiries/v1.1.5/index.html
new file mode 100644
index 000000000..1e0935bc5
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.5/index.html
@@ -0,0 +1,346 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Enquiries +
+ ++ The enquiries extension can be used to record questions raised during a contracting process, and the answers provided. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ enquirer
+
+ |
+ + Enquirer + | +
+ A party who has made an enquiry during the enquiry phase of a contracting process + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/enquiries/v1.1.5/release-schema.json b/en/extensions/enquiries/v1.1.5/release-schema.json
new file mode 100644
index 000000000..aa88f157e
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.5/release-schema.json
@@ -0,0 +1,106 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "enquiries": {
+ "title": "Enquiries",
+ "type": [
+ "array",
+ "null"
+ ],
+ "description": "Questions sent to the procuring entity, and the answers given",
+ "items": {
+ "$ref": "#/definitions/Enquiry"
+ },
+ "uniqueItems": true
+ }
+ }
+ },
+ "Enquiry": {
+ "type": "object",
+ "title": "Enquiry",
+ "description": "A question related to this contracting process, generally sent during the enquiry period.",
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "A unique identifier for the enquiry.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "date": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "title": "Date",
+ "description": "The date the enquiry was received or processed.",
+ "format": "date-time"
+ },
+ "author": {
+ "title": "Question author",
+ "description": "The party asking this question. The corresponding entry in the `parties` array should have 'enquirer' in its `roles` array. Procurement policies vary on whether or not the identity of those asking questions is disclosed, or at which stage this information is disclosed.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "title": {
+ "title": "Question title",
+ "description": "The subject line of the question.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Description",
+ "description": "The body of the question.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "answer": {
+ "title": "Answer",
+ "description": "The answer to this question, when available.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "dateAnswered": {
+ "title": "Date answered",
+ "description": "The date the answer to the question was provided.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "relatedItem": {
+ "title": "Related item",
+ "description": "If this question relates to a specific line-item, this field contains the line-item identifier.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Related lot",
+ "description": "Where lots are used, if this question relates to a specific lot, this field contains the lot identifier.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "threadID": {
+ "title": "Thread identifier",
+ "description": "If this question and answer forms part of a discussion thread (e.g. the question is a follow-up to a previous answer) a thread identifier can be used to associate multiple enquiries.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/enquiries/v1.1.5/schema/index.html b/en/extensions/enquiries/v1.1.5/schema/index.html
new file mode 100644
index 000000000..22ef5652f
--- /dev/null
+++ b/en/extensions/enquiries/v1.1.5/schema/index.html
@@ -0,0 +1,449 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Enquiries +
+ ++ The enquiries extension can be used to record questions raised during a contracting process, and the answers provided. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The enquiries extension can be used to record questions raised during a contracting process, and the answers provided.
+Structure
+The extension adds an enquiries array to tender, consisting of one or more enquiry objects, each with fields for a question, and an answer.
Example:
+{
+ "tender": {
+ "enquiries": [
+ {
+ "id": "Q1",
+ "date": "2017-01-22T14:55:00Z",
+ "author": {
+ "name": "Open Data Services Co-op",
+ "id": "GB-COH-09506232"
+ },
+ "title": "Variations of timeline accepted?",
+ "description": "The tender specifies delivery of Item 1 by end of March 2017. Will alternative proposals for the timeline be considered?",
+ "dateAnswered": "2017-02-05T09:00:00Z",
+ "answer": "There is a hard deadline of 15th April 2017. All proposals must be for delivery of Item 1 by this date.",
+ "relatedItem": "1",
+ "threadID": "1"
+ }
+ ]
+ }
+}
+Supporting documents with clarifications, or a full document containing answers to questions can be included in the tender.documents array with a documentType of 'clarifications'.
Where the answers to a question are only available in attached documents, an answer value such as 'Consult section N of "%document name%" in the documents section' may be entered to allow analysts of the data to identify that an answer to this question has been provided.
When a system allows a discussion format, where each answer can be followed by a further clarification question, the threadID property can be used to link together multiple entries in the enquiries array.
Usage guidance
+Implementations may vary on the amount of enquiry information they provide, and when it is provided.
+Some publishers may omit the identity of the question author to protect confidentiality of enquirers, or may anonymize this information (e.g. simply putting the author name as 'Organization 1' or 'Organization 2' so that it is possible to see questions from the same organization, but not to know the identity of that organization.)
+The relatedItem and relatedLot properties are available for use when questions can be asked in relation to a specific lot or item.
Where possible, the recommended approach is to:
+-
+
- Make release with a 'tenderUpdate' release tag for every new question or batch of questions received, providing an enquiries array with each of the questions in; +
- Make a release with a 'tenderUpdate' release tag when the answers to the questions are provided, updating the earlier enquiries array so each entry now contains both a question and an answer; +
This approach will enable third-party applications to watch for releases that provide answers to questions, and will support procurement monitors in reviewing the way in which questions are being answered.
+We recommend that publishers provide question answers as plain text, or with minimal HTML markup (paragraphs and line-breaks), and that consuming applications parse text appropriately to format it for readability (e.g. replace line-breaks with paragraph breaks in HTML).
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.5
+-
+
- Review normative and non-normative words +
v1.1.4
+-
+
- Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Use
OrganizationReferenceinstead ofOrganizationforEnquiry.author
+ - Correct name of +partyRole.csv codelist (was +partyRoles.csv) +
- Allow
Enquiry.dateto be null
+ - List codelists in extension.json +
- Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/essentialAssets/index.html b/en/extensions/essentialAssets/index.html
new file mode 100644
index 000000000..0e749ebde
--- /dev/null
+++ b/en/extensions/essentialAssets/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Enquiries +
+ ++ The enquiries extension can be used to record questions raised during a contracting process, and the answers provided. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ enquiries
+
+ |
+ + Enquiries + | +
+ Questions sent to the procuring entity, and the answers given + + |
+ + array of Enquiry objects + | +
+ Enquiry +
+ +
+ The extension defines a new Enquiry object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ A unique identifier for the enquiry. + + |
+ + string + | +
+
+ date
+
+ |
+ + Date + | +
+ The date the enquiry was received or processed. + + |
+ + string + | +
+
+ author
+
+ |
+ + Question author + | +
+ The party asking this question. The corresponding entry in the |
+ + OrganizationReference object + | +
+
+ title
+
+ |
+ + Question title + | +
+ The subject line of the question. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ The body of the question. + + |
+ + string + | +
+
+ answer
+
+ |
+ + Answer + | +
+ The answer to this question, when available. + + |
+ + string + | +
+
+ dateAnswered
+
+ |
+ + Date answered + | +
+ The date the answer to the question was provided. + + |
+ + string + | +
+
+ relatedItem
+
+ |
+ + Related item + | +
+ If this question relates to a specific line-item, this field contains the line-item identifier. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Related lot + | +
+ Where lots are used, if this question relates to a specific lot, this field contains the lot identifier. + + |
+ + string + | +
+
+ threadID
+
+ |
+ + Thread identifier + | +
+ If this question and answer forms part of a discussion thread (e.g. the question is a follow-up to a previous answer) a thread identifier can be used to associate multiple enquiries. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/essentialAssets/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/essentialAssets/master/release-schema.json b/en/extensions/essentialAssets/master/release-schema.json
new file mode 100644
index 000000000..424b7fdde
--- /dev/null
+++ b/en/extensions/essentialAssets/master/release-schema.json
@@ -0,0 +1,79 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "essentialAssets": {
+ "title": "Essentials assets",
+ "description": "Information about the assets used for the provision of public services.",
+ "$ref": "#/definitions/EssentialAsset"
+ },
+ "hasEssentialAssets": {
+ "title": "Has essential assets",
+ "description": "Whether there is information about the assets used for the provision of public services.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "essentialAssets": {
+ "title": "Essential assets",
+ "description": "Information about the assets used for the provision of public services.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/EssentialAsset"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "hasEssentialAssets": {
+ "title": "Has essential assets",
+ "description": "Whether there is information about the assets used for the provision of public services.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "EssentialAsset": {
+ "title": "Essential asset",
+ "description": "Information about the asset used for the provision of public services.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "Description of the essential asset.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "significance": {
+ "title": "Significance",
+ "description": "Estimated percentage share of the essential asset provided in relation to the overall asset needed for the provision of the public services.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "predominance": {
+ "title": "Predominance",
+ "description": "Estimated percentage share of asset provided compared to asset used for activities other than the public services.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/essentialAssets/master/schema/index.html b/en/extensions/essentialAssets/master/schema/index.html
new file mode 100644
index 000000000..8e1786e97
--- /dev/null
+++ b/en/extensions/essentialAssets/master/schema/index.html
@@ -0,0 +1,401 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Essential assets +
+ ++ Adds a object to the tender object to describe the assets used for the provision of public services. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an object to the tender and lot objects to describe the assets used for the provision of public services.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Legal context
+In the European Union, this extension's fields correspond to Article 4, clause 4 of Regulation 1370/2007 and eForms OPP-020-Contract (Assets related contract extension indicator), OPP-021-Contract (Used asset), OPP-022-Contract (Significance (%)), and OPP-023-Contract (Predominance (%)).For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Examples
+Tender
+{
+ "tender": {
+ "hasEssentialAssets": true,
+ "essentialAssets": {
+ "description": "Significant investments have been made by the supplier in the past years and will continue to be so in the future, which will pay for themselves over a period of time well beyond the period of the contract. It includes the purchase of new vehicles, the maintenance of the modernization of the existing fleet and the renovation of the vehicle depots.",
+ "significance": "30",
+ "predominance": "40"
+ }
+ }
+}
+Lot
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "hasEssentialAssets": true,
+ "essentialAssets": [
+ {
+ "description": "Significant investments have been made by the supplier in the past years and will continue to be so in the future, which will pay for themselves over a period of time well beyond the period of the contract. It includes the purchase of new vehicles, the maintenance of the modernization of the existing fleet and the renovation of the vehicle depots.",
+ "significance": "30",
+ "predominance": "40"
+ }
+ ]
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-06-13
+-
+
- Change
Lot.essentialAssetsfrom an object to an array.
+
2023-04-05
+-
+
- Add
essentialAssetsandhasEssentialAssetsto theLotobject.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile in issue #60 and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/eu/1.1/README.md b/en/extensions/eu/1.1/README.md
new file mode 100644
index 000000000..9cfa652b4
--- /dev/null
+++ b/en/extensions/eu/1.1/README.md
@@ -0,0 +1,226 @@
+# European Union
+
+Implements fields and codes that are specific to European law.
+
+For complete guidance on meeting the disclosure requirements of European law, see [OCDS for eForms](https://standard.open-contracting.org/profiles/eforms/latest/en/) for the 2019 regulation, or [OCDS for European Union](https://standard.open-contracting.org/profiles/eu/latest/en/) for the 2015 regulation.
+
+## Example
+
+```json
+{
+ "parties": [
+ {
+ "details": {
+ "url": "https://www.manchester.ac.uk/",
+ "buyerProfile": "https://in-tendhost.co.uk/universityofmanchester/aspx/Home"
+ },
+ "roles": [
+ "leadBuyer",
+ "awardingCentralPurchasingBody",
+ "evaluationBody",
+ "submissionReceiptBody"
+ ]
+ },
+ {
+ "name": "Royal Tax Office",
+ "id": "08797655",
+ "contactPoint": {
+ "name": "Crown Commercial Service",
+ "email": "info@crowncommercial.gov.uk",
+ "url": "https://www.gov.uk/government/publications/procurement-policy-note-0314-promoting-tax-compliance"
+ },
+ "roles": [
+ "informationService"
+ ]
+ },
+ {
+ "roles": [
+ "eSender"
+ ]
+ },
+ {
+ "roles": [
+ "procurementServiceProvider"
+ ]
+ },
+ {
+ "roles": [
+ "leadTenderer",
+ "tenderer"
+ ]
+ }
+ ],
+ "tender": {
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "reviewDetails": "NHS Wales Shared Services Partnership on behalf of Cardiff and Vale University Local Health Board will allow a minimum 10 calendar day standstill period between notifying the award decision and awarding the contract.",
+ "valueCalculationMethod": "Income from the sales of tickets over the duration of the contract minus the fees paid to the procuring entity.",
+ "items": [
+ {
+ "id": "item-1",
+ "description": "Printer ink cartridges",
+ "classification": {
+ "scheme": "CPV",
+ "id": "45233130.0",
+ "description": "Office supplies",
+ "uri": "http://cpv.data.ac.uk/code-45233130"
+ },
+ "deliveryAddresses": [
+ {
+ "streetAddress": "4, North London Business Park, Oakleigh Rd S",
+ "locality": "London",
+ "region": "London",
+ "postalCode": "N11 1NP",
+ "countryName": "United Kingdom"
+ }
+ ]
+ }
+ ],
+ "legislativeReferences": [
+ {
+ "title": "Direct taxation in the EU",
+ "url": "https://eur-lex.europa.eu/summary/chapter/2101.html",
+ "informationService": {
+ "name": "Royal Tax Office",
+ "id": "08797655"
+ }
+ }
+ ],
+ "lots": [
+ {
+ "id": "lot-1",
+ "awardPeriod": {
+ "durationInDays": 30,
+ "startDate": "2020-11-06T00:00:00Z",
+ "endDate": "2020-12-06T00:00:00Z"
+ },
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "additionalClassifications": [
+ {
+ "id": "oth-serv-contr",
+ "scheme": "eu-cvd-contract-type",
+ "description": "Other service contract"
+ }
+ ]
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2020-11-19T00:00:00Z"
+ }
+ ],
+ "documents": [
+ {
+ "id": "Fiscal1",
+ "documentType": "legislation"
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "award-1",
+ "valueCalculationMethod": "The awarded value takes into account the growing revenue expected from fees and the value of the equipment provided by the contracting authority.",
+ "items": [
+ {
+ "id": "1",
+ "additionalClassifications": [
+ {
+ "scheme": "eu-vehicle-category",
+ "id": "n2-n3",
+ "description": "Truck (N2-N3)"
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "contract-1",
+ "periodRationale": "The duration of the contract has been extended to anticipate the exceptional snowfall expected in January.",
+ "publicPassengerTransportServicesKilometers": 765,
+ "awardID": "award-1"
+ }
+ ],
+ "relatedProcesses": [
+ {
+ "id": "1",
+ "identifier": "123e4567-e89b-12d3-a456-426614174000",
+ "scheme": "eu-oj",
+ "relationship": [
+ "prior"
+ ]
+ }
+ ]
+}
+```
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### 2023-08-01
+
+- Add fields:
+ - `Organization.eDeliveryGateway`
+ - `Lot.hasAccessibilityCriteria`
+ - `Lot.noAccessibilityCriteriaRationale`
+ - `Lot.reviewDetails`
+
+### 2023-06-30
+
+- Add `Period.description` field.
+- Add codes:
+ - classificationScheme.csv:
+ - 'eu-vehicle-category'
+ - 'eu-cvd-contract-type'
+ - documentType.csv:
+ - 'legislation'
+ - partyRole.csv:
+ - 'procurementServiceProvider'
+ - 'eSender'
+ - 'leadBuyer'
+ - 'leadTenderer'
+ - 'evaluationBody'
+ - 'submissionReceiptBody'
+ - relatedProcessScheme.csv:
+ - 'eu-oj'
+- Move 'informationService' from the `+partyRole.csv` codelist to the Document publisher extension.
+
+### 2022-05-27
+
+- Move `Lot.minimumValue` to the Lots extension as `Lot.minValue`.
+
+### 2021-01-19
+
+- Set the object type of `informationService` to `OrganizationReference`.
+- Add 'informationService' code to `+partyRole.csv` codelist.
+
+### 2020-10-06
+
+- Add `Lot.awardPeriod` field.
+
+### 2020-10-05
+
+- Add `Lot.minimumValue` field.
+
+### 2020-07-13
+
+- Add the 'securityClearanceDeadline' code to the `+milestoneType.csv` codelist.
+
+### 2020-04-29
+
+- Add `Item.deliveryAddresses` field.
+
+### 2020-04-24
+
+- Add `minProperties`, `minItems` and/or `minLength` properties.
+
+This extension was originally discussed as part of the [OCDS for EU profile](https://github.com/open-contracting-extensions/european-union/issues), in [this issue](https://github.com/open-contracting/european-union-support/issues/19) and in [pull requests](https://github.com/open-contracting-extensions/ocds_eu_extension/pulls?q=is%3Apr+is%3Aclosed).
diff --git a/en/extensions/eu/1.1/codelists/+documentType.csv b/en/extensions/eu/1.1/codelists/+documentType.csv
new file mode 100644
index 000000000..9ec61eadc
--- /dev/null
+++ b/en/extensions/eu/1.1/codelists/+documentType.csv
@@ -0,0 +1,2 @@
+Section,Code,Title,Description
+tender,legislation,Legislation,"A general regulatory framework applicable in the place where the contract is to be performed. For example, tax legislation, environmental protection legislation or employment protection and working conditions legislation."
diff --git a/en/extensions/eu/1.1/codelists/+itemClassificationScheme.csv b/en/extensions/eu/1.1/codelists/+itemClassificationScheme.csv
new file mode 100644
index 000000000..2933ac89c
--- /dev/null
+++ b/en/extensions/eu/1.1/codelists/+itemClassificationScheme.csv
@@ -0,0 +1,3 @@
+Code,Title,Description,Source
+eu-vehicle-category,European Union vehicle category,The category of vehicle falling within the scope of the EU Clean Vehicles Directive 2009/33/EC.,https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/vehicle-category
+eu-cvd-contract-type,European Union Clean Vehicle Directive contract type,The category of contract according to the EU Clean Vehicles Directive 2009/33/EC.,https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/cvd-contract-type
diff --git a/en/extensions/eu/1.1/codelists/+milestoneType.csv b/en/extensions/eu/1.1/codelists/+milestoneType.csv
new file mode 100644
index 000000000..7147e36b4
--- /dev/null
+++ b/en/extensions/eu/1.1/codelists/+milestoneType.csv
@@ -0,0 +1,2 @@
+Code,Title,Description
+securityClearanceDeadline,Security clearance deadline,The tenderers may obtain their security clearance until this date.
diff --git a/en/extensions/eu/1.1/codelists/+partyRole.csv b/en/extensions/eu/1.1/codelists/+partyRole.csv
new file mode 100644
index 000000000..e1527004f
--- /dev/null
+++ b/en/extensions/eu/1.1/codelists/+partyRole.csv
@@ -0,0 +1,12 @@
+Code,Title,Description
+mediationBody,Mediation body,The body responsible for mediation procedures.
+centralPurchasingBody,Central purchasing body,"The procuring entity providing centralized purchasing activities and, possibly, ancillary purchasing activities."
+processContactPoint,Process contact point,A contact point dedicated to this contracting process.
+reviewContactPoint,Review contact point,The service from which information about the review procedure can be obtained.
+selectedParticipant,Selected participant,An organization that has already been selected to participate in the design contest.
+procurementServiceProvider,Procurement service provider,An organization that provides ancillary procurement services to buyers.
+eSender,TED eSender,An organization that provides data transfer services to buyers.
+leadBuyer,Lead buyer,The lead buyer in a group of buyers.
+leadTenderer,Lead tenderer,The lead tenderer in the case of a consortium or equivalent.
+evaluationBody,Evaluation body,The organization responsible for evaluating bids or requests to participate.
+submissionReceiptBody,Submission receipt body,The organization responsible for receiving bids or requests to participate.
diff --git a/en/extensions/eu/1.1/codelists/+relatedProcessScheme.csv b/en/extensions/eu/1.1/codelists/+relatedProcessScheme.csv
new file mode 100644
index 000000000..354f13453
--- /dev/null
+++ b/en/extensions/eu/1.1/codelists/+relatedProcessScheme.csv
@@ -0,0 +1,2 @@
+Code,Title,Description
+eu-oj,Official Journal of the European Union,An Official Journal of the European Union contracting process identifier.
diff --git a/en/extensions/eu/1.1/codelists/index.html b/en/extensions/eu/1.1/codelists/index.html
new file mode 100644
index 000000000..77c970041
--- /dev/null
+++ b/en/extensions/eu/1.1/codelists/index.html
@@ -0,0 +1,603 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Essential assets +
+ ++ Adds a object to the tender object to describe the assets used for the provision of public services. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ essentialAssets
+
+ |
+ + Essentials assets + | +
+ Information about the assets used for the provision of public services. + + |
+ + EssentialAsset object + | +
+
+ hasEssentialAssets
+
+ |
+ + Has essential assets + | +
+ Whether there is information about the assets used for the provision of public services. + + |
+ + boolean + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ essentialAssets
+
+ |
+ + Essential assets + | +
+ Information about the assets used for the provision of public services. + + |
+ + array of EssentialAsset objects + | +
+
+ hasEssentialAssets
+
+ |
+ + Has essential assets + | +
+ Whether there is information about the assets used for the provision of public services. + + |
+ + boolean + | +
+ EssentialAsset +
+ +
+ The extension defines a new EssentialAsset object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ Description of the essential asset. + + |
+ + string + | +
+
+ significance
+
+ |
+ + Significance + | +
+ Estimated percentage share of the essential asset provided in relation to the overall asset needed for the provision of the public services. + + |
+ + string + | +
+
+ predominance
+
+ |
+ + Predominance + | +
+ Estimated percentage share of asset provided compared to asset used for activities other than the public services. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/eu/1.1/extension.json b/en/extensions/eu/1.1/extension.json
new file mode 100644
index 000000000..3f8341ecd
--- /dev/null
+++ b/en/extensions/eu/1.1/extension.json
@@ -0,0 +1,34 @@
+{
+ "name": {
+ "en": "European Union",
+ "es": "Uni\u00f3n Europea"
+ },
+ "description": {
+ "en": "Implements fields and codes that are specific to European law.",
+ "es": "Implementa campos y c\u00f3digo que son espec\u00edficos de la legislaci\u00f3n europea."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/eu/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+documentType.csv",
+ "+itemClassificationScheme.csv",
+ "+milestoneType.csv",
+ "+partyRole.csv",
+ "+relatedProcessScheme.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json",
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_document_publisher_extension/master/extension.json"
+ ]
+}
diff --git a/en/extensions/eu/1.1/index.html b/en/extensions/eu/1.1/index.html
new file mode 100644
index 000000000..be9eb6468
--- /dev/null
+++ b/en/extensions/eu/1.1/index.html
@@ -0,0 +1,506 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + European Union +
+ ++ Implements fields and codes that are specific to European law. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +documentType.csv +
+ +
+ You can download the +documentType.csv file in English.
+
+ The extension adds these codes to the documentType.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ legislation
+
+ |
+ + Legislation + | +
+ A general regulatory framework applicable in the place where the contract is to be performed. For example, tax legislation, environmental protection legislation or employment protection and working conditions legislation. + +
|
+
+ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ eu-vehicle-category
+
+ |
+ + European Union vehicle category + | +
+ The category of vehicle falling within the scope of the EU Clean Vehicles Directive 2009/33/EC. + + + |
+
+
+ eu-cvd-contract-type
+
+ |
+ + European Union Clean Vehicle Directive contract type + | +
+ The category of contract according to the EU Clean Vehicles Directive 2009/33/EC. + + + |
+
+ +milestoneType.csv +
+ +
+ You can download the +milestoneType.csv file in English.
+
+ The extension adds these codes to the milestoneType.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ securityClearanceDeadline
+
+ |
+ + Security clearance deadline + | +
+ The tenderers may obtain their security clearance until this date. + + |
+
+ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ mediationBody
+
+ |
+ + Mediation body + | +
+ The body responsible for mediation procedures. + + |
+
+
+ centralPurchasingBody
+
+ |
+ + Central purchasing body + | +
+ The procuring entity providing centralized purchasing activities and, possibly, ancillary purchasing activities. + + |
+
+
+ processContactPoint
+
+ |
+ + Process contact point + | +
+ A contact point dedicated to this contracting process. + + |
+
+
+ reviewContactPoint
+
+ |
+ + Review contact point + | +
+ The service from which information about the review procedure can be obtained. + + |
+
+
+ selectedParticipant
+
+ |
+ + Selected participant + | +
+ An organization that has already been selected to participate in the design contest. + + |
+
+
+ procurementServiceProvider
+
+ |
+ + Procurement service provider + | +
+ An organization that provides ancillary procurement services to buyers. + + |
+
+
+ eSender
+
+ |
+ + TED eSender + | +
+ An organization that provides data transfer services to buyers. + + |
+
+
+ leadBuyer
+
+ |
+ + Lead buyer + | +
+ The lead buyer in a group of buyers. + + |
+
+
+ leadTenderer
+
+ |
+ + Lead tenderer + | +
+ The lead tenderer in the case of a consortium or equivalent. + + |
+
+
+ evaluationBody
+
+ |
+ + Evaluation body + | +
+ The organization responsible for evaluating bids or requests to participate. + + |
+
+
+ submissionReceiptBody
+
+ |
+ + Submission receipt body + | +
+ The organization responsible for receiving bids or requests to participate. + + |
+
+ +relatedProcessScheme.csv +
+ +
+ You can download the +relatedProcessScheme.csv file in English.
+
+ The extension adds these codes to the relatedProcessScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ eu-oj
+
+ |
+ + Official Journal of the European Union + | +
+ An Official Journal of the European Union contracting process identifier. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/eu/1.1/release-schema.json b/en/extensions/eu/1.1/release-schema.json
new file mode 100644
index 000000000..5a863dc34
--- /dev/null
+++ b/en/extensions/eu/1.1/release-schema.json
@@ -0,0 +1,201 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "reviewDetails": {
+ "title": "Review details",
+ "description": "Precise information concerning the time limits for the review procedures or contact information from which it can be obtained.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "valueCalculationMethod": {
+ "title": "Value calculation method",
+ "description": "The method used for calculating the estimated value of the concession.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "legislativeReferences": {
+ "title": "Legislative references",
+ "description": "Legislative references and associated contact points for information.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/LegislativeReference"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Organization": {
+ "properties": {
+ "details": {
+ "properties": {
+ "url": {
+ "title": "Website URL",
+ "description": "The website of the organization.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "buyerProfile": {
+ "title": "Buyer profile URL",
+ "description": "The Web address of the buyer profile.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "eDeliveryGateway": {
+ "title": "eDelivery gateway",
+ "description": "The organization's URL for the exchange of data and documents with eDelivery.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "valueCalculationMethod": {
+ "title": "Value calculation method",
+ "description": "Any details relevant to the value of the concession according to article 8(3) of Directive 2014/23/EU on concession contracts.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "periodRationale": {
+ "title": "Contract period rationale",
+ "description": "The rationale for the duration of the contract.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "publicPassengerTransportServicesKilometers": {
+ "title": "Kilometers of public passenger transport services",
+ "description": "The number of kilometers of public passenger transport services provided by a public service contract.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "minimum": 0
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "deliveryAddresses": {
+ "title": "Delivery addresses",
+ "description": "The addresse(s) to which the supplier delivers the item.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Address"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Period": {
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "The description of the period.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "LegislativeReference": {
+ "title": "Legislative reference",
+ "description": "Legislative reference and associated contact point",
+ "type": "object",
+ "properties": {
+ "title": {
+ "title": "Title",
+ "description": "The title of the legislative reference",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "url": {
+ "title": "URL",
+ "description": "A link to the Web page of the legislative reference.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "informationService": {
+ "title": "Information service",
+ "description": "An organization that can provide information about the legislative reference.",
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "minProperties": 1
+ },
+ "Lot": {
+ "properties": {
+ "awardPeriod": {
+ "title": "Award period",
+ "description": "The period for decision making regarding the contract award for the lot. The end date should be the date on which an award decision is due to be finalized. The start date may be used to indicate the start of an evaluation period.",
+ "$ref": "#/definitions/Period"
+ },
+ "hasAccessibilityCriteria": {
+ "title": "Has accessibility criteria",
+ "description": "Whether the technical specifications for the lot include accessibility criteria for people with disabilities.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "noAccessibilityCriteriaRationale": {
+ "title": "No accessibility criteria rationale",
+ "description": "The rationale for not including accessibility criteria when the object of the lot is intended for use by natural persons.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "reviewDetails": {
+ "title": "Review details",
+ "description": "Precise information concerning the time limits for the review procedures for the lot or contact information from which it can be obtained.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/eu/1.1/schema/index.html b/en/extensions/eu/1.1/schema/index.html
new file mode 100644
index 000000000..9f76cf81f
--- /dev/null
+++ b/en/extensions/eu/1.1/schema/index.html
@@ -0,0 +1,782 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + European Union +
+ ++ Implements fields and codes that are specific to European law. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Implements fields and codes that are specific to European law.
+For complete guidance on meeting the disclosure requirements of European law, see OCDS for eForms for the 2019 regulation, or OCDS for European Union for the 2015 regulation.
+Example
+{
+ "parties": [
+ {
+ "details": {
+ "url": "https://www.manchester.ac.uk/",
+ "buyerProfile": "https://in-tendhost.co.uk/universityofmanchester/aspx/Home"
+ },
+ "roles": [
+ "leadBuyer",
+ "awardingCentralPurchasingBody",
+ "evaluationBody",
+ "submissionReceiptBody"
+ ]
+ },
+ {
+ "name": "Royal Tax Office",
+ "id": "08797655",
+ "contactPoint": {
+ "name": "Crown Commercial Service",
+ "email": "info@crowncommercial.gov.uk",
+ "url": "https://www.gov.uk/government/publications/procurement-policy-note-0314-promoting-tax-compliance"
+ },
+ "roles": [
+ "informationService"
+ ]
+ },
+ {
+ "roles": [
+ "eSender"
+ ]
+ },
+ {
+ "roles": [
+ "procurementServiceProvider"
+ ]
+ },
+ {
+ "roles": [
+ "leadTenderer",
+ "tenderer"
+ ]
+ }
+ ],
+ "tender": {
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "reviewDetails": "NHS Wales Shared Services Partnership on behalf of Cardiff and Vale University Local Health Board will allow a minimum 10 calendar day standstill period between notifying the award decision and awarding the contract.",
+ "valueCalculationMethod": "Income from the sales of tickets over the duration of the contract minus the fees paid to the procuring entity.",
+ "items": [
+ {
+ "id": "item-1",
+ "description": "Printer ink cartridges",
+ "classification": {
+ "scheme": "CPV",
+ "id": "45233130.0",
+ "description": "Office supplies",
+ "uri": "http://cpv.data.ac.uk/code-45233130"
+ },
+ "deliveryAddresses": [
+ {
+ "streetAddress": "4, North London Business Park, Oakleigh Rd S",
+ "locality": "London",
+ "region": "London",
+ "postalCode": "N11 1NP",
+ "countryName": "United Kingdom"
+ }
+ ]
+ }
+ ],
+ "legislativeReferences": [
+ {
+ "title": "Direct taxation in the EU",
+ "url": "https://eur-lex.europa.eu/summary/chapter/2101.html",
+ "informationService": {
+ "name": "Royal Tax Office",
+ "id": "08797655"
+ }
+ }
+ ],
+ "lots": [
+ {
+ "id": "lot-1",
+ "awardPeriod": {
+ "durationInDays": 30,
+ "startDate": "2020-11-06T00:00:00Z",
+ "endDate": "2020-12-06T00:00:00Z"
+ },
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "additionalClassifications": [
+ {
+ "id": "oth-serv-contr",
+ "scheme": "eu-cvd-contract-type",
+ "description": "Other service contract"
+ }
+ ]
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2020-11-19T00:00:00Z"
+ }
+ ],
+ "documents": [
+ {
+ "id": "Fiscal1",
+ "documentType": "legislation"
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "award-1",
+ "valueCalculationMethod": "The awarded value takes into account the growing revenue expected from fees and the value of the equipment provided by the contracting authority.",
+ "items": [
+ {
+ "id": "1",
+ "additionalClassifications": [
+ {
+ "scheme": "eu-vehicle-category",
+ "id": "n2-n3",
+ "description": "Truck (N2-N3)"
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "contract-1",
+ "periodRationale": "The duration of the contract has been extended to anticipate the exceptional snowfall expected in January.",
+ "publicPassengerTransportServicesKilometers": 765,
+ "awardID": "award-1"
+ }
+ ],
+ "relatedProcesses": [
+ {
+ "id": "1",
+ "identifier": "123e4567-e89b-12d3-a456-426614174000",
+ "scheme": "eu-oj",
+ "relationship": [
+ "prior"
+ ]
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-08-01
+-
+
- Add fields:
+
-
+
Organization.eDeliveryGateway
+Lot.hasAccessibilityCriteria
+Lot.noAccessibilityCriteriaRationale
+Lot.reviewDetails
+
+
2023-06-30
+-
+
- Add
Period.descriptionfield.
+ - Add codes:
+
-
+
- classificationScheme.csv:
+
-
+
- 'eu-vehicle-category' +
- 'eu-cvd-contract-type' +
+ - documentType.csv:
+
-
+
- 'legislation' +
+ - partyRole.csv:
+
-
+
- 'procurementServiceProvider' +
- 'eSender' +
- 'leadBuyer' +
- 'leadTenderer' +
- 'evaluationBody' +
- 'submissionReceiptBody' +
+ - relatedProcessScheme.csv:
+
-
+
- 'eu-oj' +
+
+ - classificationScheme.csv:
+
- Move 'informationService' from the
+partyRole.csvcodelist to the Document publisher extension.
+
2022-05-27
+-
+
- Move
Lot.minimumValueto the Lots extension asLot.minValue.
+
2021-01-19
+-
+
- Set the object type of
informationServicetoOrganizationReference.
+ - Add 'informationService' code to
+partyRole.csvcodelist.
+
2020-10-06
+-
+
- Add
Lot.awardPeriodfield.
+
2020-10-05
+-
+
- Add
Lot.minimumValuefield.
+
2020-07-13
+-
+
- Add the 'securityClearanceDeadline' code to the
+milestoneType.csvcodelist.
+
2020-04-29
+-
+
- Add
Item.deliveryAddressesfield.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile, in this issue and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/eu/index.html b/en/extensions/eu/index.html
new file mode 100644
index 000000000..7210594a3
--- /dev/null
+++ b/en/extensions/eu/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + European Union +
+ ++ Implements fields and codes that are specific to European law. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ reviewDetails
+
+ |
+ + Review details + | +
+ Precise information concerning the time limits for the review procedures or contact information from which it can be obtained. + + |
+ + string + | +
+
+ valueCalculationMethod
+
+ |
+ + Value calculation method + | +
+ The method used for calculating the estimated value of the concession. + + |
+ + string + | +
+
+ legislativeReferences
+
+ |
+ + Legislative references + | +
+ Legislative references and associated contact points for information. + + |
+ + array of LegislativeReference objects + | +
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + Website URL + | +
+ The website of the organization. + + |
+ + string + | +
+
+ details.
+ |
+ + Buyer profile URL + | +
+ The Web address of the buyer profile. + + |
+ + string + | +
+
+ eDeliveryGateway
+
+ |
+ + eDelivery gateway + | +
+ The organization's URL for the exchange of data and documents with eDelivery. + + |
+ + string + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ valueCalculationMethod
+
+ |
+ + Value calculation method + | +
+ Any details relevant to the value of the concession according to article 8(3) of Directive 2014/23/EU on concession contracts. + + |
+ + string + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ periodRationale
+
+ |
+ + Contract period rationale + | +
+ The rationale for the duration of the contract. + + |
+ + string + | +
+
+ publicPassengerTransportServicesKilometers
+
+ |
+ + Kilometers of public passenger transport services + | +
+ The number of kilometers of public passenger transport services provided by a public service contract. + + |
+ + number + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryAddresses
+
+ |
+ + Delivery addresses + | +
+ The addresse(s) to which the supplier delivers the item. + + |
+ + array of Address objects + | +
+ Period +
+ +
+ The extension defines these fields in the Period object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ The description of the period. + + |
+ + string + | +
+ LegislativeReference +
+ +
+ The extension defines a new LegislativeReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Title + | +
+ The title of the legislative reference + + |
+ + string + | +
+
+ url
+
+ |
+ + URL + | +
+ A link to the Web page of the legislative reference. + + |
+ + string + | +
+
+ informationService
+
+ |
+ + Information service + | +
+ An organization that can provide information about the legislative reference. + + |
+ + OrganizationReference object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ awardPeriod
+
+ |
+ + Award period + | +
+ The period for decision making regarding the contract award for the lot. The end date should be the date on which an award decision is due to be finalized. The start date may be used to indicate the start of an evaluation period. + + |
+ + Period object + | +
+
+ hasAccessibilityCriteria
+
+ |
+ + Has accessibility criteria + | +
+ Whether the technical specifications for the lot include accessibility criteria for people with disabilities. + + |
+ + boolean + | +
+
+ noAccessibilityCriteriaRationale
+
+ |
+ + No accessibility criteria rationale + | +
+ The rationale for not including accessibility criteria when the object of the lot is intended for use by natural persons. + + |
+ + string + | +
+
+ reviewDetails
+
+ |
+ + Review details + | +
+ Precise information concerning the time limits for the review procedures for the lot or contact information from which it can be obtained. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/eu/1.1/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/eu/master/index.html b/en/extensions/eu/master/index.html
new file mode 100644
index 000000000..18dbe49fd
--- /dev/null
+++ b/en/extensions/eu/master/index.html
@@ -0,0 +1,507 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + European Union +
+ ++ Implements fields and codes that are specific to European law. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +documentType.csv +
+ +
+ You can download the +documentType.csv file in English.
+
+ The extension adds these codes to the documentType.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ legislation
+
+ |
+ + Legislation + | +
+ A general regulatory framework applicable in the place where the contract is to be performed. For example, tax legislation, environmental protection legislation or employment protection and working conditions legislation. + +
|
+
+ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ eu-vehicle-category
+
+ |
+ + European Union vehicle category + | +
+ The category of vehicle falling within the scope of the EU Clean Vehicles Directive 2009/33/EC. + + + |
+
+
+ eu-cvd-contract-type
+
+ |
+ + European Union Clean Vehicle Directive contract type + | +
+ The category of contract according to the EU Clean Vehicles Directive 2009/33/EC. + + + |
+
+ +milestoneType.csv +
+ +
+ You can download the +milestoneType.csv file in English.
+
+ The extension adds these codes to the milestoneType.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ securityClearanceDeadline
+
+ |
+ + Security clearance deadline + | +
+ The tenderers may obtain their security clearance until this date. + + |
+
+ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ mediationBody
+
+ |
+ + Mediation body + | +
+ The body responsible for mediation procedures. + + |
+
+
+ centralPurchasingBody
+
+ |
+ + Central purchasing body + | +
+ The procuring entity providing centralized purchasing activities and, possibly, ancillary purchasing activities. + + |
+
+
+ processContactPoint
+
+ |
+ + Process contact point + | +
+ A contact point dedicated to this contracting process. + + |
+
+
+ reviewContactPoint
+
+ |
+ + Review contact point + | +
+ The service from which information about the review procedure can be obtained. + + |
+
+
+ selectedParticipant
+
+ |
+ + Selected participant + | +
+ An organization that has already been selected to participate in the design contest. + + |
+
+
+ procurementServiceProvider
+
+ |
+ + Procurement service provider + | +
+ An organization that provides ancillary procurement services to buyers. + + |
+
+
+ eSender
+
+ |
+ + TED eSender + | +
+ An organization that provides data transfer services to buyers. + + |
+
+
+ leadBuyer
+
+ |
+ + Lead buyer + | +
+ The lead buyer in a group of buyers. + + |
+
+
+ leadTenderer
+
+ |
+ + Lead tenderer + | +
+ The lead tenderer in the case of a consortium or equivalent. + + |
+
+
+ evaluationBody
+
+ |
+ + Evaluation body + | +
+ The organization responsible for evaluating bids or requests to participate. + + |
+
+
+ submissionReceiptBody
+
+ |
+ + Submission receipt body + | +
+ The organization responsible for receiving bids or requests to participate. + + |
+
+ +relatedProcessScheme.csv +
+ +
+ You can download the +relatedProcessScheme.csv file in English.
+
+ The extension adds these codes to the relatedProcessScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ eu-oj
+
+ |
+ + Official Journal of the European Union + | +
+ An Official Journal of the European Union contracting process identifier. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/eu/master/release-schema.json b/en/extensions/eu/master/release-schema.json
new file mode 100644
index 000000000..5a863dc34
--- /dev/null
+++ b/en/extensions/eu/master/release-schema.json
@@ -0,0 +1,201 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "reviewDetails": {
+ "title": "Review details",
+ "description": "Precise information concerning the time limits for the review procedures or contact information from which it can be obtained.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "valueCalculationMethod": {
+ "title": "Value calculation method",
+ "description": "The method used for calculating the estimated value of the concession.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "legislativeReferences": {
+ "title": "Legislative references",
+ "description": "Legislative references and associated contact points for information.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/LegislativeReference"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Organization": {
+ "properties": {
+ "details": {
+ "properties": {
+ "url": {
+ "title": "Website URL",
+ "description": "The website of the organization.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "buyerProfile": {
+ "title": "Buyer profile URL",
+ "description": "The Web address of the buyer profile.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "eDeliveryGateway": {
+ "title": "eDelivery gateway",
+ "description": "The organization's URL for the exchange of data and documents with eDelivery.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "valueCalculationMethod": {
+ "title": "Value calculation method",
+ "description": "Any details relevant to the value of the concession according to article 8(3) of Directive 2014/23/EU on concession contracts.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "periodRationale": {
+ "title": "Contract period rationale",
+ "description": "The rationale for the duration of the contract.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "publicPassengerTransportServicesKilometers": {
+ "title": "Kilometers of public passenger transport services",
+ "description": "The number of kilometers of public passenger transport services provided by a public service contract.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "minimum": 0
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "deliveryAddresses": {
+ "title": "Delivery addresses",
+ "description": "The addresse(s) to which the supplier delivers the item.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Address"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Period": {
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "The description of the period.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "LegislativeReference": {
+ "title": "Legislative reference",
+ "description": "Legislative reference and associated contact point",
+ "type": "object",
+ "properties": {
+ "title": {
+ "title": "Title",
+ "description": "The title of the legislative reference",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "url": {
+ "title": "URL",
+ "description": "A link to the Web page of the legislative reference.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "informationService": {
+ "title": "Information service",
+ "description": "An organization that can provide information about the legislative reference.",
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "minProperties": 1
+ },
+ "Lot": {
+ "properties": {
+ "awardPeriod": {
+ "title": "Award period",
+ "description": "The period for decision making regarding the contract award for the lot. The end date should be the date on which an award decision is due to be finalized. The start date may be used to indicate the start of an evaluation period.",
+ "$ref": "#/definitions/Period"
+ },
+ "hasAccessibilityCriteria": {
+ "title": "Has accessibility criteria",
+ "description": "Whether the technical specifications for the lot include accessibility criteria for people with disabilities.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "noAccessibilityCriteriaRationale": {
+ "title": "No accessibility criteria rationale",
+ "description": "The rationale for not including accessibility criteria when the object of the lot is intended for use by natural persons.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "reviewDetails": {
+ "title": "Review details",
+ "description": "Precise information concerning the time limits for the review procedures for the lot or contact information from which it can be obtained.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/eu/master/schema/index.html b/en/extensions/eu/master/schema/index.html
new file mode 100644
index 000000000..ff5de8d81
--- /dev/null
+++ b/en/extensions/eu/master/schema/index.html
@@ -0,0 +1,783 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + European Union +
+ ++ Implements fields and codes that are specific to European law. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Implements fields and codes that are specific to European law.
+For complete guidance on meeting the disclosure requirements of European law, see OCDS for eForms for the 2019 regulation, or OCDS for European Union for the 2015 regulation.
+Example
+{
+ "parties": [
+ {
+ "details": {
+ "url": "https://www.manchester.ac.uk/",
+ "buyerProfile": "https://in-tendhost.co.uk/universityofmanchester/aspx/Home"
+ },
+ "roles": [
+ "leadBuyer",
+ "awardingCentralPurchasingBody",
+ "evaluationBody",
+ "submissionReceiptBody"
+ ]
+ },
+ {
+ "name": "Royal Tax Office",
+ "id": "08797655",
+ "contactPoint": {
+ "name": "Crown Commercial Service",
+ "email": "info@crowncommercial.gov.uk",
+ "url": "https://www.gov.uk/government/publications/procurement-policy-note-0314-promoting-tax-compliance"
+ },
+ "roles": [
+ "informationService"
+ ]
+ },
+ {
+ "roles": [
+ "eSender"
+ ]
+ },
+ {
+ "roles": [
+ "procurementServiceProvider"
+ ]
+ },
+ {
+ "roles": [
+ "leadTenderer",
+ "tenderer"
+ ]
+ }
+ ],
+ "tender": {
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "reviewDetails": "NHS Wales Shared Services Partnership on behalf of Cardiff and Vale University Local Health Board will allow a minimum 10 calendar day standstill period between notifying the award decision and awarding the contract.",
+ "valueCalculationMethod": "Income from the sales of tickets over the duration of the contract minus the fees paid to the procuring entity.",
+ "items": [
+ {
+ "id": "item-1",
+ "description": "Printer ink cartridges",
+ "classification": {
+ "scheme": "CPV",
+ "id": "45233130.0",
+ "description": "Office supplies",
+ "uri": "http://cpv.data.ac.uk/code-45233130"
+ },
+ "deliveryAddresses": [
+ {
+ "streetAddress": "4, North London Business Park, Oakleigh Rd S",
+ "locality": "London",
+ "region": "London",
+ "postalCode": "N11 1NP",
+ "countryName": "United Kingdom"
+ }
+ ]
+ }
+ ],
+ "legislativeReferences": [
+ {
+ "title": "Direct taxation in the EU",
+ "url": "https://eur-lex.europa.eu/summary/chapter/2101.html",
+ "informationService": {
+ "name": "Royal Tax Office",
+ "id": "08797655"
+ }
+ }
+ ],
+ "lots": [
+ {
+ "id": "lot-1",
+ "awardPeriod": {
+ "durationInDays": 30,
+ "startDate": "2020-11-06T00:00:00Z",
+ "endDate": "2020-12-06T00:00:00Z"
+ },
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "additionalClassifications": [
+ {
+ "id": "oth-serv-contr",
+ "scheme": "eu-cvd-contract-type",
+ "description": "Other service contract"
+ }
+ ]
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2020-11-19T00:00:00Z"
+ }
+ ],
+ "documents": [
+ {
+ "id": "Fiscal1",
+ "documentType": "legislation"
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "award-1",
+ "valueCalculationMethod": "The awarded value takes into account the growing revenue expected from fees and the value of the equipment provided by the contracting authority.",
+ "items": [
+ {
+ "id": "1",
+ "additionalClassifications": [
+ {
+ "scheme": "eu-vehicle-category",
+ "id": "n2-n3",
+ "description": "Truck (N2-N3)"
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "contract-1",
+ "periodRationale": "The duration of the contract has been extended to anticipate the exceptional snowfall expected in January.",
+ "publicPassengerTransportServicesKilometers": 765,
+ "awardID": "award-1"
+ }
+ ],
+ "relatedProcesses": [
+ {
+ "id": "1",
+ "identifier": "123e4567-e89b-12d3-a456-426614174000",
+ "scheme": "eu-oj",
+ "relationship": [
+ "prior"
+ ]
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-08-01
+-
+
- Add fields:
+
-
+
Organization.eDeliveryGateway
+Lot.hasAccessibilityCriteria
+Lot.noAccessibilityCriteriaRationale
+Lot.reviewDetails
+
+
2023-06-30
+-
+
- Add
Period.descriptionfield.
+ - Add codes:
+
-
+
- classificationScheme.csv:
+
-
+
- 'eu-vehicle-category' +
- 'eu-cvd-contract-type' +
+ - documentType.csv:
+
-
+
- 'legislation' +
+ - partyRole.csv:
+
-
+
- 'procurementServiceProvider' +
- 'eSender' +
- 'leadBuyer' +
- 'leadTenderer' +
- 'evaluationBody' +
- 'submissionReceiptBody' +
+ - relatedProcessScheme.csv:
+
-
+
- 'eu-oj' +
+
+ - classificationScheme.csv:
+
- Move 'informationService' from the
+partyRole.csvcodelist to the Document publisher extension.
+
2022-05-27
+-
+
- Move
Lot.minimumValueto the Lots extension asLot.minValue.
+
2021-01-19
+-
+
- Set the object type of
informationServicetoOrganizationReference.
+ - Add 'informationService' code to
+partyRole.csvcodelist.
+
2020-10-06
+-
+
- Add
Lot.awardPeriodfield.
+
2020-10-05
+-
+
- Add
Lot.minimumValuefield.
+
2020-07-13
+-
+
- Add the 'securityClearanceDeadline' code to the
+milestoneType.csvcodelist.
+
2020-04-29
+-
+
- Add
Item.deliveryAddressesfield.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile, in this issue and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/exclusionGrounds/index.html b/en/extensions/exclusionGrounds/index.html
new file mode 100644
index 000000000..a03cabd2c
--- /dev/null
+++ b/en/extensions/exclusionGrounds/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + European Union +
+ ++ Implements fields and codes that are specific to European law. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ reviewDetails
+
+ |
+ + Review details + | +
+ Precise information concerning the time limits for the review procedures or contact information from which it can be obtained. + + |
+ + string + | +
+
+ valueCalculationMethod
+
+ |
+ + Value calculation method + | +
+ The method used for calculating the estimated value of the concession. + + |
+ + string + | +
+
+ legislativeReferences
+
+ |
+ + Legislative references + | +
+ Legislative references and associated contact points for information. + + |
+ + array of LegislativeReference objects + | +
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + Website URL + | +
+ The website of the organization. + + |
+ + string + | +
+
+ details.
+ |
+ + Buyer profile URL + | +
+ The Web address of the buyer profile. + + |
+ + string + | +
+
+ eDeliveryGateway
+
+ |
+ + eDelivery gateway + | +
+ The organization's URL for the exchange of data and documents with eDelivery. + + |
+ + string + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ valueCalculationMethod
+
+ |
+ + Value calculation method + | +
+ Any details relevant to the value of the concession according to article 8(3) of Directive 2014/23/EU on concession contracts. + + |
+ + string + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ periodRationale
+
+ |
+ + Contract period rationale + | +
+ The rationale for the duration of the contract. + + |
+ + string + | +
+
+ publicPassengerTransportServicesKilometers
+
+ |
+ + Kilometers of public passenger transport services + | +
+ The number of kilometers of public passenger transport services provided by a public service contract. + + |
+ + number + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryAddresses
+
+ |
+ + Delivery addresses + | +
+ The addresse(s) to which the supplier delivers the item. + + |
+ + array of Address objects + | +
+ Period +
+ +
+ The extension defines these fields in the Period object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ The description of the period. + + |
+ + string + | +
+ LegislativeReference +
+ +
+ The extension defines a new LegislativeReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Title + | +
+ The title of the legislative reference + + |
+ + string + | +
+
+ url
+
+ |
+ + URL + | +
+ A link to the Web page of the legislative reference. + + |
+ + string + | +
+
+ informationService
+
+ |
+ + Information service + | +
+ An organization that can provide information about the legislative reference. + + |
+ + OrganizationReference object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ awardPeriod
+
+ |
+ + Award period + | +
+ The period for decision making regarding the contract award for the lot. The end date should be the date on which an award decision is due to be finalized. The start date may be used to indicate the start of an evaluation period. + + |
+ + Period object + | +
+
+ hasAccessibilityCriteria
+
+ |
+ + Has accessibility criteria + | +
+ Whether the technical specifications for the lot include accessibility criteria for people with disabilities. + + |
+ + boolean + | +
+
+ noAccessibilityCriteriaRationale
+
+ |
+ + No accessibility criteria rationale + | +
+ The rationale for not including accessibility criteria when the object of the lot is intended for use by natural persons. + + |
+ + string + | +
+
+ reviewDetails
+
+ |
+ + Review details + | +
+ Precise information concerning the time limits for the review procedures for the lot or contact information from which it can be obtained. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/exclusionGrounds/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/exclusionGrounds/master/release-schema.json b/en/extensions/exclusionGrounds/master/release-schema.json
new file mode 100644
index 000000000..d0b0955b0
--- /dev/null
+++ b/en/extensions/exclusionGrounds/master/release-schema.json
@@ -0,0 +1,58 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "exclusionGrounds": {
+ "title": "Exclusion grounds",
+ "description": "Information about the criteria regarding the situation of a tenderer that can lead to its exclusion from the contracting process. For example: criminal convictions, bankruptcy, presence on a blacklist or failure to pay taxes.",
+ "$ref": "#/definitions/ExclusionGrounds"
+ }
+ }
+ },
+ "ExclusionGrounds": {
+ "title": "Exclusion grounds",
+ "description": "Information about the criteria regarding the situation of a tenderer that can lead to its exclusion from the contracting process. For example: criminal convictions, bankruptcy, presence on a blacklist or failure to pay taxes.",
+ "type": "object",
+ "properties": {
+ "criteria": {
+ "title": "Exclusion criteria",
+ "description": "The exclusion criteria.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/ExclusionCriterion"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "ExclusionCriterion": {
+ "title": "Exclusion criterion",
+ "description": "A criterion regarding the situation of a tenderer that can lead to its exclusion from the contracting process.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Type",
+ "description": "The type of the criterion.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "The description of the criterion.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/exclusionGrounds/master/schema/index.html b/en/extensions/exclusionGrounds/master/schema/index.html
new file mode 100644
index 000000000..b4078d685
--- /dev/null
+++ b/en/extensions/exclusionGrounds/master/schema/index.html
@@ -0,0 +1,350 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Exclusion grounds +
+ ++ Adds an object to describe the criteria to exclude tenderers from participating in a contracting process. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an object to describe the criteria to exclude tenderers from participating in a contracting process.
+Guidance
+If you use a codelist for tender.exclusionGrounds.criteria.type, you should explain where the codes are from in your publication policy/user guide.
Example
+{
+ "tender": {
+ "id": "1",
+ "exclusionGrounds": {
+ "criteria": [
+ {
+ "description": "Applicants not satisfying...",
+ "type": "crime-org"
+ }
+ ]
+ }
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/extendsContractID/index.html b/en/extensions/extendsContractID/index.html
new file mode 100644
index 000000000..8a4cb0c79
--- /dev/null
+++ b/en/extensions/extendsContractID/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Exclusion grounds +
+ ++ Adds an object to describe the criteria to exclude tenderers from participating in a contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ exclusionGrounds
+
+ |
+ + Exclusion grounds + | +
+ Information about the criteria regarding the situation of a tenderer that can lead to its exclusion from the contracting process. For example: criminal convictions, bankruptcy, presence on a blacklist or failure to pay taxes. + + |
+ + ExclusionGrounds object + | +
+ ExclusionGrounds +
+ +
+ The extension defines a new ExclusionGrounds object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ criteria
+
+ |
+ + Exclusion criteria + | +
+ The exclusion criteria. + + |
+ + array of ExclusionCriterion objects + | +
+ ExclusionCriterion +
+ +
+ The extension defines a new ExclusionCriterion object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Type + | +
+ The type of the criterion. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ The description of the criterion. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/extendsContractID/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/extendsContractID/master/release-schema.json b/en/extensions/extendsContractID/master/release-schema.json
new file mode 100644
index 000000000..4236398b6
--- /dev/null
+++ b/en/extensions/extendsContractID/master/release-schema.json
@@ -0,0 +1,17 @@
+{
+ "definitions": {
+ "Contract": {
+ "properties": {
+ "extendsContractID": {
+ "title": "Extends contract ID",
+ "description": "If this contract extends or amends a previously issued contract, then the contract.id value for the extended/amended contract can be provided here.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/extendsContractID/master/schema/index.html b/en/extensions/extendsContractID/master/schema/index.html
new file mode 100644
index 000000000..99e376c6b
--- /dev/null
+++ b/en/extensions/extendsContractID/master/schema/index.html
@@ -0,0 +1,231 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Contract extensions via supplementary contract: extendsContractID +
+ ++ Under some procurement rules and processes, to extend the duration or value of a contract, or to make other substantial alterations, requires a new contract to be signed. This extension allows these relationships between two or more contracts in the same contracting process to be made explicit. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Under some procurement rules and processes, to extend the duration or value of a contract, or to make other substantial alterations, requires a new contract to be signed.
+This new contract will form part of the same overall contracting process as the old contract which it extends.
+In these cases, the extendsContractID field can be used to identify that a given entry in the contracts array should be understood as related to a previous contract.
Use this extension only if there is a substantive new contract signed as the extension of a previous contract. In most cases, an update to the value or duration of a contract should be modelled as an amendment within a single entry in the contracts array.
Example
+The extract below shows three contracts in the contracts array of an OCDS release.
+The first two contracts were signed in 2011: one for one year for property rental, and the other for two years for services related to property rental.
+The third contract was signed in 2012, and renews the property rental for another year. This is related back to the contract for the first year of rental with the extendsContractID field.
{
+ "contracts": [
+ {
+ "id": "207002-armin-hahner-stollmaier-21",
+ "awardID": "207002-armin-hahner-stollmaier-21",
+ "title": "Alquileres para la SNNA",
+ "status": "terminated",
+ "period": {
+ "startDate": "2011-01-02T23:59:59+00:00",
+ "endDate": "2012-01-02T23:59:59+00:00"
+ },
+ "value": {
+ "amount": 1800000,
+ "currency": "PYG"
+ },
+ "items": [
+ {
+ "id": "01",
+ "description": "Alquiler de Inmueble",
+ "classification": {
+ "scheme": "CPV",
+ "id": "70000000-1",
+ "description": "Real Estate Services",
+ "uri": "http://cpv.data.ac.uk/code-70000000"
+ }
+ }
+ ],
+ "dateSigned": "2011-03-14T16:58:40+00:00"
+ },
+ {
+ "id": "207004-armin-hahner-stollmaier-21-service",
+ "awardID": "207002-armin-hahner-stollmaier-21",
+ "title": "Servicios relacionados con alquileres para la SNNA",
+ "status": "active",
+ "period": {
+ "startDate": "2011-01-02T23:59:59+00:00",
+ "endDate": "2013-01-02T23:59:59+00:00"
+ },
+ "value": {
+ "amount": 10000,
+ "currency": "PYG"
+ },
+ "items": [
+ {
+ "id": "02",
+ "description": "Servicios relacionados con alquiler de Inmueble",
+ "classification": {
+ "scheme": "CPV",
+ "id": "70000000-1",
+ "description": "Real Estate Services",
+ "uri": "http://cpv.data.ac.uk/code-70000000"
+ }
+ }
+ ],
+ "dateSigned": "2011-03-14T16:58:40+00:00"
+ },
+ {
+ "id": "207002-armin-hahner-stollmaier-21-renovacion",
+ "awardID": "207002-armin-hahner-stollmaier-21",
+ "extendsContractID": "207002-armin-hahner-stollmaier",
+ "title": "Ad Referendum - Alquileres para la SNNA (Amends contract 207002)",
+ "status": "active",
+ "period": {
+ "startDate": "2012-01-02T23:59:59+00:00",
+ "endDate": "2013-01-02T23:59:59+00:00"
+ },
+ "value": {
+ "amount": 12780000,
+ "currency": "PYG"
+ },
+ "items": [
+ {
+ "id": "01",
+ "description": "Alquiler de Inmueble",
+ "classification": {
+ "scheme": "CPV",
+ "id": "70000000-1",
+ "description": "Real Estate Services",
+ "uri": "http://cpv.data.ac.uk/code-70000000"
+ }
+ }
+ ],
+ "dateSigned": "2012-03-14T16:58:40+00:00"
+ }
+ ]
+}
+The image below shows an example of how the information provided by the extendsContractID field is used in Paraguay, to display two contracts resulting from an award (the blue boxes), with one of those contracts then extended (the blue circle).
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-06-04
+-
+
- Review normative and non-normative words. +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2018-01-29
+-
+
- Make
Contract.extendsContractIDnullable.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/finance/index.html b/en/extensions/finance/index.html
new file mode 100644
index 000000000..4dfb39b4c
--- /dev/null
+++ b/en/extensions/finance/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Contract extensions via supplementary contract: extendsContractID +
+ ++ Under some procurement rules and processes, to extend the duration or value of a contract, or to make other substantial alterations, requires a new contract to be signed. This extension allows these relationships between two or more contracts in the same contracting process to be made explicit. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ extendsContractID
+
+ |
+ + Extends contract ID + | +
+ If this contract extends or amends a previously issued contract, then the contract.id value for the extended/amended contract can be provided here. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/finance/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/finance/master/extension.json b/en/extensions/finance/master/extension.json
new file mode 100644
index 000000000..fea48ed2e
--- /dev/null
+++ b/en/extensions/finance/master/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Finance",
+ "es": "Financiamiento"
+ },
+ "description": {
+ "en": "Adds fields to disclose the financing of the whole process and its individual contracts.",
+ "es": "Agrega campos para revelar la financiaci\u00f3n de todo el proceso y sus contratos individuales."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/finance/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "financeCategory.csv",
+ "financeType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/finance/master/index.html b/en/extensions/finance/master/index.html
new file mode 100644
index 000000000..63a1c81db
--- /dev/null
+++ b/en/extensions/finance/master/index.html
@@ -0,0 +1,418 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Finance +
+ ++ Adds fields to disclose the financing of the whole process and its individual contracts. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ financeCategory.csv +
+ +
+ You can download the financeCategory.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ equity
+
+ |
+ + Equity + | +
+ Equity finance is given in exchange for a share of ownership in the project (usually via direct or indirect shareholding in a Special Purpose Vehicle (SPV) company created to run the project). + + |
+
+
+ seniorDebt
+
+ |
+ + Senior debt + | +
+ Senior debt (sometimes called senior loans) take priority over other more junior debt. + + |
+
+
+ mezzanineDebt
+
+ |
+ + Mezzanine debt + | +
+ Mezzanine debt (sometimes called mezzanine loans) take priority over common shares. + + |
+
+
+ grant
+
+ |
+ + Grant + | +
+ A grant is finance provided without expectation of repayment. + + |
+
+
+ guarantee
+
+ |
+ + Guarantee + | +
+ A guarantee is a promise by one party to assume the debt of another if the other defaults. Guarantees are not to be counted in totals of the overall financing of a project. + + |
+
+
+ other
+
+ |
+ + Other debts or investments + | +
+ Any details of the conditions attached to this finance can be provided in the notes field. + + |
+
+ financeType.csv +
+ +
+ You can download the financeType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ institutional
+
+ |
+ + Institutional + | +
+ This finance was provided by institutional investors: organizations that pool money to purchase securities, real property, and other investment assets or originate loans. Institutional investors include banks, insurance companies, pensions, hedge funds, REITs, investment advisors, endowments, and mutual funds. + +
|
+
+
+ commercial
+
+ |
+ + Commercial + | +
+ This finance was provided by private parties who do not fall within the definition of institutional investor. + + |
+
+
+ bilateral
+
+ |
+ + Bilateral + | +
+ This finance was provided by a bilateral institution: an agency of one specific government, usually a development agency or export-credit agency with a mandate to support domestic businesses in pursuing investments abroad. + +
|
+
+
+ multilateral
+
+ |
+ + Multilateral + | +
+ This finance was provided by a multilateral institution: a body created by a group of countries to provides financing and professional support, primarily for the purpose of development. + + + |
+
+
+ publicBondIssue
+
+ |
+ + Public bond issue + | +
+ This finance was provided through a public bond issue. + + |
+
+
+ supplierCredit
+
+ |
+ + Supplier credit + | +
+ This finance was provided through a line of credit provided by a supplier. + + |
+
+
+ other
+
+ |
+ + Other + | +
+ This finance was provided through some other source. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/finance/master/release-schema.json b/en/extensions/finance/master/release-schema.json
new file mode 100644
index 000000000..e8eb8cf8e
--- /dev/null
+++ b/en/extensions/finance/master/release-schema.json
@@ -0,0 +1,207 @@
+{
+ "definitions": {
+ "Contract": {
+ "properties": {
+ "finance": {
+ "title": "Finance",
+ "description": "An array with details of each source of finance arranged for this contract.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Finance"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Budget": {
+ "properties": {
+ "finance": {
+ "title": "Finance",
+ "description": "An array with details of each source of finance planned for this procedure.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Finance"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Finance": {
+ "title": "Financing arrangement",
+ "description": "Information about a financing arrangement.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "An identifier for this financing arrangement.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "Title",
+ "description": "A short title for this financing arrangement.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "A short description of this financing arrangement. This may include details of lender rights, step in arrangements, exchange rate guarantees, and for syndicated loans, details of syndication and any members of the syndicate.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "financingParty": {
+ "title": "Financing organization",
+ "description": "The organization providing this financing arrangement.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "financeType": {
+ "title": "Finance type",
+ "description": "The type of finance arranged.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "financeType.csv",
+ "openCodelist": false,
+ "enum": [
+ "institutional",
+ "commercial",
+ "bilateral",
+ "multilateral",
+ "publicBondIssue",
+ "supplierCredit",
+ "other",
+ null
+ ]
+ },
+ "financeCategory": {
+ "title": "Finance category",
+ "description": "The nature of the finance, relevant to determining the order of preference for investors to get their money back in case of liquidation.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "financeCategory.csv",
+ "openCodelist": false,
+ "enum": [
+ "equity",
+ "seniorDebt",
+ "mezzanineDebt",
+ "grant",
+ "guarantee",
+ "other",
+ null
+ ]
+ },
+ "value": {
+ "title": "Value",
+ "description": "The total value of this finance.",
+ "$ref": "#/definitions/Value"
+ },
+ "period": {
+ "title": "Finance period",
+ "description": "What period is covered by this finance.",
+ "$ref": "#/definitions/Period"
+ },
+ "interestRate": {
+ "title": "Interest rate",
+ "description": "The interest rate associated with this finance.",
+ "type": "object",
+ "properties": {
+ "base": {
+ "title": "Base",
+ "description": "The variable to which an additional margin amount is added to get the Interest amount. This can be specified as a fixed number, as a known variable (e.g. LIBOR or LIBOR+1%), or can be omitted if margin specifies the entire interest rate.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "margin": {
+ "title": "Margin",
+ "description": "The variable added to the base to give the Interest amount expressed as a decimal fraction (e.g. 12.5% = 0.125).",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "fixed": {
+ "title": "Fixed rate",
+ "description": "A boolean field. If this interest rate of fixed, set to true. Otherwise, set to false.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "notes": {
+ "title": "Notes",
+ "description": "Any explanatory notes concerning the interest rate.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "repaymentFrequency": {
+ "title": "Repayment frequency (days)",
+ "description": "What is the average repayment frequency (in days) for this source of finance. For example, for yearly, use 365; for monthly repayment use 30.4; for daily use 1. User interfaces may wish to translate this into a more user-friendly presentation, such as 'daily','monthly' or 'yearly'.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "minimum": 0
+ },
+ "stepInRights": {
+ "title": "Step in rights",
+ "description": "Whether provision of this finance confers any step in rights to the financing organization.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "exchangeRateGuarantee": {
+ "title": "Exchange rate guarantees",
+ "description": "Whether there is an associated exchange rate guarantee with this source of finance.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "The identifiers of the lots to which this financing arrangement relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "finance",
+ "version": "master"
+ }
+ }
+ }
+}
diff --git a/en/extensions/finance/master/schema/index.html b/en/extensions/finance/master/schema/index.html
new file mode 100644
index 000000000..d48275402
--- /dev/null
+++ b/en/extensions/finance/master/schema/index.html
@@ -0,0 +1,610 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Finance +
+ ++ Adds fields to disclose the financing of the whole process and its individual contracts. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds fields to disclose the financing of the whole process and its individual contracts.
+Sometimes, particularly in the case of Public Private Partnerships, contracts are financed using a range of instruments, including loans, grants, share issues and so-on. This information can be updated over the lifetime of the contract.
+Legal context
+In the European Union, this extension's fields correspond to eForms BG-611 (Contract EU funds) and BG-61 (EU funds). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Codelists
+The financeType.csv codelist is based on the list on Page 57 of the World Bank PPP Disclosure Framework
Examples
+Procurement process financing
+{
+ "planning": {
+ "budget": {
+ "description": "Adquisición de equipos odontológicos para las Unidades de Salud de la Familia",
+ "amount": {
+ "currency": "PYG",
+ "amount": 643702500
+ },
+ "finance": [
+ {
+ "id": "1",
+ "title": "Presupuesto de financiación de deuda primaria",
+ "financingParty": {
+ "id": "XX-FI-22222222",
+ "name": "Banco Interamericano de Desarrollo (BID)"
+ },
+ "financeCategory": "seniorDebt",
+ "financeType": "multilateral",
+ "value": {
+ "amount": 643702500,
+ "currency": "PYG"
+ }
+ }
+ ]
+ }
+ }
+}
+Public-private partnership contract financing
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "title": "Public Private Partnership Agreement",
+ "description": "Public-Private Partnership agreement entered into by and between telecoms promoter, together with national fibre infrastructure and the special purpose vehicle Mega Consortium Ltd",
+ "finance": [
+ {
+ "id": "1",
+ "title": "Primary senior debt financing agreement",
+ "description": "Big Bank Corp retains the right to step in should Mega Consortium fail to comply with the repayment schedule for a period of 3 consecutive months.",
+ "financingParty": {
+ "id": "XX-FI-22222222",
+ "name": "Big Bank Corp"
+ },
+ "financeCategory": "seniorDebt",
+ "value": {
+ "amount": 41000000,
+ "currency": "USD"
+ },
+ "period": {
+ "startDate": "2016-01-24T00:00:00Z",
+ "endDate": "2021-01-23T00:00:00Z"
+ },
+ "interestRate": {
+ "base": "LIBOR",
+ "margin": 0.03,
+ "fixed": false
+ },
+ "stepInRights": true,
+ "exchangeRateGuarantee": false,
+ "repaymentFrequency": 30.4
+ },
+ {
+ "id": "2",
+ "title": "Alpha Holdings equity investment",
+ "financingParty": {
+ "id": "XX-XXX-11111111",
+ "name": "Alpha Holdings Ltd"
+ },
+ "financeCategory": "equity",
+ "value": {
+ "amount": 6674000,
+ "currency": "USD"
+ }
+ }
+ ]
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2022-05-17
+-
+
- Move
Finance.relatedLotsfrom the Lots extension
+
2020-06-04
+-
+
- Review normative and non-normative words. +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2020-04-17
+-
+
- Add
planning.budget.financefield.
+ - Fix description of
financeCategory.
+
2019-03-20
+-
+
- Set
"uniqueItems": trueon array fields, and add"minLength": 1on required string fields.
+ - Make
interestRatenon-nullable (undo earlier change).
+
2018-05-08
+-
+
- Make
Finance.idrequired and non-nullable to support revision tracking and list merging
+
2018-05-01
+-
+
- Add title and description to
Finance.financingParty.
+
2018-01-29
+-
+
- Make
interestRatenullable.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/guarantees/index.html b/en/extensions/guarantees/index.html
new file mode 100644
index 000000000..0d992555b
--- /dev/null
+++ b/en/extensions/guarantees/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Finance +
+ ++ Adds fields to disclose the financing of the whole process and its individual contracts. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ finance
+
+ |
+ + Finance + | +
+ An array with details of each source of finance arranged for this contract. + + |
+ + array of Finance objects + | +
+ Budget +
+ +
+ The extension defines these fields in the Budget object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ finance
+
+ |
+ + Finance + | +
+ An array with details of each source of finance planned for this procedure. + + |
+ + array of Finance objects + | +
+ Finance +
+ +
+ The extension defines a new Finance object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ An identifier for this financing arrangement. + + |
+ + string + | +
+
+ title
+
+ |
+ + Title + | +
+ A short title for this financing arrangement. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A short description of this financing arrangement. This may include details of lender rights, step in arrangements, exchange rate guarantees, and for syndicated loans, details of syndication and any members of the syndicate. + + |
+ + string + | +
+
+ financingParty
+
+ |
+ + Financing organization + | +
+ The organization providing this financing arrangement. + + |
+ + OrganizationReference object + | +
+
+ financeType
+
+ |
+ + Finance type + | +
+ The type of finance arranged. + + |
+ + string from closed financeType codelist + | +
+
+ financeCategory
+
+ |
+ + Finance category + | +
+ The nature of the finance, relevant to determining the order of preference for investors to get their money back in case of liquidation. + + |
+ + string from closed financeCategory codelist + | +
+
+ value
+
+ |
+ + Value + | +
+ The total value of this finance. + + |
+ + Value object + | +
+
+ period
+
+ |
+ + Finance period + | +
+ What period is covered by this finance. + + |
+ + Period object + | +
+
+ interestRate
+
+ |
+ + Interest rate + | +
+ The interest rate associated with this finance. + + |
+ + object + | +
+
+ interestRate.
+ |
+ + Base + | +
+ The variable to which an additional margin amount is added to get the Interest amount. This can be specified as a fixed number, as a known variable (e.g. LIBOR or LIBOR+1%), or can be omitted if margin specifies the entire interest rate. + + |
+ + string or number + | +
+
+ interestRate.
+ |
+ + Margin + | +
+ The variable added to the base to give the Interest amount expressed as a decimal fraction (e.g. 12.5% = 0.125). + + |
+ + number + | +
+
+ interestRate.
+ |
+ + Fixed rate + | +
+ A boolean field. If this interest rate of fixed, set to true. Otherwise, set to false. + + |
+ + boolean + | +
+
+ interestRate.
+ |
+ + Notes + | +
+ Any explanatory notes concerning the interest rate. + + |
+ + string + | +
+
+ repaymentFrequency
+
+ |
+ + Repayment frequency (days) + | +
+ What is the average repayment frequency (in days) for this source of finance. For example, for yearly, use 365; for monthly repayment use 30.4; for daily use 1. User interfaces may wish to translate this into a more user-friendly presentation, such as 'daily','monthly' or 'yearly'. + + |
+ + number + | +
+
+ stepInRights
+
+ |
+ + Step in rights + | +
+ Whether provision of this finance confers any step in rights to the financing organization. + + |
+ + boolean + | +
+
+ exchangeRateGuarantee
+
+ |
+ + Exchange rate guarantees + | +
+ Whether there is an associated exchange rate guarantee with this source of finance. + + |
+ + boolean + | +
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ The identifiers of the lots to which this financing arrangement relates. + + |
+ + array of strings + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/guarantees/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/guarantees/master/extension.json b/en/extensions/guarantees/master/extension.json
new file mode 100644
index 000000000..2ed237dc1
--- /dev/null
+++ b/en/extensions/guarantees/master/extension.json
@@ -0,0 +1,24 @@
+{
+ "name": {
+ "en": "Guarantees",
+ "es": "Garant\u00edas"
+ },
+ "description": {
+ "en": "Some procurement processes consider the specification of guarantees in order to ensure compliance with the terms of a contract.\n\nThere are many types of guarantees, so we consider the creation of a new extension based on the formats that are required for the Federal Treasury (Mexico). See discussion in https://github.com/open-contracting/standard/issues/651",
+ "es": "Algunos procesos de contrataci\u00f3n consideran la especificaci\u00f3n de garant\u00edas para asegurar el cumplimiento de los t\u00e9rminos de un contrato.\n\nExisten muchos tipos de garant\u00edas, por lo que consideramos a la creaci\u00f3n de una nueva extensi\u00f3n basada en los formatos que se requieren para la Tesorer\u00eda de la Federaci\u00f3n (M\u00e9xico). Ver discusi\u00f3n en https://github.com/open-contracting/standard/issues/651"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "documentationUrl": {
+ "en": "https://github.com/contratacionesabiertas/ocds_guarantees_extension"
+ },
+ "codelists": [
+ "guaranteeType.csv",
+ "guaranteedObligations.csv",
+ "+partyRole.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/en/extensions/guarantees/master/index.html b/en/extensions/guarantees/master/index.html
new file mode 100644
index 000000000..3ba43819e
--- /dev/null
+++ b/en/extensions/guarantees/master/index.html
@@ -0,0 +1,460 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Guarantees +
+ ++ Some procurement processes consider the specification of guarantees in order to ensure compliance with the terms of a contract. + +There are many types of guarantees, so we consider the creation of a new extension based on the formats that are required for the Federal Treasury (Mexico). See discussion in https://github.com/open-contracting/standard/issues/651 +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ guarantor
+
+ |
+ + Guarantor + | +
+ Institution that issues the guarantee. + + |
+
+ guaranteeType.csv +
+ +
+ You can download the guaranteeType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ bail
+
+ |
+ + Bail + | +
+ A bail bond is a written promise by which a person agrees with the creditor to pay for the debtor, if he does not. + + |
+
+
+ depositSlip
+
+ |
+ + Deposit slip + | +
+ The deposit slip is an instrument used to establish cash guarantees available to judicial or administrative authorities. + + |
+
+
+ letterOfCredit
+
+ |
+ + Letter of credit + | +
+ Letters of credit are used to guarantee that a supplier will receive a specified amount of money within a specified time providing strict terms. + + |
+
+
+ suretyBond
+
+ |
+ + Surety bond + | +
+ A surety bond is an instrument through which The surety is obliged to compensate the obligee for the damages suffered in the event that the principal fails to comply with the terms of the contract. + + |
+
+
+ check
+
+ |
+ + Check + | +
+ A certified check as a form of guarantee. + + |
+
+ guaranteedObligations.csv +
+ +
+ You can download the guaranteedObligations.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ fulfillment
+
+ |
+ + Fulfillment + | +
+ Guarantees fulfillment in time with the conditions stipulated in the contract. + + |
+
+
+ prepaid
+
+ |
+ + Prepaid + | +
+ Guarantee by which the supplier requests a prepayment from the procuring entity. + + |
+
+
+ latentDefects
+
+ |
+ + Latent defects + | +
+ Guarantee on the possible defects that a good may have that are not discoverable through general inspection at the time of delivery. + + |
+
+
+ confidentiality
+
+ |
+ + Confidentiality + | +
+ Guarantee that commits the supplier to safeguard the confidential information that has been granted. + + |
+
+
+ quality
+
+ |
+ + Quality + | +
+ Commitment from the supplier to deliver the goods and services in the quality specified in the contract. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/guarantees/master/release-schema.json b/en/extensions/guarantees/master/release-schema.json
new file mode 100644
index 000000000..87f1c66e2
--- /dev/null
+++ b/en/extensions/guarantees/master/release-schema.json
@@ -0,0 +1,79 @@
+{
+ "definitions": {
+ "Guarantee": {
+ "title": "Guarantee",
+ "description": "Information of the guarantee used to ensure compliance with the terms of a contract.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Guarantee ID",
+ "description": "A local identifier for this guarantee, unique within this block.",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "type": {
+ "title": "Guarantee type",
+ "description": "Specify the guarantee type for this contract using the [guaranteeType](https://github.com/contratacionesabiertas/ocds_guarantees_extension/blob/master/codelists/guaranteeType.csv) codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "guaranteeType.csv",
+ "openCodelist": true
+ },
+ "date": {
+ "title": "Guarantee date",
+ "description": "The date of the guarantee. This is the date on which the guarantee is issued.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "obligations": {
+ "title": "Guaranteed obligations",
+ "description": "Specify the type of obligations that are guaranteed, using the [obligationType](https://github.com/contratacionesabiertas/ocds_guarantees_extension/blob/master/codelists/guaranteedObligations.csv) codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "guaranteedObligations.csv",
+ "openCodelist": true
+ },
+ "value": {
+ "title": "Guarantee value",
+ "description": "Total amount of the guarantee.",
+ "$ref": "#/definitions/Value"
+ },
+ "guarantor": {
+ "title": "Guarantor",
+ "description": "Institution that issues the guarantee.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "period": {
+ "title": "Guarantee period",
+ "description": "The period on which this quote is valid.",
+ "$ref": "#/definitions/Period"
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "guarantees": {
+ "title": "Guarantees",
+ "description": "A list of the guarantees given for this contract.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Guarantee"
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/guarantees/master/schema/index.html b/en/extensions/guarantees/master/schema/index.html
new file mode 100644
index 000000000..91f15d6e0
--- /dev/null
+++ b/en/extensions/guarantees/master/schema/index.html
@@ -0,0 +1,391 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Guarantees +
+ ++ Some procurement processes consider the specification of guarantees in order to ensure compliance with the terms of a contract. + +There are many types of guarantees, so we consider the creation of a new extension based on the formats that are required for the Federal Treasury (Mexico). See discussion in https://github.com/open-contracting/standard/issues/651 +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Description:
+Some procurement processes consider the specification of guarantees in order to ensure compliance with the terms of a contract.
+There are many types of guarantees, so we consider the creation of a new extension based on the formats that are required for the Federal Treasury (Mexico).
+Proposal:
+Codelist
+-
+
-
+
Guarantee types:
+-
+
- Bail +
- Deposit slip +
- Letter of credit +
- Surety bond +
- Check +
+ -
+
Guaranteed obligations:
+-
+
- Fulfillment +
- Prepaid +
- Latent defects +
- Confidentiality +
- Quality +
+
Add an array named "guarantees" with the following fields:
+Schema
+-
+
- Contract {object}
+
-
+
- guarantees [array]
+
-
+
- Guarantee {object}
+
-
+
- id (string, integer) +
- type (string, null) (codelist) +
- date (Format: date-time) (string, null) +
- obligations (string, null) (codelist) +
- value {object}
+
-
+
- $ref : #/definitions/Value +
+ - guarantor {object}
+
-
+
- $ref : #/definitions/OrganizationReference +
+ - period {object}
+
-
+
- $ref : #/definitions/Period +
+
+
+ - Guarantee {object}
+
+ - guarantees [array]
+
Defining texts:
+| Code | +Title | +Description | +
|---|---|---|
| guarantees | +Guarantees | +A list of the guarantees given for this contract. | +
| Guarantee | +Guarantee | +Information of the guarantee used to ensure compliance with the terms of a contract. | +
| id | +Guarantee ID | +A local identifier for this guarantee, unique within this block. | +
| type | +Guarantee type | +Specify the guarantee type for this contract using the guaranteeType codelist. | +
| bail | +Bail | +A bail bond is a written promise by which a person agrees with the creditor to pay for the debtor, if he does not. | +
| depositSlip | +Deposit slip | +The deposit slip is an instrument used to establish cash guarantees available to judicial or administrative authorities. | +
| letterOfCredit | +Letter of credit | +Letters of credit are used to guarantee that a supplier will receive a specified amount of money within a specified time providing strict terms. | +
| suretyBond | +Surety bond | +A surety bond is an instrument through which The surety is obliged to compensate the obligee for the damages suffered in the event that the principal fails to comply with the terms of the contract. | +
| check | +Check | +A certified check as a form of guarantee. | +
| date | +Guarantee date | +The date of the guarantee. This is the date on which the guarantee is issued. | +
| obligations | +Guaranteed obligations | +Specify the type of obligations that are guaranteed, using the obligationType codelist. | +
| fulfillment | +Fulfillment | +Guarantees fulfillment in time with the conditions stipulated in the contract. | +
| prepaid | +Prepaid | +Guarantee by which the supplier requests a prepayment from the procuring entity. | +
| latentDefects | +Latent defects | +Guarantee on the possible defects that a good may have that are not discoverable through general inspection at the time of delivery. | +
| confidentiality | +Confidentiality | +Guarantee that commits the supplier to safeguard the confidential information that has been granted. | +
| quality | +Quality | +Commitment from the supplier to deliver the goods and services in the quality specified in the contract. | +
| value | +Guarantee value | +Total amount of the guarantee. | +
| guarantor | +Guarantor | +Institution that issues the guarantee. | +
| period | +Guarantee period | +The period on which this quote is valid. | +
Issues
+Report issues for this extension in the standard repository of the Open Contracting Partnership.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/implementationStatus/index.html b/en/extensions/implementationStatus/index.html
new file mode 100644
index 000000000..48f13d12f
--- /dev/null
+++ b/en/extensions/implementationStatus/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Guarantees +
+ ++ Some procurement processes consider the specification of guarantees in order to ensure compliance with the terms of a contract. + +There are many types of guarantees, so we consider the creation of a new extension based on the formats that are required for the Federal Treasury (Mexico). See discussion in https://github.com/open-contracting/standard/issues/651 +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Guarantee +
+ +
+ The extension defines a new Guarantee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Guarantee ID + | +
+ A local identifier for this guarantee, unique within this block. + + |
+ + string or integer + | +
+
+ type
+
+ |
+ + Guarantee type + | +
+ Specify the guarantee type for this contract using the guaranteeType codelist. + + |
+ + string from open guaranteeType codelist + | +
+
+ date
+
+ |
+ + Guarantee date + | +
+ The date of the guarantee. This is the date on which the guarantee is issued. + + |
+ + string + | +
+
+ obligations
+
+ |
+ + Guaranteed obligations + | +
+ Specify the type of obligations that are guaranteed, using the obligationType codelist. + + |
+ + string from open guaranteedObligations codelist + | +
+
+ value
+
+ |
+ + Guarantee value + | +
+ Total amount of the guarantee. + + |
+ + Value object + | +
+
+ guarantor
+
+ |
+ + Guarantor + | +
+ Institution that issues the guarantee. + + |
+ + OrganizationReference object + | +
+
+ period
+
+ |
+ + Guarantee period + | +
+ The period on which this quote is valid. + + |
+ + Period object + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ guarantees
+
+ |
+ + Guarantees + | +
+ A list of the guarantees given for this contract. + + |
+ + array of Guarantee objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/implementationStatus/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/implementationStatus/master/extension.json b/en/extensions/implementationStatus/master/extension.json
new file mode 100644
index 000000000..926224fa9
--- /dev/null
+++ b/en/extensions/implementationStatus/master/extension.json
@@ -0,0 +1,22 @@
+{
+ "name": {
+ "en": "Implementation status",
+ "es": "Estatus de la implementaci\u00f3n"
+ },
+ "description": {
+ "en": "In Mexico, when talking about works and services related with them it is necessary to publish a set of specific variables about its implementation. One of them is the implementation status of the work or service related with it. See discussion in https://github.com/open-contracting/standard/issues/624",
+ "es": "En M\u00e9xico, cuando se habla de obras y servicios relacionados a las obras, es necesario publicar un conjunto de variables espec\u00edficas sobre su implementaci\u00f3n. Uno de ellos es el estado de implementaci\u00f3n del trabajo o servicio relacionado con \u00e9l. Vea la discusi\u00f3n en https://github.com/open-contracting/standard/issues/624"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "documentationUrl": {
+ "en": "https://github.com/contratacionesabiertas/ocds_implementationStatus_extension"
+ },
+ "codelists": [
+ "implementationStatus.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/en/extensions/implementationStatus/master/index.html b/en/extensions/implementationStatus/master/index.html
new file mode 100644
index 000000000..1ebbec63c
--- /dev/null
+++ b/en/extensions/implementationStatus/master/index.html
@@ -0,0 +1,333 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Implementation status +
+ ++ In Mexico, when talking about works and services related with them it is necessary to publish a set of specific variables about its implementation. One of them is the implementation status of the work or service related with it. See discussion in https://github.com/open-contracting/standard/issues/624 +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ implementationStatus.csv +
+ +
+ You can download the implementationStatus.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ planning
+
+ |
+ + Planning + | +
+ The contract has been signed, but the provision or construction of the goods, services or works has not started. + + |
+
+
+ ongoing
+
+ |
+ + Ongoing + | +
+ The provision or construction of the goods, services or works is in progress. + + |
+
+
+ concluded
+
+ |
+ + Concluded + | +
+ The provision or construction of the goods, services or works has officially ended. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/implementationStatus/master/release-schema.json b/en/extensions/implementationStatus/master/release-schema.json
new file mode 100644
index 000000000..3ca3ee7c2
--- /dev/null
+++ b/en/extensions/implementationStatus/master/release-schema.json
@@ -0,0 +1,24 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "status": {
+ "title": "Implementation status",
+ "description": "The current status of the contract implementation based on the [implementationStatuscodelist](https://github.com/INAImexico/ocds_implementationStatus_extension/blob/master/codelists/implementationStatus).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "enum": [
+ "planning",
+ "ongoing",
+ "concluded",
+ null
+ ],
+ "codelist": "implementationStatus.csv",
+ "openCodelist": false
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/implementationStatus/master/schema/index.html b/en/extensions/implementationStatus/master/schema/index.html
new file mode 100644
index 000000000..a094e5adf
--- /dev/null
+++ b/en/extensions/implementationStatus/master/schema/index.html
@@ -0,0 +1,236 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Implementation status +
+ ++ In Mexico, when talking about works and services related with them it is necessary to publish a set of specific variables about its implementation. One of them is the implementation status of the work or service related with it. See discussion in https://github.com/open-contracting/standard/issues/624 +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Description:
+In Mexico, when talking about works and services related with them it is necessary to publish a set of specific variables about its implementation. One of them is the implementation status of the work or service related with it. It includes a code list whose values are the following:
+-
+
- planning +
- ongoing +
- concluded +
Proposal:
+Add a new field named “implementationStatus” in the “Implementation” object.
+Schema
+-
+
- Implementation {object}
+
-
+
- status (string, null) (codelist) +
+
Defining texts:
+| Code | +Title | +Description | +
|---|---|---|
| status | +Implementation status | +The current status of the contract implementation based on the implementationStatus codelist. | +
| planning | +Planning | +The contract has been signed, but the provision or construction of the goods, services or works has not started. | +
| ongoing | +Ongoing | +The provision or construction of the goods, services or works is in progress. | +
| concluded | +Concluded | +The provision or construction of the goods, services or works has officially ended. | +
Issues
+Report issues for this extension in the standard repository of the Open Contracting Partnership.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/index.html b/en/extensions/index.html
new file mode 100644
index 000000000..baf5068b7
--- /dev/null
+++ b/en/extensions/index.html
@@ -0,0 +1,1621 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Implementation status +
+ ++ In Mexico, when talking about works and services related with them it is necessary to publish a set of specific variables about its implementation. One of them is the implementation status of the work or service related with it. See discussion in https://github.com/open-contracting/standard/issues/624 +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ status
+
+ |
+ + Implementation status + | +
+ The current status of the contract implementation based on the implementationStatuscodelist. + + |
+ + string from closed implementationStatus codelist + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/itemAttributes/index.html b/en/extensions/itemAttributes/index.html
new file mode 100644
index 000000000..4300335be
--- /dev/null
+++ b/en/extensions/itemAttributes/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Extensions +
+ + + ++ Showing 69 extensions from the extension registry +
+
+
+
+
+
+
+
+
+ + + Additional Contact Points + +
++ For providing multiple contact points for an organization, or for providing the available languages of a contact point. For example, it may be used to provide a contact point for each language. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Amendment rationale classifications + +
++ Adds a field to the amendment object to classify the rationale for the amendment. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Award criteria breakdown + +
++ Adds an award criteria array to the lot object, to break down award criteria by price, cost and quality. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Beneficial owners + +
++ Adds a beneficialOwners array to the organization object to indicate the beneficial owners of an organization. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Bid opening + +
++ Adds an object to describe the date, time, place and other details of the bid opening. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Bid statistics and details + + Recommended +
++ Allowing bid statistics, and detailed bid information to be represented. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Budget Breakdown + +
++ Adds a budget breakdown array to the budget object to break down a budget by source and period. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Budget and spending classification + +
++ Extends budget breakdown and contract implementation to allow publication of detailed budget allocations and execution for a contracting process, using classifications that can be mapped to separately published budget and spend data. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Charges + +
++ Adds a charges array to the implementation object to disclose the charges to be incurred by users or government in a given period of a contract. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Communication + +
++ Adds a communication object to the tender to describe the modalities of communication about key events. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Contract terms + +
++ Adds a contract terms object to the tender and lot objects, to describe the terms governing the future contract. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Buyer per award or contract + +
++ Adds buyer fields to the award and contract objects to indicate the buyer(s) for an individual award or contract, if different from the buyer(s) involved in the contracting process as a whole. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Contract Completion + +
++ Adds fields to the contract implementation section to detail the end date, and final value of a contract. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Contract suppliers + +
++ To allow explicit declaration of suppliers within the contracts block. Used when a single award to multiple suppliers results in multiple contracts to a sub-set of those awarded suppliers. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Country code + +
++ Adds a country code field to the address object. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Covered By + +
++ Adds a field to indicate the treaties that the contracting process is covered by. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Design contest + +
++ Adds an object to the tender object to describe a design contest. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Document publisher + +
++ Adds a publisher field to the document object. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Document Details + +
++ Adds fields to the document object for page references, access details and author information. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Enquiries + + Recommended +
++ The enquiries extension can be used to record questions raised during a contracting process, and the answers provided. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Essential assets + +
++ Adds a object to the tender object to describe the assets used for the provision of public services. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + European Union + +
++ Implements fields and codes that are specific to European law. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Exclusion grounds + +
++ Adds an object to describe the criteria to exclude tenderers from participating in a contracting process. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Contract extensions via supplementary contract: extendsContractID + +
++ Under some procurement rules and processes, to extend the duration or value of a contract, or to make other substantial alterations, requires a new contract to be signed. This extension allows these relationships between two or more contracts in the same contracting process to be made explicit. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Finance + +
++ Adds fields to disclose the financing of the whole process and its individual contracts. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Guarantees + +
++ Some procurement processes consider the specification of guarantees in order to ensure compliance with the terms of a contract. + +There are many types of guarantees, so we consider the creation of a new extension based on the formats that are required for the Federal Treasury (Mexico). See discussion in https://github.com/open-contracting/standard/issues/651 +
++ + Maintained by Contrataciones Abiertas México + +
+
+
+
+
+
+
+
+
+ + + Implementation status + +
++ In Mexico, when talking about works and services related with them it is necessary to publish a set of specific variables about its implementation. One of them is the implementation status of the work or service related with it. See discussion in https://github.com/open-contracting/standard/issues/624 +
++ + Maintained by Contrataciones Abiertas México + +
+
+
+
+
+
+
+
+
+ + + Item attributes + +
++ Adds a generic list of attributes to the item object +
++ + Maintained by dncp-opendata + +
+
+
+
+
+
+
+
+
+ + + Legal basis + +
++ Adds fields to the tender object to describe the legal basis of the procedure. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Location + + Recommended +
++ Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Lots + + Recommended +
++ A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLot identifier is given, the values ought to be interpreted as applicable to the whole tender. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Medicine + +
++ Adds fields to the item object relevant to the procurement of medicines. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Metrics + +
++ The metrics extension supports publication of forecasts (planning stage), targets (tender stage), agreed performance targets (award and contract stage) and results (implementation stage). +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Milestone documents + +
++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Options + +
++ Adds fields for information on options. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Organization classification + +
++ Adds an array of classification objects to an organization's details in order to categorize it. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Other Requirements + +
++ Adds an object to describe other requirements to participate in a contracting process. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Pagination + +
++ Adds a links object to packages, to support pagination. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Participation Fees + + Recommended +
++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Organization scale + +
++ For classifying organizations as micro, sme or large. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Performance Failures + +
++ Adds fields to the implementation section to allow disclosure of an array of contracting performance failures. Based on the performance failures reporting table defined in the World Bank Framework for Disclosure in PPPs. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + OCDS for PPPs Extension + +
++ Makes changes required by the OCDS for PPPs profile. Evaluation indicators, finance summary and project details may be moved into new extensions. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Procedure + +
++ This extension adds a block to describe the procurement procedure. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Process level title and description + + Recommended +
++ For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Procurement method rationale classifications + +
++ Adds an array to the tender object to classify the procurement method rationale. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Project + +
++ Adds a project object to the planning object to describe the project to which the contracting process is related, including the total value of the project (not to be confused with the total value of the contracting process). +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Recurrence + +
++ Adds fields for information on the recurrence of the contracting process. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Release Publisher + +
++ Includes the information about the publisher at release level for the cases in that a release-package or record-packages contains releases from different publishers. +
++ + Maintained by CompraNet + +
+
+
+
+
+
+
+
+
+ + + Sources + +
++ Adds a sources array to indicate the information systems from which the data originates. +
++ + Maintained by ONCAETI + +
+
+
+
+
+
+
+
+
+ + + Renewal + +
++ Adds fields to the Tender and Lot objects to describe the options for the renewal of contracts. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Requirements + +
++ Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV). +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Risk Allocation + +
++ For providing the risk allocations defined in a public private partnership's contract. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Second stage description + +
++ Adds a second stage object to the tender and lot objects, to describe the second stage of a two-stage procedure. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Selection Criteria + +
++ Adds an object to describe the conditions for participation in a contracting process. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Shareholders + +
++ Adds company ownership fields to the organization object used in the parties array. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Signatories + +
++ Adds a signatories array to the contract object, for when the signatories differ from the buyer for the contracting process and the suppliers for the award. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Statistics + +
++ Adds a top-level statistics array to describe statistics about the contracting process. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Status Details + +
++ Add a statusDetails field to Tender, Award and Contract object +
++ + Maintained by dncp-opendata + +
+
+
+
+
+
+
+
+
+ + + Subcontracting + +
++ Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Submission terms + +
++ Adds a submission terms object to the tender and lot objects, to describe how, when and where the tenderers must submit their bids. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Suitability + +
++ Adds a suitability object to the tender, lot and lot group objects to describe their suitability to different types of tenderers. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Sustainability + +
++ Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Tariffs + +
++ Adds fields to the contract and implementation objects to capture details of the tariffs, tolls and user fees set out in the contract and in use throughout the life of the project. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Techniques + +
++ Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Tender classification + +
++ Adds an array of classification objects to the tender object, in order to categorize the procedure or call-off as a whole. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Tender Date Published + +
++ Adds a date field to indicate when the tender was published. +
++ + Maintained by Portal EDCA HN + +
+
+
+
+
+
+
+
+
+ + + Transaction related milestones + +
++ Adds a relatedImplementationMilestone field to transaction objects, so that payments against a contract can be linked with an implementation milestone. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Unstructured changes + +
++ Adds an unstructuredChanges array to the Amendment object. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Withheld information + +
++ Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+ + + This page has moved to a /en/extensions/itemAttributes/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/itemAttributes/master/release-schema.json b/en/extensions/itemAttributes/master/release-schema.json
new file mode 100644
index 000000000..2ab098c38
--- /dev/null
+++ b/en/extensions/itemAttributes/master/release-schema.json
@@ -0,0 +1,56 @@
+{
+ "definitions": {
+ "Attribute": {
+ "type": "object",
+ "title": "Attribute",
+ "description": "An attribute, including its name and value.",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "name": {
+ "title": "Name",
+ "description": "The name of the attribute, such as 'brand', 'manufacturer', and similar.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "value": {
+ "title": "Value",
+ "description": "The value of the attribute.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "id": {
+ "title": "Id",
+ "description": "A local identifier for the attribute.",
+ "type": [
+ "string"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Item": {
+ "properties": {
+ "attributes": {
+ "title": "Attributes",
+ "description": "The attributes of the item.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Attribute"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/itemAttributes/master/schema/index.html b/en/extensions/itemAttributes/master/schema/index.html
new file mode 100644
index 000000000..ccba08d60
--- /dev/null
+++ b/en/extensions/itemAttributes/master/schema/index.html
@@ -0,0 +1,316 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Item attributes +
+ ++ Adds a generic list of attributes to the item object +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an attributes array to the item object to list any
+extra attribute that an item may have, at the tender, award or
+contract stage.
+The attributes can be features like the item's model, brand, manufacturer, among others, including its value and an
+unique identifier for that attribute
Example
+{
+ "tender": {
+ "items": [
+ {
+ "id": "10121503-001-1",
+ "description": "Balanceado para Ganado Vacuno - Alta Producción en bolsas de 25 k",
+ "quantity": 350,
+ "attributes": [
+ {
+ "name": "Presentacion",
+ "value": "BOLSA",
+ "id": "1"
+ }
+ ]
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+This extension was originally discussed in https://github.com/open-contracting/standard/issues/751
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/legalBasis/1.1/README.md b/en/extensions/legalBasis/1.1/README.md
new file mode 100644
index 000000000..2e268e411
--- /dev/null
+++ b/en/extensions/legalBasis/1.1/README.md
@@ -0,0 +1,51 @@
+# Legal basis
+
+Adds fields to the tender object to describe the legal basis of the contracting process – that is, the laws and regulations that govern the contracting process and that grant legal authority to the procuring entity.
+
+The `tender.legalBasis` field is a `Classification` object. Example classification schemes are [LEX](
+
+
+
+
+ + Item attributes +
+ ++ Adds a generic list of attributes to the item object +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Attribute +
+ +
+ The extension defines a new Attribute object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ name
+
+ |
+ + Name + | +
+ The name of the attribute, such as 'brand', 'manufacturer', and similar. + + |
+ + string + | +
+
+ value
+
+ |
+ + Value + | +
+ The value of the attribute. + + |
+ + string or number + | +
+
+ id
+
+ |
+ + Id + | +
+ A local identifier for the attribute. + + |
+ + string + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ attributes
+
+ |
+ + Attributes + | +
+ The attributes of the item. + + |
+ + array of Attribute objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/legalBasis/1.1/extension.json b/en/extensions/legalBasis/1.1/extension.json
new file mode 100644
index 000000000..b5f21dcf1
--- /dev/null
+++ b/en/extensions/legalBasis/1.1/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Legal basis",
+ "es": "Base legal"
+ },
+ "description": {
+ "en": "Adds fields to the tender object to describe the legal basis of the procedure.",
+ "es": "Agregar campos al objeto de licitaci\u00f3n para describir la base legal del procedimiento."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/legalBasis/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+itemClassificationScheme.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/legalBasis/1.1/index.html b/en/extensions/legalBasis/1.1/index.html
new file mode 100644
index 000000000..c120a713b
--- /dev/null
+++ b/en/extensions/legalBasis/1.1/index.html
@@ -0,0 +1,317 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Legal basis +
+ ++ Adds fields to the tender object to describe the legal basis of the procedure. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ CELEX
+
+ |
+ + CELEX number + | +
+ Identifier scheme for EUR-Lex documents + +
|
+
+
+ ELI
+
+ |
+ + European Legislation Identifier + | +
+ Identifier scheme for European legislation + +
|
+
+
+ LEXML
+
+ |
+ + LexML URN + | +
+ Identifier scheme for BR-Lex documents + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/legalBasis/1.1/release-schema.json b/en/extensions/legalBasis/1.1/release-schema.json
new file mode 100644
index 000000000..4fcd619f2
--- /dev/null
+++ b/en/extensions/legalBasis/1.1/release-schema.json
@@ -0,0 +1,22 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "crossBorderLaw": {
+ "title": "Cross-border law",
+ "description": "In case of joint procurement, the public procurement legislation that applies to the procedure.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "legalBasis": {
+ "title": "Legal basis",
+ "description": "The legal basis of the procedure.",
+ "$ref": "#/definitions/Classification"
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/legalBasis/1.1/schema/index.html b/en/extensions/legalBasis/1.1/schema/index.html
new file mode 100644
index 000000000..9cc1f6a33
--- /dev/null
+++ b/en/extensions/legalBasis/1.1/schema/index.html
@@ -0,0 +1,253 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Legal basis +
+ ++ Adds fields to the tender object to describe the legal basis of the procedure. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds fields to the tender object to describe the legal basis of the contracting process – that is, the laws and regulations that govern the contracting process and that grant legal authority to the procuring entity.
+The tender.legalBasis field is a Classification object. Example classification schemes are LEX, CELEX and ELI.
To identify the procedure used, whether by formal name or by legal citation, use the tender.procurementMethodDetails field.
To indicate whether the contracting process is covered by a treaty, like the Agreement on Government Procurement (GPA), use the coveredBy extension. To indicate whether the contracting process is accelerated, involves framework agreements, or has other modalities, browse the extensions.
+Guidance
+If the legal basis is country-specific, it is recommended to prefix the ISO 3166-1 alpha-2 code to the classification scheme: for example, "HN-ONCAE" for the Oficina Normativa de Contratación y Adquisiciones del Estado (ONCAE) in Honduras.
+Legal context
+In the European Union, this extension's fields correspond to eForms BT-01 (Procedure Legal Basis), BT-09 (Cross Border Law) and Article 39, paragraph 5 of Directive 2014/24/EU. For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+{
+ "tender": {
+ "crossBorderLaw": "Italian procurement legislation",
+ "legalBasis": {
+ "id": "32014L0025",
+ "scheme": "CELEX"
+ }
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-08-01
+-
+
- Add 'ELI' to
+itemClassificationScheme.csv.
+
2021-01-19
+-
+
- Add guidance on the choice of the classification scheme for country-specific legal basis. +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/legalBasis/index.html b/en/extensions/legalBasis/index.html
new file mode 100644
index 000000000..40bb1974b
--- /dev/null
+++ b/en/extensions/legalBasis/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Legal basis +
+ ++ Adds fields to the tender object to describe the legal basis of the procedure. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ crossBorderLaw
+
+ |
+ + Cross-border law + | +
+ In case of joint procurement, the public procurement legislation that applies to the procedure. + + |
+ + string + | +
+
+ legalBasis
+
+ |
+ + Legal basis + | +
+ The legal basis of the procedure. + + |
+ + Classification object + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/legalBasis/1.1/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/legalBasis/master/index.html b/en/extensions/legalBasis/master/index.html
new file mode 100644
index 000000000..44cb766d6
--- /dev/null
+++ b/en/extensions/legalBasis/master/index.html
@@ -0,0 +1,318 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Legal basis +
+ ++ Adds fields to the tender object to describe the legal basis of the procedure. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ CELEX
+
+ |
+ + CELEX number + | +
+ Identifier scheme for EUR-Lex documents + +
|
+
+
+ ELI
+
+ |
+ + European Legislation Identifier + | +
+ Identifier scheme for European legislation + +
|
+
+
+ LEXML
+
+ |
+ + LexML URN + | +
+ Identifier scheme for BR-Lex documents + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/legalBasis/master/release-schema.json b/en/extensions/legalBasis/master/release-schema.json
new file mode 100644
index 000000000..4fcd619f2
--- /dev/null
+++ b/en/extensions/legalBasis/master/release-schema.json
@@ -0,0 +1,22 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "crossBorderLaw": {
+ "title": "Cross-border law",
+ "description": "In case of joint procurement, the public procurement legislation that applies to the procedure.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "legalBasis": {
+ "title": "Legal basis",
+ "description": "The legal basis of the procedure.",
+ "$ref": "#/definitions/Classification"
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/legalBasis/master/schema/index.html b/en/extensions/legalBasis/master/schema/index.html
new file mode 100644
index 000000000..96541541c
--- /dev/null
+++ b/en/extensions/legalBasis/master/schema/index.html
@@ -0,0 +1,254 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Legal basis +
+ ++ Adds fields to the tender object to describe the legal basis of the procedure. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds fields to the tender object to describe the legal basis of the contracting process – that is, the laws and regulations that govern the contracting process and that grant legal authority to the procuring entity.
+The tender.legalBasis field is a Classification object. Example classification schemes are LEX, CELEX and ELI.
To identify the procedure used, whether by formal name or by legal citation, use the tender.procurementMethodDetails field.
To indicate whether the contracting process is covered by a treaty, like the Agreement on Government Procurement (GPA), use the coveredBy extension. To indicate whether the contracting process is accelerated, involves framework agreements, or has other modalities, browse the extensions.
+Guidance
+If the legal basis is country-specific, it is recommended to prefix the ISO 3166-1 alpha-2 code to the classification scheme: for example, "HN-ONCAE" for the Oficina Normativa de Contratación y Adquisiciones del Estado (ONCAE) in Honduras.
+Legal context
+In the European Union, this extension's fields correspond to eForms BT-01 (Procedure Legal Basis), BT-09 (Cross Border Law) and Article 39, paragraph 5 of Directive 2014/24/EU. For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+{
+ "tender": {
+ "crossBorderLaw": "Italian procurement legislation",
+ "legalBasis": {
+ "id": "32014L0025",
+ "scheme": "CELEX"
+ }
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-08-01
+-
+
- Add 'ELI' to
+itemClassificationScheme.csv.
+
2021-01-19
+-
+
- Add guidance on the choice of the classification scheme for country-specific legal basis. +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/location/index.html b/en/extensions/location/index.html
new file mode 100644
index 000000000..6b3d5e2e4
--- /dev/null
+++ b/en/extensions/location/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Legal basis +
+ ++ Adds fields to the tender object to describe the legal basis of the procedure. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ crossBorderLaw
+
+ |
+ + Cross-border law + | +
+ In case of joint procurement, the public procurement legislation that applies to the procedure. + + |
+ + string + | +
+
+ legalBasis
+
+ |
+ + Legal basis + | +
+ The legal basis of the procedure. + + |
+ + Classification object + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/location/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/location/master/codelists/locationGazetteers.csv b/en/extensions/location/master/codelists/locationGazetteers.csv
new file mode 100644
index 000000000..fa5e62d4b
--- /dev/null
+++ b/en/extensions/location/master/codelists/locationGazetteers.csv
@@ -0,0 +1,7 @@
+Category,Code,Title,Description,Source,URI Pattern
+Sub-National,NUTS,EU Nomenclature of Territorial Units for Statistics,The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union.,https://ec.europa.eu/eurostat/web/nuts/linked-open-data,http://data.europa.eu/nuts/code/
+National,ISO2,ISO Country Codes (3166-1 alpha-2),ISO 2-Digit Country Codes,https://www.iso.org/iso-3166-country-codes.html,
+Universal,GEONAMES,GeoNames,"GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations.",https://www.geonames.org/,https://www.geonames.org/
+Universal,OSMN,OpenStreetMap Node,"OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes might have tags to indicate the particular geographic feature they represent.",,https://www.openstreetmap.org/node/
+Universal,OSMR,OpenStreetMap Relation,"Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap.",https://wiki.openstreetmap.org/wiki/Relation,https://www.openstreetmap.org/relation/
+Universal,OSMW,OpenStreetMap Way,An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. It can be used to describe fragments of roads or local boundaries and bounding boxes.,https://wiki.openstreetmap.org/wiki/Way,https://www.openstreetmap.org/way/
diff --git a/en/extensions/location/master/extension.json b/en/extensions/location/master/extension.json
new file mode 100644
index 000000000..7dc7660b4
--- /dev/null
+++ b/en/extensions/location/master/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Location",
+ "es": "Ubicaci\u00f3n"
+ },
+ "description": {
+ "en": "Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects.",
+ "es": "Permite indicar el punto de entrega o el sitio de las obras para una l\u00ednea de pedido determinada en los objetos de licitaci\u00f3n, adjudicaci\u00f3n y contrato."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/location/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "locationGazetteers.csv",
+ "geometryType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/location/master/index.html b/en/extensions/location/master/index.html
new file mode 100644
index 000000000..fd92cf235
--- /dev/null
+++ b/en/extensions/location/master/index.html
@@ -0,0 +1,426 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Location +
+ ++ Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ geometryType.csv +
+ +
+ You can download the geometryType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ Point
+
+ |
+ + Point + | +
+ For type 'Point', the 'coordinates' member is a single position. + +
|
+
+
+ MultiPoint
+
+ |
+ + MultiPoint + | +
+ For type 'MultiPoint', the 'coordinates' member is an array of positions. + +
|
+
+
+ LineString
+
+ |
+ + LineString + | +
+ For type 'LineString', the 'coordinates' member is an array of two or more positions. + +
|
+
+
+ MultiLineString
+
+ |
+ + MultiLineString + | +
+ For type 'MultiLineString', the 'coordinates' member is an array of LineString coordinate arrays. + +
|
+
+
+ Polygon
+
+ |
+ + Polygon + | +
+ For type 'Polygon', the 'coordinates' member must be an array of linear ring coordinate arrays. + +
|
+
+
+ MultiPolygon
+
+ |
+ + MultiPolygon + | +
+ For type 'MultiPolygon', the 'coordinates' member is an array of Polygon coordinate arrays. + +
|
+
+ locationGazetteers.csv +
+ +
+ You can download the locationGazetteers.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ NUTS
+
+ |
+ + EU Nomenclature of Territorial Units for Statistics + | +
+ The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union. + +
|
+
+
+ ISO2
+
+ |
+ + ISO Country Codes (3166-1 alpha-2) + | +
+ ISO 2-Digit Country Codes + +
|
+
+
+ GEONAMES
+
+ |
+ + GeoNames + | +
+ GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations. + +
|
+
+
+ OSMN
+
+ |
+ + OpenStreetMap Node + | +
+ OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes might have tags to indicate the particular geographic feature they represent. + +
|
+
+
+ OSMR
+
+ |
+ + OpenStreetMap Relation + | +
+ Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap. + +
|
+
+
+ OSMW
+
+ |
+ + OpenStreetMap Way + | +
+ An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. It can be used to describe fragments of roads or local boundaries and bounding boxes. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/location/master/release-schema.json b/en/extensions/location/master/release-schema.json
new file mode 100644
index 000000000..6e179b314
--- /dev/null
+++ b/en/extensions/location/master/release-schema.json
@@ -0,0 +1,180 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "deliveryLocations": {
+ "title": "Delivery Locations",
+ "description": "The locations where activity related to this tender will take place.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Location"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true
+ },
+ "deliveryAddresses": {
+ "title": "Delivery Addresses",
+ "description": "The addresses to which, or where, goods or services related to this tender will be delivered.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Address"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "deliveryLocations": {
+ "title": "Delivery Locations",
+ "description": "The locations where activity related to this tender, contract or license will be delivered.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Location"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "deliveryLocation": {
+ "title": "Delivery Location",
+ "description": "The location where activity related to this tender, contract or license will be delivered, or will take place.",
+ "$ref": "#/definitions/Location",
+ "deprecated": {
+ "description": "This field is deprecated in favour of `.deliveryLocations` to support items with multiple delivery locations.",
+ "deprecatedVersion": "1.2.0"
+ }
+ },
+ "deliveryAddresses": {
+ "title": "Delivery Addresses",
+ "description": "The addresses to which, or where, goods or services related to this tender, contract or license will be delivered.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Address"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "deliveryAddress": {
+ "title": "Delivery Address",
+ "description": "The address to which, or where, goods or services related to this tender, contract or license will be delivered.",
+ "$ref": "#/definitions/Address",
+ "deprecated": {
+ "description": "This field is deprecated in favour of `.deliveryAddresses` to support items with multiple delivery locations.",
+ "deprecatedVersion": "1.2.0"
+ }
+ }
+ }
+ },
+ "Location": {
+ "title": "Location",
+ "description": "A physical or virtual location.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "A name or description of this location. This might include the name(s) of the location(s), or might provide a human-readable description of the location to be covered.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "geometry": {
+ "title": "Geometry",
+ "description": "We follow the [GeoJSON standard](https://www.rfc-editor.org/rfc/rfc7946) to express basic location information, using longitude, latitude, and optional elevation values in the [WGS84](https://en.wikipedia.org/wiki/World_Geodetic_System) (EPSG:4326) projection. A point location can be identified by geocoding an address. For concession licenses, or other scenarios covering a polygon location that is not contained in a known gazetteer, polygon and multi-polygon can be used.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Type",
+ "description": "The type of [GeoJSON Geometry Objects](https://www.rfc-editor.org/rfc/rfc7946#section-3.1) being provided. To provide longitude, latitude, and optional elevation, use 'Point', and enter an array of [longitude, latitude] or [longitude, latitude, elevation] as the value of the coordinates field: e.g. [-122.085, 37.42].",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "geometryType.csv",
+ "openCodelist": false,
+ "enum": [
+ "Point",
+ "MultiPoint",
+ "LineString",
+ "MultiLineString",
+ "Polygon",
+ "MultiPolygon",
+ null
+ ]
+ },
+ "coordinates": {
+ "title": "Coordinates",
+ "description": "The relevant array of points, e.g. [longitude, latitude] or [longitude, latitude, elevation], or a nested array of points, for the GeoJSON geometry being described. The longitude and latitude must be expressed in decimal degrees in the WGS84 (EPSG:4326) projection.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "number",
+ "array"
+ ]
+ }
+ }
+ }
+ },
+ "gazetteer": {
+ "title": "Gazetteer",
+ "description": "Identifiers from a gazetteer (a geographical index or directory) for the location.",
+ "type": "object",
+ "properties": {
+ "scheme": {
+ "title": "Gazetteer scheme",
+ "description": "The identifier of the gazetteer. The `locationGazetteers.csv` codelist provides details of services, where available, that can resolve a gazetteer entry to provide location names.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "locationGazetteers.csv",
+ "openCodelist": true
+ },
+ "identifiers": {
+ "title": "Identifiers",
+ "description": "An array of one or more codes drawn from the gazetteer indicated by the `scheme` field.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "uri": {
+ "title": "URI",
+ "description": "A URI to a further description of the location. This might be a human-readable document with information on the location, or a machine-readable description of the location.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ },
+ "extension_explorer:source": {
+ "identifier": "location",
+ "version": "master"
+ }
+ },
+ "Address": {
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "The description of the address.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/location/master/schema/index.html b/en/extensions/location/master/schema/index.html
new file mode 100644
index 000000000..41b458321
--- /dev/null
+++ b/en/extensions/location/master/schema/index.html
@@ -0,0 +1,597 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Location +
+ ++ Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds address and location fields to tenders and items, to communicate the location of proposed or executed contract delivery.
+The locationGazetteers.csv codelist's Category column indicates whether the gazetteer has identifiers for the whole world ('Universal') or only some subset ('National' or 'Sub-National').
Example
+Below is an example of a geolocated item in the tender section:
{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "description": "Ceremonial Trumpets for Oxford Town Hall",
+ "classification": {
+ "description": "Trumpets",
+ "scheme": "CPV",
+ "id": "37312100",
+ "uri": "http://purl.org/cpv/2008/code-37312100"
+ },
+ "deliveryLocations": [
+ {
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 51.751944,
+ -1.257778
+ ]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2640729"
+ ]
+ },
+ "description": "Central Oxford",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ }
+ ],
+ "deliveryAddresses": [
+ {
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom",
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford",
+ "description": "The old town hall"
+ }
+ ],
+ "unit": {
+ "name": "Items",
+ "value": {
+ "currency": "GBP",
+ "amount": 10000
+ }
+ },
+ "quantity": 10
+ }
+ ]
+ }
+}
+If the procurement related to the rebuilding of a road, then the item could also specify more complex geometries such as:
+{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "deliveryLocations": [
+ {
+ "geometry": {
+ "type": "LineString",
+ "coordinates": [
+ [
+ 102,
+ 0
+ ],
+ [
+ 103,
+ 1
+ ],
+ [
+ 104,
+ 0
+ ],
+ [
+ 105,
+ 1
+ ]
+ ]
+ },
+ "gazetteer": {
+ "scheme": "OSMW",
+ "identifiers": [
+ "27895985"
+ ]
+ },
+ "description": "St Aldate's",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ }
+ ]
+ }
+ ]
+ }
+}
+You can take the contents of the geometry object, excluding the geometry keyword, and plug this into any GeoJSON tool to see the shape that is described.
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+Unreleased
+-
+
- Add fields:
+
-
+
Tender.deliveryAddresses
+Tender.deliveryLocations
+Address.description
+
+ - Deprecate the
Item.deliveryAddressfield in favor of the newItem.deliveryAddressesfield, to support items with multiple delivery addresses
+ - Deprecate the
Item.deliveryLocationfield in favor of the newItem.deliveryLocationsfield, to support items with multiple delivery locations
+ - Add "format": "uri" to
Location.uri
+ - Update field descriptions to allow location objects to be used in other contexts than deliveries +
v1.1.5
+-
+
- Remove type information from field descriptions +
- Review normative and non-normative words +
v1.1.4
+-
+
- Disallow
Location.geometryandLocation.gazetteerfrom being null (bug introduced in v1.1.3)
+ - Correct the order of longitude and latitude in field descriptions to match the GeoJSON specification +
- Describe elevation or altitude values +
- Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow
Location.geometry.coordinatesfrom having null in its array of coordinates
+ - Disallow
Location.gazetteer.identifiersfrom having null in its array of strings
+ - Correct name of locationGazetteers.csv codelist (was locationGazeteers.csv) +
- Allow
Location.geometryandLocation.gazetteerto be null
+ - Add title and description to
Location.gazetteer
+ - Add description to
Item.deliveryLocation,Item.deliveryAddress
+ - Add geometryType.csv codelist for
Location.geometry.type
+ - List codelists in extension.json +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/location/v1.1.4/README.md b/en/extensions/location/v1.1.4/README.md
new file mode 100644
index 000000000..06c0dff72
--- /dev/null
+++ b/en/extensions/location/v1.1.4/README.md
@@ -0,0 +1,105 @@
+# Location Data
+
+Communicating the location of proposed or executed contract delivery is important to many users of contracting data.
+
+This extension introduces two properties at the `items` level to describe location:
+
+- `deliveryAddress` - a standard `Address` block which can be used to provide a postal address where services should be delivered.
+- `deliveryLocation` - a new block consisting of GeoJSON and Gazetteer entries to describe a wider range of locations to which the contract line item relates.
+
+The `locationGazetteers.csv` codelist's `Category` column indicates whether the gazetteer has identifiers for the whole world ('Universal') or only some subset ('National' or 'Sub-National').
+
+## Example
+
+Below is an example of a geolocated item:
+
+````json
+{
+ "items": [
+ {
+ "id": "item1",
+ "description": "Ceremonial Trumpets for Oxford Town Hall",
+ "classification": {
+ "description": "Trumpets",
+ "scheme": "CPV",
+ "id": "37312100",
+ "uri": "http://purl.org/cpv/2008/code-37312100"
+ },
+ "deliveryLocation": {
+ "geometry": {
+ "type": "Point",
+ "coordinates": [51.751944, -1.257778]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": ["2640729"]
+ },
+ "description": "Central Oxford",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "deliveryAddress": {
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom",
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford"
+ },
+ "unit": {
+ "name": "Items",
+ "value": {
+ "currency": "GBP",
+ "amount": 10000
+ }
+ },
+ "quantity": 10
+ }
+ ]
+}
+``
+
+If the procurement related to the rebuilding of a road, then the item could also specify more complex geometries such as:
+
+```json
+{
+"deliveryLocation": {
+ "geometry": {
+ "type": "LineString",
+ "coordinates": [ [ -1.256503402048622, 51.747792026616821 ], [ -1.256477837243949, 51.747500168748303 ], [ -1.256466773131763, 51.747365723021403 ], [ -1.256471969911729, 51.747246699996332 ], [ -1.256481860557471, 51.747182243160943 ], [ -1.256497618535434, 51.747079648666102 ] ]
+ },
+ "gazetteer": {
+ "scheme": "OSMW",
+ "identifiers": ["27895985"]
+ },
+ "description": "St Aldate's",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+}
+}
+````
+
+You can take the contents of the geometry object, excluding the `geometry` keyword, and plug this into any GeoJSON tool to see the shape that is described.
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.4
+
+- Disallow `Location.geometry` and `Location.gazetteer` from being null (bug introduced in v1.1.3)
+- Correct the order of longitude and latitude in field descriptions to match the GeoJSON specification
+- Describe elevation or altitude values
+- Remove Sphinx directives from readme
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Disallow `Location.geometry.coordinates` from having null in its array of coordinates
+- Disallow `Location.gazetteer.identifiers` from having null in its array of strings
+- Correct name of locationGazetteers.csv codelist (was locationGazeteers.csv)
+- Allow `Location.geometry` and `Location.gazetteer` to be null
+- Add title and description to `Location.gazetteer`
+- Add description to `Item.deliveryLocation`, `Item.deliveryAddress`
+- Add geometryType.csv codelist for `Location.geometry.type`
+- List codelists in extension.json
+- Add tests and tidy code
diff --git a/en/extensions/location/v1.1.4/codelists/geometryType.csv b/en/extensions/location/v1.1.4/codelists/geometryType.csv
new file mode 100644
index 000000000..d722e2dba
--- /dev/null
+++ b/en/extensions/location/v1.1.4/codelists/geometryType.csv
@@ -0,0 +1,7 @@
+Code,Title,Description,Source
+Point,Point,"For type 'Point', the 'coordinates' member is a single position.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiPoint,MultiPoint,"For type 'MultiPoint', the 'coordinates' member is an array of positions.",https://tools.ietf.org/html/rfc7946#section-3.1
+LineString,LineString,"For type 'LineString', the 'coordinates' member is an array of two or more positions.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiLineString,MultiLineString,"For type 'MultiLineString', the 'coordinates' member is an array of LineString coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
+Polygon,Polygon,"For type 'Polygon', the 'coordinates' member MUST be an array of linear ring coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiPolygon,MultiPolygon,"For type 'MultiPolygon', the 'coordinates' member is an array of Polygon coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
diff --git a/en/extensions/location/v1.1.4/codelists/index.html b/en/extensions/location/v1.1.4/codelists/index.html
new file mode 100644
index 000000000..8b7660f20
--- /dev/null
+++ b/en/extensions/location/v1.1.4/codelists/index.html
@@ -0,0 +1,577 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Location +
+ ++ Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryLocations
+
+ |
+ + Delivery Locations + | +
+ The locations where activity related to this tender will take place. + + |
+ + array of Location objects + | +
+
+ deliveryAddresses
+
+ |
+ + Delivery Addresses + | +
+ The addresses to which, or where, goods or services related to this tender will be delivered. + + |
+ + array of Address objects + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryLocations
+
+ |
+ + Delivery Locations + | +
+ The locations where activity related to this tender, contract or license will be delivered. + + |
+ + array of Location objects + | +
+
+ deliveryLocation
+
+ |
+ + Delivery Location + | +
+ The location where activity related to this tender, contract or license will be delivered, or will take place. + ++ + Deprecated in OCDS 1.2.0: + + This field is deprecated in favour of `.deliveryLocations` to support items with multiple delivery locations. + + |
+ + Location object + | +
+
+ deliveryAddresses
+
+ |
+ + Delivery Addresses + | +
+ The addresses to which, or where, goods or services related to this tender, contract or license will be delivered. + + |
+ + array of Address objects + | +
+
+ deliveryAddress
+
+ |
+ + Delivery Address + | +
+ The address to which, or where, goods or services related to this tender, contract or license will be delivered. + ++ + Deprecated in OCDS 1.2.0: + + This field is deprecated in favour of `.deliveryAddresses` to support items with multiple delivery locations. + + |
+ + Address object + | +
+ Location +
+ +
+ The extension defines a new Location object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ A name or description of this location. This might include the name(s) of the location(s), or might provide a human-readable description of the location to be covered. + + |
+ + string + | +
+
+ geometry
+
+ |
+ + Geometry + | +
+ We follow the GeoJSON standard to express basic location information, using longitude, latitude, and optional elevation values in the WGS84 (EPSG:4326) projection. A point location can be identified by geocoding an address. For concession licenses, or other scenarios covering a polygon location that is not contained in a known gazetteer, polygon and multi-polygon can be used. + + |
+ + object + | +
+
+ geometry.
+ |
+ + Type + | +
+ The type of GeoJSON Geometry Objects being provided. To provide longitude, latitude, and optional elevation, use 'Point', and enter an array of [longitude, latitude] or [longitude, latitude, elevation] as the value of the coordinates field: e.g. [-122.085, 37.42]. + + |
+ + string from closed geometryType codelist + | +
+
+ geometry.
+ |
+ + Coordinates + | +
+ The relevant array of points, e.g. [longitude, latitude] or [longitude, latitude, elevation], or a nested array of points, for the GeoJSON geometry being described. The longitude and latitude must be expressed in decimal degrees in the WGS84 (EPSG:4326) projection. + + |
+ + array of numbers / arrays + | +
+
+ gazetteer
+
+ |
+ + Gazetteer + | +
+ Identifiers from a gazetteer (a geographical index or directory) for the location. + + |
+ + object + | +
+
+ gazetteer.
+ |
+ + Gazetteer scheme + | +
+ The identifier of the gazetteer. The |
+ + string from open locationGazetteers codelist + | +
+
+ gazetteer.
+ |
+ + Identifiers + | +
+ An array of one or more codes drawn from the gazetteer indicated by the |
+ + array of strings + | +
+
+ uri
+
+ |
+ + URI + | +
+ A URI to a further description of the location. This might be a human-readable document with information on the location, or a machine-readable description of the location. + + |
+ + string + | +
+ Address +
+ +
+ The extension defines these fields in the Address object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ The description of the address. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/location/v1.1.4/codelists/locationGazetteers.csv b/en/extensions/location/v1.1.4/codelists/locationGazetteers.csv
new file mode 100644
index 000000000..5b4e78336
--- /dev/null
+++ b/en/extensions/location/v1.1.4/codelists/locationGazetteers.csv
@@ -0,0 +1,7 @@
+Category,Code,Title,Description,Source,URI Pattern
+Sub-National,NUTS,EU Nomenclature of Territorial Units for Statistics,The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union.,http://simap.europa.eu/codes-and-nomenclatures/codes-nuts/index_en.htm,http://nuts.psi.enakting.org/id/
+National,ISO2,ISO Country Codes (3166-1 alpha-2),ISO 2-Digit Country Codes,http://www.iso.org/iso/country_codes.htm,
+Universal,GEONAMES,GeoNames,"GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations.",http://www.geonames.org/,http://www.geonames.org/
+Universal,OSMN,OpenStreetMap Node,"OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes may have tags to indicate the particular geographic feature they represent.",,http://www.openstreetmap.org/node/
+Universal,OSMR,OpenStreetMap Relation,"Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap.",http://wiki.openstreetmap.org/wiki/Relation,http://www.openstreetmap.org/relation/
+Universal,OSMW,OpenStreetMap Way,An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. May be used to describe fragments of roads or local boundaries and bounding boxes.,http://wiki.openstreetmap.org/wiki/Way,http://www.openstreetmap.org/way/
diff --git a/en/extensions/location/v1.1.4/extension.json b/en/extensions/location/v1.1.4/extension.json
new file mode 100644
index 000000000..a2c529a5d
--- /dev/null
+++ b/en/extensions/location/v1.1.4/extension.json
@@ -0,0 +1,23 @@
+{
+ "name": {
+ "en": "Location",
+ "es": "Ubicaci\u00f3n"
+ },
+ "description": {
+ "en": "Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects.",
+ "es": "Permite indicar el punto de entrega o el sitio de las obras para una l\u00ednea de pedido determinada en los objetos de licitaci\u00f3n, adjudicaci\u00f3n y contrato."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/location/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "locationGazetteers.csv",
+ "geometryType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/en/extensions/location/v1.1.4/index.html b/en/extensions/location/v1.1.4/index.html
new file mode 100644
index 000000000..9e63fce0d
--- /dev/null
+++ b/en/extensions/location/v1.1.4/index.html
@@ -0,0 +1,375 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Location +
+ ++ Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ geometryType.csv +
+ +
+ You can download the geometryType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ Point
+
+ |
+ + Point + | +
+ For type 'Point', the 'coordinates' member is a single position. + +
|
+
+
+ MultiPoint
+
+ |
+ + MultiPoint + | +
+ For type 'MultiPoint', the 'coordinates' member is an array of positions. + +
|
+
+
+ LineString
+
+ |
+ + LineString + | +
+ For type 'LineString', the 'coordinates' member is an array of two or more positions. + +
|
+
+
+ MultiLineString
+
+ |
+ + MultiLineString + | +
+ For type 'MultiLineString', the 'coordinates' member is an array of LineString coordinate arrays. + +
|
+
+
+ Polygon
+
+ |
+ + Polygon + | +
+ For type 'Polygon', the 'coordinates' member MUST be an array of linear ring coordinate arrays. + +
|
+
+
+ MultiPolygon
+
+ |
+ + MultiPolygon + | +
+ For type 'MultiPolygon', the 'coordinates' member is an array of Polygon coordinate arrays. + +
|
+
+ locationGazetteers.csv +
+ +
+ You can download the locationGazetteers.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ NUTS
+
+ |
+ + EU Nomenclature of Territorial Units for Statistics + | +
+ The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union. + +
|
+
+
+ ISO2
+
+ |
+ + ISO Country Codes (3166-1 alpha-2) + | +
+ ISO 2-Digit Country Codes + +
|
+
+
+ GEONAMES
+
+ |
+ + GeoNames + | +
+ GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations. + +
|
+
+
+ OSMN
+
+ |
+ + OpenStreetMap Node + | +
+ OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes may have tags to indicate the particular geographic feature they represent. + +
|
+
+
+ OSMR
+
+ |
+ + OpenStreetMap Relation + | +
+ Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap. + +
|
+
+
+ OSMW
+
+ |
+ + OpenStreetMap Way + | +
+ An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. May be used to describe fragments of roads or local boundaries and bounding boxes. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/location/v1.1.4/release-schema.json b/en/extensions/location/v1.1.4/release-schema.json
new file mode 100644
index 000000000..e6e64bf84
--- /dev/null
+++ b/en/extensions/location/v1.1.4/release-schema.json
@@ -0,0 +1,111 @@
+{
+ "definitions": {
+ "Item": {
+ "properties": {
+ "deliveryLocation": {
+ "title": "Delivery Location",
+ "description": "The location where activity related to this tender, contract or license will be delivered, or will take place.",
+ "$ref": "#/definitions/Location"
+ },
+ "deliveryAddress": {
+ "title": "Delivery Address",
+ "description": "The address to which, or where, goods or services related to this tender, contract or license will be delivered.",
+ "$ref": "#/definitions/Address"
+ }
+ }
+ },
+ "Location": {
+ "type": "object",
+ "title": "Delivery Location",
+ "description": "The location where activity related to this tender, contract or license will be delivered, or will take place. A location can be described by either a geometry (point location, line or polygon), or a gazetteer entry, or both.",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "A name or description of this location. This might include the name(s) of the location(s), or might provide a human readable description of the location to be covered. This description may be used in a user-interface.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "geometry": {
+ "type": "object",
+ "title": "Geometry",
+ "description": "We follow the [GeoJSON standard](http://geojson.org/) to express basic location information, using longitude, latitude, and (optionally) elevation values in the [WGS84](https://en.wikipedia.org/wiki/World_Geodetic_System) (EPSG:4326) projection. A point location can be identified by geocoding a delivery address. For concession licenses, or other contracts covering a polygon location which is not contained in a known gazetteer, polygon and multi-polygon can be used.",
+ "properties": {
+ "type": {
+ "title": "Type",
+ "description": "The type of [GeoJSON Geometry Objects](http://geojson.org/geojson-spec.html#geometry-objects) being provided. To provide longitude, latitude, and (optionally) elevation, use 'Point', and enter an array of [longitude, latitude] or [longitude, latitude, elevation] as the value of the coordinates field: e.g. [-122.085, 37.42]. Note the capitalization of type values, in order to maintain compatibility with GeoJSON.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "enum": [
+ "Point",
+ "MultiPoint",
+ "LineString",
+ "MultiLineString",
+ "Polygon",
+ "MultiPolygon",
+ null
+ ],
+ "codelist": "geometryType.csv",
+ "openCodelist": false
+ },
+ "coordinates": {
+ "title": "Coordinates",
+ "description": "The relevant array of points, e.g. [longitude, latitude] or [longitude, latitude, elevation], or a nested array of points, for the GeoJSON geometry being described. The longitude and latitude MUST be expressed in decimal degrees in the WGS84 (EPSG:4326) projection.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "number",
+ "array"
+ ]
+ }
+ }
+ }
+ },
+ "gazetteer": {
+ "type": "object",
+ "title": "Gazetteer",
+ "description": "A gazetteer is a geographical index or directory. The specific gazetteer used should be specified in scheme, and one or more codes from that gazetteer used in identifier.",
+ "properties": {
+ "scheme": {
+ "title": "Gazetteer scheme",
+ "description": "The entry of the selected gazetteer in the gazetteers codelist. The codelist provides details of services, where available, that can resolve a gazetteer entry to provide location names.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "locationGazetteers.csv",
+ "openCodelist": true
+ },
+ "identifiers": {
+ "title": "Identifiers",
+ "description": "An array of one or more codes drawn from the gazetteer indicated in scheme.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "uri": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "title": "URI",
+ "description": "A URI to a further description of the activity location. This may be a human readable document with information on the location, or a machine-readable description of the location."
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/location/v1.1.4/schema/index.html b/en/extensions/location/v1.1.4/schema/index.html
new file mode 100644
index 000000000..8c6212726
--- /dev/null
+++ b/en/extensions/location/v1.1.4/schema/index.html
@@ -0,0 +1,432 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Location +
+ ++ Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Communicating the location of proposed or executed contract delivery is important to many users of contracting data.
+This extension introduces two properties at the items level to describe location:
-
+
deliveryAddress- a standardAddressblock which can be used to provide a postal address where services should be delivered.
+deliveryLocation- a new block consisting of GeoJSON and Gazetteer entries to describe a wider range of locations to which the contract line item relates.
+
The locationGazetteers.csv codelist's Category column indicates whether the gazetteer has identifiers for the whole world ('Universal') or only some subset ('National' or 'Sub-National').
Example
+Below is an example of a geolocated item:
+{
+ "items": [
+ {
+ "id": "item1",
+ "description": "Ceremonial Trumpets for Oxford Town Hall",
+ "classification": {
+ "description": "Trumpets",
+ "scheme": "CPV",
+ "id": "37312100",
+ "uri": "http://purl.org/cpv/2008/code-37312100"
+ },
+ "deliveryLocation": {
+ "geometry": {
+ "type": "Point",
+ "coordinates": [51.751944, -1.257778]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": ["2640729"]
+ },
+ "description": "Central Oxford",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "deliveryAddress": {
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom",
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford"
+ },
+ "unit": {
+ "name": "Items",
+ "value": {
+ "currency": "GBP",
+ "amount": 10000
+ }
+ },
+ "quantity": 10
+ }
+ ]
+}
+``
+
+If the procurement related to the rebuilding of a road, then the item could also specify more complex geometries such as:
+
+```json
+{
+"deliveryLocation": {
+ "geometry": {
+ "type": "LineString",
+ "coordinates": [ [ -1.256503402048622, 51.747792026616821 ], [ -1.256477837243949, 51.747500168748303 ], [ -1.256466773131763, 51.747365723021403 ], [ -1.256471969911729, 51.747246699996332 ], [ -1.256481860557471, 51.747182243160943 ], [ -1.256497618535434, 51.747079648666102 ] ]
+ },
+ "gazetteer": {
+ "scheme": "OSMW",
+ "identifiers": ["27895985"]
+ },
+ "description": "St Aldate's",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+}
+}
+You can take the contents of the geometry object, excluding the geometry keyword, and plug this into any GeoJSON tool to see the shape that is described.
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.4
+-
+
- Disallow
Location.geometryandLocation.gazetteerfrom being null (bug introduced in v1.1.3)
+ - Correct the order of longitude and latitude in field descriptions to match the GeoJSON specification +
- Describe elevation or altitude values +
- Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow
Location.geometry.coordinatesfrom having null in its array of coordinates
+ - Disallow
Location.gazetteer.identifiersfrom having null in its array of strings
+ - Correct name of locationGazetteers.csv codelist (was locationGazeteers.csv) +
- Allow
Location.geometryandLocation.gazetteerto be null
+ - Add title and description to
Location.gazetteer
+ - Add description to
Item.deliveryLocation,Item.deliveryAddress
+ - Add geometryType.csv codelist for
Location.geometry.type
+ - List codelists in extension.json +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/location/v1.1.5/README.md b/en/extensions/location/v1.1.5/README.md
new file mode 100644
index 000000000..5346a801f
--- /dev/null
+++ b/en/extensions/location/v1.1.5/README.md
@@ -0,0 +1,143 @@
+# Location Data
+
+Communicating the location of proposed or executed contract delivery is important to many users of contracting data.
+
+This extension introduces two properties at the `items` level to describe location:
+
+- `deliveryAddress` - a standard `Address` block which can be used to provide a postal address where services should be delivered.
+- `deliveryLocation` - a new block consisting of GeoJSON and Gazetteer entries to describe a wider range of locations to which the contract line item relates.
+
+The `locationGazetteers.csv` codelist's `Category` column indicates whether the gazetteer has identifiers for the whole world ('Universal') or only some subset ('National' or 'Sub-National').
+
+## Example
+
+Below is an example of a geolocated item in the `tender` section:
+
+```json
+{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "description": "Ceremonial Trumpets for Oxford Town Hall",
+ "classification": {
+ "description": "Trumpets",
+ "scheme": "CPV",
+ "id": "37312100",
+ "uri": "http://purl.org/cpv/2008/code-37312100"
+ },
+ "deliveryLocation": {
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 51.751944,
+ -1.257778
+ ]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2640729"
+ ]
+ },
+ "description": "Central Oxford",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "deliveryAddress": {
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom",
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford"
+ },
+ "unit": {
+ "name": "Items",
+ "value": {
+ "currency": "GBP",
+ "amount": 10000
+ }
+ },
+ "quantity": 10
+ }
+ ]
+ }
+}
+```
+
+If the procurement related to the rebuilding of a road, then the item could also specify more complex geometries such as:
+
+```json
+{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "deliveryLocation": {
+ "geometry": {
+ "type": "LineString",
+ "coordinates": [
+ [
+ 102,
+ 0
+ ],
+ [
+ 103,
+ 1
+ ],
+ [
+ 104,
+ 0
+ ],
+ [
+ 105,
+ 1
+ ]
+ ]
+ },
+ "gazetteer": {
+ "scheme": "OSMW",
+ "identifiers": [
+ "27895985"
+ ]
+ },
+ "description": "St Aldate's",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ }
+ }
+ ]
+ }
+}
+```
+
+You can take the contents of the geometry object, excluding the `geometry` keyword, and plug this into any GeoJSON tool to see the shape that is described.
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.5
+
+- Remove type information from field descriptions
+- Review normative and non-normative words
+
+### v1.1.4
+
+- Disallow `Location.geometry` and `Location.gazetteer` from being null (bug introduced in v1.1.3)
+- Correct the order of longitude and latitude in field descriptions to match the GeoJSON specification
+- Describe elevation or altitude values
+- Remove Sphinx directives from readme
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Disallow `Location.geometry.coordinates` from having null in its array of coordinates
+- Disallow `Location.gazetteer.identifiers` from having null in its array of strings
+- Correct name of locationGazetteers.csv codelist (was locationGazeteers.csv)
+- Allow `Location.geometry` and `Location.gazetteer` to be null
+- Add title and description to `Location.gazetteer`
+- Add description to `Item.deliveryLocation`, `Item.deliveryAddress`
+- Add geometryType.csv codelist for `Location.geometry.type`
+- List codelists in extension.json
+- Add tests and tidy code
diff --git a/en/extensions/location/v1.1.5/codelists/geometryType.csv b/en/extensions/location/v1.1.5/codelists/geometryType.csv
new file mode 100644
index 000000000..f053feb6a
--- /dev/null
+++ b/en/extensions/location/v1.1.5/codelists/geometryType.csv
@@ -0,0 +1,7 @@
+Code,Title,Description,Source
+Point,Point,"For type 'Point', the 'coordinates' member is a single position.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiPoint,MultiPoint,"For type 'MultiPoint', the 'coordinates' member is an array of positions.",https://tools.ietf.org/html/rfc7946#section-3.1
+LineString,LineString,"For type 'LineString', the 'coordinates' member is an array of two or more positions.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiLineString,MultiLineString,"For type 'MultiLineString', the 'coordinates' member is an array of LineString coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
+Polygon,Polygon,"For type 'Polygon', the 'coordinates' member must be an array of linear ring coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiPolygon,MultiPolygon,"For type 'MultiPolygon', the 'coordinates' member is an array of Polygon coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
diff --git a/en/extensions/location/v1.1.5/codelists/index.html b/en/extensions/location/v1.1.5/codelists/index.html
new file mode 100644
index 000000000..d595d0cd4
--- /dev/null
+++ b/en/extensions/location/v1.1.5/codelists/index.html
@@ -0,0 +1,577 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Location +
+ ++ Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryLocation
+
+ |
+ + Delivery Location + | +
+ The location where activity related to this tender, contract or license will be delivered, or will take place. + + |
+ + Location object + | +
+
+ deliveryAddress
+
+ |
+ + Delivery Address + | +
+ The address to which, or where, goods or services related to this tender, contract or license will be delivered. + + |
+ + Address object + | +
+ Location +
+ +
+ The extension defines a new Location object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ A name or description of this location. This might include the name(s) of the location(s), or might provide a human readable description of the location to be covered. This description may be used in a user-interface. + + |
+ + string + | +
+
+ geometry
+
+ |
+ + Geometry + | +
+ We follow the GeoJSON standard to express basic location information, using longitude, latitude, and (optionally) elevation values in the WGS84 (EPSG:4326) projection. A point location can be identified by geocoding a delivery address. For concession licenses, or other contracts covering a polygon location which is not contained in a known gazetteer, polygon and multi-polygon can be used. + + |
+ + object + | +
+
+ geometry.
+ |
+ + Type + | +
+ The type of GeoJSON Geometry Objects being provided. To provide longitude, latitude, and (optionally) elevation, use 'Point', and enter an array of [longitude, latitude] or [longitude, latitude, elevation] as the value of the coordinates field: e.g. [-122.085, 37.42]. Note the capitalization of type values, in order to maintain compatibility with GeoJSON. + + |
+ + string from closed geometryType codelist + | +
+
+ geometry.
+ |
+ + Coordinates + | +
+ The relevant array of points, e.g. [longitude, latitude] or [longitude, latitude, elevation], or a nested array of points, for the GeoJSON geometry being described. The longitude and latitude MUST be expressed in decimal degrees in the WGS84 (EPSG:4326) projection. + + |
+ + array of numbers / arrays + | +
+
+ gazetteer
+
+ |
+ + Gazetteer + | +
+ A gazetteer is a geographical index or directory. The specific gazetteer used should be specified in scheme, and one or more codes from that gazetteer used in identifier. + + |
+ + object + | +
+
+ gazetteer.
+ |
+ + Gazetteer scheme + | +
+ The entry of the selected gazetteer in the gazetteers codelist. The codelist provides details of services, where available, that can resolve a gazetteer entry to provide location names. + + |
+ + string from open locationGazetteers codelist + | +
+
+ gazetteer.
+ |
+ + Identifiers + | +
+ An array of one or more codes drawn from the gazetteer indicated in scheme. + + |
+ + array of strings + | +
+
+ uri
+
+ |
+ + URI + | +
+ A URI to a further description of the activity location. This may be a human readable document with information on the location, or a machine-readable description of the location. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/location/v1.1.5/codelists/locationGazetteers.csv b/en/extensions/location/v1.1.5/codelists/locationGazetteers.csv
new file mode 100644
index 000000000..70a421586
--- /dev/null
+++ b/en/extensions/location/v1.1.5/codelists/locationGazetteers.csv
@@ -0,0 +1,7 @@
+Category,Code,Title,Description,Source,URI Pattern
+Sub-National,NUTS,EU Nomenclature of Territorial Units for Statistics,The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union.,http://simap.europa.eu/codes-and-nomenclatures/codes-nuts/index_en.htm,http://nuts.psi.enakting.org/id/
+National,ISO2,ISO Country Codes (3166-1 alpha-2),ISO 2-Digit Country Codes,http://www.iso.org/iso/country_codes.htm,
+Universal,GEONAMES,GeoNames,"GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations.",http://www.geonames.org/,http://www.geonames.org/
+Universal,OSMN,OpenStreetMap Node,"OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes might have tags to indicate the particular geographic feature they represent.",,http://www.openstreetmap.org/node/
+Universal,OSMR,OpenStreetMap Relation,"Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap.",http://wiki.openstreetmap.org/wiki/Relation,http://www.openstreetmap.org/relation/
+Universal,OSMW,OpenStreetMap Way,An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. It can be used to describe fragments of roads or local boundaries and bounding boxes.,http://wiki.openstreetmap.org/wiki/Way,http://www.openstreetmap.org/way/
diff --git a/en/extensions/location/v1.1.5/extension.json b/en/extensions/location/v1.1.5/extension.json
new file mode 100644
index 000000000..7dc7660b4
--- /dev/null
+++ b/en/extensions/location/v1.1.5/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Location",
+ "es": "Ubicaci\u00f3n"
+ },
+ "description": {
+ "en": "Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects.",
+ "es": "Permite indicar el punto de entrega o el sitio de las obras para una l\u00ednea de pedido determinada en los objetos de licitaci\u00f3n, adjudicaci\u00f3n y contrato."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/location/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "locationGazetteers.csv",
+ "geometryType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/location/v1.1.5/index.html b/en/extensions/location/v1.1.5/index.html
new file mode 100644
index 000000000..9d20374ca
--- /dev/null
+++ b/en/extensions/location/v1.1.5/index.html
@@ -0,0 +1,410 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Location +
+ ++ Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ geometryType.csv +
+ +
+ You can download the geometryType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ Point
+
+ |
+ + Point + | +
+ For type 'Point', the 'coordinates' member is a single position. + +
|
+
+
+ MultiPoint
+
+ |
+ + MultiPoint + | +
+ For type 'MultiPoint', the 'coordinates' member is an array of positions. + +
|
+
+
+ LineString
+
+ |
+ + LineString + | +
+ For type 'LineString', the 'coordinates' member is an array of two or more positions. + +
|
+
+
+ MultiLineString
+
+ |
+ + MultiLineString + | +
+ For type 'MultiLineString', the 'coordinates' member is an array of LineString coordinate arrays. + +
|
+
+
+ Polygon
+
+ |
+ + Polygon + | +
+ For type 'Polygon', the 'coordinates' member must be an array of linear ring coordinate arrays. + +
|
+
+
+ MultiPolygon
+
+ |
+ + MultiPolygon + | +
+ For type 'MultiPolygon', the 'coordinates' member is an array of Polygon coordinate arrays. + +
|
+
+ locationGazetteers.csv +
+ +
+ You can download the locationGazetteers.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ NUTS
+
+ |
+ + EU Nomenclature of Territorial Units for Statistics + | +
+ The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union. + +
|
+
+
+ ISO2
+
+ |
+ + ISO Country Codes (3166-1 alpha-2) + | +
+ ISO 2-Digit Country Codes + +
|
+
+
+ GEONAMES
+
+ |
+ + GeoNames + | +
+ GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations. + +
|
+
+
+ OSMN
+
+ |
+ + OpenStreetMap Node + | +
+ OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes might have tags to indicate the particular geographic feature they represent. + +
|
+
+
+ OSMR
+
+ |
+ + OpenStreetMap Relation + | +
+ Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap. + +
|
+
+
+ OSMW
+
+ |
+ + OpenStreetMap Way + | +
+ An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. It can be used to describe fragments of roads or local boundaries and bounding boxes. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/location/v1.1.5/release-schema.json b/en/extensions/location/v1.1.5/release-schema.json
new file mode 100644
index 000000000..1140f74db
--- /dev/null
+++ b/en/extensions/location/v1.1.5/release-schema.json
@@ -0,0 +1,111 @@
+{
+ "definitions": {
+ "Item": {
+ "properties": {
+ "deliveryLocation": {
+ "title": "Delivery Location",
+ "description": "The location where activity related to this tender, contract or license will be delivered, or will take place.",
+ "$ref": "#/definitions/Location"
+ },
+ "deliveryAddress": {
+ "title": "Delivery Address",
+ "description": "The address to which, or where, goods or services related to this tender, contract or license will be delivered.",
+ "$ref": "#/definitions/Address"
+ }
+ }
+ },
+ "Location": {
+ "type": "object",
+ "title": "Delivery Location",
+ "description": "The location where activity related to this tender, contract or license will be delivered, or will take place. A location can be described by either a geometry (point location, line or polygon), or a gazetteer entry, or both.",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "A name or description of this location. This might include the name(s) of the location(s), or might provide a human-readable description of the location to be covered.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "geometry": {
+ "type": "object",
+ "title": "Geometry",
+ "description": "We follow the [GeoJSON standard](http://geojson.org/) to express basic location information, using longitude, latitude, and optional elevation values in the [WGS84](https://en.wikipedia.org/wiki/World_Geodetic_System) (EPSG:4326) projection. A point location can be identified by geocoding a delivery address. For concession licenses, or other contracts covering a polygon location which is not contained in a known gazetteer, polygon and multi-polygon can be used.",
+ "properties": {
+ "type": {
+ "title": "Type",
+ "description": "The type of [GeoJSON Geometry Objects](http://geojson.org/geojson-spec.html#geometry-objects) being provided. To provide longitude, latitude, and optional elevation, use 'Point', and enter an array of [longitude, latitude] or [longitude, latitude, elevation] as the value of the coordinates field: e.g. [-122.085, 37.42].",
+ "type": [
+ "string",
+ "null"
+ ],
+ "enum": [
+ "Point",
+ "MultiPoint",
+ "LineString",
+ "MultiLineString",
+ "Polygon",
+ "MultiPolygon",
+ null
+ ],
+ "codelist": "geometryType.csv",
+ "openCodelist": false
+ },
+ "coordinates": {
+ "title": "Coordinates",
+ "description": "The relevant array of points, e.g. [longitude, latitude] or [longitude, latitude, elevation], or a nested array of points, for the GeoJSON geometry being described. The longitude and latitude must be expressed in decimal degrees in the WGS84 (EPSG:4326) projection.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "number",
+ "array"
+ ]
+ }
+ }
+ }
+ },
+ "gazetteer": {
+ "type": "object",
+ "title": "Gazetteer",
+ "description": "Identifiers from a gazetteer (a geographical index or directory) for the location.",
+ "properties": {
+ "scheme": {
+ "title": "Gazetteer scheme",
+ "description": "The identifier of the gazetteer. The `locationGazetteers.csv` codelist provides details of services, where available, that can resolve a gazetteer entry to provide location names.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "locationGazetteers.csv",
+ "openCodelist": true
+ },
+ "identifiers": {
+ "title": "Identifiers",
+ "description": "An array of one or more codes drawn from the gazetteer indicated by the `scheme` field.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "uri": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "title": "URI",
+ "description": "A URI to a further description of the activity location. This might be a human-readable document with information on the location, or a machine-readable description of the location."
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/location/v1.1.5/schema/index.html b/en/extensions/location/v1.1.5/schema/index.html
new file mode 100644
index 000000000..70804fb81
--- /dev/null
+++ b/en/extensions/location/v1.1.5/schema/index.html
@@ -0,0 +1,432 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Location +
+ ++ Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Communicating the location of proposed or executed contract delivery is important to many users of contracting data.
+This extension introduces two properties at the items level to describe location:
-
+
deliveryAddress- a standardAddressblock which can be used to provide a postal address where services should be delivered.
+deliveryLocation- a new block consisting of GeoJSON and Gazetteer entries to describe a wider range of locations to which the contract line item relates.
+
The locationGazetteers.csv codelist's Category column indicates whether the gazetteer has identifiers for the whole world ('Universal') or only some subset ('National' or 'Sub-National').
Example
+Below is an example of a geolocated item in the tender section:
{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "description": "Ceremonial Trumpets for Oxford Town Hall",
+ "classification": {
+ "description": "Trumpets",
+ "scheme": "CPV",
+ "id": "37312100",
+ "uri": "http://purl.org/cpv/2008/code-37312100"
+ },
+ "deliveryLocation": {
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 51.751944,
+ -1.257778
+ ]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2640729"
+ ]
+ },
+ "description": "Central Oxford",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "deliveryAddress": {
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom",
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford"
+ },
+ "unit": {
+ "name": "Items",
+ "value": {
+ "currency": "GBP",
+ "amount": 10000
+ }
+ },
+ "quantity": 10
+ }
+ ]
+ }
+}
+If the procurement related to the rebuilding of a road, then the item could also specify more complex geometries such as:
+{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "deliveryLocation": {
+ "geometry": {
+ "type": "LineString",
+ "coordinates": [
+ [
+ 102,
+ 0
+ ],
+ [
+ 103,
+ 1
+ ],
+ [
+ 104,
+ 0
+ ],
+ [
+ 105,
+ 1
+ ]
+ ]
+ },
+ "gazetteer": {
+ "scheme": "OSMW",
+ "identifiers": [
+ "27895985"
+ ]
+ },
+ "description": "St Aldate's",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ }
+ }
+ ]
+ }
+}
+You can take the contents of the geometry object, excluding the geometry keyword, and plug this into any GeoJSON tool to see the shape that is described.
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.5
+-
+
- Remove type information from field descriptions +
- Review normative and non-normative words +
v1.1.4
+-
+
- Disallow
Location.geometryandLocation.gazetteerfrom being null (bug introduced in v1.1.3)
+ - Correct the order of longitude and latitude in field descriptions to match the GeoJSON specification +
- Describe elevation or altitude values +
- Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow
Location.geometry.coordinatesfrom having null in its array of coordinates
+ - Disallow
Location.gazetteer.identifiersfrom having null in its array of strings
+ - Correct name of locationGazetteers.csv codelist (was locationGazeteers.csv) +
- Allow
Location.geometryandLocation.gazetteerto be null
+ - Add title and description to
Location.gazetteer
+ - Add description to
Item.deliveryLocation,Item.deliveryAddress
+ - Add geometryType.csv codelist for
Location.geometry.type
+ - List codelists in extension.json +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/lots/index.html b/en/extensions/lots/index.html
new file mode 100644
index 000000000..79f161af3
--- /dev/null
+++ b/en/extensions/lots/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Location +
+ ++ Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryLocation
+
+ |
+ + Delivery Location + | +
+ The location where activity related to this tender, contract or license will be delivered, or will take place. + + |
+ + Location object + | +
+
+ deliveryAddress
+
+ |
+ + Delivery Address + | +
+ The address to which, or where, goods or services related to this tender, contract or license will be delivered. + + |
+ + Address object + | +
+ Location +
+ +
+ The extension defines a new Location object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ A name or description of this location. This might include the name(s) of the location(s), or might provide a human-readable description of the location to be covered. + + |
+ + string + | +
+
+ geometry
+
+ |
+ + Geometry + | +
+ We follow the GeoJSON standard to express basic location information, using longitude, latitude, and optional elevation values in the WGS84 (EPSG:4326) projection. A point location can be identified by geocoding a delivery address. For concession licenses, or other contracts covering a polygon location which is not contained in a known gazetteer, polygon and multi-polygon can be used. + + |
+ + object + | +
+
+ geometry.
+ |
+ + Type + | +
+ The type of GeoJSON Geometry Objects being provided. To provide longitude, latitude, and optional elevation, use 'Point', and enter an array of [longitude, latitude] or [longitude, latitude, elevation] as the value of the coordinates field: e.g. [-122.085, 37.42]. + + |
+ + string from closed geometryType codelist + | +
+
+ geometry.
+ |
+ + Coordinates + | +
+ The relevant array of points, e.g. [longitude, latitude] or [longitude, latitude, elevation], or a nested array of points, for the GeoJSON geometry being described. The longitude and latitude must be expressed in decimal degrees in the WGS84 (EPSG:4326) projection. + + |
+ + array of numbers / arrays + | +
+
+ gazetteer
+
+ |
+ + Gazetteer + | +
+ Identifiers from a gazetteer (a geographical index or directory) for the location. + + |
+ + object + | +
+
+ gazetteer.
+ |
+ + Gazetteer scheme + | +
+ The identifier of the gazetteer. The |
+ + string from open locationGazetteers codelist + | +
+
+ gazetteer.
+ |
+ + Identifiers + | +
+ An array of one or more codes drawn from the gazetteer indicated by the |
+ + array of strings + | +
+
+ uri
+
+ |
+ + URI + | +
+ A URI to a further description of the activity location. This might be a human-readable document with information on the location, or a machine-readable description of the location. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/lots/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/lots/master/release-schema.json b/en/extensions/lots/master/release-schema.json
new file mode 100644
index 000000000..f38345061
--- /dev/null
+++ b/en/extensions/lots/master/release-schema.json
@@ -0,0 +1,409 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "lots": {
+ "title": "Lots",
+ "description": "A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLots identifier is given, the values ought to be interpreted as applicable to the whole tender. Details about the whole tender can be overridden for a given lot through their inclusion in the lot object.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Lot"
+ }
+ },
+ "lotDetails": {
+ "title": "Lot Details",
+ "description": "Details of any criteria that apply to bidding on the lots in this tender.",
+ "type": "object",
+ "properties": {
+ "maximumLotsBidPerSupplier": {
+ "title": "Maximum lots per supplier",
+ "description": "The maximum number of lots that one supplier can bid on as part of this contracting process.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "maximumLotsAwardedPerSupplier": {
+ "title": "Maximum lots per supplier",
+ "description": "The maximum number of lots that can be awarded to one supplier as part of this contracting process.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "awardCriteriaDetails": {
+ "title": "Award criteria details",
+ "description": "Any detailed or further information on the award or selection criteria.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "lotGroups": {
+ "title": "Lot groups",
+ "description": "Where the buyer reserves the right to combine lots, or wishes to specify the total value for a group of lots, a lot group is used to capture this information.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/LotGroup"
+ }
+ }
+ }
+ },
+ "Document": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "The identifiers of the lots to which this document relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "relatedLot": {
+ "title": "Related lot",
+ "description": "The identifier of the lot to which this item relates.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Milestone": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "The identifiers of the lots to which this milestone relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "The identifiers of the lots to which this award relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Amendment": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "The identifiers of the lots to which this amendment relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "RelatedProcess": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "The identifiers of the lots to which this related process relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Lot": {
+ "title": "Lots",
+ "description": "A lot is a grouping of items within a tender that can be bid on or awarded together.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Lot ID",
+ "description": "A local identifier for this lot, such as a lot number. This is used in relatedLots references at the item, document and award level.",
+ "type": "string"
+ },
+ "identifiers": {
+ "title": "Identifiers",
+ "description": "Identifiers for this lot. This field can be used to provide internal identifiers for the lot, such as identifiers from a buyer's document management system or procurement system.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/SimpleIdentifier"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "title": {
+ "title": "Title",
+ "description": "A title for this lot.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Description",
+ "description": "A description of this lot.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "title": "Lot Status",
+ "description": "The current status of the process related to this lot.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "tenderStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "planning",
+ "planned",
+ "active",
+ "cancelled",
+ "unsuccessful",
+ "complete",
+ "withdrawn",
+ null
+ ]
+ },
+ "value": {
+ "title": "Lot value",
+ "description": "The maximum estimated value of this lot.",
+ "$ref": "#/definitions/Value"
+ },
+ "minValue": {
+ "title": "Minimum value",
+ "description": "The estimated minimum value of the lot. A negative value indicates that the contracting process may involve payments from the supplier to the buyer (commonly used in concession contracts).",
+ "$ref": "#/definitions/Value"
+ },
+ "tenderPeriod": {
+ "title": "Tender period",
+ "description": "The period when this lot is open for submissions. The end date is the closing date for bid submissions.",
+ "$ref": "#/definitions/Period"
+ },
+ "contractPeriod": {
+ "title": "Contract period",
+ "description": "The period over which the contract is estimated or specified to be active. If the lot does not specify explicit dates, the duration field can be used.",
+ "$ref": "#/definitions/Period"
+ },
+ "buyer": {
+ "title": "Buyer",
+ "description": "The organization aiming to conclude a contract with a supplier or to use the goods, works or services in this lot. This may be different from the procuring entity who may be specified in the tender data.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "additionalClassifications": {
+ "title": "Additional classifications",
+ "description": "Additional classifications for this lot.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "mainProcurementCategory": {
+ "title": "Main procurement category",
+ "description": "The primary category describing the main object of this lot, using the closed procurementCategory codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "procurementCategory.csv",
+ "openCodelist": false,
+ "enum": [
+ "goods",
+ "services",
+ "works",
+ null
+ ]
+ },
+ "additionalProcurementCategories": {
+ "title": "Additional procurement categories",
+ "description": "Any additional categories describing the objects of this lot, using the open extendedProcurementCategory codelist.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "extendedProcurementCategory.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "enquiryPeriod": {
+ "title": "Enquiry period",
+ "description": "The period during which potential bidders may submit questions and requests for clarification about this lot to the buyer or the procuring entity.",
+ "$ref": "#/definitions/Period"
+ },
+ "milestones": {
+ "title": "Milestones",
+ "description": "Milestones associated with this lot.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Milestone"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "submissionMethodDetails": {
+ "title": "Submission method details",
+ "description": "Information about the methods by which bids are submitted for this lot. This can include the address, e-mail address or online service to which bids are submitted, and any special requirements to be followed for submissions. More structured information can be provided using the submission terms extension.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "extension_explorer:source": {
+ "identifier": "lots",
+ "version": "master"
+ }
+ },
+ "LotGroup": {
+ "title": "Lot group",
+ "description": "Where the buyer reserves the right to combine lots, or wishes to specify the total value for a group of lots, a lot group is used to capture this information.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Lot group identifier",
+ "description": "A local identifier for this group of lots.",
+ "type": "string"
+ },
+ "identifiers": {
+ "title": "Identifiers",
+ "description": "Identifiers for this lot group. This field can be used to provide internal identifiers for the lot group, such as identifiers from a buyer's document management system or procurement system.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/SimpleIdentifier"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "title": {
+ "title": "Title",
+ "description": "A title for this lot group.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "A description of this lot group.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "A list of the identifiers of the lots that form this group. Lots can appear in more than one group.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "optionToCombine": {
+ "title": "Option to combine",
+ "description": "The buyer reserves the right to combine the lots in this group when awarding a contract.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "maximumValue": {
+ "title": "Maximum value",
+ "description": "The maximum estimated value of the lots in this group. This can be lower than the sum total of lot values",
+ "$ref": "#/definitions/Value"
+ }
+ },
+ "extension_explorer:source": {
+ "identifier": "lots",
+ "version": "master"
+ }
+ },
+ "SimpleIdentifier": {
+ "title": "Simple identifier",
+ "description": "An unambiguous reference to a resource within a given context.",
+ "type": "object",
+ "properties": {
+ "scheme": {
+ "title": "Scheme",
+ "description": "The list, register or system from which the identifier is taken.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "The identifier taken from the scheme.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "versionId": true,
+ "minLength": 1
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "lots",
+ "version": "master"
+ }
+ }
+ }
+}
diff --git a/en/extensions/lots/master/schema/index.html b/en/extensions/lots/master/schema/index.html
new file mode 100644
index 000000000..f651eeae3
--- /dev/null
+++ b/en/extensions/lots/master/schema/index.html
@@ -0,0 +1,1158 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lots +
+ ++ A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLot identifier is given, the values ought to be interpreted as applicable to the whole tender. +
+
+
+
+
+
+
+
+ How to set
+
+
+
+ + Documentation +
+A lot is a grouping of items within a contracting process that can be bid on or awarded together. This extension adds the concept of a lot to OCDS.
+Guidance
+If a contracting process is divided into lots, then you should add each lot to the tender.lots array.
If a contracting process is not divided into lots, then you should nonetheless add a single, virtual lot. If a data element can be mapped to either a tender field or a tender.lots field, you should map it to the tender.lots field. In this way, information is accessible at the same location for all contracting processes, regardless of whether the process is actually divided into lots.
Modelling
+The lots extension maintains the overall structure of an OCDS release, with items, documents and milestones nested immediately within tender, awards and contracts sections, but it introduces an array of Lots in the tender section, and the ability to cross-reference a specific relatedLot for each item, and an array of relatedLots for documents, milestones and awards.
The lotDetails and lotGroups sections allow more complex conditions around the award of lots to be expressed, such as the maximum value of a group of lots.
This means that systems which are not 'lot aware' can still understand the overall value of contracting taking place, key events, and relationships between buyers and suppliers. At the same time, 'lot aware' systems can make use of the cross-referenced information to present a lot-centric view on the information to users, or to analyze contracting lot by lot.
+Related Lot
+The relatedLot (singular) field is available for:
-
+
- items +
An array of relatedLots (plural) can be provided for each of:
-
+
- documents +
- milestones +
- awards +
In other extensions, the following objects can also declare related lots:
+-
+
- bids submitted by tenderers, in the bid extension +
- sources of finance (
Finance), in the finance extension
+
When lots are used, all items should have a relatedLot field.
Documents and milestones may have a relatedLots field. Those without this field ought to be interpreted as applicable to the tender as a whole.
The items within an award should have a relatedLot field. Publishers may also reference all the lots an award relates to at the award level using relatedLots.
How to set tender.status if lots' statuses differ?
+tender.status and tender.lots.status use the closed tenderStatus.csv codelist. This codelist progresses from planning statuses ('planning', 'planned'), to 'active' status, and then result statuses ('complete', 'cancelled', 'unsuccessful').
-
+
- If any lot's status is 'active', then
tender.statusshould be 'active', to indicate that some lots are awaiting results.
+ - If all lots' status are a result status, then
tender.statusdescribes the aggregate result: +-
+
- If at least one lot's status is 'complete', then
tender.statusshould be 'complete', to indicate that there is at least one award.
+ - Otherwise, if at least one lot's status is 'unsuccessful', then
tender.statusshould be 'unsuccessful', to indicate that the procedure was completed but unsuccessfully.
+ - Otherwise, If all lots' status are 'cancelled', then
tender.statusshould be 'cancelled', to indicate that the procedure was discontinued as a whole.
+
+ - If at least one lot's status is 'complete', then
Examples
+A tender is issued for consultancy in the development of a new public building. This might include items for:
+-
+
- Architectural design +
- Architectural advisory services +
- Civil engineering consultancy +
- Structural engineering consultancy +
Although part of the same tender, the buyer is willing to award these different items to different firms, and so divides the tender into three lots.
+{
+ "tender": {
+ "items": [
+ {
+ "id": "0001",
+ "description": "Architectural advice",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71210000",
+ "description": "Advisory architectural services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0002",
+ "description": "Architectural design",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71220000",
+ "description": "Architectural design services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0003",
+ "description": "Civil engineering consultant",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71311000",
+ "description": "Civil engineering consultancy services"
+ },
+ "relatedLot": "lot-2"
+ },
+ {
+ "id": "0004",
+ "description": "Structural engineering services",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71312000",
+ "description": "Structural engineering consultancy services"
+ },
+ "relatedLot": "lot-3"
+ }
+ ],
+ "value": {
+ "amount": 1200000,
+ "currency": "GBP"
+ },
+ "lots": [
+ {
+ "id": "lot-1",
+ "identifiers": [
+ {
+ "id": "PROC/2020/0024-ABC-FGHI-1",
+ "scheme": "internal"
+ }
+ ],
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ },
+ "tenderPeriod": {
+ "endDate": "2020-07-30T23:59:59+01:00"
+ },
+ "submissionMethodDetails": "https://www.acme.com/tender-submission/. All missing tenderer-related documents can be submitted later. Economic operators who ...",
+ "enquiryPeriod": {
+ "endDate": "2020-07-15T23:59:59+01:00"
+ },
+ "contractPeriod": {
+ "startDate": "2020-10-10T00:00:00Z",
+ "endDate": "2021-11-10T00:00:00Z"
+ },
+ "mainProcurementCategory": "services",
+ "additionalProcurementCategories": [
+ "consultingServices"
+ ],
+ "additionalClassifications": [
+ {
+ "id": "serv-a",
+ "scheme": "internal",
+ "description": "Services (Architectural)"
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2020-10-10T00:00:00Z"
+ }
+ ]
+ },
+ {
+ "id": "lot-2",
+ "identifiers": [
+ {
+ "id": "PROC/2020/0024-ABC-FGHI-2",
+ "scheme": "internal"
+ }
+ ],
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ },
+ "mainProcurementCategory": "services",
+ "additionalProcurementCategories": [
+ "consultingServices"
+ ],
+ "tenderPeriod": {
+ "endDate": "2020-07-30T23:59:59+01:00"
+ },
+ "submissionMethodDetails": "https://www.acme.com/tender-submission/. All missing tenderer-related documents can be submitted later. Economic operators who ...",
+ "enquiryPeriod": {
+ "endDate": "2020-07-15T23:59:59+01:00"
+ },
+ "contractPeriod": {
+ "startDate": "2020-12-10T00:00:00Z",
+ "endDate": "2021-12-10T00:00:00Z"
+ },
+ "additionalClassifications": [
+ {
+ "id": "serv-ce",
+ "scheme": "internal",
+ "description": "Services (Civil engineering)"
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2020-12-10T00:00:00Z"
+ }
+ ]
+ },
+ {
+ "id": "lot-3",
+ "identifiers": [
+ {
+ "id": "PROC/2020/0024-ABC-FGHI-3",
+ "scheme": "internal"
+ }
+ ],
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ },
+ "tenderPeriod": {
+ "endDate": "2020-07-30T23:59:59+01:00"
+ },
+ "submissionMethodDetails": "https://www.acme.com/tender-submission/. All missing tenderer-related documents can be submitted later. Economic operators who ...",
+ "enquiryPeriod": {
+ "endDate": "2020-07-15T23:59:59+01:00"
+ },
+ "contractPeriod": {
+ "startDate": "2021-02-10T00:00:00Z",
+ "endDate": "2022-02-10T00:00:00Z"
+ },
+ "mainProcurementCategory": "services",
+ "additionalProcurementCategories": [
+ "consultingServices"
+ ],
+ "additionalClassifications": [
+ {
+ "id": "serv-se",
+ "scheme": "internal",
+ "description": "Services (Structural engineering)"
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2021-02-10T00:00:00Z"
+ }
+ ]
+ }
+ ],
+ "lotGroups": [
+ {
+ "id": "lot-group-1",
+ "title": "Civil and structural engineering services",
+ "description": "Civil and structural engineering services for the development of a new public building",
+ "identifiers": [
+ {
+ "id": "PROC/2020/0024-ABC-FGHI-G1",
+ "scheme": "internal"
+ }
+ ],
+ "relatedLots": [
+ "lot-2",
+ "lot-3"
+ ],
+ "optionToCombine": true,
+ "maximumValue": {
+ "currency": "GBP",
+ "amount": 1000000
+ }
+ }
+ ],
+ "lotDetails": {
+ "maximumLotsBidPerSupplier": 4,
+ "maximumLotsAwardedPerSupplier": 2,
+ "awardCriteriaDetails": "Percentage of people aggregated nationwide contestants undertake to cover, as indicated in their Economic Bids. The evaluation of proposals will be conducted based on the provisions of Article Y of the law on public private partnerships, and the provisions of the tender rules, performing in a first stage an evaluation of the technical bids and subsequently an assessment of the financial offer of the participants."
+ },
+ "amendments": [
+ {
+ "id": "1",
+ "relatedLots": [
+ "lot-1"
+ ],
+ "description": "Submission deadline extended."
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+Unreleased
+-
+
- Add fields:
+
-
+
Amendment.relatedLots
+Lot.additionalClassifications
+Lot.buyer
+Lot.enquiryPeriod
+Lot.tenderPeriod
+Lot.identifiers
+Lot.mainProcurementCategory
+Lot.additionalProcurementCategories
+Lot.milestones
+Lot.minValue
+Lot.submissionMethodDetails
+LotGroup.identifiers
+LotGroup.title
+LotGroup.description
+RelatedProcess.relatedLots
+
+ - Make
Lot.idandLotGroup.idrequired so that lots and lot groups are merged by identifier
+ - Move
Bid.relatedLotsto the Bid statistics and details extension
+ - Move
Finance.relatedLotsto the Finance extension
+ - Update field descriptions to use a neutral voice +
- Add usage guidance +
v1.1.5
+-
+
- Add
tender.lotDetails.awardCriteriaDetailsfield
+ - Add
Finance.relatedLotsfield
+ - Add
Lot.contractPeriodfield
+ - Remove type information from field descriptions +
- Review normative and non-normative words +
v1.1.4
+-
+
- Disallow
Tender.lotDetailsfrom being null (bug introduced in first release)
+ Tender.lotDetailsno longer uses a$refto aLotDetailsdefinition
+- Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow
relatedLotsfields from having null in their arrays of strings
+ - Add enum to
Lot.status
+ - Allow
relatedLotsfields to be null
+ - Add title and description to
Tender.lotDetails
+ - Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/lots/v1.1.4/README.md b/en/extensions/lots/v1.1.4/README.md
new file mode 100644
index 000000000..5109d4ed2
--- /dev/null
+++ b/en/extensions/lots/v1.1.4/README.md
@@ -0,0 +1,165 @@
+# Lots
+
+When a single tender is broken down into parts that can be bid upon, and awarded, separately, this is modelled using the **lots extension**.
+
+The lots extension maintains the overall structure of an OCDS release, with items, documents and milestones nested immediately within `tender`, `award` and `contract` items, but it introduces an array of Lots in the `tender` section, and the ability to cross-reference a specific `relatedLot` for each item, and an array of `relatedLots` for documents, milestones and awards.
+
+Optional `lotDetails` and `lotGroups` section allow more complex conditions around the award of lots to be expressed, such as the maximum value of a group of lots.
+
+This means that systems which are not 'lot aware' can still understand the overall value of contracting taking place, key events, and relationships between buyers and suppliers. At the same time, 'lot aware' systems can make use of the cross-referenced information to present a lot-centric view on the information to users, or to analyze contracting lot by lot.
+
+## Related Lot
+
+The `relatedLot` (singular) property is available for:
+
+- items
+
+An array of `relatedLots` (plural) can be provided for each of:
+
+- documents
+- milestones
+- awards
+
+When lots are used, **all** items should have a `relatedLot` property.
+
+Documents and milestones can optionally have a `relatedLots` property. Those without this property should be interpreted as applicable to the tender as a whole.
+
+The items within an award should each have a `relatedLot` property, but publishers may choose to also reference all the lots an award relates to at the award level using `relatedLots`.
+
+Where the bid extension is also in use, each bid can also declare its related lots.
+
+## Worked example
+
+A tender is issued for consultancy in the development of a new public building. This might include items for:
+
+- Architectural design
+- Architectural advisory services
+- Civil engineering consultancy
+- Structural engineering consultancy
+
+Although part of the same tender, the buyer is willing to award these different items to different firms, and so divides the tender into three lots.
+
+```json
+{
+ "tender": {
+ "items": [
+ {
+ "id": "0001",
+ "description": "Architectural advice",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71210000",
+ "description": "Advisory architectural services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0002",
+ "description": "Architectural design",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71220000",
+ "description": "Architectural design services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0003",
+ "description": "Civil engineering consultant",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71311000",
+ "description": "Civil engineering consultancy services"
+ },
+ "relatedLot": "lot-2"
+ },
+ {
+ "id": "0004",
+ "description": "Structural engineering services",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71312000",
+ "description": "Structural engineering consultancy services"
+ },
+ "relatedLot": "lot-3"
+ }
+ ],
+ "value": {
+ "amount": 1200000,
+ "currency": "GBP"
+ },
+ "lots": [
+ {
+ "id": "lot-1",
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ }
+ },
+ {
+ "id": "lot-2",
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ }
+ },
+ {
+ "id": "lot-3",
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ }
+ }
+ ],
+ "lotGroups": [
+ {
+ "id": "lot-group-1",
+ "relatedLots": [
+ "lot-2",
+ "lot-3"
+ ],
+ "optionToCombine": true,
+ "maximumValue": {
+ "currency": "GBP",
+ "amount": 1000000
+ }
+ }
+ ],
+ "lotDetails": {
+ "maximumLotsBidPerSupplier": 4,
+ "maximumLotsAwardedPerSupplier": 2
+ }
+ }
+}
+```
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.4
+
+- Disallow `Tender.lotDetails` from being null (bug introduced in first release)
+- `Tender.lotDetails` no longer uses a `$ref` to a `LotDetails` definition
+- Remove Sphinx directives from readme
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Disallow `relatedLots` fields from having null in their arrays of strings
+- Add enum to `Lot.status`
+- Allow `relatedLots` fields to be null
+- Add title and description to `Tender.lotDetails`
+- Use Apache 2.0 License
+- Add tests and tidy code
diff --git a/en/extensions/lots/v1.1.4/extension.json b/en/extensions/lots/v1.1.4/extension.json
new file mode 100644
index 000000000..bb80f5ee0
--- /dev/null
+++ b/en/extensions/lots/v1.1.4/extension.json
@@ -0,0 +1,22 @@
+{
+ "name": {
+ "en": "Lots",
+ "es": "Lotes"
+ },
+ "description": {
+ "en": "A tender process may be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features can then reference the lot they are related to using relatedLot. Where no relatedLot identifier is given, the values should be interpreted as applicable to the whole tender.",
+ "es": "Un proceso de licitaci\u00f3n se puede dividir en lotes, donde los licitadores pueden ofertar en uno o m\u00e1s lotes. Los detalles de cada lote se pueden proporcionar aqu\u00ed. Los art\u00edculos, documentos y otras caracter\u00edsticas pueden hacer referencia al lote que est\u00e1n relacionados con el uso de relatedLot. Cuando no se indique ning\u00fan identificador relacionado, los valores deben interpretarse como aplicables a toda la licitaci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/lots/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"
+ ]
+}
diff --git a/en/extensions/lots/v1.1.4/index.html b/en/extensions/lots/v1.1.4/index.html
new file mode 100644
index 000000000..0de8d988c
--- /dev/null
+++ b/en/extensions/lots/v1.1.4/index.html
@@ -0,0 +1,429 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lots +
+ ++ A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLot identifier is given, the values ought to be interpreted as applicable to the whole tender. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ lots
+
+ |
+ + Lots + | +
+ A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLots identifier is given, the values ought to be interpreted as applicable to the whole tender. Details about the whole tender can be overridden for a given lot through their inclusion in the lot object. + + |
+ + array of Lot objects + | +
+
+ lotDetails
+
+ |
+ + Lot Details + | +
+ Details of any criteria that apply to bidding on the lots in this tender. + + |
+ + object + | +
+
+ lotDetails.
+ |
+ + Maximum lots per supplier + | +
+ The maximum number of lots that one supplier can bid on as part of this contracting process. + + |
+ + integer + | +
+
+ lotDetails.
+ |
+ + Maximum lots per supplier + | +
+ The maximum number of lots that can be awarded to one supplier as part of this contracting process. + + |
+ + integer + | +
+
+ lotDetails.
+ |
+ + Award criteria details + | +
+ Any detailed or further information on the award or selection criteria. + + |
+ + string + | +
+
+ lotGroups
+
+ |
+ + Lot groups + | +
+ Where the buyer reserves the right to combine lots, or wishes to specify the total value for a group of lots, a lot group is used to capture this information. + + |
+ + array of LotGroup objects + | +
+ Document +
+ +
+ The extension defines these fields in the Document object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ The identifiers of the lots to which this document relates. + + |
+ + array of strings + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLot
+
+ |
+ + Related lot + | +
+ The identifier of the lot to which this item relates. + + |
+ + string + | +
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ The identifiers of the lots to which this milestone relates. + + |
+ + array of strings + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ The identifiers of the lots to which this award relates. + + |
+ + array of strings + | +
+ Amendment +
+ +
+ The extension defines these fields in the Amendment object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ The identifiers of the lots to which this amendment relates. + + |
+ + array of strings + | +
+ RelatedProcess +
+ +
+ The extension defines these fields in the RelatedProcess object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ The identifiers of the lots to which this related process relates. + + |
+ + array of strings + | +
+ Lot +
+ +
+ The extension defines a new Lot object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Lot ID + | +
+ A local identifier for this lot, such as a lot number. This is used in relatedLots references at the item, document and award level. + + |
+ + string + | +
+
+ identifiers
+
+ |
+ + Identifiers + | +
+ Identifiers for this lot. This field can be used to provide internal identifiers for the lot, such as identifiers from a buyer's document management system or procurement system. + + |
+ + array of SimpleIdentifier objects + | +
+
+ title
+
+ |
+ + Title + | +
+ A title for this lot. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A description of this lot. + + |
+ + string + | +
+
+ status
+
+ |
+ + Lot Status + | +
+ The current status of the process related to this lot. + + |
+ + string from closed tenderStatus codelist + | +
+
+ value
+
+ |
+ + Lot value + | +
+ The maximum estimated value of this lot. + + |
+ + Value object + | +
+
+ minValue
+
+ |
+ + Minimum value + | +
+ The estimated minimum value of the lot. A negative value indicates that the contracting process may involve payments from the supplier to the buyer (commonly used in concession contracts). + + |
+ + Value object + | +
+
+ tenderPeriod
+
+ |
+ + Tender period + | +
+ The period when this lot is open for submissions. The end date is the closing date for bid submissions. + + |
+ + Period object + | +
+
+ contractPeriod
+
+ |
+ + Contract period + | +
+ The period over which the contract is estimated or specified to be active. If the lot does not specify explicit dates, the duration field can be used. + + |
+ + Period object + | +
+
+ buyer
+
+ |
+ + Buyer + | +
+ The organization aiming to conclude a contract with a supplier or to use the goods, works or services in this lot. This may be different from the procuring entity who may be specified in the tender data. + + |
+ + OrganizationReference object + | +
+
+ additionalClassifications
+
+ |
+ + Additional classifications + | +
+ Additional classifications for this lot. + + |
+ + array of Classification objects + | +
+
+ mainProcurementCategory
+
+ |
+ + Main procurement category + | +
+ The primary category describing the main object of this lot, using the closed procurementCategory codelist. + + |
+ + string from closed procurementCategory codelist + | +
+
+ additionalProcurementCategories
+
+ |
+ + Additional procurement categories + | +
+ Any additional categories describing the objects of this lot, using the open extendedProcurementCategory codelist. + + |
+ + array of strings from open extendedProcurementCategory codelist + | +
+
+ enquiryPeriod
+
+ |
+ + Enquiry period + | +
+ The period during which potential bidders may submit questions and requests for clarification about this lot to the buyer or the procuring entity. + + |
+ + Period object + | +
+
+ milestones
+
+ |
+ + Milestones + | +
+ Milestones associated with this lot. + + |
+ + array of Milestone objects + | +
+
+ submissionMethodDetails
+
+ |
+ + Submission method details + | +
+ Information about the methods by which bids are submitted for this lot. This can include the address, e-mail address or online service to which bids are submitted, and any special requirements to be followed for submissions. More structured information can be provided using the submission terms extension. + + |
+ + string + | +
+ LotGroup +
+ +
+ The extension defines a new LotGroup object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Lot group identifier + | +
+ A local identifier for this group of lots. + + |
+ + string + | +
+
+ identifiers
+
+ |
+ + Identifiers + | +
+ Identifiers for this lot group. This field can be used to provide internal identifiers for the lot group, such as identifiers from a buyer's document management system or procurement system. + + |
+ + array of SimpleIdentifier objects + | +
+
+ title
+
+ |
+ + Title + | +
+ A title for this lot group. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A description of this lot group. + + |
+ + string + | +
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ A list of the identifiers of the lots that form this group. Lots can appear in more than one group. + + |
+ + array of strings + | +
+
+ optionToCombine
+
+ |
+ + Option to combine + | +
+ The buyer reserves the right to combine the lots in this group when awarding a contract. + + |
+ + boolean + | +
+
+ maximumValue
+
+ |
+ + Maximum value + | +
+ The maximum estimated value of the lots in this group. This can be lower than the sum total of lot values + + |
+ + Value object + | +
+ SimpleIdentifier +
+ +
+ The extension defines a new SimpleIdentifier object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ scheme
+
+ |
+ + Scheme + | +
+ The list, register or system from which the identifier is taken. + + |
+ + string + | +
+
+ id
+
+ |
+ + ID + | +
+ The identifier taken from the scheme. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/lots/v1.1.4/release-schema.json b/en/extensions/lots/v1.1.4/release-schema.json
new file mode 100644
index 000000000..e1fa5be37
--- /dev/null
+++ b/en/extensions/lots/v1.1.4/release-schema.json
@@ -0,0 +1,218 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "lots": {
+ "title": "Lots",
+ "description": "A tender process may be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features can then reference the lot they are related to using relatedLot. Where no relatedLots identifier is given, the values should be interpreted as applicable to the whole tender. Properties of tender can be overridden for a given Lot through their inclusion in the Lot object.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Lot"
+ }
+ },
+ "lotDetails": {
+ "title": "Lot Details",
+ "description": "If this tender is divided into lots, details can be provided here of any criteria that apply to bidding on these lots. This extended property is currently focused on fields required by the EU TED data standard",
+ "type": "object",
+ "properties": {
+ "maximumLotsBidPerSupplier": {
+ "title": "Maximum lots per supplier",
+ "description": "The maximum number of lots that one supplier may bid for as part of this contracting process.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "maximumLotsAwardedPerSupplier": {
+ "title": "Maximum lots per supplier",
+ "description": "The maximum number of lots that may be awarded to one supplier as part of this contracting process.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ }
+ }
+ },
+ "lotGroups": {
+ "title": "Lot groups",
+ "description": "Where the buyer reserves the right to combine lots, or wishes to specify the total value for a group of lots, a lot group is used to capture this information.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/LotGroup"
+ }
+ }
+ }
+ },
+ "Document": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "If this document relates to a particular lot, provide the identifier(s) of the related lot(s) here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "relatedLot": {
+ "title": "Related lot",
+ "description": "If this item belongs to a lot, provide the identifier of the related lot here. Each item may only belong to a single lot.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Milestone": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "If this milestone relates to a particular lot, provide the identifier(s) of the related lot(s) here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "If this award relates to one or more specific lots, provide the identifier(s) of the related lot(s) here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Bid": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "If this bid relates to one or more specific lots, provide the identifier(s) of the related lot(s) here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Lot": {
+ "title": "Lots",
+ "description": "A lot is a grouping of items within a tender that can be bid on or awarded together.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Lot ID",
+ "type": "string",
+ "description": "A local identifier for this lot, such as a lot number. This is used in relatedLots references at the item, document and award level."
+ },
+ "title": {
+ "title": "Title",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "A title for this lot."
+ },
+ "description": {
+ "title": "Description",
+ "description": "A description of this lot.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "title": "Lot Status",
+ "description": "The current status of the process related to this lot based on the [tenderStatus codelist](http://standard.open-contracting.org/1.1/en/schema/codelists/#tender-status)",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "tenderStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "planning",
+ "planned",
+ "active",
+ "cancelled",
+ "unsuccessful",
+ "complete",
+ "withdrawn",
+ null
+ ]
+ },
+ "value": {
+ "title": "Lot value",
+ "$ref": "#/definitions/Value",
+ "description": "The maximum estimated value of this lot."
+ }
+ }
+ },
+ "LotGroup": {
+ "title": "Lot group",
+ "description": "Where the buyer reserves the right to combine lots, or wishes to specify the total value for a group of lots, a lot group is used to capture this information.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Lot group identifier",
+ "type": "string",
+ "description": "A local identifier for this group of lots."
+ },
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "A list of the identifiers of the lots that form this group. Lots may appear in more than one group.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ },
+ "optionToCombine": {
+ "title": "Option to combine",
+ "description": "The buyer reserves the right to combine the lots in this group when awarding a contract.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "maximumValue": {
+ "title": "Maximum value",
+ "description": "The maximum estimated value of the lots in this group. This may be lower than the sum total of lot values",
+ "$ref": "#/definitions/Value"
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/lots/v1.1.4/schema/index.html b/en/extensions/lots/v1.1.4/schema/index.html
new file mode 100644
index 000000000..371bfd92d
--- /dev/null
+++ b/en/extensions/lots/v1.1.4/schema/index.html
@@ -0,0 +1,787 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lots +
+ ++ A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLot identifier is given, the values ought to be interpreted as applicable to the whole tender. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+When a single tender is broken down into parts that can be bid upon, and awarded, separately, this is modelled using the lots extension.
+The lots extension maintains the overall structure of an OCDS release, with items, documents and milestones nested immediately within tender, award and contract items, but it introduces an array of Lots in the tender section, and the ability to cross-reference a specific relatedLot for each item, and an array of relatedLots for documents, milestones and awards.
Optional lotDetails and lotGroups section allow more complex conditions around the award of lots to be expressed, such as the maximum value of a group of lots.
This means that systems which are not 'lot aware' can still understand the overall value of contracting taking place, key events, and relationships between buyers and suppliers. At the same time, 'lot aware' systems can make use of the cross-referenced information to present a lot-centric view on the information to users, or to analyze contracting lot by lot.
+Related Lot
+The relatedLot (singular) property is available for:
-
+
- items +
An array of relatedLots (plural) can be provided for each of:
-
+
- documents +
- milestones +
- awards +
When lots are used, all items should have a relatedLot property.
Documents and milestones can optionally have a relatedLots property. Those without this property should be interpreted as applicable to the tender as a whole.
The items within an award should each have a relatedLot property, but publishers may choose to also reference all the lots an award relates to at the award level using relatedLots.
Where the bid extension is also in use, each bid can also declare its related lots.
+Worked example
+A tender is issued for consultancy in the development of a new public building. This might include items for:
+-
+
- Architectural design +
- Architectural advisory services +
- Civil engineering consultancy +
- Structural engineering consultancy +
Although part of the same tender, the buyer is willing to award these different items to different firms, and so divides the tender into three lots.
+{
+ "tender": {
+ "items": [
+ {
+ "id": "0001",
+ "description": "Architectural advice",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71210000",
+ "description": "Advisory architectural services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0002",
+ "description": "Architectural design",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71220000",
+ "description": "Architectural design services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0003",
+ "description": "Civil engineering consultant",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71311000",
+ "description": "Civil engineering consultancy services"
+ },
+ "relatedLot": "lot-2"
+ },
+ {
+ "id": "0004",
+ "description": "Structural engineering services",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71312000",
+ "description": "Structural engineering consultancy services"
+ },
+ "relatedLot": "lot-3"
+ }
+ ],
+ "value": {
+ "amount": 1200000,
+ "currency": "GBP"
+ },
+ "lots": [
+ {
+ "id": "lot-1",
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ }
+ },
+ {
+ "id": "lot-2",
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ }
+ },
+ {
+ "id": "lot-3",
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ }
+ }
+ ],
+ "lotGroups": [
+ {
+ "id": "lot-group-1",
+ "relatedLots": [
+ "lot-2",
+ "lot-3"
+ ],
+ "optionToCombine": true,
+ "maximumValue": {
+ "currency": "GBP",
+ "amount": 1000000
+ }
+ }
+ ],
+ "lotDetails": {
+ "maximumLotsBidPerSupplier": 4,
+ "maximumLotsAwardedPerSupplier": 2
+ }
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.4
+-
+
- Disallow
Tender.lotDetailsfrom being null (bug introduced in first release)
+ Tender.lotDetailsno longer uses a$refto aLotDetailsdefinition
+- Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow
relatedLotsfields from having null in their arrays of strings
+ - Add enum to
Lot.status
+ - Allow
relatedLotsfields to be null
+ - Add title and description to
Tender.lotDetails
+ - Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/lots/v1.1.5/README.md b/en/extensions/lots/v1.1.5/README.md
new file mode 100644
index 000000000..76383044b
--- /dev/null
+++ b/en/extensions/lots/v1.1.5/README.md
@@ -0,0 +1,199 @@
+# Lots
+
+When a single tender is broken down into parts that can be bid upon, and awarded, separately, this is modelled using the **lots extension**.
+
+The lots extension maintains the overall structure of an OCDS release, with items, documents and milestones nested immediately within `tender`, `awards` and `contracts` sections, but it introduces an array of Lots in the `tender` section, and the ability to cross-reference a specific `relatedLot` for each item, and an array of `relatedLots` for documents, milestones and awards.
+
+The `lotDetails` and `lotGroups` sections allow more complex conditions around the award of lots to be expressed, such as the maximum value of a group of lots.
+
+This means that systems which are not 'lot aware' can still understand the overall value of contracting taking place, key events, and relationships between buyers and suppliers. At the same time, 'lot aware' systems can make use of the cross-referenced information to present a lot-centric view on the information to users, or to analyze contracting lot by lot.
+
+## Related Lot
+
+The `relatedLot` (singular) property is available for:
+
+- items
+
+An array of `relatedLots` (plural) can be provided for each of:
+
+- documents
+- milestones
+- awards
+
+In other extensions, the following objects can also declare related lots:
+
+- bids submitted by tenderers (`Bid`), in the [bid extension](https://github.com/open-contracting-extensions/ocds_bid_extension)
+- sources of finance (`Finance`), in the [finance extension](https://github.com/open-contracting-extensions/ocds_finance_extension)
+
+When lots are used, **all** items should have a `relatedLot` field.
+
+Documents and milestones may have a `relatedLots` field. Those without this field ought to be interpreted as applicable to the tender as a whole.
+
+The items within an award should have a `relatedLot` field. Publishers may also reference all the lots an award relates to at the award level using `relatedLots`.
+
+## How to set `tender.status` if lots' statuses differ?
+
+`tender.status` and `Lot.status` use the closed tenderStatus.csv codelist. This codelist progresses from planning statuses ('planning', 'planned'), to 'active' status, and then result statuses ('complete', 'cancelled', 'unsuccessful').
+
+- If any lot's status is 'active', then `tender.status` should be 'active', to indicate that some lots are awaiting results.
+- If all lots' status are a result status, then `tender.status` describes the aggregate result:
+ - If at least one lot's status is 'complete', then `tender.status` should be 'complete', to indicate that there is at least one award.
+ - Otherwise, if at least one lot's status is 'unsuccessful', then `tender.status` should be 'unsuccessful', to indicate that the procedure was completed but unsuccessfully.
+ - Otherwise, If all lots' status are 'cancelled', then `tender.status` should be 'cancelled', to indicate that the procedure was discontinued as a whole.
+
+## Example
+
+A tender is issued for consultancy in the development of a new public building. This might include items for:
+
+- Architectural design
+- Architectural advisory services
+- Civil engineering consultancy
+- Structural engineering consultancy
+
+Although part of the same tender, the buyer is willing to award these different items to different firms, and so divides the tender into three lots.
+
+```json
+{
+ "tender": {
+ "items": [
+ {
+ "id": "0001",
+ "description": "Architectural advice",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71210000",
+ "description": "Advisory architectural services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0002",
+ "description": "Architectural design",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71220000",
+ "description": "Architectural design services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0003",
+ "description": "Civil engineering consultant",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71311000",
+ "description": "Civil engineering consultancy services"
+ },
+ "relatedLot": "lot-2"
+ },
+ {
+ "id": "0004",
+ "description": "Structural engineering services",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71312000",
+ "description": "Structural engineering consultancy services"
+ },
+ "relatedLot": "lot-3"
+ }
+ ],
+ "value": {
+ "amount": 1200000,
+ "currency": "GBP"
+ },
+ "lots": [
+ {
+ "id": "lot-1",
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ },
+ "contractPeriod": {
+ "startDate": "2020-10-10T00:00:00Z",
+ "endDate": "2021-11-10T00:00:00Z"
+ }
+ },
+ {
+ "id": "lot-2",
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ },
+ "contractPeriod": {
+ "startDate": "2020-12-10T00:00:00Z",
+ "endDate": "2021-12-10T00:00:00Z"
+ }
+ },
+ {
+ "id": "lot-3",
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ },
+ "contractPeriod": {
+ "startDate": "2021-02-10T00:00:00Z",
+ "endDate": "2022-02-10T00:00:00Z"
+ }
+ }
+ ],
+ "lotGroups": [
+ {
+ "id": "lot-group-1",
+ "relatedLots": [
+ "lot-2",
+ "lot-3"
+ ],
+ "optionToCombine": true,
+ "maximumValue": {
+ "currency": "GBP",
+ "amount": 1000000
+ }
+ }
+ ],
+ "lotDetails": {
+ "maximumLotsBidPerSupplier": 4,
+ "maximumLotsAwardedPerSupplier": 2,
+ "awardCriteriaDetails": "Percentage of people aggregated nationwide contestants undertake to cover, as indicated in their Economic Bids. The evaluation of proposals will be conducted based on the provisions of Article Y of the law on public private partnerships, and the provisions of the tender rules, performing in a first stage an evaluation of the technical bids and subsequently an assessment of the financial offer of the participants."
+ }
+ }
+}
+```
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.5
+
+- Add `tender.lotDetails.awardCriteriaDetails` field
+- Add `Finance.relatedLots` field
+- Add `Lot.contractPeriod` field
+- Remove type information from field descriptions
+- Review normative and non-normative words
+
+### v1.1.4
+
+- Disallow `Tender.lotDetails` from being null (bug introduced in first release)
+- `Tender.lotDetails` no longer uses a `$ref` to a `LotDetails` definition
+- Remove Sphinx directives from readme
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Disallow `relatedLots` fields from having null in their arrays of strings
+- Add enum to `Lot.status`
+- Allow `relatedLots` fields to be null
+- Add title and description to `Tender.lotDetails`
+- Use Apache 2.0 License
+- Add tests and tidy code
diff --git a/en/extensions/lots/v1.1.5/extension.json b/en/extensions/lots/v1.1.5/extension.json
new file mode 100644
index 000000000..47ce11118
--- /dev/null
+++ b/en/extensions/lots/v1.1.5/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Lots",
+ "es": "Lotes"
+ },
+ "description": {
+ "en": "A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLot identifier is given, the values ought to be interpreted as applicable to the whole tender.",
+ "es": "Un proceso de licitaci\u00f3n se puede dividir en lotes, donde los licitadores pueden ofertar en uno o m\u00e1s lotes. Los detalles de cada lote se pueden proporcionar aqu\u00ed. Los art\u00edculos, documentos y otras caracter\u00edsticas pueden hacer referencia al lote que est\u00e1n relacionados con el uso de relatedLot. Cuando no se indique ning\u00fan identificador relacionado, los valores deben interpretarse como aplicables a toda la licitaci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/lots/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json",
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_finance_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/lots/v1.1.5/index.html b/en/extensions/lots/v1.1.5/index.html
new file mode 100644
index 000000000..4aa95109a
--- /dev/null
+++ b/en/extensions/lots/v1.1.5/index.html
@@ -0,0 +1,471 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lots +
+ ++ A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLot identifier is given, the values ought to be interpreted as applicable to the whole tender. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ lots
+
+ |
+ + Lots + | +
+ A tender process may be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features can then reference the lot they are related to using relatedLot. Where no relatedLots identifier is given, the values should be interpreted as applicable to the whole tender. Properties of tender can be overridden for a given Lot through their inclusion in the Lot object. + + |
+ + array of Lot objects + | +
+
+ lotDetails
+
+ |
+ + Lot Details + | +
+ If this tender is divided into lots, details can be provided here of any criteria that apply to bidding on these lots. This extended property is currently focused on fields required by the EU TED data standard + + |
+ + object + | +
+
+ lotDetails.
+ |
+ + Maximum lots per supplier + | +
+ The maximum number of lots that one supplier may bid for as part of this contracting process. + + |
+ + integer + | +
+
+ lotDetails.
+ |
+ + Maximum lots per supplier + | +
+ The maximum number of lots that may be awarded to one supplier as part of this contracting process. + + |
+ + integer + | +
+
+ lotGroups
+
+ |
+ + Lot groups + | +
+ Where the buyer reserves the right to combine lots, or wishes to specify the total value for a group of lots, a lot group is used to capture this information. + + |
+ + array of LotGroup objects + | +
+ Document +
+ +
+ The extension defines these fields in the Document object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ If this document relates to a particular lot, provide the identifier(s) of the related lot(s) here. + + |
+ + array of strings + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLot
+
+ |
+ + Related lot + | +
+ If this item belongs to a lot, provide the identifier of the related lot here. Each item may only belong to a single lot. + + |
+ + string + | +
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ If this milestone relates to a particular lot, provide the identifier(s) of the related lot(s) here. + + |
+ + array of strings + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ If this award relates to one or more specific lots, provide the identifier(s) of the related lot(s) here. + + |
+ + array of strings + | +
+ Bid +
+ +
+ The extension defines these fields in the Bid object from the Bid statistics and details extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ + This field is modified from its original version. + +If this bid relates to one or more specific lots, provide the identifier(s) of the related lot(s) here. + + |
+ + array of strings + | +
+ Lot +
+ +
+ The extension defines a new Lot object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Lot ID + | +
+ A local identifier for this lot, such as a lot number. This is used in relatedLots references at the item, document and award level. + + |
+ + string + | +
+
+ title
+
+ |
+ + Title + | +
+ A title for this lot. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A description of this lot. + + |
+ + string + | +
+
+ status
+
+ |
+ + Lot Status + | +
+ The current status of the process related to this lot based on the tenderStatus codelist + + |
+ + string from closed tenderStatus codelist + | +
+
+ value
+
+ |
+ + Lot value + | +
+ The maximum estimated value of this lot. + + |
+ + Value object + | +
+ LotGroup +
+ +
+ The extension defines a new LotGroup object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Lot group identifier + | +
+ A local identifier for this group of lots. + + |
+ + string + | +
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ A list of the identifiers of the lots that form this group. Lots may appear in more than one group. + + |
+ + array of strings + | +
+
+ optionToCombine
+
+ |
+ + Option to combine + | +
+ The buyer reserves the right to combine the lots in this group when awarding a contract. + + |
+ + boolean + | +
+
+ maximumValue
+
+ |
+ + Maximum value + | +
+ The maximum estimated value of the lots in this group. This may be lower than the sum total of lot values + + |
+ + Value object + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/lots/v1.1.5/release-schema.json b/en/extensions/lots/v1.1.5/release-schema.json
new file mode 100644
index 000000000..674246dd6
--- /dev/null
+++ b/en/extensions/lots/v1.1.5/release-schema.json
@@ -0,0 +1,248 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "lots": {
+ "title": "Lots",
+ "description": "A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLots identifier is given, the values ought to be interpreted as applicable to the whole tender. Properties of tender can be overridden for a given Lot through their inclusion in the Lot object.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Lot"
+ }
+ },
+ "lotDetails": {
+ "title": "Lot Details",
+ "description": "If this tender is divided into lots, details can be provided here of any criteria that apply to bidding on these lots.",
+ "type": "object",
+ "properties": {
+ "maximumLotsBidPerSupplier": {
+ "title": "Maximum lots per supplier",
+ "description": "The maximum number of lots that one supplier can bid on as part of this contracting process.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "maximumLotsAwardedPerSupplier": {
+ "title": "Maximum lots per supplier",
+ "description": "The maximum number of lots that can be awarded to one supplier as part of this contracting process.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "awardCriteriaDetails": {
+ "title": "Award criteria details",
+ "description": "Any detailed or further information on the award or selection criteria.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "lotGroups": {
+ "title": "Lot groups",
+ "description": "Where the buyer reserves the right to combine lots, or wishes to specify the total value for a group of lots, a lot group is used to capture this information.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/LotGroup"
+ }
+ }
+ }
+ },
+ "Document": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "If this document relates to a particular lot, provide the identifier(s) of the related lot(s) here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "relatedLot": {
+ "title": "Related lot",
+ "description": "If this item belongs to a lot, provide the identifier of the related lot here.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Milestone": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "If this milestone relates to a particular lot, provide the identifier(s) of the related lot(s) here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "If this award relates to one or more specific lots, provide the identifier(s) of the related lot(s) here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Bid": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "If this bid relates to one or more specific lots, provide the identifier(s) of the related lot(s) here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Finance": {
+ "properties": {
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "If this source of finance relates to one or more specific lots, provide the identifier(s) of the related lot(s) here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Lot": {
+ "title": "Lots",
+ "description": "A lot is a grouping of items within a tender that can be bid on or awarded together.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Lot ID",
+ "type": "string",
+ "description": "A local identifier for this lot, such as a lot number. This is used in relatedLots references at the item, document and award level."
+ },
+ "title": {
+ "title": "Title",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "A title for this lot."
+ },
+ "description": {
+ "title": "Description",
+ "description": "A description of this lot.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "title": "Lot Status",
+ "description": "The current status of the process related to this lot.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "tenderStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "planning",
+ "planned",
+ "active",
+ "cancelled",
+ "unsuccessful",
+ "complete",
+ "withdrawn",
+ null
+ ]
+ },
+ "value": {
+ "title": "Lot value",
+ "$ref": "#/definitions/Value",
+ "description": "The maximum estimated value of this lot."
+ },
+ "contractPeriod": {
+ "title": "Contract period",
+ "description": "The period over which the contract is estimated or specified to be active. If the lot does not specify explicit dates, the duration field can be used.",
+ "$ref": "#/definitions/Period"
+ }
+ }
+ },
+ "LotGroup": {
+ "title": "Lot group",
+ "description": "Where the buyer reserves the right to combine lots, or wishes to specify the total value for a group of lots, a lot group is used to capture this information.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Lot group identifier",
+ "type": "string",
+ "description": "A local identifier for this group of lots."
+ },
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "A list of the identifiers of the lots that form this group. Lots can appear in more than one group.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ },
+ "optionToCombine": {
+ "title": "Option to combine",
+ "description": "The buyer reserves the right to combine the lots in this group when awarding a contract.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "maximumValue": {
+ "title": "Maximum value",
+ "description": "The maximum estimated value of the lots in this group. This can be lower than the sum total of lot values",
+ "$ref": "#/definitions/Value"
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/lots/v1.1.5/schema/index.html b/en/extensions/lots/v1.1.5/schema/index.html
new file mode 100644
index 000000000..13d53fb59
--- /dev/null
+++ b/en/extensions/lots/v1.1.5/schema/index.html
@@ -0,0 +1,875 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lots +
+ ++ A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLot identifier is given, the values ought to be interpreted as applicable to the whole tender. +
+
+
+
+
+
+
+
+ How to set
+
+
+
+ + Documentation +
+When a single tender is broken down into parts that can be bid upon, and awarded, separately, this is modelled using the lots extension.
+The lots extension maintains the overall structure of an OCDS release, with items, documents and milestones nested immediately within tender, awards and contracts sections, but it introduces an array of Lots in the tender section, and the ability to cross-reference a specific relatedLot for each item, and an array of relatedLots for documents, milestones and awards.
The lotDetails and lotGroups sections allow more complex conditions around the award of lots to be expressed, such as the maximum value of a group of lots.
This means that systems which are not 'lot aware' can still understand the overall value of contracting taking place, key events, and relationships between buyers and suppliers. At the same time, 'lot aware' systems can make use of the cross-referenced information to present a lot-centric view on the information to users, or to analyze contracting lot by lot.
+Related Lot
+The relatedLot (singular) property is available for:
-
+
- items +
An array of relatedLots (plural) can be provided for each of:
-
+
- documents +
- milestones +
- awards +
In other extensions, the following objects can also declare related lots:
+-
+
- bids submitted by tenderers (
Bid), in the bid extension
+ - sources of finance (
Finance), in the finance extension
+
When lots are used, all items should have a relatedLot field.
Documents and milestones may have a relatedLots field. Those without this field ought to be interpreted as applicable to the tender as a whole.
The items within an award should have a relatedLot field. Publishers may also reference all the lots an award relates to at the award level using relatedLots.
How to set tender.status if lots' statuses differ?
+tender.status and Lot.status use the closed tenderStatus.csv codelist. This codelist progresses from planning statuses ('planning', 'planned'), to 'active' status, and then result statuses ('complete', 'cancelled', 'unsuccessful').
-
+
- If any lot's status is 'active', then
tender.statusshould be 'active', to indicate that some lots are awaiting results.
+ - If all lots' status are a result status, then
tender.statusdescribes the aggregate result: +-
+
- If at least one lot's status is 'complete', then
tender.statusshould be 'complete', to indicate that there is at least one award.
+ - Otherwise, if at least one lot's status is 'unsuccessful', then
tender.statusshould be 'unsuccessful', to indicate that the procedure was completed but unsuccessfully.
+ - Otherwise, If all lots' status are 'cancelled', then
tender.statusshould be 'cancelled', to indicate that the procedure was discontinued as a whole.
+
+ - If at least one lot's status is 'complete', then
Example
+A tender is issued for consultancy in the development of a new public building. This might include items for:
+-
+
- Architectural design +
- Architectural advisory services +
- Civil engineering consultancy +
- Structural engineering consultancy +
Although part of the same tender, the buyer is willing to award these different items to different firms, and so divides the tender into three lots.
+{
+ "tender": {
+ "items": [
+ {
+ "id": "0001",
+ "description": "Architectural advice",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71210000",
+ "description": "Advisory architectural services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0002",
+ "description": "Architectural design",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71220000",
+ "description": "Architectural design services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0003",
+ "description": "Civil engineering consultant",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71311000",
+ "description": "Civil engineering consultancy services"
+ },
+ "relatedLot": "lot-2"
+ },
+ {
+ "id": "0004",
+ "description": "Structural engineering services",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71312000",
+ "description": "Structural engineering consultancy services"
+ },
+ "relatedLot": "lot-3"
+ }
+ ],
+ "value": {
+ "amount": 1200000,
+ "currency": "GBP"
+ },
+ "lots": [
+ {
+ "id": "lot-1",
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ },
+ "contractPeriod": {
+ "startDate": "2020-10-10T00:00:00Z",
+ "endDate": "2021-11-10T00:00:00Z"
+ }
+ },
+ {
+ "id": "lot-2",
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ },
+ "contractPeriod": {
+ "startDate": "2020-12-10T00:00:00Z",
+ "endDate": "2021-12-10T00:00:00Z"
+ }
+ },
+ {
+ "id": "lot-3",
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ },
+ "contractPeriod": {
+ "startDate": "2021-02-10T00:00:00Z",
+ "endDate": "2022-02-10T00:00:00Z"
+ }
+ }
+ ],
+ "lotGroups": [
+ {
+ "id": "lot-group-1",
+ "relatedLots": [
+ "lot-2",
+ "lot-3"
+ ],
+ "optionToCombine": true,
+ "maximumValue": {
+ "currency": "GBP",
+ "amount": 1000000
+ }
+ }
+ ],
+ "lotDetails": {
+ "maximumLotsBidPerSupplier": 4,
+ "maximumLotsAwardedPerSupplier": 2,
+ "awardCriteriaDetails": "Percentage of people aggregated nationwide contestants undertake to cover, as indicated in their Economic Bids. The evaluation of proposals will be conducted based on the provisions of Article Y of the law on public private partnerships, and the provisions of the tender rules, performing in a first stage an evaluation of the technical bids and subsequently an assessment of the financial offer of the participants."
+ }
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.5
+-
+
- Add
tender.lotDetails.awardCriteriaDetailsfield
+ - Add
Finance.relatedLotsfield
+ - Add
Lot.contractPeriodfield
+ - Remove type information from field descriptions +
- Review normative and non-normative words +
v1.1.4
+-
+
- Disallow
Tender.lotDetailsfrom being null (bug introduced in first release)
+ Tender.lotDetailsno longer uses a$refto aLotDetailsdefinition
+- Remove Sphinx directives from readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow
relatedLotsfields from having null in their arrays of strings
+ - Add enum to
Lot.status
+ - Allow
relatedLotsfields to be null
+ - Add title and description to
Tender.lotDetails
+ - Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/medicine/index.html b/en/extensions/medicine/index.html
new file mode 100644
index 000000000..bd3403abd
--- /dev/null
+++ b/en/extensions/medicine/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lots +
+ ++ A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLot identifier is given, the values ought to be interpreted as applicable to the whole tender. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ lots
+
+ |
+ + Lots + | +
+ A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLots identifier is given, the values ought to be interpreted as applicable to the whole tender. Properties of tender can be overridden for a given Lot through their inclusion in the Lot object. + + |
+ + array of Lot objects + | +
+
+ lotDetails
+
+ |
+ + Lot Details + | +
+ If this tender is divided into lots, details can be provided here of any criteria that apply to bidding on these lots. + + |
+ + object + | +
+
+ lotDetails.
+ |
+ + Maximum lots per supplier + | +
+ The maximum number of lots that one supplier can bid on as part of this contracting process. + + |
+ + integer + | +
+
+ lotDetails.
+ |
+ + Maximum lots per supplier + | +
+ The maximum number of lots that can be awarded to one supplier as part of this contracting process. + + |
+ + integer + | +
+
+ lotDetails.
+ |
+ + Award criteria details + | +
+ Any detailed or further information on the award or selection criteria. + + |
+ + string + | +
+
+ lotGroups
+
+ |
+ + Lot groups + | +
+ Where the buyer reserves the right to combine lots, or wishes to specify the total value for a group of lots, a lot group is used to capture this information. + + |
+ + array of LotGroup objects + | +
+ Document +
+ +
+ The extension defines these fields in the Document object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ If this document relates to a particular lot, provide the identifier(s) of the related lot(s) here. + + |
+ + array of strings + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLot
+
+ |
+ + Related lot + | +
+ If this item belongs to a lot, provide the identifier of the related lot here. + + |
+ + string + | +
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ If this milestone relates to a particular lot, provide the identifier(s) of the related lot(s) here. + + |
+ + array of strings + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ If this award relates to one or more specific lots, provide the identifier(s) of the related lot(s) here. + + |
+ + array of strings + | +
+ Bid +
+ +
+ The extension defines these fields in the Bid object from the Bid statistics and details extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ + This field is modified from its original version. + +If this bid relates to one or more specific lots, provide the identifier(s) of the related lot(s) here. + + |
+ + array of strings + | +
+ Finance +
+ +
+ The extension defines these fields in the Finance object from the Finance extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ + This field is modified from its original version. + +If this source of finance relates to one or more specific lots, provide the identifier(s) of the related lot(s) here. + + |
+ + array of strings + | +
+ Lot +
+ +
+ The extension defines a new Lot object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Lot ID + | +
+ A local identifier for this lot, such as a lot number. This is used in relatedLots references at the item, document and award level. + + |
+ + string + | +
+
+ title
+
+ |
+ + Title + | +
+ A title for this lot. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A description of this lot. + + |
+ + string + | +
+
+ status
+
+ |
+ + Lot Status + | +
+ The current status of the process related to this lot. + + |
+ + string from closed tenderStatus codelist + | +
+
+ value
+
+ |
+ + Lot value + | +
+ The maximum estimated value of this lot. + + |
+ + Value object + | +
+
+ contractPeriod
+
+ |
+ + Contract period + | +
+ The period over which the contract is estimated or specified to be active. If the lot does not specify explicit dates, the duration field can be used. + + |
+ + Period object + | +
+ LotGroup +
+ +
+ The extension defines a new LotGroup object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Lot group identifier + | +
+ A local identifier for this group of lots. + + |
+ + string + | +
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ A list of the identifiers of the lots that form this group. Lots can appear in more than one group. + + |
+ + array of strings + | +
+
+ optionToCombine
+
+ |
+ + Option to combine + | +
+ The buyer reserves the right to combine the lots in this group when awarding a contract. + + |
+ + boolean + | +
+
+ maximumValue
+
+ |
+ + Maximum value + | +
+ The maximum estimated value of the lots in this group. This can be lower than the sum total of lot values + + |
+ + Value object + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/medicine/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/medicine/master/extension.json b/en/extensions/medicine/master/extension.json
new file mode 100644
index 000000000..76d9542f7
--- /dev/null
+++ b/en/extensions/medicine/master/extension.json
@@ -0,0 +1,28 @@
+{
+ "name": {
+ "en": "Medicine",
+ "es": "Medicina"
+ },
+ "description": {
+ "en": "Adds fields to the item object relevant to the procurement of medicines.",
+ "es": "Agrega campos al objeto art\u00edculo relevantes para la adquisici\u00f3n de medicamentos."
+ },
+ "documentationUrl": {
+ "en": "http://extensions.open-contracting.org/en/extensions/medicine/"
+ },
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "dosageForm.csv",
+ "administrationRoute.csv",
+ "container.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/medicine/master/index.html b/en/extensions/medicine/master/index.html
new file mode 100644
index 000000000..bac870958
--- /dev/null
+++ b/en/extensions/medicine/master/index.html
@@ -0,0 +1,441 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Medicine +
+ ++ Adds fields to the item object relevant to the procurement of medicines. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ administrationRoute.csv +
+ +
+ You can download the administrationRoute.csv file in English.
+
| + Code + | ++ Title + | +
|---|---|
+
+ AMNINJ
+
+ |
+ + Injection, amniotic fluid + | +
+
+ BILINJ
+
+ |
+ + Injection, biliary tract + | +
+
+ CHOLINJ
+
+ |
+ + Injection, for cholangiography + | +
+
+ DRESS
+
+ |
+ + Topical application, soaked dressing + | +
+
+ ELECTOSMOS
+
+ |
+ + Electro-osmosis + | +
+
+ IONTO
+
+ |
+ + Topical application, iontophoresis + | +
+
+ SOAK
+
+ |
+ + Immersion (soak) + | +
+
+ SWAB
+
+ |
+ + Topical application, swab + | +
+
+ TOPICAL
+
+ |
+ + Topical + | +
+
+ BUC
+
+ |
+ + Topical application, buccal + | +
+
+ CECINSTL
+
+ |
+ + Instillation, cecostomy + | +
+
+ CERV
+
+ |
+ + Topical application, cervical + | +
+
+ CERVINJ
+
+ |
+ + Injection, cervical + | +
+
+ CERVINS
+
+ |
+ + Insertion, cervical (uterine) + | +
+
+ DEN
+
+ |
+ + Topical application, dental + | +
+
+ DENRINSE
+
+ |
+ + Rinse, dental + | +
+
+ CHEW
+
+ |
+ + Chew, oral + | +
+
+ EXTCORPDIF
+
+ |
+ + Diffusion, extracorporeal + | +
+
+ HEMODIFF
+
+ |
+ + Diffusion, hemodialysis + | +
+
+ TRNSDERMD
+
+ |
+ + Diffusion, transdermal + | +
+
+ DISSOLVE
+
+ |
+ + Dissolve, oral + | +
+
+ SL
+
+ |
+ + Dissolve, sublingual + | +
+
+ DOUCHE
+
+ |
+ + Douche, vaginal + | +
+
+ ENEMA
+
+ |
+ + Enema, rectal + | +
+
+ RETENEMA
+
+ |
+ + Enema, rectal retention + | +
+
+ EFT
+
+ |
+ + Instillation, enteral feeding tube + | +
+
+ ENTINSTL
+
+ |
+ + Instillation, enteral + | +
+
+ EPI
+
+ |
+ + Infusion, epidural + | +
+
+ EPIDURINJ
+
+ |
+ + Injection, epidural + | +
+
+ EPIINJ
+
+ |
+ + Injection, epidural, push + | +
+
+ EPINJSP
+
+ |
+ + Injection, epidural, slow push + | +
+
+ EXTRAMNINJ
+
+ |
+ + Injection, extra-amniotic + | +
+
+ EXTCORPINJ
+
+ |
+ + Injection, extracorporeal + | +
+
+ IVFLUSH
+
+ |
+ + Flush, intravenous catheter + | +
+
+ GBINJ
+
+ |
+ + Injection, gastric button + | +
+
+ GT
+
+ |
+ + Instillation, gastrostomy tube + | +
+
+ NGT
+
+ |
+ + Instillation, nasogastric tube + | +
+
+ OGT
+
+ |
+ + Instillation, orogastric tube + | +
+
+ GUIRR
+
+ |
+ + Irrigation, genitourinary + | +
+
+ GIN
+
+ |
+ + Topical application, gingival + | +
+
+ GINGINJ
+
+ |
+ + Injection, gingival + | +
+
+ HAIR
+
+ |
+ + Topical application, hair + | +
+
+ SHAMPOO
+
+ |
+ + Shampoo + | +
+
+ IDIMPLNT
+
+ |
+ + Implantation, intradermal + | +
+
+ IVITIMPLNT
+
+ |
+ + Implantation, intravitreal + | +
+
+ SQIMPLNT
+
+ |
+ + Implantation, subcutaneous + | +
+
+ IA
+
+ |
+ + Infusion, intraarterial catheter + | +
+
+ IC
+
+ |
+ + Infusion, intracardiac + | +
+
+ ICOR
+
+ |
+ + Infusion, intracoronary + | +
+
+ IOSSC
+
+ |
+ + Infusion, intraosseous, continuous + | +
+
+ IT
+
+ |
+ + Infusion, intrathecal + | +
+
+ IV
+
+ |
+ + Infusion, intravenous + | +
+
+ IVASCINFUS
+
+ |
+ + Infusion, intravascular + | +
+
+ SQINFUS
+
+ |
+ + Infusion, subcutaneous + | +
+
+ IPINHL
+
+ |
+ + Inhalation, respiratory + | +
+
+ IPPB
+
+ |
+ + Inhalation, intermittent positive pressure breathing (ippb) + | +
+
+ NASINHL
+
+ |
+ + Inhalation, nasal + | +
+
+ NEB
+
+ |
+ + Inhalation, nebulization + | +
+
+ TRACH
+
+ |
+ + Inhalation, tracheostomy + | +
+
+ VENT
+
+ |
+ + Inhalation, ventilator + | +
+
+ VENTMASK
+
+ |
+ + Inhalation, ventimask + | +
+
+ BLADINJ
+
+ |
+ + Injection, urinary bladder + | +
+
+ ENDOSININJ
+
+ |
+ + Injection, endosinusial + | +
+
+ HEMOPORT
+
+ |
+ + Injection, hemodialysis port + | +
+
+ IABDINJ
+
+ |
+ + Injection, intra-abdominal + | +
+
+ IAINJ
+
+ |
+ + Injection, intraarterial + | +
+
+ IARTINJ
+
+ |
+ + Injection, intraarticular + | +
+
+ IBURSINJ
+
+ |
+ + Injection, intrabursal + | +
+
+ ICARDINJ
+
+ |
+ + Injection, intracardiac + | +
+
+ ICARTINJ
+
+ |
+ + Injection, intracartilaginous + | +
+
+ ICAUDINJ
+
+ |
+ + Injection, intracaudal + | +
+
+ ICAVINJ
+
+ |
+ + Injection, intracavernous + | +
+
+ ICAVITINJ
+
+ |
+ + Injection, intracavitary + | +
+
+ ICEREBINJ
+
+ |
+ + Injection, intracerebral + | +
+
+ ICISTERNINJ
+
+ |
+ + Injection, intracisternal + | +
+
+ ICORONINJ
+
+ |
+ + Injection, intracoronary + | +
+
+ ICORPCAVINJ
+
+ |
+ + Injection, intracorpus cavernosum + | +
+
+ IDINJ
+
+ |
+ + Injection, intradermal + | +
+
+ IDISCINJ
+
+ |
+ + Injection, intradiscal + | +
+
+ IDUCTINJ
+
+ |
+ + Injection, intraductal + | +
+
+ IDURINJ
+
+ |
+ + Injection, intradural + | +
+
+ IEPIDINJ
+
+ |
+ + Injection, intraepidermal + | +
+
+ IEPITHINJ
+
+ |
+ + Injection, intraepithelial + | +
+
+ ILESINJ
+
+ |
+ + Injection, intralesional + | +
+
+ ILUMINJ
+
+ |
+ + Injection, intraluminal + | +
+
+ ILYMPJINJ
+
+ |
+ + Injection, intralymphatic + | +
+
+ IM
+
+ |
+ + Injection, intramuscular + | +
+
+ IMEDULINJ
+
+ |
+ + Injection, intramedullary + | +
+
+ INTERMENINJ
+
+ |
+ + Injection, interameningeal + | +
+
+ INTERSTITINJ
+
+ |
+ + Injection, interstitial + | +
+
+ IOINJ
+
+ |
+ + Injection, intraocular + | +
+
+ IOSSINJ
+
+ |
+ + Injection, intraosseous + | +
+
+ IOVARINJ
+
+ |
+ + Injection, intraovarian + | +
+
+ IPCARDINJ
+
+ |
+ + Injection, intrapericardial + | +
+
+ IPERINJ
+
+ |
+ + Injection, intraperitoneal + | +
+
+ IPINJ
+
+ |
+ + Injection, intrapulmonary + | +
+
+ IPLRINJ
+
+ |
+ + Injection, intrapleural + | +
+
+ IPROSTINJ
+
+ |
+ + Injection, intraprostatic + | +
+
+ IPUMPINJ
+
+ |
+ + Injection, insulin pump + | +
+
+ ISINJ
+
+ |
+ + Injection, intraspinal + | +
+
+ ISTERINJ
+
+ |
+ + Injection, intrasternal + | +
+
+ ISYNINJ
+
+ |
+ + Injection, intrasynovial + | +
+
+ ITENDINJ
+
+ |
+ + Injection, intratendinous + | +
+
+ ITESTINJ
+
+ |
+ + Injection, intratesticular + | +
+
+ ITHORINJ
+
+ |
+ + Injection, intrathoracic + | +
+
+ ITINJ
+
+ |
+ + Injection, intrathecal + | +
+
+ ITUBINJ
+
+ |
+ + Injection, intratubular + | +
+
+ ITUMINJ
+
+ |
+ + Injection, intratumor + | +
+
+ ITYMPINJ
+
+ |
+ + Injection, intratympanic + | +
+
+ IUINJ
+
+ |
+ + Injection, intrauterine + | +
+
+ IUINJC
+
+ |
+ + Injection, intracervical (uterus) + | +
+
+ IURETINJ
+
+ |
+ + Injection, intraureteral, retrograde + | +
+
+ IVASCINJ
+
+ |
+ + Injection, intravascular + | +
+
+ IVENTINJ
+
+ |
+ + Injection, intraventricular (heart) + | +
+
+ IVESINJ
+
+ |
+ + Injection, intravesicle + | +
+
+ IVINJ
+
+ |
+ + Injection, intravenous + | +
+
+ IVITINJ
+
+ |
+ + Injection, intravitreal + | +
+
+ PAINJ
+
+ |
+ + Injection, periarticular + | +
+
+ PARENTINJ
+
+ |
+ + Injection, parenteral + | +
+
+ PDONTINJ
+
+ |
+ + Injection, periodontal + | +
+
+ PDPINJ
+
+ |
+ + Injection, peritoneal dialysis port + | +
+
+ PDURINJ
+
+ |
+ + Injection, peridural + | +
+
+ PNINJ
+
+ |
+ + Injection, perineural + | +
+
+ PNSINJ
+
+ |
+ + Injection, paranasal sinuses + | +
+
+ RBINJ
+
+ |
+ + Injection, retrobulbar + | +
+
+ SCINJ
+
+ |
+ + Injection, subconjunctival + | +
+
+ SLESINJ
+
+ |
+ + Injection, sublesional + | +
+
+ SOFTISINJ
+
+ |
+ + Injection, soft tissue + | +
+
+ SQ
+
+ |
+ + Injection, subcutaneous + | +
+
+ SUBARACHINJ
+
+ |
+ + Injection, subarachnoid + | +
+
+ SUBMUCINJ
+
+ |
+ + Injection, submucosal + | +
+
+ TRPLACINJ
+
+ |
+ + Injection, transplacental + | +
+
+ TRTRACHINJ
+
+ |
+ + Injection, transtracheal + | +
+
+ URETHINJ
+
+ |
+ + Injection, urethral + | +
+
+ URETINJ
+
+ |
+ + Injection, ureteral + | +
+
+ IOSURGINS
+
+ |
+ + Insertion, intraocular, surgical + | +
+
+ IU
+
+ |
+ + Insertion, intrauterine + | +
+
+ LPINS
+
+ |
+ + Insertion, lacrimal puncta + | +
+
+ PR
+
+ |
+ + Insertion, rectal + | +
+
+ SQSURGINS
+
+ |
+ + Insertion, subcutaneous, surgical + | +
+
+ URETHINS
+
+ |
+ + Insertion, urethral + | +
+
+ VAGINSI
+
+ |
+ + Insertion, vaginal + | +
+
+ BLADINSTL
+
+ |
+ + Instillation, urinary catheter + | +
+
+ CAPDINSTL
+
+ |
+ + Instillation, continuous ambulatory peritoneal dialysis port + | +
+
+ CTINSTL
+
+ |
+ + Instillation, chest tube + | +
+
+ ETINSTL
+
+ |
+ + Instillation, endotracheal tube + | +
+
+ GJT
+
+ |
+ + Instillation, gastro-jejunostomy tube + | +
+
+ IBRONCHINSTIL
+
+ |
+ + Instillation, intrabronchial + | +
+
+ IDUODINSTIL
+
+ |
+ + Instillation, intraduodenal + | +
+
+ IESOPHINSTIL
+
+ |
+ + Instillation, intraesophageal + | +
+
+ IGASTINSTIL
+
+ |
+ + Instillation, intragastric + | +
+
+ IILEALINJ
+
+ |
+ + Instillation, intraileal + | +
+
+ IOINSTL
+
+ |
+ + Instillation, intraocular + | +
+
+ ISININSTIL
+
+ |
+ + Instillation, intrasinal + | +
+
+ ITRACHINSTIL
+
+ |
+ + Instillation, intratracheal + | +
+
+ IUINSTL
+
+ |
+ + Instillation, intrauterine + | +
+
+ JJTINSTL
+
+ |
+ + Instillation, jejunostomy tube + | +
+
+ LARYNGINSTIL
+
+ |
+ + Instillation, laryngeal + | +
+
+ NASALINSTIL
+
+ |
+ + Instillation, nasal + | +
+
+ NASOGASINSTIL
+
+ |
+ + Instillation, nasogastric + | +
+
+ NTT
+
+ |
+ + Instillation, nasotracheal tube + | +
+
+ OJJ
+
+ |
+ + Instillation, orojejunum tube + | +
+
+ OT
+
+ |
+ + Instillation, otic + | +
+
+ PDPINSTL
+
+ |
+ + Instillation, peritoneal dialysis port + | +
+
+ PNSINSTL
+
+ |
+ + Instillation, paranasal sinuses + | +
+
+ RECINSTL
+
+ |
+ + Instillation, rectal + | +
+
+ SININSTIL
+
+ |
+ + Instillation, sinus, unspecified + | +
+
+ SOFTISINSTIL
+
+ |
+ + Instillation, soft tissue + | +
+
+ TRACHINSTL
+
+ |
+ + Instillation, tracheostomy + | +
+
+ TRTYMPINSTIL
+
+ |
+ + Instillation, transtympanic + | +
+
+ URETHINSTL
+
+ |
+ + Instillation, urethral + | +
+
+ ICORNTA
+
+ |
+ + Topical application, intracorneal + | +
+
+ ICORONTA
+
+ |
+ + Topical application, intracoronal (dental) + | +
+
+ IDOUDMAB
+
+ |
+ + Mucosal absorption, intraduodenal + | +
+
+ IESOPHTA
+
+ |
+ + Topical application, intraesophageal + | +
+
+ IGASTIRR
+
+ |
+ + Irrigation, intragastric + | +
+
+ IGASTLAV
+
+ |
+ + Lavage, intragastric + | +
+
+ IILEALTA
+
+ |
+ + Topical application, intraileal + | +
+
+ ILESIRR
+
+ |
+ + Irrigation, intralesional + | +
+
+ ILTOP
+
+ |
+ + Topical application, intralesional + | +
+
+ ILUMTA
+
+ |
+ + Topical application, intraluminal + | +
+
+ IOIRR
+
+ |
+ + Irrigation, intraocular + | +
+
+ IOTOP
+
+ |
+ + Topical application, intraocular + | +
+
+ ITRACHMAB
+
+ |
+ + Mucosal absorption, intratracheal + | +
+
+ BLADIRR
+
+ |
+ + Irrigation, urinary bladder + | +
+
+ RECIRR
+
+ |
+ + Irrigation, rectal + | +
+
+ LARYNGTA
+
+ |
+ + Topical application, laryngeal + | +
+
+ TRNSLING
+
+ |
+ + Translingual + | +
+
+ SMUCMAB
+
+ |
+ + Mucosal absorption, submucosal + | +
+
+ MUC
+
+ |
+ + Topical application, mucous membrane + | +
+
+ NAIL
+
+ |
+ + Topical application, nail + | +
+
+ NASAL
+
+ |
+ + Topical application, nasal + | +
+
+ ETNEB
+
+ |
+ + Nebulization, endotracheal tube + | +
+
+ OPTHALTA
+
+ |
+ + Topical application, ophthalmic + | +
+
+ ORALTA
+
+ |
+ + Topical application, oral + | +
+
+ ORRINSE
+
+ |
+ + Rinse, oral + | +
+
+ PO
+
+ |
+ + Swallow, oral + | +
+
+ GARGLE
+
+ |
+ + Gargle + | +
+
+ ORMUC
+
+ |
+ + Topical application, oromucosal + | +
+
+ SUCK
+
+ |
+ + Suck, oromucosal + | +
+
+ SWISHSPIT
+
+ |
+ + Swish and spit out, oromucosal + | +
+
+ SWISHSWAL
+
+ |
+ + Swish and swallow, oromucosal + | +
+
+ OROPHARTA
+
+ |
+ + Topical application, oropharyngeal + | +
+
+ PERIANAL
+
+ |
+ + Topical application, perianal + | +
+
+ PERINEAL
+
+ |
+ + Topical application, perineal + | +
+
+ PDONTTA
+
+ |
+ + Topical application, periodontal + | +
+
+ RECTAL
+
+ |
+ + Topical application, rectal + | +
+
+ INSUF
+
+ |
+ + Insufflation + | +
+
+ TRNSDERM
+
+ |
+ + Transdermal + | +
+
+ SCALP
+
+ |
+ + Topical application, scalp + | +
+
+ OCDRESTA
+
+ |
+ + Occlusive dressing technique + | +
+
+ SKIN
+
+ |
+ + Topical application, skin + | +
+
+ SUBCONJTA
+
+ |
+ + Subconjunctival + | +
+
+ URETHSUP
+
+ |
+ + Suppository, urethral + | +
+
+ TTYMPTABSORP
+
+ |
+ + Topical absorption, transtympanic + | +
+
+ TMUCTA
+
+ |
+ + Topical application, transmucosal + | +
+
+ VAGINS
+
+ |
+ + Topical application, vaginal + | +
+ container.csv +
+ +
+ You can download the container.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ amp
+
+ |
+ + Ampule + | +
+ Container sealed by fusion and to be opened exclusively by breaking. The contents are intended for use on one occasion only. + + |
+
+
+ bag
+
+ |
+ + Bag + | +
+ Container consisting of surfaces, whether or not with a flat bottom, made of flexible material, generally closed at the bottom and at the sides by sealing; at the top possibly to be closed by fusion of the material, depending on the intended use. Equipped with special attachments. Contains the final preparation in one compartment or the components necessary for its preparation in different compartments. + + |
+
+
+ blstrpk
+
+ |
+ + Blister Pack + | +
+ Container (usually multidose) consisting of two layers of which one is shaped to contain the individual doses. Strips are excluded. + + |
+
+
+ bot
+
+ |
+ + Bottle + | +
+ Container with a more or less pronounced neck and usually a flat bottom. + + |
+
+
+ box
+
+ |
+ + Box + | +
+ Primary container consisting of one or more parts made of a light material, can be closed. + + |
+
+
+ can
+
+ |
+ + Can + | ++ + | +
+
+ cart
+
+ |
+ + Cartridge + | +
+ Filled container, usually cylindrical, containing a sterile, single-dose or multidose, parenteral preparation; it contains the final preparation in one compartment, or the components necessary for its preparation in different compartments. It may be supplied as an integral part of a pre-filled pen or be intended for use in a reusable device especially designed for that purpose, such as a pen. + + |
+
+
+ disk
+
+ |
+ + Disk + | ++ + | +
+
+ doset
+
+ |
+ + Dosette + | ++ + | +
+
+ jar
+
+ |
+ + Jar + | +
+ Container, without a pronounced neck, with a wide opening at the top and a more-or-less flat bottom. It is suited for semi-solid and solid pharmaceutical forms (including those that are stored/supplied in a liquid medium, such as living tissue equivalents). It can be reclosed. + + |
+
+
+ jug
+
+ |
+ + Jug + | ++ + | +
+
+ minim
+
+ |
+ + Minim + | ++ + | +
+
+ nebamp
+
+ |
+ + Nebule Amp + | ++ + | +
+
+ ovul
+
+ |
+ + Ovule + | ++ + | +
+
+ pch
+
+ |
+ + Pouch + | +
+ Item of packaging intended for use as an intermediate or outer container, intended to contain one or more medicinal product(s); it is made of a flexible material and may be for single use or be re-usable, and may be fitted with a closure system. Bags and sachets are excluded. + + |
+
+
+ pkt
+
+ |
+ + Packet + | ++ + | +
+
+ sash
+
+ |
+ + Sashet + | +
+ Container consisting of two surfaces made of flexible material to be closed only by sealing or folding over. The contents are intended for single use. + + |
+
+
+ strip
+
+ |
+ + Strip + | +
+ Multidose container consisting of two layers, usually provided with perforations, suited for containing single doses of solid or semi-solid preparations. Blisters are excluded. + + |
+
+
+ tin
+
+ |
+ + Tin + | ++ + | +
+
+ tub
+
+ |
+ + Tub + | ++ + | +
+
+ tube
+
+ |
+ + Tube + | +
+ Container for semi-solid pharmaceutical forms, usually multidose, consisting of collapsible material intended to release the contents via a nozzle by squeezing the package. + + |
+
+
+ vial
+
+ |
+ + Vial + | +
+ Small container for parenteral medicinal products, with a stopper and overseal; the contents are removed after piercing the stopper. Single-dose and multidose uses are included. + + |
+
+ dosageForm.csv +
+ +
+ You can download the dosageForm.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ APPFUL
+
+ |
+ + Applicatorful + | ++ + | +
+
+ DROP
+
+ |
+ + Drops + | ++ + | +
+
+ PUFF
+
+ |
+ + Puff + | ++ + | +
+
+ SCOOP
+
+ |
+ + Scoops + | ++ + | +
+
+ SPRY
+
+ |
+ + Sprays + | ++ + | +
+
+ GASINHL
+
+ |
+ + Gas for Inhalation + | ++ + | +
+
+ AER
+
+ |
+ + Aerosol + | ++ + | +
+
+ FOAM
+
+ |
+ + Foam + | ++ + | +
+
+ INHL
+
+ |
+ + Inhalant + | ++ + | +
+
+ LIQCLN
+
+ |
+ + Liquid Cleanser + | ++ + | +
+
+ OIL
+
+ |
+ + Oil + | +
+ An unctuous, combustible substance which is liquid, or easily liquefiable, on warming, and is soluble in ether but insoluble in water. Such substances, depending on their origin, are classified as animal, mineral, or vegetable oils. + + |
+
+
+ SOL
+
+ |
+ + Solution + | +
+ A liquid preparation that contains one or more chemical substances dissolved, i.e., molecularly dispersed, in a suitable solvent or mixture of mutually miscible solvents. + + |
+
+
+ CRM
+
+ |
+ + Cream + | +
+ A semisolid dosage form containing one or more drug substances dissolved or dispersed in a suitable base; more recently, the term has been restricted to products consisting of oil-in-water emulsions or aqueous microcrystalline dispersions of long chain fatty acids or alcohols that are water washable and more cosmetically and aesthetically acceptable. + + |
+
+
+ LTN
+
+ |
+ + Lotion + | +
+ The term "lotion" has been used to categorize many topical suspensions, solutions and emulsions intended for application to the skin. + + |
+
+
+ OINT
+
+ |
+ + Ointment + | +
+ A semisolid preparation intended for external application to the skin or mucous membranes. + + |
+
+
+ GEL
+
+ |
+ + Gel + | +
+ A semisolid system consisting of either suspensions made up of small inorganic particles or large organic molecules interpenetrated by a liquid. + + |
+
+
+ PASTE
+
+ |
+ + Paste + | +
+ A semisolid dosage form that contains one or more drug substances intended for topical application. + + |
+
+
+ SUSP
+
+ |
+ + Suspension + | ++ + | +
+
+ BAR
+
+ |
+ + Bar + | ++ + | +
+
+ BEAD
+
+ |
+ + Beads + | +
+ A solid dosage form in the shape of a small ball. + + |
+
+
+ CAKE
+
+ |
+ + Cake + | ++ + | +
+
+ CEMENT
+
+ |
+ + Cement + | +
+ A substance that serves to produce solid union between two surfaces. + + |
+
+
+ CRYS
+
+ |
+ + Crystals + | +
+ A naturally produced angular solid of definite form in which the ultimate units from which it is built up are systematically arranged; they are usually evenly spaced on a regular space lattice. + + |
+
+
+ DISK
+
+ |
+ + Disk + | +
+ A circular plate-like organ or structure. + + |
+
+
+ FLAKE
+
+ |
+ + Flakes + | ++ + | +
+
+ GRAN
+
+ |
+ + Granules + | +
+ A small particle or grain. + + |
+
+
+ GUM
+
+ |
+ + ChewingGum + | +
+ A sweetened and flavored insoluble plastic material of various shapes which when chewed, releases a drug substance into the oral cavity. + + |
+
+
+ PAD
+
+ |
+ + Pad + | ++ + | +
+
+ PATCH
+
+ |
+ + Patch + | +
+ A drug delivery system that contains an adhesived backing and that permits its ingredients to diffuse from some portion of it (e.g., the backing itself, a reservoir, the adhesive, or some other component) into the body from the external site where it is applied. + + |
+
+
+ PELLET
+
+ |
+ + Pellet + | +
+ A small sterile solid mass consisting of a highly purified drug (with or without excipients) made by the formation of granules, or by compression and molding. + + |
+
+
+ PILL
+
+ |
+ + Pill + | +
+ A small, round solid dosage form containing a medicinal agent intended for oral administration. + + |
+
+
+ POWD
+
+ |
+ + Powder + | +
+ An intimate mixture of dry, finely divided drugs and/or chemicals that may be intended for internal or external use. + + |
+
+
+ SUPP
+
+ |
+ + Suppository + | +
+ A solid body of various weights and shapes, adapted for introduction into the rectal, vaginal, or urethral orifice of the human body; they usually melt, soften, or dissolve at body temperature. + + |
+
+
+ SWAB
+
+ |
+ + Swab + | +
+ A wad of absorbent material usually wound around one end of a small stick and used for applying medication or for removing material from an area. + + |
+
+
+ WAFER
+
+ |
+ + Wafer + | +
+ A thin slice of material containing a medicinal agent. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/medicine/master/release-schema.json b/en/extensions/medicine/master/release-schema.json
new file mode 100644
index 000000000..a1323209b
--- /dev/null
+++ b/en/extensions/medicine/master/release-schema.json
@@ -0,0 +1,144 @@
+{
+ "definitions": {
+ "Item": {
+ "properties": {
+ "activeIngredients": {
+ "title": "Active ingredients",
+ "description": "The active ingredients, typically chemical compounds or biological substances.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/ActiveIngredient"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "dosageForm": {
+ "title": "Dosage form",
+ "description": "The dosage form in which the medicine is available, from the dosageForm codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "dosageForm.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "administrationRoute": {
+ "title": "Administration route",
+ "description": "The route by which the medicine can be administered, from the administrationRoute codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "administrationRoute.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "container": {
+ "title": "Container",
+ "description": "The immediate container for the medicine. Also known as: presentation, presentation form, package.",
+ "$ref": "#/definitions/Container"
+ }
+ }
+ },
+ "ActiveIngredient": {
+ "title": "Active ingredient",
+ "description": "An active ingredient, typically a chemical compound or biological substance.",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Name",
+ "description": "The name of the active ingredient. It is recommended to use the lowercase Latin name from the International Nonproprietary Names (INN). Also known as: generic name, drug, substance name, active substance.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "strength": {
+ "title": "Strength",
+ "description": "The strength of the active ingredient. Also known as: concentration, potency.",
+ "$ref": "#/definitions/Quantity"
+ }
+ },
+ "minProperties": 1
+ },
+ "Container": {
+ "title": "Container",
+ "description": "The immediate container for the medicine. Also known as: presentation, presentation form, package.",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Name",
+ "description": "The common name of the container, from the container codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "container.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "capacity": {
+ "title": "Capacity",
+ "description": "The storage capacity of the container.",
+ "$ref": "#/definitions/Quantity"
+ }
+ },
+ "minProperties": 1
+ },
+ "Quantity": {
+ "title": "Quantity",
+ "description": "The quantity of a thing.",
+ "type": "object",
+ "properties": {
+ "unit": {
+ "title": "Unit",
+ "description": "The unit of measurement for the quantity.",
+ "$ref": "#/definitions/SimpleUnit"
+ },
+ "value": {
+ "title": "Value",
+ "description": "The quantity, as a multiple of the unit of measurement. The quantity is expressed in interval notation, for example: \"[10,10]\" for 10 units, \"[1,10]\" for 1 to 10 units, or \"[10,INF[\" for 10 or more units.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "pattern": "^[([\\]][0-9]+,([0-9]+|INF)[)[\\]]$"
+ }
+ },
+ "minProperties": 1
+ },
+ "SimpleUnit": {
+ "title": "Simple unit",
+ "description": "A unit of measurement.",
+ "type": "object",
+ "properties": {
+ "scheme": {
+ "title": "Scheme",
+ "description": "The codelist from which the identifier for the unit of measurement is taken, using the open [unitClassificationScheme](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#unit-classification-scheme) codelist. 'UNCEFACT' is recommended.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "The identifier for the unit of measurement, taken from the codelist referenced by the `scheme` field. Refer to the [unitClassificationScheme](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#unit-classification-scheme) codelist for details of how to find identifiers within schemes.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "versionId": true,
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/medicine/master/schema/index.html b/en/extensions/medicine/master/schema/index.html
new file mode 100644
index 000000000..4b5534a5f
--- /dev/null
+++ b/en/extensions/medicine/master/schema/index.html
@@ -0,0 +1,559 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Medicine +
+ ++ Adds fields to the item object relevant to the procurement of medicines. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds fields to the item object relevant to the procurement of medicines.
+Guidance
+This extension is used to describe medicinal products at the tender, award and/or contract stages. Using this extension, a publisher can specify the medicinal product's active ingredients and their strength, the dosage form, the medicine's container, and the administration route. In doing so, it makes it easier to compare the procurement of medicinal products across jurisdictions, and thereby supports external reference pricing.
+Dosage forms and container sizes differ significantly across countries, which makes comparison difficult. To ease comparison, the extension provides standardized codelists for the dosage form, immediate container and administration route, based on Health Level Seven (HL7), a set of international standards for health data. That said, if you haven't adopted and can't map your values to the HL7 codes, you may use your own codes. To allow a user to interpret your codes, you should describe the codelists, and how to find the definitions of codes, in your publication policy.
+For the names of active ingredients, it is recommended to use International Nonproprietary Names (INN). The World Health Organization (WHO) maintains a cumulative list of all INNs, with equivalent names in Latin, English, French, Spanish, Arabic, Chinese and Russian. To ease comparison, it is recommended to use the lowercase Latin name.
+If a contracting process is in the award or contract stage, it’s possible to know more information about the medicine, such as the brand, the manufacturer, the country of origin, the expiration date, if they must maintain a cold chain and all the other commercial, financial and logistical conditions. Use the generic item attributes extension for all the cases where the medicine item has other attributes not included in this extension.
+If a medicine item has more than one active ingredient, add each one to the activeIngredients array.
Examples
+One active ingredient
+In this example, we demonstrate how to use this extension to describe a drug procurement process from Chile. (You can view its original OCDS data.)
+Item 3 is described as:
+| Description | +Minimum dispensing unit | +
|---|---|
| Acetilcisteina | +ACETILCISTEINA-N 100 MG/ML SOLUCION PARA NEBULIZAR FRASCO 15-30 ML ENVASE INDIVIDUAL RESISTENTE CON SELLO QUE ASEGURE INVIOLABILIDAD DEL CONTENIDO | +
The strength is expressed as "100 MG/ML". The UN/CEFACT Recommendation 20 – Codes for Units of Measure Used in International Trade codelist includes units like mg/l, g/l and kg/l, but not mg/ml. So, "100 MG/ML" is expressed as 100 g/l below.
+Based on this information, we can add the dosageForm, administrationRoute, container and activeIngredients.
{
+ "tender": {
+ "items": [
+ {
+ "id": "1",
+ "description": "Acetilcisteina",
+ "classification": {
+ "id": "51161701",
+ "scheme": "UNSPSC",
+ "uri": "https://apis.mercadopublico.cl/OCDS/data/productos/categoria/51161701"
+ },
+ "dosageForm": "SOL",
+ "administrationRoute": "NASINHL",
+ "container": {
+ "name": "vial",
+ "capacity": {
+ "unit": {
+ "scheme": "UNCEFACT",
+ "id": "ml"
+ },
+ "value": "[15,30]"
+ }
+ },
+ "activeIngredients": [
+ {
+ "name": "acetylcysteinum",
+ "strength": {
+ "unit": {
+ "scheme": "UNCEFACT",
+ "id": "g/l"
+ },
+ "value": 100
+ }
+ }
+ ]
+ }
+ ]
+ }
+}
+More than one active ingredient
+In this example, we demonstrate how to use this extension to describe a drug procurement process from Paraguay. (You can view its original OCDS data.)
+In the "Suministros requeridos - especificaciones técnicas" tab, item 1 of lot 8 ("LOTE N° 8 - ANESTESICOS LOCALES - 2") is described as:
+| Description | +Technical specifications | +Unit of measurement | +Presentation | +Delivery presentation | +
|---|---|---|---|---|
| Clorhidrato de Bupivacaina Hiperbarica Inyectable | +clorhidrato de bupivacaina 25 mg. + dextrosa 82,5 mg. - solución inyectable | +UNIDAD | +AMPOLLA | +ampollas como minimo de 5 ml. | +
For the name of the active ingredient, Annex 2 of the INN Stem Book 2018, describes how to name acid salts: in this case, "bupivacainum hydrochloridum".
+Based on this information, we can add the dosageForm, administrationRoute, container and activeIngredients.
{
+ "tender": {
+ "items": [
+ {
+ "id": "1",
+ "dosageForm": "SOL",
+ "administrationRoute": "ISINJ",
+ "container": {
+ "name": "amp",
+ "capacity": {
+ "unit": {
+ "scheme": "UNCEFACT",
+ "id": "ml"
+ },
+ "value": "[5,INF["
+ }
+ },
+ "activeIngredients": [
+ {
+ "name": "bupivacainum hydrochloridum",
+ "strength": {
+ "unit": {
+ "scheme": "UNCEFACT",
+ "id": "mg"
+ },
+ "value": 25
+ }
+ },
+ {
+ "name": "dextrosa",
+ "strength": {
+ "unit": {
+ "scheme": "UNCEFACT",
+ "id": "mg"
+ },
+ "value": 82.5
+ }
+ }
+ ],
+ "quantity": 25
+ }
+ ]
+ }
+}
+Related standards
+The fields, definitions and codelists used in this extension are based on the following standards that are commonly used in the data on public medicine purchases.
+-
+
- Most of the fields are based on the Drug definition by the Schema.org Community Group and the Medication Resource from Fast Healthcare Interoperability Resources (FHIR) standard. +
- The
administrationRoutecodelist contains the top-level concepts in HL7's Route of Administration codelist, excluding any synonymous terms.
+ - The
dosageFormcodelist contains the top-level concepts in HL7's Orderable Drug Form codelist, excluding the specific forms of sprays.
+ - The
containercodelist is a copy of the codes and titles from FHIR's Medication Knowledge Package Type codelist. Given that the terms are undefined in FHIR, the descriptions are copied from corresponding terms from the EDQM Standard Terms database, reproduced with the permission of the European Directorate for the Quality of Medicines & HealthCare, Council of Europe (EDQM). The EDQM Standard Terms database is not a static list and content can change over time; the descriptions were retrieved on July 21, 2021.
+
Background
+This extension is based on research with 4 data users and 6 data publishers including public organizations, journalists, medicine price analysts, and software developers for medicine purchase systems from 9 countries in Latin America, Europe, and Africa. The extension includes the most used fields from the different countries.
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/metrics/1.1/README.md b/en/extensions/metrics/1.1/README.md
new file mode 100644
index 000000000..7904ff3b0
--- /dev/null
+++ b/en/extensions/metrics/1.1/README.md
@@ -0,0 +1,141 @@
+# Metrics Extension
+
+The metrics extension provides a common building block for reporting structured performance information on contracts.
+
+Metrics are structured like an [OLAP data cube](https://en.wikipedia.org/wiki/OLAP_cube) with each instance of `Metric` representing a single **observation**, categorized by a number of **dimensions**.
+
+The metrics extension can be used at:
+
+- The `planning` stage for forecasts for the contracting process (e.g. forecast demand levels)
+- The `tender` stage for targets for the contracting process (e.g. target availability levels or KPIs)
+- The `awards` and `contracts` stages for targets agreed with the successful supplier (e.g. availability levels or KPIs)
+- The `implementation` stage for actual performance information (e.g. actual demand, availability, KPIs etc.)
+
+Where the metrics extension is used to model targets for a contracting process, the `description` field can be used to indicate whether the target is a minimum or recommended target.
+
+## Example
+
+### Forecasts
+
+```json
+{
+ "planning": {
+ "forecasts": [
+ {
+ "id": "annualDemand",
+ "title": "Annual Demand",
+ "description": "The annual demand",
+ "observations": [
+ {
+ "id": "1",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 10000,
+ "dimensions": {
+ "vehicleType": "Car"
+ }
+ },
+ {
+ "id": "2",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 1000,
+ "dimensions": {
+ "vehicleType": "Trucks"
+ },
+ "notes": "Simple note"
+ }
+ ]
+ }
+ ]
+ }
+}
+```
+
+### Physical progress
+
+The metrics extension can also be used to report on the physical progress of a contract. The following JSON snippet shows how the metrics extension could be used to report on progress for the construction of a highway, both by percent completion and number of kilometres constructed:
+
+```json
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "implementation": {
+ "metrics": [
+ {
+ "id": "completionPercent",
+ "title": "Construction progress (percent)",
+ "description": "Percent completion of the construction of example highway",
+ "observations": [
+ {
+ "id": "completionPercent-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "25",
+ "unit": {
+ "name": "percent",
+ "id": "P1",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ },
+ {
+ "id": "completionKilometres",
+ "title": "Construction progress (kilometres)",
+ "description": "Progress of construction of example highway measured in kilometres",
+ "observations": [
+ {
+ "id": "completionKilometres-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "15",
+ "unit": {
+ "name": "kilometre",
+ "id": "KMT",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+```
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### 2020-04-24
+
+- Add `minProperties`, `minItems` and/or `minLength` properties.
+
+### 2019-03-20
+
+- Set `"uniqueItems": true` on array fields, and add `"minLength": 1` on required string fields.
+- Make `Observation.unit` non-nullable, like `Item.unit`.
+- Make `Observation.dimensions` non-nullable (undo earlier change).
+
+### 2018-05-08
+
+- Make `Metric.id` and `Observation.id` required to support revision tracking and [list merging](http://standard.open-contracting.org/latest/en/schema/merging/#lists)
+
+### 2018-05-01
+
+- Add title and description to `Observation.period` and `Observation.value`.
+- Make `Observation.dimensions` nullable.
diff --git a/en/extensions/metrics/1.1/extension.json b/en/extensions/metrics/1.1/extension.json
new file mode 100644
index 000000000..56af39e2c
--- /dev/null
+++ b/en/extensions/metrics/1.1/extension.json
@@ -0,0 +1,23 @@
+{
+ "name": {
+ "en": "Metrics",
+ "es": "M\u00e9trica"
+ },
+ "description": {
+ "en": "The metrics extension supports publication of forecasts (planning stage), targets (tender stage), agreed performance targets (award and contract stage) and results (implementation stage).",
+ "es": "La extensi\u00f3n de m\u00e9tricas admite la publicaci\u00f3n de pron\u00f3sticos (etapa de planificaci\u00f3n), objetivos (etapa de licitaci\u00f3n), objetivos de desempe\u00f1o acordados (etapa de adjudicaci\u00f3n y contrato) y resultados (etapa de implementaci\u00f3n)."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/metrics/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/metrics/1.1/index.html b/en/extensions/metrics/1.1/index.html
new file mode 100644
index 000000000..1c65db51d
--- /dev/null
+++ b/en/extensions/metrics/1.1/index.html
@@ -0,0 +1,408 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Medicine +
+ ++ Adds fields to the item object relevant to the procurement of medicines. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ activeIngredients
+
+ |
+ + Active ingredients + | +
+ The active ingredients, typically chemical compounds or biological substances. + + |
+ + array of ActiveIngredient objects + | +
+
+ dosageForm
+
+ |
+ + Dosage form + | +
+ The dosage form in which the medicine is available, from the dosageForm codelist. + + |
+ + string from open dosageForm codelist + | +
+
+ administrationRoute
+
+ |
+ + Administration route + | +
+ The route by which the medicine can be administered, from the administrationRoute codelist. + + |
+ + string from open administrationRoute codelist + | +
+
+ container
+
+ |
+ + Container + | +
+ The immediate container for the medicine. Also known as: presentation, presentation form, package. + + |
+ + Container object + | +
+ ActiveIngredient +
+ +
+ The extension defines a new ActiveIngredient object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ name
+
+ |
+ + Name + | +
+ The name of the active ingredient. It is recommended to use the lowercase Latin name from the International Nonproprietary Names (INN). Also known as: generic name, drug, substance name, active substance. + + |
+ + string + | +
+
+ strength
+
+ |
+ + Strength + | +
+ The strength of the active ingredient. Also known as: concentration, potency. + + |
+ + Quantity object + | +
+ Container +
+ +
+ The extension defines a new Container object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ name
+
+ |
+ + Name + | +
+ The common name of the container, from the container codelist. + + |
+ + string from open container codelist + | +
+
+ capacity
+
+ |
+ + Capacity + | +
+ The storage capacity of the container. + + |
+ + Quantity object + | +
+ Quantity +
+ +
+ The extension defines a new Quantity object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ unit
+
+ |
+ + Unit + | +
+ The unit of measurement for the quantity. + + |
+ + SimpleUnit object + | +
+
+ value
+
+ |
+ + Value + | +
+ The quantity, as a multiple of the unit of measurement. The quantity is expressed in interval notation, for example: "[10,10]" for 10 units, "[1,10]" for 1 to 10 units, or "[10,INF[" for 10 or more units. + + |
+ + string or number + | +
+ SimpleUnit +
+ +
+ The extension defines a new SimpleUnit object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ scheme
+
+ |
+ + Scheme + | +
+ The codelist from which the identifier for the unit of measurement is taken, using the open unitClassificationScheme codelist. 'UNCEFACT' is recommended. + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ id
+
+ |
+ + ID + | +
+ The identifier for the unit of measurement, taken from the codelist referenced by the |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/metrics/1.1/release-schema.json b/en/extensions/metrics/1.1/release-schema.json
new file mode 100644
index 000000000..e160ad97b
--- /dev/null
+++ b/en/extensions/metrics/1.1/release-schema.json
@@ -0,0 +1,269 @@
+{
+ "definitions": {
+ "Planning": {
+ "properties": {
+ "forecasts": {
+ "title": "Forecasts",
+ "description": "Any forecasts metrics for this results of this contracting process.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "targets": {
+ "title": "Targets",
+ "description": "Any target metrics for this results of this contracting process.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "agreedMetrics": {
+ "title": "Agreed metrics",
+ "description": "Any target metrics set out as part of the contract award.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "agreedMetrics": {
+ "title": "Agreed metrics",
+ "description": "Any target metrics set out as part of the contract documents.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Implementation": {
+ "properties": {
+ "metrics": {
+ "title": "Metrics",
+ "description": "Reported results from the delivery of the contracted goods, works or services.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Metric": {
+ "title": "Metric",
+ "description": "Metrics are used to set out targets and results from a contracting process. During the planning and tender sections, a metric indicates the anticipated results. In award and contract sections it indicates the awarded/contracted results. In the implementation section it is used to provide updates on actually delivered results, also known as outputs.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "An identifier for this metric. In some cases this may be drawn from a codelist of metrics required for this type of contracting process, or in other instances may be an arbitrary identifier.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "Title",
+ "description": "The title of this metric",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "A short description of the metric. This may include short details of measurement methods.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "observations": {
+ "title": "Observations",
+ "description": "An array of target or actual values for this metric.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Observation"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "metrics",
+ "version": "1.1"
+ }
+ },
+ "Observation": {
+ "title": "Observation",
+ "description": "An actual or target observation. Observations should include either a value (for financial metrics) or measure (for other metrics).",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "A local identifier for this specific observation. This may be an arbitrary identifier, or could be a composite of the metric identifier, and the date and other dimensions of this observation.",
+ "type": "string",
+ "minLength": 1
+ },
+ "period": {
+ "title": "Period",
+ "description": "The period over which this observation is measured.",
+ "$ref": "#/definitions/Period"
+ },
+ "value": {
+ "title": "Value",
+ "description": "For financial metrics, the value of this forecast, target or actual observation.",
+ "$ref": "#/definitions/Value"
+ },
+ "measure": {
+ "title": "Measure",
+ "description": "For non-financial metrics, the measure of this forecast, target or actual observation. Measures may be provided as free text or numerical values.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "unit": {
+ "title": "Unit",
+ "description": "Unit",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Unit name",
+ "description": "The name of the unit.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "scheme": {
+ "title": "Scheme",
+ "description": "The list from which units of measure identifiers are taken. Use of the scheme 'UNCEFACT' for the UN/CEFACT Recommendation 20 list of \"Codes for Units of Measure Used in International Trade\" is recommended.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "The identifier from the codelist referenced in the scheme field. For example, with UNCEFACT, this is the value of the 'Common Code' column. From this identifier, applications can look-up the human readable name or symbol for this unit of measure.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "uri": {
+ "title": "URI",
+ "description": "If the scheme used provide a machine-readable URI for this unit of measure, this can be given.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ },
+ "minProperties": 1
+ },
+ "dimensions": {
+ "title": "Dimensions",
+ "description": "Any number of dimensions can be recorded within this object. Dimensions names should follow the camelCase conventions of OCDS.",
+ "type": "object",
+ "patternProperties": {
+ "^.*": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "notes": {
+ "title": "Notes",
+ "description": "Any notes on this observation. This may include clarifying information.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "relatedImplementationMilestone": {
+ "title": "Related implementation milestone",
+ "description": "A link to the milestone in the implementation section of OCDS to which this forecast, target or actual observation relates.",
+ "$ref": "#/definitions/MilestoneReference"
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "metrics",
+ "version": "1.1"
+ }
+ },
+ "MilestoneReference": {
+ "title": "Milestone Reference",
+ "description": "A block used to reference a milestone, including the ID and title of the milestone being referenced.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Milestone ID",
+ "description": "The ID of the milestone being referenced, this must match the ID of a milestone described elsewhere in a release about this contracting process.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "Milestone title",
+ "description": "The title of the milestone being referenced, this must match the title of a milestone described elsewhere in a release about this contracting process.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "metrics",
+ "version": "1.1"
+ }
+ }
+ }
+}
diff --git a/en/extensions/metrics/1.1/schema/index.html b/en/extensions/metrics/1.1/schema/index.html
new file mode 100644
index 000000000..3d1c8bf1a
--- /dev/null
+++ b/en/extensions/metrics/1.1/schema/index.html
@@ -0,0 +1,864 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Metrics +
+ ++ The metrics extension supports publication of forecasts (planning stage), targets (tender stage), agreed performance targets (award and contract stage) and results (implementation stage). +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The metrics extension provides a common building block for reporting structured performance information on contracts.
+Metrics are structured like an OLAP data cube with each instance of Metric representing a single observation, categorized by a number of dimensions.
The metrics extension can be used at:
+-
+
- The
planningstage for forecasts for the contracting process (e.g. forecast demand levels)
+ - The
tenderstage for targets for the contracting process (e.g. target availability levels or KPIs)
+ - The
awardsandcontractsstages for targets agreed with the successful supplier (e.g. availability levels or KPIs)
+ - The
implementationstage for actual performance information (e.g. actual demand, availability, KPIs etc.)
+
Where the metrics extension is used to model targets for a contracting process, the description field can be used to indicate whether the target is a minimum or recommended target.
Example
+Forecasts
+{
+ "planning": {
+ "forecasts": [
+ {
+ "id": "annualDemand",
+ "title": "Annual Demand",
+ "description": "The annual demand",
+ "observations": [
+ {
+ "id": "1",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 10000,
+ "dimensions": {
+ "vehicleType": "Car"
+ }
+ },
+ {
+ "id": "2",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 1000,
+ "dimensions": {
+ "vehicleType": "Trucks"
+ },
+ "notes": "Simple note"
+ }
+ ]
+ }
+ ]
+ }
+}
+Physical progress
+The metrics extension can also be used to report on the physical progress of a contract. The following JSON snippet shows how the metrics extension could be used to report on progress for the construction of a highway, both by percent completion and number of kilometres constructed:
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "implementation": {
+ "metrics": [
+ {
+ "id": "completionPercent",
+ "title": "Construction progress (percent)",
+ "description": "Percent completion of the construction of example highway",
+ "observations": [
+ {
+ "id": "completionPercent-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "25",
+ "unit": {
+ "name": "percent",
+ "id": "P1",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ },
+ {
+ "id": "completionKilometres",
+ "title": "Construction progress (kilometres)",
+ "description": "Progress of construction of example highway measured in kilometres",
+ "observations": [
+ {
+ "id": "completionKilometres-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "15",
+ "unit": {
+ "name": "kilometre",
+ "id": "KMT",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2019-03-20
+-
+
- Set
"uniqueItems": trueon array fields, and add"minLength": 1on required string fields.
+ - Make
Observation.unitnon-nullable, likeItem.unit.
+ - Make
Observation.dimensionsnon-nullable (undo earlier change).
+
2018-05-08
+-
+
- Make
Metric.idandObservation.idrequired to support revision tracking and list merging
+
2018-05-01
+-
+
- Add title and description to
Observation.periodandObservation.value.
+ - Make
Observation.dimensionsnullable.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/metrics/index.html b/en/extensions/metrics/index.html
new file mode 100644
index 000000000..40c8c68ee
--- /dev/null
+++ b/en/extensions/metrics/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Metrics +
+ ++ The metrics extension supports publication of forecasts (planning stage), targets (tender stage), agreed performance targets (award and contract stage) and results (implementation stage). +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Planning +
+ +
+ The extension defines these fields in the Planning object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ forecasts
+
+ |
+ + Forecasts + | +
+ Any forecasts metrics for this results of this contracting process. + + |
+ + array of Metric objects + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ targets
+
+ |
+ + Targets + | +
+ Any target metrics for this results of this contracting process. + + |
+ + array of Metric objects + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Agreed metrics + | +
+ Any target metrics set out as part of the contract award. + + |
+ + array of Metric objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Agreed metrics + | +
+ Any target metrics set out as part of the contract documents. + + |
+ + array of Metric objects + | +
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ metrics
+
+ |
+ + Metrics + | +
+ Reported results from the delivery of the contracted goods, works or services. + + |
+ + array of Metric objects + | +
+ Metric +
+ +
+ The extension defines a new Metric object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ An identifier for this metric. In some cases this may be drawn from a codelist of metrics required for this type of contracting process, or in other instances may be an arbitrary identifier. + + |
+ + string + | +
+
+ title
+
+ |
+ + Title + | +
+ The title of this metric + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A short description of the metric. This may include short details of measurement methods. + + |
+ + string + | +
+
+ observations
+
+ |
+ + Observations + | +
+ An array of target or actual values for this metric. + + |
+ + array of Observation objects + | +
+ Observation +
+ +
+ The extension defines a new Observation object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ A local identifier for this specific observation. This may be an arbitrary identifier, or could be a composite of the metric identifier, and the date and other dimensions of this observation. + + |
+ + string + | +
+
+ period
+
+ |
+ + Period + | +
+ The period over which this observation is measured. + + |
+ + Period object + | +
+
+ value
+
+ |
+ + Value + | +
+ For financial metrics, the value of this forecast, target or actual observation. + + |
+ + Value object + | +
+
+ measure
+
+ |
+ + Measure + | +
+ For non-financial metrics, the measure of this forecast, target or actual observation. Measures may be provided as free text or numerical values. + + |
+ + string or number + | +
+
+ unit
+
+ |
+ + Unit + | +
+ Unit + + |
+ + object + | +
+
+ unit.
+ |
+ + Unit name + | +
+ The name of the unit. + + |
+ + string + | +
+
+ unit.
+ |
+ + Scheme + | +
+ The list from which units of measure identifiers are taken. Use of the scheme 'UNCEFACT' for the UN/CEFACT Recommendation 20 list of "Codes for Units of Measure Used in International Trade" is recommended. + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ unit.
+ |
+ + ID + | +
+ The identifier from the codelist referenced in the scheme field. For example, with UNCEFACT, this is the value of the 'Common Code' column. From this identifier, applications can look-up the human readable name or symbol for this unit of measure. + + |
+ + string + | +
+
+ unit.
+ |
+ + URI + | +
+ If the scheme used provide a machine-readable URI for this unit of measure, this can be given. + + |
+ + string + | +
+
+ dimensions
+
+ |
+ + Dimensions + | +
+ Any number of dimensions can be recorded within this object. Dimensions names should follow the camelCase conventions of OCDS. + + |
+ + object + | +
+
+ dimensions.
+ |
+ + + | ++ + | ++ string + | +
+
+ notes
+
+ |
+ + Notes + | +
+ Any notes on this observation. This may include clarifying information. + + |
+ + string + | +
+
+ relatedImplementationMilestone
+
+ |
+ + Related implementation milestone + | +
+ A link to the milestone in the implementation section of OCDS to which this forecast, target or actual observation relates. + + |
+ + MilestoneReference object + | +
+ MilestoneReference +
+ +
+ The extension defines a new MilestoneReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Milestone ID + | +
+ The ID of the milestone being referenced, this must match the ID of a milestone described elsewhere in a release about this contracting process. + + |
+ + string + | +
+
+ title
+
+ |
+ + Milestone title + | +
+ The title of the milestone being referenced, this must match the title of a milestone described elsewhere in a release about this contracting process. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/metrics/1.1/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/metrics/master/release-schema.json b/en/extensions/metrics/master/release-schema.json
new file mode 100644
index 000000000..e160ad97b
--- /dev/null
+++ b/en/extensions/metrics/master/release-schema.json
@@ -0,0 +1,269 @@
+{
+ "definitions": {
+ "Planning": {
+ "properties": {
+ "forecasts": {
+ "title": "Forecasts",
+ "description": "Any forecasts metrics for this results of this contracting process.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "targets": {
+ "title": "Targets",
+ "description": "Any target metrics for this results of this contracting process.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "agreedMetrics": {
+ "title": "Agreed metrics",
+ "description": "Any target metrics set out as part of the contract award.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "agreedMetrics": {
+ "title": "Agreed metrics",
+ "description": "Any target metrics set out as part of the contract documents.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Implementation": {
+ "properties": {
+ "metrics": {
+ "title": "Metrics",
+ "description": "Reported results from the delivery of the contracted goods, works or services.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Metric": {
+ "title": "Metric",
+ "description": "Metrics are used to set out targets and results from a contracting process. During the planning and tender sections, a metric indicates the anticipated results. In award and contract sections it indicates the awarded/contracted results. In the implementation section it is used to provide updates on actually delivered results, also known as outputs.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "An identifier for this metric. In some cases this may be drawn from a codelist of metrics required for this type of contracting process, or in other instances may be an arbitrary identifier.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "Title",
+ "description": "The title of this metric",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "A short description of the metric. This may include short details of measurement methods.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "observations": {
+ "title": "Observations",
+ "description": "An array of target or actual values for this metric.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Observation"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "metrics",
+ "version": "1.1"
+ }
+ },
+ "Observation": {
+ "title": "Observation",
+ "description": "An actual or target observation. Observations should include either a value (for financial metrics) or measure (for other metrics).",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "A local identifier for this specific observation. This may be an arbitrary identifier, or could be a composite of the metric identifier, and the date and other dimensions of this observation.",
+ "type": "string",
+ "minLength": 1
+ },
+ "period": {
+ "title": "Period",
+ "description": "The period over which this observation is measured.",
+ "$ref": "#/definitions/Period"
+ },
+ "value": {
+ "title": "Value",
+ "description": "For financial metrics, the value of this forecast, target or actual observation.",
+ "$ref": "#/definitions/Value"
+ },
+ "measure": {
+ "title": "Measure",
+ "description": "For non-financial metrics, the measure of this forecast, target or actual observation. Measures may be provided as free text or numerical values.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "unit": {
+ "title": "Unit",
+ "description": "Unit",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Unit name",
+ "description": "The name of the unit.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "scheme": {
+ "title": "Scheme",
+ "description": "The list from which units of measure identifiers are taken. Use of the scheme 'UNCEFACT' for the UN/CEFACT Recommendation 20 list of \"Codes for Units of Measure Used in International Trade\" is recommended.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "The identifier from the codelist referenced in the scheme field. For example, with UNCEFACT, this is the value of the 'Common Code' column. From this identifier, applications can look-up the human readable name or symbol for this unit of measure.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "uri": {
+ "title": "URI",
+ "description": "If the scheme used provide a machine-readable URI for this unit of measure, this can be given.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ },
+ "minProperties": 1
+ },
+ "dimensions": {
+ "title": "Dimensions",
+ "description": "Any number of dimensions can be recorded within this object. Dimensions names should follow the camelCase conventions of OCDS.",
+ "type": "object",
+ "patternProperties": {
+ "^.*": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "notes": {
+ "title": "Notes",
+ "description": "Any notes on this observation. This may include clarifying information.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "relatedImplementationMilestone": {
+ "title": "Related implementation milestone",
+ "description": "A link to the milestone in the implementation section of OCDS to which this forecast, target or actual observation relates.",
+ "$ref": "#/definitions/MilestoneReference"
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "metrics",
+ "version": "1.1"
+ }
+ },
+ "MilestoneReference": {
+ "title": "Milestone Reference",
+ "description": "A block used to reference a milestone, including the ID and title of the milestone being referenced.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Milestone ID",
+ "description": "The ID of the milestone being referenced, this must match the ID of a milestone described elsewhere in a release about this contracting process.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "Milestone title",
+ "description": "The title of the milestone being referenced, this must match the title of a milestone described elsewhere in a release about this contracting process.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1,
+ "extension_explorer:source": {
+ "identifier": "metrics",
+ "version": "1.1"
+ }
+ }
+ }
+}
diff --git a/en/extensions/metrics/master/schema/index.html b/en/extensions/metrics/master/schema/index.html
new file mode 100644
index 000000000..3ca5b34f2
--- /dev/null
+++ b/en/extensions/metrics/master/schema/index.html
@@ -0,0 +1,865 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Metrics +
+ ++ The metrics extension supports publication of forecasts (planning stage), targets (tender stage), agreed performance targets (award and contract stage) and results (implementation stage). +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The metrics extension provides a common building block for reporting structured performance information on contracts.
+Metrics are structured like an OLAP data cube with each instance of Metric representing a single observation, categorized by a number of dimensions.
The metrics extension can be used at:
+-
+
- The
planningstage for forecasts for the contracting process (e.g. forecast demand levels)
+ - The
tenderstage for targets for the contracting process (e.g. target availability levels or KPIs)
+ - The
awardsandcontractsstages for targets agreed with the successful supplier (e.g. availability levels or KPIs)
+ - The
implementationstage for actual performance information (e.g. actual demand, availability, KPIs etc.)
+
Where the metrics extension is used to model targets for a contracting process, the description field can be used to indicate whether the target is a minimum or recommended target.
Example
+Forecasts
+{
+ "planning": {
+ "forecasts": [
+ {
+ "id": "annualDemand",
+ "title": "Annual Demand",
+ "description": "The annual demand",
+ "observations": [
+ {
+ "id": "1",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 10000,
+ "dimensions": {
+ "vehicleType": "Car"
+ }
+ },
+ {
+ "id": "2",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 1000,
+ "dimensions": {
+ "vehicleType": "Trucks"
+ },
+ "notes": "Simple note"
+ }
+ ]
+ }
+ ]
+ }
+}
+Physical progress
+The metrics extension can also be used to report on the physical progress of a contract. The following JSON snippet shows how the metrics extension could be used to report on progress for the construction of a highway, both by percent completion and number of kilometres constructed:
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "implementation": {
+ "metrics": [
+ {
+ "id": "completionPercent",
+ "title": "Construction progress (percent)",
+ "description": "Percent completion of the construction of example highway",
+ "observations": [
+ {
+ "id": "completionPercent-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "25",
+ "unit": {
+ "name": "percent",
+ "id": "P1",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ },
+ {
+ "id": "completionKilometres",
+ "title": "Construction progress (kilometres)",
+ "description": "Progress of construction of example highway measured in kilometres",
+ "observations": [
+ {
+ "id": "completionKilometres-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "15",
+ "unit": {
+ "name": "kilometre",
+ "id": "KMT",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2019-03-20
+-
+
- Set
"uniqueItems": trueon array fields, and add"minLength": 1on required string fields.
+ - Make
Observation.unitnon-nullable, likeItem.unit.
+ - Make
Observation.dimensionsnon-nullable (undo earlier change).
+
2018-05-08
+-
+
- Make
Metric.idandObservation.idrequired to support revision tracking and list merging
+
2018-05-01
+-
+
- Add title and description to
Observation.periodandObservation.value.
+ - Make
Observation.dimensionsnullable.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/metrics/v1.1/README.md b/en/extensions/metrics/v1.1/README.md
new file mode 100644
index 000000000..ed31873b4
--- /dev/null
+++ b/en/extensions/metrics/v1.1/README.md
@@ -0,0 +1,57 @@
+# Metrics Extension
+
+The metrics extension provides a common building block for reporting structured performance information on contracts.
+
+Metrics are structured like an [OLAP data cube](https://en.wikipedia.org/wiki/OLAP_cube) with each instance of `Metric` representing a single **observation**, categorised by a number of **dimensions**.
+
+```json
+{
+ "metrics":[
+ {
+ "id":"annualDemand",
+ "title":"Annual Demand",
+ "description":"The annual demand",
+ "observations":[
+ {
+ "period":{
+ "startDate":"2015-01-01T00:00:00Z",
+ "endDate":"2015-12-31T23:59:59Z"
+ },
+ "quantity":"10000",
+ "dimensions":{
+ "vehicleType":"Car"
+ }
+ },
+ {
+ "period":{
+ "startDate":"2015-01-01T00:00:00Z",
+ "endDate":"2015-12-31T23:59:59Z"
+ },
+ "quantity":"1000",
+ "dimensions":{
+ "vehicleType":"Trucks"
+ },
+ "note":"Simple note"
+ }
+ ]
+ },
+ {
+
+ }
+ ]
+}
+```
+
+## Use with requirements
+
+Metrics can be used along with the **requirements extension** which will add a 'relatedRequirementID' property to metrics.
+
+With the requirements extension, bids, awards and contracts can include a `requirementResponse` indicating the values against each metric that a supplier intends to meet.
+
+This can allow a degree of comparison between performance anticipated at bid, award, contract and implementation phases.
+
+## To Do
+
+- \[ \] Check oneOf schema syntax for value **or** quantity
+- \[ \] Add relatedRequirementID to requirements extension
+- \[ \] Validate schema updates
diff --git a/en/extensions/metrics/v1.1/extension.json b/en/extensions/metrics/v1.1/extension.json
new file mode 100644
index 000000000..0813d55bb
--- /dev/null
+++ b/en/extensions/metrics/v1.1/extension.json
@@ -0,0 +1,15 @@
+{
+ "name": {
+ "en": "Metrics",
+ "es": "M\u00e9trica"
+ },
+ "description": {
+ "en": "The metrics extension supports publication of forecasts (planning stage), targets (tender stage), agreed performance targets (award and contract stage) and results (implementation stage).",
+ "es": "La extensi\u00f3n de m\u00e9tricas admite la publicaci\u00f3n de pron\u00f3sticos (etapa de planificaci\u00f3n), objetivos (etapa de licitaci\u00f3n), objetivos de desempe\u00f1o acordados (etapa de adjudicaci\u00f3n y contrato) y resultados (etapa de implementaci\u00f3n)."
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "dependencies": [],
+ "documentationUrl": {}
+}
diff --git a/en/extensions/metrics/v1.1/index.html b/en/extensions/metrics/v1.1/index.html
new file mode 100644
index 000000000..8f4a4ca0d
--- /dev/null
+++ b/en/extensions/metrics/v1.1/index.html
@@ -0,0 +1,315 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Metrics +
+ ++ The metrics extension supports publication of forecasts (planning stage), targets (tender stage), agreed performance targets (award and contract stage) and results (implementation stage). +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Planning +
+ +
+ The extension defines these fields in the Planning object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ forecasts
+
+ |
+ + Forecasts + | +
+ Any forecasts metrics for this results of this contracting process. + + |
+ + array of Metric objects + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ targets
+
+ |
+ + Targets + | +
+ Any target metrics for this results of this contracting process. + + |
+ + array of Metric objects + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Agreed metrics + | +
+ Any target metrics set out as part of the contract award. + + |
+ + array of Metric objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Agreed metrics + | +
+ Any target metrics set out as part of the contract documents. + + |
+ + array of Metric objects + | +
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ metrics
+
+ |
+ + Metrics + | +
+ Reported results from the delivery of the contracted goods, works or services. + + |
+ + array of Metric objects + | +
+ Metric +
+ +
+ The extension defines a new Metric object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ An identifier for this metric. In some cases this may be drawn from a codelist of metrics required for this type of contracting process, or in other instances may be an arbitrary identifier. + + |
+ + string + | +
+
+ title
+
+ |
+ + Title + | +
+ The title of this metric + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A short description of the metric. This may include short details of measurement methods. + + |
+ + string + | +
+
+ observations
+
+ |
+ + Observations + | +
+ An array of target or actual values for this metric. + + |
+ + array of Observation objects + | +
+ Observation +
+ +
+ The extension defines a new Observation object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ A local identifier for this specific observation. This may be an arbitrary identifier, or could be a composite of the metric identifier, and the date and other dimensions of this observation. + + |
+ + string + | +
+
+ period
+
+ |
+ + Period + | +
+ The period over which this observation is measured. + + |
+ + Period object + | +
+
+ value
+
+ |
+ + Value + | +
+ For financial metrics, the value of this forecast, target or actual observation. + + |
+ + Value object + | +
+
+ measure
+
+ |
+ + Measure + | +
+ For non-financial metrics, the measure of this forecast, target or actual observation. Measures may be provided as free text or numerical values. + + |
+ + string or number + | +
+
+ unit
+
+ |
+ + Unit + | +
+ Unit + + |
+ + object + | +
+
+ unit.
+ |
+ + Unit name + | +
+ The name of the unit. + + |
+ + string + | +
+
+ unit.
+ |
+ + Scheme + | +
+ The list from which units of measure identifiers are taken. Use of the scheme 'UNCEFACT' for the UN/CEFACT Recommendation 20 list of "Codes for Units of Measure Used in International Trade" is recommended. + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ unit.
+ |
+ + ID + | +
+ The identifier from the codelist referenced in the scheme field. For example, with UNCEFACT, this is the value of the 'Common Code' column. From this identifier, applications can look-up the human readable name or symbol for this unit of measure. + + |
+ + string + | +
+
+ unit.
+ |
+ + URI + | +
+ If the scheme used provide a machine-readable URI for this unit of measure, this can be given. + + |
+ + string + | +
+
+ dimensions
+
+ |
+ + Dimensions + | +
+ Any number of dimensions can be recorded within this object. Dimensions names should follow the camelCase conventions of OCDS. + + |
+ + object + | +
+
+ dimensions.
+ |
+ + + | ++ + | ++ string + | +
+
+ notes
+
+ |
+ + Notes + | +
+ Any notes on this observation. This may include clarifying information. + + |
+ + string + | +
+
+ relatedImplementationMilestone
+
+ |
+ + Related implementation milestone + | +
+ A link to the milestone in the implementation section of OCDS to which this forecast, target or actual observation relates. + + |
+ + MilestoneReference object + | +
+ MilestoneReference +
+ +
+ The extension defines a new MilestoneReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Milestone ID + | +
+ The ID of the milestone being referenced, this must match the ID of a milestone described elsewhere in a release about this contracting process. + + |
+ + string + | +
+
+ title
+
+ |
+ + Milestone title + | +
+ The title of the milestone being referenced, this must match the title of a milestone described elsewhere in a release about this contracting process. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/metrics/v1.1/release-schema.json b/en/extensions/metrics/v1.1/release-schema.json
new file mode 100644
index 000000000..d56c6da55
--- /dev/null
+++ b/en/extensions/metrics/v1.1/release-schema.json
@@ -0,0 +1,220 @@
+{
+ "definitions": {
+ "Planning": {
+ "properties": {
+ "forecasts": {
+ "type": "array",
+ "title": "Forecasts",
+ "description": "Any forecasts metrics for this results of this contracting process.",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ }
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "targets": {
+ "type": "array",
+ "title": "Targets",
+ "description": "Any target metrics for this results of this contracting process.",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ }
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "agreedMetrics": {
+ "type": "array",
+ "title": "Agreed metrics",
+ "description": "Any target metrics set out as part of the contract award.",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ }
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "agreedMetrics": {
+ "type": "array",
+ "title": "Agreed metrics",
+ "description": "Any target metrics set out as part of the contract documents.",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ }
+ }
+ }
+ },
+ "Implementation": {
+ "properties": {
+ "metrics": {
+ "type": "array",
+ "title": "Metrics",
+ "description": "Reported results from the delivery of the contracted goods, works or services.",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ }
+ }
+ }
+ },
+ "Metric": {
+ "type": "object",
+ "title": "Metric",
+ "description": "Metrics are used to set out targets and results from a contracting process. During the planning and tender sections, a metric indicates the anticipated results. In award and contract sections it indicates the awarded/contracted results. In the implementation section it is used to provide updates on actually delivered results, also known as outputs.",
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "An identifier for this metric. In some cases this may be drawn from a codelist of metrics required for this type of contracting process, or in other instances may be an arbitrary identifier.",
+ "type": [
+ "string"
+ ]
+ },
+ "title": {
+ "title": "Title",
+ "description": "The title of this metric",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Description",
+ "description": "A short description of the metric. This may include short details of measurement methods.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "observations": {
+ "type": "array",
+ "title": "Observations",
+ "description": "An array of target or actual values for this metric.",
+ "items": {
+ "$ref": "#/definitions/Observation"
+ }
+ }
+ }
+ },
+ "Observation": {
+ "type": "object",
+ "title": "Observation",
+ "description": "An actual or target observation. Observations should include either a value (for financial metrics) or measure (for other metrics).",
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "A local identifier for this specific observation. This may be an arbitrary identifier, or could be a composite of the metric identifier, and the date and other dimensions of this observation.",
+ "type": "string"
+ },
+ "period": {
+ "$ref": "#/definitions/Period"
+ },
+ "value": {
+ "$ref": "#/definitions/Value"
+ },
+ "measure": {
+ "title": "Observation measure",
+ "description": "For non-financial metrics, the measure of this forecast, target or actual observation. Measures may be provided as free text or numerical values.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ]
+ },
+ "unit": {
+ "type": [
+ "object",
+ "null"
+ ],
+ "title": "Unit",
+ "description": "Unit",
+ "properties": {
+ "name": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "title": "Unit name",
+ "description": "The name of the unit."
+ },
+ "scheme": {
+ "title": "Scheme",
+ "description": "The list from which units of measure identifiers are taken. This should be an entry in the unitClassificationScheme codelist. Use of the scheme 'UNCEFACT' for the UN/CEFACT Recommendation 20 list of 'Codes for Units of Measure Used in International Trade' is recommended.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true
+ },
+ "id": {
+ "title": "ID",
+ "description": "The identifier from the codelist referenced in the schema property. For example, with UNCEFACT, this is the value of the 'Common Code' column. From this identifier, applications can look-up the human readable name or symbol for this unit of measure.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "uri": {
+ "title": "URI",
+ "description": "If the scheme used provide a machine-readable URI for this unit of measure, this can be given.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ }
+ },
+ "dimensions": {
+ "type": "object",
+ "title": "Dimensions",
+ "description": "Any number of dimensions can be recorded within this object. Dimensions names should follow the camelCase conventions of OCDS.",
+ "patternProperties": {
+ "^.*": {
+ "type": "string"
+ }
+ }
+ },
+ "notes": {
+ "title": "Notes",
+ "description": "Any notes on this observation. This may include clarifying information.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedImplementationMilestone": {
+ "title": "Related implementation milestone",
+ "description": "A link to the milestone in the implementation section of OCDS to which this forecast, target or actual observation relates.",
+ "$ref": "#/definitions/MilestoneReference"
+ }
+ }
+ },
+ "MilestoneReference": {
+ "type": "object",
+ "title": "Milestone Reference",
+ "description": "A block used to reference a milestone, including the ID and title of the milestone being referenced.",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Milestone ID",
+ "description": "The ID of the milestone being referenced, this must match the ID of a milestone described elsewhere in a release about this contracting process.",
+ "type": "string"
+ },
+ "title": {
+ "title": "Milestone title",
+ "description": "The title of the milestone being referenced, this must match the title of a milestone described elsewhere in a release about this contracting process.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/metrics/v1.1/schema/index.html b/en/extensions/metrics/v1.1/schema/index.html
new file mode 100644
index 000000000..aefb023d8
--- /dev/null
+++ b/en/extensions/metrics/v1.1/schema/index.html
@@ -0,0 +1,862 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Metrics +
+ ++ The metrics extension supports publication of forecasts (planning stage), targets (tender stage), agreed performance targets (award and contract stage) and results (implementation stage). +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The metrics extension provides a common building block for reporting structured performance information on contracts.
+Metrics are structured like an OLAP data cube with each instance of Metric representing a single observation, categorised by a number of dimensions.
{
+ "metrics":[
+ {
+ "id":"annualDemand",
+ "title":"Annual Demand",
+ "description":"The annual demand",
+ "observations":[
+ {
+ "period":{
+ "startDate":"2015-01-01T00:00:00Z",
+ "endDate":"2015-12-31T23:59:59Z"
+ },
+ "quantity":"10000",
+ "dimensions":{
+ "vehicleType":"Car"
+ }
+ },
+ {
+ "period":{
+ "startDate":"2015-01-01T00:00:00Z",
+ "endDate":"2015-12-31T23:59:59Z"
+ },
+ "quantity":"1000",
+ "dimensions":{
+ "vehicleType":"Trucks"
+ },
+ "note":"Simple note"
+ }
+ ]
+ },
+ {
+
+ }
+ ]
+}
+Use with requirements
+Metrics can be used along with the requirements extension which will add a 'relatedRequirementID' property to metrics.
+With the requirements extension, bids, awards and contracts can include a requirementResponse indicating the values against each metric that a supplier intends to meet.
This can allow a degree of comparison between performance anticipated at bid, award, contract and implementation phases.
+To Do
+-
+
- [ ] Check oneOf schema syntax for value or quantity +
- [ ] Add relatedRequirementID to requirements extension +
- [ ] Validate schema updates +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/index.html b/en/extensions/milestone_documents/index.html
new file mode 100644
index 000000000..9b28673ca
--- /dev/null
+++ b/en/extensions/milestone_documents/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Metrics +
+ ++ The metrics extension supports publication of forecasts (planning stage), targets (tender stage), agreed performance targets (award and contract stage) and results (implementation stage). +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Planning +
+ +
+ The extension defines these fields in the Planning object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ forecasts
+
+ |
+ + Forecasts + | +
+ Any forecasts metrics for this results of this contracting process. + + |
+ + array of Metric objects + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ targets
+
+ |
+ + Targets + | +
+ Any target metrics for this results of this contracting process. + + |
+ + array of Metric objects + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Agreed metrics + | +
+ Any target metrics set out as part of the contract award. + + |
+ + array of Metric objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Agreed metrics + | +
+ Any target metrics set out as part of the contract documents. + + |
+ + array of Metric objects + | +
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ metrics
+
+ |
+ + Metrics + | +
+ Reported results from the delivery of the contracted goods, works or services. + + |
+ + array of Metric objects + | +
+ Metric +
+ +
+ The extension defines a new Metric object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ An identifier for this metric. In some cases this may be drawn from a codelist of metrics required for this type of contracting process, or in other instances may be an arbitrary identifier. + + |
+ + string + | +
+
+ title
+
+ |
+ + Title + | +
+ The title of this metric + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A short description of the metric. This may include short details of measurement methods. + + |
+ + string + | +
+
+ observations
+
+ |
+ + Observations + | +
+ An array of target or actual values for this metric. + + |
+ + array of Observation objects + | +
+ Observation +
+ +
+ The extension defines a new Observation object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ A local identifier for this specific observation. This may be an arbitrary identifier, or could be a composite of the metric identifier, and the date and other dimensions of this observation. + + |
+ + string + | +
+
+ period
+
+ |
+ + + | ++ + | ++ Period object + | +
+
+ value
+
+ |
+ + + | ++ + | ++ Value object + | +
+
+ measure
+
+ |
+ + Observation measure + | +
+ For non-financial metrics, the measure of this forecast, target or actual observation. Measures may be provided as free text or numerical values. + + |
+ + string or number + | +
+
+ unit
+
+ |
+ + Unit + | +
+ Unit + + |
+ + object + | +
+
+ unit.
+ |
+ + Unit name + | +
+ The name of the unit. + + |
+ + string + | +
+
+ unit.
+ |
+ + Scheme + | +
+ The list from which units of measure identifiers are taken. This should be an entry in the unitClassificationScheme codelist. Use of the scheme 'UNCEFACT' for the UN/CEFACT Recommendation 20 list of 'Codes for Units of Measure Used in International Trade' is recommended. + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ unit.
+ |
+ + ID + | +
+ The identifier from the codelist referenced in the schema property. For example, with UNCEFACT, this is the value of the 'Common Code' column. From this identifier, applications can look-up the human readable name or symbol for this unit of measure. + + |
+ + string + | +
+
+ unit.
+ |
+ + URI + | +
+ If the scheme used provide a machine-readable URI for this unit of measure, this can be given. + + |
+ + string + | +
+
+ dimensions
+
+ |
+ + Dimensions + | +
+ Any number of dimensions can be recorded within this object. Dimensions names should follow the camelCase conventions of OCDS. + + |
+ + object + | +
+
+ dimensions.
+ |
+ + + | ++ + | ++ string + | +
+
+ notes
+
+ |
+ + Notes + | +
+ Any notes on this observation. This may include clarifying information. + + |
+ + string + | +
+
+ relatedImplementationMilestone
+
+ |
+ + Related implementation milestone + | +
+ A link to the milestone in the implementation section of OCDS to which this forecast, target or actual observation relates. + + |
+ + MilestoneReference object + | +
+ MilestoneReference +
+ +
+ The extension defines a new MilestoneReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Milestone ID + | +
+ The ID of the milestone being referenced, this must match the ID of a milestone described elsewhere in a release about this contracting process. + + |
+ + string + | +
+
+ title
+
+ |
+ + Milestone title + | +
+ The title of the milestone being referenced, this must match the title of a milestone described elsewhere in a release about this contracting process. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/milestone_documents/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/master/release-schema.json b/en/extensions/milestone_documents/master/release-schema.json
new file mode 100644
index 000000000..b8100cd08
--- /dev/null
+++ b/en/extensions/milestone_documents/master/release-schema.json
@@ -0,0 +1,11 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "deprecated": null
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/milestone_documents/master/schema/index.html b/en/extensions/milestone_documents/master/schema/index.html
new file mode 100644
index 000000000..22c7a5052
--- /dev/null
+++ b/en/extensions/milestone_documents/master/schema/index.html
@@ -0,0 +1,257 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In OCDS 1.1, core support for documents attached to individual milestones was removed from the milestones block to simplify the standard.
+This extension re-introduces the documents block to milestones, providing fields to detail the documents related to each individual milestone.
Guidance
+Publishers ought to consider that many consuming applications will only look at the tender.documents, awards.documents, contracts.documents and contracts.implementation.documents section to access and display relevant documentation to users.
Document titles, document types, and descriptions can be used to indicate to human readers the particular nature of the documents and any milestones they relate to.
+However, in cases where it is important to track documents on a milestone-by-milestone basis this extension can be introduced.
+Depending on the nature of the documents, publishers ought to consider duplicating information in the parent section's documents block.
+Example
+During the implementation of a contract, the buyer sets milestones that the supplier needs to meet. Each of these milestones can have an associated document that offers more details about the met milestone: for example, a consultancy report:
+{
+ "contracts": [
+ {
+ "id": "CO-40002-18-166811",
+ "awardID": "354469-jorge-augusto-zarate-leiva-1",
+ "implementation": {
+ "milestones": [
+ {
+ "id": "fcrMXKIb3/o=",
+ "title": "Informe de Consultoria",
+ "type": "reporting",
+ "dueDate": "2020-02-13T00:00:00-04:00",
+ "dateMet": "2020-02-14T00:00:00-04:00",
+ "status": "met",
+ "documents": [
+ {
+ "id": "QQ1cjJZ82Rk=",
+ "url": "https://www.contrataciones.gov.py/documentos/download/contrato_detalle_entregable/vki7v5RKGrA%253D",
+ "datePublished": "2020-02-17T13:38:25-04:00",
+ "language": "es",
+ "title": "informe_n__13_1581957505348.pdf",
+ "format": "application/pdf"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.5
+-
+
- Review normative and non-normative words +
v1.1.4
+-
+
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/v1.1.1/README.md b/en/extensions/milestone_documents/v1.1.1/README.md
new file mode 100644
index 000000000..fca3c77d4
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.1/README.md
@@ -0,0 +1,15 @@
+# Milestone Documents
+
+In OCDS 1.1, core support for documents attached to individual milestones was removed from the milestones block to simplify the standard.
+
+This extension re-introduces the `documents` block to `milestones`, providing fields to detail the documents related to each individual milestone.
+
+## Guidance
+
+Publishers should consider that many consuming applications will only look at the `tender/documents`, `award/documents`, `contracts/documents` and `contracts/implementation/documents` section to access and display relevant documentation to users.
+
+Document titles, document types, and descriptions can be used to indicate to human readers the particular nature of the documents and any milestones they relate to.
+
+However, in cases where it is important to track documents on a milestone-by-milestone basis this extension can be introduced.
+
+Depending on the nature of the documents, publishers should consider duplicating information in the parent sections documents block also.
diff --git a/en/extensions/milestone_documents/v1.1.1/extension.json b/en/extensions/milestone_documents/v1.1.1/extension.json
new file mode 100644
index 000000000..a5e7776b7
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.1/extension.json
@@ -0,0 +1,15 @@
+{
+ "name": {
+ "en": "Milestone documents",
+ "es": "Documentos del hito"
+ },
+ "description": {
+ "en": "Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone.",
+ "es": "Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensi\u00f3n re-introduce la capacidad de adjuntar documentos a cada hito individual."
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "dependencies": [],
+ "documentationUrl": {}
+}
diff --git a/en/extensions/milestone_documents/v1.1.1/index.html b/en/extensions/milestone_documents/v1.1.1/index.html
new file mode 100644
index 000000000..42d7baadf
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.1/index.html
@@ -0,0 +1,285 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + + | +
+ + This field is modified from its original version. + + ++ The extension undoes the deprecation of this field. + + |
+ + + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/v1.1.1/release-schema.json b/en/extensions/milestone_documents/v1.1.1/release-schema.json
new file mode 100644
index 000000000..8175e79ed
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.1/release-schema.json
@@ -0,0 +1,18 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "title": "Documents",
+ "description": "A list of documents specifically associated with this milestone.",
+ "type": "array",
+ "deprecated": null,
+ "items": {
+ "$ref": "#/definitions/Document"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/milestone_documents/v1.1.1/schema/index.html b/en/extensions/milestone_documents/v1.1.1/schema/index.html
new file mode 100644
index 000000000..122172139
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.1/schema/index.html
@@ -0,0 +1,258 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In OCDS 1.1, core support for documents attached to individual milestones was removed from the milestones block to simplify the standard.
+This extension re-introduces the documents block to milestones, providing fields to detail the documents related to each individual milestone.
Guidance
+Publishers should consider that many consuming applications will only look at the tender/documents, award/documents, contracts/documents and contracts/implementation/documents section to access and display relevant documentation to users.
Document titles, document types, and descriptions can be used to indicate to human readers the particular nature of the documents and any milestones they relate to.
+However, in cases where it is important to track documents on a milestone-by-milestone basis this extension can be introduced.
+Depending on the nature of the documents, publishers should consider duplicating information in the parent sections documents block also.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/v1.1.3/README.md b/en/extensions/milestone_documents/v1.1.3/README.md
new file mode 100644
index 000000000..d4b803da2
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.3/README.md
@@ -0,0 +1,26 @@
+# Milestone Documents
+
+In OCDS 1.1, core support for documents attached to individual milestones was removed from the milestones block to simplify the standard.
+
+This extension re-introduces the `documents` block to `milestones`, providing fields to detail the documents related to each individual milestone.
+
+## Guidance
+
+Publishers should consider that many consuming applications will only look at the `tender/documents`, `award/documents`, `contracts/documents` and `contracts/implementation/documents` section to access and display relevant documentation to users.
+
+Document titles, document types, and descriptions can be used to indicate to human readers the particular nature of the documents and any milestones they relate to.
+
+However, in cases where it is important to track documents on a milestone-by-milestone basis this extension can be introduced.
+
+Depending on the nature of the documents, publishers should consider duplicating information in the parent sections documents block also.
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.3
+
+- Use Apache 2.0 License
+- Add tests and tidy code
diff --git a/en/extensions/milestone_documents/v1.1.3/extension.json b/en/extensions/milestone_documents/v1.1.3/extension.json
new file mode 100644
index 000000000..ec5daf958
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.3/extension.json
@@ -0,0 +1,16 @@
+{
+ "name": {
+ "en": "Milestone documents",
+ "es": "Documentos del hito"
+ },
+ "description": {
+ "en": "Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone.",
+ "es": "Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensi\u00f3n re-introduce la capacidad de adjuntar documentos a cada hito individual."
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting/ocds_milestone_documents_extension"
+ }
+}
diff --git a/en/extensions/milestone_documents/v1.1.3/index.html b/en/extensions/milestone_documents/v1.1.3/index.html
new file mode 100644
index 000000000..75bd22581
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.3/index.html
@@ -0,0 +1,303 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + Documents + | +
+ + This field is modified from its original version. + +A list of documents specifically associated with this milestone. + ++ The extension undoes the deprecation of this field. + + |
+ + array of Document objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/v1.1.3/release-schema.json b/en/extensions/milestone_documents/v1.1.3/release-schema.json
new file mode 100644
index 000000000..b8100cd08
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.3/release-schema.json
@@ -0,0 +1,11 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "deprecated": null
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/milestone_documents/v1.1.3/schema/index.html b/en/extensions/milestone_documents/v1.1.3/schema/index.html
new file mode 100644
index 000000000..1632f0d5c
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.3/schema/index.html
@@ -0,0 +1,257 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In OCDS 1.1, core support for documents attached to individual milestones was removed from the milestones block to simplify the standard.
+This extension re-introduces the documents block to milestones, providing fields to detail the documents related to each individual milestone.
Guidance
+Publishers should consider that many consuming applications will only look at the tender/documents, award/documents, contracts/documents and contracts/implementation/documents section to access and display relevant documentation to users.
Document titles, document types, and descriptions can be used to indicate to human readers the particular nature of the documents and any milestones they relate to.
+However, in cases where it is important to track documents on a milestone-by-milestone basis this extension can be introduced.
+Depending on the nature of the documents, publishers should consider duplicating information in the parent sections documents block also.
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.3
+-
+
- Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/v1.1.4/README.md b/en/extensions/milestone_documents/v1.1.4/README.md
new file mode 100644
index 000000000..b1676d91f
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.4/README.md
@@ -0,0 +1,30 @@
+# Milestone Documents
+
+In OCDS 1.1, core support for documents attached to individual milestones was removed from the milestones block to simplify the standard.
+
+This extension re-introduces the `documents` block to `milestones`, providing fields to detail the documents related to each individual milestone.
+
+## Guidance
+
+Publishers should consider that many consuming applications will only look at the `tender/documents`, `award/documents`, `contracts/documents` and `contracts/implementation/documents` section to access and display relevant documentation to users.
+
+Document titles, document types, and descriptions can be used to indicate to human readers the particular nature of the documents and any milestones they relate to.
+
+However, in cases where it is important to track documents on a milestone-by-milestone basis this extension can be introduced.
+
+Depending on the nature of the documents, publishers should consider duplicating information in the parent sections documents block also.
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.4
+
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Use Apache 2.0 License
+- Add tests and tidy code
diff --git a/en/extensions/milestone_documents/v1.1.4/extension.json b/en/extensions/milestone_documents/v1.1.4/extension.json
new file mode 100644
index 000000000..9a2474f6c
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.4/extension.json
@@ -0,0 +1,19 @@
+{
+ "name": {
+ "en": "Milestone documents",
+ "es": "Documentos del hito"
+ },
+ "description": {
+ "en": "Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone.",
+ "es": "Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensi\u00f3n re-introduce la capacidad de adjuntar documentos a cada hito individual."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/milestone_documents/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/en/extensions/milestone_documents/v1.1.4/index.html b/en/extensions/milestone_documents/v1.1.4/index.html
new file mode 100644
index 000000000..00b92b712
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.4/index.html
@@ -0,0 +1,307 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + + | +
+ + This field is modified from its original version. + + ++ The extension undoes the deprecation of this field. + + |
+ + + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/v1.1.4/release-schema.json b/en/extensions/milestone_documents/v1.1.4/release-schema.json
new file mode 100644
index 000000000..b8100cd08
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.4/release-schema.json
@@ -0,0 +1,11 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "deprecated": null
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/milestone_documents/v1.1.4/schema/index.html b/en/extensions/milestone_documents/v1.1.4/schema/index.html
new file mode 100644
index 000000000..a5ea5e8e8
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.4/schema/index.html
@@ -0,0 +1,257 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In OCDS 1.1, core support for documents attached to individual milestones was removed from the milestones block to simplify the standard.
+This extension re-introduces the documents block to milestones, providing fields to detail the documents related to each individual milestone.
Guidance
+Publishers should consider that many consuming applications will only look at the tender/documents, award/documents, contracts/documents and contracts/implementation/documents section to access and display relevant documentation to users.
Document titles, document types, and descriptions can be used to indicate to human readers the particular nature of the documents and any milestones they relate to.
+However, in cases where it is important to track documents on a milestone-by-milestone basis this extension can be introduced.
+Depending on the nature of the documents, publishers should consider duplicating information in the parent sections documents block also.
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.4
+-
+
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/v1.1.5/README.md b/en/extensions/milestone_documents/v1.1.5/README.md
new file mode 100644
index 000000000..b35eaa058
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.5/README.md
@@ -0,0 +1,71 @@
+# Milestone Documents
+
+In OCDS 1.1, core support for documents attached to individual milestones was removed from the milestones block to simplify the standard.
+
+This extension re-introduces the `documents` block to `milestones`, providing fields to detail the documents related to each individual milestone.
+
+## Guidance
+
+Publishers ought to consider that many consuming applications will only look at the `tender.documents`, `awards.documents`, `contracts.documents` and `contracts.implementation.documents` section to access and display relevant documentation to users.
+
+Document titles, document types, and descriptions can be used to indicate to human readers the particular nature of the documents and any milestones they relate to.
+
+However, in cases where it is important to track documents on a milestone-by-milestone basis this extension can be introduced.
+
+Depending on the nature of the documents, publishers ought to consider duplicating information in the parent section's documents block.
+
+## Example
+
+During the implementation of a contract, the buyer sets milestones that the supplier needs to meet. Each of these milestones can have an associated document that offers more details about the met milestone: for example, a consultancy report:
+
+```json
+{
+ "contracts": [
+ {
+ "id": "CO-40002-18-166811",
+ "awardID": "354469-jorge-augusto-zarate-leiva-1",
+ "implementation": {
+ "milestones": [
+ {
+ "id": "fcrMXKIb3/o=",
+ "title": "Informe de Consultoria",
+ "type": "reporting",
+ "dueDate": "2020-02-13T00:00:00-04:00",
+ "dateMet": "2020-02-14T00:00:00-04:00",
+ "status": "met",
+ "documents": [
+ {
+ "id": "QQ1cjJZ82Rk=",
+ "url": "https://www.contrataciones.gov.py/documentos/download/contrato_detalle_entregable/vki7v5RKGrA%253D",
+ "datePublished": "2020-02-17T13:38:25-04:00",
+ "language": "es",
+ "title": "informe_n__13_1581957505348.pdf",
+ "format": "application/pdf"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+```
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.5
+
+- Review normative and non-normative words
+
+### v1.1.4
+
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Use Apache 2.0 License
+- Add tests and tidy code
diff --git a/en/extensions/milestone_documents/v1.1.5/extension.json b/en/extensions/milestone_documents/v1.1.5/extension.json
new file mode 100644
index 000000000..a9304fd6c
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.5/extension.json
@@ -0,0 +1,23 @@
+{
+ "name": {
+ "en": "Milestone documents",
+ "es": "Documentos del hito"
+ },
+ "description": {
+ "en": "Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone.",
+ "es": "Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensi\u00f3n re-introduce la capacidad de adjuntar documentos a cada hito individual."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/milestone_documents/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/milestone_documents/v1.1.5/index.html b/en/extensions/milestone_documents/v1.1.5/index.html
new file mode 100644
index 000000000..285424400
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.5/index.html
@@ -0,0 +1,349 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + + | +
+ + This field is modified from its original version. + + ++ The extension undoes the deprecation of this field. + + |
+ + + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/v1.1.5/release-schema.json b/en/extensions/milestone_documents/v1.1.5/release-schema.json
new file mode 100644
index 000000000..b8100cd08
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.5/release-schema.json
@@ -0,0 +1,11 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "deprecated": null
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/milestone_documents/v1.1.5/schema/index.html b/en/extensions/milestone_documents/v1.1.5/schema/index.html
new file mode 100644
index 000000000..4a1878a7d
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1.5/schema/index.html
@@ -0,0 +1,257 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In OCDS 1.1, core support for documents attached to individual milestones was removed from the milestones block to simplify the standard.
+This extension re-introduces the documents block to milestones, providing fields to detail the documents related to each individual milestone.
Guidance
+Publishers ought to consider that many consuming applications will only look at the tender.documents, awards.documents, contracts.documents and contracts.implementation.documents section to access and display relevant documentation to users.
Document titles, document types, and descriptions can be used to indicate to human readers the particular nature of the documents and any milestones they relate to.
+However, in cases where it is important to track documents on a milestone-by-milestone basis this extension can be introduced.
+Depending on the nature of the documents, publishers ought to consider duplicating information in the parent section's documents block.
+Example
+During the implementation of a contract, the buyer sets milestones that the supplier needs to meet. Each of these milestones can have an associated document that offers more details about the met milestone: for example, a consultancy report:
+{
+ "contracts": [
+ {
+ "id": "CO-40002-18-166811",
+ "awardID": "354469-jorge-augusto-zarate-leiva-1",
+ "implementation": {
+ "milestones": [
+ {
+ "id": "fcrMXKIb3/o=",
+ "title": "Informe de Consultoria",
+ "type": "reporting",
+ "dueDate": "2020-02-13T00:00:00-04:00",
+ "dateMet": "2020-02-14T00:00:00-04:00",
+ "status": "met",
+ "documents": [
+ {
+ "id": "QQ1cjJZ82Rk=",
+ "url": "https://www.contrataciones.gov.py/documentos/download/contrato_detalle_entregable/vki7v5RKGrA%253D",
+ "datePublished": "2020-02-17T13:38:25-04:00",
+ "language": "es",
+ "title": "informe_n__13_1581957505348.pdf",
+ "format": "application/pdf"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.5
+-
+
- Review normative and non-normative words +
v1.1.4
+-
+
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/v1.1/README.md b/en/extensions/milestone_documents/v1.1/README.md
new file mode 100644
index 000000000..fca3c77d4
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1/README.md
@@ -0,0 +1,15 @@
+# Milestone Documents
+
+In OCDS 1.1, core support for documents attached to individual milestones was removed from the milestones block to simplify the standard.
+
+This extension re-introduces the `documents` block to `milestones`, providing fields to detail the documents related to each individual milestone.
+
+## Guidance
+
+Publishers should consider that many consuming applications will only look at the `tender/documents`, `award/documents`, `contracts/documents` and `contracts/implementation/documents` section to access and display relevant documentation to users.
+
+Document titles, document types, and descriptions can be used to indicate to human readers the particular nature of the documents and any milestones they relate to.
+
+However, in cases where it is important to track documents on a milestone-by-milestone basis this extension can be introduced.
+
+Depending on the nature of the documents, publishers should consider duplicating information in the parent sections documents block also.
diff --git a/en/extensions/milestone_documents/v1.1/extension.json b/en/extensions/milestone_documents/v1.1/extension.json
new file mode 100644
index 000000000..a5e7776b7
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1/extension.json
@@ -0,0 +1,15 @@
+{
+ "name": {
+ "en": "Milestone documents",
+ "es": "Documentos del hito"
+ },
+ "description": {
+ "en": "Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone.",
+ "es": "Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensi\u00f3n re-introduce la capacidad de adjuntar documentos a cada hito individual."
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "dependencies": [],
+ "documentationUrl": {}
+}
diff --git a/en/extensions/milestone_documents/v1.1/index.html b/en/extensions/milestone_documents/v1.1/index.html
new file mode 100644
index 000000000..feda08fa3
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1/index.html
@@ -0,0 +1,285 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + + | +
+ + This field is modified from its original version. + + ++ The extension undoes the deprecation of this field. + + |
+ + + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/milestone_documents/v1.1/release-schema.json b/en/extensions/milestone_documents/v1.1/release-schema.json
new file mode 100644
index 000000000..8175e79ed
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1/release-schema.json
@@ -0,0 +1,18 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "title": "Documents",
+ "description": "A list of documents specifically associated with this milestone.",
+ "type": "array",
+ "deprecated": null,
+ "items": {
+ "$ref": "#/definitions/Document"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/milestone_documents/v1.1/schema/index.html b/en/extensions/milestone_documents/v1.1/schema/index.html
new file mode 100644
index 000000000..cf29b0522
--- /dev/null
+++ b/en/extensions/milestone_documents/v1.1/schema/index.html
@@ -0,0 +1,258 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In OCDS 1.1, core support for documents attached to individual milestones was removed from the milestones block to simplify the standard.
+This extension re-introduces the documents block to milestones, providing fields to detail the documents related to each individual milestone.
Guidance
+Publishers should consider that many consuming applications will only look at the tender/documents, award/documents, contracts/documents and contracts/implementation/documents section to access and display relevant documentation to users.
Document titles, document types, and descriptions can be used to indicate to human readers the particular nature of the documents and any milestones they relate to.
+However, in cases where it is important to track documents on a milestone-by-milestone basis this extension can be introduced.
+Depending on the nature of the documents, publishers should consider duplicating information in the parent sections documents block also.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/options/index.html b/en/extensions/options/index.html
new file mode 100644
index 000000000..b211c9320
--- /dev/null
+++ b/en/extensions/options/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Milestone documents +
+ ++ Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + Documents + | +
+ + This field is modified from its original version. + +A list of documents specifically associated with this milestone. + ++ The extension undoes the deprecation of this field. + + |
+ + array of Document objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/options/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/options/master/release-schema.json b/en/extensions/options/master/release-schema.json
new file mode 100644
index 000000000..b48587d78
--- /dev/null
+++ b/en/extensions/options/master/release-schema.json
@@ -0,0 +1,60 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "options": {
+ "title": "Options",
+ "description": "A description of the options.",
+ "$ref": "#/definitions/Options"
+ },
+ "hasOptions": {
+ "title": "Options used",
+ "description": "Whether or not the buyer reserves the right to make additional purchases from the supplier, as long as the contract is valid.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "options": {
+ "title": "Options",
+ "description": "A description of the options.",
+ "$ref": "#/definitions/Options"
+ },
+ "hasOptions": {
+ "title": "Options used",
+ "description": "Whether the buyer reserves the right to make additional purchases from the supplier, as long as the contract is valid.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "Options": {
+ "title": "Options",
+ "description": "A description of the options.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "A description of the options.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "period": {
+ "title": "Period",
+ "description": "The period over which the options can be used.",
+ "$ref": "#/definitions/Period"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/options/master/schema/index.html b/en/extensions/options/master/schema/index.html
new file mode 100644
index 000000000..a6ad4af9e
--- /dev/null
+++ b/en/extensions/options/master/schema/index.html
@@ -0,0 +1,384 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Options +
+ ++ Adds fields for information on options. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds fields to indicate whether options are used and other information about options.
+A buyer may have a right – but not an obligation – to additional purchases from a supplier while the contract is valid.
+For example, a contract may concern a thousand uniforms, and the buyer may have the option to request an additional hundred uniforms. This might occur if the buyer doesn't yet know whether a planned increase in staff will take place.
+Legal context
+The Revised Agreement on Government Procurement (GPA) includes: "each notice of intended procurement shall include … d. a description of any options".
+The European Union is a party to the GPA, and as such its Directive 2014/24/EU (Public contracts — setting out clear ground rules) includes: "Part C: Information to be included in contract notices … 7. … Where appropriate, description of any options."
+Example
+{
+ "tender": {
+ "hasOptions": true,
+ "options": {
+ "description": "The buyer has the option to buy an additional hundred uniforms.",
+ "period": {
+ "durationInDays": 180
+ }
+ }
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-10-06
+-
+
- Add
Options.periodfield.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile, in pull requests and in https://github.com/open-contracting/standard/issues/691.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/organizationClassification/1.1/README.md b/en/extensions/organizationClassification/1.1/README.md
new file mode 100644
index 000000000..b13c5150c
--- /dev/null
+++ b/en/extensions/organizationClassification/1.1/README.md
@@ -0,0 +1,44 @@
+# Organization classification
+
+Adds an array of classification objects to an organization's details, in order to categorize it.
+
+## Legal context
+
+In the European Union, this extension's fields correspond to [eForms BT-10 (Activity Authority)](https://docs.ted.europa.eu/eforms/latest/reference/business-terms/). For correspondences to eForms fields, see [OCDS for eForms](https://standard.open-contracting.org/profiles/eforms/latest/en/). For correspondences to Tenders Electronic Daily (TED), see [OCDS for the European Union](http://standard.open-contracting.org/profiles/eu/latest/en/).
+
+## Examples
+
+```json
+{
+ "parties": [
+ {
+ "id": "1",
+ "details": {
+ "classifications": [
+ {
+ "id": "10",
+ "scheme": "TED_CA_ACTIVITY",
+ "description": "Social protection"
+ }
+ ]
+ }
+ }
+ ]
+}
+```
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### 2023-08-01
+
+- Add 'eu-main-activity' and 'eu-buyer-contracting-type' to `+itemClassificationScheme.csv`.
+
+### 2020-04-24
+
+- Add `minProperties`, `minItems` and/or `minLength` properties.
+
+This extension was originally discussed as part of the [OCDS for EU profile](https://github.com/open-contracting-extensions/european-union/issues), in [pull requests](https://github.com/open-contracting-extensions/ocds_organizationClassification_extension/pulls?q=is%3Apr+is%3Aclosed) and in
+
+
+
+
+ + Options +
+ ++ Adds fields for information on options. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ options
+
+ |
+ + Options + | +
+ A description of the options. + + |
+ + Options object + | +
+
+ hasOptions
+
+ |
+ + Options used + | +
+ Whether or not the buyer reserves the right to make additional purchases from the supplier, as long as the contract is valid. + + |
+ + boolean + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ options
+
+ |
+ + Options + | +
+ A description of the options. + + |
+ + Options object + | +
+
+ hasOptions
+
+ |
+ + Options used + | +
+ Whether the buyer reserves the right to make additional purchases from the supplier, as long as the contract is valid. + + |
+ + boolean + | +
+ Options +
+ +
+ The extension defines a new Options object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ A description of the options. + + |
+ + string + | +
+
+ period
+
+ |
+ + Period + | +
+ The period over which the options can be used. + + |
+ + Period object + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/organizationClassification/1.1/extension.json b/en/extensions/organizationClassification/1.1/extension.json
new file mode 100644
index 000000000..6515b8a0f
--- /dev/null
+++ b/en/extensions/organizationClassification/1.1/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Organization classification",
+ "es": "Clasificaci\u00f3n de la organizaci\u00f3n"
+ },
+ "description": {
+ "en": "Adds an array of classification objects to an organization's details in order to categorize it.",
+ "es": "Adds an array of classification objects to an organization's details in order to categorize it."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/organizationClassification/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+itemClassificationScheme.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/organizationClassification/1.1/index.html b/en/extensions/organizationClassification/1.1/index.html
new file mode 100644
index 000000000..18375dad0
--- /dev/null
+++ b/en/extensions/organizationClassification/1.1/index.html
@@ -0,0 +1,310 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization classification +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ COFOG
+
+ |
+ + Classification of the Functions of Government + | +
+ A standard classifying the purposes of government activities, developed by the Organisation for Economic Co-operation and Development and published by the United Nations Statistical Division. + +
|
+
+
+ eu-buyer-contracting-type
+
+ |
+ + EU buyer contracting type + | +
+ Whether a buyer is a contracting entity within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ eu-main-activity
+
+ |
+ + EU main activity + | +
+ The main activities of buyers within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ TED_CA_TYPE
+
+ |
+ + EC Type of contracting authority + | +
+ The types of contracting authority within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ TED_CE_ACTIVITY
+
+ |
+ + EC Main activity of contracting entity + | +
+ The main activities of contracting entities within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/organizationClassification/1.1/release-schema.json b/en/extensions/organizationClassification/1.1/release-schema.json
new file mode 100644
index 000000000..d69ff494b
--- /dev/null
+++ b/en/extensions/organizationClassification/1.1/release-schema.json
@@ -0,0 +1,23 @@
+{
+ "definitions": {
+ "Organization": {
+ "properties": {
+ "details": {
+ "properties": {
+ "classifications": {
+ "title": "Organization classifications",
+ "description": "The classifications that categorize the organization",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/organizationClassification/1.1/schema/index.html b/en/extensions/organizationClassification/1.1/schema/index.html
new file mode 100644
index 000000000..a0f751c44
--- /dev/null
+++ b/en/extensions/organizationClassification/1.1/schema/index.html
@@ -0,0 +1,255 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization classification +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an array of classification objects to an organization's details, in order to categorize it.
+Legal context
+In the European Union, this extension's fields correspond to eForms BT-10 (Activity Authority). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Examples
+{
+ "parties": [
+ {
+ "id": "1",
+ "details": {
+ "classifications": [
+ {
+ "id": "10",
+ "scheme": "TED_CA_ACTIVITY",
+ "description": "Social protection"
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-08-01
+-
+
- Add 'eu-main-activity' and 'eu-buyer-contracting-type' to
+itemClassificationScheme.csv.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile, in pull requests and in https://github.com/open-contracting/standard/issues/711.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/organizationClassification/index.html b/en/extensions/organizationClassification/index.html
new file mode 100644
index 000000000..8a780219f
--- /dev/null
+++ b/en/extensions/organizationClassification/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization classification +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + Organization classifications + | +
+ The classifications that categorize the organization + + |
+ + array of Classification objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/organizationClassification/1.1/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/organizationClassification/master/index.html b/en/extensions/organizationClassification/master/index.html
new file mode 100644
index 000000000..13cde632b
--- /dev/null
+++ b/en/extensions/organizationClassification/master/index.html
@@ -0,0 +1,311 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization classification +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ COFOG
+
+ |
+ + Classification of the Functions of Government + | +
+ A standard classifying the purposes of government activities, developed by the Organisation for Economic Co-operation and Development and published by the United Nations Statistical Division. + +
|
+
+
+ eu-buyer-contracting-type
+
+ |
+ + EU buyer contracting type + | +
+ Whether a buyer is a contracting entity within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ eu-main-activity
+
+ |
+ + EU main activity + | +
+ The main activities of buyers within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ TED_CA_TYPE
+
+ |
+ + EC Type of contracting authority + | +
+ The types of contracting authority within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ TED_CE_ACTIVITY
+
+ |
+ + EC Main activity of contracting entity + | +
+ The main activities of contracting entities within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/organizationClassification/master/release-schema.json b/en/extensions/organizationClassification/master/release-schema.json
new file mode 100644
index 000000000..d69ff494b
--- /dev/null
+++ b/en/extensions/organizationClassification/master/release-schema.json
@@ -0,0 +1,23 @@
+{
+ "definitions": {
+ "Organization": {
+ "properties": {
+ "details": {
+ "properties": {
+ "classifications": {
+ "title": "Organization classifications",
+ "description": "The classifications that categorize the organization",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/organizationClassification/master/schema/index.html b/en/extensions/organizationClassification/master/schema/index.html
new file mode 100644
index 000000000..0896187f7
--- /dev/null
+++ b/en/extensions/organizationClassification/master/schema/index.html
@@ -0,0 +1,256 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization classification +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an array of classification objects to an organization's details, in order to categorize it.
+Legal context
+In the European Union, this extension's fields correspond to eForms BT-10 (Activity Authority). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Examples
+{
+ "parties": [
+ {
+ "id": "1",
+ "details": {
+ "classifications": [
+ {
+ "id": "10",
+ "scheme": "TED_CA_ACTIVITY",
+ "description": "Social protection"
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-08-01
+-
+
- Add 'eu-main-activity' and 'eu-buyer-contracting-type' to
+itemClassificationScheme.csv.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile, in pull requests and in https://github.com/open-contracting/standard/issues/711.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/otherRequirements/index.html b/en/extensions/otherRequirements/index.html
new file mode 100644
index 000000000..37a3d6b05
--- /dev/null
+++ b/en/extensions/otherRequirements/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization classification +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + Organization classifications + | +
+ The classifications that categorize the organization + + |
+ + array of Classification objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/otherRequirements/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/otherRequirements/master/codelists/reservedParticipation.csv b/en/extensions/otherRequirements/master/codelists/reservedParticipation.csv
new file mode 100644
index 000000000..2036d2ee0
--- /dev/null
+++ b/en/extensions/otherRequirements/master/codelists/reservedParticipation.csv
@@ -0,0 +1,3 @@
+Code,Title,Description
+shelteredWorkshop,Sheltered workshop,Participation is reserved to sheltered workshops and suppliers aiming at the social and professional integration of disabled or disadvantaged persons.
+publicServiceMissionOrganization,Public service mission organization,Participation is reserved to organizations pursuing a public service mission and fulfilling other legislative conditions.
diff --git a/en/extensions/otherRequirements/master/extension.json b/en/extensions/otherRequirements/master/extension.json
new file mode 100644
index 000000000..6529fd213
--- /dev/null
+++ b/en/extensions/otherRequirements/master/extension.json
@@ -0,0 +1,29 @@
+{
+ "name": {
+ "en": "Other Requirements",
+ "es": "Otros requisitos"
+ },
+ "description": {
+ "en": "Adds an object to describe other requirements to participate in a contracting process.",
+ "es": "Agregar un objeto para describir otros requisitos para participar en un proceso de contrataci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/otherRequirements/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "reservedParticipation.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/en/extensions/otherRequirements/master/index.html b/en/extensions/otherRequirements/master/index.html
new file mode 100644
index 000000000..c06fec117
--- /dev/null
+++ b/en/extensions/otherRequirements/master/index.html
@@ -0,0 +1,363 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Other Requirements +
+ ++ Adds an object to describe other requirements to participate in a contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ reservedParticipation.csv +
+ +
+ You can download the reservedParticipation.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ shelteredWorkshop
+
+ |
+ + Sheltered workshop + | +
+ Participation is reserved to sheltered workshops and suppliers aiming at the social and professional integration of disabled or disadvantaged persons. + + |
+
+
+ publicServiceMissionOrganization
+
+ |
+ + Public service mission organization + | +
+ Participation is reserved to organizations pursuing a public service mission and fulfilling other legislative conditions. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/otherRequirements/master/release-schema.json b/en/extensions/otherRequirements/master/release-schema.json
new file mode 100644
index 000000000..7b8358918
--- /dev/null
+++ b/en/extensions/otherRequirements/master/release-schema.json
@@ -0,0 +1,100 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "otherRequirements": {
+ "title": "Other requirements",
+ "description": "Other requirements to participate in the procedure.",
+ "$ref": "#/definitions/OtherRequirements"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "otherRequirements": {
+ "title": "Other requirements",
+ "description": "Other requirements to participate in the lot.",
+ "$ref": "#/definitions/OtherRequirements"
+ }
+ }
+ },
+ "OtherRequirements": {
+ "title": "Other requirements",
+ "description": "Other requirements to participate in the procedure or lot.",
+ "type": "object",
+ "properties": {
+ "requiresStaffNamesAndQualifications": {
+ "title": "Requires staff names and qualifications",
+ "description": "Whether the bidders are obligated to indicate the names and professional qualifications of the staff assigned to performing the contract.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "reservedParticipation": {
+ "title": "Reserved participation",
+ "description": "The types of organizations to which participation is reserved.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "reservedParticipation.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "qualificationSystemConditions": {
+ "title": "Qualification system conditions",
+ "description": "The conditions to be fulfilled by candidates in view of their qualification for the system.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "qualificationSystemMethods": {
+ "title": "Qualification system methods",
+ "description": "The methods according to which each of the qualification system conditions will be verified.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "reductionCriteria": {
+ "title": "Reduction criteria",
+ "description": "The criteria or rules for selecting a limited number of qualified candidates to submit bids.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "securityClearance": {
+ "title": "Security clearance",
+ "description": "Information about the required security clearance (e.g. which clearance level is needed, which team members need it, whether it is needed already for accessing documents or only for contract execution).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/otherRequirements/master/schema/index.html b/en/extensions/otherRequirements/master/schema/index.html
new file mode 100644
index 000000000..5bd9a077c
--- /dev/null
+++ b/en/extensions/otherRequirements/master/schema/index.html
@@ -0,0 +1,423 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Other Requirements +
+ ++ Adds an object to describe other requirements to participate in a contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an object to describe other requirements to participate in a contracting process.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Legal context
+In the European Union, this extension's fields correspond to eForms BG-705 (Other Requirements), although not all the fields have been implemented yet. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+Tender
+{
+ "tender": {
+ "otherRequirements": {
+ "requiresStaffNamesAndQualifications": true,
+ "reservedParticipation": [
+ "shelteredWorkshop"
+ ],
+ "qualificationSystemConditions": [
+ "The candidates are required to comply with all the technical and financial requisites listed on the National Procurement portal: https://procurement.example.org/requisites",
+ "The candidates are required to create an electronic profile on https://procurement.example.org."
+ ],
+ "qualificationSystemMethods": [
+ "Pre-qualification questionnaire",
+ "Standard test, based on the results of the pre-qualification questionnaire"
+ ],
+ "reductionCriteria": "The candidates will be selected according to their technical, financial and legal capacity to undertake the works described in the present notice. More details on the criteria can be found in section 4.3 of the PCG.",
+ "securityClearance": "EU Confidential security clearance of Key Management Personnel must be achieved before access to procurement documents be granted"
+ }
+ }
+}
+Lot
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "otherRequirements": {
+ "requiresStaffNamesAndQualifications": true,
+ "reservedParticipation": [
+ "shelteredWorkshop"
+ ],
+ "qualificationSystemConditions": [
+ "The candidates are required to comply with all the technical and financial requisites listed on the National Procurement portal: https://procurement.example.org/requisites",
+ "The candidates are required to create an electronic profile on https://procurement.example.org."
+ ],
+ "qualificationSystemMethods": [
+ "Pre-qualification questionnaire",
+ "Standard test, based on the results of the pre-qualification questionnaire"
+ ],
+ "reductionCriteria": "The candidates will be selected according to their technical, financial and legal capacity to undertake the works described in the present notice. More details on the criteria can be found in section 4.3 of the PCG.",
+ "securityClearance": "EU Confidential security clearance of Key Management Personnel must be achieved before access to procurement documents be granted"
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-03-09
+-
+
- Add
OtherRequirements.securityClearancefield.
+
2022-03-09
+-
+
- Add
itemsto theOtherRequirements.qualificationSystemConditionsandOtherRequirements.qualificationSystemMethodsobjects.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/pagination/index.html b/en/extensions/pagination/index.html
new file mode 100644
index 000000000..dea527d1f
--- /dev/null
+++ b/en/extensions/pagination/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Other Requirements +
+ ++ Adds an object to describe other requirements to participate in a contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ otherRequirements
+
+ |
+ + Other requirements + | +
+ Other requirements to participate in the procedure. + + |
+ + OtherRequirements object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ otherRequirements
+
+ |
+ + Other requirements + | +
+ Other requirements to participate in the lot. + + |
+ + OtherRequirements object + | +
+ OtherRequirements +
+ +
+ The extension defines a new OtherRequirements object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ requiresStaffNamesAndQualifications
+
+ |
+ + Requires staff names and qualifications + | +
+ Whether the bidders are obligated to indicate the names and professional qualifications of the staff assigned to performing the contract. + + |
+ + boolean + | +
+
+ reservedParticipation
+
+ |
+ + Reserved participation + | +
+ The types of organizations to which participation is reserved. + + |
+ + array of strings from open reservedParticipation codelist + | +
+
+ qualificationSystemConditions
+
+ |
+ + Qualification system conditions + | +
+ The conditions to be fulfilled by candidates in view of their qualification for the system. + + |
+ + array of strings + | +
+
+ qualificationSystemMethods
+
+ |
+ + Qualification system methods + | +
+ The methods according to which each of the qualification system conditions will be verified. + + |
+ + array of strings + | +
+
+ reductionCriteria
+
+ |
+ + Reduction criteria + | +
+ The criteria or rules for selecting a limited number of qualified candidates to submit bids. + + |
+ + string + | +
+
+ securityClearance
+
+ |
+ + Security clearance + | +
+ Information about the required security clearance (e.g. which clearance level is needed, which team members need it, whether it is needed already for accessing documents or only for contract execution). + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/pagination/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/index.html b/en/extensions/participation_fee/index.html
new file mode 100644
index 000000000..9607e7007
--- /dev/null
+++ b/en/extensions/participation_fee/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Pagination +
+ ++ Adds a links object to packages, to support pagination. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a links object to packages, to support pagination.
+Links
+The top-level links object in release packages and record packages has three fields:
-
+
next: A URL to the next sequential package
+prev: A URL to the previous sequential package
+
To construct the next and/or prev URLs, it is encouraged to use query string parameters like:
-
+
since=TIMESTAMP, to return a page of results that are modified after thesincetimestamp, in chronological order
+offset=NUMBER, to return a page of results that are positioned after theoffsetnumber, in sequential order (for example, if the results are retrieved from a SQL database)
+
It is discouraged to use page=NUMBER with results ordered in reverse chronology, because:
-
+
- A given page won't return the same results over time.
page=1will return different results today, next week, and next year.
+ - Users can receive duplicate results while paginating. For example, if a new release is published to page 1 while users are paginating, then the result at the bottom of each page will be moved to the top of the following page. +
- It is harder for users to synchronize with the API. With
sinceoroffset, users can retrieve new results by submitting the timestamp or offset of their last request. Withpage, users need to determine which results are new or old.
+
Reference: HTML link types, 18F API Standards, Government of Canada Standards on APIs, Government of Ontario API Guidelines, OpenActive Realtime Paged Data Exchange.
+Example
+A publisher has a large number of releases. Instead of gathering them into one release package, it segments them into multiple release packages, via an API with pagination. The links.next field provides the link to the next page.
{
+ "uri": "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-05-contract.json",
+ "license": "http://opendatacommons.org/licenses/pddl/1.0/",
+ "publicationPolicy": "https://github.com/open-contracting/sample-data/",
+ "version": "1.1",
+ "releases": [
+ {
+ "ocid": "ocds-213czf-000-00001",
+ "id": "ocds-213czf-000-00001-05-contract",
+ "date": "2010-05-10T10:30:00Z",
+ "language": "en",
+ "tag": [
+ "contract"
+ ],
+ "initiationType": "tender"
+ }
+ ],
+ "links": {
+ "next": "https://raw.githubusercontent.com/open-contracting/api-specification/master/multiple-file-api-next/releases-2015.json"
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-11-05
+-
+
- Remove
links.all.
+ - Remove
packageMetadata.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2020-04-15
+-
+
- Deprecate
links.all.
+ - Deprecate
packageMetadata.
+
+
+
+
+
+
+ + + This page has moved to a /en/extensions/participation_fee/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/master/codelists/methodOfPayment.csv b/en/extensions/participation_fee/master/codelists/methodOfPayment.csv
new file mode 100644
index 000000000..85a4e71fc
--- /dev/null
+++ b/en/extensions/participation_fee/master/codelists/methodOfPayment.csv
@@ -0,0 +1,7 @@
+Code,Title,Description
+cash,Cash,"The payment is made in cash, such as banknotes and coins."
+check,Check,"The payment is made by check (also written as ""cheque"")."
+creditCard,Credit card,The payment is made by credit card.
+directDebit,Direct debit,"The payment is made by direct debit, also known as direct withdrawal, pre-authorized debit (PAD) or pre-authorized payment (PAP)."
+letterOfCredit,Letter of credit,The payment is made by letter of credit.
+wireTransfer,Wire transfer,"The payment is made by wire transfer, also known as bank transfer or credit transfer."
diff --git a/en/extensions/participation_fee/master/codelists/participationFeeType.csv b/en/extensions/participation_fee/master/codelists/participationFeeType.csv
new file mode 100644
index 000000000..307acd1a9
--- /dev/null
+++ b/en/extensions/participation_fee/master/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Code,Title,Description
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/en/extensions/participation_fee/master/extension.json b/en/extensions/participation_fee/master/extension.json
new file mode 100644
index 000000000..e5770843c
--- /dev/null
+++ b/en/extensions/participation_fee/master/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/participation_fee/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "participationFeeType.csv",
+ "methodOfPayment.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/participation_fee/master/index.html b/en/extensions/participation_fee/master/index.html
new file mode 100644
index 000000000..d059d7bb3
--- /dev/null
+++ b/en/extensions/participation_fee/master/index.html
@@ -0,0 +1,373 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ methodOfPayment.csv +
+ +
+ You can download the methodOfPayment.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ cash
+
+ |
+ + Cash + | +
+ The payment is made in cash, such as banknotes and coins. + + |
+
+
+ check
+
+ |
+ + Check + | +
+ The payment is made by check (also written as "cheque"). + + |
+
+
+ creditCard
+
+ |
+ + Credit card + | +
+ The payment is made by credit card. + + |
+
+
+ directDebit
+
+ |
+ + Direct debit + | +
+ The payment is made by direct debit, also known as direct withdrawal, pre-authorized debit (PAD) or pre-authorized payment (PAP). + + |
+
+
+ letterOfCredit
+
+ |
+ + Letter of credit + | +
+ The payment is made by letter of credit. + + |
+
+
+ wireTransfer
+
+ |
+ + Wire transfer + | +
+ The payment is made by wire transfer, also known as bank transfer or credit transfer. + + |
+
+ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/master/release-schema.json b/en/extensions/participation_fee/master/release-schema.json
new file mode 100644
index 000000000..93f12e1ef
--- /dev/null
+++ b/en/extensions/participation_fee/master/release-schema.json
@@ -0,0 +1,78 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Participation fee",
+ "description": "A fee applicable to bidders wishing to participate in the tender process. Fees can apply for accessing bidding documents or for submitting bids, or there can be a \"win fee\" payable by the successful bidder.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Fee ID",
+ "description": "A local identifier for this fee, unique within this block. This field is used to keep track of multiple revisions of a fee through the compilation from release to record mechanism.",
+ "type": "string"
+ },
+ "type": {
+ "title": "Fee type",
+ "description": "The type of this fee.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win"
+ ]
+ },
+ "codelist": "participationFeeType.csv",
+ "openCodelist": false
+ },
+ "value": {
+ "title": "Value",
+ "description": "The monetary value of this fee.",
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Description",
+ "description": "Additional information about this fee, for example: the specific cases in which the fee is applicable (e.g. hard copies of documents only), the way in which the fee is levied, or the exact nature of the fee.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "methodOfPayment": {
+ "title": "Method(s) of payment",
+ "description": "The accepted ways in which fees can be paid.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ },
+ "codelist": "methodOfPayment.csv",
+ "openCodelist": true,
+ "uniqueItems": true
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Participation fees",
+ "description": "Any fees applicable to bidders wishing to participate in the tender process. Fees can apply for accessing bidding documents or for submitting bids, or there can be a \"win fee\" payable by the successful bidder.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/participation_fee/master/schema/index.html b/en/extensions/participation_fee/master/schema/index.html
new file mode 100644
index 000000000..405d241e4
--- /dev/null
+++ b/en/extensions/participation_fee/master/schema/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds a participation fees array to the tender object, to disclose any participation fees for the contracting process.
+There are sometimes costs involved in accessing bidding documents relating to a contracting process, or in otherwise participating in a contracting process. Potential bidders want to know about such fees. Procurement monitors might also want to ensure that participation fees are within legal parameters (often set as a fixed maximum value, or as a percentage of the total contract value) or to monitor how participation fees are being used.
+Guidance
+The id field will be required in future versions of the extension.
In some cases, a fee is levied for official copies of procurement documents, with unofficial copies being freely available. Bidders might be required to prove that they have paid for official copies as part of their submission. In such cases, the fee should use the 'submission' code in the type field, rather than the 'document' code.
Example
+The following JSON snippet models a contracting process where fees are applied to access bidding documents and to submit bids:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "id": "1",
+ "type": [
+ "document"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 8.0
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment": [
+ "wireTransfer",
+ "cheque"
+ ]
+ },
+ {
+ "id": "2",
+ "type": [
+ "submission"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.0
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment": [
+ "wireTransfer"
+ ]
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+Unreleased
+-
+
- Make
ParticipationFee.idrequired so that participation fees are merged by identifier
+
v1.1.5
+-
+
- Add
idfield to example in readme
+ - Fix description of
ParticipationFee.typefield
+ - Merge and reconcile field and code descriptions with schema and codelist +
- Remove indication of fields as "optional" +
- Add
methodOfPaymentcodelist from paymentMethod extension
+ - Remove type information from field descriptions +
- Review normative and non-normative words +
v1.1.4
+-
+
- Update
mergeStrategyproperty towholeListMergeproperty
+ - Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow
ParticipationFee.typefrom having null in its array of strings
+ - Allow
ParticipationFee.descriptionto be null
+ - Add
ParticipationFee.idfield
+ - Add description to
ParticipationFee
+ - Add title and description to
ParticipationFee.value
+ - Add participationFeeType.csv codelist for
ParticipationFee.type
+ - Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.1/README.md b/en/extensions/participation_fee/v1.1.1/README.md
new file mode 100644
index 000000000..7b8784558
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.1/README.md
@@ -0,0 +1,73 @@
+# Participation fees
+
+## Background
+
+There are a number of cases where there may be costs to access documents for, or to participate within, a tender process.
+
+Potential bidders will want to be aware of the fees that a process might involve.
+
+Procurement monitors may wish to ensure that participation fees are within legal parameters (often set as a fixed maximum, or a percentage of total contract value), or to monitor how participation fees are being used.
+
+## Extension fields
+
+This extension adds a `participationFees` field to the `tender` section of OCDS and introduces a new `participationFee` building block.
+
+The `participationFees` field is an array of `participationFee` building blocks.
+
+The `participationFee` building block is made up of three fields:
+
+- `type` - a value from the `participationFeeType` codelist, describing the type of the fee
+- `value` - the amount and currency of the fee
+- `description` - an optional field with more information on the fee requirements. For example, sometimes a document fee is only applicable to the hard copy of the documents.
+- `methodOfPayment` - an optional field providing information on methods of payment accepted for the documentation. This is currently an array of strings, but an open codelist may be introduced in future.
+
+## Extension codelists
+
+This extension adds **closed** `participationFeeType` codelist with the following codes:
+
+- document - a fee payable for access to bidding documents
+- deposit - a refundable fee payable for the submission of bids
+- submission - a non-refundable fee payable for the submission of bids
+- win - a fee payable by the winning bidder
+
+## Example
+
+The following JSON snippet models a contracting process where fees are applicable for both access to documents and submission of bids:
+
+```JSON
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+```
+
+## Usage notes
+
+In some cases, a fee may be levied for 'official copies' of procurement documents (although copies may also be available freely online), and bidders required to prove they have paid for an official copy of the documents as part of their submission.
+
+In this case, the fee should be modelled as a **submission** fee, as submission is only possible when this document access fee has been paid.
+
+## To do
+
+- participation / submission terminology
+- finalize codelist
diff --git a/en/extensions/participation_fee/v1.1.1/codelists/index.html b/en/extensions/participation_fee/v1.1.1/codelists/index.html
new file mode 100644
index 000000000..ae05ce081
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.1/codelists/index.html
@@ -0,0 +1,289 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Fee ID + | +
+ A local identifier for this fee, unique within this block. This field is used to keep track of multiple revisions of a fee through the compilation from release to record mechanism. + + |
+ + string + | +
+
+ type
+
+ |
+ + Fee type + | +
+ The type of this fee. + + |
+ + array of strings from closed participationFeeType codelist + | +
+
+ value
+
+ |
+ + Value + | +
+ The monetary value of this fee. + + |
+ + Value object + | +
+
+ description
+
+ |
+ + Description + | +
+ Additional information about this fee, for example: the specific cases in which the fee is applicable (e.g. hard copies of documents only), the way in which the fee is levied, or the exact nature of the fee. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Method(s) of payment + | +
+ The accepted ways in which fees can be paid. + + |
+ + array of strings from open methodOfPayment codelist + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Participation fees + | +
+ Any fees applicable to bidders wishing to participate in the tender process. Fees can apply for accessing bidding documents or for submitting bids, or there can be a "win fee" payable by the successful bidder. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.1/codelists/participationFeeType.csv b/en/extensions/participation_fee/v1.1.1/codelists/participationFeeType.csv
new file mode 100644
index 000000000..307acd1a9
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.1/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Code,Title,Description
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/en/extensions/participation_fee/v1.1.1/extension.json b/en/extensions/participation_fee/v1.1.1/extension.json
new file mode 100644
index 000000000..c6284aacc
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.1/extension.json
@@ -0,0 +1,14 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {},
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/en/extensions/participation_fee/v1.1.1/index.html b/en/extensions/participation_fee/v1.1.1/index.html
new file mode 100644
index 000000000..1f7a5edc2
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.1/index.html
@@ -0,0 +1,365 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.1/release-schema.json b/en/extensions/participation_fee/v1.1.1/release-schema.json
new file mode 100644
index 000000000..10332fdec
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.1/release-schema.json
@@ -0,0 +1,61 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Participation fee",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Fee type",
+ "description": "A fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win",
+ null
+ ]
+ }
+ },
+ "value": {
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Description",
+ "description": "Optional information about the way in which fees are levied, or the exact nature of the fees.",
+ "type": "string"
+ },
+ "methodOfPayment": {
+ "title": "Method(s) of payment",
+ "description": "Optional information about the way in which fees can be paid.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Participation fees",
+ "description": "Any fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder.",
+ "type": "array",
+ "mergeStrategy": "ocdsVersion",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/participation_fee/v1.1.1/schema/index.html b/en/extensions/participation_fee/v1.1.1/schema/index.html
new file mode 100644
index 000000000..466830b49
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.1/schema/index.html
@@ -0,0 +1,358 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Background
+There are a number of cases where there may be costs to access documents for, or to participate within, a tender process.
+Potential bidders will want to be aware of the fees that a process might involve.
+Procurement monitors may wish to ensure that participation fees are within legal parameters (often set as a fixed maximum, or a percentage of total contract value), or to monitor how participation fees are being used.
+Extension fields
+This extension adds a participationFees field to the tender section of OCDS and introduces a new participationFee building block.
The participationFees field is an array of participationFee building blocks.
The participationFee building block is made up of three fields:
-
+
type- a value from theparticipationFeeTypecodelist, describing the type of the fee
+value- the amount and currency of the fee
+description- an optional field with more information on the fee requirements. For example, sometimes a document fee is only applicable to the hard copy of the documents.
+methodOfPayment- an optional field providing information on methods of payment accepted for the documentation. This is currently an array of strings, but an open codelist may be introduced in future.
+
Extension codelists
+This extension adds closed participationFeeType codelist with the following codes:
-
+
- document - a fee payable for access to bidding documents +
- deposit - a refundable fee payable for the submission of bids +
- submission - a non-refundable fee payable for the submission of bids +
- win - a fee payable by the winning bidder +
Example
+The following JSON snippet models a contracting process where fees are applicable for both access to documents and submission of bids:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+Usage notes
+In some cases, a fee may be levied for 'official copies' of procurement documents (although copies may also be available freely online), and bidders required to prove they have paid for an official copy of the documents as part of their submission.
+In this case, the fee should be modelled as a submission fee, as submission is only possible when this document access fee has been paid.
+To do
+-
+
- participation / submission terminology +
- finalize codelist +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.3/README.md b/en/extensions/participation_fee/v1.1.3/README.md
new file mode 100644
index 000000000..ba2104889
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.3/README.md
@@ -0,0 +1,84 @@
+# Participation fees
+
+## Background
+
+There are a number of cases where there may be costs to access documents for, or to participate within, a tender process.
+
+Potential bidders will want to be aware of the fees that a process might involve.
+
+Procurement monitors may wish to ensure that participation fees are within legal parameters (often set as a fixed maximum, or a percentage of total contract value), or to monitor how participation fees are being used.
+
+## Extension fields
+
+This extension adds a `participationFees` field to the `tender` section of OCDS and introduces a new `participationFee` building block.
+
+The `participationFees` field is an array of `participationFee` building blocks.
+
+The `participationFee` building block is made up of three fields:
+
+- `type` - a value from the `participationFeeType` codelist, describing the type of the fee
+- `value` - the amount and currency of the fee
+- `description` - an optional field with more information on the fee requirements. For example, sometimes a document fee is only applicable to the hard copy of the documents.
+- `methodOfPayment` - an optional field providing information on methods of payment accepted for the documentation. This is currently an array of strings, but an open codelist may be introduced in future.
+
+## Extension codelists
+
+This extension adds **closed** `participationFeeType` codelist with the following codes:
+
+- document - a fee payable for access to bidding documents
+- deposit - a refundable fee payable for the submission of bids
+- submission - a non-refundable fee payable for the submission of bids
+- win - a fee payable by the winning bidder
+
+## Example
+
+The following JSON snippet models a contracting process where fees are applicable for both access to documents and submission of bids:
+
+```JSON
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+```
+
+## Usage notes
+
+In some cases, a fee may be levied for 'official copies' of procurement documents (although copies may also be available freely online), and bidders required to prove they have paid for an official copy of the documents as part of their submission.
+
+In this case, the fee should be modelled as a **submission** fee, as submission is only possible when this document access fee has been paid.
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.3
+
+- Disallow `ParticipationFee.type` from having null in its array of strings
+- Allow `ParticipationFee.description` to be null
+- Add `ParticipationFee.id` field
+- Add description to `ParticipationFee`
+- Add title and description to `ParticipationFee.value`
+- Add participationFeeType.csv codelist for `ParticipationFee.type`
+- Add tests and tidy code
diff --git a/en/extensions/participation_fee/v1.1.3/codelists/index.html b/en/extensions/participation_fee/v1.1.3/codelists/index.html
new file mode 100644
index 000000000..74e6134f5
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.3/codelists/index.html
@@ -0,0 +1,289 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Fee type + | +
+ A fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder. + + |
+ + array of strings + | +
+
+ value
+
+ |
+ + + | ++ + | ++ Value object + | +
+
+ description
+
+ |
+ + Description + | +
+ Optional information about the way in which fees are levied, or the exact nature of the fees. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Method(s) of payment + | +
+ Optional information about the way in which fees can be paid. + + |
+ + array of strings + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Participation fees + | +
+ Any fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.3/codelists/participationFeeType.csv b/en/extensions/participation_fee/v1.1.3/codelists/participationFeeType.csv
new file mode 100644
index 000000000..307acd1a9
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.3/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Code,Title,Description
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/en/extensions/participation_fee/v1.1.3/extension.json b/en/extensions/participation_fee/v1.1.3/extension.json
new file mode 100644
index 000000000..6dacf2629
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.3/extension.json
@@ -0,0 +1,19 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting/ocds_participationFee_extension"
+ },
+ "codelists": [
+ "participationFeeType.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/en/extensions/participation_fee/v1.1.3/index.html b/en/extensions/participation_fee/v1.1.3/index.html
new file mode 100644
index 000000000..cecbb5750
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.3/index.html
@@ -0,0 +1,378 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.3/release-schema.json b/en/extensions/participation_fee/v1.1.3/release-schema.json
new file mode 100644
index 000000000..a7425bea8
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.3/release-schema.json
@@ -0,0 +1,73 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Participation fee",
+ "description": "A fee applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Fee ID",
+ "description": "A local identifier for this fee, unique within this block. This field is used to keep track of multiple revisions of a fee through the compilation from release to record mechanism.",
+ "type": "string"
+ },
+ "type": {
+ "title": "Fee type",
+ "description": "A fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win"
+ ]
+ },
+ "codelist": "participationFeeType.csv",
+ "openCodelist": false
+ },
+ "value": {
+ "title": "Value",
+ "description": "The monetary value of this fee.",
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Description",
+ "description": "Optional information about the way in which fees are levied, or the exact nature of the fees.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "methodOfPayment": {
+ "title": "Method(s) of payment",
+ "description": "Optional information about the way in which fees can be paid.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Participation fees",
+ "description": "Any fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder.",
+ "type": "array",
+ "mergeStrategy": "ocdsVersion",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/participation_fee/v1.1.3/schema/index.html b/en/extensions/participation_fee/v1.1.3/schema/index.html
new file mode 100644
index 000000000..bdc961407
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.3/schema/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Background
+There are a number of cases where there may be costs to access documents for, or to participate within, a tender process.
+Potential bidders will want to be aware of the fees that a process might involve.
+Procurement monitors may wish to ensure that participation fees are within legal parameters (often set as a fixed maximum, or a percentage of total contract value), or to monitor how participation fees are being used.
+Extension fields
+This extension adds a participationFees field to the tender section of OCDS and introduces a new participationFee building block.
The participationFees field is an array of participationFee building blocks.
The participationFee building block is made up of three fields:
-
+
type- a value from theparticipationFeeTypecodelist, describing the type of the fee
+value- the amount and currency of the fee
+description- an optional field with more information on the fee requirements. For example, sometimes a document fee is only applicable to the hard copy of the documents.
+methodOfPayment- an optional field providing information on methods of payment accepted for the documentation. This is currently an array of strings, but an open codelist may be introduced in future.
+
Extension codelists
+This extension adds closed participationFeeType codelist with the following codes:
-
+
- document - a fee payable for access to bidding documents +
- deposit - a refundable fee payable for the submission of bids +
- submission - a non-refundable fee payable for the submission of bids +
- win - a fee payable by the winning bidder +
Example
+The following JSON snippet models a contracting process where fees are applicable for both access to documents and submission of bids:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+Usage notes
+In some cases, a fee may be levied for 'official copies' of procurement documents (although copies may also be available freely online), and bidders required to prove they have paid for an official copy of the documents as part of their submission.
+In this case, the fee should be modelled as a submission fee, as submission is only possible when this document access fee has been paid.
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.3
+-
+
- Disallow
ParticipationFee.typefrom having null in its array of strings
+ - Allow
ParticipationFee.descriptionto be null
+ - Add
ParticipationFee.idfield
+ - Add description to
ParticipationFee
+ - Add title and description to
ParticipationFee.value
+ - Add participationFeeType.csv codelist for
ParticipationFee.type
+ - Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.4/README.md b/en/extensions/participation_fee/v1.1.4/README.md
new file mode 100644
index 000000000..3c67d2d08
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.4/README.md
@@ -0,0 +1,89 @@
+# Participation fees
+
+## Background
+
+There are a number of cases where there may be costs to access documents for, or to participate within, a tender process.
+
+Potential bidders will want to be aware of the fees that a process might involve.
+
+Procurement monitors may wish to ensure that participation fees are within legal parameters (often set as a fixed maximum, or a percentage of total contract value), or to monitor how participation fees are being used.
+
+## Extension fields
+
+This extension adds a `participationFees` field to the `tender` section of OCDS and introduces a new `participationFee` building block.
+
+The `participationFees` field is an array of `participationFee` building blocks.
+
+The `participationFee` building block is made up of three fields:
+
+- `type` - a value from the `participationFeeType` codelist, describing the type of the fee
+- `value` - the amount and currency of the fee
+- `description` - an optional field with more information on the fee requirements. For example, sometimes a document fee is only applicable to the hard copy of the documents.
+- `methodOfPayment` - an optional field providing information on methods of payment accepted for the documentation. This is currently an array of strings, but an open codelist may be introduced in future.
+
+## Extension codelists
+
+This extension adds **closed** `participationFeeType` codelist with the following codes:
+
+- document - a fee payable for access to bidding documents
+- deposit - a refundable fee payable for the submission of bids
+- submission - a non-refundable fee payable for the submission of bids
+- win - a fee payable by the winning bidder
+
+## Example
+
+The following JSON snippet models a contracting process where fees are applicable for both access to documents and submission of bids:
+
+```json
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+```
+
+## Usage notes
+
+In some cases, a fee may be levied for 'official copies' of procurement documents (although copies may also be available freely online), and bidders required to prove they have paid for an official copy of the documents as part of their submission.
+
+In this case, the fee should be modelled as a **submission** fee, as submission is only possible when this document access fee has been paid.
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.4
+
+- Update `mergeStrategy` property to `wholeListMerge` property
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Disallow `ParticipationFee.type` from having null in its array of strings
+- Allow `ParticipationFee.description` to be null
+- Add `ParticipationFee.id` field
+- Add description to `ParticipationFee`
+- Add title and description to `ParticipationFee.value`
+- Add participationFeeType.csv codelist for `ParticipationFee.type`
+- Add tests and tidy code
diff --git a/en/extensions/participation_fee/v1.1.4/codelists/index.html b/en/extensions/participation_fee/v1.1.4/codelists/index.html
new file mode 100644
index 000000000..0d4d5891c
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.4/codelists/index.html
@@ -0,0 +1,289 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Fee ID + | +
+ A local identifier for this fee, unique within this block. This field is used to keep track of multiple revisions of a fee through the compilation from release to record mechanism. + + |
+ + string + | +
+
+ type
+
+ |
+ + Fee type + | +
+ A fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder. + + |
+ + array of strings from closed participationFeeType codelist + | +
+
+ value
+
+ |
+ + Value + | +
+ The monetary value of this fee. + + |
+ + Value object + | +
+
+ description
+
+ |
+ + Description + | +
+ Optional information about the way in which fees are levied, or the exact nature of the fees. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Method(s) of payment + | +
+ Optional information about the way in which fees can be paid. + + |
+ + array of strings + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Participation fees + | +
+ Any fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.4/codelists/participationFeeType.csv b/en/extensions/participation_fee/v1.1.4/codelists/participationFeeType.csv
new file mode 100644
index 000000000..307acd1a9
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.4/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Code,Title,Description
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/en/extensions/participation_fee/v1.1.4/extension.json b/en/extensions/participation_fee/v1.1.4/extension.json
new file mode 100644
index 000000000..636aa0a51
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.4/extension.json
@@ -0,0 +1,22 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/participation_fee/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "participationFeeType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/en/extensions/participation_fee/v1.1.4/index.html b/en/extensions/participation_fee/v1.1.4/index.html
new file mode 100644
index 000000000..27fb050c1
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.4/index.html
@@ -0,0 +1,383 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.4/release-schema.json b/en/extensions/participation_fee/v1.1.4/release-schema.json
new file mode 100644
index 000000000..196526cee
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.4/release-schema.json
@@ -0,0 +1,73 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Participation fee",
+ "description": "A fee applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Fee ID",
+ "description": "A local identifier for this fee, unique within this block. This field is used to keep track of multiple revisions of a fee through the compilation from release to record mechanism.",
+ "type": "string"
+ },
+ "type": {
+ "title": "Fee type",
+ "description": "A fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win"
+ ]
+ },
+ "codelist": "participationFeeType.csv",
+ "openCodelist": false
+ },
+ "value": {
+ "title": "Value",
+ "description": "The monetary value of this fee.",
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Description",
+ "description": "Optional information about the way in which fees are levied, or the exact nature of the fees.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "methodOfPayment": {
+ "title": "Method(s) of payment",
+ "description": "Optional information about the way in which fees can be paid.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Participation fees",
+ "description": "Any fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true,
+ "wholeListMerge": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/participation_fee/v1.1.4/schema/index.html b/en/extensions/participation_fee/v1.1.4/schema/index.html
new file mode 100644
index 000000000..07c7c8b80
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.4/schema/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Background
+There are a number of cases where there may be costs to access documents for, or to participate within, a tender process.
+Potential bidders will want to be aware of the fees that a process might involve.
+Procurement monitors may wish to ensure that participation fees are within legal parameters (often set as a fixed maximum, or a percentage of total contract value), or to monitor how participation fees are being used.
+Extension fields
+This extension adds a participationFees field to the tender section of OCDS and introduces a new participationFee building block.
The participationFees field is an array of participationFee building blocks.
The participationFee building block is made up of three fields:
-
+
type- a value from theparticipationFeeTypecodelist, describing the type of the fee
+value- the amount and currency of the fee
+description- an optional field with more information on the fee requirements. For example, sometimes a document fee is only applicable to the hard copy of the documents.
+methodOfPayment- an optional field providing information on methods of payment accepted for the documentation. This is currently an array of strings, but an open codelist may be introduced in future.
+
Extension codelists
+This extension adds closed participationFeeType codelist with the following codes:
-
+
- document - a fee payable for access to bidding documents +
- deposit - a refundable fee payable for the submission of bids +
- submission - a non-refundable fee payable for the submission of bids +
- win - a fee payable by the winning bidder +
Example
+The following JSON snippet models a contracting process where fees are applicable for both access to documents and submission of bids:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+Usage notes
+In some cases, a fee may be levied for 'official copies' of procurement documents (although copies may also be available freely online), and bidders required to prove they have paid for an official copy of the documents as part of their submission.
+In this case, the fee should be modelled as a submission fee, as submission is only possible when this document access fee has been paid.
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.4
+-
+
- Update
mergeStrategyproperty towholeListMergeproperty
+ - Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow
ParticipationFee.typefrom having null in its array of strings
+ - Allow
ParticipationFee.descriptionto be null
+ - Add
ParticipationFee.idfield
+ - Add description to
ParticipationFee
+ - Add title and description to
ParticipationFee.value
+ - Add participationFeeType.csv codelist for
ParticipationFee.type
+ - Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.5/README.md b/en/extensions/participation_fee/v1.1.5/README.md
new file mode 100644
index 000000000..f6d3c1ae3
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.5/README.md
@@ -0,0 +1,86 @@
+# Participation fees
+
+This extension adds a participation fees array to the tender object, to disclose any participation fees for the contracting process.
+
+The `id` field will be required in future versions of the extension.
+
+## Context
+
+There are sometimes costs involved in accessing bidding documents relating to a contracting process, or in otherwise participating in a contracting process. Potential bidders want to know about such fees. Procurement monitors might also want to ensure that participation fees are within legal parameters (often set as a fixed maximum value, or as a percentage of the total contract value) or to monitor how participation fees are being used.
+
+## Example
+
+The following JSON snippet models a contracting process where fees are applied to access bidding documents and to submit bids:
+
+```json
+{
+ "tender": {
+ "participationFees": [
+ {
+ "id": "1",
+ "type": [
+ "document"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 8.0
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment": [
+ "wireTransfer",
+ "cheque"
+ ]
+ },
+ {
+ "id": "2",
+ "type": [
+ "submission"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.0
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment": [
+ "wireTransfer"
+ ]
+ }
+ ]
+ }
+}
+```
+
+## Usage notes
+
+In some cases, a fee can be levied for 'official copies' of procurement documents (although copies can also be available freely online), and bidders might be required to prove that they have paid for an official copy of the documents as part of their submission. In this case, the fee should be modelled as a **submission** fee, as submission is only possible when this document access fee has been paid.
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.5
+
+- Add `id` field to example in readme
+- Fix description of `ParticipationFee.type` field
+- Merge and reconcile field and code descriptions with schema and codelist
+- Remove indication of fields as "optional"
+- Add `methodOfPayment` codelist from [paymentMethod extension](https://github.com/INAImexico/ocds_paymentMethod_extension/blob/master/codelists/paymentMethod.csv)
+- Remove type information from field descriptions
+- Review normative and non-normative words
+
+### v1.1.4
+
+- Update `mergeStrategy` property to `wholeListMerge` property
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Disallow `ParticipationFee.type` from having null in its array of strings
+- Allow `ParticipationFee.description` to be null
+- Add `ParticipationFee.id` field
+- Add description to `ParticipationFee`
+- Add title and description to `ParticipationFee.value`
+- Add participationFeeType.csv codelist for `ParticipationFee.type`
+- Add tests and tidy code
diff --git a/en/extensions/participation_fee/v1.1.5/codelists/index.html b/en/extensions/participation_fee/v1.1.5/codelists/index.html
new file mode 100644
index 000000000..313778153
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.5/codelists/index.html
@@ -0,0 +1,405 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Fee ID + | +
+ A local identifier for this fee, unique within this block. This field is used to keep track of multiple revisions of a fee through the compilation from release to record mechanism. + + |
+ + string + | +
+
+ type
+
+ |
+ + Fee type + | +
+ A fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder. + + |
+ + array of strings from closed participationFeeType codelist + | +
+
+ value
+
+ |
+ + Value + | +
+ The monetary value of this fee. + + |
+ + Value object + | +
+
+ description
+
+ |
+ + Description + | +
+ Optional information about the way in which fees are levied, or the exact nature of the fees. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Method(s) of payment + | +
+ Optional information about the way in which fees can be paid. + + |
+ + array of strings + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Participation fees + | +
+ Any fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.5/codelists/methodOfPayment.csv b/en/extensions/participation_fee/v1.1.5/codelists/methodOfPayment.csv
new file mode 100644
index 000000000..85a4e71fc
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.5/codelists/methodOfPayment.csv
@@ -0,0 +1,7 @@
+Code,Title,Description
+cash,Cash,"The payment is made in cash, such as banknotes and coins."
+check,Check,"The payment is made by check (also written as ""cheque"")."
+creditCard,Credit card,The payment is made by credit card.
+directDebit,Direct debit,"The payment is made by direct debit, also known as direct withdrawal, pre-authorized debit (PAD) or pre-authorized payment (PAP)."
+letterOfCredit,Letter of credit,The payment is made by letter of credit.
+wireTransfer,Wire transfer,"The payment is made by wire transfer, also known as bank transfer or credit transfer."
diff --git a/en/extensions/participation_fee/v1.1.5/codelists/participationFeeType.csv b/en/extensions/participation_fee/v1.1.5/codelists/participationFeeType.csv
new file mode 100644
index 000000000..307acd1a9
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.5/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Code,Title,Description
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/en/extensions/participation_fee/v1.1.5/extension.json b/en/extensions/participation_fee/v1.1.5/extension.json
new file mode 100644
index 000000000..e5770843c
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.5/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/participation_fee/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "participationFeeType.csv",
+ "methodOfPayment.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/participation_fee/v1.1.5/index.html b/en/extensions/participation_fee/v1.1.5/index.html
new file mode 100644
index 000000000..5579be3fa
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.5/index.html
@@ -0,0 +1,375 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ methodOfPayment.csv +
+ +
+ You can download the methodOfPayment.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ cash
+
+ |
+ + Cash + | +
+ The payment is made in cash, such as banknotes and coins. + + |
+
+
+ check
+
+ |
+ + Check + | +
+ The payment is made by check (also written as "cheque"). + + |
+
+
+ creditCard
+
+ |
+ + Credit card + | +
+ The payment is made by credit card. + + |
+
+
+ directDebit
+
+ |
+ + Direct debit + | +
+ The payment is made by direct debit, also known as direct withdrawal, pre-authorized debit (PAD) or pre-authorized payment (PAP). + + |
+
+
+ letterOfCredit
+
+ |
+ + Letter of credit + | +
+ The payment is made by letter of credit. + + |
+
+
+ wireTransfer
+
+ |
+ + Wire transfer + | +
+ The payment is made by wire transfer, also known as bank transfer or credit transfer. + + |
+
+ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1.5/release-schema.json b/en/extensions/participation_fee/v1.1.5/release-schema.json
new file mode 100644
index 000000000..c1e06f8f3
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.5/release-schema.json
@@ -0,0 +1,76 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Participation fee",
+ "description": "A fee applicable to bidders wishing to participate in the tender process. Fees can apply for accessing bidding documents or for submitting bids, or there can be a \"win fee\" payable by the successful bidder.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Fee ID",
+ "description": "A local identifier for this fee, unique within this block. This field is used to keep track of multiple revisions of a fee through the compilation from release to record mechanism.",
+ "type": "string"
+ },
+ "type": {
+ "title": "Fee type",
+ "description": "The type of this fee.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win"
+ ]
+ },
+ "codelist": "participationFeeType.csv",
+ "openCodelist": false
+ },
+ "value": {
+ "title": "Value",
+ "description": "The monetary value of this fee.",
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Description",
+ "description": "Additional information about this fee, for example: the specific cases in which the fee is applicable (e.g. hard copies of documents only), the way in which the fee is levied, or the exact nature of the fee.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "methodOfPayment": {
+ "title": "Method(s) of payment",
+ "description": "The accepted ways in which fees can be paid.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ },
+ "uniqueItems": true,
+ "codelist": "methodOfPayment.csv",
+ "openCodelist": true
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Participation fees",
+ "description": "Any fees applicable to bidders wishing to participate in the tender process. Fees can apply for accessing bidding documents or for submitting bids, or there can be a \"win fee\" payable by the successful bidder.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true,
+ "wholeListMerge": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/participation_fee/v1.1.5/schema/index.html b/en/extensions/participation_fee/v1.1.5/schema/index.html
new file mode 100644
index 000000000..e831aea92
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1.5/schema/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds a participation fees array to the tender object, to disclose any participation fees for the contracting process.
+The id field will be required in future versions of the extension.
Context
+There are sometimes costs involved in accessing bidding documents relating to a contracting process, or in otherwise participating in a contracting process. Potential bidders want to know about such fees. Procurement monitors might also want to ensure that participation fees are within legal parameters (often set as a fixed maximum value, or as a percentage of the total contract value) or to monitor how participation fees are being used.
+Example
+The following JSON snippet models a contracting process where fees are applied to access bidding documents and to submit bids:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "id": "1",
+ "type": [
+ "document"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 8.0
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment": [
+ "wireTransfer",
+ "cheque"
+ ]
+ },
+ {
+ "id": "2",
+ "type": [
+ "submission"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.0
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment": [
+ "wireTransfer"
+ ]
+ }
+ ]
+ }
+}
+Usage notes
+In some cases, a fee can be levied for 'official copies' of procurement documents (although copies can also be available freely online), and bidders might be required to prove that they have paid for an official copy of the documents as part of their submission. In this case, the fee should be modelled as a submission fee, as submission is only possible when this document access fee has been paid.
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.5
+-
+
- Add
idfield to example in readme
+ - Fix description of
ParticipationFee.typefield
+ - Merge and reconcile field and code descriptions with schema and codelist +
- Remove indication of fields as "optional" +
- Add
methodOfPaymentcodelist from paymentMethod extension
+ - Remove type information from field descriptions +
- Review normative and non-normative words +
v1.1.4
+-
+
- Update
mergeStrategyproperty towholeListMergeproperty
+ - Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Disallow
ParticipationFee.typefrom having null in its array of strings
+ - Allow
ParticipationFee.descriptionto be null
+ - Add
ParticipationFee.idfield
+ - Add description to
ParticipationFee
+ - Add title and description to
ParticipationFee.value
+ - Add participationFeeType.csv codelist for
ParticipationFee.type
+ - Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1/README.md b/en/extensions/participation_fee/v1.1/README.md
new file mode 100644
index 000000000..1cc7ffebe
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1/README.md
@@ -0,0 +1,73 @@
+# Participation fees
+
+## Background
+
+There are a number of cases where there may be costs to access documents for, or to participate within, a tender process.
+
+Potential bidders will want to be aware of the fees that a process might involve.
+
+Procurement monitors may wish to ensure that participation fees are within legal parameters (often set as a fixed maximum, or a percentage of total contract value), or to monitor how participation fees are being used.
+
+## Extension fields
+
+This extension adds a `participationFees` field to the `tender` section of OCDS and introduces a new `participationFee` building block.
+
+The `participationFees` field is an array of `participationFee` building blocks.
+
+The `participationFee` building block is made up of three fields:
+
+- `type` - a value from the `participationFeeType` codelist, describing the type of the fee
+- `value` - the amount and currency of the fee
+- `description` - an optional field with more information on the fee requirements. For example, sometimes a document fee is only applicable to the hard copy of the documents.
+- `methodOfPayment` - an optional field providing information on methods of payment accepted for the documentation. This is currently an array of strings, but an open codelist may be introduced in future.
+
+## Extension codelists
+
+This extension adds **closed** `participationFeeType` codelist with the following codes:
+
+- document - a fee payable for access to bidding documents
+- deposit - a refundable fee payable for the submission of bids
+- submission - a non-refundable fee payable for the submission of bids
+- win - a fee payable by the winning bidder
+
+## Example
+
+The following JSON snippet models a contracting process where fees are applicable for both access to documents and submission of bids:
+
+```JSON
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+```
+
+## Usage notes
+
+In some cases, a fee may be levied for 'official copies' of procurement documents (although copies may also be available freely online), and bidders required to prove they have paid for an official copy of the documents as part of their submission.
+
+In this case, the fee should be modelled as a **submission** fee, as submission is only possible when this document access fee has been paid.
+
+## To do
+
+- participation / submission terminology
+- finalise codelist
diff --git a/en/extensions/participation_fee/v1.1/codelists/index.html b/en/extensions/participation_fee/v1.1/codelists/index.html
new file mode 100644
index 000000000..f45f4df9d
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1/codelists/index.html
@@ -0,0 +1,289 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Fee ID + | +
+ A local identifier for this fee, unique within this block. This field is used to keep track of multiple revisions of a fee through the compilation from release to record mechanism. + + |
+ + string + | +
+
+ type
+
+ |
+ + Fee type + | +
+ The type of this fee. + + |
+ + array of strings from closed participationFeeType codelist + | +
+
+ value
+
+ |
+ + Value + | +
+ The monetary value of this fee. + + |
+ + Value object + | +
+
+ description
+
+ |
+ + Description + | +
+ Additional information about this fee, for example: the specific cases in which the fee is applicable (e.g. hard copies of documents only), the way in which the fee is levied, or the exact nature of the fee. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Method(s) of payment + | +
+ The accepted ways in which fees can be paid. + + |
+ + array of strings from open methodOfPayment codelist + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Participation fees + | +
+ Any fees applicable to bidders wishing to participate in the tender process. Fees can apply for accessing bidding documents or for submitting bids, or there can be a "win fee" payable by the successful bidder. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1/codelists/participationFeeType.csv b/en/extensions/participation_fee/v1.1/codelists/participationFeeType.csv
new file mode 100644
index 000000000..307acd1a9
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Code,Title,Description
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/en/extensions/participation_fee/v1.1/extension.json b/en/extensions/participation_fee/v1.1/extension.json
new file mode 100644
index 000000000..c6284aacc
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1/extension.json
@@ -0,0 +1,14 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {},
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/en/extensions/participation_fee/v1.1/index.html b/en/extensions/participation_fee/v1.1/index.html
new file mode 100644
index 000000000..d24d0e49f
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1/index.html
@@ -0,0 +1,365 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/participation_fee/v1.1/release-schema.json b/en/extensions/participation_fee/v1.1/release-schema.json
new file mode 100644
index 000000000..10332fdec
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1/release-schema.json
@@ -0,0 +1,61 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Participation fee",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Fee type",
+ "description": "A fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win",
+ null
+ ]
+ }
+ },
+ "value": {
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Description",
+ "description": "Optional information about the way in which fees are levied, or the exact nature of the fees.",
+ "type": "string"
+ },
+ "methodOfPayment": {
+ "title": "Method(s) of payment",
+ "description": "Optional information about the way in which fees can be paid.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Participation fees",
+ "description": "Any fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder.",
+ "type": "array",
+ "mergeStrategy": "ocdsVersion",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/participation_fee/v1.1/schema/index.html b/en/extensions/participation_fee/v1.1/schema/index.html
new file mode 100644
index 000000000..ddff4b9b9
--- /dev/null
+++ b/en/extensions/participation_fee/v1.1/schema/index.html
@@ -0,0 +1,358 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Background
+There are a number of cases where there may be costs to access documents for, or to participate within, a tender process.
+Potential bidders will want to be aware of the fees that a process might involve.
+Procurement monitors may wish to ensure that participation fees are within legal parameters (often set as a fixed maximum, or a percentage of total contract value), or to monitor how participation fees are being used.
+Extension fields
+This extension adds a participationFees field to the tender section of OCDS and introduces a new participationFee building block.
The participationFees field is an array of participationFee building blocks.
The participationFee building block is made up of three fields:
-
+
type- a value from theparticipationFeeTypecodelist, describing the type of the fee
+value- the amount and currency of the fee
+description- an optional field with more information on the fee requirements. For example, sometimes a document fee is only applicable to the hard copy of the documents.
+methodOfPayment- an optional field providing information on methods of payment accepted for the documentation. This is currently an array of strings, but an open codelist may be introduced in future.
+
Extension codelists
+This extension adds closed participationFeeType codelist with the following codes:
-
+
- document - a fee payable for access to bidding documents +
- deposit - a refundable fee payable for the submission of bids +
- submission - a non-refundable fee payable for the submission of bids +
- win - a fee payable by the winning bidder +
Example
+The following JSON snippet models a contracting process where fees are applicable for both access to documents and submission of bids:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+Usage notes
+In some cases, a fee may be levied for 'official copies' of procurement documents (although copies may also be available freely online), and bidders required to prove they have paid for an official copy of the documents as part of their submission.
+In this case, the fee should be modelled as a submission fee, as submission is only possible when this document access fee has been paid.
+To do
+-
+
- participation / submission terminology +
- finalise codelist +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/partyScale/index.html b/en/extensions/partyScale/index.html
new file mode 100644
index 000000000..c4a348f40
--- /dev/null
+++ b/en/extensions/partyScale/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Participation Fees +
+ ++ Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Fee type + | +
+ A fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder. + + |
+ + array of strings + | +
+
+ value
+
+ |
+ + + | ++ + | ++ Value object + | +
+
+ description
+
+ |
+ + Description + | +
+ Optional information about the way in which fees are levied, or the exact nature of the fees. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Method(s) of payment + | +
+ Optional information about the way in which fees can be paid. + + |
+ + array of strings + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Participation fees + | +
+ Any fees applicable to bidders wishing to participate in the tender process. Fees may apply for access to bidding documents, for the submission of bids or there may be a win fee payable by the successful bidder. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/partyScale/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/partyScale/master/codelists/partyScale.csv b/en/extensions/partyScale/master/codelists/partyScale.csv
new file mode 100644
index 000000000..b22073eed
--- /dev/null
+++ b/en/extensions/partyScale/master/codelists/partyScale.csv
@@ -0,0 +1,7 @@
+Code,Title,Description
+micro,Micro,"This a micro enterprise, according to the definitions used by the procuring entity or buyer."
+sme,Small or medium enterprise,"This is a Small or Medium Enterprise (SME), according to the definitions used by the procuring entity or buyer."
+small,Small,"This is a small enterprise, according to the definitions used by the procuring entity or buyer."
+medium,Medium,"This is a medium enterprise, according to the definitions used by the procuring entity or buyer."
+large,Large,"This is a large enterprise, according to the definitions used by the procuring entity or buyer."
+selfEmployed,Self-employed individual,"This is a self-employed natural person, also known as a sole trader."
diff --git a/en/extensions/partyScale/master/extension.json b/en/extensions/partyScale/master/extension.json
new file mode 100644
index 000000000..af0f1361c
--- /dev/null
+++ b/en/extensions/partyScale/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Organization scale",
+ "es": "Organization scale"
+ },
+ "description": {
+ "en": "For classifying organizations as micro, sme or large.",
+ "es": "Para clasificar organizaciones como micro, PyME or grande"
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/partyScale/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "partyScale.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/partyScale/master/index.html b/en/extensions/partyScale/master/index.html
new file mode 100644
index 000000000..8b7b93934
--- /dev/null
+++ b/en/extensions/partyScale/master/index.html
@@ -0,0 +1,332 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization scale +
+ ++ For classifying organizations as micro, sme or large. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ partyScale.csv +
+ +
+ You can download the partyScale.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ micro
+
+ |
+ + Micro + | +
+ This a micro enterprise, according to the definitions used by the procuring entity or buyer. + + |
+
+
+ sme
+
+ |
+ + Small or medium enterprise + | +
+ This is a Small or Medium Enterprise (SME), according to the definitions used by the procuring entity or buyer. + + |
+
+
+ small
+
+ |
+ + Small + | +
+ This is a small enterprise, according to the definitions used by the procuring entity or buyer. + + |
+
+
+ medium
+
+ |
+ + Medium + | +
+ This is a medium enterprise, according to the definitions used by the procuring entity or buyer. + + |
+
+
+ large
+
+ |
+ + Large + | +
+ This is a large enterprise, according to the definitions used by the procuring entity or buyer. + + |
+
+
+ selfEmployed
+
+ |
+ + Self-employed individual + | +
+ This is a self-employed natural person, also known as a sole trader. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/partyScale/master/release-schema.json b/en/extensions/partyScale/master/release-schema.json
new file mode 100644
index 000000000..14437803a
--- /dev/null
+++ b/en/extensions/partyScale/master/release-schema.json
@@ -0,0 +1,31 @@
+{
+ "definitions": {
+ "Organization": {
+ "properties": {
+ "details": {
+ "properties": {
+ "scale": {
+ "title": "Scale",
+ "description": "The size or scale of the organization.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "partyScale.csv",
+ "openCodelist": false,
+ "enum": [
+ "micro",
+ "sme",
+ "small",
+ "medium",
+ "large",
+ "selfEmployed",
+ null
+ ]
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/partyScale/master/schema/index.html b/en/extensions/partyScale/master/schema/index.html
new file mode 100644
index 000000000..bef15cfe7
--- /dev/null
+++ b/en/extensions/partyScale/master/schema/index.html
@@ -0,0 +1,255 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization scale +
+ ++ For classifying organizations as micro, sme or large. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds a scale field to the parties.details object, to indicate the size or scale of an organization, in particular commercial enterprises or economic operators.
This information can be used to calculate procurement statistics, like the share of contracts awarded to micro, small and medium-sized enterprises.
+The codes in the partyScale.csv codelist do not have precise definitions, and instead defer to local laws and regulations, for example:
Guidance
+For small and medium-sized enterprises, if you can distinguish between the two sizes, use the 'small' and 'medium' codes. Otherwise, use the 'sme' code.
+For self-employed individuals and sole traders, if you can distinguish them from micro enterprises, use the 'selfEmployed' code. Otherwise, use the 'micro' code.
+For enterprises without employees, use the 'micro' code.
+Example
+{
+ "parties": [
+ {
+ "id": "GB-COH-1234567844",
+ "name": "AnyCorp Cycle Provision",
+ "details": {
+ "scale": "sme"
+ }
+ }
+ ]
+}
+Changelog
+2020-05-20
+-
+
- Add 'selfEmployed' code to
partyScale.csv
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties
+
2020-03-11
+-
+
- Clarify use of codes +
2020-03-10
+-
+
- Add 'small' and 'medium' codes to
partyScale.csv
+
2018-05-22
+-
+
- Add description to 'large' code in
partyScale.csv
+
2018-05-21
+-
+
- Remove '' code from
partyScale.csv
+
2018-01-09
+-
+
- Add partyScale.csv codelist for
Organization.details.scale
+
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/performance_failures/index.html b/en/extensions/performance_failures/index.html
new file mode 100644
index 000000000..460dc0f89
--- /dev/null
+++ b/en/extensions/performance_failures/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization scale +
+ ++ For classifying organizations as micro, sme or large. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + Scale + | +
+ The size or scale of the organization. + + |
+ + string from closed partyScale codelist + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/performance_failures/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/performance_failures/master/release-schema.json b/en/extensions/performance_failures/master/release-schema.json
new file mode 100644
index 000000000..b9a25291f
--- /dev/null
+++ b/en/extensions/performance_failures/master/release-schema.json
@@ -0,0 +1,83 @@
+{
+ "definitions": {
+ "PerformanceFailure": {
+ "title": "Performance failure disclosure",
+ "description": "Details of the performance failures for a given period and category. Details of the associated penalties and abatements provided for in the contract, imposed and paid can also be provided.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "A local identifier for this specific category and period of performance failure. This field is used to keep track of revisions of a charge across multiple OCDS releases.",
+ "type": "string",
+ "minLength": 1
+ },
+ "period": {
+ "title": "Performance failure period",
+ "description": "The reporting period for the performance failures.",
+ "$ref": "#/definitions/Period"
+ },
+ "category": {
+ "title": "Performance failure category",
+ "description": "The category of the performance failures.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "events": {
+ "title": "Number of events",
+ "description": "The number of performance failures for this period and category.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "penaltyContracted": {
+ "title": "Contracted penalty",
+ "description": "A description of the penalty or abatement provided for in the contract for this period, category and number of performance failures.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "penaltyImposed": {
+ "title": "Penalty imposed",
+ "description": "A description of the penalty or abatement imposed for this period, category and number of performance failures.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "penaltyPaid": {
+ "title": "Penalty paid",
+ "description": "Whether the penalty imposed for this period, category and number of performance failures has been paid.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ },
+ "minProperties": 1
+ },
+ "Implementation": {
+ "properties": {
+ "performanceFailures": {
+ "title": "Performance failure disclosures",
+ "description": "An array of performance failure disclosures, detailing performance failures for different periods and categories.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/PerformanceFailure"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/performance_failures/master/schema/index.html b/en/extensions/performance_failures/master/schema/index.html
new file mode 100644
index 000000000..1935c3dfe
--- /dev/null
+++ b/en/extensions/performance_failures/master/schema/index.html
@@ -0,0 +1,384 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Performance Failures +
+ ++ Adds fields to the implementation section to allow disclosure of an array of contracting performance failures. Based on the performance failures reporting table defined in the World Bank Framework for Disclosure in PPPs. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The Framework for disclosure in Public Private Partnerships requires disclosure of instances of performance failures during the the life of a contract, along with the penalties or abatements defined, imposed and paid in relation to each category of performance failures.
+Example
+The following JSON snippet models the performance failures reported for a single period and category.
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "implementation": {
+ "performanceFailures": [
+ {
+ "id": "1",
+ "period": {
+ "startDate": "2016-01-01T00:00:00Z",
+ "endDate": "2016-12-31T23:59:59Z"
+ },
+ "category": "Daily average journey time exceeds 10 minutes",
+ "events": 73,
+ "penaltyContracted": "If the daily average journey time exceeds 10 minutes on more than 52 days per calendar year the project company will be subject to a penalty charge equal to (days - 52) * avgToll. Where days is the total number of days where the average journey time exceeded 10 minutes and avgToll is the average daily toll revenue to the project company over the calendar year in which the failures occurred.",
+ "penaltyImposed": "A penalty of £3,360,000 was imposed",
+ "penaltyPaid": true
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2019-03-20
+-
+
- Add
"minLength": 1on required string fields.
+ - Make
PerformanceFailure.periodnon-nullable (undo earlier change), given that it refers to thePeriodobject.
+
2018-05-08
+-
+
- Make
PerformanceFailure.idrequired to support revision tracking and list merging
+
2018-01-29
+-
+
- Make
PerformanceFailure.periodnullable.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/ppp/index.html b/en/extensions/ppp/index.html
new file mode 100644
index 000000000..9092ba6e7
--- /dev/null
+++ b/en/extensions/ppp/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Performance Failures +
+ ++ Adds fields to the implementation section to allow disclosure of an array of contracting performance failures. Based on the performance failures reporting table defined in the World Bank Framework for Disclosure in PPPs. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ PerformanceFailure +
+ +
+ The extension defines a new PerformanceFailure object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ A local identifier for this specific category and period of performance failure. This field is used to keep track of revisions of a charge across multiple OCDS releases. + + |
+ + string + | +
+
+ period
+
+ |
+ + Performance failure period + | +
+ The reporting period for the performance failures. + + |
+ + Period object + | +
+
+ category
+
+ |
+ + Performance failure category + | +
+ The category of the performance failures. + + |
+ + string + | +
+
+ events
+
+ |
+ + Number of events + | +
+ The number of performance failures for this period and category. + + |
+ + number + | +
+
+ penaltyContracted
+
+ |
+ + Contracted penalty + | +
+ A description of the penalty or abatement provided for in the contract for this period, category and number of performance failures. + + |
+ + string + | +
+
+ penaltyImposed
+
+ |
+ + Penalty imposed + | +
+ A description of the penalty or abatement imposed for this period, category and number of performance failures. + + |
+ + string + | +
+
+ penaltyPaid
+
+ |
+ + Penalty paid + | +
+ Whether the penalty imposed for this period, category and number of performance failures has been paid. + + |
+ + boolean + | +
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ performanceFailures
+
+ |
+ + Performance failure disclosures + | +
+ An array of performance failure disclosures, detailing performance failures for different periods and categories. + + |
+ + array of PerformanceFailure objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/ppp/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/ppp/master/codelists/metricID.csv b/en/extensions/ppp/master/codelists/metricID.csv
new file mode 100644
index 000000000..7fcdedc8d
--- /dev/null
+++ b/en/extensions/ppp/master/codelists/metricID.csv
@@ -0,0 +1,4 @@
+Code,Title,Description
+demand,Demand,For reporting on forecast or actual demand
+revenue,Revenue,For reporting on forecast or actual revenues
+IRR,Internal rate of return,For reporting on forecast or actual project IRR
diff --git a/en/extensions/ppp/master/codelists/milestoneCode.csv b/en/extensions/ppp/master/codelists/milestoneCode.csv
new file mode 100644
index 000000000..a348a7579
--- /dev/null
+++ b/en/extensions/ppp/master/codelists/milestoneCode.csv
@@ -0,0 +1,10 @@
+Code,Title,Description,Source,Notes
+projectApproval,Project approval,The dates of approvals from relevant authorities.,https://github.com/open-contracting/ocds-milestones-update,milestone/type = approval
+commercialClose,Commercial close,"In a financing, the point at which the commercial documentation has been executed but before conditions precedent have been satisfied or waived; before financial close.",https://pppknowledgelab.org/glossary#Commercial_Close,milestone/type = contractClose
+financialClose,Financial close,"In a financing, the point at which the documentation has been executed and conditions precedent have been satisfied or waived. Drawdowns become permissible after this point.",https://pppknowledgelab.org/glossary#Financial_Close,milestone/type = contractClose
+commencement,Commencement of construction or development,The date of commencement of construction or development,,milestone/type = delivery
+completion,Completion of construction of development,The date of completion of construction or development,,milestone/type = delivery
+commissioning,Commissioning,The testing and inspection of the completed works to verify that the works are ready for commercial operation.,https://pppknowledgelab.org/glossary#Commissioning,milestone/type = delivery
+enquiryPeriodStart,Enquiry period start,"For processes with multiple enquiry periods, the start date of a period during which enquiries can be made and responded to which is not provided in the tender/enquiryPeriod block. Sometimes known as clarification periods.",,milestone/type = procurement
+enquiryPeriodEnd,Enquiry period end,"For processes with multiple enquiry periods, the end date of a period during which enquiries can be made and responded to which is not provided in the tender/enquiryPeriod block. Sometimes known as clarification periods.",,milestone/type = procurement
+draftFinalTender,Submission of draft final bid,"For competitive dialogue processes, the deadline for submission of draft final bids",,milestone/type = procurement
diff --git a/en/extensions/ppp/master/extension.json b/en/extensions/ppp/master/extension.json
new file mode 100644
index 000000000..f83a3fe7a
--- /dev/null
+++ b/en/extensions/ppp/master/extension.json
@@ -0,0 +1,34 @@
+{
+ "name": {
+ "en": "OCDS for PPPs Extension",
+ "es": "Extensi\u00f3n OCDS para APPs"
+ },
+ "description": {
+ "en": "Makes changes required by the OCDS for PPPs profile. Evaluation indicators, finance summary and project details may be moved into new extensions.",
+ "es": "Realiza los cambios requeridos por el perfil de OCDS para APPs. Los indicadores de evaluaci\u00f3n, resumen financiero y detalles del proyecto podr\u00edan ser movidos a otra extensi\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/ppp/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "+milestoneType.csv",
+ "+partyRole.csv",
+ "+documentType.csv",
+ "metricID.csv",
+ "milestoneCode.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_metrics_extension/1.1/extension.json",
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_location_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/ppp/master/index.html b/en/extensions/ppp/master/index.html
new file mode 100644
index 000000000..cca978b47
--- /dev/null
+++ b/en/extensions/ppp/master/index.html
@@ -0,0 +1,402 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + OCDS for PPPs Extension +
+ ++ Makes changes required by the OCDS for PPPs profile. Evaluation indicators, finance summary and project details may be moved into new extensions. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +documentType.csv +
+ +
+ You can download the +documentType.csv file in English.
+
+ The extension adds these codes to the documentType.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ valueForMoneyAnalysis
+
+ |
+ + Value for money analysis + | +
+ A summary of the value for money analysis carried out for the project, along with supporting figures, calculations and business case, based on projected or actual procurement outcomes. + +
|
+
+
+ serviceDescription
+
+ |
+ + Service descriptions + | +
+ A high-level description of the services + +
|
+
+
+ estimatedDemand
+
+ |
+ + Estimated demand + | +
+ A narrative describing the estimated demand to be served (annually) by the project. + +
|
+
+
+ projectAdditionality
+
+ |
+ + Project additionality + | +
+ A description of the additionality provided by the project + +
|
+
+
+ financeAdditionality
+
+ |
+ + Finance additionality + | +
+ A description of the additionality provided by the finance method + +
|
+
+
+ pppModeRationale
+
+ |
+ + Rationale for PPP modality + | +
+ A description of the reasons for choosing to conduct this project as a PPP + +
|
+
+
+ evaluationCommittee
+
+ |
+ + Evaluation committee details + | +
+ Information on the constitution of the evaluation committee + +
|
+
+
+ requestForQualification
+
+ |
+ + Request for qualification + | +
+ The set of documents issued by the procuring authority that constitute the basis of the qualification and potentially the pre-selection of candidates (the short list). Qualified (or short-listed candidates) will then be invited to submit a proposal (or to enter into a new phase prior to bid submission, such as a dialogue phase or interactive phase). + +
|
+
+
+ minutes
+
+ |
+ + Minutes + | +
+ Minutes of pre-bid meetings, or other relevant meetings. + +
|
+
+
+ negotiationParameters
+
+ |
+ + Negotiation parameters + | +
+ A description of the parameters for negotiation with the preferred proponent + +
|
+
+
+ riskComparison
+
+ |
+ + Risk comparison + | +
+ Risk comparison of other financing methods + +
|
+
+
+ discountRate
+
+ |
+ + Discount rate and risk premium + | +
+ An explanation of the discount rate, and any risk premium used, including information on project-specific circumstances that justify the risk premium rate used. + +
|
+
+
+ equityTransferCaps
+
+ |
+ + Equity transfer caps + | +
+ Details of any restrictions on the transfer of equity by shareholders or other relevant participants in the project. Certain contracts provide for caps on equity transfer in different stages of the contract, especially during the construction stage and for a few years thereafter. + +
|
+
+
+ financeArrangements
+
+ |
+ + Security and step in arrangements + | +
+ Details of any rights granted to a lender to access value in the event of default by a borrower and any rights granted to a party to "step in" to the shoes of another party, for example, a right granted to a lender or public authority to take over temporarily the operation of a project in case of failure to perform by a private party. + +
|
+
+
+ guaranteeReports
+
+ |
+ + Fiscal commitments and contingent liabilities disclosure reports + | +
+ Reports detailing the fiscal commitments of the public authority to the PPP, for example known payments that need to be made if the PPP proceeds or payment commitments whose occurrence, timing and magnitude depend on some uncertain future event, outside the control of the public authority. + +
|
+
+
+ grants
+
+ |
+ + Grants + | +
+ Information on grants given to support the project. Grant information ought to detail the total value of subsidy, and/or the value of subsidy as a proportion of the overall project value, as well as providing information on the nature of the grant. For capital subsidies paid during construction of a project, or operating subsidies paid during operation, details of periodicity of grant payments, and particular grant milestones, ought to be provided. + +
|
+
+
+ servicePayments
+
+ |
+ + Service payments + | +
+ Service payments are payments made by the public authority or purchaser to the private provider for infrastructure services (applicable in some types of Public Private Partnership projects). The documentation ought to cover the total number of payments and their periodicity, as well as the methodology used for calculating payments and the indexation used. + +
|
+
+
+ landTransfer
+
+ |
+ + Land transfer + | +
+ Details of land transferred on lease or other basis by government, including details of property numbers with the quantum of land transferred, zoning information and conditions of transfer. + +
|
+
+
+ assetTransfer
+
+ |
+ + Asset transfer + | +
+ Details of asset, human resource of personnel transfers, including documentation of the conditions of transfer. + +
|
+
+
+ revenueShare
+
+ |
+ + Revenue share + | +
+ Documentation of any revenue share arrangements, including revenue share on the base-case and upside for a public private partnership project. + +
|
+
+
+ otherGovernmentSupport
+
+ |
+ + Other government support + | +
+ Documentation of any other government support, including non-complete clauses or provision for revenue shortfall loans. + +
|
+
+
+ defaultEvents
+
+ |
+ + Defaults + | +
+ Information on events of default + +
|
+
+
+ termination
+
+ |
+ + Termination + | +
+ Information on contract termination + +
|
+
+
+ handover
+
+ |
+ + Handover + | +
+ Contractual provisions for, or reporting on, handover of assets back to the state, including details of condition of assets and any other conditions of handover. + +
|
+
+
+ financialStatement
+
+ |
+ + Financial statement + | +
+ Audited financial statements of the project company + +
|
+
+
+ performanceReport
+
+ |
+ + Performance report + | +
+ Performance assessment reports + +
|
+
+ +milestoneType.csv +
+ +
+ You can download the +milestoneType.csv file in English.
+
+ The extension adds these codes to the milestoneType.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ procurement
+
+ |
+ + Procurement + | +
+ Events taking place during the procurement which are not captured by fields in core OCDS, such as additional enquiry periods or draft bid submissions in a competitive dialogue process + + |
+
+
+ contractClose
+
+ |
+ + Contract close + | +
+ Events such as commercial and financial close + +
|
+
+ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ privateParty
+
+ |
+ + Private party + | +
+ The counter party of the procuring authority in the PPP contract. A private organization that has been granted the contract to construct and operate a government asset, and that is usually created under the form of a Special Purpose Vehicle (SPV). + +
|
+
+
+ leadBank
+
+ |
+ + Lead bank + | +
+ A lead bank is a bank that oversees the arrangement of a loan syndication + + |
+
+
+ lender
+
+ |
+ + Lender + | +
+ The APMG PPP Certification Program defines lenders as "Institutions that provide lending to the project: mainly banks and institutional investors through project bonds" + + |
+
+
+ equityInvestor
+
+ |
+ + Equity investor + | +
+ The APMG PPP Certification Program defines equity investors as "Investors who finance a portion of the project’s capital expenditures (Capex), typically as share capital or subordinated debt" + + |
+
+ metricID.csv +
+ +
+ You can download the metricID.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ demand
+
+ |
+ + Demand + | +
+ For reporting on forecast or actual demand + + |
+
+
+ revenue
+
+ |
+ + Revenue + | +
+ For reporting on forecast or actual revenues + + |
+
+
+ IRR
+
+ |
+ + Internal rate of return + | +
+ For reporting on forecast or actual project IRR + + |
+
+ milestoneCode.csv +
+ +
+ You can download the milestoneCode.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ projectApproval
+
+ |
+ + Project approval + | +
+ The dates of approvals from relevant authorities. + +
|
+
+
+ commercialClose
+
+ |
+ + Commercial close + | +
+ In a financing, the point at which the commercial documentation has been executed but before conditions precedent have been satisfied or waived; before financial close. + +
|
+
+
+ financialClose
+
+ |
+ + Financial close + | +
+ In a financing, the point at which the documentation has been executed and conditions precedent have been satisfied or waived. Drawdowns become permissible after this point. + +
|
+
+
+ commencement
+
+ |
+ + Commencement of construction or development + | +
+ The date of commencement of construction or development + +
|
+
+
+ completion
+
+ |
+ + Completion of construction of development + | +
+ The date of completion of construction or development + +
|
+
+
+ commissioning
+
+ |
+ + Commissioning + | +
+ The testing and inspection of the completed works to verify that the works are ready for commercial operation. + +
|
+
+
+ enquiryPeriodStart
+
+ |
+ + Enquiry period start + | +
+ For processes with multiple enquiry periods, the start date of a period during which enquiries can be made and responded to which is not provided in the tender/enquiryPeriod block. Sometimes known as clarification periods. + +
|
+
+
+ enquiryPeriodEnd
+
+ |
+ + Enquiry period end + | +
+ For processes with multiple enquiry periods, the end date of a period during which enquiries can be made and responded to which is not provided in the tender/enquiryPeriod block. Sometimes known as clarification periods. + +
|
+
+
+ draftFinalTender
+
+ |
+ + Submission of draft final bid + | +
+ For competitive dialogue processes, the deadline for submission of draft final bids + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/ppp/master/release-schema.json b/en/extensions/ppp/master/release-schema.json
new file mode 100644
index 000000000..7de346c4f
--- /dev/null
+++ b/en/extensions/ppp/master/release-schema.json
@@ -0,0 +1,167 @@
+{
+ "definitions": {
+ "Award": {
+ "properties": {
+ "evaluationIndicators": {
+ "title": "Evaluation of PPP option",
+ "description": "Key indicators that describe how the PPP option has been evaluated by government.",
+ "$ref": "#/definitions/EvaluationIndicators"
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "financeSummary": {
+ "title": "Finance summary",
+ "description": "Key indicators that describe the financial model of the PPP.",
+ "$ref": "#/definitions/FinanceSummary"
+ }
+ }
+ },
+ "EvaluationIndicators": {
+ "title": "Evaluation indicators",
+ "description": "Key indicators that describe how the PPP option has been evaluated by government.",
+ "type": "object",
+ "properties": {
+ "riskPremium": {
+ "title": "Risk premium",
+ "description": "The risk premium used by government when evaluating the PPP option expressed as a decimal fraction (e.g. 3.2% = 0.032). An explanation of the risk premium used should be provided in the riskPremiumDetails field.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "riskPremiumDetails": {
+ "title": "Risk premium details",
+ "description": "Further details on the risk premium used including an explanation of why it was used.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "discountRate": {
+ "title": "Discount rate",
+ "description": "The discount rate used by government when evaluating the PPP option expressed as a decimal fraction (e.g. 3.2% = 0.032). Further details can be provided in the discountRateDetails field.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "discountRateDetails": {
+ "title": "Discount rate details",
+ "description": "Further details on the discount rate used.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "netPresentValue": {
+ "title": "Net present value",
+ "description": "The discounted value of an investment's cash inflows minus the discounted value of its cash outflows. Further details can be provided in the netPresentValueRateDetails field.",
+ "$ref": "#/definitions/Value"
+ },
+ "netPresentValueDetails": {
+ "title": "Net present value details",
+ "description": "Further details on the calculation of the net present value.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "FinanceSummary": {
+ "title": "Finance summary",
+ "description": "Key indicators that describe the financial model of the PPP.",
+ "type": "object",
+ "properties": {
+ "debtEquityRatio": {
+ "title": "Debt equity ratio",
+ "description": "The debt-equity ratio of the project, expressed as a decimal value. The World Bank PPPIRC defines the debt equity ratio as 'long term debt (divided by) the shareholder equity of the project company'. Also known as 'leverage' or 'gearing'. Further details on the debt equity ratio can be provided in the debtEquityRatioDetails field.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "debtEquityRatioDetails": {
+ "title": "Debt equity ratio details",
+ "description": "Further details on the calculation of the debt equity ratio.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "shareCapital": {
+ "title": "Share capital",
+ "description": "The value of the capital in the project that comes from the issue of shares. Further details on the share capital can be provided in the shareCapitalDetails field.",
+ "$ref": "#/definitions/Value"
+ },
+ "shareCapitalDetails": {
+ "title": "Share capital details",
+ "description": "Further details on the calculation of the share capital.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "subsidyRatio": {
+ "title": "Subsidy ratio",
+ "description": "Subsidy as a proportion of project value, expressed as a decimal fraction (e.g. 3.2% = 0.032). Further details of the subsidy ratio can be provided in the subsidyRatioDetails field.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "subsidyRatioDetails": {
+ "title": "Subsidy ratio details",
+ "description": "Further details on the calculation of the subsidy ratio.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "projectIRR": {
+ "title": "Project Internal Rate of Return",
+ "description": "The internal rate of return of the project, expressed as a decimal fraction (e.g. 3.2% = 0.032). The APMG PPP Certification Program defines IRR as 'The rate of return of an investment calculated from its projected cash flows. The internal rate of return (IRR) is also the discount rate that equates the present value of a future stream of cash flows to the initial investment'. Further details on the project IRR can be provided in the projectIRRDetails field.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "projectIRRDetails": {
+ "title": "Project IRR details",
+ "description": "Further details on the calculation of the project IRR.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Metric": {
+ "properties": {
+ "id": {
+ "codelist": "metricID.csv",
+ "openCodelist": true
+ }
+ }
+ },
+ "Milestone": {
+ "properties": {
+ "code": {
+ "codelist": "milestoneCode.csv",
+ "openCodelist": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/ppp/master/schema/index.html b/en/extensions/ppp/master/schema/index.html
new file mode 100644
index 000000000..ea786c389
--- /dev/null
+++ b/en/extensions/ppp/master/schema/index.html
@@ -0,0 +1,699 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + OCDS for PPPs Extension +
+ ++ Makes changes required by the OCDS for PPPs profile. Evaluation indicators, finance summary and project details may be moved into new extensions. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The Open Contracting Data Standard for Public Private Partnerships profile provides an extended Open Contracting Data Standard schema, offering a structured data model for presenting information on Public Private Partnership Projects.
+It is based on the World Bank Framework for Disclosure in Public Private Partnership Projects and was developed between May 2016 and May 2017 through a partnership between the World Bank Open Contracting team, PPP team, Open Contracting Partnership, and Open Data Services Co-operative.
+Full documentation of the profile is available at http://standard.open-contracting.org/profiles/ppp/
+The consolidated OCDS for PPPs extension can be declared in OCDS package metadata using:
+{
+ "extensions": [
+ "http://standard.open-contracting.org/profiles/ppp/extension/1__0__0__beta/extension.json"
+ ],
+ "releases": []
+}
+About PPP extensions
+OCDS for PPPs is constructed from a number of different modular extensions to OCDS, most of which can be used independently from the profile.
+This repository contains one additional extension that forms part of the OCDS for PPPs profile. This extension introduces a number of fields and building blocks that are specific to PPP disclosure against the World Bank Framework.
+PPP Specific extensions
+Evaluation Indicators
+The PPP disclosure framework calls for a number of different indicators to be reported relating to governments evaluation of a PPP project.
+The awards.evaluationIndicators section includes fields to express the value and supporting free-text details for each indicator:
-
+
- discountRate +
- riskPremium +
- netPresentValue +
Example
+"evaluationIndicators": {
+ "riskPremium": 0.0092,
+ "riskPremiumDetails": "Based on a market risk premium of 6.0% (per government guidelines) and an asset beta of 0.45 (per a sample of listed telecommunication network providers) the project risk allocation gives rise to a risk premium of 0.92%",
+ "discountRate": 0.03,
+ "discountRateDetails": "Based on the current long term public sector bond rate",
+ "netPresentValue": {
+ "amount": 118044591901.35034,
+ "currency": "USD"
+ }
+Finance Summary
+The PPP disclosure framework calls for a number of different indicators relating to the financial model of a PPP project. Whilst some of these may be reported as metrics on an ongoing basis, some are simple single values.
+The contracts.financeSummary section includes fields to express the value and supporting free-text details for each indicator:
-
+
- debtEquityRatio +
- shareCapital +
- subsidyRatio +
- projectIRR +
Example
+"financeSummary": {
+ "debtEquityRatio": 2.05,
+ "debtEquityRatioDetails": "Until the target population coverage is reached mega Consortium must comply with a contribution of capital of at least 30% of the total value of the company",
+ "shareCapital": {
+ "amount": 20000000,
+ "currency": "USD"
+ }
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-06-07
+-
+
- Remove unused
+partyRole.csvcodes: +-
+
- consortiaMember +
- grantor +
- notary +
- otherWitness +
- socialWitness +
+
2021-04-19
+-
+
- Replace
documentType.csvwith+documentType.csv, which adds new codes instead of replacing the codelist.
+
2021-02-15
+-
+
- Restore 'procuringEntity', 'tenderer' and 'funder' roles. Remove 'bidder' role. +
2021-01-14
+-
+
- Remove
+releaseTag.csvcodelist.
+
2021-01-11
+-
+
- Remove
initiationType.csvcodelist.
+ - Restore
buyerandawards.suppliersfields.
+
2020-11-16
+-
+
- Restore deprecated fields. +
- Restore
Budget.projectandBudget.projectIDfields.
+
2020-06-04
+-
+
- Review normative and non-normative words. +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2019-05-01
+-
+
- Remove 'qualifiedBidder' and 'disqualifiedBidder' codes from
+partyRole.csv(moved to qualification extension).
+
2019-03-20
+-
+
- Set
"uniqueItems": trueon array fields.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/procedure/index.html b/en/extensions/procedure/index.html
new file mode 100644
index 000000000..ebd354610
--- /dev/null
+++ b/en/extensions/procedure/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + OCDS for PPPs Extension +
+ ++ Makes changes required by the OCDS for PPPs profile. Evaluation indicators, finance summary and project details may be moved into new extensions. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ evaluationIndicators
+
+ |
+ + Evaluation of PPP option + | +
+ Key indicators that describe how the PPP option has been evaluated by government. + + |
+ + EvaluationIndicators object + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ financeSummary
+
+ |
+ + Finance summary + | +
+ Key indicators that describe the financial model of the PPP. + + |
+ + FinanceSummary object + | +
+ EvaluationIndicators +
+ +
+ The extension defines a new EvaluationIndicators object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ riskPremium
+
+ |
+ + Risk premium + | +
+ The risk premium used by government when evaluating the PPP option expressed as a decimal fraction (e.g. 3.2% = 0.032). An explanation of the risk premium used should be provided in the riskPremiumDetails field. + + |
+ + number + | +
+
+ riskPremiumDetails
+
+ |
+ + Risk premium details + | +
+ Further details on the risk premium used including an explanation of why it was used. + + |
+ + string + | +
+
+ discountRate
+
+ |
+ + Discount rate + | +
+ The discount rate used by government when evaluating the PPP option expressed as a decimal fraction (e.g. 3.2% = 0.032). Further details can be provided in the discountRateDetails field. + + |
+ + number + | +
+
+ discountRateDetails
+
+ |
+ + Discount rate details + | +
+ Further details on the discount rate used. + + |
+ + string + | +
+
+ netPresentValue
+
+ |
+ + Net present value + | +
+ The discounted value of an investment's cash inflows minus the discounted value of its cash outflows. Further details can be provided in the netPresentValueRateDetails field. + + |
+ + Value object + | +
+
+ netPresentValueDetails
+
+ |
+ + Net present value details + | +
+ Further details on the calculation of the net present value. + + |
+ + string + | +
+ FinanceSummary +
+ +
+ The extension defines a new FinanceSummary object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ debtEquityRatio
+
+ |
+ + Debt equity ratio + | +
+ The debt-equity ratio of the project, expressed as a decimal value. The World Bank PPPIRC defines the debt equity ratio as 'long term debt (divided by) the shareholder equity of the project company'. Also known as 'leverage' or 'gearing'. Further details on the debt equity ratio can be provided in the debtEquityRatioDetails field. + + |
+ + number + | +
+
+ debtEquityRatioDetails
+
+ |
+ + Debt equity ratio details + | +
+ Further details on the calculation of the debt equity ratio. + + |
+ + string + | +
+
+ shareCapital
+
+ |
+ + Share capital + | +
+ The value of the capital in the project that comes from the issue of shares. Further details on the share capital can be provided in the shareCapitalDetails field. + + |
+ + Value object + | +
+
+ shareCapitalDetails
+
+ |
+ + Share capital details + | +
+ Further details on the calculation of the share capital. + + |
+ + string + | +
+
+ subsidyRatio
+
+ |
+ + Subsidy ratio + | +
+ Subsidy as a proportion of project value, expressed as a decimal fraction (e.g. 3.2% = 0.032). Further details of the subsidy ratio can be provided in the subsidyRatioDetails field. + + |
+ + number + | +
+
+ subsidyRatioDetails
+
+ |
+ + Subsidy ratio details + | +
+ Further details on the calculation of the subsidy ratio. + + |
+ + string + | +
+
+ projectIRR
+
+ |
+ + Project Internal Rate of Return + | +
+ The internal rate of return of the project, expressed as a decimal fraction (e.g. 3.2% = 0.032). The APMG PPP Certification Program defines IRR as 'The rate of return of an investment calculated from its projected cash flows. The internal rate of return (IRR) is also the discount rate that equates the present value of a future stream of cash flows to the initial investment'. Further details on the project IRR can be provided in the projectIRRDetails field. + + |
+ + number + | +
+
+ projectIRRDetails
+
+ |
+ + Project IRR details + | +
+ Further details on the calculation of the project IRR. + + |
+ + string + | +
+ Metric +
+ +
+ The extension defines these fields in the Metric object from the Metrics extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ code
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/procedure/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/procedure/master/release-schema.json b/en/extensions/procedure/master/release-schema.json
new file mode 100644
index 000000000..23cc7452b
--- /dev/null
+++ b/en/extensions/procedure/master/release-schema.json
@@ -0,0 +1,47 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "procedure": {
+ "title": "Procedure",
+ "description": "Information about the procurement procedure.",
+ "$ref": "#/definitions/Procedure"
+ }
+ }
+ },
+ "Procedure": {
+ "title": "Procedure",
+ "description": "Information about the procurement procedure.",
+ "type": "object",
+ "properties": {
+ "isAccelerated": {
+ "title": "Accelerated procedure used",
+ "description": "Whether the time limit for receipt of bids or requests to participate can be reduced due to a state of urgency.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "acceleratedRationale": {
+ "title": "Accelerated procedure rationale",
+ "description": "The justification for using an accelerated procedure.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "features": {
+ "title": "Features",
+ "description": "The main features of the procedure (e.g. description of the individual stages) and information about where the full rules for the procedure can be found.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/procedure/master/schema/index.html b/en/extensions/procedure/master/schema/index.html
new file mode 100644
index 000000000..6696f68e6
--- /dev/null
+++ b/en/extensions/procedure/master/schema/index.html
@@ -0,0 +1,316 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Procedure +
+ ++ This extension adds a block to describe the procurement procedure. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds a block to describe the procurement procedure.
+Legal context
+In the European Union, this extension's fields correspond to eForms BT-88, BT-106, BT-1351 and Article 93 and 45(3) of Directive 2014/25/EU. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+{
+ "tender": {
+ "procedure": {
+ "isAccelerated": true,
+ "acceleratedRationale": "The medicinal product is of major public health interest particularly from the point of view of therapeutic innovation.",
+ "features": "http://www.legislation.gov.uk/uksi/2015/102/pdfs/uksi_20150102_en.pdf"
+ }
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile, in pull requests and in https://github.com/open-contracting/standard/issues/695.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/process_title/index.html b/en/extensions/process_title/index.html
new file mode 100644
index 000000000..3d024cb1d
--- /dev/null
+++ b/en/extensions/process_title/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Procedure +
+ ++ This extension adds a block to describe the procurement procedure. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ procedure
+
+ |
+ + Procedure + | +
+ Information about the procurement procedure. + + |
+ + Procedure object + | +
+ Procedure +
+ +
+ The extension defines a new Procedure object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ isAccelerated
+
+ |
+ + Accelerated procedure used + | +
+ Whether the time limit for receipt of bids or requests to participate can be reduced due to a state of urgency. + + |
+ + boolean + | +
+
+ acceleratedRationale
+
+ |
+ + Accelerated procedure rationale + | +
+ The justification for using an accelerated procedure. + + |
+ + string + | +
+
+ features
+
+ |
+ + Features + | +
+ The main features of the procedure (e.g. description of the individual stages) and information about where the full rules for the procedure can be found. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/process_title/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/process_title/master/release-schema.json b/en/extensions/process_title/master/release-schema.json
new file mode 100644
index 000000000..beb33c926
--- /dev/null
+++ b/en/extensions/process_title/master/release-schema.json
@@ -0,0 +1,20 @@
+{
+ "properties": {
+ "title": {
+ "title": "Title",
+ "description": "A overall title for this contracting process or release.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Description",
+ "description": "An overall description of this contracting process or release. This does not replace a detailed breakdown of the objects of the contracting process in the planning, tender, award or contracts section.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+}
diff --git a/en/extensions/process_title/master/schema/index.html b/en/extensions/process_title/master/schema/index.html
new file mode 100644
index 000000000..df4cbef47
--- /dev/null
+++ b/en/extensions/process_title/master/schema/index.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Process level title and description +
+ ++ For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In some cases it is important to provide an overall title and description for a contracting process, distinct from the individual title and description fields contained within tender, awards and contracts sections.
This extension adds title and description fields to the release schema.
These will often be used to provide a human-readable summary of information that is provided elsewhere in the OCDS document as structured data.
+Publishers using these fields ought to be aware that not all applications will display their contents, and so key information for understanding the nature of the contracting process ought to also be provided using core OCDS fields.
+Example
+{
+ "title": "Next-Generation Telecommunications PPP",
+ "description": "The Next-Generation Telecommunications PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators. The project will increase the telecommunication services coverage, promote competitive prices and enhance the quality of services according to international standards."
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.5
+-
+
- Review normative and non-normative words +
v1.1.4
+-
+
- Add example to readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/process_title/v1.1.3/README.md b/en/extensions/process_title/v1.1.3/README.md
new file mode 100644
index 000000000..840891d7f
--- /dev/null
+++ b/en/extensions/process_title/v1.1.3/README.md
@@ -0,0 +1,20 @@
+# Process title and description
+
+In some cases it is important to provide an overall title and description for a contracting process, distinct from the individual title and description fields contained within `tender`, `award` and `contract` blocks.
+
+This extension provides `release.title` and `release.description` fields.
+
+These will often be used to provide a human-readable summary of information that is provided elsewhere in the OCDS document as structured data.
+
+Publishers using these fields should be aware that not all applications will display their contents, and so key information for understanding the nature of the contracting process should generally **also** be provided using core OCDS fields.
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.3
+
+- Use Apache 2.0 License
+- Add tests and tidy code
diff --git a/en/extensions/process_title/v1.1.3/extension.json b/en/extensions/process_title/v1.1.3/extension.json
new file mode 100644
index 000000000..294f96c48
--- /dev/null
+++ b/en/extensions/process_title/v1.1.3/extension.json
@@ -0,0 +1,16 @@
+{
+ "name": {
+ "en": "Process level title and description",
+ "es": "T\u00edtulo y descripci\u00f3n del nivel del proceso"
+ },
+ "description": {
+ "en": "For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole.",
+ "es": "Para proporcionar t\u00edtulos y descripciones del proceso en general, a menudo para dar un resumen de texto libre del proceso de contrataci\u00f3n como un todo."
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting/ocds_process_title_extension"
+ }
+}
diff --git a/en/extensions/process_title/v1.1.3/index.html b/en/extensions/process_title/v1.1.3/index.html
new file mode 100644
index 000000000..111b07176
--- /dev/null
+++ b/en/extensions/process_title/v1.1.3/index.html
@@ -0,0 +1,287 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Process level title and description +
+ ++ For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Title + | +
+ A overall title for this contracting process or release. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ An overall description of this contracting process or release. This does not replace a detailed breakdown of the objects of the contracting process in the planning, tender, award or contracts section. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/process_title/v1.1.3/release-schema.json b/en/extensions/process_title/v1.1.3/release-schema.json
new file mode 100644
index 000000000..893ef9f1d
--- /dev/null
+++ b/en/extensions/process_title/v1.1.3/release-schema.json
@@ -0,0 +1,20 @@
+{
+ "properties": {
+ "title": {
+ "title": "Title",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "A overall title for this contracting process or release."
+ },
+ "description": {
+ "title": "Description",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "An overall description for this contracting process or release. This should not replace provision of a detailed breakdown of the objects of the contracting process in the planning, tender, award or contracts section."
+ }
+ }
+}
diff --git a/en/extensions/process_title/v1.1.3/schema/index.html b/en/extensions/process_title/v1.1.3/schema/index.html
new file mode 100644
index 000000000..19856782c
--- /dev/null
+++ b/en/extensions/process_title/v1.1.3/schema/index.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Process level title and description +
+ ++ For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In some cases it is important to provide an overall title and description for a contracting process, distinct from the individual title and description fields contained within tender, award and contract blocks.
This extension provides release.title and release.description fields.
These will often be used to provide a human-readable summary of information that is provided elsewhere in the OCDS document as structured data.
+Publishers using these fields should be aware that not all applications will display their contents, and so key information for understanding the nature of the contracting process should generally also be provided using core OCDS fields.
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.3
+-
+
- Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/process_title/v1.1.4/README.md b/en/extensions/process_title/v1.1.4/README.md
new file mode 100644
index 000000000..f01e123d5
--- /dev/null
+++ b/en/extensions/process_title/v1.1.4/README.md
@@ -0,0 +1,34 @@
+# Process title and description
+
+In some cases it is important to provide an overall title and description for a contracting process, distinct from the individual title and description fields contained within `tender`, `award` and `contract` blocks.
+
+This extension adds `title` and `description` fields to the release schema.
+
+These will often be used to provide a human-readable summary of information that is provided elsewhere in the OCDS document as structured data.
+
+Publishers using these fields should be aware that not all applications will display their contents, and so key information for understanding the nature of the contracting process should generally **also** be provided using core OCDS fields.
+
+## Example
+
+```json
+{
+ "title": "Next-Generation Telecommunications PPP",
+ "description": "The Next-Generation Telecommunications PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators. The project will increase the telecommunication services coverage, promote competitive prices and enhance the quality of services according to international standards."
+}
+```
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.4
+
+- Add example to readme
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Use Apache 2.0 License
+- Add tests and tidy code
diff --git a/en/extensions/process_title/v1.1.4/extension.json b/en/extensions/process_title/v1.1.4/extension.json
new file mode 100644
index 000000000..0a06b344a
--- /dev/null
+++ b/en/extensions/process_title/v1.1.4/extension.json
@@ -0,0 +1,19 @@
+{
+ "name": {
+ "en": "Process level title and description",
+ "es": "T\u00edtulo y descripci\u00f3n del nivel del proceso"
+ },
+ "description": {
+ "en": "For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole.",
+ "es": "Para proporcionar t\u00edtulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contrataci\u00f3n como un todo."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/process_title/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/en/extensions/process_title/v1.1.4/index.html b/en/extensions/process_title/v1.1.4/index.html
new file mode 100644
index 000000000..6a4461873
--- /dev/null
+++ b/en/extensions/process_title/v1.1.4/index.html
@@ -0,0 +1,303 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Process level title and description +
+ ++ For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Title + | +
+ A overall title for this contracting process or release. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ An overall description for this contracting process or release. This should not replace provision of a detailed breakdown of the objects of the contracting process in the planning, tender, award or contracts section. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/process_title/v1.1.4/release-schema.json b/en/extensions/process_title/v1.1.4/release-schema.json
new file mode 100644
index 000000000..893ef9f1d
--- /dev/null
+++ b/en/extensions/process_title/v1.1.4/release-schema.json
@@ -0,0 +1,20 @@
+{
+ "properties": {
+ "title": {
+ "title": "Title",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "A overall title for this contracting process or release."
+ },
+ "description": {
+ "title": "Description",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "An overall description for this contracting process or release. This should not replace provision of a detailed breakdown of the objects of the contracting process in the planning, tender, award or contracts section."
+ }
+ }
+}
diff --git a/en/extensions/process_title/v1.1.4/schema/index.html b/en/extensions/process_title/v1.1.4/schema/index.html
new file mode 100644
index 000000000..981e7c179
--- /dev/null
+++ b/en/extensions/process_title/v1.1.4/schema/index.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Process level title and description +
+ ++ For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In some cases it is important to provide an overall title and description for a contracting process, distinct from the individual title and description fields contained within tender, award and contract blocks.
This extension adds title and description fields to the release schema.
These will often be used to provide a human-readable summary of information that is provided elsewhere in the OCDS document as structured data.
+Publishers using these fields should be aware that not all applications will display their contents, and so key information for understanding the nature of the contracting process should generally also be provided using core OCDS fields.
+Example
+{
+ "title": "Next-Generation Telecommunications PPP",
+ "description": "The Next-Generation Telecommunications PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators. The project will increase the telecommunication services coverage, promote competitive prices and enhance the quality of services according to international standards."
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.4
+-
+
- Add example to readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/process_title/v1.1.5/README.md b/en/extensions/process_title/v1.1.5/README.md
new file mode 100644
index 000000000..b7233896a
--- /dev/null
+++ b/en/extensions/process_title/v1.1.5/README.md
@@ -0,0 +1,38 @@
+# Process title and description
+
+In some cases it is important to provide an overall title and description for a contracting process, distinct from the individual title and description fields contained within `tender`, `awards` and `contracts` sections.
+
+This extension adds `title` and `description` fields to the release schema.
+
+These will often be used to provide a human-readable summary of information that is provided elsewhere in the OCDS document as structured data.
+
+Publishers using these fields ought to be aware that not all applications will display their contents, and so key information for understanding the nature of the contracting process ought to also be provided using core OCDS fields.
+
+## Example
+
+```json
+{
+ "title": "Next-Generation Telecommunications PPP",
+ "description": "The Next-Generation Telecommunications PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators. The project will increase the telecommunication services coverage, promote competitive prices and enhance the quality of services according to international standards."
+}
+```
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### v1.1.5
+
+- Review normative and non-normative words
+
+### v1.1.4
+
+- Add example to readme
+- Update extension.json for Extension Explorer
+
+### v1.1.3
+
+- Use Apache 2.0 License
+- Add tests and tidy code
diff --git a/en/extensions/process_title/v1.1.5/extension.json b/en/extensions/process_title/v1.1.5/extension.json
new file mode 100644
index 000000000..07e317e58
--- /dev/null
+++ b/en/extensions/process_title/v1.1.5/extension.json
@@ -0,0 +1,23 @@
+{
+ "name": {
+ "en": "Process level title and description",
+ "es": "T\u00edtulo y descripci\u00f3n del nivel del proceso"
+ },
+ "description": {
+ "en": "For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole.",
+ "es": "Para proporcionar t\u00edtulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contrataci\u00f3n como un todo."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/process_title/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/process_title/v1.1.5/index.html b/en/extensions/process_title/v1.1.5/index.html
new file mode 100644
index 000000000..a6b74c85f
--- /dev/null
+++ b/en/extensions/process_title/v1.1.5/index.html
@@ -0,0 +1,307 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Process level title and description +
+ ++ For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Title + | +
+ A overall title for this contracting process or release. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ An overall description for this contracting process or release. This should not replace provision of a detailed breakdown of the objects of the contracting process in the planning, tender, award or contracts section. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/process_title/v1.1.5/release-schema.json b/en/extensions/process_title/v1.1.5/release-schema.json
new file mode 100644
index 000000000..72785372f
--- /dev/null
+++ b/en/extensions/process_title/v1.1.5/release-schema.json
@@ -0,0 +1,20 @@
+{
+ "properties": {
+ "title": {
+ "title": "Title",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "A overall title for this contracting process or release."
+ },
+ "description": {
+ "title": "Description",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "An overall description of this contracting process or release. This does not replace a detailed breakdown of the objects of the contracting process in the planning, tender, award or contracts section."
+ }
+ }
+}
diff --git a/en/extensions/process_title/v1.1.5/schema/index.html b/en/extensions/process_title/v1.1.5/schema/index.html
new file mode 100644
index 000000000..656a95fe2
--- /dev/null
+++ b/en/extensions/process_title/v1.1.5/schema/index.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Process level title and description +
+ ++ For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In some cases it is important to provide an overall title and description for a contracting process, distinct from the individual title and description fields contained within tender, awards and contracts sections.
This extension adds title and description fields to the release schema.
These will often be used to provide a human-readable summary of information that is provided elsewhere in the OCDS document as structured data.
+Publishers using these fields ought to be aware that not all applications will display their contents, and so key information for understanding the nature of the contracting process ought to also be provided using core OCDS fields.
+Example
+{
+ "title": "Next-Generation Telecommunications PPP",
+ "description": "The Next-Generation Telecommunications PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators. The project will increase the telecommunication services coverage, promote competitive prices and enhance the quality of services according to international standards."
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+v1.1.5
+-
+
- Review normative and non-normative words +
v1.1.4
+-
+
- Add example to readme +
- Update extension.json for Extension Explorer +
v1.1.3
+-
+
- Use Apache 2.0 License +
- Add tests and tidy code +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/procurementMethodRationaleClassifications/index.html b/en/extensions/procurementMethodRationaleClassifications/index.html
new file mode 100644
index 000000000..4b6b24b76
--- /dev/null
+++ b/en/extensions/procurementMethodRationaleClassifications/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Process level title and description +
+ ++ For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Title + | +
+ A overall title for this contracting process or release. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ An overall description of this contracting process or release. This does not replace a detailed breakdown of the objects of the contracting process in the planning, tender, award or contracts section. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/procurementMethodRationaleClassifications/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/procurementMethodRationaleClassifications/master/extension.json b/en/extensions/procurementMethodRationaleClassifications/master/extension.json
new file mode 100644
index 000000000..9475271cc
--- /dev/null
+++ b/en/extensions/procurementMethodRationaleClassifications/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Procurement method rationale classifications",
+ "es": "Clasificaciones de los fundamentos de m\u00e9todos de contrataci\u00f3n"
+ },
+ "description": {
+ "en": "Adds an array to the tender object to classify the procurement method rationale.",
+ "es": "Agregar una lista al objeto de licitaci\u00f3n para clasificar la justificaci\u00f3n del m\u00e9todo de contrataci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/procurementMethodRationaleClassifications/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+itemClassificationScheme.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/procurementMethodRationaleClassifications/master/index.html b/en/extensions/procurementMethodRationaleClassifications/master/index.html
new file mode 100644
index 000000000..f1734fcdc
--- /dev/null
+++ b/en/extensions/procurementMethodRationaleClassifications/master/index.html
@@ -0,0 +1,310 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Procurement method rationale classifications +
+ ++ Adds an array to the tender object to classify the procurement method rationale. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ TED_PT_AWARD_CONTRACT_WITHOUT_CALL
+
+ |
+ + European Union direct award justification (TED schema) + | +
+ Justification for using a procedure which allows awarding contracts directly without the requirement of publishing a call for competition in the Official Journal of the European Union. This scheme's codes match those in the TED schema. + +
|
+
+
+ eforms-direct-award-justification
+
+ |
+ + European Union direct award justification (eForms) + | +
+ Justification for using a procedure which allows awarding contracts directly without the requirement of publishing a call for competition in the Official Journal of the European Union. This scheme's codes match those in eForms. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/procurementMethodRationaleClassifications/master/release-schema.json b/en/extensions/procurementMethodRationaleClassifications/master/release-schema.json
new file mode 100644
index 000000000..baff241ca
--- /dev/null
+++ b/en/extensions/procurementMethodRationaleClassifications/master/release-schema.json
@@ -0,0 +1,19 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "procurementMethodRationaleClassifications": {
+ "title": "Procurement method rationale classifications",
+ "description": "The classifications of the procurement method rationale.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/procurementMethodRationaleClassifications/master/schema/index.html b/en/extensions/procurementMethodRationaleClassifications/master/schema/index.html
new file mode 100644
index 000000000..7c2451363
--- /dev/null
+++ b/en/extensions/procurementMethodRationaleClassifications/master/schema/index.html
@@ -0,0 +1,236 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Procurement method rationale classifications +
+ ++ Adds an array to the tender object to classify the procurement method rationale. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an array to the tender object to classify the procurement method rationale.
+Legal context
+In the European Union, this extension's fields correspond to eForms BT-136 (Direct Award Justification Code). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+{
+ "tender": {
+ "procurementMethodRationaleClassifications": [
+ {
+ "id": "D_NO_TENDERS_REQUESTS",
+ "description": "No tenders or no suitable tenders/requests to participate in response to a procedure with prior call for competition",
+ "scheme": "TED_PT_AWARD_CONTRACT_WITHOUT_CALL"
+ },
+ {
+ "id": "D_FROM_LIQUIDATOR_CREDITOR",
+ "description": "Purchase of supplies or services on particularly advantageous terms from the liquidator in an insolvency procedure, an arrangement with creditors or a similar procedure under national laws and regulations",
+ "scheme": "TED_PT_AWARD_CONTRACT_WITHOUT_CALL"
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-04-05
+-
+
- Add 'eforms-direct-award-justification' to the
+itemClassificationScheme.csvcodelist.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/project/index.html b/en/extensions/project/index.html
new file mode 100644
index 000000000..a53ed28dc
--- /dev/null
+++ b/en/extensions/project/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Procurement method rationale classifications +
+ ++ Adds an array to the tender object to classify the procurement method rationale. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ procurementMethodRationaleClassifications
+
+ |
+ + Procurement method rationale classifications + | +
+ The classifications of the procurement method rationale. + + |
+ + array of Classification objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/project/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/project/master/release-schema.json b/en/extensions/project/master/release-schema.json
new file mode 100644
index 000000000..393a661cf
--- /dev/null
+++ b/en/extensions/project/master/release-schema.json
@@ -0,0 +1,105 @@
+{
+ "definitions": {
+ "Planning": {
+ "properties": {
+ "project": {
+ "title": "Project information",
+ "description": "The project section can be used to describe the relationship between this contracting process and a project or programme of work.",
+ "$ref": "#/definitions/Project"
+ }
+ }
+ },
+ "Project": {
+ "title": "Project information",
+ "description": "A project or programme of work.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Project identifier",
+ "description": "An externally provided identifier for the project. This might be drawn from a projects register, or may be based on the canonical version of a project name. Project IDs should be unique to a publisher. URIs can be used.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "title": {
+ "title": "Project title",
+ "description": "The name of the project to which this contracting process relates. Some organizations maintain a registry of projects, and the data should use the name by which the project is known in that registry.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Project description",
+ "description": "A short free text description of the project.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "totalValue": {
+ "title": "Total project value",
+ "description": "The total anticipated value of the project over it's lifetime.",
+ "$ref": "#/definitions/Value"
+ },
+ "uri": {
+ "title": "Linked project information",
+ "description": "A URI pointing to further information about this project.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "sector": {
+ "title": "Project sector",
+ "description": "A high-level categorization of the main sector this procurement process relates to. Use of [UN COFOG codes](https://unstats.un.org/unsd/publications/catalogue?selectID=145), with 'COFOG' as the classification scheme, and the numerical COFOG code is recommended for the primary sector classification.",
+ "$ref": "#/definitions/Classification"
+ },
+ "additionalClassifications": {
+ "title": "Additional sector classifications",
+ "description": "Additional project classification, by other sector classifications, or using other classification schemes (e.g. against a strategic framework).",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "locations": {
+ "title": "Project location",
+ "description": "Information about the location where a project is taking place.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Location"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "patternProperties": {
+ "^(description_(((([A-Za-z]{2,3}(-([A-Za-z]{3}(-[A-Za-z]{3}){0,2}))?)|[A-Za-z]{4}|[A-Za-z]{5,8})(-([A-Za-z]{4}))?(-([A-Za-z]{2}|[0-9]{3}))?(-([A-Za-z0-9]{5,8}|[0-9][A-Za-z0-9]{3}))*(-([0-9A-WY-Za-wy-z](-[A-Za-z0-9]{2,8})+))*(-(x(-[A-Za-z0-9]{1,8})+))?)|(x(-[A-Za-z0-9]{1,8})+)))$": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "^(title_(((([A-Za-z]{2,3}(-([A-Za-z]{3}(-[A-Za-z]{3}){0,2}))?)|[A-Za-z]{4}|[A-Za-z]{5,8})(-([A-Za-z]{4}))?(-([A-Za-z]{2}|[0-9]{3}))?(-([A-Za-z0-9]{5,8}|[0-9][A-Za-z0-9]{3}))*(-([0-9A-WY-Za-wy-z](-[A-Za-z0-9]{2,8})+))*(-(x(-[A-Za-z0-9]{1,8})+))?)|(x(-[A-Za-z0-9]{1,8})+)))$": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/project/master/schema/index.html b/en/extensions/project/master/schema/index.html
new file mode 100644
index 000000000..23c60560b
--- /dev/null
+++ b/en/extensions/project/master/schema/index.html
@@ -0,0 +1,407 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Project +
+ ++ Adds a project object to the planning object to describe the project to which the contracting process is related, including the total value of the project (not to be confused with the total value of the contracting process). +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds a project object to the planning object.
In OCDS, project information is nested under the planning.budget object. However, in some cases, budget management systems and project management systems are separate, and it might be important to separately specify:
-
+
- The amount reserved in the budget for a specific contracting process +
- The project the contract relates to, and the total value of that project +
- Sector classifications +
- Additional classifications +
- Project locations, with options for gazetteer or point locations +
This is particularly important in cases of Public-Private Partnerships and large infrastructure projects, where users might want to track all the contracting processes related to the large-scale project, and to understand the individual contracts in the context of their contracting process and overall project values.
+This extension must be used with the Location extension.
+Examples
+Infrastructure project
+{
+ "planning": {
+ "project": {
+ "id": "oc4ids-gx3fo2-000002",
+ "title": "Construcción de red de drenaje sanitario en diversas calles de la colonia Ruperto Martínez",
+ "description": "Construcción de red de drenaje sanitario consistente en excavación de 756 metros cúbicos para alojar la red de drenaje sanitario, suministro y colocación de 712 metros de tubería PVC tipo serie 20 pared solida, construcción de 15 pozos de visita y 30 descargas domiciliarias sencillas en la colonia Ruperto Martinez, en el municipio de Higueras, N.L.",
+ "totalValue": {
+ "amount": 4010130.1,
+ "currency": "MXN"
+ },
+ "locations": [
+ {
+ "description": "Col. Ruperto Martínez, Higueras, N.L.",
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 25.953400063796533,
+ -100.01606973176307
+ ]
+ }
+ }
+ ]
+ }
+ }
+}
+Public-Private Partnership project
+{
+ "planning": {
+ "project": {
+ "title": "Example PPP",
+ "description": "The Example PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators.",
+ "id": "example_ppp",
+ "uri": "http://communications.gov.example/projects/example_ppp",
+ "totalValue": {
+ "amount": 600000000,
+ "currency": "USD"
+ },
+ "sector": {
+ "scheme": "COFOG",
+ "description": "Road transportation",
+ "id": "04.5.1"
+ },
+ "locations": [
+ {
+ "description": "Local Authority Area: Halton Borough Council",
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2647601"
+ ]
+ }
+ }
+ ]
+ }
+ }
+}
+Changelog
+2021-04-15
+-
+
- Add infrastructure project example +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2020-04-16
+-
+
- Remove guidance related to the
planning.budgetobject. See #701.
+
2018-05-03
+-
+
- Add additional guidance on the use of OCDS fields in the context of this extension +
2017-12-29
+-
+
- Remove the repetition of OCDS fields in this extension +
2017-07-08
+-
+
- Add multilingual support for
Project.titlefields
+ - Remove multilingual support for non-existent
Project.sourceandProject.projectfields
+ - Restore
Budget.projectandBudget.projectIDfields
+ - Remove obsolete
mergeStrategyproperties
+
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/recurrence/index.html b/en/extensions/recurrence/index.html
new file mode 100644
index 000000000..1ff9c2ba8
--- /dev/null
+++ b/en/extensions/recurrence/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Project +
+ ++ Adds a project object to the planning object to describe the project to which the contracting process is related, including the total value of the project (not to be confused with the total value of the contracting process). +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Planning +
+ +
+ The extension defines these fields in the Planning object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ project
+
+ |
+ + Project information + | +
+ The project section can be used to describe the relationship between this contracting process and a project or programme of work. + + |
+ + Project object + | +
+ Project +
+ +
+ The extension defines a new Project object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Project identifier + | +
+ An externally provided identifier for the project. This might be drawn from a projects register, or may be based on the canonical version of a project name. Project IDs should be unique to a publisher. URIs can be used. + + |
+ + string + | +
+
+ title
+
+ |
+ + Project title + | +
+ The name of the project to which this contracting process relates. Some organizations maintain a registry of projects, and the data should use the name by which the project is known in that registry. + ++ This field has multilingual support. + + |
+ + string + | +
+
+ description
+
+ |
+ + Project description + | +
+ A short free text description of the project. + ++ This field has multilingual support. + + |
+ + string + | +
+
+ totalValue
+
+ |
+ + Total project value + | +
+ The total anticipated value of the project over it's lifetime. + + |
+ + Value object + | +
+
+ uri
+
+ |
+ + Linked project information + | +
+ A URI pointing to further information about this project. + + |
+ + string + | +
+
+ sector
+
+ |
+ + Project sector + | +
+ A high-level categorization of the main sector this procurement process relates to. Use of UN COFOG codes, with 'COFOG' as the classification scheme, and the numerical COFOG code is recommended for the primary sector classification. + + |
+ + Classification object + | +
+
+ additionalClassifications
+
+ |
+ + Additional sector classifications + | +
+ Additional project classification, by other sector classifications, or using other classification schemes (e.g. against a strategic framework). + + |
+ + array of Classification objects + | +
+
+ locations
+
+ |
+ + Project location + | +
+ Information about the location where a project is taking place. + + |
+ + array of Location objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/recurrence/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/recurrence/master/release-schema.json b/en/extensions/recurrence/master/release-schema.json
new file mode 100644
index 000000000..4acccbd1a
--- /dev/null
+++ b/en/extensions/recurrence/master/release-schema.json
@@ -0,0 +1,66 @@
+{
+ "definitions": {
+ "Recurrence": {
+ "title": "Recurrence",
+ "description": "Information on the recurrence of the contracting process.",
+ "type": "object",
+ "properties": {
+ "dates": {
+ "title": "Estimated dates",
+ "description": "An estimate of the timing of subsequent initiations of contracting processes (e.g. notices of intended procurement).",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Period"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "description": {
+ "title": "Further information",
+ "description": "Any further information on the recurrence of the contracting process.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Tender": {
+ "properties": {
+ "recurrence": {
+ "title": "Recurrence",
+ "description": "Information on the recurrence of the contracting process.",
+ "$ref": "#/definitions/Recurrence"
+ },
+ "hasRecurrence": {
+ "title": "Has recurrence",
+ "description": "Whether the contracting process is recurrent.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "recurrence": {
+ "title": "Recurrence",
+ "description": "Information on the recurrence of the lot.",
+ "$ref": "#/definitions/Recurrence"
+ },
+ "hasRecurrence": {
+ "title": "Has recurrence",
+ "description": "Whether the contracting process is recurrent.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/recurrence/master/schema/index.html b/en/extensions/recurrence/master/schema/index.html
new file mode 100644
index 000000000..700bf3e75
--- /dev/null
+++ b/en/extensions/recurrence/master/schema/index.html
@@ -0,0 +1,384 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Recurrence +
+ ++ Adds fields for information on the recurrence of the contracting process. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds fields for information on the recurrence of the contracting process.
+"Recurrence" means another contracting process for the same goods, services or works is likely to occur. This is not the same as awarding multiple contracts within a framework agreement.
+A company might, for example, use this information to decide to invest in the machinery they would need to compete for the potential future contract.
+Legal context
+The Revised Agreement on Government Procurement (GPA) includes: "each notice of intended procurement shall include … c. for recurring contracts, an estimate, if possible, of the timing of subsequent notices of intended procurement".
+The European Union is a party to the GPA, and as such its Directive 2014/24/EU (Public contracts — setting out clear ground rules) includes: "Part C: Information to be included in contract notices … 27. In the case of recurrent procurement, estimated timing for further notices to be published."
+This extension's fields correspond to eForms BT-94 (Recurrence) and BT-95 (Recurrence Description).
+Example
+{
+ "tender": {
+ "hasRecurrence": true,
+ "recurrence": {
+ "dates": [
+ {
+ "startDate": "2020-01-01T00:00:00Z"
+ },
+ {
+ "startDate": "2021-01-01T00:00:00Z"
+ }
+ ],
+ "description": "The duration of this contract and recurrent contracts will not exceed three years."
+ }
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
The original draft extension can be found in the archived trade profile repository
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/releasePublisher/index.html b/en/extensions/releasePublisher/index.html
new file mode 100644
index 000000000..64f8ea027
--- /dev/null
+++ b/en/extensions/releasePublisher/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Recurrence +
+ ++ Adds fields for information on the recurrence of the contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Recurrence +
+ +
+ The extension defines a new Recurrence object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ dates
+
+ |
+ + Estimated dates + | +
+ An estimate of the timing of subsequent initiations of contracting processes (e.g. notices of intended procurement). + + |
+ + array of Period objects + | +
+
+ description
+
+ |
+ + Further information + | +
+ Any further information on the recurrence of the contracting process. + + |
+ + string + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ recurrence
+
+ |
+ + Recurrence + | +
+ Information on the recurrence of the contracting process. + + |
+ + Recurrence object + | +
+
+ hasRecurrence
+
+ |
+ + Has recurrence + | +
+ Whether the contracting process is recurrent. + + |
+ + boolean + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ recurrence
+
+ |
+ + Recurrence + | +
+ Information on the recurrence of the lot. + + |
+ + Recurrence object + | +
+
+ hasRecurrence
+
+ |
+ + Has recurrence + | +
+ Whether the contracting process is recurrent. + + |
+ + boolean + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/releasePublisher/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/releasePublisher/master/release-schema.json b/en/extensions/releasePublisher/master/release-schema.json
new file mode 100644
index 000000000..ef23f6692
--- /dev/null
+++ b/en/extensions/releasePublisher/master/release-schema.json
@@ -0,0 +1,44 @@
+{
+ "properties": {
+ "publisher": {
+ "title": "Publisher",
+ "description": "Information to uniquely identify the publisher of this release.",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Name",
+ "description": "The name of the organisation or department responsible for publishing this data.",
+ "type": "string"
+ },
+ "scheme": {
+ "title": "Scheme",
+ "description": "The scheme that holds the unique identifiers used to identify the item being identified.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "uid": {
+ "title": "uid",
+ "description": "The unique ID for this entity under the given ID scheme. Note the use of 'uid' rather than 'id'. See issue #245.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "uri": {
+ "title": "URI",
+ "description": "A URI to identify the publisher.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ },
+ "required": [
+ "name"
+ ]
+ }
+ }
+}
diff --git a/en/extensions/releasePublisher/master/schema/index.html b/en/extensions/releasePublisher/master/schema/index.html
new file mode 100644
index 000000000..fc8e871a1
--- /dev/null
+++ b/en/extensions/releasePublisher/master/schema/index.html
@@ -0,0 +1,299 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Release Publisher +
+ ++ Includes the information about the publisher at release level for the cases in that a release-package or record-packages contains releases from different publishers. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Release Publisher Extension
+Description
+Includes the information about the publisher at release level for the cases in that a release-package or record-packages +contains releases from different publishers.
+Fields
+-
+
- release.publisher: Information to uniquely identify the publisher of this release. +
Example
+{
+ "publisher": {
+ "name": "SECRETARÍA DE LA FUNCIÓNN PÚBLICA / SECRETARIA DE HACIENDA Y CRÉDITO PÚBLICO",
+ "uri": "http://www.gob.mx/contratacionesabiertas/"
+ },
+ "license": "https://datos.gob.mx/libreusomx",
+ "publishedDate": "2018-02-14T19:23:19.405517Z",
+ "uri": "https://api.datos.gob.mx/v1/",
+ "records": [
+ {
+ "ocid": "ocds-07smqs-1303516",
+ "releases": [
+ {
+ "publisher": {
+ "uri": "http://www.gob.mx/sfp",
+ "uid": "27511",
+ "name": "SECRETARÍA DE LA FUNCIÓN PÚBLICA"
+ },
+ "language": "es"
+ ....
+ },
+ {
+ "publisher": {
+ "uri": "http://www.gob.mx/shcp",
+ "uid": "00000",
+ "name": "SECRETARÍA DE HACIENDA Y CRÉDITO PÚBLICO"
+ },
+ "language": "es"
+ ....
+ }
+ ]
+ }
+ ]
+}
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/releaseSource/index.html b/en/extensions/releaseSource/index.html
new file mode 100644
index 000000000..ed1740275
--- /dev/null
+++ b/en/extensions/releaseSource/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Release Publisher +
+ ++ Includes the information about the publisher at release level for the cases in that a release-package or record-packages contains releases from different publishers. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ publisher
+
+ |
+ + Publisher + | +
+ Information to uniquely identify the publisher of this release. + + |
+ + object + | +
+
+ publisher.
+ |
+ + Name + | +
+ The name of the organisation or department responsible for publishing this data. + + |
+ + string + | +
+
+ publisher.
+ |
+ + Scheme + | +
+ The scheme that holds the unique identifiers used to identify the item being identified. + + |
+ + string + | +
+
+ publisher.
+ |
+ + uid + | +
+ The unique ID for this entity under the given ID scheme. Note the use of 'uid' rather than 'id'. See issue #245. + + |
+ + string + | +
+
+ publisher.
+ |
+ + URI + | +
+ A URI to identify the publisher. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/releaseSource/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/releaseSource/master/release-schema.json b/en/extensions/releaseSource/master/release-schema.json
new file mode 100644
index 000000000..49deceb2e
--- /dev/null
+++ b/en/extensions/releaseSource/master/release-schema.json
@@ -0,0 +1,51 @@
+{
+ "properties": {
+ "sources": {
+ "title": "Sources",
+ "description": "The information systems from which the data originates.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Source"
+ },
+ "uniqueItems": true
+ }
+ },
+ "definitions": {
+ "Source": {
+ "type": "object",
+ "title": "Source",
+ "description": "An information system from which data originates.",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "The locally unique identifier for the source.",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "name": {
+ "title": "Name",
+ "description": "The name of the source.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "title": "URL",
+ "description": "The web address of the source.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/releaseSource/master/schema/index.html b/en/extensions/releaseSource/master/schema/index.html
new file mode 100644
index 000000000..db7f2334d
--- /dev/null
+++ b/en/extensions/releaseSource/master/schema/index.html
@@ -0,0 +1,316 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Sources +
+ ++ Adds a sources array to indicate the information systems from which the data originates. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In many cases, an OCDS publication combines information from multiple information systems or databases. For example:
+-
+
- A publisher can source information from multiple systems to author a single release. +
- Different systems can be responsible for different types of contracting processes; for example, traditional procurement, framework agreements and public-private partnerships can be managed in different systems. +
- Different systems can be responsible for different stages of the contracting process, published in different releases; for example, budget data from a Ministry of Finance system, and solicitation data from a Public Procurement Agency system. +
- Different systems can cover different periods; for example, older data might not be migrated into a newer system. +
Data's provenance is relevant to many use cases, including data verification.
+To satisfy such use cases, this extension adds a sources array to the release schema, in which the publisher can list the information systems from which the data in the release originates.
Example
+{
+ "sources": [
+ {
+ "id": "sample-source",
+ "name": "Sample Source",
+ "url": "http://example.com"
+ },
+ {
+ "id": "honducompras",
+ "name": "HonduCompras 1.0",
+ "url": "http://h1.honducompras.gob.hn/"
+ }
+ ]
+}
+Usage notes
+There are some cases where the data source for a release comes from different information systems of the same publisher.
+There are some cases in which you can link the data from the contracts database with the bidding and traditional process databases.
+Changelog
+This extension was originally discussed in https://github.com/open-contracting/standard/issues/800.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/renewal/index.html b/en/extensions/renewal/index.html
new file mode 100644
index 000000000..adbb8dc7c
--- /dev/null
+++ b/en/extensions/renewal/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Sources +
+ ++ Adds a sources array to indicate the information systems from which the data originates. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ sources
+
+ |
+ + Sources + | +
+ The information systems from which the data originates. + + |
+ + array of Source objects + | +
+ Source +
+ +
+ The extension defines a new Source object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ The locally unique identifier for the source. + + |
+ + string or integer + | +
+
+ name
+
+ |
+ + Name + | +
+ The name of the source. + + |
+ + string + | +
+
+ url
+
+ |
+ + URL + | +
+ The web address of the source. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/renewal/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/renewal/master/release-schema.json b/en/extensions/renewal/master/release-schema.json
new file mode 100644
index 000000000..bc1759a65
--- /dev/null
+++ b/en/extensions/renewal/master/release-schema.json
@@ -0,0 +1,76 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "hasRenewal": {
+ "title": "Has renewal",
+ "description": "Whether the contracts can be renewed.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "renewal": {
+ "title": "Renewal",
+ "description": "The options for the renewal of the contracts.",
+ "$ref": "#/definitions/Renewal"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "hasRenewal": {
+ "title": "Has renewal",
+ "description": "Whether the contract related to the lot can be renewed.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "renewal": {
+ "title": "Renewal",
+ "description": "The options for the renewal of the contract related to the lot.",
+ "$ref": "#/definitions/Renewal"
+ }
+ }
+ },
+ "Renewal": {
+ "title": "Renewal",
+ "description": "Information about the options for the renewal of a contract.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "A description of the options for the renewal of the contract.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "minimumRenewals": {
+ "title": "Minimum renewal",
+ "description": "The minimum number of renewals.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "maximumRenewals": {
+ "title": "Maximum renewal",
+ "description": "The maximum number of renewals. If there is no maximum, set to 1e9999 (which parses to infinity).",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "period": {
+ "title": "Renewal period",
+ "description": "The period over which the contract can be renewed.",
+ "$ref": "#/definitions/Period"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/renewal/master/schema/index.html b/en/extensions/renewal/master/schema/index.html
new file mode 100644
index 000000000..e44f27895
--- /dev/null
+++ b/en/extensions/renewal/master/schema/index.html
@@ -0,0 +1,418 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Renewal +
+ ++ Adds fields to the Tender and Lot objects to describe the options for the renewal of contracts. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds fields to the Tender and Lot objects to describe the options for the renewal of contracts.
+Legal context
+In the European Union, this extension's fields correspond to eForms BT-57 (Renewal Description). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Guidance
+If the number of times a contract can be renewed is an exact number and not a range, set minimumRenewals and maximumRenewals to the same number.
Example
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "lot-1",
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ },
+ "contractPeriod": {
+ "startDate": "2020-10-10T00:00:00Z",
+ "endDate": "2021-11-10T00:00:00Z"
+ },
+ "hasRenewal": false
+ },
+ {
+ "id": "lot-2",
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ },
+ "contractPeriod": {
+ "startDate": "2020-12-10T00:00:00Z",
+ "endDate": "2021-12-10T00:00:00Z"
+ },
+ "hasRenewal": true,
+ "renewal": {
+ "description": "The contracting authority reserves the right to extend the term for a period or periods of up to 1 year with a maximum of 2 such extensions on the same terms and conditions, subject to the contracting authority’s obligations at law.",
+ "maximumRenewals": 2,
+ "period": {
+ "durationInDays": 365
+ }
+ }
+ },
+ {
+ "id": "lot-3",
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ },
+ "contractPeriod": {
+ "startDate": "2021-02-10T00:00:00Z",
+ "endDate": "2022-02-10T00:00:00Z"
+ },
+ "hasRenewal": true,
+ "renewal": {
+ "description": "Contracts are due to be renewed one time at the end of the initial term.",
+ "minimumRenewals": 3,
+ "maximumRenewals": 3,
+ "period": {
+ "startDate": "2021-02-10T00:00:00Z",
+ "endDate": "2024-02-10T00:00:00Z"
+ }
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2021-01-19
+-
+
- Add fields:
+
-
+
Tender.hasRenewal
+Tender.renewal
+
+
2020-10-06
+-
+
- Add fields:
+
-
+
Renewal.minimumRenewals
+Renewal.maximumRenewals
+Renewal.period
+
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile in issue 22 and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/requirements/index.html b/en/extensions/requirements/index.html
new file mode 100644
index 000000000..8eabc05dc
--- /dev/null
+++ b/en/extensions/requirements/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Renewal +
+ ++ Adds fields to the Tender and Lot objects to describe the options for the renewal of contracts. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasRenewal
+
+ |
+ + Has renewal + | +
+ Whether the contracts can be renewed. + + |
+ + boolean + | +
+
+ renewal
+
+ |
+ + Renewal + | +
+ The options for the renewal of the contracts. + + |
+ + Renewal object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasRenewal
+
+ |
+ + Has renewal + | +
+ Whether the contract related to the lot can be renewed. + + |
+ + boolean + | +
+
+ renewal
+
+ |
+ + Renewal + | +
+ The options for the renewal of the contract related to the lot. + + |
+ + Renewal object + | +
+ Renewal +
+ +
+ The extension defines a new Renewal object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ A description of the options for the renewal of the contract. + + |
+ + string + | +
+
+ minimumRenewals
+
+ |
+ + Minimum renewal + | +
+ The minimum number of renewals. + + |
+ + number + | +
+
+ maximumRenewals
+
+ |
+ + Maximum renewal + | +
+ The maximum number of renewals. If there is no maximum, set to 1e9999 (which parses to infinity). + + |
+ + number + | +
+
+ period
+
+ |
+ + Renewal period + | +
+ The period over which the contract can be renewed. + + |
+ + Period object + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/requirements/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/requirements/master/extension.json b/en/extensions/requirements/master/extension.json
new file mode 100644
index 000000000..42cc20416
--- /dev/null
+++ b/en/extensions/requirements/master/extension.json
@@ -0,0 +1,29 @@
+{
+ "name": {
+ "en": "Requirements",
+ "es": "Requisitos"
+ },
+ "description": {
+ "en": "Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV).",
+ "es": "Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV)."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/requirements/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "dataType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/requirements/master/index.html b/en/extensions/requirements/master/index.html
new file mode 100644
index 000000000..62724ac83
--- /dev/null
+++ b/en/extensions/requirements/master/index.html
@@ -0,0 +1,461 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Requirements +
+ ++ Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV). +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ dataType.csv +
+ +
+ You can download the dataType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ string
+
+ |
+ + String + | +
+ The response must be of type string + + |
+
+
+ date-time
+
+ |
+ + Date-time + | +
+ The response must be of type date-time (ISO8601) + + |
+
+
+ number
+
+ |
+ + Number + | +
+ The response must be of type number, i.e. a floating point or whole number + + |
+
+
+ integer
+
+ |
+ + Integer + | +
+ The response must be of type integer + + |
+
+
+ boolean
+
+ |
+ + Boolean + | +
+ The response must be of type boolean + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/requirements/master/release-schema.json b/en/extensions/requirements/master/release-schema.json
new file mode 100644
index 000000000..9da7f0127
--- /dev/null
+++ b/en/extensions/requirements/master/release-schema.json
@@ -0,0 +1,328 @@
+{
+ "definitions": {
+ "Criterion": {
+ "title": "Criterion",
+ "description": "A criterion on which bids, tenderers, lots or items will be judged, evaluated or assessed.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "The identifier for this criterion. It must be unique and cannot change within the Open Contracting Process it is part of (defined by a single ocid). See the [identifier guidance](http://standard.open-contracting.org/latest/en/schema/identifiers/) for further details.",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "title": {
+ "title": "Title",
+ "description": "A title for this criterion.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "A description of this criterion.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "relatesToTenderer": {
+ "title": "Relates to tenderer",
+ "description": "The criterion judges, evaluates or assesses a tenderer.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "relatedItem": {
+ "title": "Related item",
+ "description": "The identifier of the item in the tender section to which this criterion applies.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "The identifiers of the lots to which this criterion applies.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "requirementGroups": {
+ "title": "Requirement groups",
+ "description": "A list of requirement groups for this Criterion. A criterion is satisfied by one or more requirement groups being met. A requirement group is met when all requirements in the group are satisfied.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/RequirementGroup"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "RequirementGroup": {
+ "title": "Requirement group",
+ "description": "A requirement group is a set of requirements that must be fulfilled together to validate a criterion.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "The identifier for this requirement group. It must be unique and cannot change within the Open Contracting Process it is part of (defined by a single ocid). See the [identifier guidance](http://standard.open-contracting.org/latest/en/schema/identifiers/) for further details.",
+ "type": "string",
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "A description of this requirement group.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "requirements": {
+ "title": "Requirements",
+ "description": "A list requirements which must all be satisfied for the requirement group to be met.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Requirement"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Requirement": {
+ "title": "Requirement",
+ "description": "An atomic requirement. Requirements can specify the expected value that the response has to contain, or a range of threshold values within which the response has to fit in. The requirement may apply to a certain period of time.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Requirement identifier",
+ "description": "The identifier for this requirement. It must be unique and cannot change within the Open Contracting Process it is part of (defined by a single ocid). See the [identifier guidance](http://standard.open-contracting.org/latest/en/schema/identifiers/) for further details.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "Requirement title",
+ "description": "The title of this atomic requirement.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Requirement description",
+ "description": "A free text description for this atomic requirement.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "dataType": {
+ "title": "Requirement datatype",
+ "description": "The data type in which the response must be provided.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "dataType.csv",
+ "openCodelist": false,
+ "enum": [
+ "string",
+ "date-time",
+ "number",
+ "integer",
+ "boolean",
+ null
+ ]
+ },
+ "pattern": {
+ "title": "Response validation pattern",
+ "description": "A regular expression with which to validate the response.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "expectedValue": {
+ "title": "Expected value",
+ "description": "The expected value of the requirement, when the response must be specific value.",
+ "type": [
+ "string",
+ "integer",
+ "number",
+ "boolean",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "minValue": {
+ "title": "Minimum value",
+ "description": "The lower bound of the requirement, when the response must be within a certain range.",
+ "type": [
+ "integer",
+ "number",
+ "null"
+ ]
+ },
+ "maxValue": {
+ "title": "Maximum value",
+ "description": "The upper bound of the requirement, when the response must be within a certain range.",
+ "type": [
+ "integer",
+ "number",
+ "null"
+ ]
+ },
+ "period": {
+ "title": "Period",
+ "description": "The period to which the requirement applies: for example, the tenderer's turnover in a given year.",
+ "$ref": "#/definitions/Period"
+ }
+ },
+ "minProperties": 1
+ },
+ "RequirementResponse": {
+ "title": "Requirement response",
+ "description": "An assertion that responds to a single requirement. A response provides the value for the requirement and may provide the period to which it applies.",
+ "type": "object",
+ "required": [
+ "id",
+ "requirement"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "The unique identifier of this response in the context of the contracting process.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "Title",
+ "description": "The title of this response.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "The description of this response.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "value": {
+ "title": "Value",
+ "description": "The value of this response.",
+ "type": [
+ "string",
+ "integer",
+ "number",
+ "boolean",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "period": {
+ "title": "Period",
+ "description": "The period to which the response applies.",
+ "$ref": "#/definitions/Period"
+ },
+ "requirement": {
+ "title": "Related requirement",
+ "description": "A reference to the requirement to which the response applies.",
+ "$ref": "#/definitions/RequirementReference"
+ }
+ },
+ "minProperties": 1
+ },
+ "RequirementReference": {
+ "title": "Requirement reference",
+ "description": "A reference to a requirement.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Requirement ID",
+ "description": "The identifier of the requirement to which the response applies.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "Requirement title",
+ "description": "The title of the requirement to which the response applies.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Bid": {
+ "properties": {
+ "requirementResponses": {
+ "title": "Requirement responses",
+ "description": "The responses of this bid to the requirements.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/RequirementResponse"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "criteria": {
+ "title": "Criteria",
+ "description": "Criteria on which bids, tenderers, lots or items will be judged, evaluated or assessed.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Criterion"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/requirements/master/schema/index.html b/en/extensions/requirements/master/schema/index.html
new file mode 100644
index 000000000..4dc4c3f9e
--- /dev/null
+++ b/en/extensions/requirements/master/schema/index.html
@@ -0,0 +1,916 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Requirements +
+ ++ Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV). +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV).
+CCCEV is designed to support the exchange of information between buyers or procuring entities that define criteria and tenderers that respond to these criteria by means of evidences. Criteria can relate to bids, tenderers, lots or items.
+If your data does not closely follow the Core Criterion and Core Evidence Vocabulary (CCCEV), consider the Selection criteria extension.
+CCCEV Model
+The CCCEV model defines the following concepts:
+Criterion +A criterion represents a rule or principle used to judge, evaluate or assess bids, tenderers, lots or items. A criterion is satisfied when one or more of its requirement groups is satisfied.
+Requirement Group +A requirement group is a collection of one or more individual requirements. A requirement group is satisfied when all of it's requirements are satisfied.
+Requirement +An atomic requirement which can be expressed as either an expected value or a range of accepted values.
+Requirement Response +A requirements response is an assertion that responds to a specific requirement.
+Therefore the CCCEV model can be used to express both AND conditions, where a group of requirements must be met to satisfy a criterion, and OR conditions, where there are alternative requirements that can satisfy a criterion.
+The CCCEV model also defines a number of additional concepts including formalFrameworks, used to specify the legal instruments from criteria are derived, evidence, used both to specify and provide the evidence required to support a response, and additional properties of requirements such as certificationLevel. These are not yet implemented in this extension. This extension also does not describe formulae for calculating computed values, nor does it describe whether data should be published openly or not.
+Example
+Criteria for an item and a tenderer, with AND and OR conditions:
+{
+ "tender": {
+ "criteria": [
+ {
+ "id": "0001",
+ "title": "Air intake",
+ "description": "The vacuum cleaner air intake must be at least 100W",
+ "relatedItem": "item1",
+ "requirementGroups": [
+ {
+ "id": "0001-001",
+ "description": "The vacuum cleaner air intake must be at least 100W",
+ "requirements": [
+ {
+ "id": "0001-001-01",
+ "title": "Air intake",
+ "description": "Power of vacuum cleaner air intake in W",
+ "dataType": "integer",
+ "pattern": "[0-9]*",
+ "minValue": 100
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "id": "0002",
+ "title": "Warranty",
+ "description": "The vacuum cleaner must have warranty support options for at least 36 months",
+ "relatedItem": "item1",
+ "requirementGroups": [
+ {
+ "id": "0002-001",
+ "description": "The standard warranty period for the vacuum cleaner must be at least 36 months",
+ "requirements": [
+ {
+ "id": "0002-001-01",
+ "title": "Standard warranty period",
+ "description": "Length of the vacuum cleaner standard warranty period in months",
+ "dataType": "integer",
+ "pattern": "[0-9]*",
+ "minValue": 36
+ }
+ ]
+ },
+ {
+ "id": "0002-002",
+ "description": "The standard warranty period for the vacuum cleaner must be at least 12 months with an option to extend to 36 months",
+ "requirements": [
+ {
+ "id": "0002-002-01",
+ "title": "Standard warranty period",
+ "description": "Length of the vacuum cleaner standard warranty period in months",
+ "dataType": "integer",
+ "pattern": "[0-9]*",
+ "minValue": 12
+ },
+ {
+ "id": "0002-002-02",
+ "title": "Extended warranty option",
+ "description": "There is an extended warranty option for at least 36 months",
+ "dataType": "boolean",
+ "expectedValue": true
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "id": "0003",
+ "title": "Years trading",
+ "description": "Number of years the tenderer has been trading",
+ "relatesToTenderer": true,
+ "requirementGroups": [
+ {
+ "id": "0003-001",
+ "description": "Number of years the tenderer has been trading",
+ "requirements": [
+ {
+ "id": "0003-001-01",
+ "title": "Years trading",
+ "description": "Number of years the tenderer has been trading",
+ "dataType": "integer",
+ "pattern": "[0-9]*",
+ "minValue": 3
+ }
+ ]
+ }
+ ]
+ }
+ ]
+ }
+}
+Responses to the criteria:
+{
+ "bids": {
+ "details": [
+ {
+ "id": "1",
+ "requirementResponses": [
+ {
+ "id": "air",
+ "value": 125,
+ "requirement": {
+ "id": "0001-001-01"
+ }
+ },
+ {
+ "id": "warranty",
+ "value": 36,
+ "requirement": {
+ "id": "0002-001-01"
+ }
+ },
+ {
+ "id": "years",
+ "value": 10,
+ "requirement": {
+ "id": "0003-001-01"
+ }
+ }
+ ]
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-06-07
+-
+
- Remove fields:
+
-
+
Award.requirementResponses
+Contract.requirementResponses
+Criterion.source
+RequirementResponse.relatedTenderer
+
+ - Replace
Criterion.relatesTocodelist field withCriterion.relatesToTendererboolean field.
+ - Remove
relatesTo.csvcodelist.
+ - Remove
responseSource.csvcodelist.
+
2023-04-18
+-
+
- Add
Criterion.relatedLotsfield.
+ - Remove unnecessary instructions from field descriptions. +
2020-06-04
+-
+
- Review normative and non-normative words. +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed in https://github.com/open-contracting/standard/issues/223.
+2019-03-20
+-
+
- Set
"uniqueItems": trueon array fields, and add"minLength": 1on required string fields.
+
2018-12-18
+-
+
Requirement.expectedValueandRequirementResponse.valueallow boolean values.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/risk_allocation/index.html b/en/extensions/risk_allocation/index.html
new file mode 100644
index 000000000..aeeb392a8
--- /dev/null
+++ b/en/extensions/risk_allocation/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Requirements +
+ ++ Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV). +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Criterion +
+ +
+ The extension defines a new Criterion object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ The identifier for this criterion. It must be unique and cannot change within the Open Contracting Process it is part of (defined by a single ocid). See the identifier guidance for further details. + + |
+ + string or integer + | +
+
+ title
+
+ |
+ + Title + | +
+ A title for this criterion. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A description of this criterion. + + |
+ + string + | +
+
+ relatesToTenderer
+
+ |
+ + Relates to tenderer + | +
+ The criterion judges, evaluates or assesses a tenderer. + + |
+ + boolean + | +
+
+ relatedItem
+
+ |
+ + Related item + | +
+ The identifier of the item in the tender section to which this criterion applies. + + |
+ + string + | +
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ The identifiers of the lots to which this criterion applies. + + |
+ + array of strings + | +
+
+ requirementGroups
+
+ |
+ + Requirement groups + | +
+ A list of requirement groups for this Criterion. A criterion is satisfied by one or more requirement groups being met. A requirement group is met when all requirements in the group are satisfied. + + |
+ + array of RequirementGroup objects + | +
+ RequirementGroup +
+ +
+ The extension defines a new RequirementGroup object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ The identifier for this requirement group. It must be unique and cannot change within the Open Contracting Process it is part of (defined by a single ocid). See the identifier guidance for further details. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A description of this requirement group. + + |
+ + string + | +
+
+ requirements
+
+ |
+ + Requirements + | +
+ A list requirements which must all be satisfied for the requirement group to be met. + + |
+ + array of Requirement objects + | +
+ Requirement +
+ +
+ The extension defines a new Requirement object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Requirement identifier + | +
+ The identifier for this requirement. It must be unique and cannot change within the Open Contracting Process it is part of (defined by a single ocid). See the identifier guidance for further details. + + |
+ + string + | +
+
+ title
+
+ |
+ + Requirement title + | +
+ The title of this atomic requirement. + + |
+ + string + | +
+
+ description
+
+ |
+ + Requirement description + | +
+ A free text description for this atomic requirement. + + |
+ + string + | +
+
+ dataType
+
+ |
+ + Requirement datatype + | +
+ The data type in which the response must be provided. + + |
+ + string from closed dataType codelist + | +
+
+ pattern
+
+ |
+ + Response validation pattern + | +
+ A regular expression with which to validate the response. + + |
+ + string + | +
+
+ expectedValue
+
+ |
+ + Expected value + | +
+ The expected value of the requirement, when the response must be specific value. + + |
+ + string or integer or number or boolean + | +
+
+ minValue
+
+ |
+ + Minimum value + | +
+ The lower bound of the requirement, when the response must be within a certain range. + + |
+ + integer or number + | +
+
+ maxValue
+
+ |
+ + Maximum value + | +
+ The upper bound of the requirement, when the response must be within a certain range. + + |
+ + integer or number + | +
+
+ period
+
+ |
+ + Period + | +
+ The period to which the requirement applies: for example, the tenderer's turnover in a given year. + + |
+ + Period object + | +
+ RequirementResponse +
+ +
+ The extension defines a new RequirementResponse object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ The unique identifier of this response in the context of the contracting process. + + |
+ + string + | +
+
+ title
+
+ |
+ + Title + | +
+ The title of this response. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ The description of this response. + + |
+ + string + | +
+
+ value
+
+ |
+ + Value + | +
+ The value of this response. + + |
+ + string or integer or number or boolean + | +
+
+ period
+
+ |
+ + Period + | +
+ The period to which the response applies. + + |
+ + Period object + | +
+
+ requirement
+
+ |
+ + Related requirement + | +
+ A reference to the requirement to which the response applies. + + |
+ + RequirementReference object + | +
+ RequirementReference +
+ +
+ The extension defines a new RequirementReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Requirement ID + | +
+ The identifier of the requirement to which the response applies. + + |
+ + string + | +
+
+ title
+
+ |
+ + Requirement title + | +
+ The title of the requirement to which the response applies. + + |
+ + string + | +
+ Bid +
+ +
+ The extension defines these fields in the Bid object from the Bid statistics and details extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ requirementResponses
+
+ |
+ + Requirement responses + | +
+ The responses of this bid to the requirements. + + |
+ + array of RequirementResponse objects + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ criteria
+
+ |
+ + Criteria + | +
+ Criteria on which bids, tenderers, lots or items will be judged, evaluated or assessed. + + |
+ + array of Criterion objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/risk_allocation/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/risk_allocation/master/codelists/riskAllocation.csv b/en/extensions/risk_allocation/master/codelists/riskAllocation.csv
new file mode 100644
index 000000000..44c09ce47
--- /dev/null
+++ b/en/extensions/risk_allocation/master/codelists/riskAllocation.csv
@@ -0,0 +1,4 @@
+Code,Title,Description
+publicAuthority,Public authority,The risk is wholly or mostly retained by the public authority
+privateParty,Private party,The risk is wholly or mostly retained by the private party
+undefined,Undefined,The risk is not clearly assigned to a specific party to the contract. Further details can be provided in the notes field.
diff --git a/en/extensions/risk_allocation/master/codelists/riskCategory.csv b/en/extensions/risk_allocation/master/codelists/riskCategory.csv
new file mode 100644
index 000000000..920f1aeef
--- /dev/null
+++ b/en/extensions/risk_allocation/master/codelists/riskCategory.csv
@@ -0,0 +1,17 @@
+Category,Code,Title,Description,Source
+designAndConstruction,landAvailability,Land availability and acquisition risk,Relates to the unavailability of land or site to construct the infrastructure at the time of contract signature,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+designAndConstruction,environmental,Environmental risk,"Environmental risks might be related to a number of environmental issues such as general contamination, pollution, water contamination, impact on the natural environment etc. An adverse assessment might lead to changes in design, leading to a direct impact on cost of infrastructure",https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+designAndConstruction,design,Design risks,Represents the possibility that design quality for the asset is not adequate to meet project requirements,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+designAndConstruction,construction,Construction risks,"Represents the possibility that during the construction Phase, the actual project costs or construction time exceeds the projected time and costs",https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+designAndConstruction,completion,Completion and commissioning,Refers to the failure to meet the construction outcome or finalization as prescribed,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+operating,revenue,Revenue risk,Refers to the risk of the revenue flows not being correctly assessed,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+operating,inflationAndFx,"Foreign exchange, inflation and indexation risk",Risk that changes in exchange rates or inflation adversely affect the project outcomes,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+operating,availabilityAndQuality,Availability and quality risk,Risk linked to availability and quality issues relating to performance requirements and performance target levels,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+operating,otherRevenue,Other revenue risk events,credit or counterparty risk; fraud/non-payment by users,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+finance,financeAvailability,Availability of finance,Represents the risk of financing not being available at commercial close or before construction starts,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+finance,refinancing,Refinancing risks,Risks relating to the downside of refinancing,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+other,changeInLaw,Changes in law,Risk that a change in general law or the sector regulatory framework adversely affect the project,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+other,forceMajeure,Force majeure,"Risk that external events beyond the control of the parties to the contract, such as natural disasters, wars, terrorism etc., affect the project",https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+other,earlyTermination,Early termination,Risk that compensation sum due to early termination might be insufficient to meet private party’s financial obligations or is less than expected,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+other,compliance,Compliance risks,Risks deriving from the compliance or lack thereof of regulatory obligations related to the development of the project,
+other,all,All risks,All risks deriving from the project,
diff --git a/en/extensions/risk_allocation/master/extension.json b/en/extensions/risk_allocation/master/extension.json
new file mode 100644
index 000000000..095a540b1
--- /dev/null
+++ b/en/extensions/risk_allocation/master/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Risk Allocation",
+ "es": "Asignaci\u00f3n de Riesgo"
+ },
+ "description": {
+ "en": "For providing the risk allocations defined in a public private partnership's contract.",
+ "es": "Para proporcionar las asignaciones de riesgo definidas en un contrato de asociaci\u00f3n p\u00fablico-privada."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/risk_allocation/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "riskAllocation.csv",
+ "riskCategory.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/risk_allocation/master/index.html b/en/extensions/risk_allocation/master/index.html
new file mode 100644
index 000000000..b5b8e6fe4
--- /dev/null
+++ b/en/extensions/risk_allocation/master/index.html
@@ -0,0 +1,330 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Risk Allocation +
+ ++ For providing the risk allocations defined in a public private partnership's contract. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ riskAllocation.csv +
+ +
+ You can download the riskAllocation.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ publicAuthority
+
+ |
+ + Public authority + | +
+ The risk is wholly or mostly retained by the public authority + + |
+
+
+ privateParty
+
+ |
+ + Private party + | +
+ The risk is wholly or mostly retained by the private party + + |
+
+
+ undefined
+
+ |
+ + Undefined + | +
+ The risk is not clearly assigned to a specific party to the contract. Further details can be provided in the notes field. + + |
+
+ riskCategory.csv +
+ +
+ You can download the riskCategory.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ landAvailability
+
+ |
+ + Land availability and acquisition risk + | +
+ Relates to the unavailability of land or site to construct the infrastructure at the time of contract signature + +
|
+
+
+ environmental
+
+ |
+ + Environmental risk + | +
+ Environmental risks might be related to a number of environmental issues such as general contamination, pollution, water contamination, impact on the natural environment etc. An adverse assessment might lead to changes in design, leading to a direct impact on cost of infrastructure + +
|
+
+
+ design
+
+ |
+ + Design risks + | +
+ Represents the possibility that design quality for the asset is not adequate to meet project requirements + +
|
+
+
+ construction
+
+ |
+ + Construction risks + | +
+ Represents the possibility that during the construction Phase, the actual project costs or construction time exceeds the projected time and costs + +
|
+
+
+ completion
+
+ |
+ + Completion and commissioning + | +
+ Refers to the failure to meet the construction outcome or finalization as prescribed + +
|
+
+
+ revenue
+
+ |
+ + Revenue risk + | +
+ Refers to the risk of the revenue flows not being correctly assessed + +
|
+
+
+ inflationAndFx
+
+ |
+ + Foreign exchange, inflation and indexation risk + | +
+ Risk that changes in exchange rates or inflation adversely affect the project outcomes + +
|
+
+
+ availabilityAndQuality
+
+ |
+ + Availability and quality risk + | +
+ Risk linked to availability and quality issues relating to performance requirements and performance target levels + +
|
+
+
+ otherRevenue
+
+ |
+ + Other revenue risk events + | +
+ credit or counterparty risk; fraud/non-payment by users + +
|
+
+
+ financeAvailability
+
+ |
+ + Availability of finance + | +
+ Represents the risk of financing not being available at commercial close or before construction starts + +
|
+
+
+ refinancing
+
+ |
+ + Refinancing risks + | +
+ Risks relating to the downside of refinancing + +
|
+
+
+ changeInLaw
+
+ |
+ + Changes in law + | +
+ Risk that a change in general law or the sector regulatory framework adversely affect the project + +
|
+
+
+ forceMajeure
+
+ |
+ + Force majeure + | +
+ Risk that external events beyond the control of the parties to the contract, such as natural disasters, wars, terrorism etc., affect the project + +
|
+
+
+ earlyTermination
+
+ |
+ + Early termination + | +
+ Risk that compensation sum due to early termination might be insufficient to meet private party’s financial obligations or is less than expected + +
|
+
+
+ compliance
+
+ |
+ + Compliance risks + | +
+ Risks deriving from the compliance or lack thereof of regulatory obligations related to the development of the project + +
|
+
+
+ all
+
+ |
+ + All risks + | +
+ All risks deriving from the project + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/risk_allocation/master/release-schema.json b/en/extensions/risk_allocation/master/release-schema.json
new file mode 100644
index 000000000..d9b56661d
--- /dev/null
+++ b/en/extensions/risk_allocation/master/release-schema.json
@@ -0,0 +1,83 @@
+{
+ "definitions": {
+ "Risk": {
+ "title": "Risk",
+ "description": "A risk relating to the project.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Risk ID",
+ "description": "A local identifier for this risk, unique within this block. This field is used to keep track of multiple revisions of a risk through the compilation from release to record mechanism.",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "category": {
+ "title": "Risk category",
+ "description": "The category of the risk, from the riskCategory codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "riskCategory.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "description": {
+ "title": "Risk description",
+ "description": "The description of the risk.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "allocation": {
+ "title": "Risk allocation",
+ "description": "The party to the contract that retains the risk.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "riskAllocation.csv",
+ "openCodelist": false,
+ "enum": [
+ "publicAuthority",
+ "privateParty",
+ "undefined",
+ null
+ ]
+ },
+ "notes": {
+ "title": "Risk notes",
+ "description": "Additional notes on the risk, for example the rationale for the allocation.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Contract": {
+ "properties": {
+ "riskAllocation": {
+ "title": "Risk allocation",
+ "description": "Information on the allocation of risks relating to the contract.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Risk"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/risk_allocation/master/schema/index.html b/en/extensions/risk_allocation/master/schema/index.html
new file mode 100644
index 000000000..7bd72f844
--- /dev/null
+++ b/en/extensions/risk_allocation/master/schema/index.html
@@ -0,0 +1,359 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Risk Allocation +
+ ++ For providing the risk allocations defined in a public private partnership's contract. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The framework for disclosure in PPPs calls for individual risk allocation information.
+The risk allocation extension is used to provide structured data on the risk allocations defined in a public private partnership's contract, through a contracts.riskAllocation array.
The riskCategory.csv codelist is based on the APMG PPP Certification Program. The codelist's Category column indicates the stage or aspect of the contracting process to which the risk category applies.
Example
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "title": "Public Private Partnership Agreement",
+ "description": "Public-Private Partnership agreement entered into by and between telecoms promoter, together with national fibre infrastructure and the special purpose vehicle Mega Consortium Ltd",
+ "riskAllocation": [
+ {
+ "id": "1",
+ "category": "compliance",
+ "description": "Risks deriving from the compliance or lack thereof of regulatory obligations related to the development of the Project",
+ "allocation": "privateParty"
+ },
+ {
+ "id": "2",
+ "category": "construction",
+ "description": "Risks deriving from procurement or lack thereof of the necessary licenses and permits for the Project’s development",
+ "allocation": "privateParty"
+ },
+ {
+ "id": "3",
+ "category": "construction",
+ "description": "Risks arising from the procurement or lack thereof of rights of way required for the Project’s development",
+ "allocation": "privateParty"
+ }
+ ]
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-06-04
+-
+
- Review normative and non-normative words. +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2019-03-20
+-
+
- Add
"minLength": 1on required string fields.
+
2018-05-08
+-
+
- Make
Risk.idrequired to support revision tracking and list merging
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/risk_allocation/v1.1/README.md b/en/extensions/risk_allocation/v1.1/README.md
new file mode 100644
index 000000000..6e24742bb
--- /dev/null
+++ b/en/extensions/risk_allocation/v1.1/README.md
@@ -0,0 +1,17 @@
+# Risk allocation
+
+The [framework for disclosure in PPPs](http://pubdocs.worldbank.org/en/773541448296707678/Disclosure-in-PPPs-Framework.pdf) calls for individual risk allocation information.
+
+The risk allocation extension is used to provide structured data on the risk allocations defined in a public private partnerships contract.
+
+## Overview
+
+Risk allocations can be represented using an array of [risk blocks](../../../schema/reference/#organization) in the `riskAllocation` field of the `contract` section of an OCDS release.
+
+The risk category can be represented using the `risk/category` field using values from the [risk category codelist](../schema/codelists/#risk-category) based on the APMG PPP Certification Program.
+
+The party retaining each risk should be represented using the `risk/allocation` field using values from the [risk allocation codelist](../schema/codelists/#risk-allocation).
+
+The description of the risk should be provided as free text using the `risk/description` field and the mitigation for the risk should be provided as free text using the `risk/mitigation` field.
+
+Additional free text information on the risk can be provided using the `risk/notes` field.
diff --git a/en/extensions/risk_allocation/v1.1/codelists/index.html b/en/extensions/risk_allocation/v1.1/codelists/index.html
new file mode 100644
index 000000000..390d8e1ec
--- /dev/null
+++ b/en/extensions/risk_allocation/v1.1/codelists/index.html
@@ -0,0 +1,538 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Risk Allocation +
+ ++ For providing the risk allocations defined in a public private partnership's contract. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Risk +
+ +
+ The extension defines a new Risk object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Risk ID + | +
+ A local identifier for this risk, unique within this block. This field is used to keep track of multiple revisions of a risk through the compilation from release to record mechanism. + + |
+ + string or integer + | +
+
+ category
+
+ |
+ + Risk category + | +
+ The category of the risk, from the riskCategory codelist. + + |
+ + string from open riskCategory codelist + | +
+
+ description
+
+ |
+ + Risk description + | +
+ The description of the risk. + + |
+ + string + | +
+
+ allocation
+
+ |
+ + Risk allocation + | +
+ The party to the contract that retains the risk. + + |
+ + string from closed riskAllocation codelist + | +
+
+ notes
+
+ |
+ + Risk notes + | +
+ Additional notes on the risk, for example the rationale for the allocation. + + |
+ + string + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ riskAllocation
+
+ |
+ + Risk allocation + | +
+ Information on the allocation of risks relating to the contract. + + |
+ + array of Risk objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/risk_allocation/v1.1/codelists/riskAllocation.csv b/en/extensions/risk_allocation/v1.1/codelists/riskAllocation.csv
new file mode 100644
index 000000000..9a0b4a8aa
--- /dev/null
+++ b/en/extensions/risk_allocation/v1.1/codelists/riskAllocation.csv
@@ -0,0 +1,4 @@
+Category,Code,Title_en,Description_en,Source
+,publicAuthority,Public authority,The risk is wholly or mostly retained by the public authority,
+,privateParty,Private party,The risk is wholly or mostly retained by the private party,
+,undefined,Undefined,The risk is not clearly assigned to a specific party. Further details can be provided in the notes field.,
diff --git a/en/extensions/risk_allocation/v1.1/codelists/riskCategory.csv b/en/extensions/risk_allocation/v1.1/codelists/riskCategory.csv
new file mode 100644
index 000000000..bd7a739a1
--- /dev/null
+++ b/en/extensions/risk_allocation/v1.1/codelists/riskCategory.csv
@@ -0,0 +1,13 @@
+Category,Code,Title_en,Description_en,Source
+,development,Development Risk,"Risks relating to the development phase, which involves the preparation and procurement of the project up to financial close, including invitation to tender and bidding; negotiation of the various project documents; and obtaining debt and equity funding.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,completion,Completion Risk,"The risk that the project is not completed in accordance with its initial specifications within the agreed timeframe. Completion risk covers: construction, testing and commissioning of the project.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,costIncrease,Cost Increase Risk,"The risk that the amount forecast for the cost of construction and operation of the project in the financial model will, for some reason, be surpassed. Cost increase risk includes: exchange rate risk, interest rate and refinancing risk, inflation, taxes, input price increase, construction cost increase, operation cost increase, cost of spare and replacement parts, decrease in off-take price, and coverage of cost overrun risk.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,performance,Performance Risk,"The risk that the project does not perform at the levels specified in the contract. This risk covers design and construction, operation, input supply, and offtake purchaser infrastructure.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,operation,Operation Risk,"Operation risk includes: the risk of defects in design, equipment or materials beyond the construction contractor’s defects liability period, the availability of labor and materials, changes in operating requirements, the cost of asset replacement and major maintenance, the availability of experienced management, the availability of working capital financing to cover short-term financing needs, the availability of locally sourced/cost-effective supplies and services, the availability of associated infrastructure and services, the program for operation and maintenance, as well as other costs subject to change over the period of the concession.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,market,Market Risk,Primary market risks that are likely to be encountered in a PPP project include: offtake (output) price and input cost risk.,"Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,political,Political Risk,"Political risk, such as events of war, rebellion, default or failure of public sector entities, change in law and delays by authorities.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,environmental,Environmental Risk,"Risk related to the liabilities and constraints generated by environmental requirements, and the cost of compliance to environmental laws and regulations.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,social,Social Risk,"Risk related to the project’s impact on the local communities, and the potential resistance from local interest groups that can delay project implementation, increase the cost of implementation and undermine project viability.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,credit,Credit Risk,"The risk that project participants are not able to assume their project obligations to ensure the financial viability of the project. This risk takes into consideration the financial stability, technical capacity, available resources, longevity, and managerial capacity of each such participant.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,compliance,Compliance risks,Risks deriving from the compliance or lack thereof of regulatory obligations related to the development of the project,
+,all,All risks,All risks deriving from the project,
diff --git a/en/extensions/risk_allocation/v1.1/extension.json b/en/extensions/risk_allocation/v1.1/extension.json
new file mode 100644
index 000000000..03cff8398
--- /dev/null
+++ b/en/extensions/risk_allocation/v1.1/extension.json
@@ -0,0 +1,14 @@
+{
+ "name": {
+ "en": "ocds-riskAllocation-extension",
+ "es": "ocds-riskAllocation-extension"
+ },
+ "description": {
+ "en": "Draft risk allocation extension for ppp extension",
+ "es": "Proyecto de extensi\u00f3n de asignaci\u00f3n de riesgos para la extensi\u00f3n de APP"
+ },
+ "documentationUrl": {},
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/en/extensions/risk_allocation/v1.1/index.html b/en/extensions/risk_allocation/v1.1/index.html
new file mode 100644
index 000000000..63cbc4096
--- /dev/null
+++ b/en/extensions/risk_allocation/v1.1/index.html
@@ -0,0 +1,274 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Risk Allocation +
+ ++ For providing the risk allocations defined in a public private partnership's contract. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ riskAllocation.csv +
+ +
+ You can download the riskAllocation.csv file in English.
+
| + Code + | ++ Title_en + | ++ Description_en + | +
|---|---|---|
+
+ publicAuthority
+
+ |
+ + Public authority + | +
+ The risk is wholly or mostly retained by the public authority + + |
+
+
+ privateParty
+
+ |
+ + Private party + | +
+ The risk is wholly or mostly retained by the private party + + |
+
+
+ undefined
+
+ |
+ + Undefined + | +
+ The risk is not clearly assigned to a specific party. Further details can be provided in the notes field. + + |
+
+ riskCategory.csv +
+ +
+ You can download the riskCategory.csv file in English.
+
| + Code + | ++ Title_en + | ++ Description_en + | +
|---|---|---|
+
+ development
+
+ |
+ + Development Risk + | +
+ Risks relating to the development phase, which involves the preparation and procurement of the project up to financial close, including invitation to tender and bidding; negotiation of the various project documents; and obtaining debt and equity funding. + +
|
+
+
+ completion
+
+ |
+ + Completion Risk + | +
+ The risk that the project is not completed in accordance with its initial specifications within the agreed timeframe. Completion risk covers: construction, testing and commissioning of the project. + +
|
+
+
+ costIncrease
+
+ |
+ + Cost Increase Risk + | +
+ The risk that the amount forecast for the cost of construction and operation of the project in the financial model will, for some reason, be surpassed. Cost increase risk includes: exchange rate risk, interest rate and refinancing risk, inflation, taxes, input price increase, construction cost increase, operation cost increase, cost of spare and replacement parts, decrease in off-take price, and coverage of cost overrun risk. + +
|
+
+
+ performance
+
+ |
+ + Performance Risk + | +
+ The risk that the project does not perform at the levels specified in the contract. This risk covers design and construction, operation, input supply, and offtake purchaser infrastructure. + +
|
+
+
+ operation
+
+ |
+ + Operation Risk + | +
+ Operation risk includes: the risk of defects in design, equipment or materials beyond the construction contractor’s defects liability period, the availability of labor and materials, changes in operating requirements, the cost of asset replacement and major maintenance, the availability of experienced management, the availability of working capital financing to cover short-term financing needs, the availability of locally sourced/cost-effective supplies and services, the availability of associated infrastructure and services, the program for operation and maintenance, as well as other costs subject to change over the period of the concession. + +
|
+
+
+ market
+
+ |
+ + Market Risk + | +
+ Primary market risks that are likely to be encountered in a PPP project include: offtake (output) price and input cost risk. + +
|
+
+
+ political
+
+ |
+ + Political Risk + | +
+ Political risk, such as events of war, rebellion, default or failure of public sector entities, change in law and delays by authorities. + +
|
+
+
+ environmental
+
+ |
+ + Environmental Risk + | +
+ Risk related to the liabilities and constraints generated by environmental requirements, and the cost of compliance to environmental laws and regulations. + +
|
+
+
+ social
+
+ |
+ + Social Risk + | +
+ Risk related to the project’s impact on the local communities, and the potential resistance from local interest groups that can delay project implementation, increase the cost of implementation and undermine project viability. + +
|
+
+
+ credit
+
+ |
+ + Credit Risk + | +
+ The risk that project participants are not able to assume their project obligations to ensure the financial viability of the project. This risk takes into consideration the financial stability, technical capacity, available resources, longevity, and managerial capacity of each such participant. + +
|
+
+
+ compliance
+
+ |
+ + Compliance risks + | +
+ Risks deriving from the compliance or lack thereof of regulatory obligations related to the development of the project + + |
+
+
+ all
+
+ |
+ + All risks + | +
+ All risks deriving from the project + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/risk_allocation/v1.1/release-schema.json b/en/extensions/risk_allocation/v1.1/release-schema.json
new file mode 100644
index 000000000..0b410a320
--- /dev/null
+++ b/en/extensions/risk_allocation/v1.1/release-schema.json
@@ -0,0 +1,68 @@
+{
+ "definitions": {
+ "Risk": {
+ "title": "Risk",
+ "description": "A risk relating to the project.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Risk ID",
+ "description": "A local identifier for this risk, unique within this block. This field is used to keep track of multiple revisions of a risk through the compilation from release to record mechanism.",
+ "type": [
+ "string",
+ "integer"
+ ]
+ },
+ "category": {
+ "title": "Risk category",
+ "description": "Specify the category of the risk against the risk category codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "riskCategory.csv",
+ "openCodelist": true
+ },
+ "description": {
+ "title": "Risk description",
+ "description": "A description for this risk.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "allocation": {
+ "title": "Risk allocation",
+ "description": "The party which retains the risk.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "riskAllocation.csv",
+ "openCodelist": false
+ },
+ "notes": {
+ "title": "Risk notes",
+ "description": "Additional notes on the risk, for example the rationale for the allocation",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "riskAllocation": {
+ "title": "Risk allocation",
+ "description": "Information on the allocation of risks relating to the contract.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Risk"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/risk_allocation/v1.1/schema/index.html b/en/extensions/risk_allocation/v1.1/schema/index.html
new file mode 100644
index 000000000..a3b80e1e7
--- /dev/null
+++ b/en/extensions/risk_allocation/v1.1/schema/index.html
@@ -0,0 +1,359 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Risk Allocation +
+ ++ For providing the risk allocations defined in a public private partnership's contract. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The framework for disclosure in PPPs calls for individual risk allocation information.
+The risk allocation extension is used to provide structured data on the risk allocations defined in a public private partnerships contract.
+Overview
+Risk allocations can be represented using an array of risk blocks in the riskAllocation field of the contract section of an OCDS release.
The risk category can be represented using the risk/category field using values from the risk category codelist based on the APMG PPP Certification Program.
The party retaining each risk should be represented using the risk/allocation field using values from the risk allocation codelist.
The description of the risk should be provided as free text using the risk/description field and the mitigation for the risk should be provided as free text using the risk/mitigation field.
Additional free text information on the risk can be provided using the risk/notes field.
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/secondStageDescription/index.html b/en/extensions/secondStageDescription/index.html
new file mode 100644
index 000000000..c4ecd36d0
--- /dev/null
+++ b/en/extensions/secondStageDescription/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Risk Allocation +
+ ++ For providing the risk allocations defined in a public private partnership's contract. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Risk +
+ +
+ The extension defines a new Risk object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Risk ID + | +
+ A local identifier for this risk, unique within this block. This field is used to keep track of multiple revisions of a risk through the compilation from release to record mechanism. + + |
+ + string or integer + | +
+
+ category
+
+ |
+ + Risk category + | +
+ Specify the category of the risk against the risk category codelist. + + |
+ + string from open riskCategory codelist + | +
+
+ description
+
+ |
+ + Risk description + | +
+ A description for this risk. + + |
+ + string + | +
+
+ allocation
+
+ |
+ + Risk allocation + | +
+ The party which retains the risk. + + |
+ + string from closed riskAllocation codelist + | +
+
+ notes
+
+ |
+ + Risk notes + | +
+ Additional notes on the risk, for example the rationale for the allocation + + |
+ + string + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ riskAllocation
+
+ |
+ + Risk allocation + | +
+ Information on the allocation of risks relating to the contract. + + |
+ + array of Risk objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/secondStageDescription/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/secondStageDescription/master/release-schema.json b/en/extensions/secondStageDescription/master/release-schema.json
new file mode 100644
index 000000000..c68392f26
--- /dev/null
+++ b/en/extensions/secondStageDescription/master/release-schema.json
@@ -0,0 +1,71 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "secondStage": {
+ "title": "Second stage",
+ "description": "Information about the second stage of a two-stage procedure (e.g. a restricted procedure, a competitive procedure with negotiation, a competitive dialogue or an innovation partnership).",
+ "$ref": "#/definitions/SecondStage"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "secondStage": {
+ "title": "Second stage",
+ "description": "Information about the second stage of a two-stage procedure (e.g. a restricted procedure, a competitive procedure with negotiation, a competitive dialogue or an innovation partnership).",
+ "$ref": "#/definitions/SecondStage"
+ }
+ }
+ },
+ "SecondStage": {
+ "title": "Second stage",
+ "description": "Information about the second stage of a two-stage procedure (e.g. a restricted procedure, a competitive procedure with negotiation, a competitive dialogue or an innovation partnership).",
+ "type": "object",
+ "properties": {
+ "minimumCandidates": {
+ "title": "Minimum number of candidates",
+ "description": "The minimum number of candidates to be invited for the second stage of the procedure. If there is an exact limit on the number of candidates, set `minimumCandidates` and `maximumCandidates` to the same number.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "maximumCandidates": {
+ "title": "Maximum number of candidates",
+ "description": "The maximum number of candidates to be invited for the second stage of the procedure. If there is an exact limit on the number of candidates, set `minimumCandidates` and `maximumCandidates` to the same number.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "successiveReduction": {
+ "title": "Successive reduction",
+ "description": "The procedure will take place in successive stages. In each stage, some participants might be eliminated.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "noNegotiationNecessary": {
+ "title": "No negotiation necessary",
+ "description": "The buyer or procuring entity reserves the right to award the contract on the basis of the initial bids without any further negotiations.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "invitationDate": {
+ "title": "Invitation date",
+ "description": "The estimated date of dispatch of the invitations to participate or to submit bids.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/secondStageDescription/master/schema/index.html b/en/extensions/secondStageDescription/master/schema/index.html
new file mode 100644
index 000000000..aed8ed3c4
--- /dev/null
+++ b/en/extensions/secondStageDescription/master/schema/index.html
@@ -0,0 +1,401 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Second stage description +
+ ++ Adds a second stage object to the tender and lot objects, to describe the second stage of a two-stage procedure. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a second stage object to the tender and lot objects, to describe the second stage of a two-stage procedure. In particular, it adds two fields to describe the limits on the number of candidates to be invited.
+Guidance
+If there is an exact limit on the number of candidates, set minimumCandidates and maximumCandidates to the same number.
If maximumCandidates is set, use the selection criteria extension (TBD) to describe how the selection criteria will be used to select candidates to be invited for the second stage.
Legal context
+In the European Union, this extension's fields correspond to eForms BG-709 (Second Stage). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "secondStage": {
+ "minimumCandidates": 5,
+ "maximumCandidates": 50,
+ "successiveReduction": true,
+ "noNegotiationNecessary": false,
+ "invitationDate": "2019-08-16T10:30:00Z"
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile, in pull requests and in https://github.com/open-contracting/standard/issues/695.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/selectionCriteria/index.html b/en/extensions/selectionCriteria/index.html
new file mode 100644
index 000000000..fd5e354c5
--- /dev/null
+++ b/en/extensions/selectionCriteria/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Second stage description +
+ ++ Adds a second stage object to the tender and lot objects, to describe the second stage of a two-stage procedure. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ secondStage
+
+ |
+ + Second stage + | +
+ Information about the second stage of a two-stage procedure (e.g. a restricted procedure, a competitive procedure with negotiation, a competitive dialogue or an innovation partnership). + + |
+ + SecondStage object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ secondStage
+
+ |
+ + Second stage + | +
+ Information about the second stage of a two-stage procedure (e.g. a restricted procedure, a competitive procedure with negotiation, a competitive dialogue or an innovation partnership). + + |
+ + SecondStage object + | +
+ SecondStage +
+ +
+ The extension defines a new SecondStage object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ minimumCandidates
+
+ |
+ + Minimum number of candidates + | +
+ The minimum number of candidates to be invited for the second stage of the procedure. If there is an exact limit on the number of candidates, set |
+ + number + | +
+
+ maximumCandidates
+
+ |
+ + Maximum number of candidates + | +
+ The maximum number of candidates to be invited for the second stage of the procedure. If there is an exact limit on the number of candidates, set |
+ + number + | +
+
+ successiveReduction
+
+ |
+ + Successive reduction + | +
+ The procedure will take place in successive stages. In each stage, some participants might be eliminated. + + |
+ + boolean + | +
+
+ noNegotiationNecessary
+
+ |
+ + No negotiation necessary + | +
+ The buyer or procuring entity reserves the right to award the contract on the basis of the initial bids without any further negotiations. + + |
+ + boolean + | +
+
+ invitationDate
+
+ |
+ + Invitation date + | +
+ The estimated date of dispatch of the invitations to participate or to submit bids. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/selectionCriteria/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/selectionCriteria/master/codelists/selectionCriterionType.csv b/en/extensions/selectionCriteria/master/codelists/selectionCriterionType.csv
new file mode 100644
index 000000000..475780ee7
--- /dev/null
+++ b/en/extensions/selectionCriteria/master/codelists/selectionCriterionType.csv
@@ -0,0 +1,5 @@
+Code,Title,Description
+economic,Economic,The criterion relates to the economic or financial standing of the tenderer.
+technical,Technical,The criterion relates to the technical or professional ability of the tenderer.
+suitability,Suitability,The criterion relates to the suitability of the tenderer (e.g. enrolment in trade register or membership of professional organization).
+other,Other,The criterion relates to other aspects of the tenderer.
diff --git a/en/extensions/selectionCriteria/master/extension.json b/en/extensions/selectionCriteria/master/extension.json
new file mode 100644
index 000000000..5e9c63d23
--- /dev/null
+++ b/en/extensions/selectionCriteria/master/extension.json
@@ -0,0 +1,33 @@
+{
+ "name": {
+ "en": "Selection Criteria",
+ "es": "Criterios de Selecci\u00f3n"
+ },
+ "description": {
+ "en": "Adds an object to describe the conditions for participation in a contracting process.",
+ "es": "Agrega un objeto para describir las condiciones de participaci\u00f3n en un proceso de contrataci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/selectionCriteria/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "selectionCriterionType.csv",
+ "appliesTo.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "dependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_awardCriteria_extension/master/extension.json"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/en/extensions/selectionCriteria/master/index.html b/en/extensions/selectionCriteria/master/index.html
new file mode 100644
index 000000000..3c8aacd0a
--- /dev/null
+++ b/en/extensions/selectionCriteria/master/index.html
@@ -0,0 +1,363 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Selection Criteria +
+ ++ Adds an object to describe the conditions for participation in a contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ appliesTo.csv +
+ +
+ You can download the appliesTo.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ supplier
+
+ |
+ + Supplier + | +
+ The selection criterion applies to the suppliers. + + |
+
+
+ subcontractor
+
+ |
+ + Subcontractor + | +
+ The selection criterion applies to the subcontractors. + + |
+
+ selectionCriterionType.csv +
+ +
+ You can download the selectionCriterionType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ economic
+
+ |
+ + Economic + | +
+ The criterion relates to the economic or financial standing of the tenderer. + + |
+
+
+ technical
+
+ |
+ + Technical + | +
+ The criterion relates to the technical or professional ability of the tenderer. + + |
+
+
+ suitability
+
+ |
+ + Suitability + | +
+ The criterion relates to the suitability of the tenderer (e.g. enrolment in trade register or membership of professional organization). + + |
+
+
+ other
+
+ |
+ + Other + | +
+ The criterion relates to other aspects of the tenderer. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/selectionCriteria/master/release-schema.json b/en/extensions/selectionCriteria/master/release-schema.json
new file mode 100644
index 000000000..83792afc8
--- /dev/null
+++ b/en/extensions/selectionCriteria/master/release-schema.json
@@ -0,0 +1,131 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "selectionCriteria": {
+ "title": "Selection criteria",
+ "description": "Information about the conditions for participation in a procedure.",
+ "$ref": "#/definitions/SelectionCriteria"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "selectionCriteria": {
+ "title": "Selection criteria",
+ "description": "Information about the conditions for participation in a lot.",
+ "$ref": "#/definitions/SelectionCriteria"
+ }
+ }
+ },
+ "SelectionCriteria": {
+ "title": "Selection criteria",
+ "description": "Information about conditions for participation.",
+ "type": "object",
+ "properties": {
+ "criteria": {
+ "title": "Selection criteria",
+ "description": "The selection criteria.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/SelectionCriterion"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "The description of the criteria used to select the economic operators who will be allowed to bid.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "SelectionCriterion": {
+ "title": "Selection criterion",
+ "description": "Information about the selection criterion.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Type",
+ "description": "The type of the criterion.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "selectionCriterionType.csv",
+ "openCodelist": false,
+ "enum": [
+ "technical",
+ "economic",
+ "suitability",
+ "other",
+ null
+ ]
+ },
+ "description": {
+ "title": "Description",
+ "description": "The description of the criterion.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "minimum": {
+ "title": "Minimum value or level",
+ "description": "The minimum value or level of compliance a candidate needs to meet in order to participate.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "appliesTo": {
+ "title": "Applies to",
+ "description": "Whether the criterion applies to suppliers, subcontractors, or both.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "supplier",
+ "subcontractor"
+ ]
+ },
+ "codelist": "appliesTo.csv",
+ "openCodelist": false,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "forReduction": {
+ "title": "For reduction?",
+ "description": "Whether the criterion is used to select the potential suppliers to be invited to the second stage of the contracting process, if the number of invitations is limited.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "numbers": {
+ "title": "Numbers",
+ "description": "Numbers linked to the criterion.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/CriterionNumber"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/selectionCriteria/master/schema/index.html b/en/extensions/selectionCriteria/master/schema/index.html
new file mode 100644
index 000000000..259ed7fdd
--- /dev/null
+++ b/en/extensions/selectionCriteria/master/schema/index.html
@@ -0,0 +1,491 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Selection Criteria +
+ ++ Adds an object to describe the conditions for participation in a contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an object to describe the criteria to qualify candidates to participate in a contracting process.
+This extension must be used with the Award criteria breakdown extension.
+If your data closely follows the Core Criterion and Core Evidence Vocabulary (CCCEV), consider the Requirements extension.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Legal context
+In the European Union, this extension's fields correspond to eForms BG-702 (Selection Criteria) and BG-72 (Selection Criteria Second Stage Invite Number). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Examples
+Tender
+Potential suppliers and subcontractors must demonstrate a minimum of 10 years experience on similar projects.
+{
+ "tender": {
+ "selectionCriteria": {
+ "criteria": [
+ {
+ "description": "Minimum number of years of experience on similar projects",
+ "minimum": "10",
+ "type": "technical",
+ "appliesTo": [
+ "supplier",
+ "subcontractor"
+ ]
+ }
+ ]
+ }
+ }
+}
+Lot
+A tender with a single lot where the selection criterion only applies for selecting candidates to be invited to the second stage of the procedure. The candidates will be selected only if the rate of their turnover over the value of the contract is at least 2.
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "selectionCriteria": {
+ "criteria": [
+ {
+ "description": "Turnover over contract value rate",
+ "type": "economic",
+ "forReduction": true,
+ "numbers": [
+ {
+ "number": 2,
+ "threshold": "minimumScore"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-04-05
+-
+
- Add
forReductionandnumbersfields to theSelectionCriterionobject. Thenumbersfield reuses theCriterionNumberdefinition from the Award criteria breakdown extension.
+
2020-07-13
+-
+
- Add
appliesTofield.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/shareholders/index.html b/en/extensions/shareholders/index.html
new file mode 100644
index 000000000..1864a5e59
--- /dev/null
+++ b/en/extensions/shareholders/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Selection Criteria +
+ ++ Adds an object to describe the conditions for participation in a contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ selectionCriteria
+
+ |
+ + Selection criteria + | +
+ Information about the conditions for participation in a procedure. + + |
+ + SelectionCriteria object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ selectionCriteria
+
+ |
+ + Selection criteria + | +
+ Information about the conditions for participation in a lot. + + |
+ + SelectionCriteria object + | +
+ SelectionCriteria +
+ +
+ The extension defines a new SelectionCriteria object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ criteria
+
+ |
+ + Selection criteria + | +
+ The selection criteria. + + |
+ + array of SelectionCriterion objects + | +
+
+ description
+
+ |
+ + Description + | +
+ The description of the criteria used to select the economic operators who will be allowed to bid. + + |
+ + string + | +
+ SelectionCriterion +
+ +
+ The extension defines a new SelectionCriterion object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Type + | +
+ The type of the criterion. + + |
+ + string from closed selectionCriterionType codelist + | +
+
+ description
+
+ |
+ + Description + | +
+ The description of the criterion. + + |
+ + string + | +
+
+ minimum
+
+ |
+ + Minimum value or level + | +
+ The minimum value or level of compliance a candidate needs to meet in order to participate. + + |
+ + string + | +
+
+ appliesTo
+
+ |
+ + Applies to + | +
+ Whether the criterion applies to suppliers, subcontractors, or both. + + |
+ + array of strings from closed appliesTo codelist + | +
+
+ forReduction
+
+ |
+ + For reduction? + | +
+ Whether the criterion is used to select the potential suppliers to be invited to the second stage of the contracting process, if the number of invitations is limited. + + |
+ + boolean + | +
+
+ numbers
+
+ |
+ + Numbers + | +
+ Numbers linked to the criterion. + + |
+ + array of CriterionNumber objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/shareholders/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/shareholders/master/codelists/votingRights.csv b/en/extensions/shareholders/master/codelists/votingRights.csv
new file mode 100644
index 000000000..1ca302772
--- /dev/null
+++ b/en/extensions/shareholders/master/codelists/votingRights.csv
@@ -0,0 +1,6 @@
+Code,Title,Description
+ordinary,Ordinary voting rights,The shareholder is entitled to a single vote per share in all circumstances
+none,No voting rights,The shareholder is not entitled to vote under any circumstances
+restricted,Restricted voting rights,The shareholder is entitled to vote in specific circumstances only
+additional,Additional voting rights,The shareholder is entitled to more than one vote per share in all circumstances
+enhanced,Enhanced voting rights,The shareholder is entitled to more than one vote per share in specific circumstances only
diff --git a/en/extensions/shareholders/master/extension.json b/en/extensions/shareholders/master/extension.json
new file mode 100644
index 000000000..15f5b7912
--- /dev/null
+++ b/en/extensions/shareholders/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Shareholders",
+ "es": "Accionistas"
+ },
+ "description": {
+ "en": "Adds company ownership fields to the organization object used in the parties array.",
+ "es": "Agrega campos de propiedad de la empresa al objeto de organizaci\u00f3n utilizado en la lista de partes."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/shareholders/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "votingRights.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/shareholders/master/index.html b/en/extensions/shareholders/master/index.html
new file mode 100644
index 000000000..d518a93e1
--- /dev/null
+++ b/en/extensions/shareholders/master/index.html
@@ -0,0 +1,339 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Shareholders +
+ ++ Adds company ownership fields to the organization object used in the parties array. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ votingRights.csv +
+ +
+ You can download the votingRights.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ ordinary
+
+ |
+ + Ordinary voting rights + | +
+ The shareholder is entitled to a single vote per share in all circumstances + + |
+
+
+ none
+
+ |
+ + No voting rights + | +
+ The shareholder is not entitled to vote under any circumstances + + |
+
+
+ restricted
+
+ |
+ + Restricted voting rights + | +
+ The shareholder is entitled to vote in specific circumstances only + + |
+
+
+ additional
+
+ |
+ + Additional voting rights + | +
+ The shareholder is entitled to more than one vote per share in all circumstances + + |
+
+
+ enhanced
+
+ |
+ + Enhanced voting rights + | +
+ The shareholder is entitled to more than one vote per share in specific circumstances only + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/shareholders/master/release-schema.json b/en/extensions/shareholders/master/release-schema.json
new file mode 100644
index 000000000..47a1ea4c3
--- /dev/null
+++ b/en/extensions/shareholders/master/release-schema.json
@@ -0,0 +1,86 @@
+{
+ "definitions": {
+ "Shareholder": {
+ "title": "Shareholding",
+ "description": "A shareholding in an organization.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "A local identifier for this shareholding, unique within this array.",
+ "type": "string",
+ "minLength": 1
+ },
+ "shareholder": {
+ "title": "Shareholder",
+ "description": "The organization holding the share.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "shareholding": {
+ "title": "Shareholding",
+ "description": "The percentage of the organization's shares held by the shareholder, expressed as a decimal between 0 and 1.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "minimum": 0,
+ "maximum": 1
+ },
+ "votingRights": {
+ "title": "Voting rights",
+ "description": "The type of voting rights associated with the shareholder's shares.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "votingRights.csv",
+ "openCodelist": false,
+ "enum": [
+ "ordinary",
+ "none",
+ "restricted",
+ "additional",
+ "enhanced",
+ null
+ ]
+ },
+ "votingRightsDetails": {
+ "title": "Voting rights details",
+ "description": "Detailed information about the voting rights associated with the shareholder's shares: for example, when the shareholder voting rights are restricted, additional or enhanced.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "notes": {
+ "title": "Notes",
+ "description": "Additional notes on the shareholding or shareholder: for example, details on any caps on equity transfer, or lock-in arrangements, applicable to the shareholder.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Organization": {
+ "properties": {
+ "shareholders": {
+ "title": "Shareholdings",
+ "description": "Shareholdings in the organization: used to provide company ownership information for firms, primarily in the case of large and complex contracts, like public private partnerships, that require disclosure of this information by bidders or suppliers.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Shareholder"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/shareholders/master/schema/index.html b/en/extensions/shareholders/master/schema/index.html
new file mode 100644
index 000000000..c87f5d71d
--- /dev/null
+++ b/en/extensions/shareholders/master/schema/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Shareholders +
+ ++ Adds company ownership fields to the organization object used in the parties array. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds company ownership fields to the organization object used in the parties array.
+For example, when bidding in Public Private Partnerships, companies can be required to disclose their ownership information. After a contract is signed and during project implementation, the ownership information of the Special Purpose Vehicle (SPV) that is operating the contract might need to be updated.
+Since each owner mentioned in the shareholders array should have a corresponding entry in the parties array, it is possible to use this extension to describe multiple levels of corporate ownership.
Example
+{
+ "parties": [
+ {
+ "id": "MEGA",
+ "name": "Mega Consortium",
+ "shareholders": [
+ {
+ "id": "1",
+ "shareholder": {
+ "id": "AHL",
+ "name": "Alpha Holdings Ltd"
+ },
+ "shareholding": 0.67,
+ "votingRights": "additional",
+ "votingRightsDetails": "Alpha Holdings Ltd. is entitled to 5 votes per share.",
+ "notes": "Alpha Holdings Ltd. must maintain a minimum shareholding of 30% in the project company until 10 years from the date of commissioning have elapsed."
+ },
+ {
+ "id": "2",
+ "shareholder": {
+ "id": "BET",
+ "name": "Beta Investment Company Ltd"
+ },
+ "shareholding": 0.33,
+ "votingRights": "ordinary"
+ }
+ ]
+ },
+ {
+ "id": "BET",
+ "name": "Beta Investment Company Ltd"
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2021-05-24
+-
+
- Remove
Organization.beneficialOwnership.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2019-03-20
+-
+
- Add
"minLength": 1on required string fields.
+ - Make
Organization.beneficialOwnershipnon-nullable (undo earlier change).
+
2018-05-08
+-
+
- Make
Shareholder.idrequired to support revision tracking and list merging
+
2018-01-29
+-
+
- Make
Organization.beneficialOwnershipnullable.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/shareholders/v1.1/README.md b/en/extensions/shareholders/v1.1/README.md
new file mode 100644
index 000000000..ddd560664
--- /dev/null
+++ b/en/extensions/shareholders/v1.1/README.md
@@ -0,0 +1,13 @@
+# Shareholder and ownership details
+
+The shareholder extension can be used to provide details of the owners of parties involved in a contracting process.
+
+For example, in Public Private Partnerships processes, companies are often required to disclose information on their ownership structures when bidding, and when the contract is awarded, information on the ownership of a Special Purpose Vehicle (SPV) operating the contract may need to be kept up to date during project implementation.
+
+Because each owner mentioned in the shareholders array should also gain an entry in the 'parties' array, it is possible to use this extension to build up information on corporate ownership networks involved in a contracting process.
+
+## Beneficial ownership
+
+This extension also includes a 'stub' entry for recording beneficial ownership information against a party.
+
+At present this includes space for free-text description of ownership and control structures, but this may be further extended with structured beneficial ownership information drawing on the draft [Beneficial Ownership Data Standard](https://github.com/openownership/data-standard).
diff --git a/en/extensions/shareholders/v1.1/codelists/index.html b/en/extensions/shareholders/v1.1/codelists/index.html
new file mode 100644
index 000000000..f8b72ebf6
--- /dev/null
+++ b/en/extensions/shareholders/v1.1/codelists/index.html
@@ -0,0 +1,286 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Shareholders +
+ ++ Adds company ownership fields to the organization object used in the parties array. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Shareholder +
+ +
+ The extension defines a new Shareholder object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ A local identifier for this shareholding, unique within this array. + + |
+ + string + | +
+
+ shareholder
+
+ |
+ + Shareholder + | +
+ The organization holding the share. + + |
+ + OrganizationReference object + | +
+
+ shareholding
+
+ |
+ + Shareholding + | +
+ The percentage of the organization's shares held by the shareholder, expressed as a decimal between 0 and 1. + + |
+ + number + | +
+
+ votingRights
+
+ |
+ + Voting rights + | +
+ The type of voting rights associated with the shareholder's shares. + + |
+ + string from closed votingRights codelist + | +
+
+ votingRightsDetails
+
+ |
+ + Voting rights details + | +
+ Detailed information about the voting rights associated with the shareholder's shares: for example, when the shareholder voting rights are restricted, additional or enhanced. + + |
+ + string + | +
+
+ notes
+
+ |
+ + Notes + | +
+ Additional notes on the shareholding or shareholder: for example, details on any caps on equity transfer, or lock-in arrangements, applicable to the shareholder. + + |
+ + string + | +
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ shareholders
+
+ |
+ + Shareholdings + | +
+ Shareholdings in the organization: used to provide company ownership information for firms, primarily in the case of large and complex contracts, like public private partnerships, that require disclosure of this information by bidders or suppliers. + + |
+ + array of Shareholder objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/shareholders/v1.1/codelists/votingRights.csv b/en/extensions/shareholders/v1.1/codelists/votingRights.csv
new file mode 100644
index 000000000..e787d158c
--- /dev/null
+++ b/en/extensions/shareholders/v1.1/codelists/votingRights.csv
@@ -0,0 +1,6 @@
+Category,Code,Title_en,Description_en,Source
+,ordinary,Ordinary voting rights,The shareholder is entitled to a single vote per share in all circumstances,
+,none,No voting rights,The shareholder is not entitled to vote under any circumstances,
+,restricted,Restricted voting rights,The shareholder is entitled to vote in specific circumstances only,
+,additional,Additional voting rights,The shareholder is entitled to more than one vote per share in all circumstances,
+,enhanced,Enhanced voting rights,The shareholder is entitled to more than one vote per share in specific circumstances only,
diff --git a/en/extensions/shareholders/v1.1/extension.json b/en/extensions/shareholders/v1.1/extension.json
new file mode 100644
index 000000000..3403523b7
--- /dev/null
+++ b/en/extensions/shareholders/v1.1/extension.json
@@ -0,0 +1,14 @@
+{
+ "name": {
+ "en": "ocds-shareholders-extension",
+ "es": "ocds-shareholders-extension"
+ },
+ "description": {
+ "en": "The shareholders extension can be used to attach company ownership details to each party in the parties array.",
+ "es": "La extensi\u00f3n de las partes se puede utilizar para adjuntar los detalles de propiedad de la compa\u00f1\u00eda a cada parte en la matriz de partes."
+ },
+ "documentationUrl": {},
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/en/extensions/shareholders/v1.1/index.html b/en/extensions/shareholders/v1.1/index.html
new file mode 100644
index 000000000..67429ba46
--- /dev/null
+++ b/en/extensions/shareholders/v1.1/index.html
@@ -0,0 +1,272 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Shareholders +
+ ++ Adds company ownership fields to the organization object used in the parties array. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ votingRights.csv +
+ +
+ You can download the votingRights.csv file in English.
+
| + Code + | ++ Title_en + | ++ Description_en + | +
|---|---|---|
+
+ ordinary
+
+ |
+ + Ordinary voting rights + | +
+ The shareholder is entitled to a single vote per share in all circumstances + + |
+
+
+ none
+
+ |
+ + No voting rights + | +
+ The shareholder is not entitled to vote under any circumstances + + |
+
+
+ restricted
+
+ |
+ + Restricted voting rights + | +
+ The shareholder is entitled to vote in specific circumstances only + + |
+
+
+ additional
+
+ |
+ + Additional voting rights + | +
+ The shareholder is entitled to more than one vote per share in all circumstances + + |
+
+
+ enhanced
+
+ |
+ + Enhanced voting rights + | +
+ The shareholder is entitled to more than one vote per share in specific circumstances only + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/shareholders/v1.1/release-schema.json b/en/extensions/shareholders/v1.1/release-schema.json
new file mode 100644
index 000000000..6268200b5
--- /dev/null
+++ b/en/extensions/shareholders/v1.1/release-schema.json
@@ -0,0 +1,84 @@
+{
+ "definitions": {
+ "Shareholder": {
+ "type": "object",
+ "title": "Shareholder",
+ "description": "A shareholder in an organization.",
+ "properties": {
+ "id": {
+ "title": "Shareholder ID",
+ "description": "A local identifier for this shareholder, unique within this block. This field is used to keep track of multiple revisions of a shareholder through the compilation from release to record mechanism.",
+ "type": [
+ "string"
+ ]
+ },
+ "shareholder": {
+ "title": "Shareholder organization reference.",
+ "description": "An organization reference pointing the entry in the parties section for the shareholding organization.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "shareholding": {
+ "title": "Shareholding",
+ "description": "The percentage of shares held by the shareholder, expressed as a decimal value between 0 and 1.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "minimum": 0,
+ "maximum": 1
+ },
+ "votingRights": {
+ "title": "Shareholder voting rights",
+ "description": "Specify the type of voting rights associated with the shares held by the shareholder against the [voting rights codelist](http://standard.open-contracting.org/latest/en/schema/codelists/#voting-rights).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "votingRights.csv",
+ "openCodelist": false
+ },
+ "votingRightsDetails": {
+ "title": "Shareholder voting rights details",
+ "description": "Detailed information about the shareholder's voting rights. This field should be completed when the shareholder voting rights are restricted, additional or enhanced.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "notes": {
+ "title": "Shareholder notes",
+ "description": "Additional notes on this shareholder. This field should be used to provide details on any caps on equity transfer, or lock-in arrangements, applicable to this shareholder.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Organization": {
+ "properties": {
+ "shareholders": {
+ "title": "Organization shareholders",
+ "description": "A list of shareholders in the organization: used to provide company ownership information for firms, primarily in the case of large and complex contracts, or Public Private Partnerships, that require disclosure of this information for certain bidders or awarded parties.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Shareholder"
+ },
+ "uniqueItems": true
+ },
+ "beneficialOwnership": {
+ "type": "object",
+ "title": "Beneficial ownership",
+ "description": "This section can be used to record information concerning individuals or organisations with a beneficial ownership or control interests in this party. Where structured data is available, this section may be extended by embedding or linking to information modelled using the [Beneficial Ownership Data Standard (BODS)](https://github.com/openownership/data-standard).",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "A free text description of beneficial ownership or control arrangements.",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/shareholders/v1.1/schema/index.html b/en/extensions/shareholders/v1.1/schema/index.html
new file mode 100644
index 000000000..397c7954a
--- /dev/null
+++ b/en/extensions/shareholders/v1.1/schema/index.html
@@ -0,0 +1,410 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Shareholders +
+ ++ Adds company ownership fields to the organization object used in the parties array. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+The shareholder extension can be used to provide details of the owners of parties involved in a contracting process.
+For example, in Public Private Partnerships processes, companies are often required to disclose information on their ownership structures when bidding, and when the contract is awarded, information on the ownership of a Special Purpose Vehicle (SPV) operating the contract may need to be kept up to date during project implementation.
+Because each owner mentioned in the shareholders array should also gain an entry in the 'parties' array, it is possible to use this extension to build up information on corporate ownership networks involved in a contracting process.
+Beneficial ownership
+This extension also includes a 'stub' entry for recording beneficial ownership information against a party.
+At present this includes space for free-text description of ownership and control structures, but this may be further extended with structured beneficial ownership information drawing on the draft Beneficial Ownership Data Standard.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/signatories/index.html b/en/extensions/signatories/index.html
new file mode 100644
index 000000000..00f1f4cd6
--- /dev/null
+++ b/en/extensions/signatories/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Shareholders +
+ ++ Adds company ownership fields to the organization object used in the parties array. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Shareholder +
+ +
+ The extension defines a new Shareholder object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Shareholder ID + | +
+ A local identifier for this shareholder, unique within this block. This field is used to keep track of multiple revisions of a shareholder through the compilation from release to record mechanism. + + |
+ + string + | +
+
+ shareholder
+
+ |
+ + Shareholder organization reference. + | +
+ An organization reference pointing the entry in the parties section for the shareholding organization. + + |
+ + OrganizationReference object + | +
+
+ shareholding
+
+ |
+ + Shareholding + | +
+ The percentage of shares held by the shareholder, expressed as a decimal value between 0 and 1. + + |
+ + number + | +
+
+ votingRights
+
+ |
+ + Shareholder voting rights + | +
+ Specify the type of voting rights associated with the shares held by the shareholder against the voting rights codelist. + + |
+ + string from closed votingRights codelist + | +
+
+ votingRightsDetails
+
+ |
+ + Shareholder voting rights details + | +
+ Detailed information about the shareholder's voting rights. This field should be completed when the shareholder voting rights are restricted, additional or enhanced. + + |
+ + string + | +
+
+ notes
+
+ |
+ + Shareholder notes + | +
+ Additional notes on this shareholder. This field should be used to provide details on any caps on equity transfer, or lock-in arrangements, applicable to this shareholder. + + |
+ + string + | +
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ shareholders
+
+ |
+ + Organization shareholders + | +
+ A list of shareholders in the organization: used to provide company ownership information for firms, primarily in the case of large and complex contracts, or Public Private Partnerships, that require disclosure of this information for certain bidders or awarded parties. + + |
+ + array of Shareholder objects + | +
+
+ beneficialOwnership
+
+ |
+ + Beneficial ownership + | +
+ This section can be used to record information concerning individuals or organisations with a beneficial ownership or control interests in this party. Where structured data is available, this section may be extended by embedding or linking to information modelled using the Beneficial Ownership Data Standard (BODS). + + |
+ + object + | +
+
+ beneficialOwnership.
+ |
+ + Description + | +
+ A free text description of beneficial ownership or control arrangements. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/signatories/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/signatories/master/release-schema.json b/en/extensions/signatories/master/release-schema.json
new file mode 100644
index 000000000..ea373e2ec
--- /dev/null
+++ b/en/extensions/signatories/master/release-schema.json
@@ -0,0 +1,18 @@
+{
+ "definitions": {
+ "Contract": {
+ "properties": {
+ "signatories": {
+ "title": "Contract signatories",
+ "description": "The signatories to the contract. Each signatory should have a corresponding entry in the `parties` array.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/signatories/master/schema/index.html b/en/extensions/signatories/master/schema/index.html
new file mode 100644
index 000000000..0526cd5fc
--- /dev/null
+++ b/en/extensions/signatories/master/schema/index.html
@@ -0,0 +1,231 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Signatories +
+ ++ Adds a signatories array to the contract object, for when the signatories differ from the buyer for the contracting process and the suppliers for the award. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a signatories array to the contract object, for when the signatories differ from the buyer for the contracting process and the suppliers for the award.
+In OCDS, the signatories to a contract are not explicitly declared in the contracts section. Instead, the signatories are implicitly assumed to be the buyer and the suppliers in the award associated to the contract.
In some types of contracting processes, there can be additional signatories to the contract, or the signatories to the contract can differ from those specified in buyer and suppliers.
Use this extension only if the signatories to a contract differ from its related award's suppliers and the contracting process' buyer. If that is the case, list all signatories to the contract, including the buyer and suppliers.
Guidance
+Each signatory should have an associated entry in the parties section.
Example
+The following JSON snippet models a contracting process where there is an additional signatory to the contract beyond those defined in the buyer and awards.suppliers fields.
{
+ "buyer": {
+ "name": "Ministry of Communications",
+ "id": "GB-GOV-12345678"
+ },
+ "awards": [
+ {
+ "id": "1",
+ "suppliers": [
+ {
+ "name": "Example Consortium",
+ "id": "GB-COH-00000000"
+ }
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "signatories": [
+ {
+ "name": "Ministry of Communications",
+ "id": "GB-GOV-12345678"
+ },
+ {
+ "name": "Example Consortium",
+ "id": "GB-COH-00000000"
+ },
+ {
+ "name": "Telecommunications UK",
+ "id": "GB-GOV-99999999"
+ }
+ ]
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/statistics/index.html b/en/extensions/statistics/index.html
new file mode 100644
index 000000000..f32a5c616
--- /dev/null
+++ b/en/extensions/statistics/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Signatories +
+ ++ Adds a signatories array to the contract object, for when the signatories differ from the buyer for the contracting process and the suppliers for the award. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ signatories
+
+ |
+ + Contract signatories + | +
+ The signatories to the contract. Each signatory should have a corresponding entry in the |
+ + array of OrganizationReference objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/statistics/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/statistics/master/codelists/statisticScope.csv b/en/extensions/statistics/master/codelists/statisticScope.csv
new file mode 100644
index 000000000..a1a298817
--- /dev/null
+++ b/en/extensions/statistics/master/codelists/statisticScope.csv
@@ -0,0 +1,2 @@
+Code,Title,Description
+complaints,Complaints,Statistics relating to complaints and complainants. Also known as review requests.
diff --git a/en/extensions/statistics/master/extension.json b/en/extensions/statistics/master/extension.json
new file mode 100644
index 000000000..e39a6cba6
--- /dev/null
+++ b/en/extensions/statistics/master/extension.json
@@ -0,0 +1,30 @@
+{
+ "name": {
+ "en": "Statistics",
+ "es": "Statistics"
+ },
+ "description": {
+ "en": "Adds a top-level statistics array to describe statistics about the contracting process.",
+ "es": "Adds a top-level statistics array to describe statistics about the contracting process."
+ },
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting-extensions/ocds_statistics_extension"
+ },
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+statistic.csv",
+ "statisticScope.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ],
+ "dependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/statistics/master/index.html b/en/extensions/statistics/master/index.html
new file mode 100644
index 000000000..0c8bea002
--- /dev/null
+++ b/en/extensions/statistics/master/index.html
@@ -0,0 +1,292 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Statistics +
+ ++ Adds a top-level statistics array to describe statistics about the contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +statistic.csv +
+ +
+ You can download the +statistic.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ complainants
+
+ |
+ + Complainants + | +
+ The total number of organizations that submitted a complaint. + + |
+
+ statisticScope.csv +
+ +
+ You can download the statisticScope.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ complaints
+
+ |
+ + Complaints + | +
+ Statistics relating to complaints and complainants. Also known as review requests. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/statistics/master/release-schema.json b/en/extensions/statistics/master/release-schema.json
new file mode 100644
index 000000000..10a2d8f33
--- /dev/null
+++ b/en/extensions/statistics/master/release-schema.json
@@ -0,0 +1,35 @@
+{
+ "properties": {
+ "statistics": {
+ "title": "Statistics",
+ "description": "Statistics about the contracting process.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Statistic"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "definitions": {
+ "Statistic": {
+ "properties": {
+ "scope": {
+ "title": "Scope",
+ "description": "The scope of the statistic, from the closed statistic scope codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "statisticScope.csv",
+ "openCodelist": false,
+ "enum": [
+ "complaints",
+ null
+ ]
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/statistics/master/schema/index.html b/en/extensions/statistics/master/schema/index.html
new file mode 100644
index 000000000..269266ce8
--- /dev/null
+++ b/en/extensions/statistics/master/schema/index.html
@@ -0,0 +1,287 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Statistics +
+ ++ Adds a top-level statistics array to describe statistics about the contracting process. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a top-level statistics array to describe statistics about the contracting process.
+This extension must be used with the Bid statistics and details extension.
+Guidance
+If you use a codelist for statistics.measure, you should explain where the codes are from in your publication policy/user guide.
Example
+A statistic describing the number of complaints received about the unjustified rejection of abnormally low tenders. The value of statistics.measure is taken from the EU's irregularity type codelist.
{
+ "statistics": [
+ {
+ "id": "1",
+ "value": 2,
+ "measure": "ab-low",
+ "scope": "complaints",
+ "notes": "Unjustified rejection of abnormally low tenders"
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/statusDetails/index.html b/en/extensions/statusDetails/index.html
new file mode 100644
index 000000000..31c8d15df
--- /dev/null
+++ b/en/extensions/statusDetails/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Statistics +
+ ++ Adds a top-level statistics array to describe statistics about the contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statistics
+
+ |
+ + Statistics + | +
+ Statistics about the contracting process. + + |
+ + array of Statistic objects + | +
+ Statistic +
+ +
+ The extension defines these fields in the Statistic object from the Bid statistics and details extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ scope
+
+ |
+ + Scope + | +
+ The scope of the statistic, from the closed statistic scope codelist. + + |
+ + string from closed statisticScope codelist + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/statusDetails/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/statusDetails/master/release-schema.json b/en/extensions/statusDetails/master/release-schema.json
new file mode 100644
index 000000000..7f62f1ba8
--- /dev/null
+++ b/en/extensions/statusDetails/master/release-schema.json
@@ -0,0 +1,48 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "mainProcurementCategoryDetails": {
+ "title": "Main Procurement Category Details",
+ "description": "The local name of the Main Procurement Category",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "statusDetails": {
+ "title": "Status Details",
+ "description": "Additional detail on the status of the tender. This field can be used to provide the local name of the status.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "statusDetails": {
+ "title": "Status Details",
+ "description": "Additional detail on the status of the award. This field can be used to provide the local name of the status.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "statusDetails": {
+ "title": "Status Details",
+ "description": "Additional detail on the status of the contract. This field can be used to provide the local name of the status",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/statusDetails/master/schema/index.html b/en/extensions/statusDetails/master/schema/index.html
new file mode 100644
index 000000000..da7746b88
--- /dev/null
+++ b/en/extensions/statusDetails/master/schema/index.html
@@ -0,0 +1,350 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Status Details +
+ ++ Add a statusDetails field to Tender, Award and Contract object +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+In some cases, it is important to preserve the local name of the status in which the tender, award or contract are. This extension adds the field statusDetails to the tender, award and contract objecs, in order to provide the local name of the particular status used.
Examples
+{
+ "tender": {
+ "id": "tender-1",
+ "status": "complete",
+ "statusDetails": "Adjudicado"
+ },
+ "awards": [
+ {
+ "id": "award-1",
+ "status": "active",
+ "statusDetails": "Adjudicado"
+ }
+ ],
+ "contracts": [
+ {
+ "id": "contract-1",
+ "awardID": "award-1",
+ "status": "active",
+ "statusDetails": "Adjudicado"
+ }
+ ]
+}
+An example of contract.statusDetails reflecting a court order:
{
+ "tender": {
+ "id": "tender-1",
+ "status": "complete"
+ },
+ "awards": [
+ {
+ "id": "award-1",
+ "status": "active"
+ }
+ ],
+ "contracts": [
+ {
+ "id": "contract-1",
+ "awardID": "award-1",
+ "status": "active",
+ "statusDetails": "Suspended as a result of a court order."
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2021-01-11
+-
+
- Add example of
contract.statusDetailsreflecting a court order.
+
This extension was originally discussed in https://github.com/open-contracting/standard/issues/764.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/subcontracting/index.html b/en/extensions/subcontracting/index.html
new file mode 100644
index 000000000..786786942
--- /dev/null
+++ b/en/extensions/subcontracting/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Status Details +
+ ++ Add a statusDetails field to Tender, Award and Contract object +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ mainProcurementCategoryDetails
+
+ |
+ + Main Procurement Category Details + | +
+ The local name of the Main Procurement Category + + |
+ + string + | +
+
+ statusDetails
+
+ |
+ + Status Details + | +
+ Additional detail on the status of the tender. This field can be used to provide the local name of the status. + + |
+ + string + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statusDetails
+
+ |
+ + Status Details + | +
+ Additional detail on the status of the award. This field can be used to provide the local name of the status. + + |
+ + string + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statusDetails
+
+ |
+ + Status Details + | +
+ Additional detail on the status of the contract. This field can be used to provide the local name of the status + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/subcontracting/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/subcontracting/master/extension.json b/en/extensions/subcontracting/master/extension.json
new file mode 100644
index 000000000..c9aebf61a
--- /dev/null
+++ b/en/extensions/subcontracting/master/extension.json
@@ -0,0 +1,30 @@
+{
+ "name": {
+ "en": "Subcontracting",
+ "es": "Subcontrataci\u00f3n"
+ },
+ "description": {
+ "en": "Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties.",
+ "es": "Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/subcontracting/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+partyRole.csv"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json",
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/subcontracting/master/index.html b/en/extensions/subcontracting/master/index.html
new file mode 100644
index 000000000..af960754c
--- /dev/null
+++ b/en/extensions/subcontracting/master/index.html
@@ -0,0 +1,428 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Subcontracting +
+ ++ Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ subcontractor
+
+ |
+ + Subcontractor + | +
+ An organization that will perform part of a contract on behalf of a supplier. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/subcontracting/master/release-schema.json b/en/extensions/subcontracting/master/release-schema.json
new file mode 100644
index 000000000..c4b29ee1e
--- /dev/null
+++ b/en/extensions/subcontracting/master/release-schema.json
@@ -0,0 +1,210 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "subcontractingTerms": {
+ "title": "Subcontracting terms",
+ "description": "Information about the terms governing subcontracting.",
+ "$ref": "#/definitions/SubcontractingTerms"
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "hasSubcontracting": {
+ "title": "Subcontracting involved",
+ "description": "Whether a part of the contract will be subcontracted.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "subcontracting": {
+ "title": "Subcontracting",
+ "description": "Information about the parts of the contract that the supplier will subcontract to third parties.",
+ "$ref": "#/definitions/Subcontracting"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "subcontractingTerms": {
+ "title": "Subcontracting terms",
+ "description": "Information about the terms governing subcontracting.",
+ "$ref": "#/definitions/SubcontractingTerms"
+ }
+ }
+ },
+ "Bid": {
+ "properties": {
+ "hasSubcontracting": {
+ "title": "Subcontracting involved",
+ "description": "Whether a part of the contract will be subcontracted to third parties.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "subcontracting": {
+ "title": "Subcontracting",
+ "description": "Information about the parts of the contract that will be subcontracted to third parties.",
+ "$ref": "#/definitions/Subcontracting"
+ }
+ }
+ },
+ "SubcontractingTerms": {
+ "title": "Subcontracting terms",
+ "description": "The obligations of the suppliers who subcontract.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "A description of the terms governing subcontracting.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "competitiveMaximumPercentage": {
+ "title": "Maximum percentage of contract value for competitive subcontracting",
+ "description": "The maximum percentage of the contract value that the buyer or procuring entity allows the supplier to subcontract to third parties through a competitive procedure.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0,
+ "exclusiveMinimum": true
+ },
+ "competitiveMinimumPercentage": {
+ "title": "Minimum percentage of contract value for competitive subcontracting",
+ "description": "The minimum percentage of the contract value that the buyer or procuring entity requires the supplier to subcontract to third parties through a competitive procedure.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0
+ }
+ },
+ "minProperties": 1
+ },
+ "Subcontracting": {
+ "title": "Subcontracting",
+ "description": "Information about the parts of the contract that will be subcontracted to third parties.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "The description of the part of the contract that will be subcontracted to third parties.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "maximumPercentage": {
+ "title": "Maximum percentage of contract value",
+ "description": "The maximum percentage of the contract value that will be subcontracted.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0,
+ "exclusiveMinimum": true
+ },
+ "minimumPercentage": {
+ "title": "Minimum percentage of contract value",
+ "description": "The minimum percentage of the contract value that will be subcontracted.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0
+ },
+ "competitiveMaximumPercentage": {
+ "title": "Maximum percentage of contract value for competitive subcontracting",
+ "description": "The maximum percentage of the contract value that the buyer or procuring entity allows the supplier to subcontract to third parties through a competitive procedure.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0,
+ "exclusiveMinimum": true
+ },
+ "competitiveMinimumPercentage": {
+ "title": "Minimum percentage of contract value for competitive subcontracting",
+ "description": "The minimum percentage of the contract value that the buyer or procuring entity requires the supplier to subcontract to third parties through a competitive procedure.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0
+ },
+ "value": {
+ "title": "Subcontracted value",
+ "description": "The estimated value of the part of the contract that will be subcontracted to third parties.",
+ "$ref": "#/definitions/Value"
+ },
+ "competitive": {
+ "title": "Competitive subcontracting",
+ "description": "Whether the supplier will subcontract part of the contract to third parties through a competitive procedure.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "subcontracts": {
+ "title": "Subcontracts",
+ "description": "Information about the subcontracts that will be established.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Subcontract"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Subcontract": {
+ "title": "Subcontract",
+ "description": "A relationship that suppliers establish with a third party to perform part of the contract on their behalf.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "The locally unique identifier for the subcontract.",
+ "type": [
+ "string"
+ ],
+ "minLength": 1
+ },
+ "subcontractor": {
+ "title": "Subcontractor",
+ "description": "The organization that performs part of the contract on behalf of the suppliers.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "mainContractors": {
+ "title": "Main contractors",
+ "description": "The organizations to which the subcontractor will be subcontracted, if they are a subset of the tenderers submitting the bid or the suppliers receiving the award.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/subcontracting/master/schema/index.html b/en/extensions/subcontracting/master/schema/index.html
new file mode 100644
index 000000000..8c4a53521
--- /dev/null
+++ b/en/extensions/subcontracting/master/schema/index.html
@@ -0,0 +1,763 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Subcontracting +
+ ++ Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
If the percentage of the contract value that is subcontracted is an exact number and not a range, set minimumPercentage and maximumPercentage to the same number.
Legal context
+In the European Union, this extension's fields correspond to article 21 of directive 2009/81/EC and the eForms business terms in BG-180 (Subcontracting) and BG-711 (Contract Terms).
+For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+TED XML schema R2.0.9 models the minimum and maximum percentages of the contract value that the contractor needs to subcontract as part of each award for F15: Voluntary ex ante transparency notice. eForms XML models these as part of each lot. As such, different fields ought to be used when implementing each profile.
+Examples
+Tender and awards
+Information about the terms governing subcontracting is disclosed at the tender and award stages, and information about the parts of the contract that the supplier will subcontract is disclosed at the award stage.
+{
+ "tender": {
+ "subcontractingTerms": {
+ "description": "The successful tenderer is obliged to specify which part or parts of the contract it intends to subcontract beyond the required percentage and to indicate the subcontractors already identified."
+ }
+ },
+ "awards": [
+ {
+ "id": "1",
+ "hasSubcontracting": true,
+ "subcontracting": {
+ "competitive": true,
+ "value": {
+ "amount": 28000,
+ "currency": "EUR"
+ },
+ "minimumPercentage": 0.3,
+ "maximumPercentage": 0.3,
+ "competitiveMinimumPercentage": 0.1,
+ "competitiveMaximumPercentage": 0.25,
+ "description": "The painting and electricity tasks are subcontracted."
+ }
+ }
+ ]
+}
+Lots and bids
+Information about the terms governing subcontracting is disclosed per lot at the tender stage, and information about the parts of the contract that the tenderer will subcontract is disclosed at the bid stage.
+{
+ "parties": [
+ {
+ "id": "ORG-0005",
+ "roles": [
+ "tenderer"
+ ]
+ },
+ {
+ "id": "ORG-0012",
+ "roles": [
+ "subcontractor"
+ ]
+ }
+ ],
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "subcontractingTerms": {
+ "description": "The contractor must subcontract a minimum percentage of the contract using the procedure set out in Title III of Directive 2009/81/EC.",
+ "competitiveMinimumPercentage": 0.255,
+ "competitiveMaximumPercentage": 0.455
+ }
+ }
+ ]
+ },
+ "bids": {
+ "details": [
+ {
+ "id": "1",
+ "hasSubcontracting": true,
+ "subcontracting": {
+ "description": "The subcontracting will be...",
+ "value": {
+ "amount": 9999999.99,
+ "currency": "EUR"
+ },
+ "minimumPercentage": 0.3,
+ "maximumPercentage": 0.3,
+ "subcontracts": [
+ {
+ "id": "1",
+ "subcontractor": {
+ "id": "ORG-0012",
+ "name": "Company ABC"
+ },
+ "mainContractors": [
+ {
+ "id": "ORG-0005",
+ "name": "Tendering Company Ltd"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-05-22
+-
+
- Add fields for eForms:
+
-
+
Bid.hasSubcontracting
+Bid.subcontracting
+SubcontractingTerms.competitiveMaximumPercentage
+SubcontractingTerms.competitiveMinimumPercentage
+Subcontracting.subcontracts
+
+ - Update field descriptions to allow the
Subcontractingobject to be used in the context of bids: +-
+
Subcontracting
+Subcontracting.description
+Subcontracting.value
+
+ - Add 'subcontractor' to party role codelist. +
2022-07-18
+-
+
- Add
Lot.subcontractingTermsfield.
+
2020-10-07
+-
+
- Rename the
subcontractingfield in theTenderobject tosubcontractingTerms.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests. You can also see discussions about this extension in this issue.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/submissionTerms/index.html b/en/extensions/submissionTerms/index.html
new file mode 100644
index 000000000..c353539b7
--- /dev/null
+++ b/en/extensions/submissionTerms/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Subcontracting +
+ ++ Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ subcontractingTerms
+
+ |
+ + Subcontracting terms + | +
+ Information about the terms governing subcontracting. + + |
+ + SubcontractingTerms object + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasSubcontracting
+
+ |
+ + Subcontracting involved + | +
+ Whether a part of the contract will be subcontracted. + + |
+ + boolean + | +
+
+ subcontracting
+
+ |
+ + Subcontracting + | +
+ Information about the parts of the contract that the supplier will subcontract to third parties. + + |
+ + Subcontracting object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ subcontractingTerms
+
+ |
+ + Subcontracting terms + | +
+ Information about the terms governing subcontracting. + + |
+ + SubcontractingTerms object + | +
+ Bid +
+ +
+ The extension defines these fields in the Bid object from the Bid statistics and details extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasSubcontracting
+
+ |
+ + Subcontracting involved + | +
+ Whether a part of the contract will be subcontracted to third parties. + + |
+ + boolean + | +
+
+ subcontracting
+
+ |
+ + Subcontracting + | +
+ Information about the parts of the contract that will be subcontracted to third parties. + + |
+ + Subcontracting object + | +
+ SubcontractingTerms +
+ +
+ The extension defines a new SubcontractingTerms object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ A description of the terms governing subcontracting. + + |
+ + string + | +
+
+ competitiveMaximumPercentage
+
+ |
+ + Maximum percentage of contract value for competitive subcontracting + | +
+ The maximum percentage of the contract value that the buyer or procuring entity allows the supplier to subcontract to third parties through a competitive procedure. + + |
+ + number + | +
+
+ competitiveMinimumPercentage
+
+ |
+ + Minimum percentage of contract value for competitive subcontracting + | +
+ The minimum percentage of the contract value that the buyer or procuring entity requires the supplier to subcontract to third parties through a competitive procedure. + + |
+ + number + | +
+ Subcontracting +
+ +
+ The extension defines a new Subcontracting object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ The description of the part of the contract that will be subcontracted to third parties. + + |
+ + string + | +
+
+ maximumPercentage
+
+ |
+ + Maximum percentage of contract value + | +
+ The maximum percentage of the contract value that will be subcontracted. + + |
+ + number + | +
+
+ minimumPercentage
+
+ |
+ + Minimum percentage of contract value + | +
+ The minimum percentage of the contract value that will be subcontracted. + + |
+ + number + | +
+
+ competitiveMaximumPercentage
+
+ |
+ + Maximum percentage of contract value for competitive subcontracting + | +
+ The maximum percentage of the contract value that the buyer or procuring entity allows the supplier to subcontract to third parties through a competitive procedure. + + |
+ + number + | +
+
+ competitiveMinimumPercentage
+
+ |
+ + Minimum percentage of contract value for competitive subcontracting + | +
+ The minimum percentage of the contract value that the buyer or procuring entity requires the supplier to subcontract to third parties through a competitive procedure. + + |
+ + number + | +
+
+ value
+
+ |
+ + Subcontracted value + | +
+ The estimated value of the part of the contract that will be subcontracted to third parties. + + |
+ + Value object + | +
+
+ competitive
+
+ |
+ + Competitive subcontracting + | +
+ Whether the supplier will subcontract part of the contract to third parties through a competitive procedure. + + |
+ + boolean + | +
+
+ subcontracts
+
+ |
+ + Subcontracts + | +
+ Information about the subcontracts that will be established. + + |
+ + array of Subcontract objects + | +
+ Subcontract +
+ +
+ The extension defines a new Subcontract object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ The locally unique identifier for the subcontract. + + |
+ + string + | +
+
+ subcontractor
+
+ |
+ + Subcontractor + | +
+ The organization that performs part of the contract on behalf of the suppliers. + + |
+ + OrganizationReference object + | +
+
+ mainContractors
+
+ |
+ + Main contractors + | +
+ The organizations to which the subcontractor will be subcontracted, if they are a subset of the tenderers submitting the bid or the suppliers receiving the award. + + |
+ + array of OrganizationReference objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/submissionTerms/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/submissionTerms/master/codelists/permission.csv b/en/extensions/submissionTerms/master/codelists/permission.csv
new file mode 100644
index 000000000..e72d40d7a
--- /dev/null
+++ b/en/extensions/submissionTerms/master/codelists/permission.csv
@@ -0,0 +1,4 @@
+Code,Title,Description
+required,Required,The activity is required.
+allowed,Allowed,The activity is allowed.
+notAllowed,Not allowed,The activity is not allowed.
diff --git a/en/extensions/submissionTerms/master/extension.json b/en/extensions/submissionTerms/master/extension.json
new file mode 100644
index 000000000..b34b9da20
--- /dev/null
+++ b/en/extensions/submissionTerms/master/extension.json
@@ -0,0 +1,29 @@
+{
+ "name": {
+ "en": "Submission terms",
+ "es": "T\u00e9rminos de Presentaci\u00f3n de la Oferta"
+ },
+ "description": {
+ "en": "Adds a submission terms object to the tender and lot objects, to describe how, when and where the tenderers must submit their bids.",
+ "es": "Agrega un objeto t\u00e9rminos de presentaci\u00f3n de la oferta a los objetos de la licitaci\u00f3n y del lote, para describir c\u00f3mo, cu\u00e1ndo y d\u00f3nde los oferentes deber\u00e1n presentar sus ofertas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/submissionTerms/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "permission.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/en/extensions/submissionTerms/master/index.html b/en/extensions/submissionTerms/master/index.html
new file mode 100644
index 000000000..c23c605cc
--- /dev/null
+++ b/en/extensions/submissionTerms/master/index.html
@@ -0,0 +1,335 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Submission terms +
+ ++ Adds a submission terms object to the tender and lot objects, to describe how, when and where the tenderers must submit their bids. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ permission.csv +
+ +
+ You can download the permission.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ required
+
+ |
+ + Required + | +
+ The activity is required. + + |
+
+
+ allowed
+
+ |
+ + Allowed + | +
+ The activity is allowed. + + |
+
+
+ notAllowed
+
+ |
+ + Not allowed + | +
+ The activity is not allowed. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/submissionTerms/master/release-schema.json b/en/extensions/submissionTerms/master/release-schema.json
new file mode 100644
index 000000000..2a631f515
--- /dev/null
+++ b/en/extensions/submissionTerms/master/release-schema.json
@@ -0,0 +1,145 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "submissionTerms": {
+ "title": "Submission terms",
+ "description": "Information about the submission terms to describe how, when and where the tenderers need to submit their bids for the procedure.",
+ "$ref": "#/definitions/SubmissionTerms"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "submissionTerms": {
+ "title": "Submission terms",
+ "description": "Information about the submission terms to describe how, when and where the tenderers need to submit their bids for the lot.",
+ "$ref": "#/definitions/SubmissionTerms"
+ }
+ }
+ },
+ "SubmissionTerms": {
+ "title": "Submission terms",
+ "description": "Information about the submission terms to describe how, when and where the tenderers need to submit their bids.",
+ "type": "object",
+ "properties": {
+ "electronicSubmissionPolicy": {
+ "title": "Electronic submission policy",
+ "description": "Whether tenderers are required, allowed or not allowed to submit bids electronically.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "permission.csv",
+ "openCodelist": false,
+ "enum": [
+ "required",
+ "allowed",
+ "notAllowed",
+ null
+ ]
+ },
+ "variantPolicy": {
+ "title": "Variant policy",
+ "description": "Whether tenderers are required, allowed or not allowed to submit bids which fulfill the buyer's needs differently than as proposed in the procurement documents.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "permission.csv",
+ "openCodelist": false,
+ "enum": [
+ "required",
+ "allowed",
+ "notAllowed",
+ null
+ ]
+ },
+ "electronicCataloguePolicy": {
+ "title": "Electronic catalog policy",
+ "description": "Whether tenderers are required, allowed or not allowed to submit bids as electronic catalogs. An electronic catalog is an electronic format (typically prescribed by the buyer) that participants in the contracting process need to follow when exchanging information about technical specifications, evaluation criteria, bids, lots, etc.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "permission.csv",
+ "openCodelist": false,
+ "enum": [
+ "required",
+ "allowed",
+ "notAllowed",
+ null
+ ]
+ },
+ "languages": {
+ "title": "Submission language",
+ "description": "One or more languages in which bids or requests to participate can be submitted, using either two-letter [ISO639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes), or extended [BCP47 language tags](http://www.w3.org/International/articles/language-tags/). The use of lowercase two-letter codes from [ISO639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) is recommended.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "bidValidityPeriod": {
+ "title": "Bid validity period",
+ "description": "The period, from the bid submission deadline, for which bids must remain valid.",
+ "$ref": "#/definitions/Period"
+ },
+ "depositsGuarantees": {
+ "title": "Deposits and guarantees",
+ "description": "Information about the deposits or guarantees required from the tenderers.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "advancedElectronicSignatureRequired": {
+ "title": "Advanced electronic signature required",
+ "description": "Whether an advanced or qualified electronic signature or seal is needed.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "multipleBidsAllowed": {
+ "title": "Multiple bids allowed",
+ "description": "Whether tenderers can submit more than one bid.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "nonElectronicSubmissionRationale": {
+ "title": "Non-electronic submission rationale",
+ "description": "The rationale for electronic submission not being allowed.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "subcontractingClauses": {
+ "title": "Subcontracting clauses",
+ "description": "The information about subcontracting that needs to be provided in the bid.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/submissionTerms/master/schema/index.html b/en/extensions/submissionTerms/master/schema/index.html
new file mode 100644
index 000000000..5c59a8fe7
--- /dev/null
+++ b/en/extensions/submissionTerms/master/schema/index.html
@@ -0,0 +1,491 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Submission terms +
+ ++ Adds a submission terms object to the tender and lot objects, to describe how, when and where the tenderers must submit their bids. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a submission terms object to the tender and lot objects, to describe how, when and where the tenderers must submit their bids.
+Legal context
+In the European Union, this extension's fields correspond to eForms BG-102 (Submission Terms). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+{
+ "tender": {
+ "submissionTerms": {
+ "electronicSubmissionPolicy": "notAllowed",
+ "nonElectronicSubmissionRationale": "Inclusion of a physical model",
+ "advancedElectronicSignatureRequired": false,
+ "electronicCataloguePolicy": "notAllowed",
+ "variantPolicy": "notAllowed",
+ "multipleBidsAllowed": true,
+ "languages": [
+ "fr",
+ "es"
+ ],
+ "bidValidityPeriod": {
+ "startDate": "2019-09-20T00:00:00Z",
+ "endDate": "2019-12-02T23:59:59Z",
+ "durationInDays": 74
+ },
+ "depositsGuarantees": "An on-demand performance bond issued by an entity that the Contracting Entity judges to be acceptable (e.g. a bank or insurance company) and whose value is a percentage of the total contract price.",
+ "subcontractingClauses": [
+ "subc-oblig"
+ ]
+ }
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-06-07
+-
+
- Define "electronic catalog" for the
electronicCataloguePolicyfield.
+
2023-05-22
+-
+
- Add fields for eForms:
+
-
+
SubmissionTerms.advancedElectronicSignatureRequired
+SubmissionTerms.multipleBidsAllowed
+SubmissionTerms.nonElectronicSubmissionRationale
+SubmissionTerms.subcontractingClauses
+
+
2020-09-29
+-
+
- Rename
requiresGuaranteestodepositsGuarantees
+ - Change the
typeofdepositsGuaranteesfrom a boolean to a string, to match the type of the corresponding XML element in TED XML Schema 2.09.
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/suitability/index.html b/en/extensions/suitability/index.html
new file mode 100644
index 000000000..d7262fef6
--- /dev/null
+++ b/en/extensions/suitability/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Submission terms +
+ ++ Adds a submission terms object to the tender and lot objects, to describe how, when and where the tenderers must submit their bids. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ submissionTerms
+
+ |
+ + Submission terms + | +
+ Information about the submission terms to describe how, when and where the tenderers need to submit their bids for the procedure. + + |
+ + SubmissionTerms object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ submissionTerms
+
+ |
+ + Submission terms + | +
+ Information about the submission terms to describe how, when and where the tenderers need to submit their bids for the lot. + + |
+ + SubmissionTerms object + | +
+ SubmissionTerms +
+ +
+ The extension defines a new SubmissionTerms object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ electronicSubmissionPolicy
+
+ |
+ + Electronic submission policy + | +
+ Whether tenderers are required, allowed or not allowed to submit bids electronically. + + |
+ + string from closed permission codelist + | +
+
+ variantPolicy
+
+ |
+ + Variant policy + | +
+ Whether tenderers are required, allowed or not allowed to submit bids which fulfill the buyer's needs differently than as proposed in the procurement documents. + + |
+ + string from closed permission codelist + | +
+
+ electronicCataloguePolicy
+
+ |
+ + Electronic catalog policy + | +
+ Whether tenderers are required, allowed or not allowed to submit bids as electronic catalogs. An electronic catalog is an electronic format (typically prescribed by the buyer) that participants in the contracting process need to follow when exchanging information about technical specifications, evaluation criteria, bids, lots, etc. + + |
+ + string from closed permission codelist + | +
+
+ languages
+
+ |
+ + Submission language + | +
+ One or more languages in which bids or requests to participate can be submitted, using either two-letter ISO639-1, or extended BCP47 language tags. The use of lowercase two-letter codes from ISO639-1 is recommended. + + |
+ + array of strings + | +
+
+ bidValidityPeriod
+
+ |
+ + Bid validity period + | +
+ The period, from the bid submission deadline, for which bids must remain valid. + + |
+ + Period object + | +
+
+ depositsGuarantees
+
+ |
+ + Deposits and guarantees + | +
+ Information about the deposits or guarantees required from the tenderers. + + |
+ + string + | +
+
+ advancedElectronicSignatureRequired
+
+ |
+ + Advanced electronic signature required + | +
+ Whether an advanced or qualified electronic signature or seal is needed. + + |
+ + boolean + | +
+
+ multipleBidsAllowed
+
+ |
+ + Multiple bids allowed + | +
+ Whether tenderers can submit more than one bid. + + |
+ + boolean + | +
+
+ nonElectronicSubmissionRationale
+
+ |
+ + Non-electronic submission rationale + | +
+ The rationale for electronic submission not being allowed. + + |
+ + string + | +
+
+ subcontractingClauses
+
+ |
+ + Subcontracting clauses + | +
+ The information about subcontracting that needs to be provided in the bid. + + |
+ + array of strings + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/suitability/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/suitability/master/release-schema.json b/en/extensions/suitability/master/release-schema.json
new file mode 100644
index 000000000..1725b6ce7
--- /dev/null
+++ b/en/extensions/suitability/master/release-schema.json
@@ -0,0 +1,47 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "suitability": {
+ "title": "Suitability",
+ "description": "Information about the suitability of the contracting process to different types of tenderers.",
+ "$ref": "#/definitions/Suitability"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "suitability": {
+ "title": "Suitability",
+ "description": "Information about the suitability of the lot to different types of tenderers.",
+ "$ref": "#/definitions/Suitability"
+ }
+ }
+ },
+ "LotGroup": {
+ "properties": {
+ "suitability": {
+ "title": "Suitability",
+ "description": "Information about the suitability of the lot group to different types of tenderers.",
+ "$ref": "#/definitions/Suitability"
+ }
+ }
+ },
+ "Suitability": {
+ "title": "Suitability",
+ "description": "Information about the suitability of a contracting process, lot or lot group to different types of tenderers.",
+ "type": "object",
+ "properties": {
+ "sme": {
+ "title": "Small and medium enterprises",
+ "description": "Whether the contracting process, lot or lot group is suitable to small and medium enterprises.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/suitability/master/schema/index.html b/en/extensions/suitability/master/schema/index.html
new file mode 100644
index 000000000..56e720a88
--- /dev/null
+++ b/en/extensions/suitability/master/schema/index.html
@@ -0,0 +1,384 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Suitability +
+ ++ Adds a suitability object to the tender, lot and lot group objects to describe their suitability to different types of tenderers. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a suitability object to the tender, lot and lot group objects to describe their suitability to different types of tenderers.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Legal context
+In the European Union, this extension's fields correspond to eForms BT-726 (Suitable For SMEs). For correspondences to eForms fields, see OCDS for eForms.
+Examples
+Tender
+{
+ "tender": {
+ "id": "1",
+ "suitability": {
+ "sme": true
+ }
+ }
+}
+Lot
+{
+ "tender": {
+ "id": "1",
+ "lots": [
+ {
+ "id": "1",
+ "suitability": {
+ "sme": true
+ }
+ }
+ ]
+ }
+}
+Lot group
+{
+ "tender": {
+ "id": "1",
+ "lotGroups": [
+ {
+ "id": "1",
+ "suitability": {
+ "sme": true
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/sustainability/index.html b/en/extensions/sustainability/index.html
new file mode 100644
index 000000000..ae909319d
--- /dev/null
+++ b/en/extensions/sustainability/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Suitability +
+ ++ Adds a suitability object to the tender, lot and lot group objects to describe their suitability to different types of tenderers. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ suitability
+
+ |
+ + Suitability + | +
+ Information about the suitability of the contracting process to different types of tenderers. + + |
+ + Suitability object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ suitability
+
+ |
+ + Suitability + | +
+ Information about the suitability of the lot to different types of tenderers. + + |
+ + Suitability object + | +
+ LotGroup +
+ +
+ The extension defines these fields in the LotGroup object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ suitability
+
+ |
+ + Suitability + | +
+ Information about the suitability of the lot group to different types of tenderers. + + |
+ + Suitability object + | +
+ Suitability +
+ +
+ The extension defines a new Suitability object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ sme
+
+ |
+ + Small and medium enterprises + | +
+ Whether the contracting process, lot or lot group is suitable to small and medium enterprises. + + |
+ + boolean + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/sustainability/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/sustainability/master/codelists/sustainabilityGoal.csv b/en/extensions/sustainability/master/codelists/sustainabilityGoal.csv
new file mode 100644
index 000000000..590079056
--- /dev/null
+++ b/en/extensions/sustainability/master/codelists/sustainabilityGoal.csv
@@ -0,0 +1,30 @@
+Code,Title,Description
+economic,Economic,"The goal is economic, such as formal employment and the local economy."
+economic.formalEmploymentPromotion,Formal employment promotion,The goal is to promote formal employment.
+economic.innovativePurchase,Innovative purchase,"The goal is to procure innovative goods, services or works."
+economic.localEconomyPromotion,Local economy promotion,The goal is to promote the local economy.
+economic.marketInnovationPromotion,Market innovation promotion,The goal is to promote market innovation.
+economic.processInnovationPromotion,Process innovation promotion,"The goal is to procure goods, services or works that entail process innovation."
+economic.productInnovationPromotion,Product innovation promotion,"The goal is to procure goods, services or works that entail product innovation."
+economic.researchDevelopmentActivities,Research and development activities,"The goal is to procure goods, services or works that involve research and development activities."
+environmental,Environmental,"The goal is to minimize and, if possible, avoid environmental damage: for example, reducing CO2 emissions and waste or promoting resource reuse and energy efficiency."
+environmental.biodiversityProtectionRestoration,Biodiversity protection and restoration,The goal is to protect and restore biodiversity and ecosystems.
+environmental.carbonEmissionsReduction,Carbon emissions reduction,The goal is to reduce carbon dioxide (CO2) emissions.
+environmental.circularEconomy,Circular economy,The goal is to promote the transition to a circular economy.
+environmental.climateChangeAdaptation,Climate change adaptation,The goal is to promote climate change adaptation.
+environmental.climateChangeMitigation,Climate change mitigation,The goal is to promote climate change mitigation.
+environmental.energyEfficiency,Energy efficiency,The goal is to promote energy efficiency.
+environmental.pollutionPrevention,Pollution prevention,The goal is to prevent pollution.
+environmental.recycling,Recycling,The goal is to promote recycling.
+environmental.resourceReuse,Resource reuse,The goal is to maximize the reuse of resources.
+environmental.waterResourcesProtection,Water resources protection,The goal is to promote the sustainable use and protection of water and marine resources.
+environmental.wasteReduction,Waste reduction,The goal is to reduce waste.
+social,Social,"The goal is to generate benefits to society: for example, promoting labor rights, diversity and equal opportunity, and occupational health and safety."
+social.accessibility,Accessibility,The goal is to promote accessibility for disabled and not disabled persons.
+social.disadvantagedEmploymentOpportunities,Disadvantaged employment opportunities,"The goal is to promote employment opportunities for the long-term unemployed, disadvantaged and/or for persons with disabilities."
+social.ethnicEquality,Ethnic equality,The goal is to promote ethnic equality.
+social.genderEquality,Gender equality,The goal is to promote gender equality.
+social.humanRightsInSupplyChains,Human rights in supply chains,The goal is to promote human rights due diligence in global supply chains.
+social.laborRightsPromotion,Labor rights promotion,The goal is to promote labor rights.
+social.smeInclusion,SME inclusion,The goal is to promote the participation of small and medium-sized enterprises (SMEs).
+social.womenInclusion,Women inclusion,The goal is to promote the participation of women-owned suppliers.
diff --git a/en/extensions/sustainability/master/codelists/sustainabilityStrategy.csv b/en/extensions/sustainability/master/codelists/sustainabilityStrategy.csv
new file mode 100644
index 000000000..87f7d6dad
--- /dev/null
+++ b/en/extensions/sustainability/master/codelists/sustainabilityStrategy.csv
@@ -0,0 +1,10 @@
+Code,Title,Description
+awardCriteria,Award criteria,"Award criteria are used to pursue sustainability goals: for example, allocating points relative to the percentage of recycled materials."
+contractPerformanceConditions,Contract performance conditions,"Contract performance conditions are used to pursue sustainability goals: for example, requiring the supplier to monitor carbon emissions during the contract's implementation."
+marginOfPreference,Margin of preference,"Margins of preference are used to pursue sustainability goals: for example, accepting the bid of a local supplier that is within a margin of the lowest bid."
+reservedParticipation,Reserved participation,"Reserved participation is used to pursue sustainability goals: for example, allowing only SMEs to participate in the contracting process."
+selectionCriteria,Selection criteria,"Selection criteria are used to fulfill sustainability goals: for example, requiring a bidder to have a sustainability certificate."
+technicalSpecifications,Technical specifications,"Items' technical specifications are used to pursue sustainability goals: for example, requiring a product to have an energy efficiency certificate."
+euGPPCriteria,EU GPP criteria,"Green public procurement criteria established at the European Union-level are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses."
+nationalGPPCriteria,National GPP criteria,"Green public procurement criteria established at the national level are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses."
+otherGPPCriteria,Other GPP criteria,"Green public procurement criteria established at a level other than the European Union or national levels are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses."
diff --git a/en/extensions/sustainability/master/extension.json b/en/extensions/sustainability/master/extension.json
new file mode 100644
index 000000000..42980c4ff
--- /dev/null
+++ b/en/extensions/sustainability/master/extension.json
@@ -0,0 +1,30 @@
+{
+ "name": {
+ "en": "Sustainability",
+ "es": "Sustainability"
+ },
+ "description": {
+ "en": "Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement.",
+ "es": "Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/sustainability"
+ },
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "sustainabilityGoal.csv",
+ "sustainabilityStrategy.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/sustainability/master/index.html b/en/extensions/sustainability/master/index.html
new file mode 100644
index 000000000..696790c8a
--- /dev/null
+++ b/en/extensions/sustainability/master/index.html
@@ -0,0 +1,462 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Sustainability +
+ ++ Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ sustainabilityGoal.csv +
+ +
+ You can download the sustainabilityGoal.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ economic
+
+ |
+ + Economic + | +
+ The goal is economic, such as formal employment and the local economy. + + |
+
+
+ economic.formalEmploymentPromotion
+
+ |
+ + Formal employment promotion + | +
+ The goal is to promote formal employment. + + |
+
+
+ economic.innovativePurchase
+
+ |
+ + Innovative purchase + | +
+ The goal is to procure innovative goods, services or works. + + |
+
+
+ economic.localEconomyPromotion
+
+ |
+ + Local economy promotion + | +
+ The goal is to promote the local economy. + + |
+
+
+ economic.marketInnovationPromotion
+
+ |
+ + Market innovation promotion + | +
+ The goal is to promote market innovation. + + |
+
+
+ economic.processInnovationPromotion
+
+ |
+ + Process innovation promotion + | +
+ The goal is to procure goods, services or works that entail process innovation. + + |
+
+
+ economic.productInnovationPromotion
+
+ |
+ + Product innovation promotion + | +
+ The goal is to procure goods, services or works that entail product innovation. + + |
+
+
+ economic.researchDevelopmentActivities
+
+ |
+ + Research and development activities + | +
+ The goal is to procure goods, services or works that involve research and development activities. + + |
+
+
+ environmental
+
+ |
+ + Environmental + | +
+ The goal is to minimize and, if possible, avoid environmental damage: for example, reducing CO2 emissions and waste or promoting resource reuse and energy efficiency. + + |
+
+
+ environmental.biodiversityProtectionRestoration
+
+ |
+ + Biodiversity protection and restoration + | +
+ The goal is to protect and restore biodiversity and ecosystems. + + |
+
+
+ environmental.carbonEmissionsReduction
+
+ |
+ + Carbon emissions reduction + | +
+ The goal is to reduce carbon dioxide (CO2) emissions. + + |
+
+
+ environmental.circularEconomy
+
+ |
+ + Circular economy + | +
+ The goal is to promote the transition to a circular economy. + + |
+
+
+ environmental.climateChangeAdaptation
+
+ |
+ + Climate change adaptation + | +
+ The goal is to promote climate change adaptation. + + |
+
+
+ environmental.climateChangeMitigation
+
+ |
+ + Climate change mitigation + | +
+ The goal is to promote climate change mitigation. + + |
+
+
+ environmental.energyEfficiency
+
+ |
+ + Energy efficiency + | +
+ The goal is to promote energy efficiency. + + |
+
+
+ environmental.pollutionPrevention
+
+ |
+ + Pollution prevention + | +
+ The goal is to prevent pollution. + + |
+
+
+ environmental.recycling
+
+ |
+ + Recycling + | +
+ The goal is to promote recycling. + + |
+
+
+ environmental.resourceReuse
+
+ |
+ + Resource reuse + | +
+ The goal is to maximize the reuse of resources. + + |
+
+
+ environmental.waterResourcesProtection
+
+ |
+ + Water resources protection + | +
+ The goal is to promote the sustainable use and protection of water and marine resources. + + |
+
+
+ environmental.wasteReduction
+
+ |
+ + Waste reduction + | +
+ The goal is to reduce waste. + + |
+
+
+ social
+
+ |
+ + Social + | +
+ The goal is to generate benefits to society: for example, promoting labor rights, diversity and equal opportunity, and occupational health and safety. + + |
+
+
+ social.accessibility
+
+ |
+ + Accessibility + | +
+ The goal is to promote accessibility for disabled and not disabled persons. + + |
+
+
+ social.disadvantagedEmploymentOpportunities
+
+ |
+ + Disadvantaged employment opportunities + | +
+ The goal is to promote employment opportunities for the long-term unemployed, disadvantaged and/or for persons with disabilities. + + |
+
+
+ social.ethnicEquality
+
+ |
+ + Ethnic equality + | +
+ The goal is to promote ethnic equality. + + |
+
+
+ social.genderEquality
+
+ |
+ + Gender equality + | +
+ The goal is to promote gender equality. + + |
+
+
+ social.humanRightsInSupplyChains
+
+ |
+ + Human rights in supply chains + | +
+ The goal is to promote human rights due diligence in global supply chains. + + |
+
+
+ social.laborRightsPromotion
+
+ |
+ + Labor rights promotion + | +
+ The goal is to promote labor rights. + + |
+
+
+ social.smeInclusion
+
+ |
+ + SME inclusion + | +
+ The goal is to promote the participation of small and medium-sized enterprises (SMEs). + + |
+
+
+ social.womenInclusion
+
+ |
+ + Women inclusion + | +
+ The goal is to promote the participation of women-owned suppliers. + + |
+
+ sustainabilityStrategy.csv +
+ +
+ You can download the sustainabilityStrategy.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ awardCriteria
+
+ |
+ + Award criteria + | +
+ Award criteria are used to pursue sustainability goals: for example, allocating points relative to the percentage of recycled materials. + + |
+
+
+ contractPerformanceConditions
+
+ |
+ + Contract performance conditions + | +
+ Contract performance conditions are used to pursue sustainability goals: for example, requiring the supplier to monitor carbon emissions during the contract's implementation. + + |
+
+
+ marginOfPreference
+
+ |
+ + Margin of preference + | +
+ Margins of preference are used to pursue sustainability goals: for example, accepting the bid of a local supplier that is within a margin of the lowest bid. + + |
+
+
+ reservedParticipation
+
+ |
+ + Reserved participation + | +
+ Reserved participation is used to pursue sustainability goals: for example, allowing only SMEs to participate in the contracting process. + + |
+
+
+ selectionCriteria
+
+ |
+ + Selection criteria + | +
+ Selection criteria are used to fulfill sustainability goals: for example, requiring a bidder to have a sustainability certificate. + + |
+
+
+ technicalSpecifications
+
+ |
+ + Technical specifications + | +
+ Items' technical specifications are used to pursue sustainability goals: for example, requiring a product to have an energy efficiency certificate. + + |
+
+
+ euGPPCriteria
+
+ |
+ + EU GPP criteria + | +
+ Green public procurement criteria established at the European Union-level are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses. + + |
+
+
+ nationalGPPCriteria
+
+ |
+ + National GPP criteria + | +
+ Green public procurement criteria established at the national level are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses. + + |
+
+
+ otherGPPCriteria
+
+ |
+ + Other GPP criteria + | +
+ Green public procurement criteria established at a level other than the European Union or national levels are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/sustainability/master/release-schema.json b/en/extensions/sustainability/master/release-schema.json
new file mode 100644
index 000000000..075f1abf4
--- /dev/null
+++ b/en/extensions/sustainability/master/release-schema.json
@@ -0,0 +1,94 @@
+{
+ "definitions": {
+ "Sustainability": {
+ "title": "Sustainability",
+ "description": "Information about how the contracting process or lot incorporates Sustainable Public Procurement.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "A description of how the contracting process or lot incorporates Sustainable Public Procurement.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "goal": {
+ "title": "Goal",
+ "description": "The sustainability goal pursued, from the sustainabilityGoal codelist. New sub-codes may be used outside those in the codelist, following the format [existing-code].[sub-code].",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "sustainabilityGoal.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "strategies": {
+ "title": "Strategies",
+ "description": "The strategies used to pursue the sustainability goal(s), from the sustainabilityStrategy codelist.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "sustainabilityStrategy.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Tender": {
+ "properties": {
+ "hasSustainability": {
+ "title": "Has sustainability",
+ "description": "Whether the contracting process incorporates Sustainable Public Procurement.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "sustainability": {
+ "title": "Sustainability",
+ "description": "Information about how the contracting process incorporates Sustainable Public Procurement.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Sustainability"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "hasSustainability": {
+ "title": "Has sustainability",
+ "description": "Whether the lot incorporates Sustainable Public Procurement.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "sustainability": {
+ "title": "Sustainability",
+ "description": "Information about how the lot incorporates Sustainable Public Procurement.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Sustainability"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/sustainability/master/schema/index.html b/en/extensions/sustainability/master/schema/index.html
new file mode 100644
index 000000000..c204e0cbc
--- /dev/null
+++ b/en/extensions/sustainability/master/schema/index.html
@@ -0,0 +1,406 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Sustainability +
+ ++ Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement (SPP).
+Motivation
+To calculate SPP indicators, a user or an application needs to be able to perform the following tasks, using OCDS data:
+-
+
- Select the contracting processes or individual lots that relate to SPP. +
- Select the contracting processes or individual lots that relate to a specific sustainability goal. +
- Determine which strategies are being used to promote a sustainability goal, within a contracting process or lot. +
- Determine whether a procured item or a supplier has characteristics related to sustainability. +
This extension add the fields needed for the above tasks as structured data.
+Guidance
+If you know a contracting process or lot is SPP-related, set hasSustainability to true.
If you know the sustainability goals pursued through the contracting process or lot, then, for each goal, add an entry in its sustainability array, from the sustainabilityGoal.csv codelist. This codelist contains codes for broad goals (like 'environmental') and narrower goals (like 'environmental.wasteReduction'). It is an open codelist, such that you can add new codes if no existing code is appropriate.
If you know the strategies used to pursue the sustainability goal(s), then, for each goal, add an entry in the strategies array, from the sustainabilityStrategy.csv codelist.
Examples
+hasSustainability only
+Public Health Wales adopts SPP in a contracting process to design office space and supply furniture.
+{
+ "tender": {
+ "id": "P427",
+ "title": "Design of office space and supply of furniture, reusing existing furniture",
+ "hasSustainability": true
+ }
+}
+If the contracting process is divided into lots, and it is known which lot(s) relate to SPP, set the lot's hasSustainability field:
{
+ "tender": {
+ "lots": [
+ {
+ "id": "123",
+ "hasSustainability": true
+ }
+ ]
+ }
+}
+The sustainability goal is known
+Public Health Wales intends to reduce waste and CO2 emissions as part of a contracting process to design office space and supply furniture.
+{
+ "tender": {
+ "sustainability": [
+ {
+ "goal": "environmental.wasteReduction"
+ },
+ {
+ "goal": "environmental.carbonEmissionsReduction"
+ }
+ ]
+ }
+}
+If only the broad goal is known, create a single entry using the broad code:
+{
+ "tender": {
+ "sustainability": [
+ {
+ "goal": "environmental"
+ }
+ ]
+ }
+}
+If the sustainabilityGoal.csv codelist contains no appropriate code, create your own code. To create a narrower code, add a period to an existing code, followed by a camelCase word:
{
+ "tender": {
+ "sustainability": [
+ {
+ "goal": "environmental.CFCReduction"
+ }
+ ]
+ }
+}
+If there is a free-text description of the sustainability goal:
+{
+ "tender": {
+ "sustainability": [
+ {
+ "description": "This procurement procedure is aimed at reducing the environmental impact of Public Health Wales office space and furniture."
+ }
+ ]
+ }
+}
+The strategies are known
+Public Health Wales sets SPP-related technical specifications as part of a contracting process to design office space and supply furniture.
+{
+ "tender": {
+ "sustainability": [
+ {
+ "goal": "environmental.wasteReduction",
+ "strategies": [
+ "technicalSpecifications"
+ ]
+ },
+ {
+ "goal": "environmental.CO2Reduction",
+ "strategies": [
+ "technicalSpecifications"
+ ]
+ }
+ ]
+ }
+}
+If the goal is unknown or is sustainability in general, omit goal and set strategies only:
{
+ "tender": {
+ "sustainability": [
+ {
+ "strategies": [
+ "technicalSpecifications"
+ ]
+ }
+ ]
+ }
+}
+Background
+This extension uses the UNEP definition of SPP:
+++A process whereby public sector organizations meet their needs for goods, services, works and utilities in a way that achieves value for money on a whole life basis in terms of generating benefits not only to the organization, but also to society and the economy, whilst minimizing, and if possible, avoiding, damage to the environment.
+
The sustainabilityGoal.csv codelist is based on the goals defined in the OpenSPP toolkit and the EU's strategic procurement codelist.
The sustainabilityStrategy.csv codelist is based on the strategies described in the OpenSPP toolkit and the EU's strategic procurement codelist.
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+This extension was originally discussed in https://github.com/open-contracting/standard/issues/1543.
+Changelog
+2023-04-12
+-
+
- Add
Sustainability.descriptionfield.
+ - Add codes to
sustainabilityGoal.csv: +-
+
- 'economic.innovativePurchase' +
- 'economic.processInnovationPromotion' +
- 'economic.productInnovationPromotion' +
- 'economic.researchDevelopmentActivities' +
- 'environmental.biodiversityProtectionRestoration' +
- 'environmental.circularEconomy' +
- 'environmental.circularEconomy' +
- 'environmental.climateChangeMitigation' +
- 'environmental.pollutionPrevention' +
- 'environmental.waterResourcesProtection' +
- 'social.accessibility' +
- 'social.disadvantagedEmploymentOpportunities' +
- 'social.ethnicEquality' +
- 'social.genderEquality' +
- 'social.humanRightsInSupplyChains' +
+ - Add codes to
sustainabilityStrategy.csv: +-
+
- 'euGPPCriteria' +
- 'nationalGPPCriteria' +
- 'otherGPPCriteria' +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/tariffs/1.1/README.md b/en/extensions/tariffs/1.1/README.md
new file mode 100644
index 000000000..a6e37288c
--- /dev/null
+++ b/en/extensions/tariffs/1.1/README.md
@@ -0,0 +1,128 @@
+# Tariffs
+
+## Introduction
+
+Some contracts, particularly Public Private Partnership contracts, include agreements about the user fees to be charged for use of the infrastructure or services the contract relates to.
+
+For example, a Public Private Partnership project to build a bridge may set out the tolls for cars and other vehicles cross the bridge.
+
+The tariff extension allows a structured list of these charges to be set out.
+
+It also includes an additional codelist entries for the documentType codelist for:
+
+- tariffs
+- tariffMethod
+- tariffReview
+- tariffIllustration
+
+## Tariff modelling
+
+The tariff model builds upon the metrics extension, allowing an array of tariff items, each with an identifier, title, period, value, units and an arbitrary set of dimensions.
+
+For example, if the toll for a road bridge varies based on (a) the type of vehicle; and (b) the time of day; an implementation of the tariff extension may create new fields for `dimensions.vehicleType` and `dimensions.timeOfDay`, populating these according to local codelists. In PPP cases, these additional dimensions may mirror those used in the estimated demand and other metrics sections.
+
+## Example
+
+The example below shows a very simply tariff table, without periods or units, but with two dimensions. Tariffs which relate to a particular set of dates could have a `period` block. Those which relate to a particular unit (e.g. tonnes) could have this indicated using a `unit` block.
+
+```json
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "tariffs": [
+ {
+ "id": "1",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 1",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 0.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "2",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 2",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 2.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "3",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 3",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 6.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "4",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 4",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 8.0,
+ "currency": "GBP"
+ }
+ }
+ ]
+ }
+ ]
+}
+```
+
+## Codelist entries
+
+The following document types are introduced by the tariff extension
+
+- tariffs - For providing tariff and pricing schedules.
+- tariffMethod - For summarizing the method by which tariffs are set, and linking to detailed documentation of the methods for setting tariffs. This may include written documentation, and spreadsheets providing the models used to calculate tariffs.
+- tariffReview - For summarizing the arrangements for the review and regulation of tariffs, and linking to detailed documentation that covers how tariffs are regulated. This is important to explain to users why they are paying what they are paying, and the scope for changes to payment structures.
+- tariffIllustration - For linking to graphs and reports on the change over time in tariff prices. Use the relevant image media type when linking to PNG, JPEG or GIF graphs to allow applications to directly display this content.
+
+## Issues
+
+Report issues for this extension in the [ocds-extensions repository](https://github.com/open-contracting/ocds-extensions/issues), putting the extension's name in the issue's title.
+
+## Changelog
+
+### 2021-04-19
+
+- Add Section column to `+documentType.csv` codelist.
+
+### 2020-06-04
+
+- Review normative and non-normative words.
+
+### 2020-04-24
+
+- Add `minProperties`, `minItems` and/or `minLength` properties.
+
+### 2019-03-20
+
+- Set `"uniqueItems": true` on array fields, and add `"minLength": 1` on required string fields.
+- Make `Tariff.unit` non-nullable, like `Item.unit`.
+- Make `Tariff.dimensions` non-nullable (undo earlier change).
+
+### 2018-05-08
+
+- Make `Tariff.id` required to support revision tracking and [list merging](http://standard.open-contracting.org/latest/en/schema/merging/#lists)
+
+### 2018-05-01
+
+- Make `Tariff.dimensions` nullable.
diff --git a/en/extensions/tariffs/1.1/codelists/+documentType.csv b/en/extensions/tariffs/1.1/codelists/+documentType.csv
new file mode 100644
index 000000000..d8f45f3d6
--- /dev/null
+++ b/en/extensions/tariffs/1.1/codelists/+documentType.csv
@@ -0,0 +1,5 @@
+Code,Title,Description,Section
+tariffs,Tariffs,For providing tariff and pricing schedules.,contract
+tariffMethod,Tariff method,For summarizing the method by which tariffs are set and linking to detailed documentation of the methods for setting tariffs. This might include written documentation and spreadsheets providing the models used to calculate tariffs.,contract
+tariffReview,Tariff review,For summarizing the arrangements for the review and regulation of tariffs and linking to detailed documentation that covers how tariffs are regulated. This is important to explain to users why they are paying what they are paying and the scope for changes to payment structures.,contract
+tariffIllustration,Tariff illustration,For linking to graphs and reports on the change over time in tariff prices. Use the relevant image media type when linking to PNG or JPEG or GIF graphs to allow applications to directly display this content.,contract
diff --git a/en/extensions/tariffs/1.1/codelists/chargePaidBy.csv b/en/extensions/tariffs/1.1/codelists/chargePaidBy.csv
new file mode 100644
index 000000000..58c8f3831
--- /dev/null
+++ b/en/extensions/tariffs/1.1/codelists/chargePaidBy.csv
@@ -0,0 +1,3 @@
+Code,Title,Description
+government,Government,The charge is paid by the government
+user,User,The charge is paid by businesses or citizens using the facilities provided by the contract
diff --git a/en/extensions/tariffs/1.1/codelists/index.html b/en/extensions/tariffs/1.1/codelists/index.html
new file mode 100644
index 000000000..d0198109d
--- /dev/null
+++ b/en/extensions/tariffs/1.1/codelists/index.html
@@ -0,0 +1,363 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Sustainability +
+ ++ Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Sustainability +
+ +
+ The extension defines a new Sustainability object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ A description of how the contracting process or lot incorporates Sustainable Public Procurement. + + |
+ + string + | +
+
+ goal
+
+ |
+ + Goal + | +
+ The sustainability goal pursued, from the sustainabilityGoal codelist. New sub-codes may be used outside those in the codelist, following the format [existing-code].[sub-code]. + + |
+ + string from open sustainabilityGoal codelist + | +
+
+ strategies
+
+ |
+ + Strategies + | +
+ The strategies used to pursue the sustainability goal(s), from the sustainabilityStrategy codelist. + + |
+ + array of strings from open sustainabilityStrategy codelist + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasSustainability
+
+ |
+ + Has sustainability + | +
+ Whether the contracting process incorporates Sustainable Public Procurement. + + |
+ + boolean + | +
+
+ sustainability
+
+ |
+ + Sustainability + | +
+ Information about how the contracting process incorporates Sustainable Public Procurement. + + |
+ + array of Sustainability objects + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasSustainability
+
+ |
+ + Has sustainability + | +
+ Whether the lot incorporates Sustainable Public Procurement. + + |
+ + boolean + | +
+
+ sustainability
+
+ |
+ + Sustainability + | +
+ Information about how the lot incorporates Sustainable Public Procurement. + + |
+ + array of Sustainability objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/tariffs/1.1/extension.json b/en/extensions/tariffs/1.1/extension.json
new file mode 100644
index 000000000..ef23eff3e
--- /dev/null
+++ b/en/extensions/tariffs/1.1/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Tariffs",
+ "es": "Tarifas"
+ },
+ "description": {
+ "en": "Adds fields to the contract and implementation objects to capture details of the tariffs, tolls and user fees set out in the contract and in use throughout the life of the project.",
+ "es": "Agrega campos al contrato y objetos de implementaci\u00f3n para capturar los detalles de las tarifas, los peajes y las tarifas de los usuarios establecidos en el contrato y en uso durante la vida del proyecto."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/tariffs/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "+documentType.csv",
+ "chargePaidBy.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/tariffs/1.1/index.html b/en/extensions/tariffs/1.1/index.html
new file mode 100644
index 000000000..3b62643ef
--- /dev/null
+++ b/en/extensions/tariffs/1.1/index.html
@@ -0,0 +1,399 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tariffs +
+ ++ Adds fields to the contract and implementation objects to capture details of the tariffs, tolls and user fees set out in the contract and in use throughout the life of the project. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +documentType.csv +
+ +
+ You can download the +documentType.csv file in English.
+
+ The extension adds these codes to the documentType.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ tariffs
+
+ |
+ + Tariffs + | +
+ For providing tariff and pricing schedules. + +
|
+
+
+ tariffMethod
+
+ |
+ + Tariff method + | +
+ For summarizing the method by which tariffs are set and linking to detailed documentation of the methods for setting tariffs. This might include written documentation and spreadsheets providing the models used to calculate tariffs. + +
|
+
+
+ tariffReview
+
+ |
+ + Tariff review + | +
+ For summarizing the arrangements for the review and regulation of tariffs and linking to detailed documentation that covers how tariffs are regulated. This is important to explain to users why they are paying what they are paying and the scope for changes to payment structures. + +
|
+
+
+ tariffIllustration
+
+ |
+ + Tariff illustration + | +
+ For linking to graphs and reports on the change over time in tariff prices. Use the relevant image media type when linking to PNG or JPEG or GIF graphs to allow applications to directly display this content. + +
|
+
+ chargePaidBy.csv +
+ +
+ You can download the chargePaidBy.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ government
+
+ |
+ + Government + | +
+ The charge is paid by the government + + |
+
+
+ user
+
+ |
+ + User + | +
+ The charge is paid by businesses or citizens using the facilities provided by the contract + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/tariffs/1.1/release-schema.json b/en/extensions/tariffs/1.1/release-schema.json
new file mode 100644
index 000000000..d7112b56f
--- /dev/null
+++ b/en/extensions/tariffs/1.1/release-schema.json
@@ -0,0 +1,153 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "tariffs": {
+ "title": "Tariffs",
+ "description": "The tariffs as they apply during the life of the project. Also known as tolls or user charges. These may be initially copied from the contract section, and then updated with any revisions over the lifetime of the implementation phase.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Tariff"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "tariffs": {
+ "title": "Tariffs",
+ "description": "The tariffs as set out in the contract schedules. Also known as tolls or user charges. Updates to tariffs over the operation of the contract can be provided in the implementation section.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Tariff"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Tariff": {
+ "title": "Tariff",
+ "description": "An item in a tariff table, setting out a breakdown of the user or government fees payable in relation to each unit of a particular good or services.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Tariff identifier",
+ "description": "A local identifier for this specific tariff. This field is used to keep track of revisions of a tariff across multiple OCDS releases.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "Tariff title",
+ "description": "The title of this tariff.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "paidBy": {
+ "title": "Paid by",
+ "description": "Is this a user charge (paid by businesses or citizens using the facilities provided by the contract), or a charge paid by the government?",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "chargePaidBy.csv",
+ "openCodelist": false,
+ "enum": [
+ "government",
+ "user",
+ null
+ ]
+ },
+ "period": {
+ "title": "Tariff period",
+ "description": "The period to which this tariff applies.",
+ "$ref": "#/definitions/Period"
+ },
+ "value": {
+ "title": "Tariff value",
+ "description": "The price per unit of this tariff.",
+ "$ref": "#/definitions/Value"
+ },
+ "unit": {
+ "title": "Tariff unit",
+ "description": "The unit against which this tariff is charged.",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Unit name",
+ "description": "The name of the unit that the tariff is charged against. E.g. tonnes,",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "scheme": {
+ "title": "Scheme",
+ "description": "The list from which units of measure identifiers are taken. Use of the scheme 'UNCEFACT' for the UN/CEFACT Recommendation 20 list of \"Codes for Units of Measure Used in International Trade\" is recommended.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "The identifier from the codelist referenced in the schema property. For example, with UNCEFACT, this is the value of the 'Common Code' column. From this identifier, applications can look-up the human readable name or symbol for this unit of measure.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "uri": {
+ "title": "URI",
+ "description": "If the scheme used provide a machine-readable URI for this unit of measure, this can be given.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ },
+ "minProperties": 1
+ },
+ "dimensions": {
+ "title": "Tariff dimensions",
+ "description": "Used to capture the different breakdowns in tariff charges. Any number of dimensions can be recorded within this object. Dimensions names should follow the camelCase conventions of OCDS.",
+ "type": "object",
+ "patternProperties": {
+ "^.*": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "notes": {
+ "title": "Tariff notes",
+ "description": "Any notes on this tariff line item. This may include clarifying information.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/tariffs/1.1/schema/index.html b/en/extensions/tariffs/1.1/schema/index.html
new file mode 100644
index 000000000..1449382bb
--- /dev/null
+++ b/en/extensions/tariffs/1.1/schema/index.html
@@ -0,0 +1,541 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tariffs +
+ ++ Adds fields to the contract and implementation objects to capture details of the tariffs, tolls and user fees set out in the contract and in use throughout the life of the project. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Introduction
+Some contracts, particularly Public Private Partnership contracts, include agreements about the user fees to be charged for use of the infrastructure or services the contract relates to.
+For example, a Public Private Partnership project to build a bridge may set out the tolls for cars and other vehicles cross the bridge.
+The tariff extension allows a structured list of these charges to be set out.
+It also includes an additional codelist entries for the documentType codelist for:
+-
+
- tariffs +
- tariffMethod +
- tariffReview +
- tariffIllustration +
Tariff modelling
+The tariff model builds upon the metrics extension, allowing an array of tariff items, each with an identifier, title, period, value, units and an arbitrary set of dimensions.
+For example, if the toll for a road bridge varies based on (a) the type of vehicle; and (b) the time of day; an implementation of the tariff extension may create new fields for dimensions.vehicleType and dimensions.timeOfDay, populating these according to local codelists. In PPP cases, these additional dimensions may mirror those used in the estimated demand and other metrics sections.
Example
+The example below shows a very simply tariff table, without periods or units, but with two dimensions. Tariffs which relate to a particular set of dates could have a period block. Those which relate to a particular unit (e.g. tonnes) could have this indicated using a unit block.
{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "tariffs": [
+ {
+ "id": "1",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 1",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 0.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "2",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 2",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 2.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "3",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 3",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 6.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "4",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 4",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 8.0,
+ "currency": "GBP"
+ }
+ }
+ ]
+ }
+ ]
+}
+Codelist entries
+The following document types are introduced by the tariff extension
+-
+
- tariffs - For providing tariff and pricing schedules. +
- tariffMethod - For summarizing the method by which tariffs are set, and linking to detailed documentation of the methods for setting tariffs. This may include written documentation, and spreadsheets providing the models used to calculate tariffs. +
- tariffReview - For summarizing the arrangements for the review and regulation of tariffs, and linking to detailed documentation that covers how tariffs are regulated. This is important to explain to users why they are paying what they are paying, and the scope for changes to payment structures. +
- tariffIllustration - For linking to graphs and reports on the change over time in tariff prices. Use the relevant image media type when linking to PNG, JPEG or GIF graphs to allow applications to directly display this content. +
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2021-04-19
+-
+
- Add Section column to
+documentType.csvcodelist.
+
2020-06-04
+-
+
- Review normative and non-normative words. +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2019-03-20
+-
+
- Set
"uniqueItems": trueon array fields, and add"minLength": 1on required string fields.
+ - Make
Tariff.unitnon-nullable, likeItem.unit.
+ - Make
Tariff.dimensionsnon-nullable (undo earlier change).
+
2018-05-08
+-
+
- Make
Tariff.idrequired to support revision tracking and list merging
+
2018-05-01
+-
+
- Make
Tariff.dimensionsnullable.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/tariffs/index.html b/en/extensions/tariffs/index.html
new file mode 100644
index 000000000..ee3ff1957
--- /dev/null
+++ b/en/extensions/tariffs/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tariffs +
+ ++ Adds fields to the contract and implementation objects to capture details of the tariffs, tolls and user fees set out in the contract and in use throughout the life of the project. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ tariffs
+
+ |
+ + Tariffs + | +
+ The tariffs as they apply during the life of the project. Also known as tolls or user charges. These may be initially copied from the contract section, and then updated with any revisions over the lifetime of the implementation phase. + + |
+ + array of Tariff objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ tariffs
+
+ |
+ + Tariffs + | +
+ The tariffs as set out in the contract schedules. Also known as tolls or user charges. Updates to tariffs over the operation of the contract can be provided in the implementation section. + + |
+ + array of Tariff objects + | +
+ Tariff +
+ +
+ The extension defines a new Tariff object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Tariff identifier + | +
+ A local identifier for this specific tariff. This field is used to keep track of revisions of a tariff across multiple OCDS releases. + + |
+ + string + | +
+
+ title
+
+ |
+ + Tariff title + | +
+ The title of this tariff. + + |
+ + string + | +
+
+ paidBy
+
+ |
+ + Paid by + | +
+ Is this a user charge (paid by businesses or citizens using the facilities provided by the contract), or a charge paid by the government? + + |
+ + string from closed chargePaidBy codelist + | +
+
+ period
+
+ |
+ + Tariff period + | +
+ The period to which this tariff applies. + + |
+ + Period object + | +
+
+ value
+
+ |
+ + Tariff value + | +
+ The price per unit of this tariff. + + |
+ + Value object + | +
+
+ unit
+
+ |
+ + Tariff unit + | +
+ The unit against which this tariff is charged. + + |
+ + object + | +
+
+ unit.
+ |
+ + Unit name + | +
+ The name of the unit that the tariff is charged against. E.g. tonnes, + + |
+ + string + | +
+
+ unit.
+ |
+ + Scheme + | +
+ The list from which units of measure identifiers are taken. Use of the scheme 'UNCEFACT' for the UN/CEFACT Recommendation 20 list of "Codes for Units of Measure Used in International Trade" is recommended. + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ unit.
+ |
+ + ID + | +
+ The identifier from the codelist referenced in the schema property. For example, with UNCEFACT, this is the value of the 'Common Code' column. From this identifier, applications can look-up the human readable name or symbol for this unit of measure. + + |
+ + string + | +
+
+ unit.
+ |
+ + URI + | +
+ If the scheme used provide a machine-readable URI for this unit of measure, this can be given. + + |
+ + string + | +
+
+ dimensions
+
+ |
+ + Tariff dimensions + | +
+ Used to capture the different breakdowns in tariff charges. Any number of dimensions can be recorded within this object. Dimensions names should follow the camelCase conventions of OCDS. + + |
+ + object + | +
+
+ dimensions.
+ |
+ + + | ++ + | ++ string + | +
+
+ notes
+
+ |
+ + Tariff notes + | +
+ Any notes on this tariff line item. This may include clarifying information. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/tariffs/1.1/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/tariffs/master/index.html b/en/extensions/tariffs/master/index.html
new file mode 100644
index 000000000..4e1e6d772
--- /dev/null
+++ b/en/extensions/tariffs/master/index.html
@@ -0,0 +1,400 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tariffs +
+ ++ Adds fields to the contract and implementation objects to capture details of the tariffs, tolls and user fees set out in the contract and in use throughout the life of the project. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +documentType.csv +
+ +
+ You can download the +documentType.csv file in English.
+
+ The extension adds these codes to the documentType.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ tariffs
+
+ |
+ + Tariffs + | +
+ For providing tariff and pricing schedules. + +
|
+
+
+ tariffMethod
+
+ |
+ + Tariff method + | +
+ For summarizing the method by which tariffs are set and linking to detailed documentation of the methods for setting tariffs. This might include written documentation and spreadsheets providing the models used to calculate tariffs. + +
|
+
+
+ tariffReview
+
+ |
+ + Tariff review + | +
+ For summarizing the arrangements for the review and regulation of tariffs and linking to detailed documentation that covers how tariffs are regulated. This is important to explain to users why they are paying what they are paying and the scope for changes to payment structures. + +
|
+
+
+ tariffIllustration
+
+ |
+ + Tariff illustration + | +
+ For linking to graphs and reports on the change over time in tariff prices. Use the relevant image media type when linking to PNG or JPEG or GIF graphs to allow applications to directly display this content. + +
|
+
+ chargePaidBy.csv +
+ +
+ You can download the chargePaidBy.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ government
+
+ |
+ + Government + | +
+ The charge is paid by the government + + |
+
+
+ user
+
+ |
+ + User + | +
+ The charge is paid by businesses or citizens using the facilities provided by the contract + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/tariffs/master/release-schema.json b/en/extensions/tariffs/master/release-schema.json
new file mode 100644
index 000000000..d7112b56f
--- /dev/null
+++ b/en/extensions/tariffs/master/release-schema.json
@@ -0,0 +1,153 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "tariffs": {
+ "title": "Tariffs",
+ "description": "The tariffs as they apply during the life of the project. Also known as tolls or user charges. These may be initially copied from the contract section, and then updated with any revisions over the lifetime of the implementation phase.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Tariff"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "tariffs": {
+ "title": "Tariffs",
+ "description": "The tariffs as set out in the contract schedules. Also known as tolls or user charges. Updates to tariffs over the operation of the contract can be provided in the implementation section.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Tariff"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Tariff": {
+ "title": "Tariff",
+ "description": "An item in a tariff table, setting out a breakdown of the user or government fees payable in relation to each unit of a particular good or services.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Tariff identifier",
+ "description": "A local identifier for this specific tariff. This field is used to keep track of revisions of a tariff across multiple OCDS releases.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "Tariff title",
+ "description": "The title of this tariff.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "paidBy": {
+ "title": "Paid by",
+ "description": "Is this a user charge (paid by businesses or citizens using the facilities provided by the contract), or a charge paid by the government?",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "chargePaidBy.csv",
+ "openCodelist": false,
+ "enum": [
+ "government",
+ "user",
+ null
+ ]
+ },
+ "period": {
+ "title": "Tariff period",
+ "description": "The period to which this tariff applies.",
+ "$ref": "#/definitions/Period"
+ },
+ "value": {
+ "title": "Tariff value",
+ "description": "The price per unit of this tariff.",
+ "$ref": "#/definitions/Value"
+ },
+ "unit": {
+ "title": "Tariff unit",
+ "description": "The unit against which this tariff is charged.",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Unit name",
+ "description": "The name of the unit that the tariff is charged against. E.g. tonnes,",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "scheme": {
+ "title": "Scheme",
+ "description": "The list from which units of measure identifiers are taken. Use of the scheme 'UNCEFACT' for the UN/CEFACT Recommendation 20 list of \"Codes for Units of Measure Used in International Trade\" is recommended.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "The identifier from the codelist referenced in the schema property. For example, with UNCEFACT, this is the value of the 'Common Code' column. From this identifier, applications can look-up the human readable name or symbol for this unit of measure.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "uri": {
+ "title": "URI",
+ "description": "If the scheme used provide a machine-readable URI for this unit of measure, this can be given.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ },
+ "minProperties": 1
+ },
+ "dimensions": {
+ "title": "Tariff dimensions",
+ "description": "Used to capture the different breakdowns in tariff charges. Any number of dimensions can be recorded within this object. Dimensions names should follow the camelCase conventions of OCDS.",
+ "type": "object",
+ "patternProperties": {
+ "^.*": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "notes": {
+ "title": "Tariff notes",
+ "description": "Any notes on this tariff line item. This may include clarifying information.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/tariffs/master/schema/index.html b/en/extensions/tariffs/master/schema/index.html
new file mode 100644
index 000000000..0771d70d3
--- /dev/null
+++ b/en/extensions/tariffs/master/schema/index.html
@@ -0,0 +1,542 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tariffs +
+ ++ Adds fields to the contract and implementation objects to capture details of the tariffs, tolls and user fees set out in the contract and in use throughout the life of the project. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Introduction
+Some contracts, particularly Public Private Partnership contracts, include agreements about the user fees to be charged for use of the infrastructure or services the contract relates to.
+For example, a Public Private Partnership project to build a bridge may set out the tolls for cars and other vehicles cross the bridge.
+The tariff extension allows a structured list of these charges to be set out.
+It also includes an additional codelist entries for the documentType codelist for:
+-
+
- tariffs +
- tariffMethod +
- tariffReview +
- tariffIllustration +
Tariff modelling
+The tariff model builds upon the metrics extension, allowing an array of tariff items, each with an identifier, title, period, value, units and an arbitrary set of dimensions.
+For example, if the toll for a road bridge varies based on (a) the type of vehicle; and (b) the time of day; an implementation of the tariff extension may create new fields for dimensions.vehicleType and dimensions.timeOfDay, populating these according to local codelists. In PPP cases, these additional dimensions may mirror those used in the estimated demand and other metrics sections.
Example
+The example below shows a very simply tariff table, without periods or units, but with two dimensions. Tariffs which relate to a particular set of dates could have a period block. Those which relate to a particular unit (e.g. tonnes) could have this indicated using a unit block.
{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "tariffs": [
+ {
+ "id": "1",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 1",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 0.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "2",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 2",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 2.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "3",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 3",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 6.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "4",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 4",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 8.0,
+ "currency": "GBP"
+ }
+ }
+ ]
+ }
+ ]
+}
+Codelist entries
+The following document types are introduced by the tariff extension
+-
+
- tariffs - For providing tariff and pricing schedules. +
- tariffMethod - For summarizing the method by which tariffs are set, and linking to detailed documentation of the methods for setting tariffs. This may include written documentation, and spreadsheets providing the models used to calculate tariffs. +
- tariffReview - For summarizing the arrangements for the review and regulation of tariffs, and linking to detailed documentation that covers how tariffs are regulated. This is important to explain to users why they are paying what they are paying, and the scope for changes to payment structures. +
- tariffIllustration - For linking to graphs and reports on the change over time in tariff prices. Use the relevant image media type when linking to PNG, JPEG or GIF graphs to allow applications to directly display this content. +
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2021-04-19
+-
+
- Add Section column to
+documentType.csvcodelist.
+
2020-06-04
+-
+
- Review normative and non-normative words. +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
2019-03-20
+-
+
- Set
"uniqueItems": trueon array fields, and add"minLength": 1on required string fields.
+ - Make
Tariff.unitnon-nullable, likeItem.unit.
+ - Make
Tariff.dimensionsnon-nullable (undo earlier change).
+
2018-05-08
+-
+
- Make
Tariff.idrequired to support revision tracking and list merging
+
2018-05-01
+-
+
- Make
Tariff.dimensionsnullable.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/techniques/index.html b/en/extensions/techniques/index.html
new file mode 100644
index 000000000..b7f2c428f
--- /dev/null
+++ b/en/extensions/techniques/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tariffs +
+ ++ Adds fields to the contract and implementation objects to capture details of the tariffs, tolls and user fees set out in the contract and in use throughout the life of the project. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ tariffs
+
+ |
+ + Tariffs + | +
+ The tariffs as they apply during the life of the project. Also known as tolls or user charges. These may be initially copied from the contract section, and then updated with any revisions over the lifetime of the implementation phase. + + |
+ + array of Tariff objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ tariffs
+
+ |
+ + Tariffs + | +
+ The tariffs as set out in the contract schedules. Also known as tolls or user charges. Updates to tariffs over the operation of the contract can be provided in the implementation section. + + |
+ + array of Tariff objects + | +
+ Tariff +
+ +
+ The extension defines a new Tariff object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Tariff identifier + | +
+ A local identifier for this specific tariff. This field is used to keep track of revisions of a tariff across multiple OCDS releases. + + |
+ + string + | +
+
+ title
+
+ |
+ + Tariff title + | +
+ The title of this tariff. + + |
+ + string + | +
+
+ paidBy
+
+ |
+ + Paid by + | +
+ Is this a user charge (paid by businesses or citizens using the facilities provided by the contract), or a charge paid by the government? + + |
+ + string from closed chargePaidBy codelist + | +
+
+ period
+
+ |
+ + Tariff period + | +
+ The period to which this tariff applies. + + |
+ + Period object + | +
+
+ value
+
+ |
+ + Tariff value + | +
+ The price per unit of this tariff. + + |
+ + Value object + | +
+
+ unit
+
+ |
+ + Tariff unit + | +
+ The unit against which this tariff is charged. + + |
+ + object + | +
+
+ unit.
+ |
+ + Unit name + | +
+ The name of the unit that the tariff is charged against. E.g. tonnes, + + |
+ + string + | +
+
+ unit.
+ |
+ + Scheme + | +
+ The list from which units of measure identifiers are taken. Use of the scheme 'UNCEFACT' for the UN/CEFACT Recommendation 20 list of "Codes for Units of Measure Used in International Trade" is recommended. + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ unit.
+ |
+ + ID + | +
+ The identifier from the codelist referenced in the schema property. For example, with UNCEFACT, this is the value of the 'Common Code' column. From this identifier, applications can look-up the human readable name or symbol for this unit of measure. + + |
+ + string + | +
+
+ unit.
+ |
+ + URI + | +
+ If the scheme used provide a machine-readable URI for this unit of measure, this can be given. + + |
+ + string + | +
+
+ dimensions
+
+ |
+ + Tariff dimensions + | +
+ Used to capture the different breakdowns in tariff charges. Any number of dimensions can be recorded within this object. Dimensions names should follow the camelCase conventions of OCDS. + + |
+ + object + | +
+
+ dimensions.
+ |
+ + + | ++ + | ++ string + | +
+
+ notes
+
+ |
+ + Tariff notes + | +
+ Any notes on this tariff line item. This may include clarifying information. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/techniques/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/techniques/master/extension.json b/en/extensions/techniques/master/extension.json
new file mode 100644
index 000000000..902a884d0
--- /dev/null
+++ b/en/extensions/techniques/master/extension.json
@@ -0,0 +1,31 @@
+{
+ "name": {
+ "en": "Techniques",
+ "es": "T\u00e9cnicas"
+ },
+ "description": {
+ "en": "Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions.",
+ "es": "Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/techniques/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "dynamicPurchasingSystemType.csv",
+ "dynamicPurchasingSystemStatus.csv",
+ "frameworkAgreementMethod.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/en/extensions/techniques/master/index.html b/en/extensions/techniques/master/index.html
new file mode 100644
index 000000000..271a0f9e9
--- /dev/null
+++ b/en/extensions/techniques/master/index.html
@@ -0,0 +1,474 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Techniques +
+ ++ Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ dynamicPurchasingSystemStatus.csv +
+ +
+ You can download the dynamicPurchasingSystemStatus.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ pending
+
+ |
+ + Pending + | +
+ The DPS has not yet started. + + |
+
+
+ active
+
+ |
+ + Active + | +
+ The DPS has started. + + |
+
+
+ cancelled
+
+ |
+ + Cancelled + | +
+ The DPS has been cancelled prior to starting. + + |
+
+
+ terminated
+
+ |
+ + Terminated + | +
+ The DPS had started, and has now come to a close. This might be due to its successful completion, or might be early termination due to some non-completion. + + |
+
+ dynamicPurchasingSystemType.csv +
+ +
+ You can download the dynamicPurchasingSystemType.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ open
+
+ |
+ + Open + | +
+ The dynamic purchasing system can also be used by buyers not listed in the contracting process. + + |
+
+
+ closed
+
+ |
+ + Closed + | +
+ The dynamic purchasing system can only be used by buyers listed in the contracting process. + + |
+
+ frameworkAgreementMethod.csv +
+ +
+ You can download the frameworkAgreementMethod.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ withReopeningCompetition
+
+ |
+ + With reopening of competition + | +
+ Contracts are awarded by reopening the competition (e.g. mini-competition or mini-tender). + + |
+
+
+ withoutReopeningCompetition
+
+ |
+ + Without reopening of competition + | +
+ Contracts are awarded without the reopening of competition (e.g. direct call-off or direct award). + + |
+
+
+ withAndWithoutReopeningCompetition
+
+ |
+ + With and without reopening of competition + | +
+ Contracts are awarded both with and without the reopening of competition. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/techniques/master/release-schema.json b/en/extensions/techniques/master/release-schema.json
new file mode 100644
index 000000000..0215793d1
--- /dev/null
+++ b/en/extensions/techniques/master/release-schema.json
@@ -0,0 +1,229 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "techniques": {
+ "title": "Techniques",
+ "description": "Information about the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions.",
+ "$ref": "#/definitions/Techniques"
+ },
+ "competitive": {
+ "title": "Is the framework agreement call-off competitive?",
+ "description": "Whether this call-off is competitive or not.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "techniques": {
+ "title": "Techniques",
+ "description": "Information about the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions.",
+ "$ref": "#/definitions/Techniques"
+ }
+ }
+ },
+ "LotGroup": {
+ "properties": {
+ "techniques": {
+ "title": "Techniques",
+ "description": "Information about the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions.",
+ "$ref": "#/definitions/Techniques"
+ }
+ }
+ },
+ "Techniques": {
+ "title": "Techniques",
+ "description": "Information about the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions.",
+ "type": "object",
+ "properties": {
+ "hasFrameworkAgreement": {
+ "title": "Framework agreement involved",
+ "description": "Whether a framework agreement is involved.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "frameworkAgreement": {
+ "title": "Framework agreement",
+ "description": "Information about the framework agreement.",
+ "$ref": "#/definitions/FrameworkAgreement"
+ },
+ "hasDynamicPurchasingSystem": {
+ "title": "Dynamic purchasing system involved",
+ "description": "Whether a dynamic purchasing system is involved.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "dynamicPurchasingSystem": {
+ "title": "Dynamic purchasing system",
+ "description": "Information about the dynamic purchasing system.",
+ "$ref": "#/definitions/DynamicPurchasingSystem"
+ },
+ "hasElectronicAuction": {
+ "title": "Electronic auction used",
+ "description": "Whether an electronic auction is used.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "electronicAuction": {
+ "title": "Electronic auction",
+ "description": "Information about the electronic auction.",
+ "$ref": "#/definitions/ElectronicAuction"
+ }
+ },
+ "minProperties": 1
+ },
+ "FrameworkAgreement": {
+ "title": "Framework agreement",
+ "description": "Information about the framework agreement.",
+ "type": "object",
+ "properties": {
+ "minimumParticipants": {
+ "title": "Minimum number of participants",
+ "description": "The minimum number of participants in the framework agreement.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "maximumParticipants": {
+ "title": "Maximum number of participants",
+ "description": "The maximum number of participants in the framework agreement. If there is no maximum, set to 1e9999 (which parses to infinity).",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "method": {
+ "title": "Method",
+ "description": "Whether contracts are awarded with, without, or both with and without the reopening of competition.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "frameworkAgreementMethod.csv",
+ "openCodelist": false,
+ "enum": [
+ "withReopeningCompetition",
+ "withoutReopeningCompetition",
+ "withAndWithoutReopeningCompetition",
+ null
+ ]
+ },
+ "periodRationale": {
+ "title": "Duration rationale",
+ "description": "The justification for exceptional cases when the duration of a framework agreement exceeds the legal limits.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "buyerCategories": {
+ "title": "Buyer categories",
+ "description": "Any additional categories of buyers participating in the framework agreement and not mentioned by name (e.g. 'all hospitals in the Tuscany region').",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "value": {
+ "title": "Value",
+ "description": "The total upper estimated value of the framework agreement.",
+ "$ref": "#/definitions/Value"
+ },
+ "period": {
+ "title": "Period",
+ "description": "The period over which the framework agreement is estimated to be active.",
+ "$ref": "#/definitions/Period"
+ },
+ "description": {
+ "title": "Description",
+ "description": "A summary description of the framework agreement. This complements any structured information provided using the other fields.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "DynamicPurchasingSystem": {
+ "title": "Dynamic purchasing system",
+ "description": "Information about the dynamic purchasing system.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Type",
+ "description": "In the case of central purchasing bodies, whether the dynamic purchasing system can be used by buyers not listed in the contracting process.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "dynamicPurchasingSystemType.csv",
+ "openCodelist": false,
+ "enum": [
+ "open",
+ "closed",
+ null
+ ]
+ },
+ "status": {
+ "title": "Status",
+ "description": "The status of the dynamic purchasing system.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "dynamicPurchasingSystemStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "pending",
+ "active",
+ "cancelled",
+ "terminated",
+ null
+ ]
+ }
+ },
+ "minProperties": 1
+ },
+ "ElectronicAuction": {
+ "title": "Electronic auction",
+ "description": "Information about the electronic auction.",
+ "type": "object",
+ "properties": {
+ "url": {
+ "title": "URL",
+ "description": "The internet address of the electronic auction.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "Any additional information about the electronic auction.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/techniques/master/schema/index.html b/en/extensions/techniques/master/schema/index.html
new file mode 100644
index 000000000..7e3870946
--- /dev/null
+++ b/en/extensions/techniques/master/schema/index.html
@@ -0,0 +1,797 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Techniques +
+ ++ Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. +
+
+
+
+
+
+
+
+ Framework agreement's
+Framework agreement's
+
+
+
+
+
+
+ + Documentation +
+Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. Also, adds a field to the tender object in a framework agreement call-off to indicate if it is competitive or direct.
+Guidance
+Framework agreement's value and period
+The value and period fields of FrameworkAgreement objects should only be used if a data source provides values and periods for both the contract/lot and the framework agreement, like TED XML Schema R2.08. Otherwise:
-
+
- If a procurement isn't divided into lots, use the
tender.valueandtender.contractPeriodfields.
+ - If a procurement is divided into lots, use the
valueandcontractPeriodfields ofLotobjects.
+
Framework agreement's method
+Here are the possible values for a framework agreement's method field, and common synonyms:
-
+
- withoutReopeningCompetition: call-offs +
- withReopeningCompetition: mini-competitions +
- withAndWithoutReopeningCompetition: call-offs and mini-competitions +
Legal context
+In the European Union, this extension's fields correspond to eForms BG-706 (Techniques), BG-157 (Group Framework Maximum Value and BT-271 (Framework Maximum Value). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Examples
+Framework agreement
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "techniques": {
+ "hasFrameworkAgreement": true,
+ "frameworkAgreement": {
+ "minimumParticipants": 2,
+ "maximumParticipants": 100,
+ "method": "withoutReopeningCompetition",
+ "periodRationale": "<A good justification>",
+ "buyerCategories": "all hospitals in the Tuscany region",
+ "value": {
+ "amount": 240000,
+ "currency": "EUR"
+ },
+ "period": {
+ "durationInDays": 730
+ },
+ "description": "Call offs are estimated to be organized every 3 months, with an average value of 60,000 euros per contract."
+ }
+ }
+ }
+ ]
+ }
+}
+Dynamic purchasing system
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "techniques": {
+ "hasDynamicPurchasingSystem": true,
+ "dynamicPurchasingSystem": {
+ "type": "closed",
+ "status": "active"
+ }
+ }
+ }
+ ]
+ }
+}
+Electronic auction
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "techniques": {
+ "hasElectronicAuction": true,
+ "electronicAuction": {
+ "url": "https://example.com/auction/1",
+ "description": "<Any relevant details>"
+ }
+ }
+ }
+ ]
+ }
+}
+Direct call-off
+{
+ "tender": {
+ "id": "2421-1016-CM20",
+ "procuringEntity": {
+ "name": "I.MUNICIPALIDAD DE CONCEPCION | DIRECCION DE SALUD MUNICIPAL DE CONCEPCION",
+ "id": "CL-MP-3413"
+ },
+ "competitive": false
+ },
+ "awards": [
+ {
+ "id": "42133251",
+ "title": "JERINGAS DAS CONCEPCION",
+ "description": "2239-16-LR15 Órtesis, Prótesis, Endoprótesis e Insumos de Salud. FINANCIAMIENTO: 215.22.04.005.001 SP 28 SE SOLICITA LA ACEPTACIÓN DE ESTA ORCOM A TRAVÉS DE LA PLATAFORMA MERCADO PUBLICO ANTES DE REALIZAR LA ENTREGA DEL BIEN O SERVICIO",
+ "status": "active",
+ "date": "2020-06-23T15:40:44Z",
+ "value": {
+ "amount": 7526475.0,
+ "currency": "CLP"
+ },
+ "suppliers": [
+ {
+ "name": "Tecnika S.A. | Tecnika S.A.",
+ "id": "CL-MP-27291"
+ }
+ ],
+ "items": [
+ {
+ "id": "111570611",
+ "description": "Aparatos de inyección hipodérmica o accesorios(1391678 )JERINGA HIPODERMICA CONTROLADA VENOTEK 10ML LUER LOCK CON AGUJA 21GX1 1/2 100 UNIDADES 1418179",
+ "quantity": 500.0,
+ "unit": {
+ "value": {
+ "amount": 4228.0,
+ "currency": "CLP"
+ }
+ }
+ }
+ ]
+ }
+ ],
+ "relatedProcesses": [
+ {
+ "id": "1",
+ "relationship": [
+ "framework"
+ ],
+ "title": "Órtesis, Prótesis, Endoprótesis e Insumos de Salud",
+ "scheme": "ocid",
+ "identifier": "ocds-70d2nz-2239-16-LR15"
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2023-06-07
+-
+
- Merge the Competitive extension. +
- Add
LotGroup.techniquesfield.
+
2020-10-05
+-
+
- Add fields:
+
-
+
FrameworkAgreement.minimumParticipants
+FrameworkAgreement.value
+FrameworkAgreement.period
+FrameworkAgreement.description
+
+
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile, in pull requests and in https://github.com/open-contracting/standard/issues/695.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/tenderClassification/index.html b/en/extensions/tenderClassification/index.html
new file mode 100644
index 000000000..90c4d5628
--- /dev/null
+++ b/en/extensions/tenderClassification/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Techniques +
+ ++ Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ techniques
+
+ |
+ + Techniques + | +
+ Information about the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. + + |
+ + Techniques object + | +
+
+ competitive
+
+ |
+ + Is the framework agreement call-off competitive? + | +
+ Whether this call-off is competitive or not. + + |
+ + boolean + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ techniques
+
+ |
+ + Techniques + | +
+ Information about the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. + + |
+ + Techniques object + | +
+ LotGroup +
+ +
+ The extension defines these fields in the LotGroup object from the Lots extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ techniques
+
+ |
+ + Techniques + | +
+ Information about the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. + + |
+ + Techniques object + | +
+ Techniques +
+ +
+ The extension defines a new Techniques object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasFrameworkAgreement
+
+ |
+ + Framework agreement involved + | +
+ Whether a framework agreement is involved. + + |
+ + boolean + | +
+
+ frameworkAgreement
+
+ |
+ + Framework agreement + | +
+ Information about the framework agreement. + + |
+ + FrameworkAgreement object + | +
+
+ hasDynamicPurchasingSystem
+
+ |
+ + Dynamic purchasing system involved + | +
+ Whether a dynamic purchasing system is involved. + + |
+ + boolean + | +
+
+ dynamicPurchasingSystem
+
+ |
+ + Dynamic purchasing system + | +
+ Information about the dynamic purchasing system. + + |
+ + DynamicPurchasingSystem object + | +
+
+ hasElectronicAuction
+
+ |
+ + Electronic auction used + | +
+ Whether an electronic auction is used. + + |
+ + boolean + | +
+
+ electronicAuction
+
+ |
+ + Electronic auction + | +
+ Information about the electronic auction. + + |
+ + ElectronicAuction object + | +
+ FrameworkAgreement +
+ +
+ The extension defines a new FrameworkAgreement object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ minimumParticipants
+
+ |
+ + Minimum number of participants + | +
+ The minimum number of participants in the framework agreement. + + |
+ + number + | +
+
+ maximumParticipants
+
+ |
+ + Maximum number of participants + | +
+ The maximum number of participants in the framework agreement. If there is no maximum, set to 1e9999 (which parses to infinity). + + |
+ + number + | +
+
+ method
+
+ |
+ + Method + | +
+ Whether contracts are awarded with, without, or both with and without the reopening of competition. + + |
+ + string from closed frameworkAgreementMethod codelist + | +
+
+ periodRationale
+
+ |
+ + Duration rationale + | +
+ The justification for exceptional cases when the duration of a framework agreement exceeds the legal limits. + + |
+ + string + | +
+
+ buyerCategories
+
+ |
+ + Buyer categories + | +
+ Any additional categories of buyers participating in the framework agreement and not mentioned by name (e.g. 'all hospitals in the Tuscany region'). + + |
+ + string + | +
+
+ value
+
+ |
+ + Value + | +
+ The total upper estimated value of the framework agreement. + + |
+ + Value object + | +
+
+ period
+
+ |
+ + Period + | +
+ The period over which the framework agreement is estimated to be active. + + |
+ + Period object + | +
+
+ description
+
+ |
+ + Description + | +
+ A summary description of the framework agreement. This complements any structured information provided using the other fields. + + |
+ + string + | +
+ DynamicPurchasingSystem +
+ +
+ The extension defines a new DynamicPurchasingSystem object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Type + | +
+ In the case of central purchasing bodies, whether the dynamic purchasing system can be used by buyers not listed in the contracting process. + + |
+ + string from closed dynamicPurchasingSystemType codelist + | +
+
+ status
+
+ |
+ + Status + | +
+ The status of the dynamic purchasing system. + + |
+ + string from closed dynamicPurchasingSystemStatus codelist + | +
+ ElectronicAuction +
+ +
+ The extension defines a new ElectronicAuction object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ url
+
+ |
+ + URL + | +
+ The internet address of the electronic auction. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ Any additional information about the electronic auction. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/tenderClassification/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/tenderClassification/master/extension.json b/en/extensions/tenderClassification/master/extension.json
new file mode 100644
index 000000000..2b2806257
--- /dev/null
+++ b/en/extensions/tenderClassification/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Tender classification",
+ "es": "Clasificaci\u00f3n de la licitaci\u00f3n"
+ },
+ "description": {
+ "en": "Adds an array of classification objects to the tender object, in order to categorize the procedure or call-off as a whole.",
+ "es": "Agregar una serie de objetos de clasificaci\u00f3n al objeto de licitaci\u00f3n para categorizar el procedimiento o la solicitud de orden de compra como un todo."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/tenderClassification/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+itemClassificationScheme.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/tenderClassification/master/index.html b/en/extensions/tenderClassification/master/index.html
new file mode 100644
index 000000000..0d74d3556
--- /dev/null
+++ b/en/extensions/tenderClassification/master/index.html
@@ -0,0 +1,316 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tender classification +
+ ++ Adds an array of classification objects to the tender object, in order to categorize the procedure or call-off as a whole. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ TED_CATEGORY
+
+ |
+ + EC Public passenger transport services covered + | +
+ A classification of the services covered by the award of contracts for public passenger transport services according to Regulation 1370/2007 of the European Parliament. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/tenderClassification/master/release-schema.json b/en/extensions/tenderClassification/master/release-schema.json
new file mode 100644
index 000000000..9eb0d6e1f
--- /dev/null
+++ b/en/extensions/tenderClassification/master/release-schema.json
@@ -0,0 +1,24 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "classification": {
+ "title": "Tender classification",
+ "description": "The primary classification of the contracting process.",
+ "$ref": "#/definitions/Classification"
+ },
+ "additionalClassifications": {
+ "title": "Tender additional classifications",
+ "description": "Additional classifications of the contracting process.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/tenderClassification/master/schema/index.html b/en/extensions/tenderClassification/master/schema/index.html
new file mode 100644
index 000000000..2d11832dc
--- /dev/null
+++ b/en/extensions/tenderClassification/master/schema/index.html
@@ -0,0 +1,253 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tender classification +
+ ++ Adds an array of classification objects to the tender object, in order to categorize the procedure or call-off as a whole. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an array of classification objects to the tender object, in order to categorize the procedure or call-off as a whole.
+The items to be procured are expected to have more specific classifications than the procedure as a whole.
+Legal context
+In the European Union, this extension's fields correspond to eForms BG-261 (Classification). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Example
+{
+ "tender": {
+ "classification": {
+ "description": "Advertising management services",
+ "id": "79341200-8",
+ "scheme": "CPV"
+ },
+ "additionalClassifications": [
+ {
+ "description": "Advertising campaign services",
+ "id": "79341400-0",
+ "scheme": "CPV"
+ },
+ {
+ "description": "Customer services",
+ "id": "79342300-6",
+ "scheme": "CPV"
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2021-01-19
+-
+
- Add "or call-off" in the description of the extension. +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/tender_datePublished/index.html b/en/extensions/tender_datePublished/index.html
new file mode 100644
index 000000000..8f2d18425
--- /dev/null
+++ b/en/extensions/tender_datePublished/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tender classification +
+ ++ Adds an array of classification objects to the tender object, in order to categorize the procedure or call-off as a whole. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ classification
+
+ |
+ + Tender classification + | +
+ The primary classification of the contracting process. + + |
+ + Classification object + | +
+
+ additionalClassifications
+
+ |
+ + Tender additional classifications + | +
+ Additional classifications of the contracting process. + + |
+ + array of Classification objects + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/tender_datePublished/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/tender_datePublished/master/release-schema.json b/en/extensions/tender_datePublished/master/release-schema.json
new file mode 100644
index 000000000..e73dfa209
--- /dev/null
+++ b/en/extensions/tender_datePublished/master/release-schema.json
@@ -0,0 +1,17 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "datePublished": {
+ "title": "Date Published",
+ "description": "The date when the tender was published.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/tender_datePublished/master/schema/index.html b/en/extensions/tender_datePublished/master/schema/index.html
new file mode 100644
index 000000000..3edb551c5
--- /dev/null
+++ b/en/extensions/tender_datePublished/master/schema/index.html
@@ -0,0 +1,231 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tender Date Published +
+ ++ Adds a date field to indicate when the tender was published. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds a field to explicitly indicate the date and time when the tender was published. This field can be different from tender/tenderPeriod/startDate and date fields.
Usage
+Having this information in a easy way to access it can have many benefits, for instance, to be able to compute some indicators that will say how many days a potential bidder has to prepare an offer.
+To satisfy such use cases, the tender/datePublished field should be used.
Example
+{
+ "tender": {
+ "datePublished": "2019-07-23T1:27:10.673000-06:00"
+ }
+}
+Changelog
+This extension was originally discussed in https://github.com/open-contracting/standard/issues/892.
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/transaction_milestones/index.html b/en/extensions/transaction_milestones/index.html
new file mode 100644
index 000000000..1df73e0ca
--- /dev/null
+++ b/en/extensions/transaction_milestones/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tender Date Published +
+ ++ Adds a date field to indicate when the tender was published. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ datePublished
+
+ |
+ + Date Published + | +
+ The date when the tender was published. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/transaction_milestones/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/transaction_milestones/master/release-schema.json b/en/extensions/transaction_milestones/master/release-schema.json
new file mode 100644
index 000000000..f65f2cc04
--- /dev/null
+++ b/en/extensions/transaction_milestones/master/release-schema.json
@@ -0,0 +1,13 @@
+{
+ "definitions": {
+ "Transaction": {
+ "properties": {
+ "relatedImplementationMilestone": {
+ "title": "Related implementation milestone",
+ "description": "A link to the milestone in the implementation section of OCDS to which this transaction relates.",
+ "$ref": "#/definitions/MilestoneReference"
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/transaction_milestones/master/schema/index.html b/en/extensions/transaction_milestones/master/schema/index.html
new file mode 100644
index 000000000..de0eb5dde
--- /dev/null
+++ b/en/extensions/transaction_milestones/master/schema/index.html
@@ -0,0 +1,235 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Transaction related milestones +
+ ++ Adds a relatedImplementationMilestone field to transaction objects, so that payments against a contract can be linked with an implementation milestone. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds a relatedImplementationMilestone field to transaction objects, so that payments against a contract can be linked with an implementation milestone.
This extension must be used with the Metrics extension.
+Example
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "implementation": {
+ "milestones": [
+ {
+ "id": "1234",
+ "title": "Example milestone",
+ "dueDate": "2017-01-01T17:00:00Z",
+ "dateMet": "2016-12-28T17:00:00Z",
+ "status": "met",
+ "dateModified": "2016-12-28T17:00:00Z"
+ }
+ ],
+ "transactions": [
+ {
+ "id": "ABC-123",
+ "source": "http://www.example.com/budget/FY17",
+ "date": "2017-01-05T13:00:00Z",
+ "value": {
+ "amount": 150000,
+ "currency": "GBP"
+ },
+ "payer": {
+ "id": "GB-GOV-00000000",
+ "name": "Example ministry"
+ },
+ "payee": {
+ "id": "GB-COH-99999999",
+ "name": "Example consortium"
+ },
+ "relatedImplementationMilestone": {
+ "id": "1234",
+ "title": "Example milestone"
+ }
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/transaction_milestones/v1.1/README.md b/en/extensions/transaction_milestones/v1.1/README.md
new file mode 100644
index 000000000..deaebf2bd
--- /dev/null
+++ b/en/extensions/transaction_milestones/v1.1/README.md
@@ -0,0 +1,55 @@
+# Transactions - relatedMilestone Extension
+
+## Background
+
+In core OCDS `transactions` are a property of the `implementation` object.
+
+Some contracts link payments against a contract to specific milestones for the delivery of the contract.
+
+## Extension fields
+
+This extension adds a `relatedImplementationMilestone` property to the `transaction` object.
+
+The `relatedImplementationMilestone` property is a `milestoneReference` object.
+
+The `milestoneReference` object is introduced by the [metrics extension](https://github.com/open-contracting/ocds_metrics_extension).
+
+## Example
+
+```json
+"implementation": {
+ "milestones": [
+ {
+ "id": "1234",
+ "title": "Example milestone",
+ "dueDate": "2017-01-01T17:00:00Z",
+ "dateMet": "2016-12-28T17:00:00Z",
+ "status": "met",
+ "dateModified": "2016-12-28T17:00:00Z"
+ }
+ ],
+ "transactions": [
+ {
+ "id": "ABC-123",
+ "source": "http://www.example.com/budget/FY17",
+ "date": "2017-01-05T13:00:00Z",
+ "value": {
+ "amount": 150000,
+ "currency": "GBP"
+ },
+ "payer": {
+ "id": "GB-GOV-00000000",
+ "name": "Example ministry"
+ },
+ "payee": {
+ "id": "GB-COH-99999999",
+ "name": "Example consortium"
+ },
+ "relatedImplementationMilestone": {
+ "id": "1234",
+ "title": "Example milestone"
+ }
+ }
+ ]
+}
+```
diff --git a/en/extensions/transaction_milestones/v1.1/extension.json b/en/extensions/transaction_milestones/v1.1/extension.json
new file mode 100644
index 000000000..236bb4ae9
--- /dev/null
+++ b/en/extensions/transaction_milestones/v1.1/extension.json
@@ -0,0 +1,14 @@
+{
+ "name": {
+ "en": "ocds_transactions_relatedMilestone_extension",
+ "es": "ocds_transactions_relatedMilestone_extension"
+ },
+ "description": {
+ "en": "Adds a relatedImplementationMilestone property to the transactions object so that disbursements can be linked with their associated milestone.",
+ "es": "Agrega una propiedad relatedImplementationMilestone al objeto de transacciones para que los desembolsos se puedan vincular con su hito asociado."
+ },
+ "documentationUrl": {},
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/en/extensions/transaction_milestones/v1.1/index.html b/en/extensions/transaction_milestones/v1.1/index.html
new file mode 100644
index 000000000..d5d186ef2
--- /dev/null
+++ b/en/extensions/transaction_milestones/v1.1/index.html
@@ -0,0 +1,315 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Transaction related milestones +
+ ++ Adds a relatedImplementationMilestone field to transaction objects, so that payments against a contract can be linked with an implementation milestone. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Transaction +
+ +
+ The extension defines these fields in the Transaction object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedImplementationMilestone
+
+ |
+ + Related implementation milestone + | +
+ A link to the milestone in the implementation section of OCDS to which this transaction relates. + + |
+ + MilestoneReference object + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/transaction_milestones/v1.1/release-schema.json b/en/extensions/transaction_milestones/v1.1/release-schema.json
new file mode 100644
index 000000000..f65f2cc04
--- /dev/null
+++ b/en/extensions/transaction_milestones/v1.1/release-schema.json
@@ -0,0 +1,13 @@
+{
+ "definitions": {
+ "Transaction": {
+ "properties": {
+ "relatedImplementationMilestone": {
+ "title": "Related implementation milestone",
+ "description": "A link to the milestone in the implementation section of OCDS to which this transaction relates.",
+ "$ref": "#/definitions/MilestoneReference"
+ }
+ }
+ }
+ }
+}
diff --git a/en/extensions/transaction_milestones/v1.1/schema/index.html b/en/extensions/transaction_milestones/v1.1/schema/index.html
new file mode 100644
index 000000000..fb61d88be
--- /dev/null
+++ b/en/extensions/transaction_milestones/v1.1/schema/index.html
@@ -0,0 +1,235 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Transaction related milestones +
+ ++ Adds a relatedImplementationMilestone field to transaction objects, so that payments against a contract can be linked with an implementation milestone. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Background
+In core OCDS transactions are a property of the implementation object.
Some contracts link payments against a contract to specific milestones for the delivery of the contract.
+Extension fields
+This extension adds a relatedImplementationMilestone property to the transaction object.
The relatedImplementationMilestone property is a milestoneReference object.
The milestoneReference object is introduced by the metrics extension.
Example
+"implementation": {
+ "milestones": [
+ {
+ "id": "1234",
+ "title": "Example milestone",
+ "dueDate": "2017-01-01T17:00:00Z",
+ "dateMet": "2016-12-28T17:00:00Z",
+ "status": "met",
+ "dateModified": "2016-12-28T17:00:00Z"
+ }
+ ],
+ "transactions": [
+ {
+ "id": "ABC-123",
+ "source": "http://www.example.com/budget/FY17",
+ "date": "2017-01-05T13:00:00Z",
+ "value": {
+ "amount": 150000,
+ "currency": "GBP"
+ },
+ "payer": {
+ "id": "GB-GOV-00000000",
+ "name": "Example ministry"
+ },
+ "payee": {
+ "id": "GB-COH-99999999",
+ "name": "Example consortium"
+ },
+ "relatedImplementationMilestone": {
+ "id": "1234",
+ "title": "Example milestone"
+ }
+ }
+ ]
+}
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/unstructuredChanges/index.html b/en/extensions/unstructuredChanges/index.html
new file mode 100644
index 000000000..0c81401fc
--- /dev/null
+++ b/en/extensions/unstructuredChanges/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Transaction related milestones +
+ ++ Adds a relatedImplementationMilestone field to transaction objects, so that payments against a contract can be linked with an implementation milestone. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Transaction +
+ +
+ The extension defines these fields in the Transaction object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedImplementationMilestone
+
+ |
+ + Related implementation milestone + | +
+ A link to the milestone in the implementation section of OCDS to which this transaction relates. + + |
+ + MilestoneReference object + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/unstructuredChanges/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/unstructuredChanges/master/release-schema.json b/en/extensions/unstructuredChanges/master/release-schema.json
new file mode 100644
index 000000000..5e4df977d
--- /dev/null
+++ b/en/extensions/unstructuredChanges/master/release-schema.json
@@ -0,0 +1,109 @@
+{
+ "definitions": {
+ "Amendment": {
+ "properties": {
+ "unstructuredChanges": {
+ "title": "Unstructured changes",
+ "description": "Unstructured or semi-structured changes to an earlier notice.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/UnstructuredChange"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "UnstructuredChange": {
+ "title": "Unstructured change",
+ "description": "Unstructured or semi-structured change to an earlier notice.",
+ "type": "object",
+ "properties": {
+ "relatedLot": {
+ "title": "Related lot",
+ "description": "The identifier of the lot to which this change relates, if any.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "oldValue": {
+ "title": "Old value",
+ "description": "The value of the data element referenced by the `where` field, before the change.",
+ "$ref": "#/definitions/UnstructuredChangeValue"
+ },
+ "newValue": {
+ "title": "New value",
+ "description": "The value of the data element referenced by the `where` field, after the change.",
+ "$ref": "#/definitions/UnstructuredChangeValue"
+ },
+ "where": {
+ "title": "Where",
+ "description": "A reference to a data element on an earlier notice that is being changed.",
+ "type": "object",
+ "properties": {
+ "section": {
+ "title": "Section",
+ "description": "The identifier of the section containing the data element, if the earlier notice is organized into sections.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "label": {
+ "title": "Label",
+ "description": "The label for the data element.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "UnstructuredChangeValue": {
+ "title": "Unstructured change value",
+ "description": "A value of a data element. The value must be described using exactly one of the fields `text`, `classifications` or `date`.",
+ "type": "object",
+ "properties": {
+ "text": {
+ "title": "Text value",
+ "description": "A text. If the change deleted or erased the data element, use the empty string (\"\").",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "classifications": {
+ "title": "Classifications",
+ "description": "A list of classifications.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "date": {
+ "title": "Date",
+ "description": "A date.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "pattern": "^\\d{4}-[01]\\d-[0-3]\\d(T[0-2]\\d:[0-5]\\d:[0-5]\\d([+-][0-2]\\d:?[0-5]\\d|Z))?$"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/unstructuredChanges/master/schema/index.html b/en/extensions/unstructuredChanges/master/schema/index.html
new file mode 100644
index 000000000..bdd94dc7a
--- /dev/null
+++ b/en/extensions/unstructuredChanges/master/schema/index.html
@@ -0,0 +1,452 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Unstructured changes +
+ ++ Adds an unstructuredChanges array to the Amendment object. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an unstructuredChanges array to the Amendment object.
+Guidance
+In many procurement regimes, it is common to amend a procurement notice by describing the changes in words, rather than by re-publishing the full notice. This is because the process is designed for humans: it is easier for a human to read a description of changes, than to calculate the difference between two full notices.
+On the other hand, it is easy for a machine to calculate the difference between two full notices, but difficult or impossible to interpret a description of changes. There are many ways in which a change description can go wrong, which a human can recover from, but which a machine cannot. For example:
+-
+
- The label of the field that is subject to modification can refer to:
+
-
+
- a label that doesn't occur on the earlier notice +
- an incorrect or imprecise label on the earlier notice +
+ - The data type of the new value can be inconsistent with the data type of the field. +
OCDS is designed to be read by machines. Ideally, the source system from which OCDS data is exported contains the values of each field before and after a change. In that case, you should simply follow the releases and records model.
+This extension is intended to be used only in cases where a source system doesn't track the values of fields, but instead tracks a description of changes, like in the EU (see Legal context below). Note: The lack of structure prevents much data analysis.
+Legal context
+This extension was developed primarily to enable the mapping of the European Union's standard forms for public procurement to OCDS (specifically Form 14 Corrigendum), but it might be useful in non-EU contexts.
+See OCDS for the European Union for guidance on how to use it with TED F14 data.
+Example
+{
+ "tender": {
+ "amendments": [
+ {
+ "id": "1",
+ "unstructuredChanges": [
+ {
+ "oldValue": {
+ "text": "https://city.example.org/procurement"
+ },
+ "newValue": {
+ "text": "https://procurement.example.org"
+ },
+ "where": {
+ "section": "I.1",
+ "label": "Main address"
+ }
+ },
+ {
+ "oldValue": {
+ "date": "2020-12-15"
+ },
+ "newValue": {
+ "date": "2019-12-15T14:00:00+03:00"
+ },
+ "where": {
+ "section": "I.4",
+ "label": "Notice date"
+ }
+ },
+ {
+ "oldValue": {
+ "classifications": [
+ {
+ "scheme": "CPV",
+ "id": "79000000"
+ }
+ ]
+ },
+ "newValue": {
+ "classifications": [
+ {
+ "scheme": "CPV",
+ "id": "79822500"
+ }
+ ]
+ },
+ "where": {
+ "section": "II.2.2",
+ "label": "Main CPV code"
+ },
+ "relatedLot": "lot-2"
+ }
+ ]
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+Changelog
+2020-09-16
+-
+
- Add Guidance section +
2020-07-13
+-
+
- Relax date format to allow either date or datetime +
2020-06-04
+-
+
- Review normative and non-normative words. +
2020-04-24
+-
+
- Add
minProperties,minItemsand/orminLengthproperties.
+
This extension was originally discussed as part of the OCDS for EU profile and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/withheldInformation/index.html b/en/extensions/withheldInformation/index.html
new file mode 100644
index 000000000..8ca3ab2a9
--- /dev/null
+++ b/en/extensions/withheldInformation/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Unstructured changes +
+ ++ Adds an unstructuredChanges array to the Amendment object. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Amendment +
+ +
+ The extension defines these fields in the Amendment object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ unstructuredChanges
+
+ |
+ + Unstructured changes + | +
+ Unstructured or semi-structured changes to an earlier notice. + + |
+ + array of UnstructuredChange objects + | +
+ UnstructuredChange +
+ +
+ The extension defines a new UnstructuredChange object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLot
+
+ |
+ + Related lot + | +
+ The identifier of the lot to which this change relates, if any. + + |
+ + string + | +
+
+ oldValue
+
+ |
+ + Old value + | +
+ The value of the data element referenced by the |
+ + UnstructuredChangeValue object + | +
+
+ newValue
+
+ |
+ + New value + | +
+ The value of the data element referenced by the |
+ + UnstructuredChangeValue object + | +
+
+ where
+
+ |
+ + Where + | +
+ A reference to a data element on an earlier notice that is being changed. + + |
+ + object + | +
+
+ where.
+ |
+ + Section + | +
+ The identifier of the section containing the data element, if the earlier notice is organized into sections. + + |
+ + string + | +
+
+ where.
+ |
+ + Label + | +
+ The label for the data element. + + |
+ + string + | +
+ UnstructuredChangeValue +
+ +
+ The extension defines a new UnstructuredChangeValue object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ text
+
+ |
+ + Text value + | +
+ A text. If the change deleted or erased the data element, use the empty string (""). + + |
+ + string + | +
+
+ classifications
+
+ |
+ + Classifications + | +
+ A list of classifications. + + |
+ + array of Classification objects + | +
+
+ date
+
+ |
+ + Date + | +
+ A date. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /en/extensions/withheldInformation/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/withheldInformation/master/extension.json b/en/extensions/withheldInformation/master/extension.json
new file mode 100644
index 000000000..08685aa88
--- /dev/null
+++ b/en/extensions/withheldInformation/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Withheld information",
+ "es": "Withheld information"
+ },
+ "description": {
+ "en": "Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld.",
+ "es": "Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld."
+ },
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting-extensions/ocds_withheldInformation_extension"
+ },
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+itemClassificationScheme.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/en/extensions/withheldInformation/master/index.html b/en/extensions/withheldInformation/master/index.html
new file mode 100644
index 000000000..796cae760
--- /dev/null
+++ b/en/extensions/withheldInformation/master/index.html
@@ -0,0 +1,298 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Withheld information +
+ ++ Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ eu-non-publication-justification
+
+ |
+ + European Union non-publication justification + | +
+ The main reasons for not immediately publishing information required by eForms within the context of public procurement according to the legislation of the European Parliament. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/extensions/withheldInformation/master/release-schema.json b/en/extensions/withheldInformation/master/release-schema.json
new file mode 100644
index 000000000..5130b0229
--- /dev/null
+++ b/en/extensions/withheldInformation/master/release-schema.json
@@ -0,0 +1,80 @@
+{
+ "properties": {
+ "withheldInformation": {
+ "title": "Withheld information",
+ "description": "Details of items of information whose publication is temporarily or permanently withheld.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/WithheldInformationItem"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "definitions": {
+ "WithheldInformationItem": {
+ "title": "Withheld information item",
+ "description": "An item of information whose publication is temporarily or permanently withheld.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "The locally unique identifier for the withheld information item.",
+ "type": "string",
+ "minLength": 1
+ },
+ "field": {
+ "title": "Field",
+ "description": "The identifier of the field with which the withheld information would otherwise be published.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "name": {
+ "title": "Name",
+ "description": "The name or title of the field with which the withheld information would otherwise be published.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "availabilityDate": {
+ "title": "Availability date",
+ "description": "The date on which the withheld information will be published.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "rationale": {
+ "title": "Rationale",
+ "description": "The rationale for withholding the information.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "rationaleClassifications": {
+ "title": "Rationale classifications",
+ "description": "Classifications of the rationale for withholding the information.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/en/extensions/withheldInformation/master/schema/index.html b/en/extensions/withheldInformation/master/schema/index.html
new file mode 100644
index 000000000..a32e6dddf
--- /dev/null
+++ b/en/extensions/withheldInformation/master/schema/index.html
@@ -0,0 +1,372 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Withheld information +
+ ++ Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld.
+Legal context
+In the European Union, this extension's fields correspond to eForms BG-8 (Not Immediately Published). For correspondences to eForms fields, see OCDS for eForms.
+Example
+{
+ "withheldInformation": [
+ {
+ "id": "cro-bor-law-18d27a53-0109-4f93-9231-6659d931bce0",
+ "field": "cro-bor-law",
+ "name": "Cross Border Law",
+ "rationale": "Publication of this information is delayed because...",
+ "rationaleClassifications": [
+ {
+ "scheme": "eu-non-publication-justification",
+ "id": "oth-int",
+ "description": "Other public interest",
+ "uri": "http://publications.europa.eu/resource/authority/non-publication-justification/oth-int"
+ }
+ ],
+ "availabilityDate": "2024-12-31T09:00:00+01:00"
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/en/index.html b/en/index.html
new file mode 100644
index 000000000..281577399
--- /dev/null
+++ b/en/index.html
@@ -0,0 +1,117 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Withheld information +
+ ++ Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ withheldInformation
+
+ |
+ + Withheld information + | +
+ Details of items of information whose publication is temporarily or permanently withheld. + + |
+ + array of WithheldInformationItem objects + | +
+ WithheldInformationItem +
+ +
+ The extension defines a new WithheldInformationItem object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ The locally unique identifier for the withheld information item. + + |
+ + string + | +
+
+ field
+
+ |
+ + Field + | +
+ The identifier of the field with which the withheld information would otherwise be published. + + |
+ + string + | +
+
+ name
+
+ |
+ + Name + | +
+ The name or title of the field with which the withheld information would otherwise be published. + + |
+ + string + | +
+
+ availabilityDate
+
+ |
+ + Availability date + | +
+ The date on which the withheld information will be published. + + |
+ + string + | +
+
+ rationale
+
+ |
+ + Rationale + | +
+ The rationale for withholding the information. + + |
+ + string + | +
+
+ rationaleClassifications
+
+ |
+ + Rationale classifications + | +
+ Classifications of the rationale for withholding the information. + + |
+ + array of Classification objects + | +
+
+
+
+
+
+ + OCDS Extension Explorer +
+ ++ Disclose more data about your contracting processes, using extensions to the Open Contracting Data Standard. +
+ +
+
+
+
+
+
+
+
+
+
+
+ For data publishers
+OCDS defines a core set of fields and codes for describing contracting processes. You can use extensions to describe additional fields outside the core set.
+ Read the publisher guidance +
+
+
+
+
+
+ For data users
+OCDS data can include fields and codes from the OCDS schema and from extensions. To understand extended data, you need to identify which extensions are used and read the extensions' documentation.
+ Read the user guidance +
+
+
+
+
+
+ + Publisher Guidance +
+ ++ To implement OCDS, you must identify the fields and codes in OCDS that match the data elements that you want to publish. Some data elements might not match any field or code in OCDS. To cover such cases, you can add additional fields or codes to your OCDS data. Extensions provide a way to document these additional fields and codes. +
+ ++ Why use extensions? +
+ ++ We recommend using extensions to describe your additional fields and codes so that: +
+ +-
+
- + Analysts can access definitions for fields and codes to help them interpret your data. + +
- + Developers can access information about the structure of your data to help write software to process it. + +
- + Your data is consistent with that of other publishers and compatible with reusable tools and methodologies. + +
+ Use an extension +
+ ++ To publish additional fields or codes using an extension: +
+ +-
+
- + Use the Extension Explorer to find an extension that describes the data element(s) you want to publish. If you can’t find a suitable extension, you might need to create an extension. + +
- + Structure your data according to the extension’s schema and documentation. + +
-
+ Declare the extension in your package’s `extensions` array using the URL from the extension’s documentation. For example, to declare the Bid statistics and details extension:
+ ++
+ {"extensions": ["https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"]} ++
+ - + Check your data using the OCDS Data Review Tool. + +
+ Create an extension +
++ If you can’t find a suitable extension to describe the data elements you want to publish, you can create an extension. +
+ ++ Extensions can introduce new fields, add codes to open codelists and introduce additional validation rules to existing OCDS fields. However, extensions cannot remove fields, change the title or description of fields or add codes to closed codelists. To suggest such changes, open an issue on the standard issue tracker. +
+ ++ You should also consider whether the data you want to publish belongs to the contracting process or whether it exists independently. Data that exists independently of the contracting process is typically better published in a separate dataset. For example, data on changes to the beneficial ownership of suppliers, which is usually tracked outside of procurement systems. +
+ ++ To create an extension you need to understand JSON Schema and the structure of the OCDS schema. Extensions are fragments of JSON Schema that can be merged into the OCDS schema to create an extended schema. +
+ ++ The standard extension template describes the structure and components of an extension and the technical steps to document an extension. +
+ ++ There are five steps to creating an extension: +
+ ++ Discuss +
+ ++ Before creating an extension, search for related discussions on the standard issue tracker. +
+ ++ If you can’t find any related discussions, open an issue to describe the extension you plan to create. The issue’s description should include: +
+ +-
+
- + The extension’s use case(s). Describe your reason for adding additional fields and/or codes and what users will do with the data. + +
- + The concepts or process that you want to represent. Explain the underlying concepts described by the extension and the workflow for collecting the data. Include references to legislation and other documentation, and consider providing a + diagram. + +
- + Examples of existing data. Provide examples of how the data covered by the extension is represented in your data sources. + +
- + To encourage collaboration, keep this issue up to date throughout the development of your extension. + +
+ Develop +
+ ++ You first need to decide on the name, structure and format of the fields in your extension. +
+ ++ You can start by mocking up an example of the data you are creating an extension for in JSON format. Consider: +
+ +-
+
- + How would different data fit into this structure? + +
- + Are the field names intuitive for users? + +
- + Is the structure easy for applications to consume? + +
- + You can also check other standards for potential models. The more different examples of source data, and different use cases for the data you can consider, the better. + +
+ Before continuing, you should invite feedback on your mockup using the Github issue you created in the previous step. +
+ ++ Once you have settled on a model, you should then document the schema for your extension. The following tools are available to help you: +
+ +-
+
- + You can use the OCDS Extension Creator to edit the OCDS schema and generate a patch. For more information on using the extension creator, refer to its documentation. + +
- + You can copy the standard extension template and use a text editor to edit the schema files. + +
- + You can use JSONschema.net to generate a schema from your JSON mockup. + +
+ Your schema should follow the schema style guide. +
+ ++ Document +
+ ++ You will need to find somewhere to host your extension online at a stable URL. Creating a GitHub repository for your extension is a good option because it offers version control and issue tracking. +
+ ++ You also need to write a README file and/or other documentation for your extension. +
+ ++ Your documentation should include a description of the extension and its use cases, and examples of data structured according to the extension. +
+ ++ Test +
++ Test your extension by following steps 2-4 in Use an extension. +
+ ++ Register +
++ We encourage you to register your extension so that others can discover it using the Extension Explorer. +
+ ++ Extensions that are useful to only a single publisher do not need to be registered. +
+ ++ To register an extension, it must meet the following criteria: +
+ +-
+
- + The documentation is in English. According to the translation and localization policy, “the authoritative language for the standard is English.” As such, all extensions in the Extension Explorer – as part of the standard’s documentation + – must be in English. + +
- + The documentation, excluding examples, is more than 200 characters long. Documentation of less than 200 characters cannot adequately describe an extension, its purpose and technical details. + +
- + The extension.json and README.md files are not publisher-specific. If the extension’s name or description suggests it is relevant to only one publisher, then it is unlikely to be used by other publishers, even if the schema patch is + relevant. + +
- + No other extension expresses the same concepts. Having multiple ways to express the same concept would be counter-productive to standardization. + +
- + The extension follows the schema style guide. + +
+ Versioning +
++ OCDS extensions should use semantic versioning. +
+ +
+
+
+
+
+
+ + User Guidance +
+ ++ To use data, you first need to understand its structure and meaning. OCDS data can contain fields from: +
+ +
-
+
- + OCDS, whose fields are described in its schema and in its Schema Reference. + +
- + Extensions, whose fields are described in their schema and in their documentation. + +
+ To identify which extensions are used in OCDS data, you can either: +
+ +-
+
-
+ Check for an
extensionsfield at the package level. For data with extensions, this field contains an array of URLs toextension.jsonfiles. Each file contains adocumentationUrlobject with a URL to the extension's documentation. Open the URL to read its documentation (in many cases, the URL leads to this website). For example, the following data declares the Bid statistics and details extension: ++++ {"extensions": ["https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"]} ++
+ - + Upload the data to the OCDS Data Review Tool, which lists the extensions used and links to their documentation. + +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/additionalContactPoint/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/additionalContactPoint/master/release-schema.json b/es/extensions/additionalContactPoint/master/release-schema.json
new file mode 100644
index 000000000..8ba8eed87
--- /dev/null
+++ b/es/extensions/additionalContactPoint/master/release-schema.json
@@ -0,0 +1,37 @@
+{
+ "definitions": {
+ "Organization": {
+ "properties": {
+ "additionalContactPoints": {
+ "title": "Puntos adicionales de contacto",
+ "description": "Una lista de puntos de contacto adicionales puede consultarse para obtener informaci\u00f3n. Los puntos de contacto adicionales deben listar en su nombre los idiomas en los que operan y como datos estructurados en el campo availableLanguage.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/ContactPoint"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "ContactPoint": {
+ "properties": {
+ "availableLanguage": {
+ "title": "Lenguajes disponibles",
+ "description": "Los idiomas en los que opera el punto de contacto, utilizando [ISO639-1] de dos letras (https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes), o extendido [BCP47 language tags](http://www.w3.org/International/articles/language-tags/). Se recomienda el uso del c\u00f3digo de dos letras en min\u00fasculas de [ISO639-1](https://es.wikipedia.org/wiki/List_of_ISO_639-1_codes) a menos que exista una clara necesidad del usuario para distinguir el subtipo de idioma.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/additionalContactPoint/master/schema/index.html b/es/extensions/additionalContactPoint/master/schema/index.html
new file mode 100644
index 000000000..f68589d9e
--- /dev/null
+++ b/es/extensions/additionalContactPoint/master/schema/index.html
@@ -0,0 +1,282 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Puntos de contacto adicionales +
+ ++ Para proveer múltiples puntos de contacto de una organización, o para indicar los idiomas disponibles de un punto de contacto. Por ejemplo, puede usarse para indicar un punto de contacto para cada idioma. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Hay algunos casos en los que es importante enumerar varios puntos de contacto para una organización, especialmente en los casos en los que cada punto de contacto se ocupa únicamente de consultas en determinados idiomas.
+Esta extensión añade una matriz de additionalContactPoints al objeto organization e introduce una matriz de availableLanguage sobre los lenguajes disponibles a ContactPoint.
Cuando se utiliza esta extensión, los editores deben incluir un punto de contacto principal para el objeto contactPoint, ya que muchas aplicaciones no conocerán la lista additionalContactPoints. Sin embargo, si no se puede determinar un punto de contacto principal, todos los puntos de contacto pueden ser revelados en la lista additionalContactPoints.
Ejemplo
+{
+ "parties": [
+ {
+ "id": "GB-LAC-E09000003",
+ "roles": [
+ "procuringEntity"
+ ],
+ "identifier": {
+ "scheme": "GB-LAC",
+ "id": "E09000003",
+ "legalName": "AnyTown Council"
+ },
+ "name": "AnyTown Council",
+ "address": {
+ "streetAddress": "4, North London Business Park, Oakleigh Rd S",
+ "locality": "London",
+ "region": "London",
+ "postalCode": "N11 1NP",
+ "countryName": "United Kingdom"
+ },
+ "contactPoint": {
+ "name": "Procurement Team",
+ "email": "procurement-team@example.com",
+ "telephone": "01234 345 346",
+ "availableLanguage": [
+ "en"
+ ]
+ },
+ "additionalContactPoints": [
+ {
+ "name": "Procurement Team (International Enquiries)",
+ "email": "procurement-team-international@example.com",
+ "telephone": "01234 345 346 Extension 123",
+ "availableLanguage": [
+ "es",
+ "fr",
+ "de"
+ ]
+ }
+ ]
+ }
+ ]
+}
+Notas de modelado
+availableLanguage es singular, aunque es una lista, para alinearse con Schema.org.
Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-06-04
+-
+
- Revisar las palabras normativas y no-normativas +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-03-20
+-
+
- Colocar
"uniqueItems": trueen los campos de la matriz.
+
2018-12-21
+-
+
- Colocar
wholeListMergeenOrganization.additionalContactPoints.
+ - Aclarar el uso de códigos de idioma en
ContactPoint.availableLanguage
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/amendment_rationale_classifications/index.html b/es/extensions/amendment_rationale_classifications/index.html
new file mode 100644
index 000000000..dfe03727d
--- /dev/null
+++ b/es/extensions/amendment_rationale_classifications/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Puntos de contacto adicionales +
+ ++ Para proveer múltiples puntos de contacto de una organización, o para indicar los idiomas disponibles de un punto de contacto. Por ejemplo, puede usarse para indicar un punto de contacto para cada idioma. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ additionalContactPoints
+
+ |
+ + Puntos adicionales de contacto + | +
+ Una lista de puntos de contacto adicionales puede consultarse para obtener información. Los puntos de contacto adicionales deben listar en su nombre los idiomas en los que operan y como datos estructurados en el campo availableLanguage. + + |
+ + array of ContactPoint objects + | +
+ ContactPoint +
+ +
+ The extension defines these fields in the ContactPoint object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ availableLanguage
+
+ |
+ + Lenguajes disponibles + | +
+ Los idiomas en los que opera el punto de contacto, utilizando [ISO639-1] de dos letras (https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes), o extendido BCP47 language tags. Se recomienda el uso del código de dos letras en minúsculas de ISO639-1 a menos que exista una clara necesidad del usuario para distinguir el subtipo de idioma. + + |
+ + array of strings + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/amendment_rationale_classifications/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/amendment_rationale_classifications/master/extension.json b/es/extensions/amendment_rationale_classifications/master/extension.json
new file mode 100644
index 000000000..1a850c46f
--- /dev/null
+++ b/es/extensions/amendment_rationale_classifications/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Amendment rationale classifications",
+ "es": "Amendment rationale classifications"
+ },
+ "description": {
+ "en": "Adds a field to the amendment object to classify the rationale for the amendment.",
+ "es": "Adds a field to the amendment object to classify the rationale for the amendment."
+ },
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting-extensions/ocds_amendment_rationale_classifications_extension"
+ },
+ "codelists": [
+ "+itemClassificationScheme.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "compatibility": [
+ "1.1"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/amendment_rationale_classifications/master/index.html b/es/extensions/amendment_rationale_classifications/master/index.html
new file mode 100644
index 000000000..fbe9c4673
--- /dev/null
+++ b/es/extensions/amendment_rationale_classifications/master/index.html
@@ -0,0 +1,295 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Amendment rationale classifications +
+ ++ Adds a field to the amendment object to classify the rationale for the amendment. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ eu-change-corrig-justification
+
+ |
+ + EU modification justification + | +
+ The main reasons for modifying a contract within the domain of public procurement according to the legislation of the European Parliament. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/amendment_rationale_classifications/master/release-schema.json b/es/extensions/amendment_rationale_classifications/master/release-schema.json
new file mode 100644
index 000000000..eda5881c9
--- /dev/null
+++ b/es/extensions/amendment_rationale_classifications/master/release-schema.json
@@ -0,0 +1,19 @@
+{
+ "definitions": {
+ "Amendment": {
+ "properties": {
+ "rationaleClassifications": {
+ "title": "Rationale classifications",
+ "description": "The classifications of the rationale.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/amendment_rationale_classifications/master/schema/index.html b/es/extensions/amendment_rationale_classifications/master/schema/index.html
new file mode 100644
index 000000000..48c2962df
--- /dev/null
+++ b/es/extensions/amendment_rationale_classifications/master/schema/index.html
@@ -0,0 +1,236 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Amendment rationale classifications +
+ ++ Adds a field to the amendment object to classify the rationale for the amendment. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a field to the amendment object to classify its rationale.
+Legal context
+In the European Union, this extension's fields correspond to eForms BT-140 (Change Reason Code) and BT-200 (Modification Reason Code). For correspondences to eForms fields, see OCDS for eForms.
+Example
+{
+ "tender": {
+ "id": "1",
+ "amendments": [
+ {
+ "rationaleClassifications": [
+ {
+ "id": "update-add",
+ "description": "Information updated",
+ "scheme": "eu-change-corrig-justification"
+ }
+ ]
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/awardCriteria/index.html b/es/extensions/awardCriteria/index.html
new file mode 100644
index 000000000..0ccd1f5b6
--- /dev/null
+++ b/es/extensions/awardCriteria/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Amendment rationale classifications +
+ ++ Adds a field to the amendment object to classify the rationale for the amendment. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Amendment +
+ +
+ The extension defines these fields in the Amendment object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ rationaleClassifications
+
+ |
+ + Rationale classifications + | +
+ The classifications of the rationale. + + |
+ + array of Classification objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/awardCriteria/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/awardCriteria/master/extension.json b/es/extensions/awardCriteria/master/extension.json
new file mode 100644
index 000000000..951f22f14
--- /dev/null
+++ b/es/extensions/awardCriteria/master/extension.json
@@ -0,0 +1,32 @@
+{
+ "name": {
+ "en": "Award criteria breakdown",
+ "es": "Desglose de los criterios de adjudicaci\u00f3n"
+ },
+ "description": {
+ "en": "Adds an award criteria array to the lot object, to break down award criteria by price, cost and quality.",
+ "es": "Agrega una matriz de criterios de adjudicaci\u00f3n al objeto lote, para desglosar los criterios de adjudicaci\u00f3n por precio, costo y calidad."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/awardCriteria/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "awardCriterionType.csv",
+ "awardCriterionFixed.csv",
+ "criterionWeight.csv",
+ "criterionThreshold.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/es/extensions/awardCriteria/master/index.html b/es/extensions/awardCriteria/master/index.html
new file mode 100644
index 000000000..b298763d7
--- /dev/null
+++ b/es/extensions/awardCriteria/master/index.html
@@ -0,0 +1,437 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Desglose de los criterios de adjudicación +
+ ++ Agrega una matriz de criterios de adjudicación al objeto lote, para desglosar los criterios de adjudicación por precio, costo y calidad. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ awardCriterionFixed.csv +
+ +
+ You can download the awardCriterionFixed.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ total
+
+ |
+ + Fixed (total) + | +
+ The number is the fixed price or fixed cost for the bid. For example: "The price of a bid must be $100,000." + + |
+
+
+ unit
+
+ |
+ + Fixed (per unit) + | +
+ The number is the fixed price or fixed cost for a unit. For example: "The price of each widget must be $100." + + |
+
+ awardCriterionType.csv +
+ +
+ You can download the awardCriterionType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ price
+
+ |
+ + Price + | +
+ The criterion concerns the acquisition price of the bid. + + |
+
+
+ cost
+
+ |
+ + Cost + | +
+ The criterion concerns any other non-price monetary attribute of the bid. + + |
+
+
+ quality
+
+ |
+ + Quality + | +
+ The criterion concerns a non-price, non-cost attribute of the bid. + + |
+
+ criterionThreshold.csv +
+ +
+ You can download the criterionThreshold.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ minimumScore
+
+ |
+ + Minimum score + | +
+ The number is a minimum score that bids or requests to participate need to receive for the criterion. For example: "A bid must receive 20 points or more for criterion X." + + |
+
+
+ maximumBids
+
+ |
+ + Maximum number of passing bids + | +
+ The number is the maximum number of bids or requests to participate that can pass the criterion. For example: "A bid must receive one of the highest 3 scores for criterion X." + + |
+
+ criterionWeight.csv +
+ +
+ You can download the criterionWeight.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ percentageExact
+
+ |
+ + Weight (percentage, exact) + | +
+ The number is an exact percentage. The numbers must add up to 100. + + |
+
+
+ percentageRangeMiddle
+
+ |
+ + Weight (percentage, middle of a range) + | +
+ The weighting is expressed as a range of percentages. The sum of the minima must be less than or equal to 100. The sum of the maxima must be equal to or greater than 100. + + |
+
+
+ decimalExact
+
+ |
+ + Weight (decimal, exact) + | +
+ The number is an exact finite decimal proper fraction. The numbers must add up to 1. + + |
+
+
+ decimalRangeMiddle
+
+ |
+ + Weight (decimal, middle of a range) + | +
+ The weighting is expressed as a range of finite decimal proper fractions. The sum of the minima must be less than or equal to 1. The sum of the maxima must be equal to or greater than 1. + + |
+
+
+ pointsExact
+
+ |
+ + Weight (points, exact) + | +
+ The weighting is expressed as an exact number of points. + + |
+
+
+ pointsRangeMiddle
+
+ |
+ + Weight (points, middle of a range) + | +
+ The weighting is expressed as a range of numbers of points. + + |
+
+
+ order
+
+ |
+ + Order of importance + | +
+ The number indicates an order of importance. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/awardCriteria/master/release-schema.json b/es/extensions/awardCriteria/master/release-schema.json
new file mode 100644
index 000000000..bd0e187b0
--- /dev/null
+++ b/es/extensions/awardCriteria/master/release-schema.json
@@ -0,0 +1,173 @@
+{
+ "definitions": {
+ "Lot": {
+ "properties": {
+ "awardCriteria": {
+ "title": "Criterio de adjudicaci\u00f3n",
+ "description": "Informaci\u00f3n acerca del criterio de adjudicaci\u00f3n del lote.",
+ "$ref": "#/definitions/AwardCriteria"
+ }
+ }
+ },
+ "LotGroup": {
+ "properties": {
+ "awardCriteria": {
+ "title": "Criterio de adjudicaci\u00f3n",
+ "description": "Informaci\u00f3n acerca del criterio de adjudicaci\u00f3n del lote.",
+ "$ref": "#/definitions/AwardCriteria"
+ }
+ }
+ },
+ "AwardCriteria": {
+ "title": "Criterio de adjudicaci\u00f3n",
+ "description": "Informaci\u00f3n sobre el criterio de adjudicaci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "weightingDescription": {
+ "title": "Descripci\u00f3n de ponderaci\u00f3n compleja",
+ "description": "Cuando la ponderaci\u00f3n no se puede expresar por criterio, la ecuaci\u00f3n matem\u00e1tica (u otra descripci\u00f3n) que expresa la ponderaci\u00f3n compleja (por ejemplo, no lineal).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "orderRationale": {
+ "title": "Justificaci\u00f3n para el orden de importancia",
+ "description": "La justificaci\u00f3n para indicar \u00fanicamente el orden de importancia de los criterios de adjudicaci\u00f3n, no su ponderaci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "criteria": {
+ "title": "Criterio de adjudicaci\u00f3n",
+ "description": "El criterio de adjudicaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/AwardCriterion"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "AwardCriterion": {
+ "title": "Criterio de adjudicaci\u00f3n",
+ "description": "Informaci\u00f3n sobre el criterio de adjudicaci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Tipo",
+ "description": "El aspecto de la oferta al que se refiere el criterio.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "awardCriterionType.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "name": {
+ "title": "Nombre",
+ "description": "El nombre del criterio.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "La descripci\u00f3n del criterio.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "numbers": {
+ "title": "N\u00fameros",
+ "description": "N\u00fameros ligados al criterio.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/CriterionNumber"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "CriterionNumber": {
+ "title": "Criterion number",
+ "description": "Information about a number linked to a criterion.",
+ "type": "object",
+ "properties": {
+ "number": {
+ "title": "N\u00famero",
+ "description": "El n\u00famero.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "weight": {
+ "title": "Peso",
+ "description": "Si el n\u00famero es un tipo de ponderaci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "criterionWeight.csv",
+ "openCodelist": false,
+ "enum": [
+ "percentageExact",
+ "percentageRangeMiddle",
+ "decimalExact",
+ "decimalRangeMiddle",
+ "pointsExact",
+ "pointsRangeMiddle",
+ "order",
+ null
+ ]
+ },
+ "fixed": {
+ "title": "Fijado",
+ "description": "Si el n\u00famero es un valor fijo.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "awardCriterionFixed.csv",
+ "openCodelist": false,
+ "enum": [
+ "total",
+ "unit",
+ null
+ ]
+ },
+ "threshold": {
+ "title": "Umbral",
+ "description": "Si el n\u00famero es un tipo de umbral.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "criterionThreshold.csv",
+ "openCodelist": false,
+ "enum": [
+ "minimumScore",
+ "maximumBids",
+ null
+ ]
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/awardCriteria/master/schema/index.html b/es/extensions/awardCriteria/master/schema/index.html
new file mode 100644
index 000000000..ad131ff88
--- /dev/null
+++ b/es/extensions/awardCriteria/master/schema/index.html
@@ -0,0 +1,576 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Desglose de los criterios de adjudicación +
+ ++ Agrega una matriz de criterios de adjudicación al objeto lote, para desglosar los criterios de adjudicación por precio, costo y calidad. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an award criteria array to the Lot and LotGroup objects, to break down award criteria by price, cost and quality.
Contexto legal
+In the European Union, this extension's fields correspond to eForms BG-707 (Award Criteria).For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Directiva 2014/24/EU Artículo 67(5) describe ponderaciones y órdenes de importancia.
+Ejemplos
+Lots
+Peso
+The award criteria for the lot are 50% service quality and 50% price.
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "awardCriteria": {
+ "criteria": [
+ {
+ "type": "quality",
+ "name": "Service quality",
+ "numbers": [
+ {
+ "number": 50,
+ "weight": "percentageExact"
+ }
+ ]
+ },
+ {
+ "type": "price",
+ "name": "Price",
+ "numbers": [
+ {
+ "number": 50,
+ "weight": "percentageExact"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Fijado
+The price of the lot is fixed at $100,000, such that tenderers compete on quality only.
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "awardCriteria": {
+ "criteria": [
+ {
+ "type": "price",
+ "name": "Fixed price",
+ "numbers": [
+ {
+ "number": 100000,
+ "fixed": "total"
+ },
+ {
+ "number": 0,
+ "weight": "decimalExact"
+ }
+ ]
+ },
+ {
+ "type": "quality",
+ "name": "Service quality",
+ "numbers": [
+ {
+ "number": 1,
+ "weight": "decimalExact"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Lot group
+The award criteria for the lot group is 100% price.
+{
+ "tender": {
+ "lotGroups": [
+ {
+ "id": "1",
+ "awardCriteria": {
+ "criteria": [
+ {
+ "type": "price",
+ "name": "Price",
+ "numbers": [
+ {
+ "number": 100,
+ "weight": "percentageExact"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2022-04-25
+-
+
- Add requests to participate to
criterionThreshold.csvcode descriptions.
+ - Generalize AwardCriterionNumber to
CriterionNumberfor reuse in other extensions.
+
2022-02-27
+-
+
- Add
LotGroup.awardCriteriafield.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Este modelo fue discutido en https://github.com/eForms/eForms/issues/119, https://github.com/eprocurementontology/eprocurementontology/issues/157 y https://github.com/eprocurementontology/eprocurementontology/issues/203. Esta extensión fue discutida originalmente como parte de OCDS para el perfil de la UE, en pull requests y en https://github.com/open-contracting/standard/issues/443.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/beneficialOwners/index.html b/es/extensions/beneficialOwners/index.html
new file mode 100644
index 000000000..3e6692127
--- /dev/null
+++ b/es/extensions/beneficialOwners/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Desglose de los criterios de adjudicación +
+ ++ Agrega una matriz de criterios de adjudicación al objeto lote, para desglosar los criterios de adjudicación por precio, costo y calidad. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ awardCriteria
+
+ |
+ + Criterio de adjudicación + | +
+ Información acerca del criterio de adjudicación del lote. + + |
+ + AwardCriteria object + | +
+ LotGroup +
+ +
+ The extension defines these fields in the LotGroup object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ awardCriteria
+
+ |
+ + Criterio de adjudicación + | +
+ Información acerca del criterio de adjudicación del lote. + + |
+ + AwardCriteria object + | +
+ AwardCriteria +
+ +
+ The extension defines a new AwardCriteria object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ weightingDescription
+
+ |
+ + Descripción de ponderación compleja + | +
+ Cuando la ponderación no se puede expresar por criterio, la ecuación matemática (u otra descripción) que expresa la ponderación compleja (por ejemplo, no lineal). + + |
+ + string + | +
+
+ orderRationale
+
+ |
+ + Justificación para el orden de importancia + | +
+ La justificación para indicar únicamente el orden de importancia de los criterios de adjudicación, no su ponderación. + + |
+ + string + | +
+
+ criteria
+
+ |
+ + Criterio de adjudicación + | +
+ El criterio de adjudicación. + + |
+ + array of AwardCriterion objects + | +
+ AwardCriterion +
+ +
+ The extension defines a new AwardCriterion object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Tipo + | +
+ El aspecto de la oferta al que se refiere el criterio. + + |
+ + string from open awardCriterionType codelist + | +
+
+ name
+
+ |
+ + Nombre + | +
+ El nombre del criterio. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ La descripción del criterio. + + |
+ + string + | +
+
+ numbers
+
+ |
+ + Números + | +
+ Números ligados al criterio. + + |
+ + array of CriterionNumber objects + | +
+ CriterionNumber +
+ +
+ The extension defines a new CriterionNumber object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ number
+
+ |
+ + Número + | +
+ El número. + + |
+ + number + | +
+
+ weight
+
+ |
+ + Peso + | +
+ Si el número es un tipo de ponderación. + + |
+ + string from closed criterionWeight codelist + | +
+
+ fixed
+
+ |
+ + Fijado + | +
+ Si el número es un valor fijo. + + |
+ + string from closed awardCriterionFixed codelist + | +
+
+ threshold
+
+ |
+ + Umbral + | +
+ Si el número es un tipo de umbral. + + |
+ + string from closed criterionThreshold codelist + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/beneficialOwners/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/beneficialOwners/master/extension.json b/es/extensions/beneficialOwners/master/extension.json
new file mode 100644
index 000000000..ea20eb9c8
--- /dev/null
+++ b/es/extensions/beneficialOwners/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Beneficial owners",
+ "es": "Beneficiarios finales"
+ },
+ "description": {
+ "en": "Adds a beneficialOwners array to the organization object to indicate the beneficial owners of an organization.",
+ "es": "Agregue una lista de beneficialOwners al objeto organizaci\u00f3n para indicar los beneficiarios finales de una organizaci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/beneficialOwners/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "country.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/beneficialOwners/master/index.html b/es/extensions/beneficialOwners/master/index.html
new file mode 100644
index 000000000..a2351be09
--- /dev/null
+++ b/es/extensions/beneficialOwners/master/index.html
@@ -0,0 +1,378 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Beneficiarios finales +
+ ++ Agregue una lista de beneficialOwners al objeto organización para indicar los beneficiarios finales de una organización. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ country.csv +
+ +
+ You can download the country.csv file in English.
+
| + Code + | ++ Title + | +
|---|---|
+
+ AD
+
+ |
+ + Andorra + | +
+
+ AE
+
+ |
+ + United Arab Emirates + | +
+
+ AF
+
+ |
+ + Afghanistan + | +
+
+ AG
+
+ |
+ + Antigua and Barbuda + | +
+
+ AI
+
+ |
+ + Anguilla + | +
+
+ AL
+
+ |
+ + Albania + | +
+
+ AM
+
+ |
+ + Armenia + | +
+
+ AO
+
+ |
+ + Angola + | +
+
+ AQ
+
+ |
+ + Antarctica + | +
+
+ AR
+
+ |
+ + Argentina + | +
+
+ AS
+
+ |
+ + American Samoa + | +
+
+ AT
+
+ |
+ + Austria + | +
+
+ AU
+
+ |
+ + Australia + | +
+
+ AW
+
+ |
+ + Aruba + | +
+
+ AX
+
+ |
+ + Åland Islands + | +
+
+ AZ
+
+ |
+ + Azerbaijan + | +
+
+ BA
+
+ |
+ + Bosnia and Herzegovina + | +
+
+ BB
+
+ |
+ + Barbados + | +
+
+ BD
+
+ |
+ + Bangladesh + | +
+
+ BE
+
+ |
+ + Belgium + | +
+
+ BF
+
+ |
+ + Burkina Faso + | +
+
+ BG
+
+ |
+ + Bulgaria + | +
+
+ BH
+
+ |
+ + Bahrain + | +
+
+ BI
+
+ |
+ + Burundi + | +
+
+ BJ
+
+ |
+ + Benin + | +
+
+ BL
+
+ |
+ + Saint Barthélemy + | +
+
+ BM
+
+ |
+ + Bermuda + | +
+
+ BN
+
+ |
+ + Brunei Darussalam + | +
+
+ BO
+
+ |
+ + Bolivia (Plurinational State of) + | +
+
+ BQ
+
+ |
+ + Bonaire, Sint Eustatius and Saba + | +
+
+ BR
+
+ |
+ + Brazil + | +
+
+ BS
+
+ |
+ + Bahamas + | +
+
+ BT
+
+ |
+ + Bhutan + | +
+
+ BV
+
+ |
+ + Bouvet Island + | +
+
+ BW
+
+ |
+ + Botswana + | +
+
+ BY
+
+ |
+ + Belarus + | +
+
+ BZ
+
+ |
+ + Belize + | +
+
+ CA
+
+ |
+ + Canada + | +
+
+ CC
+
+ |
+ + Cocos (Keeling) Islands + | +
+
+ CD
+
+ |
+ + Congo (the Democratic Republic of the) + | +
+
+ CF
+
+ |
+ + Central African Republic + | +
+
+ CG
+
+ |
+ + Congo + | +
+
+ CH
+
+ |
+ + Switzerland + | +
+
+ CI
+
+ |
+ + Côte d'Ivoire + | +
+
+ CK
+
+ |
+ + Cook Islands + | +
+
+ CL
+
+ |
+ + Chile + | +
+
+ CM
+
+ |
+ + Cameroon + | +
+
+ CN
+
+ |
+ + China + | +
+
+ CO
+
+ |
+ + Colombia + | +
+
+ CR
+
+ |
+ + Costa Rica + | +
+
+ CU
+
+ |
+ + Cuba + | +
+
+ CV
+
+ |
+ + Cabo Verde + | +
+
+ CW
+
+ |
+ + Curaçao + | +
+
+ CX
+
+ |
+ + Christmas Island + | +
+
+ CY
+
+ |
+ + Cyprus + | +
+
+ CZ
+
+ |
+ + Czechia + | +
+
+ DE
+
+ |
+ + Germany + | +
+
+ DJ
+
+ |
+ + Djibouti + | +
+
+ DK
+
+ |
+ + Denmark + | +
+
+ DM
+
+ |
+ + Dominica + | +
+
+ DO
+
+ |
+ + Dominican Republic + | +
+
+ DZ
+
+ |
+ + Algeria + | +
+
+ EC
+
+ |
+ + Ecuador + | +
+
+ EE
+
+ |
+ + Estonia + | +
+
+ EG
+
+ |
+ + Egypt + | +
+
+ EH
+
+ |
+ + Western Sahara + | +
+
+ ER
+
+ |
+ + Eritrea + | +
+
+ ES
+
+ |
+ + Spain + | +
+
+ ET
+
+ |
+ + Ethiopia + | +
+
+ FI
+
+ |
+ + Finland + | +
+
+ FJ
+
+ |
+ + Fiji + | +
+
+ FK
+
+ |
+ + Falkland Islands [Malvinas] + | +
+
+ FM
+
+ |
+ + Micronesia (Federated States of) + | +
+
+ FO
+
+ |
+ + Faroe Islands + | +
+
+ FR
+
+ |
+ + France + | +
+
+ GA
+
+ |
+ + Gabon + | +
+
+ GB
+
+ |
+ + United Kingdom of Great Britain and Northern Ireland + | +
+
+ GD
+
+ |
+ + Grenada + | +
+
+ GE
+
+ |
+ + Georgia + | +
+
+ GF
+
+ |
+ + French Guiana + | +
+
+ GG
+
+ |
+ + Guernsey + | +
+
+ GH
+
+ |
+ + Ghana + | +
+
+ GI
+
+ |
+ + Gibraltar + | +
+
+ GL
+
+ |
+ + Greenland + | +
+
+ GM
+
+ |
+ + Gambia + | +
+
+ GN
+
+ |
+ + Guinea + | +
+
+ GP
+
+ |
+ + Guadeloupe + | +
+
+ GQ
+
+ |
+ + Equatorial Guinea + | +
+
+ GR
+
+ |
+ + Greece + | +
+
+ GS
+
+ |
+ + South Georgia and the South Sandwich Islands + | +
+
+ GT
+
+ |
+ + Guatemala + | +
+
+ GU
+
+ |
+ + Guam + | +
+
+ GW
+
+ |
+ + Guinea-Bissau + | +
+
+ GY
+
+ |
+ + Guyana + | +
+
+ HK
+
+ |
+ + Hong Kong + | +
+
+ HM
+
+ |
+ + Heard Island and McDonald Islands + | +
+
+ HN
+
+ |
+ + Honduras + | +
+
+ HR
+
+ |
+ + Croatia + | +
+
+ HT
+
+ |
+ + Haiti + | +
+
+ HU
+
+ |
+ + Hungary + | +
+
+ ID
+
+ |
+ + Indonesia + | +
+
+ IE
+
+ |
+ + Ireland + | +
+
+ IL
+
+ |
+ + Israel + | +
+
+ IM
+
+ |
+ + Isle of Man + | +
+
+ IN
+
+ |
+ + India + | +
+
+ IO
+
+ |
+ + British Indian Ocean Territory + | +
+
+ IQ
+
+ |
+ + Iraq + | +
+
+ IR
+
+ |
+ + Iran (Islamic Republic of) + | +
+
+ IS
+
+ |
+ + Iceland + | +
+
+ IT
+
+ |
+ + Italy + | +
+
+ JE
+
+ |
+ + Jersey + | +
+
+ JM
+
+ |
+ + Jamaica + | +
+
+ JO
+
+ |
+ + Jordan + | +
+
+ JP
+
+ |
+ + Japan + | +
+
+ KE
+
+ |
+ + Kenya + | +
+
+ KG
+
+ |
+ + Kyrgyzstan + | +
+
+ KH
+
+ |
+ + Cambodia + | +
+
+ KI
+
+ |
+ + Kiribati + | +
+
+ KM
+
+ |
+ + Comoros + | +
+
+ KN
+
+ |
+ + Saint Kitts and Nevis + | +
+
+ KP
+
+ |
+ + Korea (the Democratic People's Republic of) + | +
+
+ KR
+
+ |
+ + Korea (the Republic of) + | +
+
+ KW
+
+ |
+ + Kuwait + | +
+
+ KY
+
+ |
+ + Cayman Islands + | +
+
+ KZ
+
+ |
+ + Kazakhstan + | +
+
+ LA
+
+ |
+ + Lao People's Democratic Republic + | +
+
+ LB
+
+ |
+ + Lebanon + | +
+
+ LC
+
+ |
+ + Saint Lucia + | +
+
+ LI
+
+ |
+ + Liechtenstein + | +
+
+ LK
+
+ |
+ + Sri Lanka + | +
+
+ LR
+
+ |
+ + Liberia + | +
+
+ LS
+
+ |
+ + Lesotho + | +
+
+ LT
+
+ |
+ + Lithuania + | +
+
+ LU
+
+ |
+ + Luxembourg + | +
+
+ LV
+
+ |
+ + Latvia + | +
+
+ LY
+
+ |
+ + Libya + | +
+
+ MA
+
+ |
+ + Morocco + | +
+
+ MC
+
+ |
+ + Monaco + | +
+
+ MD
+
+ |
+ + Moldova (the Republic of) + | +
+
+ ME
+
+ |
+ + Montenegro + | +
+
+ MF
+
+ |
+ + Saint Martin (French part) + | +
+
+ MG
+
+ |
+ + Madagascar + | +
+
+ MH
+
+ |
+ + Marshall Islands + | +
+
+ MK
+
+ |
+ + North Macedonia + | +
+
+ ML
+
+ |
+ + Mali + | +
+
+ MM
+
+ |
+ + Myanmar + | +
+
+ MN
+
+ |
+ + Mongolia + | +
+
+ MO
+
+ |
+ + Macao + | +
+
+ MP
+
+ |
+ + Northern Mariana Islands + | +
+
+ MQ
+
+ |
+ + Martinique + | +
+
+ MR
+
+ |
+ + Mauritania + | +
+
+ MS
+
+ |
+ + Montserrat + | +
+
+ MT
+
+ |
+ + Malta + | +
+
+ MU
+
+ |
+ + Mauritius + | +
+
+ MV
+
+ |
+ + Maldives + | +
+
+ MW
+
+ |
+ + Malawi + | +
+
+ MX
+
+ |
+ + Mexico + | +
+
+ MY
+
+ |
+ + Malaysia + | +
+
+ MZ
+
+ |
+ + Mozambique + | +
+
+ NA
+
+ |
+ + Namibia + | +
+
+ NC
+
+ |
+ + New Caledonia + | +
+
+ NE
+
+ |
+ + Niger + | +
+
+ NF
+
+ |
+ + Norfolk Island + | +
+
+ NG
+
+ |
+ + Nigeria + | +
+
+ NI
+
+ |
+ + Nicaragua + | +
+
+ NL
+
+ |
+ + Netherlands + | +
+
+ NO
+
+ |
+ + Norway + | +
+
+ NP
+
+ |
+ + Nepal + | +
+
+ NR
+
+ |
+ + Nauru + | +
+
+ NU
+
+ |
+ + Niue + | +
+
+ NZ
+
+ |
+ + New Zealand + | +
+
+ OM
+
+ |
+ + Oman + | +
+
+ PA
+
+ |
+ + Panama + | +
+
+ PE
+
+ |
+ + Peru + | +
+
+ PF
+
+ |
+ + French Polynesia + | +
+
+ PG
+
+ |
+ + Papua New Guinea + | +
+
+ PH
+
+ |
+ + Philippines + | +
+
+ PK
+
+ |
+ + Pakistan + | +
+
+ PL
+
+ |
+ + Poland + | +
+
+ PM
+
+ |
+ + Saint Pierre and Miquelon + | +
+
+ PN
+
+ |
+ + Pitcairn + | +
+
+ PR
+
+ |
+ + Puerto Rico + | +
+
+ PS
+
+ |
+ + Palestine, State of + | +
+
+ PT
+
+ |
+ + Portugal + | +
+
+ PW
+
+ |
+ + Palau + | +
+
+ PY
+
+ |
+ + Paraguay + | +
+
+ QA
+
+ |
+ + Qatar + | +
+
+ RE
+
+ |
+ + Réunion + | +
+
+ RO
+
+ |
+ + Romania + | +
+
+ RS
+
+ |
+ + Serbia + | +
+
+ RU
+
+ |
+ + Russian Federation + | +
+
+ RW
+
+ |
+ + Rwanda + | +
+
+ SA
+
+ |
+ + Saudi Arabia + | +
+
+ SB
+
+ |
+ + Solomon Islands + | +
+
+ SC
+
+ |
+ + Seychelles + | +
+
+ SD
+
+ |
+ + Sudan + | +
+
+ SE
+
+ |
+ + Sweden + | +
+
+ SG
+
+ |
+ + Singapore + | +
+
+ SH
+
+ |
+ + Saint Helena, Ascension and Tristan da Cunha + | +
+
+ SI
+
+ |
+ + Slovenia + | +
+
+ SJ
+
+ |
+ + Svalbard and Jan Mayen + | +
+
+ SK
+
+ |
+ + Slovakia + | +
+
+ SL
+
+ |
+ + Sierra Leone + | +
+
+ SM
+
+ |
+ + San Marino + | +
+
+ SN
+
+ |
+ + Senegal + | +
+
+ SO
+
+ |
+ + Somalia + | +
+
+ SR
+
+ |
+ + Suriname + | +
+
+ SS
+
+ |
+ + South Sudan + | +
+
+ ST
+
+ |
+ + Sao Tome and Principe + | +
+
+ SV
+
+ |
+ + El Salvador + | +
+
+ SX
+
+ |
+ + Sint Maarten (Dutch part) + | +
+
+ SY
+
+ |
+ + Syrian Arab Republic + | +
+
+ SZ
+
+ |
+ + Eswatini + | +
+
+ TC
+
+ |
+ + Turks and Caicos Islands + | +
+
+ TD
+
+ |
+ + Chad + | +
+
+ TF
+
+ |
+ + French Southern Territories + | +
+
+ TG
+
+ |
+ + Togo + | +
+
+ TH
+
+ |
+ + Thailand + | +
+
+ TJ
+
+ |
+ + Tajikistan + | +
+
+ TK
+
+ |
+ + Tokelau + | +
+
+ TL
+
+ |
+ + Timor-Leste + | +
+
+ TM
+
+ |
+ + Turkmenistan + | +
+
+ TN
+
+ |
+ + Tunisia + | +
+
+ TO
+
+ |
+ + Tonga + | +
+
+ TR
+
+ |
+ + Turkey + | +
+
+ TT
+
+ |
+ + Trinidad and Tobago + | +
+
+ TV
+
+ |
+ + Tuvalu + | +
+
+ TW
+
+ |
+ + Taiwan (Province of China) + | +
+
+ TZ
+
+ |
+ + Tanzania, the United Republic of + | +
+
+ UA
+
+ |
+ + Ukraine + | +
+
+ UG
+
+ |
+ + Uganda + | +
+
+ UM
+
+ |
+ + United States Minor Outlying Islands + | +
+
+ US
+
+ |
+ + United States of America + | +
+
+ UY
+
+ |
+ + Uruguay + | +
+
+ UZ
+
+ |
+ + Uzbekistan + | +
+
+ VA
+
+ |
+ + Holy See + | +
+
+ VC
+
+ |
+ + Saint Vincent and the Grenadines + | +
+
+ VE
+
+ |
+ + Venezuela (Bolivarian Republic of) + | +
+
+ VG
+
+ |
+ + Virgin Islands (British) + | +
+
+ VI
+
+ |
+ + Virgin Islands (U.S.) + | +
+
+ VN
+
+ |
+ + Viet Nam + | +
+
+ VU
+
+ |
+ + Vanuatu + | +
+
+ WF
+
+ |
+ + Wallis and Futuna + | +
+
+ WS
+
+ |
+ + Samoa + | +
+
+ XK
+
+ |
+ + Kosovo + | +
+
+ YE
+
+ |
+ + Yemen + | +
+
+ YT
+
+ |
+ + Mayotte + | +
+
+ ZA
+
+ |
+ + South Africa + | +
+
+ ZM
+
+ |
+ + Zambia + | +
+
+ ZW
+
+ |
+ + Zimbabwe + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/beneficialOwners/master/release-schema.json b/es/extensions/beneficialOwners/master/release-schema.json
new file mode 100644
index 000000000..90a8119a5
--- /dev/null
+++ b/es/extensions/beneficialOwners/master/release-schema.json
@@ -0,0 +1,361 @@
+{
+ "definitions": {
+ "Organization": {
+ "properties": {
+ "beneficialOwners": {
+ "title": "Beneficiarios finales",
+ "description": "Los beneficiarios finales de la organizaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Person"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "details": {
+ "properties": {
+ "listedOnRegulatedMarket": {
+ "title": "Listed on regulated market",
+ "description": "Whether the organization is listed on a regulated market (e.g. a stock exchange) that ensures adequate transparency in line with anti-money laundering legislation.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+ },
+ "Person": {
+ "title": "Persona",
+ "description": "Una persona f\u00edsica.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID ",
+ "description": "Un identificador local para la persona.",
+ "type": "string",
+ "minLength": 1
+ },
+ "name": {
+ "title": "Nombre",
+ "description": "El nombre completo de la persona.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "identifier": {
+ "title": "Identificador",
+ "description": "Un identificador oficial de la persona. El esquema debe seguir el patr\u00f3n {JURISDICCI\u00d3N}-{TIPO}, donde JURISDICCI\u00d3N es un c\u00f3digo de pa\u00eds ISO 3166-1 alfa-3 de tres letras, y TIPO es uno de los siguientes: \"PASAPORTE\", \"TAXID\" o \"IDCARD\".",
+ "$ref": "#/definitions/Identifier"
+ },
+ "nationalities": {
+ "title": "Nationalities",
+ "description": "The nationalities of the person, from the closed country codelist.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "AD",
+ "AE",
+ "AF",
+ "AG",
+ "AI",
+ "AL",
+ "AM",
+ "AO",
+ "AQ",
+ "AR",
+ "AS",
+ "AT",
+ "AU",
+ "AW",
+ "AX",
+ "AZ",
+ "BA",
+ "BB",
+ "BD",
+ "BE",
+ "BF",
+ "BG",
+ "BH",
+ "BI",
+ "BJ",
+ "BL",
+ "BM",
+ "BN",
+ "BO",
+ "BQ",
+ "BR",
+ "BS",
+ "BT",
+ "BV",
+ "BW",
+ "BY",
+ "BZ",
+ "CA",
+ "CC",
+ "CD",
+ "CF",
+ "CG",
+ "CH",
+ "CI",
+ "CK",
+ "CL",
+ "CM",
+ "CN",
+ "CO",
+ "CR",
+ "CU",
+ "CV",
+ "CW",
+ "CX",
+ "CY",
+ "CZ",
+ "DE",
+ "DJ",
+ "DK",
+ "DM",
+ "DO",
+ "DZ",
+ "EC",
+ "EE",
+ "EG",
+ "EH",
+ "ER",
+ "ES",
+ "ET",
+ "FI",
+ "FJ",
+ "FK",
+ "FM",
+ "FO",
+ "FR",
+ "GA",
+ "GB",
+ "GD",
+ "GE",
+ "GF",
+ "GG",
+ "GH",
+ "GI",
+ "GL",
+ "GM",
+ "GN",
+ "GP",
+ "GQ",
+ "GR",
+ "GS",
+ "GT",
+ "GU",
+ "GW",
+ "GY",
+ "HK",
+ "HM",
+ "HN",
+ "HR",
+ "HT",
+ "HU",
+ "ID",
+ "IE",
+ "IL",
+ "IM",
+ "IN",
+ "IO",
+ "IQ",
+ "IR",
+ "IS",
+ "IT",
+ "JE",
+ "JM",
+ "JO",
+ "JP",
+ "KE",
+ "KG",
+ "KH",
+ "KI",
+ "KM",
+ "KN",
+ "KP",
+ "KR",
+ "KW",
+ "KY",
+ "KZ",
+ "LA",
+ "LB",
+ "LC",
+ "LI",
+ "LK",
+ "LR",
+ "LS",
+ "LT",
+ "LU",
+ "LV",
+ "LY",
+ "MA",
+ "MC",
+ "MD",
+ "ME",
+ "MF",
+ "MG",
+ "MH",
+ "MK",
+ "ML",
+ "MM",
+ "MN",
+ "MO",
+ "MP",
+ "MQ",
+ "MR",
+ "MS",
+ "MT",
+ "MU",
+ "MV",
+ "MW",
+ "MX",
+ "MY",
+ "MZ",
+ "NA",
+ "NC",
+ "NE",
+ "NF",
+ "NG",
+ "NI",
+ "NL",
+ "NO",
+ "NP",
+ "NR",
+ "NU",
+ "NZ",
+ "OM",
+ "PA",
+ "PE",
+ "PF",
+ "PG",
+ "PH",
+ "PK",
+ "PL",
+ "PM",
+ "PN",
+ "PR",
+ "PS",
+ "PT",
+ "PW",
+ "PY",
+ "QA",
+ "RE",
+ "RO",
+ "RS",
+ "RU",
+ "RW",
+ "SA",
+ "SB",
+ "SC",
+ "SD",
+ "SE",
+ "SG",
+ "SH",
+ "SI",
+ "SJ",
+ "SK",
+ "SL",
+ "SM",
+ "SN",
+ "SO",
+ "SR",
+ "SS",
+ "ST",
+ "SV",
+ "SX",
+ "SY",
+ "SZ",
+ "TC",
+ "TD",
+ "TF",
+ "TG",
+ "TH",
+ "TJ",
+ "TK",
+ "TL",
+ "TM",
+ "TN",
+ "TO",
+ "TR",
+ "TT",
+ "TV",
+ "TW",
+ "TZ",
+ "UA",
+ "UG",
+ "UM",
+ "US",
+ "UY",
+ "UZ",
+ "VA",
+ "VC",
+ "VE",
+ "VG",
+ "VI",
+ "VN",
+ "VU",
+ "WF",
+ "WS",
+ "XK",
+ "YE",
+ "YT",
+ "ZA",
+ "ZM",
+ "ZW"
+ ]
+ },
+ "codelist": "country.csv",
+ "openCodelist": false,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "address": {
+ "title": "Address",
+ "description": "The address of the person.",
+ "$ref": "#/definitions/Address"
+ },
+ "email": {
+ "title": "Email",
+ "description": "The e-mail address of the person.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "email",
+ "minLength": 1
+ },
+ "faxNumber": {
+ "title": "Fax number",
+ "description": "The fax number of the person. This must include the international dialing code.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "telephone": {
+ "title": "Telephone",
+ "description": "The telephone number of the person. This must include the international dialing code.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/beneficialOwners/master/schema/index.html b/es/extensions/beneficialOwners/master/schema/index.html
new file mode 100644
index 000000000..59cc50d5d
--- /dev/null
+++ b/es/extensions/beneficialOwners/master/schema/index.html
@@ -0,0 +1,442 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Beneficiarios finales +
+ ++ Agregue una lista de beneficialOwners al objeto organización para indicar los beneficiarios finales de una organización. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar una lista de beneficiarios finales al objeto organización para indicar los beneficiarios finales de una organización.
+If beneficial ownership (BO) information is collected via contracting processes, then this extension is appropriate: for example, if tenderers are obligated to disclose their beneficial owners within their bid submission. Similarly, to use this extension, the laws in your jurisdiction must permit the publication of personal identifiers.
+You can find the complete guidance on publishing personal identifiers in the Beneficial Ownership Data Standard documentation
+Por otro lado, si la información de beneficiarios finales se recoge en un registro central por otros medios, se recomienda publicar esa información como un conjunto de datos separados. El conjunto de datos de beneficiarios finales y el conjunto de datos OCDS deben identificar las organizaciones de la misma manera, para que los usuarios puedan cruzar los conjuntos de datos. El conjunto de datos de Beneficiarios Finales puede seguir el Estándar de Datos sobre Beneficiarios Finales.
+Ejemplo
+With nationality
+The beneficial owner's nationality is disclosed.
+{
+ "parties": [
+ {
+ "id": "AHL",
+ "name": "Alpha Holdings Ltd",
+ "beneficialOwners": [
+ {
+ "id": "1",
+ "name": "Juan Perez",
+ "identifier": {
+ "scheme": "PRY-IDCARD",
+ "id": "12345"
+ },
+ "nationalities": [
+ "PY"
+ ],
+ "address": {
+ "streetAddress": "Avenida Eusebio Ayala 1347",
+ "locality": "Asunción",
+ "region": "Gran Asunción",
+ "postalCode": "1001",
+ "countryName": "Paraguay"
+ },
+ "email": "jperez@example.com",
+ "faxNumber": "+595210000001",
+ "telephone": "+595210000000"
+ }
+ ]
+ }
+ ]
+}
+Without nationality
+The beneficial owner's nationality is not disclosed because the organization is listed on a regulated market (e.g. a stock exchange) that ensures adequate transparency in line with anti-money laundering legislation.
+{
+ "parties": [
+ {
+ "id": "AHL",
+ "name": "Alpha Holdings Ltd",
+ "beneficialOwners": [
+ {
+ "id": "1",
+ "name": "Juan Perez",
+ "identifier": {
+ "scheme": "PRY-IDCARD",
+ "id": "12345"
+ },
+ "address": {
+ "streetAddress": "Avenida Eusebio Ayala 1347",
+ "locality": "Asunción",
+ "region": "Gran Asunción",
+ "postalCode": "1001",
+ "countryName": "Paraguay"
+ },
+ "email": "jperez@example.com",
+ "faxNumber": "+595210000001",
+ "telephone": "+595210000000"
+ }
+ ],
+ "details": {
+ "listedOnRegulatedMarket": true
+ }
+ }
+ ]
+}
+Issues
+Reportar issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Changelog
+2023-08-04
+-
+
- Convert nationality field to
nationalitiesarray.
+
2023-06-07
+-
+
- Add
country.csvcodelist for nationality field.
+
2023-02-27
+-
+
- Add fields:
+
-
+
Person.address
+Person.email
+Person.faxNumber
+Person.telephone
+Organization.details.listedOnRegulatedMarket
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/bidOpening/index.html b/es/extensions/bidOpening/index.html
new file mode 100644
index 000000000..1baa75168
--- /dev/null
+++ b/es/extensions/bidOpening/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Beneficiarios finales +
+ ++ Agregue una lista de beneficialOwners al objeto organización para indicar los beneficiarios finales de una organización. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ beneficialOwners
+
+ |
+ + Beneficiarios finales + | +
+ Los beneficiarios finales de la organización. + + |
+ + array of Person objects + | +
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + Listed on regulated market + | +
+ Whether the organization is listed on a regulated market (e.g. a stock exchange) that ensures adequate transparency in line with anti-money laundering legislation. + + |
+ + boolean + | +
+ Person +
+ +
+ The extension defines a new Person object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ Un identificador local para la persona. + + |
+ + string + | +
+
+ name
+
+ |
+ + Nombre + | +
+ El nombre completo de la persona. + + |
+ + string + | +
+
+ identifier
+
+ |
+ + Identificador + | +
+ Un identificador oficial de la persona. El esquema debe seguir el patrón {JURISDICCIÓN}-{TIPO}, donde JURISDICCIÓN es un código de país ISO 3166-1 alfa-3 de tres letras, y TIPO es uno de los siguientes: "PASAPORTE", "TAXID" o "IDCARD". + + |
+ + Identifier object + | +
+
+ nationalities
+
+ |
+ + Nationalities + | +
+ The nationalities of the person, from the closed country codelist. + + |
+ + array of strings from closed country codelist + | +
+
+ address
+
+ |
+ + Address + | +
+ The address of the person. + + |
+ + Address object + | +
+
+ email
+
+ |
+ + Email + | +
+ The e-mail address of the person. + + |
+ + string + | +
+
+ faxNumber
+
+ |
+ + Fax number + | +
+ The fax number of the person. This must include the international dialing code. + + |
+ + string + | +
+
+ telephone
+
+ |
+ + Telephone + | +
+ The telephone number of the person. This must include the international dialing code. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/bidOpening/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/bidOpening/master/release-schema.json b/es/extensions/bidOpening/master/release-schema.json
new file mode 100644
index 000000000..2b0c7c7cd
--- /dev/null
+++ b/es/extensions/bidOpening/master/release-schema.json
@@ -0,0 +1,58 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "bidOpening": {
+ "title": "Apertura de ofertas",
+ "description": "The date, time, place and other details of the public bid opening.",
+ "$ref": "#/definitions/BidOpening"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "bidOpening": {
+ "title": "Apertura de ofertas",
+ "description": "The date, time, place and other details of the public bid opening.",
+ "$ref": "#/definitions/BidOpening"
+ }
+ }
+ },
+ "BidOpening": {
+ "title": "Apertura de ofertas",
+ "description": "The date, time, place and other details of the public bid opening.",
+ "type": "object",
+ "properties": {
+ "date": {
+ "title": "Fecha y hora",
+ "description": "Fecha y hora de la apertura de ofertas.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "location": {
+ "title": "Ubicaci\u00f3n",
+ "description": "El lugar donde se realiza la apertura de ofertas.",
+ "$ref": "#/definitions/Location"
+ },
+ "address": {
+ "title": "Direcci\u00f3n",
+ "description": "La direcci\u00f3n del lugar donde se realiza la apertura de ofertas",
+ "$ref": "#/definitions/Address"
+ },
+ "description": {
+ "title": "Detalles",
+ "description": "Cualquier otro detalle con relaci\u00f3n a la apertura de ofertas (Quienes pueden participar, si es necesaria una autorizaci\u00f3n, etc.)",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/bidOpening/master/schema/index.html b/es/extensions/bidOpening/master/schema/index.html
new file mode 100644
index 000000000..d77afcdaa
--- /dev/null
+++ b/es/extensions/bidOpening/master/schema/index.html
@@ -0,0 +1,384 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Apertura de ofertas +
+ ++ Agregar un objeto para describir la fecha, hora, lugar y otros detalles de la apertura de ofertas. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an object to describe the date, time, place and other details of the public bid opening.
+This extension must be used with the Location extension.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Contexto legal
+In the European Union, this extension's fields correspond to eForms BT-132 (Public Opening Date), BT-133 (Public Opening Place), BT-134 (Public Opening Description). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+Tender
+{
+ "tender": {
+ "bidOpening": {
+ "date": "2019-10-16T15:00:00+01:00",
+ "address": {
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford",
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom"
+ },
+ "location": {
+ "description": "Central Oxford",
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 51.751944,
+ -1.257778
+ ]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2640729"
+ ]
+ },
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "description": "We recommend that people who wish to attend the opening register on this page: https://wwww.example.org/register"
+ }
+ }
+}
+Lots
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "bidOpening": {
+ "date": "2019-10-16T15:00:00+01:00",
+ "address": {
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford",
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom"
+ },
+ "location": {
+ "description": "Central Oxford",
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 51.751944,
+ -1.257778
+ ]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2640729"
+ ]
+ },
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "description": "We recommend that people who wish to attend the opening register on this page: https://wwww.example.org/register"
+ }
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-06-07
+-
+
- Clarify that the extension is for bid openings that are public events. +
2023-02-13
+-
+
- Add
Lot.bidOpeningfield.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión fue originalmente discutida como parte del OCDS para el perfil de EU, en pull requests y en https://github.com/open-contracting/standard/issues/749.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/bids/index.html b/es/extensions/bids/index.html
new file mode 100644
index 000000000..60a64403f
--- /dev/null
+++ b/es/extensions/bids/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Apertura de ofertas +
+ ++ Agregar un objeto para describir la fecha, hora, lugar y otros detalles de la apertura de ofertas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ bidOpening
+
+ |
+ + Apertura de ofertas + | +
+ The date, time, place and other details of the public bid opening. + + |
+ + BidOpening object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ bidOpening
+
+ |
+ + Apertura de ofertas + | +
+ The date, time, place and other details of the public bid opening. + + |
+ + BidOpening object + | +
+ BidOpening +
+ +
+ The extension defines a new BidOpening object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ date
+
+ |
+ + Fecha y hora + | +
+ Fecha y hora de la apertura de ofertas. + + |
+ + string + | +
+
+ location
+
+ |
+ + Ubicación + | +
+ El lugar donde se realiza la apertura de ofertas. + + |
+ + Location object + | +
+
+ address
+
+ |
+ + Dirección + | +
+ La dirección del lugar donde se realiza la apertura de ofertas + + |
+ + Address object + | +
+
+ description
+
+ |
+ + Detalles + | +
+ Cualquier otro detalle con relación a la apertura de ofertas (Quienes pueden participar, si es necesaria una autorización, etc.) + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/bids/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/bids/master/codelists/statistic.csv b/es/extensions/bids/master/codelists/statistic.csv
new file mode 100644
index 000000000..d55ad1fdf
--- /dev/null
+++ b/es/extensions/bids/master/codelists/statistic.csv
@@ -0,0 +1,19 @@
+Categoría,Código,Título,Descripción
+bids,requests,Requests to participate,The total number of unique requests to participate received
+bids,bids,Bids,The total number of unique bids received (prior to any being discounted for not meeting essential criteria).
+bids,validBids,Valid bids,"The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids are considered during the tender evaluation stage."
+EU,disqualifiedBids,Disqualified bids,"The number of bids that were found inadmissible. A bid is found inadmissible where it has been verified that it has been submitted by a tenderer who has been excluded or who did not meet the selection criteria, or when it is not in conformity with the technical specifications, or is irregular (e.g. it was received late, having an abnormally low price or cost), unacceptable or unsuitable."
+bids,lowestValidBidValue,Lowest valid bid value,The value of the lowest valid bid.
+bids,highestValidBidValue,Highest valid bid value,The value of the highest valid bid.
+bidders,bidders,Bidders,The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria).
+bidders,qualifiedBidders,Qualified bidders,The total number of unique organizations or consortia passing the qualification stage of the evaluation process.
+bidders,disqualifiedBidders,Disqualified bidders,The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process.
+EU,electronicBids,Electronic bids,The number of bids received by electronic means.
+EU,microBids,Bids from micro companies,The number of bids received from micro enterprises.
+EU,smeBids,Bids from SMEs,The number of bids received from small and medium enterprises.
+EU,smallBids,Bids from small companies,The number of bids received from small enterprises.
+EU,mediumBids,Bids from medium companies,The number of bids received from medium enterprises.
+EU,foreignBids,Bids from foreign firms,The number of bids received from bidders from outside the country where the tender is issued.
+EU,foreignBidsFromEU,Bids from firms in other European Economic Area countries,The number of bids received from tenderers from other European Economic Area countries.
+EU,foreignBidsFromNonEU,Bids from firms in non-European Economic Area countries,The number of bids received from tenderers from non-European Economic Area countries.
+EU,tendersAbnormallyLow,Tenders excluded because they were abnormally low,"The number of tenders excluded because they were abnormally low. Note that in some EU datasets this might have been converted from a boolean, such that a value of 1 would indicate ""1 or more"" tenders were excluded. Users need to evaluate and interpret data accordingly."
diff --git a/es/extensions/bids/master/extension.json b/es/extensions/bids/master/extension.json
new file mode 100644
index 000000000..35155b927
--- /dev/null
+++ b/es/extensions/bids/master/extension.json
@@ -0,0 +1,28 @@
+{
+ "name": {
+ "en": "Bid statistics and details",
+ "es": "Estad\u00edsticas y detalles de las ofertas"
+ },
+ "description": {
+ "en": "Allowing bid statistics, and detailed bid information to be represented.",
+ "es": "Permite que se muestren las estad\u00edsticas de ofertas y la informaci\u00f3n detallada de las ofertas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/bids/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "statistic.csv",
+ "bidStatus.csv",
+ "country.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/bids/master/index.html b/es/extensions/bids/master/index.html
new file mode 100644
index 000000000..2d51ac672
--- /dev/null
+++ b/es/extensions/bids/master/index.html
@@ -0,0 +1,513 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estadísticas y detalles de las ofertas +
+ ++ Permite que se muestren las estadísticas de ofertas y la información detallada de las ofertas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ bidStatus.csv +
+ +
+ You can download the bidStatus.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ invited
+
+ |
+ + Invited + | +
+ A bid has been invited from the listed tenderer(s). + + |
+
+
+ pending
+
+ |
+ + Pending + | +
+ A bid has been submitted but not yet evaluated. + + |
+
+
+ valid
+
+ |
+ + Valid + | +
+ The submitted bid met the qualification requirements in order to be evaluated. + + |
+
+
+ disqualified
+
+ |
+ + Disqualified + | +
+ The submitted bid did not meet the qualification requirements in order to be evaluated. + + |
+
+
+ withdrawn
+
+ |
+ + Withdrawn + | +
+ The submitted bid was withdrawn by the tenderer(s). + + |
+
+ country.csv +
+ +
+ You can download the country.csv file in English.
+
| + Código + | ++ Título + | +
|---|---|
+
+ AD
+
+ |
+ + Andorra + | +
+
+ AE
+
+ |
+ + United Arab Emirates + | +
+
+ AF
+
+ |
+ + Afghanistan + | +
+
+ AG
+
+ |
+ + Antigua and Barbuda + | +
+
+ AI
+
+ |
+ + Anguilla + | +
+
+ AL
+
+ |
+ + Albania + | +
+
+ AM
+
+ |
+ + Armenia + | +
+
+ AO
+
+ |
+ + Angola + | +
+
+ AQ
+
+ |
+ + Antarctica + | +
+
+ AR
+
+ |
+ + Argentina + | +
+
+ AS
+
+ |
+ + American Samoa + | +
+
+ AT
+
+ |
+ + Austria + | +
+
+ AU
+
+ |
+ + Australia + | +
+
+ AW
+
+ |
+ + Aruba + | +
+
+ AX
+
+ |
+ + Åland Islands + | +
+
+ AZ
+
+ |
+ + Azerbaijan + | +
+
+ BA
+
+ |
+ + Bosnia and Herzegovina + | +
+
+ BB
+
+ |
+ + Barbados + | +
+
+ BD
+
+ |
+ + Bangladesh + | +
+
+ BE
+
+ |
+ + Belgium + | +
+
+ BF
+
+ |
+ + Burkina Faso + | +
+
+ BG
+
+ |
+ + Bulgaria + | +
+
+ BH
+
+ |
+ + Bahrain + | +
+
+ BI
+
+ |
+ + Burundi + | +
+
+ BJ
+
+ |
+ + Benin + | +
+
+ BL
+
+ |
+ + Saint Barthélemy + | +
+
+ BM
+
+ |
+ + Bermuda + | +
+
+ BN
+
+ |
+ + Brunei Darussalam + | +
+
+ BO
+
+ |
+ + Bolivia (Plurinational State of) + | +
+
+ BQ
+
+ |
+ + Bonaire, Sint Eustatius and Saba + | +
+
+ BR
+
+ |
+ + Brazil + | +
+
+ BS
+
+ |
+ + Bahamas + | +
+
+ BT
+
+ |
+ + Bhutan + | +
+
+ BV
+
+ |
+ + Bouvet Island + | +
+
+ BW
+
+ |
+ + Botswana + | +
+
+ BY
+
+ |
+ + Belarus + | +
+
+ BZ
+
+ |
+ + Belize + | +
+
+ CA
+
+ |
+ + Canada + | +
+
+ CC
+
+ |
+ + Cocos (Keeling) Islands + | +
+
+ CD
+
+ |
+ + Congo (the Democratic Republic of the) + | +
+
+ CF
+
+ |
+ + Central African Republic + | +
+
+ CG
+
+ |
+ + Congo + | +
+
+ CH
+
+ |
+ + Switzerland + | +
+
+ CI
+
+ |
+ + Côte d'Ivoire + | +
+
+ CK
+
+ |
+ + Cook Islands + | +
+
+ CL
+
+ |
+ + Chile + | +
+
+ CM
+
+ |
+ + Cameroon + | +
+
+ CN
+
+ |
+ + China + | +
+
+ CO
+
+ |
+ + Colombia + | +
+
+ CR
+
+ |
+ + Costa Rica + | +
+
+ CU
+
+ |
+ + Cuba + | +
+
+ CV
+
+ |
+ + Cabo Verde + | +
+
+ CW
+
+ |
+ + Curaçao + | +
+
+ CX
+
+ |
+ + Christmas Island + | +
+
+ CY
+
+ |
+ + Cyprus + | +
+
+ CZ
+
+ |
+ + Czechia + | +
+
+ DE
+
+ |
+ + Germany + | +
+
+ DJ
+
+ |
+ + Djibouti + | +
+
+ DK
+
+ |
+ + Denmark + | +
+
+ DM
+
+ |
+ + Dominica + | +
+
+ DO
+
+ |
+ + Dominican Republic + | +
+
+ DZ
+
+ |
+ + Algeria + | +
+
+ EC
+
+ |
+ + Ecuador + | +
+
+ EE
+
+ |
+ + Estonia + | +
+
+ EG
+
+ |
+ + Egypt + | +
+
+ EH
+
+ |
+ + Western Sahara + | +
+
+ ER
+
+ |
+ + Eritrea + | +
+
+ ES
+
+ |
+ + Spain + | +
+
+ ET
+
+ |
+ + Ethiopia + | +
+
+ FI
+
+ |
+ + Finland + | +
+
+ FJ
+
+ |
+ + Fiji + | +
+
+ FK
+
+ |
+ + Falkland Islands [Malvinas] + | +
+
+ FM
+
+ |
+ + Micronesia (Federated States of) + | +
+
+ FO
+
+ |
+ + Faroe Islands + | +
+
+ FR
+
+ |
+ + France + | +
+
+ GA
+
+ |
+ + Gabon + | +
+
+ GB
+
+ |
+ + United Kingdom of Great Britain and Northern Ireland + | +
+
+ GD
+
+ |
+ + Grenada + | +
+
+ GE
+
+ |
+ + Georgia + | +
+
+ GF
+
+ |
+ + French Guiana + | +
+
+ GG
+
+ |
+ + Guernsey + | +
+
+ GH
+
+ |
+ + Ghana + | +
+
+ GI
+
+ |
+ + Gibraltar + | +
+
+ GL
+
+ |
+ + Greenland + | +
+
+ GM
+
+ |
+ + Gambia + | +
+
+ GN
+
+ |
+ + Guinea + | +
+
+ GP
+
+ |
+ + Guadeloupe + | +
+
+ GQ
+
+ |
+ + Equatorial Guinea + | +
+
+ GR
+
+ |
+ + Greece + | +
+
+ GS
+
+ |
+ + South Georgia and the South Sandwich Islands + | +
+
+ GT
+
+ |
+ + Guatemala + | +
+
+ GU
+
+ |
+ + Guam + | +
+
+ GW
+
+ |
+ + Guinea-Bissau + | +
+
+ GY
+
+ |
+ + Guyana + | +
+
+ HK
+
+ |
+ + Hong Kong + | +
+
+ HM
+
+ |
+ + Heard Island and McDonald Islands + | +
+
+ HN
+
+ |
+ + Honduras + | +
+
+ HR
+
+ |
+ + Croatia + | +
+
+ HT
+
+ |
+ + Haiti + | +
+
+ HU
+
+ |
+ + Hungary + | +
+
+ ID
+
+ |
+ + Indonesia + | +
+
+ IE
+
+ |
+ + Ireland + | +
+
+ IL
+
+ |
+ + Israel + | +
+
+ IM
+
+ |
+ + Isle of Man + | +
+
+ IN
+
+ |
+ + India + | +
+
+ IO
+
+ |
+ + British Indian Ocean Territory + | +
+
+ IQ
+
+ |
+ + Iraq + | +
+
+ IR
+
+ |
+ + Iran (Islamic Republic of) + | +
+
+ IS
+
+ |
+ + Iceland + | +
+
+ IT
+
+ |
+ + Italy + | +
+
+ JE
+
+ |
+ + Jersey + | +
+
+ JM
+
+ |
+ + Jamaica + | +
+
+ JO
+
+ |
+ + Jordan + | +
+
+ JP
+
+ |
+ + Japan + | +
+
+ KE
+
+ |
+ + Kenya + | +
+
+ KG
+
+ |
+ + Kyrgyzstan + | +
+
+ KH
+
+ |
+ + Cambodia + | +
+
+ KI
+
+ |
+ + Kiribati + | +
+
+ KM
+
+ |
+ + Comoros + | +
+
+ KN
+
+ |
+ + Saint Kitts and Nevis + | +
+
+ KP
+
+ |
+ + Korea (the Democratic People's Republic of) + | +
+
+ KR
+
+ |
+ + Korea (the Republic of) + | +
+
+ KW
+
+ |
+ + Kuwait + | +
+
+ KY
+
+ |
+ + Cayman Islands + | +
+
+ KZ
+
+ |
+ + Kazakhstan + | +
+
+ LA
+
+ |
+ + Lao People's Democratic Republic + | +
+
+ LB
+
+ |
+ + Lebanon + | +
+
+ LC
+
+ |
+ + Saint Lucia + | +
+
+ LI
+
+ |
+ + Liechtenstein + | +
+
+ LK
+
+ |
+ + Sri Lanka + | +
+
+ LR
+
+ |
+ + Liberia + | +
+
+ LS
+
+ |
+ + Lesotho + | +
+
+ LT
+
+ |
+ + Lithuania + | +
+
+ LU
+
+ |
+ + Luxembourg + | +
+
+ LV
+
+ |
+ + Latvia + | +
+
+ LY
+
+ |
+ + Libya + | +
+
+ MA
+
+ |
+ + Morocco + | +
+
+ MC
+
+ |
+ + Monaco + | +
+
+ MD
+
+ |
+ + Moldova (the Republic of) + | +
+
+ ME
+
+ |
+ + Montenegro + | +
+
+ MF
+
+ |
+ + Saint Martin (French part) + | +
+
+ MG
+
+ |
+ + Madagascar + | +
+
+ MH
+
+ |
+ + Marshall Islands + | +
+
+ MK
+
+ |
+ + North Macedonia + | +
+
+ ML
+
+ |
+ + Mali + | +
+
+ MM
+
+ |
+ + Myanmar + | +
+
+ MN
+
+ |
+ + Mongolia + | +
+
+ MO
+
+ |
+ + Macao + | +
+
+ MP
+
+ |
+ + Northern Mariana Islands + | +
+
+ MQ
+
+ |
+ + Martinique + | +
+
+ MR
+
+ |
+ + Mauritania + | +
+
+ MS
+
+ |
+ + Montserrat + | +
+
+ MT
+
+ |
+ + Malta + | +
+
+ MU
+
+ |
+ + Mauritius + | +
+
+ MV
+
+ |
+ + Maldives + | +
+
+ MW
+
+ |
+ + Malawi + | +
+
+ MX
+
+ |
+ + Mexico + | +
+
+ MY
+
+ |
+ + Malaysia + | +
+
+ MZ
+
+ |
+ + Mozambique + | +
+
+ NA
+
+ |
+ + Namibia + | +
+
+ NC
+
+ |
+ + New Caledonia + | +
+
+ NE
+
+ |
+ + Niger + | +
+
+ NF
+
+ |
+ + Norfolk Island + | +
+
+ NG
+
+ |
+ + Nigeria + | +
+
+ NI
+
+ |
+ + Nicaragua + | +
+
+ NL
+
+ |
+ + Netherlands + | +
+
+ NO
+
+ |
+ + Norway + | +
+
+ NP
+
+ |
+ + Nepal + | +
+
+ NR
+
+ |
+ + Nauru + | +
+
+ NU
+
+ |
+ + Niue + | +
+
+ NZ
+
+ |
+ + New Zealand + | +
+
+ OM
+
+ |
+ + Oman + | +
+
+ PA
+
+ |
+ + Panama + | +
+
+ PE
+
+ |
+ + Peru + | +
+
+ PF
+
+ |
+ + French Polynesia + | +
+
+ PG
+
+ |
+ + Papua New Guinea + | +
+
+ PH
+
+ |
+ + Philippines + | +
+
+ PK
+
+ |
+ + Pakistan + | +
+
+ PL
+
+ |
+ + Poland + | +
+
+ PM
+
+ |
+ + Saint Pierre and Miquelon + | +
+
+ PN
+
+ |
+ + Pitcairn + | +
+
+ PR
+
+ |
+ + Puerto Rico + | +
+
+ PS
+
+ |
+ + Palestine, State of + | +
+
+ PT
+
+ |
+ + Portugal + | +
+
+ PW
+
+ |
+ + Palau + | +
+
+ PY
+
+ |
+ + Paraguay + | +
+
+ QA
+
+ |
+ + Qatar + | +
+
+ RE
+
+ |
+ + Réunion + | +
+
+ RO
+
+ |
+ + Romania + | +
+
+ RS
+
+ |
+ + Serbia + | +
+
+ RU
+
+ |
+ + Russian Federation + | +
+
+ RW
+
+ |
+ + Rwanda + | +
+
+ SA
+
+ |
+ + Saudi Arabia + | +
+
+ SB
+
+ |
+ + Solomon Islands + | +
+
+ SC
+
+ |
+ + Seychelles + | +
+
+ SD
+
+ |
+ + Sudan + | +
+
+ SE
+
+ |
+ + Sweden + | +
+
+ SG
+
+ |
+ + Singapore + | +
+
+ SH
+
+ |
+ + Saint Helena, Ascension and Tristan da Cunha + | +
+
+ SI
+
+ |
+ + Slovenia + | +
+
+ SJ
+
+ |
+ + Svalbard and Jan Mayen + | +
+
+ SK
+
+ |
+ + Slovakia + | +
+
+ SL
+
+ |
+ + Sierra Leone + | +
+
+ SM
+
+ |
+ + San Marino + | +
+
+ SN
+
+ |
+ + Senegal + | +
+
+ SO
+
+ |
+ + Somalia + | +
+
+ SR
+
+ |
+ + Suriname + | +
+
+ SS
+
+ |
+ + South Sudan + | +
+
+ ST
+
+ |
+ + Sao Tome and Principe + | +
+
+ SV
+
+ |
+ + El Salvador + | +
+
+ SX
+
+ |
+ + Sint Maarten (Dutch part) + | +
+
+ SY
+
+ |
+ + Syrian Arab Republic + | +
+
+ SZ
+
+ |
+ + Eswatini + | +
+
+ TC
+
+ |
+ + Turks and Caicos Islands + | +
+
+ TD
+
+ |
+ + Chad + | +
+
+ TF
+
+ |
+ + French Southern Territories + | +
+
+ TG
+
+ |
+ + Togo + | +
+
+ TH
+
+ |
+ + Thailand + | +
+
+ TJ
+
+ |
+ + Tajikistan + | +
+
+ TK
+
+ |
+ + Tokelau + | +
+
+ TL
+
+ |
+ + Timor-Leste + | +
+
+ TM
+
+ |
+ + Turkmenistan + | +
+
+ TN
+
+ |
+ + Tunisia + | +
+
+ TO
+
+ |
+ + Tonga + | +
+
+ TR
+
+ |
+ + Turkey + | +
+
+ TT
+
+ |
+ + Trinidad and Tobago + | +
+
+ TV
+
+ |
+ + Tuvalu + | +
+
+ TW
+
+ |
+ + Taiwan (Province of China) + | +
+
+ TZ
+
+ |
+ + Tanzania, the United Republic of + | +
+
+ UA
+
+ |
+ + Ukraine + | +
+
+ UG
+
+ |
+ + Uganda + | +
+
+ UM
+
+ |
+ + United States Minor Outlying Islands + | +
+
+ US
+
+ |
+ + United States of America + | +
+
+ UY
+
+ |
+ + Uruguay + | +
+
+ UZ
+
+ |
+ + Uzbekistan + | +
+
+ VA
+
+ |
+ + Holy See + | +
+
+ VC
+
+ |
+ + Saint Vincent and the Grenadines + | +
+
+ VE
+
+ |
+ + Venezuela (Bolivarian Republic of) + | +
+
+ VG
+
+ |
+ + Virgin Islands (British) + | +
+
+ VI
+
+ |
+ + Virgin Islands (U.S.) + | +
+
+ VN
+
+ |
+ + Viet Nam + | +
+
+ VU
+
+ |
+ + Vanuatu + | +
+
+ WF
+
+ |
+ + Wallis and Futuna + | +
+
+ WS
+
+ |
+ + Samoa + | +
+
+ XK
+
+ |
+ + Kosovo + | +
+
+ YE
+
+ |
+ + Yemen + | +
+
+ YT
+
+ |
+ + Mayotte + | +
+
+ ZA
+
+ |
+ + South Africa + | +
+
+ ZM
+
+ |
+ + Zambia + | +
+
+ ZW
+
+ |
+ + Zimbabwe + | +
+ statistic.csv +
+ +
+ You can download the statistic.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ requests
+
+ |
+ + Requests to participate + | +
+ The total number of unique requests to participate received + +
|
+
+
+ bids
+
+ |
+ + Bids + | +
+ The total number of unique bids received (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ validBids
+
+ |
+ + Valid bids + | +
+ The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids are considered during the tender evaluation stage. + +
|
+
+
+ disqualifiedBids
+
+ |
+ + Disqualified bids + | +
+ The number of bids that were found inadmissible. A bid is found inadmissible where it has been verified that it has been submitted by a tenderer who has been excluded or who did not meet the selection criteria, or when it is not in conformity with the technical specifications, or is irregular (e.g. it was received late, having an abnormally low price or cost), unacceptable or unsuitable. + +
|
+
+
+ lowestValidBidValue
+
+ |
+ + Lowest valid bid value + | +
+ The value of the lowest valid bid. + +
|
+
+
+ highestValidBidValue
+
+ |
+ + Highest valid bid value + | +
+ The value of the highest valid bid. + +
|
+
+
+ bidders
+
+ |
+ + Bidders + | +
+ The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ qualifiedBidders
+
+ |
+ + Qualified bidders + | +
+ The total number of unique organizations or consortia passing the qualification stage of the evaluation process. + +
|
+
+
+ disqualifiedBidders
+
+ |
+ + Disqualified bidders + | +
+ The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process. + +
|
+
+
+ electronicBids
+
+ |
+ + Electronic bids + | +
+ The number of bids received by electronic means. + +
|
+
+
+ microBids
+
+ |
+ + Bids from micro companies + | +
+ The number of bids received from micro enterprises. + +
|
+
+
+ smeBids
+
+ |
+ + Bids from SMEs + | +
+ The number of bids received from small and medium enterprises. + +
|
+
+
+ smallBids
+
+ |
+ + Bids from small companies + | +
+ The number of bids received from small enterprises. + +
|
+
+
+ mediumBids
+
+ |
+ + Bids from medium companies + | +
+ The number of bids received from medium enterprises. + +
|
+
+
+ foreignBids
+
+ |
+ + Bids from foreign firms + | +
+ The number of bids received from bidders from outside the country where the tender is issued. + +
|
+
+
+ foreignBidsFromEU
+
+ |
+ + Bids from firms in other European Economic Area countries + | +
+ The number of bids received from tenderers from other European Economic Area countries. + +
|
+
+
+ foreignBidsFromNonEU
+
+ |
+ + Bids from firms in non-European Economic Area countries + | +
+ The number of bids received from tenderers from non-European Economic Area countries. + +
|
+
+
+ tendersAbnormallyLow
+
+ |
+ + Tenders excluded because they were abnormally low + | +
+ The number of tenders excluded because they were abnormally low. Note that in some EU datasets this might have been converted from a boolean, such that a value of 1 would indicate "1 or more" tenders were excluded. Users need to evaluate and interpret data accordingly. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/bids/master/release-schema.json b/es/extensions/bids/master/release-schema.json
new file mode 100644
index 000000000..2eaeae6c0
--- /dev/null
+++ b/es/extensions/bids/master/release-schema.json
@@ -0,0 +1,878 @@
+{
+ "properties": {
+ "bids": {
+ "title": "Ofertas",
+ "description": "La secci\u00f3n de ofertas se utiliza para publicar res\u00famenes estad\u00edsticos y, si aplica, informaci\u00f3n de ofertas individuales.",
+ "$ref": "#/definitions/Bids"
+ }
+ },
+ "definitions": {
+ "Award": {
+ "properties": {
+ "relatedBid": {
+ "title": "Oferta relacionada",
+ "description": "Cuando se usan los detalles de la oferta, una referencia cruzada a la entrada en la lista de ofertas a la que se refiere esta adjudicaci\u00f3n. Proporcione el identificador de oferta aqu\u00ed.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "deprecated": {
+ "description": "El campo se descontin\u00faa a favor de `relatedBids` para permitir a una adjudicaci\u00f3n combinar m\u00faltiples ofertas.",
+ "deprecatedVersion": "1.2"
+ }
+ },
+ "relatedBids": {
+ "title": "Ofertas relacionadas",
+ "description": "D\u00f3nde se usan los detalles de la oferta, una referencia cruzada a las entradas del array de ofertas al cu\u00e1l se relaciona esta adjudicaci\u00f3n. Aqu\u00ed se deben de poner los identificadores de ofertas. ",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "relatedBids": {
+ "title": "Ofertas relacionadas",
+ "description": "Where bid details are used, a cross reference to the entries in the bids array to which this contract relates. Provide the bid identifiers here.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Statistic": {
+ "title": "Statistic",
+ "description": "For reporting aggregate statistics related to a tender. Where lots are in use, statistics can be broken down by lot.",
+ "type": "object",
+ "required": [
+ "id",
+ "measure",
+ "value"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "Un identificador interno para esta estad\u00edstica.",
+ "type": "string"
+ },
+ "measure": {
+ "title": "Medida",
+ "description": "La estad\u00edstica reportada por este valor.",
+ "type": "string",
+ "codelist": "statistic.csv",
+ "openCodelist": true
+ },
+ "date": {
+ "title": "Fecha",
+ "description": "La fecha en que se actualiz\u00f3 por \u00faltima vez esta estad\u00edstica. Esta es a menudo la fecha de cierre del proceso de licitaci\u00f3n. Este campo puede dejarse en blanco a menos que (a) se proporcione la misma estad\u00edstica desde m\u00faltiples puntos en el tiempo, o (b) exista un requerimiento local espec\u00edfico para proveer la fecha en la cual las estad\u00edsticas fueron calculadas.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor de la medida en cuesti\u00f3n. Los recuentos totales deben proporcionarse como un entero. Los porcentajes deber\u00edan presentarse como una proporci\u00f3n de 1 (por ejemplo, 10% = 0.1)",
+ "type": "number"
+ },
+ "valueGross": {
+ "title": "Valor bruto",
+ "description": "El valor monetario de las medidas en cuesti\u00f3n, incluyendo los impuestos. ",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "currency": {
+ "title": "Moneda",
+ "description": "La moneda para el monto contenido en el campo `value`, si la estad\u00edstica tiene un valor monetario.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "currency.csv",
+ "openCodelist": false,
+ "enum": [
+ "ADP",
+ "AED",
+ "AFA",
+ "AFN",
+ "ALK",
+ "ALL",
+ "AMD",
+ "ANG",
+ "AOA",
+ "AOK",
+ "AON",
+ "AOR",
+ "ARA",
+ "ARP",
+ "ARS",
+ "ARY",
+ "ATS",
+ "AUD",
+ "AWG",
+ "AYM",
+ "AZM",
+ "AZN",
+ "BAD",
+ "BAM",
+ "BBD",
+ "BDT",
+ "BEC",
+ "BEF",
+ "BEL",
+ "BGJ",
+ "BGK",
+ "BGL",
+ "BGN",
+ "BHD",
+ "BIF",
+ "BMD",
+ "BND",
+ "BOB",
+ "BOP",
+ "BOV",
+ "BRB",
+ "BRC",
+ "BRE",
+ "BRL",
+ "BRN",
+ "BRR",
+ "BSD",
+ "BTN",
+ "BUK",
+ "BWP",
+ "BYB",
+ "BYN",
+ "BYR",
+ "BZD",
+ "CAD",
+ "CDF",
+ "CHC",
+ "CHE",
+ "CHF",
+ "CHW",
+ "CLF",
+ "CLP",
+ "CNY",
+ "COP",
+ "COU",
+ "CRC",
+ "CSD",
+ "CSJ",
+ "CSK",
+ "CUC",
+ "CUP",
+ "CVE",
+ "CYP",
+ "CZK",
+ "DDM",
+ "DEM",
+ "DJF",
+ "DKK",
+ "DOP",
+ "DZD",
+ "ECS",
+ "ECV",
+ "EEK",
+ "EGP",
+ "ERN",
+ "ESA",
+ "ESB",
+ "ESP",
+ "ETB",
+ "EUR",
+ "FIM",
+ "FJD",
+ "FKP",
+ "FRF",
+ "GBP",
+ "GEK",
+ "GEL",
+ "GHC",
+ "GHP",
+ "GHS",
+ "GIP",
+ "GMD",
+ "GNE",
+ "GNF",
+ "GNS",
+ "GQE",
+ "GRD",
+ "GTQ",
+ "GWE",
+ "GWP",
+ "GYD",
+ "HKD",
+ "HNL",
+ "HRD",
+ "HRK",
+ "HTG",
+ "HUF",
+ "IDR",
+ "IEP",
+ "ILP",
+ "ILR",
+ "ILS",
+ "INR",
+ "IQD",
+ "IRR",
+ "ISJ",
+ "ISK",
+ "ITL",
+ "JMD",
+ "JOD",
+ "JPY",
+ "KES",
+ "KGS",
+ "KHR",
+ "KMF",
+ "KPW",
+ "KRW",
+ "KWD",
+ "KYD",
+ "KZT",
+ "LAJ",
+ "LAK",
+ "LBP",
+ "LKR",
+ "LRD",
+ "LSL",
+ "LSM",
+ "LTL",
+ "LTT",
+ "LUC",
+ "LUF",
+ "LUL",
+ "LVL",
+ "LVR",
+ "LYD",
+ "MAD",
+ "MDL",
+ "MGA",
+ "MGF",
+ "MKD",
+ "MLF",
+ "MMK",
+ "MNT",
+ "MOP",
+ "MRO",
+ "MRU",
+ "MTL",
+ "MTP",
+ "MUR",
+ "MVQ",
+ "MVR",
+ "MWK",
+ "MXN",
+ "MXP",
+ "MXV",
+ "MYR",
+ "MZE",
+ "MZM",
+ "MZN",
+ "NAD",
+ "NGN",
+ "NIC",
+ "NIO",
+ "NLG",
+ "NOK",
+ "NPR",
+ "NZD",
+ "OMR",
+ "PAB",
+ "PEH",
+ "PEI",
+ "PEN",
+ "PES",
+ "PGK",
+ "PHP",
+ "PKR",
+ "PLN",
+ "PLZ",
+ "PTE",
+ "PYG",
+ "QAR",
+ "RHD",
+ "ROK",
+ "ROL",
+ "RON",
+ "RSD",
+ "RUB",
+ "RUR",
+ "RWF",
+ "SAR",
+ "SBD",
+ "SCR",
+ "SDD",
+ "SDG",
+ "SDP",
+ "SEK",
+ "SGD",
+ "SHP",
+ "SIT",
+ "SKK",
+ "SLL",
+ "SOS",
+ "SRD",
+ "SRG",
+ "SSP",
+ "STD",
+ "STN",
+ "SUR",
+ "SVC",
+ "SYP",
+ "SZL",
+ "THB",
+ "TJR",
+ "TJS",
+ "TMM",
+ "TMT",
+ "TND",
+ "TOP",
+ "TPE",
+ "TRL",
+ "TRY",
+ "TTD",
+ "TWD",
+ "TZS",
+ "UAH",
+ "UAK",
+ "UGS",
+ "UGW",
+ "UGX",
+ "USD",
+ "USN",
+ "USS",
+ "UYI",
+ "UYN",
+ "UYP",
+ "UYU",
+ "UYW",
+ "UZS",
+ "VEB",
+ "VEF",
+ "VES",
+ "VNC",
+ "VND",
+ "VUV",
+ "WST",
+ "XAF",
+ "XAG",
+ "XAU",
+ "XBA",
+ "XBB",
+ "XBC",
+ "XBD",
+ "XCD",
+ "XDR",
+ "XEU",
+ "XFO",
+ "XFU",
+ "XOF",
+ "XPD",
+ "XPF",
+ "XPT",
+ "XRE",
+ "XSU",
+ "XTS",
+ "XUA",
+ "XXX",
+ "YDD",
+ "YER",
+ "YUD",
+ "YUM",
+ "YUN",
+ "ZAL",
+ "ZAR",
+ "ZMK",
+ "ZMW",
+ "ZRN",
+ "ZRZ",
+ "ZWC",
+ "ZWD",
+ "ZWL",
+ "ZWN",
+ "ZWR",
+ null
+ ]
+ },
+ "notes": {
+ "title": "Notas",
+ "description": "Cualquier nota requerida para entender o interpretar la estad\u00edstica proporcionada.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Lote Relacionado",
+ "description": "Where lots are in use, if this statistic relates to a particular lot, provide the lot identifier here. If left blank, the statistic will be interpreted as applying to the whole tender.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Bids": {
+ "title": "Ofertas",
+ "description": "Resumen e informaci\u00f3n detallada sobre las ofertas recibidas y evaluadas como parte de este proceso de contrataci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "statistics": {
+ "title": "Estad\u00edstica",
+ "description": "Estad\u00edsticas resumidas sobre el n\u00famero y la naturaleza de las ofertas recibidas. Cuando se proporciona informaci\u00f3n sobre ofertas individuales, estas estad\u00edsticas deben coincidir con las que se pueden calcular a partir de la matriz de detalles de oferta.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Statistic"
+ }
+ },
+ "details": {
+ "title": "Detalles de la oferta",
+ "description": "Una lista de ofertas que proporciona informaci\u00f3n sobre los licitantes y, en su caso, el estado de las ofertas, los valores de las ofertas y los documentos relacionados. La medida en que esta informaci\u00f3n puede ser revelada var\u00eda de jurisdicci\u00f3n en jurisdicci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Bid"
+ }
+ }
+ }
+ },
+ "Bid": {
+ "title": "Oferta",
+ "description": "Para representar una oferta o cotizaci\u00f3n como respuesta a la etapa de licitaci\u00f3n o de calificaci\u00f3n en este proceso de contrataci\u00f3n.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "Un identificador local para esta oferta",
+ "type": "string"
+ },
+ "identifiers": {
+ "title": "Identifiers",
+ "description": "Identifiers for this bid. This field can be used to provide internal identifiers for the bid, such as identifiers from a buyer's document management system or procurement system.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/SimpleIdentifier"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "date": {
+ "title": "Fecha",
+ "description": "La fecha en que se recibi\u00f3 esta oferta.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una descripci\u00f3n de esta oferta. El campo descripci\u00f3n puede utilizarse para describir los t\u00e9rminos y condiciones de la oferta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "title": "Estado",
+ "description": "El estado de la oferta.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "bidStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "invited",
+ "pending",
+ "valid",
+ "disqualified",
+ "withdrawn",
+ null
+ ]
+ },
+ "items": {
+ "title": "Art\u00edculos ofrecidos por los licitador(es)",
+ "description": "Los bienes, trabajos o servicios ofrecidos por el licitador(es), dividos en l\u00edneas de art\u00edculos cuando sea posible. Los art\u00edculos no deben de duplicarse, se debe espec\u00edficar la cantidad.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Item"
+ },
+ "uniqueItems": true
+ },
+ "tenderers": {
+ "title": "Licitante",
+ "description": "The organization(s) responsible for this bid.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor total de la oferta.",
+ "$ref": "#/definitions/Value"
+ },
+ "validityPeriod": {
+ "title": "Per\u00edodo de validez",
+ "description": "El per\u00edodo en el cu\u00e1l la oferta es v\u00e1lida.",
+ "$ref": "#/definitions/Period"
+ },
+ "documents": {
+ "title": "Documentos",
+ "description": "Todos los documentos y anexos relacionados con la oferta y su evaluaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Document"
+ },
+ "uniqueItems": true
+ },
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "The identifiers of the lots to which this bid relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "countriesOfOrigin": {
+ "title": "Countries of origin",
+ "description": "The countries of origin of the items in this bid, from the closed country codelist. If a country is missing, [create an issue](https://github.com/open-contracting/standard/issues) to discuss the addition of a user-assigned code to the country codelist.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "AD",
+ "AE",
+ "AF",
+ "AG",
+ "AI",
+ "AL",
+ "AM",
+ "AO",
+ "AQ",
+ "AR",
+ "AS",
+ "AT",
+ "AU",
+ "AW",
+ "AX",
+ "AZ",
+ "BA",
+ "BB",
+ "BD",
+ "BE",
+ "BF",
+ "BG",
+ "BH",
+ "BI",
+ "BJ",
+ "BL",
+ "BM",
+ "BN",
+ "BO",
+ "BQ",
+ "BR",
+ "BS",
+ "BT",
+ "BV",
+ "BW",
+ "BY",
+ "BZ",
+ "CA",
+ "CC",
+ "CD",
+ "CF",
+ "CG",
+ "CH",
+ "CI",
+ "CK",
+ "CL",
+ "CM",
+ "CN",
+ "CO",
+ "CR",
+ "CU",
+ "CV",
+ "CW",
+ "CX",
+ "CY",
+ "CZ",
+ "DE",
+ "DJ",
+ "DK",
+ "DM",
+ "DO",
+ "DZ",
+ "EC",
+ "EE",
+ "EG",
+ "EH",
+ "ER",
+ "ES",
+ "ET",
+ "FI",
+ "FJ",
+ "FK",
+ "FM",
+ "FO",
+ "FR",
+ "GA",
+ "GB",
+ "GD",
+ "GE",
+ "GF",
+ "GG",
+ "GH",
+ "GI",
+ "GL",
+ "GM",
+ "GN",
+ "GP",
+ "GQ",
+ "GR",
+ "GS",
+ "GT",
+ "GU",
+ "GW",
+ "GY",
+ "HK",
+ "HM",
+ "HN",
+ "HR",
+ "HT",
+ "HU",
+ "ID",
+ "IE",
+ "IL",
+ "IM",
+ "IN",
+ "IO",
+ "IQ",
+ "IR",
+ "IS",
+ "IT",
+ "JE",
+ "JM",
+ "JO",
+ "JP",
+ "KE",
+ "KG",
+ "KH",
+ "KI",
+ "KM",
+ "KN",
+ "KP",
+ "KR",
+ "KW",
+ "KY",
+ "KZ",
+ "LA",
+ "LB",
+ "LC",
+ "LI",
+ "LK",
+ "LR",
+ "LS",
+ "LT",
+ "LU",
+ "LV",
+ "LY",
+ "MA",
+ "MC",
+ "MD",
+ "ME",
+ "MF",
+ "MG",
+ "MH",
+ "MK",
+ "ML",
+ "MM",
+ "MN",
+ "MO",
+ "MP",
+ "MQ",
+ "MR",
+ "MS",
+ "MT",
+ "MU",
+ "MV",
+ "MW",
+ "MX",
+ "MY",
+ "MZ",
+ "NA",
+ "NC",
+ "NE",
+ "NF",
+ "NG",
+ "NI",
+ "NL",
+ "NO",
+ "NP",
+ "NR",
+ "NU",
+ "NZ",
+ "OM",
+ "PA",
+ "PE",
+ "PF",
+ "PG",
+ "PH",
+ "PK",
+ "PL",
+ "PM",
+ "PN",
+ "PR",
+ "PS",
+ "PT",
+ "PW",
+ "PY",
+ "QA",
+ "RE",
+ "RO",
+ "RS",
+ "RU",
+ "RW",
+ "SA",
+ "SB",
+ "SC",
+ "SD",
+ "SE",
+ "SG",
+ "SH",
+ "SI",
+ "SJ",
+ "SK",
+ "SL",
+ "SM",
+ "SN",
+ "SO",
+ "SR",
+ "SS",
+ "ST",
+ "SV",
+ "SX",
+ "SY",
+ "SZ",
+ "TC",
+ "TD",
+ "TF",
+ "TG",
+ "TH",
+ "TJ",
+ "TK",
+ "TL",
+ "TM",
+ "TN",
+ "TO",
+ "TR",
+ "TT",
+ "TV",
+ "TW",
+ "TZ",
+ "UA",
+ "UG",
+ "UM",
+ "US",
+ "UY",
+ "UZ",
+ "VA",
+ "VC",
+ "VE",
+ "VG",
+ "VI",
+ "VN",
+ "VU",
+ "WF",
+ "WS",
+ "XK",
+ "YE",
+ "YT",
+ "ZA",
+ "ZM",
+ "ZW"
+ ]
+ },
+ "codelist": "country.csv",
+ "openCodelist": false,
+ "minItems": 1
+ },
+ "hasRank": {
+ "title": "Has rank",
+ "description": "Whether this bid is ranked.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "rank": {
+ "title": "Rank",
+ "description": "The position of this bid (i.e. whether the bid is ranked first, second, third, etc.) in a design contest, a framework agreement with multiple winners (e.g. cascades), an innovation partnership, a competitive dialogue, or another procedure.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "variant": {
+ "title": "Is variant",
+ "description": "Whether the bid is a variant. A variant is a bid that fulfills the buyer's needs differently than as proposed in the procurement documents.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "SimpleIdentifier": {
+ "title": "Simple identifier",
+ "description": "An unambiguous reference to a resource within a given context.",
+ "type": "object",
+ "properties": {
+ "scheme": {
+ "title": "Scheme",
+ "description": "The list, register or system from which the identifier is taken.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "The identifier taken from the scheme.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "versionId": true,
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/bids/master/schema/index.html b/es/extensions/bids/master/schema/index.html
new file mode 100644
index 000000000..b292f803e
--- /dev/null
+++ b/es/extensions/bids/master/schema/index.html
@@ -0,0 +1,965 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estadísticas y detalles de las ofertas +
+ ++ Permite que se muestren las estadísticas de ofertas y la información detallada de las ofertas. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La información sobre las ofertas presentadas como parte de un proceso de contratación es importante para muchas formas de análisis, incluyendo:
+-
+
- Análisis de mercado para comprender la competitividad de un mercado determinado; +
- Análisis de banderas rojas para comprender los posibles riesgos de corrupción; y +
- Análisis de valor por dinero; +
Los regímenes regulatorios varían en la medida en que permiten que la información sobre licitaciones se publique de forma proactiva, y en el momento que permiten que el proceso de adquisición se publique. En algunos sistemas y procesos, se publicará una lista de licitadores invitados al comienzo de la licitación, y todos los detalles y documentos sobre las ofertas recibidas podrán ser revelados cuando se complete la evaluación. En otros sistemas, sólo pueden hacerse públicas las estadísticas resumidas sobre el número de ofertas recibidas.
+La extensión de oferta de OCDS introduce una sección nueva, flexible y de alto nivel para cada proceso de contratación para capturar información de ofertas. Los ejecutores deberán evaluar qué campos son aplicables a su régimen regulatorio local y los casos de uso locales.
+Esta extensión también se puede utilizar para publicar datos sobre cotizaciones.
+Esquema
+La lista bids/details se utiliza para proporcionar uno o más objetos Bid, cada uno de los cuales representa una única oferta recibida.
The bids.statistics array is used to represent key statistical information about the number of bids and bidders. Each entry in the array is a Statistic object containing at least:
-
+
- Un identificador +
- A measure, from the
statistic.csvcodelist
+ - Un valor para esa medida +
The statistic.csv codelist is an open codelist. Publishers can add their own codes to this list. When doing so, publishers are encouraged to engage with the open contracting community to agree upon definitions of each code.
Por ejemplo, tal vez los publicadores deseen agregar estadísticas sobre negocios pertenecientes a minorías o mujeres, u ofertas que cumplan ciertos estándares y metas ambientales.
+La lista de código en la columna Categoría muestra si la estadística aplica a las ofertas u ofertantes o si esta especificado o requerido por una categoría particular del contexto regulatorio (ej. UE)
+Guía
+Corregir el valor de una oferta
+Los compradores y entidades contratantes – y en algunas jurisdicciones, los oferentes – puden corregir el valor de una oferta después de que se envía la oferta: por ejemplo, para corregir un error aritmético o un punto decimal erróneo
+En el OCDS, el valor de la oferta se publica con el campo bids.details.value . Si el valor de la oferta se corrige, el valor del campo bids.details.value queda sobreescrito. Si esto pasa, el valor original solo está disponible a través del proceso de contratación ' change history.
Como publicador, para hacer que tanto los valores originales como los valores corregidos esten disponibles para los usuarios, publique al menos dos entregas para el proceso de contratación: una entrega con el valor original de la oferta y otra con el valor corregido.
+Ejemplo
+A continuación se muestra un ejemplo de una extensión de ofertas:
+{
+ "bids": {
+ "statistics": [
+ {
+ "id": "1",
+ "measure": "validBids",
+ "value": 1,
+ "date": "2016-12-09T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were considered valid against relevant criteria."
+ },
+ {
+ "id": "2",
+ "measure": "highestValidBidValue",
+ "value": 1000,
+ "valueGross": 1200,
+ "currency": "USD"
+ },
+ {
+ "id": "3",
+ "measure": "lowestValidBidValue",
+ "value": 1000,
+ "valueGross": 1200,
+ "currency": "USD"
+ }
+ ],
+ "details": [
+ {
+ "id": "1",
+ "date": "2016-12-09T01:00:00+01:00",
+ "status": "valid",
+ "identifiers": [
+ {
+ "id": "bid-123-456",
+ "scheme": "internal"
+ }
+ ],
+ "items": [
+ {
+ "id": "1",
+ "description": "Installation and operation of the Shared Public Telecommunications Network",
+ "classification": {
+ "scheme": "CPV",
+ "id": "32412100",
+ "description": "Telecommunications network",
+ "uri": "http://purl.org/cpv/2008/code-32412100"
+ },
+ "quantity": 1
+ }
+ ],
+ "value": {
+ "amount": 1000,
+ "currency": "USD"
+ },
+ "tenderers": [
+ {
+ "id": "MEGA",
+ "name": "Mega Consortium"
+ }
+ ],
+ "countriesOfOrigin": [
+ "MX"
+ ],
+ "hasRank": true,
+ "rank": 1,
+ "variant": true
+ },
+ {
+ "id": "2",
+ "date": "2016-12-10T01:00:00+01:00",
+ "status": "disqualified",
+ "value": {
+ "amount": 1500,
+ "currency": "USD"
+ },
+ "tenderers": [
+ {
+ "id": "BETA",
+ "name": "Beta Consortium"
+ }
+ ],
+ "hasRank": true,
+ "rank": 2
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "1",
+ "title": "Example PPP contract award",
+ "description": "Award of Example PPP contract to Mega Consortium",
+ "status": "active",
+ "date": "2016-12-17T10:00:00-06:00",
+ "relatedBids": [
+ "1"
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "relatedBids": [
+ "1"
+ ]
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+No entregado
+-
+
- Add fields:
+
-
+
Bid.identifiers
+Bid.description
+Bid.items
+Bid.countriesOfOrigin
+Bid.hasRank
+Bid.rank
+Bid.relatedLots(moved from the Lots extension)
+Bid.validityPeriod
+Bid.variant
+BidsStatistic.valueGross
+Award.relatedBids
+Contract.relatedBids
+
+ - Deprecate the
Award.relatedBidfield
+ - Añadir guía sobre como corregir los valores de una oferta +
- Rename the
BidStatisticdefinition toStatistic, and remove bid-specific language from its fields' descriptions
+ - Rename the
bidStatistics.csvcodelist tostatistic.csv
+ - Add codes to
statistic.csv: +-
+
- 'microBids' +
- 'smallBids' +
- 'mediumBids' +
- 'disqualifiedBids' +
+
v1.1.5
+-
+
- Añada el campo
BidsStatistic.currency
+ - Añada los códigos 'lowestValidBidValue' y 'highestValidBidValue' a
bidStatistics.csv
+ - Quitar la información sobre el tipo de las descripciones de los campos +
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- Se corrige el título y la descripción del código 'foreignBidsFromEU' para referirse al Área Económica Europea (AEE). Anteriormente, el título se refería al Mercado Único Europeo, pero su descripción enlistaba los miembros del AEE. +
- Añade el código
foreignBidsFromNonEU abidStatistics.csv`
+ - Quitar propiedad invalida
requireden la matriz del campoBids.details
+ - Arreglar el comportamiento de unión de
Bids.statisticsaBid.tendererspara identificar la estrategia de unión de los identificadores
+ - Quita las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que los campos requeridos
BidsStatistic.id,BidsStatistic.measure,BidsStatistic.valuesean null
+ - No permitir que
Bids.statisticstenga null en su lista de objetos
+ - Permitir que
Bids.statisticssea null
+ - Agregar enum a
Bid.status
+ - Mover
BidsStatistic.requirementResponsesa la extensión de requisitos
+ - Agregar descripciones a bidStatus.csv +
- Enlista listas de códigos en extension.json +
- Agregar un ejemplo a la documentación +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/bids/v1.1.4/README.md b/es/extensions/bids/v1.1.4/README.md
new file mode 100644
index 000000000..c01461622
--- /dev/null
+++ b/es/extensions/bids/v1.1.4/README.md
@@ -0,0 +1,134 @@
+# Estadísticas y detalles de las ofertas
+
+La información sobre las ofertas presentadas como parte de un proceso de contratación es importante para muchas formas de análisis, incluyendo:
+
+- Análisis de mercado para comprender la competitividad de un mercado determinado;
+- Análisis de banderas rojas para comprender los posibles riesgos de corrupción; y
+- Análisis de valor por dinero;
+
+Los regímenes regulatorios varían en la medida en que permiten que la información sobre licitaciones se publique de forma proactiva y en qué momento del proceso de adquisición. En algunos sistemas y procesos, se publicará una lista de licitadores invitados al comienzo de la licitación, y todos los detalles y documentos sobre las ofertas recibidas podrán ser revelados cuando se complete la evaluación. En otros sistemas, sólo pueden hacerse públicas las estadísticas resumidas sobre el número de ofertas recibidas.
+
+La extensión de oferta de OCDS introduce una sección nueva, flexible y de alto nivel para cada proceso de contratación para capturar información de ofertas. Los ejecutores deberán evaluar qué campos son aplicables a su régimen regulatorio local y los casos de uso locales.
+
+## Esquema
+
+La lista `bids/details` se utiliza para proporcionar uno o más objetos ` Bid`, cada uno de los cuales representa una única oferta recibida.
+
+La lista `bids/statistics` se usa para representar información estadísitca sobre el número de ofertas y ofertantes. En cada entrada de la lista hay un objeto `BidsStatistic` que contiene al menos:
+
+- Un identificador
+- Una medida, de la lista de códigos `bidStatistics.csv`
+- Un valor para esa medida
+
+La lista de códigos `bidStatistics.csv` es una lista de códigos **abierta**. Los publicadores pueden agregar sus propios códigos a esta lista. Al hacerlo, se alienta a los publicadores a comprometerse con la comunidad de contrataciones abiertas para acordar las definiciones de cada código.
+
+Por ejemplo, tal vez los publicadores deseen agregar estadísticas sobre negocios pertenecientes a minorías o mujeres, u ofertas que cumplan ciertos estándares y metas ambientales.
+
+La lista de código en la columna Categoría muestra si la estadística aplica a las ofertas u ofertantes o si esta especificado o requerido por una categoría particular del contexto regulatorio (ej. UE)
+
+## Ejemplo
+
+A continuación se muestra un ejemplo de una extensión de ofertas:
+
+```json
+{
+ "bids": {
+ "statistics": [{
+ "id": "1.0",
+ "measure": "validBids",
+ "value": 1,
+ "date": "2016-12-09T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were considered valid against relevant criteria."
+ }, {
+ "id": "2.0",
+ "measure": "disqualifiedBids",
+ "value": 1,
+ "date": "2016-12-10T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were disqualified."
+ }],
+ "details": [{
+ "id": "1.0",
+ "date": "2016-12-09T01:00:00+01:00",
+ "status": "valid",
+ "value": {
+ "amount": 1000,
+ "currency": "USD"
+ },
+ "documents": [{
+ "id": "1.0",
+ "documentType": "evaluationReports",
+ "title": "Mega Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Mega Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_megaConsortium.pdf",
+ "datePublished": "2016-11-17T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en",
+ "author": "Ministry of Communications"
+ }],
+ "tenderers": [{
+ "id": "MEGA",
+ "name": "Mega Consortium"
+ }]
+ }, {
+ "id": "2.0",
+ "date": "2016-12-10T01:00:00+01:00",
+ "status": "disqualified",
+ "value": {
+ "amount": 1500,
+ "currency": "USD"
+ },
+ "documents": [{
+ "id": "1.0",
+ "documentType": "evaluationReports",
+ "title": "Beta Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Beta Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_betaConsortium.pdf",
+ "datePublished": "2016-11-18T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en",
+ "author": "Ministry of Communications"
+ }],
+ "tenderers": [{
+ "id": "BETA",
+ "name": "Beta Consortium"
+ }]
+ }]
+
+ },
+ "awards": [{
+ "id": "111",
+ "title": "Example PPP contract award",
+ "description": "Award of Example PPP contract to Mega Consortium",
+ "status": "active",
+ "date": "2016-12-17T10:00:00-06:00",
+ "relatedBid": "1.0"
+ }]
+}
+```
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.4
+
+- Se corrige el título y la descripción del código 'foreignBidsFromEU' para referirse al Área Económica Europea (AEE). Anteriormente, el título se refería al Mercado Único Europeo, pero su descripción enlistaba los miembros del AEE.
+- Añade el código `foreignBidsFromNonEU a `bidStatistics.csv\`
+- Quitar propiedad `required` invalide a la matriz del campo `Bids.details`
+- Arreglar el comportamiento de unión de `Bids.statistics` a `Bid.tenderers` para identificar la estrategia de unión de los identificadores
+- Quita las directrices Sphinx del readme
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- No permitir que los campos requeridos `BidsStatistic.id`,` BidsStatistic.measure`, `BidsStatistic.value` sean null
+- No permitir que `Bids.statistics` tenga null en su lista de objetos
+- Permitir que `Bids.statistics` sea null
+- Agregar enum a `BidsStatistic.status`
+- Mover `BidsStatistic.requirementResponses` a la extensión de requisitos
+- Agregar descripciones a bidStatus.csv
+- Enlista listas de códigos en extension.json
+- Agregar un ejemplo a la documentación
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/bids/v1.1.4/codelists/bidStatistics.csv b/es/extensions/bids/v1.1.4/codelists/bidStatistics.csv
new file mode 100644
index 000000000..8c8109026
--- /dev/null
+++ b/es/extensions/bids/v1.1.4/codelists/bidStatistics.csv
@@ -0,0 +1,13 @@
+Categoría,Código,Título,Descripción
+bids,requests,Requests to participate,The total number of unique requests to participate received
+bids,bids,Bids,The total number of unique bids received (prior to any being discounted for not meeting essential criteria).
+bids,validBids,Valid bids,"The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids should be considered during the tender evaluation stage."
+bidders,bidders,Bidders,The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria).
+bidders,qualifiedBidders,Qualified bidders,The total number of unique organizations or consortia passing the qualification stage of the evaluation process.
+bidders,disqualifiedBidders,Disqualified bidders,The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process.
+EU,electronicBids,Electronic bids,The number of bids received by electronic means.
+EU,smeBids,Bids from SMEs,The number of bids received from small and medium-sized enterprises.
+EU,foreignBids,Bids from foreign firms,The number of bids received from bidders from outside the country where the tender is issued.
+EU,foreignBidsFromEU,Bids from firms in other European Economic Area countries,The number of bids received from tenderers from other European Economic Area countries.
+EU,foreignBidsFromNonEU,Bids from firms in non-European Economic Area countries,The number of bids received from tenderers from non-European Economic Area countries.
+EU,tendersAbnormallyLow,Tenders excluded because they were abnormally low,"The number of tenders excluded because they were abnormally low. Note that in some EU datasets this may have been converted from a boolean, such that a value of 1 would indicate '1 or more' tenders were excluded. Users should evaluate and interpret data accordingly."
diff --git a/es/extensions/bids/v1.1.4/codelists/bidStatus.csv b/es/extensions/bids/v1.1.4/codelists/bidStatus.csv
new file mode 100644
index 000000000..e26319d1e
--- /dev/null
+++ b/es/extensions/bids/v1.1.4/codelists/bidStatus.csv
@@ -0,0 +1,6 @@
+Código,Título,Descripción
+invited,Invited,A bid has been invited from the listed tenderer(s).
+pending,Pending,A bid has been submitted but not yet evaluated.
+valid,Valid,The submitted bid met the qualification requirements in order to be evaluated.
+disqualified,Disqualified,The submitted bid did not meet the qualification requirements in order to be evaluated.
+withdrawn,Withdrawn,The submitted bid was withdrawn by the tenderer(s).
diff --git a/es/extensions/bids/v1.1.4/codelists/index.html b/es/extensions/bids/v1.1.4/codelists/index.html
new file mode 100644
index 000000000..bd02c81fe
--- /dev/null
+++ b/es/extensions/bids/v1.1.4/codelists/index.html
@@ -0,0 +1,587 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estadísticas y detalles de las ofertas +
+ ++ Permite que se muestren las estadísticas de ofertas y la información detallada de las ofertas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ bids
+
+ |
+ + Ofertas + | +
+ La sección de ofertas se utiliza para publicar resúmenes estadísticos y, si aplica, información de ofertas individuales. + + |
+ + Bids object + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedBid
+
+ |
+ + Oferta relacionada + | +
+ Cuando se usan los detalles de la oferta, una referencia cruzada a la entrada en la lista de ofertas a la que se refiere esta adjudicación. Proporcione el identificador de oferta aquí. + ++ + Deprecated in OCDS 1.2: + + El campo se descontinúa a favor de `relatedBids` para permitir a una adjudicación combinar múltiples ofertas. + + |
+ + string + | +
+
+ relatedBids
+
+ |
+ + Ofertas relacionadas + | +
+ Dónde se usan los detalles de la oferta, una referencia cruzada a las entradas del array de ofertas al cuál se relaciona esta adjudicación. Aquí se deben de poner los identificadores de ofertas. + + |
+ + array of strings + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedBids
+
+ |
+ + Ofertas relacionadas + | +
+ Where bid details are used, a cross reference to the entries in the bids array to which this contract relates. Provide the bid identifiers here. + + |
+ + array of strings + | +
+ Statistic +
+ +
+ The extension defines a new Statistic object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ Un identificador interno para esta estadística. + + |
+ + string + | +
+
+ measure
+
+ |
+ + Medida + | +
+ La estadística reportada por este valor. + + |
+ + string from open statistic codelist + | +
+
+ date
+
+ |
+ + Fecha + | +
+ La fecha en que se actualizó por última vez esta estadística. Esta es a menudo la fecha de cierre del proceso de licitación. Este campo puede dejarse en blanco a menos que (a) se proporcione la misma estadística desde múltiples puntos en el tiempo, o (b) exista un requerimiento local específico para proveer la fecha en la cual las estadísticas fueron calculadas. + + |
+ + string + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor de la medida en cuestión. Los recuentos totales deben proporcionarse como un entero. Los porcentajes deberían presentarse como una proporción de 1 (por ejemplo, 10% = 0.1) + + |
+ + number + | +
+
+ valueGross
+
+ |
+ + Valor bruto + | +
+ El valor monetario de las medidas en cuestión, incluyendo los impuestos. + + |
+ + number + | +
+
+ currency
+
+ |
+ + Moneda + | +
+ La moneda para el monto contenido en el campo |
+ + string from closed currency codelist + | +
+
+ notes
+
+ |
+ + Notas + | +
+ Cualquier nota requerida para entender o interpretar la estadística proporcionada. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Lote Relacionado + | +
+ Where lots are in use, if this statistic relates to a particular lot, provide the lot identifier here. If left blank, the statistic will be interpreted as applying to the whole tender. + + |
+ + string + | +
+ Bids +
+ +
+ The extension defines a new Bids object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statistics
+
+ |
+ + Estadística + | +
+ Estadísticas resumidas sobre el número y la naturaleza de las ofertas recibidas. Cuando se proporciona información sobre ofertas individuales, estas estadísticas deben coincidir con las que se pueden calcular a partir de la matriz de detalles de oferta. + + |
+ + array of Statistic objects + | +
+
+ details
+
+ |
+ + Detalles de la oferta + | +
+ Una lista de ofertas que proporciona información sobre los licitantes y, en su caso, el estado de las ofertas, los valores de las ofertas y los documentos relacionados. La medida en que esta información puede ser revelada varía de jurisdicción en jurisdicción. + + |
+ + array of Bid objects + | +
+ Bid +
+ +
+ The extension defines a new Bid object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ Un identificador local para esta oferta + + |
+ + string + | +
+
+ identifiers
+
+ |
+ + Identifiers + | +
+ Identifiers for this bid. This field can be used to provide internal identifiers for the bid, such as identifiers from a buyer's document management system or procurement system. + + |
+ + array of SimpleIdentifier objects + | +
+
+ date
+
+ |
+ + Fecha + | +
+ La fecha en que se recibió esta oferta. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Una descripción de esta oferta. El campo descripción puede utilizarse para describir los términos y condiciones de la oferta. + + |
+ + string + | +
+
+ status
+
+ |
+ + Estado + | +
+ El estado de la oferta. + + |
+ + string from closed bidStatus codelist + | +
+
+ items
+
+ |
+ + Artículos ofrecidos por los licitador(es) + | +
+ Los bienes, trabajos o servicios ofrecidos por el licitador(es), dividos en líneas de artículos cuando sea posible. Los artículos no deben de duplicarse, se debe específicar la cantidad. + + |
+ + array of Item objects + | +
+
+ tenderers
+
+ |
+ + Licitante + | +
+ The organization(s) responsible for this bid. + + |
+ + array of OrganizationReference objects + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor total de la oferta. + + |
+ + Value object + | +
+
+ validityPeriod
+
+ |
+ + Período de validez + | +
+ El período en el cuál la oferta es válida. + + |
+ + Period object + | +
+
+ documents
+
+ |
+ + Documentos + | +
+ Todos los documentos y anexos relacionados con la oferta y su evaluación. + + |
+ + array of Document objects + | +
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ The identifiers of the lots to which this bid relates. + + |
+ + array of strings + | +
+
+ countriesOfOrigin
+
+ |
+ + Countries of origin + | +
+ The countries of origin of the items in this bid, from the closed country codelist. If a country is missing, create an issue to discuss the addition of a user-assigned code to the country codelist. + + |
+ + array of strings from closed country codelist + | +
+
+ hasRank
+
+ |
+ + Has rank + | +
+ Whether this bid is ranked. + + |
+ + boolean + | +
+
+ rank
+
+ |
+ + Rank + | +
+ The position of this bid (i.e. whether the bid is ranked first, second, third, etc.) in a design contest, a framework agreement with multiple winners (e.g. cascades), an innovation partnership, a competitive dialogue, or another procedure. + + |
+ + integer + | +
+
+ variant
+
+ |
+ + Is variant + | +
+ Whether the bid is a variant. A variant is a bid that fulfills the buyer's needs differently than as proposed in the procurement documents. + + |
+ + boolean + | +
+ SimpleIdentifier +
+ +
+ The extension defines a new SimpleIdentifier object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ scheme
+
+ |
+ + Scheme + | +
+ The list, register or system from which the identifier is taken. + + |
+ + string + | +
+
+ id
+
+ |
+ + ID + | +
+ The identifier taken from the scheme. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/bids/v1.1.4/extension.json b/es/extensions/bids/v1.1.4/extension.json
new file mode 100644
index 000000000..cbe6a6fe9
--- /dev/null
+++ b/es/extensions/bids/v1.1.4/extension.json
@@ -0,0 +1,23 @@
+{
+ "name": {
+ "en": "Bid statistics and details",
+ "es": "Estad\u00edsticas y detalles de las ofertas"
+ },
+ "description": {
+ "en": "Allowing bid statistics, and detailed bid information to be represented.",
+ "es": "Permite que se muestren las estad\u00edsticas de ofertas y la informaci\u00f3n detallada de las ofertas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/bids/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "bidStatistics.csv",
+ "bidStatus.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/es/extensions/bids/v1.1.4/index.html b/es/extensions/bids/v1.1.4/index.html
new file mode 100644
index 000000000..d5b9f0228
--- /dev/null
+++ b/es/extensions/bids/v1.1.4/index.html
@@ -0,0 +1,415 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estadísticas y detalles de las ofertas +
+ ++ Permite que se muestren las estadísticas de ofertas y la información detallada de las ofertas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ bidStatistics.csv +
+ +
+ You can download the bidStatistics.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ requests
+
+ |
+ + Requests to participate + | +
+ The total number of unique requests to participate received + +
|
+
+
+ bids
+
+ |
+ + Bids + | +
+ The total number of unique bids received (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ validBids
+
+ |
+ + Valid bids + | +
+ The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids should be considered during the tender evaluation stage. + +
|
+
+
+ bidders
+
+ |
+ + Bidders + | +
+ The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ qualifiedBidders
+
+ |
+ + Qualified bidders + | +
+ The total number of unique organizations or consortia passing the qualification stage of the evaluation process. + +
|
+
+
+ disqualifiedBidders
+
+ |
+ + Disqualified bidders + | +
+ The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process. + +
|
+
+
+ electronicBids
+
+ |
+ + Electronic bids + | +
+ The number of bids received by electronic means. + +
|
+
+
+ smeBids
+
+ |
+ + Bids from SMEs + | +
+ The number of bids received from small and medium-sized enterprises. + +
|
+
+
+ foreignBids
+
+ |
+ + Bids from foreign firms + | +
+ The number of bids received from bidders from outside the country where the tender is issued. + +
|
+
+
+ foreignBidsFromEU
+
+ |
+ + Bids from firms in other European Economic Area countries + | +
+ The number of bids received from tenderers from other European Economic Area countries. + +
|
+
+
+ foreignBidsFromNonEU
+
+ |
+ + Bids from firms in non-European Economic Area countries + | +
+ The number of bids received from tenderers from non-European Economic Area countries. + +
|
+
+
+ tendersAbnormallyLow
+
+ |
+ + Tenders excluded because they were abnormally low + | +
+ The number of tenders excluded because they were abnormally low. Note that in some EU datasets this may have been converted from a boolean, such that a value of 1 would indicate '1 or more' tenders were excluded. Users should evaluate and interpret data accordingly. + +
|
+
+ bidStatus.csv +
+ +
+ You can download the bidStatus.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ invited
+
+ |
+ + Invited + | +
+ A bid has been invited from the listed tenderer(s). + + |
+
+
+ pending
+
+ |
+ + Pending + | +
+ A bid has been submitted but not yet evaluated. + + |
+
+
+ valid
+
+ |
+ + Valid + | +
+ The submitted bid met the qualification requirements in order to be evaluated. + + |
+
+
+ disqualified
+
+ |
+ + Disqualified + | +
+ The submitted bid did not meet the qualification requirements in order to be evaluated. + + |
+
+
+ withdrawn
+
+ |
+ + Withdrawn + | +
+ The submitted bid was withdrawn by the tenderer(s). + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/bids/v1.1.4/release-schema.json b/es/extensions/bids/v1.1.4/release-schema.json
new file mode 100644
index 000000000..4befa22f9
--- /dev/null
+++ b/es/extensions/bids/v1.1.4/release-schema.json
@@ -0,0 +1,166 @@
+{
+ "properties": {
+ "bids": {
+ "title": "Ofertas",
+ "description": "La secci\u00f3n de ofertas se utiliza para publicar res\u00famenes estad\u00edsticos y, si aplica, informaci\u00f3n de ofertas individuales.",
+ "$ref": "#/definitions/Bids"
+ }
+ },
+ "definitions": {
+ "Award": {
+ "properties": {
+ "relatedBid": {
+ "title": "Oferta relacionada",
+ "description": "Cuando se usan los detalles de la oferta, una referencia cruzada a la entrada en la lista de ofertas a la que se refiere esta adjudicaci\u00f3n. Proporcione el identificador de oferta aqu\u00ed.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "BidsStatistic": {
+ "title": "Estad\u00edstica de ofertas",
+ "description": "Para reportar estad\u00edsticas agregadas sobre las ofertas relacionadas con una oferta. Cuando se utilizan lotes, las estad\u00edsticas pueden dividirse por lotes.",
+ "type": "object",
+ "required": [
+ "id",
+ "measure",
+ "value"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "Un identificador interno para este elemento estad\u00edstico.",
+ "type": "string"
+ },
+ "measure": {
+ "title": "Medida",
+ "description": "Un elemento de la lista de c\u00f3digos bidStatistics para la estad\u00edstica informada en valor. Esta es una lista de c\u00f3digos abierta, tambi\u00e9n se pueden incluir otras estad\u00edsticas.",
+ "type": "string",
+ "codelist": "bidStatistics.csv",
+ "openCodelist": true
+ },
+ "date": {
+ "title": "Fecha",
+ "description": "La fecha en que se actualiz\u00f3 por \u00faltima vez esta estad\u00edstica. Esta es a menudo la fecha de cierre del proceso de licitaci\u00f3n. Este campo puede dejarse en blanco a menos que (a) se proporcione la misma estad\u00edstica desde m\u00faltiples puntos en el tiempo, o (b) exista un requisito local espec\u00edfico para los datos cuando se calculen estad\u00edsticas para que est\u00e9n disponibles.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor de la medida en cuesti\u00f3n. Los recuentos totales deben proporcionarse como un entero. Los porcentajes deben presentarse como una proporci\u00f3n de 1 (por ejemplo, 10% = 0.1)",
+ "type": "number"
+ },
+ "notes": {
+ "title": "Notas",
+ "description": "Cualquier nota requerida para entender o interpretar la estad\u00edstica.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Lote Relacionado",
+ "description": "Cuando se usen lotes, si esta estad\u00edstica se relaciona con ofertas en un lote determinado, proporcione el identificador de lote aqu\u00ed. Si se deja en blanco, la estad\u00edstica se interpretar\u00e1 como aplicable a toda la oferta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Bids": {
+ "title": "Ofertas",
+ "description": "Resumen e informaci\u00f3n detallada sobre las ofertas recibidas y evaluadas como parte de este proceso de contrataci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "statistics": {
+ "title": "Estad\u00edstica",
+ "description": "Estad\u00edsticas resumidas sobre el n\u00famero y la naturaleza de las ofertas recibidas. Cuando se proporciona informaci\u00f3n sobre ofertas individuales, estas estad\u00edsticas deben coincidir con las que se pueden calcular a partir de la matriz de detalles de oferta.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/BidsStatistic"
+ }
+ },
+ "details": {
+ "title": "Detalles de la oferta",
+ "description": "Una lista de ofertas que proporciona informaci\u00f3n sobre los licitantes y, en su caso, el estado de las ofertas, los valores de las ofertas y los documentos relacionados. La medida en que esta informaci\u00f3n puede ser revelada var\u00eda de jurisdicci\u00f3n en jurisdicci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Bid"
+ }
+ }
+ }
+ },
+ "Bid": {
+ "title": "Oferta",
+ "description": "Para representar una oferta en respuesta a la licitaci\u00f3n o etapa de calificaci\u00f3n en esta etapa de contrataci\u00f3n.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "Un identificador local para esta oferta",
+ "type": [
+ "string"
+ ]
+ },
+ "date": {
+ "title": "Fecha",
+ "description": "La fecha en que se recibi\u00f3 esta oferta.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "status": {
+ "title": "Estado",
+ "description": "El estado de la oferta, extra\u00eddo de la lista de c\u00f3digos bidStatus",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "bidStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "invited",
+ "pending",
+ "valid",
+ "disqualified",
+ "withdrawn",
+ null
+ ]
+ },
+ "tenderers": {
+ "title": "Licitante",
+ "description": "La parte o partes responsables de esta oferta. Esto debe proporcionar un nombre y un identificador, con referencias cruzadas a una entrada en la matriz de partes en el nivel superior de la entrega.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor total de la oferta.",
+ "$ref": "#/definitions/Value"
+ },
+ "documents": {
+ "title": "Documentos",
+ "description": "Todos los documentos y anexos relacionados con la oferta y su evaluaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Document"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/bids/v1.1.4/schema/index.html b/es/extensions/bids/v1.1.4/schema/index.html
new file mode 100644
index 000000000..5782d9f2b
--- /dev/null
+++ b/es/extensions/bids/v1.1.4/schema/index.html
@@ -0,0 +1,636 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estadísticas y detalles de las ofertas +
+ ++ Permite que se muestren las estadísticas de ofertas y la información detallada de las ofertas. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La información sobre las ofertas presentadas como parte de un proceso de contratación es importante para muchas formas de análisis, incluyendo:
+-
+
- Análisis de mercado para comprender la competitividad de un mercado determinado; +
- Análisis de banderas rojas para comprender los posibles riesgos de corrupción; y +
- Análisis de valor por dinero; +
Los regímenes regulatorios varían en la medida en que permiten que la información sobre licitaciones se publique de forma proactiva y en qué momento del proceso de adquisición. En algunos sistemas y procesos, se publicará una lista de licitadores invitados al comienzo de la licitación, y todos los detalles y documentos sobre las ofertas recibidas podrán ser revelados cuando se complete la evaluación. En otros sistemas, sólo pueden hacerse públicas las estadísticas resumidas sobre el número de ofertas recibidas.
+La extensión de oferta de OCDS introduce una sección nueva, flexible y de alto nivel para cada proceso de contratación para capturar información de ofertas. Los ejecutores deberán evaluar qué campos son aplicables a su régimen regulatorio local y los casos de uso locales.
+Esquema
+La lista bids/details se utiliza para proporcionar uno o más objetos Bid, cada uno de los cuales representa una única oferta recibida.
La lista bids/statistics se usa para representar información estadísitca sobre el número de ofertas y ofertantes. En cada entrada de la lista hay un objeto BidsStatistic que contiene al menos:
-
+
- Un identificador +
- Una medida, de la lista de códigos
bidStatistics.csv
+ - Un valor para esa medida +
La lista de códigos bidStatistics.csv es una lista de códigos abierta. Los publicadores pueden agregar sus propios códigos a esta lista. Al hacerlo, se alienta a los publicadores a comprometerse con la comunidad de contrataciones abiertas para acordar las definiciones de cada código.
Por ejemplo, tal vez los publicadores deseen agregar estadísticas sobre negocios pertenecientes a minorías o mujeres, u ofertas que cumplan ciertos estándares y metas ambientales.
+La lista de código en la columna Categoría muestra si la estadística aplica a las ofertas u ofertantes o si esta especificado o requerido por una categoría particular del contexto regulatorio (ej. UE)
+Ejemplo
+A continuación se muestra un ejemplo de una extensión de ofertas:
+{
+ "bids": {
+ "statistics": [{
+ "id": "1.0",
+ "measure": "validBids",
+ "value": 1,
+ "date": "2016-12-09T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were considered valid against relevant criteria."
+ }, {
+ "id": "2.0",
+ "measure": "disqualifiedBids",
+ "value": 1,
+ "date": "2016-12-10T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were disqualified."
+ }],
+ "details": [{
+ "id": "1.0",
+ "date": "2016-12-09T01:00:00+01:00",
+ "status": "valid",
+ "value": {
+ "amount": 1000,
+ "currency": "USD"
+ },
+ "documents": [{
+ "id": "1.0",
+ "documentType": "evaluationReports",
+ "title": "Mega Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Mega Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_megaConsortium.pdf",
+ "datePublished": "2016-11-17T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en",
+ "author": "Ministry of Communications"
+ }],
+ "tenderers": [{
+ "id": "MEGA",
+ "name": "Mega Consortium"
+ }]
+ }, {
+ "id": "2.0",
+ "date": "2016-12-10T01:00:00+01:00",
+ "status": "disqualified",
+ "value": {
+ "amount": 1500,
+ "currency": "USD"
+ },
+ "documents": [{
+ "id": "1.0",
+ "documentType": "evaluationReports",
+ "title": "Beta Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Beta Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_betaConsortium.pdf",
+ "datePublished": "2016-11-18T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en",
+ "author": "Ministry of Communications"
+ }],
+ "tenderers": [{
+ "id": "BETA",
+ "name": "Beta Consortium"
+ }]
+ }]
+
+ },
+ "awards": [{
+ "id": "111",
+ "title": "Example PPP contract award",
+ "description": "Award of Example PPP contract to Mega Consortium",
+ "status": "active",
+ "date": "2016-12-17T10:00:00-06:00",
+ "relatedBid": "1.0"
+ }]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.4
+-
+
- Se corrige el título y la descripción del código 'foreignBidsFromEU' para referirse al Área Económica Europea (AEE). Anteriormente, el título se refería al Mercado Único Europeo, pero su descripción enlistaba los miembros del AEE. +
- Añade el código
foreignBidsFromNonEU abidStatistics.csv`
+ - Quitar propiedad
requiredinvalide a la matriz del campoBids.details
+ - Arreglar el comportamiento de unión de
Bids.statisticsaBid.tendererspara identificar la estrategia de unión de los identificadores
+ - Quita las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que los campos requeridos
BidsStatistic.id,BidsStatistic.measure,BidsStatistic.valuesean null
+ - No permitir que
Bids.statisticstenga null en su lista de objetos
+ - Permitir que
Bids.statisticssea null
+ - Agregar enum a
BidsStatistic.status
+ - Mover
BidsStatistic.requirementResponsesa la extensión de requisitos
+ - Agregar descripciones a bidStatus.csv +
- Enlista listas de códigos en extension.json +
- Agregar un ejemplo a la documentación +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/bids/v1.1.5/README.md b/es/extensions/bids/v1.1.5/README.md
new file mode 100644
index 000000000..d8557d918
--- /dev/null
+++ b/es/extensions/bids/v1.1.5/README.md
@@ -0,0 +1,166 @@
+# Estadísticas y detalles de las ofertas
+
+La información sobre las ofertas presentadas como parte de un proceso de contratación es importante para muchas formas de análisis, incluyendo:
+
+- Análisis de mercado para comprender la competitividad de un mercado determinado;
+- Análisis de banderas rojas para comprender los posibles riesgos de corrupción; y
+- Análisis de valor por dinero;
+
+Los regímenes regulatorios varían en la medida en que permiten que la información sobre licitaciones se publique de forma proactiva y en qué momento del proceso de adquisición. En algunos sistemas y procesos, se publicará una lista de licitadores invitados al comienzo de la licitación, y todos los detalles y documentos sobre las ofertas recibidas podrán ser revelados cuando se complete la evaluación. En otros sistemas, sólo pueden hacerse públicas las estadísticas resumidas sobre el número de ofertas recibidas.
+
+La extensión de oferta de OCDS introduce una sección nueva, flexible y de alto nivel para cada proceso de contratación para capturar información de ofertas. Los ejecutores deberán evaluar qué campos son aplicables a su régimen regulatorio local y los casos de uso locales.
+
+## Esquema
+
+La lista `bids/details` se utiliza para proporcionar uno o más objetos ` Bid`, cada uno de los cuales representa una única oferta recibida.
+
+La matriz `bids/statistics` se usa para representar información estadística sobre el número de ofertas y licitadores. En cada entrada de la matriz hay un objeto `BidsStatistic` que contiene al menos:
+
+- Un identificador
+- Una medida, de la lista de códigos `bidStatistics.csv`
+- Un valor para esa medida
+
+La lista de códigos `bidStatistics.csv` es una lista de códigos **abierta**. Los publicadores pueden agregar sus propios códigos a esta lista. Al hacerlo, se alienta a los publicadores a comprometerse con la comunidad de contrataciones abiertas para acordar las definiciones de cada código.
+
+Por ejemplo, tal vez los publicadores deseen agregar estadísticas sobre negocios pertenecientes a minorías o mujeres, u ofertas que cumplan ciertos estándares y metas ambientales.
+
+La lista de código en la columna Categoría muestra si la estadística aplica a las ofertas u ofertantes o si esta especificado o requerido por una categoría particular del contexto regulatorio (ej. UE)
+
+## Ejemplo
+
+A continuación se muestra un ejemplo de una extensión de ofertas:
+
+```json
+{
+ "bids": {
+ "statistics": [
+ {
+ "id": "1",
+ "measure": "validBids",
+ "value": 1,
+ "date": "2016-12-09T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were considered valid against relevant criteria."
+ },
+ {
+ "id": "2",
+ "measure": "disqualifiedBids",
+ "value": 1,
+ "date": "2016-12-10T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were disqualified."
+ },
+ {
+ "id": "3",
+ "measure": "highestValidBidValue",
+ "value": 1000,
+ "currency": "USD"
+ },
+ {
+ "id": "4",
+ "measure": "lowestValidBidValue",
+ "value": 1000,
+ "currency": "USD"
+ }
+ ],
+ "details": [
+ {
+ "id": "1",
+ "date": "2016-12-09T01:00:00+01:00",
+ "status": "valid",
+ "value": {
+ "amount": 1000,
+ "currency": "USD"
+ },
+ "documents": [
+ {
+ "id": "1",
+ "documentType": "evaluationReports",
+ "title": "Mega Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Mega Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_megaConsortium.pdf",
+ "datePublished": "2016-11-17T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en"
+ }
+ ],
+ "tenderers": [
+ {
+ "id": "MEGA",
+ "name": "Mega Consortium"
+ }
+ ]
+ },
+ {
+ "id": "2",
+ "date": "2016-12-10T01:00:00+01:00",
+ "status": "disqualified",
+ "value": {
+ "amount": 1500,
+ "currency": "USD"
+ },
+ "documents": [
+ {
+ "id": "1",
+ "documentType": "evaluationReports",
+ "title": "Beta Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Beta Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_betaConsortium.pdf",
+ "datePublished": "2016-11-18T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en"
+ }
+ ],
+ "tenderers": [
+ {
+ "id": "BETA",
+ "name": "Beta Consortium"
+ }
+ ]
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "111",
+ "title": "Example PPP contract award",
+ "description": "Award of Example PPP contract to Mega Consortium",
+ "status": "active",
+ "date": "2016-12-17T10:00:00-06:00",
+ "relatedBid": "1"
+ }
+ ]
+}
+```
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.5
+
+- Añada el campo `BidsStatistic.currency`
+- Añada los códigos 'lowestValidBidValue' y 'highestValidBidValue' a `bidStatistics.csv`
+- Quitar la información sobre el tipo de las descripciones de los campos
+- Revisar las palabras normativas y no-normativas
+
+### v1.1.4
+
+- Se corrige el título y la descripción del código 'foreignBidsFromEU' para referirse al Área Económica Europea (AEE). Anteriormente, el título se refería al Mercado Único Europeo, pero su descripción enlistaba los miembros del AEE.
+- Añade el código `foreignBidsFromNonEU a `bidStatistics.csv\`
+- Quitar propiedad `required` invalide a la matriz del campo `Bids.details`
+- Arreglar el comportamiento de unión de `Bids.statistics` a `Bid.tenderers` para identificar la estrategia de unión de los identificadores
+- Quita las directrices Sphinx del readme
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- No permitir que los campos requeridos `BidsStatistic.id`,` BidsStatistic.measure`, `BidsStatistic.value` sean null
+- No permitir que `Bids.statistics` tenga null en su lista de objetos
+- Permitir que `Bids.statistics` sea null
+- Agregar enum a `Bid.status`
+- Mover `BidsStatistic.requirementResponses` a la extensión de requisitos
+- Agregar descripciones a bidStatus.csv
+- Enlista listas de códigos en extension.json
+- Agregar un ejemplo a la documentación
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/bids/v1.1.5/codelists/bidStatistics.csv b/es/extensions/bids/v1.1.5/codelists/bidStatistics.csv
new file mode 100644
index 000000000..06a1f3fb0
--- /dev/null
+++ b/es/extensions/bids/v1.1.5/codelists/bidStatistics.csv
@@ -0,0 +1,15 @@
+Categoría,Código,Título,Descripción
+bids,requests,Requests to participate,The total number of unique requests to participate received
+bids,bids,Bids,The total number of unique bids received (prior to any being discounted for not meeting essential criteria).
+bids,validBids,Valid bids,"The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids are considered during the tender evaluation stage."
+bids,lowestValidBidValue,Lowest valid bid value,The value of the lowest valid bid.
+bids,highestValidBidValue,Highest valid bid value,The value of the highest valid bid.
+bidders,bidders,Bidders,The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria).
+bidders,qualifiedBidders,Qualified bidders,The total number of unique organizations or consortia passing the qualification stage of the evaluation process.
+bidders,disqualifiedBidders,Disqualified bidders,The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process.
+EU,electronicBids,Electronic bids,The number of bids received by electronic means.
+EU,smeBids,Bids from SMEs,The number of bids received from small and medium-sized enterprises.
+EU,foreignBids,Bids from foreign firms,The number of bids received from bidders from outside the country where the tender is issued.
+EU,foreignBidsFromEU,Bids from firms in other European Economic Area countries,The number of bids received from tenderers from other European Economic Area countries.
+EU,foreignBidsFromNonEU,Bids from firms in non-European Economic Area countries,The number of bids received from tenderers from non-European Economic Area countries.
+EU,tendersAbnormallyLow,Tenders excluded because they were abnormally low,"The number of tenders excluded because they were abnormally low. Note that in some EU datasets this might have been converted from a boolean, such that a value of 1 would indicate ""1 or more"" tenders were excluded. Users need to evaluate and interpret data accordingly."
diff --git a/es/extensions/bids/v1.1.5/codelists/bidStatus.csv b/es/extensions/bids/v1.1.5/codelists/bidStatus.csv
new file mode 100644
index 000000000..e26319d1e
--- /dev/null
+++ b/es/extensions/bids/v1.1.5/codelists/bidStatus.csv
@@ -0,0 +1,6 @@
+Código,Título,Descripción
+invited,Invited,A bid has been invited from the listed tenderer(s).
+pending,Pending,A bid has been submitted but not yet evaluated.
+valid,Valid,The submitted bid met the qualification requirements in order to be evaluated.
+disqualified,Disqualified,The submitted bid did not meet the qualification requirements in order to be evaluated.
+withdrawn,Withdrawn,The submitted bid was withdrawn by the tenderer(s).
diff --git a/es/extensions/bids/v1.1.5/codelists/index.html b/es/extensions/bids/v1.1.5/codelists/index.html
new file mode 100644
index 000000000..714d2ce49
--- /dev/null
+++ b/es/extensions/bids/v1.1.5/codelists/index.html
@@ -0,0 +1,631 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estadísticas y detalles de las ofertas +
+ ++ Permite que se muestren las estadísticas de ofertas y la información detallada de las ofertas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ bids
+
+ |
+ + Ofertas + | +
+ La sección de ofertas se utiliza para publicar resúmenes estadísticos y, si aplica, información de ofertas individuales. + + |
+ + Bids object + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedBid
+
+ |
+ + Oferta relacionada + | +
+ Cuando se usan los detalles de la oferta, una referencia cruzada a la entrada en la lista de ofertas a la que se refiere esta adjudicación. Proporcione el identificador de oferta aquí. + + |
+ + string + | +
+ BidsStatistic +
+ +
+ The extension defines a new BidsStatistic object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ Un identificador interno para este elemento estadístico. + + |
+ + string + | +
+
+ measure
+
+ |
+ + Medida + | +
+ Un elemento de la lista de códigos bidStatistics para la estadística informada en valor. Esta es una lista de códigos abierta, también se pueden incluir otras estadísticas. + + |
+ + string from open bidStatistics codelist + | +
+
+ date
+
+ |
+ + Fecha + | +
+ La fecha en que se actualizó por última vez esta estadística. Esta es a menudo la fecha de cierre del proceso de licitación. Este campo puede dejarse en blanco a menos que (a) se proporcione la misma estadística desde múltiples puntos en el tiempo, o (b) exista un requisito local específico para los datos cuando se calculen estadísticas para que estén disponibles. + + |
+ + string + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor de la medida en cuestión. Los recuentos totales deben proporcionarse como un entero. Los porcentajes deben presentarse como una proporción de 1 (por ejemplo, 10% = 0.1) + + |
+ + number + | +
+
+ notes
+
+ |
+ + Notas + | +
+ Cualquier nota requerida para entender o interpretar la estadística. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Lote Relacionado + | +
+ Cuando se usen lotes, si esta estadística se relaciona con ofertas en un lote determinado, proporcione el identificador de lote aquí. Si se deja en blanco, la estadística se interpretará como aplicable a toda la oferta. + + |
+ + string + | +
+ Bids +
+ +
+ The extension defines a new Bids object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statistics
+
+ |
+ + Estadística + | +
+ Estadísticas resumidas sobre el número y la naturaleza de las ofertas recibidas. Cuando se proporciona información sobre ofertas individuales, estas estadísticas deben coincidir con las que se pueden calcular a partir de la matriz de detalles de oferta. + + |
+ + array of BidsStatistic objects + | +
+
+ details
+
+ |
+ + Detalles de la oferta + | +
+ Una lista de ofertas que proporciona información sobre los licitantes y, en su caso, el estado de las ofertas, los valores de las ofertas y los documentos relacionados. La medida en que esta información puede ser revelada varía de jurisdicción en jurisdicción. + + |
+ + array of Bid objects + | +
+ Bid +
+ +
+ The extension defines a new Bid object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ Un identificador local para esta oferta + + |
+ + string + | +
+
+ date
+
+ |
+ + Fecha + | +
+ La fecha en que se recibió esta oferta. + + |
+ + string + | +
+
+ status
+
+ |
+ + Estado + | +
+ El estado de la oferta, extraído de la lista de códigos bidStatus + + |
+ + string from closed bidStatus codelist + | +
+
+ tenderers
+
+ |
+ + Licitante + | +
+ La parte o partes responsables de esta oferta. Esto debe proporcionar un nombre y un identificador, con referencias cruzadas a una entrada en la matriz de partes en el nivel superior de la entrega. + + |
+ + array of OrganizationReference objects + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor total de la oferta. + + |
+ + Value object + | +
+
+ documents
+
+ |
+ + Documentos + | +
+ Todos los documentos y anexos relacionados con la oferta y su evaluación. + + |
+ + array of Document objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/bids/v1.1.5/extension.json b/es/extensions/bids/v1.1.5/extension.json
new file mode 100644
index 000000000..b57fc1497
--- /dev/null
+++ b/es/extensions/bids/v1.1.5/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Bid statistics and details",
+ "es": "Estad\u00edsticas y detalles de las ofertas"
+ },
+ "description": {
+ "en": "Allowing bid statistics, and detailed bid information to be represented.",
+ "es": "Permite que se muestren las estad\u00edsticas de ofertas y la informaci\u00f3n detallada de las ofertas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/bids/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "bidStatistics.csv",
+ "bidStatus.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/bids/v1.1.5/index.html b/es/extensions/bids/v1.1.5/index.html
new file mode 100644
index 000000000..7e9220e03
--- /dev/null
+++ b/es/extensions/bids/v1.1.5/index.html
@@ -0,0 +1,452 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estadísticas y detalles de las ofertas +
+ ++ Permite que se muestren las estadísticas de ofertas y la información detallada de las ofertas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ bidStatistics.csv +
+ +
+ You can download the bidStatistics.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ requests
+
+ |
+ + Requests to participate + | +
+ The total number of unique requests to participate received + +
|
+
+
+ bids
+
+ |
+ + Bids + | +
+ The total number of unique bids received (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ validBids
+
+ |
+ + Valid bids + | +
+ The total number of unique bids received that were considered valid against relevant criteria (either of the bidder, or the bid submission itself). All valid bids are considered during the tender evaluation stage. + +
|
+
+
+ lowestValidBidValue
+
+ |
+ + Lowest valid bid value + | +
+ The value of the lowest valid bid. + +
|
+
+
+ highestValidBidValue
+
+ |
+ + Highest valid bid value + | +
+ The value of the highest valid bid. + +
|
+
+
+ bidders
+
+ |
+ + Bidders + | +
+ The total number of unique organizations or consortia submitting bids (prior to any being discounted for not meeting essential criteria). + +
|
+
+
+ qualifiedBidders
+
+ |
+ + Qualified bidders + | +
+ The total number of unique organizations or consortia passing the qualification stage of the evaluation process. + +
|
+
+
+ disqualifiedBidders
+
+ |
+ + Disqualified bidders + | +
+ The total number of unique organizations or consortia that did not pass the qualification stage of the evaluation process. + +
|
+
+
+ electronicBids
+
+ |
+ + Electronic bids + | +
+ The number of bids received by electronic means. + +
|
+
+
+ smeBids
+
+ |
+ + Bids from SMEs + | +
+ The number of bids received from small and medium-sized enterprises. + +
|
+
+
+ foreignBids
+
+ |
+ + Bids from foreign firms + | +
+ The number of bids received from bidders from outside the country where the tender is issued. + +
|
+
+
+ foreignBidsFromEU
+
+ |
+ + Bids from firms in other European Economic Area countries + | +
+ The number of bids received from tenderers from other European Economic Area countries. + +
|
+
+
+ foreignBidsFromNonEU
+
+ |
+ + Bids from firms in non-European Economic Area countries + | +
+ The number of bids received from tenderers from non-European Economic Area countries. + +
|
+
+
+ tendersAbnormallyLow
+
+ |
+ + Tenders excluded because they were abnormally low + | +
+ The number of tenders excluded because they were abnormally low. Note that in some EU datasets this might have been converted from a boolean, such that a value of 1 would indicate "1 or more" tenders were excluded. Users need to evaluate and interpret data accordingly. + +
|
+
+ bidStatus.csv +
+ +
+ You can download the bidStatus.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ invited
+
+ |
+ + Invited + | +
+ A bid has been invited from the listed tenderer(s). + + |
+
+
+ pending
+
+ |
+ + Pending + | +
+ A bid has been submitted but not yet evaluated. + + |
+
+
+ valid
+
+ |
+ + Valid + | +
+ The submitted bid met the qualification requirements in order to be evaluated. + + |
+
+
+ disqualified
+
+ |
+ + Disqualified + | +
+ The submitted bid did not meet the qualification requirements in order to be evaluated. + + |
+
+
+ withdrawn
+
+ |
+ + Withdrawn + | +
+ The submitted bid was withdrawn by the tenderer(s). + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/bids/v1.1.5/release-schema.json b/es/extensions/bids/v1.1.5/release-schema.json
new file mode 100644
index 000000000..8bb62444a
--- /dev/null
+++ b/es/extensions/bids/v1.1.5/release-schema.json
@@ -0,0 +1,481 @@
+{
+ "properties": {
+ "bids": {
+ "title": "Ofertas",
+ "description": "La secci\u00f3n de ofertas se utiliza para publicar res\u00famenes estad\u00edsticos y, si aplica, informaci\u00f3n de ofertas individuales.",
+ "$ref": "#/definitions/Bids"
+ }
+ },
+ "definitions": {
+ "Award": {
+ "properties": {
+ "relatedBid": {
+ "title": "Oferta relacionada",
+ "description": "Cuando se usan los detalles de la oferta, una referencia cruzada a la entrada en la lista de ofertas a la que se refiere esta adjudicaci\u00f3n. Proporcione el identificador de oferta aqu\u00ed.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "BidsStatistic": {
+ "title": "Estad\u00edstica de ofertas",
+ "description": "Para reportar estad\u00edsticas agregadas sobre las ofertas pertenecientes a una licitaci\u00f3n. Cuando se utilizan lotes, las estad\u00edsticas pueden dividirse por lotes.",
+ "type": "object",
+ "required": [
+ "id",
+ "measure",
+ "value"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "Un identificador interno para esta estad\u00edstica.",
+ "type": "string"
+ },
+ "measure": {
+ "title": "Medida",
+ "description": "La estad\u00edstica reportada por este valor.",
+ "type": "string",
+ "codelist": "bidStatistics.csv",
+ "openCodelist": true
+ },
+ "date": {
+ "title": "Fecha",
+ "description": "La fecha en que se actualiz\u00f3 por \u00faltima vez esta estad\u00edstica. Esta es a menudo la fecha de cierre del proceso de licitaci\u00f3n. Este campo puede dejarse en blanco a menos que (a) se proporcione la misma estad\u00edstica desde m\u00faltiples puntos en el tiempo, o (b) exista un requerimiento local espec\u00edfico para proveer la fecha en la cual las estad\u00edsticas fueron calculadas.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor de la medida en cuesti\u00f3n. Los recuentos totales deben proporcionarse como un entero. Los porcentajes deber\u00edan presentarse como una proporci\u00f3n de 1 (por ejemplo, 10% = 0.1)",
+ "type": "number"
+ },
+ "currency": {
+ "title": "Moneda",
+ "description": "La moneda para el monto contenido en el campo `value`, si la estad\u00edstica tiene un valor monetario.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "currency.csv",
+ "openCodelist": false,
+ "enum": [
+ "ADP",
+ "AED",
+ "AFA",
+ "AFN",
+ "ALK",
+ "ALL",
+ "AMD",
+ "ANG",
+ "AOA",
+ "AOK",
+ "AON",
+ "AOR",
+ "ARA",
+ "ARP",
+ "ARS",
+ "ARY",
+ "ATS",
+ "AUD",
+ "AWG",
+ "AYM",
+ "AZM",
+ "AZN",
+ "BAD",
+ "BAM",
+ "BBD",
+ "BDT",
+ "BEC",
+ "BEF",
+ "BEL",
+ "BGJ",
+ "BGK",
+ "BGL",
+ "BGN",
+ "BHD",
+ "BIF",
+ "BMD",
+ "BND",
+ "BOB",
+ "BOP",
+ "BOV",
+ "BRB",
+ "BRC",
+ "BRE",
+ "BRL",
+ "BRN",
+ "BRR",
+ "BSD",
+ "BTN",
+ "BUK",
+ "BWP",
+ "BYB",
+ "BYN",
+ "BYR",
+ "BZD",
+ "CAD",
+ "CDF",
+ "CHC",
+ "CHE",
+ "CHF",
+ "CHW",
+ "CLF",
+ "CLP",
+ "CNY",
+ "COP",
+ "COU",
+ "CRC",
+ "CSD",
+ "CSJ",
+ "CSK",
+ "CUC",
+ "CUP",
+ "CVE",
+ "CYP",
+ "CZK",
+ "DDM",
+ "DEM",
+ "DJF",
+ "DKK",
+ "DOP",
+ "DZD",
+ "ECS",
+ "ECV",
+ "EEK",
+ "EGP",
+ "ERN",
+ "ESA",
+ "ESB",
+ "ESP",
+ "ETB",
+ "EUR",
+ "FIM",
+ "FJD",
+ "FKP",
+ "FRF",
+ "GBP",
+ "GEK",
+ "GEL",
+ "GHC",
+ "GHP",
+ "GHS",
+ "GIP",
+ "GMD",
+ "GNE",
+ "GNF",
+ "GNS",
+ "GQE",
+ "GRD",
+ "GTQ",
+ "GWE",
+ "GWP",
+ "GYD",
+ "HKD",
+ "HNL",
+ "HRD",
+ "HRK",
+ "HTG",
+ "HUF",
+ "IDR",
+ "IEP",
+ "ILP",
+ "ILR",
+ "ILS",
+ "INR",
+ "IQD",
+ "IRR",
+ "ISJ",
+ "ISK",
+ "ITL",
+ "JMD",
+ "JOD",
+ "JPY",
+ "KES",
+ "KGS",
+ "KHR",
+ "KMF",
+ "KPW",
+ "KRW",
+ "KWD",
+ "KYD",
+ "KZT",
+ "LAJ",
+ "LAK",
+ "LBP",
+ "LKR",
+ "LRD",
+ "LSL",
+ "LSM",
+ "LTL",
+ "LTT",
+ "LUC",
+ "LUF",
+ "LUL",
+ "LVL",
+ "LVR",
+ "LYD",
+ "MAD",
+ "MDL",
+ "MGA",
+ "MGF",
+ "MKD",
+ "MLF",
+ "MMK",
+ "MNT",
+ "MOP",
+ "MRO",
+ "MRU",
+ "MTL",
+ "MTP",
+ "MUR",
+ "MVQ",
+ "MVR",
+ "MWK",
+ "MXN",
+ "MXP",
+ "MXV",
+ "MYR",
+ "MZE",
+ "MZM",
+ "MZN",
+ "NAD",
+ "NGN",
+ "NIC",
+ "NIO",
+ "NLG",
+ "NOK",
+ "NPR",
+ "NZD",
+ "OMR",
+ "PAB",
+ "PEH",
+ "PEI",
+ "PEN",
+ "PES",
+ "PGK",
+ "PHP",
+ "PKR",
+ "PLN",
+ "PLZ",
+ "PTE",
+ "PYG",
+ "QAR",
+ "RHD",
+ "ROK",
+ "ROL",
+ "RON",
+ "RSD",
+ "RUB",
+ "RUR",
+ "RWF",
+ "SAR",
+ "SBD",
+ "SCR",
+ "SDD",
+ "SDG",
+ "SDP",
+ "SEK",
+ "SGD",
+ "SHP",
+ "SIT",
+ "SKK",
+ "SLL",
+ "SOS",
+ "SRD",
+ "SRG",
+ "SSP",
+ "STD",
+ "STN",
+ "SUR",
+ "SVC",
+ "SYP",
+ "SZL",
+ "THB",
+ "TJR",
+ "TJS",
+ "TMM",
+ "TMT",
+ "TND",
+ "TOP",
+ "TPE",
+ "TRL",
+ "TRY",
+ "TTD",
+ "TWD",
+ "TZS",
+ "UAH",
+ "UAK",
+ "UGS",
+ "UGW",
+ "UGX",
+ "USD",
+ "USN",
+ "USS",
+ "UYI",
+ "UYN",
+ "UYP",
+ "UYU",
+ "UYW",
+ "UZS",
+ "VEB",
+ "VEF",
+ "VES",
+ "VNC",
+ "VND",
+ "VUV",
+ "WST",
+ "XAF",
+ "XAG",
+ "XAU",
+ "XBA",
+ "XBB",
+ "XBC",
+ "XBD",
+ "XCD",
+ "XDR",
+ "XEU",
+ "XFO",
+ "XFU",
+ "XOF",
+ "XPD",
+ "XPF",
+ "XPT",
+ "XRE",
+ "XSU",
+ "XTS",
+ "XUA",
+ "XXX",
+ "YDD",
+ "YER",
+ "YUD",
+ "YUM",
+ "YUN",
+ "ZAL",
+ "ZAR",
+ "ZMK",
+ "ZMW",
+ "ZRN",
+ "ZRZ",
+ "ZWC",
+ "ZWD",
+ "ZWL",
+ "ZWN",
+ "ZWR",
+ null
+ ]
+ },
+ "notes": {
+ "title": "Notas",
+ "description": "Cualquier nota requerida para entender o interpretar la estad\u00edstica proporcionada.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Lote Relacionado",
+ "description": "Cuando se usen lotes, si esta estad\u00edstica se relaciona con ofertas en un lote determinado, proporcione el identificador de lote aqu\u00ed. Si se deja en blanco, la estad\u00edstica se interpretar\u00e1 como aplicable a toda la oferta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Bids": {
+ "title": "Ofertas",
+ "description": "Resumen e informaci\u00f3n detallada sobre las ofertas recibidas y evaluadas como parte de este proceso de contrataci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "statistics": {
+ "title": "Estad\u00edstica",
+ "description": "Estad\u00edsticas resumidas sobre el n\u00famero y la naturaleza de las ofertas recibidas. Cuando se proporciona informaci\u00f3n sobre ofertas individuales, estas estad\u00edsticas deben coincidir con las que se pueden calcular a partir de la matriz de detalles de oferta.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/BidsStatistic"
+ }
+ },
+ "details": {
+ "title": "Detalles de la oferta",
+ "description": "Una lista de ofertas que proporciona informaci\u00f3n sobre los licitantes y, en su caso, el estado de las ofertas, los valores de las ofertas y los documentos relacionados. La medida en que esta informaci\u00f3n puede ser revelada var\u00eda de jurisdicci\u00f3n en jurisdicci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Bid"
+ }
+ }
+ }
+ },
+ "Bid": {
+ "title": "Oferta",
+ "description": "Para representar una oferta en respuesta a la licitaci\u00f3n o etapa de calificaci\u00f3n en esta etapa de contrataci\u00f3n.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "Un identificador local para esta oferta",
+ "type": [
+ "string"
+ ]
+ },
+ "date": {
+ "title": "Fecha",
+ "description": "La fecha en que se recibi\u00f3 esta oferta.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "status": {
+ "title": "Estado",
+ "description": "El estado de la oferta.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "bidStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "invited",
+ "pending",
+ "valid",
+ "disqualified",
+ "withdrawn",
+ null
+ ]
+ },
+ "tenderers": {
+ "title": "Licitante",
+ "description": "La parte, o partes, responsable(s) por esta oferta.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor total de la oferta.",
+ "$ref": "#/definitions/Value"
+ },
+ "documents": {
+ "title": "Documentos",
+ "description": "Todos los documentos y anexos relacionados con la oferta y su evaluaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Document"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/bids/v1.1.5/schema/index.html b/es/extensions/bids/v1.1.5/schema/index.html
new file mode 100644
index 000000000..d816600c1
--- /dev/null
+++ b/es/extensions/bids/v1.1.5/schema/index.html
@@ -0,0 +1,653 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estadísticas y detalles de las ofertas +
+ ++ Permite que se muestren las estadísticas de ofertas y la información detallada de las ofertas. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La información sobre las ofertas presentadas como parte de un proceso de contratación es importante para muchas formas de análisis, incluyendo:
+-
+
- Análisis de mercado para comprender la competitividad de un mercado determinado; +
- Análisis de banderas rojas para comprender los posibles riesgos de corrupción; y +
- Análisis de valor por dinero; +
Los regímenes regulatorios varían en la medida en que permiten que la información sobre licitaciones se publique de forma proactiva y en qué momento del proceso de adquisición. En algunos sistemas y procesos, se publicará una lista de licitadores invitados al comienzo de la licitación, y todos los detalles y documentos sobre las ofertas recibidas podrán ser revelados cuando se complete la evaluación. En otros sistemas, sólo pueden hacerse públicas las estadísticas resumidas sobre el número de ofertas recibidas.
+La extensión de oferta de OCDS introduce una sección nueva, flexible y de alto nivel para cada proceso de contratación para capturar información de ofertas. Los ejecutores deberán evaluar qué campos son aplicables a su régimen regulatorio local y los casos de uso locales.
+Esquema
+La lista bids/details se utiliza para proporcionar uno o más objetos Bid, cada uno de los cuales representa una única oferta recibida.
La matriz bids/statistics se usa para representar información estadística sobre el número de ofertas y licitadores. En cada entrada de la matriz hay un objeto BidsStatistic que contiene al menos:
-
+
- Un identificador +
- Una medida, de la lista de códigos
bidStatistics.csv
+ - Un valor para esa medida +
La lista de códigos bidStatistics.csv es una lista de códigos abierta. Los publicadores pueden agregar sus propios códigos a esta lista. Al hacerlo, se alienta a los publicadores a comprometerse con la comunidad de contrataciones abiertas para acordar las definiciones de cada código.
Por ejemplo, tal vez los publicadores deseen agregar estadísticas sobre negocios pertenecientes a minorías o mujeres, u ofertas que cumplan ciertos estándares y metas ambientales.
+La lista de código en la columna Categoría muestra si la estadística aplica a las ofertas u ofertantes o si esta especificado o requerido por una categoría particular del contexto regulatorio (ej. UE)
+Ejemplo
+A continuación se muestra un ejemplo de una extensión de ofertas:
+{
+ "bids": {
+ "statistics": [
+ {
+ "id": "1",
+ "measure": "validBids",
+ "value": 1,
+ "date": "2016-12-09T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were considered valid against relevant criteria."
+ },
+ {
+ "id": "2",
+ "measure": "disqualifiedBids",
+ "value": 1,
+ "date": "2016-12-10T01:00:00+01:00",
+ "notes": "This statistic covers the total number of unique bids received that were disqualified."
+ },
+ {
+ "id": "3",
+ "measure": "highestValidBidValue",
+ "value": 1000,
+ "currency": "USD"
+ },
+ {
+ "id": "4",
+ "measure": "lowestValidBidValue",
+ "value": 1000,
+ "currency": "USD"
+ }
+ ],
+ "details": [
+ {
+ "id": "1",
+ "date": "2016-12-09T01:00:00+01:00",
+ "status": "valid",
+ "value": {
+ "amount": 1000,
+ "currency": "USD"
+ },
+ "documents": [
+ {
+ "id": "1",
+ "documentType": "evaluationReports",
+ "title": "Mega Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Mega Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_megaConsortium.pdf",
+ "datePublished": "2016-11-17T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en"
+ }
+ ],
+ "tenderers": [
+ {
+ "id": "MEGA",
+ "name": "Mega Consortium"
+ }
+ ]
+ },
+ {
+ "id": "2",
+ "date": "2016-12-10T01:00:00+01:00",
+ "status": "disqualified",
+ "value": {
+ "amount": 1500,
+ "currency": "USD"
+ },
+ "documents": [
+ {
+ "id": "1",
+ "documentType": "evaluationReports",
+ "title": "Beta Consortium Bid Evaluation Report",
+ "description": "This document provides details of the evaluation of the bid submitted by Beta Consortium",
+ "url": "http://communications.gov.example/example_ppp/evaluationReport_betaConsortium.pdf",
+ "datePublished": "2016-11-18T10:00:00-06:00",
+ "format": "application/pdf",
+ "language": "en"
+ }
+ ],
+ "tenderers": [
+ {
+ "id": "BETA",
+ "name": "Beta Consortium"
+ }
+ ]
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "111",
+ "title": "Example PPP contract award",
+ "description": "Award of Example PPP contract to Mega Consortium",
+ "status": "active",
+ "date": "2016-12-17T10:00:00-06:00",
+ "relatedBid": "1"
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.5
+-
+
- Añada el campo
BidsStatistic.currency
+ - Añada los códigos 'lowestValidBidValue' y 'highestValidBidValue' a
bidStatistics.csv
+ - Quitar la información sobre el tipo de las descripciones de los campos +
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- Se corrige el título y la descripción del código 'foreignBidsFromEU' para referirse al Área Económica Europea (AEE). Anteriormente, el título se refería al Mercado Único Europeo, pero su descripción enlistaba los miembros del AEE. +
- Añade el código
foreignBidsFromNonEU abidStatistics.csv`
+ - Quitar propiedad
requiredinvalide a la matriz del campoBids.details
+ - Arreglar el comportamiento de unión de
Bids.statisticsaBid.tendererspara identificar la estrategia de unión de los identificadores
+ - Quita las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que los campos requeridos
BidsStatistic.id,BidsStatistic.measure,BidsStatistic.valuesean null
+ - No permitir que
Bids.statisticstenga null en su lista de objetos
+ - Permitir que
Bids.statisticssea null
+ - Agregar enum a
Bid.status
+ - Mover
BidsStatistic.requirementResponsesa la extensión de requisitos
+ - Agregar descripciones a bidStatus.csv +
- Enlista listas de códigos en extension.json +
- Agregar un ejemplo a la documentación +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/budget/index.html b/es/extensions/budget/index.html
new file mode 100644
index 000000000..0aacca477
--- /dev/null
+++ b/es/extensions/budget/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estadísticas y detalles de las ofertas +
+ ++ Permite que se muestren las estadísticas de ofertas y la información detallada de las ofertas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ bids
+
+ |
+ + Ofertas + | +
+ La sección de ofertas se utiliza para publicar resúmenes estadísticos y, si aplica, información de ofertas individuales. + + |
+ + Bids object + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedBid
+
+ |
+ + Oferta relacionada + | +
+ Cuando se usan los detalles de la oferta, una referencia cruzada a la entrada en la lista de ofertas a la que se refiere esta adjudicación. Proporcione el identificador de oferta aquí. + + |
+ + string + | +
+ BidsStatistic +
+ +
+ The extension defines a new BidsStatistic object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ Un identificador interno para esta estadística. + + |
+ + string + | +
+
+ measure
+
+ |
+ + Medida + | +
+ La estadística reportada por este valor. + + |
+ + string from open bidStatistics codelist + | +
+
+ date
+
+ |
+ + Fecha + | +
+ La fecha en que se actualizó por última vez esta estadística. Esta es a menudo la fecha de cierre del proceso de licitación. Este campo puede dejarse en blanco a menos que (a) se proporcione la misma estadística desde múltiples puntos en el tiempo, o (b) exista un requerimiento local específico para proveer la fecha en la cual las estadísticas fueron calculadas. + + |
+ + string + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor de la medida en cuestión. Los recuentos totales deben proporcionarse como un entero. Los porcentajes deberían presentarse como una proporción de 1 (por ejemplo, 10% = 0.1) + + |
+ + number + | +
+
+ currency
+
+ |
+ + Moneda + | +
+ La moneda para el monto contenido en el campo |
+ + string from closed currency codelist + | +
+
+ notes
+
+ |
+ + Notas + | +
+ Cualquier nota requerida para entender o interpretar la estadística proporcionada. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Lote Relacionado + | +
+ Cuando se usen lotes, si esta estadística se relaciona con ofertas en un lote determinado, proporcione el identificador de lote aquí. Si se deja en blanco, la estadística se interpretará como aplicable a toda la oferta. + + |
+ + string + | +
+ Bids +
+ +
+ The extension defines a new Bids object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statistics
+
+ |
+ + Estadística + | +
+ Estadísticas resumidas sobre el número y la naturaleza de las ofertas recibidas. Cuando se proporciona información sobre ofertas individuales, estas estadísticas deben coincidir con las que se pueden calcular a partir de la matriz de detalles de oferta. + + |
+ + array of BidsStatistic objects + | +
+
+ details
+
+ |
+ + Detalles de la oferta + | +
+ Una lista de ofertas que proporciona información sobre los licitantes y, en su caso, el estado de las ofertas, los valores de las ofertas y los documentos relacionados. La medida en que esta información puede ser revelada varía de jurisdicción en jurisdicción. + + |
+ + array of Bid objects + | +
+ Bid +
+ +
+ The extension defines a new Bid object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ Un identificador local para esta oferta + + |
+ + string + | +
+
+ date
+
+ |
+ + Fecha + | +
+ La fecha en que se recibió esta oferta. + + |
+ + string + | +
+
+ status
+
+ |
+ + Estado + | +
+ El estado de la oferta. + + |
+ + string from closed bidStatus codelist + | +
+
+ tenderers
+
+ |
+ + Licitante + | +
+ La parte, o partes, responsable(s) por esta oferta. + + |
+ + array of OrganizationReference objects + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor total de la oferta. + + |
+ + Value object + | +
+
+ documents
+
+ |
+ + Documentos + | +
+ Todos los documentos y anexos relacionados con la oferta y su evaluación. + + |
+ + array of Document objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/budget/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/budget/master/extension.json b/es/extensions/budget/master/extension.json
new file mode 100644
index 000000000..742a26c06
--- /dev/null
+++ b/es/extensions/budget/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Budget Breakdown",
+ "es": "Desglose del presupuesto"
+ },
+ "description": {
+ "en": "Adds a budget breakdown array to the budget object to break down a budget by source and period.",
+ "es": "Agrega una lista de desglose de presupuesto al objeto de presupuesto para desglosar un presupuesto por fuente y per\u00edodo."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/budget/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "+partyRole.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/budget/master/index.html b/es/extensions/budget/master/index.html
new file mode 100644
index 000000000..7e0e43008
--- /dev/null
+++ b/es/extensions/budget/master/index.html
@@ -0,0 +1,436 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Desglose del presupuesto +
+ ++ Agrega una lista de desglose de presupuesto al objeto de presupuesto para desglosar un presupuesto por fuente y período. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ sourceParty
+
+ |
+ + Source organization + | +
+ The organization providing the funds for a budget entry. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/budget/master/release-schema.json b/es/extensions/budget/master/release-schema.json
new file mode 100644
index 000000000..a04887aa5
--- /dev/null
+++ b/es/extensions/budget/master/release-schema.json
@@ -0,0 +1,71 @@
+{
+ "definitions": {
+ "BudgetBreakdown": {
+ "title": "Desglose detallado del presupuesto",
+ "description": "Esta secci\u00f3n permite expresar un desglose detallado del presupuesto, cubriendo tanto m\u00faltiples fuentes presupuestarias como per\u00edodos m\u00faltiples",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador para esta entrada de presupuesto en particular.",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una breve descripci\u00f3n de texto libre sobre esta entrada de presupuesto.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "amount": {
+ "title": "Monto",
+ "description": "The value of the budget line item. A positive amount means the source organization funds the contracting process. A negative amount means the contracting process pays the source organization.",
+ "$ref": "#/definitions/Value"
+ },
+ "uri": {
+ "title": "Informaci\u00f3n vinculada de presupuesto",
+ "description": "Un URI apuntando directamente a informaci\u00f3n legible por computadora acerca de esta entrada de presupuesto.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "period": {
+ "title": "Per\u00edodo de Presupuesto",
+ "description": "El per\u00edodo cubierto por esta entrada presupuestaria.",
+ "$ref": "#/definitions/Period"
+ },
+ "sourceParty": {
+ "title": "Source organization",
+ "description": "The organization providing the funds for this budget entry. The corresponding entry in the `parties` array must have 'sourceParty' in its `roles` array.",
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "minProperties": 1
+ },
+ "Budget": {
+ "properties": {
+ "budgetBreakdown": {
+ "title": "Desglose del presupuesto",
+ "description": "Un desglose detallado del presupuesto por periodo y/o financiadores participantes.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/BudgetBreakdown"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/budget/master/schema/index.html b/es/extensions/budget/master/schema/index.html
new file mode 100644
index 000000000..3909f9550
--- /dev/null
+++ b/es/extensions/budget/master/schema/index.html
@@ -0,0 +1,372 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Desglose del presupuesto +
+ ++ Agrega una lista de desglose de presupuesto al objeto de presupuesto para desglosar un presupuesto por fuente y período. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+El objeto planning.budget del OCDS puede utilizarse para describir el presupuesto del que se extraen los fondos. Incluye un único campo budget.amount para capturar el valor total del presupuesto para el proceso de contratación.
Esta extensión permite describir el presupuesto con mayor detalle, incluidos los presupuestos plurianuales o los presupuestos procedentes de múltiples organizaciones. En el caso de las APP, los presupuestos pueden proceder del sector privado o de bancos de desarrollo multilaterales.
+La divulgación de datos estructurados de presupuestos de fuentes múltiples permite a los usuarios entender cuánto de los fondos para un proyecto provienen del gobierno o de un departamento específico, mientras que los datos estructurados sobre presupuestos multi-anuales permiten a los usuarios entender el perfil de gasto esperado de un contrato.
+Guía
+En el bloque principal de planning.budget, se debe utilizar budget.amount para capturar el valor total del presupuesto para el proceso de contratación.
Cuando se utiliza budget.budgetBreakdown para expresar un presupuesto de múltiples fuentes pero los detalles de la organización no se conocen para una o más partes del presupuesto, por ejemplo, en una APP donde el licitador del sector privado proporcionará parte del presupuesto , el campo sourceParty.name debe usarse para proporcionar una explicación de texto libre de la fuente del presupuesto, por ejemplo "Inversión del sector privado del licitador ganador".
Ejemplos
+Presupuestos de múltiples fuentes
+El siguiente fragmento JSON modela un presupuesto multi-fuente de un solo año:
+{
+ "planning": {
+ "budget": {
+ "amount": {
+ "amount": 300000,
+ "currency": "GBP"
+ },
+ "budgetBreakdown": [
+ {
+ "id": "1",
+ "description": "Budget contribution from the local government",
+ "sourceParty": {
+ "id": "GB-LAC-E09000003-557",
+ "name": "London Borough of Barnet - Transport Services"
+ },
+ "amount": {
+ "amount": 150000,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "2",
+ "description": "Budget contribution from the national government",
+ "sourceParty": {
+ "id": "GB-GOV-23",
+ "name": "Department for Transport"
+ },
+ "amount": {
+ "amount": 150000,
+ "currency": "GBP"
+ }
+ }
+ ]
+ }
+ },
+ "parties": [
+ {
+ "id": "GB-GOV-23",
+ "name": "Department for Transport",
+ "roles": [
+ "funder"
+ ]
+ },
+ {
+ "id": "GB-LAC-E09000003-557",
+ "name": "London Borough of Barnet - Transport Services",
+ "roles": [
+ "funder"
+ ]
+ }
+ ]
+}
+Presupuestos multi-anuales
+El siguiente fragmento JSON modela un presupuesto multi-anual de fuente única:
+{
+ "planning": {
+ "budget": {
+ "amount": {
+ "amount": 70000,
+ "currency": "GBP"
+ },
+ "budgetBreakdown": [
+ {
+ "id": "1",
+ "description": "2021/2022",
+ "period": {
+ "startDate": "2021-04-01T00:00:00Z",
+ "endDate": "2022-03-31T23:59:59Z"
+ },
+ "amount": {
+ "amount": 20000,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "2",
+ "description": "2022/2023",
+ "period": {
+ "startDate": "2022-04-01T00:00:00Z",
+ "endDate": "2023-03-31T23:59:59Z"
+ },
+ "amount": {
+ "amount": 50000,
+ "currency": "GBP"
+ }
+ }
+ ]
+ }
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-06-07
+-
+
- Add 'sourceParty' code to the
+partyRole.csvcodelist, because the 'funder' code is deprecated in OCDS 1.2.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-03-20
+-
+
- Establecer
"uniqueItems ": trueen los campos matriz y agregar"minLength": 1en los campos de cadena obligatorios.
+
2019-01-30
+-
+
- Remover la propiedad obsoleta
mergeStrategy.
+
2018-05-08
+-
+
- Hacer obligatorio y no nulo
BudgetBreakdown.idpara permitir el seguimiento de revisiones y fusión de listas
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/budget_and_spend/index.html b/es/extensions/budget_and_spend/index.html
new file mode 100644
index 000000000..35560ac1b
--- /dev/null
+++ b/es/extensions/budget_and_spend/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Desglose del presupuesto +
+ ++ Agrega una lista de desglose de presupuesto al objeto de presupuesto para desglosar un presupuesto por fuente y período. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ BudgetBreakdown +
+ +
+ The extension defines a new BudgetBreakdown object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador para esta entrada de presupuesto en particular. + + |
+ + string or integer + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Una breve descripción de texto libre sobre esta entrada de presupuesto. + + |
+ + string + | +
+
+ amount
+
+ |
+ + Monto + | +
+ The value of the budget line item. A positive amount means the source organization funds the contracting process. A negative amount means the contracting process pays the source organization. + + |
+ + Value object + | +
+
+ uri
+
+ |
+ + Información vinculada de presupuesto + | +
+ Un URI apuntando directamente a información legible por computadora acerca de esta entrada de presupuesto. + + |
+ + string + | +
+
+ period
+
+ |
+ + Período de Presupuesto + | +
+ El período cubierto por esta entrada presupuestaria. + + |
+ + Period object + | +
+
+ sourceParty
+
+ |
+ + Source organization + | +
+ The organization providing the funds for this budget entry. The corresponding entry in the |
+ + OrganizationReference object + | +
+ Budget +
+ +
+ The extension defines these fields in the Budget object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ budgetBreakdown
+
+ |
+ + Desglose del presupuesto + | +
+ Un desglose detallado del presupuesto por periodo y/o financiadores participantes. + + |
+ + array of BudgetBreakdown objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/budget_and_spend/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/budget_and_spend/master/release-schema.json b/es/extensions/budget_and_spend/master/release-schema.json
new file mode 100644
index 000000000..3f89e4370
--- /dev/null
+++ b/es/extensions/budget_and_spend/master/release-schema.json
@@ -0,0 +1,155 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "financialProgress": {
+ "title": "Progreso financiero",
+ "description": "La secci\u00f3n de progreso financiero permite publicar informaci\u00f3n de alto nivel y detallada sobre montos asignados o gastados hasta la fecha para este contrato en particular. Esto puede usarse junto a la secci\u00f3n de transacciones, la cual permite que se registren detalles de cada pago individual.",
+ "type": "object",
+ "properties": {
+ "totalSpend": {
+ "title": "Gasto total",
+ "description": "El gasto total de este contrato a la fecha de la \u00faltima actualizaci\u00f3n. Tenga en cuenta que la medida fiscal exacta que representa este n\u00famero puede variar dependiendo del publicador de los datos (ej. monto facturado vs monto transferido al banco del proveedor).",
+ "$ref": "#/definitions/Value"
+ },
+ "measures": {
+ "title": "Medidas",
+ "description": "La secci\u00f3n de medidas reporta valores agregados del progreso financiero para este contrato (ie. sin el desglose de clasificaci\u00f3n de presupuesto. Las medidas se deben de dar como un set de pares clave-valor, donde la clave debe ser el nombre de la medida utilizada dentro de una base de datos del Paquete de Datos Fiscales u otra base de datos de presupuesto y gasto. El valor es el valor de esta medida la \u00faltima vez que fue actualizada y debe de darse como un n\u00famero en la misma moneda que cualquier reporte agregado de presupuesto o figuras de gasto.",
+ "type": "object",
+ "patternProperties": {
+ "[A-Za-z0-9._-]": {
+ "type": [
+ "number",
+ "null"
+ ]
+ }
+ },
+ "minProperties": 1
+ },
+ "breakdown": {
+ "title": "Desglose de progreso financiero",
+ "description": "Esta secci\u00f3n contienen un desglose del progreso financiero, permitiendo que varias medidas (monto facturado, monto acumulado, monto pagado, etc) se desglosen por fuente, per\u00edodo y clasificaci\u00f3n de presupuesto",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/FinancialProgressBreakdown"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+ },
+ "FinancialProgressBreakdown": {
+ "title": "Desglose de progreso financiero",
+ "description": "Esta secci\u00f3n permite un desglose detallado de cada progreso financiero que se de, cada uno cubriendo per\u00edodos particulares, o asignar el progreso financiero a fuentes de financiamiento particulares y clasificaciones fiscales.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador para esta entrada de desglose de progreso financiero particular ",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Un texto breve de descripci\u00f3n de este desglose de progreso financiero. Esto puede visualizarse en una interfaz de usuarios que interprete esta entrada. Puede ser generada autom\u00e1ticamente como datos estructurados o pueden ser ingresados manualmente.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "period": {
+ "title": "Per\u00edodo de Presupuesto",
+ "description": "El per\u00edodo cubierto por la entrada de desglose de progreso financiero. Esta informaci\u00f3n tambi\u00e9n puede ser duplicada utilizando clasificaciones cuando sea relevante. ",
+ "$ref": "#/definitions/Period"
+ },
+ "classifications": {
+ "title": "Clasificaciones de presupuesto",
+ "description": "Las clasificaciones de presupuesto deben de darse como un conjunto de pares clave-valor, donde la clave es la dimensi\u00f3n (o el nombre de la dimensi\u00f3n) usada en la clasificaci\u00f3n de presupuesto, y el valor es el valor de esa dimensi\u00f3n en el proceso de contrataciones o en el contrato espec\u00edfico (dependiendo del punto en el archivo OCDS en el cual se da la clasificaci\u00f3n).",
+ "type": "object",
+ "patternProperties": {
+ "[A-Za-z0-9._-]": {
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "measures": {
+ "title": "medidas",
+ "description": "Las medidas deben de dar un conjunto de pares clave-valor, donde la clave debe ser el nombre de una medida utilizada en la base de datos del Paquete de Datos Fiscales o en otras bases de datos de presupuesto y gasto. El valor es el valor de esta medida en la \u00faltima actualizaci\u00f3n, y debe de darse como un n\u00famero en la misma moneda que en cualquier reporte de presupuesto agregado o valores de gasto.",
+ "type": "object",
+ "patternProperties": {
+ "[A-Za-z0-9._-]": {
+ "type": [
+ "number",
+ "null"
+ ]
+ }
+ },
+ "minProperties": 1
+ },
+ "fiscalBreakdownFieldMapping": {
+ "$ref": "#/definitions/FiscalBreakdownFieldMapping"
+ }
+ },
+ "minProperties": 1
+ },
+ "BudgetBreakdown": {
+ "properties": {
+ "classifications": {
+ "title": "Clasificaciones de presupuesto",
+ "description": "Las clasificaciones de presupuesto deben de darse como un conjunto de pares clave-valor, donde la clave es la dimensi\u00f3n (o el nombre de la dimensi\u00f3n) usada en la clasificaci\u00f3n de presupuesto, y el valor es el valor de esa dimensi\u00f3n en el proceso de contrataciones o en el contrato espec\u00edfico (dependiendo del punto en el archivo OCDS en el cual se da la clasificaci\u00f3n).",
+ "type": "object",
+ "patternProperties": {
+ "[A-Za-z0-9._-]": {
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "measures": {
+ "title": "medidas",
+ "description": "Las medidas deben de dar un conjunto de pares clave-valor, donde la clave debe ser el nombre de una medida utilizada en la base de datos del Paquete de Datos Fiscales o en otras bases de datos de presupuesto y gasto. El valor es el valor de esta medida en la \u00faltima actualizaci\u00f3n, y debe de darse como un n\u00famero en la misma moneda que en cualquier reporte de presupuesto agregado o valores de gasto.",
+ "type": "object",
+ "patternProperties": {
+ "[A-Za-z0-9._-]": {
+ "type": [
+ "number",
+ "null"
+ ]
+ }
+ },
+ "minProperties": 1
+ },
+ "fiscalBreakdownFieldMapping": {
+ "$ref": "#/definitions/FiscalBreakdownFieldMapping"
+ }
+ }
+ },
+ "FiscalBreakdownFieldMapping": {
+ "title": "Mapeo de Campos de Desglose Fiscal",
+ "description": "El OCDS se remite al Paquete de Datos Fiscales para proporcionar definiciones detalladas de las clasificaciones y medidas presupuestarias, incluyendo la provisi\u00f3n de etiquetas para cada bien y la descripci\u00f3n de la relaci\u00f3n entre cada clasificaci\u00f3n o medida y los conceptos fiscales establecidos. Un paquete de datos fiscales tambi\u00e9n puede contener datos sobre el presupuesto y los gastos, utilizando las mismas clasificaciones y medidas que el archivo OCDS, y permitiendo as\u00ed la comparaci\u00f3n entre las asignaciones presupuestarias y los gastos a 'contract level', y las asignaciones y los gastos a nivel de una l\u00ednea presupuestaria concreta. Cuando se utiliza, el campo fiscalBreakdownFieldMapping debe contener un URI desreferenciable que apunte a un archivo [Fiscal Data Package (FDP)](https://frictionlessdata.io/specs/fiscal-data-package/) datapackage.json (versi\u00f3n 1.0 o superior), o un archivo que, al descomprimirse, contenga un archivo datapackage.json. La URI debe incluir un identificador de fragmento con el valor `name` de un recurso concreto dentro de ese archivo para identificar el archivo de datos de presupuesto o de gasto concreto con el que pueden compararse las asignaciones presupuestarias y las medidas de gasto a nivel de contrato, y las definiciones de columna concretas que deben utilizarse. El recurso referenciado debe contener propiedades `field` o `extraField` con su propiedad `name` que coincida con cada uno de los campos de `classification` o `measure` del desglose del presupuesto/progreso financiero en los datos de la OCDS, y como m\u00ednimo proporcionar etiquetas para estos.",
+ "type": "string",
+ "format": "uri"
+ }
+ }
+}
diff --git a/es/extensions/budget_and_spend/master/schema/index.html b/es/extensions/budget_and_spend/master/schema/index.html
new file mode 100644
index 000000000..37e04241f
--- /dev/null
+++ b/es/extensions/budget_and_spend/master/schema/index.html
@@ -0,0 +1,581 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificación de presupuesto y gasto +
+ ++ Extiende el desglose de presupuesto y la implementación de contrato para permitir la publicación del detalle de las asignaciones de presupuesto y la ejecución del proceso de contrataciones, utilizando las clasificaciones que pueden mapearse a datos de presupuesto y de gasto que fueron publicados de forma separada. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La extensión de Presupuestos y Gastos extiende la extensión de budget breakdown y la sección de implementación del contrato para permitir la publicación de asignaciones de presupuesto detalladas y la ejecución de las mismas para un proceso de contrataciones
+Un artículo de discusión que muestra los antecedentes del enfoque puede encontrarse aquí.
+Este repositorio se encuentra activamente en desarrollo, y actualmente contiene un ejemplo de cómo puede ser usada esta extensión para registrar compromisos financieros anuales de un proceso de contratación y contratos individuales.
+En resumen
+Esta extensión introduce tres nuevas funciones que surgen de la extensión budget breakdown:
+-
+
classificationspermiten que se den clasificaciones funcionales, económicas y administrativas para cada detalle del presupuesto;
+measures- permite que se usen diferentes medidas de presupuesto (planeadas, cometidas, ejecutadas, etc.) a nivel del proceso de contrataciones para cada set de clasificaciones de presupuesto
+fiscalBreakdownFieldMapping- provee una manera de vincular a un Paquete de Datos Fiscales, un archivo datapackage.json, que define el significado de cada clasificación y medida, y provee acceso a datos relacionados a nivel presupuestario.
+
Adicionalmente, introduce el objeto financialProgress en contracts/implementation, permitiendo mostrar el detalle de la ejecución financiera de cada contrato, utilizando los mismos atributos classifications, measures y fiscalBreakdownFieldMapping como para budgetBreakdown.
Para comenzar
+La mejor manera de utilizar esta extensión es viendo los ejemplos desarrollados.
+-
+
- El ejemplo de coordinación muestra como expresar los datos en una asignación presupuestaria y ejecución que pudieron haber surgido de diferentes sistemas de datos (ej. sistemas financieros y sistemas de compras). +
- El ejemplo de integración muestra como las referencias a un Paquete de Datos Fiscales pueden permitir la visualización de datos a los usuarios, y la comparación entre los datos a nivel de proceso de contrataciones y de presupuesto. +
- El ejemplo de datos planos muestra como usando esta extensión pueden ser analizados los datos estructurados publicados con herramientas de hojas de cálculo. +
Conceptos claves
+Esta extensión da las herramientas para crear datos que relacionen budgets, contracting processes y spending
+A partir de las definiciones de Global Initiative for Fiscal Transparency (GIFT):
+Un presupuesto es una declaración a futuro de como una organización propone aumentar sus ingresos, utilizar sus recursos y financiar sus operaciones. El presupuesto del Gobierno Nacional debe cubrir todas las actividades de un estado. Los presupuestos detallados pueden existir también a nivel de agencias y proyectos. En las contrataciones públicas, el fondo para un proceso de contratación puede provenir de una sección particular del Presupuesto Nacional, o de un presupuesto organizacional. Podría también provenir por completo o parcialmente de un fondo externo (Ej. el Banco Internacional de Desarrollo), ya sea directamente o a través de sistemas gubernamentales.
+Las líneas de presupuesto se construyen a partir de un set de classifications (generalmente descritas en términos de clasificaciones funcional, administrativas o económicas) y las measures (como el monto original designado a un conjunto particular de clasificaciones, o los montos modificados o ejecutados).
+Fiscal reports are records of [an organization's] actual (historical) revenues, spending and financing. They may report the fiscal activities of the central government, state governments, or local governments, or of all levels of government in a country (referred to as the general government). Reports may cover a whole government in aggregate as an organization, and/or individual government units, e.g. ministries, departments or agencies. They may be on a cash or accruals basis (full or partial). As payments are made during the execution of a contract, these may be allocated against one or more sections of the budget. In some cases, this may allow the creation of fiscal reporting at the level of individual contracts.
+El Open Contracting Data Standard se usa para compartir información sobre procesos de contrataciones. Un proceso de contrataciones puede pasar por diferentes etapas a través del tiempo, incluyendo planeación, licitación, adjudicación, firma de contrato e implementación.
+Relacionando presupuesto, contrataciones y gasto
+
La imagen anterior presenta un representación esquemática de como pueden interactuar las bases de datos de presupuesto, contratación y gasto
+Debe notar que:
+-
+
- Esto no representa una secuencia linear de eventos. Los datos pueden estar disponibles en diferentes punto en el tiempo, como cuando el presupuesto se hace en un ciclo anual, pero los contratos se firman a través de los años. En muchos casos, la información de presupuesto en la sección de
planningde un proceso de contratación OCDS puede actualizarse después de que los contratos se adjudiquen y se estén implementando.
+ - Los datos de presupuesto y gasto pueden darse en diferentes niveles de detalle, desde una línea de presupuesto única que financia múltiples procesos de contrataciones, hasta la clasificación fiscal de partes únicas contra un contrato en particular. Los publicadores de datos van a variar de acuerdo al nivel de detalle que se puede extraer con confianza de sus sistemas. +
- Los datos de ejecución del presupuesto pueden existir en un nivel transaccional, o puede existir en un nivel más agregado. Esta extensión actualmente cubre la ejecución del presupuesto, pero no cubre las clasificaciones detalladas de las transacciones. +
La siguiente imagen muestra un mapeo entre las etapas de una transacción y las etapas de un proceso de contratación. Las etapas de una transacción son generalmente comunes en diferentes jurisdicciones y reflejan las descritas en el [Paquete de Datos Fiscales] (https://frictionlessdata.io/specs/fiscal-data-package/); sin embargo, es posible que algunas jurisdicciones no registren todas las etapas, algunas pueden utilizar una terminología diferente y algunas pueden tener más etapas.
+![Mapeo del proceso de transacción y contratación] (https://raw.githubusercontent.com/open-contracting-extensions/ocds_budget_and_spend_extension/master/images/transaction-contracting_process.png)
+Los datos combinados cubiertos por esta extensión generalmente se obtienen de los sistemas de adquisiciones y los Sistemas de Información de Gestión Financiera (SIGF). Entre los ejemplos de cómo se pueden integrar dichos sistemas se incluyen:
+-
+
- Antes de iniciar una licitación, el sistema de adquisiciones verifica que los fondos estén disponibles para el proceso de contratación a través del SIGF y crea una reserva en el SIGF. +
- Cuando se firma un contrato, el sistema de adquisiciones crea un compromiso en el SIGF por el valor del contrato. +
- Cuando se completa un hito o entregable de un contrato, el sistema de adquisiciones crea una verificación o devengado en el SIGF. +
Estándares de datos unidos: conexiones con el paquete de datos fiscales
+El Fiscal Data Package desarrollado por Open Knowledge con el apoyo de GIFT da un "formato sencillo y orientado al usuario para publicar y consumir datos fiscales". A diferencia del OCDS, el cual requiere que los datos se conviertan en una estructura JSON antes de publicarse, el Paquete de Datos Fiscales consiste de:
+-
+
- Una definición de paquete de datos (datapackage.json) el cual describe el 'modelo lógico' para aplicar a los archivos de datos existentes. Esto define las columnas, su relación con los conceptos fiscales y cómo deben transformarse mediante el consumo de aplicaciones para crear datos normalizados. +
- Los archivos de datos, que dan el 'modelo físico' para la base de datos de presupuesto o de gastos, y puede ser exportado de los sistemas existentes. +
Se ha hecho bastante investigación y pruebas con usuarios para desarrollar el Paquete de Datos Fiscales, estableciendo que, en vez de buscar un acuerdo en un set global de conceptos fiscales, es importante, considerando la diversidad de sistemas de compras y presupuesto alrededor del mundo, permitir a los usuarios publicar sus datos utilizando sus conceptos fiscales existentes, y luego complementar estos con datos adicionales que pueden apoyar el análisis y la comparación entre bases de datos.
+Para evitar la duplicación de esfuerzos por parte de los editores y consumidores de datos, esta extensión difiere del modelo del Paquete de Datos Fiscales con respecto a la definición de conceptos fiscales y sigue el enfoque del FDP de permitir el uso de nombres de columnas de datos existentes. Si bien el FDP no hace una distinción directa entre "clasificaciones" y "medidas", considerando que ambas son instancias de "conceptos fiscales", en esta extensión sí trazamos una distinción para permitir que las medidas se validen como numéricas, mientras que las clasificaciones pueden pueden ser cadenas o números.
+Antecedentes
+Una exploración completa del enfoque que se toma en esta extensión se puede encontrar en el background discussion paper.
+Historias de usuarios y requisitos
+Esta extensión fue diseñada en base a un conjunto de historias de usuario.
+-
+
- U1: Como periodista quiero ver cuál es la fuente de presupuesto de un proceso de contratación particular para poder entender si el presupuesto viene de recursos domésticos, préstamos u otras fuentes de ingreso internacionales +
- U2: Como periodista, quiero encontrar todos los contratos financiados a través de una fuente de presupuesto en particular para analizar en qué medida se gasta el presupuesto a través de la contratación u otros medios. +
- U3: Como organización de la sociedad civil enfocada en infraestructura quiero encontrar todos los procesos de contratación relacionados con un determinado programa o proyecto de infraestructura para poder realizar una revisión del cumplimiento de los requisitos de transparencia del proyecto de infraestructura. +
- U4: Como periodista, quiero hacer un seguimiento de los contratos (sospechosos) para identificar posibles conexiones entre los destinatarios y los funcionarios y políticos que controlan los procesos de presupuestación y adjudicación. +
Identificar y confirmar asignaciones presupuestarias:
+-
+
- U5: Como un proveedor potencial quiero ver cuando se confirma la disponibilidad de presupuesto para un proceso de contrataciones especifico para poder planear un inventario de potenciales oportunidades de licitación. +
- U6: Como organización de monitoreo de la sociedad civil, quiero identificar proyectos sin un presupuesto confirmado para poder analizar la brecha de financiamiento de las adquisiciones planificadas. +
- U7: Como un oficial de tesorería quiero compartir información sobre el estatus de las asignaciones de presupuesto y el gasto para cualquier contrato para poder demostrar al público que el presupuesto se esta gastando de acuerdo a los planes aprobados +
- U8: Como un monitor de compras quiero ver que parte del proyecto de infraestructura viene del presupuesto de capital vs el presupuesto de ingresos para poder monitorear si se gasto de más o de menos de lo planeado +
- U9: Como organización de la sociedad civil, quiero identificar hasta qué punto se han asignado gastos en determinadas líneas presupuestarias y el estado de ese gasto a lo largo del tiempo para poder informar sobre las áreas de gasto excesivo o insuficiente. +
Siguiendo el proceso de pagos:
+-
+
- U10: Como académico, quiero identificar la brecha entre la fecha de la factura y la fecha de pago para poder analizar cómo los precios se ven afectados por los plazos de pago. +
- U11: Como auditor quiero los detalles completos sobre el proceso de cobro y de pago para poder identificar banderas rojas potenciales e investigar los procesos particulares +
Estas historias de usuario se utilizaron para identificar un conjunto de requisitos que la extensión debería cumplir. La siguiente lista describe hasta qué punto la extensión actual cumple con los requisitos que se identificaron.
+-
+
- R1: Identificar inequívocamente cada línea del presupuesto.
+
-
+
- ¿Requisito cumplido?: Sí. El Desglose de Presupuesto se amplía con un objeto flexible
classificationsque puede incluir cualquier número de campos de clasificación, reflejando los términos y nombres de columnas utilizados en los conjuntos de datos presupuestarios.
+
+ - ¿Requisito cumplido?: Sí. El Desglose de Presupuesto se amplía con un objeto flexible
- R2: Identificar inequívocamente los proyectos que aportan financiación a un proceso de contratación.
+
-
+
- ¿Requisito cumplido?: Parcialmente. Actualmente no se han introducido cambios para cumplir este caso de uso. El objeto presupuesto básico ya incluye un campo
projectID.
+
+ - ¿Requisito cumplido?: Parcialmente. Actualmente no se han introducido cambios para cumplir este caso de uso. El objeto presupuesto básico ya incluye un campo
- R3: Proveer los montos de las diferentes fases del presupuesto incluyendo las asignaciones presupuestarias confirmadas.
+
-
+
- ¿Requisito cumplido?: Sí. El Desglose de Presupuesto se amplía con un objeto flexible de
measuresque puede incluir cualquier número de campos de medida, reflejando los términos y nombres de columnas utilizados en los conjuntos de datos de presupuesto y gasto existentes.
+
+ - ¿Requisito cumplido?: Sí. El Desglose de Presupuesto se amplía con un objeto flexible de
- R4: Clasificar transacciones contra líneas presupuestarias
+
-
+
- ¿Requisito cumplido?: No. La información desglosada del progreso financiero puede clasificarse en las líneas presupuestarias en la sección de implementación del contrato
financialProgress.breakdown, pero la extensión no modifica actualmente el bloque detransactionspara permitir la clasificación a nivel de transacciones individuales.
+
+ - ¿Requisito cumplido?: No. La información desglosada del progreso financiero puede clasificarse en las líneas presupuestarias en la sección de implementación del contrato
- R5: Proporcionar información sobre el proceso de transacción, desde la factura hasta el pago.
+
-
+
- ¿Requisito cumplido?: Parcialmente. Las
measuresenfinancialProgress.breakdownpara cada contrato se pueden utilizar para describir diferentes momentos del procesamiento del pago. Sin embargo, esto solo proporciona un historial completo de la sincronización de los procesos de pago cuando se usa con un historial de versiones detallado de las entregas. En esta extensión no se ha incluido un enfoque alternativo de agregar detalles detransactionspara representar diferentes momentos, como solicitudes de pago y aprobaciones de pago, pero puede desarrollarse por separado en el futuro.
+
+ - ¿Requisito cumplido?: Parcialmente. Las
- R6: Permitir que las asignaciones de montos individuales del presupuesto a contraer dentro de OCDS se verifiquen con las asignaciones generales de la línea presupuestaria en un conjunto de datos presupuestarios
+
-
+
- ¿Requisito cumplido?: Sí. Mediante el uso de un enlace al Paquete de Datos Fiscales, es posible comparar la información financiera a nivel de contrato en OCDS con información clasificada de manera similar en un FDP. +
+ - R7: Proporcionar interfaces con la información necesaria para mostrar información presupuestaria a los usuarios.
+
-
+
- ¿Requisito cumplido?: Sí. Cuando se usan en conjunto con un Paquete de Dato Fiscal, las aplicaciones pueden buscar etiquetas y meta datos para cada
classificationsymeasuresde manera a mostrar claramente la información a los usuarios.
+
+ - ¿Requisito cumplido?: Sí. Cuando se usan en conjunto con un Paquete de Dato Fiscal, las aplicaciones pueden buscar etiquetas y meta datos para cada
Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-06-04
+-
+
- Revisar las palabras normativas y no-normativas +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-03-20
+-
+
- Establecer
"uniqueItems ": trueen los campos de la matriz y agregar"minLength": 1en los campos de cadena obligatorios.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/charges/index.html b/es/extensions/charges/index.html
new file mode 100644
index 000000000..bc769bf05
--- /dev/null
+++ b/es/extensions/charges/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificación de presupuesto y gasto +
+ ++ Extiende el desglose de presupuesto y la implementación de contrato para permitir la publicación del detalle de las asignaciones de presupuesto y la ejecución del proceso de contrataciones, utilizando las clasificaciones que pueden mapearse a datos de presupuesto y de gasto que fueron publicados de forma separada. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ financialProgress
+
+ |
+ + Progreso financiero + | +
+ La sección de progreso financiero permite publicar información de alto nivel y detallada sobre montos asignados o gastados hasta la fecha para este contrato en particular. Esto puede usarse junto a la sección de transacciones, la cual permite que se registren detalles de cada pago individual. + + |
+ + object + | +
+
+ financialProgress.
+ |
+ + Gasto total + | +
+ El gasto total de este contrato a la fecha de la última actualización. Tenga en cuenta que la medida fiscal exacta que representa este número puede variar dependiendo del publicador de los datos (ej. monto facturado vs monto transferido al banco del proveedor). + + |
+ + Value object + | +
+
+ financialProgress.
+ |
+ + Medidas + | +
+ La sección de medidas reporta valores agregados del progreso financiero para este contrato (ie. sin el desglose de clasificación de presupuesto. Las medidas se deben de dar como un set de pares clave-valor, donde la clave debe ser el nombre de la medida utilizada dentro de una base de datos del Paquete de Datos Fiscales u otra base de datos de presupuesto y gasto. El valor es el valor de esta medida la última vez que fue actualizada y debe de darse como un número en la misma moneda que cualquier reporte agregado de presupuesto o figuras de gasto. + + |
+ + object + | +
+
+ financialProgress.
+ |
+ + + | ++ + | ++ number + | +
+
+ financialProgress.
+ |
+ + Desglose de progreso financiero + | +
+ Esta sección contienen un desglose del progreso financiero, permitiendo que varias medidas (monto facturado, monto acumulado, monto pagado, etc) se desglosen por fuente, período y clasificación de presupuesto + + |
+ + array of FinancialProgressBreakdown objects + | +
+ FinancialProgressBreakdown +
+ +
+ The extension defines a new FinancialProgressBreakdown object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador para esta entrada de desglose de progreso financiero particular + + |
+ + string or integer + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Un texto breve de descripción de este desglose de progreso financiero. Esto puede visualizarse en una interfaz de usuarios que interprete esta entrada. Puede ser generada automáticamente como datos estructurados o pueden ser ingresados manualmente. + + |
+ + string + | +
+
+ period
+
+ |
+ + Período de Presupuesto + | +
+ El período cubierto por la entrada de desglose de progreso financiero. Esta información también puede ser duplicada utilizando clasificaciones cuando sea relevante. + + |
+ + Period object + | +
+
+ classifications
+
+ |
+ + Clasificaciones de presupuesto + | +
+ Las clasificaciones de presupuesto deben de darse como un conjunto de pares clave-valor, donde la clave es la dimensión (o el nombre de la dimensión) usada en la clasificación de presupuesto, y el valor es el valor de esa dimensión en el proceso de contrataciones o en el contrato específico (dependiendo del punto en el archivo OCDS en el cual se da la clasificación). + + |
+ + object + | +
+
+ classifications.
+ |
+ + + | ++ + | ++ string or number + | +
+
+ measures
+
+ |
+ + medidas + | +
+ Las medidas deben de dar un conjunto de pares clave-valor, donde la clave debe ser el nombre de una medida utilizada en la base de datos del Paquete de Datos Fiscales o en otras bases de datos de presupuesto y gasto. El valor es el valor de esta medida en la última actualización, y debe de darse como un número en la misma moneda que en cualquier reporte de presupuesto agregado o valores de gasto. + + |
+ + object + | +
+
+ measures.
+ |
+ + + | ++ + | ++ number + | +
+
+ fiscalBreakdownFieldMapping
+
+ |
+ + + | ++ + | ++ FiscalBreakdownFieldMapping object + | +
+ BudgetBreakdown +
+ +
+ The extension defines these fields in the BudgetBreakdown object from the Desglose del presupuesto extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ classifications
+
+ |
+ + Clasificaciones de presupuesto + | +
+ Las clasificaciones de presupuesto deben de darse como un conjunto de pares clave-valor, donde la clave es la dimensión (o el nombre de la dimensión) usada en la clasificación de presupuesto, y el valor es el valor de esa dimensión en el proceso de contrataciones o en el contrato específico (dependiendo del punto en el archivo OCDS en el cual se da la clasificación). + + |
+ + object + | +
+
+ classifications.
+ |
+ + + | ++ + | ++ string or number + | +
+
+ measures
+
+ |
+ + medidas + | +
+ Las medidas deben de dar un conjunto de pares clave-valor, donde la clave debe ser el nombre de una medida utilizada en la base de datos del Paquete de Datos Fiscales o en otras bases de datos de presupuesto y gasto. El valor es el valor de esta medida en la última actualización, y debe de darse como un número en la misma moneda que en cualquier reporte de presupuesto agregado o valores de gasto. + + |
+ + object + | +
+
+ measures.
+ |
+ + + | ++ + | ++ number + | +
+
+ fiscalBreakdownFieldMapping
+
+ |
+ + + | ++ + | ++ FiscalBreakdownFieldMapping object + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/charges/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/charges/master/extension.json b/es/extensions/charges/master/extension.json
new file mode 100644
index 000000000..a72aaab12
--- /dev/null
+++ b/es/extensions/charges/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Charges",
+ "es": "Cargos"
+ },
+ "description": {
+ "en": "Adds a charges array to the implementation object to disclose the charges to be incurred by users or government in a given period of a contract.",
+ "es": "Agrega una matriz de cargos al objeto de implementaci\u00f3n para publicar los cargos en que incurrir\u00e1n los usuarios o el gobierno en un per\u00edodo determinado de un contrato."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/charges/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "chargePaidBy.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/charges/master/index.html b/es/extensions/charges/master/index.html
new file mode 100644
index 000000000..f392abf4c
--- /dev/null
+++ b/es/extensions/charges/master/index.html
@@ -0,0 +1,351 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cargos +
+ ++ Agrega una matriz de cargos al objeto de implementación para publicar los cargos en que incurrirán los usuarios o el gobierno en un período determinado de un contrato. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ chargePaidBy.csv +
+ +
+ You can download the chargePaidBy.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ government
+
+ |
+ + Government + | +
+ The charge is paid by the government + + |
+
+
+ user
+
+ |
+ + User + | +
+ The charge is paid by businesses or citizens using the facilities provided by the contract + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/charges/master/release-schema.json b/es/extensions/charges/master/release-schema.json
new file mode 100644
index 000000000..cf640ab0d
--- /dev/null
+++ b/es/extensions/charges/master/release-schema.json
@@ -0,0 +1,83 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "charges": {
+ "title": "Cargos",
+ "description": "Informaci\u00f3n sobre los ingresos que se recaudar\u00e1n a trav\u00e9s de cobros, seg\u00fan lo estipulado en el contrato o revisado posteriormente durante la vida del proyecto.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Charge"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Charge": {
+ "title": "Cargo",
+ "description": "Un cargo a ser incurrido por los usuarios o el gobierno durante el curso del contrato. La informaci\u00f3n del cargo se puede desglosar por per\u00edodo. La informaci\u00f3n sobre los precios unitarios en los que se basan los valores totales puede proporcionarse en la secci\u00f3n de tarifas.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador de cargo",
+ "description": "Un identificador local para esta cargo espec\u00edfico. Este campo se utiliza para realizar un seguimiento de las revisiones de un cargo a trav\u00e9s de varias publicaciones OCDS.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo del cargo",
+ "description": "Un t\u00edtulo descriptivo para este cobro,",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "paidBy": {
+ "title": "Pagado por",
+ "description": "\u00bfSe trata de un cargo de usuario (pagado por empresas o ciudadanos que utilizan las facilidades proporcionadas por el contrato), o un cargo pagado por el gobierno?",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "chargePaidBy.csv",
+ "openCodelist": false,
+ "enum": [
+ "government",
+ "user",
+ null
+ ]
+ },
+ "period": {
+ "title": "Periodo",
+ "description": "El per\u00edodo al que se aplica este cargo.",
+ "$ref": "#/definitions/Period"
+ },
+ "estimatedValue": {
+ "title": "Valor estimado",
+ "description": "Cu\u00e1l es el valor total estimado que se levantar\u00e1 de este cargo durante este per\u00edodo.",
+ "$ref": "#/definitions/Value"
+ },
+ "actualValue": {
+ "title": "Valor real",
+ "description": "En la secci\u00f3n de implementaci\u00f3n, este campo puede ser actualizado con los ingresos totales recaudados de este cobro durante este per\u00edodo.",
+ "$ref": "#/definitions/Value"
+ },
+ "notes": {
+ "title": "Notas",
+ "description": "Cualquier nota sobre este cargo. Esto puede incluir informaci\u00f3n para aclaraci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/charges/master/schema/index.html b/es/extensions/charges/master/schema/index.html
new file mode 100644
index 000000000..0cd07939d
--- /dev/null
+++ b/es/extensions/charges/master/schema/index.html
@@ -0,0 +1,393 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cargos +
+ ++ Agrega una matriz de cargos al objeto de implementación para publicar los cargos en que incurrirán los usuarios o el gobierno en un período determinado de un contrato. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La extensión de cargos se utiliza para registrar detalles de los cargos totales estimados o aplicados a los usuarios o al gobierno durante la operación de un contrato de Asociación Público Privada.
+Esto puede utilizarse para proporcionar un desglose del apoyo gubernamental a un proyecto, sobre una base de período por período.
+La extensión de cargos introduce una lista charges al objeto contracts.implementation.
Ejemplo
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "title": "Public Private Partnership Agreement",
+ "description": "Public-Private Partnership agreement entered into by and between telecoms promoter, together with national fibre infrastructure and the special purpose vehicle Mega Consortium Ltd",
+ "implementation": {
+ "charges": [
+ {
+ "id": "2025-user",
+ "title": "User charges for calendar year 2025 resulting from 4G, 3G, voice and SMS tariffs",
+ "estimatedValue": {
+ "amount": 1019100000,
+ "currency": "USD"
+ },
+ "paidBy": "user",
+ "period": {
+ "startDate": "2025-01-01T00:00:00Z",
+ "endDate": "2025-12-31T23:59:59Z"
+ }
+ },
+ {
+ "id": "2026-user",
+ "title": "User charges for calendar year 2026 resulting from 4G, 3G, voice and SMS tariffs",
+ "estimatedValue": {
+ "amount": 1129206411.9632988,
+ "currency": "USD"
+ },
+ "paidBy": "user",
+ "period": {
+ "startDate": "2026-01-01T00:00:00Z",
+ "endDate": "2026-12-31T23:59:59Z"
+ }
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-03-20
+-
+
- Establecer
"uniqueItems ": trueen los campos matriz y agregar"minLength": 1en los campos de cadena obligatorios.
+
2018-05-08
+-
+
- Hacer que
Charge.idsea obligatorio para soportar el seguimiento de revisiones y fusión de listas
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/charges/v1.1/README.md b/es/extensions/charges/v1.1/README.md
new file mode 100644
index 000000000..2de4fa309
--- /dev/null
+++ b/es/extensions/charges/v1.1/README.md
@@ -0,0 +1,18 @@
+# Cargos
+
+La extensión de cargos se utiliza para registrar detalles de los **cargos totales** estimados o aplicados a los usuarios o al gobierno durante la operación de un contrato de Asociación Público Privada.
+
+Esto puede utilizarse para proporcionar un desglose del **apoyo gubernamental** a un proyecto, sobre una base de período por período.
+
+## Resumen
+
+La extensión Cargos introduce una propiedad `charges` tanto para`Contract` como para `Contract/Implementation`.
+
+Contiene una matriz de objetos `Charge` con propiedades para:
+
+- `title` - título descriptivo del cargo;
+- `paidBy` - ya sea 'gobierno' o 'usuario';
+- `period`: la fecha de inicio y de finalización del período cubierto por el cargo;
+- `estimatedValue` - el valor total previsto de este cargo durante el período;
+- `actualValue` - el valor real (actualizado después de finalizado el período) del cargo durante el período;
+- `notes` - información adicional sobre el cargo;
diff --git a/es/extensions/charges/v1.1/codelists/index.html b/es/extensions/charges/v1.1/codelists/index.html
new file mode 100644
index 000000000..affacdf57
--- /dev/null
+++ b/es/extensions/charges/v1.1/codelists/index.html
@@ -0,0 +1,5 @@
+
+
+
+
+
+
+
+ + Cargos +
+ ++ Agrega una matriz de cargos al objeto de implementación para publicar los cargos en que incurrirán los usuarios o el gobierno en un período determinado de un contrato. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ charges
+
+ |
+ + Cargos + | +
+ Información sobre los ingresos que se recaudarán a través de cobros, según lo estipulado en el contrato o revisado posteriormente durante la vida del proyecto. + + |
+ + array of Charge objects + | +
+ Charge +
+ +
+ The extension defines a new Charge object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador de cargo + | +
+ Un identificador local para esta cargo específico. Este campo se utiliza para realizar un seguimiento de las revisiones de un cargo a través de varias publicaciones OCDS. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título del cargo + | +
+ Un título descriptivo para este cobro, + + |
+ + string + | +
+
+ paidBy
+
+ |
+ + Pagado por + | +
+ ¿Se trata de un cargo de usuario (pagado por empresas o ciudadanos que utilizan las facilidades proporcionadas por el contrato), o un cargo pagado por el gobierno? + + |
+ + string from closed chargePaidBy codelist + | +
+
+ period
+
+ |
+ + Periodo + | +
+ El período al que se aplica este cargo. + + |
+ + Period object + | +
+
+ estimatedValue
+
+ |
+ + Valor estimado + | +
+ Cuál es el valor total estimado que se levantará de este cargo durante este período. + + |
+ + Value object + | +
+
+ actualValue
+
+ |
+ + Valor real + | +
+ En la sección de implementación, este campo puede ser actualizado con los ingresos totales recaudados de este cobro durante este período. + + |
+ + Value object + | +
+
+ notes
+
+ |
+ + Notas + | +
+ Cualquier nota sobre este cargo. Esto puede incluir información para aclaración. + + |
+ + string + | +
Not Found
+The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
diff --git a/es/extensions/charges/v1.1/extension.json b/es/extensions/charges/v1.1/extension.json new file mode 100644 index 000000000..6c298817c --- /dev/null +++ b/es/extensions/charges/v1.1/extension.json @@ -0,0 +1,15 @@ +{ + "name": { + "en": "Charges", + "es": "Cargos" + }, + "description": { + "en": "The charges extension is used to record details of the **total** charges that are estimated or applied to users or government during the operation of a Public Private Partnership contract.", + "es": "La extensi\u00f3n de cargos se utiliza para registrar detalles de los **cargos totales** estimados o aplicados a los usuarios o al gobierno durante la operaci\u00f3n de un contrato de Asociaci\u00f3n P\u00fablico Privada." + }, + "compatibility": [ + "1.1" + ], + "dependencies": [], + "documentationUrl": {} +} diff --git a/es/extensions/charges/v1.1/index.html b/es/extensions/charges/v1.1/index.html new file mode 100644 index 000000000..649ef7d86 --- /dev/null +++ b/es/extensions/charges/v1.1/index.html @@ -0,0 +1,274 @@ + + + + + + + + + +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/charges/v1.1/release-schema.json b/es/extensions/charges/v1.1/release-schema.json
new file mode 100644
index 000000000..49b13ff44
--- /dev/null
+++ b/es/extensions/charges/v1.1/release-schema.json
@@ -0,0 +1,71 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "charges": {
+ "type": "array",
+ "title": "Cargos",
+ "description": "Informaci\u00f3n sobre los ingresos que se recaudar\u00e1n a trav\u00e9s de cobros, seg\u00fan lo estipulado en el contrato o revisado posteriormente durante la vida del proyecto.",
+ "items": {
+ "$ref": "#/definitions/Charge"
+ }
+ }
+ }
+ },
+ "Charge": {
+ "type": "object",
+ "title": "Cargo",
+ "description": "Un cargo a ser incurrido por los usuarios o el gobierno durante el curso del contrato. La informaci\u00f3n del cargo se puede desglosar por per\u00edodo. La informaci\u00f3n sobre los precios unitarios en los que se basan los valores totales puede proporcionarse en la secci\u00f3n de tarifas.",
+ "properties": {
+ "id": {
+ "title": "Identificador de cargo",
+ "description": "Un identificador local para esta cargo espec\u00edfico. Este campo se utiliza para realizar un seguimiento de las revisiones de un cargo a trav\u00e9s de varias publicaciones OCDS.",
+ "type": "string"
+ },
+ "title": {
+ "title": "T\u00edtulo del cargo",
+ "description": "Un t\u00edtulo descriptivo para este cobro,",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "paidBy": {
+ "title": "Pagado por",
+ "description": "\u00bfSe trata de un cargo de usuario (pagado por empresas o ciudadanos que utilizan las facilidades proporcionadas por el contrato), o un cargo pagado por el gobierno?",
+ "type": [
+ "string",
+ "null"
+ ],
+ "enum": [
+ "government",
+ "user"
+ ]
+ },
+ "period": {
+ "title": "Periodo",
+ "description": "El per\u00edodo al que se aplica este cargo.",
+ "$ref": "#/definitions/Period"
+ },
+ "estimatedValue": {
+ "title": "Valor estimado",
+ "description": "Cu\u00e1l es el valor total estimado que se levantar\u00e1 de este cargo durante este per\u00edodo.",
+ "$ref": "#/definitions/Value"
+ },
+ "actualValue": {
+ "title": "Valor real",
+ "description": "En la secci\u00f3n de implementaci\u00f3n, este campo puede ser actualizado con los ingresos totales recaudados de este cobro durante este per\u00edodo.",
+ "$ref": "#/definitions/Value"
+ },
+ "notes": {
+ "title": "Notas",
+ "description": "Cualquier nota sobre este cargo. Esto puede incluir informaci\u00f3n para aclaraci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/charges/v1.1/schema/index.html b/es/extensions/charges/v1.1/schema/index.html
new file mode 100644
index 000000000..6fc362727
--- /dev/null
+++ b/es/extensions/charges/v1.1/schema/index.html
@@ -0,0 +1,388 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cargos +
+ ++ Agrega una matriz de cargos al objeto de implementación para publicar los cargos en que incurrirán los usuarios o el gobierno en un período determinado de un contrato. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La extensión de cargos se utiliza para registrar detalles de los cargos totales estimados o aplicados a los usuarios o al gobierno durante la operación de un contrato de Asociación Público Privada.
+Esto puede utilizarse para proporcionar un desglose del apoyo gubernamental a un proyecto, sobre una base de período por período.
+Resumen
+La extensión Cargos introduce una propiedad charges tanto paraContract como para Contract/Implementation.
Contiene una matriz de objetos Charge con propiedades para:
-
+
title- título descriptivo del cargo;
+paidBy- ya sea 'gobierno' o 'usuario';
+period: la fecha de inicio y de finalización del período cubierto por el cargo;
+estimatedValue- el valor total previsto de este cargo durante el período;
+actualValue- el valor real (actualizado después de finalizado el período) del cargo durante el período;
+notes- información adicional sobre el cargo;
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/communication/index.html b/es/extensions/communication/index.html
new file mode 100644
index 000000000..223d729a2
--- /dev/null
+++ b/es/extensions/communication/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cargos +
+ ++ Agrega una matriz de cargos al objeto de implementación para publicar los cargos en que incurrirán los usuarios o el gobierno en un período determinado de un contrato. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ charges
+
+ |
+ + Cargos + | +
+ Información sobre los ingresos que se recaudarán a través de cobros, según lo estipulado en el contrato o revisado posteriormente durante la vida del proyecto. + + |
+ + array of Charge objects + | +
+ Charge +
+ +
+ The extension defines a new Charge object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador de cargo + | +
+ Un identificador local para esta cargo específico. Este campo se utiliza para realizar un seguimiento de las revisiones de un cargo a través de varias publicaciones OCDS. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título del cargo + | +
+ Un título descriptivo para este cobro, + + |
+ + string + | +
+
+ paidBy
+
+ |
+ + Pagado por + | +
+ ¿Se trata de un cargo de usuario (pagado por empresas o ciudadanos que utilizan las facilidades proporcionadas por el contrato), o un cargo pagado por el gobierno? + + |
+ + string + | +
+
+ period
+
+ |
+ + Periodo + | +
+ El período al que se aplica este cargo. + + |
+ + Period object + | +
+
+ estimatedValue
+
+ |
+ + Valor estimado + | +
+ Cuál es el valor total estimado que se levantará de este cargo durante este período. + + |
+ + Value object + | +
+
+ actualValue
+
+ |
+ + Valor real + | +
+ En la sección de implementación, este campo puede ser actualizado con los ingresos totales recaudados de este cobro durante este período. + + |
+ + Value object + | +
+
+ notes
+
+ |
+ + Notas + | +
+ Cualquier nota sobre este cargo. Esto puede incluir información para aclaración. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/communication/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/communication/master/release-schema.json b/es/extensions/communication/master/release-schema.json
new file mode 100644
index 000000000..29052eb90
--- /dev/null
+++ b/es/extensions/communication/master/release-schema.json
@@ -0,0 +1,80 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "communication": {
+ "title": "Comunicaci\u00f3n",
+ "description": "Modalidades de comunicaci\u00f3n sobre eventos clave.",
+ "$ref": "#/definitions/Communication"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "communication": {
+ "title": "Comunicaci\u00f3n",
+ "description": "Modalities of communication about key events for this lot.",
+ "$ref": "#/definitions/Communication"
+ }
+ }
+ },
+ "Communication": {
+ "title": "Comunicaci\u00f3n",
+ "description": "Modalidades de comunicaci\u00f3n sobre eventos clave.",
+ "type": "object",
+ "properties": {
+ "atypicalToolName": {
+ "title": "Atypical tool name",
+ "description": "The name of the tools and devices that are not generally available and that are required to communicate electronically with the buyer.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "atypicalToolUrl": {
+ "title": "URL de herramienta at\u00edpica",
+ "description": "The URL of the tools and devices that are not generally available and that are required to communicate electronically with the buyer.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "noticePreferredPublicationDate": {
+ "title": "Notice preferred publication date",
+ "description": "The buyer's preferred date of publication of the notice (e.g. to avoid publication during a national holiday).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "futureNoticeDate": {
+ "title": "Fecha de notificaci\u00f3n futura",
+ "description": "The estimated date of publication of the next sequential notice. For example, the next sequential notice for a planning notice might be a competition notice.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "invitationToConfirmInterestDispatchDate": {
+ "title": "Invitation to confirm interest dispatch date",
+ "description": "The estimated date of dispatch from the buyer to potential suppliers of the invitations to confirm interest. For example, when a planning notice is used as a call for competition, the buyer might simultaneously invite the potential suppliers that have expressed their interest to confirm their continuing interest.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "documentAvailabilityPeriod": {
+ "title": "Per\u00edodo de disponibilidad del documento",
+ "description": "El per\u00edodo durante el cual los documentos pueden ser accedidos o durante el cual se pueden presentar peticiones de acceso a los documentos.",
+ "$ref": "#/definitions/Period"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/communication/master/schema/index.html b/es/extensions/communication/master/schema/index.html
new file mode 100644
index 000000000..21d12adb0
--- /dev/null
+++ b/es/extensions/communication/master/schema/index.html
@@ -0,0 +1,418 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Comunicación +
+ ++ Agrega a la licitación un objeto comunicación para describir las modalidades de comunicación de los eventos claves. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a communication object to the tender and lot objects, to describe the modalities of communication about key events.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Contexto legal
+In the European Union, this extension's fields correspond to eForms BT-124, BT-127, BT-631, BT-632 and BT-738.For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+Tender
+An example of a planning notice from which a competition notice will follow.
+{
+ "tender": {
+ "communication": {
+ "atypicalToolName": "ACertainTool",
+ "atypicalToolUrl": "https://ecomm-procurement.example.net",
+ "futureNoticeDate": "2020-06-17T00:00:00+01:00",
+ "noticePreferredPublicationDate": "2020-03-15T00:00:00+01:00",
+ "documentAvailabilityPeriod": {
+ "startDate": "2020-06-15T00:00:00+01:00",
+ "endDate": "2020-07-10T00:00:00+01:00"
+ }
+ }
+ }
+}
+Lot
+An example of a planning notice that is used as a call for competition and that is divided into lots.
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "communication": {
+ "atypicalToolName": "ACertainTool",
+ "atypicalToolUrl": "https://ecomm-procurement.example.net",
+ "noticePreferredPublicationDate": "2020-03-15T00:00:00+01:00",
+ "documentAvailabilityPeriod": {
+ "startDate": "2020-06-15T00:00:00+01:00",
+ "endDate": "2020-07-10T00:00:00+01:00"
+ },
+ "invitationToConfirmInterestDispatchDate": "2020-11-15T09:00:00+01:00"
+ }
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-03-09
+-
+
- Add fields:
+
-
+
Communication.atypicalToolName
+Communication.invitationToConfirmInterestDispatchDate
+Communication.noticePreferredPublicationDate
+Lot.communication
+
+
2021-01-19
+-
+
- Agregar el campo
tender.communication.documentAvailabilityPeriod
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), en pull resquests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/contractTerms/index.html b/es/extensions/contractTerms/index.html
new file mode 100644
index 000000000..ccaa08dd0
--- /dev/null
+++ b/es/extensions/contractTerms/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Comunicación +
+ ++ Agrega a la licitación un objeto comunicación para describir las modalidades de comunicación de los eventos claves. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ communication
+
+ |
+ + Comunicación + | +
+ Modalidades de comunicación sobre eventos clave. + + |
+ + Communication object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ communication
+
+ |
+ + Comunicación + | +
+ Modalities of communication about key events for this lot. + + |
+ + Communication object + | +
+ Communication +
+ +
+ The extension defines a new Communication object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ atypicalToolName
+
+ |
+ + Atypical tool name + | +
+ The name of the tools and devices that are not generally available and that are required to communicate electronically with the buyer. + + |
+ + string + | +
+
+ atypicalToolUrl
+
+ |
+ + URL de herramienta atípica + | +
+ The URL of the tools and devices that are not generally available and that are required to communicate electronically with the buyer. + + |
+ + string + | +
+
+ noticePreferredPublicationDate
+
+ |
+ + Notice preferred publication date + | +
+ The buyer's preferred date of publication of the notice (e.g. to avoid publication during a national holiday). + + |
+ + string + | +
+
+ futureNoticeDate
+
+ |
+ + Fecha de notificación futura + | +
+ The estimated date of publication of the next sequential notice. For example, the next sequential notice for a planning notice might be a competition notice. + + |
+ + string + | +
+
+ invitationToConfirmInterestDispatchDate
+
+ |
+ + Invitation to confirm interest dispatch date + | +
+ The estimated date of dispatch from the buyer to potential suppliers of the invitations to confirm interest. For example, when a planning notice is used as a call for competition, the buyer might simultaneously invite the potential suppliers that have expressed their interest to confirm their continuing interest. + + |
+ + string + | +
+
+ documentAvailabilityPeriod
+
+ |
+ + Período de disponibilidad del documento + | +
+ El período durante el cual los documentos pueden ser accedidos o durante el cual se pueden presentar peticiones de acceso a los documentos. + + |
+ + Period object + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/contractTerms/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/contractTerms/master/codelists/permission.csv b/es/extensions/contractTerms/master/codelists/permission.csv
new file mode 100644
index 000000000..bb143c252
--- /dev/null
+++ b/es/extensions/contractTerms/master/codelists/permission.csv
@@ -0,0 +1,4 @@
+Código,Título,Descripción
+required,Required,The activity is required.
+allowed,Allowed,The activity is allowed.
+notAllowed,Not allowed,The activity is not allowed.
diff --git a/es/extensions/contractTerms/master/extension.json b/es/extensions/contractTerms/master/extension.json
new file mode 100644
index 000000000..de01f54f9
--- /dev/null
+++ b/es/extensions/contractTerms/master/extension.json
@@ -0,0 +1,29 @@
+{
+ "name": {
+ "en": "Contract terms",
+ "es": "T\u00e9rminos del contrato"
+ },
+ "description": {
+ "en": "Adds a contract terms object to the tender and lot objects, to describe the terms governing the future contract.",
+ "es": "Agrega un objeto t\u00e9rminos del contrato a los objetos de la licitaci\u00f3n y del lote, para describir los t\u00e9rminos que rigen al futuro contrato."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/contractTerms/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "permission.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/es/extensions/contractTerms/master/index.html b/es/extensions/contractTerms/master/index.html
new file mode 100644
index 000000000..ddb0871a9
--- /dev/null
+++ b/es/extensions/contractTerms/master/index.html
@@ -0,0 +1,379 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Términos del contrato +
+ ++ Agrega un objeto términos del contrato a los objetos de la licitación y del lote, para describir los términos que rigen al futuro contrato. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ permission.csv +
+ +
+ You can download the permission.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ required
+
+ |
+ + Required + | +
+ The activity is required. + + |
+
+
+ allowed
+
+ |
+ + Allowed + | +
+ The activity is allowed. + + |
+
+
+ notAllowed
+
+ |
+ + Not allowed + | +
+ The activity is not allowed. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/contractTerms/master/release-schema.json b/es/extensions/contractTerms/master/release-schema.json
new file mode 100644
index 000000000..5e3523ee8
--- /dev/null
+++ b/es/extensions/contractTerms/master/release-schema.json
@@ -0,0 +1,214 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "contractTerms": {
+ "title": "T\u00e9rminos del contrato",
+ "description": "Informaci\u00f3n sobre los t\u00e9rminos que rigen los futuros contratos del procedimiento.",
+ "$ref": "#/definitions/ContractTerms"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "contractTerms": {
+ "title": "T\u00e9rminos del contrato",
+ "description": "Informaci\u00f3n sobre los t\u00e9rminos que rigen los contratos futuros del lote.",
+ "$ref": "#/definitions/ContractTerms"
+ }
+ }
+ },
+ "ContractTerms": {
+ "title": "T\u00e9rminos del contrato",
+ "description": "Informaci\u00f3n sobre los t\u00e9rminos que rigen los contratos futuros.",
+ "type": "object",
+ "properties": {
+ "hasElectronicPayment": {
+ "title": "Pago electr\u00f3nico utilizado",
+ "description": "Si se utiliza el pago electr\u00f3nico.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "hasElectronicOrdering": {
+ "title": "Pedido electr\u00f3nico utilizado",
+ "description": "Si se utiliza el pedido electr\u00f3nico.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "electronicInvoicingPolicy": {
+ "title": "Pol\u00edtica de facturaci\u00f3n electr\u00f3nica",
+ "description": "Si el comprador requerir\u00e1, permitir\u00e1 o no permitir\u00e1 las facturas electr\u00f3nicas.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "permission.csv",
+ "openCodelist": false,
+ "enum": [
+ "required",
+ "allowed",
+ "notAllowed",
+ null
+ ]
+ },
+ "reservedExecution": {
+ "title": "Ejecuci\u00f3n reservada",
+ "description": "Si la ejecuci\u00f3n del contrato se restringe al marco de los programas de empleo protegido",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "performanceTerms": {
+ "title": "Rendimiento de los t\u00e9rminos",
+ "description": "La informaci\u00f3n principal sobre la ejecuci\u00f3n del contrato (por ejemplo, entregables intermediarios, compensaci\u00f3n por da\u00f1os, derechos de propiedad intelectual).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "financialTerms": {
+ "title": "T\u00e9rminos financieros",
+ "description": "La principal informaci\u00f3n sobre financiaci\u00f3n y pago y/o referencia a las disposiciones que las regulan.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "tendererLegalForm": {
+ "title": "Forma jur\u00eddica del licitador",
+ "description": "Una determinada forma jur\u00eddica que debe adoptar un grupo de licitantes que es adjudicado a un contrato.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "hasExclusiveRights": {
+ "title": "Tiene derechos exclusivos",
+ "description": "Un derecho que permite a un operador de servicio p\u00fablico operar ciertos servicios p\u00fablicos de transporte de pasajeros en una ruta o red particular o en un \u00e1rea particular, con exclusi\u00f3n de cualquier otro operador.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "exclusiveRights": {
+ "title": "Derechos exclusivos",
+ "description": "La naturaleza y alcance de los derechos exclusivos otorgados por la entidad contratante al proveedor.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "operatorRevenueShare": {
+ "title": "Reparto de ingresos del operador",
+ "description": "El porcentaje de ingresos por la venta de boletos asignado al proveedor.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0
+ },
+ "otherTerms": {
+ "title": "Otros t\u00e9rminos",
+ "description": "Otros t\u00e9rminos del contrato que no se ajustan a la sem\u00e1ntica de ning\u00fan otro campo OCDS.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "rewardsAndPenalties": {
+ "title": "Recompensas y sanciones",
+ "description": "Informaci\u00f3n sobre recompensas y sanciones relacionadas con los objetivos de calidad.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "socialStandards": {
+ "title": "Est\u00e1ndares sociales",
+ "description": "Los est\u00e1ndares sociales requeridos, por ejemplo: detalle de los derechos contractuales del personal afectado y condiciones en las que se considera que los empleados est\u00e1n vinculados a los servicios.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "hasNonDisclosureAgreement": {
+ "title": "Has non-disclosure agreement",
+ "description": "Whether contract execution requires a non-disclosure agreement.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "nonDisclosureAgreement": {
+ "title": "Non-disclosure agreement",
+ "description": "A description of the non-disclosure agreement required for contract execution.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "customerServices": {
+ "title": "Customer services",
+ "description": "Information about customer service requirements.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/CustomerService"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "CustomerService": {
+ "title": "Customer service",
+ "description": "A customer service requirement.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Type",
+ "description": "The type of this customer service requirement.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "name": {
+ "title": "Name",
+ "description": "A name for this customer service requirement.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "A description of this customer service requirement.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/contractTerms/master/schema/index.html b/es/extensions/contractTerms/master/schema/index.html
new file mode 100644
index 000000000..5300cd898
--- /dev/null
+++ b/es/extensions/contractTerms/master/schema/index.html
@@ -0,0 +1,678 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Términos del contrato +
+ ++ Agrega un objeto términos del contrato a los objetos de la licitación y del lote, para describir los términos que rigen al futuro contrato. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar un objeto términos del contrato a los objetos de la licitación y del lote, para describir los términos que rigen al futuro contrato.
+Guía
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Contexto Legal
+In the European Union, this extension's fields correspond to eForms BG-711 (Contract Terms), BT-801 (Non Disclosure Agreement), BT-802 (Non Disclosure Agreement Description), OPT-071 (Quality Target Code) and OPT-072 (Quality Target Description). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+Tender
+{
+ "tender": {
+ "contractTerms": {
+ "hasElectronicPayment": true,
+ "hasElectronicOrdering": false,
+ "electronicInvoicingPolicy": "required",
+ "reservedExecution": true,
+ "performanceTerms": "A set of KPIs will be developed for this contract and the successful tenderer will be measured against these for the duration of the contract. Please refer to briefing document for further details.",
+ "financialTerms": "In the event that a work referred to in § 2.6 of the Agreement is created as part of the implementation of the Subject Matter of the Agreement, the Contractor shall indicate on the invoice what proportion of the remuneration for implementation.",
+ "tendererLegalForm": "Contractors may jointly apply for the contract.",
+ "hasExclusiveRights": false,
+ "operatorRevenueShare": 0.25,
+ "socialStandards": "The supplier maintains the social, collective bargaining and labor law obligations according to Union law, national law or collective agreements. 4 paragraph 4a Regulation 13707/2007.",
+ "hasNonDisclosureAgreement": true,
+ "nonDisclosureAgreement": "A non-disclosure agreement is required in order to...",
+ "customerServices": [
+ {
+ "type": "clean",
+ "name": "Cleanliness of rolling stock and station facilities",
+ "description": "Rolling stock and station facilities must be kept at a minimum standard of cleanliness."
+ }
+ ]
+ }
+ }
+}
+Lot
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "contractTerms": {
+ "hasElectronicPayment": true,
+ "hasElectronicOrdering": false,
+ "electronicInvoicingPolicy": "required",
+ "reservedExecution": true,
+ "performanceTerms": "A set of KPIs will be developed for this contract and the successful tenderer will be measured against these for the duration of the contract. Please refer to briefing document for further details.",
+ "financialTerms": "In the event that a work referred to in § 2.6 of the Agreement is created as part of the implementation of the Subject Matter of the Agreement, the Contractor shall indicate on the invoice what proportion of the remuneration for implementation.",
+ "tendererLegalForm": "Contractors may jointly apply for the contract.",
+ "hasExclusiveRights": false,
+ "operatorRevenueShare": 0.25,
+ "socialStandards": "The supplier maintains the social, collective bargaining and labor law obligations according to Union law, national law or collective agreements. 4 paragraph 4a Regulation 13707/2007.",
+ "hasNonDisclosureAgreement": true,
+ "nonDisclosureAgreement": "A non-disclosure agreement is required in order to...",
+ "customerServices": [
+ {
+ "type": "clean",
+ "name": "Cleanliness of rolling stock and station facilities",
+ "description": "Rolling stock and station facilities must be kept at a minimum standard of cleanliness."
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-03-10
+-
+
- Add
hasNonDisclosureAgreement,nonDisclosureAgreementandcustomerServicesfields.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del OCDS para el perfil de la UE y en pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/contract_buyer/index.html b/es/extensions/contract_buyer/index.html
new file mode 100644
index 000000000..3eebd88b6
--- /dev/null
+++ b/es/extensions/contract_buyer/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Términos del contrato +
+ ++ Agrega un objeto términos del contrato a los objetos de la licitación y del lote, para describir los términos que rigen al futuro contrato. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ contractTerms
+
+ |
+ + Términos del contrato + | +
+ Información sobre los términos que rigen los futuros contratos del procedimiento. + + |
+ + ContractTerms object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ contractTerms
+
+ |
+ + Términos del contrato + | +
+ Información sobre los términos que rigen los contratos futuros del lote. + + |
+ + ContractTerms object + | +
+ ContractTerms +
+ +
+ The extension defines a new ContractTerms object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasElectronicPayment
+
+ |
+ + Pago electrónico utilizado + | +
+ Si se utiliza el pago electrónico. + + |
+ + boolean + | +
+
+ hasElectronicOrdering
+
+ |
+ + Pedido electrónico utilizado + | +
+ Si se utiliza el pedido electrónico. + + |
+ + boolean + | +
+
+ electronicInvoicingPolicy
+
+ |
+ + Política de facturación electrónica + | +
+ Si el comprador requerirá, permitirá o no permitirá las facturas electrónicas. + + |
+ + string from closed permission codelist + | +
+
+ reservedExecution
+
+ |
+ + Ejecución reservada + | +
+ Si la ejecución del contrato se restringe al marco de los programas de empleo protegido + + |
+ + boolean + | +
+
+ performanceTerms
+
+ |
+ + Rendimiento de los términos + | +
+ La información principal sobre la ejecución del contrato (por ejemplo, entregables intermediarios, compensación por daños, derechos de propiedad intelectual). + + |
+ + string + | +
+
+ financialTerms
+
+ |
+ + Términos financieros + | +
+ La principal información sobre financiación y pago y/o referencia a las disposiciones que las regulan. + + |
+ + string + | +
+
+ tendererLegalForm
+
+ |
+ + Forma jurídica del licitador + | +
+ Una determinada forma jurídica que debe adoptar un grupo de licitantes que es adjudicado a un contrato. + + |
+ + string + | +
+
+ hasExclusiveRights
+
+ |
+ + Tiene derechos exclusivos + | +
+ Un derecho que permite a un operador de servicio público operar ciertos servicios públicos de transporte de pasajeros en una ruta o red particular o en un área particular, con exclusión de cualquier otro operador. + + |
+ + boolean + | +
+
+ exclusiveRights
+
+ |
+ + Derechos exclusivos + | +
+ La naturaleza y alcance de los derechos exclusivos otorgados por la entidad contratante al proveedor. + + |
+ + string + | +
+
+ operatorRevenueShare
+
+ |
+ + Reparto de ingresos del operador + | +
+ El porcentaje de ingresos por la venta de boletos asignado al proveedor. + + |
+ + number + | +
+
+ otherTerms
+
+ |
+ + Otros términos + | +
+ Otros términos del contrato que no se ajustan a la semántica de ningún otro campo OCDS. + + |
+ + string + | +
+
+ rewardsAndPenalties
+
+ |
+ + Recompensas y sanciones + | +
+ Información sobre recompensas y sanciones relacionadas con los objetivos de calidad. + + |
+ + string + | +
+
+ socialStandards
+
+ |
+ + Estándares sociales + | +
+ Los estándares sociales requeridos, por ejemplo: detalle de los derechos contractuales del personal afectado y condiciones en las que se considera que los empleados están vinculados a los servicios. + + |
+ + string + | +
+
+ hasNonDisclosureAgreement
+
+ |
+ + Has non-disclosure agreement + | +
+ Whether contract execution requires a non-disclosure agreement. + + |
+ + boolean + | +
+
+ nonDisclosureAgreement
+
+ |
+ + Non-disclosure agreement + | +
+ A description of the non-disclosure agreement required for contract execution. + + |
+ + string + | +
+
+ customerServices
+
+ |
+ + Customer services + | +
+ Information about customer service requirements. + + |
+ + array of CustomerService objects + | +
+ CustomerService +
+ +
+ The extension defines a new CustomerService object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Type + | +
+ The type of this customer service requirement. + + |
+ + string + | +
+
+ name
+
+ |
+ + Name + | +
+ A name for this customer service requirement. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ A description of this customer service requirement. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/contract_buyer/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/contract_buyer/master/release-schema.json b/es/extensions/contract_buyer/master/release-schema.json
new file mode 100644
index 000000000..f7c8ecc6d
--- /dev/null
+++ b/es/extensions/contract_buyer/master/release-schema.json
@@ -0,0 +1,27 @@
+{
+ "definitions": {
+ "Award": {
+ "properties": {
+ "buyers": {
+ "title": "Buyers",
+ "description": "The organizations aiming to conclude a contract with the suppliers or to use the goods, services or works resulting from the contract, if not identical to the buyers for the contracting process.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "buyer": {
+ "title": "Comprador",
+ "description": "The organization aiming to conclude a contract with the suppliers or to use the goods, services or works resulting from the contract, if not identical to the buyer for the contracting process.",
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/contract_buyer/master/schema/index.html b/es/extensions/contract_buyer/master/schema/index.html
new file mode 100644
index 000000000..21861790a
--- /dev/null
+++ b/es/extensions/contract_buyer/master/schema/index.html
@@ -0,0 +1,282 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Buyer per award or contract +
+ ++ Adds buyer fields to the award and contract objects to indicate the buyer(s) for an individual award or contract, if different from the buyer(s) involved in the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds buyer fields to the award and contract objects to indicate the buyer(s) for an individual award or contract, if different from the buyer(s) involved in the contracting process as a whole.
+OCDS indicates the (lead) buyer in a contracting process with the buyer field. If a contracting process involves multiple buyers, each buyer can be added to the parties array with a 'buyer' role.
However, in some cases, for a given award, a subset of the buyers decide on the supplier and sign the contract. Only use this extension in such cases.
+Legal context
+In the European Union, this extension's fields correspond to eForms OPT-300-Contract-Signatory. For correspondences to eForms fields, see OCDS for eForms.
+Ejemplo
+Contracts
+Two contracts are issued with a different buyer for each.
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "buyer": {
+ "name": "Example Department of Transport",
+ "id": "GB-GOV-00000000"
+ }
+ },
+ {
+ "id": "2",
+ "awardID": "2",
+ "buyer": {
+ "name": "Example Department of Education",
+ "id": "GB-GOV-12345678"
+ }
+ }
+ ]
+}
+Awards
+One award is issued with two buyers.
+{
+ "awards": [
+ {
+ "id": "1",
+ "buyers": [
+ {
+ "name": "Example Department of Education",
+ "id": "GB-GOV-12345678"
+ },
+ {
+ "name": "Example Department of Transport",
+ "id": "GB-GOV-00000000"
+ }
+ ]
+ }
+ ]
+}
+Changelog
+2023-04-12
+-
+
- Add
awards.buyersfield.
+
Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/contract_completion/index.html b/es/extensions/contract_completion/index.html
new file mode 100644
index 000000000..f6cdfe17d
--- /dev/null
+++ b/es/extensions/contract_completion/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Buyer per award or contract +
+ ++ Adds buyer fields to the award and contract objects to indicate the buyer(s) for an individual award or contract, if different from the buyer(s) involved in the contracting process as a whole. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ buyers
+
+ |
+ + Buyers + | +
+ The organizations aiming to conclude a contract with the suppliers or to use the goods, services or works resulting from the contract, if not identical to the buyers for the contracting process. + + |
+ + array of OrganizationReference objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ buyer
+
+ |
+ + Comprador + | +
+ The organization aiming to conclude a contract with the suppliers or to use the goods, services or works resulting from the contract, if not identical to the buyer for the contracting process. + + |
+ + OrganizationReference object + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/contract_completion/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/contract_completion/master/release-schema.json b/es/extensions/contract_completion/master/release-schema.json
new file mode 100644
index 000000000..17fa5f6e5
--- /dev/null
+++ b/es/extensions/contract_completion/master/release-schema.json
@@ -0,0 +1,40 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "endDate": {
+ "title": "Fecha de fin",
+ "description": "La fecha real en la que finaliz\u00f3 la implementaci\u00f3n del contrato. Cuando `deployment/endDate` difiera del `contract/period/endDate` anticipado, se debe proporcionar una explicaci\u00f3n de la variaci\u00f3n en `deployment/endDateDetails`.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "endDateDetails": {
+ "title": "Detalles de fecha de t\u00e9rmino",
+ "description": "Detalles relacionados con la endDate. Esto puede justificar que la fecha de cumplimento del contrato sea diferente a la del contrato original.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "finalValue": {
+ "title": "Valor final",
+ "description": "Valor total real de todos los pagos para un contrato completado. Si se utiliza `implementation/transactions` para este contrato, este campo debe ser igual a la suma de los campos `transaction/value/amount`. Cuando `finalValue/amount` difiera de `contract/value/amount` se debe dar una explicaci\u00f3n de la variaci\u00f3n en `finalValueDetails`.",
+ "$ref": "#/definitions/Value"
+ },
+ "finalValueDetails": {
+ "title": "Detalles del valor final",
+ "description": "Detalles relacionados al valor final. Esto puede ser una justificaci\u00f3n del cambio del valor del contrato terminado contra el valor en el contrato original.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/contract_completion/master/schema/index.html b/es/extensions/contract_completion/master/schema/index.html
new file mode 100644
index 000000000..572628250
--- /dev/null
+++ b/es/extensions/contract_completion/master/schema/index.html
@@ -0,0 +1,282 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cumplimiento del contrato +
+ ++ Añade campos a la sección de implementación del contrato para detallar la fecha de finalización, y el valor final de un contrato. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+El Estándar de Datos de Contrataciones Abiertas se puede usar para dar información sobre todas las etapas del proceso de contrataciones, desde la planeación hasta la implementación.
+Esta extensión introduce cuatro campos que pueden usarse al final de un proceso de contratación para dar detalles sobre la fecha final y valor del contrato, también se pueden utilizar cuando hay variaciones para dar una justificación de las mismas.
+Utilizar campos OCDS existentes dentro de un registro de contratos
+El OCDS tiene muchos campos que pueden usarse como parte de un Registro de Contratos. Estos están documentados en el esquema. Esta extensión no modifica ninguno de estos campos. De cualquier manera, la siguiente lista se da para la conveniencia de las personas que están considerado el diseño de un registro de contratos.
+-
+
- Los detalles del proveedor deben registrarse dentro de la sección
awards, enlazada a través decontract.awardID(incluso si solo está publicando información en la etapa del contrato, puede proporcionar información en las secciones de licitación y adjudicación).
+ - Documentos del contrato se puede enlazar en
contracts.documents.
+ - Reportes de desempeño se pueden proporcionar en
contracts.implementation.documents.
+ - Detalles de los pagos se pueden proporcionar en
contracts.implementation.transactions.
+ - Los detalles del progreso se pueden proporcionar usando
contracts.implementation.milestones.
+ - Enmiendas pueden describirse utilizando la lista
contracts.amendments, y con los valores anteriores proporcionados mediante el OCDS modelo de entregas como se describe aquí.
+
Utilizar hitos para mostrar la finalización de un contrato
+Los hitos pueden tener un status de 'scheduled', 'met', 'notMet' o 'partiallyMet'. Al dar al menos un hito por contrato, y asegurar que milestone/status se actualice cuando implementation/endDate se puede indicar que un contrato terminó con la entrega exitosa de todos los hitos y entregables.
Ejemplo
+Observe la diferencia entre period y value del contrato (según lo acordado en el contrato, o en el contrato modificado o enmendado), y el finalValue y endDate, de la implementación, junto con la explicación de esta diferencia.
{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "title": "Contract to build new cycle lanes in the centre of town.",
+ "period": {
+ "startDate": "2010-07-01T00:00:00Z",
+ "endDate": "2012-01-01T23:59:00Z",
+ "maxExtentDate": "2012-01-31T23:59:00Z"
+ },
+ "value": {
+ "amount": 11500000,
+ "currency": "GBP"
+ },
+ "implementation": {
+ "endDate": "2012-02-01T00:00:00Z",
+ "endDateDetails": "Project was completed one day beyond the extended deadline.",
+ "finalValue": {
+ "amount": 11800000,
+ "currency": "GBP"
+ },
+ "finalValueDetails": "The final payment to the supplier included a compensation payment triggered by the local authority failure to provide work permits on schedule."
+ }
+ }
+ ]
+}
+El directorio de ejemplos contiene un completo ejemplo práctico con:
+-
+
- Un lanzamiento que da detalles sobre un contrato; +
- Un lanzamiento que incluye una enmienda al contrato para incrementar el valor total, así como el valor inicial de las transacciones; +
- Un lanzamiento que contiene una fecha final confirmada, el valor final y la explicación de variación en ellas +
Esto también se proporciona como registro OCDS y como archivo Excel.
+En el archivo Excel, es posible ver tres entregas que describen los tres momentos clave del mismo proceso de contratación.
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-06-04
+-
+
- Revisar las palabras normativas y no-normativas +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente en https://github.com/open-contracting/standard/issues/703.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/contract_suppliers/index.html b/es/extensions/contract_suppliers/index.html
new file mode 100644
index 000000000..cdbf59a69
--- /dev/null
+++ b/es/extensions/contract_suppliers/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cumplimiento del contrato +
+ ++ Añade campos a la sección de implementación del contrato para detallar la fecha de finalización, y el valor final de un contrato. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ endDate
+
+ |
+ + Fecha de fin + | +
+ La fecha real en la que finalizó la implementación del contrato. Cuando |
+ + string + | +
+
+ endDateDetails
+
+ |
+ + Detalles de fecha de término + | +
+ Detalles relacionados con la endDate. Esto puede justificar que la fecha de cumplimento del contrato sea diferente a la del contrato original. + + |
+ + string + | +
+
+ finalValue
+
+ |
+ + Valor final + | +
+ Valor total real de todos los pagos para un contrato completado. Si se utiliza |
+ + Value object + | +
+
+ finalValueDetails
+
+ |
+ + Detalles del valor final + | +
+ Detalles relacionados al valor final. Esto puede ser una justificación del cambio del valor del contrato terminado contra el valor en el contrato original. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/contract_suppliers/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/contract_suppliers/master/release-schema.json b/es/extensions/contract_suppliers/master/release-schema.json
new file mode 100644
index 000000000..31efa1d14
--- /dev/null
+++ b/es/extensions/contract_suppliers/master/release-schema.json
@@ -0,0 +1,18 @@
+{
+ "definitions": {
+ "Contract": {
+ "properties": {
+ "suppliers": {
+ "title": "Proveedores",
+ "description": "Los proveedores mencionados expl\u00edcitamente en este contrato.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/contract_suppliers/master/schema/index.html b/es/extensions/contract_suppliers/master/schema/index.html
new file mode 100644
index 000000000..9ba702f75
--- /dev/null
+++ b/es/extensions/contract_suppliers/master/schema/index.html
@@ -0,0 +1,231 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Proveedores contratados +
+ ++ Permitir la declaración explícita de proveedores dentro del bloque de contratos. Se usa cuando una sola adjudicación a múltiples proveedores resulta en múltiples contratos para un subconjunto de los proveedores adjudicados. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+El OCDS se ha diseñado alrededor de un modelo de contrataciones que:
+-
+
- Uno o más licitaciones se hacen nombrando a los proveedores seleccionados; +
- Un contrato se firma por cada licitación, refiriéndose a la licitación relacionada; +
Por esta razón, el principal bloque Contract no incluye información sobre los suppliers. Estos se pueden encontrar en el Award relacionado usando la referencia cruzada awardID.
De cualquier forma, existen algunos procesos de contratación en las que una misma adjudicación a múltiples proveedores, resulta en contratos múltiples, cada uno para un solo proveedor. En esas instancias, es importante especificar los proveedores al nivel contrato.
+La extensión Proveedores de Contratos introduce la matriz contracts.suppliers para este propósito.
Ejemplo
+Se otorga una adjudicación a un consorcio con múltiples proveedores. Luego, se firma un contrato con cada uno de ellos por separado. Cuando se utiliza esta extensión, se debe completar contratos.items y contract.value con los ítems adjudicados y el valor para cada proveedor.
{
+ "awards": [
+ {
+ "id": "ocds-213czf-000-00001-award-01",
+ "value": {
+ "amount": 100000,
+ "currency": "GBP"
+ },
+ "items": [
+ {
+ "id": "0001",
+ "description": "Construction work for highways",
+ "quantity": 10,
+ "unit": {
+ "name": "Miles",
+ "value": {
+ "amount": 10000,
+ "currency": "GBP"
+ }
+ }
+ }
+ ],
+ "suppliers": [
+ {
+ "id": "GB-COH-1234567844",
+ "name": "AnyCorp Cycle Provision"
+ },
+ {
+ "id": "GB-COH-789456123",
+ "name": "OtherCorp"
+ }
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "ocds-213czf-000-00001-contract-01",
+ "awardID": "ocds-213czf-000-00001-award-01",
+ "value": {
+ "amount": 70000,
+ "currency": "GBP"
+ },
+ "suppliers": [
+ {
+ "id": "GB-COH-1234567844",
+ "name": "AnyCorp Cycle Provision"
+ }
+ ],
+ "items": [
+ {
+ "id": "0001",
+ "description": "Construction work for highways",
+ "quantity": 7,
+ "unit": {
+ "name": "Miles",
+ "value": {
+ "amount": 10000,
+ "currency": "GBP"
+ }
+ }
+ }
+ ]
+ },
+ {
+ "id": "ocds-213czf-000-00001-contract-02",
+ "awardID": "ocds-213czf-000-00001-award-01",
+ "value": {
+ "amount": 30000,
+ "currency": "GBP"
+ },
+ "suppliers": [
+ {
+ "id": "GB-COH-789456123",
+ "name": "OtherCorp"
+ }
+ ],
+ "items": [
+ {
+ "id": "0001",
+ "description": "Construction work for highways",
+ "quantity": 3,
+ "unit": {
+ "name": "Miles",
+ "value": {
+ "amount": 10000,
+ "currency": "GBP"
+ }
+ }
+ }
+ ]
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/countryCode/index.html b/es/extensions/countryCode/index.html
new file mode 100644
index 000000000..b6da646b7
--- /dev/null
+++ b/es/extensions/countryCode/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Proveedores contratados +
+ ++ Permitir la declaración explícita de proveedores dentro del bloque de contratos. Se usa cuando una sola adjudicación a múltiples proveedores resulta en múltiples contratos para un subconjunto de los proveedores adjudicados. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ suppliers
+
+ |
+ + Proveedores + | +
+ Los proveedores mencionados explícitamente en este contrato. + + |
+ + array of OrganizationReference objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/countryCode/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/countryCode/master/extension.json b/es/extensions/countryCode/master/extension.json
new file mode 100644
index 000000000..7e48beda6
--- /dev/null
+++ b/es/extensions/countryCode/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Country code",
+ "es": "C\u00f3digo de pa\u00eds"
+ },
+ "description": {
+ "en": "Adds a country code field to the address object.",
+ "es": "Agregar un campo c\u00f3digo de pa\u00eds al objeto de direcci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/countryCode/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "country.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/countryCode/master/index.html b/es/extensions/countryCode/master/index.html
new file mode 100644
index 000000000..d234b0218
--- /dev/null
+++ b/es/extensions/countryCode/master/index.html
@@ -0,0 +1,312 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Código de país +
+ ++ Agregar un campo código de país al objeto de dirección. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ country.csv +
+ +
+ You can download the country.csv file in English.
+
| + Código + | ++ Título + | +
|---|---|
+
+ AD
+
+ |
+ + Andorra + | +
+
+ AE
+
+ |
+ + United Arab Emirates + | +
+
+ AF
+
+ |
+ + Afghanistan + | +
+
+ AG
+
+ |
+ + Antigua and Barbuda + | +
+
+ AI
+
+ |
+ + Anguilla + | +
+
+ AL
+
+ |
+ + Albania + | +
+
+ AM
+
+ |
+ + Armenia + | +
+
+ AO
+
+ |
+ + Angola + | +
+
+ AQ
+
+ |
+ + Antarctica + | +
+
+ AR
+
+ |
+ + Argentina + | +
+
+ AS
+
+ |
+ + American Samoa + | +
+
+ AT
+
+ |
+ + Austria + | +
+
+ AU
+
+ |
+ + Australia + | +
+
+ AW
+
+ |
+ + Aruba + | +
+
+ AX
+
+ |
+ + Åland Islands + | +
+
+ AZ
+
+ |
+ + Azerbaijan + | +
+
+ BA
+
+ |
+ + Bosnia and Herzegovina + | +
+
+ BB
+
+ |
+ + Barbados + | +
+
+ BD
+
+ |
+ + Bangladesh + | +
+
+ BE
+
+ |
+ + Belgium + | +
+
+ BF
+
+ |
+ + Burkina Faso + | +
+
+ BG
+
+ |
+ + Bulgaria + | +
+
+ BH
+
+ |
+ + Bahrain + | +
+
+ BI
+
+ |
+ + Burundi + | +
+
+ BJ
+
+ |
+ + Benin + | +
+
+ BL
+
+ |
+ + Saint Barthélemy + | +
+
+ BM
+
+ |
+ + Bermuda + | +
+
+ BN
+
+ |
+ + Brunei Darussalam + | +
+
+ BO
+
+ |
+ + Bolivia (Plurinational State of) + | +
+
+ BQ
+
+ |
+ + Bonaire, Sint Eustatius and Saba + | +
+
+ BR
+
+ |
+ + Brazil + | +
+
+ BS
+
+ |
+ + Bahamas + | +
+
+ BT
+
+ |
+ + Bhutan + | +
+
+ BV
+
+ |
+ + Bouvet Island + | +
+
+ BW
+
+ |
+ + Botswana + | +
+
+ BY
+
+ |
+ + Belarus + | +
+
+ BZ
+
+ |
+ + Belize + | +
+
+ CA
+
+ |
+ + Canada + | +
+
+ CC
+
+ |
+ + Cocos (Keeling) Islands + | +
+
+ CD
+
+ |
+ + Congo (the Democratic Republic of the) + | +
+
+ CF
+
+ |
+ + Central African Republic + | +
+
+ CG
+
+ |
+ + Congo + | +
+
+ CH
+
+ |
+ + Switzerland + | +
+
+ CI
+
+ |
+ + Côte d'Ivoire + | +
+
+ CK
+
+ |
+ + Cook Islands + | +
+
+ CL
+
+ |
+ + Chile + | +
+
+ CM
+
+ |
+ + Cameroon + | +
+
+ CN
+
+ |
+ + China + | +
+
+ CO
+
+ |
+ + Colombia + | +
+
+ CR
+
+ |
+ + Costa Rica + | +
+
+ CU
+
+ |
+ + Cuba + | +
+
+ CV
+
+ |
+ + Cabo Verde + | +
+
+ CW
+
+ |
+ + Curaçao + | +
+
+ CX
+
+ |
+ + Christmas Island + | +
+
+ CY
+
+ |
+ + Cyprus + | +
+
+ CZ
+
+ |
+ + Czechia + | +
+
+ DE
+
+ |
+ + Germany + | +
+
+ DJ
+
+ |
+ + Djibouti + | +
+
+ DK
+
+ |
+ + Denmark + | +
+
+ DM
+
+ |
+ + Dominica + | +
+
+ DO
+
+ |
+ + Dominican Republic + | +
+
+ DZ
+
+ |
+ + Algeria + | +
+
+ EC
+
+ |
+ + Ecuador + | +
+
+ EE
+
+ |
+ + Estonia + | +
+
+ EG
+
+ |
+ + Egypt + | +
+
+ EH
+
+ |
+ + Western Sahara + | +
+
+ ER
+
+ |
+ + Eritrea + | +
+
+ ES
+
+ |
+ + Spain + | +
+
+ ET
+
+ |
+ + Ethiopia + | +
+
+ FI
+
+ |
+ + Finland + | +
+
+ FJ
+
+ |
+ + Fiji + | +
+
+ FK
+
+ |
+ + Falkland Islands [Malvinas] + | +
+
+ FM
+
+ |
+ + Micronesia (Federated States of) + | +
+
+ FO
+
+ |
+ + Faroe Islands + | +
+
+ FR
+
+ |
+ + France + | +
+
+ GA
+
+ |
+ + Gabon + | +
+
+ GB
+
+ |
+ + United Kingdom of Great Britain and Northern Ireland + | +
+
+ GD
+
+ |
+ + Grenada + | +
+
+ GE
+
+ |
+ + Georgia + | +
+
+ GF
+
+ |
+ + French Guiana + | +
+
+ GG
+
+ |
+ + Guernsey + | +
+
+ GH
+
+ |
+ + Ghana + | +
+
+ GI
+
+ |
+ + Gibraltar + | +
+
+ GL
+
+ |
+ + Greenland + | +
+
+ GM
+
+ |
+ + Gambia + | +
+
+ GN
+
+ |
+ + Guinea + | +
+
+ GP
+
+ |
+ + Guadeloupe + | +
+
+ GQ
+
+ |
+ + Equatorial Guinea + | +
+
+ GR
+
+ |
+ + Greece + | +
+
+ GS
+
+ |
+ + South Georgia and the South Sandwich Islands + | +
+
+ GT
+
+ |
+ + Guatemala + | +
+
+ GU
+
+ |
+ + Guam + | +
+
+ GW
+
+ |
+ + Guinea-Bissau + | +
+
+ GY
+
+ |
+ + Guyana + | +
+
+ HK
+
+ |
+ + Hong Kong + | +
+
+ HM
+
+ |
+ + Heard Island and McDonald Islands + | +
+
+ HN
+
+ |
+ + Honduras + | +
+
+ HR
+
+ |
+ + Croatia + | +
+
+ HT
+
+ |
+ + Haiti + | +
+
+ HU
+
+ |
+ + Hungary + | +
+
+ ID
+
+ |
+ + Indonesia + | +
+
+ IE
+
+ |
+ + Ireland + | +
+
+ IL
+
+ |
+ + Israel + | +
+
+ IM
+
+ |
+ + Isle of Man + | +
+
+ IN
+
+ |
+ + India + | +
+
+ IO
+
+ |
+ + British Indian Ocean Territory + | +
+
+ IQ
+
+ |
+ + Iraq + | +
+
+ IR
+
+ |
+ + Iran (Islamic Republic of) + | +
+
+ IS
+
+ |
+ + Iceland + | +
+
+ IT
+
+ |
+ + Italy + | +
+
+ JE
+
+ |
+ + Jersey + | +
+
+ JM
+
+ |
+ + Jamaica + | +
+
+ JO
+
+ |
+ + Jordan + | +
+
+ JP
+
+ |
+ + Japan + | +
+
+ KE
+
+ |
+ + Kenya + | +
+
+ KG
+
+ |
+ + Kyrgyzstan + | +
+
+ KH
+
+ |
+ + Cambodia + | +
+
+ KI
+
+ |
+ + Kiribati + | +
+
+ KM
+
+ |
+ + Comoros + | +
+
+ KN
+
+ |
+ + Saint Kitts and Nevis + | +
+
+ KP
+
+ |
+ + Korea (the Democratic People's Republic of) + | +
+
+ KR
+
+ |
+ + Korea (the Republic of) + | +
+
+ KW
+
+ |
+ + Kuwait + | +
+
+ KY
+
+ |
+ + Cayman Islands + | +
+
+ KZ
+
+ |
+ + Kazakhstan + | +
+
+ LA
+
+ |
+ + Lao People's Democratic Republic + | +
+
+ LB
+
+ |
+ + Lebanon + | +
+
+ LC
+
+ |
+ + Saint Lucia + | +
+
+ LI
+
+ |
+ + Liechtenstein + | +
+
+ LK
+
+ |
+ + Sri Lanka + | +
+
+ LR
+
+ |
+ + Liberia + | +
+
+ LS
+
+ |
+ + Lesotho + | +
+
+ LT
+
+ |
+ + Lithuania + | +
+
+ LU
+
+ |
+ + Luxembourg + | +
+
+ LV
+
+ |
+ + Latvia + | +
+
+ LY
+
+ |
+ + Libya + | +
+
+ MA
+
+ |
+ + Morocco + | +
+
+ MC
+
+ |
+ + Monaco + | +
+
+ MD
+
+ |
+ + Moldova (the Republic of) + | +
+
+ ME
+
+ |
+ + Montenegro + | +
+
+ MF
+
+ |
+ + Saint Martin (French part) + | +
+
+ MG
+
+ |
+ + Madagascar + | +
+
+ MH
+
+ |
+ + Marshall Islands + | +
+
+ MK
+
+ |
+ + North Macedonia + | +
+
+ ML
+
+ |
+ + Mali + | +
+
+ MM
+
+ |
+ + Myanmar + | +
+
+ MN
+
+ |
+ + Mongolia + | +
+
+ MO
+
+ |
+ + Macao + | +
+
+ MP
+
+ |
+ + Northern Mariana Islands + | +
+
+ MQ
+
+ |
+ + Martinique + | +
+
+ MR
+
+ |
+ + Mauritania + | +
+
+ MS
+
+ |
+ + Montserrat + | +
+
+ MT
+
+ |
+ + Malta + | +
+
+ MU
+
+ |
+ + Mauritius + | +
+
+ MV
+
+ |
+ + Maldives + | +
+
+ MW
+
+ |
+ + Malawi + | +
+
+ MX
+
+ |
+ + Mexico + | +
+
+ MY
+
+ |
+ + Malaysia + | +
+
+ MZ
+
+ |
+ + Mozambique + | +
+
+ NA
+
+ |
+ + Namibia + | +
+
+ NC
+
+ |
+ + New Caledonia + | +
+
+ NE
+
+ |
+ + Niger + | +
+
+ NF
+
+ |
+ + Norfolk Island + | +
+
+ NG
+
+ |
+ + Nigeria + | +
+
+ NI
+
+ |
+ + Nicaragua + | +
+
+ NL
+
+ |
+ + Netherlands + | +
+
+ NO
+
+ |
+ + Norway + | +
+
+ NP
+
+ |
+ + Nepal + | +
+
+ NR
+
+ |
+ + Nauru + | +
+
+ NU
+
+ |
+ + Niue + | +
+
+ NZ
+
+ |
+ + New Zealand + | +
+
+ OM
+
+ |
+ + Oman + | +
+
+ PA
+
+ |
+ + Panama + | +
+
+ PE
+
+ |
+ + Peru + | +
+
+ PF
+
+ |
+ + French Polynesia + | +
+
+ PG
+
+ |
+ + Papua New Guinea + | +
+
+ PH
+
+ |
+ + Philippines + | +
+
+ PK
+
+ |
+ + Pakistan + | +
+
+ PL
+
+ |
+ + Poland + | +
+
+ PM
+
+ |
+ + Saint Pierre and Miquelon + | +
+
+ PN
+
+ |
+ + Pitcairn + | +
+
+ PR
+
+ |
+ + Puerto Rico + | +
+
+ PS
+
+ |
+ + Palestine, State of + | +
+
+ PT
+
+ |
+ + Portugal + | +
+
+ PW
+
+ |
+ + Palau + | +
+
+ PY
+
+ |
+ + Paraguay + | +
+
+ QA
+
+ |
+ + Qatar + | +
+
+ RE
+
+ |
+ + Réunion + | +
+
+ RO
+
+ |
+ + Romania + | +
+
+ RS
+
+ |
+ + Serbia + | +
+
+ RU
+
+ |
+ + Russian Federation + | +
+
+ RW
+
+ |
+ + Rwanda + | +
+
+ SA
+
+ |
+ + Saudi Arabia + | +
+
+ SB
+
+ |
+ + Solomon Islands + | +
+
+ SC
+
+ |
+ + Seychelles + | +
+
+ SD
+
+ |
+ + Sudan + | +
+
+ SE
+
+ |
+ + Sweden + | +
+
+ SG
+
+ |
+ + Singapore + | +
+
+ SH
+
+ |
+ + Saint Helena, Ascension and Tristan da Cunha + | +
+
+ SI
+
+ |
+ + Slovenia + | +
+
+ SJ
+
+ |
+ + Svalbard and Jan Mayen + | +
+
+ SK
+
+ |
+ + Slovakia + | +
+
+ SL
+
+ |
+ + Sierra Leone + | +
+
+ SM
+
+ |
+ + San Marino + | +
+
+ SN
+
+ |
+ + Senegal + | +
+
+ SO
+
+ |
+ + Somalia + | +
+
+ SR
+
+ |
+ + Suriname + | +
+
+ SS
+
+ |
+ + South Sudan + | +
+
+ ST
+
+ |
+ + Sao Tome and Principe + | +
+
+ SV
+
+ |
+ + El Salvador + | +
+
+ SX
+
+ |
+ + Sint Maarten (Dutch part) + | +
+
+ SY
+
+ |
+ + Syrian Arab Republic + | +
+
+ SZ
+
+ |
+ + Eswatini + | +
+
+ TC
+
+ |
+ + Turks and Caicos Islands + | +
+
+ TD
+
+ |
+ + Chad + | +
+
+ TF
+
+ |
+ + French Southern Territories + | +
+
+ TG
+
+ |
+ + Togo + | +
+
+ TH
+
+ |
+ + Thailand + | +
+
+ TJ
+
+ |
+ + Tajikistan + | +
+
+ TK
+
+ |
+ + Tokelau + | +
+
+ TL
+
+ |
+ + Timor-Leste + | +
+
+ TM
+
+ |
+ + Turkmenistan + | +
+
+ TN
+
+ |
+ + Tunisia + | +
+
+ TO
+
+ |
+ + Tonga + | +
+
+ TR
+
+ |
+ + Turkey + | +
+
+ TT
+
+ |
+ + Trinidad and Tobago + | +
+
+ TV
+
+ |
+ + Tuvalu + | +
+
+ TW
+
+ |
+ + Taiwan (Province of China) + | +
+
+ TZ
+
+ |
+ + Tanzania, the United Republic of + | +
+
+ UA
+
+ |
+ + Ukraine + | +
+
+ UG
+
+ |
+ + Uganda + | +
+
+ UM
+
+ |
+ + United States Minor Outlying Islands + | +
+
+ US
+
+ |
+ + United States of America + | +
+
+ UY
+
+ |
+ + Uruguay + | +
+
+ UZ
+
+ |
+ + Uzbekistan + | +
+
+ VA
+
+ |
+ + Holy See + | +
+
+ VC
+
+ |
+ + Saint Vincent and the Grenadines + | +
+
+ VE
+
+ |
+ + Venezuela (Bolivarian Republic of) + | +
+
+ VG
+
+ |
+ + Virgin Islands (British) + | +
+
+ VI
+
+ |
+ + Virgin Islands (U.S.) + | +
+
+ VN
+
+ |
+ + Viet Nam + | +
+
+ VU
+
+ |
+ + Vanuatu + | +
+
+ WF
+
+ |
+ + Wallis and Futuna + | +
+
+ WS
+
+ |
+ + Samoa + | +
+
+ XK
+
+ |
+ + Kosovo + | +
+
+ YE
+
+ |
+ + Yemen + | +
+
+ YT
+
+ |
+ + Mayotte + | +
+
+ ZA
+
+ |
+ + South Africa + | +
+
+ ZM
+
+ |
+ + Zambia + | +
+
+ ZW
+
+ |
+ + Zimbabwe + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/countryCode/master/release-schema.json b/es/extensions/countryCode/master/release-schema.json
new file mode 100644
index 000000000..3119ec3fb
--- /dev/null
+++ b/es/extensions/countryCode/master/release-schema.json
@@ -0,0 +1,271 @@
+{
+ "definitions": {
+ "Address": {
+ "properties": {
+ "country": {
+ "title": "C\u00f3digo de pa\u00eds",
+ "description": "The country, from the closed country codelist. If a country is missing, [create an issue](https://github.com/open-contracting/standard/issues) to discuss the addition of a user-assigned code to the country codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "country.csv",
+ "openCodelist": false,
+ "enum": [
+ "AD",
+ "AE",
+ "AF",
+ "AG",
+ "AI",
+ "AL",
+ "AM",
+ "AO",
+ "AQ",
+ "AR",
+ "AS",
+ "AT",
+ "AU",
+ "AW",
+ "AX",
+ "AZ",
+ "BA",
+ "BB",
+ "BD",
+ "BE",
+ "BF",
+ "BG",
+ "BH",
+ "BI",
+ "BJ",
+ "BL",
+ "BM",
+ "BN",
+ "BO",
+ "BQ",
+ "BR",
+ "BS",
+ "BT",
+ "BV",
+ "BW",
+ "BY",
+ "BZ",
+ "CA",
+ "CC",
+ "CD",
+ "CF",
+ "CG",
+ "CH",
+ "CI",
+ "CK",
+ "CL",
+ "CM",
+ "CN",
+ "CO",
+ "CR",
+ "CU",
+ "CV",
+ "CW",
+ "CX",
+ "CY",
+ "CZ",
+ "DE",
+ "DJ",
+ "DK",
+ "DM",
+ "DO",
+ "DZ",
+ "EC",
+ "EE",
+ "EG",
+ "EH",
+ "ER",
+ "ES",
+ "ET",
+ "FI",
+ "FJ",
+ "FK",
+ "FM",
+ "FO",
+ "FR",
+ "GA",
+ "GB",
+ "GD",
+ "GE",
+ "GF",
+ "GG",
+ "GH",
+ "GI",
+ "GL",
+ "GM",
+ "GN",
+ "GP",
+ "GQ",
+ "GR",
+ "GS",
+ "GT",
+ "GU",
+ "GW",
+ "GY",
+ "HK",
+ "HM",
+ "HN",
+ "HR",
+ "HT",
+ "HU",
+ "ID",
+ "IE",
+ "IL",
+ "IM",
+ "IN",
+ "IO",
+ "IQ",
+ "IR",
+ "IS",
+ "IT",
+ "JE",
+ "JM",
+ "JO",
+ "JP",
+ "KE",
+ "KG",
+ "KH",
+ "KI",
+ "KM",
+ "KN",
+ "KP",
+ "KR",
+ "KW",
+ "KY",
+ "KZ",
+ "LA",
+ "LB",
+ "LC",
+ "LI",
+ "LK",
+ "LR",
+ "LS",
+ "LT",
+ "LU",
+ "LV",
+ "LY",
+ "MA",
+ "MC",
+ "MD",
+ "ME",
+ "MF",
+ "MG",
+ "MH",
+ "MK",
+ "ML",
+ "MM",
+ "MN",
+ "MO",
+ "MP",
+ "MQ",
+ "MR",
+ "MS",
+ "MT",
+ "MU",
+ "MV",
+ "MW",
+ "MX",
+ "MY",
+ "MZ",
+ "NA",
+ "NC",
+ "NE",
+ "NF",
+ "NG",
+ "NI",
+ "NL",
+ "NO",
+ "NP",
+ "NR",
+ "NU",
+ "NZ",
+ "OM",
+ "PA",
+ "PE",
+ "PF",
+ "PG",
+ "PH",
+ "PK",
+ "PL",
+ "PM",
+ "PN",
+ "PR",
+ "PS",
+ "PT",
+ "PW",
+ "PY",
+ "QA",
+ "RE",
+ "RO",
+ "RS",
+ "RU",
+ "RW",
+ "SA",
+ "SB",
+ "SC",
+ "SD",
+ "SE",
+ "SG",
+ "SH",
+ "SI",
+ "SJ",
+ "SK",
+ "SL",
+ "SM",
+ "SN",
+ "SO",
+ "SR",
+ "SS",
+ "ST",
+ "SV",
+ "SX",
+ "SY",
+ "SZ",
+ "TC",
+ "TD",
+ "TF",
+ "TG",
+ "TH",
+ "TJ",
+ "TK",
+ "TL",
+ "TM",
+ "TN",
+ "TO",
+ "TR",
+ "TT",
+ "TV",
+ "TW",
+ "TZ",
+ "UA",
+ "UG",
+ "UM",
+ "US",
+ "UY",
+ "UZ",
+ "VA",
+ "VC",
+ "VE",
+ "VG",
+ "VI",
+ "VN",
+ "VU",
+ "WF",
+ "WS",
+ "XK",
+ "YE",
+ "YT",
+ "ZA",
+ "ZM",
+ "ZW",
+ null
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/countryCode/master/schema/index.html b/es/extensions/countryCode/master/schema/index.html
new file mode 100644
index 000000000..30a3e83db
--- /dev/null
+++ b/es/extensions/countryCode/master/schema/index.html
@@ -0,0 +1,236 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Código de país +
+ ++ Agregar un campo código de país al objeto de dirección. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar un campo código de país al objeto de dirección.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BT-514 (Organisation Country Code), BT-5141 (Place Country Code). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+{
+ "parties": [
+ {
+ "id": "GB-LAC-E09000003",
+ "name": "London Borough of Barnet",
+ "address": {
+ "streetAddress": "4, North London Business Park, Oakleigh Rd S",
+ "locality": "London",
+ "region": "London",
+ "postalCode": "N11 1NP",
+ "countryName": "United Kingdom",
+ "country": "GB"
+ }
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Si necesita usar un código asignado por el usuario, crear un issue para discutir su adición a la lista de códigos.
+Registro de cambios
+2023-02-07
+-
+
- Rename
countryCodetocountryto match OCDS 1.2.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), en pull requests y en https://github.com/open-contracting/standard/issues/524.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/coveredBy/index.html b/es/extensions/coveredBy/index.html
new file mode 100644
index 000000000..19eb45ce5
--- /dev/null
+++ b/es/extensions/coveredBy/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Código de país +
+ ++ Agregar un campo código de país al objeto de dirección. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Address +
+ +
+ The extension defines these fields in the Address object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ country
+
+ |
+ + Código de país + | +
+ The country, from the closed country codelist. If a country is missing, create an issue to discuss the addition of a user-assigned code to the country codelist. + + |
+ + string from closed country codelist + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/coveredBy/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/coveredBy/master/extension.json b/es/extensions/coveredBy/master/extension.json
new file mode 100644
index 000000000..d3ff1b08a
--- /dev/null
+++ b/es/extensions/coveredBy/master/extension.json
@@ -0,0 +1,29 @@
+{
+ "name": {
+ "en": "Covered By",
+ "es": "Cubierto por"
+ },
+ "description": {
+ "en": "Adds a field to indicate the treaties that the contracting process is covered by.",
+ "es": "Agregar un campo para indicar los tratados que cubre el proceso de contrataci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/coveredBy/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "coveredBy.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/es/extensions/coveredBy/master/index.html b/es/extensions/coveredBy/master/index.html
new file mode 100644
index 000000000..106a083ae
--- /dev/null
+++ b/es/extensions/coveredBy/master/index.html
@@ -0,0 +1,364 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cubierto por +
+ ++ Agregar un campo para indicar los tratados que cubre el proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ coveredBy.csv +
+ +
+ You can download the coveredBy.csv file in English.
+
| + Código + | ++ Título + | +
|---|---|
+
+ GPA
+
+ |
+ + Agreement on Government Procurement + | +
+
+ EU-CVD
+
+ |
+ + European Parliament and Council 2009/33/EC (Clean Vehicles Directive) + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/coveredBy/master/release-schema.json b/es/extensions/coveredBy/master/release-schema.json
new file mode 100644
index 000000000..4c23bab25
--- /dev/null
+++ b/es/extensions/coveredBy/master/release-schema.json
@@ -0,0 +1,44 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "coveredBy": {
+ "title": "Cubierto por",
+ "description": "The international legal instruments that the contracting process is covered by.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "coveredBy.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "coveredBy": {
+ "title": "Cubierto por",
+ "description": "The international legal instruments that the lot is covered by.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "coveredBy.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/coveredBy/master/schema/index.html b/es/extensions/coveredBy/master/schema/index.html
new file mode 100644
index 000000000..38dc3bb42
--- /dev/null
+++ b/es/extensions/coveredBy/master/schema/index.html
@@ -0,0 +1,287 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cubierto por +
+ ++ Agregar un campo para indicar los tratados que cubre el proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds a field to indicate the international legal instruments that the contracting process is covered by.
+For example, the Agreement on Government Procurement (GPA) is a treaty that requires members to indicate whether a contracting process is covered by it. The Clean Vehicles Directive is a legal act that provides for member states of the European Union to indicate associated information in procurement notices. The coveredBy field should be used to meet such requirements.
Para revelar las leyes o reglamentos que rigen el proceso de contratación y que otorgan autoridad legal a la entidad contratante, utilice la extensión legalBasis en vez.
+Guía
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Si necesita hacer referencia a un tratado que no está en el lista de códigos coveredBy:
-
+
- Si el tratado tiene un alcance nacional o subnacional, elegir un código de país relevante ISO 3166-1 alpha-2 country code (por ejemplo "CA" para Canadá). +
- Si el tratado tiene un alcance subnacional, elegir un código de región relevante [ISO 3166-2 region code] (https://en.wikipedia.org/wiki/ISO_3166-2) (por ejemplo "NT" para Northern Territories, una provincia de Canadá). +
- Concatenate the code(s) to the acronym of the treaty, separating each part with a dash (e.g "CA-NT-BIP"). +
- Add this code to the
coveredByarray.
+ - Documentar el nuevo código (ver Extending open codelists). +
Contexto legal
+El Revised Agreement on Government Procurement (GPA) incluye: "cada aviso de contratación prevista deberá incluir ... l. una indicación que la contratación está cubierta por este Acuerdo".
+La Unión Europea es una parte al GPA, y como tal su Directive 2014/24/EU (Contratos públicos - que establecen reglas básicas claras) incluye: "Parte C: Información que debe incluirse en los avisos de contrato ... 29. Indicación de si el contrato está cubierto por GPA".
+Ejemplo
+The coveredBy field is an array of strings, whose values are selected from the coveredBy.csv open codelist.
Tender
+{
+ "tender": {
+ "coveredBy": [
+ "GPA"
+ ]
+ }
+}
+Lot
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "coveredBy": [
+ "EU-CVD"
+ ]
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-03-02
+-
+
- Add 'EU-CVD' to the
coveredBycodelist.
+ - Add
coveredByto theLotobject.
+
2020-11-04
+-
+
- Agregar guía acerca de la creación de nuevos códigos para la lista de códigos
coveredBy.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/designContest/index.html b/es/extensions/designContest/index.html
new file mode 100644
index 000000000..b4b722074
--- /dev/null
+++ b/es/extensions/designContest/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cubierto por +
+ ++ Agregar un campo para indicar los tratados que cubre el proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ coveredBy
+
+ |
+ + Cubierto por + | +
+ The international legal instruments that the contracting process is covered by. + + |
+ + array of strings from open coveredBy codelist + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ coveredBy
+
+ |
+ + Cubierto por + | +
+ The international legal instruments that the lot is covered by. + + |
+ + array of strings from open coveredBy codelist + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/designContest/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/designContest/master/release-schema.json b/es/extensions/designContest/master/release-schema.json
new file mode 100644
index 000000000..02ded25bc
--- /dev/null
+++ b/es/extensions/designContest/master/release-schema.json
@@ -0,0 +1,167 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "designContest": {
+ "title": "Concurso de proyecto",
+ "description": "Informaci\u00f3n acerca de la organizaci\u00f3n de un concurso de proyecto.",
+ "$ref": "#/definitions/DesignContest"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "designContest": {
+ "title": "Concurso de proyecto",
+ "description": "Informaci\u00f3n acerca de la organizaci\u00f3n de un concurso de proyecto.",
+ "$ref": "#/definitions/DesignContest"
+ }
+ }
+ },
+ "DesignContest": {
+ "title": "Concurso de proyecto",
+ "description": "Informaci\u00f3n acerca de la organizaci\u00f3n de un concurso de proyecto.",
+ "type": "object",
+ "properties": {
+ "selectedParticipants": {
+ "title": "Participantes seleccionados",
+ "description": "The organizations that have already been selected to participate in the design contest.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "hasPrizes": {
+ "title": "Tiene premios",
+ "description": "Si se adjudicar\u00e1n los premios en el concurso de proyecto.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "prizes": {
+ "title": "Premio",
+ "description": "Informaci\u00f3n acerca de los premios adjudicados en el concurso de proyecto.",
+ "$ref": "#/definitions/Prizes"
+ },
+ "rewardsDetails": {
+ "title": "Detalles de recompensas",
+ "description": "Los detalles y condiciones de los pagos a realizar a los participantes.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "followUpContracts": {
+ "title": "Contratos de seguimiento",
+ "description": "Si los contratos posteriores al concurso de dise\u00f1o se otorgar\u00e1n al ganador o a los ganadores del concurso de dise\u00f1o.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "bindingJuryDecision": {
+ "title": "Decisi\u00f3n vinculante del jurado",
+ "description": "Si la decisi\u00f3n del jurado es vinculante para la entidad adjudicadora.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "juryMembers": {
+ "title": "Miembros del jurado",
+ "description": "Los miembros del jurado.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/JuryMember"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "JuryMember": {
+ "title": "Miembro del jurado",
+ "description": "Miembro del jurado.",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Nombre",
+ "description": "El nombre del miembro del jurado.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Prizes": {
+ "title": "Premio",
+ "description": "Information about the prizes awarded in a design contest.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "La descripci\u00f3n de los premios.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "details": {
+ "title": "Details",
+ "description": "Information about the individual prizes.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Prize"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Prize": {
+ "title": "Prize",
+ "description": "Information about an individual prize awarded in a design contest.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "The locally unique identifier for the prize.",
+ "type": [
+ "string"
+ ],
+ "versionId": true,
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "The description of the prize.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "value": {
+ "title": "Value",
+ "description": "The value of the prize.",
+ "$ref": "#/definitions/Value"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/designContest/master/schema/index.html b/es/extensions/designContest/master/schema/index.html
new file mode 100644
index 000000000..2d21e4e3c
--- /dev/null
+++ b/es/extensions/designContest/master/schema/index.html
@@ -0,0 +1,639 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Concurso de proyecto +
+ ++ Agregar un objeto al objeto de la licitación para describir un concurso de proyecto. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an object to the tender and lot objects to describe a design contest.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BG-704 (Reward and Jury) and BG-44 (Prize) and Title III, Chapter II of Directive 2014/24/EU. For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplos
+A contracting process with a single prize.
+{
+ "tender": {
+ "designContest": {
+ "selectedParticipants": [
+ {
+ "id": "1",
+ "name": "Brigitte Hermon"
+ },
+ {
+ "id": "2",
+ "name": "Paolo Travino"
+ }
+ ],
+ "hasPrizes": true,
+ "prizes": {
+ "description": "The winner(s) will receive a prize of EUR 3,000.00 (VAT free).",
+ "details": [
+ {
+ "id": "1",
+ "value": {
+ "amount": 3000,
+ "currency": "EUR"
+ }
+ }
+ ]
+ },
+ "rewardsDetails": "The payment is made by administrative mandate within 30 days in accordance with the regulations in force.",
+ "followUpContracts": true,
+ "bindingJuryDecision": true,
+ "juryMembers": [
+ {
+ "name": "Karla Schaffer"
+ },
+ {
+ "name": "Bulat Kazinsky"
+ },
+ {
+ "name": "Alexandra Martinez"
+ },
+ {
+ "name": "Scott MacDougall"
+ }
+ ]
+ }
+ }
+}
+Lot
+A lot with multiple prizes.
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "designContest": {
+ "selectedParticipants": [
+ {
+ "id": "1",
+ "name": "Brigitte Hermon"
+ },
+ {
+ "id": "2",
+ "name": "Paolo Travino"
+ }
+ ],
+ "hasPrizes": true,
+ "prizes": {
+ "details": [
+ {
+ "id": "1",
+ "description": "A lump sum indemnity of an amount identical to that paid to unsuccessful competitors will be paid to the winning team in the form of an advance on the project management contract at the end of the competition; this sum being credited to the amount of fees to be collected subsequently under the project management contract.",
+ "value": {
+ "amount": 3000,
+ "currency": "EUR"
+ }
+ },
+ {
+ "id": "2",
+ "description": "The two competitors (candidates admitted to compete) will receive a maximum fixed compensation of 10,000 EUR excluding tax. For the services provided, subject to the admissibility of their services with regard to the rules of the competition and compliance with the program. Compensation is fixed, in accordance with the provisions of article R. 2172-4 of the public procurement code, the buyer, on the proposal of the jury, reserves the right, in the case of a project that he deems incomplete or whose performances do not comply with the competition rules and/or the programme, to totally or partially cancel the indemnity.",
+ "value": {
+ "amount": 10000,
+ "currency": "EUR"
+ }
+ }
+ ]
+ },
+ "rewardsDetails": "The payment is made by administrative mandate within 30 days in accordance with the regulations in force.",
+ "followUpContracts": true,
+ "bindingJuryDecision": true,
+ "juryMembers": [
+ {
+ "name": "Karla Schaffer"
+ },
+ {
+ "name": "Bulat Kazinsky"
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-03-10
+-
+
- Add
lots.designContestobject.
+ - Add
detailsarray toDesignContest.prizesarray, to describe theid,descriptionandvalueof each prize.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del OCDS para el perfil de la UE y en pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/document_publisher/index.html b/es/extensions/document_publisher/index.html
new file mode 100644
index 000000000..354321304
--- /dev/null
+++ b/es/extensions/document_publisher/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Concurso de proyecto +
+ ++ Agregar un objeto al objeto de la licitación para describir un concurso de proyecto. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ designContest
+
+ |
+ + Concurso de proyecto + | +
+ Información acerca de la organización de un concurso de proyecto. + + |
+ + DesignContest object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ designContest
+
+ |
+ + Concurso de proyecto + | +
+ Información acerca de la organización de un concurso de proyecto. + + |
+ + DesignContest object + | +
+ DesignContest +
+ +
+ The extension defines a new DesignContest object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ selectedParticipants
+
+ |
+ + Participantes seleccionados + | +
+ The organizations that have already been selected to participate in the design contest. + + |
+ + array of OrganizationReference objects + | +
+
+ hasPrizes
+
+ |
+ + Tiene premios + | +
+ Si se adjudicarán los premios en el concurso de proyecto. + + |
+ + boolean + | +
+
+ prizes
+
+ |
+ + Premio + | +
+ Información acerca de los premios adjudicados en el concurso de proyecto. + + |
+ + Prizes object + | +
+
+ rewardsDetails
+
+ |
+ + Detalles de recompensas + | +
+ Los detalles y condiciones de los pagos a realizar a los participantes. + + |
+ + string + | +
+
+ followUpContracts
+
+ |
+ + Contratos de seguimiento + | +
+ Si los contratos posteriores al concurso de diseño se otorgarán al ganador o a los ganadores del concurso de diseño. + + |
+ + boolean + | +
+
+ bindingJuryDecision
+
+ |
+ + Decisión vinculante del jurado + | +
+ Si la decisión del jurado es vinculante para la entidad adjudicadora. + + |
+ + boolean + | +
+
+ juryMembers
+
+ |
+ + Miembros del jurado + | +
+ Los miembros del jurado. + + |
+ + array of JuryMember objects + | +
+ JuryMember +
+ +
+ The extension defines a new JuryMember object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ name
+
+ |
+ + Nombre + | +
+ El nombre del miembro del jurado. + + |
+ + string + | +
+ Prizes +
+ +
+ The extension defines a new Prizes object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Descripción + | +
+ La descripción de los premios. + + |
+ + string + | +
+
+ details
+
+ |
+ + Details + | +
+ Information about the individual prizes. + + |
+ + array of Prize objects + | +
+ Prize +
+ +
+ The extension defines a new Prize object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ The locally unique identifier for the prize. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ The description of the prize. + + |
+ + string + | +
+
+ value
+
+ |
+ + Value + | +
+ The value of the prize. + + |
+ + Value object + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/document_publisher/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/document_publisher/master/extension.json b/es/extensions/document_publisher/master/extension.json
new file mode 100644
index 000000000..78a87174c
--- /dev/null
+++ b/es/extensions/document_publisher/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Document publisher",
+ "es": "Document publisher"
+ },
+ "description": {
+ "en": "Adds a publisher field to the document object.",
+ "es": "Adds a publisher field to the document object."
+ },
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting-extensions/ocds_document_publisher_extension"
+ },
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+partyRole.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/document_publisher/master/index.html b/es/extensions/document_publisher/master/index.html
new file mode 100644
index 000000000..a5254267b
--- /dev/null
+++ b/es/extensions/document_publisher/master/index.html
@@ -0,0 +1,307 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Document publisher +
+ ++ Adds a publisher field to the document object. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ informationService
+
+ |
+ + Information service + | +
+ An organization that can provide information regarding specific aspects of the contracting process. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/document_publisher/master/release-schema.json b/es/extensions/document_publisher/master/release-schema.json
new file mode 100644
index 000000000..fe549fb2c
--- /dev/null
+++ b/es/extensions/document_publisher/master/release-schema.json
@@ -0,0 +1,13 @@
+{
+ "definitions": {
+ "Document": {
+ "properties": {
+ "publisher": {
+ "title": "Publisher",
+ "description": "The organization responsible for making the document available.",
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/document_publisher/master/schema/index.html b/es/extensions/document_publisher/master/schema/index.html
new file mode 100644
index 000000000..bfde0a903
--- /dev/null
+++ b/es/extensions/document_publisher/master/schema/index.html
@@ -0,0 +1,236 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Document publisher +
+ ++ Adds a publisher field to the document object. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a publisher field to the document object and an 'informationService' role to indicate the organization responsible for making the document available.
+Usage
+For each organization referenced by a Document.publisher field, add the 'informationService' code to its roles array.
Legal context
+In the European Union, this extension's fields correspond to eForms OPT-301 (Party ID reference). For correspondences to eForms fields, see OCDS for eForms.
+Example
+{
+ "parties": [
+ {
+ "id": "ORG-0001",
+ "roles": [
+ "informationService"
+ ]
+ }
+ ],
+ "tender": {
+ "id": "1",
+ "documents": [
+ {
+ "id": "1",
+ "publisher": {
+ "id": "ORG-0001"
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/documentation_details/index.html b/es/extensions/documentation_details/index.html
new file mode 100644
index 000000000..5f5583610
--- /dev/null
+++ b/es/extensions/documentation_details/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Document publisher +
+ ++ Adds a publisher field to the document object. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Document +
+ +
+ The extension defines these fields in the Document object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ publisher
+
+ |
+ + Publisher + | +
+ The organization responsible for making the document available. + + |
+ + OrganizationReference object + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/documentation_details/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/documentation_details/master/codelists/language.csv b/es/extensions/documentation_details/master/codelists/language.csv
new file mode 100644
index 000000000..5749f4af7
--- /dev/null
+++ b/es/extensions/documentation_details/master/codelists/language.csv
@@ -0,0 +1,185 @@
+Code,Title
+aa,Afar
+ab,Abkhazian
+ae,Avestan
+af,Afrikaans
+ak,Akan
+am,Amharic
+an,Aragonese
+ar,Arabic
+as,Assamese
+av,Avaric
+ay,Aymara
+az,Azerbaijani
+ba,Bashkir
+be,Belarusian
+bg,Bulgarian
+bh,Bihari languages
+bi,Bislama
+bm,Bambara
+bn,Bengali
+bo,Tibetan
+br,Breton
+bs,Bosnian
+ca,"Catalan, Valencian"
+ce,Chechen
+ch,Chamorro
+co,Corsican
+cr,Cree
+cs,Czech
+cu,"Church Slavic, Old Slavonic, Church Slavonic, Old Bulgarian, Old Church Slavonic"
+cv,Chuvash
+cy,Welsh
+da,Danish
+de,German
+dv,"Divehi, Dhivehi, Maldivian"
+dz,Dzongkha
+ee,Ewe
+el,Modern Greek
+en,English
+eo,Esperanto
+es,"Spanish, Castilian"
+et,Estonian
+eu,Basque
+fa,Persian
+ff,Fulah
+fi,Finnish
+fj,Fijian
+fo,Faroese
+fr,French
+fy,Western Frisian
+ga,Irish
+gd,"Gaelic, Scottish Gaelic"
+gl,Galician
+gn,Guarani
+gu,Gujarati
+gv,Manx
+ha,Hausa
+he,Hebrew
+hi,Hindi
+ho,Hiri Motu
+hr,Croatian
+ht,"Haitian, Haitian Creole"
+hu,Hungarian
+hy,Armenian
+hz,Herero
+ia,Interlingua
+id,Indonesian
+ie,"Interlingue, Occidental"
+ig,Igbo
+ii,"Sichuan Yi, Nuosu"
+ik,Inupiaq
+io,Ido
+is,Icelandic
+it,Italian
+iu,Inuktitut
+ja,Japanese
+jv,Javanese
+ka,Georgian
+kg,Kongo
+ki,"Kikuyu, Gikuyu"
+kj,"Kuanyama, Kwanyama"
+kk,Kazakh
+kl,"Kalaallisut, Greenlandic"
+km,Central Khmer
+kn,Kannada
+ko,Korean
+kr,Kanuri
+ks,Kashmiri
+ku,Kurdish
+kv,Komi
+kw,Cornish
+ky,"Kirghiz, Kyrgyz"
+la,Latin
+lb,"Luxembourgish, Letzeburgesch"
+lg,Ganda
+li,"Limburgan, Limburger, Limburgish"
+ln,Lingala
+lo,Lao
+lt,Lithuanian
+lu,Luba-Katanga
+lv,Latvian
+mg,Malagasy
+mh,Marshallese
+mi,Maori
+mk,Macedonian
+ml,Malayalam
+mn,Mongolian
+mr,Marathi
+ms,Malay
+mt,Maltese
+my,Burmese
+na,Nauru
+nb,Norwegian Bokmål
+nd,North Ndebele
+ne,Nepali
+ng,Ndonga
+nl,"Dutch, Flemish"
+nn,Norwegian Nynorsk
+no,Norwegian
+nr,South Ndebele
+nv,"Navajo, Navaho"
+ny,"Chichewa, Chewa, Nyanja"
+oc,Occitan
+oj,Ojibwa
+om,Oromo
+or,Oriya
+os,"Ossetian, Ossetic"
+pa,"Panjabi, Punjabi"
+pi,Pali
+pl,Polish
+ps,"Pushto, Pashto"
+pt,Portuguese
+qu,Quechua
+rm,Romansh
+rn,Rundi
+ro,"Romanian, Moldavian, Moldovan"
+ru,Russian
+rw,Kinyarwanda
+sa,Sanskrit
+sc,Sardinian
+sd,Sindhi
+se,Northern Sami
+sg,Sango
+si,"Sinhala, Sinhalese"
+sk,Slovak
+sl,Slovenian
+sm,Samoan
+sn,Shona
+so,Somali
+sq,Albanian
+sr,Serbian
+ss,Swati
+st,Southern Sotho
+su,Sundanese
+sv,Swedish
+sw,Swahili
+ta,Tamil
+te,Telugu
+tg,Tajik
+th,Thai
+ti,Tigrinya
+tk,Turkmen
+tl,Tagalog
+tn,Tswana
+to,Tonga
+tr,Turkish
+ts,Tsonga
+tt,Tatar
+tw,Twi
+ty,Tahitian
+ug,"Uighur, Uyghur"
+uk,Ukrainian
+ur,Urdu
+uz,Uzbek
+ve,Venda
+vi,Vietnamese
+vo,Volapük
+wa,Walloon
+wo,Wolof
+xh,Xhosa
+yi,Yiddish
+yo,Yoruba
+za,"Zhuang, Chuang"
+zh,Chinese
+zu,Zulu
diff --git a/es/extensions/documentation_details/master/extension.json b/es/extensions/documentation_details/master/extension.json
new file mode 100644
index 000000000..fac7335b0
--- /dev/null
+++ b/es/extensions/documentation_details/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Document Details",
+ "es": "Detalles de Documentos"
+ },
+ "description": {
+ "en": "Adds fields to the document object for page references, access details and author information.",
+ "es": "Agrega campos al objeto document para referencias a p\u00e1ginas, acceso a detalles e informaci\u00f3n del autor."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/documentation_details/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "language.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/documentation_details/master/index.html b/es/extensions/documentation_details/master/index.html
new file mode 100644
index 000000000..4bc8f340a
--- /dev/null
+++ b/es/extensions/documentation_details/master/index.html
@@ -0,0 +1,358 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Detalles de Documentos +
+ ++ Agrega campos al objeto document para referencias a páginas, acceso a detalles e información del autor. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ language.csv +
+ +
+ You can download the language.csv file in English.
+
| + Code + | ++ Title + | +
|---|---|
+
+ aa
+
+ |
+ + Afar + | +
+
+ ab
+
+ |
+ + Abkhazian + | +
+
+ ae
+
+ |
+ + Avestan + | +
+
+ af
+
+ |
+ + Afrikaans + | +
+
+ ak
+
+ |
+ + Akan + | +
+
+ am
+
+ |
+ + Amharic + | +
+
+ an
+
+ |
+ + Aragonese + | +
+
+ ar
+
+ |
+ + Arabic + | +
+
+ as
+
+ |
+ + Assamese + | +
+
+ av
+
+ |
+ + Avaric + | +
+
+ ay
+
+ |
+ + Aymara + | +
+
+ az
+
+ |
+ + Azerbaijani + | +
+
+ ba
+
+ |
+ + Bashkir + | +
+
+ be
+
+ |
+ + Belarusian + | +
+
+ bg
+
+ |
+ + Bulgarian + | +
+
+ bh
+
+ |
+ + Bihari languages + | +
+
+ bi
+
+ |
+ + Bislama + | +
+
+ bm
+
+ |
+ + Bambara + | +
+
+ bn
+
+ |
+ + Bengali + | +
+
+ bo
+
+ |
+ + Tibetan + | +
+
+ br
+
+ |
+ + Breton + | +
+
+ bs
+
+ |
+ + Bosnian + | +
+
+ ca
+
+ |
+ + Catalan, Valencian + | +
+
+ ce
+
+ |
+ + Chechen + | +
+
+ ch
+
+ |
+ + Chamorro + | +
+
+ co
+
+ |
+ + Corsican + | +
+
+ cr
+
+ |
+ + Cree + | +
+
+ cs
+
+ |
+ + Czech + | +
+
+ cu
+
+ |
+ + Church Slavic, Old Slavonic, Church Slavonic, Old Bulgarian, Old Church Slavonic + | +
+
+ cv
+
+ |
+ + Chuvash + | +
+
+ cy
+
+ |
+ + Welsh + | +
+
+ da
+
+ |
+ + Danish + | +
+
+ de
+
+ |
+ + German + | +
+
+ dv
+
+ |
+ + Divehi, Dhivehi, Maldivian + | +
+
+ dz
+
+ |
+ + Dzongkha + | +
+
+ ee
+
+ |
+ + Ewe + | +
+
+ el
+
+ |
+ + Modern Greek + | +
+
+ en
+
+ |
+ + English + | +
+
+ eo
+
+ |
+ + Esperanto + | +
+
+ es
+
+ |
+ + Spanish, Castilian + | +
+
+ et
+
+ |
+ + Estonian + | +
+
+ eu
+
+ |
+ + Basque + | +
+
+ fa
+
+ |
+ + Persian + | +
+
+ ff
+
+ |
+ + Fulah + | +
+
+ fi
+
+ |
+ + Finnish + | +
+
+ fj
+
+ |
+ + Fijian + | +
+
+ fo
+
+ |
+ + Faroese + | +
+
+ fr
+
+ |
+ + French + | +
+
+ fy
+
+ |
+ + Western Frisian + | +
+
+ ga
+
+ |
+ + Irish + | +
+
+ gd
+
+ |
+ + Gaelic, Scottish Gaelic + | +
+
+ gl
+
+ |
+ + Galician + | +
+
+ gn
+
+ |
+ + Guarani + | +
+
+ gu
+
+ |
+ + Gujarati + | +
+
+ gv
+
+ |
+ + Manx + | +
+
+ ha
+
+ |
+ + Hausa + | +
+
+ he
+
+ |
+ + Hebrew + | +
+
+ hi
+
+ |
+ + Hindi + | +
+
+ ho
+
+ |
+ + Hiri Motu + | +
+
+ hr
+
+ |
+ + Croatian + | +
+
+ ht
+
+ |
+ + Haitian, Haitian Creole + | +
+
+ hu
+
+ |
+ + Hungarian + | +
+
+ hy
+
+ |
+ + Armenian + | +
+
+ hz
+
+ |
+ + Herero + | +
+
+ ia
+
+ |
+ + Interlingua + | +
+
+ id
+
+ |
+ + Indonesian + | +
+
+ ie
+
+ |
+ + Interlingue, Occidental + | +
+
+ ig
+
+ |
+ + Igbo + | +
+
+ ii
+
+ |
+ + Sichuan Yi, Nuosu + | +
+
+ ik
+
+ |
+ + Inupiaq + | +
+
+ io
+
+ |
+ + Ido + | +
+
+ is
+
+ |
+ + Icelandic + | +
+
+ it
+
+ |
+ + Italian + | +
+
+ iu
+
+ |
+ + Inuktitut + | +
+
+ ja
+
+ |
+ + Japanese + | +
+
+ jv
+
+ |
+ + Javanese + | +
+
+ ka
+
+ |
+ + Georgian + | +
+
+ kg
+
+ |
+ + Kongo + | +
+
+ ki
+
+ |
+ + Kikuyu, Gikuyu + | +
+
+ kj
+
+ |
+ + Kuanyama, Kwanyama + | +
+
+ kk
+
+ |
+ + Kazakh + | +
+
+ kl
+
+ |
+ + Kalaallisut, Greenlandic + | +
+
+ km
+
+ |
+ + Central Khmer + | +
+
+ kn
+
+ |
+ + Kannada + | +
+
+ ko
+
+ |
+ + Korean + | +
+
+ kr
+
+ |
+ + Kanuri + | +
+
+ ks
+
+ |
+ + Kashmiri + | +
+
+ ku
+
+ |
+ + Kurdish + | +
+
+ kv
+
+ |
+ + Komi + | +
+
+ kw
+
+ |
+ + Cornish + | +
+
+ ky
+
+ |
+ + Kirghiz, Kyrgyz + | +
+
+ la
+
+ |
+ + Latin + | +
+
+ lb
+
+ |
+ + Luxembourgish, Letzeburgesch + | +
+
+ lg
+
+ |
+ + Ganda + | +
+
+ li
+
+ |
+ + Limburgan, Limburger, Limburgish + | +
+
+ ln
+
+ |
+ + Lingala + | +
+
+ lo
+
+ |
+ + Lao + | +
+
+ lt
+
+ |
+ + Lithuanian + | +
+
+ lu
+
+ |
+ + Luba-Katanga + | +
+
+ lv
+
+ |
+ + Latvian + | +
+
+ mg
+
+ |
+ + Malagasy + | +
+
+ mh
+
+ |
+ + Marshallese + | +
+
+ mi
+
+ |
+ + Maori + | +
+
+ mk
+
+ |
+ + Macedonian + | +
+
+ ml
+
+ |
+ + Malayalam + | +
+
+ mn
+
+ |
+ + Mongolian + | +
+
+ mr
+
+ |
+ + Marathi + | +
+
+ ms
+
+ |
+ + Malay + | +
+
+ mt
+
+ |
+ + Maltese + | +
+
+ my
+
+ |
+ + Burmese + | +
+
+ na
+
+ |
+ + Nauru + | +
+
+ nb
+
+ |
+ + Norwegian Bokmål + | +
+
+ nd
+
+ |
+ + North Ndebele + | +
+
+ ne
+
+ |
+ + Nepali + | +
+
+ ng
+
+ |
+ + Ndonga + | +
+
+ nl
+
+ |
+ + Dutch, Flemish + | +
+
+ nn
+
+ |
+ + Norwegian Nynorsk + | +
+
+ no
+
+ |
+ + Norwegian + | +
+
+ nr
+
+ |
+ + South Ndebele + | +
+
+ nv
+
+ |
+ + Navajo, Navaho + | +
+
+ ny
+
+ |
+ + Chichewa, Chewa, Nyanja + | +
+
+ oc
+
+ |
+ + Occitan + | +
+
+ oj
+
+ |
+ + Ojibwa + | +
+
+ om
+
+ |
+ + Oromo + | +
+
+ or
+
+ |
+ + Oriya + | +
+
+ os
+
+ |
+ + Ossetian, Ossetic + | +
+
+ pa
+
+ |
+ + Panjabi, Punjabi + | +
+
+ pi
+
+ |
+ + Pali + | +
+
+ pl
+
+ |
+ + Polish + | +
+
+ ps
+
+ |
+ + Pushto, Pashto + | +
+
+ pt
+
+ |
+ + Portuguese + | +
+
+ qu
+
+ |
+ + Quechua + | +
+
+ rm
+
+ |
+ + Romansh + | +
+
+ rn
+
+ |
+ + Rundi + | +
+
+ ro
+
+ |
+ + Romanian, Moldavian, Moldovan + | +
+
+ ru
+
+ |
+ + Russian + | +
+
+ rw
+
+ |
+ + Kinyarwanda + | +
+
+ sa
+
+ |
+ + Sanskrit + | +
+
+ sc
+
+ |
+ + Sardinian + | +
+
+ sd
+
+ |
+ + Sindhi + | +
+
+ se
+
+ |
+ + Northern Sami + | +
+
+ sg
+
+ |
+ + Sango + | +
+
+ si
+
+ |
+ + Sinhala, Sinhalese + | +
+
+ sk
+
+ |
+ + Slovak + | +
+
+ sl
+
+ |
+ + Slovenian + | +
+
+ sm
+
+ |
+ + Samoan + | +
+
+ sn
+
+ |
+ + Shona + | +
+
+ so
+
+ |
+ + Somali + | +
+
+ sq
+
+ |
+ + Albanian + | +
+
+ sr
+
+ |
+ + Serbian + | +
+
+ ss
+
+ |
+ + Swati + | +
+
+ st
+
+ |
+ + Southern Sotho + | +
+
+ su
+
+ |
+ + Sundanese + | +
+
+ sv
+
+ |
+ + Swedish + | +
+
+ sw
+
+ |
+ + Swahili + | +
+
+ ta
+
+ |
+ + Tamil + | +
+
+ te
+
+ |
+ + Telugu + | +
+
+ tg
+
+ |
+ + Tajik + | +
+
+ th
+
+ |
+ + Thai + | +
+
+ ti
+
+ |
+ + Tigrinya + | +
+
+ tk
+
+ |
+ + Turkmen + | +
+
+ tl
+
+ |
+ + Tagalog + | +
+
+ tn
+
+ |
+ + Tswana + | +
+
+ to
+
+ |
+ + Tonga + | +
+
+ tr
+
+ |
+ + Turkish + | +
+
+ ts
+
+ |
+ + Tsonga + | +
+
+ tt
+
+ |
+ + Tatar + | +
+
+ tw
+
+ |
+ + Twi + | +
+
+ ty
+
+ |
+ + Tahitian + | +
+
+ ug
+
+ |
+ + Uighur, Uyghur + | +
+
+ uk
+
+ |
+ + Ukrainian + | +
+
+ ur
+
+ |
+ + Urdu + | +
+
+ uz
+
+ |
+ + Uzbek + | +
+
+ ve
+
+ |
+ + Venda + | +
+
+ vi
+
+ |
+ + Vietnamese + | +
+
+ vo
+
+ |
+ + Volapük + | +
+
+ wa
+
+ |
+ + Walloon + | +
+
+ wo
+
+ |
+ + Wolof + | +
+
+ xh
+
+ |
+ + Xhosa + | +
+
+ yi
+
+ |
+ + Yiddish + | +
+
+ yo
+
+ |
+ + Yoruba + | +
+
+ za
+
+ |
+ + Zhuang, Chuang + | +
+
+ zh
+
+ |
+ + Chinese + | +
+
+ zu
+
+ |
+ + Zulu + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/documentation_details/master/release-schema.json b/es/extensions/documentation_details/master/release-schema.json
new file mode 100644
index 000000000..fd8736d70
--- /dev/null
+++ b/es/extensions/documentation_details/master/release-schema.json
@@ -0,0 +1,69 @@
+{
+ "definitions": {
+ "Document": {
+ "properties": {
+ "pageStart": {
+ "title": "Inicio de p\u00e1gina",
+ "description": "Cuando la informaci\u00f3n mencionada exista dentro de un documento grande, se debe indicar la primera p\u00e1gina en la que se puede encontrar. Esto debe de referirse al n\u00famero de p\u00e1gina impreso, no al n\u00famero de p\u00e1gina reportado por software.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "pageEnd": {
+ "title": "Fin de p\u00e1gina",
+ "description": "Cuando la informaci\u00f3n mencionada existe dentro de un documento grande, se debe indicar la \u00faltima p\u00e1gina en la que se puede encontrar. Esto debe de referirse al n\u00famero de p\u00e1gina impreso, no al n\u00famero de p\u00e1gina reportado por software.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "accessDetails": {
+ "title": "Detalles de acceso",
+ "description": "Una descripci\u00f3n de cualquier arreglo especial necesitado para acceder a estos documentos, por ejemplo: registrarse para acceder, pagar una tarifa o visitar un lugar para inspeccionar el documento.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "accessDetailsURL": {
+ "title": "Access details URL",
+ "description": "A web address for information on any special arrangements needed to access the document.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "author": {
+ "title": "Autor",
+ "description": "Los nombres de los autores del documento.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "unofficialTranslations": {
+ "title": "Unofficial translations",
+ "description": "The languages in which unofficial translations of the document are available, from the open [language](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#language) codelist. A [BCP47 language tag](https://www.w3.org/International/articles/language-tags/) is allowed, if there is a user need for the additional information.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "language.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/documentation_details/master/schema/index.html b/es/extensions/documentation_details/master/schema/index.html
new file mode 100644
index 000000000..8b1b30b95
--- /dev/null
+++ b/es/extensions/documentation_details/master/schema/index.html
@@ -0,0 +1,321 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Detalles de Documentos +
+ ++ Agrega campos al objeto document para referencias a páginas, acceso a detalles e información del autor. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Los objetos document son usados para describir y enlazar a documentos. Esta extensión agrega campos a los objetos documento para:
+-
+
- Indique los números de página en los que se puede encontrar información relevante dentro de un documento grande +
- Describe cualquier arreglo especial necesario para acceder al documento. +
- Nombre del autor del documento (a no ser confundido con su publicador) +
- Indicate the languages in which unofficial translations of the document are available +
Los casos de usos incluyen:
+-
+
- Acceder al documento y localizar la información en él +
- Comprobar si los autores participan de otras formas en el proceso de contratación, por ejemplo, como licitadores +
- Medir la accesibilidad de los documentos +
Ejemplo
+{
+ "tender": {
+ "documents": [
+ {
+ "id": "1",
+ "documentType": "equityTransferCaps",
+ "title": "Equity transfer cap terms",
+ "description": "No equity transfer is permitted until construction is completed. See document for more details.",
+ "url": "http://example.com/ppp_unit/documents/contracts/4g_network_signed_contract.pdf",
+ "language": "en",
+ "unofficialTranslations": [
+ "it"
+ ],
+ "pageStart": "334",
+ "pageEnd": "336",
+ "accessDetails": "This document can only be accessed by visiting the PPP unit office by appointment. Please see the PPP unit website for further details.",
+ "accessDetailsURL": "http://example.com/ppp_unit/registration/",
+ "author": "Contract department, PPP unit"
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-08-04
+-
+
- Change unofficialTranslation field to
unofficialTranslationsarray of languages.
+
2023-04-05
+-
+
- Add
accessDetailsURLand unofficialTranslation fields.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2020-04-15
+-
+
- Mejora en la documentación +
- Uso de palabras clave no normativas donde es apropiado +
2019-01-30
+-
+
- Elimina la propiedad obsoleta
mergeStrategy
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/enquiries/index.html b/es/extensions/enquiries/index.html
new file mode 100644
index 000000000..60a18ebab
--- /dev/null
+++ b/es/extensions/enquiries/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Detalles de Documentos +
+ ++ Agrega campos al objeto document para referencias a páginas, acceso a detalles e información del autor. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Document +
+ +
+ The extension defines these fields in the Document object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ pageStart
+
+ |
+ + Inicio de página + | +
+ Cuando la información mencionada exista dentro de un documento grande, se debe indicar la primera página en la que se puede encontrar. Esto debe de referirse al número de página impreso, no al número de página reportado por software. + + |
+ + string + | +
+
+ pageEnd
+
+ |
+ + Fin de página + | +
+ Cuando la información mencionada existe dentro de un documento grande, se debe indicar la última página en la que se puede encontrar. Esto debe de referirse al número de página impreso, no al número de página reportado por software. + + |
+ + string + | +
+
+ accessDetails
+
+ |
+ + Detalles de acceso + | +
+ Una descripción de cualquier arreglo especial necesitado para acceder a estos documentos, por ejemplo: registrarse para acceder, pagar una tarifa o visitar un lugar para inspeccionar el documento. + + |
+ + string + | +
+
+ accessDetailsURL
+
+ |
+ + Access details URL + | +
+ A web address for information on any special arrangements needed to access the document. + + |
+ + string + | +
+
+ author
+
+ |
+ + Autor + | +
+ Los nombres de los autores del documento. + + |
+ + string + | +
+
+ unofficialTranslations
+
+ |
+ + Unofficial translations + | +
+ The languages in which unofficial translations of the document are available, from the open language codelist. A BCP47 language tag is allowed, if there is a user need for the additional information. + + |
+ + array of strings from open language codelist + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/enquiries/master/ +
+Not Found
+The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
diff --git a/es/extensions/enquiries/master/extension.json b/es/extensions/enquiries/master/extension.json new file mode 100644 index 000000000..0588b98e1 --- /dev/null +++ b/es/extensions/enquiries/master/extension.json @@ -0,0 +1,23 @@ +{ + "name": { + "en": "Enquiries", + "es": "Consultas" + }, + "description": { + "en": "The enquiries extension can be used to record questions raised during a contracting process, and the answers provided.", + "es": "La extensi\u00f3n sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contrataci\u00f3n y las respuestas proporcionadas." + }, + "documentationUrl": { + "en": "https://extensions.open-contracting.org/en/extensions/enquiries/" + }, + "compatibility": [ + "1.1" + ], + "schemas": [ + "release-schema.json" + ], + "contactPoint": { + "name": "Open Contracting Partnership", + "email": "data@open-contracting.org" + } +} diff --git a/es/extensions/enquiries/master/index.html b/es/extensions/enquiries/master/index.html new file mode 100644 index 000000000..fc1910aca --- /dev/null +++ b/es/extensions/enquiries/master/index.html @@ -0,0 +1,367 @@ + + + + + + + + + +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/enquiries/master/release-schema.json b/es/extensions/enquiries/master/release-schema.json
new file mode 100644
index 000000000..7e62678e0
--- /dev/null
+++ b/es/extensions/enquiries/master/release-schema.json
@@ -0,0 +1,103 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "enquiries": {
+ "title": "Consultas",
+ "description": "Preguntas enviadas a la entidad contratante y las respuestas dadas",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Enquiry"
+ },
+ "uniqueItems": true
+ }
+ }
+ },
+ "Enquiry": {
+ "title": "Consulta",
+ "description": "Una pregunta relacionada con el proceso de contrataciones, hecha generalmente durante el per\u00edodo de preguntas.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador \u00fanico para la consulta.",
+ "type": "string"
+ },
+ "date": {
+ "title": "Fecha",
+ "description": "La fecha en que se recibi\u00f3 o proces\u00f3 la consulta.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "author": {
+ "title": "Autor de la pregunta",
+ "description": "The organization asking this question. The corresponding entry in the `parties` array should have 'enquirer' in its `roles` array.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "title": {
+ "title": "T\u00edtulo de la pregunta",
+ "description": "La l\u00ednea de asunto de la pregunta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "El cuerpo de la pregunta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "answer": {
+ "title": "Respuesta",
+ "description": "La respuesta a esta pregunta, cuando est\u00e9 disponible.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "dateAnswered": {
+ "title": "Fecha de respuesta",
+ "description": "La fecha en que se proporcion\u00f3 la respuesta a la pregunta.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "relatedItem": {
+ "title": "Art\u00edculo relacionado",
+ "description": "Si esta pregunta se refiere a una partida presupuestaria en espec\u00edfico, este campo contiene el identificador de la partida.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Lote relacionado",
+ "description": "Cuando se usan lotes, si esta pregunta se refiere a un lote espec\u00edfico, este campo contiene el identificador de lote.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "threadID": {
+ "title": "Identificador de hilo",
+ "description": "Si esta pregunta y respuesta forma parte de un hilo de discusi\u00f3n (ej. la pregunta es la continuaci\u00f3n a una respuesta previa) un identificador de hilo puede ser usado para asociar m\u00faltiples preguntas.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/enquiries/master/schema/index.html b/es/extensions/enquiries/master/schema/index.html
new file mode 100644
index 000000000..f3f4ea30d
--- /dev/null
+++ b/es/extensions/enquiries/master/schema/index.html
@@ -0,0 +1,444 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Consultas +
+ ++ La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas.
+Estructura
+La extensión agrega una lista de enquiries a la licitación, la cual consiste en uno o más objetos de consultas, cada uno con campos para una pregunta y una respuesta.
Ejemplo:
+{
+ "tender": {
+ "enquiries": [
+ {
+ "id": "Q1",
+ "date": "2017-01-22T14:55:00Z",
+ "author": {
+ "name": "Open Data Services Co-op",
+ "id": "GB-COH-09506232"
+ },
+ "title": "Variations of timeline accepted?",
+ "description": "The tender specifies delivery of Item 1 by end of March 2017. Will alternative proposals for the timeline be considered?",
+ "dateAnswered": "2017-02-05T09:00:00Z",
+ "answer": "There is a hard deadline of 15th April 2017. All proposals must be for delivery of Item 1 by this date.",
+ "relatedItem": "1",
+ "threadID": "1"
+ }
+ ]
+ }
+}
+Los documentos de soporte con aclaraciones o un documento completo que contenga respuestas a preguntas pueden incluirse en la matriz tender/documents con un documentType de 'clarifications'.
Si las respuestas a una pregunta sólo están disponibles en los documentos adjuntos, se puede ingresar un valor answer como "Consultar la sección N de (nombre del documento) en la sección de documentos" para permitir que los usuarios identifiquen que se ha dado respuesta a esta pregunta.
Cuando un sistema permite un formato de discusión, en el que cada respuesta puede ir seguida de otra pregunta de aclaración, el campo threadID puede utilizarse para enlazar varias entradas en la lista enquiries.
Guidance
+Las implementaciones pueden variar en la cantidad de información de consultas que proporcionan y cuándo se proporciona.
+Algunos editores pueden omitir la identidad del autor de la pregunta para proteger la confidencialidad de los solicitantes, o pueden anonimizar esta información (por ejemplo, simplemente poniendo el nombre del autor como "Organización 1" u "Organización 2" para que sea posible ver preguntas de la misma organización , sin conocer la identidad de esa organización.)
+Los campos relatedItem y relatedLot están disponibles para su uso cuando se pueden hacer preguntas en relación con un lote o artículo específico.
Cuando sea posible, el enfoque recomendado es:
+-
+
- Haga una entrega con una etiqueta
tenderUpdatepara cada nueva pregunta o lote de preguntas recibidas, proporcionando una matriz de preguntas con cada una de las preguntas en;
+ - Haga una entrega con una etiqueta de
tenderUpdatecuando se proporcionen las respuestas a las preguntas, actualizando la matriz de consultas anteriores para que cada entrada contenga una pregunta y una respuesta;
+
Este enfoque permitirá a las aplicaciones de terceros vigilar las entregas que proporcionen respuestas a las preguntas y apoyará en el monitoreo de adquisiciones en la revisión de la forma en que se responden las preguntas.
+Recomendamos que los publicadores proporcionen respuestas como texto sin formato o con un marcado HTML mínimo (párrafos y saltos de línea) y que las aplicaciones que consumen analicen el texto apropiadamente para darle formato para legibilidad (por ejemplo, reemplazar saltos de línea con saltos de párrafo en HTML).
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+No entregado
+-
+
- Eliminar la lista de códigos
+partyRole.csv, cuyos códigos ya existen en OCDS 1.1
+ - Make
Enquiry.idrequired so that enquiries are merged by identifier
+ - Make
Tender.enquiriesnon-nullable
+
v1.1.5
+-
+
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- Quita las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- Usar
OrganizationReferenceen lugar deOrganizationparaEnquiry.author
+ - Corrige el nombre de la lista de código + partyRole.csv (era + partyRoles.csv) +
- Permitir que
Enquiry.datesea null
+ - Enlista listas de códigos en extension.json +
- Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/enquiries/v1.1.4/README.md b/es/extensions/enquiries/v1.1.4/README.md
new file mode 100644
index 000000000..485cf0e09
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.4/README.md
@@ -0,0 +1,75 @@
+# Consultas
+
+La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas.
+
+## Estructura
+
+La extensión agrega una lista de `enquiries` a la licitación, la cual consiste en uno o más objetos de consultas, cada uno con campos para una pregunta y una respuesta.
+
+Ejemplo:
+
+```json
+{
+ "tender": {
+ "enquiries": [
+ {
+ "id": "Q1",
+ "date": "2017-01-22T14:55:00Z",
+ "author": {
+ "name": "Open Data Services Co-op",
+ "id": "GB-COH-09506232"
+ },
+ "title": "Variations of timeline accepted?",
+ "description": "The tender specifies delivery of Item 1 by end of March 2017. Will alternative proposals for the timeline be considered?",
+ "dateAnswered": "2017-02-05T09:00:00Z",
+ "answer": "There is a hard deadline of 15th April 2017. All proposals must be for delivery of Item 1 by this date.",
+ "relatedItem": "1",
+ "threadID": "1"
+ }
+ ]
+ }
+}
+```
+
+Los documentos de soporte con aclaraciones o un documento completo que contenga respuestas a preguntas pueden incluirse en la lista `tender/documents` con un `documentType` de 'clarifications'.
+
+Si las respuestas a una pregunta sólo están disponibles en los documentos adjuntos, se puede ingresar un valor `answer` como "Consultar la sección N de (nombre del documento) en la sección de documentos" para permitir que los usuarios identifiquen que se ha dado respuesta a esta pregunta.
+
+Cuando un sistema permite un formato de discusión, donde cada respuesta puede ser seguida por una pregunta de aclaración adicional, se puede usar la propiedad `threadID` para enlazar múltiples entradas en la matriz `enquiries`.
+
+## Guía de uso
+
+Las implementaciones pueden variar en la cantidad de información de consultas que proporcionan y cuándo se proporciona.
+
+Algunos editores pueden omitir la identidad del autor de la pregunta para proteger la confidencialidad de los solicitantes, o pueden anonimizar esta información (por ejemplo, simplemente poniendo el nombre del autor como "Organización 1" u "Organización 2" para que sea posible ver preguntas de la misma organización , Pero no conocer la identidad de esa organización.)
+
+Las propiedades `relatedItem` y `relatedLot` están disponibles para su uso cuando se pueden hacer preguntas en relación con un lote o artículo específico.
+
+Cuando sea posible, el enfoque recomendado es:
+
+- Haga una entrega con una etiqueta `tenderUpdate` para cada nueva pregunta o lote de preguntas recibidas, proporcionando una lista de preguntas con cada una de las preguntas en;
+- Haga una entrega con una etiqueta de `tenderUpdate` cuando se proporcionen las respuestas a las preguntas, actualizando la lista de consultas anteriores para que cada entrada contenga una pregunta y una respuesta;
+
+Este enfoque permitirá a las aplicaciones de terceros vigilar las entregas que proporcionen respuestas a las preguntas y apoyará en el monitoreo de adquisiciones en la revisión de la forma en que se responden las preguntas.
+
+Recomendamos que los publicadores proporcionen respuestas como texto sin formato o con un marcado HTML mínimo (párrafos y saltos de línea) y que las aplicaciones que consumen analicen el texto apropiadamente para darle formato para legibilidad (por ejemplo, reemplazar saltos de línea con saltos de párrafo en HTML).
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.4
+
+- Quita las directrices Sphinx del readme
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- Usar `OrganizationReference` en lugar de` Organization` para `Enquiry.author`
+- Corrige el nombre de la lista de código + partyRole.csv (era + partyRoles.csv)
+- Permitir que `Enquiry.date` sea null
+- Enlista listas de códigos en extension.json
+- Usa la licencia Apache 2.0
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/enquiries/v1.1.4/codelists/+partyRole.csv b/es/extensions/enquiries/v1.1.4/codelists/+partyRole.csv
new file mode 100644
index 000000000..d5b0e0fbb
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.4/codelists/+partyRole.csv
@@ -0,0 +1,2 @@
+Código,Título,Descripción
+enquirer,Enquirer,A party who has made an enquiry during the enquiry phase of a contracting process
diff --git a/es/extensions/enquiries/v1.1.4/codelists/index.html b/es/extensions/enquiries/v1.1.4/codelists/index.html
new file mode 100644
index 000000000..349b86a7d
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.4/codelists/index.html
@@ -0,0 +1,238 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Consultas +
+ ++ La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ enquiries
+
+ |
+ + Consultas + | +
+ Preguntas enviadas a la entidad contratante y las respuestas dadas + + |
+ + array of Enquiry objects + | +
+ Enquiry +
+ +
+ The extension defines a new Enquiry object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador único para la consulta. + + |
+ + string + | +
+
+ date
+
+ |
+ + Fecha + | +
+ La fecha en que se recibió o procesó la consulta. + + |
+ + string + | +
+
+ author
+
+ |
+ + Autor de la pregunta + | +
+ The organization asking this question. The corresponding entry in the |
+ + OrganizationReference object + | +
+
+ title
+
+ |
+ + Título de la pregunta + | +
+ La línea de asunto de la pregunta. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ El cuerpo de la pregunta. + + |
+ + string + | +
+
+ answer
+
+ |
+ + Respuesta + | +
+ La respuesta a esta pregunta, cuando esté disponible. + + |
+ + string + | +
+
+ dateAnswered
+
+ |
+ + Fecha de respuesta + | +
+ La fecha en que se proporcionó la respuesta a la pregunta. + + |
+ + string + | +
+
+ relatedItem
+
+ |
+ + Artículo relacionado + | +
+ Si esta pregunta se refiere a una partida presupuestaria en específico, este campo contiene el identificador de la partida. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Lote relacionado + | +
+ Cuando se usan lotes, si esta pregunta se refiere a un lote específico, este campo contiene el identificador de lote. + + |
+ + string + | +
+
+ threadID
+
+ |
+ + Identificador de hilo + | +
+ Si esta pregunta y respuesta forma parte de un hilo de discusión (ej. la pregunta es la continuación a una respuesta previa) un identificador de hilo puede ser usado para asociar múltiples preguntas. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/enquiries/v1.1.4/extension.json b/es/extensions/enquiries/v1.1.4/extension.json
new file mode 100644
index 000000000..1d4becafe
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.4/extension.json
@@ -0,0 +1,22 @@
+{
+ "name": {
+ "en": "Enquiries",
+ "es": "Consultas"
+ },
+ "description": {
+ "en": "The enquiries extension can be used to record questions raised during a contracting process, and the answers provided.",
+ "es": "La extensi\u00f3n sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contrataci\u00f3n y las respuestas proporcionadas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/enquiries/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "+partyRole.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/es/extensions/enquiries/v1.1.4/index.html b/es/extensions/enquiries/v1.1.4/index.html
new file mode 100644
index 000000000..f33766ad6
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.4/index.html
@@ -0,0 +1,352 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Consultas +
+ ++ La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ enquirer
+
+ |
+ + Enquirer + | +
+ A party who has made an enquiry during the enquiry phase of a contracting process + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/enquiries/v1.1.4/release-schema.json b/es/extensions/enquiries/v1.1.4/release-schema.json
new file mode 100644
index 000000000..6ac1d5f53
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.4/release-schema.json
@@ -0,0 +1,105 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "enquiries": {
+ "title": "Consultas",
+ "type": [
+ "array",
+ "null"
+ ],
+ "description": "Preguntas enviadas a la entidad contratante y las respuestas dadas",
+ "items": {
+ "$ref": "#/definitions/Enquiry"
+ }
+ }
+ }
+ },
+ "Enquiry": {
+ "type": "object",
+ "title": "Consulta",
+ "description": "Una pregunta relacionada con el proceso de contrataciones, hecha generalmente durante el per\u00edodo de preguntas.",
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador \u00fanico para la consulta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "date": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "title": "Fecha",
+ "description": "La fecha en que se recibi\u00f3 o proces\u00f3 la consulta.",
+ "format": "date-time"
+ },
+ "author": {
+ "title": "Autor de la pregunta",
+ "description": "El identificador y el nombre de la parte involucrada que hace esta pregunta. Los solicitantes pueden mostrarse en la lista de las partes con un rol de \"enquirer\". Las pol\u00edticas de adquisici\u00f3n var\u00edan en cuanto a si la identidad de los que hacen preguntas debe ser divulgada, o en qu\u00e9 etapa se puede divulgar esta informaci\u00f3n. Cuando no se pueda identificar al solicitante de la informaci\u00f3n, deje la secci\u00f3n de autor en blanco. Los sistemas deber\u00edan de interpretar esta como una pregunta an\u00f3nima.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "title": {
+ "title": "T\u00edtulo de la pregunta",
+ "description": "La l\u00ednea de asunto de la pregunta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "El cuerpo de la pregunta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "answer": {
+ "title": "Respuesta",
+ "description": "La respuesta a esta pregunta, cuando est\u00e9 disponible.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "dateAnswered": {
+ "title": "Fecha de respuesta",
+ "description": "La fecha en que se proporcion\u00f3 la respuesta a la pregunta.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "relatedItem": {
+ "title": "Art\u00edculo relacionado",
+ "description": "Si esta pregunta se refiere a una partida presupuestaria en espec\u00edfico, este campo contiene el identificador de la partida.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Lote relacionado",
+ "description": "Cuando se usan lotes, si esta pregunta se refiere a un lote espec\u00edfico, este campo contiene el identificador de lote.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "threadID": {
+ "title": "Identificador de hilo",
+ "description": "Si esta pregunta y respuesta forma parte de un hilo de discusi\u00f3n (por ejemplo, la pregunta es un seguimiento a una respuesta anterior), se puede usar un identificador de hilo opcional para asociar varias consultas.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/enquiries/v1.1.4/schema/index.html b/es/extensions/enquiries/v1.1.4/schema/index.html
new file mode 100644
index 000000000..86a3ae48e
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.4/schema/index.html
@@ -0,0 +1,449 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Consultas +
+ ++ La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas.
+Estructura
+La extensión agrega una lista de enquiries a la licitación, la cual consiste en uno o más objetos de consultas, cada uno con campos para una pregunta y una respuesta.
Ejemplo:
+{
+ "tender": {
+ "enquiries": [
+ {
+ "id": "Q1",
+ "date": "2017-01-22T14:55:00Z",
+ "author": {
+ "name": "Open Data Services Co-op",
+ "id": "GB-COH-09506232"
+ },
+ "title": "Variations of timeline accepted?",
+ "description": "The tender specifies delivery of Item 1 by end of March 2017. Will alternative proposals for the timeline be considered?",
+ "dateAnswered": "2017-02-05T09:00:00Z",
+ "answer": "There is a hard deadline of 15th April 2017. All proposals must be for delivery of Item 1 by this date.",
+ "relatedItem": "1",
+ "threadID": "1"
+ }
+ ]
+ }
+}
+Los documentos de soporte con aclaraciones o un documento completo que contenga respuestas a preguntas pueden incluirse en la lista tender/documents con un documentType de 'clarifications'.
Si las respuestas a una pregunta sólo están disponibles en los documentos adjuntos, se puede ingresar un valor answer como "Consultar la sección N de (nombre del documento) en la sección de documentos" para permitir que los usuarios identifiquen que se ha dado respuesta a esta pregunta.
Cuando un sistema permite un formato de discusión, donde cada respuesta puede ser seguida por una pregunta de aclaración adicional, se puede usar la propiedad threadID para enlazar múltiples entradas en la matriz enquiries.
Guía de uso
+Las implementaciones pueden variar en la cantidad de información de consultas que proporcionan y cuándo se proporciona.
+Algunos editores pueden omitir la identidad del autor de la pregunta para proteger la confidencialidad de los solicitantes, o pueden anonimizar esta información (por ejemplo, simplemente poniendo el nombre del autor como "Organización 1" u "Organización 2" para que sea posible ver preguntas de la misma organización , Pero no conocer la identidad de esa organización.)
+Las propiedades relatedItem y relatedLot están disponibles para su uso cuando se pueden hacer preguntas en relación con un lote o artículo específico.
Cuando sea posible, el enfoque recomendado es:
+-
+
- Haga una entrega con una etiqueta
tenderUpdatepara cada nueva pregunta o lote de preguntas recibidas, proporcionando una lista de preguntas con cada una de las preguntas en;
+ - Haga una entrega con una etiqueta de
tenderUpdatecuando se proporcionen las respuestas a las preguntas, actualizando la lista de consultas anteriores para que cada entrada contenga una pregunta y una respuesta;
+
Este enfoque permitirá a las aplicaciones de terceros vigilar las entregas que proporcionen respuestas a las preguntas y apoyará en el monitoreo de adquisiciones en la revisión de la forma en que se responden las preguntas.
+Recomendamos que los publicadores proporcionen respuestas como texto sin formato o con un marcado HTML mínimo (párrafos y saltos de línea) y que las aplicaciones que consumen analicen el texto apropiadamente para darle formato para legibilidad (por ejemplo, reemplazar saltos de línea con saltos de párrafo en HTML).
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.4
+-
+
- Quita las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- Usar
OrganizationReferenceen lugar deOrganizationparaEnquiry.author
+ - Corrige el nombre de la lista de código + partyRole.csv (era + partyRoles.csv) +
- Permitir que
Enquiry.datesea null
+ - Enlista listas de códigos en extension.json +
- Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/enquiries/v1.1.5/README.md b/es/extensions/enquiries/v1.1.5/README.md
new file mode 100644
index 000000000..9d678a9f5
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.5/README.md
@@ -0,0 +1,79 @@
+# Consultas
+
+La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas.
+
+## Estructura
+
+La extensión agrega una lista de `enquiries` a la licitación, la cual consiste en uno o más objetos de consultas, cada uno con campos para una pregunta y una respuesta.
+
+Ejemplo:
+
+```json
+{
+ "tender": {
+ "enquiries": [
+ {
+ "id": "Q1",
+ "date": "2017-01-22T14:55:00Z",
+ "author": {
+ "name": "Open Data Services Co-op",
+ "id": "GB-COH-09506232"
+ },
+ "title": "Variations of timeline accepted?",
+ "description": "The tender specifies delivery of Item 1 by end of March 2017. Will alternative proposals for the timeline be considered?",
+ "dateAnswered": "2017-02-05T09:00:00Z",
+ "answer": "There is a hard deadline of 15th April 2017. All proposals must be for delivery of Item 1 by this date.",
+ "relatedItem": "1",
+ "threadID": "1"
+ }
+ ]
+ }
+}
+```
+
+Los documentos de soporte con aclaraciones o un documento completo que contenga respuestas a preguntas pueden incluirse en la matriz `tender/documents` con un `documentType` de 'clarifications'.
+
+Si las respuestas a una pregunta sólo están disponibles en los documentos adjuntos, se puede ingresar un valor `answer` como "Consultar la sección N de (nombre del documento) en la sección de documentos" para permitir que los usuarios identifiquen que se ha dado respuesta a esta pregunta.
+
+Cuando un sistema permite un formato de discusión, donde cada respuesta puede ser seguida por una pregunta de aclaración adicional, se puede usar la propiedad `threadID` para enlazar múltiples entradas en la matriz `enquiries`.
+
+## Guía de uso
+
+Las implementaciones pueden variar en la cantidad de información de consultas que proporcionan y cuándo se proporciona.
+
+Algunos editores pueden omitir la identidad del autor de la pregunta para proteger la confidencialidad de los solicitantes, o pueden anonimizar esta información (por ejemplo, simplemente poniendo el nombre del autor como "Organización 1" u "Organización 2" para que sea posible ver preguntas de la misma organización , Pero no conocer la identidad de esa organización.)
+
+Las propiedades `relatedItem` y `relatedLot` están disponibles para su uso cuando se pueden hacer preguntas en relación con un lote o artículo específico.
+
+Cuando sea posible, el enfoque recomendado es:
+
+- Haga una entrega con una etiqueta `tenderUpdate` para cada nueva pregunta o lote de preguntas recibidas, proporcionando una matriz de preguntas con cada una de las preguntas en;
+- Haga una entrega con una etiqueta de `tenderUpdate` cuando se proporcionen las respuestas a las preguntas, actualizando la matriz de consultas anteriores para que cada entrada contenga una pregunta y una respuesta;
+
+Este enfoque permitirá a las aplicaciones de terceros vigilar las entregas que proporcionen respuestas a las preguntas y apoyará en el monitoreo de adquisiciones en la revisión de la forma en que se responden las preguntas.
+
+Recomendamos que los publicadores proporcionen respuestas como texto sin formato o con un marcado HTML mínimo (párrafos y saltos de línea) y que las aplicaciones que consumen analicen el texto apropiadamente para darle formato para legibilidad (por ejemplo, reemplazar saltos de línea con saltos de párrafo en HTML).
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.5
+
+- Revisar las palabras normativas y no-normativas
+
+### v1.1.4
+
+- Quita las directrices Sphinx del readme
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- Usar `OrganizationReference` en lugar de` Organization` para `Enquiry.author`
+- Corrige el nombre de la lista de código + partyRole.csv (era + partyRoles.csv)
+- Permitir que `Enquiry.date` sea null
+- Enlista listas de códigos en extension.json
+- Usa la licencia Apache 2.0
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/enquiries/v1.1.5/codelists/+partyRole.csv b/es/extensions/enquiries/v1.1.5/codelists/+partyRole.csv
new file mode 100644
index 000000000..d5b0e0fbb
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.5/codelists/+partyRole.csv
@@ -0,0 +1,2 @@
+Código,Título,Descripción
+enquirer,Enquirer,A party who has made an enquiry during the enquiry phase of a contracting process
diff --git a/es/extensions/enquiries/v1.1.5/codelists/index.html b/es/extensions/enquiries/v1.1.5/codelists/index.html
new file mode 100644
index 000000000..27cacde4c
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.5/codelists/index.html
@@ -0,0 +1,238 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Consultas +
+ ++ La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ enquiries
+
+ |
+ + Consultas + | +
+ Preguntas enviadas a la entidad contratante y las respuestas dadas + + |
+ + array of Enquiry objects + | +
+ Enquiry +
+ +
+ The extension defines a new Enquiry object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador único para la consulta. + + |
+ + string + | +
+
+ date
+
+ |
+ + Fecha + | +
+ La fecha en que se recibió o procesó la consulta. + + |
+ + string + | +
+
+ author
+
+ |
+ + Autor de la pregunta + | +
+ El identificador y el nombre de la parte involucrada que hace esta pregunta. Los solicitantes pueden mostrarse en la lista de las partes con un rol de "enquirer". Las políticas de adquisición varían en cuanto a si la identidad de los que hacen preguntas debe ser divulgada, o en qué etapa se puede divulgar esta información. Cuando no se pueda identificar al solicitante de la información, deje la sección de autor en blanco. Los sistemas deberían de interpretar esta como una pregunta anónima. + + |
+ + OrganizationReference object + | +
+
+ title
+
+ |
+ + Título de la pregunta + | +
+ La línea de asunto de la pregunta. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ El cuerpo de la pregunta. + + |
+ + string + | +
+
+ answer
+
+ |
+ + Respuesta + | +
+ La respuesta a esta pregunta, cuando esté disponible. + + |
+ + string + | +
+
+ dateAnswered
+
+ |
+ + Fecha de respuesta + | +
+ La fecha en que se proporcionó la respuesta a la pregunta. + + |
+ + string + | +
+
+ relatedItem
+
+ |
+ + Artículo relacionado + | +
+ Si esta pregunta se refiere a una partida presupuestaria en específico, este campo contiene el identificador de la partida. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Lote relacionado + | +
+ Cuando se usan lotes, si esta pregunta se refiere a un lote específico, este campo contiene el identificador de lote. + + |
+ + string + | +
+
+ threadID
+
+ |
+ + Identificador de hilo + | +
+ Si esta pregunta y respuesta forma parte de un hilo de discusión (por ejemplo, la pregunta es un seguimiento a una respuesta anterior), se puede usar un identificador de hilo opcional para asociar varias consultas. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/enquiries/v1.1.5/extension.json b/es/extensions/enquiries/v1.1.5/extension.json
new file mode 100644
index 000000000..288c8b201
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.5/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Enquiries",
+ "es": "Consultas"
+ },
+ "description": {
+ "en": "The enquiries extension can be used to record questions raised during a contracting process, and the answers provided.",
+ "es": "La extensi\u00f3n sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contrataci\u00f3n y las respuestas proporcionadas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/enquiries/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "+partyRole.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/enquiries/v1.1.5/index.html b/es/extensions/enquiries/v1.1.5/index.html
new file mode 100644
index 000000000..2d0b2b834
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.5/index.html
@@ -0,0 +1,361 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Consultas +
+ ++ La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ enquirer
+
+ |
+ + Enquirer + | +
+ A party who has made an enquiry during the enquiry phase of a contracting process + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/enquiries/v1.1.5/release-schema.json b/es/extensions/enquiries/v1.1.5/release-schema.json
new file mode 100644
index 000000000..c9c6df07b
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.5/release-schema.json
@@ -0,0 +1,106 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "enquiries": {
+ "title": "Consultas",
+ "type": [
+ "array",
+ "null"
+ ],
+ "description": "Preguntas enviadas a la entidad contratante y las respuestas dadas",
+ "items": {
+ "$ref": "#/definitions/Enquiry"
+ },
+ "uniqueItems": true
+ }
+ }
+ },
+ "Enquiry": {
+ "type": "object",
+ "title": "Consulta",
+ "description": "Una pregunta relacionada con el proceso de contrataciones, hecha generalmente durante el per\u00edodo de preguntas.",
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador \u00fanico para la consulta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "date": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "title": "Fecha",
+ "description": "La fecha en que se recibi\u00f3 o proces\u00f3 la consulta.",
+ "format": "date-time"
+ },
+ "author": {
+ "title": "Autor de la pregunta",
+ "description": "La parte que realiza esta pregunta. La entrada correspondiente en la lista de `parties` deber\u00eda tener el valor 'enquirer' en su lista de `roles`. Las pol\u00edticas de adquisici\u00f3n var\u00edan sobre si se divulga la identidad de los que realizan preguntas, o en qu\u00e9 etapa se divulga esta informaci\u00f3n.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "title": {
+ "title": "T\u00edtulo de la pregunta",
+ "description": "La l\u00ednea de asunto de la pregunta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "El cuerpo de la pregunta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "answer": {
+ "title": "Respuesta",
+ "description": "La respuesta a esta pregunta, cuando est\u00e9 disponible.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "dateAnswered": {
+ "title": "Fecha de respuesta",
+ "description": "La fecha en que se proporcion\u00f3 la respuesta a la pregunta.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "relatedItem": {
+ "title": "Art\u00edculo relacionado",
+ "description": "Si esta pregunta se refiere a una partida presupuestaria en espec\u00edfico, este campo contiene el identificador de la partida.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedLot": {
+ "title": "Lote relacionado",
+ "description": "Cuando se usan lotes, si esta pregunta se refiere a un lote espec\u00edfico, este campo contiene el identificador de lote.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "threadID": {
+ "title": "Identificador de hilo",
+ "description": "Si esta pregunta y respuesta forma parte de un hilo de discusi\u00f3n (ej. la pregunta es la continuaci\u00f3n a una respuesta previa) un identificador de hilo puede ser usado para asociar m\u00faltiples preguntas.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/enquiries/v1.1.5/schema/index.html b/es/extensions/enquiries/v1.1.5/schema/index.html
new file mode 100644
index 000000000..a375ac43c
--- /dev/null
+++ b/es/extensions/enquiries/v1.1.5/schema/index.html
@@ -0,0 +1,449 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Consultas +
+ ++ La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas.
+Estructura
+La extensión agrega una lista de enquiries a la licitación, la cual consiste en uno o más objetos de consultas, cada uno con campos para una pregunta y una respuesta.
Ejemplo:
+{
+ "tender": {
+ "enquiries": [
+ {
+ "id": "Q1",
+ "date": "2017-01-22T14:55:00Z",
+ "author": {
+ "name": "Open Data Services Co-op",
+ "id": "GB-COH-09506232"
+ },
+ "title": "Variations of timeline accepted?",
+ "description": "The tender specifies delivery of Item 1 by end of March 2017. Will alternative proposals for the timeline be considered?",
+ "dateAnswered": "2017-02-05T09:00:00Z",
+ "answer": "There is a hard deadline of 15th April 2017. All proposals must be for delivery of Item 1 by this date.",
+ "relatedItem": "1",
+ "threadID": "1"
+ }
+ ]
+ }
+}
+Los documentos de soporte con aclaraciones o un documento completo que contenga respuestas a preguntas pueden incluirse en la matriz tender/documents con un documentType de 'clarifications'.
Si las respuestas a una pregunta sólo están disponibles en los documentos adjuntos, se puede ingresar un valor answer como "Consultar la sección N de (nombre del documento) en la sección de documentos" para permitir que los usuarios identifiquen que se ha dado respuesta a esta pregunta.
Cuando un sistema permite un formato de discusión, donde cada respuesta puede ser seguida por una pregunta de aclaración adicional, se puede usar la propiedad threadID para enlazar múltiples entradas en la matriz enquiries.
Guía de uso
+Las implementaciones pueden variar en la cantidad de información de consultas que proporcionan y cuándo se proporciona.
+Algunos editores pueden omitir la identidad del autor de la pregunta para proteger la confidencialidad de los solicitantes, o pueden anonimizar esta información (por ejemplo, simplemente poniendo el nombre del autor como "Organización 1" u "Organización 2" para que sea posible ver preguntas de la misma organización , Pero no conocer la identidad de esa organización.)
+Las propiedades relatedItem y relatedLot están disponibles para su uso cuando se pueden hacer preguntas en relación con un lote o artículo específico.
Cuando sea posible, el enfoque recomendado es:
+-
+
- Haga una entrega con una etiqueta
tenderUpdatepara cada nueva pregunta o lote de preguntas recibidas, proporcionando una matriz de preguntas con cada una de las preguntas en;
+ - Haga una entrega con una etiqueta de
tenderUpdatecuando se proporcionen las respuestas a las preguntas, actualizando la matriz de consultas anteriores para que cada entrada contenga una pregunta y una respuesta;
+
Este enfoque permitirá a las aplicaciones de terceros vigilar las entregas que proporcionen respuestas a las preguntas y apoyará en el monitoreo de adquisiciones en la revisión de la forma en que se responden las preguntas.
+Recomendamos que los publicadores proporcionen respuestas como texto sin formato o con un marcado HTML mínimo (párrafos y saltos de línea) y que las aplicaciones que consumen analicen el texto apropiadamente para darle formato para legibilidad (por ejemplo, reemplazar saltos de línea con saltos de párrafo en HTML).
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.5
+-
+
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- Quita las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- Usar
OrganizationReferenceen lugar deOrganizationparaEnquiry.author
+ - Corrige el nombre de la lista de código + partyRole.csv (era + partyRoles.csv) +
- Permitir que
Enquiry.datesea null
+ - Enlista listas de códigos en extension.json +
- Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/essentialAssets/index.html b/es/extensions/essentialAssets/index.html
new file mode 100644
index 000000000..a186d8e33
--- /dev/null
+++ b/es/extensions/essentialAssets/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Consultas +
+ ++ La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ enquiries
+
+ |
+ + Consultas + | +
+ Preguntas enviadas a la entidad contratante y las respuestas dadas + + |
+ + array of Enquiry objects + | +
+ Enquiry +
+ +
+ The extension defines a new Enquiry object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador único para la consulta. + + |
+ + string + | +
+
+ date
+
+ |
+ + Fecha + | +
+ La fecha en que se recibió o procesó la consulta. + + |
+ + string + | +
+
+ author
+
+ |
+ + Autor de la pregunta + | +
+ La parte que realiza esta pregunta. La entrada correspondiente en la lista de |
+ + OrganizationReference object + | +
+
+ title
+
+ |
+ + Título de la pregunta + | +
+ La línea de asunto de la pregunta. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ El cuerpo de la pregunta. + + |
+ + string + | +
+
+ answer
+
+ |
+ + Respuesta + | +
+ La respuesta a esta pregunta, cuando esté disponible. + + |
+ + string + | +
+
+ dateAnswered
+
+ |
+ + Fecha de respuesta + | +
+ La fecha en que se proporcionó la respuesta a la pregunta. + + |
+ + string + | +
+
+ relatedItem
+
+ |
+ + Artículo relacionado + | +
+ Si esta pregunta se refiere a una partida presupuestaria en específico, este campo contiene el identificador de la partida. + + |
+ + string + | +
+
+ relatedLot
+
+ |
+ + Lote relacionado + | +
+ Cuando se usan lotes, si esta pregunta se refiere a un lote específico, este campo contiene el identificador de lote. + + |
+ + string + | +
+
+ threadID
+
+ |
+ + Identificador de hilo + | +
+ Si esta pregunta y respuesta forma parte de un hilo de discusión (ej. la pregunta es la continuación a una respuesta previa) un identificador de hilo puede ser usado para asociar múltiples preguntas. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/essentialAssets/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/essentialAssets/master/release-schema.json b/es/extensions/essentialAssets/master/release-schema.json
new file mode 100644
index 000000000..89c79ff53
--- /dev/null
+++ b/es/extensions/essentialAssets/master/release-schema.json
@@ -0,0 +1,79 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "essentialAssets": {
+ "title": "Activos esenciales",
+ "description": "Informaci\u00f3n sobre los activos utilizados para la prestaci\u00f3n de servicios p\u00fablicos.",
+ "$ref": "#/definitions/EssentialAsset"
+ },
+ "hasEssentialAssets": {
+ "title": "Tiene activos esenciales",
+ "description": "Si existe informaci\u00f3n sobre los activos utilizados para la prestaci\u00f3n de servicios p\u00fablicos.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "essentialAssets": {
+ "title": "Activos esenciales",
+ "description": "Informaci\u00f3n sobre los activos utilizados para la prestaci\u00f3n de servicios p\u00fablicos.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/EssentialAsset"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "hasEssentialAssets": {
+ "title": "Tiene activos esenciales",
+ "description": "Si existe informaci\u00f3n sobre los activos utilizados para la prestaci\u00f3n de servicios p\u00fablicos.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "EssentialAsset": {
+ "title": "Essential asset",
+ "description": "Information about the asset used for the provision of public services.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Description of the essential asset.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "significance": {
+ "title": "Significado",
+ "description": "Estimated percentage share of the essential asset provided in relation to the overall asset needed for the provision of the public services.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "predominance": {
+ "title": "Predominancia",
+ "description": "Estimated percentage share of asset provided compared to asset used for activities other than the public services.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/essentialAssets/master/schema/index.html b/es/extensions/essentialAssets/master/schema/index.html
new file mode 100644
index 000000000..e8f8ba1ed
--- /dev/null
+++ b/es/extensions/essentialAssets/master/schema/index.html
@@ -0,0 +1,401 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Activos esenciales +
+ ++ Agregar un objeto al objeto de licitación para describir los activos utilizados para la prestación de servicios públicos. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an object to the tender and lot objects to describe the assets used for the provision of public services.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Contexto legal
+In the European Union, this extension's fields correspond to Article 4, clause 4 of Regulation 1370/2007 and eForms OPP-020-Contract (Assets related contract extension indicator), OPP-021-Contract (Used asset), OPP-022-Contract (Significance (%)), and OPP-023-Contract (Predominance (%)).For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplos
+Tender
+{
+ "tender": {
+ "hasEssentialAssets": true,
+ "essentialAssets": {
+ "description": "Significant investments have been made by the supplier in the past years and will continue to be so in the future, which will pay for themselves over a period of time well beyond the period of the contract. It includes the purchase of new vehicles, the maintenance of the modernization of the existing fleet and the renovation of the vehicle depots.",
+ "significance": "30",
+ "predominance": "40"
+ }
+ }
+}
+Lot
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "hasEssentialAssets": true,
+ "essentialAssets": [
+ {
+ "description": "Significant investments have been made by the supplier in the past years and will continue to be so in the future, which will pay for themselves over a period of time well beyond the period of the contract. It includes the purchase of new vehicles, the maintenance of the modernization of the existing fleet and the renovation of the vehicle depots.",
+ "significance": "30",
+ "predominance": "40"
+ }
+ ]
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-06-13
+-
+
- Change
Lot.essentialAssetsfrom an object to an array.
+
2023-04-05
+-
+
- Add
essentialAssetsandhasEssentialAssetsto theLotobject.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del OCDS para el perfil de la UE en issue #60 y en pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/eu/1.1/README.md b/es/extensions/eu/1.1/README.md
new file mode 100644
index 000000000..dbb3a193d
--- /dev/null
+++ b/es/extensions/eu/1.1/README.md
@@ -0,0 +1,226 @@
+# Unión Europea
+
+Implementa campos y código que son específicos de la legislación europea.
+
+For complete guidance on meeting the disclosure requirements of European law, see [OCDS for eForms](https://standard.open-contracting.org/profiles/eforms/latest/en/) for the 2019 regulation, or [OCDS for European Union](https://standard.open-contracting.org/profiles/eu/latest/en/) for the 2015 regulation.
+
+## Ejemplo
+
+```json
+{
+ "parties": [
+ {
+ "details": {
+ "url": "https://www.manchester.ac.uk/",
+ "buyerProfile": "https://in-tendhost.co.uk/universityofmanchester/aspx/Home"
+ },
+ "roles": [
+ "leadBuyer",
+ "awardingCentralPurchasingBody",
+ "evaluationBody",
+ "submissionReceiptBody"
+ ]
+ },
+ {
+ "name": "Royal Tax Office",
+ "id": "08797655",
+ "contactPoint": {
+ "name": "Crown Commercial Service",
+ "email": "info@crowncommercial.gov.uk",
+ "url": "https://www.gov.uk/government/publications/procurement-policy-note-0314-promoting-tax-compliance"
+ },
+ "roles": [
+ "informationService"
+ ]
+ },
+ {
+ "roles": [
+ "eSender"
+ ]
+ },
+ {
+ "roles": [
+ "procurementServiceProvider"
+ ]
+ },
+ {
+ "roles": [
+ "leadTenderer",
+ "tenderer"
+ ]
+ }
+ ],
+ "tender": {
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "reviewDetails": "NHS Wales Shared Services Partnership on behalf of Cardiff and Vale University Local Health Board will allow a minimum 10 calendar day standstill period between notifying the award decision and awarding the contract.",
+ "valueCalculationMethod": "Income from the sales of tickets over the duration of the contract minus the fees paid to the procuring entity.",
+ "items": [
+ {
+ "id": "item-1",
+ "description": "Printer ink cartridges",
+ "classification": {
+ "scheme": "CPV",
+ "id": "45233130.0",
+ "description": "Office supplies",
+ "uri": "http://cpv.data.ac.uk/code-45233130"
+ },
+ "deliveryAddresses": [
+ {
+ "streetAddress": "4, North London Business Park, Oakleigh Rd S",
+ "locality": "London",
+ "region": "London",
+ "postalCode": "N11 1NP",
+ "countryName": "United Kingdom"
+ }
+ ]
+ }
+ ],
+ "legislativeReferences": [
+ {
+ "title": "Direct taxation in the EU",
+ "url": "https://eur-lex.europa.eu/summary/chapter/2101.html",
+ "informationService": {
+ "name": "Royal Tax Office",
+ "id": "08797655"
+ }
+ }
+ ],
+ "lots": [
+ {
+ "id": "lot-1",
+ "awardPeriod": {
+ "durationInDays": 30,
+ "startDate": "2020-11-06T00:00:00Z",
+ "endDate": "2020-12-06T00:00:00Z"
+ },
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "additionalClassifications": [
+ {
+ "id": "oth-serv-contr",
+ "scheme": "eu-cvd-contract-type",
+ "description": "Other service contract"
+ }
+ ]
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2020-11-19T00:00:00Z"
+ }
+ ],
+ "documents": [
+ {
+ "id": "Fiscal1",
+ "documentType": "legislation"
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "award-1",
+ "valueCalculationMethod": "The awarded value takes into account the growing revenue expected from fees and the value of the equipment provided by the contracting authority.",
+ "items": [
+ {
+ "id": "1",
+ "additionalClassifications": [
+ {
+ "scheme": "eu-vehicle-category",
+ "id": "n2-n3",
+ "description": "Truck (N2-N3)"
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "contract-1",
+ "periodRationale": "The duration of the contract has been extended to anticipate the exceptional snowfall expected in January.",
+ "publicPassengerTransportServicesKilometers": 765,
+ "awardID": "award-1"
+ }
+ ],
+ "relatedProcesses": [
+ {
+ "id": "1",
+ "identifier": "123e4567-e89b-12d3-a456-426614174000",
+ "scheme": "eu-oj",
+ "relationship": [
+ "prior"
+ ]
+ }
+ ]
+}
+```
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### 2023-08-01
+
+- Add fields:
+ - `Organization.eDeliveryGateway`
+ - `Lot.hasAccessibilityCriteria`
+ - `Lot.noAccessibilityCriteriaRationale`
+ - `Lot.reviewDetails`
+
+### 2023-06-30
+
+- Add `Period.description` field.
+- Add codes:
+ - classificationScheme.csv:
+ - 'eu-vehicle-category'
+ - 'eu-cvd-contract-type'
+ - documentType.csv:
+ - 'legislation'
+ - partyRole.csv:
+ - 'procurementServiceProvider'
+ - 'eSender'
+ - 'leadBuyer'
+ - 'leadTenderer'
+ - 'evaluationBody'
+ - 'submissionReceiptBody'
+ - relatedProcessScheme.csv:
+ - 'eu-oj'
+- Move 'informationService' from the `+partyRole.csv` codelist to the Document publisher extension.
+
+### 2022-05-27
+
+- Move `Lot.minimumValue` to the Lots extension as `Lot.minValue`.
+
+### 2021-01-19
+
+- Establecer el tipo de objeto de `informationService` a` OrganizationReference`.
+- Agregar el código 'informationService' a la lista de códigos `+ partyRole.csv`.
+
+### 2020-10-06
+
+- Add `Lot.awardPeriod` field.
+
+### 2020-10-05
+
+- Add `Lot.minimumValue` field.
+
+### 2020-07-13
+
+- Agregue el código 'securityClearanceDeadline' a la lista de códigos `+ milestoneType.csv`.
+
+### 2020-04-29
+
+- Add `Item.deliveryAddresses` field.
+
+### 2020-04-24
+
+- Agregar las propiedades `minProperties`, `minItems` y/o `minLength`.
+
+Esta extensión se discutió originalmente como parte del \[OCDS para el perfil de la UE\] (https://github.com/open-contracting-extensions/european-union/issues), en [este issue](https://github.com/open-contracting/european-union-support/issues/19) y en [pull requests](https://github.com/open-contracting-extensions/ocds_eu_extension/pulls?q=is%3Apr+is%3Aclosed).
diff --git a/es/extensions/eu/1.1/codelists/+documentType.csv b/es/extensions/eu/1.1/codelists/+documentType.csv
new file mode 100644
index 000000000..9df75919a
--- /dev/null
+++ b/es/extensions/eu/1.1/codelists/+documentType.csv
@@ -0,0 +1,2 @@
+Section,Código,Título,Descripción
+tender,legislation,Legislation,"A general regulatory framework applicable in the place where the contract is to be performed. For example, tax legislation, environmental protection legislation or employment protection and working conditions legislation."
diff --git a/es/extensions/eu/1.1/codelists/+itemClassificationScheme.csv b/es/extensions/eu/1.1/codelists/+itemClassificationScheme.csv
new file mode 100644
index 000000000..1f8564173
--- /dev/null
+++ b/es/extensions/eu/1.1/codelists/+itemClassificationScheme.csv
@@ -0,0 +1,3 @@
+Código,Título,Descripción,Source
+eu-vehicle-category,European Union vehicle category,The category of vehicle falling within the scope of the EU Clean Vehicles Directive 2009/33/EC.,https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/vehicle-category
+eu-cvd-contract-type,European Union Clean Vehicle Directive contract type,The category of contract according to the EU Clean Vehicles Directive 2009/33/EC.,https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/cvd-contract-type
diff --git a/es/extensions/eu/1.1/codelists/+milestoneType.csv b/es/extensions/eu/1.1/codelists/+milestoneType.csv
new file mode 100644
index 000000000..8cac8e0b7
--- /dev/null
+++ b/es/extensions/eu/1.1/codelists/+milestoneType.csv
@@ -0,0 +1,2 @@
+Código,Título,Descripción
+securityClearanceDeadline,Security clearance deadline,The tenderers may obtain their security clearance until this date.
diff --git a/es/extensions/eu/1.1/codelists/+partyRole.csv b/es/extensions/eu/1.1/codelists/+partyRole.csv
new file mode 100644
index 000000000..7bc5f024a
--- /dev/null
+++ b/es/extensions/eu/1.1/codelists/+partyRole.csv
@@ -0,0 +1,12 @@
+Código,Título,Descripción
+mediationBody,Mediation body,The body responsible for mediation procedures.
+centralPurchasingBody,Central purchasing body,"The procuring entity providing centralized purchasing activities and, possibly, ancillary purchasing activities."
+processContactPoint,Process contact point,A contact point dedicated to this contracting process.
+reviewContactPoint,Review contact point,The service from which information about the review procedure can be obtained.
+selectedParticipant,Selected participant,An organization that has already been selected to participate in the design contest.
+procurementServiceProvider,Procurement service provider,An organization that provides ancillary procurement services to buyers.
+eSender,TED eSender,An organization that provides data transfer services to buyers.
+leadBuyer,Lead buyer,The lead buyer in a group of buyers.
+leadTenderer,Lead tenderer,The lead tenderer in the case of a consortium or equivalent.
+evaluationBody,Evaluation body,The organization responsible for evaluating bids or requests to participate.
+submissionReceiptBody,Submission receipt body,The organization responsible for receiving bids or requests to participate.
diff --git a/es/extensions/eu/1.1/codelists/+relatedProcessScheme.csv b/es/extensions/eu/1.1/codelists/+relatedProcessScheme.csv
new file mode 100644
index 000000000..e547de410
--- /dev/null
+++ b/es/extensions/eu/1.1/codelists/+relatedProcessScheme.csv
@@ -0,0 +1,2 @@
+Código,Título,Descripción
+eu-oj,Official Journal of the European Union,An Official Journal of the European Union contracting process identifier.
diff --git a/es/extensions/eu/1.1/codelists/index.html b/es/extensions/eu/1.1/codelists/index.html
new file mode 100644
index 000000000..8392f5d36
--- /dev/null
+++ b/es/extensions/eu/1.1/codelists/index.html
@@ -0,0 +1,603 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Activos esenciales +
+ ++ Agregar un objeto al objeto de licitación para describir los activos utilizados para la prestación de servicios públicos. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ essentialAssets
+
+ |
+ + Activos esenciales + | +
+ Información sobre los activos utilizados para la prestación de servicios públicos. + + |
+ + EssentialAsset object + | +
+
+ hasEssentialAssets
+
+ |
+ + Tiene activos esenciales + | +
+ Si existe información sobre los activos utilizados para la prestación de servicios públicos. + + |
+ + boolean + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ essentialAssets
+
+ |
+ + Activos esenciales + | +
+ Información sobre los activos utilizados para la prestación de servicios públicos. + + |
+ + array of EssentialAsset objects + | +
+
+ hasEssentialAssets
+
+ |
+ + Tiene activos esenciales + | +
+ Si existe información sobre los activos utilizados para la prestación de servicios públicos. + + |
+ + boolean + | +
+ EssentialAsset +
+ +
+ The extension defines a new EssentialAsset object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Descripción + | +
+ Description of the essential asset. + + |
+ + string + | +
+
+ significance
+
+ |
+ + Significado + | +
+ Estimated percentage share of the essential asset provided in relation to the overall asset needed for the provision of the public services. + + |
+ + string + | +
+
+ predominance
+
+ |
+ + Predominancia + | +
+ Estimated percentage share of asset provided compared to asset used for activities other than the public services. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/eu/1.1/extension.json b/es/extensions/eu/1.1/extension.json
new file mode 100644
index 000000000..3f8341ecd
--- /dev/null
+++ b/es/extensions/eu/1.1/extension.json
@@ -0,0 +1,34 @@
+{
+ "name": {
+ "en": "European Union",
+ "es": "Uni\u00f3n Europea"
+ },
+ "description": {
+ "en": "Implements fields and codes that are specific to European law.",
+ "es": "Implementa campos y c\u00f3digo que son espec\u00edficos de la legislaci\u00f3n europea."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/eu/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+documentType.csv",
+ "+itemClassificationScheme.csv",
+ "+milestoneType.csv",
+ "+partyRole.csv",
+ "+relatedProcessScheme.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json",
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_document_publisher_extension/master/extension.json"
+ ]
+}
diff --git a/es/extensions/eu/1.1/index.html b/es/extensions/eu/1.1/index.html
new file mode 100644
index 000000000..b94eb3271
--- /dev/null
+++ b/es/extensions/eu/1.1/index.html
@@ -0,0 +1,551 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Unión Europea +
+ ++ Implementa campos y código que son específicos de la legislación europea. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +documentType.csv +
+ +
+ You can download the +documentType.csv file in English.
+
+ The extension adds these codes to the documentType.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ legislation
+
+ |
+ + Legislation + | +
+ A general regulatory framework applicable in the place where the contract is to be performed. For example, tax legislation, environmental protection legislation or employment protection and working conditions legislation. + +
|
+
+ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ eu-vehicle-category
+
+ |
+ + European Union vehicle category + | +
+ The category of vehicle falling within the scope of the EU Clean Vehicles Directive 2009/33/EC. + + + |
+
+
+ eu-cvd-contract-type
+
+ |
+ + European Union Clean Vehicle Directive contract type + | +
+ The category of contract according to the EU Clean Vehicles Directive 2009/33/EC. + + + |
+
+ +milestoneType.csv +
+ +
+ You can download the +milestoneType.csv file in English.
+
+ The extension adds these codes to the milestoneType.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ securityClearanceDeadline
+
+ |
+ + Security clearance deadline + | +
+ The tenderers may obtain their security clearance until this date. + + |
+
+ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ mediationBody
+
+ |
+ + Mediation body + | +
+ The body responsible for mediation procedures. + + |
+
+
+ centralPurchasingBody
+
+ |
+ + Central purchasing body + | +
+ The procuring entity providing centralized purchasing activities and, possibly, ancillary purchasing activities. + + |
+
+
+ processContactPoint
+
+ |
+ + Process contact point + | +
+ A contact point dedicated to this contracting process. + + |
+
+
+ reviewContactPoint
+
+ |
+ + Review contact point + | +
+ The service from which information about the review procedure can be obtained. + + |
+
+
+ selectedParticipant
+
+ |
+ + Selected participant + | +
+ An organization that has already been selected to participate in the design contest. + + |
+
+
+ procurementServiceProvider
+
+ |
+ + Procurement service provider + | +
+ An organization that provides ancillary procurement services to buyers. + + |
+
+
+ eSender
+
+ |
+ + TED eSender + | +
+ An organization that provides data transfer services to buyers. + + |
+
+
+ leadBuyer
+
+ |
+ + Lead buyer + | +
+ The lead buyer in a group of buyers. + + |
+
+
+ leadTenderer
+
+ |
+ + Lead tenderer + | +
+ The lead tenderer in the case of a consortium or equivalent. + + |
+
+
+ evaluationBody
+
+ |
+ + Evaluation body + | +
+ The organization responsible for evaluating bids or requests to participate. + + |
+
+
+ submissionReceiptBody
+
+ |
+ + Submission receipt body + | +
+ The organization responsible for receiving bids or requests to participate. + + |
+
+ +relatedProcessScheme.csv +
+ +
+ You can download the +relatedProcessScheme.csv file in English.
+
+ The extension adds these codes to the relatedProcessScheme.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ eu-oj
+
+ |
+ + Official Journal of the European Union + | +
+ An Official Journal of the European Union contracting process identifier. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/eu/1.1/release-schema.json b/es/extensions/eu/1.1/release-schema.json
new file mode 100644
index 000000000..4f1ee35b4
--- /dev/null
+++ b/es/extensions/eu/1.1/release-schema.json
@@ -0,0 +1,201 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "reviewDetails": {
+ "title": "Detalles de la revisi\u00f3n",
+ "description": "Informaci\u00f3n precisa sobre los plazos para los procedimientos de revisi\u00f3n o informaci\u00f3n de contacto de la que se puede obtener.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "valueCalculationMethod": {
+ "title": "M\u00e9todo de c\u00e1lculo de valor",
+ "description": "El m\u00e9todo usado para el c\u00e1lculo del valor estimado de la concesi\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "legislativeReferences": {
+ "title": "Referencias legislativas",
+ "description": "Referencias legislativas y puntos de contacto asociados para informaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/LegislativeReference"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Organization": {
+ "properties": {
+ "details": {
+ "properties": {
+ "url": {
+ "title": "URL del sitio web",
+ "description": "Sitio web de la organizaci\u00f3n",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "buyerProfile": {
+ "title": "URL del perfil del comprador",
+ "description": "Direcci\u00f3n web del perfil del comprador.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "eDeliveryGateway": {
+ "title": "eDelivery gateway",
+ "description": "The organization's URL for the exchange of data and documents with eDelivery.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "valueCalculationMethod": {
+ "title": "M\u00e9todo de c\u00e1lculo de valor",
+ "description": "Cualquier detalle relevante al valor de la concesi\u00f3n seg\u00fan el art\u00edculo 8(3) de la Directiva 2014/23/UE sobre contratos de concesi\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "periodRationale": {
+ "title": "Justificaci\u00f3n del per\u00edodo del contrato",
+ "description": "La justificaci\u00f3n de la duraci\u00f3n del contrato.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "publicPassengerTransportServicesKilometers": {
+ "title": "Kil\u00f3metros de servicios de transporte p\u00fablico de pasajeros",
+ "description": "El n\u00famero de kil\u00f3metros de servicios de transporte p\u00fablico de pasajeros prestados por un contrato de servicio p\u00fablico.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "minimum": 0
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "deliveryAddresses": {
+ "title": "Direcci\u00f3n de entrega",
+ "description": "La(s) direcci\u00f3n(es) a la(s) cual(es) el proveedor entrega el \u00edtem.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Address"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Period": {
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "The description of the period.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "LegislativeReference": {
+ "title": "Referencia legislativa",
+ "description": "Referencias legislativas y puntos de contacto asociados",
+ "type": "object",
+ "properties": {
+ "title": {
+ "title": "T\u00edtulo",
+ "description": "El t\u00edtulo de una referencia legislativa",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "url": {
+ "title": "URL",
+ "description": "Un enlace a la p\u00e1gina web de la referencia legislativa.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "informationService": {
+ "title": "Servicio de informaci\u00f3n",
+ "description": "Una organizaci\u00f3n que puede proporcionar informaci\u00f3n sobre la referencia legislativa.",
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "minProperties": 1
+ },
+ "Lot": {
+ "properties": {
+ "awardPeriod": {
+ "title": "Periodo de adjudicaci\u00f3n",
+ "description": "El plazo para la toma de decisiones sobre la adjudicaci\u00f3n del contrato del lote. La fecha de finalizaci\u00f3n debe ser la fecha en la que se debe finalizar la decisi\u00f3n de adjudicaci\u00f3n. La fecha de inicio se puede utilizar para indicar el inicio de un per\u00edodo de evaluaci\u00f3n.",
+ "$ref": "#/definitions/Period"
+ },
+ "hasAccessibilityCriteria": {
+ "title": "Has accessibility criteria",
+ "description": "Whether the technical specifications for the lot include accessibility criteria for people with disabilities.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "noAccessibilityCriteriaRationale": {
+ "title": "No accessibility criteria rationale",
+ "description": "The rationale for not including accessibility criteria when the object of the lot is intended for use by natural persons.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "reviewDetails": {
+ "title": "Detalles de la revisi\u00f3n",
+ "description": "Precise information concerning the time limits for the review procedures for the lot or contact information from which it can be obtained.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/eu/1.1/schema/index.html b/es/extensions/eu/1.1/schema/index.html
new file mode 100644
index 000000000..50f921f77
--- /dev/null
+++ b/es/extensions/eu/1.1/schema/index.html
@@ -0,0 +1,782 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Unión Europea +
+ ++ Implementa campos y código que son específicos de la legislación europea. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Implementa campos y código que son específicos de la legislación europea.
+For complete guidance on meeting the disclosure requirements of European law, see OCDS for eForms for the 2019 regulation, or OCDS for European Union for the 2015 regulation.
+Ejemplo
+{
+ "parties": [
+ {
+ "details": {
+ "url": "https://www.manchester.ac.uk/",
+ "buyerProfile": "https://in-tendhost.co.uk/universityofmanchester/aspx/Home"
+ },
+ "roles": [
+ "leadBuyer",
+ "awardingCentralPurchasingBody",
+ "evaluationBody",
+ "submissionReceiptBody"
+ ]
+ },
+ {
+ "name": "Royal Tax Office",
+ "id": "08797655",
+ "contactPoint": {
+ "name": "Crown Commercial Service",
+ "email": "info@crowncommercial.gov.uk",
+ "url": "https://www.gov.uk/government/publications/procurement-policy-note-0314-promoting-tax-compliance"
+ },
+ "roles": [
+ "informationService"
+ ]
+ },
+ {
+ "roles": [
+ "eSender"
+ ]
+ },
+ {
+ "roles": [
+ "procurementServiceProvider"
+ ]
+ },
+ {
+ "roles": [
+ "leadTenderer",
+ "tenderer"
+ ]
+ }
+ ],
+ "tender": {
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "reviewDetails": "NHS Wales Shared Services Partnership on behalf of Cardiff and Vale University Local Health Board will allow a minimum 10 calendar day standstill period between notifying the award decision and awarding the contract.",
+ "valueCalculationMethod": "Income from the sales of tickets over the duration of the contract minus the fees paid to the procuring entity.",
+ "items": [
+ {
+ "id": "item-1",
+ "description": "Printer ink cartridges",
+ "classification": {
+ "scheme": "CPV",
+ "id": "45233130.0",
+ "description": "Office supplies",
+ "uri": "http://cpv.data.ac.uk/code-45233130"
+ },
+ "deliveryAddresses": [
+ {
+ "streetAddress": "4, North London Business Park, Oakleigh Rd S",
+ "locality": "London",
+ "region": "London",
+ "postalCode": "N11 1NP",
+ "countryName": "United Kingdom"
+ }
+ ]
+ }
+ ],
+ "legislativeReferences": [
+ {
+ "title": "Direct taxation in the EU",
+ "url": "https://eur-lex.europa.eu/summary/chapter/2101.html",
+ "informationService": {
+ "name": "Royal Tax Office",
+ "id": "08797655"
+ }
+ }
+ ],
+ "lots": [
+ {
+ "id": "lot-1",
+ "awardPeriod": {
+ "durationInDays": 30,
+ "startDate": "2020-11-06T00:00:00Z",
+ "endDate": "2020-12-06T00:00:00Z"
+ },
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "additionalClassifications": [
+ {
+ "id": "oth-serv-contr",
+ "scheme": "eu-cvd-contract-type",
+ "description": "Other service contract"
+ }
+ ]
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2020-11-19T00:00:00Z"
+ }
+ ],
+ "documents": [
+ {
+ "id": "Fiscal1",
+ "documentType": "legislation"
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "award-1",
+ "valueCalculationMethod": "The awarded value takes into account the growing revenue expected from fees and the value of the equipment provided by the contracting authority.",
+ "items": [
+ {
+ "id": "1",
+ "additionalClassifications": [
+ {
+ "scheme": "eu-vehicle-category",
+ "id": "n2-n3",
+ "description": "Truck (N2-N3)"
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "contract-1",
+ "periodRationale": "The duration of the contract has been extended to anticipate the exceptional snowfall expected in January.",
+ "publicPassengerTransportServicesKilometers": 765,
+ "awardID": "award-1"
+ }
+ ],
+ "relatedProcesses": [
+ {
+ "id": "1",
+ "identifier": "123e4567-e89b-12d3-a456-426614174000",
+ "scheme": "eu-oj",
+ "relationship": [
+ "prior"
+ ]
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-08-01
+-
+
- Add fields:
+
-
+
Organization.eDeliveryGateway
+Lot.hasAccessibilityCriteria
+Lot.noAccessibilityCriteriaRationale
+Lot.reviewDetails
+
+
2023-06-30
+-
+
- Add
Period.descriptionfield.
+ - Add codes:
+
-
+
- classificationScheme.csv:
+
-
+
- 'eu-vehicle-category' +
- 'eu-cvd-contract-type' +
+ - documentType.csv:
+
-
+
- 'legislation' +
+ - partyRole.csv:
+
-
+
- 'procurementServiceProvider' +
- 'eSender' +
- 'leadBuyer' +
- 'leadTenderer' +
- 'evaluationBody' +
- 'submissionReceiptBody' +
+ - relatedProcessScheme.csv:
+
-
+
- 'eu-oj' +
+
+ - classificationScheme.csv:
+
- Move 'informationService' from the
+partyRole.csvcodelist to the Document publisher extension.
+
2022-05-27
+-
+
- Move
Lot.minimumValueto the Lots extension asLot.minValue.
+
2021-01-19
+-
+
- Establecer el tipo de objeto de
informationServiceaOrganizationReference.
+ - Agregar el código 'informationService' a la lista de códigos
+ partyRole.csv.
+
2020-10-06
+-
+
- Add
Lot.awardPeriodfield.
+
2020-10-05
+-
+
- Add
Lot.minimumValuefield.
+
2020-07-13
+-
+
- Agregue el código 'securityClearanceDeadline' a la lista de códigos
+ milestoneType.csv.
+
2020-04-29
+-
+
- Add
Item.deliveryAddressesfield.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), en este issue y en pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/eu/index.html b/es/extensions/eu/index.html
new file mode 100644
index 000000000..d0e537e0a
--- /dev/null
+++ b/es/extensions/eu/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Unión Europea +
+ ++ Implementa campos y código que son específicos de la legislación europea. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ reviewDetails
+
+ |
+ + Detalles de la revisión + | +
+ Información precisa sobre los plazos para los procedimientos de revisión o información de contacto de la que se puede obtener. + + |
+ + string + | +
+
+ valueCalculationMethod
+
+ |
+ + Método de cálculo de valor + | +
+ El método usado para el cálculo del valor estimado de la concesión. + + |
+ + string + | +
+
+ legislativeReferences
+
+ |
+ + Referencias legislativas + | +
+ Referencias legislativas y puntos de contacto asociados para información. + + |
+ + array of LegislativeReference objects + | +
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + URL del sitio web + | +
+ Sitio web de la organización + + |
+ + string + | +
+
+ details.
+ |
+ + URL del perfil del comprador + | +
+ Dirección web del perfil del comprador. + + |
+ + string + | +
+
+ eDeliveryGateway
+
+ |
+ + eDelivery gateway + | +
+ The organization's URL for the exchange of data and documents with eDelivery. + + |
+ + string + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ valueCalculationMethod
+
+ |
+ + Método de cálculo de valor + | +
+ Cualquier detalle relevante al valor de la concesión según el artículo 8(3) de la Directiva 2014/23/UE sobre contratos de concesión. + + |
+ + string + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ periodRationale
+
+ |
+ + Justificación del período del contrato + | +
+ La justificación de la duración del contrato. + + |
+ + string + | +
+
+ publicPassengerTransportServicesKilometers
+
+ |
+ + Kilómetros de servicios de transporte público de pasajeros + | +
+ El número de kilómetros de servicios de transporte público de pasajeros prestados por un contrato de servicio público. + + |
+ + number + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryAddresses
+
+ |
+ + Dirección de entrega + | +
+ La(s) dirección(es) a la(s) cual(es) el proveedor entrega el ítem. + + |
+ + array of Address objects + | +
+ Period +
+ +
+ The extension defines these fields in the Period object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ The description of the period. + + |
+ + string + | +
+ LegislativeReference +
+ +
+ The extension defines a new LegislativeReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Título + | +
+ El título de una referencia legislativa + + |
+ + string + | +
+
+ url
+
+ |
+ + URL + | +
+ Un enlace a la página web de la referencia legislativa. + + |
+ + string + | +
+
+ informationService
+
+ |
+ + Servicio de información + | +
+ Una organización que puede proporcionar información sobre la referencia legislativa. + + |
+ + OrganizationReference object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ awardPeriod
+
+ |
+ + Periodo de adjudicación + | +
+ El plazo para la toma de decisiones sobre la adjudicación del contrato del lote. La fecha de finalización debe ser la fecha en la que se debe finalizar la decisión de adjudicación. La fecha de inicio se puede utilizar para indicar el inicio de un período de evaluación. + + |
+ + Period object + | +
+
+ hasAccessibilityCriteria
+
+ |
+ + Has accessibility criteria + | +
+ Whether the technical specifications for the lot include accessibility criteria for people with disabilities. + + |
+ + boolean + | +
+
+ noAccessibilityCriteriaRationale
+
+ |
+ + No accessibility criteria rationale + | +
+ The rationale for not including accessibility criteria when the object of the lot is intended for use by natural persons. + + |
+ + string + | +
+
+ reviewDetails
+
+ |
+ + Detalles de la revisión + | +
+ Precise information concerning the time limits for the review procedures for the lot or contact information from which it can be obtained. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/eu/1.1/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/eu/master/index.html b/es/extensions/eu/master/index.html
new file mode 100644
index 000000000..7724b73ca
--- /dev/null
+++ b/es/extensions/eu/master/index.html
@@ -0,0 +1,552 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Unión Europea +
+ ++ Implementa campos y código que son específicos de la legislación europea. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +documentType.csv +
+ +
+ You can download the +documentType.csv file in English.
+
+ The extension adds these codes to the documentType.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ legislation
+
+ |
+ + Legislation + | +
+ A general regulatory framework applicable in the place where the contract is to be performed. For example, tax legislation, environmental protection legislation or employment protection and working conditions legislation. + +
|
+
+ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ eu-vehicle-category
+
+ |
+ + European Union vehicle category + | +
+ The category of vehicle falling within the scope of the EU Clean Vehicles Directive 2009/33/EC. + + + |
+
+
+ eu-cvd-contract-type
+
+ |
+ + European Union Clean Vehicle Directive contract type + | +
+ The category of contract according to the EU Clean Vehicles Directive 2009/33/EC. + + + |
+
+ +milestoneType.csv +
+ +
+ You can download the +milestoneType.csv file in English.
+
+ The extension adds these codes to the milestoneType.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ securityClearanceDeadline
+
+ |
+ + Security clearance deadline + | +
+ The tenderers may obtain their security clearance until this date. + + |
+
+ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ mediationBody
+
+ |
+ + Mediation body + | +
+ The body responsible for mediation procedures. + + |
+
+
+ centralPurchasingBody
+
+ |
+ + Central purchasing body + | +
+ The procuring entity providing centralized purchasing activities and, possibly, ancillary purchasing activities. + + |
+
+
+ processContactPoint
+
+ |
+ + Process contact point + | +
+ A contact point dedicated to this contracting process. + + |
+
+
+ reviewContactPoint
+
+ |
+ + Review contact point + | +
+ The service from which information about the review procedure can be obtained. + + |
+
+
+ selectedParticipant
+
+ |
+ + Selected participant + | +
+ An organization that has already been selected to participate in the design contest. + + |
+
+
+ procurementServiceProvider
+
+ |
+ + Procurement service provider + | +
+ An organization that provides ancillary procurement services to buyers. + + |
+
+
+ eSender
+
+ |
+ + TED eSender + | +
+ An organization that provides data transfer services to buyers. + + |
+
+
+ leadBuyer
+
+ |
+ + Lead buyer + | +
+ The lead buyer in a group of buyers. + + |
+
+
+ leadTenderer
+
+ |
+ + Lead tenderer + | +
+ The lead tenderer in the case of a consortium or equivalent. + + |
+
+
+ evaluationBody
+
+ |
+ + Evaluation body + | +
+ The organization responsible for evaluating bids or requests to participate. + + |
+
+
+ submissionReceiptBody
+
+ |
+ + Submission receipt body + | +
+ The organization responsible for receiving bids or requests to participate. + + |
+
+ +relatedProcessScheme.csv +
+ +
+ You can download the +relatedProcessScheme.csv file in English.
+
+ The extension adds these codes to the relatedProcessScheme.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ eu-oj
+
+ |
+ + Official Journal of the European Union + | +
+ An Official Journal of the European Union contracting process identifier. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/eu/master/release-schema.json b/es/extensions/eu/master/release-schema.json
new file mode 100644
index 000000000..4f1ee35b4
--- /dev/null
+++ b/es/extensions/eu/master/release-schema.json
@@ -0,0 +1,201 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "reviewDetails": {
+ "title": "Detalles de la revisi\u00f3n",
+ "description": "Informaci\u00f3n precisa sobre los plazos para los procedimientos de revisi\u00f3n o informaci\u00f3n de contacto de la que se puede obtener.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "valueCalculationMethod": {
+ "title": "M\u00e9todo de c\u00e1lculo de valor",
+ "description": "El m\u00e9todo usado para el c\u00e1lculo del valor estimado de la concesi\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "legislativeReferences": {
+ "title": "Referencias legislativas",
+ "description": "Referencias legislativas y puntos de contacto asociados para informaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/LegislativeReference"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Organization": {
+ "properties": {
+ "details": {
+ "properties": {
+ "url": {
+ "title": "URL del sitio web",
+ "description": "Sitio web de la organizaci\u00f3n",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "buyerProfile": {
+ "title": "URL del perfil del comprador",
+ "description": "Direcci\u00f3n web del perfil del comprador.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "eDeliveryGateway": {
+ "title": "eDelivery gateway",
+ "description": "The organization's URL for the exchange of data and documents with eDelivery.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "valueCalculationMethod": {
+ "title": "M\u00e9todo de c\u00e1lculo de valor",
+ "description": "Cualquier detalle relevante al valor de la concesi\u00f3n seg\u00fan el art\u00edculo 8(3) de la Directiva 2014/23/UE sobre contratos de concesi\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "periodRationale": {
+ "title": "Justificaci\u00f3n del per\u00edodo del contrato",
+ "description": "La justificaci\u00f3n de la duraci\u00f3n del contrato.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "publicPassengerTransportServicesKilometers": {
+ "title": "Kil\u00f3metros de servicios de transporte p\u00fablico de pasajeros",
+ "description": "El n\u00famero de kil\u00f3metros de servicios de transporte p\u00fablico de pasajeros prestados por un contrato de servicio p\u00fablico.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "minimum": 0
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "deliveryAddresses": {
+ "title": "Direcci\u00f3n de entrega",
+ "description": "La(s) direcci\u00f3n(es) a la(s) cual(es) el proveedor entrega el \u00edtem.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Address"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Period": {
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "The description of the period.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "LegislativeReference": {
+ "title": "Referencia legislativa",
+ "description": "Referencias legislativas y puntos de contacto asociados",
+ "type": "object",
+ "properties": {
+ "title": {
+ "title": "T\u00edtulo",
+ "description": "El t\u00edtulo de una referencia legislativa",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "url": {
+ "title": "URL",
+ "description": "Un enlace a la p\u00e1gina web de la referencia legislativa.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "informationService": {
+ "title": "Servicio de informaci\u00f3n",
+ "description": "Una organizaci\u00f3n que puede proporcionar informaci\u00f3n sobre la referencia legislativa.",
+ "$ref": "#/definitions/OrganizationReference"
+ }
+ },
+ "minProperties": 1
+ },
+ "Lot": {
+ "properties": {
+ "awardPeriod": {
+ "title": "Periodo de adjudicaci\u00f3n",
+ "description": "El plazo para la toma de decisiones sobre la adjudicaci\u00f3n del contrato del lote. La fecha de finalizaci\u00f3n debe ser la fecha en la que se debe finalizar la decisi\u00f3n de adjudicaci\u00f3n. La fecha de inicio se puede utilizar para indicar el inicio de un per\u00edodo de evaluaci\u00f3n.",
+ "$ref": "#/definitions/Period"
+ },
+ "hasAccessibilityCriteria": {
+ "title": "Has accessibility criteria",
+ "description": "Whether the technical specifications for the lot include accessibility criteria for people with disabilities.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "noAccessibilityCriteriaRationale": {
+ "title": "No accessibility criteria rationale",
+ "description": "The rationale for not including accessibility criteria when the object of the lot is intended for use by natural persons.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "reviewDetails": {
+ "title": "Detalles de la revisi\u00f3n",
+ "description": "Precise information concerning the time limits for the review procedures for the lot or contact information from which it can be obtained.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/eu/master/schema/index.html b/es/extensions/eu/master/schema/index.html
new file mode 100644
index 000000000..f54bfb942
--- /dev/null
+++ b/es/extensions/eu/master/schema/index.html
@@ -0,0 +1,783 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Unión Europea +
+ ++ Implementa campos y código que son específicos de la legislación europea. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Implementa campos y código que son específicos de la legislación europea.
+For complete guidance on meeting the disclosure requirements of European law, see OCDS for eForms for the 2019 regulation, or OCDS for European Union for the 2015 regulation.
+Ejemplo
+{
+ "parties": [
+ {
+ "details": {
+ "url": "https://www.manchester.ac.uk/",
+ "buyerProfile": "https://in-tendhost.co.uk/universityofmanchester/aspx/Home"
+ },
+ "roles": [
+ "leadBuyer",
+ "awardingCentralPurchasingBody",
+ "evaluationBody",
+ "submissionReceiptBody"
+ ]
+ },
+ {
+ "name": "Royal Tax Office",
+ "id": "08797655",
+ "contactPoint": {
+ "name": "Crown Commercial Service",
+ "email": "info@crowncommercial.gov.uk",
+ "url": "https://www.gov.uk/government/publications/procurement-policy-note-0314-promoting-tax-compliance"
+ },
+ "roles": [
+ "informationService"
+ ]
+ },
+ {
+ "roles": [
+ "eSender"
+ ]
+ },
+ {
+ "roles": [
+ "procurementServiceProvider"
+ ]
+ },
+ {
+ "roles": [
+ "leadTenderer",
+ "tenderer"
+ ]
+ }
+ ],
+ "tender": {
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "reviewDetails": "NHS Wales Shared Services Partnership on behalf of Cardiff and Vale University Local Health Board will allow a minimum 10 calendar day standstill period between notifying the award decision and awarding the contract.",
+ "valueCalculationMethod": "Income from the sales of tickets over the duration of the contract minus the fees paid to the procuring entity.",
+ "items": [
+ {
+ "id": "item-1",
+ "description": "Printer ink cartridges",
+ "classification": {
+ "scheme": "CPV",
+ "id": "45233130.0",
+ "description": "Office supplies",
+ "uri": "http://cpv.data.ac.uk/code-45233130"
+ },
+ "deliveryAddresses": [
+ {
+ "streetAddress": "4, North London Business Park, Oakleigh Rd S",
+ "locality": "London",
+ "region": "London",
+ "postalCode": "N11 1NP",
+ "countryName": "United Kingdom"
+ }
+ ]
+ }
+ ],
+ "legislativeReferences": [
+ {
+ "title": "Direct taxation in the EU",
+ "url": "https://eur-lex.europa.eu/summary/chapter/2101.html",
+ "informationService": {
+ "name": "Royal Tax Office",
+ "id": "08797655"
+ }
+ }
+ ],
+ "lots": [
+ {
+ "id": "lot-1",
+ "awardPeriod": {
+ "durationInDays": 30,
+ "startDate": "2020-11-06T00:00:00Z",
+ "endDate": "2020-12-06T00:00:00Z"
+ },
+ "contractPeriod": {
+ "description": "unknown"
+ },
+ "additionalClassifications": [
+ {
+ "id": "oth-serv-contr",
+ "scheme": "eu-cvd-contract-type",
+ "description": "Other service contract"
+ }
+ ]
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2020-11-19T00:00:00Z"
+ }
+ ],
+ "documents": [
+ {
+ "id": "Fiscal1",
+ "documentType": "legislation"
+ }
+ ]
+ },
+ "awards": [
+ {
+ "id": "award-1",
+ "valueCalculationMethod": "The awarded value takes into account the growing revenue expected from fees and the value of the equipment provided by the contracting authority.",
+ "items": [
+ {
+ "id": "1",
+ "additionalClassifications": [
+ {
+ "scheme": "eu-vehicle-category",
+ "id": "n2-n3",
+ "description": "Truck (N2-N3)"
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "contract-1",
+ "periodRationale": "The duration of the contract has been extended to anticipate the exceptional snowfall expected in January.",
+ "publicPassengerTransportServicesKilometers": 765,
+ "awardID": "award-1"
+ }
+ ],
+ "relatedProcesses": [
+ {
+ "id": "1",
+ "identifier": "123e4567-e89b-12d3-a456-426614174000",
+ "scheme": "eu-oj",
+ "relationship": [
+ "prior"
+ ]
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-08-01
+-
+
- Add fields:
+
-
+
Organization.eDeliveryGateway
+Lot.hasAccessibilityCriteria
+Lot.noAccessibilityCriteriaRationale
+Lot.reviewDetails
+
+
2023-06-30
+-
+
- Add
Period.descriptionfield.
+ - Add codes:
+
-
+
- classificationScheme.csv:
+
-
+
- 'eu-vehicle-category' +
- 'eu-cvd-contract-type' +
+ - documentType.csv:
+
-
+
- 'legislation' +
+ - partyRole.csv:
+
-
+
- 'procurementServiceProvider' +
- 'eSender' +
- 'leadBuyer' +
- 'leadTenderer' +
- 'evaluationBody' +
- 'submissionReceiptBody' +
+ - relatedProcessScheme.csv:
+
-
+
- 'eu-oj' +
+
+ - classificationScheme.csv:
+
- Move 'informationService' from the
+partyRole.csvcodelist to the Document publisher extension.
+
2022-05-27
+-
+
- Move
Lot.minimumValueto the Lots extension asLot.minValue.
+
2021-01-19
+-
+
- Establecer el tipo de objeto de
informationServiceaOrganizationReference.
+ - Agregar el código 'informationService' a la lista de códigos
+ partyRole.csv.
+
2020-10-06
+-
+
- Add
Lot.awardPeriodfield.
+
2020-10-05
+-
+
- Add
Lot.minimumValuefield.
+
2020-07-13
+-
+
- Agregue el código 'securityClearanceDeadline' a la lista de códigos
+ milestoneType.csv.
+
2020-04-29
+-
+
- Add
Item.deliveryAddressesfield.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), en este issue y en pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/exclusionGrounds/index.html b/es/extensions/exclusionGrounds/index.html
new file mode 100644
index 000000000..68a2d76bb
--- /dev/null
+++ b/es/extensions/exclusionGrounds/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Unión Europea +
+ ++ Implementa campos y código que son específicos de la legislación europea. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ reviewDetails
+
+ |
+ + Detalles de la revisión + | +
+ Información precisa sobre los plazos para los procedimientos de revisión o información de contacto de la que se puede obtener. + + |
+ + string + | +
+
+ valueCalculationMethod
+
+ |
+ + Método de cálculo de valor + | +
+ El método usado para el cálculo del valor estimado de la concesión. + + |
+ + string + | +
+
+ legislativeReferences
+
+ |
+ + Referencias legislativas + | +
+ Referencias legislativas y puntos de contacto asociados para información. + + |
+ + array of LegislativeReference objects + | +
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + URL del sitio web + | +
+ Sitio web de la organización + + |
+ + string + | +
+
+ details.
+ |
+ + URL del perfil del comprador + | +
+ Dirección web del perfil del comprador. + + |
+ + string + | +
+
+ eDeliveryGateway
+
+ |
+ + eDelivery gateway + | +
+ The organization's URL for the exchange of data and documents with eDelivery. + + |
+ + string + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ valueCalculationMethod
+
+ |
+ + Método de cálculo de valor + | +
+ Cualquier detalle relevante al valor de la concesión según el artículo 8(3) de la Directiva 2014/23/UE sobre contratos de concesión. + + |
+ + string + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ periodRationale
+
+ |
+ + Justificación del período del contrato + | +
+ La justificación de la duración del contrato. + + |
+ + string + | +
+
+ publicPassengerTransportServicesKilometers
+
+ |
+ + Kilómetros de servicios de transporte público de pasajeros + | +
+ El número de kilómetros de servicios de transporte público de pasajeros prestados por un contrato de servicio público. + + |
+ + number + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryAddresses
+
+ |
+ + Dirección de entrega + | +
+ La(s) dirección(es) a la(s) cual(es) el proveedor entrega el ítem. + + |
+ + array of Address objects + | +
+ Period +
+ +
+ The extension defines these fields in the Period object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ The description of the period. + + |
+ + string + | +
+ LegislativeReference +
+ +
+ The extension defines a new LegislativeReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Título + | +
+ El título de una referencia legislativa + + |
+ + string + | +
+
+ url
+
+ |
+ + URL + | +
+ Un enlace a la página web de la referencia legislativa. + + |
+ + string + | +
+
+ informationService
+
+ |
+ + Servicio de información + | +
+ Una organización que puede proporcionar información sobre la referencia legislativa. + + |
+ + OrganizationReference object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ awardPeriod
+
+ |
+ + Periodo de adjudicación + | +
+ El plazo para la toma de decisiones sobre la adjudicación del contrato del lote. La fecha de finalización debe ser la fecha en la que se debe finalizar la decisión de adjudicación. La fecha de inicio se puede utilizar para indicar el inicio de un período de evaluación. + + |
+ + Period object + | +
+
+ hasAccessibilityCriteria
+
+ |
+ + Has accessibility criteria + | +
+ Whether the technical specifications for the lot include accessibility criteria for people with disabilities. + + |
+ + boolean + | +
+
+ noAccessibilityCriteriaRationale
+
+ |
+ + No accessibility criteria rationale + | +
+ The rationale for not including accessibility criteria when the object of the lot is intended for use by natural persons. + + |
+ + string + | +
+
+ reviewDetails
+
+ |
+ + Detalles de la revisión + | +
+ Precise information concerning the time limits for the review procedures for the lot or contact information from which it can be obtained. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/exclusionGrounds/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/exclusionGrounds/master/release-schema.json b/es/extensions/exclusionGrounds/master/release-schema.json
new file mode 100644
index 000000000..d0b0955b0
--- /dev/null
+++ b/es/extensions/exclusionGrounds/master/release-schema.json
@@ -0,0 +1,58 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "exclusionGrounds": {
+ "title": "Exclusion grounds",
+ "description": "Information about the criteria regarding the situation of a tenderer that can lead to its exclusion from the contracting process. For example: criminal convictions, bankruptcy, presence on a blacklist or failure to pay taxes.",
+ "$ref": "#/definitions/ExclusionGrounds"
+ }
+ }
+ },
+ "ExclusionGrounds": {
+ "title": "Exclusion grounds",
+ "description": "Information about the criteria regarding the situation of a tenderer that can lead to its exclusion from the contracting process. For example: criminal convictions, bankruptcy, presence on a blacklist or failure to pay taxes.",
+ "type": "object",
+ "properties": {
+ "criteria": {
+ "title": "Exclusion criteria",
+ "description": "The exclusion criteria.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/ExclusionCriterion"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "ExclusionCriterion": {
+ "title": "Exclusion criterion",
+ "description": "A criterion regarding the situation of a tenderer that can lead to its exclusion from the contracting process.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Type",
+ "description": "The type of the criterion.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Description",
+ "description": "The description of the criterion.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/exclusionGrounds/master/schema/index.html b/es/extensions/exclusionGrounds/master/schema/index.html
new file mode 100644
index 000000000..9b1d3cebe
--- /dev/null
+++ b/es/extensions/exclusionGrounds/master/schema/index.html
@@ -0,0 +1,350 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Exclusion grounds +
+ ++ Adds an object to describe the criteria to exclude tenderers from participating in a contracting process. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an object to describe the criteria to exclude tenderers from participating in a contracting process.
+Guidance
+If you use a codelist for tender.exclusionGrounds.criteria.type, you should explain where the codes are from in your publication policy/user guide.
Example
+{
+ "tender": {
+ "id": "1",
+ "exclusionGrounds": {
+ "criteria": [
+ {
+ "description": "Applicants not satisfying...",
+ "type": "crime-org"
+ }
+ ]
+ }
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/extendsContractID/index.html b/es/extensions/extendsContractID/index.html
new file mode 100644
index 000000000..a37288069
--- /dev/null
+++ b/es/extensions/extendsContractID/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Exclusion grounds +
+ ++ Adds an object to describe the criteria to exclude tenderers from participating in a contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ exclusionGrounds
+
+ |
+ + Exclusion grounds + | +
+ Information about the criteria regarding the situation of a tenderer that can lead to its exclusion from the contracting process. For example: criminal convictions, bankruptcy, presence on a blacklist or failure to pay taxes. + + |
+ + ExclusionGrounds object + | +
+ ExclusionGrounds +
+ +
+ The extension defines a new ExclusionGrounds object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ criteria
+
+ |
+ + Exclusion criteria + | +
+ The exclusion criteria. + + |
+ + array of ExclusionCriterion objects + | +
+ ExclusionCriterion +
+ +
+ The extension defines a new ExclusionCriterion object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Type + | +
+ The type of the criterion. + + |
+ + string + | +
+
+ description
+
+ |
+ + Description + | +
+ The description of the criterion. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/extendsContractID/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/extendsContractID/master/release-schema.json b/es/extensions/extendsContractID/master/release-schema.json
new file mode 100644
index 000000000..d47902365
--- /dev/null
+++ b/es/extensions/extendsContractID/master/release-schema.json
@@ -0,0 +1,17 @@
+{
+ "definitions": {
+ "Contract": {
+ "properties": {
+ "extendsContractID": {
+ "title": "ID extensi\u00f3n del contrato",
+ "description": "Si este contrato extiende o modifica un contrato emitido anteriormente, entonces el valor de contract.id para el contrato ampliado / modificado se puede proporcionar aqu\u00ed",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/extendsContractID/master/schema/index.html b/es/extensions/extendsContractID/master/schema/index.html
new file mode 100644
index 000000000..9e9a53109
--- /dev/null
+++ b/es/extensions/extendsContractID/master/schema/index.html
@@ -0,0 +1,231 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Extensión de contratos a través de contratos complementario: extendsContractiD +
+ ++ Bajo algunas reglas y procesos de contrataciones, para extender la duración o el valor de un contrato, o para realizar otras modificaciones sustanciales, se requiere la firma de un nuevo contrato. Esta extensión permite que se hagan explícitas las relaciones entre dos o más contratos en el mismo proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Bajo algunas reglas y procesos de compras públicas, para extender el valor o duración del contrato, o para hacer grandes cambios, se requiere firmar un nuevo contrato.
+Este nuevo contrato forma parte de el mismo proceso de contrataciones así como el contrato antiguo que esta extendiendo
+En estos casos, el campo extendsContractID puede utilizarse para identificar que una entrada determinada en la lista contracts debe entenderse como relacionada a un contrato anterior.
Utilice esta extensión sólo si hay un nuevo contrato sustantivo firmado como la extensión de un contrato anterior. En la mayoría de los casos, una actualización del valor o de la duración de un contrato debería modelarse como una enmienda dentro de una única entrada en la lista contracts.
Ejemplo
+El extracto más abajo muestra tres contratos en la matriz de contratos en un release OCDS.
+Los primeros dos contratos se firmaron en 2011: uno por cada año de renta de la propiedad, y otro por dos años de servicios relacionados con la propiedad rentada.
+El tercer contrato se firmó en 2012, y renueva el alquiler de la propiedad por un año más. Se relaciona de nuevo con el contrato del primer año de alquiler con el campo extendsContractID.
{
+ "contracts": [
+ {
+ "id": "207002-armin-hahner-stollmaier-21",
+ "awardID": "207002-armin-hahner-stollmaier-21",
+ "title": "Alquileres para la SNNA",
+ "status": "terminated",
+ "period": {
+ "startDate": "2011-01-02T23:59:59+00:00",
+ "endDate": "2012-01-02T23:59:59+00:00"
+ },
+ "value": {
+ "amount": 1800000,
+ "currency": "PYG"
+ },
+ "items": [
+ {
+ "id": "01",
+ "description": "Alquiler de Inmueble",
+ "classification": {
+ "scheme": "CPV",
+ "id": "70000000-1",
+ "description": "Real Estate Services",
+ "uri": "http://cpv.data.ac.uk/code-70000000"
+ }
+ }
+ ],
+ "dateSigned": "2011-03-14T16:58:40+00:00"
+ },
+ {
+ "id": "207004-armin-hahner-stollmaier-21-service",
+ "awardID": "207002-armin-hahner-stollmaier-21",
+ "title": "Servicios relacionados con alquileres para la SNNA",
+ "status": "active",
+ "period": {
+ "startDate": "2011-01-02T23:59:59+00:00",
+ "endDate": "2013-01-02T23:59:59+00:00"
+ },
+ "value": {
+ "amount": 10000,
+ "currency": "PYG"
+ },
+ "items": [
+ {
+ "id": "02",
+ "description": "Servicios relacionados con alquiler de Inmueble",
+ "classification": {
+ "scheme": "CPV",
+ "id": "70000000-1",
+ "description": "Real Estate Services",
+ "uri": "http://cpv.data.ac.uk/code-70000000"
+ }
+ }
+ ],
+ "dateSigned": "2011-03-14T16:58:40+00:00"
+ },
+ {
+ "id": "207002-armin-hahner-stollmaier-21-renovacion",
+ "awardID": "207002-armin-hahner-stollmaier-21",
+ "extendsContractID": "207002-armin-hahner-stollmaier",
+ "title": "Ad Referendum - Alquileres para la SNNA (Amends contract 207002)",
+ "status": "active",
+ "period": {
+ "startDate": "2012-01-02T23:59:59+00:00",
+ "endDate": "2013-01-02T23:59:59+00:00"
+ },
+ "value": {
+ "amount": 12780000,
+ "currency": "PYG"
+ },
+ "items": [
+ {
+ "id": "01",
+ "description": "Alquiler de Inmueble",
+ "classification": {
+ "scheme": "CPV",
+ "id": "70000000-1",
+ "description": "Real Estate Services",
+ "uri": "http://cpv.data.ac.uk/code-70000000"
+ }
+ }
+ ],
+ "dateSigned": "2012-03-14T16:58:40+00:00"
+ }
+ ]
+}
+La imagen siguiente muestra un ejemplo de cómo se utiliza la información proporcionada por el campo extendsContractID en Paraguay, para mostrar dos contratos resultantes de una adjudicación (las casillas azules), con uno de esos contratos prorrogado (el círculo azul).
Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-06-04
+-
+
- Revisar las palabras normativas y no normativas. +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2018-01-29
+-
+
- Hacer que
Contract.extendsContractIDpueda ser nulo.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/finance/index.html b/es/extensions/finance/index.html
new file mode 100644
index 000000000..764aff8d8
--- /dev/null
+++ b/es/extensions/finance/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Extensión de contratos a través de contratos complementario: extendsContractiD +
+ ++ Bajo algunas reglas y procesos de contrataciones, para extender la duración o el valor de un contrato, o para realizar otras modificaciones sustanciales, se requiere la firma de un nuevo contrato. Esta extensión permite que se hagan explícitas las relaciones entre dos o más contratos en el mismo proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ extendsContractID
+
+ |
+ + ID extensión del contrato + | +
+ Si este contrato extiende o modifica un contrato emitido anteriormente, entonces el valor de contract.id para el contrato ampliado / modificado se puede proporcionar aquí + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/finance/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/finance/master/extension.json b/es/extensions/finance/master/extension.json
new file mode 100644
index 000000000..fea48ed2e
--- /dev/null
+++ b/es/extensions/finance/master/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Finance",
+ "es": "Financiamiento"
+ },
+ "description": {
+ "en": "Adds fields to disclose the financing of the whole process and its individual contracts.",
+ "es": "Agrega campos para revelar la financiaci\u00f3n de todo el proceso y sus contratos individuales."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/finance/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "financeCategory.csv",
+ "financeType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/finance/master/index.html b/es/extensions/finance/master/index.html
new file mode 100644
index 000000000..0f4ee674d
--- /dev/null
+++ b/es/extensions/finance/master/index.html
@@ -0,0 +1,458 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Financiamiento +
+ ++ Agrega campos para revelar la financiación de todo el proceso y sus contratos individuales. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ financeCategory.csv +
+ +
+ You can download the financeCategory.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ equity
+
+ |
+ + Equity + | +
+ Equity finance is given in exchange for a share of ownership in the project (usually via direct or indirect shareholding in a Special Purpose Vehicle (SPV) company created to run the project). + + |
+
+
+ seniorDebt
+
+ |
+ + Senior debt + | +
+ Senior debt (sometimes called senior loans) take priority over other more junior debt. + + |
+
+
+ mezzanineDebt
+
+ |
+ + Mezzanine debt + | +
+ Mezzanine debt (sometimes called mezzanine loans) take priority over common shares. + + |
+
+
+ grant
+
+ |
+ + Grant + | +
+ A grant is finance provided without expectation of repayment. + + |
+
+
+ guarantee
+
+ |
+ + Guarantee + | +
+ A guarantee is a promise by one party to assume the debt of another if the other defaults. Guarantees are not to be counted in totals of the overall financing of a project. + + |
+
+
+ other
+
+ |
+ + Other debts or investments + | +
+ Any details of the conditions attached to this finance can be provided in the notes field. + + |
+
+ financeType.csv +
+ +
+ You can download the financeType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ institutional
+
+ |
+ + Institutional + | +
+ This finance was provided by institutional investors: organizations that pool money to purchase securities, real property, and other investment assets or originate loans. Institutional investors include banks, insurance companies, pensions, hedge funds, REITs, investment advisors, endowments, and mutual funds. + +
|
+
+
+ commercial
+
+ |
+ + Commercial + | +
+ This finance was provided by private parties who do not fall within the definition of institutional investor. + + |
+
+
+ bilateral
+
+ |
+ + Bilateral + | +
+ This finance was provided by a bilateral institution: an agency of one specific government, usually a development agency or export-credit agency with a mandate to support domestic businesses in pursuing investments abroad. + +
|
+
+
+ multilateral
+
+ |
+ + Multilateral + | +
+ This finance was provided by a multilateral institution: a body created by a group of countries to provides financing and professional support, primarily for the purpose of development. + + + |
+
+
+ publicBondIssue
+
+ |
+ + Public bond issue + | +
+ This finance was provided through a public bond issue. + + |
+
+
+ supplierCredit
+
+ |
+ + Supplier credit + | +
+ This finance was provided through a line of credit provided by a supplier. + + |
+
+
+ other
+
+ |
+ + Other + | +
+ This finance was provided through some other source. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/finance/master/release-schema.json b/es/extensions/finance/master/release-schema.json
new file mode 100644
index 000000000..77cc7861d
--- /dev/null
+++ b/es/extensions/finance/master/release-schema.json
@@ -0,0 +1,203 @@
+{
+ "definitions": {
+ "Contract": {
+ "properties": {
+ "finance": {
+ "title": "Financiamiento",
+ "description": "Una lista con los detalles de cada fuente de financiamiento acordada para este contrato.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Finance"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Budget": {
+ "properties": {
+ "finance": {
+ "title": "Financiamiento",
+ "description": "Una matriz con los detalles de cada fuente de financiaci\u00f3n prevista para este procedimiento.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Finance"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Finance": {
+ "title": "Financing arrangement",
+ "description": "Information about a financing arrangement.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "Un identificador para este acuerdo de financiamiento",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo",
+ "description": "T\u00edtulo breve de este acuerdo de financiamiento.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "A short description of this financing arrangement. This may include details of lender rights, step in arrangements, exchange rate guarantees, and for syndicated loans, details of syndication and any members of the syndicate.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "financingParty": {
+ "title": "Financing organization",
+ "description": "The organization providing this financing arrangement.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "financeType": {
+ "title": "Tipo de financiamiento",
+ "description": "El tipo de financiaci\u00f3n concertada.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "financeType.csv",
+ "openCodelist": false,
+ "enum": [
+ "institutional",
+ "commercial",
+ "bilateral",
+ "multilateral",
+ "publicBondIssue",
+ "supplierCredit",
+ "other",
+ null
+ ]
+ },
+ "financeCategory": {
+ "title": "Categor\u00eda de financiamiento",
+ "description": "The nature of the finance, relevant to determining the order of preference for investors to get their money back in case of liquidation.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "financeCategory.csv",
+ "openCodelist": false,
+ "enum": [
+ "equity",
+ "seniorDebt",
+ "mezzanineDebt",
+ "grant",
+ "guarantee",
+ "other",
+ null
+ ]
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor total de este financiamiento.",
+ "$ref": "#/definitions/Value"
+ },
+ "period": {
+ "title": "Periodo de financiamiento",
+ "description": "El per\u00edodo cubierto por este financiamiento.",
+ "$ref": "#/definitions/Period"
+ },
+ "interestRate": {
+ "title": "Tasa de inter\u00e9s",
+ "description": "La tasa de inter\u00e9s asociada con este financiamiento.",
+ "type": "object",
+ "properties": {
+ "base": {
+ "title": "Base",
+ "description": "La variable a la que se a\u00f1ade un importe de margen adicional para obtener el importe de los intereses. Puede especificarse como un n\u00famero fijo, como una variable conocida (por ejemplo, LIBOR o LIBOR+1%), o puede omitirse si el margen especifica todo el tipo de inter\u00e9s.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "margin": {
+ "title": "Margen",
+ "description": "La variable a\u00f1adida a la base para dar el monto de inter\u00e9s expresado como una fracci\u00f3n decimal (por ejemplo 12,5% = 0,125).",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "fixed": {
+ "title": "Tipo de inter\u00e9s fijo",
+ "description": "Un campo booleano. Si este tipo de inter\u00e9s es fijo, se establece en true. De lo contrario, se establece en false.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "notes": {
+ "title": "Notas",
+ "description": "Notas explicativas sobre el tipo de inter\u00e9s.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "repaymentFrequency": {
+ "title": "Frecuencia de pagos (d\u00edas)",
+ "description": "Define cu\u00e1l es la frecuencia media de reembolso (en d\u00edas) de esta fuente de financiamiento. Por ejemplo, para cada a\u00f1o, use 365; Para el uso del reembolso mensual 30.4; Para el uso diario 1. Las interfaces de usuario pueden traducir esto en una presentaci\u00f3n m\u00e1s f\u00e1cil de usar, como 'diario', 'mensual' o 'anual'.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "minimum": 0
+ },
+ "stepInRights": {
+ "title": "Derechos de intervenci\u00f3n",
+ "description": "Whether provision of this finance confers any step in rights to the financing organization.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "exchangeRateGuarantee": {
+ "title": "Garant\u00edas del tipo de cambio",
+ "description": "Whether there is an associated exchange rate guarantee with this source of finance.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "The identifiers of the lots to which this financing arrangement relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/finance/master/schema/index.html b/es/extensions/finance/master/schema/index.html
new file mode 100644
index 000000000..2fb2d411e
--- /dev/null
+++ b/es/extensions/finance/master/schema/index.html
@@ -0,0 +1,610 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Financiamiento +
+ ++ Agrega campos para revelar la financiación de todo el proceso y sus contratos individuales. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar campos para revelar la financiación de todo el proceso y sus contratos individuales.
+A veces, sobre todo en el caso de las asociaciones público-privadas, los contratos se financian con una serie de instrumentos, como préstamos, subvenciones, emisión de acciones, etc. Esta información puede actualizarse a lo largo de la vida del contrato.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BG-611 (Contract EU funds) and BG-61 (EU funds). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Listas de códigos
+La lista de códigos financeType.csv se basa en la lista de Página 57 del Marco de divulgación de APP del Banco Mundial
Ejemplos
+Financiamiento del proceso de contratación
+{
+ "planning": {
+ "budget": {
+ "description": "Adquisición de equipos odontológicos para las Unidades de Salud de la Familia",
+ "amount": {
+ "currency": "PYG",
+ "amount": 643702500
+ },
+ "finance": [
+ {
+ "id": "1",
+ "title": "Presupuesto de financiación de deuda primaria",
+ "financingParty": {
+ "id": "XX-FI-22222222",
+ "name": "Banco Interamericano de Desarrollo (BID)"
+ },
+ "financeCategory": "seniorDebt",
+ "financeType": "multilateral",
+ "value": {
+ "amount": 643702500,
+ "currency": "PYG"
+ }
+ }
+ ]
+ }
+ }
+}
+Financiamiento de contratos de Asociación público-privada
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "title": "Public Private Partnership Agreement",
+ "description": "Public-Private Partnership agreement entered into by and between telecoms promoter, together with national fibre infrastructure and the special purpose vehicle Mega Consortium Ltd",
+ "finance": [
+ {
+ "id": "1",
+ "title": "Primary senior debt financing agreement",
+ "description": "Big Bank Corp retains the right to step in should Mega Consortium fail to comply with the repayment schedule for a period of 3 consecutive months.",
+ "financingParty": {
+ "id": "XX-FI-22222222",
+ "name": "Big Bank Corp"
+ },
+ "financeCategory": "seniorDebt",
+ "value": {
+ "amount": 41000000,
+ "currency": "USD"
+ },
+ "period": {
+ "startDate": "2016-01-24T00:00:00Z",
+ "endDate": "2021-01-23T00:00:00Z"
+ },
+ "interestRate": {
+ "base": "LIBOR",
+ "margin": 0.03,
+ "fixed": false
+ },
+ "stepInRights": true,
+ "exchangeRateGuarantee": false,
+ "repaymentFrequency": 30.4
+ },
+ {
+ "id": "2",
+ "title": "Alpha Holdings equity investment",
+ "financingParty": {
+ "id": "XX-XXX-11111111",
+ "name": "Alpha Holdings Ltd"
+ },
+ "financeCategory": "equity",
+ "value": {
+ "amount": 6674000,
+ "currency": "USD"
+ }
+ }
+ ]
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2022-05-17
+-
+
- Move
Finance.relatedLotsfrom the Lots extension
+
2020-06-04
+-
+
- Revisar las palabras normativas y no normativas. +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2020-04-17
+-
+
- Agregar el campo
planning.budget.finance.
+ - Arreglar la descripción de
financeCategory.
+
2019-03-20
+-
+
- Establecer
"uniqueItems ": trueen los campos matriz y agregar"minLength": 1en los campos de cadena obligatorios.
+ - Hacer
interestRateno nulo (deshacer el cambio anterior).
+
2018-05-08
+-
+
- Hacer
Finance.idrequerido y no nulo para soportar el seguimiento de revisiones y list merging
+
2018-05-01
+-
+
- Agregar título y descripción a
Finance.financingParty.
+
2018-01-29
+-
+
- Se permite que
interestRatesea nulo.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/guarantees/index.html b/es/extensions/guarantees/index.html
new file mode 100644
index 000000000..eefbd12a5
--- /dev/null
+++ b/es/extensions/guarantees/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Financiamiento +
+ ++ Agrega campos para revelar la financiación de todo el proceso y sus contratos individuales. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ finance
+
+ |
+ + Financiamiento + | +
+ Una lista con los detalles de cada fuente de financiamiento acordada para este contrato. + + |
+ + array of Finance objects + | +
+ Budget +
+ +
+ The extension defines these fields in the Budget object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ finance
+
+ |
+ + Financiamiento + | +
+ Una matriz con los detalles de cada fuente de financiación prevista para este procedimiento. + + |
+ + array of Finance objects + | +
+ Finance +
+ +
+ The extension defines a new Finance object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ Un identificador para este acuerdo de financiamiento + + |
+ + string + | +
+
+ title
+
+ |
+ + Título + | +
+ Título breve de este acuerdo de financiamiento. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ A short description of this financing arrangement. This may include details of lender rights, step in arrangements, exchange rate guarantees, and for syndicated loans, details of syndication and any members of the syndicate. + + |
+ + string + | +
+
+ financingParty
+
+ |
+ + Financing organization + | +
+ The organization providing this financing arrangement. + + |
+ + OrganizationReference object + | +
+
+ financeType
+
+ |
+ + Tipo de financiamiento + | +
+ El tipo de financiación concertada. + + |
+ + string from closed financeType codelist + | +
+
+ financeCategory
+
+ |
+ + Categoría de financiamiento + | +
+ The nature of the finance, relevant to determining the order of preference for investors to get their money back in case of liquidation. + + |
+ + string from closed financeCategory codelist + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor total de este financiamiento. + + |
+ + Value object + | +
+
+ period
+
+ |
+ + Periodo de financiamiento + | +
+ El período cubierto por este financiamiento. + + |
+ + Period object + | +
+
+ interestRate
+
+ |
+ + Tasa de interés + | +
+ La tasa de interés asociada con este financiamiento. + + |
+ + object + | +
+
+ interestRate.
+ |
+ + Base + | +
+ La variable a la que se añade un importe de margen adicional para obtener el importe de los intereses. Puede especificarse como un número fijo, como una variable conocida (por ejemplo, LIBOR o LIBOR+1%), o puede omitirse si el margen especifica todo el tipo de interés. + + |
+ + string or number + | +
+
+ interestRate.
+ |
+ + Margen + | +
+ La variable añadida a la base para dar el monto de interés expresado como una fracción decimal (por ejemplo 12,5% = 0,125). + + |
+ + number + | +
+
+ interestRate.
+ |
+ + Tipo de interés fijo + | +
+ Un campo booleano. Si este tipo de interés es fijo, se establece en true. De lo contrario, se establece en false. + + |
+ + boolean + | +
+
+ interestRate.
+ |
+ + Notas + | +
+ Notas explicativas sobre el tipo de interés. + + |
+ + string + | +
+
+ repaymentFrequency
+
+ |
+ + Frecuencia de pagos (días) + | +
+ Define cuál es la frecuencia media de reembolso (en días) de esta fuente de financiamiento. Por ejemplo, para cada año, use 365; Para el uso del reembolso mensual 30.4; Para el uso diario 1. Las interfaces de usuario pueden traducir esto en una presentación más fácil de usar, como 'diario', 'mensual' o 'anual'. + + |
+ + number + | +
+
+ stepInRights
+
+ |
+ + Derechos de intervención + | +
+ Whether provision of this finance confers any step in rights to the financing organization. + + |
+ + boolean + | +
+
+ exchangeRateGuarantee
+
+ |
+ + Garantías del tipo de cambio + | +
+ Whether there is an associated exchange rate guarantee with this source of finance. + + |
+ + boolean + | +
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ The identifiers of the lots to which this financing arrangement relates. + + |
+ + array of strings + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/guarantees/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/guarantees/master/extension.json b/es/extensions/guarantees/master/extension.json
new file mode 100644
index 000000000..2ed237dc1
--- /dev/null
+++ b/es/extensions/guarantees/master/extension.json
@@ -0,0 +1,24 @@
+{
+ "name": {
+ "en": "Guarantees",
+ "es": "Garant\u00edas"
+ },
+ "description": {
+ "en": "Some procurement processes consider the specification of guarantees in order to ensure compliance with the terms of a contract.\n\nThere are many types of guarantees, so we consider the creation of a new extension based on the formats that are required for the Federal Treasury (Mexico). See discussion in https://github.com/open-contracting/standard/issues/651",
+ "es": "Algunos procesos de contrataci\u00f3n consideran la especificaci\u00f3n de garant\u00edas para asegurar el cumplimiento de los t\u00e9rminos de un contrato.\n\nExisten muchos tipos de garant\u00edas, por lo que consideramos a la creaci\u00f3n de una nueva extensi\u00f3n basada en los formatos que se requieren para la Tesorer\u00eda de la Federaci\u00f3n (M\u00e9xico). Ver discusi\u00f3n en https://github.com/open-contracting/standard/issues/651"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "documentationUrl": {
+ "en": "https://github.com/contratacionesabiertas/ocds_guarantees_extension"
+ },
+ "codelists": [
+ "guaranteeType.csv",
+ "guaranteedObligations.csv",
+ "+partyRole.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/es/extensions/guarantees/master/index.html b/es/extensions/guarantees/master/index.html
new file mode 100644
index 000000000..5e4fcc076
--- /dev/null
+++ b/es/extensions/guarantees/master/index.html
@@ -0,0 +1,460 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Garantías +
+ ++ Algunos procesos de contratación consideran la especificación de garantías para asegurar el cumplimiento de los términos de un contrato. + +Existen muchos tipos de garantías, por lo que consideramos a la creación de una nueva extensión basada en los formatos que se requieren para la Tesorería de la Federación (México). Ver discusión en https://github.com/open-contracting/standard/issues/651 +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ guarantor
+
+ |
+ + Guarantor + | +
+ Institution that issues the guarantee. + + |
+
+ guaranteeType.csv +
+ +
+ You can download the guaranteeType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ bail
+
+ |
+ + Bail + | +
+ A bail bond is a written promise by which a person agrees with the creditor to pay for the debtor, if he does not. + + |
+
+
+ depositSlip
+
+ |
+ + Deposit slip + | +
+ The deposit slip is an instrument used to establish cash guarantees available to judicial or administrative authorities. + + |
+
+
+ letterOfCredit
+
+ |
+ + Letter of credit + | +
+ Letters of credit are used to guarantee that a supplier will receive a specified amount of money within a specified time providing strict terms. + + |
+
+
+ suretyBond
+
+ |
+ + Surety bond + | +
+ A surety bond is an instrument through which The surety is obliged to compensate the obligee for the damages suffered in the event that the principal fails to comply with the terms of the contract. + + |
+
+
+ check
+
+ |
+ + Check + | +
+ A certified check as a form of guarantee. + + |
+
+ guaranteedObligations.csv +
+ +
+ You can download the guaranteedObligations.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ fulfillment
+
+ |
+ + Fulfillment + | +
+ Guarantees fulfillment in time with the conditions stipulated in the contract. + + |
+
+
+ prepaid
+
+ |
+ + Prepaid + | +
+ Guarantee by which the supplier requests a prepayment from the procuring entity. + + |
+
+
+ latentDefects
+
+ |
+ + Latent defects + | +
+ Guarantee on the possible defects that a good may have that are not discoverable through general inspection at the time of delivery. + + |
+
+
+ confidentiality
+
+ |
+ + Confidentiality + | +
+ Guarantee that commits the supplier to safeguard the confidential information that has been granted. + + |
+
+
+ quality
+
+ |
+ + Quality + | +
+ Commitment from the supplier to deliver the goods and services in the quality specified in the contract. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/guarantees/master/release-schema.json b/es/extensions/guarantees/master/release-schema.json
new file mode 100644
index 000000000..67f01d478
--- /dev/null
+++ b/es/extensions/guarantees/master/release-schema.json
@@ -0,0 +1,79 @@
+{
+ "definitions": {
+ "Guarantee": {
+ "title": "Garant\u00eda",
+ "description": "Informaci\u00f3n de la garant\u00eda utilizada para asegurar el cumplimiento de los t\u00e9rminos de un contrato.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID de garant\u00eda",
+ "description": "Un identificador local para esta garant\u00eda, \u00fanico dentro de este bloque. ",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "type": {
+ "title": "Tipo de garant\u00eda",
+ "description": "Especifique el tipo de garant\u00eda para este contrato usando la lista de c\u00f3digos [guaranteeType] (https://github.com/contratacionesabiertas/ocds_guarantees_extension/blob/master/codelists/guaranteeType.csv)",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "guaranteeType.csv",
+ "openCodelist": true
+ },
+ "date": {
+ "title": "Fecha de garant\u00eda",
+ "description": "La fecha de la garant\u00eda. Esta es la fecha en la que se emite la garant\u00eda.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "obligations": {
+ "title": "Obligaciones garantizadas",
+ "description": "Especifique el tipo de obligaciones que est\u00e1n garantizadas, utilizando la lista de c\u00f3digos [obligationType](https://github.com/contratacionesabiertas/ocds_guarantees_extension/blob/master/codelists/guaranteedObligations.csv).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "guaranteedObligations.csv",
+ "openCodelist": true
+ },
+ "value": {
+ "title": "Valor de la garant\u00eda",
+ "description": "Importe total de la garant\u00eda.",
+ "$ref": "#/definitions/Value"
+ },
+ "guarantor": {
+ "title": "Garante",
+ "description": "Instituci\u00f3n que emite la garant\u00eda.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "period": {
+ "title": "Per\u00edodo de garant\u00eda",
+ "description": "El per\u00edodo en el que esta cotizaci\u00f3n es v\u00e1lida.",
+ "$ref": "#/definitions/Period"
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "guarantees": {
+ "title": "Garant\u00edas",
+ "description": "Una lista de las garant\u00edas otorgadas para este contrato.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Guarantee"
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/guarantees/master/schema/index.html b/es/extensions/guarantees/master/schema/index.html
new file mode 100644
index 000000000..0afb299a3
--- /dev/null
+++ b/es/extensions/guarantees/master/schema/index.html
@@ -0,0 +1,391 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Garantías +
+ ++ Algunos procesos de contratación consideran la especificación de garantías para asegurar el cumplimiento de los términos de un contrato. + +Existen muchos tipos de garantías, por lo que consideramos a la creación de una nueva extensión basada en los formatos que se requieren para la Tesorería de la Federación (México). Ver discusión en https://github.com/open-contracting/standard/issues/651 +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Descripción:
+Algunos procesos de adquisiciones consideran la especificación de garantías para asegurar el cumplimiento de los términos de un contrato.
+Existen muchos tipos de garantías, por lo que consideramos la creación de una nueva extensión en base a los formatos que se requieren para la Tesorería de la Federación (México).
+Propuesta:
+Lista de códigos
+-
+
-
+
Tipos de garantías:
+-
+
- Fianza +
- Comprobante de depósito +
- Carta de crédito +
- Fianza de garantía +
- Cheque +
+ -
+
Obligaciones garantizadas:
+-
+
- Cumplimiento +
- Pagado por adelantado +
- Defectos ocultos +
- Confidencialidad +
- Calidad +
+
Agregar una matriz llamada "garantías" con los siguientes campos:
+Esquema
+-
+
- Contrato {objeto}
+
-
+
- garantías [matriz]
+
-
+
- Garantía {objeto}
+
-
+
- id (string, integer) +
- tipo (string, null) (lista de códigos) +
- fecha (Formato: fecha-hora) (string, null) +
- obligaciones (string, null) (lista de códigos) +
- valor {objeto}
+
-
+
- $ref : #/definitions/Value +
+ - garante {objeto}
+
-
+
- $ref : #/definitions/OrganizationReference +
+ - período {objeto}
+
-
+
- $ref : #/definiciones/Periodo +
+
+
+ - Garantía {objeto}
+
+ - garantías [matriz]
+
Textos definidos:
+| Code | +Title | +Description | +
|---|---|---|
| guarantees | +Guarantees | +A list of the guarantees given for this contract. | +
| Guarantee | +Guarantee | +Information of the guarantee used to ensure compliance with the terms of a contract. | +
| id | +Guarantee ID | +A local identifier for this guarantee, unique within this block. | +
| type | +Guarantee type | +Specify the guarantee type for this contract using the guaranteeType codelist. | +
| bail | +Bail | +A bail bond is a written promise by which a person agrees with the creditor to pay for the debtor, if he does not. | +
| depositSlip | +Deposit slip | +The deposit slip is an instrument used to establish cash guarantees available to judicial or administrative authorities. | +
| letterOfCredit | +Letter of credit | +Letters of credit are used to guarantee that a supplier will receive a specified amount of money within a specified time providing strict terms. | +
| suretyBond | +Surety bond | +A surety bond is an instrument through which The surety is obliged to compensate the obligee for the damages suffered in the event that the principal fails to comply with the terms of the contract. | +
| check | +Check | +A certified check as a form of guarantee. | +
| date | +Guarantee date | +The date of the guarantee. This is the date on which the guarantee is issued. | +
| obligations | +Guaranteed obligations | +Specify the type of obligations that are guaranteed, using the obligationType codelist. | +
| fulfillment | +Fulfillment | +Guarantees fulfillment in time with the conditions stipulated in the contract. | +
| prepaid | +Prepaid | +Guarantee by which the supplier requests a prepayment from the procuring entity. | +
| latentDefects | +Latent defects | +Guarantee on the possible defects that a good may have that are not discoverable through general inspection at the time of delivery. | +
| confidentiality | +Confidentiality | +Guarantee that commits the supplier to safeguard the confidential information that has been granted. | +
| quality | +Quality | +Commitment from the supplier to deliver the goods and services in the quality specified in the contract. | +
| value | +Guarantee value | +Total amount of the guarantee. | +
| guarantor | +Guarantor | +Institution that issues the guarantee. | +
| period | +Guarantee period | +The period on which this quote is valid. | +
Issues
+Informar problemas de esta extensión en el [repositorio estándar] (https://github.com/open-contracting/standard/issues/651) de Open Contracting Partnership.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/implementationStatus/index.html b/es/extensions/implementationStatus/index.html
new file mode 100644
index 000000000..78bff2ff2
--- /dev/null
+++ b/es/extensions/implementationStatus/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Garantías +
+ ++ Algunos procesos de contratación consideran la especificación de garantías para asegurar el cumplimiento de los términos de un contrato. + +Existen muchos tipos de garantías, por lo que consideramos a la creación de una nueva extensión basada en los formatos que se requieren para la Tesorería de la Federación (México). Ver discusión en https://github.com/open-contracting/standard/issues/651 +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Guarantee +
+ +
+ The extension defines a new Guarantee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID de garantía + | +
+ Un identificador local para esta garantía, único dentro de este bloque. + + |
+ + string or integer + | +
+
+ type
+
+ |
+ + Tipo de garantía + | +
+ Especifique el tipo de garantía para este contrato usando la lista de códigos [guaranteeType] (https://github.com/contratacionesabiertas/ocds_guarantees_extension/blob/master/codelists/guaranteeType.csv) + + |
+ + string from open guaranteeType codelist + | +
+
+ date
+
+ |
+ + Fecha de garantía + | +
+ La fecha de la garantía. Esta es la fecha en la que se emite la garantía. + + |
+ + string + | +
+
+ obligations
+
+ |
+ + Obligaciones garantizadas + | +
+ Especifique el tipo de obligaciones que están garantizadas, utilizando la lista de códigos obligationType. + + |
+ + string from open guaranteedObligations codelist + | +
+
+ value
+
+ |
+ + Valor de la garantía + | +
+ Importe total de la garantía. + + |
+ + Value object + | +
+
+ guarantor
+
+ |
+ + Garante + | +
+ Institución que emite la garantía. + + |
+ + OrganizationReference object + | +
+
+ period
+
+ |
+ + Período de garantía + | +
+ El período en el que esta cotización es válida. + + |
+ + Period object + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ guarantees
+
+ |
+ + Garantías + | +
+ Una lista de las garantías otorgadas para este contrato. + + |
+ + array of Guarantee objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/implementationStatus/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/implementationStatus/master/extension.json b/es/extensions/implementationStatus/master/extension.json
new file mode 100644
index 000000000..926224fa9
--- /dev/null
+++ b/es/extensions/implementationStatus/master/extension.json
@@ -0,0 +1,22 @@
+{
+ "name": {
+ "en": "Implementation status",
+ "es": "Estatus de la implementaci\u00f3n"
+ },
+ "description": {
+ "en": "In Mexico, when talking about works and services related with them it is necessary to publish a set of specific variables about its implementation. One of them is the implementation status of the work or service related with it. See discussion in https://github.com/open-contracting/standard/issues/624",
+ "es": "En M\u00e9xico, cuando se habla de obras y servicios relacionados a las obras, es necesario publicar un conjunto de variables espec\u00edficas sobre su implementaci\u00f3n. Uno de ellos es el estado de implementaci\u00f3n del trabajo o servicio relacionado con \u00e9l. Vea la discusi\u00f3n en https://github.com/open-contracting/standard/issues/624"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "documentationUrl": {
+ "en": "https://github.com/contratacionesabiertas/ocds_implementationStatus_extension"
+ },
+ "codelists": [
+ "implementationStatus.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/es/extensions/implementationStatus/master/index.html b/es/extensions/implementationStatus/master/index.html
new file mode 100644
index 000000000..182f018da
--- /dev/null
+++ b/es/extensions/implementationStatus/master/index.html
@@ -0,0 +1,333 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estatus de la implementación +
+ ++ En México, cuando se habla de obras y servicios relacionados a las obras, es necesario publicar un conjunto de variables específicas sobre su implementación. Uno de ellos es el estado de implementación del trabajo o servicio relacionado con él. Vea la discusión en https://github.com/open-contracting/standard/issues/624 +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ implementationStatus.csv +
+ +
+ You can download the implementationStatus.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ planning
+
+ |
+ + Planning + | +
+ The contract has been signed, but the provision or construction of the goods, services or works has not started. + + |
+
+
+ ongoing
+
+ |
+ + Ongoing + | +
+ The provision or construction of the goods, services or works is in progress. + + |
+
+
+ concluded
+
+ |
+ + Concluded + | +
+ The provision or construction of the goods, services or works has officially ended. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/implementationStatus/master/release-schema.json b/es/extensions/implementationStatus/master/release-schema.json
new file mode 100644
index 000000000..0ba66d57a
--- /dev/null
+++ b/es/extensions/implementationStatus/master/release-schema.json
@@ -0,0 +1,24 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "status": {
+ "title": "Estatus de la implementaci\u00f3n",
+ "description": "El estado actual de la implementaci\u00f3n del contrato en funci\u00f3n de [implementationStatuscodelist] (https://github.com/INAImexico/ocds_implementationStatus_extension/blob/master/codelists/implementationStatus).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "enum": [
+ "planning",
+ "ongoing",
+ "concluded",
+ null
+ ],
+ "codelist": "implementationStatus.csv",
+ "openCodelist": false
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/implementationStatus/master/schema/index.html b/es/extensions/implementationStatus/master/schema/index.html
new file mode 100644
index 000000000..9f75a7f62
--- /dev/null
+++ b/es/extensions/implementationStatus/master/schema/index.html
@@ -0,0 +1,236 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estatus de la implementación +
+ ++ En México, cuando se habla de obras y servicios relacionados a las obras, es necesario publicar un conjunto de variables específicas sobre su implementación. Uno de ellos es el estado de implementación del trabajo o servicio relacionado con él. Vea la discusión en https://github.com/open-contracting/standard/issues/624 +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Descripción:
+En México, cuando se habla de trabajos y servicios relacionados, es necesario publicar un set de variables específicas sobre su implementación. Una de las variables es el status de la implementación del trabajo o servicios, esto incluye una lista de código con los siguientes valores:
+-
+
- planeación +
- proyectos en marcha +
- proyectos concluidos +
Propuesta:
+Añadir un campo nuevo llamado "“implementationStatus” en el objeto “Implementation”.
+Esquema
+-
+
- Implementación {object}
+
-
+
- Estatus (string, null) (codelist) +
+
Textos definidos:
+| Code | +Title | +Description | +
|---|---|---|
| status | +Implementation status | +The current status of the contract implementation based on the implementationStatus codelist. | +
| planning | +Planning | +The contract has been signed, but the provision or construction of the goods, services or works has not started. | +
| ongoing | +Ongoing | +The provision or construction of the goods, services or works is in progress. | +
| concluded | +Concluded | +The provision or construction of the goods, services or works has officially ended. | +
Issues
+Reportar issues para esta extensión en standard repository de Open Contracting Partnership.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/index.html b/es/extensions/index.html
new file mode 100644
index 000000000..f7f91a2c5
--- /dev/null
+++ b/es/extensions/index.html
@@ -0,0 +1,1621 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Estatus de la implementación +
+ ++ En México, cuando se habla de obras y servicios relacionados a las obras, es necesario publicar un conjunto de variables específicas sobre su implementación. Uno de ellos es el estado de implementación del trabajo o servicio relacionado con él. Vea la discusión en https://github.com/open-contracting/standard/issues/624 +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ status
+
+ |
+ + Estatus de la implementación + | +
+ El estado actual de la implementación del contrato en función de [implementationStatuscodelist] (https://github.com/INAImexico/ocds_implementationStatus_extension/blob/master/codelists/implementationStatus). + + |
+ + string from closed implementationStatus codelist + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/itemAttributes/index.html b/es/extensions/itemAttributes/index.html
new file mode 100644
index 000000000..55f3b98cb
--- /dev/null
+++ b/es/extensions/itemAttributes/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Extensions +
+ + + ++ Showing 69 extensions from the extension registry +
+
+
+
+
+
+
+
+
+ + + Puntos de contacto adicionales + +
++ Para proveer múltiples puntos de contacto de una organización, o para indicar los idiomas disponibles de un punto de contacto. Por ejemplo, puede usarse para indicar un punto de contacto para cada idioma. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Amendment rationale classifications + +
++ Adds a field to the amendment object to classify the rationale for the amendment. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Desglose de los criterios de adjudicación + +
++ Agrega una matriz de criterios de adjudicación al objeto lote, para desglosar los criterios de adjudicación por precio, costo y calidad. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Beneficiarios finales + +
++ Agregue una lista de beneficialOwners al objeto organización para indicar los beneficiarios finales de una organización. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Apertura de ofertas + +
++ Agregar un objeto para describir la fecha, hora, lugar y otros detalles de la apertura de ofertas. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Estadísticas y detalles de las ofertas + + Recommended +
++ Permite que se muestren las estadísticas de ofertas y la información detallada de las ofertas. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Desglose del presupuesto + +
++ Agrega una lista de desglose de presupuesto al objeto de presupuesto para desglosar un presupuesto por fuente y período. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Clasificación de presupuesto y gasto + +
++ Extiende el desglose de presupuesto y la implementación de contrato para permitir la publicación del detalle de las asignaciones de presupuesto y la ejecución del proceso de contrataciones, utilizando las clasificaciones que pueden mapearse a datos de presupuesto y de gasto que fueron publicados de forma separada. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Cargos + +
++ Agrega una matriz de cargos al objeto de implementación para publicar los cargos en que incurrirán los usuarios o el gobierno en un período determinado de un contrato. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Comunicación + +
++ Agrega a la licitación un objeto comunicación para describir las modalidades de comunicación de los eventos claves. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Términos del contrato + +
++ Agrega un objeto términos del contrato a los objetos de la licitación y del lote, para describir los términos que rigen al futuro contrato. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Buyer per award or contract + +
++ Adds buyer fields to the award and contract objects to indicate the buyer(s) for an individual award or contract, if different from the buyer(s) involved in the contracting process as a whole. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Cumplimiento del contrato + +
++ Añade campos a la sección de implementación del contrato para detallar la fecha de finalización, y el valor final de un contrato. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Proveedores contratados + +
++ Permitir la declaración explícita de proveedores dentro del bloque de contratos. Se usa cuando una sola adjudicación a múltiples proveedores resulta en múltiples contratos para un subconjunto de los proveedores adjudicados. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Código de país + +
++ Agregar un campo código de país al objeto de dirección. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Cubierto por + +
++ Agregar un campo para indicar los tratados que cubre el proceso de contratación. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Concurso de proyecto + +
++ Agregar un objeto al objeto de la licitación para describir un concurso de proyecto. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Document publisher + +
++ Adds a publisher field to the document object. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Detalles de Documentos + +
++ Agrega campos al objeto document para referencias a páginas, acceso a detalles e información del autor. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Consultas + + Recommended +
++ La extensión sobre consultas puede usarse para registrar las preguntas planteadas durante un proceso de contratación y las respuestas proporcionadas. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Activos esenciales + +
++ Agregar un objeto al objeto de licitación para describir los activos utilizados para la prestación de servicios públicos. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Unión Europea + +
++ Implementa campos y código que son específicos de la legislación europea. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Exclusion grounds + +
++ Adds an object to describe the criteria to exclude tenderers from participating in a contracting process. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Extensión de contratos a través de contratos complementario: extendsContractiD + +
++ Bajo algunas reglas y procesos de contrataciones, para extender la duración o el valor de un contrato, o para realizar otras modificaciones sustanciales, se requiere la firma de un nuevo contrato. Esta extensión permite que se hagan explícitas las relaciones entre dos o más contratos en el mismo proceso de contratación. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Financiamiento + +
++ Agrega campos para revelar la financiación de todo el proceso y sus contratos individuales. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Garantías + +
++ Algunos procesos de contratación consideran la especificación de garantías para asegurar el cumplimiento de los términos de un contrato. + +Existen muchos tipos de garantías, por lo que consideramos a la creación de una nueva extensión basada en los formatos que se requieren para la Tesorería de la Federación (México). Ver discusión en https://github.com/open-contracting/standard/issues/651 +
++ + Maintained by Contrataciones Abiertas México + +
+
+
+
+
+
+
+
+
+ + + Estatus de la implementación + +
++ En México, cuando se habla de obras y servicios relacionados a las obras, es necesario publicar un conjunto de variables específicas sobre su implementación. Uno de ellos es el estado de implementación del trabajo o servicio relacionado con él. Vea la discusión en https://github.com/open-contracting/standard/issues/624 +
++ + Maintained by Contrataciones Abiertas México + +
+
+
+
+
+
+
+
+
+ + + Atributos del artículo + +
++ Agrega una lista genérica de atributos al objeto artículo +
++ + Maintained by dncp-opendata + +
+
+
+
+
+
+
+
+
+ + + Base legal + +
++ Agregar campos al objeto de licitación para describir la base legal del procedimiento. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Ubicación + + Recommended +
++ Permite indicar el punto de entrega o el sitio de las obras para una línea de pedido determinada en los objetos de licitación, adjudicación y contrato. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Lotes + + Recommended +
++ Un proceso de licitación se puede dividir en lotes, donde los licitadores pueden ofertar en uno o más lotes. Los detalles de cada lote se pueden proporcionar aquí. Los artículos, documentos y otras características pueden hacer referencia al lote que están relacionados con el uso de relatedLot. Cuando no se indique ningún identificador relacionado, los valores deben interpretarse como aplicables a toda la licitación. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Medicina + +
++ Agrega campos al objeto artículo relevantes para la adquisición de medicamentos. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Métrica + +
++ La extensión de métricas admite la publicación de pronósticos (etapa de planificación), objetivos (etapa de licitación), objetivos de desempeño acordados (etapa de adjudicación y contrato) y resultados (etapa de implementación). +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Documentos del hito + +
++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Opciones + +
++ Agregar campos para obtener información sobre las opciones. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Clasificación de la organización + +
++ Adds an array of classification objects to an organization's details in order to categorize it. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Otros requisitos + +
++ Agregar un objeto para describir otros requisitos para participar en un proceso de contratación. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Paginación + +
++ Agregar un objeto de enlaces a los paquetes para dar soporte a la paginación. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Cuotas/Cargos de participación + + Recommended +
++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Organization scale + +
++ Para clasificar organizaciones como micro, PyME or grande +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Fallos de desempleño + +
++ Agrega campos a la sección de implementación para permitir la divulgación de una serie de fallas de rendimiento de contratación. Basado en la tabla de informes de fallas de rendimiento definida en el Marco de Divulgación para el Banco Mundial en las APP. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Extensión OCDS para APPs + +
++ Realiza los cambios requeridos por el perfil de OCDS para APPs. Los indicadores de evaluación, resumen financiero y detalles del proyecto podrían ser movidos a otra extensión. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Procedimiento + +
++ Esta extensión agrega un bloque para describir el procedimiento de contratación. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Título y descripción del nivel del proceso + + Recommended +
++ Para proporcionar títulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contratación como un todo. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Clasificaciones de los fundamentos de métodos de contratación + +
++ Agregar una lista al objeto de licitación para clasificar la justificación del método de contratación. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Proyecto + +
++ Agrega un objeto de proyecto al objeto de planificación para describir el proyecto con el que está relacionado el proceso de contratación, incluido el valor total del proyecto (no debe confundirse con el valor total del proceso de contratación). +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Recurrencia + +
++ Agregar campos de información acerca de la recurrencia del proceso de contratación. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Publicador del Release + +
++ Incluye información sobre el publicador a nivel release para los casos en los que un paquete de releases o un paquete de records contienen releases de diferentes publicadores +
++ + Maintained by CompraNet + +
+
+
+
+
+
+
+
+
+ + + Fuentes + +
++ Añade una lista de fuentes para indicar los sistemas de información de los cuales se originan los datos +
++ + Maintained by ONCAETI + +
+
+
+
+
+
+
+
+
+ + + Renovación + +
++ Agrega campos a los objetos de la licitación y del lote, para describir las opciones de los términos de renovación de los contratos. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Requisitos + +
++ Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV). +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Asignación de Riesgo + +
++ Para proporcionar las asignaciones de riesgo definidas en un contrato de asociación público-privada. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Descripción de la segunda etapa + +
++ Agregar un objeto de segunda etapa a los objetos de licitación y lote, para describir la segunda etapa de un procedimiento de dos etapas. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Criterios de Selección + +
++ Agrega un objeto para describir las condiciones de participación en un proceso de contratación. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Accionistas + +
++ Agrega campos de propiedad de la empresa al objeto de organización utilizado en la lista de partes. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Firmantes + +
++ Adds a signatories array to the contract object, for when the signatories differ from the buyer for the contracting process and the suppliers for the award. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Statistics + +
++ Adds a top-level statistics array to describe statistics about the contracting process. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Detalles de estado + +
++ Agregar un campo statusDetails al objeto Tender, Award y Contract. +
++ + Maintained by dncp-opendata + +
+
+
+
+
+
+
+
+
+ + + Subcontratación + +
++ Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Términos de Presentación de la Oferta + +
++ Agrega un objeto términos de presentación de la oferta a los objetos de la licitación y del lote, para describir cómo, cuándo y dónde los oferentes deberán presentar sus ofertas. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Suitability + +
++ Adds a suitability object to the tender, lot and lot group objects to describe their suitability to different types of tenderers. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Sustainability + +
++ Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Tarifas + +
++ Agrega campos al contrato y objetos de implementación para capturar los detalles de las tarifas, los peajes y las tarifas de los usuarios establecidos en el contrato y en uso durante la vida del proyecto. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Técnicas + +
++ Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Clasificación de la licitación + +
++ Agregar una serie de objetos de clasificación al objeto de licitación para categorizar el procedimiento o la solicitud de orden de compra como un todo. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Fecha de publicación de la licitación + +
++ Agregar un campo de fecha para indicar cuándo se publicó la licitación. +
++ + Maintained by Portal EDCA HN + +
+
+
+
+
+
+
+
+
+ + + Hitos relacionados con transacción + +
++ Agregar un campo a relatedImplementationMilestone a los objetos de transacción, para que los pagos de un contrato puedan vincularse a un hito de implementación. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Cambios no estructurados + +
++ Agrega una matriz unstructuredChanges al objeto Amendment. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+
+
+ + + Withheld information + +
++ Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld. +
++ + Maintained by Open Contracting Data Standard Extensions + +
+
+
+
+
+
+
+ + + This page has moved to a /es/extensions/itemAttributes/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/itemAttributes/master/release-schema.json b/es/extensions/itemAttributes/master/release-schema.json
new file mode 100644
index 000000000..7e53b5d47
--- /dev/null
+++ b/es/extensions/itemAttributes/master/release-schema.json
@@ -0,0 +1,56 @@
+{
+ "definitions": {
+ "Attribute": {
+ "type": "object",
+ "title": "Attribute",
+ "description": "An attribute, including its name and value.",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "name": {
+ "title": "Nombre",
+ "description": "El nombre del atributo, como 'brand', 'manufacturer', y similares.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor del atributo.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "id": {
+ "title": "Id",
+ "description": "Un identificador local para el atributo.",
+ "type": [
+ "string"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Item": {
+ "properties": {
+ "attributes": {
+ "title": "Atributos",
+ "description": "Los atributos del art\u00edculo.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Attribute"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/itemAttributes/master/schema/index.html b/es/extensions/itemAttributes/master/schema/index.html
new file mode 100644
index 000000000..515584364
--- /dev/null
+++ b/es/extensions/itemAttributes/master/schema/index.html
@@ -0,0 +1,316 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Atributos del artículo +
+ ++ Agrega una lista genérica de atributos al objeto artículo +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds an attributes array to the item object to list any
+extra attribute that an item may have, at the tender, award or
+contract stage.
+The attributes can be features like the item's model, brand, manufacturer, among others, including its value and an
+unique identifier for that attribute
Ejemplo
+{
+ "tender": {
+ "items": [
+ {
+ "id": "10121503-001-1",
+ "description": "Balanceado para Ganado Vacuno - Alta Producción en bolsas de 25 k",
+ "quantity": 350,
+ "attributes": [
+ {
+ "name": "Presentacion",
+ "value": "BOLSA",
+ "id": "1"
+ }
+ ]
+ }
+ ]
+ }
+}
+Issues
+Informe los issues para esta extensión en el repositorio ocds-extensiones, poniendo el nombre de la extensión en el título del issue.
+Esta extensión se discutió originalmente en https://github.com/open-contracting/standard/issues/751
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/legalBasis/1.1/README.md b/es/extensions/legalBasis/1.1/README.md
new file mode 100644
index 000000000..138bb9ebf
--- /dev/null
+++ b/es/extensions/legalBasis/1.1/README.md
@@ -0,0 +1,51 @@
+# Base legal
+
+Agregar campos al objeto de licitación para describir la base legal del proceso de contratación – es decir, las leyes y reglamentos que rigen el proceso de contratación y que otorgan autoridad legal a la entidad contratante.
+
+El campo `tender.legalBasis` es un objeto de `Classification`. Ejemplos de esquemas de clasificación son [LEX](
+
+
+
+
+ + Atributos del artículo +
+ ++ Agrega una lista genérica de atributos al objeto artículo +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Attribute +
+ +
+ The extension defines a new Attribute object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ name
+
+ |
+ + Nombre + | +
+ El nombre del atributo, como 'brand', 'manufacturer', y similares. + + |
+ + string + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor del atributo. + + |
+ + string or number + | +
+
+ id
+
+ |
+ + Id + | +
+ Un identificador local para el atributo. + + |
+ + string + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ attributes
+
+ |
+ + Atributos + | +
+ Los atributos del artículo. + + |
+ + array of Attribute objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/legalBasis/1.1/extension.json b/es/extensions/legalBasis/1.1/extension.json
new file mode 100644
index 000000000..b5f21dcf1
--- /dev/null
+++ b/es/extensions/legalBasis/1.1/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Legal basis",
+ "es": "Base legal"
+ },
+ "description": {
+ "en": "Adds fields to the tender object to describe the legal basis of the procedure.",
+ "es": "Agregar campos al objeto de licitaci\u00f3n para describir la base legal del procedimiento."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/legalBasis/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+itemClassificationScheme.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/legalBasis/1.1/index.html b/es/extensions/legalBasis/1.1/index.html
new file mode 100644
index 000000000..22c8be3bd
--- /dev/null
+++ b/es/extensions/legalBasis/1.1/index.html
@@ -0,0 +1,332 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Base legal +
+ ++ Agregar campos al objeto de licitación para describir la base legal del procedimiento. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ CELEX
+
+ |
+ + CELEX number + | +
+ Identifier scheme for EUR-Lex documents + +
|
+
+
+ ELI
+
+ |
+ + European Legislation Identifier + | +
+ Identifier scheme for European legislation + +
|
+
+
+ LEXML
+
+ |
+ + LexML URN + | +
+ Identifier scheme for BR-Lex documents + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/legalBasis/1.1/release-schema.json b/es/extensions/legalBasis/1.1/release-schema.json
new file mode 100644
index 000000000..1477b6930
--- /dev/null
+++ b/es/extensions/legalBasis/1.1/release-schema.json
@@ -0,0 +1,22 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "crossBorderLaw": {
+ "title": "Ley transfronteriza",
+ "description": "En caso de una contrataci\u00f3n conjunta, la legislaci\u00f3n de contrataci\u00f3n p\u00fablica que se aplica a ese procedimiento.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "legalBasis": {
+ "title": "Base legal",
+ "description": "La base legal del procedimiento.",
+ "$ref": "#/definitions/Classification"
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/legalBasis/1.1/schema/index.html b/es/extensions/legalBasis/1.1/schema/index.html
new file mode 100644
index 000000000..7c10cf689
--- /dev/null
+++ b/es/extensions/legalBasis/1.1/schema/index.html
@@ -0,0 +1,253 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Base legal +
+ ++ Agregar campos al objeto de licitación para describir la base legal del procedimiento. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar campos al objeto de licitación para describir la base legal del proceso de contratación – es decir, las leyes y reglamentos que rigen el proceso de contratación y que otorgan autoridad legal a la entidad contratante.
+El campo tender.legalBasis es un objeto de Classification. Ejemplos de esquemas de clasificación son LEX, CELEX y [ELI] (https://es.wikipedia.org/wiki/Identificador_Europeo_de_Legislación)
Para identificar el procedimiento utilizado, ya sea por nombre formal o por citación legal, utilice el campo tender.procurementMethodDetails.
Para indicar si el proceso de contratación está cubierto por un tratado, como el Agreement on Government Procurement (GPA), usar la extensión coveredBy. Para indicar si el proceso de contratación es acelerado, involucra acuerdos marco o tiene otras modalidades, echar un vistazo a las extensiones.
+Guía
+Si la base legal es específica de un país, se recomienda anteponer el prefijo ISO 3166-1 alpha-2 code al esquema de clasificación: por ejemplo, "HN-ONCAE" para la Oficina Normativa de Contratación y Adquisiciones del Estado (ONCAE) en Honduras.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BT-01 (Procedure Legal Basis), BT-09 (Cross Border Law) and Article 39, paragraph 5 of Directive 2014/24/EU. For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+{
+ "tender": {
+ "crossBorderLaw": "Italian procurement legislation",
+ "legalBasis": {
+ "id": "32014L0025",
+ "scheme": "CELEX"
+ }
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-08-01
+-
+
- Add 'ELI' to
+itemClassificationScheme.csv.
+
2021-01-19
+-
+
- Agregar orientación sobre la elección del esquema de clasificación para la base legal específica del país. +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), y en pull resquests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/legalBasis/index.html b/es/extensions/legalBasis/index.html
new file mode 100644
index 000000000..c885564aa
--- /dev/null
+++ b/es/extensions/legalBasis/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Base legal +
+ ++ Agregar campos al objeto de licitación para describir la base legal del procedimiento. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ crossBorderLaw
+
+ |
+ + Ley transfronteriza + | +
+ En caso de una contratación conjunta, la legislación de contratación pública que se aplica a ese procedimiento. + + |
+ + string + | +
+
+ legalBasis
+
+ |
+ + Base legal + | +
+ La base legal del procedimiento. + + |
+ + Classification object + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/legalBasis/1.1/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/legalBasis/master/index.html b/es/extensions/legalBasis/master/index.html
new file mode 100644
index 000000000..22bc72028
--- /dev/null
+++ b/es/extensions/legalBasis/master/index.html
@@ -0,0 +1,333 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Base legal +
+ ++ Agregar campos al objeto de licitación para describir la base legal del procedimiento. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ CELEX
+
+ |
+ + CELEX number + | +
+ Identifier scheme for EUR-Lex documents + +
|
+
+
+ ELI
+
+ |
+ + European Legislation Identifier + | +
+ Identifier scheme for European legislation + +
|
+
+
+ LEXML
+
+ |
+ + LexML URN + | +
+ Identifier scheme for BR-Lex documents + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/legalBasis/master/release-schema.json b/es/extensions/legalBasis/master/release-schema.json
new file mode 100644
index 000000000..1477b6930
--- /dev/null
+++ b/es/extensions/legalBasis/master/release-schema.json
@@ -0,0 +1,22 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "crossBorderLaw": {
+ "title": "Ley transfronteriza",
+ "description": "En caso de una contrataci\u00f3n conjunta, la legislaci\u00f3n de contrataci\u00f3n p\u00fablica que se aplica a ese procedimiento.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "legalBasis": {
+ "title": "Base legal",
+ "description": "La base legal del procedimiento.",
+ "$ref": "#/definitions/Classification"
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/legalBasis/master/schema/index.html b/es/extensions/legalBasis/master/schema/index.html
new file mode 100644
index 000000000..a8a6c8572
--- /dev/null
+++ b/es/extensions/legalBasis/master/schema/index.html
@@ -0,0 +1,254 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Base legal +
+ ++ Agregar campos al objeto de licitación para describir la base legal del procedimiento. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar campos al objeto de licitación para describir la base legal del proceso de contratación – es decir, las leyes y reglamentos que rigen el proceso de contratación y que otorgan autoridad legal a la entidad contratante.
+El campo tender.legalBasis es un objeto de Classification. Ejemplos de esquemas de clasificación son LEX, CELEX y [ELI] (https://es.wikipedia.org/wiki/Identificador_Europeo_de_Legislación)
Para identificar el procedimiento utilizado, ya sea por nombre formal o por citación legal, utilice el campo tender.procurementMethodDetails.
Para indicar si el proceso de contratación está cubierto por un tratado, como el Agreement on Government Procurement (GPA), usar la extensión coveredBy. Para indicar si el proceso de contratación es acelerado, involucra acuerdos marco o tiene otras modalidades, echar un vistazo a las extensiones.
+Guía
+Si la base legal es específica de un país, se recomienda anteponer el prefijo ISO 3166-1 alpha-2 code al esquema de clasificación: por ejemplo, "HN-ONCAE" para la Oficina Normativa de Contratación y Adquisiciones del Estado (ONCAE) en Honduras.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BT-01 (Procedure Legal Basis), BT-09 (Cross Border Law) and Article 39, paragraph 5 of Directive 2014/24/EU. For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+{
+ "tender": {
+ "crossBorderLaw": "Italian procurement legislation",
+ "legalBasis": {
+ "id": "32014L0025",
+ "scheme": "CELEX"
+ }
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-08-01
+-
+
- Add 'ELI' to
+itemClassificationScheme.csv.
+
2021-01-19
+-
+
- Agregar orientación sobre la elección del esquema de clasificación para la base legal específica del país. +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), y en pull resquests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/location/index.html b/es/extensions/location/index.html
new file mode 100644
index 000000000..1a5ee7908
--- /dev/null
+++ b/es/extensions/location/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Base legal +
+ ++ Agregar campos al objeto de licitación para describir la base legal del procedimiento. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ crossBorderLaw
+
+ |
+ + Ley transfronteriza + | +
+ En caso de una contratación conjunta, la legislación de contratación pública que se aplica a ese procedimiento. + + |
+ + string + | +
+
+ legalBasis
+
+ |
+ + Base legal + | +
+ La base legal del procedimiento. + + |
+ + Classification object + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/location/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/location/master/codelists/locationGazetteers.csv b/es/extensions/location/master/codelists/locationGazetteers.csv
new file mode 100644
index 000000000..0a8de5795
--- /dev/null
+++ b/es/extensions/location/master/codelists/locationGazetteers.csv
@@ -0,0 +1,7 @@
+Categoría,Código,Título,Descripción,Fuente,Patrón de URI
+Sub-National,NUTS,EU Nomenclature of Territorial Units for Statistics,The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union.,https://ec.europa.eu/eurostat/web/nuts/linked-open-data,http://data.europa.eu/nuts/code/
+National,ISO2,ISO Country Codes (3166-1 alpha-2),ISO 2-Digit Country Codes,https://www.iso.org/iso-3166-country-codes.html,
+Universal,GEONAMES,GeoNames,"GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations.",https://www.geonames.org/,https://www.geonames.org/
+Universal,OSMN,OpenStreetMap Node,"OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes might have tags to indicate the particular geographic feature they represent.",,https://www.openstreetmap.org/node/
+Universal,OSMR,OpenStreetMap Relation,"Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap.",https://wiki.openstreetmap.org/wiki/Relation,https://www.openstreetmap.org/relation/
+Universal,OSMW,OpenStreetMap Way,An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. It can be used to describe fragments of roads or local boundaries and bounding boxes.,https://wiki.openstreetmap.org/wiki/Way,https://www.openstreetmap.org/way/
diff --git a/es/extensions/location/master/extension.json b/es/extensions/location/master/extension.json
new file mode 100644
index 000000000..7dc7660b4
--- /dev/null
+++ b/es/extensions/location/master/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Location",
+ "es": "Ubicaci\u00f3n"
+ },
+ "description": {
+ "en": "Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects.",
+ "es": "Permite indicar el punto de entrega o el sitio de las obras para una l\u00ednea de pedido determinada en los objetos de licitaci\u00f3n, adjudicaci\u00f3n y contrato."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/location/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "locationGazetteers.csv",
+ "geometryType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/location/master/index.html b/es/extensions/location/master/index.html
new file mode 100644
index 000000000..66742b8ef
--- /dev/null
+++ b/es/extensions/location/master/index.html
@@ -0,0 +1,446 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Ubicación +
+ ++ Permite indicar el punto de entrega o el sitio de las obras para una línea de pedido determinada en los objetos de licitación, adjudicación y contrato. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ geometryType.csv +
+ +
+ You can download the geometryType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ Point
+
+ |
+ + Point + | +
+ For type 'Point', the 'coordinates' member is a single position. + +
|
+
+
+ MultiPoint
+
+ |
+ + MultiPoint + | +
+ For type 'MultiPoint', the 'coordinates' member is an array of positions. + +
|
+
+
+ LineString
+
+ |
+ + LineString + | +
+ For type 'LineString', the 'coordinates' member is an array of two or more positions. + +
|
+
+
+ MultiLineString
+
+ |
+ + MultiLineString + | +
+ For type 'MultiLineString', the 'coordinates' member is an array of LineString coordinate arrays. + +
|
+
+
+ Polygon
+
+ |
+ + Polygon + | +
+ For type 'Polygon', the 'coordinates' member must be an array of linear ring coordinate arrays. + +
|
+
+
+ MultiPolygon
+
+ |
+ + MultiPolygon + | +
+ For type 'MultiPolygon', the 'coordinates' member is an array of Polygon coordinate arrays. + +
|
+
+ locationGazetteers.csv +
+ +
+ You can download the locationGazetteers.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ NUTS
+
+ |
+ + EU Nomenclature of Territorial Units for Statistics + | +
+ The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union. + +
|
+
+
+ ISO2
+
+ |
+ + ISO Country Codes (3166-1 alpha-2) + | +
+ ISO 2-Digit Country Codes + +
|
+
+
+ GEONAMES
+
+ |
+ + GeoNames + | +
+ GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations. + +
|
+
+
+ OSMN
+
+ |
+ + OpenStreetMap Node + | +
+ OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes might have tags to indicate the particular geographic feature they represent. + +
|
+
+
+ OSMR
+
+ |
+ + OpenStreetMap Relation + | +
+ Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap. + +
|
+
+
+ OSMW
+
+ |
+ + OpenStreetMap Way + | +
+ An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. It can be used to describe fragments of roads or local boundaries and bounding boxes. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/location/master/release-schema.json b/es/extensions/location/master/release-schema.json
new file mode 100644
index 000000000..cdb8d4274
--- /dev/null
+++ b/es/extensions/location/master/release-schema.json
@@ -0,0 +1,176 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "deliveryLocations": {
+ "title": "Delivery Locations",
+ "description": "The locations where activity related to this tender will take place.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Location"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true
+ },
+ "deliveryAddresses": {
+ "title": "Delivery Addresses",
+ "description": "The addresses to which, or where, goods or services related to this tender will be delivered.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Address"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "deliveryLocations": {
+ "title": "Delivery Locations",
+ "description": "The locations where activity related to this tender, contract or license will be delivered.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Location"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "deliveryLocation": {
+ "title": "Ubicaci\u00f3n de Entrega",
+ "description": "La ubicaci\u00f3n donde la actividad relacionada con esta licitaci\u00f3n, contrato o licencia ser\u00e1 entregada o se llevar\u00e1 a cabo. ",
+ "$ref": "#/definitions/Location",
+ "deprecated": {
+ "description": "This field is deprecated in favour of `.deliveryLocations` to support items with multiple delivery locations.",
+ "deprecatedVersion": "1.2.0"
+ }
+ },
+ "deliveryAddresses": {
+ "title": "Delivery Addresses",
+ "description": "The addresses to which, or where, goods or services related to this tender, contract or license will be delivered.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Address"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "deliveryAddress": {
+ "title": "Direcci\u00f3n de Entrega",
+ "description": "La direcci\u00f3n en la que bienes y servicios relacionados con esta licitaci\u00f3n, contrato o licencia ser\u00e1n entregados.",
+ "$ref": "#/definitions/Address",
+ "deprecated": {
+ "description": "This field is deprecated in favour of `.deliveryAddresses` to support items with multiple delivery locations.",
+ "deprecatedVersion": "1.2.0"
+ }
+ }
+ }
+ },
+ "Location": {
+ "title": "Ubicaci\u00f3n",
+ "description": "A physical or virtual location.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Un nombre o descripci\u00f3n para esta ubicaci\u00f3n. Esto puede incluir el(los) nombre(s) de la ubicaci\u00f3n (o ubicaciones), o puede incluir una descripci\u00f3n legible de la ubicaci\u00f3n a ser cubierta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "geometry": {
+ "title": "Geometr\u00eda",
+ "description": "We follow the [GeoJSON standard](https://www.rfc-editor.org/rfc/rfc7946) to express basic location information, using longitude, latitude, and optional elevation values in the [WGS84](https://en.wikipedia.org/wiki/World_Geodetic_System) (EPSG:4326) projection. A point location can be identified by geocoding an address. For concession licenses, or other scenarios covering a polygon location that is not contained in a known gazetteer, polygon and multi-polygon can be used.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Tipo",
+ "description": "The type of [GeoJSON Geometry Objects](https://www.rfc-editor.org/rfc/rfc7946#section-3.1) being provided. To provide longitude, latitude, and optional elevation, use 'Point', and enter an array of [longitude, latitude] or [longitude, latitude, elevation] as the value of the coordinates field: e.g. [-122.085, 37.42].",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "geometryType.csv",
+ "openCodelist": false,
+ "enum": [
+ "Point",
+ "MultiPoint",
+ "LineString",
+ "MultiLineString",
+ "Polygon",
+ "MultiPolygon",
+ null
+ ]
+ },
+ "coordinates": {
+ "title": "Coordenadas",
+ "description": "La lista de puntos, ej. [longitud, latitud] o [longitud, latitud, elevaci\u00f3n], o una lista anidada de puntos, para el objeto geom\u00e9trico JSON que est\u00e1 siendo descrito. La longitud y latitud deben ser expresadas en grados decimales en la proyecci\u00f3n WGS84 (EPSG:4326).",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "number",
+ "array"
+ ]
+ }
+ }
+ }
+ },
+ "gazetteer": {
+ "title": "Diccionario Geogr\u00e1fico",
+ "description": "Identificadores de un diccionario geogr\u00e1fico (un \u00edndice o directorio geogr\u00e1fico) para la ubicaci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "scheme": {
+ "title": "Esquema de diccionario geogr\u00e1fico",
+ "description": "El identificador del diccionario geogr\u00e1fico. La lista de c\u00f3digos `locationGazetteers.csv` provee detalles de servicios, si est\u00e1n disponibles, que pueden resolver una entrada del diccionario geogr\u00e1fico para proveer nombres de ubicaci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "locationGazetteers.csv",
+ "openCodelist": true
+ },
+ "identifiers": {
+ "title": "Identificadores",
+ "description": "Una lista de uno o m\u00e1s c\u00f3digos tomados del diccionario geogr\u00e1fico indicado en el campo `scheme`.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "uri": {
+ "title": "URI",
+ "description": "A URI to a further description of the location. This might be a human-readable document with information on the location, or a machine-readable description of the location.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ }
+ },
+ "Address": {
+ "properties": {
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "The description of the address.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/location/master/schema/index.html b/es/extensions/location/master/schema/index.html
new file mode 100644
index 000000000..d01f76d06
--- /dev/null
+++ b/es/extensions/location/master/schema/index.html
@@ -0,0 +1,597 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Ubicación +
+ ++ Permite indicar el punto de entrega o el sitio de las obras para una línea de pedido determinada en los objetos de licitación, adjudicación y contrato. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+This extension adds address and location fields to tenders and items, to communicate the location of proposed or executed contract delivery.
+La columna Category en la lista de código locationGazetteers.csv indica si el diccionario geográfico tiene identificadores para todo el mundo ('Universal') o solo un subconjunto ('National' o 'Sub-National').
Ejemplo
+A continuación se muestra un ejemplo de un elemento geolocalizado en la sección tender:
{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "description": "Ceremonial Trumpets for Oxford Town Hall",
+ "classification": {
+ "description": "Trumpets",
+ "scheme": "CPV",
+ "id": "37312100",
+ "uri": "http://purl.org/cpv/2008/code-37312100"
+ },
+ "deliveryLocations": [
+ {
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 51.751944,
+ -1.257778
+ ]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2640729"
+ ]
+ },
+ "description": "Central Oxford",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ }
+ ],
+ "deliveryAddresses": [
+ {
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom",
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford",
+ "description": "The old town hall"
+ }
+ ],
+ "unit": {
+ "name": "Items",
+ "value": {
+ "currency": "GBP",
+ "amount": 10000
+ }
+ },
+ "quantity": 10
+ }
+ ]
+ }
+}
+Si la adquisición relacionada con la reconstrucción de una carretera, entonces el elemento también podría especificar geometrías más complejas, tales como:
+{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "deliveryLocations": [
+ {
+ "geometry": {
+ "type": "LineString",
+ "coordinates": [
+ [
+ 102,
+ 0
+ ],
+ [
+ 103,
+ 1
+ ],
+ [
+ 104,
+ 0
+ ],
+ [
+ 105,
+ 1
+ ]
+ ]
+ },
+ "gazetteer": {
+ "scheme": "OSMW",
+ "identifiers": [
+ "27895985"
+ ]
+ },
+ "description": "St Aldate's",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ }
+ ]
+ }
+ ]
+ }
+}
+Puede tomar el contenido del objeto geométrico, excluyendo la palabra clave geometry, y conectarlo a cualquier herramienta de GeoJSON para ver la forma en que se describe.
Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+Unreleased
+-
+
- Add fields:
+
-
+
Tender.deliveryAddresses
+Tender.deliveryLocations
+Address.description
+
+ - Deprecate the
Item.deliveryAddressfield in favor of the newItem.deliveryAddressesfield, to support items with multiple delivery addresses
+ - Deprecate the
Item.deliveryLocationfield in favor of the newItem.deliveryLocationsfield, to support items with multiple delivery locations
+ - Añadir "format": "uri" a
Location.uri
+ - Update field descriptions to allow location objects to be used in other contexts than deliveries +
v1.1.5
+-
+
- Quitar la información sobre el tipo de las descripciones de los campos +
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- No permitir que
Location.geometryyLocation.gazetteersean null (bug se introdujo en v1.1.3)
+ - Corregir el orden de longitud y latitud en los campos de descripción para que sean iguales a la especificación GeoJSON. +
- Describe los valores de elevación o altitud +
- Quita las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que
Location.geometry.coordinatestenga null en su matriz de coordenadas
+ - No permitir que
Location.gazetteer.identifierstenga null en su lista de strings
+ - Corregir el nombre de la lista de código locationGazetteers.csv (era locationGazeteers.csv) +
- Permitir que
Location.geometryyLocation.gazetteersean null
+ - Agregar título y descripción a
Location.gazetteer
+ - Agregar descripción a
Item.deliveryLocation,Item.deliveryAddress
+ - Agregar la lista de código geometryType.csv para
Location.geometry.type
+ - Enlista listas de códigos en extension.json +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/location/v1.1.4/README.md b/es/extensions/location/v1.1.4/README.md
new file mode 100644
index 000000000..455b05652
--- /dev/null
+++ b/es/extensions/location/v1.1.4/README.md
@@ -0,0 +1,105 @@
+# Datos de ubicación
+
+Comunicar la ubicación del contrato propuesto o ejecutad es importante para muchos usuarios de los datos de contrataciones.
+
+Esta extensión introduce dos propiedades en el nivel `items` para describir la ubicación:
+
+- `deliveryAddress` - un bloque estándar `Address` que puede usarse para proporcionar una dirección postal donde deben entregarse los servicios.
+- `deliveryLocation` - un nuevo bloque que consta de entradas GeoJSON y de diccionario geográfico para describir una gama más amplia de ubicaciones a las que se refiere la partida del contrato.
+
+La columna `Category` en la lista de código `locationGazetteers.csv` indica si el diccionario geográfico tiene identificadores para todo el mundo ('Universal') o solo un subconjunto ('National' o 'Sub-National').
+
+## Ejemplo
+
+A continuación se muestra un ejemplo de un elemento geolocalizado:
+
+````json
+{
+ "items": [
+ {
+ "id": "item1",
+ "description": "Ceremonial Trumpets for Oxford Town Hall",
+ "classification": {
+ "description": "Trumpets",
+ "scheme": "CPV",
+ "id": "37312100",
+ "uri": "http://purl.org/cpv/2008/code-37312100"
+ },
+ "deliveryLocation": {
+ "geometry": {
+ "type": "Point",
+ "coordinates": [51.751944, -1.257778]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": ["2640729"]
+ },
+ "description": "Central Oxford",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "deliveryAddress": {
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom",
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford"
+ },
+ "unit": {
+ "name": "Items",
+ "value": {
+ "currency": "GBP",
+ "amount": 10000
+ }
+ },
+ "quantity": 10
+ }
+ ]
+}
+``
+
+If the procurement related to the rebuilding of a road, then the item could also specify more complex geometries such as:
+
+```json
+{
+"deliveryLocation": {
+ "geometry": {
+ "type": "LineString",
+ "coordinates": [ [ -1.256503402048622, 51.747792026616821 ], [ -1.256477837243949, 51.747500168748303 ], [ -1.256466773131763, 51.747365723021403 ], [ -1.256471969911729, 51.747246699996332 ], [ -1.256481860557471, 51.747182243160943 ], [ -1.256497618535434, 51.747079648666102 ] ]
+ },
+ "gazetteer": {
+ "scheme": "OSMW",
+ "identifiers": ["27895985"]
+ },
+ "description": "St Aldate's",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+}
+}
+````
+
+Puede tomar el contenido del objeto geométrico, excluyendo la palabra clave `geometry`, y conectarlo a cualquier herramienta de GeoJSON para ver la forma en que se describe.
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.4
+
+- No permitir que `Location.geometry` y` Location.gazetteer` sean null (bug se introdujo en v1.1.3)
+- Corregir el orden de longitud y latitud en los campos de descripción deben ser iguales a la especificación GeoJSON.
+- Describe los valores de elevación o altitud
+- Quita las directrices Sphinx del readme
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- No permitir que `Location.geometry.coordinates` tenga null en su matriz de coordenadas
+- No permitir que `Location.gazetteer.identifiers` tenga null en su lista de strings
+- Corregir el nombre de la lista de código locationGazetteers.csv (era locationGazeteers.csv)
+- Permitir que `Location.geometry` y` Location.gazetteer` sean null
+- Agregar título y descripción a `Location.gazetteer`
+- Agregar descripción a `Item.deliveryLocation`,` Item.deliveryAddress`
+- Agregar la lista de código geometryType.csv para `Location.geometry.type`
+- Enlista listas de códigos en extension.json
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/location/v1.1.4/codelists/geometryType.csv b/es/extensions/location/v1.1.4/codelists/geometryType.csv
new file mode 100644
index 000000000..618325558
--- /dev/null
+++ b/es/extensions/location/v1.1.4/codelists/geometryType.csv
@@ -0,0 +1,7 @@
+Código,Título,Descripción,Fuente
+Point,Point,"For type 'Point', the 'coordinates' member is a single position.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiPoint,MultiPoint,"For type 'MultiPoint', the 'coordinates' member is an array of positions.",https://tools.ietf.org/html/rfc7946#section-3.1
+LineString,LineString,"For type 'LineString', the 'coordinates' member is an array of two or more positions.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiLineString,MultiLineString,"For type 'MultiLineString', the 'coordinates' member is an array of LineString coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
+Polygon,Polygon,"For type 'Polygon', the 'coordinates' member MUST be an array of linear ring coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiPolygon,MultiPolygon,"For type 'MultiPolygon', the 'coordinates' member is an array of Polygon coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
diff --git a/es/extensions/location/v1.1.4/codelists/index.html b/es/extensions/location/v1.1.4/codelists/index.html
new file mode 100644
index 000000000..094c5b8db
--- /dev/null
+++ b/es/extensions/location/v1.1.4/codelists/index.html
@@ -0,0 +1,577 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Ubicación +
+ ++ Permite indicar el punto de entrega o el sitio de las obras para una línea de pedido determinada en los objetos de licitación, adjudicación y contrato. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryLocations
+
+ |
+ + Delivery Locations + | +
+ The locations where activity related to this tender will take place. + + |
+ + array of Location objects + | +
+
+ deliveryAddresses
+
+ |
+ + Delivery Addresses + | +
+ The addresses to which, or where, goods or services related to this tender will be delivered. + + |
+ + array of Address objects + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryLocations
+
+ |
+ + Delivery Locations + | +
+ The locations where activity related to this tender, contract or license will be delivered. + + |
+ + array of Location objects + | +
+
+ deliveryLocation
+
+ |
+ + Ubicación de Entrega + | +
+ La ubicación donde la actividad relacionada con esta licitación, contrato o licencia será entregada o se llevará a cabo. + ++ + Deprecated in OCDS 1.2.0: + + This field is deprecated in favour of `.deliveryLocations` to support items with multiple delivery locations. + + |
+ + Location object + | +
+
+ deliveryAddresses
+
+ |
+ + Delivery Addresses + | +
+ The addresses to which, or where, goods or services related to this tender, contract or license will be delivered. + + |
+ + array of Address objects + | +
+
+ deliveryAddress
+
+ |
+ + Dirección de Entrega + | +
+ La dirección en la que bienes y servicios relacionados con esta licitación, contrato o licencia serán entregados. + ++ + Deprecated in OCDS 1.2.0: + + This field is deprecated in favour of `.deliveryAddresses` to support items with multiple delivery locations. + + |
+ + Address object + | +
+ Location +
+ +
+ The extension defines a new Location object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Descripción + | +
+ Un nombre o descripción para esta ubicación. Esto puede incluir el(los) nombre(s) de la ubicación (o ubicaciones), o puede incluir una descripción legible de la ubicación a ser cubierta. + + |
+ + string + | +
+
+ geometry
+
+ |
+ + Geometría + | +
+ We follow the GeoJSON standard to express basic location information, using longitude, latitude, and optional elevation values in the WGS84 (EPSG:4326) projection. A point location can be identified by geocoding an address. For concession licenses, or other scenarios covering a polygon location that is not contained in a known gazetteer, polygon and multi-polygon can be used. + + |
+ + object + | +
+
+ geometry.
+ |
+ + Tipo + | +
+ The type of GeoJSON Geometry Objects being provided. To provide longitude, latitude, and optional elevation, use 'Point', and enter an array of [longitude, latitude] or [longitude, latitude, elevation] as the value of the coordinates field: e.g. [-122.085, 37.42]. + + |
+ + string from closed geometryType codelist + | +
+
+ geometry.
+ |
+ + Coordenadas + | +
+ La lista de puntos, ej. [longitud, latitud] o [longitud, latitud, elevación], o una lista anidada de puntos, para el objeto geométrico JSON que está siendo descrito. La longitud y latitud deben ser expresadas en grados decimales en la proyección WGS84 (EPSG:4326). + + |
+ + array of numbers / arrays + | +
+
+ gazetteer
+
+ |
+ + Diccionario Geográfico + | +
+ Identificadores de un diccionario geográfico (un índice o directorio geográfico) para la ubicación. + + |
+ + object + | +
+
+ gazetteer.
+ |
+ + Esquema de diccionario geográfico + | +
+ El identificador del diccionario geográfico. La lista de códigos |
+ + string from open locationGazetteers codelist + | +
+
+ gazetteer.
+ |
+ + Identificadores + | +
+ Una lista de uno o más códigos tomados del diccionario geográfico indicado en el campo |
+ + array of strings + | +
+
+ uri
+
+ |
+ + URI + | +
+ A URI to a further description of the location. This might be a human-readable document with information on the location, or a machine-readable description of the location. + + |
+ + string + | +
+ Address +
+ +
+ The extension defines these fields in the Address object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Descripción + | +
+ The description of the address. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/location/v1.1.4/codelists/locationGazetteers.csv b/es/extensions/location/v1.1.4/codelists/locationGazetteers.csv
new file mode 100644
index 000000000..5075c92fb
--- /dev/null
+++ b/es/extensions/location/v1.1.4/codelists/locationGazetteers.csv
@@ -0,0 +1,7 @@
+Categoría,Código,Título,Descripción,Fuente,Patrón de URI
+Sub-National,NUTS,EU Nomenclature of Territorial Units for Statistics,The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union.,http://simap.europa.eu/codes-and-nomenclatures/codes-nuts/index_en.htm,http://nuts.psi.enakting.org/id/
+National,ISO2,ISO Country Codes (3166-1 alpha-2),ISO 2-Digit Country Codes,http://www.iso.org/iso/country_codes.htm,
+Universal,GEONAMES,GeoNames,"GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations.",http://www.geonames.org/,http://www.geonames.org/
+Universal,OSMN,OpenStreetMap Node,"OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes may have tags to indicate the particular geographic feature they represent.",,http://www.openstreetmap.org/node/
+Universal,OSMR,OpenStreetMap Relation,"Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap.",http://wiki.openstreetmap.org/wiki/Relation,http://www.openstreetmap.org/relation/
+Universal,OSMW,OpenStreetMap Way,An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. May be used to describe fragments of roads or local boundaries and bounding boxes.,http://wiki.openstreetmap.org/wiki/Way,http://www.openstreetmap.org/way/
diff --git a/es/extensions/location/v1.1.4/extension.json b/es/extensions/location/v1.1.4/extension.json
new file mode 100644
index 000000000..a2c529a5d
--- /dev/null
+++ b/es/extensions/location/v1.1.4/extension.json
@@ -0,0 +1,23 @@
+{
+ "name": {
+ "en": "Location",
+ "es": "Ubicaci\u00f3n"
+ },
+ "description": {
+ "en": "Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects.",
+ "es": "Permite indicar el punto de entrega o el sitio de las obras para una l\u00ednea de pedido determinada en los objetos de licitaci\u00f3n, adjudicaci\u00f3n y contrato."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/location/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "locationGazetteers.csv",
+ "geometryType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/es/extensions/location/v1.1.4/index.html b/es/extensions/location/v1.1.4/index.html
new file mode 100644
index 000000000..9b0c9401d
--- /dev/null
+++ b/es/extensions/location/v1.1.4/index.html
@@ -0,0 +1,385 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Ubicación +
+ ++ Permite indicar el punto de entrega o el sitio de las obras para una línea de pedido determinada en los objetos de licitación, adjudicación y contrato. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ geometryType.csv +
+ +
+ You can download the geometryType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ Point
+
+ |
+ + Point + | +
+ For type 'Point', the 'coordinates' member is a single position. + +
|
+
+
+ MultiPoint
+
+ |
+ + MultiPoint + | +
+ For type 'MultiPoint', the 'coordinates' member is an array of positions. + +
|
+
+
+ LineString
+
+ |
+ + LineString + | +
+ For type 'LineString', the 'coordinates' member is an array of two or more positions. + +
|
+
+
+ MultiLineString
+
+ |
+ + MultiLineString + | +
+ For type 'MultiLineString', the 'coordinates' member is an array of LineString coordinate arrays. + +
|
+
+
+ Polygon
+
+ |
+ + Polygon + | +
+ For type 'Polygon', the 'coordinates' member MUST be an array of linear ring coordinate arrays. + +
|
+
+
+ MultiPolygon
+
+ |
+ + MultiPolygon + | +
+ For type 'MultiPolygon', the 'coordinates' member is an array of Polygon coordinate arrays. + +
|
+
+ locationGazetteers.csv +
+ +
+ You can download the locationGazetteers.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ NUTS
+
+ |
+ + EU Nomenclature of Territorial Units for Statistics + | +
+ The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union. + +
|
+
+
+ ISO2
+
+ |
+ + ISO Country Codes (3166-1 alpha-2) + | +
+ ISO 2-Digit Country Codes + +
|
+
+
+ GEONAMES
+
+ |
+ + GeoNames + | +
+ GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations. + +
|
+
+
+ OSMN
+
+ |
+ + OpenStreetMap Node + | +
+ OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes may have tags to indicate the particular geographic feature they represent. + +
|
+
+
+ OSMR
+
+ |
+ + OpenStreetMap Relation + | +
+ Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap. + +
|
+
+
+ OSMW
+
+ |
+ + OpenStreetMap Way + | +
+ An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. May be used to describe fragments of roads or local boundaries and bounding boxes. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/location/v1.1.4/release-schema.json b/es/extensions/location/v1.1.4/release-schema.json
new file mode 100644
index 000000000..158cf6c6d
--- /dev/null
+++ b/es/extensions/location/v1.1.4/release-schema.json
@@ -0,0 +1,111 @@
+{
+ "definitions": {
+ "Item": {
+ "properties": {
+ "deliveryLocation": {
+ "title": "Ubicaci\u00f3n de Entrega",
+ "description": "La ubicaci\u00f3n donde la actividad relacionada con esta licitaci\u00f3n, contrato o licencia ser\u00e1 entregada o se llevar\u00e1 a cabo. ",
+ "$ref": "#/definitions/Location"
+ },
+ "deliveryAddress": {
+ "title": "Direcci\u00f3n de Entrega",
+ "description": "La direcci\u00f3n en la que bienes y servicios relacionados con esta licitaci\u00f3n, contrato o licencia ser\u00e1n entregados.",
+ "$ref": "#/definitions/Address"
+ }
+ }
+ },
+ "Location": {
+ "type": "object",
+ "title": "Ubicaci\u00f3n de Entrega",
+ "description": "El lugar donde la actividad relacionada con esta licitaci\u00f3n, contrato o licencia ser\u00e1 entregada, o tendr\u00e1 lugar. Una ubicaci\u00f3n puede ser descrita por una geometr\u00eda (ubicaci\u00f3n de punto, l\u00ednea o pol\u00edgono), o una entrada de un diccionario geogr\u00e1fico, o ambas.",
+ "properties": {
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Un nombre o descripci\u00f3n de esta ubicaci\u00f3n. Esto podr\u00eda incluir el nombre de la(s) ubicaci\u00f3n(es), o podr\u00eda proporcionar una descripci\u00f3n legible por el usuario de la ubicaci\u00f3n a cubrir. Esta descripci\u00f3n se puede utilizar en una interfaz de usuario.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "geometry": {
+ "type": "object",
+ "title": "Geometr\u00eda",
+ "description": "Seguimos el est\u00e1ndar [GeoJSON] (http://geojson.org/) para expresar informaci\u00f3n b\u00e1sica de ubicaci\u00f3n, usando los valores de longitud, latitud y (opcionalmente) elevaci\u00f3n en [WGS84] (https://en.wikipedia.org/wiki/World_Geodetic_System) (EPSG: 4326). Una ubicaci\u00f3n de punto se puede identificar geocodificando una direcci\u00f3n de entrega. Para licencias de concesi\u00f3n, u otros contratos que cubran una ubicaci\u00f3n de pol\u00edgono que no est\u00e9 contenida en un diccionario geogr\u00e1fico conocido, se pueden usar pol\u00edgonos y pol\u00edgonos m\u00faltiples.",
+ "properties": {
+ "type": {
+ "title": "Tipo",
+ "description": "El tipo de [GeoJSON Geometry Objects] (http://geojson.org/geojson-spec.html#geometry-objects) que se proporciona. Para proporcionar longitud, latitud y (opcionalmente) elevaci\u00f3n, use 'Point', e ingrese una matriz de [longitude, latitude] o [longitude, latitude, elevation] como el valor del campo de coordenadas: por ejemplo, [-122.085, 37.42]. Tenga en cuenta la capitalizaci\u00f3n de los valores de tipo, a fin de mantener la compatibilidad con GeoJSON.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "enum": [
+ "Point",
+ "MultiPoint",
+ "LineString",
+ "MultiLineString",
+ "Polygon",
+ "MultiPolygon",
+ null
+ ],
+ "codelist": "geometryType.csv",
+ "openCodelist": false
+ },
+ "coordinates": {
+ "title": "Coordenadas",
+ "description": "El conjunto relevante de puntos, por ejemplo, [longitude, latitude] o [longitude, latitude, elevation], o una matriz anidada de puntos, para la geometr\u00eda GeoJSON que se describe. La longitud y la latitud DEBEN expresarse en grados decimales en la proyecci\u00f3n WGS84 (EPSG: 4326).",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "number",
+ "array"
+ ]
+ }
+ }
+ }
+ },
+ "gazetteer": {
+ "type": "object",
+ "title": "Diccionario Geogr\u00e1fico",
+ "description": "Un diccionario geogr\u00e1fico es un \u00edndice o directorio geogr\u00e1fico. El diccionario espec\u00edfico utilizado debe especificarse en el esquema, y \u200b\u200bse deben utilizar uno o m\u00e1s c\u00f3digos de ese diccionario en el identificador.",
+ "properties": {
+ "scheme": {
+ "title": "Esquema de diccionario geogr\u00e1fico",
+ "description": "La entrada del diccionario geogr\u00e1fico seleccionado en la lista de c\u00f3digos de diccionarios geogr\u00e1ficos. La lista de c\u00f3digos proporciona detalles de los servicios, cuando est\u00e1n disponibles, que pueden resolver una entrada de un diccionario geogr\u00e1fico para proporcionar nombres de ubicaci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "locationGazetteers.csv",
+ "openCodelist": true
+ },
+ "identifiers": {
+ "title": "Identificadores",
+ "description": "Una matriz de uno o m\u00e1s c\u00f3digos extra\u00eddos del diccionario geogr\u00e1fico indicado en el esquema.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "uri": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "title": "URI",
+ "description": "Un URI para una descripci\u00f3n m\u00e1s detallada de la ubicaci\u00f3n de la actividad. Esto puede ser un documento legible por el usuario con informaci\u00f3n sobre la ubicaci\u00f3n o una descripci\u00f3n legible por computadora de la ubicaci\u00f3n."
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/location/v1.1.4/schema/index.html b/es/extensions/location/v1.1.4/schema/index.html
new file mode 100644
index 000000000..f12cbc048
--- /dev/null
+++ b/es/extensions/location/v1.1.4/schema/index.html
@@ -0,0 +1,432 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Ubicación +
+ ++ Permite indicar el punto de entrega o el sitio de las obras para una línea de pedido determinada en los objetos de licitación, adjudicación y contrato. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Comunicar la ubicación del contrato propuesto o ejecutad es importante para muchos usuarios de los datos de contrataciones.
+Esta extensión introduce dos propiedades en el nivel items para describir la ubicación:
-
+
deliveryAddress- un bloque estándarAddressque puede usarse para proporcionar una dirección postal donde deben entregarse los servicios.
+deliveryLocation- un nuevo bloque que consta de entradas GeoJSON y de diccionario geográfico para describir una gama más amplia de ubicaciones a las que se refiere la partida del contrato.
+
La columna Category en la lista de código locationGazetteers.csv indica si el diccionario geográfico tiene identificadores para todo el mundo ('Universal') o solo un subconjunto ('National' o 'Sub-National').
Ejemplo
+A continuación se muestra un ejemplo de un elemento geolocalizado:
+{
+ "items": [
+ {
+ "id": "item1",
+ "description": "Ceremonial Trumpets for Oxford Town Hall",
+ "classification": {
+ "description": "Trumpets",
+ "scheme": "CPV",
+ "id": "37312100",
+ "uri": "http://purl.org/cpv/2008/code-37312100"
+ },
+ "deliveryLocation": {
+ "geometry": {
+ "type": "Point",
+ "coordinates": [51.751944, -1.257778]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": ["2640729"]
+ },
+ "description": "Central Oxford",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "deliveryAddress": {
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom",
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford"
+ },
+ "unit": {
+ "name": "Items",
+ "value": {
+ "currency": "GBP",
+ "amount": 10000
+ }
+ },
+ "quantity": 10
+ }
+ ]
+}
+``
+
+If the procurement related to the rebuilding of a road, then the item could also specify more complex geometries such as:
+
+```json
+{
+"deliveryLocation": {
+ "geometry": {
+ "type": "LineString",
+ "coordinates": [ [ -1.256503402048622, 51.747792026616821 ], [ -1.256477837243949, 51.747500168748303 ], [ -1.256466773131763, 51.747365723021403 ], [ -1.256471969911729, 51.747246699996332 ], [ -1.256481860557471, 51.747182243160943 ], [ -1.256497618535434, 51.747079648666102 ] ]
+ },
+ "gazetteer": {
+ "scheme": "OSMW",
+ "identifiers": ["27895985"]
+ },
+ "description": "St Aldate's",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+}
+}
+Puede tomar el contenido del objeto geométrico, excluyendo la palabra clave geometry, y conectarlo a cualquier herramienta de GeoJSON para ver la forma en que se describe.
Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.4
+-
+
- No permitir que
Location.geometryyLocation.gazetteersean null (bug se introdujo en v1.1.3)
+ - Corregir el orden de longitud y latitud en los campos de descripción deben ser iguales a la especificación GeoJSON. +
- Describe los valores de elevación o altitud +
- Quita las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que
Location.geometry.coordinatestenga null en su matriz de coordenadas
+ - No permitir que
Location.gazetteer.identifierstenga null en su lista de strings
+ - Corregir el nombre de la lista de código locationGazetteers.csv (era locationGazeteers.csv) +
- Permitir que
Location.geometryyLocation.gazetteersean null
+ - Agregar título y descripción a
Location.gazetteer
+ - Agregar descripción a
Item.deliveryLocation,Item.deliveryAddress
+ - Agregar la lista de código geometryType.csv para
Location.geometry.type
+ - Enlista listas de códigos en extension.json +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/location/v1.1.5/README.md b/es/extensions/location/v1.1.5/README.md
new file mode 100644
index 000000000..5d9f37fbf
--- /dev/null
+++ b/es/extensions/location/v1.1.5/README.md
@@ -0,0 +1,143 @@
+# Datos de ubicación
+
+Comunicar la ubicación del contrato propuesto o ejecutad es importante para muchos usuarios de los datos de contrataciones.
+
+Esta extensión introduce dos propiedades en el nivel `items` para describir la ubicación:
+
+- `deliveryAddress` - un bloque estándar `Address` que puede usarse para proporcionar una dirección postal donde deben entregarse los servicios.
+- `deliveryLocation` - un nuevo bloque que consta de entradas GeoJSON y de diccionario geográfico para describir una gama más amplia de ubicaciones a las que se refiere la partida del contrato.
+
+La columna `Category` en la lista de código `locationGazetteers.csv` indica si el diccionario geográfico tiene identificadores para todo el mundo ('Universal') o solo un subconjunto ('National' o 'Sub-National').
+
+## Ejemplo
+
+A continuación se muestra un ejemplo de un elemento geolocalizado en la sección `tender`:
+
+```json
+{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "description": "Ceremonial Trumpets for Oxford Town Hall",
+ "classification": {
+ "description": "Trumpets",
+ "scheme": "CPV",
+ "id": "37312100",
+ "uri": "http://purl.org/cpv/2008/code-37312100"
+ },
+ "deliveryLocation": {
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 51.751944,
+ -1.257778
+ ]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2640729"
+ ]
+ },
+ "description": "Central Oxford",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "deliveryAddress": {
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom",
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford"
+ },
+ "unit": {
+ "name": "Items",
+ "value": {
+ "currency": "GBP",
+ "amount": 10000
+ }
+ },
+ "quantity": 10
+ }
+ ]
+ }
+}
+```
+
+Si la adquisición relacionada con la reconstrucción de una carretera, entonces el elemento también podría especificar geometrías más complejas, tales como:
+
+```json
+{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "deliveryLocation": {
+ "geometry": {
+ "type": "LineString",
+ "coordinates": [
+ [
+ 102,
+ 0
+ ],
+ [
+ 103,
+ 1
+ ],
+ [
+ 104,
+ 0
+ ],
+ [
+ 105,
+ 1
+ ]
+ ]
+ },
+ "gazetteer": {
+ "scheme": "OSMW",
+ "identifiers": [
+ "27895985"
+ ]
+ },
+ "description": "St Aldate's",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ }
+ }
+ ]
+ }
+}
+```
+
+Puede tomar el contenido del objeto geométrico, excluyendo la palabra clave `geometry`, y conectarlo a cualquier herramienta de GeoJSON para ver la forma en que se describe.
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.5
+
+- Quitar la información sobre el tipo de las descripciones de los campos
+- Revisar las palabras normativas y no-normativas
+
+### v1.1.4
+
+- No permitir que `Location.geometry` y ` Location.gazetteer` sean null (bug se introdujo en v1.1.3)
+- Corregir el orden de longitud y latitud en los campos de descripción deben ser iguales a la especificación GeoJSON.
+- Describe los valores de elevación o altitud
+- Quita las directrices Sphinx del readme
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- No permitir que `Location.geometry.coordinates` tenga null en su matriz de coordenadas
+- No permitir que `Location.gazetteer.identifiers` tenga null en su lista de strings
+- Corregir el nombre de la lista de código locationGazetteers.csv (era locationGazeteers.csv)
+- Permitir que `Location.geometry` y` Location.gazetteer` sean null
+- Agregar título y descripción a `Location.gazetteer`
+- Agregar descripción a `Item.deliveryLocation`,` Item.deliveryAddress`
+- Agregar la lista de código geometryType.csv para `Location.geometry.type`
+- Enlista listas de códigos en extension.json
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/location/v1.1.5/codelists/geometryType.csv b/es/extensions/location/v1.1.5/codelists/geometryType.csv
new file mode 100644
index 000000000..b7ac1260b
--- /dev/null
+++ b/es/extensions/location/v1.1.5/codelists/geometryType.csv
@@ -0,0 +1,7 @@
+Código,Título,Descripción,Fuente
+Point,Point,"For type 'Point', the 'coordinates' member is a single position.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiPoint,MultiPoint,"For type 'MultiPoint', the 'coordinates' member is an array of positions.",https://tools.ietf.org/html/rfc7946#section-3.1
+LineString,LineString,"For type 'LineString', the 'coordinates' member is an array of two or more positions.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiLineString,MultiLineString,"For type 'MultiLineString', the 'coordinates' member is an array of LineString coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
+Polygon,Polygon,"For type 'Polygon', the 'coordinates' member must be an array of linear ring coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
+MultiPolygon,MultiPolygon,"For type 'MultiPolygon', the 'coordinates' member is an array of Polygon coordinate arrays.",https://tools.ietf.org/html/rfc7946#section-3.1
diff --git a/es/extensions/location/v1.1.5/codelists/index.html b/es/extensions/location/v1.1.5/codelists/index.html
new file mode 100644
index 000000000..eb4a8f377
--- /dev/null
+++ b/es/extensions/location/v1.1.5/codelists/index.html
@@ -0,0 +1,577 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Ubicación +
+ ++ Permite indicar el punto de entrega o el sitio de las obras para una línea de pedido determinada en los objetos de licitación, adjudicación y contrato. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryLocation
+
+ |
+ + Ubicación de Entrega + | +
+ La ubicación donde la actividad relacionada con esta licitación, contrato o licencia será entregada o se llevará a cabo. + + |
+ + Location object + | +
+
+ deliveryAddress
+
+ |
+ + Dirección de Entrega + | +
+ La dirección en la que bienes y servicios relacionados con esta licitación, contrato o licencia serán entregados. + + |
+ + Address object + | +
+ Location +
+ +
+ The extension defines a new Location object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Descripción + | +
+ Un nombre o descripción de esta ubicación. Esto podría incluir el nombre de la(s) ubicación(es), o podría proporcionar una descripción legible por el usuario de la ubicación a cubrir. Esta descripción se puede utilizar en una interfaz de usuario. + + |
+ + string + | +
+
+ geometry
+
+ |
+ + Geometría + | +
+ Seguimos el estándar [GeoJSON] (http://geojson.org/) para expresar información básica de ubicación, usando los valores de longitud, latitud y (opcionalmente) elevación en [WGS84] (https://en.wikipedia.org/wiki/World_Geodetic_System) (EPSG: 4326). Una ubicación de punto se puede identificar geocodificando una dirección de entrega. Para licencias de concesión, u otros contratos que cubran una ubicación de polígono que no esté contenida en un diccionario geográfico conocido, se pueden usar polígonos y polígonos múltiples. + + |
+ + object + | +
+
+ geometry.
+ |
+ + Tipo + | +
+ El tipo de [GeoJSON Geometry Objects] (http://geojson.org/geojson-spec.html#geometry-objects) que se proporciona. Para proporcionar longitud, latitud y (opcionalmente) elevación, use 'Point', e ingrese una matriz de [longitude, latitude] o [longitude, latitude, elevation] como el valor del campo de coordenadas: por ejemplo, [-122.085, 37.42]. Tenga en cuenta la capitalización de los valores de tipo, a fin de mantener la compatibilidad con GeoJSON. + + |
+ + string from closed geometryType codelist + | +
+
+ geometry.
+ |
+ + Coordenadas + | +
+ El conjunto relevante de puntos, por ejemplo, [longitude, latitude] o [longitude, latitude, elevation], o una matriz anidada de puntos, para la geometría GeoJSON que se describe. La longitud y la latitud DEBEN expresarse en grados decimales en la proyección WGS84 (EPSG: 4326). + + |
+ + array of numbers / arrays + | +
+
+ gazetteer
+
+ |
+ + Diccionario Geográfico + | +
+ Un diccionario geográfico es un índice o directorio geográfico. El diccionario específico utilizado debe especificarse en el esquema, y se deben utilizar uno o más códigos de ese diccionario en el identificador. + + |
+ + object + | +
+
+ gazetteer.
+ |
+ + Esquema de diccionario geográfico + | +
+ La entrada del diccionario geográfico seleccionado en la lista de códigos de diccionarios geográficos. La lista de códigos proporciona detalles de los servicios, cuando están disponibles, que pueden resolver una entrada de un diccionario geográfico para proporcionar nombres de ubicación. + + |
+ + string from open locationGazetteers codelist + | +
+
+ gazetteer.
+ |
+ + Identificadores + | +
+ Una matriz de uno o más códigos extraídos del diccionario geográfico indicado en el esquema. + + |
+ + array of strings + | +
+
+ uri
+
+ |
+ + URI + | +
+ Un URI para una descripción más detallada de la ubicación de la actividad. Esto puede ser un documento legible por el usuario con información sobre la ubicación o una descripción legible por computadora de la ubicación. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/location/v1.1.5/codelists/locationGazetteers.csv b/es/extensions/location/v1.1.5/codelists/locationGazetteers.csv
new file mode 100644
index 000000000..b8ccde9c5
--- /dev/null
+++ b/es/extensions/location/v1.1.5/codelists/locationGazetteers.csv
@@ -0,0 +1,7 @@
+Categoría,Código,Título,Descripción,Fuente,Patrón de URI
+Sub-National,NUTS,EU Nomenclature of Territorial Units for Statistics,The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union.,http://simap.europa.eu/codes-and-nomenclatures/codes-nuts/index_en.htm,http://nuts.psi.enakting.org/id/
+National,ISO2,ISO Country Codes (3166-1 alpha-2),ISO 2-Digit Country Codes,http://www.iso.org/iso/country_codes.htm,
+Universal,GEONAMES,GeoNames,"GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations.",http://www.geonames.org/,http://www.geonames.org/
+Universal,OSMN,OpenStreetMap Node,"OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes might have tags to indicate the particular geographic feature they represent.",,http://www.openstreetmap.org/node/
+Universal,OSMR,OpenStreetMap Relation,"Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap.",http://wiki.openstreetmap.org/wiki/Relation,http://www.openstreetmap.org/relation/
+Universal,OSMW,OpenStreetMap Way,An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. It can be used to describe fragments of roads or local boundaries and bounding boxes.,http://wiki.openstreetmap.org/wiki/Way,http://www.openstreetmap.org/way/
diff --git a/es/extensions/location/v1.1.5/extension.json b/es/extensions/location/v1.1.5/extension.json
new file mode 100644
index 000000000..7dc7660b4
--- /dev/null
+++ b/es/extensions/location/v1.1.5/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Location",
+ "es": "Ubicaci\u00f3n"
+ },
+ "description": {
+ "en": "Allows the point of delivery or site of works for a given line item to be indicated in tender, award and contract objects.",
+ "es": "Permite indicar el punto de entrega o el sitio de las obras para una l\u00ednea de pedido determinada en los objetos de licitaci\u00f3n, adjudicaci\u00f3n y contrato."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/location/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "locationGazetteers.csv",
+ "geometryType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/location/v1.1.5/index.html b/es/extensions/location/v1.1.5/index.html
new file mode 100644
index 000000000..ee2eb0cc3
--- /dev/null
+++ b/es/extensions/location/v1.1.5/index.html
@@ -0,0 +1,425 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Ubicación +
+ ++ Permite indicar el punto de entrega o el sitio de las obras para una línea de pedido determinada en los objetos de licitación, adjudicación y contrato. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ geometryType.csv +
+ +
+ You can download the geometryType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ Point
+
+ |
+ + Point + | +
+ For type 'Point', the 'coordinates' member is a single position. + +
|
+
+
+ MultiPoint
+
+ |
+ + MultiPoint + | +
+ For type 'MultiPoint', the 'coordinates' member is an array of positions. + +
|
+
+
+ LineString
+
+ |
+ + LineString + | +
+ For type 'LineString', the 'coordinates' member is an array of two or more positions. + +
|
+
+
+ MultiLineString
+
+ |
+ + MultiLineString + | +
+ For type 'MultiLineString', the 'coordinates' member is an array of LineString coordinate arrays. + +
|
+
+
+ Polygon
+
+ |
+ + Polygon + | +
+ For type 'Polygon', the 'coordinates' member must be an array of linear ring coordinate arrays. + +
|
+
+
+ MultiPolygon
+
+ |
+ + MultiPolygon + | +
+ For type 'MultiPolygon', the 'coordinates' member is an array of Polygon coordinate arrays. + +
|
+
+ locationGazetteers.csv +
+ +
+ You can download the locationGazetteers.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ NUTS
+
+ |
+ + EU Nomenclature of Territorial Units for Statistics + | +
+ The Nomenclature of Territorial Units for Statistics (NUTS) was established by Eurostat in order to provide a single uniform breakdown of territorial units for the production of regional statistics for the European Union. + +
|
+
+
+ ISO2
+
+ |
+ + ISO Country Codes (3166-1 alpha-2) + | +
+ ISO 2-Digit Country Codes + +
|
+
+
+ GEONAMES
+
+ |
+ + GeoNames + | +
+ GeoNames provides numerical identifiers for many points of interest around the world, including administrative divisions, populated centres and other locations, embedded within a structured tree of geographic relations. + +
|
+
+
+ OSMN
+
+ |
+ + OpenStreetMap Node + | +
+ OpenStreetMap Nodes consist of a single point in space defined by a latitude, longitude and node ID. Nodes might have tags to indicate the particular geographic feature they represent. + +
|
+
+
+ OSMR
+
+ |
+ + OpenStreetMap Relation + | +
+ Relations are used to model logical (and usually local) or geographic relationships between objects. In practice, boundaries of geographic areas are available as Relations in OpenStreetMap. + +
|
+
+
+ OSMW
+
+ |
+ + OpenStreetMap Way + | +
+ An OpenStreetMap Way is an ordered list of OpenStreetMap nodes. It can be used to describe fragments of roads or local boundaries and bounding boxes. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/location/v1.1.5/release-schema.json b/es/extensions/location/v1.1.5/release-schema.json
new file mode 100644
index 000000000..bd6386565
--- /dev/null
+++ b/es/extensions/location/v1.1.5/release-schema.json
@@ -0,0 +1,111 @@
+{
+ "definitions": {
+ "Item": {
+ "properties": {
+ "deliveryLocation": {
+ "title": "Ubicaci\u00f3n de Entrega",
+ "description": "La ubicaci\u00f3n donde la actividad relacionada con esta licitaci\u00f3n, contrato o licencia ser\u00e1 entregada o se llevar\u00e1 a cabo. ",
+ "$ref": "#/definitions/Location"
+ },
+ "deliveryAddress": {
+ "title": "Direcci\u00f3n de Entrega",
+ "description": "La direcci\u00f3n en la que bienes y servicios relacionados con esta licitaci\u00f3n, contrato o licencia ser\u00e1n entregados.",
+ "$ref": "#/definitions/Address"
+ }
+ }
+ },
+ "Location": {
+ "type": "object",
+ "title": "Ubicaci\u00f3n de Entrega",
+ "description": "El lugar donde la actividad relacionada con esta licitaci\u00f3n, contrato o licencia ser\u00e1 entregada, o tendr\u00e1 lugar. Una ubicaci\u00f3n puede ser descrita por una geometr\u00eda (ubicaci\u00f3n de punto, l\u00ednea o pol\u00edgono), o una entrada de un diccionario geogr\u00e1fico, o ambas.",
+ "properties": {
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Un nombre o descripci\u00f3n para esta ubicaci\u00f3n. Esto puede incluir el(los) nombre(s) de la ubicaci\u00f3n (o ubicaciones), o puede incluir una descripci\u00f3n legible de la ubicaci\u00f3n a ser cubierta.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "geometry": {
+ "type": "object",
+ "title": "Geometr\u00eda",
+ "description": "Seguimos el [est\u00e1ndar GeoJSON] (http://geojson.org/) para expresar informaci\u00f3n b\u00e1sica de ubicaci\u00f3n, usando los valores de longitud, latitud y (opcionalmente) elevaci\u00f3n en la proyecci\u00f3n [WGS84] (https://en.wikipedia.org/wiki/World_Geodetic_System) (EPSG: 4326). Un punto de ubicaci\u00f3n se puede identificar geocodificando una direcci\u00f3n de entrega. Para licencias de concesi\u00f3n, u otros contratos que cubran una ubicaci\u00f3n en pol\u00edgono que no est\u00e9 contenida en un diccionario geogr\u00e1fico conocido, se pueden usar pol\u00edgonos y pol\u00edgonos m\u00faltiples.",
+ "properties": {
+ "type": {
+ "title": "Tipo",
+ "description": "El tipo de [Objeto Geom\u00e9trico GeoJSON] (http://geojson.org/geojson-spec.html#geometry-objects) que se proporciona. Para proporcionar longitud, latitud y (opcionalmente) elevaci\u00f3n, use 'Point', e ingrese una lista de [longitud, latitud] o [longitud, latitud, elevaci\u00f3n] como el valor del campo de coordenadas: por ejemplo, [-122.085, 37.42].",
+ "type": [
+ "string",
+ "null"
+ ],
+ "enum": [
+ "Point",
+ "MultiPoint",
+ "LineString",
+ "MultiLineString",
+ "Polygon",
+ "MultiPolygon",
+ null
+ ],
+ "codelist": "geometryType.csv",
+ "openCodelist": false
+ },
+ "coordinates": {
+ "title": "Coordenadas",
+ "description": "La lista de puntos, ej. [longitud, latitud] o [longitud, latitud, elevaci\u00f3n], o una lista anidada de puntos, para el objeto geom\u00e9trico JSON que est\u00e1 siendo descrito. La longitud y latitud deben ser expresadas en grados decimales en la proyecci\u00f3n WGS84 (EPSG:4326).",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "number",
+ "array"
+ ]
+ }
+ }
+ }
+ },
+ "gazetteer": {
+ "type": "object",
+ "title": "Diccionario Geogr\u00e1fico",
+ "description": "Identificadores de un diccionario geogr\u00e1fico (un \u00edndice o directorio geogr\u00e1fico) para la ubicaci\u00f3n.",
+ "properties": {
+ "scheme": {
+ "title": "Esquema de diccionario geogr\u00e1fico",
+ "description": "El identificador del diccionario geogr\u00e1fico. La lista de c\u00f3digos `locationGazetteers.csv` provee detalles de servicios, si est\u00e1n disponibles, que pueden resolver una entrada del diccionario geogr\u00e1fico para proveer nombres de ubicaci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "locationGazetteers.csv",
+ "openCodelist": true
+ },
+ "identifiers": {
+ "title": "Identificadores",
+ "description": "Una lista de uno o m\u00e1s c\u00f3digos tomados del diccionario geogr\u00e1fico indicado en el campo `scheme`.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "uri": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "title": "URI",
+ "description": "Un URI a una descripci\u00f3n m\u00e1s detallada de la ubicaci\u00f3n de la actividad. Esto puede ser un documento legible por el usuario con informaci\u00f3n sobre la ubicaci\u00f3n o una descripci\u00f3n legible por computadora de la ubicaci\u00f3n."
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/location/v1.1.5/schema/index.html b/es/extensions/location/v1.1.5/schema/index.html
new file mode 100644
index 000000000..c5a05d6e8
--- /dev/null
+++ b/es/extensions/location/v1.1.5/schema/index.html
@@ -0,0 +1,432 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Ubicación +
+ ++ Permite indicar el punto de entrega o el sitio de las obras para una línea de pedido determinada en los objetos de licitación, adjudicación y contrato. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Comunicar la ubicación del contrato propuesto o ejecutad es importante para muchos usuarios de los datos de contrataciones.
+Esta extensión introduce dos propiedades en el nivel items para describir la ubicación:
-
+
deliveryAddress- un bloque estándarAddressque puede usarse para proporcionar una dirección postal donde deben entregarse los servicios.
+deliveryLocation- un nuevo bloque que consta de entradas GeoJSON y de diccionario geográfico para describir una gama más amplia de ubicaciones a las que se refiere la partida del contrato.
+
La columna Category en la lista de código locationGazetteers.csv indica si el diccionario geográfico tiene identificadores para todo el mundo ('Universal') o solo un subconjunto ('National' o 'Sub-National').
Ejemplo
+A continuación se muestra un ejemplo de un elemento geolocalizado en la sección tender:
{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "description": "Ceremonial Trumpets for Oxford Town Hall",
+ "classification": {
+ "description": "Trumpets",
+ "scheme": "CPV",
+ "id": "37312100",
+ "uri": "http://purl.org/cpv/2008/code-37312100"
+ },
+ "deliveryLocation": {
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 51.751944,
+ -1.257778
+ ]
+ },
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2640729"
+ ]
+ },
+ "description": "Central Oxford",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ },
+ "deliveryAddress": {
+ "postalCode": "OX1 1BX",
+ "countryName": "United Kingdom",
+ "streetAddress": "Town Hall, St Aldate's",
+ "region": "Oxfordshire",
+ "locality": "Oxford"
+ },
+ "unit": {
+ "name": "Items",
+ "value": {
+ "currency": "GBP",
+ "amount": 10000
+ }
+ },
+ "quantity": 10
+ }
+ ]
+ }
+}
+Si la adquisición relacionada con la reconstrucción de una carretera, entonces el elemento también podría especificar geometrías más complejas, tales como:
+{
+ "tender": {
+ "items": [
+ {
+ "id": "item1",
+ "deliveryLocation": {
+ "geometry": {
+ "type": "LineString",
+ "coordinates": [
+ [
+ 102,
+ 0
+ ],
+ [
+ 103,
+ 1
+ ],
+ [
+ 104,
+ 0
+ ],
+ [
+ 105,
+ 1
+ ]
+ ]
+ },
+ "gazetteer": {
+ "scheme": "OSMW",
+ "identifiers": [
+ "27895985"
+ ]
+ },
+ "description": "St Aldate's",
+ "uri": "http://www.geonames.org/2640729/oxford.html"
+ }
+ }
+ ]
+ }
+}
+Puede tomar el contenido del objeto geométrico, excluyendo la palabra clave geometry, y conectarlo a cualquier herramienta de GeoJSON para ver la forma en que se describe.
Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.5
+-
+
- Quitar la información sobre el tipo de las descripciones de los campos +
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- No permitir que
Location.geometryyLocation.gazetteersean null (bug se introdujo en v1.1.3)
+ - Corregir el orden de longitud y latitud en los campos de descripción deben ser iguales a la especificación GeoJSON. +
- Describe los valores de elevación o altitud +
- Quita las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que
Location.geometry.coordinatestenga null en su matriz de coordenadas
+ - No permitir que
Location.gazetteer.identifierstenga null en su lista de strings
+ - Corregir el nombre de la lista de código locationGazetteers.csv (era locationGazeteers.csv) +
- Permitir que
Location.geometryyLocation.gazetteersean null
+ - Agregar título y descripción a
Location.gazetteer
+ - Agregar descripción a
Item.deliveryLocation,Item.deliveryAddress
+ - Agregar la lista de código geometryType.csv para
Location.geometry.type
+ - Enlista listas de códigos en extension.json +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/lots/index.html b/es/extensions/lots/index.html
new file mode 100644
index 000000000..f302f4c9c
--- /dev/null
+++ b/es/extensions/lots/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Ubicación +
+ ++ Permite indicar el punto de entrega o el sitio de las obras para una línea de pedido determinada en los objetos de licitación, adjudicación y contrato. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ deliveryLocation
+
+ |
+ + Ubicación de Entrega + | +
+ La ubicación donde la actividad relacionada con esta licitación, contrato o licencia será entregada o se llevará a cabo. + + |
+ + Location object + | +
+
+ deliveryAddress
+
+ |
+ + Dirección de Entrega + | +
+ La dirección en la que bienes y servicios relacionados con esta licitación, contrato o licencia serán entregados. + + |
+ + Address object + | +
+ Location +
+ +
+ The extension defines a new Location object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Descripción + | +
+ Un nombre o descripción para esta ubicación. Esto puede incluir el(los) nombre(s) de la ubicación (o ubicaciones), o puede incluir una descripción legible de la ubicación a ser cubierta. + + |
+ + string + | +
+
+ geometry
+
+ |
+ + Geometría + | +
+ Seguimos el [estándar GeoJSON] (http://geojson.org/) para expresar información básica de ubicación, usando los valores de longitud, latitud y (opcionalmente) elevación en la proyección [WGS84] (https://en.wikipedia.org/wiki/World_Geodetic_System) (EPSG: 4326). Un punto de ubicación se puede identificar geocodificando una dirección de entrega. Para licencias de concesión, u otros contratos que cubran una ubicación en polígono que no esté contenida en un diccionario geográfico conocido, se pueden usar polígonos y polígonos múltiples. + + |
+ + object + | +
+
+ geometry.
+ |
+ + Tipo + | +
+ El tipo de [Objeto Geométrico GeoJSON] (http://geojson.org/geojson-spec.html#geometry-objects) que se proporciona. Para proporcionar longitud, latitud y (opcionalmente) elevación, use 'Point', e ingrese una lista de [longitud, latitud] o [longitud, latitud, elevación] como el valor del campo de coordenadas: por ejemplo, [-122.085, 37.42]. + + |
+ + string from closed geometryType codelist + | +
+
+ geometry.
+ |
+ + Coordenadas + | +
+ La lista de puntos, ej. [longitud, latitud] o [longitud, latitud, elevación], o una lista anidada de puntos, para el objeto geométrico JSON que está siendo descrito. La longitud y latitud deben ser expresadas en grados decimales en la proyección WGS84 (EPSG:4326). + + |
+ + array of numbers / arrays + | +
+
+ gazetteer
+
+ |
+ + Diccionario Geográfico + | +
+ Identificadores de un diccionario geográfico (un índice o directorio geográfico) para la ubicación. + + |
+ + object + | +
+
+ gazetteer.
+ |
+ + Esquema de diccionario geográfico + | +
+ El identificador del diccionario geográfico. La lista de códigos |
+ + string from open locationGazetteers codelist + | +
+
+ gazetteer.
+ |
+ + Identificadores + | +
+ Una lista de uno o más códigos tomados del diccionario geográfico indicado en el campo |
+ + array of strings + | +
+
+ uri
+
+ |
+ + URI + | +
+ Un URI a una descripción más detallada de la ubicación de la actividad. Esto puede ser un documento legible por el usuario con información sobre la ubicación o una descripción legible por computadora de la ubicación. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/lots/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/lots/master/release-schema.json b/es/extensions/lots/master/release-schema.json
new file mode 100644
index 000000000..57a99b1ab
--- /dev/null
+++ b/es/extensions/lots/master/release-schema.json
@@ -0,0 +1,397 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "lots": {
+ "title": "Lotes",
+ "description": "Un proceso de licitaci\u00f3n puede dividirse en lotes, en los que los licitadores pueden pujar por uno o varios lotes. Los detalles de cada lote se pueden proporcionar aqu\u00ed. Los art\u00edculos, documentos y otras caracter\u00edsticas pueden entonces hacer referencia al lote con el que est\u00e1n relacionados utilizando relatedLot. Si no se indica un identificador de relatedLots, los valores deben interpretarse como aplicables a toda la licitaci\u00f3n. Los detalles sobre toda la licitaci\u00f3n pueden anularse para un lote determinado mediante su inclusi\u00f3n en el objeto lote.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Lot"
+ }
+ },
+ "lotDetails": {
+ "title": "Detalles del lote",
+ "description": "Details of any criteria that apply to bidding on the lots in this tender.",
+ "type": "object",
+ "properties": {
+ "maximumLotsBidPerSupplier": {
+ "title": "Lotes m\u00e1ximos por proveedor",
+ "description": "El n\u00famero m\u00e1ximo de lotes por los que un proveedor puede ofertar como parte de este proceso de contrataci\u00f3n.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "maximumLotsAwardedPerSupplier": {
+ "title": "Lotes m\u00e1ximos por proveedor",
+ "description": "El n\u00famero m\u00e1ximo de lotes que pueden adjudicarse a un proveedor como parte de este proceso de contrataci\u00f3n.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "awardCriteriaDetails": {
+ "title": "Detalles de criterios de adjudicaci\u00f3n",
+ "description": "Cualquier informaci\u00f3n detallada o adicional sobre la adjudicaci\u00f3n o los criterios de selecci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "lotGroups": {
+ "title": "Grupos de lote",
+ "description": "Cuando el comprador se reserva el derecho de combinar lotes, o desea especificar el valor total para un grupo de lotes, se utiliza un grupo de lotes para capturar esta informaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/LotGroup"
+ }
+ }
+ }
+ },
+ "Document": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lote(s) relacionado(s)",
+ "description": "The identifiers of the lots to which this document relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "relatedLot": {
+ "title": "Lote relacionado",
+ "description": "The identifier of the lot to which this item relates.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Milestone": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lote(s) relacionado(s)",
+ "description": "The identifiers of the lots to which this milestone relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lote(s) relacionado(s)",
+ "description": "The identifiers of the lots to which this award relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Amendment": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lote(s) relacionado(s)",
+ "description": "The identifiers of the lots to which this amendment relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "RelatedProcess": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lote(s) relacionado(s)",
+ "description": "The identifiers of the lots to which this related process relates.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Lot": {
+ "title": "Lotes",
+ "description": "Un lote es una agrupaci\u00f3n de art\u00edculos en una licitaci\u00f3n que se pueden ofertar o adjudicar juntos.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID Lote",
+ "description": "Un identificador local para este lote, tal como un n\u00famero de lote. Esto se utiliza en las referencias relatedLots en el nivel de art\u00edculo, documento y adjudicaci\u00f3n.",
+ "type": "string"
+ },
+ "identifiers": {
+ "title": "Identifiers",
+ "description": "Identifiers for this lot. This field can be used to provide internal identifiers for the lot, such as identifiers from a buyer's document management system or procurement system.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/SimpleIdentifier"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "title": {
+ "title": "T\u00edtulo",
+ "description": "Un t\u00edtulo para este lote.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una descripci\u00f3n de este lote.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "title": "Estatus de lote",
+ "description": "El estado actual del proceso relacionado a este lote.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "tenderStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "planning",
+ "planned",
+ "active",
+ "cancelled",
+ "unsuccessful",
+ "complete",
+ "withdrawn",
+ null
+ ]
+ },
+ "value": {
+ "title": "Valor del lote",
+ "description": "El valor m\u00e1ximo estimado de este lote.",
+ "$ref": "#/definitions/Value"
+ },
+ "minValue": {
+ "title": "Minimum value",
+ "description": "The estimated minimum value of the lot. A negative value indicates that the contracting process may involve payments from the supplier to the buyer (commonly used in concession contracts).",
+ "$ref": "#/definitions/Value"
+ },
+ "tenderPeriod": {
+ "title": "Tender period",
+ "description": "The period when this lot is open for submissions. The end date is the closing date for bid submissions.",
+ "$ref": "#/definitions/Period"
+ },
+ "contractPeriod": {
+ "title": "Per\u00edodo del contrato",
+ "description": "El per\u00edodo sobre el cual se estima o especifica que el contrato estar\u00e1 activo. Si el lote no especifica fechas expl\u00edcitas, se puede usar el campo `duration`.",
+ "$ref": "#/definitions/Period"
+ },
+ "buyer": {
+ "title": "Buyer",
+ "description": "The organization aiming to conclude a contract with a supplier or to use the goods, works or services in this lot. This may be different from the procuring entity who may be specified in the tender data.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "additionalClassifications": {
+ "title": "Additional classifications",
+ "description": "Additional classifications for this lot.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "mainProcurementCategory": {
+ "title": "Main procurement category",
+ "description": "The primary category describing the main object of this lot, using the closed procurementCategory codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "procurementCategory.csv",
+ "openCodelist": false,
+ "enum": [
+ "goods",
+ "services",
+ "works",
+ null
+ ]
+ },
+ "additionalProcurementCategories": {
+ "title": "Additional procurement categories",
+ "description": "Any additional categories describing the objects of this lot, using the open extendedProcurementCategory codelist.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "extendedProcurementCategory.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "enquiryPeriod": {
+ "title": "Enquiry period",
+ "description": "The period during which potential bidders may submit questions and requests for clarification about this lot to the buyer or the procuring entity.",
+ "$ref": "#/definitions/Period"
+ },
+ "milestones": {
+ "title": "Milestones",
+ "description": "Milestones associated with this lot.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Milestone"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "submissionMethodDetails": {
+ "title": "Submission method details",
+ "description": "Information about the methods by which bids are submitted for this lot. This can include the address, e-mail address or online service to which bids are submitted, and any special requirements to be followed for submissions. More structured information can be provided using the submission terms extension.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ }
+ },
+ "LotGroup": {
+ "title": "Grupo del lote",
+ "description": "Cuando el comprador se reserva el derecho de combinar lotes, o desea especificar el valor total para un grupo de lotes, se utiliza un grupo de lotes para capturar esta informaci\u00f3n.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador del grupo de lote",
+ "description": "Un identificador local para este grupo de lotes.",
+ "type": "string"
+ },
+ "identifiers": {
+ "title": "Identifiers",
+ "description": "Identifiers for this lot group. This field can be used to provide internal identifiers for the lot group, such as identifiers from a buyer's document management system or procurement system.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/SimpleIdentifier"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "title": {
+ "title": "T\u00edtulo",
+ "description": "A title for this lot group.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "A description of this lot group.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "relatedLots": {
+ "title": "Lote(s) relacionado(s)",
+ "description": "Una lista de los identificadores de los lotes que forman este grupo. Los lotes pueden aparecer en m\u00e1s de un grupo.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "optionToCombine": {
+ "title": "Opci\u00f3n de combinar",
+ "description": "El comprador se reserva el derecho de combinar los lotes de este grupo al adjudicar un contrato.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "maximumValue": {
+ "title": "Valor m\u00e1ximo",
+ "description": "El valor m\u00e1ximo estimado de los lotes de este grupo. Este puede ser inferior a la suma total de los valores de los lotes.",
+ "$ref": "#/definitions/Value"
+ }
+ }
+ },
+ "SimpleIdentifier": {
+ "title": "Simple identifier",
+ "description": "An unambiguous reference to a resource within a given context.",
+ "type": "object",
+ "properties": {
+ "scheme": {
+ "title": "Scheme",
+ "description": "The list, register or system from which the identifier is taken.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "The identifier taken from the scheme.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "versionId": true,
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/lots/master/schema/index.html b/es/extensions/lots/master/schema/index.html
new file mode 100644
index 000000000..737b6ca94
--- /dev/null
+++ b/es/extensions/lots/master/schema/index.html
@@ -0,0 +1,1158 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lotes +
+ ++ Un proceso de licitación se puede dividir en lotes, donde los licitadores pueden ofertar en uno o más lotes. Los detalles de cada lote se pueden proporcionar aquí. Los artículos, documentos y otras características pueden hacer referencia al lote que están relacionados con el uso de relatedLot. Cuando no se indique ningún identificador relacionado, los valores deben interpretarse como aplicables a toda la licitación. +
+
+
+
+
+
+
+
+ ¿Cómo establecer
+
+
+
+ + Documentation +
+A lot is a grouping of items within a contracting process that can be bid on or awarded together. This extension adds the concept of a lot to OCDS.
+Guidance
+If a contracting process is divided into lots, then you should add each lot to the tender.lots array.
If a contracting process is not divided into lots, then you should nonetheless add a single, virtual lot. If a data element can be mapped to either a tender field or a tender.lots field, you should map it to the tender.lots field. In this way, information is accessible at the same location for all contracting processes, regardless of whether the process is actually divided into lots.
Modelling
+La extensión de lotes mantiene la estructura general de una entrega de OCDS, con artículos, documentos e hitos incluidos inmediatamente dentro de los elementos tender, award y contract, pero introduce una lista de lotes en la sección tender, y la capacidad de hacer referencia cruzada a un relatedLot específico para cada elemento, y una lista de relatedLots para documentos, hitos y adjudicaciones
La sección opcional lotDetails y lotGroups permite que se expresen condiciones más complejas en torno a la adjudicación de lotes, como el valor máximo de un grupo de lotes.
Esto significa que los sistemas que no conocen la 'existencia de lotes' de igual forma pueden entender el valor global de la contratación que se esta llevando a cabo, los acontecimientos clave y las relaciones entre los compradores y los proveedores. Al mismo tiempo, los sistemas que sí conocen de la 'existencia de lotes' pueden hacer uso de la información referenciada para presentar una visión centrada-en-lotes en la información a los usuarios, o para analizar la contratación lote por lote.
+Lote Relacionado
+El campo relatedLot (singular) está disponible para:
-
+
- items +
Se puede proporcionar una lista de relatedLots (plural) para cada uno de los siguientes:
-
+
- documents +
- milestones +
- awards +
En otras extensiones, los siguientes objetos también pueden declararse lotes relacionados:
+-
+
- bids submitted by tenderers, in the bid extension +
- las fuentes de finanzas (
Finance), en la extensión finanzas
+
Cuando se usan lotes, todos los elementos deben tener un campo relatedLot.
Los documentos e hitos pueden tener una propiedad relatedLots. Aquellos sin esta propiedad deben interpretarse como aplicables a la licitación en su conjunto.
Los artículos dentro de una adjudicación deben tener un campo relatedLot. Los publicadores pueden también hacer referencia a todos los lotes a los que se relaciona una adjudicación utilizando relatedLots.
¿Cómo establecer tender.status si los estados de los lotes son diferentes?
+tender.status y tender.lots.status utilizan la lista de códigos cerada tenderStatus.csv. Esta lista de códigos avanza desde los estados de planeación ('planning', 'planned'), a estado activo 'active', y luego los estados de los resultados completo, cancelado, no exitoso ('complete', 'cancelled', 'unsuccessful').
-
+
- Si cualquiera de los estados del lote esta 'activo', entonces
tender.statusdebe ser 'activo', para indicar que algunos lotes están esperando resultados.
+ - Si todos los estados del lote se encuentran en estado de resultados, entonces
tender.statusdescribe el resultado agregado: +-
+
- Si al menos uno de los estados del lote esta 'completo', entonces
tender.statusdebe mostrar 'completo', para indicar que hay al menos una adjudicación.
+ - Si no es así, y al menos uno de los estados del lote es 'fallido', el
tender.statusdebe ser 'fallido' para indicar que el procedimiento se completo pero no exitosamente.
+ - De otra manera, si todos los estados del lote están 'cancelados', entonces
tender.statusdeben de estar 'cancelados', para indicar que el procedimiento se descontinuo en su totalidad.
+
+ - Si al menos uno de los estados del lote esta 'completo', entonces
Examples
+Se emite una licitación para consultoría en el desarrollo de un nuevo edificio público. Esto podría incluir elementos para:
+-
+
- Diseño arquitectónico +
- Servicios de asesoramiento arquitectónico +
- Consultoría de ingeniería civil +
- Consultoría en ingeniería estructural +
Aunque forma parte de la misma oferta, el comprador está dispuesto a adjudicar estos diferentes artículos a diferentes empresas, y así divide la oferta en tres lotes.
+{
+ "tender": {
+ "items": [
+ {
+ "id": "0001",
+ "description": "Architectural advice",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71210000",
+ "description": "Advisory architectural services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0002",
+ "description": "Architectural design",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71220000",
+ "description": "Architectural design services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0003",
+ "description": "Civil engineering consultant",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71311000",
+ "description": "Civil engineering consultancy services"
+ },
+ "relatedLot": "lot-2"
+ },
+ {
+ "id": "0004",
+ "description": "Structural engineering services",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71312000",
+ "description": "Structural engineering consultancy services"
+ },
+ "relatedLot": "lot-3"
+ }
+ ],
+ "value": {
+ "amount": 1200000,
+ "currency": "GBP"
+ },
+ "lots": [
+ {
+ "id": "lot-1",
+ "identifiers": [
+ {
+ "id": "PROC/2020/0024-ABC-FGHI-1",
+ "scheme": "internal"
+ }
+ ],
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ },
+ "tenderPeriod": {
+ "endDate": "2020-07-30T23:59:59+01:00"
+ },
+ "submissionMethodDetails": "https://www.acme.com/tender-submission/. All missing tenderer-related documents can be submitted later. Economic operators who ...",
+ "enquiryPeriod": {
+ "endDate": "2020-07-15T23:59:59+01:00"
+ },
+ "contractPeriod": {
+ "startDate": "2020-10-10T00:00:00Z",
+ "endDate": "2021-11-10T00:00:00Z"
+ },
+ "mainProcurementCategory": "services",
+ "additionalProcurementCategories": [
+ "consultingServices"
+ ],
+ "additionalClassifications": [
+ {
+ "id": "serv-a",
+ "scheme": "internal",
+ "description": "Services (Architectural)"
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2020-10-10T00:00:00Z"
+ }
+ ]
+ },
+ {
+ "id": "lot-2",
+ "identifiers": [
+ {
+ "id": "PROC/2020/0024-ABC-FGHI-2",
+ "scheme": "internal"
+ }
+ ],
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ },
+ "mainProcurementCategory": "services",
+ "additionalProcurementCategories": [
+ "consultingServices"
+ ],
+ "tenderPeriod": {
+ "endDate": "2020-07-30T23:59:59+01:00"
+ },
+ "submissionMethodDetails": "https://www.acme.com/tender-submission/. All missing tenderer-related documents can be submitted later. Economic operators who ...",
+ "enquiryPeriod": {
+ "endDate": "2020-07-15T23:59:59+01:00"
+ },
+ "contractPeriod": {
+ "startDate": "2020-12-10T00:00:00Z",
+ "endDate": "2021-12-10T00:00:00Z"
+ },
+ "additionalClassifications": [
+ {
+ "id": "serv-ce",
+ "scheme": "internal",
+ "description": "Services (Civil engineering)"
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2020-12-10T00:00:00Z"
+ }
+ ]
+ },
+ {
+ "id": "lot-3",
+ "identifiers": [
+ {
+ "id": "PROC/2020/0024-ABC-FGHI-3",
+ "scheme": "internal"
+ }
+ ],
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ },
+ "tenderPeriod": {
+ "endDate": "2020-07-30T23:59:59+01:00"
+ },
+ "submissionMethodDetails": "https://www.acme.com/tender-submission/. All missing tenderer-related documents can be submitted later. Economic operators who ...",
+ "enquiryPeriod": {
+ "endDate": "2020-07-15T23:59:59+01:00"
+ },
+ "contractPeriod": {
+ "startDate": "2021-02-10T00:00:00Z",
+ "endDate": "2022-02-10T00:00:00Z"
+ },
+ "mainProcurementCategory": "services",
+ "additionalProcurementCategories": [
+ "consultingServices"
+ ],
+ "additionalClassifications": [
+ {
+ "id": "serv-se",
+ "scheme": "internal",
+ "description": "Services (Structural engineering)"
+ }
+ ],
+ "milestones": [
+ {
+ "id": "1",
+ "type": "securityClearanceDeadline",
+ "dueDate": "2021-02-10T00:00:00Z"
+ }
+ ]
+ }
+ ],
+ "lotGroups": [
+ {
+ "id": "lot-group-1",
+ "title": "Civil and structural engineering services",
+ "description": "Civil and structural engineering services for the development of a new public building",
+ "identifiers": [
+ {
+ "id": "PROC/2020/0024-ABC-FGHI-G1",
+ "scheme": "internal"
+ }
+ ],
+ "relatedLots": [
+ "lot-2",
+ "lot-3"
+ ],
+ "optionToCombine": true,
+ "maximumValue": {
+ "currency": "GBP",
+ "amount": 1000000
+ }
+ }
+ ],
+ "lotDetails": {
+ "maximumLotsBidPerSupplier": 4,
+ "maximumLotsAwardedPerSupplier": 2,
+ "awardCriteriaDetails": "Percentage of people aggregated nationwide contestants undertake to cover, as indicated in their Economic Bids. The evaluation of proposals will be conducted based on the provisions of Article Y of the law on public private partnerships, and the provisions of the tender rules, performing in a first stage an evaluation of the technical bids and subsequently an assessment of the financial offer of the participants."
+ },
+ "amendments": [
+ {
+ "id": "1",
+ "relatedLots": [
+ "lot-1"
+ ],
+ "description": "Submission deadline extended."
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+Unreleased
+-
+
- Add fields:
+
-
+
Amendment.relatedLots
+Lot.additionalClassifications
+Lot.buyer
+Lot.enquiryPeriod
+Lot.tenderPeriod
+Lot.identifiers
+Lot.mainProcurementCategory
+Lot.additionalProcurementCategories
+Lot.milestones
+Lot.minValue
+Lot.submissionMethodDetails
+LotGroup.identifiers
+LotGroup.title
+LotGroup.description
+RelatedProcess.relatedLots
+
+ - Make
Lot.idandLotGroup.idrequired so that lots and lot groups are merged by identifier
+ - Move
Bid.relatedLotsto the Bid statistics and details extension
+ - Move
Finance.relatedLotsto the Finance extension
+ - Update field descriptions to use a neutral voice +
- Add usage guidance +
v1.1.5
+-
+
- Añadir el campo
tender.lotDetails.awardCriteriaDetails.
+ - Añadir el campo
Finance.relatedLots.
+ - Añadir el campo
Lot.contractPeriod.
+ - Quitar la información sobre el tipo de las descripciones de los campos +
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- No permitir que
Tender.lotDetailssea nulo (error introducido en la primera versión)
+ Tender.lotDetailsya no usa$refpara una definición deLotDetails
+- Quitar las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que los campos
relatedLotstengan null en sus listas de cadenas
+ - Agregar enum a
Lot.status
+ - Permitir que los campos
relatedLotssean null
+ - Agregar título y descripción a
Tender.lotDetails
+ - Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/lots/v1.1.4/README.md b/es/extensions/lots/v1.1.4/README.md
new file mode 100644
index 000000000..1fa23df55
--- /dev/null
+++ b/es/extensions/lots/v1.1.4/README.md
@@ -0,0 +1,165 @@
+# Lotes
+
+Cuando se desglosa una sola licitación en partes que pueden ofertarse y se adjudican separadamente, esto se presenta utilizando la **extensión de lotes**.
+
+La extensión de lotes mantiene la estructura general de una entrega de OCDS, con artículos, documentos e hitos incluidos inmediatamente dentro de los elementos `tender`, `award` y `contract`, pero introduce una lista de lotes en la sección `tender`, y la capacidad de hacer referencia cruzada a un `relatedLot` específico para cada elemento, y una lista de `relatedLots` para documentos, hitos y adjudicaciones
+
+La sección opcional `lotDetails` y `lotGroups` permite que se expresen condiciones más complejas en torno a la adjudicación de lotes, como el valor máximo de un grupo de lotes.
+
+Esto significa que los sistemas que no conocen la 'existencia de lotes' de igual forma pueden entender el valor global de la contratación que se esta llevando a cabo, los acontecimientos clave y las relaciones entre los compradores y los proveedores. Al mismo tiempo, los sistemas que sí conocen de la 'existencia de lotes' pueden hacer uso de la información referenciada para presentar una visión centrada-en-lotes en la información a los usuarios, o para analizar la contratación lote por lote.
+
+## Lote Relacionado
+
+La propiedad `relatedLot` (singular) está disponible para:
+
+- items
+
+Se puede proporcionar una lista de `relatedLots` (plural) para cada uno de los siguientes:
+
+- documents
+- milestones
+- awards
+
+Cuando se usan lotes, **todos los elementos** deben tener una propiedad `relatedLot`.
+
+Los documentos e hitos pueden tener opcionalmente una propiedad `relatedLots`. Aquellos sin esta propiedad deben interpretarse como aplicables a la licitación en su conjunto.
+
+Los artículos dentro de una adjudicación deben tener cada uno una propiedad `relatedLot`, pero los publicadores pueden también hacer referencia a todos los lotes en los que se relaciona una adjudicación en el nivel de adjudicación usando `relatedLots`
+
+Cuando la extensión de ofertas también está en uso, cada oferta también puede declarar sus lotes relacionados.
+
+## Ejemplo desarrollado
+
+Se emite una licitación para consultoría en el desarrollo de un nuevo edificio público. Esto podría incluir elementos para:
+
+- Diseño arquitectónico
+- Servicios de asesoramiento arquitectónico
+- Consultoría de ingeniería civil
+- Consultoría en ingeniería estructural
+
+Aunque forma parte de la misma oferta, el comprador está dispuesto a adjudicar estos diferentes artículos a diferentes empresas, y así divide la oferta en tres lotes.
+
+```json
+{
+ "tender": {
+ "items": [
+ {
+ "id": "0001",
+ "description": "Architectural advice",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71210000",
+ "description": "Advisory architectural services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0002",
+ "description": "Architectural design",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71220000",
+ "description": "Architectural design services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0003",
+ "description": "Civil engineering consultant",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71311000",
+ "description": "Civil engineering consultancy services"
+ },
+ "relatedLot": "lot-2"
+ },
+ {
+ "id": "0004",
+ "description": "Structural engineering services",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71312000",
+ "description": "Structural engineering consultancy services"
+ },
+ "relatedLot": "lot-3"
+ }
+ ],
+ "value": {
+ "amount": 1200000,
+ "currency": "GBP"
+ },
+ "lots": [
+ {
+ "id": "lot-1",
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ }
+ },
+ {
+ "id": "lot-2",
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ }
+ },
+ {
+ "id": "lot-3",
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ }
+ }
+ ],
+ "lotGroups": [
+ {
+ "id": "lot-group-1",
+ "relatedLots": [
+ "lot-2",
+ "lot-3"
+ ],
+ "optionToCombine": true,
+ "maximumValue": {
+ "currency": "GBP",
+ "amount": 1000000
+ }
+ }
+ ],
+ "lotDetails": {
+ "maximumLotsBidPerSupplier": 4,
+ "maximumLotsAwardedPerSupplier": 2
+ }
+ }
+}
+```
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.4
+
+- No permitir que `Tender.lotDetails` sea nulo (error introducido en la primera versión)
+- `Tender.lotDetails` ya no usa `$ref` para una definición de `LotDetails`
+- Quita las directrices Sphinx del readme
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- No permitir que los campos `relatedLots` tengan null en sus listas de cadenas
+- Agregar enum a `Lot.status`
+- Permitir que los campos `relatedLots` sean null
+- Agregar título y descripción a `Tender.lotDetails`
+- Usa la licencia Apache 2.0
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/lots/v1.1.4/extension.json b/es/extensions/lots/v1.1.4/extension.json
new file mode 100644
index 000000000..bb80f5ee0
--- /dev/null
+++ b/es/extensions/lots/v1.1.4/extension.json
@@ -0,0 +1,22 @@
+{
+ "name": {
+ "en": "Lots",
+ "es": "Lotes"
+ },
+ "description": {
+ "en": "A tender process may be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features can then reference the lot they are related to using relatedLot. Where no relatedLot identifier is given, the values should be interpreted as applicable to the whole tender.",
+ "es": "Un proceso de licitaci\u00f3n se puede dividir en lotes, donde los licitadores pueden ofertar en uno o m\u00e1s lotes. Los detalles de cada lote se pueden proporcionar aqu\u00ed. Los art\u00edculos, documentos y otras caracter\u00edsticas pueden hacer referencia al lote que est\u00e1n relacionados con el uso de relatedLot. Cuando no se indique ning\u00fan identificador relacionado, los valores deben interpretarse como aplicables a toda la licitaci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/lots/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"
+ ]
+}
diff --git a/es/extensions/lots/v1.1.4/index.html b/es/extensions/lots/v1.1.4/index.html
new file mode 100644
index 000000000..e31c72d83
--- /dev/null
+++ b/es/extensions/lots/v1.1.4/index.html
@@ -0,0 +1,439 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lotes +
+ ++ Un proceso de licitación se puede dividir en lotes, donde los licitadores pueden ofertar en uno o más lotes. Los detalles de cada lote se pueden proporcionar aquí. Los artículos, documentos y otras características pueden hacer referencia al lote que están relacionados con el uso de relatedLot. Cuando no se indique ningún identificador relacionado, los valores deben interpretarse como aplicables a toda la licitación. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ lots
+
+ |
+ + Lotes + | +
+ Un proceso de licitación puede dividirse en lotes, en los que los licitadores pueden pujar por uno o varios lotes. Los detalles de cada lote se pueden proporcionar aquí. Los artículos, documentos y otras características pueden entonces hacer referencia al lote con el que están relacionados utilizando relatedLot. Si no se indica un identificador de relatedLots, los valores deben interpretarse como aplicables a toda la licitación. Los detalles sobre toda la licitación pueden anularse para un lote determinado mediante su inclusión en el objeto lote. + + |
+ + array of Lot objects + | +
+
+ lotDetails
+
+ |
+ + Detalles del lote + | +
+ Details of any criteria that apply to bidding on the lots in this tender. + + |
+ + object + | +
+
+ lotDetails.
+ |
+ + Lotes máximos por proveedor + | +
+ El número máximo de lotes por los que un proveedor puede ofertar como parte de este proceso de contratación. + + |
+ + integer + | +
+
+ lotDetails.
+ |
+ + Lotes máximos por proveedor + | +
+ El número máximo de lotes que pueden adjudicarse a un proveedor como parte de este proceso de contratación. + + |
+ + integer + | +
+
+ lotDetails.
+ |
+ + Detalles de criterios de adjudicación + | +
+ Cualquier información detallada o adicional sobre la adjudicación o los criterios de selección. + + |
+ + string + | +
+
+ lotGroups
+
+ |
+ + Grupos de lote + | +
+ Cuando el comprador se reserva el derecho de combinar lotes, o desea especificar el valor total para un grupo de lotes, se utiliza un grupo de lotes para capturar esta información. + + |
+ + array of LotGroup objects + | +
+ Document +
+ +
+ The extension defines these fields in the Document object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lote(s) relacionado(s) + | +
+ The identifiers of the lots to which this document relates. + + |
+ + array of strings + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLot
+
+ |
+ + Lote relacionado + | +
+ The identifier of the lot to which this item relates. + + |
+ + string + | +
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lote(s) relacionado(s) + | +
+ The identifiers of the lots to which this milestone relates. + + |
+ + array of strings + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lote(s) relacionado(s) + | +
+ The identifiers of the lots to which this award relates. + + |
+ + array of strings + | +
+ Amendment +
+ +
+ The extension defines these fields in the Amendment object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lote(s) relacionado(s) + | +
+ The identifiers of the lots to which this amendment relates. + + |
+ + array of strings + | +
+ RelatedProcess +
+ +
+ The extension defines these fields in the RelatedProcess object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lote(s) relacionado(s) + | +
+ The identifiers of the lots to which this related process relates. + + |
+ + array of strings + | +
+ Lot +
+ +
+ The extension defines a new Lot object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID Lote + | +
+ Un identificador local para este lote, tal como un número de lote. Esto se utiliza en las referencias relatedLots en el nivel de artículo, documento y adjudicación. + + |
+ + string + | +
+
+ identifiers
+
+ |
+ + Identifiers + | +
+ Identifiers for this lot. This field can be used to provide internal identifiers for the lot, such as identifiers from a buyer's document management system or procurement system. + + |
+ + array of SimpleIdentifier objects + | +
+
+ title
+
+ |
+ + Título + | +
+ Un título para este lote. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Una descripción de este lote. + + |
+ + string + | +
+
+ status
+
+ |
+ + Estatus de lote + | +
+ El estado actual del proceso relacionado a este lote. + + |
+ + string from closed tenderStatus codelist + | +
+
+ value
+
+ |
+ + Valor del lote + | +
+ El valor máximo estimado de este lote. + + |
+ + Value object + | +
+
+ minValue
+
+ |
+ + Minimum value + | +
+ The estimated minimum value of the lot. A negative value indicates that the contracting process may involve payments from the supplier to the buyer (commonly used in concession contracts). + + |
+ + Value object + | +
+
+ tenderPeriod
+
+ |
+ + Tender period + | +
+ The period when this lot is open for submissions. The end date is the closing date for bid submissions. + + |
+ + Period object + | +
+
+ contractPeriod
+
+ |
+ + Período del contrato + | +
+ El período sobre el cual se estima o especifica que el contrato estará activo. Si el lote no especifica fechas explícitas, se puede usar el campo |
+ + Period object + | +
+
+ buyer
+
+ |
+ + Buyer + | +
+ The organization aiming to conclude a contract with a supplier or to use the goods, works or services in this lot. This may be different from the procuring entity who may be specified in the tender data. + + |
+ + OrganizationReference object + | +
+
+ additionalClassifications
+
+ |
+ + Additional classifications + | +
+ Additional classifications for this lot. + + |
+ + array of Classification objects + | +
+
+ mainProcurementCategory
+
+ |
+ + Main procurement category + | +
+ The primary category describing the main object of this lot, using the closed procurementCategory codelist. + + |
+ + string from closed procurementCategory codelist + | +
+
+ additionalProcurementCategories
+
+ |
+ + Additional procurement categories + | +
+ Any additional categories describing the objects of this lot, using the open extendedProcurementCategory codelist. + + |
+ + array of strings from open extendedProcurementCategory codelist + | +
+
+ enquiryPeriod
+
+ |
+ + Enquiry period + | +
+ The period during which potential bidders may submit questions and requests for clarification about this lot to the buyer or the procuring entity. + + |
+ + Period object + | +
+
+ milestones
+
+ |
+ + Milestones + | +
+ Milestones associated with this lot. + + |
+ + array of Milestone objects + | +
+
+ submissionMethodDetails
+
+ |
+ + Submission method details + | +
+ Information about the methods by which bids are submitted for this lot. This can include the address, e-mail address or online service to which bids are submitted, and any special requirements to be followed for submissions. More structured information can be provided using the submission terms extension. + + |
+ + string + | +
+ LotGroup +
+ +
+ The extension defines a new LotGroup object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador del grupo de lote + | +
+ Un identificador local para este grupo de lotes. + + |
+ + string + | +
+
+ identifiers
+
+ |
+ + Identifiers + | +
+ Identifiers for this lot group. This field can be used to provide internal identifiers for the lot group, such as identifiers from a buyer's document management system or procurement system. + + |
+ + array of SimpleIdentifier objects + | +
+
+ title
+
+ |
+ + Título + | +
+ A title for this lot group. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ A description of this lot group. + + |
+ + string + | +
+
+ relatedLots
+
+ |
+ + Lote(s) relacionado(s) + | +
+ Una lista de los identificadores de los lotes que forman este grupo. Los lotes pueden aparecer en más de un grupo. + + |
+ + array of strings + | +
+
+ optionToCombine
+
+ |
+ + Opción de combinar + | +
+ El comprador se reserva el derecho de combinar los lotes de este grupo al adjudicar un contrato. + + |
+ + boolean + | +
+
+ maximumValue
+
+ |
+ + Valor máximo + | +
+ El valor máximo estimado de los lotes de este grupo. Este puede ser inferior a la suma total de los valores de los lotes. + + |
+ + Value object + | +
+ SimpleIdentifier +
+ +
+ The extension defines a new SimpleIdentifier object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ scheme
+
+ |
+ + Scheme + | +
+ The list, register or system from which the identifier is taken. + + |
+ + string + | +
+
+ id
+
+ |
+ + ID + | +
+ The identifier taken from the scheme. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/lots/v1.1.4/release-schema.json b/es/extensions/lots/v1.1.4/release-schema.json
new file mode 100644
index 000000000..d9742ffd2
--- /dev/null
+++ b/es/extensions/lots/v1.1.4/release-schema.json
@@ -0,0 +1,218 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "lots": {
+ "title": "Lotes",
+ "description": "Un proceso de licitaci\u00f3n se puede dividir en lotes, donde los licitadores pueden ofertar en uno o m\u00e1s lotes. Los detalles de cada lote se pueden proporcionar aqu\u00ed. Los art\u00edculos, documentos y otras caracter\u00edsticas pueden hacer referencia a la porci\u00f3n que est\u00e1n relacionados con el uso de relatedLot. Cuando no se indique ning\u00fan identificador relacionado, los valores deben interpretarse como aplicables a toda la licitaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Lot"
+ }
+ },
+ "lotDetails": {
+ "title": "Detalles del lote",
+ "description": "Si esta oferta esta dividida en lotes, los detalles se pueden poner aqu\u00ed para cualquier criterio que aplique para hacer una oferta en estos lotes. Esta propiedad extendida actualmente se enfoca en los campos requeridos por el est\u00e1ndar de datos EU TED.",
+ "type": "object",
+ "properties": {
+ "maximumLotsBidPerSupplier": {
+ "title": "Lotes m\u00e1ximos por proveedor",
+ "description": "El n\u00famero m\u00e1ximo de lotes por los que un proveedor puede ofertar como parte de este proceso de contrataci\u00f3n.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "maximumLotsAwardedPerSupplier": {
+ "title": "Lotes m\u00e1ximos por proveedor",
+ "description": "El n\u00famero m\u00e1ximo de lotes que pueden adjudicarse a un proveedor como parte de este proceso de contrataci\u00f3n.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ }
+ }
+ },
+ "lotGroups": {
+ "title": "Grupos de lote",
+ "description": "Cuando el comprador se reserva el derecho de combinar lotes, o desea especificar el valor total para un grupo de lotes, se utiliza un grupo de lotes para capturar esta informaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/LotGroup"
+ }
+ }
+ }
+ },
+ "Document": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lotes relacionados",
+ "description": "Si este documento se refiere a un lote en particular, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aqu\u00ed.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "relatedLot": {
+ "title": "Lote relacionado",
+ "description": "Si este art\u00edculo pertenece a un lote, proporcione el identificador del lote relacionado aqu\u00ed. Cada art\u00edculo puede pertenecer solamente a un solo lote.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Milestone": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lotes relacionados",
+ "description": "Si este documento se refiere a un lote en particular, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aqu\u00ed.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lotes relacionados",
+ "description": "Si esta adjudicaci\u00f3n se relaciona con uno o m\u00e1s lotes espec\u00edficos, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aqu\u00ed.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Bid": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lotes relacionados",
+ "description": "Si esta oferta se relaciona con uno o m\u00e1s lotes espec\u00edficos, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aqu\u00ed.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Lot": {
+ "title": "Lotes",
+ "description": "Un lote es una agrupaci\u00f3n de art\u00edculos en una licitaci\u00f3n que se pueden ofertar o adjudicar juntos.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "ID Lote",
+ "type": "string",
+ "description": "Un identificador local para este lote, tal como un n\u00famero de lote. Esto se utiliza en las referencias relatedLots en el nivel de art\u00edculo, documento y adjudicaci\u00f3n."
+ },
+ "title": {
+ "title": "T\u00edtulo",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "Un t\u00edtulo para este lote."
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una descripci\u00f3n de este lote.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "title": "Estatus de lote",
+ "description": "El estatus actual del proceso relacionado a este lote se puede encontrar en [tenderStatus codelist](http://standard.open-contracting.org/1.1/en/schema/codelists/#tender-status)",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "tenderStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "planning",
+ "planned",
+ "active",
+ "cancelled",
+ "unsuccessful",
+ "complete",
+ "withdrawn",
+ null
+ ]
+ },
+ "value": {
+ "title": "Valor del lote",
+ "$ref": "#/definitions/Value",
+ "description": "El valor m\u00e1ximo estimado de este lote."
+ }
+ }
+ },
+ "LotGroup": {
+ "title": "Grupo del lote",
+ "description": "Cuando el comprador se reserva el derecho de combinar lotes, o desea especificar el valor total para un grupo de lotes, se utiliza un grupo de lotes para capturar esta informaci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Identificador del grupo de lote",
+ "type": "string",
+ "description": "Un identificador local para este grupo de lotes."
+ },
+ "relatedLots": {
+ "title": "Lotes relacionados",
+ "description": "Una lista de los identificadores de los lotes que forman este grupo. Los lotes pueden aparecer en m\u00e1s de un grupo.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ },
+ "optionToCombine": {
+ "title": "Opci\u00f3n de combinar",
+ "description": "El comprador se reserva el derecho de combinar los lotes de este grupo al adjudicar un contrato.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "maximumValue": {
+ "title": "Valor m\u00e1ximo",
+ "description": "El valor m\u00e1ximo estimado de los lotes de este grupo. Este puede ser inferior a la suma total de los valores del lote",
+ "$ref": "#/definitions/Value"
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/lots/v1.1.4/schema/index.html b/es/extensions/lots/v1.1.4/schema/index.html
new file mode 100644
index 000000000..c0d49406b
--- /dev/null
+++ b/es/extensions/lots/v1.1.4/schema/index.html
@@ -0,0 +1,787 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lotes +
+ ++ Un proceso de licitación se puede dividir en lotes, donde los licitadores pueden ofertar en uno o más lotes. Los detalles de cada lote se pueden proporcionar aquí. Los artículos, documentos y otras características pueden hacer referencia al lote que están relacionados con el uso de relatedLot. Cuando no se indique ningún identificador relacionado, los valores deben interpretarse como aplicables a toda la licitación. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Cuando se desglosa una sola licitación en partes que pueden ofertarse y se adjudican separadamente, esto se presenta utilizando la extensión de lotes.
+La extensión de lotes mantiene la estructura general de una entrega de OCDS, con artículos, documentos e hitos incluidos inmediatamente dentro de los elementos tender, award y contract, pero introduce una lista de lotes en la sección tender, y la capacidad de hacer referencia cruzada a un relatedLot específico para cada elemento, y una lista de relatedLots para documentos, hitos y adjudicaciones
La sección opcional lotDetails y lotGroups permite que se expresen condiciones más complejas en torno a la adjudicación de lotes, como el valor máximo de un grupo de lotes.
Esto significa que los sistemas que no conocen la 'existencia de lotes' de igual forma pueden entender el valor global de la contratación que se esta llevando a cabo, los acontecimientos clave y las relaciones entre los compradores y los proveedores. Al mismo tiempo, los sistemas que sí conocen de la 'existencia de lotes' pueden hacer uso de la información referenciada para presentar una visión centrada-en-lotes en la información a los usuarios, o para analizar la contratación lote por lote.
+Lote Relacionado
+La propiedad relatedLot (singular) está disponible para:
-
+
- items +
Se puede proporcionar una lista de relatedLots (plural) para cada uno de los siguientes:
-
+
- documents +
- milestones +
- awards +
Cuando se usan lotes, todos los elementos deben tener una propiedad relatedLot.
Los documentos e hitos pueden tener opcionalmente una propiedad relatedLots. Aquellos sin esta propiedad deben interpretarse como aplicables a la licitación en su conjunto.
Los artículos dentro de una adjudicación deben tener cada uno una propiedad relatedLot, pero los publicadores pueden también hacer referencia a todos los lotes en los que se relaciona una adjudicación en el nivel de adjudicación usando relatedLots
Cuando la extensión de ofertas también está en uso, cada oferta también puede declarar sus lotes relacionados.
+Ejemplo desarrollado
+Se emite una licitación para consultoría en el desarrollo de un nuevo edificio público. Esto podría incluir elementos para:
+-
+
- Diseño arquitectónico +
- Servicios de asesoramiento arquitectónico +
- Consultoría de ingeniería civil +
- Consultoría en ingeniería estructural +
Aunque forma parte de la misma oferta, el comprador está dispuesto a adjudicar estos diferentes artículos a diferentes empresas, y así divide la oferta en tres lotes.
+{
+ "tender": {
+ "items": [
+ {
+ "id": "0001",
+ "description": "Architectural advice",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71210000",
+ "description": "Advisory architectural services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0002",
+ "description": "Architectural design",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71220000",
+ "description": "Architectural design services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0003",
+ "description": "Civil engineering consultant",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71311000",
+ "description": "Civil engineering consultancy services"
+ },
+ "relatedLot": "lot-2"
+ },
+ {
+ "id": "0004",
+ "description": "Structural engineering services",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71312000",
+ "description": "Structural engineering consultancy services"
+ },
+ "relatedLot": "lot-3"
+ }
+ ],
+ "value": {
+ "amount": 1200000,
+ "currency": "GBP"
+ },
+ "lots": [
+ {
+ "id": "lot-1",
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ }
+ },
+ {
+ "id": "lot-2",
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ }
+ },
+ {
+ "id": "lot-3",
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ }
+ }
+ ],
+ "lotGroups": [
+ {
+ "id": "lot-group-1",
+ "relatedLots": [
+ "lot-2",
+ "lot-3"
+ ],
+ "optionToCombine": true,
+ "maximumValue": {
+ "currency": "GBP",
+ "amount": 1000000
+ }
+ }
+ ],
+ "lotDetails": {
+ "maximumLotsBidPerSupplier": 4,
+ "maximumLotsAwardedPerSupplier": 2
+ }
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.4
+-
+
- No permitir que
Tender.lotDetailssea nulo (error introducido en la primera versión)
+ Tender.lotDetailsya no usa$refpara una definición deLotDetails
+- Quita las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que los campos
relatedLotstengan null en sus listas de cadenas
+ - Agregar enum a
Lot.status
+ - Permitir que los campos
relatedLotssean null
+ - Agregar título y descripción a
Tender.lotDetails
+ - Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/lots/v1.1.5/README.md b/es/extensions/lots/v1.1.5/README.md
new file mode 100644
index 000000000..ef2fd7b8e
--- /dev/null
+++ b/es/extensions/lots/v1.1.5/README.md
@@ -0,0 +1,199 @@
+# Lotes
+
+Cuando se desglosa una sola licitación en partes que pueden ofertarse y se adjudican separadamente, esto se presenta utilizando la **extensión de lotes**.
+
+La extensión de lotes mantiene la estructura general de una entrega de OCDS, con artículos, documentos e hitos incluidos inmediatamente dentro de los elementos `tender`, `award` y `contract`, pero introduce una lista de lotes en la sección `tender`, y la capacidad de hacer referencia cruzada a un `relatedLot` específico para cada elemento, y una lista de `relatedLots` para documentos, hitos y adjudicaciones
+
+La sección opcional `lotDetails` y `lotGroups` permite que se expresen condiciones más complejas en torno a la adjudicación de lotes, como el valor máximo de un grupo de lotes.
+
+Esto significa que los sistemas que no conocen la 'existencia de lotes' de igual forma pueden entender el valor global de la contratación que se esta llevando a cabo, los acontecimientos clave y las relaciones entre los compradores y los proveedores. Al mismo tiempo, los sistemas que sí conocen de la 'existencia de lotes' pueden hacer uso de la información referenciada para presentar una visión centrada-en-lotes en la información a los usuarios, o para analizar la contratación lote por lote.
+
+## Lote Relacionado
+
+La propiedad `relatedLot` (singular) está disponible para:
+
+- items
+
+Se puede proporcionar una lista de `relatedLots` (plural) para cada uno de los siguientes:
+
+- documents
+- milestones
+- awards
+
+En otras extensiones, los siguientes objetos también pueden declararse lotes relacionados:
+
+- las ofertas presentadas por licitantes (`Bid`), en la [extensión ofertas](https://github.com/open-contracting-extensions/ocds_bid_extension)
+- las fuentes de finanzas (`Finance`), in the [extensión finanzas](https://github.com/open-contracting-extensions/ocds_finance_extension)
+
+Cuando se usan lotes, **todos** los elementos deben tener un campo `relatedLot`.
+
+Los documentos e hitos pueden tener una propiedad `relatedLots`. Aquellos sin esta propiedad deben interpretarse como aplicables a la licitación en su conjunto.
+
+Los artículos dentro de una adjudicación deben tener un campo `relatedLot`. Los publicadores pueden también hacer referencia a todos los lotes a los que se relaciona una adjudicación utilizando `relatedLots`.
+
+## ¿Cómo establecer `tender.status` si los estados de los lotes son diferentes?
+
+`tender.status` y `Lot.status` usan la lista de código cerrada tenderStatus.csv. La lista de código avanza desde el estado de planeación ('planning', 'planned'), al estado 'activo', y finalmente el estado de los resultados ('complete', 'cancelled', 'unsuccessful').
+
+- Si cualquiera de los estados del lote esta 'activo', entonces `tender.status` debe ser 'activo', para indicar que algunos lotes están esperando resultados.
+- Si todos los estados del lote se encuentran en estado de resultados, entonces `tender.status` describe el resultado agregado:
+ - Si al menos uno de los estados del lote esta 'completo', entonces `tender.status` debe mostrar 'completo', para indicar que hay al menos una adjudicación.
+ - Si no es así, y al menos uno de los estados del lote es 'fallido', el `tender.status` debe ser 'fallido' para indicar que el procedimiento se completo pero no exitosamente.
+ - De otra manera, si todos los estados del lote están 'cancelados', entonces `tender.status` deben de estar 'cancelados', para indicar que el procedimiento se descontinuo en su totalidad.
+
+## Ejemplo
+
+Se emite una licitación para consultoría en el desarrollo de un nuevo edificio público. Esto podría incluir elementos para:
+
+- Diseño arquitectónico
+- Servicios de asesoramiento arquitectónico
+- Consultoría de ingeniería civil
+- Consultoría en ingeniería estructural
+
+Aunque forma parte de la misma oferta, el comprador está dispuesto a adjudicar estos diferentes artículos a diferentes empresas, y así divide la oferta en tres lotes.
+
+```json
+{
+ "tender": {
+ "items": [
+ {
+ "id": "0001",
+ "description": "Architectural advice",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71210000",
+ "description": "Advisory architectural services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0002",
+ "description": "Architectural design",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71220000",
+ "description": "Architectural design services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0003",
+ "description": "Civil engineering consultant",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71311000",
+ "description": "Civil engineering consultancy services"
+ },
+ "relatedLot": "lot-2"
+ },
+ {
+ "id": "0004",
+ "description": "Structural engineering services",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71312000",
+ "description": "Structural engineering consultancy services"
+ },
+ "relatedLot": "lot-3"
+ }
+ ],
+ "value": {
+ "amount": 1200000,
+ "currency": "GBP"
+ },
+ "lots": [
+ {
+ "id": "lot-1",
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ },
+ "contractPeriod": {
+ "startDate": "2020-10-10T00:00:00Z",
+ "endDate": "2021-11-10T00:00:00Z"
+ }
+ },
+ {
+ "id": "lot-2",
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ },
+ "contractPeriod": {
+ "startDate": "2020-12-10T00:00:00Z",
+ "endDate": "2021-12-10T00:00:00Z"
+ }
+ },
+ {
+ "id": "lot-3",
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ },
+ "contractPeriod": {
+ "startDate": "2021-02-10T00:00:00Z",
+ "endDate": "2022-02-10T00:00:00Z"
+ }
+ }
+ ],
+ "lotGroups": [
+ {
+ "id": "lot-group-1",
+ "relatedLots": [
+ "lot-2",
+ "lot-3"
+ ],
+ "optionToCombine": true,
+ "maximumValue": {
+ "currency": "GBP",
+ "amount": 1000000
+ }
+ }
+ ],
+ "lotDetails": {
+ "maximumLotsBidPerSupplier": 4,
+ "maximumLotsAwardedPerSupplier": 2,
+ "awardCriteriaDetails": "Percentage of people aggregated nationwide contestants undertake to cover, as indicated in their Economic Bids. The evaluation of proposals will be conducted based on the provisions of Article Y of the law on public private partnerships, and the provisions of the tender rules, performing in a first stage an evaluation of the technical bids and subsequently an assessment of the financial offer of the participants."
+ }
+ }
+}
+```
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.5
+
+- Añadir el campo `tender.lotDetails.awardCriteriaDetails`.
+- Añadir el campo `Finance.relatedLots`.
+- Añadir el campo `Lot.contractPeriod`.
+- Quitar la información sobre el tipo de las descripciones de los campos
+- Revisar las palabras normativas y no-normativas
+
+### v1.1.4
+
+- No permitir que `Tender.lotDetails` sea null (error introducido en la primera versión)
+- `Tender.lotDetails` ya no usa `$ref` para una definición de `LotDetails`
+- Quita las directrices Sphinx del readme
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- No permitir que los campos `relatedLots` tengan null en sus listas de cadenas
+- Agregar enum a `Lot.status`
+- Permitir que los campos `relatedLots` sean null
+- Agregar título y descripción a `Tender.lotDetails`
+- Usa la licencia Apache 2.0
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/lots/v1.1.5/extension.json b/es/extensions/lots/v1.1.5/extension.json
new file mode 100644
index 000000000..47ce11118
--- /dev/null
+++ b/es/extensions/lots/v1.1.5/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Lots",
+ "es": "Lotes"
+ },
+ "description": {
+ "en": "A tender process can be divided into lots, where bidders can bid on one or more lots. Details of each lot can be provided here. Items, documents and other features may then reference the lot they are related to using relatedLot. Where no relatedLot identifier is given, the values ought to be interpreted as applicable to the whole tender.",
+ "es": "Un proceso de licitaci\u00f3n se puede dividir en lotes, donde los licitadores pueden ofertar en uno o m\u00e1s lotes. Los detalles de cada lote se pueden proporcionar aqu\u00ed. Los art\u00edculos, documentos y otras caracter\u00edsticas pueden hacer referencia al lote que est\u00e1n relacionados con el uso de relatedLot. Cuando no se indique ning\u00fan identificador relacionado, los valores deben interpretarse como aplicables a toda la licitaci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/lots/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json",
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_finance_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/lots/v1.1.5/index.html b/es/extensions/lots/v1.1.5/index.html
new file mode 100644
index 000000000..94cce5a8f
--- /dev/null
+++ b/es/extensions/lots/v1.1.5/index.html
@@ -0,0 +1,486 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lotes +
+ ++ Un proceso de licitación se puede dividir en lotes, donde los licitadores pueden ofertar en uno o más lotes. Los detalles de cada lote se pueden proporcionar aquí. Los artículos, documentos y otras características pueden hacer referencia al lote que están relacionados con el uso de relatedLot. Cuando no se indique ningún identificador relacionado, los valores deben interpretarse como aplicables a toda la licitación. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ lots
+
+ |
+ + Lotes + | +
+ Un proceso de licitación se puede dividir en lotes, donde los licitadores pueden ofertar en uno o más lotes. Los detalles de cada lote se pueden proporcionar aquí. Los artículos, documentos y otras características pueden hacer referencia a la porción que están relacionados con el uso de relatedLot. Cuando no se indique ningún identificador relacionado, los valores deben interpretarse como aplicables a toda la licitación. + + |
+ + array of Lot objects + | +
+
+ lotDetails
+
+ |
+ + Detalles del lote + | +
+ Si esta oferta esta dividida en lotes, los detalles se pueden poner aquí para cualquier criterio que aplique para hacer una oferta en estos lotes. Esta propiedad extendida actualmente se enfoca en los campos requeridos por el estándar de datos EU TED. + + |
+ + object + | +
+
+ lotDetails.
+ |
+ + Lotes máximos por proveedor + | +
+ El número máximo de lotes por los que un proveedor puede ofertar como parte de este proceso de contratación. + + |
+ + integer + | +
+
+ lotDetails.
+ |
+ + Lotes máximos por proveedor + | +
+ El número máximo de lotes que pueden adjudicarse a un proveedor como parte de este proceso de contratación. + + |
+ + integer + | +
+
+ lotGroups
+
+ |
+ + Grupos de lote + | +
+ Cuando el comprador se reserva el derecho de combinar lotes, o desea especificar el valor total para un grupo de lotes, se utiliza un grupo de lotes para capturar esta información. + + |
+ + array of LotGroup objects + | +
+ Document +
+ +
+ The extension defines these fields in the Document object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lotes relacionados + | +
+ Si este documento se refiere a un lote en particular, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aquí. + + |
+ + array of strings + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLot
+
+ |
+ + Lote relacionado + | +
+ Si este artículo pertenece a un lote, proporcione el identificador del lote relacionado aquí. Cada artículo puede pertenecer solamente a un solo lote. + + |
+ + string + | +
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lotes relacionados + | +
+ Si este documento se refiere a un lote en particular, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aquí. + + |
+ + array of strings + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lotes relacionados + | +
+ Si esta adjudicación se relaciona con uno o más lotes específicos, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aquí. + + |
+ + array of strings + | +
+ Bid +
+ +
+ The extension defines these fields in the Bid object from the Estadísticas y detalles de las ofertas extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lotes relacionados + | +
+ + This field is modified from its original version. + +Si esta oferta se relaciona con uno o más lotes específicos, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aquí. + + |
+ + array of strings + | +
+ Lot +
+ +
+ The extension defines a new Lot object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID Lote + | +
+ Un identificador local para este lote, tal como un número de lote. Esto se utiliza en las referencias relatedLots en el nivel de artículo, documento y adjudicación. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título + | +
+ Un título para este lote. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Una descripción de este lote. + + |
+ + string + | +
+
+ status
+
+ |
+ + Estatus de lote + | +
+ El estatus actual del proceso relacionado a este lote se puede encontrar en tenderStatus codelist + + |
+ + string from closed tenderStatus codelist + | +
+
+ value
+
+ |
+ + Valor del lote + | +
+ El valor máximo estimado de este lote. + + |
+ + Value object + | +
+ LotGroup +
+ +
+ The extension defines a new LotGroup object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador del grupo de lote + | +
+ Un identificador local para este grupo de lotes. + + |
+ + string + | +
+
+ relatedLots
+
+ |
+ + Lotes relacionados + | +
+ Una lista de los identificadores de los lotes que forman este grupo. Los lotes pueden aparecer en más de un grupo. + + |
+ + array of strings + | +
+
+ optionToCombine
+
+ |
+ + Opción de combinar + | +
+ El comprador se reserva el derecho de combinar los lotes de este grupo al adjudicar un contrato. + + |
+ + boolean + | +
+
+ maximumValue
+
+ |
+ + Valor máximo + | +
+ El valor máximo estimado de los lotes de este grupo. Este puede ser inferior a la suma total de los valores del lote + + |
+ + Value object + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/lots/v1.1.5/release-schema.json b/es/extensions/lots/v1.1.5/release-schema.json
new file mode 100644
index 000000000..09e314aee
--- /dev/null
+++ b/es/extensions/lots/v1.1.5/release-schema.json
@@ -0,0 +1,248 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "lots": {
+ "title": "Lotes",
+ "description": "Un proceso de licitaci\u00f3n se puede dividir en lotes, donde los licitadores pueden ofertar en uno o m\u00e1s lotes. Los detalles de cada lote se pueden proporcionar aqu\u00ed. Los art\u00edculos, documentos y otras caracter\u00edsticas pueden hacer referencia al lote al que est\u00e1n relacionados con el uso de relatedLot. Cuando no se indique ning\u00fan identificador relacionado, los valores deben interpretarse como aplicables a toda la licitaci\u00f3n. Las propiedades de la licitaci\u00f3n pueden ser sobreescritas para un lote dado a trav\u00e9s de su inclusi\u00f3n en el objeto Lot.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Lot"
+ }
+ },
+ "lotDetails": {
+ "title": "Detalles del lote",
+ "description": "Si esta licitaci\u00f3n est\u00e1 dividida en lotes, aqu\u00ed pueden darse detalles de los criterios que aplican para hacer una oferta en estos lotes.",
+ "type": "object",
+ "properties": {
+ "maximumLotsBidPerSupplier": {
+ "title": "Lotes m\u00e1ximos por proveedor",
+ "description": "El n\u00famero m\u00e1ximo de lotes por los que un proveedor puede ofertar como parte de este proceso de contrataci\u00f3n.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "maximumLotsAwardedPerSupplier": {
+ "title": "Lotes m\u00e1ximos por proveedor",
+ "description": "El n\u00famero m\u00e1ximo de lotes que pueden adjudicarse a un proveedor como parte de este proceso de contrataci\u00f3n.",
+ "type": [
+ "integer",
+ "null"
+ ]
+ },
+ "awardCriteriaDetails": {
+ "title": "Detalles de criterios de adjudicaci\u00f3n",
+ "description": "Cualquier informaci\u00f3n detallada o adicional sobre la adjudicaci\u00f3n o los criterios de selecci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "lotGroups": {
+ "title": "Grupos de lote",
+ "description": "Cuando el comprador se reserva el derecho de combinar lotes, o desea especificar el valor total para un grupo de lotes, se utiliza un grupo de lotes para capturar esta informaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/LotGroup"
+ }
+ }
+ }
+ },
+ "Document": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lotes relacionados",
+ "description": "Si este documento se refiere a un lote en particular, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aqu\u00ed.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Item": {
+ "properties": {
+ "relatedLot": {
+ "title": "Lote relacionado",
+ "description": "Si este art\u00edculo pertenece a un lote, provea el identificador del lote relacionado aqu\u00ed.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Milestone": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lotes relacionados",
+ "description": "Si este documento se refiere a un lote en particular, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aqu\u00ed.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lotes relacionados",
+ "description": "Si esta adjudicaci\u00f3n se relaciona con uno o m\u00e1s lotes espec\u00edficos, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aqu\u00ed.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Bid": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lotes relacionados",
+ "description": "Si esta oferta se relaciona con uno o m\u00e1s lotes espec\u00edficos, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aqu\u00ed.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Finance": {
+ "properties": {
+ "relatedLots": {
+ "title": "Lotes relacionados",
+ "description": "Si esta fuente de financiamiento se relaciona con uno o m\u00e1s lotes espec\u00edficos, provea el/los identificador(es) de los lotes relacionados aqu\u00ed.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ }
+ }
+ },
+ "Lot": {
+ "title": "Lotes",
+ "description": "Un lote es una agrupaci\u00f3n de art\u00edculos en una licitaci\u00f3n que se pueden ofertar o adjudicar juntos.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "ID Lote",
+ "type": "string",
+ "description": "Un identificador local para este lote, tal como un n\u00famero de lote. Esto se utiliza en las referencias relatedLots en el nivel de art\u00edculo, documento y adjudicaci\u00f3n."
+ },
+ "title": {
+ "title": "T\u00edtulo",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "Un t\u00edtulo para este lote."
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una descripci\u00f3n de este lote.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "title": "Estatus de lote",
+ "description": "El estado actual del proceso relacionado a este lote.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "tenderStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "planning",
+ "planned",
+ "active",
+ "cancelled",
+ "unsuccessful",
+ "complete",
+ "withdrawn",
+ null
+ ]
+ },
+ "value": {
+ "title": "Valor del lote",
+ "$ref": "#/definitions/Value",
+ "description": "El valor m\u00e1ximo estimado de este lote."
+ },
+ "contractPeriod": {
+ "title": "Per\u00edodo del contrato",
+ "description": "El per\u00edodo sobre el cual se estima o especifica que el contrato estar\u00e1 activo. Si el lote no especifica fechas expl\u00edcitas, se puede usar el campo `duration`.",
+ "$ref": "#/definitions/Period"
+ }
+ }
+ },
+ "LotGroup": {
+ "title": "Grupo del lote",
+ "description": "Cuando el comprador se reserva el derecho de combinar lotes, o desea especificar el valor total para un grupo de lotes, se utiliza un grupo de lotes para capturar esta informaci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Identificador del grupo de lote",
+ "type": "string",
+ "description": "Un identificador local para este grupo de lotes."
+ },
+ "relatedLots": {
+ "title": "Lotes relacionados",
+ "description": "Una lista de los identificadores de los lotes que forman este grupo. Los lotes pueden aparecer en m\u00e1s de un grupo.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": [
+ "string"
+ ]
+ }
+ },
+ "optionToCombine": {
+ "title": "Opci\u00f3n de combinar",
+ "description": "El comprador se reserva el derecho de combinar los lotes de este grupo al adjudicar un contrato.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "maximumValue": {
+ "title": "Valor m\u00e1ximo",
+ "description": "El valor m\u00e1ximo estimado de los lotes de este grupo. Este puede ser inferior a la suma total de los valores de los lotes.",
+ "$ref": "#/definitions/Value"
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/lots/v1.1.5/schema/index.html b/es/extensions/lots/v1.1.5/schema/index.html
new file mode 100644
index 000000000..3529a63f1
--- /dev/null
+++ b/es/extensions/lots/v1.1.5/schema/index.html
@@ -0,0 +1,875 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lotes +
+ ++ Un proceso de licitación se puede dividir en lotes, donde los licitadores pueden ofertar en uno o más lotes. Los detalles de cada lote se pueden proporcionar aquí. Los artículos, documentos y otras características pueden hacer referencia al lote que están relacionados con el uso de relatedLot. Cuando no se indique ningún identificador relacionado, los valores deben interpretarse como aplicables a toda la licitación. +
+
+
+
+
+
+
+
+ ¿Cómo establecer
+
+
+
+ + Documentation +
+Cuando se desglosa una sola licitación en partes que pueden ofertarse y se adjudican separadamente, esto se presenta utilizando la extensión de lotes.
+La extensión de lotes mantiene la estructura general de una entrega de OCDS, con artículos, documentos e hitos incluidos inmediatamente dentro de los elementos tender, award y contract, pero introduce una lista de lotes en la sección tender, y la capacidad de hacer referencia cruzada a un relatedLot específico para cada elemento, y una lista de relatedLots para documentos, hitos y adjudicaciones
La sección opcional lotDetails y lotGroups permite que se expresen condiciones más complejas en torno a la adjudicación de lotes, como el valor máximo de un grupo de lotes.
Esto significa que los sistemas que no conocen la 'existencia de lotes' de igual forma pueden entender el valor global de la contratación que se esta llevando a cabo, los acontecimientos clave y las relaciones entre los compradores y los proveedores. Al mismo tiempo, los sistemas que sí conocen de la 'existencia de lotes' pueden hacer uso de la información referenciada para presentar una visión centrada-en-lotes en la información a los usuarios, o para analizar la contratación lote por lote.
+Lote Relacionado
+La propiedad relatedLot (singular) está disponible para:
-
+
- items +
Se puede proporcionar una lista de relatedLots (plural) para cada uno de los siguientes:
-
+
- documents +
- milestones +
- awards +
En otras extensiones, los siguientes objetos también pueden declararse lotes relacionados:
+-
+
- las ofertas presentadas por licitantes (
Bid), en la extensión ofertas
+ - las fuentes de finanzas (
Finance), in the extensión finanzas
+
Cuando se usan lotes, todos los elementos deben tener un campo relatedLot.
Los documentos e hitos pueden tener una propiedad relatedLots. Aquellos sin esta propiedad deben interpretarse como aplicables a la licitación en su conjunto.
Los artículos dentro de una adjudicación deben tener un campo relatedLot. Los publicadores pueden también hacer referencia a todos los lotes a los que se relaciona una adjudicación utilizando relatedLots.
¿Cómo establecer tender.status si los estados de los lotes son diferentes?
+tender.status y Lot.status usan la lista de código cerrada tenderStatus.csv. La lista de código avanza desde el estado de planeación ('planning', 'planned'), al estado 'activo', y finalmente el estado de los resultados ('complete', 'cancelled', 'unsuccessful').
-
+
- Si cualquiera de los estados del lote esta 'activo', entonces
tender.statusdebe ser 'activo', para indicar que algunos lotes están esperando resultados.
+ - Si todos los estados del lote se encuentran en estado de resultados, entonces
tender.statusdescribe el resultado agregado: +-
+
- Si al menos uno de los estados del lote esta 'completo', entonces
tender.statusdebe mostrar 'completo', para indicar que hay al menos una adjudicación.
+ - Si no es así, y al menos uno de los estados del lote es 'fallido', el
tender.statusdebe ser 'fallido' para indicar que el procedimiento se completo pero no exitosamente.
+ - De otra manera, si todos los estados del lote están 'cancelados', entonces
tender.statusdeben de estar 'cancelados', para indicar que el procedimiento se descontinuo en su totalidad.
+
+ - Si al menos uno de los estados del lote esta 'completo', entonces
Ejemplo
+Se emite una licitación para consultoría en el desarrollo de un nuevo edificio público. Esto podría incluir elementos para:
+-
+
- Diseño arquitectónico +
- Servicios de asesoramiento arquitectónico +
- Consultoría de ingeniería civil +
- Consultoría en ingeniería estructural +
Aunque forma parte de la misma oferta, el comprador está dispuesto a adjudicar estos diferentes artículos a diferentes empresas, y así divide la oferta en tres lotes.
+{
+ "tender": {
+ "items": [
+ {
+ "id": "0001",
+ "description": "Architectural advice",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71210000",
+ "description": "Advisory architectural services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0002",
+ "description": "Architectural design",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71220000",
+ "description": "Architectural design services"
+ },
+ "relatedLot": "lot-1"
+ },
+ {
+ "id": "0003",
+ "description": "Civil engineering consultant",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71311000",
+ "description": "Civil engineering consultancy services"
+ },
+ "relatedLot": "lot-2"
+ },
+ {
+ "id": "0004",
+ "description": "Structural engineering services",
+ "classification": {
+ "scheme": "CPV",
+ "id": "71312000",
+ "description": "Structural engineering consultancy services"
+ },
+ "relatedLot": "lot-3"
+ }
+ ],
+ "value": {
+ "amount": 1200000,
+ "currency": "GBP"
+ },
+ "lots": [
+ {
+ "id": "lot-1",
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ },
+ "contractPeriod": {
+ "startDate": "2020-10-10T00:00:00Z",
+ "endDate": "2021-11-10T00:00:00Z"
+ }
+ },
+ {
+ "id": "lot-2",
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ },
+ "contractPeriod": {
+ "startDate": "2020-12-10T00:00:00Z",
+ "endDate": "2021-12-10T00:00:00Z"
+ }
+ },
+ {
+ "id": "lot-3",
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ },
+ "contractPeriod": {
+ "startDate": "2021-02-10T00:00:00Z",
+ "endDate": "2022-02-10T00:00:00Z"
+ }
+ }
+ ],
+ "lotGroups": [
+ {
+ "id": "lot-group-1",
+ "relatedLots": [
+ "lot-2",
+ "lot-3"
+ ],
+ "optionToCombine": true,
+ "maximumValue": {
+ "currency": "GBP",
+ "amount": 1000000
+ }
+ }
+ ],
+ "lotDetails": {
+ "maximumLotsBidPerSupplier": 4,
+ "maximumLotsAwardedPerSupplier": 2,
+ "awardCriteriaDetails": "Percentage of people aggregated nationwide contestants undertake to cover, as indicated in their Economic Bids. The evaluation of proposals will be conducted based on the provisions of Article Y of the law on public private partnerships, and the provisions of the tender rules, performing in a first stage an evaluation of the technical bids and subsequently an assessment of the financial offer of the participants."
+ }
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.5
+-
+
- Añadir el campo
tender.lotDetails.awardCriteriaDetails.
+ - Añadir el campo
Finance.relatedLots.
+ - Añadir el campo
Lot.contractPeriod.
+ - Quitar la información sobre el tipo de las descripciones de los campos +
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- No permitir que
Tender.lotDetailssea null (error introducido en la primera versión)
+ Tender.lotDetailsya no usa$refpara una definición deLotDetails
+- Quita las directrices Sphinx del readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que los campos
relatedLotstengan null en sus listas de cadenas
+ - Agregar enum a
Lot.status
+ - Permitir que los campos
relatedLotssean null
+ - Agregar título y descripción a
Tender.lotDetails
+ - Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/medicine/index.html b/es/extensions/medicine/index.html
new file mode 100644
index 000000000..f39fdfaac
--- /dev/null
+++ b/es/extensions/medicine/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Lotes +
+ ++ Un proceso de licitación se puede dividir en lotes, donde los licitadores pueden ofertar en uno o más lotes. Los detalles de cada lote se pueden proporcionar aquí. Los artículos, documentos y otras características pueden hacer referencia al lote que están relacionados con el uso de relatedLot. Cuando no se indique ningún identificador relacionado, los valores deben interpretarse como aplicables a toda la licitación. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ lots
+
+ |
+ + Lotes + | +
+ Un proceso de licitación se puede dividir en lotes, donde los licitadores pueden ofertar en uno o más lotes. Los detalles de cada lote se pueden proporcionar aquí. Los artículos, documentos y otras características pueden hacer referencia al lote al que están relacionados con el uso de relatedLot. Cuando no se indique ningún identificador relacionado, los valores deben interpretarse como aplicables a toda la licitación. Las propiedades de la licitación pueden ser sobreescritas para un lote dado a través de su inclusión en el objeto Lot. + + |
+ + array of Lot objects + | +
+
+ lotDetails
+
+ |
+ + Detalles del lote + | +
+ Si esta licitación está dividida en lotes, aquí pueden darse detalles de los criterios que aplican para hacer una oferta en estos lotes. + + |
+ + object + | +
+
+ lotDetails.
+ |
+ + Lotes máximos por proveedor + | +
+ El número máximo de lotes por los que un proveedor puede ofertar como parte de este proceso de contratación. + + |
+ + integer + | +
+
+ lotDetails.
+ |
+ + Lotes máximos por proveedor + | +
+ El número máximo de lotes que pueden adjudicarse a un proveedor como parte de este proceso de contratación. + + |
+ + integer + | +
+
+ lotDetails.
+ |
+ + Detalles de criterios de adjudicación + | +
+ Cualquier información detallada o adicional sobre la adjudicación o los criterios de selección. + + |
+ + string + | +
+
+ lotGroups
+
+ |
+ + Grupos de lote + | +
+ Cuando el comprador se reserva el derecho de combinar lotes, o desea especificar el valor total para un grupo de lotes, se utiliza un grupo de lotes para capturar esta información. + + |
+ + array of LotGroup objects + | +
+ Document +
+ +
+ The extension defines these fields in the Document object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lotes relacionados + | +
+ Si este documento se refiere a un lote en particular, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aquí. + + |
+ + array of strings + | +
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLot
+
+ |
+ + Lote relacionado + | +
+ Si este artículo pertenece a un lote, provea el identificador del lote relacionado aquí. + + |
+ + string + | +
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lotes relacionados + | +
+ Si este documento se refiere a un lote en particular, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aquí. + + |
+ + array of strings + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lotes relacionados + | +
+ Si esta adjudicación se relaciona con uno o más lotes específicos, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aquí. + + |
+ + array of strings + | +
+ Bid +
+ +
+ The extension defines these fields in the Bid object from the Estadísticas y detalles de las ofertas extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lotes relacionados + | +
+ + This field is modified from its original version. + +Si esta oferta se relaciona con uno o más lotes específicos, proporcione el (los) identificador(es) del(los) lote(s) relacionado(s) aquí. + + |
+ + array of strings + | +
+ Finance +
+ +
+ The extension defines these fields in the Finance object from the Financiamiento extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLots
+
+ |
+ + Lotes relacionados + | +
+ + This field is modified from its original version. + +Si esta fuente de financiamiento se relaciona con uno o más lotes específicos, provea el/los identificador(es) de los lotes relacionados aquí. + + |
+ + array of strings + | +
+ Lot +
+ +
+ The extension defines a new Lot object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID Lote + | +
+ Un identificador local para este lote, tal como un número de lote. Esto se utiliza en las referencias relatedLots en el nivel de artículo, documento y adjudicación. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título + | +
+ Un título para este lote. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Una descripción de este lote. + + |
+ + string + | +
+
+ status
+
+ |
+ + Estatus de lote + | +
+ El estado actual del proceso relacionado a este lote. + + |
+ + string from closed tenderStatus codelist + | +
+
+ value
+
+ |
+ + Valor del lote + | +
+ El valor máximo estimado de este lote. + + |
+ + Value object + | +
+
+ contractPeriod
+
+ |
+ + Período del contrato + | +
+ El período sobre el cual se estima o especifica que el contrato estará activo. Si el lote no especifica fechas explícitas, se puede usar el campo |
+ + Period object + | +
+ LotGroup +
+ +
+ The extension defines a new LotGroup object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador del grupo de lote + | +
+ Un identificador local para este grupo de lotes. + + |
+ + string + | +
+
+ relatedLots
+
+ |
+ + Lotes relacionados + | +
+ Una lista de los identificadores de los lotes que forman este grupo. Los lotes pueden aparecer en más de un grupo. + + |
+ + array of strings + | +
+
+ optionToCombine
+
+ |
+ + Opción de combinar + | +
+ El comprador se reserva el derecho de combinar los lotes de este grupo al adjudicar un contrato. + + |
+ + boolean + | +
+
+ maximumValue
+
+ |
+ + Valor máximo + | +
+ El valor máximo estimado de los lotes de este grupo. Este puede ser inferior a la suma total de los valores de los lotes. + + |
+ + Value object + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/medicine/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/medicine/master/extension.json b/es/extensions/medicine/master/extension.json
new file mode 100644
index 000000000..76d9542f7
--- /dev/null
+++ b/es/extensions/medicine/master/extension.json
@@ -0,0 +1,28 @@
+{
+ "name": {
+ "en": "Medicine",
+ "es": "Medicina"
+ },
+ "description": {
+ "en": "Adds fields to the item object relevant to the procurement of medicines.",
+ "es": "Agrega campos al objeto art\u00edculo relevantes para la adquisici\u00f3n de medicamentos."
+ },
+ "documentationUrl": {
+ "en": "http://extensions.open-contracting.org/en/extensions/medicine/"
+ },
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "dosageForm.csv",
+ "administrationRoute.csv",
+ "container.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/medicine/master/index.html b/es/extensions/medicine/master/index.html
new file mode 100644
index 000000000..562fe00f3
--- /dev/null
+++ b/es/extensions/medicine/master/index.html
@@ -0,0 +1,441 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Medicina +
+ ++ Agrega campos al objeto artículo relevantes para la adquisición de medicamentos. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ administrationRoute.csv +
+ +
+ You can download the administrationRoute.csv file in English.
+
| + Código + | ++ Título + | +
|---|---|
+
+ AMNINJ
+
+ |
+ + Injection, amniotic fluid + | +
+
+ BILINJ
+
+ |
+ + Injection, biliary tract + | +
+
+ CHOLINJ
+
+ |
+ + Injection, for cholangiography + | +
+
+ DRESS
+
+ |
+ + Topical application, soaked dressing + | +
+
+ ELECTOSMOS
+
+ |
+ + Electro-osmosis + | +
+
+ IONTO
+
+ |
+ + Topical application, iontophoresis + | +
+
+ SOAK
+
+ |
+ + Immersion (soak) + | +
+
+ SWAB
+
+ |
+ + Topical application, swab + | +
+
+ TOPICAL
+
+ |
+ + Topical + | +
+
+ BUC
+
+ |
+ + Topical application, buccal + | +
+
+ CECINSTL
+
+ |
+ + Instillation, cecostomy + | +
+
+ CERV
+
+ |
+ + Topical application, cervical + | +
+
+ CERVINJ
+
+ |
+ + Injection, cervical + | +
+
+ CERVINS
+
+ |
+ + Insertion, cervical (uterine) + | +
+
+ DEN
+
+ |
+ + Topical application, dental + | +
+
+ DENRINSE
+
+ |
+ + Rinse, dental + | +
+
+ CHEW
+
+ |
+ + Chew, oral + | +
+
+ EXTCORPDIF
+
+ |
+ + Diffusion, extracorporeal + | +
+
+ HEMODIFF
+
+ |
+ + Diffusion, hemodialysis + | +
+
+ TRNSDERMD
+
+ |
+ + Diffusion, transdermal + | +
+
+ DISSOLVE
+
+ |
+ + Dissolve, oral + | +
+
+ SL
+
+ |
+ + Dissolve, sublingual + | +
+
+ DOUCHE
+
+ |
+ + Douche, vaginal + | +
+
+ ENEMA
+
+ |
+ + Enema, rectal + | +
+
+ RETENEMA
+
+ |
+ + Enema, rectal retention + | +
+
+ EFT
+
+ |
+ + Instillation, enteral feeding tube + | +
+
+ ENTINSTL
+
+ |
+ + Instillation, enteral + | +
+
+ EPI
+
+ |
+ + Infusion, epidural + | +
+
+ EPIDURINJ
+
+ |
+ + Injection, epidural + | +
+
+ EPIINJ
+
+ |
+ + Injection, epidural, push + | +
+
+ EPINJSP
+
+ |
+ + Injection, epidural, slow push + | +
+
+ EXTRAMNINJ
+
+ |
+ + Injection, extra-amniotic + | +
+
+ EXTCORPINJ
+
+ |
+ + Injection, extracorporeal + | +
+
+ IVFLUSH
+
+ |
+ + Flush, intravenous catheter + | +
+
+ GBINJ
+
+ |
+ + Injection, gastric button + | +
+
+ GT
+
+ |
+ + Instillation, gastrostomy tube + | +
+
+ NGT
+
+ |
+ + Instillation, nasogastric tube + | +
+
+ OGT
+
+ |
+ + Instillation, orogastric tube + | +
+
+ GUIRR
+
+ |
+ + Irrigation, genitourinary + | +
+
+ GIN
+
+ |
+ + Topical application, gingival + | +
+
+ GINGINJ
+
+ |
+ + Injection, gingival + | +
+
+ HAIR
+
+ |
+ + Topical application, hair + | +
+
+ SHAMPOO
+
+ |
+ + Shampoo + | +
+
+ IDIMPLNT
+
+ |
+ + Implantation, intradermal + | +
+
+ IVITIMPLNT
+
+ |
+ + Implantation, intravitreal + | +
+
+ SQIMPLNT
+
+ |
+ + Implantation, subcutaneous + | +
+
+ IA
+
+ |
+ + Infusion, intraarterial catheter + | +
+
+ IC
+
+ |
+ + Infusion, intracardiac + | +
+
+ ICOR
+
+ |
+ + Infusion, intracoronary + | +
+
+ IOSSC
+
+ |
+ + Infusion, intraosseous, continuous + | +
+
+ IT
+
+ |
+ + Infusion, intrathecal + | +
+
+ IV
+
+ |
+ + Infusion, intravenous + | +
+
+ IVASCINFUS
+
+ |
+ + Infusion, intravascular + | +
+
+ SQINFUS
+
+ |
+ + Infusion, subcutaneous + | +
+
+ IPINHL
+
+ |
+ + Inhalation, respiratory + | +
+
+ IPPB
+
+ |
+ + Inhalation, intermittent positive pressure breathing (ippb) + | +
+
+ NASINHL
+
+ |
+ + Inhalation, nasal + | +
+
+ NEB
+
+ |
+ + Inhalation, nebulization + | +
+
+ TRACH
+
+ |
+ + Inhalation, tracheostomy + | +
+
+ VENT
+
+ |
+ + Inhalation, ventilator + | +
+
+ VENTMASK
+
+ |
+ + Inhalation, ventimask + | +
+
+ BLADINJ
+
+ |
+ + Injection, urinary bladder + | +
+
+ ENDOSININJ
+
+ |
+ + Injection, endosinusial + | +
+
+ HEMOPORT
+
+ |
+ + Injection, hemodialysis port + | +
+
+ IABDINJ
+
+ |
+ + Injection, intra-abdominal + | +
+
+ IAINJ
+
+ |
+ + Injection, intraarterial + | +
+
+ IARTINJ
+
+ |
+ + Injection, intraarticular + | +
+
+ IBURSINJ
+
+ |
+ + Injection, intrabursal + | +
+
+ ICARDINJ
+
+ |
+ + Injection, intracardiac + | +
+
+ ICARTINJ
+
+ |
+ + Injection, intracartilaginous + | +
+
+ ICAUDINJ
+
+ |
+ + Injection, intracaudal + | +
+
+ ICAVINJ
+
+ |
+ + Injection, intracavernous + | +
+
+ ICAVITINJ
+
+ |
+ + Injection, intracavitary + | +
+
+ ICEREBINJ
+
+ |
+ + Injection, intracerebral + | +
+
+ ICISTERNINJ
+
+ |
+ + Injection, intracisternal + | +
+
+ ICORONINJ
+
+ |
+ + Injection, intracoronary + | +
+
+ ICORPCAVINJ
+
+ |
+ + Injection, intracorpus cavernosum + | +
+
+ IDINJ
+
+ |
+ + Injection, intradermal + | +
+
+ IDISCINJ
+
+ |
+ + Injection, intradiscal + | +
+
+ IDUCTINJ
+
+ |
+ + Injection, intraductal + | +
+
+ IDURINJ
+
+ |
+ + Injection, intradural + | +
+
+ IEPIDINJ
+
+ |
+ + Injection, intraepidermal + | +
+
+ IEPITHINJ
+
+ |
+ + Injection, intraepithelial + | +
+
+ ILESINJ
+
+ |
+ + Injection, intralesional + | +
+
+ ILUMINJ
+
+ |
+ + Injection, intraluminal + | +
+
+ ILYMPJINJ
+
+ |
+ + Injection, intralymphatic + | +
+
+ IM
+
+ |
+ + Injection, intramuscular + | +
+
+ IMEDULINJ
+
+ |
+ + Injection, intramedullary + | +
+
+ INTERMENINJ
+
+ |
+ + Injection, interameningeal + | +
+
+ INTERSTITINJ
+
+ |
+ + Injection, interstitial + | +
+
+ IOINJ
+
+ |
+ + Injection, intraocular + | +
+
+ IOSSINJ
+
+ |
+ + Injection, intraosseous + | +
+
+ IOVARINJ
+
+ |
+ + Injection, intraovarian + | +
+
+ IPCARDINJ
+
+ |
+ + Injection, intrapericardial + | +
+
+ IPERINJ
+
+ |
+ + Injection, intraperitoneal + | +
+
+ IPINJ
+
+ |
+ + Injection, intrapulmonary + | +
+
+ IPLRINJ
+
+ |
+ + Injection, intrapleural + | +
+
+ IPROSTINJ
+
+ |
+ + Injection, intraprostatic + | +
+
+ IPUMPINJ
+
+ |
+ + Injection, insulin pump + | +
+
+ ISINJ
+
+ |
+ + Injection, intraspinal + | +
+
+ ISTERINJ
+
+ |
+ + Injection, intrasternal + | +
+
+ ISYNINJ
+
+ |
+ + Injection, intrasynovial + | +
+
+ ITENDINJ
+
+ |
+ + Injection, intratendinous + | +
+
+ ITESTINJ
+
+ |
+ + Injection, intratesticular + | +
+
+ ITHORINJ
+
+ |
+ + Injection, intrathoracic + | +
+
+ ITINJ
+
+ |
+ + Injection, intrathecal + | +
+
+ ITUBINJ
+
+ |
+ + Injection, intratubular + | +
+
+ ITUMINJ
+
+ |
+ + Injection, intratumor + | +
+
+ ITYMPINJ
+
+ |
+ + Injection, intratympanic + | +
+
+ IUINJ
+
+ |
+ + Injection, intrauterine + | +
+
+ IUINJC
+
+ |
+ + Injection, intracervical (uterus) + | +
+
+ IURETINJ
+
+ |
+ + Injection, intraureteral, retrograde + | +
+
+ IVASCINJ
+
+ |
+ + Injection, intravascular + | +
+
+ IVENTINJ
+
+ |
+ + Injection, intraventricular (heart) + | +
+
+ IVESINJ
+
+ |
+ + Injection, intravesicle + | +
+
+ IVINJ
+
+ |
+ + Injection, intravenous + | +
+
+ IVITINJ
+
+ |
+ + Injection, intravitreal + | +
+
+ PAINJ
+
+ |
+ + Injection, periarticular + | +
+
+ PARENTINJ
+
+ |
+ + Injection, parenteral + | +
+
+ PDONTINJ
+
+ |
+ + Injection, periodontal + | +
+
+ PDPINJ
+
+ |
+ + Injection, peritoneal dialysis port + | +
+
+ PDURINJ
+
+ |
+ + Injection, peridural + | +
+
+ PNINJ
+
+ |
+ + Injection, perineural + | +
+
+ PNSINJ
+
+ |
+ + Injection, paranasal sinuses + | +
+
+ RBINJ
+
+ |
+ + Injection, retrobulbar + | +
+
+ SCINJ
+
+ |
+ + Injection, subconjunctival + | +
+
+ SLESINJ
+
+ |
+ + Injection, sublesional + | +
+
+ SOFTISINJ
+
+ |
+ + Injection, soft tissue + | +
+
+ SQ
+
+ |
+ + Injection, subcutaneous + | +
+
+ SUBARACHINJ
+
+ |
+ + Injection, subarachnoid + | +
+
+ SUBMUCINJ
+
+ |
+ + Injection, submucosal + | +
+
+ TRPLACINJ
+
+ |
+ + Injection, transplacental + | +
+
+ TRTRACHINJ
+
+ |
+ + Injection, transtracheal + | +
+
+ URETHINJ
+
+ |
+ + Injection, urethral + | +
+
+ URETINJ
+
+ |
+ + Injection, ureteral + | +
+
+ IOSURGINS
+
+ |
+ + Insertion, intraocular, surgical + | +
+
+ IU
+
+ |
+ + Insertion, intrauterine + | +
+
+ LPINS
+
+ |
+ + Insertion, lacrimal puncta + | +
+
+ PR
+
+ |
+ + Insertion, rectal + | +
+
+ SQSURGINS
+
+ |
+ + Insertion, subcutaneous, surgical + | +
+
+ URETHINS
+
+ |
+ + Insertion, urethral + | +
+
+ VAGINSI
+
+ |
+ + Insertion, vaginal + | +
+
+ BLADINSTL
+
+ |
+ + Instillation, urinary catheter + | +
+
+ CAPDINSTL
+
+ |
+ + Instillation, continuous ambulatory peritoneal dialysis port + | +
+
+ CTINSTL
+
+ |
+ + Instillation, chest tube + | +
+
+ ETINSTL
+
+ |
+ + Instillation, endotracheal tube + | +
+
+ GJT
+
+ |
+ + Instillation, gastro-jejunostomy tube + | +
+
+ IBRONCHINSTIL
+
+ |
+ + Instillation, intrabronchial + | +
+
+ IDUODINSTIL
+
+ |
+ + Instillation, intraduodenal + | +
+
+ IESOPHINSTIL
+
+ |
+ + Instillation, intraesophageal + | +
+
+ IGASTINSTIL
+
+ |
+ + Instillation, intragastric + | +
+
+ IILEALINJ
+
+ |
+ + Instillation, intraileal + | +
+
+ IOINSTL
+
+ |
+ + Instillation, intraocular + | +
+
+ ISININSTIL
+
+ |
+ + Instillation, intrasinal + | +
+
+ ITRACHINSTIL
+
+ |
+ + Instillation, intratracheal + | +
+
+ IUINSTL
+
+ |
+ + Instillation, intrauterine + | +
+
+ JJTINSTL
+
+ |
+ + Instillation, jejunostomy tube + | +
+
+ LARYNGINSTIL
+
+ |
+ + Instillation, laryngeal + | +
+
+ NASALINSTIL
+
+ |
+ + Instillation, nasal + | +
+
+ NASOGASINSTIL
+
+ |
+ + Instillation, nasogastric + | +
+
+ NTT
+
+ |
+ + Instillation, nasotracheal tube + | +
+
+ OJJ
+
+ |
+ + Instillation, orojejunum tube + | +
+
+ OT
+
+ |
+ + Instillation, otic + | +
+
+ PDPINSTL
+
+ |
+ + Instillation, peritoneal dialysis port + | +
+
+ PNSINSTL
+
+ |
+ + Instillation, paranasal sinuses + | +
+
+ RECINSTL
+
+ |
+ + Instillation, rectal + | +
+
+ SININSTIL
+
+ |
+ + Instillation, sinus, unspecified + | +
+
+ SOFTISINSTIL
+
+ |
+ + Instillation, soft tissue + | +
+
+ TRACHINSTL
+
+ |
+ + Instillation, tracheostomy + | +
+
+ TRTYMPINSTIL
+
+ |
+ + Instillation, transtympanic + | +
+
+ URETHINSTL
+
+ |
+ + Instillation, urethral + | +
+
+ ICORNTA
+
+ |
+ + Topical application, intracorneal + | +
+
+ ICORONTA
+
+ |
+ + Topical application, intracoronal (dental) + | +
+
+ IDOUDMAB
+
+ |
+ + Mucosal absorption, intraduodenal + | +
+
+ IESOPHTA
+
+ |
+ + Topical application, intraesophageal + | +
+
+ IGASTIRR
+
+ |
+ + Irrigation, intragastric + | +
+
+ IGASTLAV
+
+ |
+ + Lavage, intragastric + | +
+
+ IILEALTA
+
+ |
+ + Topical application, intraileal + | +
+
+ ILESIRR
+
+ |
+ + Irrigation, intralesional + | +
+
+ ILTOP
+
+ |
+ + Topical application, intralesional + | +
+
+ ILUMTA
+
+ |
+ + Topical application, intraluminal + | +
+
+ IOIRR
+
+ |
+ + Irrigation, intraocular + | +
+
+ IOTOP
+
+ |
+ + Topical application, intraocular + | +
+
+ ITRACHMAB
+
+ |
+ + Mucosal absorption, intratracheal + | +
+
+ BLADIRR
+
+ |
+ + Irrigation, urinary bladder + | +
+
+ RECIRR
+
+ |
+ + Irrigation, rectal + | +
+
+ LARYNGTA
+
+ |
+ + Topical application, laryngeal + | +
+
+ TRNSLING
+
+ |
+ + Translingual + | +
+
+ SMUCMAB
+
+ |
+ + Mucosal absorption, submucosal + | +
+
+ MUC
+
+ |
+ + Topical application, mucous membrane + | +
+
+ NAIL
+
+ |
+ + Topical application, nail + | +
+
+ NASAL
+
+ |
+ + Topical application, nasal + | +
+
+ ETNEB
+
+ |
+ + Nebulization, endotracheal tube + | +
+
+ OPTHALTA
+
+ |
+ + Topical application, ophthalmic + | +
+
+ ORALTA
+
+ |
+ + Topical application, oral + | +
+
+ ORRINSE
+
+ |
+ + Rinse, oral + | +
+
+ PO
+
+ |
+ + Swallow, oral + | +
+
+ GARGLE
+
+ |
+ + Gargle + | +
+
+ ORMUC
+
+ |
+ + Topical application, oromucosal + | +
+
+ SUCK
+
+ |
+ + Suck, oromucosal + | +
+
+ SWISHSPIT
+
+ |
+ + Swish and spit out, oromucosal + | +
+
+ SWISHSWAL
+
+ |
+ + Swish and swallow, oromucosal + | +
+
+ OROPHARTA
+
+ |
+ + Topical application, oropharyngeal + | +
+
+ PERIANAL
+
+ |
+ + Topical application, perianal + | +
+
+ PERINEAL
+
+ |
+ + Topical application, perineal + | +
+
+ PDONTTA
+
+ |
+ + Topical application, periodontal + | +
+
+ RECTAL
+
+ |
+ + Topical application, rectal + | +
+
+ INSUF
+
+ |
+ + Insufflation + | +
+
+ TRNSDERM
+
+ |
+ + Transdermal + | +
+
+ SCALP
+
+ |
+ + Topical application, scalp + | +
+
+ OCDRESTA
+
+ |
+ + Occlusive dressing technique + | +
+
+ SKIN
+
+ |
+ + Topical application, skin + | +
+
+ SUBCONJTA
+
+ |
+ + Subconjunctival + | +
+
+ URETHSUP
+
+ |
+ + Suppository, urethral + | +
+
+ TTYMPTABSORP
+
+ |
+ + Topical absorption, transtympanic + | +
+
+ TMUCTA
+
+ |
+ + Topical application, transmucosal + | +
+
+ VAGINS
+
+ |
+ + Topical application, vaginal + | +
+ container.csv +
+ +
+ You can download the container.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ amp
+
+ |
+ + Ampule + | +
+ Container sealed by fusion and to be opened exclusively by breaking. The contents are intended for use on one occasion only. + + |
+
+
+ bag
+
+ |
+ + Bag + | +
+ Container consisting of surfaces, whether or not with a flat bottom, made of flexible material, generally closed at the bottom and at the sides by sealing; at the top possibly to be closed by fusion of the material, depending on the intended use. Equipped with special attachments. Contains the final preparation in one compartment or the components necessary for its preparation in different compartments. + + |
+
+
+ blstrpk
+
+ |
+ + Blister Pack + | +
+ Container (usually multidose) consisting of two layers of which one is shaped to contain the individual doses. Strips are excluded. + + |
+
+
+ bot
+
+ |
+ + Bottle + | +
+ Container with a more or less pronounced neck and usually a flat bottom. + + |
+
+
+ box
+
+ |
+ + Box + | +
+ Primary container consisting of one or more parts made of a light material, can be closed. + + |
+
+
+ can
+
+ |
+ + Can + | ++ + | +
+
+ cart
+
+ |
+ + Cartridge + | +
+ Filled container, usually cylindrical, containing a sterile, single-dose or multidose, parenteral preparation; it contains the final preparation in one compartment, or the components necessary for its preparation in different compartments. It may be supplied as an integral part of a pre-filled pen or be intended for use in a reusable device especially designed for that purpose, such as a pen. + + |
+
+
+ disk
+
+ |
+ + Disk + | ++ + | +
+
+ doset
+
+ |
+ + Dosette + | ++ + | +
+
+ jar
+
+ |
+ + Jar + | +
+ Container, without a pronounced neck, with a wide opening at the top and a more-or-less flat bottom. It is suited for semi-solid and solid pharmaceutical forms (including those that are stored/supplied in a liquid medium, such as living tissue equivalents). It can be reclosed. + + |
+
+
+ jug
+
+ |
+ + Jug + | ++ + | +
+
+ minim
+
+ |
+ + Minim + | ++ + | +
+
+ nebamp
+
+ |
+ + Nebule Amp + | ++ + | +
+
+ ovul
+
+ |
+ + Ovule + | ++ + | +
+
+ pch
+
+ |
+ + Pouch + | +
+ Item of packaging intended for use as an intermediate or outer container, intended to contain one or more medicinal product(s); it is made of a flexible material and may be for single use or be re-usable, and may be fitted with a closure system. Bags and sachets are excluded. + + |
+
+
+ pkt
+
+ |
+ + Packet + | ++ + | +
+
+ sash
+
+ |
+ + Sashet + | +
+ Container consisting of two surfaces made of flexible material to be closed only by sealing or folding over. The contents are intended for single use. + + |
+
+
+ strip
+
+ |
+ + Strip + | +
+ Multidose container consisting of two layers, usually provided with perforations, suited for containing single doses of solid or semi-solid preparations. Blisters are excluded. + + |
+
+
+ tin
+
+ |
+ + Tin + | ++ + | +
+
+ tub
+
+ |
+ + Tub + | ++ + | +
+
+ tube
+
+ |
+ + Tube + | +
+ Container for semi-solid pharmaceutical forms, usually multidose, consisting of collapsible material intended to release the contents via a nozzle by squeezing the package. + + |
+
+
+ vial
+
+ |
+ + Vial + | +
+ Small container for parenteral medicinal products, with a stopper and overseal; the contents are removed after piercing the stopper. Single-dose and multidose uses are included. + + |
+
+ dosageForm.csv +
+ +
+ You can download the dosageForm.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ APPFUL
+
+ |
+ + Applicatorful + | ++ + | +
+
+ DROP
+
+ |
+ + Drops + | ++ + | +
+
+ PUFF
+
+ |
+ + Puff + | ++ + | +
+
+ SCOOP
+
+ |
+ + Scoops + | ++ + | +
+
+ SPRY
+
+ |
+ + Sprays + | ++ + | +
+
+ GASINHL
+
+ |
+ + Gas for Inhalation + | ++ + | +
+
+ AER
+
+ |
+ + Aerosol + | ++ + | +
+
+ FOAM
+
+ |
+ + Foam + | ++ + | +
+
+ INHL
+
+ |
+ + Inhalant + | ++ + | +
+
+ LIQCLN
+
+ |
+ + Liquid Cleanser + | ++ + | +
+
+ OIL
+
+ |
+ + Oil + | +
+ An unctuous, combustible substance which is liquid, or easily liquefiable, on warming, and is soluble in ether but insoluble in water. Such substances, depending on their origin, are classified as animal, mineral, or vegetable oils. + + |
+
+
+ SOL
+
+ |
+ + Solution + | +
+ A liquid preparation that contains one or more chemical substances dissolved, i.e., molecularly dispersed, in a suitable solvent or mixture of mutually miscible solvents. + + |
+
+
+ CRM
+
+ |
+ + Cream + | +
+ A semisolid dosage form containing one or more drug substances dissolved or dispersed in a suitable base; more recently, the term has been restricted to products consisting of oil-in-water emulsions or aqueous microcrystalline dispersions of long chain fatty acids or alcohols that are water washable and more cosmetically and aesthetically acceptable. + + |
+
+
+ LTN
+
+ |
+ + Lotion + | +
+ The term "lotion" has been used to categorize many topical suspensions, solutions and emulsions intended for application to the skin. + + |
+
+
+ OINT
+
+ |
+ + Ointment + | +
+ A semisolid preparation intended for external application to the skin or mucous membranes. + + |
+
+
+ GEL
+
+ |
+ + Gel + | +
+ A semisolid system consisting of either suspensions made up of small inorganic particles or large organic molecules interpenetrated by a liquid. + + |
+
+
+ PASTE
+
+ |
+ + Paste + | +
+ A semisolid dosage form that contains one or more drug substances intended for topical application. + + |
+
+
+ SUSP
+
+ |
+ + Suspension + | ++ + | +
+
+ BAR
+
+ |
+ + Bar + | ++ + | +
+
+ BEAD
+
+ |
+ + Beads + | +
+ A solid dosage form in the shape of a small ball. + + |
+
+
+ CAKE
+
+ |
+ + Cake + | ++ + | +
+
+ CEMENT
+
+ |
+ + Cement + | +
+ A substance that serves to produce solid union between two surfaces. + + |
+
+
+ CRYS
+
+ |
+ + Crystals + | +
+ A naturally produced angular solid of definite form in which the ultimate units from which it is built up are systematically arranged; they are usually evenly spaced on a regular space lattice. + + |
+
+
+ DISK
+
+ |
+ + Disk + | +
+ A circular plate-like organ or structure. + + |
+
+
+ FLAKE
+
+ |
+ + Flakes + | ++ + | +
+
+ GRAN
+
+ |
+ + Granules + | +
+ A small particle or grain. + + |
+
+
+ GUM
+
+ |
+ + ChewingGum + | +
+ A sweetened and flavored insoluble plastic material of various shapes which when chewed, releases a drug substance into the oral cavity. + + |
+
+
+ PAD
+
+ |
+ + Pad + | ++ + | +
+
+ PATCH
+
+ |
+ + Patch + | +
+ A drug delivery system that contains an adhesived backing and that permits its ingredients to diffuse from some portion of it (e.g., the backing itself, a reservoir, the adhesive, or some other component) into the body from the external site where it is applied. + + |
+
+
+ PELLET
+
+ |
+ + Pellet + | +
+ A small sterile solid mass consisting of a highly purified drug (with or without excipients) made by the formation of granules, or by compression and molding. + + |
+
+
+ PILL
+
+ |
+ + Pill + | +
+ A small, round solid dosage form containing a medicinal agent intended for oral administration. + + |
+
+
+ POWD
+
+ |
+ + Powder + | +
+ An intimate mixture of dry, finely divided drugs and/or chemicals that may be intended for internal or external use. + + |
+
+
+ SUPP
+
+ |
+ + Suppository + | +
+ A solid body of various weights and shapes, adapted for introduction into the rectal, vaginal, or urethral orifice of the human body; they usually melt, soften, or dissolve at body temperature. + + |
+
+
+ SWAB
+
+ |
+ + Swab + | +
+ A wad of absorbent material usually wound around one end of a small stick and used for applying medication or for removing material from an area. + + |
+
+
+ WAFER
+
+ |
+ + Wafer + | +
+ A thin slice of material containing a medicinal agent. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/medicine/master/release-schema.json b/es/extensions/medicine/master/release-schema.json
new file mode 100644
index 000000000..2c40bbe48
--- /dev/null
+++ b/es/extensions/medicine/master/release-schema.json
@@ -0,0 +1,144 @@
+{
+ "definitions": {
+ "Item": {
+ "properties": {
+ "activeIngredients": {
+ "title": "Principios activos",
+ "description": "Los ingredientes o principios activos, normalmente compuestos qu\u00edmicos o sustancias biol\u00f3gicas.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/ActiveIngredient"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "dosageForm": {
+ "title": "Forma de dosificaci\u00f3n",
+ "description": "La forma de dosificaci\u00f3n farmac\u00e9utica en la que est\u00e1 disponible el medicamento, de la lista de c\u00f3digos dosageForm.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "dosageForm.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "administrationRoute": {
+ "title": "V\u00eda de administraci\u00f3n",
+ "description": "La v\u00eda por la que se puede administrar el medicamento, a partir de la lista de c\u00f3digos administrationRoute.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "administrationRoute.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "container": {
+ "title": "Envase",
+ "description": "El recipiente inmediato del medicamento. Tambi\u00e9n se conoce como: presentaci\u00f3n, forma de presentaci\u00f3n, envase.",
+ "$ref": "#/definitions/Container"
+ }
+ }
+ },
+ "ActiveIngredient": {
+ "title": "Principio activo",
+ "description": "Un principio activo, normalmente un compuesto qu\u00edmico o una sustancia biol\u00f3gica.",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Nombre",
+ "description": "The name of the active ingredient. It is recommended to use the lowercase Latin name from the International Nonproprietary Names (INN). Also known as: generic name, drug, substance name, active substance.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "strength": {
+ "title": "Concentraci\u00f3n",
+ "description": "La fuerza del ingrediente o principio activo. Tambi\u00e9n se conoce como: concentraci\u00f3n, potencia.",
+ "$ref": "#/definitions/Quantity"
+ }
+ },
+ "minProperties": 1
+ },
+ "Container": {
+ "title": "Envase",
+ "description": "El recipiente inmediato del medicamento. Tambi\u00e9n se conoce como: presentaci\u00f3n, forma de presentaci\u00f3n, envase.",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Nombre",
+ "description": "El nombre com\u00fan del envase de la lista de c\u00f3digos del container codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "container.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "capacity": {
+ "title": "Capacidad",
+ "description": "La capacidad de almacenamiento del recipiente o envase.",
+ "$ref": "#/definitions/Quantity"
+ }
+ },
+ "minProperties": 1
+ },
+ "Quantity": {
+ "title": "Cantidad",
+ "description": "La cantidad de un elemento.",
+ "type": "object",
+ "properties": {
+ "unit": {
+ "title": "Unidad",
+ "description": "La unidad de medida para la cantidad.",
+ "$ref": "#/definitions/SimpleUnit"
+ },
+ "value": {
+ "title": "Valor",
+ "description": "La cantidad, como m\u00faltiplo de la unidad de medida. La cantidad se expresa en notaci\u00f3n de intervalo, por ejemplo \"[10,10]\" para 10 unidades, \"[1,10]\" para 1 a 10 unidades, o \"[10,INF[\" para 10 o m\u00e1s unidades.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "pattern": "^[([\\]][0-9]+,([0-9]+|INF)[)[\\]]$"
+ }
+ },
+ "minProperties": 1
+ },
+ "SimpleUnit": {
+ "title": "Unidad simple",
+ "description": "Una unidad de medida.",
+ "type": "object",
+ "properties": {
+ "scheme": {
+ "title": "Esquema",
+ "description": "La lista de c\u00f3digos de la que se toma el identificador de la unidad de medida, utilizando la lista de c\u00f3digos abierta [unitClassificationScheme](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#unit-classification-scheme). Se recomienda utilizar 'UNCEFACT'.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "El identificador de la unidad de medida, tomado de la lista de c\u00f3digos a la que hace referencia el campo `scheme`. Consulte la lista de c\u00f3digos [unitClassificationScheme](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#unit-classification-scheme) para obtener detalles sobre c\u00f3mo encontrar identificadores dentro de los esquemas.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "versionId": true,
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/medicine/master/schema/index.html b/es/extensions/medicine/master/schema/index.html
new file mode 100644
index 000000000..c274a67ab
--- /dev/null
+++ b/es/extensions/medicine/master/schema/index.html
@@ -0,0 +1,559 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Medicina +
+ ++ Agrega campos al objeto artículo relevantes para la adquisición de medicamentos. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agrega campos al objeto artículo relevantes para la adquisición de medicamentos.
+Guía
+Esta extensión se utiliza para describir medicamentos en las fases de licitación, adjudicación y/o contrato. Con esta extensión, un publicador puede especificar los principios activos del medicamento y su concentración, la forma de dosificación, el envase del medicamento y la vía de administración. De este modo, se facilita la comparación de la adquisición de medicamentos entre jurisdicciones y, por tanto, se apoya los precios de referencia externos.
+Las formas de dosificación y los tamaños de los envases difieren significativamente entre países, lo que dificulta la comparación. Para facilitar la comparación, la extensión proporciona listas de códigos estandarizadas para la forma de dosificación, el recipiente inmediato y la vía de administración, basadas en Health Level Seven (HL7), un conjunto de normas internacionales para datos sanitarios. Dicho esto, si no ha adoptado y no puede mapear sus valores a los códigos HL7, puede utilizar sus propios códigos. Para que un usuario pueda interpretar sus códigos, debe describir las listas de códigos, y cómo encontrar las definiciones de los mismos, en su política de publicación.
+Para los nombres de los principios activos, se recomienda utilizar las Denominaciones Comunes Internacionales o por sus siglas en inglés International Nonproprietary Names (INN). La Organización Mundial de la Salud (OMS) mantiene una lista acumulativa de todas las INNs, con nombres equivalentes en latín, inglés, francés, español, árabe, chino y ruso. Para facilitar la comparación, se recomienda utilizar el nombre latino en minúsculas.
+Si un proceso de contratación está en fase de adjudicación o contrato, es posible conocer más información sobre el medicamento, como la marca, el fabricante, el país de origen, la fecha de caducidad, si deben mantener una cadena de frío y todas las demás condiciones comerciales, financieras y logísticas. Utilice la extensión atributos genéricos del artículo para todos los casos en que el artículo del medicamento tenga otros atributos no incluidos en esta extensión.
+Si un medicamento tiene más de un principio activo, agregue cada uno de ellos a la lista de activeIngredients.
Ejemplos
+Un principio activo
+En este ejemplo, demostramos cómo utilizar esta extensión para describir un proceso de adquisición de medicamentos de Chile. (Puede ver sus datos originales OCDS.)
+El punto 3 se describe como:
+| Description | +Minimum dispensing unit | +
|---|---|
| Acetilcisteina | +ACETILCISTEINA-N 100 MG/ML SOLUCION PARA NEBULIZAR FRASCO 15-30 ML ENVASE INDIVIDUAL RESISTENTE CON SELLO QUE ASEGURE INVIOLABILIDAD DEL CONTENIDO | +
La concentración se expresa como "100 MG/ML". La lista de códigos UN/CEFACT Recomendación 20 - Códigos de Unidades de Medida Utilizados en el Comercio Internacional incluye unidades como mg/l, g/l y kg/l, pero no mg/ml. Así, "100 MG/ML" se expresa como 100 g/l a continuación.
+A partir de esta información, podemos agregar el dosageForm, administrationRoute, container y activeIngredients.
{
+ "tender": {
+ "items": [
+ {
+ "id": "1",
+ "description": "Acetilcisteina",
+ "classification": {
+ "id": "51161701",
+ "scheme": "UNSPSC",
+ "uri": "https://apis.mercadopublico.cl/OCDS/data/productos/categoria/51161701"
+ },
+ "dosageForm": "SOL",
+ "administrationRoute": "NASINHL",
+ "container": {
+ "name": "vial",
+ "capacity": {
+ "unit": {
+ "scheme": "UNCEFACT",
+ "id": "ml"
+ },
+ "value": "[15,30]"
+ }
+ },
+ "activeIngredients": [
+ {
+ "name": "acetylcysteinum",
+ "strength": {
+ "unit": {
+ "scheme": "UNCEFACT",
+ "id": "g/l"
+ },
+ "value": 100
+ }
+ }
+ ]
+ }
+ ]
+ }
+}
+Más de un principio activo
+En este ejemplo, demostramos cómo utilizar esta extensión para describir un proceso de adquisición de medicamentos de Paraguay. (Puede ver sus datos originales del OCDS.)
+En la pestaña "Suministros requeridos - especificaciones técnicas", artículo 1 del lote 8 ("LOTE N° 8 - ANESTESICOS LOCALES - 2") se describe como:
+| Description | +Technical specifications | +Unit of measurement | +Presentation | +Delivery presentation | +
|---|---|---|---|---|
| Clorhidrato de Bupivacaina Hiperbarica Inyectable | +clorhidrato de bupivacaina 25 mg. + dextrosa 82,5 mg. - solución inyectable | +UNIDAD | +AMPOLLA | +ampollas como minimo de 5 ml. | +
Para el nombre del principio activo, el Anexo 2 del INN Stem Book 2018, describe cómo nombrar las sales ácidas: en este caso, "bupivacainum hydrochloridum".
+A partir de esta información, podemos agregar el dosageForm, administrationRoute, container y activeIngredients.
{
+ "tender": {
+ "items": [
+ {
+ "id": "1",
+ "dosageForm": "SOL",
+ "administrationRoute": "ISINJ",
+ "container": {
+ "name": "amp",
+ "capacity": {
+ "unit": {
+ "scheme": "UNCEFACT",
+ "id": "ml"
+ },
+ "value": "[5,INF["
+ }
+ },
+ "activeIngredients": [
+ {
+ "name": "bupivacainum hydrochloridum",
+ "strength": {
+ "unit": {
+ "scheme": "UNCEFACT",
+ "id": "mg"
+ },
+ "value": 25
+ }
+ },
+ {
+ "name": "dextrosa",
+ "strength": {
+ "unit": {
+ "scheme": "UNCEFACT",
+ "id": "mg"
+ },
+ "value": 82.5
+ }
+ }
+ ],
+ "quantity": 25
+ }
+ ]
+ }
+}
+Estándares relacionados
+Los campos, las definiciones y las listas de códigos utilizados en esta extensión se basan en las siguientes normas que se utilizan habitualmente en los datos sobre compras de medicamentos públicos.
+-
+
- La mayoría de los campos se basan en la definición Medicamentos del Schema.org Community Group y en el Recursos para la Medicación del estándar Fast Healthcare Interoperability Resources (FHIR). +
- La lista de códigos
administrationRoutecontiene los conceptos de nivel superior de la lista de códigos HL7 Vía de Administración, excluyendo cualquier término sinónimo.
+ - La lista de códigos
dosageFormcontiene los conceptos de nivel superior de la lista de códigos HL7 Formulario de pedido de medicamentos, excluyendo las formas específicas de aerosoles.
+ - La lista de códigos
containeres una copia de los códigos y títulos de la lista de códigos Medication Knowledge Package Type de FHIR. Dado que los términos no están definidos en FHIR, las descripciones se han copiado de los términos correspondientes de la base de datos EDQM Términos estándar, reproducidos con el permiso de la Dirección Europea de Calidad del Medicamento y Asistencia Sanitaria del Consejo de Europa (EDQM). La base de datos EDQM Términos estándar no es una lista estática y su contenido puede cambiar con el tiempo; las descripciones se recuperaron el 21 de julio de 2021.
+
Antecedentes
+This extension is based on research with 4 data users and 6 data publishers including public organizations, journalists, medicine price analysts, and software developers for medicine purchase systems from 9 countries in Latin America, Europe, and Africa. The extension includes the most used fields from the different countries.
+Issues
+Reporte issues para esta extensión en el repositorio de ocds-extensiones, poniendo el nombre de la extensión en el título del issue.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/metrics/1.1/README.md b/es/extensions/metrics/1.1/README.md
new file mode 100644
index 000000000..f1cb97d3f
--- /dev/null
+++ b/es/extensions/metrics/1.1/README.md
@@ -0,0 +1,141 @@
+# Extensión de Métricas
+
+La extensión de métricas proporciona un bloque de construcción común para reportar información estructurada de rendimiento de los contratos.
+
+Las métricas están estructuradas como un [cubo de datos OLAP](https://en.wikipedia.org/wiki/OLAP_cube) con cada instancia de `Metric` representando una sola **observación**, categorizada por un número de **dimensiones**.
+
+La extensión de métricas se puede usar en:
+
+- La etapa `planning` para predicciones sobre el proceso de contratación (ejemplo: predicciones de los niveles de demanda)
+- La etapa `tender` para objetivos del proceso de contrataciones (por ejemplo: niveles de disponibilidad objetivo o indicadores clave de rendimiento)
+- Las etapas `awards` y `contracts` para los objetivos acordados con el proveedor adjudicado (por ejemplo, niveles de disponibilidad o KPI)
+- La etapa `implementation` para la información de desempeño actual (por ejemplo: demanda actual, disponibilidad o indicadores claves de rendimiento)
+
+Dónde se usa la extensión métricas para modelar objetivos para un proceso de contratación, el campo `description` puede usarse para indicar si el objetivo es un mínimo o un objetivo recomendando.
+
+## Ejemplo
+
+### Pronósticos
+
+```json
+{
+ "planning": {
+ "forecasts": [
+ {
+ "id": "annualDemand",
+ "title": "Annual Demand",
+ "description": "The annual demand",
+ "observations": [
+ {
+ "id": "1",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 10000,
+ "dimensions": {
+ "vehicleType": "Car"
+ }
+ },
+ {
+ "id": "2",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 1000,
+ "dimensions": {
+ "vehicleType": "Trucks"
+ },
+ "notes": "Simple note"
+ }
+ ]
+ }
+ ]
+ }
+}
+```
+
+### Progreso físico
+
+La extensión de métricas también puede ser utilizada para reportar el progreso físico de un contrato. El siguiente fragmento de JSON muestra como la extensión de métrica puede ser utilizada para reportar el progreso en la construcción de una carretera, tanto por porcentaje completado como por número de kilómetros construidos:
+
+```json
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "implementation": {
+ "metrics": [
+ {
+ "id": "completionPercent",
+ "title": "Construction progress (percent)",
+ "description": "Percent completion of the construction of example highway",
+ "observations": [
+ {
+ "id": "completionPercent-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "25",
+ "unit": {
+ "name": "percent",
+ "id": "P1",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ },
+ {
+ "id": "completionKilometres",
+ "title": "Construction progress (kilometres)",
+ "description": "Progress of construction of example highway measured in kilometres",
+ "observations": [
+ {
+ "id": "completionKilometres-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "15",
+ "unit": {
+ "name": "kilometre",
+ "id": "KMT",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+```
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### 2020-04-24
+
+- Agregar las propiedades `minProperties`, `minItems` y/o `minLength`.
+
+### 2019-03-20
+
+- Establecer `"uniqueItems ": true` en los campos matriz y agregar `"minLength": 1` en los campos de cadena obligatorios.
+- Hacer `Observation.unit` no nulo, como `Item.unit`.
+- Hacer `Observation.dimensions` no nulo (deshacer el cambio anterior).
+
+### 2018-05-08
+
+- Hacer `Metric.id` y `Observation.id` obligatorios para soportar el seguimiento de revisiones y [fusión de listas](http://standard.open-contracting.org/latest/es/schema/merging/#lists)
+
+### 2018-05-01
+
+- Agregar título y descripción a `Observation.period` y `Observation.value`.
+- Hacer que `Observation.dimensions` pueda ser nulo.
diff --git a/es/extensions/metrics/1.1/extension.json b/es/extensions/metrics/1.1/extension.json
new file mode 100644
index 000000000..56af39e2c
--- /dev/null
+++ b/es/extensions/metrics/1.1/extension.json
@@ -0,0 +1,23 @@
+{
+ "name": {
+ "en": "Metrics",
+ "es": "M\u00e9trica"
+ },
+ "description": {
+ "en": "The metrics extension supports publication of forecasts (planning stage), targets (tender stage), agreed performance targets (award and contract stage) and results (implementation stage).",
+ "es": "La extensi\u00f3n de m\u00e9tricas admite la publicaci\u00f3n de pron\u00f3sticos (etapa de planificaci\u00f3n), objetivos (etapa de licitaci\u00f3n), objetivos de desempe\u00f1o acordados (etapa de adjudicaci\u00f3n y contrato) y resultados (etapa de implementaci\u00f3n)."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/metrics/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/metrics/1.1/index.html b/es/extensions/metrics/1.1/index.html
new file mode 100644
index 000000000..d4754f5c5
--- /dev/null
+++ b/es/extensions/metrics/1.1/index.html
@@ -0,0 +1,428 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Medicina +
+ ++ Agrega campos al objeto artículo relevantes para la adquisición de medicamentos. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Item +
+ +
+ The extension defines these fields in the Item object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ activeIngredients
+
+ |
+ + Principios activos + | +
+ Los ingredientes o principios activos, normalmente compuestos químicos o sustancias biológicas. + + |
+ + array of ActiveIngredient objects + | +
+
+ dosageForm
+
+ |
+ + Forma de dosificación + | +
+ La forma de dosificación farmacéutica en la que está disponible el medicamento, de la lista de códigos dosageForm. + + |
+ + string from open dosageForm codelist + | +
+
+ administrationRoute
+
+ |
+ + Vía de administración + | +
+ La vía por la que se puede administrar el medicamento, a partir de la lista de códigos administrationRoute. + + |
+ + string from open administrationRoute codelist + | +
+
+ container
+
+ |
+ + Envase + | +
+ El recipiente inmediato del medicamento. También se conoce como: presentación, forma de presentación, envase. + + |
+ + Container object + | +
+ ActiveIngredient +
+ +
+ The extension defines a new ActiveIngredient object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ name
+
+ |
+ + Nombre + | +
+ The name of the active ingredient. It is recommended to use the lowercase Latin name from the International Nonproprietary Names (INN). Also known as: generic name, drug, substance name, active substance. + + |
+ + string + | +
+
+ strength
+
+ |
+ + Concentración + | +
+ La fuerza del ingrediente o principio activo. También se conoce como: concentración, potencia. + + |
+ + Quantity object + | +
+ Container +
+ +
+ The extension defines a new Container object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ name
+
+ |
+ + Nombre + | +
+ El nombre común del envase de la lista de códigos del container codelist. + + |
+ + string from open container codelist + | +
+
+ capacity
+
+ |
+ + Capacidad + | +
+ La capacidad de almacenamiento del recipiente o envase. + + |
+ + Quantity object + | +
+ Quantity +
+ +
+ The extension defines a new Quantity object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ unit
+
+ |
+ + Unidad + | +
+ La unidad de medida para la cantidad. + + |
+ + SimpleUnit object + | +
+
+ value
+
+ |
+ + Valor + | +
+ La cantidad, como múltiplo de la unidad de medida. La cantidad se expresa en notación de intervalo, por ejemplo "[10,10]" para 10 unidades, "[1,10]" para 1 a 10 unidades, o "[10,INF[" para 10 o más unidades. + + |
+ + string or number + | +
+ SimpleUnit +
+ +
+ The extension defines a new SimpleUnit object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ scheme
+
+ |
+ + Esquema + | +
+ La lista de códigos de la que se toma el identificador de la unidad de medida, utilizando la lista de códigos abierta unitClassificationScheme. Se recomienda utilizar 'UNCEFACT'. + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ id
+
+ |
+ + ID + | +
+ El identificador de la unidad de medida, tomado de la lista de códigos a la que hace referencia el campo |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/metrics/1.1/release-schema.json b/es/extensions/metrics/1.1/release-schema.json
new file mode 100644
index 000000000..50fb5ba0a
--- /dev/null
+++ b/es/extensions/metrics/1.1/release-schema.json
@@ -0,0 +1,257 @@
+{
+ "definitions": {
+ "Planning": {
+ "properties": {
+ "forecasts": {
+ "title": "Pron\u00f3sticos",
+ "description": "Cualquier m\u00e9trica de pron\u00f3stico para los resultados de este proceso de contrataci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "targets": {
+ "title": "Objetivos",
+ "description": "Cualquier m\u00e9trica del objetivo para el resultado de este proceso de contrataci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "agreedMetrics": {
+ "title": "M\u00e9tricas acordadas",
+ "description": "Cualquier m\u00e9trica objetivo establecida como parte de la adjudicaci\u00f3n del contrato.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "agreedMetrics": {
+ "title": "M\u00e9tricas acordadas",
+ "description": "Cualquier m\u00e9trica objetivo establecida como parte de los documentos del contrato.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Implementation": {
+ "properties": {
+ "metrics": {
+ "title": "M\u00e9trica",
+ "description": "Resultados reportados de la entrega de los bienes, obras o servicios contratados.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Metric": {
+ "title": "M\u00e9trica",
+ "description": "Las m\u00e9tricas se usan para establecer objetivos y resultados de un proceso de contrataci\u00f3n. Durante las secciones de planeaci\u00f3n y licitaci\u00f3n, una m\u00e9trica indica los resultados esperados. En las secciones adjudicaci\u00f3n y contrato se indican los resultados adjudicados / contratados. En la secci\u00f3n de implementaci\u00f3n se utiliza para proporcionar actualizaciones sobre los resultados realmente entregados, tambi\u00e9n conocidos como rendimiento.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador para esta m\u00e9trica. En algunos casos, esto puede extraerse de una lista de c\u00f3digos de m\u00e9tricas requerida para este tipo de proceso de contrataci\u00f3n, o en otros casos puede ser un identificador arbitrario.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo",
+ "description": "El t\u00edtulo de esta m\u00e9trica",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una breve descripci\u00f3n de la m\u00e9trica. Esto puede incluir peque\u00f1os detalles de los m\u00e9todos de medici\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "observations": {
+ "title": "Observaciones",
+ "description": "Una lista de valores objetivo o reales para esta m\u00e9trica.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Observation"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Observation": {
+ "title": "Observaci\u00f3n",
+ "description": "Una observaci\u00f3n real u objetivo. Las observaciones deben incluir un valor (para m\u00e9tricas financieras) o una medida (para otras m\u00e9tricas).",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador local para esta observaci\u00f3n espec\u00edfica. Esto puede ser un identificador arbitrario, o podr\u00eda ser un compuesto del identificador de m\u00e9trica, y la fecha y otras dimensiones de esta observaci\u00f3n.",
+ "type": "string",
+ "minLength": 1
+ },
+ "period": {
+ "title": "Periodo",
+ "description": "El per\u00edodo en que esta observaci\u00f3n se mide.",
+ "$ref": "#/definitions/Period"
+ },
+ "value": {
+ "title": "Valor",
+ "description": "Para m\u00e9tricas financieras, el valor de este pron\u00f3stico, objetivo u observaci\u00f3n real.",
+ "$ref": "#/definitions/Value"
+ },
+ "measure": {
+ "title": "Medida",
+ "description": "Para las m\u00e9tricas no financieras, la medida de este pron\u00f3stico, objetivo o observaci\u00f3n real. Las medidas pueden proporcionarse como texto libre o valores num\u00e9ricos.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "unit": {
+ "title": "Unidad",
+ "description": "Unidad",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Nombre de la unidad",
+ "description": "El nombre de la unidad.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "scheme": {
+ "title": "Esquema",
+ "description": "La lista de la que se toman los identificadores de las unidades de medida. Se recomienda el uso del esquema 'UNCEFACT' para la lista Recomendaci\u00f3n 20 de CEFACT/ONU de \"C\u00f3digos de unidades de medida utilizados en el comercio internacional\".",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "El identificador de la lista de c\u00f3digos al que se hace referencia en el campo del esquema. Por ejemplo, con UNCEFACT, es el valor de la columna 'Common Code'. A partir de este identificador, las aplicaciones pueden buscar el nombre o s\u00edmbolo legible por el ser humano para esta unidad de medida.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "uri": {
+ "title": "URI",
+ "description": "Si el esquema utilizado provee una URI legible por computadora para esta unidad de medici\u00f3n, \u00e9sta puede proporcionarse.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ },
+ "minProperties": 1
+ },
+ "dimensions": {
+ "title": "Dimensiones",
+ "description": "Cualquier n\u00famero de dimensiones se puede registrar dentro de este objeto. Los nombres de dimensiones deben seguir las convenciones de OCDS de camelCase.",
+ "type": "object",
+ "patternProperties": {
+ "^.*": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "notes": {
+ "title": "Notas",
+ "description": "Cualquier nota sobre esta observaci\u00f3n. Esto puede incluir informaci\u00f3n para aclaraci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "relatedImplementationMilestone": {
+ "title": "Hito de implementaci\u00f3n relacionado",
+ "description": "Un enlace al hito en la secci\u00f3n de implementaci\u00f3n de OCDS a la cual se le relaciona esta observaci\u00f3n de pron\u00f3stico, objetivo o real.",
+ "$ref": "#/definitions/MilestoneReference"
+ }
+ },
+ "minProperties": 1
+ },
+ "MilestoneReference": {
+ "title": "Referencia del hito",
+ "description": "Un bloque usado para hacer referencia a un hito, incluyendo el ID y el t\u00edtulo del hito que al que se hace referencia.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID del hito",
+ "description": "El ID del hito que se hace referencia, debe coincidir con el identificador de un hito descrito en alguna otra parte de una entrega sobre este proceso de contrataci\u00f3n.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo del hito",
+ "description": "El t\u00edtulo del hito al que se hace referencia, debe coincidir con el t\u00edtulo de un hito descrito en alguna otra parte en una entrega sobre este proceso de contrataci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/metrics/1.1/schema/index.html b/es/extensions/metrics/1.1/schema/index.html
new file mode 100644
index 000000000..bc45c8110
--- /dev/null
+++ b/es/extensions/metrics/1.1/schema/index.html
@@ -0,0 +1,864 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Métrica +
+ ++ La extensión de métricas admite la publicación de pronósticos (etapa de planificación), objetivos (etapa de licitación), objetivos de desempeño acordados (etapa de adjudicación y contrato) y resultados (etapa de implementación). +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La extensión de métricas proporciona un bloque de construcción común para reportar información estructurada de rendimiento de los contratos.
+Las métricas están estructuradas como un cubo de datos OLAP con cada instancia de Metric representando una sola observación, categorizada por un número de dimensiones.
La extensión de métricas se puede usar en:
+-
+
- La etapa
planningpara predicciones sobre el proceso de contratación (ejemplo: predicciones de los niveles de demanda)
+ - La etapa
tenderpara objetivos del proceso de contrataciones (por ejemplo: niveles de disponibilidad objetivo o indicadores clave de rendimiento)
+ - Las etapas
awardsycontractspara los objetivos acordados con el proveedor adjudicado (por ejemplo, niveles de disponibilidad o KPI)
+ - La etapa
implementationpara la información de desempeño actual (por ejemplo: demanda actual, disponibilidad o indicadores claves de rendimiento)
+
Dónde se usa la extensión métricas para modelar objetivos para un proceso de contratación, el campo description puede usarse para indicar si el objetivo es un mínimo o un objetivo recomendando.
Ejemplo
+Pronósticos
+{
+ "planning": {
+ "forecasts": [
+ {
+ "id": "annualDemand",
+ "title": "Annual Demand",
+ "description": "The annual demand",
+ "observations": [
+ {
+ "id": "1",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 10000,
+ "dimensions": {
+ "vehicleType": "Car"
+ }
+ },
+ {
+ "id": "2",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 1000,
+ "dimensions": {
+ "vehicleType": "Trucks"
+ },
+ "notes": "Simple note"
+ }
+ ]
+ }
+ ]
+ }
+}
+Progreso físico
+La extensión de métricas también puede ser utilizada para reportar el progreso físico de un contrato. El siguiente fragmento de JSON muestra como la extensión de métrica puede ser utilizada para reportar el progreso en la construcción de una carretera, tanto por porcentaje completado como por número de kilómetros construidos:
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "implementation": {
+ "metrics": [
+ {
+ "id": "completionPercent",
+ "title": "Construction progress (percent)",
+ "description": "Percent completion of the construction of example highway",
+ "observations": [
+ {
+ "id": "completionPercent-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "25",
+ "unit": {
+ "name": "percent",
+ "id": "P1",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ },
+ {
+ "id": "completionKilometres",
+ "title": "Construction progress (kilometres)",
+ "description": "Progress of construction of example highway measured in kilometres",
+ "observations": [
+ {
+ "id": "completionKilometres-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "15",
+ "unit": {
+ "name": "kilometre",
+ "id": "KMT",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-03-20
+-
+
- Establecer
"uniqueItems ": trueen los campos matriz y agregar"minLength": 1en los campos de cadena obligatorios.
+ - Hacer
Observation.unitno nulo, comoItem.unit.
+ - Hacer
Observation.dimensionsno nulo (deshacer el cambio anterior).
+
2018-05-08
+-
+
- Hacer
Metric.idyObservation.idobligatorios para soportar el seguimiento de revisiones y fusión de listas
+
2018-05-01
+-
+
- Agregar título y descripción a
Observation.periodyObservation.value.
+ - Hacer que
Observation.dimensionspueda ser nulo.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/metrics/index.html b/es/extensions/metrics/index.html
new file mode 100644
index 000000000..a8c6897f4
--- /dev/null
+++ b/es/extensions/metrics/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Métrica +
+ ++ La extensión de métricas admite la publicación de pronósticos (etapa de planificación), objetivos (etapa de licitación), objetivos de desempeño acordados (etapa de adjudicación y contrato) y resultados (etapa de implementación). +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Planning +
+ +
+ The extension defines these fields in the Planning object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ forecasts
+
+ |
+ + Pronósticos + | +
+ Cualquier métrica de pronóstico para los resultados de este proceso de contratación. + + |
+ + array of Metric objects + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ targets
+
+ |
+ + Objetivos + | +
+ Cualquier métrica del objetivo para el resultado de este proceso de contratación. + + |
+ + array of Metric objects + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Métricas acordadas + | +
+ Cualquier métrica objetivo establecida como parte de la adjudicación del contrato. + + |
+ + array of Metric objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Métricas acordadas + | +
+ Cualquier métrica objetivo establecida como parte de los documentos del contrato. + + |
+ + array of Metric objects + | +
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ metrics
+
+ |
+ + Métrica + | +
+ Resultados reportados de la entrega de los bienes, obras o servicios contratados. + + |
+ + array of Metric objects + | +
+ Metric +
+ +
+ The extension defines a new Metric object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador para esta métrica. En algunos casos, esto puede extraerse de una lista de códigos de métricas requerida para este tipo de proceso de contratación, o en otros casos puede ser un identificador arbitrario. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título + | +
+ El título de esta métrica + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Una breve descripción de la métrica. Esto puede incluir pequeños detalles de los métodos de medición. + + |
+ + string + | +
+
+ observations
+
+ |
+ + Observaciones + | +
+ Una lista de valores objetivo o reales para esta métrica. + + |
+ + array of Observation objects + | +
+ Observation +
+ +
+ The extension defines a new Observation object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador local para esta observación específica. Esto puede ser un identificador arbitrario, o podría ser un compuesto del identificador de métrica, y la fecha y otras dimensiones de esta observación. + + |
+ + string + | +
+
+ period
+
+ |
+ + Periodo + | +
+ El período en que esta observación se mide. + + |
+ + Period object + | +
+
+ value
+
+ |
+ + Valor + | +
+ Para métricas financieras, el valor de este pronóstico, objetivo u observación real. + + |
+ + Value object + | +
+
+ measure
+
+ |
+ + Medida + | +
+ Para las métricas no financieras, la medida de este pronóstico, objetivo o observación real. Las medidas pueden proporcionarse como texto libre o valores numéricos. + + |
+ + string or number + | +
+
+ unit
+
+ |
+ + Unidad + | +
+ Unidad + + |
+ + object + | +
+
+ unit.
+ |
+ + Nombre de la unidad + | +
+ El nombre de la unidad. + + |
+ + string + | +
+
+ unit.
+ |
+ + Esquema + | +
+ La lista de la que se toman los identificadores de las unidades de medida. Se recomienda el uso del esquema 'UNCEFACT' para la lista Recomendación 20 de CEFACT/ONU de "Códigos de unidades de medida utilizados en el comercio internacional". + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ unit.
+ |
+ + ID + | +
+ El identificador de la lista de códigos al que se hace referencia en el campo del esquema. Por ejemplo, con UNCEFACT, es el valor de la columna 'Common Code'. A partir de este identificador, las aplicaciones pueden buscar el nombre o símbolo legible por el ser humano para esta unidad de medida. + + |
+ + string + | +
+
+ unit.
+ |
+ + URI + | +
+ Si el esquema utilizado provee una URI legible por computadora para esta unidad de medición, ésta puede proporcionarse. + + |
+ + string + | +
+
+ dimensions
+
+ |
+ + Dimensiones + | +
+ Cualquier número de dimensiones se puede registrar dentro de este objeto. Los nombres de dimensiones deben seguir las convenciones de OCDS de camelCase. + + |
+ + object + | +
+
+ dimensions.
+ |
+ + + | ++ + | ++ string + | +
+
+ notes
+
+ |
+ + Notas + | +
+ Cualquier nota sobre esta observación. Esto puede incluir información para aclaración. + + |
+ + string + | +
+
+ relatedImplementationMilestone
+
+ |
+ + Hito de implementación relacionado + | +
+ Un enlace al hito en la sección de implementación de OCDS a la cual se le relaciona esta observación de pronóstico, objetivo o real. + + |
+ + MilestoneReference object + | +
+ MilestoneReference +
+ +
+ The extension defines a new MilestoneReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID del hito + | +
+ El ID del hito que se hace referencia, debe coincidir con el identificador de un hito descrito en alguna otra parte de una entrega sobre este proceso de contratación. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título del hito + | +
+ El título del hito al que se hace referencia, debe coincidir con el título de un hito descrito en alguna otra parte en una entrega sobre este proceso de contratación. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/metrics/1.1/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/metrics/master/release-schema.json b/es/extensions/metrics/master/release-schema.json
new file mode 100644
index 000000000..50fb5ba0a
--- /dev/null
+++ b/es/extensions/metrics/master/release-schema.json
@@ -0,0 +1,257 @@
+{
+ "definitions": {
+ "Planning": {
+ "properties": {
+ "forecasts": {
+ "title": "Pron\u00f3sticos",
+ "description": "Cualquier m\u00e9trica de pron\u00f3stico para los resultados de este proceso de contrataci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "targets": {
+ "title": "Objetivos",
+ "description": "Cualquier m\u00e9trica del objetivo para el resultado de este proceso de contrataci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "agreedMetrics": {
+ "title": "M\u00e9tricas acordadas",
+ "description": "Cualquier m\u00e9trica objetivo establecida como parte de la adjudicaci\u00f3n del contrato.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "agreedMetrics": {
+ "title": "M\u00e9tricas acordadas",
+ "description": "Cualquier m\u00e9trica objetivo establecida como parte de los documentos del contrato.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Implementation": {
+ "properties": {
+ "metrics": {
+ "title": "M\u00e9trica",
+ "description": "Resultados reportados de la entrega de los bienes, obras o servicios contratados.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Metric": {
+ "title": "M\u00e9trica",
+ "description": "Las m\u00e9tricas se usan para establecer objetivos y resultados de un proceso de contrataci\u00f3n. Durante las secciones de planeaci\u00f3n y licitaci\u00f3n, una m\u00e9trica indica los resultados esperados. En las secciones adjudicaci\u00f3n y contrato se indican los resultados adjudicados / contratados. En la secci\u00f3n de implementaci\u00f3n se utiliza para proporcionar actualizaciones sobre los resultados realmente entregados, tambi\u00e9n conocidos como rendimiento.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador para esta m\u00e9trica. En algunos casos, esto puede extraerse de una lista de c\u00f3digos de m\u00e9tricas requerida para este tipo de proceso de contrataci\u00f3n, o en otros casos puede ser un identificador arbitrario.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo",
+ "description": "El t\u00edtulo de esta m\u00e9trica",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una breve descripci\u00f3n de la m\u00e9trica. Esto puede incluir peque\u00f1os detalles de los m\u00e9todos de medici\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "observations": {
+ "title": "Observaciones",
+ "description": "Una lista de valores objetivo o reales para esta m\u00e9trica.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Observation"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Observation": {
+ "title": "Observaci\u00f3n",
+ "description": "Una observaci\u00f3n real u objetivo. Las observaciones deben incluir un valor (para m\u00e9tricas financieras) o una medida (para otras m\u00e9tricas).",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador local para esta observaci\u00f3n espec\u00edfica. Esto puede ser un identificador arbitrario, o podr\u00eda ser un compuesto del identificador de m\u00e9trica, y la fecha y otras dimensiones de esta observaci\u00f3n.",
+ "type": "string",
+ "minLength": 1
+ },
+ "period": {
+ "title": "Periodo",
+ "description": "El per\u00edodo en que esta observaci\u00f3n se mide.",
+ "$ref": "#/definitions/Period"
+ },
+ "value": {
+ "title": "Valor",
+ "description": "Para m\u00e9tricas financieras, el valor de este pron\u00f3stico, objetivo u observaci\u00f3n real.",
+ "$ref": "#/definitions/Value"
+ },
+ "measure": {
+ "title": "Medida",
+ "description": "Para las m\u00e9tricas no financieras, la medida de este pron\u00f3stico, objetivo o observaci\u00f3n real. Las medidas pueden proporcionarse como texto libre o valores num\u00e9ricos.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "unit": {
+ "title": "Unidad",
+ "description": "Unidad",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Nombre de la unidad",
+ "description": "El nombre de la unidad.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "scheme": {
+ "title": "Esquema",
+ "description": "La lista de la que se toman los identificadores de las unidades de medida. Se recomienda el uso del esquema 'UNCEFACT' para la lista Recomendaci\u00f3n 20 de CEFACT/ONU de \"C\u00f3digos de unidades de medida utilizados en el comercio internacional\".",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "El identificador de la lista de c\u00f3digos al que se hace referencia en el campo del esquema. Por ejemplo, con UNCEFACT, es el valor de la columna 'Common Code'. A partir de este identificador, las aplicaciones pueden buscar el nombre o s\u00edmbolo legible por el ser humano para esta unidad de medida.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "uri": {
+ "title": "URI",
+ "description": "Si el esquema utilizado provee una URI legible por computadora para esta unidad de medici\u00f3n, \u00e9sta puede proporcionarse.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ },
+ "minProperties": 1
+ },
+ "dimensions": {
+ "title": "Dimensiones",
+ "description": "Cualquier n\u00famero de dimensiones se puede registrar dentro de este objeto. Los nombres de dimensiones deben seguir las convenciones de OCDS de camelCase.",
+ "type": "object",
+ "patternProperties": {
+ "^.*": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "notes": {
+ "title": "Notas",
+ "description": "Cualquier nota sobre esta observaci\u00f3n. Esto puede incluir informaci\u00f3n para aclaraci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "relatedImplementationMilestone": {
+ "title": "Hito de implementaci\u00f3n relacionado",
+ "description": "Un enlace al hito en la secci\u00f3n de implementaci\u00f3n de OCDS a la cual se le relaciona esta observaci\u00f3n de pron\u00f3stico, objetivo o real.",
+ "$ref": "#/definitions/MilestoneReference"
+ }
+ },
+ "minProperties": 1
+ },
+ "MilestoneReference": {
+ "title": "Referencia del hito",
+ "description": "Un bloque usado para hacer referencia a un hito, incluyendo el ID y el t\u00edtulo del hito que al que se hace referencia.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID del hito",
+ "description": "El ID del hito que se hace referencia, debe coincidir con el identificador de un hito descrito en alguna otra parte de una entrega sobre este proceso de contrataci\u00f3n.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo del hito",
+ "description": "El t\u00edtulo del hito al que se hace referencia, debe coincidir con el t\u00edtulo de un hito descrito en alguna otra parte en una entrega sobre este proceso de contrataci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/metrics/master/schema/index.html b/es/extensions/metrics/master/schema/index.html
new file mode 100644
index 000000000..c178f50fe
--- /dev/null
+++ b/es/extensions/metrics/master/schema/index.html
@@ -0,0 +1,865 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Métrica +
+ ++ La extensión de métricas admite la publicación de pronósticos (etapa de planificación), objetivos (etapa de licitación), objetivos de desempeño acordados (etapa de adjudicación y contrato) y resultados (etapa de implementación). +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La extensión de métricas proporciona un bloque de construcción común para reportar información estructurada de rendimiento de los contratos.
+Las métricas están estructuradas como un cubo de datos OLAP con cada instancia de Metric representando una sola observación, categorizada por un número de dimensiones.
La extensión de métricas se puede usar en:
+-
+
- La etapa
planningpara predicciones sobre el proceso de contratación (ejemplo: predicciones de los niveles de demanda)
+ - La etapa
tenderpara objetivos del proceso de contrataciones (por ejemplo: niveles de disponibilidad objetivo o indicadores clave de rendimiento)
+ - Las etapas
awardsycontractspara los objetivos acordados con el proveedor adjudicado (por ejemplo, niveles de disponibilidad o KPI)
+ - La etapa
implementationpara la información de desempeño actual (por ejemplo: demanda actual, disponibilidad o indicadores claves de rendimiento)
+
Dónde se usa la extensión métricas para modelar objetivos para un proceso de contratación, el campo description puede usarse para indicar si el objetivo es un mínimo o un objetivo recomendando.
Ejemplo
+Pronósticos
+{
+ "planning": {
+ "forecasts": [
+ {
+ "id": "annualDemand",
+ "title": "Annual Demand",
+ "description": "The annual demand",
+ "observations": [
+ {
+ "id": "1",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 10000,
+ "dimensions": {
+ "vehicleType": "Car"
+ }
+ },
+ {
+ "id": "2",
+ "period": {
+ "startDate": "2015-01-01T00:00:00Z",
+ "endDate": "2015-12-31T23:59:59Z"
+ },
+ "measure": 1000,
+ "dimensions": {
+ "vehicleType": "Trucks"
+ },
+ "notes": "Simple note"
+ }
+ ]
+ }
+ ]
+ }
+}
+Progreso físico
+La extensión de métricas también puede ser utilizada para reportar el progreso físico de un contrato. El siguiente fragmento de JSON muestra como la extensión de métrica puede ser utilizada para reportar el progreso en la construcción de una carretera, tanto por porcentaje completado como por número de kilómetros construidos:
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "implementation": {
+ "metrics": [
+ {
+ "id": "completionPercent",
+ "title": "Construction progress (percent)",
+ "description": "Percent completion of the construction of example highway",
+ "observations": [
+ {
+ "id": "completionPercent-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "25",
+ "unit": {
+ "name": "percent",
+ "id": "P1",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ },
+ {
+ "id": "completionKilometres",
+ "title": "Construction progress (kilometres)",
+ "description": "Progress of construction of example highway measured in kilometres",
+ "observations": [
+ {
+ "id": "completionKilometres-2016-Q1",
+ "period": {
+ "startDate": "2016-03-31T23:59:59Z",
+ "endDate": "2016-03-31T23:59:59Z"
+ },
+ "measure": "15",
+ "unit": {
+ "name": "kilometre",
+ "id": "KMT",
+ "scheme": "UNCEFACT"
+ }
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-03-20
+-
+
- Establecer
"uniqueItems ": trueen los campos matriz y agregar"minLength": 1en los campos de cadena obligatorios.
+ - Hacer
Observation.unitno nulo, comoItem.unit.
+ - Hacer
Observation.dimensionsno nulo (deshacer el cambio anterior).
+
2018-05-08
+-
+
- Hacer
Metric.idyObservation.idobligatorios para soportar el seguimiento de revisiones y fusión de listas
+
2018-05-01
+-
+
- Agregar título y descripción a
Observation.periodyObservation.value.
+ - Hacer que
Observation.dimensionspueda ser nulo.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/metrics/v1.1/README.md b/es/extensions/metrics/v1.1/README.md
new file mode 100644
index 000000000..7acc87ec7
--- /dev/null
+++ b/es/extensions/metrics/v1.1/README.md
@@ -0,0 +1,57 @@
+# Extensión de Métricas
+
+La extensión de métricas proporciona un bloque de construcción común para reportar información estructurada de rendimiento de los contratos.
+
+Las métricas están estructuradas como un [cubo de datos OLAP](https://en.wikipedia.org/wiki/OLAP_cube) con cada instancia de `Metric` representando una sola **observation**, categorizada por un número de **dimensions**.
+
+```json
+{
+ "metrics":[
+ {
+ "id":"annualDemand",
+ "title":"Annual Demand",
+ "description":"The annual demand",
+ "observations":[
+ {
+ "period":{
+ "startDate":"2015-01-01T00:00:00Z",
+ "endDate":"2015-12-31T23:59:59Z"
+ },
+ "quantity":"10000",
+ "dimensions":{
+ "vehicleType":"Car"
+ }
+ },
+ {
+ "period":{
+ "startDate":"2015-01-01T00:00:00Z",
+ "endDate":"2015-12-31T23:59:59Z"
+ },
+ "quantity":"1000",
+ "dimensions":{
+ "vehicleType":"Trucks"
+ },
+ "note":"Simple note"
+ }
+ ]
+ },
+ {
+
+ }
+ ]
+}
+```
+
+## Uso con requerimientos
+
+Las métricas se pueden utilizar junto con la **extensión de requisitos** que agregará una propiedad 'relatedRequirementID' a las métricas.
+
+Con la extensión de requisitos, las ofertas, adjudicaciones y contratos pueden incluir un `requirementResponse` que indica los valores contra cada métrica que un proveedor desea cumplir.
+
+Esto puede permitir un cierto grado de comparación entre el rendimiento previsto en las fases de licitación, adjudicación, contrato y ejecución.
+
+## Por hacer
+
+- \[ \] Comprobar la sintaxis del esquema oneOf para value **o**quantity
+- \[ \] Agregar relatedRequirementID a la extensión de requisitos
+- \[ \] Validar actualizaciones de esquema
diff --git a/es/extensions/metrics/v1.1/extension.json b/es/extensions/metrics/v1.1/extension.json
new file mode 100644
index 000000000..0813d55bb
--- /dev/null
+++ b/es/extensions/metrics/v1.1/extension.json
@@ -0,0 +1,15 @@
+{
+ "name": {
+ "en": "Metrics",
+ "es": "M\u00e9trica"
+ },
+ "description": {
+ "en": "The metrics extension supports publication of forecasts (planning stage), targets (tender stage), agreed performance targets (award and contract stage) and results (implementation stage).",
+ "es": "La extensi\u00f3n de m\u00e9tricas admite la publicaci\u00f3n de pron\u00f3sticos (etapa de planificaci\u00f3n), objetivos (etapa de licitaci\u00f3n), objetivos de desempe\u00f1o acordados (etapa de adjudicaci\u00f3n y contrato) y resultados (etapa de implementaci\u00f3n)."
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "dependencies": [],
+ "documentationUrl": {}
+}
diff --git a/es/extensions/metrics/v1.1/index.html b/es/extensions/metrics/v1.1/index.html
new file mode 100644
index 000000000..384d18290
--- /dev/null
+++ b/es/extensions/metrics/v1.1/index.html
@@ -0,0 +1,315 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Métrica +
+ ++ La extensión de métricas admite la publicación de pronósticos (etapa de planificación), objetivos (etapa de licitación), objetivos de desempeño acordados (etapa de adjudicación y contrato) y resultados (etapa de implementación). +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Planning +
+ +
+ The extension defines these fields in the Planning object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ forecasts
+
+ |
+ + Pronósticos + | +
+ Cualquier métrica de pronóstico para los resultados de este proceso de contratación. + + |
+ + array of Metric objects + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ targets
+
+ |
+ + Objetivos + | +
+ Cualquier métrica del objetivo para el resultado de este proceso de contratación. + + |
+ + array of Metric objects + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Métricas acordadas + | +
+ Cualquier métrica objetivo establecida como parte de la adjudicación del contrato. + + |
+ + array of Metric objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Métricas acordadas + | +
+ Cualquier métrica objetivo establecida como parte de los documentos del contrato. + + |
+ + array of Metric objects + | +
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ metrics
+
+ |
+ + Métrica + | +
+ Resultados reportados de la entrega de los bienes, obras o servicios contratados. + + |
+ + array of Metric objects + | +
+ Metric +
+ +
+ The extension defines a new Metric object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador para esta métrica. En algunos casos, esto puede extraerse de una lista de códigos de métricas requerida para este tipo de proceso de contratación, o en otros casos puede ser un identificador arbitrario. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título + | +
+ El título de esta métrica + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Una breve descripción de la métrica. Esto puede incluir pequeños detalles de los métodos de medición. + + |
+ + string + | +
+
+ observations
+
+ |
+ + Observaciones + | +
+ Una lista de valores objetivo o reales para esta métrica. + + |
+ + array of Observation objects + | +
+ Observation +
+ +
+ The extension defines a new Observation object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador local para esta observación específica. Esto puede ser un identificador arbitrario, o podría ser un compuesto del identificador de métrica, y la fecha y otras dimensiones de esta observación. + + |
+ + string + | +
+
+ period
+
+ |
+ + Periodo + | +
+ El período en que esta observación se mide. + + |
+ + Period object + | +
+
+ value
+
+ |
+ + Valor + | +
+ Para métricas financieras, el valor de este pronóstico, objetivo u observación real. + + |
+ + Value object + | +
+
+ measure
+
+ |
+ + Medida + | +
+ Para las métricas no financieras, la medida de este pronóstico, objetivo o observación real. Las medidas pueden proporcionarse como texto libre o valores numéricos. + + |
+ + string or number + | +
+
+ unit
+
+ |
+ + Unidad + | +
+ Unidad + + |
+ + object + | +
+
+ unit.
+ |
+ + Nombre de la unidad + | +
+ El nombre de la unidad. + + |
+ + string + | +
+
+ unit.
+ |
+ + Esquema + | +
+ La lista de la que se toman los identificadores de las unidades de medida. Se recomienda el uso del esquema 'UNCEFACT' para la lista Recomendación 20 de CEFACT/ONU de "Códigos de unidades de medida utilizados en el comercio internacional". + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ unit.
+ |
+ + ID + | +
+ El identificador de la lista de códigos al que se hace referencia en el campo del esquema. Por ejemplo, con UNCEFACT, es el valor de la columna 'Common Code'. A partir de este identificador, las aplicaciones pueden buscar el nombre o símbolo legible por el ser humano para esta unidad de medida. + + |
+ + string + | +
+
+ unit.
+ |
+ + URI + | +
+ Si el esquema utilizado provee una URI legible por computadora para esta unidad de medición, ésta puede proporcionarse. + + |
+ + string + | +
+
+ dimensions
+
+ |
+ + Dimensiones + | +
+ Cualquier número de dimensiones se puede registrar dentro de este objeto. Los nombres de dimensiones deben seguir las convenciones de OCDS de camelCase. + + |
+ + object + | +
+
+ dimensions.
+ |
+ + + | ++ + | ++ string + | +
+
+ notes
+
+ |
+ + Notas + | +
+ Cualquier nota sobre esta observación. Esto puede incluir información para aclaración. + + |
+ + string + | +
+
+ relatedImplementationMilestone
+
+ |
+ + Hito de implementación relacionado + | +
+ Un enlace al hito en la sección de implementación de OCDS a la cual se le relaciona esta observación de pronóstico, objetivo o real. + + |
+ + MilestoneReference object + | +
+ MilestoneReference +
+ +
+ The extension defines a new MilestoneReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID del hito + | +
+ El ID del hito que se hace referencia, debe coincidir con el identificador de un hito descrito en alguna otra parte de una entrega sobre este proceso de contratación. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título del hito + | +
+ El título del hito al que se hace referencia, debe coincidir con el título de un hito descrito en alguna otra parte en una entrega sobre este proceso de contratación. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/metrics/v1.1/release-schema.json b/es/extensions/metrics/v1.1/release-schema.json
new file mode 100644
index 000000000..cdd08ae20
--- /dev/null
+++ b/es/extensions/metrics/v1.1/release-schema.json
@@ -0,0 +1,220 @@
+{
+ "definitions": {
+ "Planning": {
+ "properties": {
+ "forecasts": {
+ "type": "array",
+ "title": "Pron\u00f3sticos",
+ "description": "Cualquier m\u00e9trica de pron\u00f3stico para los resultados de este proceso de contrataci\u00f3n.",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ }
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "targets": {
+ "type": "array",
+ "title": "Objetivos",
+ "description": "Cualquier m\u00e9trica del objetivo para el resultado de este proceso de contrataci\u00f3n.",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ }
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "agreedMetrics": {
+ "type": "array",
+ "title": "M\u00e9tricas acordadas",
+ "description": "Cualquier m\u00e9trica objetivo establecida como parte de la adjudicaci\u00f3n del contrato.",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ }
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "agreedMetrics": {
+ "type": "array",
+ "title": "M\u00e9tricas acordadas",
+ "description": "Cualquier m\u00e9trica objetivo establecida como parte de los documentos del contrato.",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ }
+ }
+ }
+ },
+ "Implementation": {
+ "properties": {
+ "metrics": {
+ "type": "array",
+ "title": "M\u00e9trica",
+ "description": "Resultados reportados de la entrega de los bienes, obras o servicios contratados.",
+ "items": {
+ "$ref": "#/definitions/Metric"
+ }
+ }
+ }
+ },
+ "Metric": {
+ "type": "object",
+ "title": "M\u00e9trica",
+ "description": "Las m\u00e9tricas se usan para establecer objetivos y resultados de un proceso de contrataci\u00f3n. Durante las secciones de planeaci\u00f3n y licitaci\u00f3n, una m\u00e9trica indica los resultados esperados. En las secciones adjudicaci\u00f3n y contrato se indican los resultados adjudicados / contratados. En la secci\u00f3n de implementaci\u00f3n se utiliza para proporcionar actualizaciones sobre los resultados realmente entregados, tambi\u00e9n conocidos como rendimiento.",
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador para esta m\u00e9trica. En algunos casos, esto puede extraerse de una lista de c\u00f3digos de m\u00e9tricas requerida para este tipo de proceso de contrataci\u00f3n, o en otros casos puede ser un identificador arbitrario.",
+ "type": [
+ "string"
+ ]
+ },
+ "title": {
+ "title": "T\u00edtulo",
+ "description": "El t\u00edtulo de esta m\u00e9trica",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una breve descripci\u00f3n de la m\u00e9trica. Esto puede incluir peque\u00f1os detalles de los m\u00e9todos de medici\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "observations": {
+ "type": "array",
+ "title": "Observaciones",
+ "description": "Una lista de valores objetivo o reales para esta m\u00e9trica.",
+ "items": {
+ "$ref": "#/definitions/Observation"
+ }
+ }
+ }
+ },
+ "Observation": {
+ "type": "object",
+ "title": "Observaci\u00f3n",
+ "description": "Una observaci\u00f3n real u objetivo. Las observaciones deben incluir un valor (para m\u00e9tricas financieras) o una medida (para otras m\u00e9tricas).",
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador local para esta observaci\u00f3n espec\u00edfica. Esto puede ser un identificador arbitrario, o podr\u00eda ser un compuesto del identificador de m\u00e9trica, y la fecha y otras dimensiones de esta observaci\u00f3n.",
+ "type": "string"
+ },
+ "period": {
+ "$ref": "#/definitions/Period"
+ },
+ "value": {
+ "$ref": "#/definitions/Value"
+ },
+ "measure": {
+ "title": "Medida de observaci\u00f3n",
+ "description": "Para las m\u00e9tricas no financieras, la medida de este pron\u00f3stico, objetivo o observaci\u00f3n real. Las medidas pueden proporcionarse como texto libre o valores num\u00e9ricos.",
+ "type": [
+ "string",
+ "number",
+ "null"
+ ]
+ },
+ "unit": {
+ "type": [
+ "object",
+ "null"
+ ],
+ "title": "Unidad",
+ "description": "Unidad",
+ "properties": {
+ "name": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "title": "Nombre de la unidad",
+ "description": "El nombre de la unidad."
+ },
+ "scheme": {
+ "title": "Esquema",
+ "description": "La lista desde la cual se toman los identificadores de unidades de medida. Esta debe ser una entrada en la lista de c\u00f3digos unitClassificationScheme. Se recomienda el uso del esquema \"UNCEFACT\" para la recomendaci\u00f3n 20 del CEFACT-ONU de \"C\u00f3digos para unidades de medida utilizadas en el comercio internacional\".",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true
+ },
+ "id": {
+ "title": "ID",
+ "description": "El identificador de la lista de c\u00f3digos se hace referencia en la propiedad de esquema. Por ejemplo, con UNCEFACT, este es el valor de la columna \"Common Code\". A partir de este identificador, las aplicaciones pueden buscar el nombre o s\u00edmbolo legible para humanos para esta unidad de medida.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "uri": {
+ "title": "URI",
+ "description": "Si el esquema utilizado provee una URI legible por computadora para esta unidad de medici\u00f3n, \u00e9sta puede proporcionarse.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ }
+ },
+ "dimensions": {
+ "type": "object",
+ "title": "Dimensiones",
+ "description": "Cualquier n\u00famero de dimensiones se puede registrar dentro de este objeto. Los nombres de dimensiones deben seguir las convenciones de OCDS de camelCase.",
+ "patternProperties": {
+ "^.*": {
+ "type": "string"
+ }
+ }
+ },
+ "notes": {
+ "title": "Notas",
+ "description": "Cualquier nota sobre esta observaci\u00f3n. Esto puede incluir informaci\u00f3n para aclaraci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "relatedImplementationMilestone": {
+ "title": "Hito de implementaci\u00f3n relacionado",
+ "description": "Un enlace al hito en la secci\u00f3n de implementaci\u00f3n de OCDS a la cual se le relaciona esta observaci\u00f3n de pron\u00f3stico, objetivo o real.",
+ "$ref": "#/definitions/MilestoneReference"
+ }
+ }
+ },
+ "MilestoneReference": {
+ "type": "object",
+ "title": "Referencia del hito",
+ "description": "Un bloque usado para hacer referencia a un hito, incluyendo el ID y el t\u00edtulo del hito que al que se hace referencia.",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID del hito",
+ "description": "El ID del hito que se hace referencia, debe coincidir con el identificador de un hito descrito en alguna otra parte de una entrega sobre este proceso de contrataci\u00f3n.",
+ "type": "string"
+ },
+ "title": {
+ "title": "T\u00edtulo del hito",
+ "description": "El t\u00edtulo del hito al que se hace referencia, debe coincidir con el t\u00edtulo de un hito descrito en alguna otra parte en una entrega sobre este proceso de contrataci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/metrics/v1.1/schema/index.html b/es/extensions/metrics/v1.1/schema/index.html
new file mode 100644
index 000000000..bc3eb077d
--- /dev/null
+++ b/es/extensions/metrics/v1.1/schema/index.html
@@ -0,0 +1,862 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Métrica +
+ ++ La extensión de métricas admite la publicación de pronósticos (etapa de planificación), objetivos (etapa de licitación), objetivos de desempeño acordados (etapa de adjudicación y contrato) y resultados (etapa de implementación). +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La extensión de métricas proporciona un bloque de construcción común para reportar información estructurada de rendimiento de los contratos.
+Las métricas están estructuradas como un cubo de datos OLAP con cada instancia de Metric representando una sola observation, categorizada por un número de dimensions.
{
+ "metrics":[
+ {
+ "id":"annualDemand",
+ "title":"Annual Demand",
+ "description":"The annual demand",
+ "observations":[
+ {
+ "period":{
+ "startDate":"2015-01-01T00:00:00Z",
+ "endDate":"2015-12-31T23:59:59Z"
+ },
+ "quantity":"10000",
+ "dimensions":{
+ "vehicleType":"Car"
+ }
+ },
+ {
+ "period":{
+ "startDate":"2015-01-01T00:00:00Z",
+ "endDate":"2015-12-31T23:59:59Z"
+ },
+ "quantity":"1000",
+ "dimensions":{
+ "vehicleType":"Trucks"
+ },
+ "note":"Simple note"
+ }
+ ]
+ },
+ {
+
+ }
+ ]
+}
+Uso con requerimientos
+Las métricas se pueden utilizar junto con la extensión de requisitos que agregará una propiedad 'relatedRequirementID' a las métricas.
+Con la extensión de requisitos, las ofertas, adjudicaciones y contratos pueden incluir un requirementResponse que indica los valores contra cada métrica que un proveedor desea cumplir.
Esto puede permitir un cierto grado de comparación entre el rendimiento previsto en las fases de licitación, adjudicación, contrato y ejecución.
+Por hacer
+-
+
- [ ] Comprobar la sintaxis del esquema oneOf para value oquantity +
- [ ] Agregar relatedRequirementID a la extensión de requisitos +
- [ ] Validar actualizaciones de esquema +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/index.html b/es/extensions/milestone_documents/index.html
new file mode 100644
index 000000000..1fe6374dc
--- /dev/null
+++ b/es/extensions/milestone_documents/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Métrica +
+ ++ La extensión de métricas admite la publicación de pronósticos (etapa de planificación), objetivos (etapa de licitación), objetivos de desempeño acordados (etapa de adjudicación y contrato) y resultados (etapa de implementación). +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Planning +
+ +
+ The extension defines these fields in the Planning object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ forecasts
+
+ |
+ + Pronósticos + | +
+ Cualquier métrica de pronóstico para los resultados de este proceso de contratación. + + |
+ + array of Metric objects + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ targets
+
+ |
+ + Objetivos + | +
+ Cualquier métrica del objetivo para el resultado de este proceso de contratación. + + |
+ + array of Metric objects + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Métricas acordadas + | +
+ Cualquier métrica objetivo establecida como parte de la adjudicación del contrato. + + |
+ + array of Metric objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ agreedMetrics
+
+ |
+ + Métricas acordadas + | +
+ Cualquier métrica objetivo establecida como parte de los documentos del contrato. + + |
+ + array of Metric objects + | +
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ metrics
+
+ |
+ + Métrica + | +
+ Resultados reportados de la entrega de los bienes, obras o servicios contratados. + + |
+ + array of Metric objects + | +
+ Metric +
+ +
+ The extension defines a new Metric object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador para esta métrica. En algunos casos, esto puede extraerse de una lista de códigos de métricas requerida para este tipo de proceso de contratación, o en otros casos puede ser un identificador arbitrario. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título + | +
+ El título de esta métrica + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Una breve descripción de la métrica. Esto puede incluir pequeños detalles de los métodos de medición. + + |
+ + string + | +
+
+ observations
+
+ |
+ + Observaciones + | +
+ Una lista de valores objetivo o reales para esta métrica. + + |
+ + array of Observation objects + | +
+ Observation +
+ +
+ The extension defines a new Observation object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador local para esta observación específica. Esto puede ser un identificador arbitrario, o podría ser un compuesto del identificador de métrica, y la fecha y otras dimensiones de esta observación. + + |
+ + string + | +
+
+ period
+
+ |
+ + + | ++ + | ++ Period object + | +
+
+ value
+
+ |
+ + + | ++ + | ++ Value object + | +
+
+ measure
+
+ |
+ + Medida de observación + | +
+ Para las métricas no financieras, la medida de este pronóstico, objetivo o observación real. Las medidas pueden proporcionarse como texto libre o valores numéricos. + + |
+ + string or number + | +
+
+ unit
+
+ |
+ + Unidad + | +
+ Unidad + + |
+ + object + | +
+
+ unit.
+ |
+ + Nombre de la unidad + | +
+ El nombre de la unidad. + + |
+ + string + | +
+
+ unit.
+ |
+ + Esquema + | +
+ La lista desde la cual se toman los identificadores de unidades de medida. Esta debe ser una entrada en la lista de códigos unitClassificationScheme. Se recomienda el uso del esquema "UNCEFACT" para la recomendación 20 del CEFACT-ONU de "Códigos para unidades de medida utilizadas en el comercio internacional". + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ unit.
+ |
+ + ID + | +
+ El identificador de la lista de códigos se hace referencia en la propiedad de esquema. Por ejemplo, con UNCEFACT, este es el valor de la columna "Common Code". A partir de este identificador, las aplicaciones pueden buscar el nombre o símbolo legible para humanos para esta unidad de medida. + + |
+ + string + | +
+
+ unit.
+ |
+ + URI + | +
+ Si el esquema utilizado provee una URI legible por computadora para esta unidad de medición, ésta puede proporcionarse. + + |
+ + string + | +
+
+ dimensions
+
+ |
+ + Dimensiones + | +
+ Cualquier número de dimensiones se puede registrar dentro de este objeto. Los nombres de dimensiones deben seguir las convenciones de OCDS de camelCase. + + |
+ + object + | +
+
+ dimensions.
+ |
+ + + | ++ + | ++ string + | +
+
+ notes
+
+ |
+ + Notas + | +
+ Cualquier nota sobre esta observación. Esto puede incluir información para aclaración. + + |
+ + string + | +
+
+ relatedImplementationMilestone
+
+ |
+ + Hito de implementación relacionado + | +
+ Un enlace al hito en la sección de implementación de OCDS a la cual se le relaciona esta observación de pronóstico, objetivo o real. + + |
+ + MilestoneReference object + | +
+ MilestoneReference +
+ +
+ The extension defines a new MilestoneReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID del hito + | +
+ El ID del hito que se hace referencia, debe coincidir con el identificador de un hito descrito en alguna otra parte de una entrega sobre este proceso de contratación. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título del hito + | +
+ El título del hito al que se hace referencia, debe coincidir con el título de un hito descrito en alguna otra parte en una entrega sobre este proceso de contratación. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/milestone_documents/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/master/release-schema.json b/es/extensions/milestone_documents/master/release-schema.json
new file mode 100644
index 000000000..b8100cd08
--- /dev/null
+++ b/es/extensions/milestone_documents/master/release-schema.json
@@ -0,0 +1,11 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "deprecated": null
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/milestone_documents/master/schema/index.html b/es/extensions/milestone_documents/master/schema/index.html
new file mode 100644
index 000000000..05755c92b
--- /dev/null
+++ b/es/extensions/milestone_documents/master/schema/index.html
@@ -0,0 +1,257 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En OCDS 1.1, el soporte básico para documentos adjuntos a hitos individuales se eliminó del bloque de hitos para simplificar el estándar.
+Esta extensión reintroduce el bloque documents en milestones, proporcionando campos para detallar los documentos relacionados con cada hito individual.
Guía
+Los publicadores deben considerar que muchas aplicaciones consumidoras sólo buscarán en la sección tender/documents, award/documents, contracts/documents y contracts/implementation/documents para acceder y mostrar la documentación relevante a los usuarios.
Los títulos de los documentos, los tipos de documentos y las descripciones se pueden utilizar para indicar a los lectores humanos la naturaleza particular de los documentos y los hitos con los que se relacionan.
+Sin embargo, en los casos en que es importante rastrear los documentos hito por hito, esta extensión puede ser introducida.
+Dependiendo de la naturaleza de los documentos, los publicadores deberán considerar duplicar la información en el bloque de documentos de las secciones principales también.
+Ejemplo
+Durante la implementación de un contrato, el comprador establece hitos que el proveedor debe de cumplir. Cada uno de estos hitos tiene un documento asociado que ofrece más detalles sobre el hito alcanzado: por ejemplo, un reporte de consultoría:
+{
+ "contracts": [
+ {
+ "id": "CO-40002-18-166811",
+ "awardID": "354469-jorge-augusto-zarate-leiva-1",
+ "implementation": {
+ "milestones": [
+ {
+ "id": "fcrMXKIb3/o=",
+ "title": "Informe de Consultoria",
+ "type": "reporting",
+ "dueDate": "2020-02-13T00:00:00-04:00",
+ "dateMet": "2020-02-14T00:00:00-04:00",
+ "status": "met",
+ "documents": [
+ {
+ "id": "QQ1cjJZ82Rk=",
+ "url": "https://www.contrataciones.gov.py/documentos/download/contrato_detalle_entregable/vki7v5RKGrA%253D",
+ "datePublished": "2020-02-17T13:38:25-04:00",
+ "language": "es",
+ "title": "informe_n__13_1581957505348.pdf",
+ "format": "application/pdf"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.5
+-
+
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/v1.1.1/README.md b/es/extensions/milestone_documents/v1.1.1/README.md
new file mode 100644
index 000000000..6aeec6822
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.1/README.md
@@ -0,0 +1,15 @@
+# Documentos de Hito
+
+En OCDS 1.1, el soporte básico para documentos adjuntos a hitos individuales se eliminó del bloque de hitos para simplificar el estándar.
+
+Esta extensión reintroduce el bloque `documents` en ` milestones`, proporcionando campos para detallar los documentos relacionados con cada hito individual.
+
+## Guía
+
+Los publicadores deben considerar que muchas aplicaciones consumidoras sólo buscarán en la sección `tender/documents`, `award/documents`, `contracts/documents` y `contracts/implementation/documents` para acceder y mostrar la documentación relevante a los usuarios.
+
+Los títulos de los documentos, los tipos de documentos y las descripciones se pueden utilizar para indicar a los lectores humanos la naturaleza particular de los documentos y los hitos con los que se relacionan.
+
+Sin embargo, en los casos en que es importante rastrear los documentos hito por hito, esta extensión puede ser introducida.
+
+Dependiendo de la naturaleza de los documentos, los publicadores deberán considerar duplicar la información en el bloque de documentos de las secciones principales también.
diff --git a/es/extensions/milestone_documents/v1.1.1/extension.json b/es/extensions/milestone_documents/v1.1.1/extension.json
new file mode 100644
index 000000000..a5e7776b7
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.1/extension.json
@@ -0,0 +1,15 @@
+{
+ "name": {
+ "en": "Milestone documents",
+ "es": "Documentos del hito"
+ },
+ "description": {
+ "en": "Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone.",
+ "es": "Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensi\u00f3n re-introduce la capacidad de adjuntar documentos a cada hito individual."
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "dependencies": [],
+ "documentationUrl": {}
+}
diff --git a/es/extensions/milestone_documents/v1.1.1/index.html b/es/extensions/milestone_documents/v1.1.1/index.html
new file mode 100644
index 000000000..b4c1c133b
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.1/index.html
@@ -0,0 +1,285 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + + | +
+ + This field is modified from its original version. + + ++ The extension undoes the deprecation of this field. + + |
+ + + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/v1.1.1/release-schema.json b/es/extensions/milestone_documents/v1.1.1/release-schema.json
new file mode 100644
index 000000000..ce802faaa
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.1/release-schema.json
@@ -0,0 +1,18 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "title": "Documentos",
+ "description": "Una lista de documentos espec\u00edficamente asociados con este hito.",
+ "type": "array",
+ "deprecated": null,
+ "items": {
+ "$ref": "#/definitions/Document"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/milestone_documents/v1.1.1/schema/index.html b/es/extensions/milestone_documents/v1.1.1/schema/index.html
new file mode 100644
index 000000000..994f8b3c6
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.1/schema/index.html
@@ -0,0 +1,258 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En OCDS 1.1, el soporte básico para documentos adjuntos a hitos individuales se eliminó del bloque de hitos para simplificar el estándar.
+Esta extensión reintroduce el bloque documents en milestones, proporcionando campos para detallar los documentos relacionados con cada hito individual.
Guía
+Los publicadores deben considerar que muchas aplicaciones consumidoras sólo buscarán en la sección tender/documents, award/documents, contracts/documents y contracts/implementation/documents para acceder y mostrar la documentación relevante a los usuarios.
Los títulos de los documentos, los tipos de documentos y las descripciones se pueden utilizar para indicar a los lectores humanos la naturaleza particular de los documentos y los hitos con los que se relacionan.
+Sin embargo, en los casos en que es importante rastrear los documentos hito por hito, esta extensión puede ser introducida.
+Dependiendo de la naturaleza de los documentos, los publicadores deberán considerar duplicar la información en el bloque de documentos de las secciones principales también.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/v1.1.3/README.md b/es/extensions/milestone_documents/v1.1.3/README.md
new file mode 100644
index 000000000..794af5143
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.3/README.md
@@ -0,0 +1,26 @@
+# Documentos de Hito
+
+En OCDS 1.1, el soporte básico para documentos adjuntos a hitos individuales se eliminó del bloque de hitos para simplificar el estándar.
+
+Esta extensión reintroduce el bloque `documents` en ` milestones`, proporcionando campos para detallar los documentos relacionados con cada hito individual.
+
+## Guía
+
+Los publicadores deben considerar que muchas aplicaciones consumidoras sólo buscarán en la sección `tender/documents`, `award/documents`, `contracts/documents` y `contracts/implementation/documents` para acceder y mostrar la documentación relevante a los usuarios.
+
+Los títulos de los documentos, los tipos de documentos y las descripciones se pueden utilizar para indicar a los lectores humanos la naturaleza particular de los documentos y los hitos con los que se relacionan.
+
+Sin embargo, en los casos en que es importante rastrear los documentos hito por hito, esta extensión puede ser introducida.
+
+Dependiendo de la naturaleza de los documentos, los publicadores deberán considerar duplicar la información en el bloque de documentos de las secciones principales también.
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.3
+
+- Usa la licencia Apache 2.0
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/milestone_documents/v1.1.3/extension.json b/es/extensions/milestone_documents/v1.1.3/extension.json
new file mode 100644
index 000000000..ec5daf958
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.3/extension.json
@@ -0,0 +1,16 @@
+{
+ "name": {
+ "en": "Milestone documents",
+ "es": "Documentos del hito"
+ },
+ "description": {
+ "en": "Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone.",
+ "es": "Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensi\u00f3n re-introduce la capacidad de adjuntar documentos a cada hito individual."
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting/ocds_milestone_documents_extension"
+ }
+}
diff --git a/es/extensions/milestone_documents/v1.1.3/index.html b/es/extensions/milestone_documents/v1.1.3/index.html
new file mode 100644
index 000000000..7273ac0a2
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.3/index.html
@@ -0,0 +1,308 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + Documentos + | +
+ + This field is modified from its original version. + +Una lista de documentos específicamente asociados con este hito. + ++ The extension undoes the deprecation of this field. + + |
+ + array of Document objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/v1.1.3/release-schema.json b/es/extensions/milestone_documents/v1.1.3/release-schema.json
new file mode 100644
index 000000000..b8100cd08
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.3/release-schema.json
@@ -0,0 +1,11 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "deprecated": null
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/milestone_documents/v1.1.3/schema/index.html b/es/extensions/milestone_documents/v1.1.3/schema/index.html
new file mode 100644
index 000000000..8f07f6bb6
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.3/schema/index.html
@@ -0,0 +1,257 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En OCDS 1.1, el soporte básico para documentos adjuntos a hitos individuales se eliminó del bloque de hitos para simplificar el estándar.
+Esta extensión reintroduce el bloque documents en milestones, proporcionando campos para detallar los documentos relacionados con cada hito individual.
Guía
+Los publicadores deben considerar que muchas aplicaciones consumidoras sólo buscarán en la sección tender/documents, award/documents, contracts/documents y contracts/implementation/documents para acceder y mostrar la documentación relevante a los usuarios.
Los títulos de los documentos, los tipos de documentos y las descripciones se pueden utilizar para indicar a los lectores humanos la naturaleza particular de los documentos y los hitos con los que se relacionan.
+Sin embargo, en los casos en que es importante rastrear los documentos hito por hito, esta extensión puede ser introducida.
+Dependiendo de la naturaleza de los documentos, los publicadores deberán considerar duplicar la información en el bloque de documentos de las secciones principales también.
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.3
+-
+
- Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/v1.1.4/README.md b/es/extensions/milestone_documents/v1.1.4/README.md
new file mode 100644
index 000000000..e01edc6cc
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.4/README.md
@@ -0,0 +1,30 @@
+# Documentos de Hito
+
+En OCDS 1.1, el soporte básico para documentos adjuntos a hitos individuales se eliminó del bloque de hitos para simplificar el estándar.
+
+Esta extensión reintroduce el bloque `documents` en ` milestones`, proporcionando campos para detallar los documentos relacionados con cada hito individual.
+
+## Guía
+
+Los publicadores deben considerar que muchas aplicaciones consumidoras sólo buscarán en la sección `tender/documents`, `award/documents`, `contracts/documents` y `contracts/implementation/documents` para acceder y mostrar la documentación relevante a los usuarios.
+
+Los títulos de los documentos, los tipos de documentos y las descripciones se pueden utilizar para indicar a los lectores humanos la naturaleza particular de los documentos y los hitos con los que se relacionan.
+
+Sin embargo, en los casos en que es importante rastrear los documentos hito por hito, esta extensión puede ser introducida.
+
+Dependiendo de la naturaleza de los documentos, los publicadores deberán considerar duplicar la información en el bloque de documentos de las secciones principales también.
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.4
+
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- Usa la licencia Apache 2.0
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/milestone_documents/v1.1.4/extension.json b/es/extensions/milestone_documents/v1.1.4/extension.json
new file mode 100644
index 000000000..9a2474f6c
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.4/extension.json
@@ -0,0 +1,19 @@
+{
+ "name": {
+ "en": "Milestone documents",
+ "es": "Documentos del hito"
+ },
+ "description": {
+ "en": "Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone.",
+ "es": "Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensi\u00f3n re-introduce la capacidad de adjuntar documentos a cada hito individual."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/milestone_documents/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/es/extensions/milestone_documents/v1.1.4/index.html b/es/extensions/milestone_documents/v1.1.4/index.html
new file mode 100644
index 000000000..e59429bae
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.4/index.html
@@ -0,0 +1,317 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + + | +
+ + This field is modified from its original version. + + ++ The extension undoes the deprecation of this field. + + |
+ + + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/v1.1.4/release-schema.json b/es/extensions/milestone_documents/v1.1.4/release-schema.json
new file mode 100644
index 000000000..b8100cd08
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.4/release-schema.json
@@ -0,0 +1,11 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "deprecated": null
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/milestone_documents/v1.1.4/schema/index.html b/es/extensions/milestone_documents/v1.1.4/schema/index.html
new file mode 100644
index 000000000..adf3d1c55
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.4/schema/index.html
@@ -0,0 +1,257 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En OCDS 1.1, el soporte básico para documentos adjuntos a hitos individuales se eliminó del bloque de hitos para simplificar el estándar.
+Esta extensión reintroduce el bloque documents en milestones, proporcionando campos para detallar los documentos relacionados con cada hito individual.
Guía
+Los publicadores deben considerar que muchas aplicaciones consumidoras sólo buscarán en la sección tender/documents, award/documents, contracts/documents y contracts/implementation/documents para acceder y mostrar la documentación relevante a los usuarios.
Los títulos de los documentos, los tipos de documentos y las descripciones se pueden utilizar para indicar a los lectores humanos la naturaleza particular de los documentos y los hitos con los que se relacionan.
+Sin embargo, en los casos en que es importante rastrear los documentos hito por hito, esta extensión puede ser introducida.
+Dependiendo de la naturaleza de los documentos, los publicadores deberán considerar duplicar la información en el bloque de documentos de las secciones principales también.
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.4
+-
+
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/v1.1.5/README.md b/es/extensions/milestone_documents/v1.1.5/README.md
new file mode 100644
index 000000000..3ad43ac7e
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.5/README.md
@@ -0,0 +1,71 @@
+# Documentos de Hito
+
+En OCDS 1.1, el soporte básico para documentos adjuntos a hitos individuales se eliminó del bloque de hitos para simplificar el estándar.
+
+Esta extensión reintroduce el bloque `documents` en ` milestones`, proporcionando campos para detallar los documentos relacionados con cada hito individual.
+
+## Guía
+
+Los publicadores deben considerar que muchas aplicaciones consumidoras sólo buscarán en la sección `tender/documents`, `award/documents`, `contracts/documents` y `contracts/implementation/documents` para acceder y mostrar la documentación relevante a los usuarios.
+
+Los títulos de los documentos, los tipos de documentos y las descripciones se pueden utilizar para indicar a los lectores humanos la naturaleza particular de los documentos y los hitos con los que se relacionan.
+
+Sin embargo, en los casos en que es importante rastrear los documentos hito por hito, esta extensión puede ser introducida.
+
+Dependiendo de la naturaleza de los documentos, los publicadores deberán considerar duplicar la información en el bloque de documentos de las secciones principales también.
+
+## Ejemplo
+
+Durante la implementación de un contrato, el comprador establece hitos que el proveedor debe de cumplir. Cada uno de estos hitos tiene un documento asociado que ofrece más detalles sobre el hito alcanzado: por ejemplo, un reporte de consultoría:
+
+```json
+{
+ "contracts": [
+ {
+ "id": "CO-40002-18-166811",
+ "awardID": "354469-jorge-augusto-zarate-leiva-1",
+ "implementation": {
+ "milestones": [
+ {
+ "id": "fcrMXKIb3/o=",
+ "title": "Informe de Consultoria",
+ "type": "reporting",
+ "dueDate": "2020-02-13T00:00:00-04:00",
+ "dateMet": "2020-02-14T00:00:00-04:00",
+ "status": "met",
+ "documents": [
+ {
+ "id": "QQ1cjJZ82Rk=",
+ "url": "https://www.contrataciones.gov.py/documentos/download/contrato_detalle_entregable/vki7v5RKGrA%253D",
+ "datePublished": "2020-02-17T13:38:25-04:00",
+ "language": "es",
+ "title": "informe_n__13_1581957505348.pdf",
+ "format": "application/pdf"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+```
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.5
+
+- Revisar las palabras normativas y no-normativas
+
+### v1.1.4
+
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- Usa la licencia Apache 2.0
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/milestone_documents/v1.1.5/extension.json b/es/extensions/milestone_documents/v1.1.5/extension.json
new file mode 100644
index 000000000..a9304fd6c
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.5/extension.json
@@ -0,0 +1,23 @@
+{
+ "name": {
+ "en": "Milestone documents",
+ "es": "Documentos del hito"
+ },
+ "description": {
+ "en": "Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone.",
+ "es": "Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensi\u00f3n re-introduce la capacidad de adjuntar documentos a cada hito individual."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/milestone_documents/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/milestone_documents/v1.1.5/index.html b/es/extensions/milestone_documents/v1.1.5/index.html
new file mode 100644
index 000000000..1e4cb2863
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.5/index.html
@@ -0,0 +1,364 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + + | +
+ + This field is modified from its original version. + + ++ The extension undoes the deprecation of this field. + + |
+ + + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/v1.1.5/release-schema.json b/es/extensions/milestone_documents/v1.1.5/release-schema.json
new file mode 100644
index 000000000..b8100cd08
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.5/release-schema.json
@@ -0,0 +1,11 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "deprecated": null
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/milestone_documents/v1.1.5/schema/index.html b/es/extensions/milestone_documents/v1.1.5/schema/index.html
new file mode 100644
index 000000000..6d8dc90b4
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1.5/schema/index.html
@@ -0,0 +1,257 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En OCDS 1.1, el soporte básico para documentos adjuntos a hitos individuales se eliminó del bloque de hitos para simplificar el estándar.
+Esta extensión reintroduce el bloque documents en milestones, proporcionando campos para detallar los documentos relacionados con cada hito individual.
Guía
+Los publicadores deben considerar que muchas aplicaciones consumidoras sólo buscarán en la sección tender/documents, award/documents, contracts/documents y contracts/implementation/documents para acceder y mostrar la documentación relevante a los usuarios.
Los títulos de los documentos, los tipos de documentos y las descripciones se pueden utilizar para indicar a los lectores humanos la naturaleza particular de los documentos y los hitos con los que se relacionan.
+Sin embargo, en los casos en que es importante rastrear los documentos hito por hito, esta extensión puede ser introducida.
+Dependiendo de la naturaleza de los documentos, los publicadores deberán considerar duplicar la información en el bloque de documentos de las secciones principales también.
+Ejemplo
+Durante la implementación de un contrato, el comprador establece hitos que el proveedor debe de cumplir. Cada uno de estos hitos tiene un documento asociado que ofrece más detalles sobre el hito alcanzado: por ejemplo, un reporte de consultoría:
+{
+ "contracts": [
+ {
+ "id": "CO-40002-18-166811",
+ "awardID": "354469-jorge-augusto-zarate-leiva-1",
+ "implementation": {
+ "milestones": [
+ {
+ "id": "fcrMXKIb3/o=",
+ "title": "Informe de Consultoria",
+ "type": "reporting",
+ "dueDate": "2020-02-13T00:00:00-04:00",
+ "dateMet": "2020-02-14T00:00:00-04:00",
+ "status": "met",
+ "documents": [
+ {
+ "id": "QQ1cjJZ82Rk=",
+ "url": "https://www.contrataciones.gov.py/documentos/download/contrato_detalle_entregable/vki7v5RKGrA%253D",
+ "datePublished": "2020-02-17T13:38:25-04:00",
+ "language": "es",
+ "title": "informe_n__13_1581957505348.pdf",
+ "format": "application/pdf"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.5
+-
+
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/v1.1/README.md b/es/extensions/milestone_documents/v1.1/README.md
new file mode 100644
index 000000000..6aeec6822
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1/README.md
@@ -0,0 +1,15 @@
+# Documentos de Hito
+
+En OCDS 1.1, el soporte básico para documentos adjuntos a hitos individuales se eliminó del bloque de hitos para simplificar el estándar.
+
+Esta extensión reintroduce el bloque `documents` en ` milestones`, proporcionando campos para detallar los documentos relacionados con cada hito individual.
+
+## Guía
+
+Los publicadores deben considerar que muchas aplicaciones consumidoras sólo buscarán en la sección `tender/documents`, `award/documents`, `contracts/documents` y `contracts/implementation/documents` para acceder y mostrar la documentación relevante a los usuarios.
+
+Los títulos de los documentos, los tipos de documentos y las descripciones se pueden utilizar para indicar a los lectores humanos la naturaleza particular de los documentos y los hitos con los que se relacionan.
+
+Sin embargo, en los casos en que es importante rastrear los documentos hito por hito, esta extensión puede ser introducida.
+
+Dependiendo de la naturaleza de los documentos, los publicadores deberán considerar duplicar la información en el bloque de documentos de las secciones principales también.
diff --git a/es/extensions/milestone_documents/v1.1/extension.json b/es/extensions/milestone_documents/v1.1/extension.json
new file mode 100644
index 000000000..a5e7776b7
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1/extension.json
@@ -0,0 +1,15 @@
+{
+ "name": {
+ "en": "Milestone documents",
+ "es": "Documentos del hito"
+ },
+ "description": {
+ "en": "Documents at the milestone level were deprecated in OCDS 1.1. This extension re-introduces the ability to attach documents to each individual milestone.",
+ "es": "Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensi\u00f3n re-introduce la capacidad de adjuntar documentos a cada hito individual."
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "dependencies": [],
+ "documentationUrl": {}
+}
diff --git a/es/extensions/milestone_documents/v1.1/index.html b/es/extensions/milestone_documents/v1.1/index.html
new file mode 100644
index 000000000..7367b9693
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1/index.html
@@ -0,0 +1,285 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + + | +
+ + This field is modified from its original version. + + ++ The extension undoes the deprecation of this field. + + |
+ + + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/milestone_documents/v1.1/release-schema.json b/es/extensions/milestone_documents/v1.1/release-schema.json
new file mode 100644
index 000000000..ce802faaa
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1/release-schema.json
@@ -0,0 +1,18 @@
+{
+ "definitions": {
+ "Milestone": {
+ "properties": {
+ "documents": {
+ "title": "Documentos",
+ "description": "Una lista de documentos espec\u00edficamente asociados con este hito.",
+ "type": "array",
+ "deprecated": null,
+ "items": {
+ "$ref": "#/definitions/Document"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/milestone_documents/v1.1/schema/index.html b/es/extensions/milestone_documents/v1.1/schema/index.html
new file mode 100644
index 000000000..24dd80f0a
--- /dev/null
+++ b/es/extensions/milestone_documents/v1.1/schema/index.html
@@ -0,0 +1,258 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En OCDS 1.1, el soporte básico para documentos adjuntos a hitos individuales se eliminó del bloque de hitos para simplificar el estándar.
+Esta extensión reintroduce el bloque documents en milestones, proporcionando campos para detallar los documentos relacionados con cada hito individual.
Guía
+Los publicadores deben considerar que muchas aplicaciones consumidoras sólo buscarán en la sección tender/documents, award/documents, contracts/documents y contracts/implementation/documents para acceder y mostrar la documentación relevante a los usuarios.
Los títulos de los documentos, los tipos de documentos y las descripciones se pueden utilizar para indicar a los lectores humanos la naturaleza particular de los documentos y los hitos con los que se relacionan.
+Sin embargo, en los casos en que es importante rastrear los documentos hito por hito, esta extensión puede ser introducida.
+Dependiendo de la naturaleza de los documentos, los publicadores deberán considerar duplicar la información en el bloque de documentos de las secciones principales también.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/options/index.html b/es/extensions/options/index.html
new file mode 100644
index 000000000..ad1be3a58
--- /dev/null
+++ b/es/extensions/options/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentos del hito +
+ ++ Los documentos en el nivel del hito son obsoletos en OCDS 1.1. Esta extensión re-introduce la capacidad de adjuntar documentos a cada hito individual. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ documents
+
+ |
+ + Documentos + | +
+ + This field is modified from its original version. + +Una lista de documentos específicamente asociados con este hito. + ++ The extension undoes the deprecation of this field. + + |
+ + array of Document objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/options/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/options/master/release-schema.json b/es/extensions/options/master/release-schema.json
new file mode 100644
index 000000000..9e80f0d22
--- /dev/null
+++ b/es/extensions/options/master/release-schema.json
@@ -0,0 +1,60 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "options": {
+ "title": "Opciones",
+ "description": "Una descripci\u00f3n de las opciones.",
+ "$ref": "#/definitions/Options"
+ },
+ "hasOptions": {
+ "title": "Opciones utilizadas",
+ "description": "Si el comprador se reserva o no el derecho de realizar compras adicionales al proveedor, siempre que el contrato sea v\u00e1lido.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "options": {
+ "title": "Opciones",
+ "description": "Una descripci\u00f3n de las opciones.",
+ "$ref": "#/definitions/Options"
+ },
+ "hasOptions": {
+ "title": "Opciones utilizadas",
+ "description": "Si el comprador se reserva el derecho de realizar compras adicionales al proveedor, siempre que el contrato sea v\u00e1lido.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "Options": {
+ "title": "Opciones",
+ "description": "Una descripci\u00f3n de las opciones.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una descripci\u00f3n de las opciones.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "period": {
+ "title": "Periodo",
+ "description": "El per\u00edodo durante el cual se pueden utilizar las opciones.",
+ "$ref": "#/definitions/Period"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/options/master/schema/index.html b/es/extensions/options/master/schema/index.html
new file mode 100644
index 000000000..83252deb2
--- /dev/null
+++ b/es/extensions/options/master/schema/index.html
@@ -0,0 +1,384 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Opciones +
+ ++ Agregar campos para obtener información sobre las opciones. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Esta extensión agrega campos para indicar si se utilizan opciones y otra información sobre las mismas.
+Un comprador puede tener el derecho, pero no la obligación, de realizar compras adicionales a un proveedor mientras el contrato sea válido.
+For example, a contract may concern a thousand uniforms, and the buyer may have the option to request an additional hundred uniforms. This might occur if the buyer doesn't yet know whether a planned increase in staff will take place.
+Contexto legal
+El [Acuerdo Revisado Sobre Contratación Pública] (https://www.wto.org/english/docs_e/legal_e/rev-gpr-94_01_e.htm) (GPA) incluye: "cada aviso de contratación prevista deberá incluir ... d. una descripción de las opciones".
+La Unión Europea es una parte para el Acuerdo sobre Contratación Pública GPA, y como tal su Directiva 2014/24/EU (Contratos públicos — establecimiento de reglas básicas claras) incluye: "Parte C: Información que se incluirá en los avisos de contrato ... 7. ... Donde corresponda, descripción de las opciones".
+Ejemplo
+{
+ "tender": {
+ "hasOptions": true,
+ "options": {
+ "description": "The buyer has the option to buy an additional hundred uniforms.",
+ "period": {
+ "durationInDays": 180
+ }
+ }
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-10-06
+-
+
- Add
Options.periodfield.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), en [pull requests] (https://github.com/open-contracting-extensions/ocds_options_extension/pulls?q=is%3Apr+is%3Aclosed) y en https://github.com/open-contracting/standard/issues/691.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/organizationClassification/1.1/README.md b/es/extensions/organizationClassification/1.1/README.md
new file mode 100644
index 000000000..c07c243ab
--- /dev/null
+++ b/es/extensions/organizationClassification/1.1/README.md
@@ -0,0 +1,44 @@
+# Clasificación de la organización
+
+Agrega una lista de objetos de clasificación a los detalles de una organización, con el fin de categorizarla.
+
+## Contexto legal
+
+In the European Union, this extension's fields correspond to [eForms BT-10 (Activity Authority)](https://docs.ted.europa.eu/eforms/latest/reference/business-terms/). For correspondences to eForms fields, see [OCDS for eForms](https://standard.open-contracting.org/profiles/eforms/latest/en/). For correspondences to Tenders Electronic Daily (TED), see [OCDS for the European Union](http://standard.open-contracting.org/profiles/eu/latest/en/).
+
+## Ejemplos
+
+```json
+{
+ "parties": [
+ {
+ "id": "1",
+ "details": {
+ "classifications": [
+ {
+ "id": "10",
+ "scheme": "TED_CA_ACTIVITY",
+ "description": "Social protection"
+ }
+ ]
+ }
+ }
+ ]
+}
+```
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### 2023-08-01
+
+- Add 'eu-main-activity' and 'eu-buyer-contracting-type' to `+itemClassificationScheme.csv`.
+
+### 2020-04-24
+
+- Agregar las propiedades `minProperties`, `minItems` y/o `minLength`.
+
+Esta extensión se discutió originalmente como parte del \[OCDS para el perfil de la UE\] (https://github.com/open-contracting-extensions/european-union/issues), en [pull requests](https://github.com/open-contracting-extensions/ocds_organizationClassification_extension/pulls?q=is%3Apr+is%3Aclosed) y en
+
+
+
+
+ + Opciones +
+ ++ Agregar campos para obtener información sobre las opciones. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ options
+
+ |
+ + Opciones + | +
+ Una descripción de las opciones. + + |
+ + Options object + | +
+
+ hasOptions
+
+ |
+ + Opciones utilizadas + | +
+ Si el comprador se reserva o no el derecho de realizar compras adicionales al proveedor, siempre que el contrato sea válido. + + |
+ + boolean + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ options
+
+ |
+ + Opciones + | +
+ Una descripción de las opciones. + + |
+ + Options object + | +
+
+ hasOptions
+
+ |
+ + Opciones utilizadas + | +
+ Si el comprador se reserva el derecho de realizar compras adicionales al proveedor, siempre que el contrato sea válido. + + |
+ + boolean + | +
+ Options +
+ +
+ The extension defines a new Options object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Descripción + | +
+ Una descripción de las opciones. + + |
+ + string + | +
+
+ period
+
+ |
+ + Periodo + | +
+ El período durante el cual se pueden utilizar las opciones. + + |
+ + Period object + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/organizationClassification/1.1/extension.json b/es/extensions/organizationClassification/1.1/extension.json
new file mode 100644
index 000000000..6515b8a0f
--- /dev/null
+++ b/es/extensions/organizationClassification/1.1/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Organization classification",
+ "es": "Clasificaci\u00f3n de la organizaci\u00f3n"
+ },
+ "description": {
+ "en": "Adds an array of classification objects to an organization's details in order to categorize it.",
+ "es": "Adds an array of classification objects to an organization's details in order to categorize it."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/organizationClassification/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+itemClassificationScheme.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/organizationClassification/1.1/index.html b/es/extensions/organizationClassification/1.1/index.html
new file mode 100644
index 000000000..b81446c98
--- /dev/null
+++ b/es/extensions/organizationClassification/1.1/index.html
@@ -0,0 +1,320 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificación de la organización +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ COFOG
+
+ |
+ + Classification of the Functions of Government + | +
+ A standard classifying the purposes of government activities, developed by the Organisation for Economic Co-operation and Development and published by the United Nations Statistical Division. + +
|
+
+
+ eu-buyer-contracting-type
+
+ |
+ + EU buyer contracting type + | +
+ Whether a buyer is a contracting entity within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ eu-main-activity
+
+ |
+ + EU main activity + | +
+ The main activities of buyers within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ TED_CA_TYPE
+
+ |
+ + EC Type of contracting authority + | +
+ The types of contracting authority within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ TED_CE_ACTIVITY
+
+ |
+ + EC Main activity of contracting entity + | +
+ The main activities of contracting entities within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/organizationClassification/1.1/release-schema.json b/es/extensions/organizationClassification/1.1/release-schema.json
new file mode 100644
index 000000000..3e656625b
--- /dev/null
+++ b/es/extensions/organizationClassification/1.1/release-schema.json
@@ -0,0 +1,23 @@
+{
+ "definitions": {
+ "Organization": {
+ "properties": {
+ "details": {
+ "properties": {
+ "classifications": {
+ "title": "Clasificaciones de organizaci\u00f3n",
+ "description": "Las clasificaciones que categorizan a la organizaci\u00f3n",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/organizationClassification/1.1/schema/index.html b/es/extensions/organizationClassification/1.1/schema/index.html
new file mode 100644
index 000000000..0595a934d
--- /dev/null
+++ b/es/extensions/organizationClassification/1.1/schema/index.html
@@ -0,0 +1,255 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificación de la organización +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agrega una lista de objetos de clasificación a los detalles de una organización, con el fin de categorizarla.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BT-10 (Activity Authority). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplos
+{
+ "parties": [
+ {
+ "id": "1",
+ "details": {
+ "classifications": [
+ {
+ "id": "10",
+ "scheme": "TED_CA_ACTIVITY",
+ "description": "Social protection"
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-08-01
+-
+
- Add 'eu-main-activity' and 'eu-buyer-contracting-type' to
+itemClassificationScheme.csv.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), en pull requests y en https://github.com/open-contracting/standard/issues/711.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/organizationClassification/index.html b/es/extensions/organizationClassification/index.html
new file mode 100644
index 000000000..4a131c379
--- /dev/null
+++ b/es/extensions/organizationClassification/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificación de la organización +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + Clasificaciones de organización + | +
+ Las clasificaciones que categorizan a la organización + + |
+ + array of Classification objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/organizationClassification/1.1/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/organizationClassification/master/index.html b/es/extensions/organizationClassification/master/index.html
new file mode 100644
index 000000000..e7027b3c5
--- /dev/null
+++ b/es/extensions/organizationClassification/master/index.html
@@ -0,0 +1,321 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificación de la organización +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ COFOG
+
+ |
+ + Classification of the Functions of Government + | +
+ A standard classifying the purposes of government activities, developed by the Organisation for Economic Co-operation and Development and published by the United Nations Statistical Division. + +
|
+
+
+ eu-buyer-contracting-type
+
+ |
+ + EU buyer contracting type + | +
+ Whether a buyer is a contracting entity within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ eu-main-activity
+
+ |
+ + EU main activity + | +
+ The main activities of buyers within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ TED_CA_TYPE
+
+ |
+ + EC Type of contracting authority + | +
+ The types of contracting authority within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+ TED_CE_ACTIVITY
+
+ |
+ + EC Main activity of contracting entity + | +
+ The main activities of contracting entities within the domain of public procurement according to legislation of the European Parliament. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/organizationClassification/master/release-schema.json b/es/extensions/organizationClassification/master/release-schema.json
new file mode 100644
index 000000000..3e656625b
--- /dev/null
+++ b/es/extensions/organizationClassification/master/release-schema.json
@@ -0,0 +1,23 @@
+{
+ "definitions": {
+ "Organization": {
+ "properties": {
+ "details": {
+ "properties": {
+ "classifications": {
+ "title": "Clasificaciones de organizaci\u00f3n",
+ "description": "Las clasificaciones que categorizan a la organizaci\u00f3n",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/organizationClassification/master/schema/index.html b/es/extensions/organizationClassification/master/schema/index.html
new file mode 100644
index 000000000..56479c01a
--- /dev/null
+++ b/es/extensions/organizationClassification/master/schema/index.html
@@ -0,0 +1,256 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificación de la organización +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agrega una lista de objetos de clasificación a los detalles de una organización, con el fin de categorizarla.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BT-10 (Activity Authority). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplos
+{
+ "parties": [
+ {
+ "id": "1",
+ "details": {
+ "classifications": [
+ {
+ "id": "10",
+ "scheme": "TED_CA_ACTIVITY",
+ "description": "Social protection"
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-08-01
+-
+
- Add 'eu-main-activity' and 'eu-buyer-contracting-type' to
+itemClassificationScheme.csv.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), en pull requests y en https://github.com/open-contracting/standard/issues/711.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/otherRequirements/index.html b/es/extensions/otherRequirements/index.html
new file mode 100644
index 000000000..24de5099c
--- /dev/null
+++ b/es/extensions/otherRequirements/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificación de la organización +
+ ++ Adds an array of classification objects to an organization's details in order to categorize it. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + Clasificaciones de organización + | +
+ Las clasificaciones que categorizan a la organización + + |
+ + array of Classification objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/otherRequirements/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/otherRequirements/master/codelists/reservedParticipation.csv b/es/extensions/otherRequirements/master/codelists/reservedParticipation.csv
new file mode 100644
index 000000000..31caefb37
--- /dev/null
+++ b/es/extensions/otherRequirements/master/codelists/reservedParticipation.csv
@@ -0,0 +1,3 @@
+Código,Título,Descripción
+shelteredWorkshop,Sheltered workshop,Participation is reserved to sheltered workshops and suppliers aiming at the social and professional integration of disabled or disadvantaged persons.
+publicServiceMissionOrganization,Public service mission organization,Participation is reserved to organizations pursuing a public service mission and fulfilling other legislative conditions.
diff --git a/es/extensions/otherRequirements/master/extension.json b/es/extensions/otherRequirements/master/extension.json
new file mode 100644
index 000000000..6529fd213
--- /dev/null
+++ b/es/extensions/otherRequirements/master/extension.json
@@ -0,0 +1,29 @@
+{
+ "name": {
+ "en": "Other Requirements",
+ "es": "Otros requisitos"
+ },
+ "description": {
+ "en": "Adds an object to describe other requirements to participate in a contracting process.",
+ "es": "Agregar un objeto para describir otros requisitos para participar en un proceso de contrataci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/otherRequirements/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "reservedParticipation.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/es/extensions/otherRequirements/master/index.html b/es/extensions/otherRequirements/master/index.html
new file mode 100644
index 000000000..b9da4c34f
--- /dev/null
+++ b/es/extensions/otherRequirements/master/index.html
@@ -0,0 +1,378 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Otros requisitos +
+ ++ Agregar un objeto para describir otros requisitos para participar en un proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ reservedParticipation.csv +
+ +
+ You can download the reservedParticipation.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ shelteredWorkshop
+
+ |
+ + Sheltered workshop + | +
+ Participation is reserved to sheltered workshops and suppliers aiming at the social and professional integration of disabled or disadvantaged persons. + + |
+
+
+ publicServiceMissionOrganization
+
+ |
+ + Public service mission organization + | +
+ Participation is reserved to organizations pursuing a public service mission and fulfilling other legislative conditions. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/otherRequirements/master/release-schema.json b/es/extensions/otherRequirements/master/release-schema.json
new file mode 100644
index 000000000..79197cb3d
--- /dev/null
+++ b/es/extensions/otherRequirements/master/release-schema.json
@@ -0,0 +1,100 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "otherRequirements": {
+ "title": "Otros requisitos",
+ "description": "Otros requisitos para participar del procedimiento.",
+ "$ref": "#/definitions/OtherRequirements"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "otherRequirements": {
+ "title": "Otros requisitos",
+ "description": "Otros requisitos para participar del lote.",
+ "$ref": "#/definitions/OtherRequirements"
+ }
+ }
+ },
+ "OtherRequirements": {
+ "title": "Otros requisitos",
+ "description": "Otros requisitos para participar del procedimiento o lote.",
+ "type": "object",
+ "properties": {
+ "requiresStaffNamesAndQualifications": {
+ "title": "Se requiere nombres y calificaciones del personal",
+ "description": "Si los oferentes est\u00e1n obligados a indicar los nombres y las calificaciones profesionales del personal asignado a la ejecuci\u00f3n del contrato.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "reservedParticipation": {
+ "title": "Participaci\u00f3n reservada",
+ "description": "Los tipos de organizaciones a las que se reserva la participaci\u00f3n.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "reservedParticipation.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "qualificationSystemConditions": {
+ "title": "Condiciones del sistema de calificaci\u00f3n",
+ "description": "Las condiciones que deben cumplir los candidatos en vista de su calificaci\u00f3n para el sistema.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "qualificationSystemMethods": {
+ "title": "M\u00e9todos del sistema de calificaci\u00f3n",
+ "description": "Los m\u00e9todos seg\u00fan los cuales se verificar\u00e1n cada una de las condiciones del sistema de calificaci\u00f3n.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "reductionCriteria": {
+ "title": "Criterios de reducci\u00f3n",
+ "description": "Los criterios o reglas para seleccionar un n\u00famero limitado de candidatos calificados para presentar ofertas.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "securityClearance": {
+ "title": "Security clearance",
+ "description": "Information about the required security clearance (e.g. which clearance level is needed, which team members need it, whether it is needed already for accessing documents or only for contract execution).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/otherRequirements/master/schema/index.html b/es/extensions/otherRequirements/master/schema/index.html
new file mode 100644
index 000000000..ed379493a
--- /dev/null
+++ b/es/extensions/otherRequirements/master/schema/index.html
@@ -0,0 +1,423 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Otros requisitos +
+ ++ Agregar un objeto para describir otros requisitos para participar en un proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar un objeto para describir otros requisitos para participar en un proceso de contratación.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Contexto legal
+In the European Union, this extension's fields correspond to eForms BG-705 (Other Requirements), although not all the fields have been implemented yet. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+Tender
+{
+ "tender": {
+ "otherRequirements": {
+ "requiresStaffNamesAndQualifications": true,
+ "reservedParticipation": [
+ "shelteredWorkshop"
+ ],
+ "qualificationSystemConditions": [
+ "The candidates are required to comply with all the technical and financial requisites listed on the National Procurement portal: https://procurement.example.org/requisites",
+ "The candidates are required to create an electronic profile on https://procurement.example.org."
+ ],
+ "qualificationSystemMethods": [
+ "Pre-qualification questionnaire",
+ "Standard test, based on the results of the pre-qualification questionnaire"
+ ],
+ "reductionCriteria": "The candidates will be selected according to their technical, financial and legal capacity to undertake the works described in the present notice. More details on the criteria can be found in section 4.3 of the PCG.",
+ "securityClearance": "EU Confidential security clearance of Key Management Personnel must be achieved before access to procurement documents be granted"
+ }
+ }
+}
+Lot
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "otherRequirements": {
+ "requiresStaffNamesAndQualifications": true,
+ "reservedParticipation": [
+ "shelteredWorkshop"
+ ],
+ "qualificationSystemConditions": [
+ "The candidates are required to comply with all the technical and financial requisites listed on the National Procurement portal: https://procurement.example.org/requisites",
+ "The candidates are required to create an electronic profile on https://procurement.example.org."
+ ],
+ "qualificationSystemMethods": [
+ "Pre-qualification questionnaire",
+ "Standard test, based on the results of the pre-qualification questionnaire"
+ ],
+ "reductionCriteria": "The candidates will be selected according to their technical, financial and legal capacity to undertake the works described in the present notice. More details on the criteria can be found in section 4.3 of the PCG.",
+ "securityClearance": "EU Confidential security clearance of Key Management Personnel must be achieved before access to procurement documents be granted"
+ }
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-03-09
+-
+
- Add
OtherRequirements.securityClearancefield.
+
2022-03-09
+-
+
- Add
itemsto theOtherRequirements.qualificationSystemConditionsandOtherRequirements.qualificationSystemMethodsobjects.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues) y en pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/pagination/index.html b/es/extensions/pagination/index.html
new file mode 100644
index 000000000..e0f8d3988
--- /dev/null
+++ b/es/extensions/pagination/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Otros requisitos +
+ ++ Agregar un objeto para describir otros requisitos para participar en un proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ otherRequirements
+
+ |
+ + Otros requisitos + | +
+ Otros requisitos para participar del procedimiento. + + |
+ + OtherRequirements object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ otherRequirements
+
+ |
+ + Otros requisitos + | +
+ Otros requisitos para participar del lote. + + |
+ + OtherRequirements object + | +
+ OtherRequirements +
+ +
+ The extension defines a new OtherRequirements object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ requiresStaffNamesAndQualifications
+
+ |
+ + Se requiere nombres y calificaciones del personal + | +
+ Si los oferentes están obligados a indicar los nombres y las calificaciones profesionales del personal asignado a la ejecución del contrato. + + |
+ + boolean + | +
+
+ reservedParticipation
+
+ |
+ + Participación reservada + | +
+ Los tipos de organizaciones a las que se reserva la participación. + + |
+ + array of strings from open reservedParticipation codelist + | +
+
+ qualificationSystemConditions
+
+ |
+ + Condiciones del sistema de calificación + | +
+ Las condiciones que deben cumplir los candidatos en vista de su calificación para el sistema. + + |
+ + array of strings + | +
+
+ qualificationSystemMethods
+
+ |
+ + Métodos del sistema de calificación + | +
+ Los métodos según los cuales se verificarán cada una de las condiciones del sistema de calificación. + + |
+ + array of strings + | +
+
+ reductionCriteria
+
+ |
+ + Criterios de reducción + | +
+ Los criterios o reglas para seleccionar un número limitado de candidatos calificados para presentar ofertas. + + |
+ + string + | +
+
+ securityClearance
+
+ |
+ + Security clearance + | +
+ Information about the required security clearance (e.g. which clearance level is needed, which team members need it, whether it is needed already for accessing documents or only for contract execution). + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/pagination/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/index.html b/es/extensions/participation_fee/index.html
new file mode 100644
index 000000000..c81926b38
--- /dev/null
+++ b/es/extensions/participation_fee/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Paginación +
+ ++ Agregar un objeto de enlaces a los paquetes para dar soporte a la paginación. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar un objeto de enlaces a los paquetes para dar soporte a la paginación.
+Enlaces
+El objeto links de nivel superior en paquetes de entrega y paquetes de registro tiene tres campos:
-
+
next: una URL al siguiente paquete secuencial
+prev: una URL al paquete secuencial anterior
+
Para construir las URLs next y / o prev, se recomienda utilizar parámetros de cadena de consulta como:
-
+
since=TIMESTAMP, para devolver a una página de resultados que se modifican después desincetimestamp, en orden cronológico
+offset=NUMBER, para devolver a una página de resultados que se colocan después del númerooffseten orden secuencial (por ejemplo, si los resultados se recuperan de un SQL database)
+
No se aconseja utilizar page = NUMBER con los resultados ordenados en cronología inversa, porque:
-
+
- Una página determinada no devolverá los mismos resultados a lo largo del tiempo.
page = 1devolverá resultados diferentes hoy, la semana que viene y el año que viene.
+ - Los usuarios pueden recibir resultados duplicados mientras paginan. Por ejemplo, si se publica una nueva versión en la página 1 mientras los usuarios están paginando, el resultado en la parte inferior de cada página se moverá a la parte superior de la página siguiente. +
- Es más difícil para los usuarios sincronizar con la API. Con
sinceooffset, los usuarios pueden recuperar nuevos resultados enviando timestamp o el last request. Conpage, los usuarios deben determinar qué resultados son nuevos o antiguos.
+
Referencia: HTML link types, 18F API Standards, Government of Canada Standards on APIs, Government of Ontario API Guidelines, OpenActive Realtime Paged Data Exchange.
+Ejemplo
+Un publicador tiene una gran cantidad de entregas. En lugar de reunirlas en un paquete de entrega, las segmenta en varios paquetes de entrega, a través de una API con paginación. El campo links.next proporciona el enlace a la página siguiente.
{
+ "uri": "https://standard.open-contracting.org/examples/releases/ocds-213czf-000-00001-05-contract.json",
+ "license": "http://opendatacommons.org/licenses/pddl/1.0/",
+ "publicationPolicy": "https://github.com/open-contracting/sample-data/",
+ "version": "1.1",
+ "releases": [
+ {
+ "ocid": "ocds-213czf-000-00001",
+ "id": "ocds-213czf-000-00001-05-contract",
+ "date": "2010-05-10T10:30:00Z",
+ "language": "en",
+ "tag": [
+ "contract"
+ ],
+ "initiationType": "tender"
+ }
+ ],
+ "links": {
+ "next": "https://raw.githubusercontent.com/open-contracting/api-specification/master/multiple-file-api-next/releases-2015.json"
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-11-05
+-
+
- Remover
links.all.
+ - Eliminar
packageMetadata.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2020-04-15
+-
+
- Descontinuar
links.all.
+ - Descontinuar
packageMetadata.
+
+
+
+
+
+
+ + + This page has moved to a /es/extensions/participation_fee/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/master/codelists/methodOfPayment.csv b/es/extensions/participation_fee/master/codelists/methodOfPayment.csv
new file mode 100644
index 000000000..463ee8431
--- /dev/null
+++ b/es/extensions/participation_fee/master/codelists/methodOfPayment.csv
@@ -0,0 +1,7 @@
+Código,Título,Descripción
+cash,Cash,"The payment is made in cash, such as banknotes and coins."
+check,Check,"The payment is made by check (also written as ""cheque"")."
+creditCard,Credit card,The payment is made by credit card.
+directDebit,Direct debit,"The payment is made by direct debit, also known as direct withdrawal, pre-authorized debit (PAD) or pre-authorized payment (PAP)."
+letterOfCredit,Letter of credit,The payment is made by letter of credit.
+wireTransfer,Wire transfer,"The payment is made by wire transfer, also known as bank transfer or credit transfer."
diff --git a/es/extensions/participation_fee/master/codelists/participationFeeType.csv b/es/extensions/participation_fee/master/codelists/participationFeeType.csv
new file mode 100644
index 000000000..e5b0e873f
--- /dev/null
+++ b/es/extensions/participation_fee/master/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Código,Título,Descripción
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/es/extensions/participation_fee/master/extension.json b/es/extensions/participation_fee/master/extension.json
new file mode 100644
index 000000000..e5770843c
--- /dev/null
+++ b/es/extensions/participation_fee/master/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/participation_fee/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "participationFeeType.csv",
+ "methodOfPayment.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/participation_fee/master/index.html b/es/extensions/participation_fee/master/index.html
new file mode 100644
index 000000000..19f69d23c
--- /dev/null
+++ b/es/extensions/participation_fee/master/index.html
@@ -0,0 +1,393 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ methodOfPayment.csv +
+ +
+ You can download the methodOfPayment.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ cash
+
+ |
+ + Cash + | +
+ The payment is made in cash, such as banknotes and coins. + + |
+
+
+ check
+
+ |
+ + Check + | +
+ The payment is made by check (also written as "cheque"). + + |
+
+
+ creditCard
+
+ |
+ + Credit card + | +
+ The payment is made by credit card. + + |
+
+
+ directDebit
+
+ |
+ + Direct debit + | +
+ The payment is made by direct debit, also known as direct withdrawal, pre-authorized debit (PAD) or pre-authorized payment (PAP). + + |
+
+
+ letterOfCredit
+
+ |
+ + Letter of credit + | +
+ The payment is made by letter of credit. + + |
+
+
+ wireTransfer
+
+ |
+ + Wire transfer + | +
+ The payment is made by wire transfer, also known as bank transfer or credit transfer. + + |
+
+ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/master/release-schema.json b/es/extensions/participation_fee/master/release-schema.json
new file mode 100644
index 000000000..c2aacaac2
--- /dev/null
+++ b/es/extensions/participation_fee/master/release-schema.json
@@ -0,0 +1,78 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Cuota/Cargos de participaci\u00f3n",
+ "description": "Una tarifa que aplica a los ofertantes que quieren participar en el proceso de licitaciones. Las tarifas pueden aplicar para acceder los documentos de oferta, para enviar las ofertas o puede haber una cuota que debe ser pagada por el ofertante ganador.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID de tarifa",
+ "description": "Un identificador local de esta tarifa, \u00fanica en este bloque. Este campo se usa para hacer un seguimiento de m\u00faltiples revisiones de la tarifa a trav\u00e9s de la compilaci\u00f3n de los mecanismos de release y record",
+ "type": "string"
+ },
+ "type": {
+ "title": "Tipo de cuota/cargo",
+ "description": "El tipo de esta tarifa.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win"
+ ]
+ },
+ "codelist": "participationFeeType.csv",
+ "openCodelist": false
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor monetario de esta tarifa",
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Informaci\u00f3n adicional sobre esta tarifa, por ejemplo: casos espec\u00edficos en los que la tarifa es aplicable (ej. s\u00f3lo para copias f\u00edsicas de documentos), la manera en la cual la tarifa es cobrada o la naturaleza exacta de la tarifa.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "methodOfPayment": {
+ "title": "M\u00e9todos de pago",
+ "description": "Las v\u00edas aceptadas para el pago de las tarifas.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ },
+ "codelist": "methodOfPayment.csv",
+ "openCodelist": true,
+ "uniqueItems": true
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Cuotas de participaci\u00f3n",
+ "description": "Cualquier tarifa aplicable a los ofertantes que quieren participar en el proceso de licitaciones. Las tarifas pueden aplicar para acceder los documentos de oferta, para enviar las ofertas o puede haber una cuota que debe ser pagada por el ofertante ganador.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/participation_fee/master/schema/index.html b/es/extensions/participation_fee/master/schema/index.html
new file mode 100644
index 000000000..8508c58d3
--- /dev/null
+++ b/es/extensions/participation_fee/master/schema/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Esta extensión añade una matriz de los costos de participación al objeto de licitación, para revelar cualquier costo de participación en el proceso de contrataciones.
+Algunas veces hay costos asociados con el acceso a documentos de licitaciones relacionados al proceso de contratación. Los licitadores potenciales quieren saber sobre esos costos. Los monitores de adquisiciones también deben de asegurar que los costos de participación estén dentro de los parámetros legales (generalmente se establecen con un valor fijo máximo, o como un porcentaje del valor total del contrato) o para monitorear como se usan las tarifas de participación.
+Guidance
+El campo id se va a requerir en las futuras versiones de la extensión.
In some cases, a fee is levied for official copies of procurement documents, with unofficial copies being freely available. Bidders might be required to prove that they have paid for official copies as part of their submission. In such cases, the fee should use the 'submission' code in the type field, rather than the 'document' code.
Ejemplo
+El siguiente fragmento de JSON modela un proceso de contratación donde las tarifas son aplicables al acceso a documentos y para la presentación de ofertas:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "id": "1",
+ "type": [
+ "document"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 8.0
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment": [
+ "wireTransfer",
+ "cheque"
+ ]
+ },
+ {
+ "id": "2",
+ "type": [
+ "submission"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.0
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment": [
+ "wireTransfer"
+ ]
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+Unreleased
+-
+
- Make
ParticipationFee.idrequired so that participation fees are merged by identifier
+
v1.1.5
+-
+
- Añadir el campo
idal ejemplo en readme
+ - Corregir la descripción del campo
ParticipationFee.type
+ - Combinar y conciliar descripciones de campos y códigos con esquemas y listas de códigos +
- Quitar la indicación de campos "opcionales" +
- Añadir la lista de código
methodOfPaymentde la [extensión paymentMethod] (https://github.com/INAImexico/ocds_paymentMethod_extension/blob/master/codelists/paymentMethod.csv)
+ - Quitar la información sobre el tipo de las descripciones de los campos +
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- Actualizar la propiedad
mergeStrategypara la propiedadwholeListMerge
+ - Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que
ParticipationFee.typetenga null en su conjunto de strings
+ - Permitir que
ParticipationFee.descriptionsea null
+ - Agregar el campo
ParticipationFee.id
+ - Agregar descripción a
ParticipationFee
+ - Agregar título y descripción a
ParticipationFee.value
+ - Agregar la lista de códigos de participaciónFeeType.csv para
ParticipationFee.type
+ - Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.1/README.md b/es/extensions/participation_fee/v1.1.1/README.md
new file mode 100644
index 000000000..1a1e313a3
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.1/README.md
@@ -0,0 +1,73 @@
+# Cuotas de participación
+
+## Antecedentes
+
+Hay una serie de casos en los que puede haber costos para acceder a los documentos o participar en un proceso de licitación.
+
+Los licitadores potenciales desearán estar enterados de los costos que un proceso puede implicar.
+
+Los monitores de adquisiciones tal vez deseen asegurarse de que los costos de participación estén dentro de los parámetros legales (a menudo fijados como un máximo fijo, o un porcentaje del valor total del contrato), o para controlar cómo se usan las cuotas de participación.
+
+## Campos de extensión
+
+Esta extensión agrega un campo `participationFees` a la sección ` tender` del OCDS e introduce un nuevo bloque `participationFee`.
+
+El campo `participationFees` es una matriz de bloques ` participationFee`.
+
+El bloque `participationFee` consta de tres campos:
+
+- `type` - un valor de la lista de códigos `participationFeeType`, que describe el tipo de cuota
+- `value` - el importe y la moneda de la cuota
+- `description` - un campo opcional con más información sobre los requisitos de la cuota. Por ejemplo, a veces una cuota de documento sólo es aplicable a la copia impresa de los documentos.
+- `methodOfPayment` - un campo opcional que proporciona información sobre los métodos de pago aceptados para la documentación. Actualmente se trata de una serie de cadenas, pero se podría introducir una lista de códigos abierta en el futuro.
+
+## Listas de códigos de extensión
+
+Esta extensión agrega una lista de códigos **cerrada** `participationFeeType` con los siguientes códigos:
+
+- document - una cuota a pagar por el acceso a los documentos de licitación
+- deposit - una cuota reembolsable a pagar por la presentación de ofertas
+- submission - una cuota no reembolsable a pagar por la presentación de ofertas
+- win - una cuota a pagar por el ganador
+
+## Ejemplo
+
+El siguiente fragmento de JSON modela un proceso de contratación donde las tarifas son aplicables tanto para el acceso a documentos como para la presentación de ofertas:
+
+```JSON
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+```
+
+## Notas de uso
+
+En algunos casos, se puede cobrar una cuota por las "copias oficiales" de los documentos de adquisición (aunque también se pueden obtener copias en línea de forma gratuita) y los licitadores deben probar que han pagado una copia oficial de los documentos como parte de su presentación.
+
+En este caso, la cuota debe ser modelada como un cargo de **oferta**, ya que la presentación sólo es posible cuando se ha pagado la cuota de acceso al documento.
+
+## Por hacer
+
+- Terminología de participación / presentación
+- finalizar lista de códigos
diff --git a/es/extensions/participation_fee/v1.1.1/codelists/index.html b/es/extensions/participation_fee/v1.1.1/codelists/index.html
new file mode 100644
index 000000000..ff4eb1898
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.1/codelists/index.html
@@ -0,0 +1,289 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID de tarifa + | +
+ Un identificador local de esta tarifa, única en este bloque. Este campo se usa para hacer un seguimiento de múltiples revisiones de la tarifa a través de la compilación de los mecanismos de release y record + + |
+ + string + | +
+
+ type
+
+ |
+ + Tipo de cuota/cargo + | +
+ El tipo de esta tarifa. + + |
+ + array of strings from closed participationFeeType codelist + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor monetario de esta tarifa + + |
+ + Value object + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Información adicional sobre esta tarifa, por ejemplo: casos específicos en los que la tarifa es aplicable (ej. sólo para copias físicas de documentos), la manera en la cual la tarifa es cobrada o la naturaleza exacta de la tarifa. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Métodos de pago + | +
+ Las vías aceptadas para el pago de las tarifas. + + |
+ + array of strings from open methodOfPayment codelist + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Cuotas de participación + | +
+ Cualquier tarifa aplicable a los ofertantes que quieren participar en el proceso de licitaciones. Las tarifas pueden aplicar para acceder los documentos de oferta, para enviar las ofertas o puede haber una cuota que debe ser pagada por el ofertante ganador. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.1/codelists/participationFeeType.csv b/es/extensions/participation_fee/v1.1.1/codelists/participationFeeType.csv
new file mode 100644
index 000000000..e5b0e873f
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.1/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Código,Título,Descripción
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/es/extensions/participation_fee/v1.1.1/extension.json b/es/extensions/participation_fee/v1.1.1/extension.json
new file mode 100644
index 000000000..c6284aacc
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.1/extension.json
@@ -0,0 +1,14 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {},
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/es/extensions/participation_fee/v1.1.1/index.html b/es/extensions/participation_fee/v1.1.1/index.html
new file mode 100644
index 000000000..a69f64a62
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.1/index.html
@@ -0,0 +1,365 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.1/release-schema.json b/es/extensions/participation_fee/v1.1.1/release-schema.json
new file mode 100644
index 000000000..ca8e0b8c7
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.1/release-schema.json
@@ -0,0 +1,61 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Cuota/Cargos de participaci\u00f3n",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Tipo de cuota/cargo",
+ "description": "Las cuotas que aplican a los ofertantes que participen en el proceso de licitaciones. Las cuotas pueden aplicar para tener acceso a documentos de la oferta, hacer presentaci\u00f3n de ofertas o una cuota puede aplicar para el ofertante ganador.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win",
+ null
+ ]
+ }
+ },
+ "value": {
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Informaci\u00f3n adicional sobre la manera en que se cobran las cuotas o la naturaleza exacta de las mismas.",
+ "type": "string"
+ },
+ "methodOfPayment": {
+ "title": "M\u00e9todos de pago",
+ "description": "Informaci\u00f3n opcional sobre la manera en que se pueden pagar las cuotas",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Cuotas de participaci\u00f3n",
+ "description": "Cualquier cuota que sea aplicable a los ofertantes que quieran participar en el proceso de contrataciones. Las cuotas pueden aplicar para tener acceso a documentos de compras, para hacer ofertas o cuotas que deben ser pagadas por el ofertante ganador.",
+ "type": "array",
+ "mergeStrategy": "ocdsVersion",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/participation_fee/v1.1.1/schema/index.html b/es/extensions/participation_fee/v1.1.1/schema/index.html
new file mode 100644
index 000000000..5dba0a55c
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.1/schema/index.html
@@ -0,0 +1,358 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Antecedentes
+Hay una serie de casos en los que puede haber costos para acceder a los documentos o participar en un proceso de licitación.
+Los licitadores potenciales desearán estar enterados de los costos que un proceso puede implicar.
+Los monitores de adquisiciones tal vez deseen asegurarse de que los costos de participación estén dentro de los parámetros legales (a menudo fijados como un máximo fijo, o un porcentaje del valor total del contrato), o para controlar cómo se usan las cuotas de participación.
+Campos de extensión
+Esta extensión agrega un campo participationFees a la sección tender del OCDS e introduce un nuevo bloque participationFee.
El campo participationFees es una matriz de bloques participationFee.
El bloque participationFee consta de tres campos:
-
+
type- un valor de la lista de códigosparticipationFeeType, que describe el tipo de cuota
+value- el importe y la moneda de la cuota
+description- un campo opcional con más información sobre los requisitos de la cuota. Por ejemplo, a veces una cuota de documento sólo es aplicable a la copia impresa de los documentos.
+methodOfPayment- un campo opcional que proporciona información sobre los métodos de pago aceptados para la documentación. Actualmente se trata de una serie de cadenas, pero se podría introducir una lista de códigos abierta en el futuro.
+
Listas de códigos de extensión
+Esta extensión agrega una lista de códigos cerrada participationFeeType con los siguientes códigos:
-
+
- document - una cuota a pagar por el acceso a los documentos de licitación +
- deposit - una cuota reembolsable a pagar por la presentación de ofertas +
- submission - una cuota no reembolsable a pagar por la presentación de ofertas +
- win - una cuota a pagar por el ganador +
Ejemplo
+El siguiente fragmento de JSON modela un proceso de contratación donde las tarifas son aplicables tanto para el acceso a documentos como para la presentación de ofertas:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+Notas de uso
+En algunos casos, se puede cobrar una cuota por las "copias oficiales" de los documentos de adquisición (aunque también se pueden obtener copias en línea de forma gratuita) y los licitadores deben probar que han pagado una copia oficial de los documentos como parte de su presentación.
+En este caso, la cuota debe ser modelada como un cargo de oferta, ya que la presentación sólo es posible cuando se ha pagado la cuota de acceso al documento.
+Por hacer
+-
+
- Terminología de participación / presentación +
- finalizar lista de códigos +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.3/README.md b/es/extensions/participation_fee/v1.1.3/README.md
new file mode 100644
index 000000000..181302420
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.3/README.md
@@ -0,0 +1,84 @@
+# Cuotas de participación
+
+## Antecedentes
+
+Hay una serie de casos en los que puede haber costos para acceder a los documentos o participar en un proceso de licitación.
+
+Los licitadores potenciales desearán estar enterados de los costos que un proceso puede implicar.
+
+Los monitores de adquisiciones tal vez deseen asegurarse de que los costos de participación estén dentro de los parámetros legales (a menudo fijados como un máximo fijo, o un porcentaje del valor total del contrato), o para controlar cómo se usan las cuotas de participación.
+
+## Campos de extensión
+
+Esta extensión agrega un campo `participationFees` a la sección ` tender` del OCDS e introduce un nuevo bloque `participationFee`.
+
+El campo `participationFees` es una lista de bloques ` participationFee`.
+
+El bloque `participationFee` consta de tres campos:
+
+- `type` - un valor de la lista de códigos `participationFeeType`, que describe el tipo de costo
+- `value` - el importe y la moneda del costo
+- `description` - un campo opcional con más información sobre los requisitos del costo de participación. Por ejemplo, a veces un costo de un documento sólo es aplicable a la copia impresa de los documentos.
+- `methodOfPayment` - un campo opcional que proporciona información sobre los métodos de pago aceptados para la documentación. Actualmente se trata de una serie de cadenas, pero se podría introducir una lista de códigos abierta en el futuro.
+
+## Listas de códigos de extensión
+
+Esta extensión agrega una lista de códigos **cerrada** `participationFeeType` con los siguientes códigos:
+
+- document - una cuota a pagar por el acceso a los documentos de licitación
+- deposit - una cuota reembolsable a pagar por la presentación de ofertas
+- submission - una cuota no reembolsable a pagar por la presentación de ofertas
+- win - una cuota a pagar por el ganador
+
+## Ejemplo
+
+El siguiente fragmento de JSON modela un proceso de contratación donde las tarifas son aplicables tanto para el acceso a documentos como para la presentación de ofertas:
+
+```JSON
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+```
+
+## Notas de uso
+
+En algunos casos, se puede cobrar una cuota por las "copias oficiales" de los documentos de adquisición (aunque también se pueden obtener copias en línea de forma gratuita) y los licitadores deben probar que han pagado una copia oficial de los documentos como parte de su presentación.
+
+En este caso, la cuota debe ser modelada como un cargo de **oferta**, ya que la presentación sólo es posible cuando se ha pagado la cuota de acceso al documento.
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.3
+
+- No permitir que `ParticipationFee.type` tenga null en su conjunto de strings
+- Permitir que `ParticipationFee.description` sea null
+- Agregar el campo `ParticipationFee.id`
+- Agregar descripción a `ParticipationFee`
+- Agregar título y descripción a `ParticipationFee.value`
+- Agregar la lista de códigos de participaciónFeeType.csv para `ParticipationFee.type`
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/participation_fee/v1.1.3/codelists/index.html b/es/extensions/participation_fee/v1.1.3/codelists/index.html
new file mode 100644
index 000000000..cf12d97ea
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.3/codelists/index.html
@@ -0,0 +1,289 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Tipo de cuota/cargo + | +
+ Las cuotas que aplican a los ofertantes que participen en el proceso de licitaciones. Las cuotas pueden aplicar para tener acceso a documentos de la oferta, hacer presentación de ofertas o una cuota puede aplicar para el ofertante ganador. + + |
+ + array of strings + | +
+
+ value
+
+ |
+ + + | ++ + | ++ Value object + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Información adicional sobre la manera en que se cobran las cuotas o la naturaleza exacta de las mismas. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Métodos de pago + | +
+ Información opcional sobre la manera en que se pueden pagar las cuotas + + |
+ + array of strings + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Cuotas de participación + | +
+ Cualquier cuota que sea aplicable a los ofertantes que quieran participar en el proceso de contrataciones. Las cuotas pueden aplicar para tener acceso a documentos de compras, para hacer ofertas o cuotas que deben ser pagadas por el ofertante ganador. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.3/codelists/participationFeeType.csv b/es/extensions/participation_fee/v1.1.3/codelists/participationFeeType.csv
new file mode 100644
index 000000000..e5b0e873f
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.3/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Código,Título,Descripción
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/es/extensions/participation_fee/v1.1.3/extension.json b/es/extensions/participation_fee/v1.1.3/extension.json
new file mode 100644
index 000000000..6dacf2629
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.3/extension.json
@@ -0,0 +1,19 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting/ocds_participationFee_extension"
+ },
+ "codelists": [
+ "participationFeeType.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/es/extensions/participation_fee/v1.1.3/index.html b/es/extensions/participation_fee/v1.1.3/index.html
new file mode 100644
index 000000000..b82757099
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.3/index.html
@@ -0,0 +1,383 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.3/release-schema.json b/es/extensions/participation_fee/v1.1.3/release-schema.json
new file mode 100644
index 000000000..91b66f17f
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.3/release-schema.json
@@ -0,0 +1,73 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Cuota/Cargos de participaci\u00f3n",
+ "description": "Una tarifa que aplica a los ofertantes que quieren participar en el proceso de licitaciones. Las tarifas pueden aplicar para acceder los documentos de oferta, para enviar las ofertas o puede haber una cuota que debe ser pagada por el ofertante ganador",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "ID de tarifa",
+ "description": "Un identificador local de esta tarifa, \u00fanica en este bloque. Este campo se usa para hacer un seguimiento de m\u00faltiples revisiones de la tarifa a trav\u00e9s de la compilaci\u00f3n de los mecanismos de release y record",
+ "type": "string"
+ },
+ "type": {
+ "title": "Tipo de cuota/cargo",
+ "description": "Las cuotas que aplican a los ofertantes que participen en el proceso de licitaciones. Las cuotas pueden aplicar para tener acceso a documentos de la oferta, hacer presentaci\u00f3n de ofertas o una cuota puede aplicar para el ofertante ganador.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win"
+ ]
+ },
+ "codelist": "participationFeeType.csv",
+ "openCodelist": false
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor monetario de esta tarifa",
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Informaci\u00f3n adicional sobre la manera en que se cobran las cuotas o la naturaleza exacta de las mismas.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "methodOfPayment": {
+ "title": "M\u00e9todos de pago",
+ "description": "Informaci\u00f3n opcional sobre la manera en que se pueden pagar las cuotas",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Cuotas de participaci\u00f3n",
+ "description": "Cualquier cuota que sea aplicable a los ofertantes que quieran participar en el proceso de contrataciones. Las cuotas pueden aplicar para tener acceso a documentos de compras, para hacer ofertas o cuotas que deben ser pagadas por el ofertante ganador.",
+ "type": "array",
+ "mergeStrategy": "ocdsVersion",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/participation_fee/v1.1.3/schema/index.html b/es/extensions/participation_fee/v1.1.3/schema/index.html
new file mode 100644
index 000000000..26dcf0527
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.3/schema/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Antecedentes
+Hay una serie de casos en los que puede haber costos para acceder a los documentos o participar en un proceso de licitación.
+Los licitadores potenciales desearán estar enterados de los costos que un proceso puede implicar.
+Los monitores de adquisiciones tal vez deseen asegurarse de que los costos de participación estén dentro de los parámetros legales (a menudo fijados como un máximo fijo, o un porcentaje del valor total del contrato), o para controlar cómo se usan las cuotas de participación.
+Campos de extensión
+Esta extensión agrega un campo participationFees a la sección tender del OCDS e introduce un nuevo bloque participationFee.
El campo participationFees es una lista de bloques participationFee.
El bloque participationFee consta de tres campos:
-
+
type- un valor de la lista de códigosparticipationFeeType, que describe el tipo de costo
+value- el importe y la moneda del costo
+description- un campo opcional con más información sobre los requisitos del costo de participación. Por ejemplo, a veces un costo de un documento sólo es aplicable a la copia impresa de los documentos.
+methodOfPayment- un campo opcional que proporciona información sobre los métodos de pago aceptados para la documentación. Actualmente se trata de una serie de cadenas, pero se podría introducir una lista de códigos abierta en el futuro.
+
Listas de códigos de extensión
+Esta extensión agrega una lista de códigos cerrada participationFeeType con los siguientes códigos:
-
+
- document - una cuota a pagar por el acceso a los documentos de licitación +
- deposit - una cuota reembolsable a pagar por la presentación de ofertas +
- submission - una cuota no reembolsable a pagar por la presentación de ofertas +
- win - una cuota a pagar por el ganador +
Ejemplo
+El siguiente fragmento de JSON modela un proceso de contratación donde las tarifas son aplicables tanto para el acceso a documentos como para la presentación de ofertas:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+Notas de uso
+En algunos casos, se puede cobrar una cuota por las "copias oficiales" de los documentos de adquisición (aunque también se pueden obtener copias en línea de forma gratuita) y los licitadores deben probar que han pagado una copia oficial de los documentos como parte de su presentación.
+En este caso, la cuota debe ser modelada como un cargo de oferta, ya que la presentación sólo es posible cuando se ha pagado la cuota de acceso al documento.
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.3
+-
+
- No permitir que
ParticipationFee.typetenga null en su conjunto de strings
+ - Permitir que
ParticipationFee.descriptionsea null
+ - Agregar el campo
ParticipationFee.id
+ - Agregar descripción a
ParticipationFee
+ - Agregar título y descripción a
ParticipationFee.value
+ - Agregar la lista de códigos de participaciónFeeType.csv para
ParticipationFee.type
+ - Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.4/README.md b/es/extensions/participation_fee/v1.1.4/README.md
new file mode 100644
index 000000000..1d7f527fa
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.4/README.md
@@ -0,0 +1,89 @@
+# Cuotas de participación
+
+## Antecedentes
+
+Hay una serie de casos en los que puede haber costos para acceder a los documentos o participar en un proceso de licitación.
+
+Los licitadores potenciales desearán estar enterados de los costos que un proceso puede implicar.
+
+Los monitores de adquisiciones tal vez deseen asegurarse de que los costos de participación estén dentro de los parámetros legales (a menudo fijados como un máximo fijo, o un porcentaje del valor total del contrato), o para controlar cómo se usan las cuotas de participación.
+
+## Campos de extensión
+
+Esta extensión agrega un campo `participationFees` a la sección ` tender` del OCDS e introduce un nuevo bloque `participationFee`.
+
+El campo `participationFees` es una lista de bloques ` participationFee`.
+
+El bloque `participationFee` consta de tres campos:
+
+- `type` - un valor de la lista de códigos `participationFeeType`, que describe el tipo de costo
+- `value` - el importe y la moneda del costo
+- `description` - un campo opcional con más información sobre los requisitos del costo de participación. Por ejemplo, a veces un costo de un documento sólo es aplicable a la copia impresa de los documentos.
+- `methodOfPayment` - un campo opcional que proporciona información sobre los métodos de pago aceptados para la documentación. Actualmente se trata de una serie de cadenas, pero se podría introducir una lista de códigos abierta en el futuro.
+
+## Listas de códigos de extensión
+
+Esta extensión agrega una lista de códigos **cerrada** `participationFeeType` con los siguientes códigos:
+
+- document - una cuota a pagar por el acceso a los documentos de licitación
+- deposit - una cuota reembolsable a pagar por la presentación de ofertas
+- submission - una cuota no reembolsable a pagar por la presentación de ofertas
+- win - una cuota a pagar por el ganador
+
+## Ejemplo
+
+El siguiente fragmento de JSON modela un proceso de contratación donde las tarifas son aplicables tanto para el acceso a documentos como para la presentación de ofertas:
+
+```json
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+```
+
+## Notas de uso
+
+En algunos casos, se puede cobrar una cuota por las "copias oficiales" de los documentos de adquisición (aunque también se pueden obtener copias en línea de forma gratuita) y los licitadores deben probar que han pagado una copia oficial de los documentos como parte de su presentación.
+
+En este caso, la cuota debe ser modelada como un cargo de **oferta**, ya que la presentación sólo es posible cuando se ha pagado la cuota de acceso al documento.
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.4
+
+- Actualizar la propiedad `mergeStrategy` para la propiedad `wholeListMerge`
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- No permitir que `ParticipationFee.type` tenga null en su conjunto de strings
+- Permitir que `ParticipationFee.description` sea null
+- Agregar el campo `ParticipationFee.id`
+- Agregar descripción a `ParticipationFee`
+- Agregar título y descripción a `ParticipationFee.value`
+- Agregar la lista de códigos de participaciónFeeType.csv para `ParticipationFee.type`
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/participation_fee/v1.1.4/codelists/index.html b/es/extensions/participation_fee/v1.1.4/codelists/index.html
new file mode 100644
index 000000000..5290f6611
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.4/codelists/index.html
@@ -0,0 +1,289 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID de tarifa + | +
+ Un identificador local de esta tarifa, única en este bloque. Este campo se usa para hacer un seguimiento de múltiples revisiones de la tarifa a través de la compilación de los mecanismos de release y record + + |
+ + string + | +
+
+ type
+
+ |
+ + Tipo de cuota/cargo + | +
+ Las cuotas que aplican a los ofertantes que participen en el proceso de licitaciones. Las cuotas pueden aplicar para tener acceso a documentos de la oferta, hacer presentación de ofertas o una cuota puede aplicar para el ofertante ganador. + + |
+ + array of strings from closed participationFeeType codelist + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor monetario de esta tarifa + + |
+ + Value object + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Información adicional sobre la manera en que se cobran las cuotas o la naturaleza exacta de las mismas. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Métodos de pago + | +
+ Información opcional sobre la manera en que se pueden pagar las cuotas + + |
+ + array of strings + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Cuotas de participación + | +
+ Cualquier cuota que sea aplicable a los ofertantes que quieran participar en el proceso de contrataciones. Las cuotas pueden aplicar para tener acceso a documentos de compras, para hacer ofertas o cuotas que deben ser pagadas por el ofertante ganador. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.4/codelists/participationFeeType.csv b/es/extensions/participation_fee/v1.1.4/codelists/participationFeeType.csv
new file mode 100644
index 000000000..e5b0e873f
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.4/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Código,Título,Descripción
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/es/extensions/participation_fee/v1.1.4/extension.json b/es/extensions/participation_fee/v1.1.4/extension.json
new file mode 100644
index 000000000..636aa0a51
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.4/extension.json
@@ -0,0 +1,22 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/participation_fee/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "participationFeeType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/es/extensions/participation_fee/v1.1.4/index.html b/es/extensions/participation_fee/v1.1.4/index.html
new file mode 100644
index 000000000..c8cc62f03
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.4/index.html
@@ -0,0 +1,393 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.4/release-schema.json b/es/extensions/participation_fee/v1.1.4/release-schema.json
new file mode 100644
index 000000000..e5628a4d0
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.4/release-schema.json
@@ -0,0 +1,73 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Cuota/Cargos de participaci\u00f3n",
+ "description": "Una tarifa que aplica a los ofertantes que quieren participar en el proceso de licitaciones. Las tarifas pueden aplicar para acceder los documentos de oferta, para enviar las ofertas o puede haber una cuota que debe ser pagada por el ofertante ganador",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "ID de tarifa",
+ "description": "Un identificador local de esta tarifa, \u00fanica en este bloque. Este campo se usa para hacer un seguimiento de m\u00faltiples revisiones de la tarifa a trav\u00e9s de la compilaci\u00f3n de los mecanismos de release y record",
+ "type": "string"
+ },
+ "type": {
+ "title": "Tipo de cuota/cargo",
+ "description": "Las cuotas que aplican a los ofertantes que participen en el proceso de licitaciones. Las cuotas pueden aplicar para tener acceso a documentos de la oferta, hacer presentaci\u00f3n de ofertas o una cuota puede aplicar para el ofertante ganador.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win"
+ ]
+ },
+ "codelist": "participationFeeType.csv",
+ "openCodelist": false
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor monetario de esta tarifa",
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Informaci\u00f3n adicional sobre la manera en que se cobran las cuotas o la naturaleza exacta de las mismas.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "methodOfPayment": {
+ "title": "M\u00e9todos de pago",
+ "description": "Informaci\u00f3n opcional sobre la manera en que se pueden pagar las cuotas",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Cuotas de participaci\u00f3n",
+ "description": "Cualquier cuota que sea aplicable a los ofertantes que quieran participar en el proceso de contrataciones. Las cuotas pueden aplicar para tener acceso a documentos de compras, para hacer ofertas o cuotas que deben ser pagadas por el ofertante ganador.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true,
+ "wholeListMerge": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/participation_fee/v1.1.4/schema/index.html b/es/extensions/participation_fee/v1.1.4/schema/index.html
new file mode 100644
index 000000000..058ad39b1
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.4/schema/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Antecedentes
+Hay una serie de casos en los que puede haber costos para acceder a los documentos o participar en un proceso de licitación.
+Los licitadores potenciales desearán estar enterados de los costos que un proceso puede implicar.
+Los monitores de adquisiciones tal vez deseen asegurarse de que los costos de participación estén dentro de los parámetros legales (a menudo fijados como un máximo fijo, o un porcentaje del valor total del contrato), o para controlar cómo se usan las cuotas de participación.
+Campos de extensión
+Esta extensión agrega un campo participationFees a la sección tender del OCDS e introduce un nuevo bloque participationFee.
El campo participationFees es una lista de bloques participationFee.
El bloque participationFee consta de tres campos:
-
+
type- un valor de la lista de códigosparticipationFeeType, que describe el tipo de costo
+value- el importe y la moneda del costo
+description- un campo opcional con más información sobre los requisitos del costo de participación. Por ejemplo, a veces un costo de un documento sólo es aplicable a la copia impresa de los documentos.
+methodOfPayment- un campo opcional que proporciona información sobre los métodos de pago aceptados para la documentación. Actualmente se trata de una serie de cadenas, pero se podría introducir una lista de códigos abierta en el futuro.
+
Listas de códigos de extensión
+Esta extensión agrega una lista de códigos cerrada participationFeeType con los siguientes códigos:
-
+
- document - una cuota a pagar por el acceso a los documentos de licitación +
- deposit - una cuota reembolsable a pagar por la presentación de ofertas +
- submission - una cuota no reembolsable a pagar por la presentación de ofertas +
- win - una cuota a pagar por el ganador +
Ejemplo
+El siguiente fragmento de JSON modela un proceso de contratación donde las tarifas son aplicables tanto para el acceso a documentos como para la presentación de ofertas:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+Notas de uso
+En algunos casos, se puede cobrar una cuota por las "copias oficiales" de los documentos de adquisición (aunque también se pueden obtener copias en línea de forma gratuita) y los licitadores deben probar que han pagado una copia oficial de los documentos como parte de su presentación.
+En este caso, la cuota debe ser modelada como un cargo de oferta, ya que la presentación sólo es posible cuando se ha pagado la cuota de acceso al documento.
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.4
+-
+
- Actualizar la propiedad
mergeStrategypara la propiedadwholeListMerge
+ - Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que
ParticipationFee.typetenga null en su conjunto de strings
+ - Permitir que
ParticipationFee.descriptionsea null
+ - Agregar el campo
ParticipationFee.id
+ - Agregar descripción a
ParticipationFee
+ - Agregar título y descripción a
ParticipationFee.value
+ - Agregar la lista de códigos de participaciónFeeType.csv para
ParticipationFee.type
+ - Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.5/README.md b/es/extensions/participation_fee/v1.1.5/README.md
new file mode 100644
index 000000000..b531c9662
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.5/README.md
@@ -0,0 +1,86 @@
+# Cuotas de participación
+
+Esta extensión añade una matriz de los costos de participación al objeto de licitación, para revelar cualquier costo de participación en el proceso de contrataciones.
+
+El campo `id` se va a requerir en las futuras versiones de la extensión.
+
+## Contexto
+
+Algunas veces hay costos asociados con el acceso a documentos de licitaciones relacionados al proceso de contratación. Los licitadores potenciales quieren saber sobre esos costos. Los monitores de adquisiciones también deben de asegurar que los costos de participación estén dentro de los parámetros legales (generalmente se establecen con un valor fijo máximo, o como un porcentaje del valor total del contrato) o para monitorear como se usan las tarifas de participación.
+
+## Ejemplo
+
+El siguiente fragmento de JSON modela un proceso de contratación donde las tarifas son aplicables al acceso a documentos y para la presentación de ofertas:
+
+```json
+{
+ "tender": {
+ "participationFees": [
+ {
+ "id": "1",
+ "type": [
+ "document"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 8.0
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment": [
+ "wireTransfer",
+ "cheque"
+ ]
+ },
+ {
+ "id": "2",
+ "type": [
+ "submission"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.0
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment": [
+ "wireTransfer"
+ ]
+ }
+ ]
+ }
+}
+```
+
+## Notas de uso
+
+En algunos casos, se puede cobrar una cuota por las "copias oficiales" de los documentos de adquisición (aunque también se pueden obtener copias en línea de forma gratuita) y los licitadores deben probar que han pagado una copia oficial de los documentos como parte de su presentación. En ese caso, las tarifas deben de modelarse como una tarifa de **envío de documentos**, ya que solo se puede enviar los documentos una vez que la tarifa de acceso a los documentos se ha pagado.
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.5
+
+- Añadir el campo `id` al ejemplo en readme
+- Corregir la descripción del campo `ParticipationFee.type`
+- Combinar y conciliar descripciones de campos y códigos con esquemas y listas de códigos
+- Quitar la indicación de campos "opcionales"
+- Añadir la lista de código `methodOfPayment` de la \[extensión paymentMethod\] (https://github.com/INAImexico/ocds_paymentMethod_extension/blob/master/codelists/paymentMethod.csv)
+- Quitar la información sobre el tipo de las descripciones de los campos
+- Revisar las palabras normativas y no-normativas
+
+### v1.1.4
+
+- Actualizar la propiedad `mergeStrategy` para la propiedad `wholeListMerge`
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- No permitir que `ParticipationFee.type` tenga null en su conjunto de strings
+- Permitir que `ParticipationFee.description` sea null
+- Agregar el campo `ParticipationFee.id`
+- Agregar descripción a `ParticipationFee`
+- Agregar título y descripción a `ParticipationFee.value`
+- Agregar la lista de códigos de participaciónFeeType.csv para `ParticipationFee.type`
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/participation_fee/v1.1.5/codelists/index.html b/es/extensions/participation_fee/v1.1.5/codelists/index.html
new file mode 100644
index 000000000..eb187cfbb
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.5/codelists/index.html
@@ -0,0 +1,405 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID de tarifa + | +
+ Un identificador local de esta tarifa, única en este bloque. Este campo se usa para hacer un seguimiento de múltiples revisiones de la tarifa a través de la compilación de los mecanismos de release y record + + |
+ + string + | +
+
+ type
+
+ |
+ + Tipo de cuota/cargo + | +
+ Las cuotas que aplican a los ofertantes que participen en el proceso de licitaciones. Las cuotas pueden aplicar para tener acceso a documentos de la oferta, hacer presentación de ofertas o una cuota puede aplicar para el ofertante ganador. + + |
+ + array of strings from closed participationFeeType codelist + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor monetario de esta tarifa + + |
+ + Value object + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Información adicional sobre la manera en que se cobran las cuotas o la naturaleza exacta de las mismas. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Métodos de pago + | +
+ Información opcional sobre la manera en que se pueden pagar las cuotas + + |
+ + array of strings + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Cuotas de participación + | +
+ Cualquier cuota que sea aplicable a los ofertantes que quieran participar en el proceso de contrataciones. Las cuotas pueden aplicar para tener acceso a documentos de compras, para hacer ofertas o cuotas que deben ser pagadas por el ofertante ganador. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.5/codelists/methodOfPayment.csv b/es/extensions/participation_fee/v1.1.5/codelists/methodOfPayment.csv
new file mode 100644
index 000000000..463ee8431
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.5/codelists/methodOfPayment.csv
@@ -0,0 +1,7 @@
+Código,Título,Descripción
+cash,Cash,"The payment is made in cash, such as banknotes and coins."
+check,Check,"The payment is made by check (also written as ""cheque"")."
+creditCard,Credit card,The payment is made by credit card.
+directDebit,Direct debit,"The payment is made by direct debit, also known as direct withdrawal, pre-authorized debit (PAD) or pre-authorized payment (PAP)."
+letterOfCredit,Letter of credit,The payment is made by letter of credit.
+wireTransfer,Wire transfer,"The payment is made by wire transfer, also known as bank transfer or credit transfer."
diff --git a/es/extensions/participation_fee/v1.1.5/codelists/participationFeeType.csv b/es/extensions/participation_fee/v1.1.5/codelists/participationFeeType.csv
new file mode 100644
index 000000000..e5b0e873f
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.5/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Código,Título,Descripción
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/es/extensions/participation_fee/v1.1.5/extension.json b/es/extensions/participation_fee/v1.1.5/extension.json
new file mode 100644
index 000000000..e5770843c
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.5/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/participation_fee/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "participationFeeType.csv",
+ "methodOfPayment.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/participation_fee/v1.1.5/index.html b/es/extensions/participation_fee/v1.1.5/index.html
new file mode 100644
index 000000000..95a7b7b67
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.5/index.html
@@ -0,0 +1,390 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ methodOfPayment.csv +
+ +
+ You can download the methodOfPayment.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ cash
+
+ |
+ + Cash + | +
+ The payment is made in cash, such as banknotes and coins. + + |
+
+
+ check
+
+ |
+ + Check + | +
+ The payment is made by check (also written as "cheque"). + + |
+
+
+ creditCard
+
+ |
+ + Credit card + | +
+ The payment is made by credit card. + + |
+
+
+ directDebit
+
+ |
+ + Direct debit + | +
+ The payment is made by direct debit, also known as direct withdrawal, pre-authorized debit (PAD) or pre-authorized payment (PAP). + + |
+
+
+ letterOfCredit
+
+ |
+ + Letter of credit + | +
+ The payment is made by letter of credit. + + |
+
+
+ wireTransfer
+
+ |
+ + Wire transfer + | +
+ The payment is made by wire transfer, also known as bank transfer or credit transfer. + + |
+
+ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1.5/release-schema.json b/es/extensions/participation_fee/v1.1.5/release-schema.json
new file mode 100644
index 000000000..a43920576
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.5/release-schema.json
@@ -0,0 +1,76 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Cuota/Cargos de participaci\u00f3n",
+ "description": "Una tarifa que aplica a los ofertantes que quieren participar en el proceso de licitaciones. Las tarifas pueden aplicar para acceder los documentos de oferta, para enviar las ofertas o puede haber una cuota que debe ser pagada por el ofertante ganador.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "ID de tarifa",
+ "description": "Un identificador local de esta tarifa, \u00fanica en este bloque. Este campo se usa para hacer un seguimiento de m\u00faltiples revisiones de la tarifa a trav\u00e9s de la compilaci\u00f3n de los mecanismos de release y record",
+ "type": "string"
+ },
+ "type": {
+ "title": "Tipo de cuota/cargo",
+ "description": "El tipo de esta tarifa.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win"
+ ]
+ },
+ "codelist": "participationFeeType.csv",
+ "openCodelist": false
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor monetario de esta tarifa",
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Informaci\u00f3n adicional sobre esta tarifa, por ejemplo: casos espec\u00edficos en los que la tarifa es aplicable (ej. s\u00f3lo para copias f\u00edsicas de documentos), la manera en la cual la tarifa es cobrada o la naturaleza exacta de la tarifa.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "methodOfPayment": {
+ "title": "M\u00e9todo(s) de pago",
+ "description": "Las v\u00edas aceptadas para el pago de las tarifas.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ },
+ "uniqueItems": true,
+ "codelist": "methodOfPayment.csv",
+ "openCodelist": true
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Cuotas de participaci\u00f3n",
+ "description": "Cualquier tarifa aplicable a los ofertantes que quieren participar en el proceso de licitaciones. Las tarifas pueden aplicar para acceder los documentos de oferta, para enviar las ofertas o puede haber una cuota que debe ser pagada por el ofertante ganador.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true,
+ "wholeListMerge": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/participation_fee/v1.1.5/schema/index.html b/es/extensions/participation_fee/v1.1.5/schema/index.html
new file mode 100644
index 000000000..feb9d63b3
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1.5/schema/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Esta extensión añade una matriz de los costos de participación al objeto de licitación, para revelar cualquier costo de participación en el proceso de contrataciones.
+El campo id se va a requerir en las futuras versiones de la extensión.
Contexto
+Algunas veces hay costos asociados con el acceso a documentos de licitaciones relacionados al proceso de contratación. Los licitadores potenciales quieren saber sobre esos costos. Los monitores de adquisiciones también deben de asegurar que los costos de participación estén dentro de los parámetros legales (generalmente se establecen con un valor fijo máximo, o como un porcentaje del valor total del contrato) o para monitorear como se usan las tarifas de participación.
+Ejemplo
+El siguiente fragmento de JSON modela un proceso de contratación donde las tarifas son aplicables al acceso a documentos y para la presentación de ofertas:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "id": "1",
+ "type": [
+ "document"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 8.0
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment": [
+ "wireTransfer",
+ "cheque"
+ ]
+ },
+ {
+ "id": "2",
+ "type": [
+ "submission"
+ ],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.0
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment": [
+ "wireTransfer"
+ ]
+ }
+ ]
+ }
+}
+Notas de uso
+En algunos casos, se puede cobrar una cuota por las "copias oficiales" de los documentos de adquisición (aunque también se pueden obtener copias en línea de forma gratuita) y los licitadores deben probar que han pagado una copia oficial de los documentos como parte de su presentación. En ese caso, las tarifas deben de modelarse como una tarifa de envío de documentos, ya que solo se puede enviar los documentos una vez que la tarifa de acceso a los documentos se ha pagado.
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.5
+-
+
- Añadir el campo
idal ejemplo en readme
+ - Corregir la descripción del campo
ParticipationFee.type
+ - Combinar y conciliar descripciones de campos y códigos con esquemas y listas de códigos +
- Quitar la indicación de campos "opcionales" +
- Añadir la lista de código
methodOfPaymentde la [extensión paymentMethod] (https://github.com/INAImexico/ocds_paymentMethod_extension/blob/master/codelists/paymentMethod.csv)
+ - Quitar la información sobre el tipo de las descripciones de los campos +
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- Actualizar la propiedad
mergeStrategypara la propiedadwholeListMerge
+ - Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- No permitir que
ParticipationFee.typetenga null en su conjunto de strings
+ - Permitir que
ParticipationFee.descriptionsea null
+ - Agregar el campo
ParticipationFee.id
+ - Agregar descripción a
ParticipationFee
+ - Agregar título y descripción a
ParticipationFee.value
+ - Agregar la lista de códigos de participaciónFeeType.csv para
ParticipationFee.type
+ - Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1/README.md b/es/extensions/participation_fee/v1.1/README.md
new file mode 100644
index 000000000..9691a4eea
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1/README.md
@@ -0,0 +1,73 @@
+# Cuotas de participación
+
+## Antecedentes
+
+Hay una serie de casos en los que puede haber costos para acceder a los documentos o participar en un proceso de licitación.
+
+Los licitadores potenciales desearán estar enterados de los costos que un proceso puede implicar.
+
+Los monitores de adquisiciones tal vez deseen asegurarse de que los costos de participación estén dentro de los parámetros legales (a menudo fijados como un máximo fijo, o un porcentaje del valor total del contrato), o para controlar cómo se usan las cuotas de participación.
+
+## Campos de extensión
+
+Esta extensión agrega un campo `participationFees` a la sección ` tender` del OCDS e introduce un nuevo bloque `participationFee`.
+
+El campo `participationFees` es una matriz de bloques ` participationFee`.
+
+El bloque `participationFee` consta de tres campos:
+
+- `type` - un valor de la lista de códigos `participationFeeType`, que describe el tipo de cuota
+- `value` - el importe y la moneda de la cuota
+- `description` - un campo opcional con más información sobre los requisitos de la cuota. Por ejemplo, a veces una cuota de documento sólo es aplicable a la copia impresa de los documentos.
+- `methodOfPayment` - un campo opcional que proporciona información sobre los métodos de pago aceptados para la documentación. Actualmente se trata de una serie de cadenas, pero se podría introducir una lista de códigos abierta en el futuro.
+
+## Listas de códigos de extensión
+
+Esta extensión agrega una lista de códigos **cerrada** `participationFeeType` con los siguientes códigos:
+
+- document - una cuota a pagar por el acceso a los documentos de licitación
+- deposit - una cuota reembolsable a pagar por la presentación de ofertas
+- submission - una cuota no reembolsable a pagar por la presentación de ofertas
+- win - una cuota a pagar por el ganador
+
+## Ejemplo
+
+El siguiente fragmento de JSON modela un proceso de contratación donde las tarifas son aplicables tanto para el acceso a documentos como para la presentación de ofertas:
+
+```JSON
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+```
+
+## Notas de uso
+
+En algunos casos, se puede cobrar una cuota por las "copias oficiales" de los documentos de adquisición (aunque también se pueden obtener copias en línea de forma gratuita) y los licitadores deben probar que han pagado una copia oficial de los documentos como parte de su presentación.
+
+En este caso, la cuota debe ser modelada como un cargo de **oferta**, ya que la presentación sólo es posible cuando se ha pagado la cuota de acceso al documento.
+
+## Por hacer
+
+- Terminología de participación / presentación
+- finalizar lista de código
diff --git a/es/extensions/participation_fee/v1.1/codelists/index.html b/es/extensions/participation_fee/v1.1/codelists/index.html
new file mode 100644
index 000000000..232bce272
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1/codelists/index.html
@@ -0,0 +1,289 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID de tarifa + | +
+ Un identificador local de esta tarifa, única en este bloque. Este campo se usa para hacer un seguimiento de múltiples revisiones de la tarifa a través de la compilación de los mecanismos de release y record + + |
+ + string + | +
+
+ type
+
+ |
+ + Tipo de cuota/cargo + | +
+ El tipo de esta tarifa. + + |
+ + array of strings from closed participationFeeType codelist + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor monetario de esta tarifa + + |
+ + Value object + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Información adicional sobre esta tarifa, por ejemplo: casos específicos en los que la tarifa es aplicable (ej. sólo para copias físicas de documentos), la manera en la cual la tarifa es cobrada o la naturaleza exacta de la tarifa. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Método(s) de pago + | +
+ Las vías aceptadas para el pago de las tarifas. + + |
+ + array of strings from open methodOfPayment codelist + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Cuotas de participación + | +
+ Cualquier tarifa aplicable a los ofertantes que quieren participar en el proceso de licitaciones. Las tarifas pueden aplicar para acceder los documentos de oferta, para enviar las ofertas o puede haber una cuota que debe ser pagada por el ofertante ganador. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1/codelists/participationFeeType.csv b/es/extensions/participation_fee/v1.1/codelists/participationFeeType.csv
new file mode 100644
index 000000000..e5b0e873f
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1/codelists/participationFeeType.csv
@@ -0,0 +1,5 @@
+Código,Título,Descripción
+document,Document,A fee payable for access to bidding documents.
+deposit,Deposit,A refundable fee payable for the submission of bids.
+submission,Submission,A non-refundable fee payable for the submission of bids.
+win,Win,A fee payable by the winning bidder.
diff --git a/es/extensions/participation_fee/v1.1/extension.json b/es/extensions/participation_fee/v1.1/extension.json
new file mode 100644
index 000000000..c6284aacc
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1/extension.json
@@ -0,0 +1,14 @@
+{
+ "name": {
+ "en": "Participation Fees",
+ "es": "Cuotas/Cargos de participaci\u00f3n"
+ },
+ "description": {
+ "en": "Where a tender process involves payment of fees to access documents, submit a proposal, or be awarded a contract, this extension can be used to provide fee details.",
+ "es": "Cuando un proceso de licitaci\u00f3n implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensi\u00f3n se puede utilizar para proporcionar detalles de la tasa."
+ },
+ "documentationUrl": {},
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/es/extensions/participation_fee/v1.1/index.html b/es/extensions/participation_fee/v1.1/index.html
new file mode 100644
index 000000000..d6ad36796
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1/index.html
@@ -0,0 +1,365 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ participationFeeType.csv +
+ +
+ You can download the participationFeeType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ document
+
+ |
+ + Document + | +
+ A fee payable for access to bidding documents. + + |
+
+
+ deposit
+
+ |
+ + Deposit + | +
+ A refundable fee payable for the submission of bids. + + |
+
+
+ submission
+
+ |
+ + Submission + | +
+ A non-refundable fee payable for the submission of bids. + + |
+
+
+ win
+
+ |
+ + Win + | +
+ A fee payable by the winning bidder. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/participation_fee/v1.1/release-schema.json b/es/extensions/participation_fee/v1.1/release-schema.json
new file mode 100644
index 000000000..ca8e0b8c7
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1/release-schema.json
@@ -0,0 +1,61 @@
+{
+ "definitions": {
+ "ParticipationFee": {
+ "title": "Cuota/Cargos de participaci\u00f3n",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Tipo de cuota/cargo",
+ "description": "Las cuotas que aplican a los ofertantes que participen en el proceso de licitaciones. Las cuotas pueden aplicar para tener acceso a documentos de la oferta, hacer presentaci\u00f3n de ofertas o una cuota puede aplicar para el ofertante ganador.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "document",
+ "deposit",
+ "submission",
+ "win",
+ null
+ ]
+ }
+ },
+ "value": {
+ "$ref": "#/definitions/Value"
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Informaci\u00f3n adicional sobre la manera en que se cobran las cuotas o la naturaleza exacta de las mismas.",
+ "type": "string"
+ },
+ "methodOfPayment": {
+ "title": "M\u00e9todos de pago",
+ "description": "Informaci\u00f3n opcional sobre la manera en que se pueden pagar las cuotas",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "participationFees": {
+ "title": "Cuotas de participaci\u00f3n",
+ "description": "Cualquier cuota que sea aplicable a los ofertantes que quieran participar en el proceso de contrataciones. Las cuotas pueden aplicar para tener acceso a documentos de compras, para hacer ofertas o cuotas que deben ser pagadas por el ofertante ganador.",
+ "type": "array",
+ "mergeStrategy": "ocdsVersion",
+ "items": {
+ "$ref": "#/definitions/ParticipationFee"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/participation_fee/v1.1/schema/index.html b/es/extensions/participation_fee/v1.1/schema/index.html
new file mode 100644
index 000000000..d2db89ef0
--- /dev/null
+++ b/es/extensions/participation_fee/v1.1/schema/index.html
@@ -0,0 +1,358 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Antecedentes
+Hay una serie de casos en los que puede haber costos para acceder a los documentos o participar en un proceso de licitación.
+Los licitadores potenciales desearán estar enterados de los costos que un proceso puede implicar.
+Los monitores de adquisiciones tal vez deseen asegurarse de que los costos de participación estén dentro de los parámetros legales (a menudo fijados como un máximo fijo, o un porcentaje del valor total del contrato), o para controlar cómo se usan las cuotas de participación.
+Campos de extensión
+Esta extensión agrega un campo participationFees a la sección tender del OCDS e introduce un nuevo bloque participationFee.
El campo participationFees es una matriz de bloques participationFee.
El bloque participationFee consta de tres campos:
-
+
type- un valor de la lista de códigosparticipationFeeType, que describe el tipo de cuota
+value- el importe y la moneda de la cuota
+description- un campo opcional con más información sobre los requisitos de la cuota. Por ejemplo, a veces una cuota de documento sólo es aplicable a la copia impresa de los documentos.
+methodOfPayment- un campo opcional que proporciona información sobre los métodos de pago aceptados para la documentación. Actualmente se trata de una serie de cadenas, pero se podría introducir una lista de códigos abierta en el futuro.
+
Listas de códigos de extensión
+Esta extensión agrega una lista de códigos cerrada participationFeeType con los siguientes códigos:
-
+
- document - una cuota a pagar por el acceso a los documentos de licitación +
- deposit - una cuota reembolsable a pagar por la presentación de ofertas +
- submission - una cuota no reembolsable a pagar por la presentación de ofertas +
- win - una cuota a pagar por el ganador +
Ejemplo
+El siguiente fragmento de JSON modela un proceso de contratación donde las tarifas son aplicables tanto para el acceso a documentos como para la presentación de ofertas:
+{
+ "tender": {
+ "participationFees": [
+ {
+ "type": "document",
+ "value": {
+ "currency": "GBP",
+ "amount": 8.00
+ },
+ "description": "Fee payable for both soft and hard copies of documents.",
+ "methodOfPayment":["electronic","cheque"]
+ },
+ {
+ "type": ["submission"],
+ "value": {
+ "currency": "GBP",
+ "amount": 10.00
+ },
+ "description": "Fee payable within e-procurement system.",
+ "methodOfPayment":["electronic"]
+ }
+ ]
+ }
+}
+Notas de uso
+En algunos casos, se puede cobrar una cuota por las "copias oficiales" de los documentos de adquisición (aunque también se pueden obtener copias en línea de forma gratuita) y los licitadores deben probar que han pagado una copia oficial de los documentos como parte de su presentación.
+En este caso, la cuota debe ser modelada como un cargo de oferta, ya que la presentación sólo es posible cuando se ha pagado la cuota de acceso al documento.
+Por hacer
+-
+
- Terminología de participación / presentación +
- finalizar lista de código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/partyScale/index.html b/es/extensions/partyScale/index.html
new file mode 100644
index 000000000..f7b53ccff
--- /dev/null
+++ b/es/extensions/partyScale/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cuotas/Cargos de participación +
+ ++ Cuando un proceso de licitación implica el pago de cargos para acceder a los documentos, presentar una propuesta, o ser adjudicado un contrato, esta extensión se puede utilizar para proporcionar detalles de la tasa. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ ParticipationFee +
+ +
+ The extension defines a new ParticipationFee object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Tipo de cuota/cargo + | +
+ Las cuotas que aplican a los ofertantes que participen en el proceso de licitaciones. Las cuotas pueden aplicar para tener acceso a documentos de la oferta, hacer presentación de ofertas o una cuota puede aplicar para el ofertante ganador. + + |
+ + array of strings + | +
+
+ value
+
+ |
+ + + | ++ + | ++ Value object + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Información adicional sobre la manera en que se cobran las cuotas o la naturaleza exacta de las mismas. + + |
+ + string + | +
+
+ methodOfPayment
+
+ |
+ + Métodos de pago + | +
+ Información opcional sobre la manera en que se pueden pagar las cuotas + + |
+ + array of strings + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ participationFees
+
+ |
+ + Cuotas de participación + | +
+ Cualquier cuota que sea aplicable a los ofertantes que quieran participar en el proceso de contrataciones. Las cuotas pueden aplicar para tener acceso a documentos de compras, para hacer ofertas o cuotas que deben ser pagadas por el ofertante ganador. + + |
+ + array of ParticipationFee objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/partyScale/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/partyScale/master/codelists/partyScale.csv b/es/extensions/partyScale/master/codelists/partyScale.csv
new file mode 100644
index 000000000..610f8d1b5
--- /dev/null
+++ b/es/extensions/partyScale/master/codelists/partyScale.csv
@@ -0,0 +1,7 @@
+Código,Título,Descripción
+micro,Micro,"This a micro enterprise, according to the definitions used by the procuring entity or buyer."
+sme,Small or medium enterprise,"This is a Small or Medium Enterprise (SME), according to the definitions used by the procuring entity or buyer."
+small,Small,"This is a small enterprise, according to the definitions used by the procuring entity or buyer."
+medium,Medium,"This is a medium enterprise, according to the definitions used by the procuring entity or buyer."
+large,Large,"This is a large enterprise, according to the definitions used by the procuring entity or buyer."
+selfEmployed,Self-employed individual,"This is a self-employed natural person, also known as a sole trader."
diff --git a/es/extensions/partyScale/master/extension.json b/es/extensions/partyScale/master/extension.json
new file mode 100644
index 000000000..af0f1361c
--- /dev/null
+++ b/es/extensions/partyScale/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Organization scale",
+ "es": "Organization scale"
+ },
+ "description": {
+ "en": "For classifying organizations as micro, sme or large.",
+ "es": "Para clasificar organizaciones como micro, PyME or grande"
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/partyScale/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "partyScale.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/partyScale/master/index.html b/es/extensions/partyScale/master/index.html
new file mode 100644
index 000000000..d79b3b5bd
--- /dev/null
+++ b/es/extensions/partyScale/master/index.html
@@ -0,0 +1,367 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization scale +
+ ++ Para clasificar organizaciones como micro, PyME or grande +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ partyScale.csv +
+ +
+ You can download the partyScale.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ micro
+
+ |
+ + Micro + | +
+ This a micro enterprise, according to the definitions used by the procuring entity or buyer. + + |
+
+
+ sme
+
+ |
+ + Small or medium enterprise + | +
+ This is a Small or Medium Enterprise (SME), according to the definitions used by the procuring entity or buyer. + + |
+
+
+ small
+
+ |
+ + Small + | +
+ This is a small enterprise, according to the definitions used by the procuring entity or buyer. + + |
+
+
+ medium
+
+ |
+ + Medium + | +
+ This is a medium enterprise, according to the definitions used by the procuring entity or buyer. + + |
+
+
+ large
+
+ |
+ + Large + | +
+ This is a large enterprise, according to the definitions used by the procuring entity or buyer. + + |
+
+
+ selfEmployed
+
+ |
+ + Self-employed individual + | +
+ This is a self-employed natural person, also known as a sole trader. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/partyScale/master/release-schema.json b/es/extensions/partyScale/master/release-schema.json
new file mode 100644
index 000000000..667da6697
--- /dev/null
+++ b/es/extensions/partyScale/master/release-schema.json
@@ -0,0 +1,31 @@
+{
+ "definitions": {
+ "Organization": {
+ "properties": {
+ "details": {
+ "properties": {
+ "scale": {
+ "title": "Escala",
+ "description": "El tama\u00f1o o escala de la organizaci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "partyScale.csv",
+ "openCodelist": false,
+ "enum": [
+ "micro",
+ "sme",
+ "small",
+ "medium",
+ "large",
+ "selfEmployed",
+ null
+ ]
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/partyScale/master/schema/index.html b/es/extensions/partyScale/master/schema/index.html
new file mode 100644
index 000000000..cb1655ded
--- /dev/null
+++ b/es/extensions/partyScale/master/schema/index.html
@@ -0,0 +1,255 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization scale +
+ ++ Para clasificar organizaciones como micro, PyME or grande +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Esta extensión añade un campo scale al objetoparties.details para indicar el tamaño o la escala de una organización, en particular de empresas comerciales u operadores económicos.
Esta información se puede utilizar para calcular estadísticas de contrataciones, como la proporción de contratos adjudicados a micro, pequeñas y medianas empresas.
+Los códigos de la lista de códigos partyScale.csv no tienen definiciones precisas y, en cambio, se rigen por las leyes y regulaciones locales, por ejemplo:
-
+
- OECD: Pequeñas y medianas empresas definición (SMEs) +
- Comisión Europea: ¿Qué son las pequeñas y medianas empresas (SME)? +
Guía
+Para las pequeñas y medianas empresas, si puede distinguir entre los dos tamaños, utilice los códigos 'small' y 'medium'. De lo contrario, use el código 'sme'.
+Para los trabajadores autónomos y los comerciantes individuales, si puede distinguirlos de las microempresas, utilice el código 'selfEmployed'. De lo contrario, use el código 'micro'.
+Para empresas sin empleados, use el código 'micro'.
+Ejemplo
+{
+ "parties": [
+ {
+ "id": "GB-COH-1234567844",
+ "name": "AnyCorp Cycle Provision",
+ "details": {
+ "scale": "sme"
+ }
+ }
+ ]
+}
+Registro de cambios
+2020-05-20
+-
+
- Agregue el código 'selfEmployed' a
partyScale.csv
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2020-03-11
+-
+
- Aclarar el uso de los códigos +
2020-03-10
+-
+
- Agregue códigos 'small' y 'medium' a
partyScale.csv
+
2018-05-22
+-
+
- Agregue una descripción al código 'large' en
partyScale.csv
+
2018-05-21
+-
+
- Eliminar el código '' de
partyScale.csv
+
2018-01-09
+-
+
- Agregue la lista de códigos partyScale.csv para
Organization.details.scale
+
Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/performance_failures/index.html b/es/extensions/performance_failures/index.html
new file mode 100644
index 000000000..736fd0fe0
--- /dev/null
+++ b/es/extensions/performance_failures/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Organization scale +
+ ++ Para clasificar organizaciones como micro, PyME or grande +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ details
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+ details.
+ |
+ + Escala + | +
+ El tamaño o escala de la organización. + + |
+ + string from closed partyScale codelist + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/performance_failures/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/performance_failures/master/release-schema.json b/es/extensions/performance_failures/master/release-schema.json
new file mode 100644
index 000000000..0eab246f4
--- /dev/null
+++ b/es/extensions/performance_failures/master/release-schema.json
@@ -0,0 +1,83 @@
+{
+ "definitions": {
+ "PerformanceFailure": {
+ "title": "Divulgaci\u00f3n de los fallos de funcionamiento",
+ "description": "Detalles de los incumplimientos para un determinado periodo y categor\u00eda. Los detalles de las penalizaciones y reducciones contempladas en el contrato, impuestas y pagadas tambi\u00e9n pueden ser provistas.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "Un identificador local para esta categor\u00eda espec\u00edfica y el periodo de falla en el desempe\u00f1o. Este campo se usa para llevar registro de las revisiones de un cargo a lo largo de varias entregas de OCDS.",
+ "type": "string",
+ "minLength": 1
+ },
+ "period": {
+ "title": "Periodo de falla en el desempe\u00f1o",
+ "description": "El periodo de notificaci\u00f3n de los fallos de rendimiento.",
+ "$ref": "#/definitions/Period"
+ },
+ "category": {
+ "title": "Categor\u00eda de la falla en el desempe\u00f1o",
+ "description": "La categor\u00eda de los fallos de rendimiento.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "events": {
+ "title": "N\u00famero de eventos",
+ "description": "El n\u00famero de fallos de rendimiento para este periodo y categor\u00eda.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "penaltyContracted": {
+ "title": "Penalizaci\u00f3n contractual",
+ "description": "Descripci\u00f3n de la penalizaci\u00f3n o reducci\u00f3n prevista en el contrato para este periodo, categor\u00eda y n\u00famero de fallos de incumplimiento.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "penaltyImposed": {
+ "title": "Penalizaci\u00f3n impuesta",
+ "description": "Una descripci\u00f3n de la penalizaci\u00f3n o reducci\u00f3n impuesta para este periodo, categor\u00eda y n\u00famero de fallos de incumplimiento.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "penaltyPaid": {
+ "title": "Penalizaci\u00f3n pagada",
+ "description": "Si se ha pagado la penalizaci\u00f3n impuesta para este periodo, categor\u00eda y n\u00famero de fallos de incumplimiento.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ },
+ "minProperties": 1
+ },
+ "Implementation": {
+ "properties": {
+ "performanceFailures": {
+ "title": "Incumplimiento de divulgaci\u00f3n",
+ "description": "Una lista de incumplimientos de divulgaci\u00f3n, detallando los incumplimientos para diferentes periodos y categor\u00edas.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/PerformanceFailure"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/performance_failures/master/schema/index.html b/es/extensions/performance_failures/master/schema/index.html
new file mode 100644
index 000000000..14e82f5b1
--- /dev/null
+++ b/es/extensions/performance_failures/master/schema/index.html
@@ -0,0 +1,384 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Fallos de desempleño +
+ ++ Agrega campos a la sección de implementación para permitir la divulgación de una serie de fallas de rendimiento de contratación. Basado en la tabla de informes de fallas de rendimiento definida en el Marco de Divulgación para el Banco Mundial en las APP. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+El [Marco de divulgación en las Asociaciones Público-Privadas] (http://pubdocs.worldbank.org/en/773541448296707678/Disclosure-in-PPPs-Framework.pdf) requiere la divulgación de casos de incumplimiento durante la duración de un contrato, junto con las sanciones o reducciones definidas, impuestas y pagadas en relación con cada categoría de incumplimiento.
+Ejemplo
+El fragmento de JSON a continuación modela los incumplimientos reportados para un solo período y categoría.
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "implementation": {
+ "performanceFailures": [
+ {
+ "id": "1",
+ "period": {
+ "startDate": "2016-01-01T00:00:00Z",
+ "endDate": "2016-12-31T23:59:59Z"
+ },
+ "category": "Daily average journey time exceeds 10 minutes",
+ "events": 73,
+ "penaltyContracted": "If the daily average journey time exceeds 10 minutes on more than 52 days per calendar year the project company will be subject to a penalty charge equal to (days - 52) * avgToll. Where days is the total number of days where the average journey time exceeded 10 minutes and avgToll is the average daily toll revenue to the project company over the calendar year in which the failures occurred.",
+ "penaltyImposed": "A penalty of £3,360,000 was imposed",
+ "penaltyPaid": true
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-03-20
+-
+
- Agregar
"minLength": 1en los campos de cadena obligatorios.
+ - Hacer
PerformanceFailure.periodno nulo (deshacer el cambio anterior), dado que se refiere al objetoPeriod.
+
2018-05-08
+-
+
- Hacer
PerformanceFailure.idobligatorio para soportar el seguimiento de revisiones y fusión de listas
+
2018-01-29
+-
+
- Hacer que
PerformanceFailure.periodpueda ser nulo.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/ppp/index.html b/es/extensions/ppp/index.html
new file mode 100644
index 000000000..2e21c1689
--- /dev/null
+++ b/es/extensions/ppp/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Fallos de desempleño +
+ ++ Agrega campos a la sección de implementación para permitir la divulgación de una serie de fallas de rendimiento de contratación. Basado en la tabla de informes de fallas de rendimiento definida en el Marco de Divulgación para el Banco Mundial en las APP. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ PerformanceFailure +
+ +
+ The extension defines a new PerformanceFailure object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ Un identificador local para esta categoría específica y el periodo de falla en el desempeño. Este campo se usa para llevar registro de las revisiones de un cargo a lo largo de varias entregas de OCDS. + + |
+ + string + | +
+
+ period
+
+ |
+ + Periodo de falla en el desempeño + | +
+ El periodo de notificación de los fallos de rendimiento. + + |
+ + Period object + | +
+
+ category
+
+ |
+ + Categoría de la falla en el desempeño + | +
+ La categoría de los fallos de rendimiento. + + |
+ + string + | +
+
+ events
+
+ |
+ + Número de eventos + | +
+ El número de fallos de rendimiento para este periodo y categoría. + + |
+ + number + | +
+
+ penaltyContracted
+
+ |
+ + Penalización contractual + | +
+ Descripción de la penalización o reducción prevista en el contrato para este periodo, categoría y número de fallos de incumplimiento. + + |
+ + string + | +
+
+ penaltyImposed
+
+ |
+ + Penalización impuesta + | +
+ Una descripción de la penalización o reducción impuesta para este periodo, categoría y número de fallos de incumplimiento. + + |
+ + string + | +
+
+ penaltyPaid
+
+ |
+ + Penalización pagada + | +
+ Si se ha pagado la penalización impuesta para este periodo, categoría y número de fallos de incumplimiento. + + |
+ + boolean + | +
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ performanceFailures
+
+ |
+ + Incumplimiento de divulgación + | +
+ Una lista de incumplimientos de divulgación, detallando los incumplimientos para diferentes periodos y categorías. + + |
+ + array of PerformanceFailure objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/ppp/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/ppp/master/codelists/metricID.csv b/es/extensions/ppp/master/codelists/metricID.csv
new file mode 100644
index 000000000..5b6651b70
--- /dev/null
+++ b/es/extensions/ppp/master/codelists/metricID.csv
@@ -0,0 +1,4 @@
+Código,Título,Descripción
+demand,Demand,For reporting on forecast or actual demand
+revenue,Revenue,For reporting on forecast or actual revenues
+IRR,Internal rate of return,For reporting on forecast or actual project IRR
diff --git a/es/extensions/ppp/master/codelists/milestoneCode.csv b/es/extensions/ppp/master/codelists/milestoneCode.csv
new file mode 100644
index 000000000..109685ee1
--- /dev/null
+++ b/es/extensions/ppp/master/codelists/milestoneCode.csv
@@ -0,0 +1,10 @@
+Código,Título,Descripción,Fuente,Notas
+projectApproval,Project approval,The dates of approvals from relevant authorities.,https://github.com/open-contracting/ocds-milestones-update,milestone/type = approval
+commercialClose,Commercial close,"In a financing, the point at which the commercial documentation has been executed but before conditions precedent have been satisfied or waived; before financial close.",https://pppknowledgelab.org/glossary#Commercial_Close,milestone/type = contractClose
+financialClose,Financial close,"In a financing, the point at which the documentation has been executed and conditions precedent have been satisfied or waived. Drawdowns become permissible after this point.",https://pppknowledgelab.org/glossary#Financial_Close,milestone/type = contractClose
+commencement,Commencement of construction or development,The date of commencement of construction or development,,milestone/type = delivery
+completion,Completion of construction of development,The date of completion of construction or development,,milestone/type = delivery
+commissioning,Commissioning,The testing and inspection of the completed works to verify that the works are ready for commercial operation.,https://pppknowledgelab.org/glossary#Commissioning,milestone/type = delivery
+enquiryPeriodStart,Enquiry period start,"For processes with multiple enquiry periods, the start date of a period during which enquiries can be made and responded to which is not provided in the tender/enquiryPeriod block. Sometimes known as clarification periods.",,milestone/type = procurement
+enquiryPeriodEnd,Enquiry period end,"For processes with multiple enquiry periods, the end date of a period during which enquiries can be made and responded to which is not provided in the tender/enquiryPeriod block. Sometimes known as clarification periods.",,milestone/type = procurement
+draftFinalTender,Submission of draft final bid,"For competitive dialogue processes, the deadline for submission of draft final bids",,milestone/type = procurement
diff --git a/es/extensions/ppp/master/extension.json b/es/extensions/ppp/master/extension.json
new file mode 100644
index 000000000..f83a3fe7a
--- /dev/null
+++ b/es/extensions/ppp/master/extension.json
@@ -0,0 +1,34 @@
+{
+ "name": {
+ "en": "OCDS for PPPs Extension",
+ "es": "Extensi\u00f3n OCDS para APPs"
+ },
+ "description": {
+ "en": "Makes changes required by the OCDS for PPPs profile. Evaluation indicators, finance summary and project details may be moved into new extensions.",
+ "es": "Realiza los cambios requeridos por el perfil de OCDS para APPs. Los indicadores de evaluaci\u00f3n, resumen financiero y detalles del proyecto podr\u00edan ser movidos a otra extensi\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/ppp/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "+milestoneType.csv",
+ "+partyRole.csv",
+ "+documentType.csv",
+ "metricID.csv",
+ "milestoneCode.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_metrics_extension/1.1/extension.json",
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_location_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/ppp/master/index.html b/es/extensions/ppp/master/index.html
new file mode 100644
index 000000000..aa4c075cd
--- /dev/null
+++ b/es/extensions/ppp/master/index.html
@@ -0,0 +1,452 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Extensión OCDS para APPs +
+ ++ Realiza los cambios requeridos por el perfil de OCDS para APPs. Los indicadores de evaluación, resumen financiero y detalles del proyecto podrían ser movidos a otra extensión. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +documentType.csv +
+ +
+ You can download the +documentType.csv file in English.
+
+ The extension adds these codes to the documentType.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ valueForMoneyAnalysis
+
+ |
+ + Value for money analysis + | +
+ A summary of the value for money analysis carried out for the project, along with supporting figures, calculations and business case, based on projected or actual procurement outcomes. + +
|
+
+
+ serviceDescription
+
+ |
+ + Service descriptions + | +
+ A high-level description of the services + +
|
+
+
+ estimatedDemand
+
+ |
+ + Estimated demand + | +
+ A narrative describing the estimated demand to be served (annually) by the project. + +
|
+
+
+ projectAdditionality
+
+ |
+ + Project additionality + | +
+ A description of the additionality provided by the project + +
|
+
+
+ financeAdditionality
+
+ |
+ + Finance additionality + | +
+ A description of the additionality provided by the finance method + +
|
+
+
+ pppModeRationale
+
+ |
+ + Rationale for PPP modality + | +
+ A description of the reasons for choosing to conduct this project as a PPP + +
|
+
+
+ evaluationCommittee
+
+ |
+ + Evaluation committee details + | +
+ Information on the constitution of the evaluation committee + +
|
+
+
+ requestForQualification
+
+ |
+ + Request for qualification + | +
+ The set of documents issued by the procuring authority that constitute the basis of the qualification and potentially the pre-selection of candidates (the short list). Qualified (or short-listed candidates) will then be invited to submit a proposal (or to enter into a new phase prior to bid submission, such as a dialogue phase or interactive phase). + +
|
+
+
+ minutes
+
+ |
+ + Minutes + | +
+ Minutes of pre-bid meetings, or other relevant meetings. + +
|
+
+
+ negotiationParameters
+
+ |
+ + Negotiation parameters + | +
+ A description of the parameters for negotiation with the preferred proponent + +
|
+
+
+ riskComparison
+
+ |
+ + Risk comparison + | +
+ Risk comparison of other financing methods + +
|
+
+
+ discountRate
+
+ |
+ + Discount rate and risk premium + | +
+ An explanation of the discount rate, and any risk premium used, including information on project-specific circumstances that justify the risk premium rate used. + +
|
+
+
+ equityTransferCaps
+
+ |
+ + Equity transfer caps + | +
+ Details of any restrictions on the transfer of equity by shareholders or other relevant participants in the project. Certain contracts provide for caps on equity transfer in different stages of the contract, especially during the construction stage and for a few years thereafter. + +
|
+
+
+ financeArrangements
+
+ |
+ + Security and step in arrangements + | +
+ Details of any rights granted to a lender to access value in the event of default by a borrower and any rights granted to a party to "step in" to the shoes of another party, for example, a right granted to a lender or public authority to take over temporarily the operation of a project in case of failure to perform by a private party. + +
|
+
+
+ guaranteeReports
+
+ |
+ + Fiscal commitments and contingent liabilities disclosure reports + | +
+ Reports detailing the fiscal commitments of the public authority to the PPP, for example known payments that need to be made if the PPP proceeds or payment commitments whose occurrence, timing and magnitude depend on some uncertain future event, outside the control of the public authority. + +
|
+
+
+ grants
+
+ |
+ + Grants + | +
+ Information on grants given to support the project. Grant information ought to detail the total value of subsidy, and/or the value of subsidy as a proportion of the overall project value, as well as providing information on the nature of the grant. For capital subsidies paid during construction of a project, or operating subsidies paid during operation, details of periodicity of grant payments, and particular grant milestones, ought to be provided. + +
|
+
+
+ servicePayments
+
+ |
+ + Service payments + | +
+ Service payments are payments made by the public authority or purchaser to the private provider for infrastructure services (applicable in some types of Public Private Partnership projects). The documentation ought to cover the total number of payments and their periodicity, as well as the methodology used for calculating payments and the indexation used. + +
|
+
+
+ landTransfer
+
+ |
+ + Land transfer + | +
+ Details of land transferred on lease or other basis by government, including details of property numbers with the quantum of land transferred, zoning information and conditions of transfer. + +
|
+
+
+ assetTransfer
+
+ |
+ + Asset transfer + | +
+ Details of asset, human resource of personnel transfers, including documentation of the conditions of transfer. + +
|
+
+
+ revenueShare
+
+ |
+ + Revenue share + | +
+ Documentation of any revenue share arrangements, including revenue share on the base-case and upside for a public private partnership project. + +
|
+
+
+ otherGovernmentSupport
+
+ |
+ + Other government support + | +
+ Documentation of any other government support, including non-complete clauses or provision for revenue shortfall loans. + +
|
+
+
+ defaultEvents
+
+ |
+ + Defaults + | +
+ Information on events of default + +
|
+
+
+ termination
+
+ |
+ + Termination + | +
+ Information on contract termination + +
|
+
+
+ handover
+
+ |
+ + Handover + | +
+ Contractual provisions for, or reporting on, handover of assets back to the state, including details of condition of assets and any other conditions of handover. + +
|
+
+
+ financialStatement
+
+ |
+ + Financial statement + | +
+ Audited financial statements of the project company + +
|
+
+
+ performanceReport
+
+ |
+ + Performance report + | +
+ Performance assessment reports + +
|
+
+ +milestoneType.csv +
+ +
+ You can download the +milestoneType.csv file in English.
+
+ The extension adds these codes to the milestoneType.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ procurement
+
+ |
+ + Procurement + | +
+ Events taking place during the procurement which are not captured by fields in core OCDS, such as additional enquiry periods or draft bid submissions in a competitive dialogue process + + |
+
+
+ contractClose
+
+ |
+ + Contract close + | +
+ Events such as commercial and financial close + +
|
+
+ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ privateParty
+
+ |
+ + Private party + | +
+ The counter party of the procuring authority in the PPP contract. A private organization that has been granted the contract to construct and operate a government asset, and that is usually created under the form of a Special Purpose Vehicle (SPV). + +
|
+
+
+ leadBank
+
+ |
+ + Lead bank + | +
+ A lead bank is a bank that oversees the arrangement of a loan syndication + + |
+
+
+ lender
+
+ |
+ + Lender + | +
+ The APMG PPP Certification Program defines lenders as "Institutions that provide lending to the project: mainly banks and institutional investors through project bonds" + + |
+
+
+ equityInvestor
+
+ |
+ + Equity investor + | +
+ The APMG PPP Certification Program defines equity investors as "Investors who finance a portion of the project’s capital expenditures (Capex), typically as share capital or subordinated debt" + + |
+
+ metricID.csv +
+ +
+ You can download the metricID.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ demand
+
+ |
+ + Demand + | +
+ For reporting on forecast or actual demand + + |
+
+
+ revenue
+
+ |
+ + Revenue + | +
+ For reporting on forecast or actual revenues + + |
+
+
+ IRR
+
+ |
+ + Internal rate of return + | +
+ For reporting on forecast or actual project IRR + + |
+
+ milestoneCode.csv +
+ +
+ You can download the milestoneCode.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ projectApproval
+
+ |
+ + Project approval + | +
+ The dates of approvals from relevant authorities. + +
|
+
+
+ commercialClose
+
+ |
+ + Commercial close + | +
+ In a financing, the point at which the commercial documentation has been executed but before conditions precedent have been satisfied or waived; before financial close. + +
|
+
+
+ financialClose
+
+ |
+ + Financial close + | +
+ In a financing, the point at which the documentation has been executed and conditions precedent have been satisfied or waived. Drawdowns become permissible after this point. + +
|
+
+
+ commencement
+
+ |
+ + Commencement of construction or development + | +
+ The date of commencement of construction or development + +
|
+
+
+ completion
+
+ |
+ + Completion of construction of development + | +
+ The date of completion of construction or development + +
|
+
+
+ commissioning
+
+ |
+ + Commissioning + | +
+ The testing and inspection of the completed works to verify that the works are ready for commercial operation. + +
|
+
+
+ enquiryPeriodStart
+
+ |
+ + Enquiry period start + | +
+ For processes with multiple enquiry periods, the start date of a period during which enquiries can be made and responded to which is not provided in the tender/enquiryPeriod block. Sometimes known as clarification periods. + +
|
+
+
+ enquiryPeriodEnd
+
+ |
+ + Enquiry period end + | +
+ For processes with multiple enquiry periods, the end date of a period during which enquiries can be made and responded to which is not provided in the tender/enquiryPeriod block. Sometimes known as clarification periods. + +
|
+
+
+ draftFinalTender
+
+ |
+ + Submission of draft final bid + | +
+ For competitive dialogue processes, the deadline for submission of draft final bids + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/ppp/master/release-schema.json b/es/extensions/ppp/master/release-schema.json
new file mode 100644
index 000000000..c9af6c0ee
--- /dev/null
+++ b/es/extensions/ppp/master/release-schema.json
@@ -0,0 +1,167 @@
+{
+ "definitions": {
+ "Award": {
+ "properties": {
+ "evaluationIndicators": {
+ "title": "Evaluaci\u00f3n de la opci\u00f3n APP",
+ "description": "Indicadores clave que describen c\u00f3mo la opci\u00f3n de APP ha sido evaluada por el gobierno.",
+ "$ref": "#/definitions/EvaluationIndicators"
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "financeSummary": {
+ "title": "Resumen financiero",
+ "description": "Indicadores clave que describen el modelo financiero de la APP.",
+ "$ref": "#/definitions/FinanceSummary"
+ }
+ }
+ },
+ "EvaluationIndicators": {
+ "title": "Indicadores de evaluaci\u00f3n",
+ "description": "Indicadores clave que describen c\u00f3mo la opci\u00f3n de APP ha sido evaluada por el gobierno.",
+ "type": "object",
+ "properties": {
+ "riskPremium": {
+ "title": "Prima de riesgo",
+ "description": "La prima de riesgo utilizada por el gobierno al evaluar la opci\u00f3n APP expresada como una fracci\u00f3n decimal (por ejemplo, 3,2% = 0,032). Se debe proporcionar una explicaci\u00f3n de la prima de riesgo utilizada en el campo riskPremiumDetails.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "riskPremiumDetails": {
+ "title": "Detalles de la prima de riesgo",
+ "description": "M\u00e1s detalles sobre la prima de riesgo utilizada, incluyendo una explicaci\u00f3n de por qu\u00e9 se utiliz\u00f3.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "discountRate": {
+ "title": "Tasa de descuento",
+ "description": "La tasa de descuento utilizada por el gobierno al evaluar la opci\u00f3n APP expresada como una fracci\u00f3n decimal (por ejemplo, 3,2% = 0,032). Se pueden proporcionar m\u00e1s detalles en el campo discountRateDetails.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "discountRateDetails": {
+ "title": "Detalles de la tasa de descuento",
+ "description": "M\u00e1s detalles sobre la tasa de descuento utilizada.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "netPresentValue": {
+ "title": "Valor presente neto",
+ "description": "El valor descontado de las entradas de efectivo de una inversi\u00f3n menos el valor descontado de sus salidas de efectivo. Se pueden proporcionar m\u00e1s detalles en el campo netPresentValueRateDetails.",
+ "$ref": "#/definitions/Value"
+ },
+ "netPresentValueDetails": {
+ "title": "Detalles del valor actual neto",
+ "description": "M\u00e1s detalles sobre el c\u00e1lculo del valor actual neto.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "FinanceSummary": {
+ "title": "Resumen financiero",
+ "description": "Indicadores clave que describen el modelo financiero de la APP.",
+ "type": "object",
+ "properties": {
+ "debtEquityRatio": {
+ "title": "Proporci\u00f3n de capital de la deuda",
+ "description": "La proporci\u00f3n deuda-capital del proyecto, expresada como un valor decimal. El PPPIRC del Banco Mundial define la proporci\u00f3n de endeudamiento como \"deuda a largo plazo (dividida por) el capital accionario de la empresa del proyecto\". Tambi\u00e9n conocido como \"apalancamiento\" o \"gearing\". Pueden proporcionarse m\u00e1s detalles sobre la proporci\u00f3n de capital de deuda en el campo debtEquityRatioDetails.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "debtEquityRatioDetails": {
+ "title": "Detalles de la relaci\u00f3n de capital de la deuda",
+ "description": "M\u00e1s detalles sobre el c\u00e1lculo de la proporci\u00f3n del capital de la deuda.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "shareCapital": {
+ "title": "Capital accionario",
+ "description": "El valor del capital en el proyecto que proviene de la emisi\u00f3n de acciones. Pueden proporcionarse m\u00e1s detalles sobre el capital accionario en el campo shareCapitalDetails.",
+ "$ref": "#/definitions/Value"
+ },
+ "shareCapitalDetails": {
+ "title": "Detalles del capital social",
+ "description": "M\u00e1s detalles sobre el c\u00e1lculo del capital social.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "subsidyRatio": {
+ "title": "Relaci\u00f3n de subsidio",
+ "description": "Subvenci\u00f3n como proporci\u00f3n del valor del proyecto, expresada como una fracci\u00f3n decimal (por ejemplo, 3,2% = 0,032). Se pueden proporcionar m\u00e1s detalles sobre el coeficiente de subvenci\u00f3n en el campo subsidyRatioDetails.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "subsidyRatioDetails": {
+ "title": "Detalles de la relaci\u00f3n de subvenci\u00f3n",
+ "description": "M\u00e1s detalles sobre el c\u00e1lculo del coeficiente de subvenci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "projectIRR": {
+ "title": "Tasa Interna de Retorno del Proyecto",
+ "description": "La tasa interna de rendimiento del proyecto, expresada como una fracci\u00f3n decimal (por ejemplo, 3,2% = 0,032). El Programa de Certificaci\u00f3n PPM de APMG define la TIR como \"La tasa de rendimiento de una inversi\u00f3n calculada a partir de sus flujos de efectivo proyectados. La tasa interna de rentabilidad (TIR) \u200b\u200bes tambi\u00e9n la tasa de descuento que equipara el valor presente de una corriente futura de flujos de efectivo a la inversi\u00f3n inicial\" Pueden proporcionarse m\u00e1s detalles sobre la TIR del proyecto en el campo projectIRRdetails.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "projectIRRDetails": {
+ "title": "Detalles de la tasa interna de retorno de la inversi\u00f3n del proyecto",
+ "description": "M\u00e1s detalles sobre el c\u00e1lculo de la TIR del proyecto.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Metric": {
+ "properties": {
+ "id": {
+ "codelist": "metricID.csv",
+ "openCodelist": true
+ }
+ }
+ },
+ "Milestone": {
+ "properties": {
+ "code": {
+ "codelist": "milestoneCode.csv",
+ "openCodelist": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/ppp/master/schema/index.html b/es/extensions/ppp/master/schema/index.html
new file mode 100644
index 000000000..089e1ba50
--- /dev/null
+++ b/es/extensions/ppp/master/schema/index.html
@@ -0,0 +1,699 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Extensión OCDS para APPs +
+ ++ Realiza los cambios requeridos por el perfil de OCDS para APPs. Los indicadores de evaluación, resumen financiero y detalles del proyecto podrían ser movidos a otra extensión. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+El Estándar de Datos de Contrataciones Abiertas para el perfil de Asociaciones Público Privadas provee un esquema extendido del esquema de Datos de Contrataciones Abiertas, ofreciendo un modelo de datos estructurados para presentar información en proyectos de Asociaciones Público Privadas.
+Esta basado en el Marco del Banco Mundial para la Divulgación de Proyectos de Asociación Público Privada y fue desarrollado entre Mayo 2016 y Mayo 2017 a través de una asociación entre el equipo del Banco Mundial Open Contracting, PPP team, Open Contracting Partnership, y Open Data Services Co-operative.
+La documentación completa del perfil esta disponible en: http://standard.open-contracting.org/profiles/ppp/
+La consolidación de la extensión OCDS para APPs puede ser declarada en OCDS package metadata](http://standard.open-contracting.org/latest/es/schema/release_package/) usando:
+{
+ "extensions": [
+ "http://standard.open-contracting.org/profiles/ppp/extension/1__0__0__beta/extension.json"
+ ],
+ "releases": []
+}
+Sobre extensiones APP
+OCDS para APPS esta construida a partir de un numero de diferentes extensiones modulares de OCDS,, de los cuales la mayoría puede ser usadas independientemente del perfil.
+Este repositorio contiene una extensión adicional que forma parte del perfil de OCDS para APPs. Esta extensión presenta una serie de campos y bloques de construcción que son específicos de la divulgación de APP según el Marco del Banco Mundial.
+Extensiones específicas de APP
+Indicadores de Evaluación
+El marco de divulgación de APP requiere que se divulguen varios indicadores diferentes relacionados con la evaluación de los gobiernos de un proyecto de APP.
+La sección awards.evaluationIndicators incluye campos para expresar el valor y los detalles de texto libre de apoyo para cada indicador:
-
+
- discountRate +
- riskPremium +
- netPresentValue +
Ejemplo
+"evaluationIndicators": {
+ "riskPremium": 0.0092,
+ "riskPremiumDetails": "Based on a market risk premium of 6.0% (per government guidelines) and an asset beta of 0.45 (per a sample of listed telecommunication network providers) the project risk allocation gives rise to a risk premium of 0.92%",
+ "discountRate": 0.03,
+ "discountRateDetails": "Based on the current long term public sector bond rate",
+ "netPresentValue": {
+ "amount": 118044591901.35034,
+ "currency": "USD"
+ }
+Resumen Financiero
+El marco de divulgación de APP requiere una serie de indicadores diferentes relacionados con el modelo financiero de un proyecto APP. Mientras que algunos de estos pueden ser reportados como métricas en forma continua, algunos son simples valores individuales.
+La sección contracts.financeSummary incluye campos para expresar el valor y los detalles de texto libre de apoyo para cada indicador:
-
+
- debtEquityRatio +
- shareCapital +
- subsidyRatio +
- projectIRR +
Ejemplo
+"financeSummary": {
+ "debtEquityRatio": 2.05,
+ "debtEquityRatioDetails": "Until the target population coverage is reached mega Consortium must comply with a contribution of capital of at least 30% of the total value of the company",
+ "shareCapital": {
+ "amount": 20000000,
+ "currency": "USD"
+ }
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-06-07
+-
+
- Remove unused
+partyRole.csvcodes: +-
+
- consortiaMember +
- grantor +
- notary +
- otherWitness +
- socialWitness +
+
2021-04-19
+-
+
- Reemplazar
documentType.csvcon+documentType.csv, que agrega nuevos códigos en lugar de sustituir la lista de códigos.
+
2021-02-15
+-
+
- Restaura los reoles 'procuringEntity', 'tenderer' y 'funder'. Elimina el rol 'bidder'. +
2021-01-14
+-
+
- Elimina la lista de códigos
+releaseTag.csv.
+
2021-01-11
+-
+
- Elimina la lista de códigos
initiationType.csv.
+ - Restaura los campos
buyeryawards.suppliers.
+
2020-11-16
+-
+
- Restaura campos deprecados. +
- Restaura los campos
Budget.projectyBudget.projectID.
+
2020-06-04
+-
+
- Revisar de las palabras normativas y no normativas. +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-05-01
+-
+
- Remove 'qualifiedBidder' and 'disqualifiedBidder' codes from
+partyRole.csv(moved to qualification extension).
+
2019-03-20
+-
+
- Establece
"uniqueItems": trueen campos matriz.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/procedure/index.html b/es/extensions/procedure/index.html
new file mode 100644
index 000000000..370fab376
--- /dev/null
+++ b/es/extensions/procedure/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Extensión OCDS para APPs +
+ ++ Realiza los cambios requeridos por el perfil de OCDS para APPs. Los indicadores de evaluación, resumen financiero y detalles del proyecto podrían ser movidos a otra extensión. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ evaluationIndicators
+
+ |
+ + Evaluación de la opción APP + | +
+ Indicadores clave que describen cómo la opción de APP ha sido evaluada por el gobierno. + + |
+ + EvaluationIndicators object + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ financeSummary
+
+ |
+ + Resumen financiero + | +
+ Indicadores clave que describen el modelo financiero de la APP. + + |
+ + FinanceSummary object + | +
+ EvaluationIndicators +
+ +
+ The extension defines a new EvaluationIndicators object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ riskPremium
+
+ |
+ + Prima de riesgo + | +
+ La prima de riesgo utilizada por el gobierno al evaluar la opción APP expresada como una fracción decimal (por ejemplo, 3,2% = 0,032). Se debe proporcionar una explicación de la prima de riesgo utilizada en el campo riskPremiumDetails. + + |
+ + number + | +
+
+ riskPremiumDetails
+
+ |
+ + Detalles de la prima de riesgo + | +
+ Más detalles sobre la prima de riesgo utilizada, incluyendo una explicación de por qué se utilizó. + + |
+ + string + | +
+
+ discountRate
+
+ |
+ + Tasa de descuento + | +
+ La tasa de descuento utilizada por el gobierno al evaluar la opción APP expresada como una fracción decimal (por ejemplo, 3,2% = 0,032). Se pueden proporcionar más detalles en el campo discountRateDetails. + + |
+ + number + | +
+
+ discountRateDetails
+
+ |
+ + Detalles de la tasa de descuento + | +
+ Más detalles sobre la tasa de descuento utilizada. + + |
+ + string + | +
+
+ netPresentValue
+
+ |
+ + Valor presente neto + | +
+ El valor descontado de las entradas de efectivo de una inversión menos el valor descontado de sus salidas de efectivo. Se pueden proporcionar más detalles en el campo netPresentValueRateDetails. + + |
+ + Value object + | +
+
+ netPresentValueDetails
+
+ |
+ + Detalles del valor actual neto + | +
+ Más detalles sobre el cálculo del valor actual neto. + + |
+ + string + | +
+ FinanceSummary +
+ +
+ The extension defines a new FinanceSummary object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ debtEquityRatio
+
+ |
+ + Proporción de capital de la deuda + | +
+ La proporción deuda-capital del proyecto, expresada como un valor decimal. El PPPIRC del Banco Mundial define la proporción de endeudamiento como "deuda a largo plazo (dividida por) el capital accionario de la empresa del proyecto". También conocido como "apalancamiento" o "gearing". Pueden proporcionarse más detalles sobre la proporción de capital de deuda en el campo debtEquityRatioDetails. + + |
+ + number + | +
+
+ debtEquityRatioDetails
+
+ |
+ + Detalles de la relación de capital de la deuda + | +
+ Más detalles sobre el cálculo de la proporción del capital de la deuda. + + |
+ + string + | +
+
+ shareCapital
+
+ |
+ + Capital accionario + | +
+ El valor del capital en el proyecto que proviene de la emisión de acciones. Pueden proporcionarse más detalles sobre el capital accionario en el campo shareCapitalDetails. + + |
+ + Value object + | +
+
+ shareCapitalDetails
+
+ |
+ + Detalles del capital social + | +
+ Más detalles sobre el cálculo del capital social. + + |
+ + string + | +
+
+ subsidyRatio
+
+ |
+ + Relación de subsidio + | +
+ Subvención como proporción del valor del proyecto, expresada como una fracción decimal (por ejemplo, 3,2% = 0,032). Se pueden proporcionar más detalles sobre el coeficiente de subvención en el campo subsidyRatioDetails. + + |
+ + number + | +
+
+ subsidyRatioDetails
+
+ |
+ + Detalles de la relación de subvención + | +
+ Más detalles sobre el cálculo del coeficiente de subvención. + + |
+ + string + | +
+
+ projectIRR
+
+ |
+ + Tasa Interna de Retorno del Proyecto + | +
+ La tasa interna de rendimiento del proyecto, expresada como una fracción decimal (por ejemplo, 3,2% = 0,032). El Programa de Certificación PPM de APMG define la TIR como "La tasa de rendimiento de una inversión calculada a partir de sus flujos de efectivo proyectados. La tasa interna de rentabilidad (TIR) es también la tasa de descuento que equipara el valor presente de una corriente futura de flujos de efectivo a la inversión inicial" Pueden proporcionarse más detalles sobre la TIR del proyecto en el campo projectIRRdetails. + + |
+ + number + | +
+
+ projectIRRDetails
+
+ |
+ + Detalles de la tasa interna de retorno de la inversión del proyecto + | +
+ Más detalles sobre el cálculo de la TIR del proyecto. + + |
+ + string + | +
+ Metric +
+ +
+ The extension defines these fields in the Metric object from the Métrica extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+ Milestone +
+ +
+ The extension defines these fields in the Milestone object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ code
+
+ |
+ + + | +
+ + This field is modified from its original version. + + + |
+ + + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/procedure/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/procedure/master/release-schema.json b/es/extensions/procedure/master/release-schema.json
new file mode 100644
index 000000000..0aac81882
--- /dev/null
+++ b/es/extensions/procedure/master/release-schema.json
@@ -0,0 +1,47 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "procedure": {
+ "title": "Procedimiento",
+ "description": "Informaci\u00f3n sobre el procedimiento de contrataci\u00f3n.",
+ "$ref": "#/definitions/Procedure"
+ }
+ }
+ },
+ "Procedure": {
+ "title": "Procedimiento",
+ "description": "Informaci\u00f3n sobre el procedimiento de contrataci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "isAccelerated": {
+ "title": "Procedimiento acelerado utilizado",
+ "description": "Si el l\u00edmite de tiempo para la recepci\u00f3n de ofertas o solicitudes de participaci\u00f3n puede reducirse debido a un estado de urgencia.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "acceleratedRationale": {
+ "title": "Justificaci\u00f3n del procedimiento acelerado",
+ "description": "La justificaci\u00f3n para utilizar un procedimiento acelerado.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "features": {
+ "title": "Caracter\u00edsticas",
+ "description": "Las principales caracter\u00edsticas del procedimiento (por ejemplo, descripci\u00f3n de las etapas individuales) e informaci\u00f3n sobre d\u00f3nde se pueden encontrar las reglas completas del procedimiento.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/procedure/master/schema/index.html b/es/extensions/procedure/master/schema/index.html
new file mode 100644
index 000000000..2351b0b79
--- /dev/null
+++ b/es/extensions/procedure/master/schema/index.html
@@ -0,0 +1,316 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Procedimiento +
+ ++ Esta extensión agrega un bloque para describir el procedimiento de contratación. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Esta extensión agrega un bloque para describir el procedimiento de contratación.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BT-88, BT-106, BT-1351 and Article 93 and 45(3) of Directive 2014/25/EU. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+{
+ "tender": {
+ "procedure": {
+ "isAccelerated": true,
+ "acceleratedRationale": "The medicinal product is of major public health interest particularly from the point of view of therapeutic innovation.",
+ "features": "http://www.legislation.gov.uk/uksi/2015/102/pdfs/uksi_20150102_en.pdf"
+ }
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), en pull requests y en https://github.com/open-contracting/standard/issues/695.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/process_title/index.html b/es/extensions/process_title/index.html
new file mode 100644
index 000000000..f68835f70
--- /dev/null
+++ b/es/extensions/process_title/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Procedimiento +
+ ++ Esta extensión agrega un bloque para describir el procedimiento de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ procedure
+
+ |
+ + Procedimiento + | +
+ Información sobre el procedimiento de contratación. + + |
+ + Procedure object + | +
+ Procedure +
+ +
+ The extension defines a new Procedure object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ isAccelerated
+
+ |
+ + Procedimiento acelerado utilizado + | +
+ Si el límite de tiempo para la recepción de ofertas o solicitudes de participación puede reducirse debido a un estado de urgencia. + + |
+ + boolean + | +
+
+ acceleratedRationale
+
+ |
+ + Justificación del procedimiento acelerado + | +
+ La justificación para utilizar un procedimiento acelerado. + + |
+ + string + | +
+
+ features
+
+ |
+ + Características + | +
+ Las principales características del procedimiento (por ejemplo, descripción de las etapas individuales) e información sobre dónde se pueden encontrar las reglas completas del procedimiento. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/process_title/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/process_title/master/release-schema.json b/es/extensions/process_title/master/release-schema.json
new file mode 100644
index 000000000..111e36e16
--- /dev/null
+++ b/es/extensions/process_title/master/release-schema.json
@@ -0,0 +1,20 @@
+{
+ "properties": {
+ "title": {
+ "title": "T\u00edtulo",
+ "description": "Un t\u00edtulo general para este proceso de contrataci\u00f3n o entrega.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una descripci\u00f3n general de este proceso de contrataci\u00f3n o entrega. Este no reemplaza a una descripci\u00f3n detallada de los objetos del proceso de contrataci\u00f3n en las secciones de planeaci\u00f3n, licitaci\u00f3n, adjudicaci\u00f3n o contrato.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+}
diff --git a/es/extensions/process_title/master/schema/index.html b/es/extensions/process_title/master/schema/index.html
new file mode 100644
index 000000000..c4cf6ba59
--- /dev/null
+++ b/es/extensions/process_title/master/schema/index.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Título y descripción del nivel del proceso +
+ ++ Para proporcionar títulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contratación como un todo. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En algunos casos, es importante proporcionar un título y una descripción generales para un proceso de contratación, distintos de los campos individuales de título y descripción contenidos en los bloques tender, awards y contracts.
La extensión añade campos title y description al esquema de release.
A menudo se utilizarán para proporcionar un resumen legible de la información que se proporciona en otra parte del documento OCDS como datos estructurados.
+Los publicadores que utilicen estos campos deben ser conscientes de que no todas las aplicaciones mostrarán su contenido y, por lo tanto, la información clave para comprender la naturaleza del proceso de contratación generalmente también se debe proporcionar utilizando los campos centrales del OCDS.
+Ejemplo
+{
+ "title": "Next-Generation Telecommunications PPP",
+ "description": "The Next-Generation Telecommunications PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators. The project will increase the telecommunication services coverage, promote competitive prices and enhance the quality of services according to international standards."
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.5
+-
+
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- Añadir el ejemplo al readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/process_title/v1.1.3/README.md b/es/extensions/process_title/v1.1.3/README.md
new file mode 100644
index 000000000..c6bdd43f6
--- /dev/null
+++ b/es/extensions/process_title/v1.1.3/README.md
@@ -0,0 +1,20 @@
+# Título y descripción del proceso
+
+En algunos casos, es importante proporcionar un título y una descripción generales para un proceso de contratación, distintos de los campos individuales de título y descripción contenidos en los bloques `tender`, ` award` y `contract`.
+
+Esta extensión proporciona los campos `release.title` y `release.description`.
+
+A menudo se utilizarán para proporcionar un resumen legible de la información que se proporciona en otra parte del documento OCDS como datos estructurados.
+
+Los publicadores que utilicen estos campos deben ser conscientes de que no todas las aplicaciones mostrarán su contenido y, por lo tanto, la información clave para comprender la naturaleza del proceso de contratación generalmente **también** se debe proporcionar utilizando los campos centrales del OCDS.
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.3
+
+- Usa la licencia Apache 2.0
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/process_title/v1.1.3/extension.json b/es/extensions/process_title/v1.1.3/extension.json
new file mode 100644
index 000000000..294f96c48
--- /dev/null
+++ b/es/extensions/process_title/v1.1.3/extension.json
@@ -0,0 +1,16 @@
+{
+ "name": {
+ "en": "Process level title and description",
+ "es": "T\u00edtulo y descripci\u00f3n del nivel del proceso"
+ },
+ "description": {
+ "en": "For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole.",
+ "es": "Para proporcionar t\u00edtulos y descripciones del proceso en general, a menudo para dar un resumen de texto libre del proceso de contrataci\u00f3n como un todo."
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting/ocds_process_title_extension"
+ }
+}
diff --git a/es/extensions/process_title/v1.1.3/index.html b/es/extensions/process_title/v1.1.3/index.html
new file mode 100644
index 000000000..32a2e66f8
--- /dev/null
+++ b/es/extensions/process_title/v1.1.3/index.html
@@ -0,0 +1,292 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Título y descripción del nivel del proceso +
+ ++ Para proporcionar títulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contratación como un todo. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Título + | +
+ Un título general para este proceso de contratación o entrega. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Una descripción general de este proceso de contratación o entrega. Este no reemplaza a una descripción detallada de los objetos del proceso de contratación en las secciones de planeación, licitación, adjudicación o contrato. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/process_title/v1.1.3/release-schema.json b/es/extensions/process_title/v1.1.3/release-schema.json
new file mode 100644
index 000000000..b14717137
--- /dev/null
+++ b/es/extensions/process_title/v1.1.3/release-schema.json
@@ -0,0 +1,20 @@
+{
+ "properties": {
+ "title": {
+ "title": "T\u00edtulo",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "Un t\u00edtulo general para este proceso de contrataci\u00f3n o entrega."
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "Descripci\u00f3n general de este proceso de contrataci\u00f3n o entrega. Esto no debe reemplazar la provisi\u00f3n de un desglose detallado de los objetos del proceso de contrataci\u00f3n en la secci\u00f3n de planificaci\u00f3n, licitaci\u00f3n, adjudicaci\u00f3n o contratos."
+ }
+ }
+}
diff --git a/es/extensions/process_title/v1.1.3/schema/index.html b/es/extensions/process_title/v1.1.3/schema/index.html
new file mode 100644
index 000000000..ef5e2f3f5
--- /dev/null
+++ b/es/extensions/process_title/v1.1.3/schema/index.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Título y descripción del nivel del proceso +
+ ++ Para proporcionar títulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contratación como un todo. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En algunos casos, es importante proporcionar un título y una descripción generales para un proceso de contratación, distintos de los campos individuales de título y descripción contenidos en los bloques tender, award y contract.
Esta extensión proporciona los campos release.title y release.description.
A menudo se utilizarán para proporcionar un resumen legible de la información que se proporciona en otra parte del documento OCDS como datos estructurados.
+Los publicadores que utilicen estos campos deben ser conscientes de que no todas las aplicaciones mostrarán su contenido y, por lo tanto, la información clave para comprender la naturaleza del proceso de contratación generalmente también se debe proporcionar utilizando los campos centrales del OCDS.
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.3
+-
+
- Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/process_title/v1.1.4/README.md b/es/extensions/process_title/v1.1.4/README.md
new file mode 100644
index 000000000..4ce95b29b
--- /dev/null
+++ b/es/extensions/process_title/v1.1.4/README.md
@@ -0,0 +1,34 @@
+# Título y descripción del proceso
+
+En algunos casos, es importante proporcionar un título y una descripción generales para un proceso de contratación, distintos de los campos individuales de título y descripción contenidos en los bloques `tender`, ` award` y `contract`.
+
+La extensión añade campos `title` y `description` al esquema de release.
+
+A menudo se utilizarán para proporcionar un resumen legible de la información que se proporciona en otra parte del documento OCDS como datos estructurados.
+
+Los publicadores que utilicen estos campos deben ser conscientes de que no todas las aplicaciones mostrarán su contenido y, por lo tanto, la información clave para comprender la naturaleza del proceso de contratación generalmente **también** se debe proporcionar utilizando los campos centrales del OCDS.
+
+## Ejemplo
+
+```json
+{
+ "title": "Next-Generation Telecommunications PPP",
+ "description": "The Next-Generation Telecommunications PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators. The project will increase the telecommunication services coverage, promote competitive prices and enhance the quality of services according to international standards."
+}
+```
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.4
+
+- Añadir el ejemplo al readme
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- Usa la licencia Apache 2.0
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/process_title/v1.1.4/extension.json b/es/extensions/process_title/v1.1.4/extension.json
new file mode 100644
index 000000000..0a06b344a
--- /dev/null
+++ b/es/extensions/process_title/v1.1.4/extension.json
@@ -0,0 +1,19 @@
+{
+ "name": {
+ "en": "Process level title and description",
+ "es": "T\u00edtulo y descripci\u00f3n del nivel del proceso"
+ },
+ "description": {
+ "en": "For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole.",
+ "es": "Para proporcionar t\u00edtulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contrataci\u00f3n como un todo."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/process_title/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ]
+}
diff --git a/es/extensions/process_title/v1.1.4/index.html b/es/extensions/process_title/v1.1.4/index.html
new file mode 100644
index 000000000..6ba6c9cb7
--- /dev/null
+++ b/es/extensions/process_title/v1.1.4/index.html
@@ -0,0 +1,313 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Título y descripción del nivel del proceso +
+ ++ Para proporcionar títulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contratación como un todo. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Título + | +
+ Un título general para este proceso de contratación o entrega. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Descripción general de este proceso de contratación o entrega. Esto no debe reemplazar la provisión de un desglose detallado de los objetos del proceso de contratación en la sección de planificación, licitación, adjudicación o contratos. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/process_title/v1.1.4/release-schema.json b/es/extensions/process_title/v1.1.4/release-schema.json
new file mode 100644
index 000000000..b14717137
--- /dev/null
+++ b/es/extensions/process_title/v1.1.4/release-schema.json
@@ -0,0 +1,20 @@
+{
+ "properties": {
+ "title": {
+ "title": "T\u00edtulo",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "Un t\u00edtulo general para este proceso de contrataci\u00f3n o entrega."
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "Descripci\u00f3n general de este proceso de contrataci\u00f3n o entrega. Esto no debe reemplazar la provisi\u00f3n de un desglose detallado de los objetos del proceso de contrataci\u00f3n en la secci\u00f3n de planificaci\u00f3n, licitaci\u00f3n, adjudicaci\u00f3n o contratos."
+ }
+ }
+}
diff --git a/es/extensions/process_title/v1.1.4/schema/index.html b/es/extensions/process_title/v1.1.4/schema/index.html
new file mode 100644
index 000000000..bb27b79dc
--- /dev/null
+++ b/es/extensions/process_title/v1.1.4/schema/index.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Título y descripción del nivel del proceso +
+ ++ Para proporcionar títulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contratación como un todo. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En algunos casos, es importante proporcionar un título y una descripción generales para un proceso de contratación, distintos de los campos individuales de título y descripción contenidos en los bloques tender, award y contract.
La extensión añade campos title y description al esquema de release.
A menudo se utilizarán para proporcionar un resumen legible de la información que se proporciona en otra parte del documento OCDS como datos estructurados.
+Los publicadores que utilicen estos campos deben ser conscientes de que no todas las aplicaciones mostrarán su contenido y, por lo tanto, la información clave para comprender la naturaleza del proceso de contratación generalmente también se debe proporcionar utilizando los campos centrales del OCDS.
+Ejemplo
+{
+ "title": "Next-Generation Telecommunications PPP",
+ "description": "The Next-Generation Telecommunications PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators. The project will increase the telecommunication services coverage, promote competitive prices and enhance the quality of services according to international standards."
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.4
+-
+
- Añadir el ejemplo al readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/process_title/v1.1.5/README.md b/es/extensions/process_title/v1.1.5/README.md
new file mode 100644
index 000000000..5306abd89
--- /dev/null
+++ b/es/extensions/process_title/v1.1.5/README.md
@@ -0,0 +1,38 @@
+# Título y descripción del proceso
+
+En algunos casos, es importante proporcionar un título y una descripción generales para un proceso de contratación, distintos de los campos individuales de título y descripción contenidos en los bloques `tender`, ` awards` y `contracts`.
+
+La extensión añade campos `title` y `description` al esquema de release.
+
+A menudo se utilizarán para proporcionar un resumen legible de la información que se proporciona en otra parte del documento OCDS como datos estructurados.
+
+Los publicadores que utilicen estos campos deben ser conscientes de que no todas las aplicaciones mostrarán su contenido y, por lo tanto, la información clave para comprender la naturaleza del proceso de contratación generalmente también se debe proporcionar utilizando los campos centrales del OCDS.
+
+## Ejemplo
+
+```json
+{
+ "title": "Next-Generation Telecommunications PPP",
+ "description": "The Next-Generation Telecommunications PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators. The project will increase the telecommunication services coverage, promote competitive prices and enhance the quality of services according to international standards."
+}
+```
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### v1.1.5
+
+- Revisar las palabras normativas y no-normativas
+
+### v1.1.4
+
+- Añadir el ejemplo al readme
+- Añadir extension.json para el Extension Explorer
+
+### v1.1.3
+
+- Usa la licencia Apache 2.0
+- Agregar pruebas y ordenar el código
diff --git a/es/extensions/process_title/v1.1.5/extension.json b/es/extensions/process_title/v1.1.5/extension.json
new file mode 100644
index 000000000..07e317e58
--- /dev/null
+++ b/es/extensions/process_title/v1.1.5/extension.json
@@ -0,0 +1,23 @@
+{
+ "name": {
+ "en": "Process level title and description",
+ "es": "T\u00edtulo y descripci\u00f3n del nivel del proceso"
+ },
+ "description": {
+ "en": "For providing overall process titles and descriptions, often to give a free-text summary of the contracting process as a whole.",
+ "es": "Para proporcionar t\u00edtulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contrataci\u00f3n como un todo."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/process_title/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/process_title/v1.1.5/index.html b/es/extensions/process_title/v1.1.5/index.html
new file mode 100644
index 000000000..a02aed842
--- /dev/null
+++ b/es/extensions/process_title/v1.1.5/index.html
@@ -0,0 +1,322 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Título y descripción del nivel del proceso +
+ ++ Para proporcionar títulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contratación como un todo. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Título + | +
+ Un título general para este proceso de contratación o entrega. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Descripción general de este proceso de contratación o entrega. Esto no debe reemplazar la provisión de un desglose detallado de los objetos del proceso de contratación en la sección de planificación, licitación, adjudicación o contratos. + + |
+ + string + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/process_title/v1.1.5/release-schema.json b/es/extensions/process_title/v1.1.5/release-schema.json
new file mode 100644
index 000000000..8f9795aba
--- /dev/null
+++ b/es/extensions/process_title/v1.1.5/release-schema.json
@@ -0,0 +1,20 @@
+{
+ "properties": {
+ "title": {
+ "title": "T\u00edtulo",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "Un t\u00edtulo general para este proceso de contrataci\u00f3n o entrega."
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "type": [
+ "string",
+ "null"
+ ],
+ "description": "Una descripci\u00f3n general de este proceso de contrataci\u00f3n o entrega. Este no reemplaza a una descripci\u00f3n detallada de los objetos del proceso de contrataci\u00f3n en las secciones de planeaci\u00f3n, licitaci\u00f3n, adjudicaci\u00f3n o contrato."
+ }
+ }
+}
diff --git a/es/extensions/process_title/v1.1.5/schema/index.html b/es/extensions/process_title/v1.1.5/schema/index.html
new file mode 100644
index 000000000..0f2842e14
--- /dev/null
+++ b/es/extensions/process_title/v1.1.5/schema/index.html
@@ -0,0 +1,261 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Título y descripción del nivel del proceso +
+ ++ Para proporcionar títulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contratación como un todo. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En algunos casos, es importante proporcionar un título y una descripción generales para un proceso de contratación, distintos de los campos individuales de título y descripción contenidos en los bloques tender, awards y contracts.
La extensión añade campos title y description al esquema de release.
A menudo se utilizarán para proporcionar un resumen legible de la información que se proporciona en otra parte del documento OCDS como datos estructurados.
+Los publicadores que utilicen estos campos deben ser conscientes de que no todas las aplicaciones mostrarán su contenido y, por lo tanto, la información clave para comprender la naturaleza del proceso de contratación generalmente también se debe proporcionar utilizando los campos centrales del OCDS.
+Ejemplo
+{
+ "title": "Next-Generation Telecommunications PPP",
+ "description": "The Next-Generation Telecommunications PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators. The project will increase the telecommunication services coverage, promote competitive prices and enhance the quality of services according to international standards."
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+v1.1.5
+-
+
- Revisar las palabras normativas y no-normativas +
v1.1.4
+-
+
- Añadir el ejemplo al readme +
- Añadir extension.json para el Extension Explorer +
v1.1.3
+-
+
- Usa la licencia Apache 2.0 +
- Agregar pruebas y ordenar el código +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/procurementMethodRationaleClassifications/index.html b/es/extensions/procurementMethodRationaleClassifications/index.html
new file mode 100644
index 000000000..afd52165f
--- /dev/null
+++ b/es/extensions/procurementMethodRationaleClassifications/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Título y descripción del nivel del proceso +
+ ++ Para proporcionar títulos y descripciones del proceso en general , a menudo para dar un resumen de texto libre del proceso de contratación como un todo. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ title
+
+ |
+ + Título + | +
+ Un título general para este proceso de contratación o entrega. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Una descripción general de este proceso de contratación o entrega. Este no reemplaza a una descripción detallada de los objetos del proceso de contratación en las secciones de planeación, licitación, adjudicación o contrato. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/procurementMethodRationaleClassifications/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/procurementMethodRationaleClassifications/master/extension.json b/es/extensions/procurementMethodRationaleClassifications/master/extension.json
new file mode 100644
index 000000000..9475271cc
--- /dev/null
+++ b/es/extensions/procurementMethodRationaleClassifications/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Procurement method rationale classifications",
+ "es": "Clasificaciones de los fundamentos de m\u00e9todos de contrataci\u00f3n"
+ },
+ "description": {
+ "en": "Adds an array to the tender object to classify the procurement method rationale.",
+ "es": "Agregar una lista al objeto de licitaci\u00f3n para clasificar la justificaci\u00f3n del m\u00e9todo de contrataci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/procurementMethodRationaleClassifications/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+itemClassificationScheme.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/procurementMethodRationaleClassifications/master/index.html b/es/extensions/procurementMethodRationaleClassifications/master/index.html
new file mode 100644
index 000000000..d1d4f6c61
--- /dev/null
+++ b/es/extensions/procurementMethodRationaleClassifications/master/index.html
@@ -0,0 +1,320 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificaciones de los fundamentos de métodos de contratación +
+ ++ Agregar una lista al objeto de licitación para clasificar la justificación del método de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ TED_PT_AWARD_CONTRACT_WITHOUT_CALL
+
+ |
+ + European Union direct award justification (TED schema) + | +
+ Justification for using a procedure which allows awarding contracts directly without the requirement of publishing a call for competition in the Official Journal of the European Union. This scheme's codes match those in the TED schema. + +
|
+
+
+ eforms-direct-award-justification
+
+ |
+ + European Union direct award justification (eForms) + | +
+ Justification for using a procedure which allows awarding contracts directly without the requirement of publishing a call for competition in the Official Journal of the European Union. This scheme's codes match those in eForms. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/procurementMethodRationaleClassifications/master/release-schema.json b/es/extensions/procurementMethodRationaleClassifications/master/release-schema.json
new file mode 100644
index 000000000..aea432eff
--- /dev/null
+++ b/es/extensions/procurementMethodRationaleClassifications/master/release-schema.json
@@ -0,0 +1,19 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "procurementMethodRationaleClassifications": {
+ "title": "Clasificaciones de los fundamentos de m\u00e9todos de contrataci\u00f3n",
+ "description": "Las clasificaciones de la justificaci\u00f3n del m\u00e9todo de contrataci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/procurementMethodRationaleClassifications/master/schema/index.html b/es/extensions/procurementMethodRationaleClassifications/master/schema/index.html
new file mode 100644
index 000000000..56701bf23
--- /dev/null
+++ b/es/extensions/procurementMethodRationaleClassifications/master/schema/index.html
@@ -0,0 +1,236 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificaciones de los fundamentos de métodos de contratación +
+ ++ Agregar una lista al objeto de licitación para clasificar la justificación del método de contratación. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar una lista al objeto de licitación para clasificar la justificación del método de contratación.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BT-136 (Direct Award Justification Code). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+{
+ "tender": {
+ "procurementMethodRationaleClassifications": [
+ {
+ "id": "D_NO_TENDERS_REQUESTS",
+ "description": "No tenders or no suitable tenders/requests to participate in response to a procedure with prior call for competition",
+ "scheme": "TED_PT_AWARD_CONTRACT_WITHOUT_CALL"
+ },
+ {
+ "id": "D_FROM_LIQUIDATOR_CREDITOR",
+ "description": "Purchase of supplies or services on particularly advantageous terms from the liquidator in an insolvency procedure, an arrangement with creditors or a similar procedure under national laws and regulations",
+ "scheme": "TED_PT_AWARD_CONTRACT_WITHOUT_CALL"
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-04-05
+-
+
- Add 'eforms-direct-award-justification' to the
+itemClassificationScheme.csvcodelist.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues) and in pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/project/index.html b/es/extensions/project/index.html
new file mode 100644
index 000000000..ea21af6cd
--- /dev/null
+++ b/es/extensions/project/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificaciones de los fundamentos de métodos de contratación +
+ ++ Agregar una lista al objeto de licitación para clasificar la justificación del método de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ procurementMethodRationaleClassifications
+
+ |
+ + Clasificaciones de los fundamentos de métodos de contratación + | +
+ Las clasificaciones de la justificación del método de contratación. + + |
+ + array of Classification objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/project/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/project/master/release-schema.json b/es/extensions/project/master/release-schema.json
new file mode 100644
index 000000000..d67ff0842
--- /dev/null
+++ b/es/extensions/project/master/release-schema.json
@@ -0,0 +1,105 @@
+{
+ "definitions": {
+ "Planning": {
+ "properties": {
+ "project": {
+ "title": "Informaci\u00f3n de proyecto",
+ "description": "Una secci\u00f3n de proyecto se puede usar para describir la relaci\u00f3n entre este proceso de contrataci\u00f3n y un proyecto o programa de trabajo.",
+ "$ref": "#/definitions/Project"
+ }
+ }
+ },
+ "Project": {
+ "title": "Informaci\u00f3n de proyecto",
+ "description": "Un proyecto o programa de trabajo.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "Identificador de proyecto",
+ "description": "Un identificador externo para el proyecto. \u00c9ste puede tomarse de un registro de proyectos o puede basarse en la versi\u00f3n can\u00f3nica de un nombre de proyecto. Los IDs de proyecto deben de ser \u00fanicos para un publicador. Se pueden usar URIs.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo del Proyecto",
+ "description": "El nombre del proyecto con el cual se relaciona este proceso de contrataci\u00f3n. Algunas organizaciones mantienen un registro de proyectos y los datos deben de usar el nombre por el cual se conoce al proyecto en dicho registro.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n del proyecto",
+ "description": "Una breve descripci\u00f3n en texto libre del proyecto.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "totalValue": {
+ "title": "Valor total del proyecto",
+ "description": "El monto total anticipado del proyecto a lo largo de su duraci\u00f3n.",
+ "$ref": "#/definitions/Value"
+ },
+ "uri": {
+ "title": "Informaci\u00f3n vinculada del proyecto",
+ "description": "Un URI que apunte a mayor informaci\u00f3n sobre este proyecto.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ },
+ "sector": {
+ "title": "Sector del proyecto",
+ "description": "Una categorizaci\u00f3n general del sector principal con el cual se relaciona este proceso de licitaci\u00f3n. Se recomienda el uso de [UN COFOG codes](https://unstats.un.org/unsd/publications/catalogue?selectID=145), con 'COFOG' como esquema de clasificaci\u00f3n y el c\u00f3digo num\u00e9rico COFOG para la clasificaci\u00f3n primaria de sector.",
+ "$ref": "#/definitions/Classification"
+ },
+ "additionalClassifications": {
+ "title": "Clasificaciones sectoriales adicionales ",
+ "description": "Clasificaci\u00f3n adicional del proyecto por otras clasificaciones de sector o usando otros esquemas de clasificaci\u00f3n (p.ej. Contra un marco estrat\u00e9gico).",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "locations": {
+ "title": "Ubicaci\u00f3n de Proyecto",
+ "description": "Informaci\u00f3n sobre la ubicaci\u00f3n donde se llevar\u00e1 a cabo un proyecto.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Location"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "patternProperties": {
+ "^(description_(((([A-Za-z]{2,3}(-([A-Za-z]{3}(-[A-Za-z]{3}){0,2}))?)|[A-Za-z]{4}|[A-Za-z]{5,8})(-([A-Za-z]{4}))?(-([A-Za-z]{2}|[0-9]{3}))?(-([A-Za-z0-9]{5,8}|[0-9][A-Za-z0-9]{3}))*(-([0-9A-WY-Za-wy-z](-[A-Za-z0-9]{2,8})+))*(-(x(-[A-Za-z0-9]{1,8})+))?)|(x(-[A-Za-z0-9]{1,8})+)))$": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "^(title_(((([A-Za-z]{2,3}(-([A-Za-z]{3}(-[A-Za-z]{3}){0,2}))?)|[A-Za-z]{4}|[A-Za-z]{5,8})(-([A-Za-z]{4}))?(-([A-Za-z]{2}|[0-9]{3}))?(-([A-Za-z0-9]{5,8}|[0-9][A-Za-z0-9]{3}))*(-([0-9A-WY-Za-wy-z](-[A-Za-z0-9]{2,8})+))*(-(x(-[A-Za-z0-9]{1,8})+))?)|(x(-[A-Za-z0-9]{1,8})+)))$": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/project/master/schema/index.html b/es/extensions/project/master/schema/index.html
new file mode 100644
index 000000000..f211bd49d
--- /dev/null
+++ b/es/extensions/project/master/schema/index.html
@@ -0,0 +1,407 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Proyecto +
+ ++ Agrega un objeto de proyecto al objeto de planificación para describir el proyecto con el que está relacionado el proceso de contratación, incluido el valor total del proyecto (no debe confundirse con el valor total del proceso de contratación). +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Esta extensión agrega un objeto project al objeto planning.
En OCDS, la información del proyecto está anidada bajo el objeto planning.budget. Sin embargo, en algunos casos, los sistemas de gestión presupuestaria y de gestión de proyecto están separados, y podría ser importante especificar por separado:
-
+
- La cantidad reservada en el presupuesto para un proceso de contratación específico +
- El proyecto al que se refiere el contrato y el valor total de dicho proyecto +
- Clasificaciones de sector +
- Clasificaciones adicionales +
- Ubicaciones del proyecto, con opciones de diccionario geográfico o ubicaciones puntuales +
Esto es particularmente importante en casos de alianzas público-privadas y grandes proyectos de infraestructura, donde los usuarios pueden querer hacer un seguimiento de todos los procesos de contratación relacionados con el proyecto a gran escala y comprender los contratos individuales en el contexto de su proceso de contratación y el proyecto en general. valores.
+This extension must be used with the Location extension.
+Ejemplos
+Proyecto de infraestructura
+{
+ "planning": {
+ "project": {
+ "id": "oc4ids-gx3fo2-000002",
+ "title": "Construcción de red de drenaje sanitario en diversas calles de la colonia Ruperto Martínez",
+ "description": "Construcción de red de drenaje sanitario consistente en excavación de 756 metros cúbicos para alojar la red de drenaje sanitario, suministro y colocación de 712 metros de tubería PVC tipo serie 20 pared solida, construcción de 15 pozos de visita y 30 descargas domiciliarias sencillas en la colonia Ruperto Martinez, en el municipio de Higueras, N.L.",
+ "totalValue": {
+ "amount": 4010130.1,
+ "currency": "MXN"
+ },
+ "locations": [
+ {
+ "description": "Col. Ruperto Martínez, Higueras, N.L.",
+ "geometry": {
+ "type": "Point",
+ "coordinates": [
+ 25.953400063796533,
+ -100.01606973176307
+ ]
+ }
+ }
+ ]
+ }
+ }
+}
+Proyecto de Asociación Público-Privada
+{
+ "planning": {
+ "project": {
+ "title": "Example PPP",
+ "description": "The Example PPP project will guarantee the installation of a wholesale shared network that allows the provision of telecommunications services by current and future operators.",
+ "id": "example_ppp",
+ "uri": "http://communications.gov.example/projects/example_ppp",
+ "totalValue": {
+ "amount": 600000000,
+ "currency": "USD"
+ },
+ "sector": {
+ "scheme": "COFOG",
+ "description": "Road transportation",
+ "id": "04.5.1"
+ },
+ "locations": [
+ {
+ "description": "Local Authority Area: Halton Borough Council",
+ "gazetteer": {
+ "scheme": "GEONAMES",
+ "identifiers": [
+ "2647601"
+ ]
+ }
+ }
+ ]
+ }
+ }
+}
+Registro de cambios
+2021-04-15
+-
+
- Agregar un ejemplo de proyecto de infraestructura +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2020-04-16
+-
+
- Eliminar guía relacionada al objeto
planning.budget. Ver #701.
+
2018-05-03
+-
+
- Agregar guía adicional sobre el uso de los campos de OCDS en el contexto de esta extensión +
2017-12-29
+-
+
- Eliminar la repetición de campos OCDS en esta extensión +
2017-07-08
+-
+
- Agregar soporte multilingüe para el campo
Project.title
+ - Eliminar el soporte multilingüe para los campos inexistentes
Project.sourceyProject.project
+ - Restaurar los campos
Budget.projectyBudget.projectID
+ - Eliminar la propiedad obsoleta
mergeStrategy.
+
Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/recurrence/index.html b/es/extensions/recurrence/index.html
new file mode 100644
index 000000000..2bf6513b9
--- /dev/null
+++ b/es/extensions/recurrence/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Proyecto +
+ ++ Agrega un objeto de proyecto al objeto de planificación para describir el proyecto con el que está relacionado el proceso de contratación, incluido el valor total del proyecto (no debe confundirse con el valor total del proceso de contratación). +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Planning +
+ +
+ The extension defines these fields in the Planning object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ project
+
+ |
+ + Información de proyecto + | +
+ Una sección de proyecto se puede usar para describir la relación entre este proceso de contratación y un proyecto o programa de trabajo. + + |
+ + Project object + | +
+ Project +
+ +
+ The extension defines a new Project object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador de proyecto + | +
+ Un identificador externo para el proyecto. Éste puede tomarse de un registro de proyectos o puede basarse en la versión canónica de un nombre de proyecto. Los IDs de proyecto deben de ser únicos para un publicador. Se pueden usar URIs. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título del Proyecto + | +
+ El nombre del proyecto con el cual se relaciona este proceso de contratación. Algunas organizaciones mantienen un registro de proyectos y los datos deben de usar el nombre por el cual se conoce al proyecto en dicho registro. + ++ This field has multilingual support. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción del proyecto + | +
+ Una breve descripción en texto libre del proyecto. + ++ This field has multilingual support. + + |
+ + string + | +
+
+ totalValue
+
+ |
+ + Valor total del proyecto + | +
+ El monto total anticipado del proyecto a lo largo de su duración. + + |
+ + Value object + | +
+
+ uri
+
+ |
+ + Información vinculada del proyecto + | +
+ Un URI que apunte a mayor información sobre este proyecto. + + |
+ + string + | +
+
+ sector
+
+ |
+ + Sector del proyecto + | +
+ Una categorización general del sector principal con el cual se relaciona este proceso de licitación. Se recomienda el uso de UN COFOG codes, con 'COFOG' como esquema de clasificación y el código numérico COFOG para la clasificación primaria de sector. + + |
+ + Classification object + | +
+
+ additionalClassifications
+
+ |
+ + Clasificaciones sectoriales adicionales + | +
+ Clasificación adicional del proyecto por otras clasificaciones de sector o usando otros esquemas de clasificación (p.ej. Contra un marco estratégico). + + |
+ + array of Classification objects + | +
+
+ locations
+
+ |
+ + Ubicación de Proyecto + | +
+ Información sobre la ubicación donde se llevará a cabo un proyecto. + + |
+ + array of Location objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/recurrence/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/recurrence/master/release-schema.json b/es/extensions/recurrence/master/release-schema.json
new file mode 100644
index 000000000..6fbafe664
--- /dev/null
+++ b/es/extensions/recurrence/master/release-schema.json
@@ -0,0 +1,66 @@
+{
+ "definitions": {
+ "Recurrence": {
+ "title": "Recurrencia",
+ "description": "Informaci\u00f3n acerca de la recurrencia del proceso de contrataci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "dates": {
+ "title": "Fechas estimadas",
+ "description": "Una estimaci\u00f3n del calendario de iniciaciones posteriores de los procesos de contrataci\u00f3n (por ejemplo, avisos de contrataci\u00f3n prevista).",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Period"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "description": {
+ "title": "Para m\u00e1s informaci\u00f3n",
+ "description": "Cualquier otra informaci\u00f3n acerca de la recurrencia del proceso de contrataci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Tender": {
+ "properties": {
+ "recurrence": {
+ "title": "Recurrencia",
+ "description": "Informaci\u00f3n acerca de la recurrencia del proceso de contrataci\u00f3n.",
+ "$ref": "#/definitions/Recurrence"
+ },
+ "hasRecurrence": {
+ "title": "Tiene recurrencia",
+ "description": "Si el proceso de contrataci\u00f3n es recurrente.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "recurrence": {
+ "title": "Recurrencia",
+ "description": "Informaci\u00f3n acerca de la recurrencia del lote.",
+ "$ref": "#/definitions/Recurrence"
+ },
+ "hasRecurrence": {
+ "title": "Tiene recurrencia",
+ "description": "Si el proceso de contrataci\u00f3n es recurrente.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/recurrence/master/schema/index.html b/es/extensions/recurrence/master/schema/index.html
new file mode 100644
index 000000000..a10e07449
--- /dev/null
+++ b/es/extensions/recurrence/master/schema/index.html
@@ -0,0 +1,384 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Recurrencia +
+ ++ Agregar campos de información acerca de la recurrencia del proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Esta extensión agrega campos de información sobre la recurrencia del proceso de contratación.
+"Recurrence" means another contracting process for the same goods, services or works is likely to occur. This is not the same as awarding multiple contracts within a framework agreement.
+A company might, for example, use this information to decide to invest in the machinery they would need to compete for the potential future contract.
+Contexto Legal
+El [Revised Agreement on Government Procurement] (https://www.wto.org/english/docs_e/legal_e/rev-gpr-94_01_e.htm) (GPA) incluye: "cada aviso de contratación prevista deberá incluir ... c. para los contratos recurrentes, una estimación, si es posible, del calendario de avisos posteriores de contratación prevista".
+La Unión Europea es una parte al GPA, y como tal su Directiva 2014/24/EU (Contratos públicos - que establecen reglas básicas claras) incluye: "Parte C: Información que se incluirá en los avisos de contrato ... 27. En el caso de adquisiciones periódicas, tiempo estimado para que se publiquen más avisos".
+This extension's fields correspond to eForms BT-94 (Recurrence) and BT-95 (Recurrence Description).
+Ejemplo
+{
+ "tender": {
+ "hasRecurrence": true,
+ "recurrence": {
+ "dates": [
+ {
+ "startDate": "2020-01-01T00:00:00Z"
+ },
+ {
+ "startDate": "2021-01-01T00:00:00Z"
+ }
+ ],
+ "description": "The duration of this contract and recurrent contracts will not exceed three years."
+ }
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
El borrador original de la extensión se puede encontrar en el repositorio archivado de perfiles comerciales
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/releasePublisher/index.html b/es/extensions/releasePublisher/index.html
new file mode 100644
index 000000000..cb0b7312e
--- /dev/null
+++ b/es/extensions/releasePublisher/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Recurrencia +
+ ++ Agregar campos de información acerca de la recurrencia del proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Recurrence +
+ +
+ The extension defines a new Recurrence object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ dates
+
+ |
+ + Fechas estimadas + | +
+ Una estimación del calendario de iniciaciones posteriores de los procesos de contratación (por ejemplo, avisos de contratación prevista). + + |
+ + array of Period objects + | +
+
+ description
+
+ |
+ + Para más información + | +
+ Cualquier otra información acerca de la recurrencia del proceso de contratación. + + |
+ + string + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ recurrence
+
+ |
+ + Recurrencia + | +
+ Información acerca de la recurrencia del proceso de contratación. + + |
+ + Recurrence object + | +
+
+ hasRecurrence
+
+ |
+ + Tiene recurrencia + | +
+ Si el proceso de contratación es recurrente. + + |
+ + boolean + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ recurrence
+
+ |
+ + Recurrencia + | +
+ Información acerca de la recurrencia del lote. + + |
+ + Recurrence object + | +
+
+ hasRecurrence
+
+ |
+ + Tiene recurrencia + | +
+ Si el proceso de contratación es recurrente. + + |
+ + boolean + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/releasePublisher/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/releasePublisher/master/release-schema.json b/es/extensions/releasePublisher/master/release-schema.json
new file mode 100644
index 000000000..eaf59345d
--- /dev/null
+++ b/es/extensions/releasePublisher/master/release-schema.json
@@ -0,0 +1,44 @@
+{
+ "properties": {
+ "publisher": {
+ "title": "Publicador",
+ "description": "Informaci\u00f3n que identifica \u00fanicamente al publicador de este release",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Nombre",
+ "description": "El nombre de la organizaci\u00f3n o departamento responsable de publicar estos datos",
+ "type": "string"
+ },
+ "scheme": {
+ "title": "Esquema",
+ "description": "El esquema tiene identificadores \u00fanicos que se usan para identificar el art\u00edculo que se esta identificando",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "uid": {
+ "title": "uid",
+ "description": "El ID \u00fanico para esta entidad bajo el esquema ID que se dio. Note el uso de 'uid' en lugar de 'id'. Vea el issue #245",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "uri": {
+ "title": "URI",
+ "description": "Se usa un URI para identificar el publicador",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ },
+ "required": [
+ "name"
+ ]
+ }
+ }
+}
diff --git a/es/extensions/releasePublisher/master/schema/index.html b/es/extensions/releasePublisher/master/schema/index.html
new file mode 100644
index 000000000..8c85aea86
--- /dev/null
+++ b/es/extensions/releasePublisher/master/schema/index.html
@@ -0,0 +1,299 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Publicador del Release +
+ ++ Incluye información sobre el publicador a nivel release para los casos en los que un paquete de releases o un paquete de records contienen releases de diferentes publicadores +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Extensión de publicador de release
+Descripción
+Includes the information about the publisher at release level for the cases in that a release-package or record-packages +contains releases from different publishers.
+Campos
+-
+
- release.publisher: Información que se usa únicamente para identificar el publicador de este release +
Ejemplo
+{
+ "publisher": {
+ "name": "SECRETARÍA DE LA FUNCIÓNN PÚBLICA / SECRETARIA DE HACIENDA Y CRÉDITO PÚBLICO",
+ "uri": "http://www.gob.mx/contratacionesabiertas/"
+ },
+ "license": "https://datos.gob.mx/libreusomx",
+ "publishedDate": "2018-02-14T19:23:19.405517Z",
+ "uri": "https://api.datos.gob.mx/v1/",
+ "records": [
+ {
+ "ocid": "ocds-07smqs-1303516",
+ "releases": [
+ {
+ "publisher": {
+ "uri": "http://www.gob.mx/sfp",
+ "uid": "27511",
+ "name": "SECRETARÍA DE LA FUNCIÓN PÚBLICA"
+ },
+ "language": "es"
+ ....
+ },
+ {
+ "publisher": {
+ "uri": "http://www.gob.mx/shcp",
+ "uid": "00000",
+ "name": "SECRETARÍA DE HACIENDA Y CRÉDITO PÚBLICO"
+ },
+ "language": "es"
+ ....
+ }
+ ]
+ }
+ ]
+}
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/releaseSource/index.html b/es/extensions/releaseSource/index.html
new file mode 100644
index 000000000..de751bf25
--- /dev/null
+++ b/es/extensions/releaseSource/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Publicador del Release +
+ ++ Incluye información sobre el publicador a nivel release para los casos en los que un paquete de releases o un paquete de records contienen releases de diferentes publicadores +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ publisher
+
+ |
+ + Publicador + | +
+ Información que identifica únicamente al publicador de este release + + |
+ + object + | +
+
+ publisher.
+ |
+ + Nombre + | +
+ El nombre de la organización o departamento responsable de publicar estos datos + + |
+ + string + | +
+
+ publisher.
+ |
+ + Esquema + | +
+ El esquema tiene identificadores únicos que se usan para identificar el artículo que se esta identificando + + |
+ + string + | +
+
+ publisher.
+ |
+ + uid + | +
+ El ID único para esta entidad bajo el esquema ID que se dio. Note el uso de 'uid' en lugar de 'id'. Vea el issue #245 + + |
+ + string + | +
+
+ publisher.
+ |
+ + URI + | +
+ Se usa un URI para identificar el publicador + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/releaseSource/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/releaseSource/master/release-schema.json b/es/extensions/releaseSource/master/release-schema.json
new file mode 100644
index 000000000..2acbdf709
--- /dev/null
+++ b/es/extensions/releaseSource/master/release-schema.json
@@ -0,0 +1,51 @@
+{
+ "properties": {
+ "sources": {
+ "title": "Fuentes",
+ "description": "Los sistemas de informaci\u00f3n de los cuales surgen los datos",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Source"
+ },
+ "uniqueItems": true
+ }
+ },
+ "definitions": {
+ "Source": {
+ "type": "object",
+ "title": "Fuente",
+ "description": "El sistema de informaci\u00f3n del cual los datos se originan",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "El identificador \u00fanico local para la fuente",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "name": {
+ "title": "Nombre",
+ "description": "El nombre de la fuente",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "title": "URL",
+ "description": "La direcci\u00f3n web de la fuente",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/releaseSource/master/schema/index.html b/es/extensions/releaseSource/master/schema/index.html
new file mode 100644
index 000000000..1e7ca3f35
--- /dev/null
+++ b/es/extensions/releaseSource/master/schema/index.html
@@ -0,0 +1,316 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Fuentes +
+ ++ Añade una lista de fuentes para indicar los sistemas de información de los cuales se originan los datos +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En muchos casos, la publicación OCDS combina información de múltiples sistemas de información o bases de datos. Por ejemplo:
+-
+
- Un publicador puede obtener información de varios sistemas para crear un release único. +
- Distintos sistemas pueden ser responsables de distintos procesos de contrataciones; por ejemplo, compras tradicionales, marcos de referencia y asociaciones público-privadas se pueden gestionar en diferentes sistemas. +
- Distintos sistemas pueden ser responsables de distintos procesos de contrataciones, publicado en distintos releases: por ejemplo, datos de presupuesto del sistema de Ministerio de Finanzas y solicitudes de datos de del sistema de la Agencia de Compras Públicas. +
- Distintos sistemas pueden cubrir diferentes períodos, por ejemplo, datos más antiguos que no se han migrado al nuevo sistema. +
La procedencia de los datos es relevante para muchos casos de uso, incluyendo la verificación de datos.
+Para satisfacer los casos de uso, esta extensión incluye una lista de sources en el esquema de release, en el cual el publicador puede hacer una lista de los sistemas de información de los cuales surgen los datos del release.
Ejemplo
+{
+ "sources": [
+ {
+ "id": "sample-source",
+ "name": "Sample Source",
+ "url": "http://example.com"
+ },
+ {
+ "id": "honducompras",
+ "name": "HonduCompras 1.0",
+ "url": "http://h1.honducompras.gob.hn/"
+ }
+ ]
+}
+Notas de uso
+Existen casos donde la fuente de los datos de un release vienen de diferentes sistemas de información del mismo publicador.
+Existen casos en donde se ligan los datos de bases de datos de contratos con las bases de datos de ofertas y procesos tradicionales.
+Registro de cambios
+Esta extensión se discutió originalmente en https://github.com/open-contracting/standard/issues/800.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/renewal/index.html b/es/extensions/renewal/index.html
new file mode 100644
index 000000000..e56f47380
--- /dev/null
+++ b/es/extensions/renewal/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Fuentes +
+ ++ Añade una lista de fuentes para indicar los sistemas de información de los cuales se originan los datos +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ sources
+
+ |
+ + Fuentes + | +
+ Los sistemas de información de los cuales surgen los datos + + |
+ + array of Source objects + | +
+ Source +
+ +
+ The extension defines a new Source object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ El identificador único local para la fuente + + |
+ + string or integer + | +
+
+ name
+
+ |
+ + Nombre + | +
+ El nombre de la fuente + + |
+ + string + | +
+
+ url
+
+ |
+ + URL + | +
+ La dirección web de la fuente + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/renewal/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/renewal/master/release-schema.json b/es/extensions/renewal/master/release-schema.json
new file mode 100644
index 000000000..a4fd7966e
--- /dev/null
+++ b/es/extensions/renewal/master/release-schema.json
@@ -0,0 +1,76 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "hasRenewal": {
+ "title": "Tiene renovaci\u00f3n",
+ "description": "Si los contratos se pueden renovar.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "renewal": {
+ "title": "Renovaci\u00f3n",
+ "description": "Las opciones para la renovaci\u00f3n de los contratos.",
+ "$ref": "#/definitions/Renewal"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "hasRenewal": {
+ "title": "Tiene renovaci\u00f3n",
+ "description": "Si se puede renovar el contrato relacionado con el lote.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "renewal": {
+ "title": "Renovaci\u00f3n",
+ "description": "Las opciones para la renovaci\u00f3n del contrato relacionadas con el lote.",
+ "$ref": "#/definitions/Renewal"
+ }
+ }
+ },
+ "Renewal": {
+ "title": "Renovaci\u00f3n",
+ "description": "Informaci\u00f3n sobre las opciones para la renovaci\u00f3n de un contrato.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una descripci\u00f3n de las opciones para la renovaci\u00f3n del contrato.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "minimumRenewals": {
+ "title": "Renovaci\u00f3n m\u00ednima",
+ "description": "El n\u00famero m\u00ednimo de renovaciones.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "maximumRenewals": {
+ "title": "Renovaci\u00f3n m\u00e1xima",
+ "description": "El n\u00famero m\u00e1ximo de renovaciones. Si no hay un m\u00e1ximo, establecer a 1e9999 (que analiza hasta infinito).",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "period": {
+ "title": "Periodo de renovaci\u00f3n",
+ "description": "El per\u00edodo durante el cual se puede renovar el contrato.",
+ "$ref": "#/definitions/Period"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/renewal/master/schema/index.html b/es/extensions/renewal/master/schema/index.html
new file mode 100644
index 000000000..8c1d76204
--- /dev/null
+++ b/es/extensions/renewal/master/schema/index.html
@@ -0,0 +1,418 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Renovación +
+ ++ Agrega campos a los objetos de la licitación y del lote, para describir las opciones de los términos de renovación de los contratos. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar campos a los objetos de la licitación y del lote, para describir las opciones de los términos de renovación de los contratos.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BT-57 (Renewal Description). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Guía
+Si el número de veces que se puede renovar un contrato es un número exacto y no un rango, establecer minimumRenewals y maximumRenewals al mismo número.
Ejemplo
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "lot-1",
+ "title": "Architectural services",
+ "description": "For architectural services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 200000
+ },
+ "contractPeriod": {
+ "startDate": "2020-10-10T00:00:00Z",
+ "endDate": "2021-11-10T00:00:00Z"
+ },
+ "hasRenewal": false
+ },
+ {
+ "id": "lot-2",
+ "title": "Civil engineering services",
+ "description": "For civil engineering services delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 400000
+ },
+ "contractPeriod": {
+ "startDate": "2020-12-10T00:00:00Z",
+ "endDate": "2021-12-10T00:00:00Z"
+ },
+ "hasRenewal": true,
+ "renewal": {
+ "description": "The contracting authority reserves the right to extend the term for a period or periods of up to 1 year with a maximum of 2 such extensions on the same terms and conditions, subject to the contracting authority’s obligations at law.",
+ "maximumRenewals": 2,
+ "period": {
+ "durationInDays": 365
+ }
+ }
+ },
+ {
+ "id": "lot-3",
+ "title": "Structural engineering",
+ "description": "For structural engineering consultancy delivered in the project",
+ "status": "active",
+ "value": {
+ "currency": "GBP",
+ "amount": 600000
+ },
+ "contractPeriod": {
+ "startDate": "2021-02-10T00:00:00Z",
+ "endDate": "2022-02-10T00:00:00Z"
+ },
+ "hasRenewal": true,
+ "renewal": {
+ "description": "Contracts are due to be renewed one time at the end of the initial term.",
+ "minimumRenewals": 3,
+ "maximumRenewals": 3,
+ "period": {
+ "startDate": "2021-02-10T00:00:00Z",
+ "endDate": "2024-02-10T00:00:00Z"
+ }
+ }
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2021-01-19
+-
+
- Add fields:
+
-
+
Tender.hasRenewal
+Tender.renewal
+
+
2020-10-06
+-
+
- Add fields:
+
-
+
Renewal.minimumRenewals
+Renewal.maximumRenewals
+Renewal.period
+
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues) en issue 22 y en pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/requirements/index.html b/es/extensions/requirements/index.html
new file mode 100644
index 000000000..99b7042d8
--- /dev/null
+++ b/es/extensions/requirements/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Renovación +
+ ++ Agrega campos a los objetos de la licitación y del lote, para describir las opciones de los términos de renovación de los contratos. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasRenewal
+
+ |
+ + Tiene renovación + | +
+ Si los contratos se pueden renovar. + + |
+ + boolean + | +
+
+ renewal
+
+ |
+ + Renovación + | +
+ Las opciones para la renovación de los contratos. + + |
+ + Renewal object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasRenewal
+
+ |
+ + Tiene renovación + | +
+ Si se puede renovar el contrato relacionado con el lote. + + |
+ + boolean + | +
+
+ renewal
+
+ |
+ + Renovación + | +
+ Las opciones para la renovación del contrato relacionadas con el lote. + + |
+ + Renewal object + | +
+ Renewal +
+ +
+ The extension defines a new Renewal object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Descripción + | +
+ Una descripción de las opciones para la renovación del contrato. + + |
+ + string + | +
+
+ minimumRenewals
+
+ |
+ + Renovación mínima + | +
+ El número mínimo de renovaciones. + + |
+ + number + | +
+
+ maximumRenewals
+
+ |
+ + Renovación máxima + | +
+ El número máximo de renovaciones. Si no hay un máximo, establecer a 1e9999 (que analiza hasta infinito). + + |
+ + number + | +
+
+ period
+
+ |
+ + Periodo de renovación + | +
+ El período durante el cual se puede renovar el contrato. + + |
+ + Period object + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/requirements/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/requirements/master/extension.json b/es/extensions/requirements/master/extension.json
new file mode 100644
index 000000000..42cc20416
--- /dev/null
+++ b/es/extensions/requirements/master/extension.json
@@ -0,0 +1,29 @@
+{
+ "name": {
+ "en": "Requirements",
+ "es": "Requisitos"
+ },
+ "description": {
+ "en": "Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV).",
+ "es": "Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV)."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/requirements/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "dataType.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/requirements/master/index.html b/es/extensions/requirements/master/index.html
new file mode 100644
index 000000000..dc2eda8ab
--- /dev/null
+++ b/es/extensions/requirements/master/index.html
@@ -0,0 +1,491 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Requisitos +
+ ++ Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV). +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ dataType.csv +
+ +
+ You can download the dataType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ string
+
+ |
+ + String + | +
+ The response must be of type string + + |
+
+
+ date-time
+
+ |
+ + Date-time + | +
+ The response must be of type date-time (ISO8601) + + |
+
+
+ number
+
+ |
+ + Number + | +
+ The response must be of type number, i.e. a floating point or whole number + + |
+
+
+ integer
+
+ |
+ + Integer + | +
+ The response must be of type integer + + |
+
+
+ boolean
+
+ |
+ + Boolean + | +
+ The response must be of type boolean + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/requirements/master/release-schema.json b/es/extensions/requirements/master/release-schema.json
new file mode 100644
index 000000000..afdd4b8a2
--- /dev/null
+++ b/es/extensions/requirements/master/release-schema.json
@@ -0,0 +1,328 @@
+{
+ "definitions": {
+ "Criterion": {
+ "title": "Criterio",
+ "description": "A criterion on which bids, tenderers, lots or items will be judged, evaluated or assessed.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "El identificador para este criterio. Debe de ser \u00fanico y no puede cambiar dentro del Proceso de Contrataci\u00f3n Abierta del cual es parte (definido por un s\u00f3lo ocid). Ver la [gu\u00eda de identificadores](http://standard.open-contracting.org/latest/en/schema/identifiers/) para mayores detalles.",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo",
+ "description": "Un t\u00edtulo para este criterio",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "A description of this criterion.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "relatesToTenderer": {
+ "title": "Relates to tenderer",
+ "description": "The criterion judges, evaluates or assesses a tenderer.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "relatedItem": {
+ "title": "Art\u00edculo relacionado",
+ "description": "The identifier of the item in the tender section to which this criterion applies.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "relatedLots": {
+ "title": "Related lot(s)",
+ "description": "The identifiers of the lots to which this criterion applies.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "requirementGroups": {
+ "title": "Grupos de requisitos",
+ "description": "Una lista de grupos de requisitos para este Criterio. Un criterio se satisface cuando uno o m\u00e1s grupos de requisitos se cumplen. Un grupo de requisitos se cumple cuando todos los requerimientos del grupo se satisfacen.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/RequirementGroup"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "RequirementGroup": {
+ "title": "Grupo de requisitos",
+ "description": "Un grupo de requisitos es un conjunto de requisitos que deben cumplirse juntos para validar un criterio.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "El identificador para este grupo de requisitos. Debe ser \u00fanico y no puede cambiar dentro del Proceso de Contrataci\u00f3n Abierta del que forma parte (definido por un solo ocid). Consulte la [gu\u00eda de identificadores](http://standard.open-contracting.org/latest/en/schema/identifiers/) para obtener m\u00e1s detalles.",
+ "type": "string",
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "A description of this requirement group.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "requirements": {
+ "title": "Requisitos",
+ "description": "Una lista de requisitos que deben ser cumplidos para que el grupo de requisitos se cumpla.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Requirement"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Requirement": {
+ "title": "Requisito",
+ "description": "Un requisito at\u00f3mico. Los requisitos pueden especificar el valor esperado que la respuesta debe contener, o un rango de valores tope en los que la respuesta debe de entrar. El requisito puede aplicar a un per\u00edodo espec\u00edfico de tiempo.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador del requisito",
+ "description": "El identificador de este requisito. Debe ser \u00fanico y no puede cambiar dentro del Proceso de Contrataci\u00f3n Abierta de que forma parte (definido por un solo ocid). Consulte la [gu\u00eda de identificadores](http://standard.open-contracting.org/latest/en/schema/identifiers/) para obtener m\u00e1s detalles.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo de requisito",
+ "description": "El t\u00edtulo de este requisito at\u00f3mico.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n del requisito",
+ "description": "Una descripci\u00f3n de texto libre para este requisito at\u00f3mico",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "dataType": {
+ "title": "Tipo de dato de Requisito",
+ "description": "The data type in which the response must be provided.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "dataType.csv",
+ "openCodelist": false,
+ "enum": [
+ "string",
+ "date-time",
+ "number",
+ "integer",
+ "boolean",
+ null
+ ]
+ },
+ "pattern": {
+ "title": "Patr\u00f3n de validaci\u00f3n de respuesta",
+ "description": "A regular expression with which to validate the response.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "expectedValue": {
+ "title": "Valor esperado",
+ "description": "The expected value of the requirement, when the response must be specific value.",
+ "type": [
+ "string",
+ "integer",
+ "number",
+ "boolean",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "minValue": {
+ "title": "Valor m\u00ednimo",
+ "description": "The lower bound of the requirement, when the response must be within a certain range.",
+ "type": [
+ "integer",
+ "number",
+ "null"
+ ]
+ },
+ "maxValue": {
+ "title": "Valor m\u00e1ximo",
+ "description": "The upper bound of the requirement, when the response must be within a certain range.",
+ "type": [
+ "integer",
+ "number",
+ "null"
+ ]
+ },
+ "period": {
+ "title": "Periodo",
+ "description": "The period to which the requirement applies: for example, the tenderer's turnover in a given year.",
+ "$ref": "#/definitions/Period"
+ }
+ },
+ "minProperties": 1
+ },
+ "RequirementResponse": {
+ "title": "Requirement response",
+ "description": "An assertion that responds to a single requirement. A response provides the value for the requirement and may provide the period to which it applies.",
+ "type": "object",
+ "required": [
+ "id",
+ "requirement"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador",
+ "description": "The unique identifier of this response in the context of the contracting process.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo",
+ "description": "The title of this response.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "The description of this response.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "value": {
+ "title": "Valor",
+ "description": "The value of this response.",
+ "type": [
+ "string",
+ "integer",
+ "number",
+ "boolean",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "period": {
+ "title": "Periodo",
+ "description": "The period to which the response applies.",
+ "$ref": "#/definitions/Period"
+ },
+ "requirement": {
+ "title": "Requisito relacionado",
+ "description": "A reference to the requirement to which the response applies.",
+ "$ref": "#/definitions/RequirementReference"
+ }
+ },
+ "minProperties": 1
+ },
+ "RequirementReference": {
+ "title": "Referencia de requisito",
+ "description": "A reference to a requirement.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID de requisito",
+ "description": "The identifier of the requirement to which the response applies.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo de requisito",
+ "description": "The title of the requirement to which the response applies.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Bid": {
+ "properties": {
+ "requirementResponses": {
+ "title": "Respuestas de requisito",
+ "description": "The responses of this bid to the requirements.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/RequirementResponse"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Tender": {
+ "properties": {
+ "criteria": {
+ "title": "Criterios",
+ "description": "Criteria on which bids, tenderers, lots or items will be judged, evaluated or assessed.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Criterion"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/requirements/master/schema/index.html b/es/extensions/requirements/master/schema/index.html
new file mode 100644
index 000000000..0dc7fba77
--- /dev/null
+++ b/es/extensions/requirements/master/schema/index.html
@@ -0,0 +1,916 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Requisitos +
+ ++ Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV). +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV).
+CCCEV is designed to support the exchange of information between buyers or procuring entities that define criteria and tenderers that respond to these criteria by means of evidences. Criteria can relate to bids, tenderers, lots or items.
+If your data does not closely follow the Core Criterion and Core Evidence Vocabulary (CCCEV), consider the Selection criteria extension.
+Modelo CCCEV
+El modelo CCCEV define los siguientes conceptos:
+Criterion +A criterion represents a rule or principle used to judge, evaluate or assess bids, tenderers, lots or items. A criterion is satisfied when one or more of its requirement groups is satisfied.
+Requirement Group +A requirement group is a collection of one or more individual requirements. A requirement group is satisfied when all of it's requirements are satisfied.
+Requirement +An atomic requirement which can be expressed as either an expected value or a range of accepted values.
+Requirement Response +A requirements response is an assertion that responds to a specific requirement.
+Por lo tanto, el modelo CCCEV puede usarse para expresar las condiciones AND, donde un grupo de requisitos debe cumplirse para satisfacer un criterio, así como las condiciones OR, donde existen requisitos alternativos que pueden satisfacer un criterio.
+The CCCEV model also defines a number of additional concepts including formalFrameworks, used to specify the legal instruments from criteria are derived, evidence, used both to specify and provide the evidence required to support a response, and additional properties of requirements such as certificationLevel. These are not yet implemented in this extension. This extension also does not describe formulae for calculating computed values, nor does it describe whether data should be published openly or not.
+Ejemplo
+Criteria for an item and a tenderer, with AND and OR conditions:
+{
+ "tender": {
+ "criteria": [
+ {
+ "id": "0001",
+ "title": "Air intake",
+ "description": "The vacuum cleaner air intake must be at least 100W",
+ "relatedItem": "item1",
+ "requirementGroups": [
+ {
+ "id": "0001-001",
+ "description": "The vacuum cleaner air intake must be at least 100W",
+ "requirements": [
+ {
+ "id": "0001-001-01",
+ "title": "Air intake",
+ "description": "Power of vacuum cleaner air intake in W",
+ "dataType": "integer",
+ "pattern": "[0-9]*",
+ "minValue": 100
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "id": "0002",
+ "title": "Warranty",
+ "description": "The vacuum cleaner must have warranty support options for at least 36 months",
+ "relatedItem": "item1",
+ "requirementGroups": [
+ {
+ "id": "0002-001",
+ "description": "The standard warranty period for the vacuum cleaner must be at least 36 months",
+ "requirements": [
+ {
+ "id": "0002-001-01",
+ "title": "Standard warranty period",
+ "description": "Length of the vacuum cleaner standard warranty period in months",
+ "dataType": "integer",
+ "pattern": "[0-9]*",
+ "minValue": 36
+ }
+ ]
+ },
+ {
+ "id": "0002-002",
+ "description": "The standard warranty period for the vacuum cleaner must be at least 12 months with an option to extend to 36 months",
+ "requirements": [
+ {
+ "id": "0002-002-01",
+ "title": "Standard warranty period",
+ "description": "Length of the vacuum cleaner standard warranty period in months",
+ "dataType": "integer",
+ "pattern": "[0-9]*",
+ "minValue": 12
+ },
+ {
+ "id": "0002-002-02",
+ "title": "Extended warranty option",
+ "description": "There is an extended warranty option for at least 36 months",
+ "dataType": "boolean",
+ "expectedValue": true
+ }
+ ]
+ }
+ ]
+ },
+ {
+ "id": "0003",
+ "title": "Years trading",
+ "description": "Number of years the tenderer has been trading",
+ "relatesToTenderer": true,
+ "requirementGroups": [
+ {
+ "id": "0003-001",
+ "description": "Number of years the tenderer has been trading",
+ "requirements": [
+ {
+ "id": "0003-001-01",
+ "title": "Years trading",
+ "description": "Number of years the tenderer has been trading",
+ "dataType": "integer",
+ "pattern": "[0-9]*",
+ "minValue": 3
+ }
+ ]
+ }
+ ]
+ }
+ ]
+ }
+}
+Responses to the criteria:
+{
+ "bids": {
+ "details": [
+ {
+ "id": "1",
+ "requirementResponses": [
+ {
+ "id": "air",
+ "value": 125,
+ "requirement": {
+ "id": "0001-001-01"
+ }
+ },
+ {
+ "id": "warranty",
+ "value": 36,
+ "requirement": {
+ "id": "0002-001-01"
+ }
+ },
+ {
+ "id": "years",
+ "value": 10,
+ "requirement": {
+ "id": "0003-001-01"
+ }
+ }
+ ]
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-06-07
+-
+
- Remove fields:
+
-
+
Award.requirementResponses
+Contract.requirementResponses
+Criterion.source
+RequirementResponse.relatedTenderer
+
+ - Replace
Criterion.relatesTocodelist field withCriterion.relatesToTendererboolean field.
+ - Remove
relatesTo.csvcodelist.
+ - Remove
responseSource.csvcodelist.
+
2023-04-18
+-
+
- Add
Criterion.relatedLotsfield.
+ - Remove unnecessary instructions from field descriptions. +
2020-06-04
+-
+
- Revisar palabras normativas y no normativas. +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente en https://github.com/open-contracting/standard/issues/223.
+2019-03-20
+-
+
- Establecer
"uniqueItems ": trueen los campos matriz y agregar"minLength": 1en los campos de cadena obligatorios.
+
2018-12-18
+-
+
Requirement.expectedValueyRequirementResponse.valuepermiten valores boolean.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/risk_allocation/index.html b/es/extensions/risk_allocation/index.html
new file mode 100644
index 000000000..4529e88a3
--- /dev/null
+++ b/es/extensions/risk_allocation/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Requisitos +
+ ++ Adds fields to express the Core Criterion and Core Evidence Vocabulary (CCCEV). +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Criterion +
+ +
+ The extension defines a new Criterion object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ El identificador para este criterio. Debe de ser único y no puede cambiar dentro del Proceso de Contratación Abierta del cual es parte (definido por un sólo ocid). Ver la guía de identificadores para mayores detalles. + + |
+ + string or integer + | +
+
+ title
+
+ |
+ + Título + | +
+ Un título para este criterio + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ A description of this criterion. + + |
+ + string + | +
+
+ relatesToTenderer
+
+ |
+ + Relates to tenderer + | +
+ The criterion judges, evaluates or assesses a tenderer. + + |
+ + boolean + | +
+
+ relatedItem
+
+ |
+ + Artículo relacionado + | +
+ The identifier of the item in the tender section to which this criterion applies. + + |
+ + string + | +
+
+ relatedLots
+
+ |
+ + Related lot(s) + | +
+ The identifiers of the lots to which this criterion applies. + + |
+ + array of strings + | +
+
+ requirementGroups
+
+ |
+ + Grupos de requisitos + | +
+ Una lista de grupos de requisitos para este Criterio. Un criterio se satisface cuando uno o más grupos de requisitos se cumplen. Un grupo de requisitos se cumple cuando todos los requerimientos del grupo se satisfacen. + + |
+ + array of RequirementGroup objects + | +
+ RequirementGroup +
+ +
+ The extension defines a new RequirementGroup object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ El identificador para este grupo de requisitos. Debe ser único y no puede cambiar dentro del Proceso de Contratación Abierta del que forma parte (definido por un solo ocid). Consulte la guía de identificadores para obtener más detalles. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ A description of this requirement group. + + |
+ + string + | +
+
+ requirements
+
+ |
+ + Requisitos + | +
+ Una lista de requisitos que deben ser cumplidos para que el grupo de requisitos se cumpla. + + |
+ + array of Requirement objects + | +
+ Requirement +
+ +
+ The extension defines a new Requirement object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador del requisito + | +
+ El identificador de este requisito. Debe ser único y no puede cambiar dentro del Proceso de Contratación Abierta de que forma parte (definido por un solo ocid). Consulte la guía de identificadores para obtener más detalles. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título de requisito + | +
+ El título de este requisito atómico. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción del requisito + | +
+ Una descripción de texto libre para este requisito atómico + + |
+ + string + | +
+
+ dataType
+
+ |
+ + Tipo de dato de Requisito + | +
+ The data type in which the response must be provided. + + |
+ + string from closed dataType codelist + | +
+
+ pattern
+
+ |
+ + Patrón de validación de respuesta + | +
+ A regular expression with which to validate the response. + + |
+ + string + | +
+
+ expectedValue
+
+ |
+ + Valor esperado + | +
+ The expected value of the requirement, when the response must be specific value. + + |
+ + string or integer or number or boolean + | +
+
+ minValue
+
+ |
+ + Valor mínimo + | +
+ The lower bound of the requirement, when the response must be within a certain range. + + |
+ + integer or number + | +
+
+ maxValue
+
+ |
+ + Valor máximo + | +
+ The upper bound of the requirement, when the response must be within a certain range. + + |
+ + integer or number + | +
+
+ period
+
+ |
+ + Periodo + | +
+ The period to which the requirement applies: for example, the tenderer's turnover in a given year. + + |
+ + Period object + | +
+ RequirementResponse +
+ +
+ The extension defines a new RequirementResponse object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador + | +
+ The unique identifier of this response in the context of the contracting process. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título + | +
+ The title of this response. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ The description of this response. + + |
+ + string + | +
+
+ value
+
+ |
+ + Valor + | +
+ The value of this response. + + |
+ + string or integer or number or boolean + | +
+
+ period
+
+ |
+ + Periodo + | +
+ The period to which the response applies. + + |
+ + Period object + | +
+
+ requirement
+
+ |
+ + Requisito relacionado + | +
+ A reference to the requirement to which the response applies. + + |
+ + RequirementReference object + | +
+ RequirementReference +
+ +
+ The extension defines a new RequirementReference object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID de requisito + | +
+ The identifier of the requirement to which the response applies. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título de requisito + | +
+ The title of the requirement to which the response applies. + + |
+ + string + | +
+ Bid +
+ +
+ The extension defines these fields in the Bid object from the Estadísticas y detalles de las ofertas extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ requirementResponses
+
+ |
+ + Respuestas de requisito + | +
+ The responses of this bid to the requirements. + + |
+ + array of RequirementResponse objects + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ criteria
+
+ |
+ + Criterios + | +
+ Criteria on which bids, tenderers, lots or items will be judged, evaluated or assessed. + + |
+ + array of Criterion objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/risk_allocation/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/risk_allocation/master/codelists/riskAllocation.csv b/es/extensions/risk_allocation/master/codelists/riskAllocation.csv
new file mode 100644
index 000000000..bc277cdef
--- /dev/null
+++ b/es/extensions/risk_allocation/master/codelists/riskAllocation.csv
@@ -0,0 +1,4 @@
+Código,Título,Descripción
+publicAuthority,Public authority,The risk is wholly or mostly retained by the public authority
+privateParty,Private party,The risk is wholly or mostly retained by the private party
+undefined,Undefined,The risk is not clearly assigned to a specific party to the contract. Further details can be provided in the notes field.
diff --git a/es/extensions/risk_allocation/master/codelists/riskCategory.csv b/es/extensions/risk_allocation/master/codelists/riskCategory.csv
new file mode 100644
index 000000000..b96e2dce6
--- /dev/null
+++ b/es/extensions/risk_allocation/master/codelists/riskCategory.csv
@@ -0,0 +1,17 @@
+Categoría,Código,Título,Descripción,Fuente
+designAndConstruction,landAvailability,Land availability and acquisition risk,Relates to the unavailability of land or site to construct the infrastructure at the time of contract signature,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+designAndConstruction,environmental,Environmental risk,"Environmental risks might be related to a number of environmental issues such as general contamination, pollution, water contamination, impact on the natural environment etc. An adverse assessment might lead to changes in design, leading to a direct impact on cost of infrastructure",https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+designAndConstruction,design,Design risks,Represents the possibility that design quality for the asset is not adequate to meet project requirements,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+designAndConstruction,construction,Construction risks,"Represents the possibility that during the construction Phase, the actual project costs or construction time exceeds the projected time and costs",https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+designAndConstruction,completion,Completion and commissioning,Refers to the failure to meet the construction outcome or finalization as prescribed,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+operating,revenue,Revenue risk,Refers to the risk of the revenue flows not being correctly assessed,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+operating,inflationAndFx,"Foreign exchange, inflation and indexation risk",Risk that changes in exchange rates or inflation adversely affect the project outcomes,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+operating,availabilityAndQuality,Availability and quality risk,Risk linked to availability and quality issues relating to performance requirements and performance target levels,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+operating,otherRevenue,Other revenue risk events,credit or counterparty risk; fraud/non-payment by users,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+finance,financeAvailability,Availability of finance,Represents the risk of financing not being available at commercial close or before construction starts,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+finance,refinancing,Refinancing risks,Risks relating to the downside of refinancing,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+other,changeInLaw,Changes in law,Risk that a change in general law or the sector regulatory framework adversely affect the project,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+other,forceMajeure,Force majeure,"Risk that external events beyond the control of the parties to the contract, such as natural disasters, wars, terrorism etc., affect the project",https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+other,earlyTermination,Early termination,Risk that compensation sum due to early termination might be insufficient to meet private party’s financial obligations or is less than expected,https://ppp-certification.com/ppp-certification-guide/58-introducing-main-project-risks-and-their-potential-allocation56
+other,compliance,Compliance risks,Risks deriving from the compliance or lack thereof of regulatory obligations related to the development of the project,
+other,all,All risks,All risks deriving from the project,
diff --git a/es/extensions/risk_allocation/master/extension.json b/es/extensions/risk_allocation/master/extension.json
new file mode 100644
index 000000000..095a540b1
--- /dev/null
+++ b/es/extensions/risk_allocation/master/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Risk Allocation",
+ "es": "Asignaci\u00f3n de Riesgo"
+ },
+ "description": {
+ "en": "For providing the risk allocations defined in a public private partnership's contract.",
+ "es": "Para proporcionar las asignaciones de riesgo definidas en un contrato de asociaci\u00f3n p\u00fablico-privada."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/risk_allocation/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "riskAllocation.csv",
+ "riskCategory.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/risk_allocation/master/index.html b/es/extensions/risk_allocation/master/index.html
new file mode 100644
index 000000000..c2f96d71f
--- /dev/null
+++ b/es/extensions/risk_allocation/master/index.html
@@ -0,0 +1,350 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Asignación de Riesgo +
+ ++ Para proporcionar las asignaciones de riesgo definidas en un contrato de asociación público-privada. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ riskAllocation.csv +
+ +
+ You can download the riskAllocation.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ publicAuthority
+
+ |
+ + Public authority + | +
+ The risk is wholly or mostly retained by the public authority + + |
+
+
+ privateParty
+
+ |
+ + Private party + | +
+ The risk is wholly or mostly retained by the private party + + |
+
+
+ undefined
+
+ |
+ + Undefined + | +
+ The risk is not clearly assigned to a specific party to the contract. Further details can be provided in the notes field. + + |
+
+ riskCategory.csv +
+ +
+ You can download the riskCategory.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ landAvailability
+
+ |
+ + Land availability and acquisition risk + | +
+ Relates to the unavailability of land or site to construct the infrastructure at the time of contract signature + +
|
+
+
+ environmental
+
+ |
+ + Environmental risk + | +
+ Environmental risks might be related to a number of environmental issues such as general contamination, pollution, water contamination, impact on the natural environment etc. An adverse assessment might lead to changes in design, leading to a direct impact on cost of infrastructure + +
|
+
+
+ design
+
+ |
+ + Design risks + | +
+ Represents the possibility that design quality for the asset is not adequate to meet project requirements + +
|
+
+
+ construction
+
+ |
+ + Construction risks + | +
+ Represents the possibility that during the construction Phase, the actual project costs or construction time exceeds the projected time and costs + +
|
+
+
+ completion
+
+ |
+ + Completion and commissioning + | +
+ Refers to the failure to meet the construction outcome or finalization as prescribed + +
|
+
+
+ revenue
+
+ |
+ + Revenue risk + | +
+ Refers to the risk of the revenue flows not being correctly assessed + +
|
+
+
+ inflationAndFx
+
+ |
+ + Foreign exchange, inflation and indexation risk + | +
+ Risk that changes in exchange rates or inflation adversely affect the project outcomes + +
|
+
+
+ availabilityAndQuality
+
+ |
+ + Availability and quality risk + | +
+ Risk linked to availability and quality issues relating to performance requirements and performance target levels + +
|
+
+
+ otherRevenue
+
+ |
+ + Other revenue risk events + | +
+ credit or counterparty risk; fraud/non-payment by users + +
|
+
+
+ financeAvailability
+
+ |
+ + Availability of finance + | +
+ Represents the risk of financing not being available at commercial close or before construction starts + +
|
+
+
+ refinancing
+
+ |
+ + Refinancing risks + | +
+ Risks relating to the downside of refinancing + +
|
+
+
+ changeInLaw
+
+ |
+ + Changes in law + | +
+ Risk that a change in general law or the sector regulatory framework adversely affect the project + +
|
+
+
+ forceMajeure
+
+ |
+ + Force majeure + | +
+ Risk that external events beyond the control of the parties to the contract, such as natural disasters, wars, terrorism etc., affect the project + +
|
+
+
+ earlyTermination
+
+ |
+ + Early termination + | +
+ Risk that compensation sum due to early termination might be insufficient to meet private party’s financial obligations or is less than expected + +
|
+
+
+ compliance
+
+ |
+ + Compliance risks + | +
+ Risks deriving from the compliance or lack thereof of regulatory obligations related to the development of the project + +
|
+
+
+ all
+
+ |
+ + All risks + | +
+ All risks deriving from the project + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/risk_allocation/master/release-schema.json b/es/extensions/risk_allocation/master/release-schema.json
new file mode 100644
index 000000000..562f31677
--- /dev/null
+++ b/es/extensions/risk_allocation/master/release-schema.json
@@ -0,0 +1,83 @@
+{
+ "definitions": {
+ "Risk": {
+ "title": "Riesgo",
+ "description": "Un riesgo relacionado al proyecto.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID de riesgo",
+ "description": "Un identificador local para este riesgo, \u00fanico en este bloque. Este campo se utiliza para mantener el monitoreo de revisiones m\u00faltiples de un riesgo a trav\u00e9s de la compilaci\u00f3n desde la entrega hasta el registro.",
+ "type": [
+ "string",
+ "integer"
+ ],
+ "minLength": 1
+ },
+ "category": {
+ "title": "Categor\u00eda de riesgo",
+ "description": "La categor\u00eda del riesgo, de la lista de c\u00f3digos riskCategory.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "riskCategory.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n de riesgo",
+ "description": "La descripci\u00f3n del riesgo.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "allocation": {
+ "title": "Asignaci\u00f3n de riesgos",
+ "description": "The party to the contract that retains the risk.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "riskAllocation.csv",
+ "openCodelist": false,
+ "enum": [
+ "publicAuthority",
+ "privateParty",
+ "undefined",
+ null
+ ]
+ },
+ "notes": {
+ "title": "Notas de Riesgo",
+ "description": "Notas adicionales sobre el riesgo, por ejemplo la justificaci\u00f3n de la asignaci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Contract": {
+ "properties": {
+ "riskAllocation": {
+ "title": "Asignaci\u00f3n de riesgos",
+ "description": "Informaci\u00f3n sobre la asignaci\u00f3n de los riesgos relacionados con el contrato.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Risk"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/risk_allocation/master/schema/index.html b/es/extensions/risk_allocation/master/schema/index.html
new file mode 100644
index 000000000..d91ab5bae
--- /dev/null
+++ b/es/extensions/risk_allocation/master/schema/index.html
@@ -0,0 +1,359 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Asignación de Riesgo +
+ ++ Para proporcionar las asignaciones de riesgo definidas en un contrato de asociación público-privada. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+El marco para la divulgación de APP exige información individual sobre la asignación de riesgos.
+La extensión de asignación de riesgos se utiliza para proporcionar datos estructurados sobre las asignaciones de riesgo definidas en un contrato de asociación público-privada, a través de una lista de contracts.riskAllocation.
La lista de códigos riskCategory.csv se basa en el programa de certificación APMG PPP. La columna Category (Categoría) de la lista de códigos indica la fase o el aspecto del proceso de contratación al que se aplica la categoría de riesgo.
Ejemplo
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "title": "Public Private Partnership Agreement",
+ "description": "Public-Private Partnership agreement entered into by and between telecoms promoter, together with national fibre infrastructure and the special purpose vehicle Mega Consortium Ltd",
+ "riskAllocation": [
+ {
+ "id": "1",
+ "category": "compliance",
+ "description": "Risks deriving from the compliance or lack thereof of regulatory obligations related to the development of the Project",
+ "allocation": "privateParty"
+ },
+ {
+ "id": "2",
+ "category": "construction",
+ "description": "Risks deriving from procurement or lack thereof of the necessary licenses and permits for the Project’s development",
+ "allocation": "privateParty"
+ },
+ {
+ "id": "3",
+ "category": "construction",
+ "description": "Risks arising from the procurement or lack thereof of rights of way required for the Project’s development",
+ "allocation": "privateParty"
+ }
+ ]
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-06-04
+-
+
- Revisar de las palabras normativas y no normativas. +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-03-20
+-
+
- Agregar
"minLength": 1en los campos de cadena obligatorios.
+
2018-05-08
+-
+
- Hacer que
Risk.idsea obligatorio para soportar el seguimiento de revisiones y fusión de listas
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/risk_allocation/v1.1/README.md b/es/extensions/risk_allocation/v1.1/README.md
new file mode 100644
index 000000000..0d07fcbe0
--- /dev/null
+++ b/es/extensions/risk_allocation/v1.1/README.md
@@ -0,0 +1,17 @@
+# Asignación de riesgos
+
+El [marco para la divulgación de APP](http://pubdocs.worldbank.org/en/773541448296707678/Disclosure-in-PPPs-Framework.pdf) exige información individual sobre la asignación de riesgos.
+
+La extensión de asignación de riesgos se utiliza para proporcionar datos estructurados sobre las asignaciones de riesgo definidas en un contrato de asociación público-privada.
+
+## Resumen
+
+Las asignaciones de riesgos se pueden representar utilizando una lista de [bloques de riesgo](../../../schema/reference/#organization) en el campo `riskAllocation` de la sección `contract` de una entrega de OCDS.
+
+La categoría de riesgo se puede representar utilizando el campo `risk/category` utilizando valores de la [lista de códigos de categoría de riesgo](../schema/codelists/#risk-category) basados en el APMG PPP Certification Program.
+
+La parte que conserva cada riesgo debe representarse utilizando el campo `risk/allocation`, utilizando valores de la [lista de códigos de asignación de riesgos](../schema/codelists/#risk-allocation).
+
+La descripción del riesgo debe proporcionarse como texto libre utilizando el campo `risk/description` y la mitigación del riesgo debe proporcionarse como texto libre utilizando el campo `risk/mitigation`.
+
+Se puede proporcionar información de texto libre adicional sobre el riesgo utilizando el campo `risk/notes`.
diff --git a/es/extensions/risk_allocation/v1.1/codelists/index.html b/es/extensions/risk_allocation/v1.1/codelists/index.html
new file mode 100644
index 000000000..75dc2a825
--- /dev/null
+++ b/es/extensions/risk_allocation/v1.1/codelists/index.html
@@ -0,0 +1,538 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Asignación de Riesgo +
+ ++ Para proporcionar las asignaciones de riesgo definidas en un contrato de asociación público-privada. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Risk +
+ +
+ The extension defines a new Risk object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID de riesgo + | +
+ Un identificador local para este riesgo, único en este bloque. Este campo se utiliza para mantener el monitoreo de revisiones múltiples de un riesgo a través de la compilación desde la entrega hasta el registro. + + |
+ + string or integer + | +
+
+ category
+
+ |
+ + Categoría de riesgo + | +
+ La categoría del riesgo, de la lista de códigos riskCategory. + + |
+ + string from open riskCategory codelist + | +
+
+ description
+
+ |
+ + Descripción de riesgo + | +
+ La descripción del riesgo. + + |
+ + string + | +
+
+ allocation
+
+ |
+ + Asignación de riesgos + | +
+ The party to the contract that retains the risk. + + |
+ + string from closed riskAllocation codelist + | +
+
+ notes
+
+ |
+ + Notas de Riesgo + | +
+ Notas adicionales sobre el riesgo, por ejemplo la justificación de la asignación. + + |
+ + string + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ riskAllocation
+
+ |
+ + Asignación de riesgos + | +
+ Información sobre la asignación de los riesgos relacionados con el contrato. + + |
+ + array of Risk objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/risk_allocation/v1.1/codelists/riskAllocation.csv b/es/extensions/risk_allocation/v1.1/codelists/riskAllocation.csv
new file mode 100644
index 000000000..8f1fe3822
--- /dev/null
+++ b/es/extensions/risk_allocation/v1.1/codelists/riskAllocation.csv
@@ -0,0 +1,4 @@
+Categoría,Código,Title_en,Description_en,Fuente
+,publicAuthority,Public authority,The risk is wholly or mostly retained by the public authority,
+,privateParty,Private party,The risk is wholly or mostly retained by the private party,
+,undefined,Undefined,The risk is not clearly assigned to a specific party. Further details can be provided in the notes field.,
diff --git a/es/extensions/risk_allocation/v1.1/codelists/riskCategory.csv b/es/extensions/risk_allocation/v1.1/codelists/riskCategory.csv
new file mode 100644
index 000000000..9c5717fa8
--- /dev/null
+++ b/es/extensions/risk_allocation/v1.1/codelists/riskCategory.csv
@@ -0,0 +1,13 @@
+Categoría,Código,Title_en,Description_en,Fuente
+,development,Development Risk,"Risks relating to the development phase, which involves the preparation and procurement of the project up to financial close, including invitation to tender and bidding; negotiation of the various project documents; and obtaining debt and equity funding.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,completion,Completion Risk,"The risk that the project is not completed in accordance with its initial specifications within the agreed timeframe. Completion risk covers: construction, testing and commissioning of the project.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,costIncrease,Cost Increase Risk,"The risk that the amount forecast for the cost of construction and operation of the project in the financial model will, for some reason, be surpassed. Cost increase risk includes: exchange rate risk, interest rate and refinancing risk, inflation, taxes, input price increase, construction cost increase, operation cost increase, cost of spare and replacement parts, decrease in off-take price, and coverage of cost overrun risk.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,performance,Performance Risk,"The risk that the project does not perform at the levels specified in the contract. This risk covers design and construction, operation, input supply, and offtake purchaser infrastructure.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,operation,Operation Risk,"Operation risk includes: the risk of defects in design, equipment or materials beyond the construction contractor’s defects liability period, the availability of labor and materials, changes in operating requirements, the cost of asset replacement and major maintenance, the availability of experienced management, the availability of working capital financing to cover short-term financing needs, the availability of locally sourced/cost-effective supplies and services, the availability of associated infrastructure and services, the program for operation and maintenance, as well as other costs subject to change over the period of the concession.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,market,Market Risk,Primary market risks that are likely to be encountered in a PPP project include: offtake (output) price and input cost risk.,"Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,political,Political Risk,"Political risk, such as events of war, rebellion, default or failure of public sector entities, change in law and delays by authorities.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,environmental,Environmental Risk,"Risk related to the liabilities and constraints generated by environmental requirements, and the cost of compliance to environmental laws and regulations.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,social,Social Risk,"Risk related to the project’s impact on the local communities, and the potential resistance from local interest groups that can delay project implementation, increase the cost of implementation and undermine project viability.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,credit,Credit Risk,"The risk that project participants are not able to assume their project obligations to ensure the financial viability of the project. This risk takes into consideration the financial stability, technical capacity, available resources, longevity, and managerial capacity of each such participant.","Private Sector Investment in Infrastructure: Project Finance, PPP Projects and Risk, J. Delmon, 2009"
+,compliance,Compliance risks,Risks deriving from the compliance or lack thereof of regulatory obligations related to the development of the project,
+,all,All risks,All risks deriving from the project,
diff --git a/es/extensions/risk_allocation/v1.1/extension.json b/es/extensions/risk_allocation/v1.1/extension.json
new file mode 100644
index 000000000..03cff8398
--- /dev/null
+++ b/es/extensions/risk_allocation/v1.1/extension.json
@@ -0,0 +1,14 @@
+{
+ "name": {
+ "en": "ocds-riskAllocation-extension",
+ "es": "ocds-riskAllocation-extension"
+ },
+ "description": {
+ "en": "Draft risk allocation extension for ppp extension",
+ "es": "Proyecto de extensi\u00f3n de asignaci\u00f3n de riesgos para la extensi\u00f3n de APP"
+ },
+ "documentationUrl": {},
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/es/extensions/risk_allocation/v1.1/index.html b/es/extensions/risk_allocation/v1.1/index.html
new file mode 100644
index 000000000..b4be9aa18
--- /dev/null
+++ b/es/extensions/risk_allocation/v1.1/index.html
@@ -0,0 +1,274 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Asignación de Riesgo +
+ ++ Para proporcionar las asignaciones de riesgo definidas en un contrato de asociación público-privada. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ riskAllocation.csv +
+ +
+ You can download the riskAllocation.csv file in English.
+
| + Código + | ++ Title_en + | ++ Description_en + | +
|---|---|---|
+
+ publicAuthority
+
+ |
+ + Public authority + | +
+ The risk is wholly or mostly retained by the public authority + + |
+
+
+ privateParty
+
+ |
+ + Private party + | +
+ The risk is wholly or mostly retained by the private party + + |
+
+
+ undefined
+
+ |
+ + Undefined + | +
+ The risk is not clearly assigned to a specific party. Further details can be provided in the notes field. + + |
+
+ riskCategory.csv +
+ +
+ You can download the riskCategory.csv file in English.
+
| + Código + | ++ Title_en + | ++ Description_en + | +
|---|---|---|
+
+ development
+
+ |
+ + Development Risk + | +
+ Risks relating to the development phase, which involves the preparation and procurement of the project up to financial close, including invitation to tender and bidding; negotiation of the various project documents; and obtaining debt and equity funding. + +
|
+
+
+ completion
+
+ |
+ + Completion Risk + | +
+ The risk that the project is not completed in accordance with its initial specifications within the agreed timeframe. Completion risk covers: construction, testing and commissioning of the project. + +
|
+
+
+ costIncrease
+
+ |
+ + Cost Increase Risk + | +
+ The risk that the amount forecast for the cost of construction and operation of the project in the financial model will, for some reason, be surpassed. Cost increase risk includes: exchange rate risk, interest rate and refinancing risk, inflation, taxes, input price increase, construction cost increase, operation cost increase, cost of spare and replacement parts, decrease in off-take price, and coverage of cost overrun risk. + +
|
+
+
+ performance
+
+ |
+ + Performance Risk + | +
+ The risk that the project does not perform at the levels specified in the contract. This risk covers design and construction, operation, input supply, and offtake purchaser infrastructure. + +
|
+
+
+ operation
+
+ |
+ + Operation Risk + | +
+ Operation risk includes: the risk of defects in design, equipment or materials beyond the construction contractor’s defects liability period, the availability of labor and materials, changes in operating requirements, the cost of asset replacement and major maintenance, the availability of experienced management, the availability of working capital financing to cover short-term financing needs, the availability of locally sourced/cost-effective supplies and services, the availability of associated infrastructure and services, the program for operation and maintenance, as well as other costs subject to change over the period of the concession. + +
|
+
+
+ market
+
+ |
+ + Market Risk + | +
+ Primary market risks that are likely to be encountered in a PPP project include: offtake (output) price and input cost risk. + +
|
+
+
+ political
+
+ |
+ + Political Risk + | +
+ Political risk, such as events of war, rebellion, default or failure of public sector entities, change in law and delays by authorities. + +
|
+
+
+ environmental
+
+ |
+ + Environmental Risk + | +
+ Risk related to the liabilities and constraints generated by environmental requirements, and the cost of compliance to environmental laws and regulations. + +
|
+
+
+ social
+
+ |
+ + Social Risk + | +
+ Risk related to the project’s impact on the local communities, and the potential resistance from local interest groups that can delay project implementation, increase the cost of implementation and undermine project viability. + +
|
+
+
+ credit
+
+ |
+ + Credit Risk + | +
+ The risk that project participants are not able to assume their project obligations to ensure the financial viability of the project. This risk takes into consideration the financial stability, technical capacity, available resources, longevity, and managerial capacity of each such participant. + +
|
+
+
+ compliance
+
+ |
+ + Compliance risks + | +
+ Risks deriving from the compliance or lack thereof of regulatory obligations related to the development of the project + + |
+
+
+ all
+
+ |
+ + All risks + | +
+ All risks deriving from the project + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/risk_allocation/v1.1/release-schema.json b/es/extensions/risk_allocation/v1.1/release-schema.json
new file mode 100644
index 000000000..581a1a65b
--- /dev/null
+++ b/es/extensions/risk_allocation/v1.1/release-schema.json
@@ -0,0 +1,68 @@
+{
+ "definitions": {
+ "Risk": {
+ "title": "Riesgo",
+ "description": "Un riesgo relacionado al proyecto.",
+ "type": "object",
+ "properties": {
+ "id": {
+ "title": "ID de riesgo",
+ "description": "Un identificador local para este riesgo, \u00fanico en este bloque. Este campo se utiliza para mantener el monitoreo de revisiones m\u00faltiples de un riesgo a trav\u00e9s de la compilaci\u00f3n desde la entrega hasta el registro.",
+ "type": [
+ "string",
+ "integer"
+ ]
+ },
+ "category": {
+ "title": "Categor\u00eda de riesgo",
+ "description": "Especificar la categor\u00eda del riesgo contra la lista de c\u00f3digos de categor\u00eda de riesgo.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "riskCategory.csv",
+ "openCodelist": true
+ },
+ "description": {
+ "title": "Descripci\u00f3n de riesgo",
+ "description": "Una descripci\u00f3n para este riesgo.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "allocation": {
+ "title": "Asignaci\u00f3n de riesgos",
+ "description": "La parte que absorbe el riesgo.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "riskAllocation.csv",
+ "openCodelist": false
+ },
+ "notes": {
+ "title": "Notas de Riesgo",
+ "description": "Notas adicionales sobre el riesgo, por ejemplo la justificaci\u00f3n para la asignaci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "riskAllocation": {
+ "title": "Asignaci\u00f3n de riesgos",
+ "description": "Informaci\u00f3n sobre la asignaci\u00f3n de los riesgos relacionados con el contrato.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Risk"
+ },
+ "uniqueItems": true
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/risk_allocation/v1.1/schema/index.html b/es/extensions/risk_allocation/v1.1/schema/index.html
new file mode 100644
index 000000000..0e928c009
--- /dev/null
+++ b/es/extensions/risk_allocation/v1.1/schema/index.html
@@ -0,0 +1,359 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Asignación de Riesgo +
+ ++ Para proporcionar las asignaciones de riesgo definidas en un contrato de asociación público-privada. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+El marco para la divulgación de APP exige información individual sobre la asignación de riesgos.
+La extensión de asignación de riesgos se utiliza para proporcionar datos estructurados sobre las asignaciones de riesgo definidas en un contrato de asociación público-privada.
+Resumen
+Las asignaciones de riesgos se pueden representar utilizando una lista de bloques de riesgo en el campo riskAllocation de la sección contract de una entrega de OCDS.
La categoría de riesgo se puede representar utilizando el campo risk/category utilizando valores de la lista de códigos de categoría de riesgo basados en el APMG PPP Certification Program.
La parte que conserva cada riesgo debe representarse utilizando el campo risk/allocation, utilizando valores de la lista de códigos de asignación de riesgos.
La descripción del riesgo debe proporcionarse como texto libre utilizando el campo risk/description y la mitigación del riesgo debe proporcionarse como texto libre utilizando el campo risk/mitigation.
Se puede proporcionar información de texto libre adicional sobre el riesgo utilizando el campo risk/notes.
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/secondStageDescription/index.html b/es/extensions/secondStageDescription/index.html
new file mode 100644
index 000000000..4a9a466a8
--- /dev/null
+++ b/es/extensions/secondStageDescription/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Asignación de Riesgo +
+ ++ Para proporcionar las asignaciones de riesgo definidas en un contrato de asociación público-privada. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Risk +
+ +
+ The extension defines a new Risk object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID de riesgo + | +
+ Un identificador local para este riesgo, único en este bloque. Este campo se utiliza para mantener el monitoreo de revisiones múltiples de un riesgo a través de la compilación desde la entrega hasta el registro. + + |
+ + string or integer + | +
+
+ category
+
+ |
+ + Categoría de riesgo + | +
+ Especificar la categoría del riesgo contra la lista de códigos de categoría de riesgo. + + |
+ + string from open riskCategory codelist + | +
+
+ description
+
+ |
+ + Descripción de riesgo + | +
+ Una descripción para este riesgo. + + |
+ + string + | +
+
+ allocation
+
+ |
+ + Asignación de riesgos + | +
+ La parte que absorbe el riesgo. + + |
+ + string from closed riskAllocation codelist + | +
+
+ notes
+
+ |
+ + Notas de Riesgo + | +
+ Notas adicionales sobre el riesgo, por ejemplo la justificación para la asignación. + + |
+ + string + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ riskAllocation
+
+ |
+ + Asignación de riesgos + | +
+ Información sobre la asignación de los riesgos relacionados con el contrato. + + |
+ + array of Risk objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/secondStageDescription/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/secondStageDescription/master/release-schema.json b/es/extensions/secondStageDescription/master/release-schema.json
new file mode 100644
index 000000000..fd27a9556
--- /dev/null
+++ b/es/extensions/secondStageDescription/master/release-schema.json
@@ -0,0 +1,71 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "secondStage": {
+ "title": "Segunda etapa",
+ "description": "Informaci\u00f3n acerca de la segunda etapa de un procedimiento de dos etapas (por ejemplo, un procedimiento restringido, un procedimiento competitivo con negociaci\u00f3n, un di\u00e1logo competitivo o una asociaci\u00f3n de innovaci\u00f3n).",
+ "$ref": "#/definitions/SecondStage"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "secondStage": {
+ "title": "Segunda etapa",
+ "description": "Informaci\u00f3n acerca de la segunda etapa de un procedimiento de dos etapas (por ejemplo, un procedimiento restringido, un procedimiento competitivo con negociaci\u00f3n, un di\u00e1logo competitivo o una asociaci\u00f3n de innovaci\u00f3n).",
+ "$ref": "#/definitions/SecondStage"
+ }
+ }
+ },
+ "SecondStage": {
+ "title": "Segunda etapa",
+ "description": "Informaci\u00f3n acerca de la segunda etapa de un procedimiento de dos etapas (por ejemplo, un procedimiento restringido, un procedimiento competitivo con negociaci\u00f3n, un di\u00e1logo competitivo o una asociaci\u00f3n de innovaci\u00f3n).",
+ "type": "object",
+ "properties": {
+ "minimumCandidates": {
+ "title": "N\u00famero m\u00ednimo de candidatos",
+ "description": "El n\u00famero m\u00ednimo de candidatos a invitar a la segunda etapa del procedimiento. Si hay un l\u00edmite exacto en el n\u00famero de candidatos, establecer `minimumCandidates` y `maximumCandidates` en el mismo n\u00famero.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "maximumCandidates": {
+ "title": "N\u00famero m\u00e1ximo de candidatos",
+ "description": "El n\u00famero m\u00e1ximo de candidatos que se invitar\u00e1 a la segunda etapa del procedimiento. Si hay un l\u00edmite exacto en el n\u00famero de candidatos, establecer `minimumCandidates` y `maximumCandidates` en el mismo n\u00famero.",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "successiveReduction": {
+ "title": "Reducci\u00f3n sucesiva",
+ "description": "El procedimiento se llevar\u00e1 a cabo en etapas sucesivas. En cada etapa, algunos participantes pueden ser eliminados.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "noNegotiationNecessary": {
+ "title": "No es necesaria la negociaci\u00f3n",
+ "description": "El comprador o la entidad contratante se reserva el derecho de adjudicar el contrato sobre la base de las ofertas iniciales sin m\u00e1s negociaciones.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "invitationDate": {
+ "title": "Fecha de la invitaci\u00f3n",
+ "description": "La fecha estimada de env\u00edo de las invitaciones para participar o presentar ofertas.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/secondStageDescription/master/schema/index.html b/es/extensions/secondStageDescription/master/schema/index.html
new file mode 100644
index 000000000..a17b0c9f1
--- /dev/null
+++ b/es/extensions/secondStageDescription/master/schema/index.html
@@ -0,0 +1,401 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Descripción de la segunda etapa +
+ ++ Agregar un objeto de segunda etapa a los objetos de licitación y lote, para describir la segunda etapa de un procedimiento de dos etapas. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar un objeto de segunda etapa a los objetos de licitación y lote, para describir la segunda etapa de un procedimiento de dos etapas. En particular, agregar dos campos para describir los límites en el número de candidatos a ser invitados.
+Guía
+Si hay un límite exacto en el número de candidatos, establecer minimumCandidates y maximumCandidates` al mismo número.
Si se establece maximumCandidates, utilizar la extensión de criterios de selección (TBD) para describir cómo se utilizarán los criterios de selección para seleccionar candidatos que serán invitados a la segunda etapa.
Contexto legal
+In the European Union, this extension's fields correspond to eForms BG-709 (Second Stage). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "secondStage": {
+ "minimumCandidates": 5,
+ "maximumCandidates": 50,
+ "successiveReduction": true,
+ "noNegotiationNecessary": false,
+ "invitationDate": "2019-08-16T10:30:00Z"
+ }
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), en [pull requests] (https://github.com/open-contracting-extensions/ocds_secondStageDescription_extension/pulls?q=is%3Apr+is%3Aclosed) y en https://github.com/open-contracting/standard/issues/695.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/selectionCriteria/index.html b/es/extensions/selectionCriteria/index.html
new file mode 100644
index 000000000..6ac797391
--- /dev/null
+++ b/es/extensions/selectionCriteria/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Descripción de la segunda etapa +
+ ++ Agregar un objeto de segunda etapa a los objetos de licitación y lote, para describir la segunda etapa de un procedimiento de dos etapas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ secondStage
+
+ |
+ + Segunda etapa + | +
+ Información acerca de la segunda etapa de un procedimiento de dos etapas (por ejemplo, un procedimiento restringido, un procedimiento competitivo con negociación, un diálogo competitivo o una asociación de innovación). + + |
+ + SecondStage object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ secondStage
+
+ |
+ + Segunda etapa + | +
+ Información acerca de la segunda etapa de un procedimiento de dos etapas (por ejemplo, un procedimiento restringido, un procedimiento competitivo con negociación, un diálogo competitivo o una asociación de innovación). + + |
+ + SecondStage object + | +
+ SecondStage +
+ +
+ The extension defines a new SecondStage object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ minimumCandidates
+
+ |
+ + Número mínimo de candidatos + | +
+ El número mínimo de candidatos a invitar a la segunda etapa del procedimiento. Si hay un límite exacto en el número de candidatos, establecer |
+ + number + | +
+
+ maximumCandidates
+
+ |
+ + Número máximo de candidatos + | +
+ El número máximo de candidatos que se invitará a la segunda etapa del procedimiento. Si hay un límite exacto en el número de candidatos, establecer |
+ + number + | +
+
+ successiveReduction
+
+ |
+ + Reducción sucesiva + | +
+ El procedimiento se llevará a cabo en etapas sucesivas. En cada etapa, algunos participantes pueden ser eliminados. + + |
+ + boolean + | +
+
+ noNegotiationNecessary
+
+ |
+ + No es necesaria la negociación + | +
+ El comprador o la entidad contratante se reserva el derecho de adjudicar el contrato sobre la base de las ofertas iniciales sin más negociaciones. + + |
+ + boolean + | +
+
+ invitationDate
+
+ |
+ + Fecha de la invitación + | +
+ La fecha estimada de envío de las invitaciones para participar o presentar ofertas. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/selectionCriteria/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/selectionCriteria/master/codelists/selectionCriterionType.csv b/es/extensions/selectionCriteria/master/codelists/selectionCriterionType.csv
new file mode 100644
index 000000000..3fb97d0d1
--- /dev/null
+++ b/es/extensions/selectionCriteria/master/codelists/selectionCriterionType.csv
@@ -0,0 +1,5 @@
+Código,Título,Descripción
+economic,Economic,The criterion relates to the economic or financial standing of the tenderer.
+technical,Technical,The criterion relates to the technical or professional ability of the tenderer.
+suitability,Suitability,The criterion relates to the suitability of the tenderer (e.g. enrolment in trade register or membership of professional organization).
+other,Other,The criterion relates to other aspects of the tenderer.
diff --git a/es/extensions/selectionCriteria/master/extension.json b/es/extensions/selectionCriteria/master/extension.json
new file mode 100644
index 000000000..5e9c63d23
--- /dev/null
+++ b/es/extensions/selectionCriteria/master/extension.json
@@ -0,0 +1,33 @@
+{
+ "name": {
+ "en": "Selection Criteria",
+ "es": "Criterios de Selecci\u00f3n"
+ },
+ "description": {
+ "en": "Adds an object to describe the conditions for participation in a contracting process.",
+ "es": "Agrega un objeto para describir las condiciones de participaci\u00f3n en un proceso de contrataci\u00f3n."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/selectionCriteria/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "selectionCriterionType.csv",
+ "appliesTo.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "dependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_awardCriteria_extension/master/extension.json"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/es/extensions/selectionCriteria/master/index.html b/es/extensions/selectionCriteria/master/index.html
new file mode 100644
index 000000000..d7e7d5dae
--- /dev/null
+++ b/es/extensions/selectionCriteria/master/index.html
@@ -0,0 +1,378 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Criterios de Selección +
+ ++ Agrega un objeto para describir las condiciones de participación en un proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ appliesTo.csv +
+ +
+ You can download the appliesTo.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ supplier
+
+ |
+ + Supplier + | +
+ The selection criterion applies to the suppliers. + + |
+
+
+ subcontractor
+
+ |
+ + Subcontractor + | +
+ The selection criterion applies to the subcontractors. + + |
+
+ selectionCriterionType.csv +
+ +
+ You can download the selectionCriterionType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ economic
+
+ |
+ + Economic + | +
+ The criterion relates to the economic or financial standing of the tenderer. + + |
+
+
+ technical
+
+ |
+ + Technical + | +
+ The criterion relates to the technical or professional ability of the tenderer. + + |
+
+
+ suitability
+
+ |
+ + Suitability + | +
+ The criterion relates to the suitability of the tenderer (e.g. enrolment in trade register or membership of professional organization). + + |
+
+
+ other
+
+ |
+ + Other + | +
+ The criterion relates to other aspects of the tenderer. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/selectionCriteria/master/release-schema.json b/es/extensions/selectionCriteria/master/release-schema.json
new file mode 100644
index 000000000..0b9efa302
--- /dev/null
+++ b/es/extensions/selectionCriteria/master/release-schema.json
@@ -0,0 +1,131 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "selectionCriteria": {
+ "title": "Criterios de selecci\u00f3n",
+ "description": "Informaci\u00f3n sobre las condiciones de participaci\u00f3n en un procedimiento.",
+ "$ref": "#/definitions/SelectionCriteria"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "selectionCriteria": {
+ "title": "Criterios de selecci\u00f3n",
+ "description": "Informaci\u00f3n sobre las condiciones para participar en un lote.",
+ "$ref": "#/definitions/SelectionCriteria"
+ }
+ }
+ },
+ "SelectionCriteria": {
+ "title": "Criterios de selecci\u00f3n",
+ "description": "Informaci\u00f3n sobre condiciones de participaci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "criteria": {
+ "title": "Criterios de selecci\u00f3n",
+ "description": "Los criterios de selecci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/SelectionCriterion"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "La descripci\u00f3n de los criterios utilizados para seleccionar los operadores econ\u00f3micos que podr\u00e1n ofertar.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "SelectionCriterion": {
+ "title": "Criterio de selecci\u00f3n",
+ "description": "Informaci\u00f3n sobre el criterio de selecci\u00f3n.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Tipo",
+ "description": "El tipo de criterio.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "selectionCriterionType.csv",
+ "openCodelist": false,
+ "enum": [
+ "technical",
+ "economic",
+ "suitability",
+ "other",
+ null
+ ]
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "La descripci\u00f3n del criterio.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "minimum": {
+ "title": "Valor o nivel m\u00ednimo",
+ "description": "El valor m\u00ednimo o nivel de cumplimiento que un candidato debe alcanzar para participar.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "appliesTo": {
+ "title": "Se aplica a",
+ "description": "Si el criterio se aplica a proveedores, subcontratistas o ambos.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "enum": [
+ "supplier",
+ "subcontractor"
+ ]
+ },
+ "codelist": "appliesTo.csv",
+ "openCodelist": false,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "forReduction": {
+ "title": "For reduction?",
+ "description": "Whether the criterion is used to select the potential suppliers to be invited to the second stage of the contracting process, if the number of invitations is limited.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "numbers": {
+ "title": "Numbers",
+ "description": "Numbers linked to the criterion.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/CriterionNumber"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/selectionCriteria/master/schema/index.html b/es/extensions/selectionCriteria/master/schema/index.html
new file mode 100644
index 000000000..c126acfab
--- /dev/null
+++ b/es/extensions/selectionCriteria/master/schema/index.html
@@ -0,0 +1,491 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Criterios de Selección +
+ ++ Agrega un objeto para describir las condiciones de participación en un proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar un objeto para describir los criterios para calificar a los candidatos a participar en un proceso de contratación.
+This extension must be used with the Award criteria breakdown extension.
+If your data closely follows the Core Criterion and Core Evidence Vocabulary (CCCEV), consider the Requirements extension.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Contexto legal
+In the European Union, this extension's fields correspond to eForms BG-702 (Selection Criteria) and BG-72 (Selection Criteria Second Stage Invite Number). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplos
+Tender
+Potential suppliers and subcontractors must demonstrate a minimum of 10 years experience on similar projects.
+{
+ "tender": {
+ "selectionCriteria": {
+ "criteria": [
+ {
+ "description": "Minimum number of years of experience on similar projects",
+ "minimum": "10",
+ "type": "technical",
+ "appliesTo": [
+ "supplier",
+ "subcontractor"
+ ]
+ }
+ ]
+ }
+ }
+}
+Lot
+A tender with a single lot where the selection criterion only applies for selecting candidates to be invited to the second stage of the procedure. The candidates will be selected only if the rate of their turnover over the value of the contract is at least 2.
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "LOT-0001",
+ "selectionCriteria": {
+ "criteria": [
+ {
+ "description": "Turnover over contract value rate",
+ "type": "economic",
+ "forReduction": true,
+ "numbers": [
+ {
+ "number": 2,
+ "threshold": "minimumScore"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-04-05
+-
+
- Add
forReductionandnumbersfields to theSelectionCriterionobject. Thenumbersfield reuses theCriterionNumberdefinition from the Award criteria breakdown extension.
+
2020-07-13
+-
+
- Add
appliesTofield.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues) y en pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/shareholders/index.html b/es/extensions/shareholders/index.html
new file mode 100644
index 000000000..e173d7c5e
--- /dev/null
+++ b/es/extensions/shareholders/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Criterios de Selección +
+ ++ Agrega un objeto para describir las condiciones de participación en un proceso de contratación. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ selectionCriteria
+
+ |
+ + Criterios de selección + | +
+ Información sobre las condiciones de participación en un procedimiento. + + |
+ + SelectionCriteria object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ selectionCriteria
+
+ |
+ + Criterios de selección + | +
+ Información sobre las condiciones para participar en un lote. + + |
+ + SelectionCriteria object + | +
+ SelectionCriteria +
+ +
+ The extension defines a new SelectionCriteria object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ criteria
+
+ |
+ + Criterios de selección + | +
+ Los criterios de selección. + + |
+ + array of SelectionCriterion objects + | +
+
+ description
+
+ |
+ + Descripción + | +
+ La descripción de los criterios utilizados para seleccionar los operadores económicos que podrán ofertar. + + |
+ + string + | +
+ SelectionCriterion +
+ +
+ The extension defines a new SelectionCriterion object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Tipo + | +
+ El tipo de criterio. + + |
+ + string from closed selectionCriterionType codelist + | +
+
+ description
+
+ |
+ + Descripción + | +
+ La descripción del criterio. + + |
+ + string + | +
+
+ minimum
+
+ |
+ + Valor o nivel mínimo + | +
+ El valor mínimo o nivel de cumplimiento que un candidato debe alcanzar para participar. + + |
+ + string + | +
+
+ appliesTo
+
+ |
+ + Se aplica a + | +
+ Si el criterio se aplica a proveedores, subcontratistas o ambos. + + |
+ + array of strings from closed appliesTo codelist + | +
+
+ forReduction
+
+ |
+ + For reduction? + | +
+ Whether the criterion is used to select the potential suppliers to be invited to the second stage of the contracting process, if the number of invitations is limited. + + |
+ + boolean + | +
+
+ numbers
+
+ |
+ + Numbers + | +
+ Numbers linked to the criterion. + + |
+ + array of CriterionNumber objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/shareholders/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/shareholders/master/codelists/votingRights.csv b/es/extensions/shareholders/master/codelists/votingRights.csv
new file mode 100644
index 000000000..e70b0ab75
--- /dev/null
+++ b/es/extensions/shareholders/master/codelists/votingRights.csv
@@ -0,0 +1,6 @@
+Código,Título,Descripción
+ordinary,Ordinary voting rights,The shareholder is entitled to a single vote per share in all circumstances
+none,No voting rights,The shareholder is not entitled to vote under any circumstances
+restricted,Restricted voting rights,The shareholder is entitled to vote in specific circumstances only
+additional,Additional voting rights,The shareholder is entitled to more than one vote per share in all circumstances
+enhanced,Enhanced voting rights,The shareholder is entitled to more than one vote per share in specific circumstances only
diff --git a/es/extensions/shareholders/master/extension.json b/es/extensions/shareholders/master/extension.json
new file mode 100644
index 000000000..15f5b7912
--- /dev/null
+++ b/es/extensions/shareholders/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Shareholders",
+ "es": "Accionistas"
+ },
+ "description": {
+ "en": "Adds company ownership fields to the organization object used in the parties array.",
+ "es": "Agrega campos de propiedad de la empresa al objeto de organizaci\u00f3n utilizado en la lista de partes."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/shareholders/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "votingRights.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/shareholders/master/index.html b/es/extensions/shareholders/master/index.html
new file mode 100644
index 000000000..c8a056713
--- /dev/null
+++ b/es/extensions/shareholders/master/index.html
@@ -0,0 +1,364 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Accionistas +
+ ++ Agrega campos de propiedad de la empresa al objeto de organización utilizado en la lista de partes. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ votingRights.csv +
+ +
+ You can download the votingRights.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ ordinary
+
+ |
+ + Ordinary voting rights + | +
+ The shareholder is entitled to a single vote per share in all circumstances + + |
+
+
+ none
+
+ |
+ + No voting rights + | +
+ The shareholder is not entitled to vote under any circumstances + + |
+
+
+ restricted
+
+ |
+ + Restricted voting rights + | +
+ The shareholder is entitled to vote in specific circumstances only + + |
+
+
+ additional
+
+ |
+ + Additional voting rights + | +
+ The shareholder is entitled to more than one vote per share in all circumstances + + |
+
+
+ enhanced
+
+ |
+ + Enhanced voting rights + | +
+ The shareholder is entitled to more than one vote per share in specific circumstances only + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/shareholders/master/release-schema.json b/es/extensions/shareholders/master/release-schema.json
new file mode 100644
index 000000000..c359c7e9b
--- /dev/null
+++ b/es/extensions/shareholders/master/release-schema.json
@@ -0,0 +1,86 @@
+{
+ "definitions": {
+ "Shareholder": {
+ "title": "Participaci\u00f3n",
+ "description": "A shareholding in an organization.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "A local identifier for this shareholding, unique within this array.",
+ "type": "string",
+ "minLength": 1
+ },
+ "shareholder": {
+ "title": "Accionista",
+ "description": "The organization holding the share.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "shareholding": {
+ "title": "Participaci\u00f3n",
+ "description": "The percentage of the organization's shares held by the shareholder, expressed as a decimal between 0 and 1.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "minimum": 0,
+ "maximum": 1
+ },
+ "votingRights": {
+ "title": "Voting rights",
+ "description": "The type of voting rights associated with the shareholder's shares.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "votingRights.csv",
+ "openCodelist": false,
+ "enum": [
+ "ordinary",
+ "none",
+ "restricted",
+ "additional",
+ "enhanced",
+ null
+ ]
+ },
+ "votingRightsDetails": {
+ "title": "Voting rights details",
+ "description": "Detailed information about the voting rights associated with the shareholder's shares: for example, when the shareholder voting rights are restricted, additional or enhanced.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "notes": {
+ "title": "Notes",
+ "description": "Additional notes on the shareholding or shareholder: for example, details on any caps on equity transfer, or lock-in arrangements, applicable to the shareholder.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Organization": {
+ "properties": {
+ "shareholders": {
+ "title": "Shareholdings",
+ "description": "Shareholdings in the organization: used to provide company ownership information for firms, primarily in the case of large and complex contracts, like public private partnerships, that require disclosure of this information by bidders or suppliers.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Shareholder"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/shareholders/master/schema/index.html b/es/extensions/shareholders/master/schema/index.html
new file mode 100644
index 000000000..630b48ca0
--- /dev/null
+++ b/es/extensions/shareholders/master/schema/index.html
@@ -0,0 +1,376 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Accionistas +
+ ++ Agrega campos de propiedad de la empresa al objeto de organización utilizado en la lista de partes. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds company ownership fields to the organization object used in the parties array.
+For example, when bidding in Public Private Partnerships, companies can be required to disclose their ownership information. After a contract is signed and during project implementation, the ownership information of the Special Purpose Vehicle (SPV) that is operating the contract might need to be updated.
+Since each owner mentioned in the shareholders array should have a corresponding entry in the parties array, it is possible to use this extension to describe multiple levels of corporate ownership.
Ejemplo
+{
+ "parties": [
+ {
+ "id": "MEGA",
+ "name": "Mega Consortium",
+ "shareholders": [
+ {
+ "id": "1",
+ "shareholder": {
+ "id": "AHL",
+ "name": "Alpha Holdings Ltd"
+ },
+ "shareholding": 0.67,
+ "votingRights": "additional",
+ "votingRightsDetails": "Alpha Holdings Ltd. is entitled to 5 votes per share.",
+ "notes": "Alpha Holdings Ltd. must maintain a minimum shareholding of 30% in the project company until 10 years from the date of commissioning have elapsed."
+ },
+ {
+ "id": "2",
+ "shareholder": {
+ "id": "BET",
+ "name": "Beta Investment Company Ltd"
+ },
+ "shareholding": 0.33,
+ "votingRights": "ordinary"
+ }
+ ]
+ },
+ {
+ "id": "BET",
+ "name": "Beta Investment Company Ltd"
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2021-05-24
+-
+
- Eliminar
Organization.beneficialOwnership.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-03-20
+-
+
- Agregar
"minLength": 1en los campos de cadena obligatorios.
+ - Hacer
Organization.beneficialOwnershipno nulo (deshacer cambio anterior).
+
2018-05-08
+-
+
- Hacer
Shareholder.idobligatorio para soportar el seguimiento de revisiones y fusión de listas
+
2018-01-29
+-
+
- Hacer que
Organization.beneficialOwnershippueda ser nulo.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/shareholders/v1.1/README.md b/es/extensions/shareholders/v1.1/README.md
new file mode 100644
index 000000000..26bdf6962
--- /dev/null
+++ b/es/extensions/shareholders/v1.1/README.md
@@ -0,0 +1,13 @@
+# Detalles del accionista y de la propiedad
+
+La extensión de accionista se puede utilizar para proporcionar detalles de los propietarios de las partes involucradas en un proceso de contratación.
+
+Por ejemplo, en los procesos de Asociaciones Público-Privadas, a menudo se requiere que las compañías divulguen información sobre sus estructuras de propiedad al licitar y cuando se adjudique el contrato, es necesario mantener información sobre la propiedad de una Sociedad con Fines Específicos (SPV) actualizada durante la ejecución del proyecto.
+
+Debido a que cada propietario mencionado en la matriz de accionistas también debe tener una entrada en la matriz de 'parties', es posible utilizar esta extensión para crear información sobre las redes de propiedad corporativa involucrados en un proceso de contratación.
+
+## Propiedad beneficiaria
+
+Esta extensión también incluye una entrada 'stub' para registrar información de propiedad beneficiaria contra una parte.
+
+En la actualidad, esto incluye espacio para la descripción en texto libre de las estructuras de propiedad y control, pero podría ampliarse con información estructurada sobre la propiedad efectiva basada en el borrador [Beneficial Ownership Data Standard](https://github.com/openownership/data-standard).
diff --git a/es/extensions/shareholders/v1.1/codelists/index.html b/es/extensions/shareholders/v1.1/codelists/index.html
new file mode 100644
index 000000000..fec2fb043
--- /dev/null
+++ b/es/extensions/shareholders/v1.1/codelists/index.html
@@ -0,0 +1,286 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Accionistas +
+ ++ Agrega campos de propiedad de la empresa al objeto de organización utilizado en la lista de partes. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Shareholder +
+ +
+ The extension defines a new Shareholder object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ A local identifier for this shareholding, unique within this array. + + |
+ + string + | +
+
+ shareholder
+
+ |
+ + Accionista + | +
+ The organization holding the share. + + |
+ + OrganizationReference object + | +
+
+ shareholding
+
+ |
+ + Participación + | +
+ The percentage of the organization's shares held by the shareholder, expressed as a decimal between 0 and 1. + + |
+ + number + | +
+
+ votingRights
+
+ |
+ + Voting rights + | +
+ The type of voting rights associated with the shareholder's shares. + + |
+ + string from closed votingRights codelist + | +
+
+ votingRightsDetails
+
+ |
+ + Voting rights details + | +
+ Detailed information about the voting rights associated with the shareholder's shares: for example, when the shareholder voting rights are restricted, additional or enhanced. + + |
+ + string + | +
+
+ notes
+
+ |
+ + Notes + | +
+ Additional notes on the shareholding or shareholder: for example, details on any caps on equity transfer, or lock-in arrangements, applicable to the shareholder. + + |
+ + string + | +
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ shareholders
+
+ |
+ + Shareholdings + | +
+ Shareholdings in the organization: used to provide company ownership information for firms, primarily in the case of large and complex contracts, like public private partnerships, that require disclosure of this information by bidders or suppliers. + + |
+ + array of Shareholder objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/shareholders/v1.1/codelists/votingRights.csv b/es/extensions/shareholders/v1.1/codelists/votingRights.csv
new file mode 100644
index 000000000..4339574c2
--- /dev/null
+++ b/es/extensions/shareholders/v1.1/codelists/votingRights.csv
@@ -0,0 +1,6 @@
+Categoría,Código,Title_en,Description_en,Fuente
+,ordinary,Ordinary voting rights,The shareholder is entitled to a single vote per share in all circumstances,
+,none,No voting rights,The shareholder is not entitled to vote under any circumstances,
+,restricted,Restricted voting rights,The shareholder is entitled to vote in specific circumstances only,
+,additional,Additional voting rights,The shareholder is entitled to more than one vote per share in all circumstances,
+,enhanced,Enhanced voting rights,The shareholder is entitled to more than one vote per share in specific circumstances only,
diff --git a/es/extensions/shareholders/v1.1/extension.json b/es/extensions/shareholders/v1.1/extension.json
new file mode 100644
index 000000000..3403523b7
--- /dev/null
+++ b/es/extensions/shareholders/v1.1/extension.json
@@ -0,0 +1,14 @@
+{
+ "name": {
+ "en": "ocds-shareholders-extension",
+ "es": "ocds-shareholders-extension"
+ },
+ "description": {
+ "en": "The shareholders extension can be used to attach company ownership details to each party in the parties array.",
+ "es": "La extensi\u00f3n de las partes se puede utilizar para adjuntar los detalles de propiedad de la compa\u00f1\u00eda a cada parte en la matriz de partes."
+ },
+ "documentationUrl": {},
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/es/extensions/shareholders/v1.1/index.html b/es/extensions/shareholders/v1.1/index.html
new file mode 100644
index 000000000..834516172
--- /dev/null
+++ b/es/extensions/shareholders/v1.1/index.html
@@ -0,0 +1,272 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Accionistas +
+ ++ Agrega campos de propiedad de la empresa al objeto de organización utilizado en la lista de partes. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ votingRights.csv +
+ +
+ You can download the votingRights.csv file in English.
+
| + Código + | ++ Title_en + | ++ Description_en + | +
|---|---|---|
+
+ ordinary
+
+ |
+ + Ordinary voting rights + | +
+ The shareholder is entitled to a single vote per share in all circumstances + + |
+
+
+ none
+
+ |
+ + No voting rights + | +
+ The shareholder is not entitled to vote under any circumstances + + |
+
+
+ restricted
+
+ |
+ + Restricted voting rights + | +
+ The shareholder is entitled to vote in specific circumstances only + + |
+
+
+ additional
+
+ |
+ + Additional voting rights + | +
+ The shareholder is entitled to more than one vote per share in all circumstances + + |
+
+
+ enhanced
+
+ |
+ + Enhanced voting rights + | +
+ The shareholder is entitled to more than one vote per share in specific circumstances only + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/shareholders/v1.1/release-schema.json b/es/extensions/shareholders/v1.1/release-schema.json
new file mode 100644
index 000000000..1ad7e461a
--- /dev/null
+++ b/es/extensions/shareholders/v1.1/release-schema.json
@@ -0,0 +1,84 @@
+{
+ "definitions": {
+ "Shareholder": {
+ "type": "object",
+ "title": "Accionista",
+ "description": "Un accionista en una organizaci\u00f3n.",
+ "properties": {
+ "id": {
+ "title": "ID del Accionista",
+ "description": "Un identificador local para este accionista, \u00fanico dentro de este bloque. Este campo se utiliza para realizar un seguimiento de las revisiones m\u00faltiples de un accionista a trav\u00e9s de la compilaci\u00f3n del mecanismo de entrega a registro.",
+ "type": [
+ "string"
+ ]
+ },
+ "shareholder": {
+ "title": "Referencia de la organizaci\u00f3n de accionistas.",
+ "description": "Una referencia de la organizaci\u00f3n se\u00f1alando la entrada en la secci\u00f3n de partes de la organizaci\u00f3n accionaria.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "shareholding": {
+ "title": "Participaci\u00f3n",
+ "description": "El porcentaje de acciones que posee el accionista, expresado como un valor decimal entre 0 y 1.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "minimum": 0,
+ "maximum": 1
+ },
+ "votingRights": {
+ "title": "Derechos de voto de los accionistas",
+ "description": "Especifica el tipo de derechos de voto asociado a las acciones que posee el accionista en contra de la [lista de c\u00f3digos de derechos de voto](http://standard.open-contracting.org/latest/en/schema/codelists/#voting-rights).",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "votingRights.csv",
+ "openCodelist": false
+ },
+ "votingRightsDetails": {
+ "title": "Detalles de los derechos de voto de los accionistas",
+ "description": "Informaci\u00f3n detallada sobre los derechos de voto del accionista. Este campo debe completarse cuando los derechos de voto de los accionistas son restringidos, adicionales o mejorados.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "notes": {
+ "title": "Notas sobre los accionistas",
+ "description": "Notas adicionales sobre este accionista. Este campo debe usarse para proporcionar detalles sobre los l\u00edmites m\u00e1ximos en la transferencia de capital, o acuerdos de bloqueo, aplicables a este accionista.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Organization": {
+ "properties": {
+ "shareholders": {
+ "title": "Accionistas de la organizaci\u00f3n",
+ "description": "Una lista de los accionistas de la organizaci\u00f3n: se utiliza para proporcionar informaci\u00f3n sobre la propiedad de la empresa para las sociedades, principalmente en el caso de contratos grandes y complejos, o Sociedades P\u00fablicas Privadas, que requieren la divulgaci\u00f3n de esta informaci\u00f3n para ciertos licitadores o adjudicatarios.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Shareholder"
+ },
+ "uniqueItems": true
+ },
+ "beneficialOwnership": {
+ "type": "object",
+ "title": "Propiedad beneficiaria ",
+ "description": "Esta secci\u00f3n puede usarse para registrar informaci\u00f3n concerniente a individuos u organizaciones con intereses de propiedad o control efectivas en esta parte. Cuando se dispone de datos estructurados, esta secci\u00f3n puede ampliarse mediante la incorporaci\u00f3n o vinculaci\u00f3n a la informaci\u00f3n modelada utilizando el [Est\u00e1ndar de Datos de Propiedad Efectiva (BODS)] (https://github.com/openownership/data-standard).",
+ "properties": {
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una descripci\u00f3n en texto libre de la propiedad efectiva o los acuerdos de control.",
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/shareholders/v1.1/schema/index.html b/es/extensions/shareholders/v1.1/schema/index.html
new file mode 100644
index 000000000..f6e2def2b
--- /dev/null
+++ b/es/extensions/shareholders/v1.1/schema/index.html
@@ -0,0 +1,410 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Accionistas +
+ ++ Agrega campos de propiedad de la empresa al objeto de organización utilizado en la lista de partes. +
+
+
+
+
+
+
+
+
+
+ + Documentation +
+La extensión de accionista se puede utilizar para proporcionar detalles de los propietarios de las partes involucradas en un proceso de contratación.
+Por ejemplo, en los procesos de Asociaciones Público-Privadas, a menudo se requiere que las compañías divulguen información sobre sus estructuras de propiedad al licitar y cuando se adjudique el contrato, es necesario mantener información sobre la propiedad de una Sociedad con Fines Específicos (SPV) actualizada durante la ejecución del proyecto.
+Debido a que cada propietario mencionado en la matriz de accionistas también debe tener una entrada en la matriz de 'parties', es posible utilizar esta extensión para crear información sobre las redes de propiedad corporativa involucrados en un proceso de contratación.
+Propiedad beneficiaria
+Esta extensión también incluye una entrada 'stub' para registrar información de propiedad beneficiaria contra una parte.
+En la actualidad, esto incluye espacio para la descripción en texto libre de las estructuras de propiedad y control, pero podría ampliarse con información estructurada sobre la propiedad efectiva basada en el borrador Beneficial Ownership Data Standard.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/signatories/index.html b/es/extensions/signatories/index.html
new file mode 100644
index 000000000..1eec8c2fc
--- /dev/null
+++ b/es/extensions/signatories/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Accionistas +
+ ++ Agrega campos de propiedad de la empresa al objeto de organización utilizado en la lista de partes. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Shareholder +
+ +
+ The extension defines a new Shareholder object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID del Accionista + | +
+ Un identificador local para este accionista, único dentro de este bloque. Este campo se utiliza para realizar un seguimiento de las revisiones múltiples de un accionista a través de la compilación del mecanismo de entrega a registro. + + |
+ + string + | +
+
+ shareholder
+
+ |
+ + Referencia de la organización de accionistas. + | +
+ Una referencia de la organización señalando la entrada en la sección de partes de la organización accionaria. + + |
+ + OrganizationReference object + | +
+
+ shareholding
+
+ |
+ + Participación + | +
+ El porcentaje de acciones que posee el accionista, expresado como un valor decimal entre 0 y 1. + + |
+ + number + | +
+
+ votingRights
+
+ |
+ + Derechos de voto de los accionistas + | +
+ Especifica el tipo de derechos de voto asociado a las acciones que posee el accionista en contra de la lista de códigos de derechos de voto. + + |
+ + string from closed votingRights codelist + | +
+
+ votingRightsDetails
+
+ |
+ + Detalles de los derechos de voto de los accionistas + | +
+ Información detallada sobre los derechos de voto del accionista. Este campo debe completarse cuando los derechos de voto de los accionistas son restringidos, adicionales o mejorados. + + |
+ + string + | +
+
+ notes
+
+ |
+ + Notas sobre los accionistas + | +
+ Notas adicionales sobre este accionista. Este campo debe usarse para proporcionar detalles sobre los límites máximos en la transferencia de capital, o acuerdos de bloqueo, aplicables a este accionista. + + |
+ + string + | +
+ Organization +
+ +
+ The extension defines these fields in the Organization object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ shareholders
+
+ |
+ + Accionistas de la organización + | +
+ Una lista de los accionistas de la organización: se utiliza para proporcionar información sobre la propiedad de la empresa para las sociedades, principalmente en el caso de contratos grandes y complejos, o Sociedades Públicas Privadas, que requieren la divulgación de esta información para ciertos licitadores o adjudicatarios. + + |
+ + array of Shareholder objects + | +
+
+ beneficialOwnership
+
+ |
+ + Propiedad beneficiaria + | +
+ Esta sección puede usarse para registrar información concerniente a individuos u organizaciones con intereses de propiedad o control efectivas en esta parte. Cuando se dispone de datos estructurados, esta sección puede ampliarse mediante la incorporación o vinculación a la información modelada utilizando el [Estándar de Datos de Propiedad Efectiva (BODS)] (https://github.com/openownership/data-standard). + + |
+ + object + | +
+
+ beneficialOwnership.
+ |
+ + Descripción + | +
+ Una descripción en texto libre de la propiedad efectiva o los acuerdos de control. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/signatories/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/signatories/master/release-schema.json b/es/extensions/signatories/master/release-schema.json
new file mode 100644
index 000000000..8ccbec268
--- /dev/null
+++ b/es/extensions/signatories/master/release-schema.json
@@ -0,0 +1,18 @@
+{
+ "definitions": {
+ "Contract": {
+ "properties": {
+ "signatories": {
+ "title": "Firmantes del contrato",
+ "description": "The signatories to the contract. Each signatory should have a corresponding entry in the `parties` array.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/signatories/master/schema/index.html b/es/extensions/signatories/master/schema/index.html
new file mode 100644
index 000000000..d18841e25
--- /dev/null
+++ b/es/extensions/signatories/master/schema/index.html
@@ -0,0 +1,231 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Firmantes +
+ ++ Adds a signatories array to the contract object, for when the signatories differ from the buyer for the contracting process and the suppliers for the award. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a signatories array to the contract object, for when the signatories differ from the buyer for the contracting process and the suppliers for the award.
+In OCDS, the signatories to a contract are not explicitly declared in the contracts section. Instead, the signatories are implicitly assumed to be the buyer and the suppliers in the award associated to the contract.
In some types of contracting processes, there can be additional signatories to the contract, or the signatories to the contract can differ from those specified in buyer and suppliers.
Utilice esta extensión sólo si los firmantes de un contrato difieren de los proveedores suppliers de su adjudicación y del comprador buyer del proceso de contratación. En ese caso, enumere todos los firmantes del contrato, incluidos el comprador buyer y los proveedores suppliers.
Guidance
+Each signatory should have an associated entry in the parties section.
Ejemplo
+El siguiente fragmento de JSON modela un proceso de contratación en el que hay un firmante adicional del contrato además de los definidos en los campos buyer y awards.suppliers.
{
+ "buyer": {
+ "name": "Ministry of Communications",
+ "id": "GB-GOV-12345678"
+ },
+ "awards": [
+ {
+ "id": "1",
+ "suppliers": [
+ {
+ "name": "Example Consortium",
+ "id": "GB-COH-00000000"
+ }
+ ]
+ }
+ ],
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "signatories": [
+ {
+ "name": "Ministry of Communications",
+ "id": "GB-GOV-12345678"
+ },
+ {
+ "name": "Example Consortium",
+ "id": "GB-COH-00000000"
+ },
+ {
+ "name": "Telecommunications UK",
+ "id": "GB-GOV-99999999"
+ }
+ ]
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/statistics/index.html b/es/extensions/statistics/index.html
new file mode 100644
index 000000000..800e45d70
--- /dev/null
+++ b/es/extensions/statistics/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Firmantes +
+ ++ Adds a signatories array to the contract object, for when the signatories differ from the buyer for the contracting process and the suppliers for the award. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ signatories
+
+ |
+ + Firmantes del contrato + | +
+ The signatories to the contract. Each signatory should have a corresponding entry in the |
+ + array of OrganizationReference objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/statistics/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/statistics/master/codelists/statisticScope.csv b/es/extensions/statistics/master/codelists/statisticScope.csv
new file mode 100644
index 000000000..a1a298817
--- /dev/null
+++ b/es/extensions/statistics/master/codelists/statisticScope.csv
@@ -0,0 +1,2 @@
+Code,Title,Description
+complaints,Complaints,Statistics relating to complaints and complainants. Also known as review requests.
diff --git a/es/extensions/statistics/master/extension.json b/es/extensions/statistics/master/extension.json
new file mode 100644
index 000000000..e39a6cba6
--- /dev/null
+++ b/es/extensions/statistics/master/extension.json
@@ -0,0 +1,30 @@
+{
+ "name": {
+ "en": "Statistics",
+ "es": "Statistics"
+ },
+ "description": {
+ "en": "Adds a top-level statistics array to describe statistics about the contracting process.",
+ "es": "Adds a top-level statistics array to describe statistics about the contracting process."
+ },
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting-extensions/ocds_statistics_extension"
+ },
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+statistic.csv",
+ "statisticScope.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ],
+ "dependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/statistics/master/index.html b/es/extensions/statistics/master/index.html
new file mode 100644
index 000000000..10c6b7ec8
--- /dev/null
+++ b/es/extensions/statistics/master/index.html
@@ -0,0 +1,292 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Statistics +
+ ++ Adds a top-level statistics array to describe statistics about the contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +statistic.csv +
+ +
+ You can download the +statistic.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ complainants
+
+ |
+ + Complainants + | +
+ The total number of organizations that submitted a complaint. + + |
+
+ statisticScope.csv +
+ +
+ You can download the statisticScope.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ complaints
+
+ |
+ + Complaints + | +
+ Statistics relating to complaints and complainants. Also known as review requests. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/statistics/master/release-schema.json b/es/extensions/statistics/master/release-schema.json
new file mode 100644
index 000000000..10a2d8f33
--- /dev/null
+++ b/es/extensions/statistics/master/release-schema.json
@@ -0,0 +1,35 @@
+{
+ "properties": {
+ "statistics": {
+ "title": "Statistics",
+ "description": "Statistics about the contracting process.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Statistic"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "definitions": {
+ "Statistic": {
+ "properties": {
+ "scope": {
+ "title": "Scope",
+ "description": "The scope of the statistic, from the closed statistic scope codelist.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "statisticScope.csv",
+ "openCodelist": false,
+ "enum": [
+ "complaints",
+ null
+ ]
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/statistics/master/schema/index.html b/es/extensions/statistics/master/schema/index.html
new file mode 100644
index 000000000..baa5a8060
--- /dev/null
+++ b/es/extensions/statistics/master/schema/index.html
@@ -0,0 +1,287 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Statistics +
+ ++ Adds a top-level statistics array to describe statistics about the contracting process. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a top-level statistics array to describe statistics about the contracting process.
+This extension must be used with the Bid statistics and details extension.
+Guidance
+If you use a codelist for statistics.measure, you should explain where the codes are from in your publication policy/user guide.
Example
+A statistic describing the number of complaints received about the unjustified rejection of abnormally low tenders. The value of statistics.measure is taken from the EU's irregularity type codelist.
{
+ "statistics": [
+ {
+ "id": "1",
+ "value": 2,
+ "measure": "ab-low",
+ "scope": "complaints",
+ "notes": "Unjustified rejection of abnormally low tenders"
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/statusDetails/index.html b/es/extensions/statusDetails/index.html
new file mode 100644
index 000000000..3e40d5624
--- /dev/null
+++ b/es/extensions/statusDetails/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Statistics +
+ ++ Adds a top-level statistics array to describe statistics about the contracting process. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statistics
+
+ |
+ + Statistics + | +
+ Statistics about the contracting process. + + |
+ + array of Statistic objects + | +
+ Statistic +
+ +
+ The extension defines these fields in the Statistic object from the Estadísticas y detalles de las ofertas extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ scope
+
+ |
+ + Scope + | +
+ The scope of the statistic, from the closed statistic scope codelist. + + |
+ + string from closed statisticScope codelist + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/statusDetails/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/statusDetails/master/release-schema.json b/es/extensions/statusDetails/master/release-schema.json
new file mode 100644
index 000000000..677c69325
--- /dev/null
+++ b/es/extensions/statusDetails/master/release-schema.json
@@ -0,0 +1,48 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "mainProcurementCategoryDetails": {
+ "title": "Detalles de la categor\u00eda principal de contrataci\u00f3n",
+ "description": "El nombre local de la Categor\u00eda Principal de Contrataci\u00f3n",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "statusDetails": {
+ "title": "Detalles de estado",
+ "description": "Detalle adicional sobre el estado de la licitaci\u00f3n. Este campo se puede utilizar para proporcionar el nombre local del estado.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "statusDetails": {
+ "title": "Detalles de estado",
+ "description": "Detalle adicional sobre el estado de la adjudicaci\u00f3n. Este campo se puede utilizar para proporcionar el nombre local del estado.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "statusDetails": {
+ "title": "Detalles de estado",
+ "description": "Detalle adicional sobre el estado del contrato. Este campo se puede utilizar para proporcionar el nombre local del estado.",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/statusDetails/master/schema/index.html b/es/extensions/statusDetails/master/schema/index.html
new file mode 100644
index 000000000..317ef61e3
--- /dev/null
+++ b/es/extensions/statusDetails/master/schema/index.html
@@ -0,0 +1,350 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Detalles de estado +
+ ++ Agregar un campo statusDetails al objeto Tender, Award y Contract. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+En algunos casos, es importante preservar el nombre local del estado en el que se encuentra la licitación, adjudicación o contrato. Esta extensión agrega el campo statusDetails a los objetos de licitación, adjudicación y contrato, con el fin de proporcionar el nombre local del estado particular utilizado.
Ejemplos
+{
+ "tender": {
+ "id": "tender-1",
+ "status": "complete",
+ "statusDetails": "Adjudicado"
+ },
+ "awards": [
+ {
+ "id": "award-1",
+ "status": "active",
+ "statusDetails": "Adjudicado"
+ }
+ ],
+ "contracts": [
+ {
+ "id": "contract-1",
+ "awardID": "award-1",
+ "status": "active",
+ "statusDetails": "Adjudicado"
+ }
+ ]
+}
+Un ejemplo de contract.statusDetails reflejando una orden judicial:
{
+ "tender": {
+ "id": "tender-1",
+ "status": "complete"
+ },
+ "awards": [
+ {
+ "id": "award-1",
+ "status": "active"
+ }
+ ],
+ "contracts": [
+ {
+ "id": "contract-1",
+ "awardID": "award-1",
+ "status": "active",
+ "statusDetails": "Suspended as a result of a court order."
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2021-01-11
+-
+
- Agregar un ejemplo de
contract.statusDetailsreflejando una orden judicial:
+
Esta extensión se discutió originalmente en https://github.com/open-contracting/standard/issues/764.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/subcontracting/index.html b/es/extensions/subcontracting/index.html
new file mode 100644
index 000000000..fa1cd5d48
--- /dev/null
+++ b/es/extensions/subcontracting/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Detalles de estado +
+ ++ Agregar un campo statusDetails al objeto Tender, Award y Contract. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ mainProcurementCategoryDetails
+
+ |
+ + Detalles de la categoría principal de contratación + | +
+ El nombre local de la Categoría Principal de Contratación + + |
+ + string + | +
+
+ statusDetails
+
+ |
+ + Detalles de estado + | +
+ Detalle adicional sobre el estado de la licitación. Este campo se puede utilizar para proporcionar el nombre local del estado. + + |
+ + string + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statusDetails
+
+ |
+ + Detalles de estado + | +
+ Detalle adicional sobre el estado de la adjudicación. Este campo se puede utilizar para proporcionar el nombre local del estado. + + |
+ + string + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ statusDetails
+
+ |
+ + Detalles de estado + | +
+ Detalle adicional sobre el estado del contrato. Este campo se puede utilizar para proporcionar el nombre local del estado. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/subcontracting/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/subcontracting/master/extension.json b/es/extensions/subcontracting/master/extension.json
new file mode 100644
index 000000000..c9aebf61a
--- /dev/null
+++ b/es/extensions/subcontracting/master/extension.json
@@ -0,0 +1,30 @@
+{
+ "name": {
+ "en": "Subcontracting",
+ "es": "Subcontrataci\u00f3n"
+ },
+ "description": {
+ "en": "Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties.",
+ "es": "Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/subcontracting/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+partyRole.csv"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json",
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/subcontracting/master/index.html b/es/extensions/subcontracting/master/index.html
new file mode 100644
index 000000000..a94a88531
--- /dev/null
+++ b/es/extensions/subcontracting/master/index.html
@@ -0,0 +1,448 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Subcontratación +
+ ++ Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +partyRole.csv +
+ +
+ You can download the +partyRole.csv file in English.
+
+ The extension adds these codes to the partyRole.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ subcontractor
+
+ |
+ + Subcontractor + | +
+ An organization that will perform part of a contract on behalf of a supplier. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/subcontracting/master/release-schema.json b/es/extensions/subcontracting/master/release-schema.json
new file mode 100644
index 000000000..d914cfbf7
--- /dev/null
+++ b/es/extensions/subcontracting/master/release-schema.json
@@ -0,0 +1,210 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "subcontractingTerms": {
+ "title": "T\u00e9rminos de subcontrataci\u00f3n ",
+ "description": "Informaci\u00f3n sobre los t\u00e9rminos que rigen la subcontrataci\u00f3n.",
+ "$ref": "#/definitions/SubcontractingTerms"
+ }
+ }
+ },
+ "Award": {
+ "properties": {
+ "hasSubcontracting": {
+ "title": "Subcontrataci\u00f3n involucrada",
+ "description": "Si se subcontratar\u00e1 una parte del contrato.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "subcontracting": {
+ "title": "Subcontrataci\u00f3n",
+ "description": "Informaci\u00f3n sobre las partes del contrato que el proveedor subcontratar\u00e1 a terceros.",
+ "$ref": "#/definitions/Subcontracting"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "subcontractingTerms": {
+ "title": "T\u00e9rminos de subcontrataci\u00f3n ",
+ "description": "Informaci\u00f3n sobre los t\u00e9rminos que rigen la subcontrataci\u00f3n.",
+ "$ref": "#/definitions/SubcontractingTerms"
+ }
+ }
+ },
+ "Bid": {
+ "properties": {
+ "hasSubcontracting": {
+ "title": "Subcontrataci\u00f3n involucrada",
+ "description": "Whether a part of the contract will be subcontracted to third parties.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "subcontracting": {
+ "title": "Subcontrataci\u00f3n",
+ "description": "Information about the parts of the contract that will be subcontracted to third parties.",
+ "$ref": "#/definitions/Subcontracting"
+ }
+ }
+ },
+ "SubcontractingTerms": {
+ "title": "T\u00e9rminos de subcontrataci\u00f3n ",
+ "description": "Las obligaciones de los proveedores que subcontratan.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una descripci\u00f3n de los t\u00e9rminos que rigen la subcontrataci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "competitiveMaximumPercentage": {
+ "title": "Porcentaje m\u00e1ximo del valor del contrato para una subcontrataci\u00f3n competitiva",
+ "description": "The maximum percentage of the contract value that the buyer or procuring entity allows the supplier to subcontract to third parties through a competitive procedure.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0,
+ "exclusiveMinimum": true
+ },
+ "competitiveMinimumPercentage": {
+ "title": "Porcentaje m\u00ednimo del valor del contrato para una subcontrataci\u00f3n competitiva",
+ "description": "The minimum percentage of the contract value that the buyer or procuring entity requires the supplier to subcontract to third parties through a competitive procedure.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0
+ }
+ },
+ "minProperties": 1
+ },
+ "Subcontracting": {
+ "title": "Subcontrataci\u00f3n",
+ "description": "Information about the parts of the contract that will be subcontracted to third parties.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "The description of the part of the contract that will be subcontracted to third parties.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "maximumPercentage": {
+ "title": "Porcentaje m\u00e1ximo del valor del contrato",
+ "description": "El porcentaje m\u00e1ximo del valor del contrato que se subcontratar\u00e1.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0,
+ "exclusiveMinimum": true
+ },
+ "minimumPercentage": {
+ "title": "Porcentaje m\u00ednimo del valor del contrato",
+ "description": "El porcentaje m\u00ednimo del valor del contrato que se subcontratar\u00e1.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0
+ },
+ "competitiveMaximumPercentage": {
+ "title": "Porcentaje m\u00e1ximo del valor del contrato para una subcontrataci\u00f3n competitiva",
+ "description": "The maximum percentage of the contract value that the buyer or procuring entity allows the supplier to subcontract to third parties through a competitive procedure.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0,
+ "exclusiveMinimum": true
+ },
+ "competitiveMinimumPercentage": {
+ "title": "Porcentaje m\u00ednimo del valor del contrato para una subcontrataci\u00f3n competitiva",
+ "description": "The minimum percentage of the contract value that the buyer or procuring entity requires the supplier to subcontract to third parties through a competitive procedure.",
+ "type": [
+ "number",
+ "null"
+ ],
+ "maximum": 1,
+ "minimum": 0
+ },
+ "value": {
+ "title": "Valor subcontratado",
+ "description": "The estimated value of the part of the contract that will be subcontracted to third parties.",
+ "$ref": "#/definitions/Value"
+ },
+ "competitive": {
+ "title": "Subcontrataci\u00f3n competitiva",
+ "description": "Si el proveedor subcontratar\u00e1 parte del contrato a terceros mediante un procedimiento competitivo.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "subcontracts": {
+ "title": "Subcontracts",
+ "description": "Information about the subcontracts that will be established.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Subcontract"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Subcontract": {
+ "title": "Subcontract",
+ "description": "A relationship that suppliers establish with a third party to perform part of the contract on their behalf.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identifier",
+ "description": "The locally unique identifier for the subcontract.",
+ "type": [
+ "string"
+ ],
+ "minLength": 1
+ },
+ "subcontractor": {
+ "title": "Subcontractor",
+ "description": "The organization that performs part of the contract on behalf of the suppliers.",
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "mainContractors": {
+ "title": "Main contractors",
+ "description": "The organizations to which the subcontractor will be subcontracted, if they are a subset of the tenderers submitting the bid or the suppliers receiving the award.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/OrganizationReference"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/subcontracting/master/schema/index.html b/es/extensions/subcontracting/master/schema/index.html
new file mode 100644
index 000000000..bc010c648
--- /dev/null
+++ b/es/extensions/subcontracting/master/schema/index.html
@@ -0,0 +1,763 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Subcontratación +
+ ++ Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties. +
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties.
+Guía
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Si el porcentaje del valor del contrato que se subcontrata es un número exacto y no un rango, establecer minimumPercentage y maximumPercentage al mismo número.
Contexto legal
+In the European Union, this extension's fields correspond to article 21 of directive 2009/81/EC and the eForms business terms in BG-180 (Subcontracting) and BG-711 (Contract Terms).
+For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+TED XML schema R2.0.9 models the minimum and maximum percentages of the contract value that the contractor needs to subcontract as part of each award for F15: Voluntary ex ante transparency notice. eForms XML models these as part of each lot. As such, different fields ought to be used when implementing each profile.
+Ejemplos
+Tender and awards
+Information about the terms governing subcontracting is disclosed at the tender and award stages, and information about the parts of the contract that the supplier will subcontract is disclosed at the award stage.
+{
+ "tender": {
+ "subcontractingTerms": {
+ "description": "The successful tenderer is obliged to specify which part or parts of the contract it intends to subcontract beyond the required percentage and to indicate the subcontractors already identified."
+ }
+ },
+ "awards": [
+ {
+ "id": "1",
+ "hasSubcontracting": true,
+ "subcontracting": {
+ "competitive": true,
+ "value": {
+ "amount": 28000,
+ "currency": "EUR"
+ },
+ "minimumPercentage": 0.3,
+ "maximumPercentage": 0.3,
+ "competitiveMinimumPercentage": 0.1,
+ "competitiveMaximumPercentage": 0.25,
+ "description": "The painting and electricity tasks are subcontracted."
+ }
+ }
+ ]
+}
+Lots and bids
+Information about the terms governing subcontracting is disclosed per lot at the tender stage, and information about the parts of the contract that the tenderer will subcontract is disclosed at the bid stage.
+{
+ "parties": [
+ {
+ "id": "ORG-0005",
+ "roles": [
+ "tenderer"
+ ]
+ },
+ {
+ "id": "ORG-0012",
+ "roles": [
+ "subcontractor"
+ ]
+ }
+ ],
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "subcontractingTerms": {
+ "description": "The contractor must subcontract a minimum percentage of the contract using the procedure set out in Title III of Directive 2009/81/EC.",
+ "competitiveMinimumPercentage": 0.255,
+ "competitiveMaximumPercentage": 0.455
+ }
+ }
+ ]
+ },
+ "bids": {
+ "details": [
+ {
+ "id": "1",
+ "hasSubcontracting": true,
+ "subcontracting": {
+ "description": "The subcontracting will be...",
+ "value": {
+ "amount": 9999999.99,
+ "currency": "EUR"
+ },
+ "minimumPercentage": 0.3,
+ "maximumPercentage": 0.3,
+ "subcontracts": [
+ {
+ "id": "1",
+ "subcontractor": {
+ "id": "ORG-0012",
+ "name": "Company ABC"
+ },
+ "mainContractors": [
+ {
+ "id": "ORG-0005",
+ "name": "Tendering Company Ltd"
+ }
+ ]
+ }
+ ]
+ }
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-05-22
+-
+
- Add fields for eForms:
+
-
+
Bid.hasSubcontracting
+Bid.subcontracting
+SubcontractingTerms.competitiveMaximumPercentage
+SubcontractingTerms.competitiveMinimumPercentage
+Subcontracting.subcontracts
+
+ - Update field descriptions to allow the
Subcontractingobject to be used in the context of bids: +-
+
Subcontracting
+Subcontracting.description
+Subcontracting.value
+
+ - Add 'subcontractor' to party role codelist. +
2022-07-18
+-
+
- Add
Lot.subcontractingTermsfield.
+
2020-10-07
+-
+
- Renombrar el nombre del campo
subcontractingenTenderal objeto desubcontractingTerms.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues) y en pull requests. También puede ver discusiones sobre esta extensión en este issue.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/submissionTerms/index.html b/es/extensions/submissionTerms/index.html
new file mode 100644
index 000000000..a074532c3
--- /dev/null
+++ b/es/extensions/submissionTerms/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Subcontratación +
+ ++ Adds objects for information about the terms governing subcontracting and the parts of the contract that tenderers and suppliers will subcontract to third parties. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ subcontractingTerms
+
+ |
+ + Términos de subcontratación + | +
+ Información sobre los términos que rigen la subcontratación. + + |
+ + SubcontractingTerms object + | +
+ Award +
+ +
+ The extension defines these fields in the Award object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasSubcontracting
+
+ |
+ + Subcontratación involucrada + | +
+ Si se subcontratará una parte del contrato. + + |
+ + boolean + | +
+
+ subcontracting
+
+ |
+ + Subcontratación + | +
+ Información sobre las partes del contrato que el proveedor subcontratará a terceros. + + |
+ + Subcontracting object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ subcontractingTerms
+
+ |
+ + Términos de subcontratación + | +
+ Información sobre los términos que rigen la subcontratación. + + |
+ + SubcontractingTerms object + | +
+ Bid +
+ +
+ The extension defines these fields in the Bid object from the Estadísticas y detalles de las ofertas extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasSubcontracting
+
+ |
+ + Subcontratación involucrada + | +
+ Whether a part of the contract will be subcontracted to third parties. + + |
+ + boolean + | +
+
+ subcontracting
+
+ |
+ + Subcontratación + | +
+ Information about the parts of the contract that will be subcontracted to third parties. + + |
+ + Subcontracting object + | +
+ SubcontractingTerms +
+ +
+ The extension defines a new SubcontractingTerms object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Descripción + | +
+ Una descripción de los términos que rigen la subcontratación. + + |
+ + string + | +
+
+ competitiveMaximumPercentage
+
+ |
+ + Porcentaje máximo del valor del contrato para una subcontratación competitiva + | +
+ The maximum percentage of the contract value that the buyer or procuring entity allows the supplier to subcontract to third parties through a competitive procedure. + + |
+ + number + | +
+
+ competitiveMinimumPercentage
+
+ |
+ + Porcentaje mínimo del valor del contrato para una subcontratación competitiva + | +
+ The minimum percentage of the contract value that the buyer or procuring entity requires the supplier to subcontract to third parties through a competitive procedure. + + |
+ + number + | +
+ Subcontracting +
+ +
+ The extension defines a new Subcontracting object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Descripción + | +
+ The description of the part of the contract that will be subcontracted to third parties. + + |
+ + string + | +
+
+ maximumPercentage
+
+ |
+ + Porcentaje máximo del valor del contrato + | +
+ El porcentaje máximo del valor del contrato que se subcontratará. + + |
+ + number + | +
+
+ minimumPercentage
+
+ |
+ + Porcentaje mínimo del valor del contrato + | +
+ El porcentaje mínimo del valor del contrato que se subcontratará. + + |
+ + number + | +
+
+ competitiveMaximumPercentage
+
+ |
+ + Porcentaje máximo del valor del contrato para una subcontratación competitiva + | +
+ The maximum percentage of the contract value that the buyer or procuring entity allows the supplier to subcontract to third parties through a competitive procedure. + + |
+ + number + | +
+
+ competitiveMinimumPercentage
+
+ |
+ + Porcentaje mínimo del valor del contrato para una subcontratación competitiva + | +
+ The minimum percentage of the contract value that the buyer or procuring entity requires the supplier to subcontract to third parties through a competitive procedure. + + |
+ + number + | +
+
+ value
+
+ |
+ + Valor subcontratado + | +
+ The estimated value of the part of the contract that will be subcontracted to third parties. + + |
+ + Value object + | +
+
+ competitive
+
+ |
+ + Subcontratación competitiva + | +
+ Si el proveedor subcontratará parte del contrato a terceros mediante un procedimiento competitivo. + + |
+ + boolean + | +
+
+ subcontracts
+
+ |
+ + Subcontracts + | +
+ Information about the subcontracts that will be established. + + |
+ + array of Subcontract objects + | +
+ Subcontract +
+ +
+ The extension defines a new Subcontract object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identifier + | +
+ The locally unique identifier for the subcontract. + + |
+ + string + | +
+
+ subcontractor
+
+ |
+ + Subcontractor + | +
+ The organization that performs part of the contract on behalf of the suppliers. + + |
+ + OrganizationReference object + | +
+
+ mainContractors
+
+ |
+ + Main contractors + | +
+ The organizations to which the subcontractor will be subcontracted, if they are a subset of the tenderers submitting the bid or the suppliers receiving the award. + + |
+ + array of OrganizationReference objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/submissionTerms/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/submissionTerms/master/codelists/permission.csv b/es/extensions/submissionTerms/master/codelists/permission.csv
new file mode 100644
index 000000000..bb143c252
--- /dev/null
+++ b/es/extensions/submissionTerms/master/codelists/permission.csv
@@ -0,0 +1,4 @@
+Código,Título,Descripción
+required,Required,The activity is required.
+allowed,Allowed,The activity is allowed.
+notAllowed,Not allowed,The activity is not allowed.
diff --git a/es/extensions/submissionTerms/master/extension.json b/es/extensions/submissionTerms/master/extension.json
new file mode 100644
index 000000000..b34b9da20
--- /dev/null
+++ b/es/extensions/submissionTerms/master/extension.json
@@ -0,0 +1,29 @@
+{
+ "name": {
+ "en": "Submission terms",
+ "es": "T\u00e9rminos de Presentaci\u00f3n de la Oferta"
+ },
+ "description": {
+ "en": "Adds a submission terms object to the tender and lot objects, to describe how, when and where the tenderers must submit their bids.",
+ "es": "Agrega un objeto t\u00e9rminos de presentaci\u00f3n de la oferta a los objetos de la licitaci\u00f3n y del lote, para describir c\u00f3mo, cu\u00e1ndo y d\u00f3nde los oferentes deber\u00e1n presentar sus ofertas."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/submissionTerms/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "permission.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/es/extensions/submissionTerms/master/index.html b/es/extensions/submissionTerms/master/index.html
new file mode 100644
index 000000000..9ee687ad3
--- /dev/null
+++ b/es/extensions/submissionTerms/master/index.html
@@ -0,0 +1,355 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Términos de Presentación de la Oferta +
+ ++ Agrega un objeto términos de presentación de la oferta a los objetos de la licitación y del lote, para describir cómo, cuándo y dónde los oferentes deberán presentar sus ofertas. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ permission.csv +
+ +
+ You can download the permission.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ required
+
+ |
+ + Required + | +
+ The activity is required. + + |
+
+
+ allowed
+
+ |
+ + Allowed + | +
+ The activity is allowed. + + |
+
+
+ notAllowed
+
+ |
+ + Not allowed + | +
+ The activity is not allowed. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/submissionTerms/master/release-schema.json b/es/extensions/submissionTerms/master/release-schema.json
new file mode 100644
index 000000000..7c8baca37
--- /dev/null
+++ b/es/extensions/submissionTerms/master/release-schema.json
@@ -0,0 +1,145 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "submissionTerms": {
+ "title": "T\u00e9rminos de Presentaci\u00f3n de la Oferta",
+ "description": "Informaci\u00f3n sobre los t\u00e9rminos de presentaci\u00f3n de la oferta para describir c\u00f3mo, cu\u00e1ndo y d\u00f3nde los oferentes deben presentar sus ofertas para el procedimiento.",
+ "$ref": "#/definitions/SubmissionTerms"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "submissionTerms": {
+ "title": "T\u00e9rminos de Presentaci\u00f3n de la Oferta",
+ "description": "Informaci\u00f3n sobre los t\u00e9rminos de presentaci\u00f3n de la oferta para describir c\u00f3mo, cu\u00e1ndo y d\u00f3nde los oferentes deben presentar sus ofertas para el lote.",
+ "$ref": "#/definitions/SubmissionTerms"
+ }
+ }
+ },
+ "SubmissionTerms": {
+ "title": "T\u00e9rminos de Presentaci\u00f3n de la Oferta",
+ "description": "Informaci\u00f3n sobre los t\u00e9rminos de presentaci\u00f3n de la oferta para describir c\u00f3mo, cu\u00e1ndo y d\u00f3nde los oferentes deben presentar sus ofertas.",
+ "type": "object",
+ "properties": {
+ "electronicSubmissionPolicy": {
+ "title": "Pol\u00edtica de presentaci\u00f3n de oferta electr\u00f3nica",
+ "description": "Si los oferentes est\u00e1n obligados, autorizados o no autorizados a presentar ofertas por v\u00eda electr\u00f3nica.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "permission.csv",
+ "openCodelist": false,
+ "enum": [
+ "required",
+ "allowed",
+ "notAllowed",
+ null
+ ]
+ },
+ "variantPolicy": {
+ "title": "Pol\u00edtica de variantes",
+ "description": "Si se exige, se permite o no se permite a los licitantes presentar ofertas que satisfagan las necesidades del comprador de forma diferente a la propuesta en los documentos de contrataci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "permission.csv",
+ "openCodelist": false,
+ "enum": [
+ "required",
+ "allowed",
+ "notAllowed",
+ null
+ ]
+ },
+ "electronicCataloguePolicy": {
+ "title": "Electronic catalog policy",
+ "description": "Whether tenderers are required, allowed or not allowed to submit bids as electronic catalogs. An electronic catalog is an electronic format (typically prescribed by the buyer) that participants in the contracting process need to follow when exchanging information about technical specifications, evaluation criteria, bids, lots, etc.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "permission.csv",
+ "openCodelist": false,
+ "enum": [
+ "required",
+ "allowed",
+ "notAllowed",
+ null
+ ]
+ },
+ "languages": {
+ "title": "Idioma de Presentaci\u00f3n de la Oferta",
+ "description": "Uno o m\u00e1s lenguajes en los que se pueden presentar ofertas o solicitudes de participaci\u00f3n, utilizando dos letras [ISO639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes), o la extendida [etiquetas de lenguaje BCP47](http://www.w3.org/International/articles/language-tags/). El uso de c\u00f3digos de dos letras [ISO639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) es el recomendado.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "bidValidityPeriod": {
+ "title": "Per\u00edodo de validez de la oferta",
+ "description": "El per\u00edodo, desde la fecha l\u00edmite de presentaci\u00f3n de ofertas, durante el cual las ofertas deben seguir siendo v\u00e1lidas.",
+ "$ref": "#/definitions/Period"
+ },
+ "depositsGuarantees": {
+ "title": "Dep\u00f3sitos y garant\u00edas",
+ "description": "Informaci\u00f3n sobre los dep\u00f3sitos o garant\u00edas exigidas a los oferentes.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "advancedElectronicSignatureRequired": {
+ "title": "Advanced electronic signature required",
+ "description": "Whether an advanced or qualified electronic signature or seal is needed.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "multipleBidsAllowed": {
+ "title": "Multiple bids allowed",
+ "description": "Whether tenderers can submit more than one bid.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "nonElectronicSubmissionRationale": {
+ "title": "Non-electronic submission rationale",
+ "description": "The rationale for electronic submission not being allowed.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "subcontractingClauses": {
+ "title": "Subcontracting clauses",
+ "description": "The information about subcontracting that needs to be provided in the bid.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/submissionTerms/master/schema/index.html b/es/extensions/submissionTerms/master/schema/index.html
new file mode 100644
index 000000000..f6fc3d15a
--- /dev/null
+++ b/es/extensions/submissionTerms/master/schema/index.html
@@ -0,0 +1,491 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Términos de Presentación de la Oferta +
+ ++ Agrega un objeto términos de presentación de la oferta a los objetos de la licitación y del lote, para describir cómo, cuándo y dónde los oferentes deberán presentar sus ofertas. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar un objeto términos de presentación de la oferta a los objetos de la licitación y del lote, para describir cómo, cuándo y dónde los oferentes deberán presentar sus ofertas.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BG-102 (Submission Terms). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+{
+ "tender": {
+ "submissionTerms": {
+ "electronicSubmissionPolicy": "notAllowed",
+ "nonElectronicSubmissionRationale": "Inclusion of a physical model",
+ "advancedElectronicSignatureRequired": false,
+ "electronicCataloguePolicy": "notAllowed",
+ "variantPolicy": "notAllowed",
+ "multipleBidsAllowed": true,
+ "languages": [
+ "fr",
+ "es"
+ ],
+ "bidValidityPeriod": {
+ "startDate": "2019-09-20T00:00:00Z",
+ "endDate": "2019-12-02T23:59:59Z",
+ "durationInDays": 74
+ },
+ "depositsGuarantees": "An on-demand performance bond issued by an entity that the Contracting Entity judges to be acceptable (e.g. a bank or insurance company) and whose value is a percentage of the total contract price.",
+ "subcontractingClauses": [
+ "subc-oblig"
+ ]
+ }
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-06-07
+-
+
- Define "electronic catalog" for the
electronicCataloguePolicyfield.
+
2023-05-22
+-
+
- Add fields for eForms:
+
-
+
SubmissionTerms.advancedElectronicSignatureRequired
+SubmissionTerms.multipleBidsAllowed
+SubmissionTerms.nonElectronicSubmissionRationale
+SubmissionTerms.subcontractingClauses
+
+
2020-09-29
+-
+
- Renombrar
requiresGuaranteesadepositsGuarantees
+ - Cambiar el
typededepositsGuaranteesde un boolean a una cadena para que coincida con el tipo del elemento XML correspondiente a TED XML Schema 2.09.
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para la Unión Europea] (https://github.com/open-contracting-extensions/european-union/issues) y en pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/suitability/index.html b/es/extensions/suitability/index.html
new file mode 100644
index 000000000..e395da87b
--- /dev/null
+++ b/es/extensions/suitability/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Términos de Presentación de la Oferta +
+ ++ Agrega un objeto términos de presentación de la oferta a los objetos de la licitación y del lote, para describir cómo, cuándo y dónde los oferentes deberán presentar sus ofertas. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ submissionTerms
+
+ |
+ + Términos de Presentación de la Oferta + | +
+ Información sobre los términos de presentación de la oferta para describir cómo, cuándo y dónde los oferentes deben presentar sus ofertas para el procedimiento. + + |
+ + SubmissionTerms object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ submissionTerms
+
+ |
+ + Términos de Presentación de la Oferta + | +
+ Información sobre los términos de presentación de la oferta para describir cómo, cuándo y dónde los oferentes deben presentar sus ofertas para el lote. + + |
+ + SubmissionTerms object + | +
+ SubmissionTerms +
+ +
+ The extension defines a new SubmissionTerms object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ electronicSubmissionPolicy
+
+ |
+ + Política de presentación de oferta electrónica + | +
+ Si los oferentes están obligados, autorizados o no autorizados a presentar ofertas por vía electrónica. + + |
+ + string from closed permission codelist + | +
+
+ variantPolicy
+
+ |
+ + Política de variantes + | +
+ Si se exige, se permite o no se permite a los licitantes presentar ofertas que satisfagan las necesidades del comprador de forma diferente a la propuesta en los documentos de contratación. + + |
+ + string from closed permission codelist + | +
+
+ electronicCataloguePolicy
+
+ |
+ + Electronic catalog policy + | +
+ Whether tenderers are required, allowed or not allowed to submit bids as electronic catalogs. An electronic catalog is an electronic format (typically prescribed by the buyer) that participants in the contracting process need to follow when exchanging information about technical specifications, evaluation criteria, bids, lots, etc. + + |
+ + string from closed permission codelist + | +
+
+ languages
+
+ |
+ + Idioma de Presentación de la Oferta + | +
+ Uno o más lenguajes en los que se pueden presentar ofertas o solicitudes de participación, utilizando dos letras ISO639-1, o la extendida etiquetas de lenguaje BCP47. El uso de códigos de dos letras ISO639-1 es el recomendado. + + |
+ + array of strings + | +
+
+ bidValidityPeriod
+
+ |
+ + Período de validez de la oferta + | +
+ El período, desde la fecha límite de presentación de ofertas, durante el cual las ofertas deben seguir siendo válidas. + + |
+ + Period object + | +
+
+ depositsGuarantees
+
+ |
+ + Depósitos y garantías + | +
+ Información sobre los depósitos o garantías exigidas a los oferentes. + + |
+ + string + | +
+
+ advancedElectronicSignatureRequired
+
+ |
+ + Advanced electronic signature required + | +
+ Whether an advanced or qualified electronic signature or seal is needed. + + |
+ + boolean + | +
+
+ multipleBidsAllowed
+
+ |
+ + Multiple bids allowed + | +
+ Whether tenderers can submit more than one bid. + + |
+ + boolean + | +
+
+ nonElectronicSubmissionRationale
+
+ |
+ + Non-electronic submission rationale + | +
+ The rationale for electronic submission not being allowed. + + |
+ + string + | +
+
+ subcontractingClauses
+
+ |
+ + Subcontracting clauses + | +
+ The information about subcontracting that needs to be provided in the bid. + + |
+ + array of strings + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/suitability/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/suitability/master/release-schema.json b/es/extensions/suitability/master/release-schema.json
new file mode 100644
index 000000000..1725b6ce7
--- /dev/null
+++ b/es/extensions/suitability/master/release-schema.json
@@ -0,0 +1,47 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "suitability": {
+ "title": "Suitability",
+ "description": "Information about the suitability of the contracting process to different types of tenderers.",
+ "$ref": "#/definitions/Suitability"
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "suitability": {
+ "title": "Suitability",
+ "description": "Information about the suitability of the lot to different types of tenderers.",
+ "$ref": "#/definitions/Suitability"
+ }
+ }
+ },
+ "LotGroup": {
+ "properties": {
+ "suitability": {
+ "title": "Suitability",
+ "description": "Information about the suitability of the lot group to different types of tenderers.",
+ "$ref": "#/definitions/Suitability"
+ }
+ }
+ },
+ "Suitability": {
+ "title": "Suitability",
+ "description": "Information about the suitability of a contracting process, lot or lot group to different types of tenderers.",
+ "type": "object",
+ "properties": {
+ "sme": {
+ "title": "Small and medium enterprises",
+ "description": "Whether the contracting process, lot or lot group is suitable to small and medium enterprises.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/suitability/master/schema/index.html b/es/extensions/suitability/master/schema/index.html
new file mode 100644
index 000000000..70de41bb9
--- /dev/null
+++ b/es/extensions/suitability/master/schema/index.html
@@ -0,0 +1,384 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Suitability +
+ ++ Adds a suitability object to the tender, lot and lot group objects to describe their suitability to different types of tenderers. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a suitability object to the tender, lot and lot group objects to describe their suitability to different types of tenderers.
+Guidance
+If you are using the Lots extension, follow its guidance on whether to use tender.lots fields or tender fields.
Legal context
+In the European Union, this extension's fields correspond to eForms BT-726 (Suitable For SMEs). For correspondences to eForms fields, see OCDS for eForms.
+Examples
+Tender
+{
+ "tender": {
+ "id": "1",
+ "suitability": {
+ "sme": true
+ }
+ }
+}
+Lot
+{
+ "tender": {
+ "id": "1",
+ "lots": [
+ {
+ "id": "1",
+ "suitability": {
+ "sme": true
+ }
+ }
+ ]
+ }
+}
+Lot group
+{
+ "tender": {
+ "id": "1",
+ "lotGroups": [
+ {
+ "id": "1",
+ "suitability": {
+ "sme": true
+ }
+ }
+ ]
+ }
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/sustainability/index.html b/es/extensions/sustainability/index.html
new file mode 100644
index 000000000..a42391d0b
--- /dev/null
+++ b/es/extensions/sustainability/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Suitability +
+ ++ Adds a suitability object to the tender, lot and lot group objects to describe their suitability to different types of tenderers. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ suitability
+
+ |
+ + Suitability + | +
+ Information about the suitability of the contracting process to different types of tenderers. + + |
+ + Suitability object + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ suitability
+
+ |
+ + Suitability + | +
+ Information about the suitability of the lot to different types of tenderers. + + |
+ + Suitability object + | +
+ LotGroup +
+ +
+ The extension defines these fields in the LotGroup object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ suitability
+
+ |
+ + Suitability + | +
+ Information about the suitability of the lot group to different types of tenderers. + + |
+ + Suitability object + | +
+ Suitability +
+ +
+ The extension defines a new Suitability object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ sme
+
+ |
+ + Small and medium enterprises + | +
+ Whether the contracting process, lot or lot group is suitable to small and medium enterprises. + + |
+ + boolean + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/sustainability/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/sustainability/master/codelists/sustainabilityGoal.csv b/es/extensions/sustainability/master/codelists/sustainabilityGoal.csv
new file mode 100644
index 000000000..590079056
--- /dev/null
+++ b/es/extensions/sustainability/master/codelists/sustainabilityGoal.csv
@@ -0,0 +1,30 @@
+Code,Title,Description
+economic,Economic,"The goal is economic, such as formal employment and the local economy."
+economic.formalEmploymentPromotion,Formal employment promotion,The goal is to promote formal employment.
+economic.innovativePurchase,Innovative purchase,"The goal is to procure innovative goods, services or works."
+economic.localEconomyPromotion,Local economy promotion,The goal is to promote the local economy.
+economic.marketInnovationPromotion,Market innovation promotion,The goal is to promote market innovation.
+economic.processInnovationPromotion,Process innovation promotion,"The goal is to procure goods, services or works that entail process innovation."
+economic.productInnovationPromotion,Product innovation promotion,"The goal is to procure goods, services or works that entail product innovation."
+economic.researchDevelopmentActivities,Research and development activities,"The goal is to procure goods, services or works that involve research and development activities."
+environmental,Environmental,"The goal is to minimize and, if possible, avoid environmental damage: for example, reducing CO2 emissions and waste or promoting resource reuse and energy efficiency."
+environmental.biodiversityProtectionRestoration,Biodiversity protection and restoration,The goal is to protect and restore biodiversity and ecosystems.
+environmental.carbonEmissionsReduction,Carbon emissions reduction,The goal is to reduce carbon dioxide (CO2) emissions.
+environmental.circularEconomy,Circular economy,The goal is to promote the transition to a circular economy.
+environmental.climateChangeAdaptation,Climate change adaptation,The goal is to promote climate change adaptation.
+environmental.climateChangeMitigation,Climate change mitigation,The goal is to promote climate change mitigation.
+environmental.energyEfficiency,Energy efficiency,The goal is to promote energy efficiency.
+environmental.pollutionPrevention,Pollution prevention,The goal is to prevent pollution.
+environmental.recycling,Recycling,The goal is to promote recycling.
+environmental.resourceReuse,Resource reuse,The goal is to maximize the reuse of resources.
+environmental.waterResourcesProtection,Water resources protection,The goal is to promote the sustainable use and protection of water and marine resources.
+environmental.wasteReduction,Waste reduction,The goal is to reduce waste.
+social,Social,"The goal is to generate benefits to society: for example, promoting labor rights, diversity and equal opportunity, and occupational health and safety."
+social.accessibility,Accessibility,The goal is to promote accessibility for disabled and not disabled persons.
+social.disadvantagedEmploymentOpportunities,Disadvantaged employment opportunities,"The goal is to promote employment opportunities for the long-term unemployed, disadvantaged and/or for persons with disabilities."
+social.ethnicEquality,Ethnic equality,The goal is to promote ethnic equality.
+social.genderEquality,Gender equality,The goal is to promote gender equality.
+social.humanRightsInSupplyChains,Human rights in supply chains,The goal is to promote human rights due diligence in global supply chains.
+social.laborRightsPromotion,Labor rights promotion,The goal is to promote labor rights.
+social.smeInclusion,SME inclusion,The goal is to promote the participation of small and medium-sized enterprises (SMEs).
+social.womenInclusion,Women inclusion,The goal is to promote the participation of women-owned suppliers.
diff --git a/es/extensions/sustainability/master/codelists/sustainabilityStrategy.csv b/es/extensions/sustainability/master/codelists/sustainabilityStrategy.csv
new file mode 100644
index 000000000..87f7d6dad
--- /dev/null
+++ b/es/extensions/sustainability/master/codelists/sustainabilityStrategy.csv
@@ -0,0 +1,10 @@
+Code,Title,Description
+awardCriteria,Award criteria,"Award criteria are used to pursue sustainability goals: for example, allocating points relative to the percentage of recycled materials."
+contractPerformanceConditions,Contract performance conditions,"Contract performance conditions are used to pursue sustainability goals: for example, requiring the supplier to monitor carbon emissions during the contract's implementation."
+marginOfPreference,Margin of preference,"Margins of preference are used to pursue sustainability goals: for example, accepting the bid of a local supplier that is within a margin of the lowest bid."
+reservedParticipation,Reserved participation,"Reserved participation is used to pursue sustainability goals: for example, allowing only SMEs to participate in the contracting process."
+selectionCriteria,Selection criteria,"Selection criteria are used to fulfill sustainability goals: for example, requiring a bidder to have a sustainability certificate."
+technicalSpecifications,Technical specifications,"Items' technical specifications are used to pursue sustainability goals: for example, requiring a product to have an energy efficiency certificate."
+euGPPCriteria,EU GPP criteria,"Green public procurement criteria established at the European Union-level are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses."
+nationalGPPCriteria,National GPP criteria,"Green public procurement criteria established at the national level are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses."
+otherGPPCriteria,Other GPP criteria,"Green public procurement criteria established at a level other than the European Union or national levels are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses."
diff --git a/es/extensions/sustainability/master/extension.json b/es/extensions/sustainability/master/extension.json
new file mode 100644
index 000000000..42980c4ff
--- /dev/null
+++ b/es/extensions/sustainability/master/extension.json
@@ -0,0 +1,30 @@
+{
+ "name": {
+ "en": "Sustainability",
+ "es": "Sustainability"
+ },
+ "description": {
+ "en": "Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement.",
+ "es": "Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/sustainability"
+ },
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "sustainabilityGoal.csv",
+ "sustainabilityStrategy.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ],
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/sustainability/master/index.html b/es/extensions/sustainability/master/index.html
new file mode 100644
index 000000000..cb4c9cc48
--- /dev/null
+++ b/es/extensions/sustainability/master/index.html
@@ -0,0 +1,462 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Sustainability +
+ ++ Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ sustainabilityGoal.csv +
+ +
+ You can download the sustainabilityGoal.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ economic
+
+ |
+ + Economic + | +
+ The goal is economic, such as formal employment and the local economy. + + |
+
+
+ economic.formalEmploymentPromotion
+
+ |
+ + Formal employment promotion + | +
+ The goal is to promote formal employment. + + |
+
+
+ economic.innovativePurchase
+
+ |
+ + Innovative purchase + | +
+ The goal is to procure innovative goods, services or works. + + |
+
+
+ economic.localEconomyPromotion
+
+ |
+ + Local economy promotion + | +
+ The goal is to promote the local economy. + + |
+
+
+ economic.marketInnovationPromotion
+
+ |
+ + Market innovation promotion + | +
+ The goal is to promote market innovation. + + |
+
+
+ economic.processInnovationPromotion
+
+ |
+ + Process innovation promotion + | +
+ The goal is to procure goods, services or works that entail process innovation. + + |
+
+
+ economic.productInnovationPromotion
+
+ |
+ + Product innovation promotion + | +
+ The goal is to procure goods, services or works that entail product innovation. + + |
+
+
+ economic.researchDevelopmentActivities
+
+ |
+ + Research and development activities + | +
+ The goal is to procure goods, services or works that involve research and development activities. + + |
+
+
+ environmental
+
+ |
+ + Environmental + | +
+ The goal is to minimize and, if possible, avoid environmental damage: for example, reducing CO2 emissions and waste or promoting resource reuse and energy efficiency. + + |
+
+
+ environmental.biodiversityProtectionRestoration
+
+ |
+ + Biodiversity protection and restoration + | +
+ The goal is to protect and restore biodiversity and ecosystems. + + |
+
+
+ environmental.carbonEmissionsReduction
+
+ |
+ + Carbon emissions reduction + | +
+ The goal is to reduce carbon dioxide (CO2) emissions. + + |
+
+
+ environmental.circularEconomy
+
+ |
+ + Circular economy + | +
+ The goal is to promote the transition to a circular economy. + + |
+
+
+ environmental.climateChangeAdaptation
+
+ |
+ + Climate change adaptation + | +
+ The goal is to promote climate change adaptation. + + |
+
+
+ environmental.climateChangeMitigation
+
+ |
+ + Climate change mitigation + | +
+ The goal is to promote climate change mitigation. + + |
+
+
+ environmental.energyEfficiency
+
+ |
+ + Energy efficiency + | +
+ The goal is to promote energy efficiency. + + |
+
+
+ environmental.pollutionPrevention
+
+ |
+ + Pollution prevention + | +
+ The goal is to prevent pollution. + + |
+
+
+ environmental.recycling
+
+ |
+ + Recycling + | +
+ The goal is to promote recycling. + + |
+
+
+ environmental.resourceReuse
+
+ |
+ + Resource reuse + | +
+ The goal is to maximize the reuse of resources. + + |
+
+
+ environmental.waterResourcesProtection
+
+ |
+ + Water resources protection + | +
+ The goal is to promote the sustainable use and protection of water and marine resources. + + |
+
+
+ environmental.wasteReduction
+
+ |
+ + Waste reduction + | +
+ The goal is to reduce waste. + + |
+
+
+ social
+
+ |
+ + Social + | +
+ The goal is to generate benefits to society: for example, promoting labor rights, diversity and equal opportunity, and occupational health and safety. + + |
+
+
+ social.accessibility
+
+ |
+ + Accessibility + | +
+ The goal is to promote accessibility for disabled and not disabled persons. + + |
+
+
+ social.disadvantagedEmploymentOpportunities
+
+ |
+ + Disadvantaged employment opportunities + | +
+ The goal is to promote employment opportunities for the long-term unemployed, disadvantaged and/or for persons with disabilities. + + |
+
+
+ social.ethnicEquality
+
+ |
+ + Ethnic equality + | +
+ The goal is to promote ethnic equality. + + |
+
+
+ social.genderEquality
+
+ |
+ + Gender equality + | +
+ The goal is to promote gender equality. + + |
+
+
+ social.humanRightsInSupplyChains
+
+ |
+ + Human rights in supply chains + | +
+ The goal is to promote human rights due diligence in global supply chains. + + |
+
+
+ social.laborRightsPromotion
+
+ |
+ + Labor rights promotion + | +
+ The goal is to promote labor rights. + + |
+
+
+ social.smeInclusion
+
+ |
+ + SME inclusion + | +
+ The goal is to promote the participation of small and medium-sized enterprises (SMEs). + + |
+
+
+ social.womenInclusion
+
+ |
+ + Women inclusion + | +
+ The goal is to promote the participation of women-owned suppliers. + + |
+
+ sustainabilityStrategy.csv +
+ +
+ You can download the sustainabilityStrategy.csv file in English.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ awardCriteria
+
+ |
+ + Award criteria + | +
+ Award criteria are used to pursue sustainability goals: for example, allocating points relative to the percentage of recycled materials. + + |
+
+
+ contractPerformanceConditions
+
+ |
+ + Contract performance conditions + | +
+ Contract performance conditions are used to pursue sustainability goals: for example, requiring the supplier to monitor carbon emissions during the contract's implementation. + + |
+
+
+ marginOfPreference
+
+ |
+ + Margin of preference + | +
+ Margins of preference are used to pursue sustainability goals: for example, accepting the bid of a local supplier that is within a margin of the lowest bid. + + |
+
+
+ reservedParticipation
+
+ |
+ + Reserved participation + | +
+ Reserved participation is used to pursue sustainability goals: for example, allowing only SMEs to participate in the contracting process. + + |
+
+
+ selectionCriteria
+
+ |
+ + Selection criteria + | +
+ Selection criteria are used to fulfill sustainability goals: for example, requiring a bidder to have a sustainability certificate. + + |
+
+
+ technicalSpecifications
+
+ |
+ + Technical specifications + | +
+ Items' technical specifications are used to pursue sustainability goals: for example, requiring a product to have an energy efficiency certificate. + + |
+
+
+ euGPPCriteria
+
+ |
+ + EU GPP criteria + | +
+ Green public procurement criteria established at the European Union-level are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses. + + |
+
+
+ nationalGPPCriteria
+
+ |
+ + National GPP criteria + | +
+ Green public procurement criteria established at the national level are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses. + + |
+
+
+ otherGPPCriteria
+
+ |
+ + Other GPP criteria + | +
+ Green public procurement criteria established at a level other than the European Union or national levels are used to pursue sustainability goals. Criteria can include selection criteria, technical specifications, award criteria and contract performance clauses. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/sustainability/master/release-schema.json b/es/extensions/sustainability/master/release-schema.json
new file mode 100644
index 000000000..075f1abf4
--- /dev/null
+++ b/es/extensions/sustainability/master/release-schema.json
@@ -0,0 +1,94 @@
+{
+ "definitions": {
+ "Sustainability": {
+ "title": "Sustainability",
+ "description": "Information about how the contracting process or lot incorporates Sustainable Public Procurement.",
+ "type": "object",
+ "properties": {
+ "description": {
+ "title": "Description",
+ "description": "A description of how the contracting process or lot incorporates Sustainable Public Procurement.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "goal": {
+ "title": "Goal",
+ "description": "The sustainability goal pursued, from the sustainabilityGoal codelist. New sub-codes may be used outside those in the codelist, following the format [existing-code].[sub-code].",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "sustainabilityGoal.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "strategies": {
+ "title": "Strategies",
+ "description": "The strategies used to pursue the sustainability goal(s), from the sustainabilityStrategy codelist.",
+ "type": [
+ "array",
+ "null"
+ ],
+ "items": {
+ "type": "string",
+ "minLength": 1
+ },
+ "codelist": "sustainabilityStrategy.csv",
+ "openCodelist": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "Tender": {
+ "properties": {
+ "hasSustainability": {
+ "title": "Has sustainability",
+ "description": "Whether the contracting process incorporates Sustainable Public Procurement.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "sustainability": {
+ "title": "Sustainability",
+ "description": "Information about how the contracting process incorporates Sustainable Public Procurement.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Sustainability"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "hasSustainability": {
+ "title": "Has sustainability",
+ "description": "Whether the lot incorporates Sustainable Public Procurement.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "sustainability": {
+ "title": "Sustainability",
+ "description": "Information about how the lot incorporates Sustainable Public Procurement.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Sustainability"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/sustainability/master/schema/index.html b/es/extensions/sustainability/master/schema/index.html
new file mode 100644
index 000000000..87c00f4ab
--- /dev/null
+++ b/es/extensions/sustainability/master/schema/index.html
@@ -0,0 +1,406 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Sustainability +
+ ++ Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement (SPP).
+Motivation
+To calculate SPP indicators, a user or an application needs to be able to perform the following tasks, using OCDS data:
+-
+
- Select the contracting processes or individual lots that relate to SPP. +
- Select the contracting processes or individual lots that relate to a specific sustainability goal. +
- Determine which strategies are being used to promote a sustainability goal, within a contracting process or lot. +
- Determine whether a procured item or a supplier has characteristics related to sustainability. +
This extension add the fields needed for the above tasks as structured data.
+Guidance
+If you know a contracting process or lot is SPP-related, set hasSustainability to true.
If you know the sustainability goals pursued through the contracting process or lot, then, for each goal, add an entry in its sustainability array, from the sustainabilityGoal.csv codelist. This codelist contains codes for broad goals (like 'environmental') and narrower goals (like 'environmental.wasteReduction'). It is an open codelist, such that you can add new codes if no existing code is appropriate.
If you know the strategies used to pursue the sustainability goal(s), then, for each goal, add an entry in the strategies array, from the sustainabilityStrategy.csv codelist.
Examples
+hasSustainability only
+Public Health Wales adopts SPP in a contracting process to design office space and supply furniture.
+{
+ "tender": {
+ "id": "P427",
+ "title": "Design of office space and supply of furniture, reusing existing furniture",
+ "hasSustainability": true
+ }
+}
+If the contracting process is divided into lots, and it is known which lot(s) relate to SPP, set the lot's hasSustainability field:
{
+ "tender": {
+ "lots": [
+ {
+ "id": "123",
+ "hasSustainability": true
+ }
+ ]
+ }
+}
+The sustainability goal is known
+Public Health Wales intends to reduce waste and CO2 emissions as part of a contracting process to design office space and supply furniture.
+{
+ "tender": {
+ "sustainability": [
+ {
+ "goal": "environmental.wasteReduction"
+ },
+ {
+ "goal": "environmental.carbonEmissionsReduction"
+ }
+ ]
+ }
+}
+If only the broad goal is known, create a single entry using the broad code:
+{
+ "tender": {
+ "sustainability": [
+ {
+ "goal": "environmental"
+ }
+ ]
+ }
+}
+If the sustainabilityGoal.csv codelist contains no appropriate code, create your own code. To create a narrower code, add a period to an existing code, followed by a camelCase word:
{
+ "tender": {
+ "sustainability": [
+ {
+ "goal": "environmental.CFCReduction"
+ }
+ ]
+ }
+}
+If there is a free-text description of the sustainability goal:
+{
+ "tender": {
+ "sustainability": [
+ {
+ "description": "This procurement procedure is aimed at reducing the environmental impact of Public Health Wales office space and furniture."
+ }
+ ]
+ }
+}
+The strategies are known
+Public Health Wales sets SPP-related technical specifications as part of a contracting process to design office space and supply furniture.
+{
+ "tender": {
+ "sustainability": [
+ {
+ "goal": "environmental.wasteReduction",
+ "strategies": [
+ "technicalSpecifications"
+ ]
+ },
+ {
+ "goal": "environmental.CO2Reduction",
+ "strategies": [
+ "technicalSpecifications"
+ ]
+ }
+ ]
+ }
+}
+If the goal is unknown or is sustainability in general, omit goal and set strategies only:
{
+ "tender": {
+ "sustainability": [
+ {
+ "strategies": [
+ "technicalSpecifications"
+ ]
+ }
+ ]
+ }
+}
+Background
+This extension uses the UNEP definition of SPP:
+++A process whereby public sector organizations meet their needs for goods, services, works and utilities in a way that achieves value for money on a whole life basis in terms of generating benefits not only to the organization, but also to society and the economy, whilst minimizing, and if possible, avoiding, damage to the environment.
+
The sustainabilityGoal.csv codelist is based on the goals defined in the OpenSPP toolkit and the EU's strategic procurement codelist.
The sustainabilityStrategy.csv codelist is based on the strategies described in the OpenSPP toolkit and the EU's strategic procurement codelist.
Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+This extension was originally discussed in https://github.com/open-contracting/standard/issues/1543.
+Changelog
+2023-04-12
+-
+
- Add
Sustainability.descriptionfield.
+ - Add codes to
sustainabilityGoal.csv: +-
+
- 'economic.innovativePurchase' +
- 'economic.processInnovationPromotion' +
- 'economic.productInnovationPromotion' +
- 'economic.researchDevelopmentActivities' +
- 'environmental.biodiversityProtectionRestoration' +
- 'environmental.circularEconomy' +
- 'environmental.circularEconomy' +
- 'environmental.climateChangeMitigation' +
- 'environmental.pollutionPrevention' +
- 'environmental.waterResourcesProtection' +
- 'social.accessibility' +
- 'social.disadvantagedEmploymentOpportunities' +
- 'social.ethnicEquality' +
- 'social.genderEquality' +
- 'social.humanRightsInSupplyChains' +
+ - Add codes to
sustainabilityStrategy.csv: +-
+
- 'euGPPCriteria' +
- 'nationalGPPCriteria' +
- 'otherGPPCriteria' +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/tariffs/1.1/README.md b/es/extensions/tariffs/1.1/README.md
new file mode 100644
index 000000000..6f5fe337a
--- /dev/null
+++ b/es/extensions/tariffs/1.1/README.md
@@ -0,0 +1,128 @@
+# Tarifas
+
+## Introducción
+
+Algunos contratos, en particular los contratos de Asociación Público Privada, incluyen acuerdos sobre las tarifas de usuario que se cobrarán por el uso de la infraestructura o los servicios a los que se refiere el contrato.
+
+Por ejemplo, un proyecto de Asociación Pública Privada para construir un puente puede establecer los peajes para coches y otros vehículos para cruzar el mismo.
+
+La extensión de tarifas permite establecer una lista estructurada de estos cargos.
+
+También incluye entradas de lista de códigos adicionales para la lista de códigos documentType para:
+
+- tariffs
+- tariffMethod
+- tariffReview
+- tariffIllustration
+
+## Modelado de tarifas
+
+El modelo de tarifas se basa en la extensión de métricas, permitiendo una lista de elementos tarrif, cada uno con un identificador, título, período, valor, unidades y un conjunto arbitrario de dimensiones.
+
+Por ejemplo, si el peaje para un puente de carretera varía según (a) el tipo de vehículo y (b) la hora del día; una implementación de la extensión de tarifas puede crear nuevos campos para `dimensions.vehicleType` y `dimensions.timeOfDay`, rellenando estos de acuerdo con las listas de códigos locales. En los casos de APP, estas dimensiones adicionales pueden reflejar las utilizadas en las secciones de demanda estimada y otras métricas.
+
+## Ejemplo
+
+El ejemplo siguiente muestra una tabla de tarifas muy sencilla, sin períodos ni unidades, pero con dos dimensiones. Las tarifas que se refieren a un determinado conjunto de fechas podrían tener un bloque `period`. Los que se refieren a una unidad particular (por ejemplo, toneladas) podrían tener esto indicado usando un bloque `unit`.
+
+```json
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "tariffs": [
+ {
+ "id": "1",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 1",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 0.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "2",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 2",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 2.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "3",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 3",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 6.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "4",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 4",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 8.0,
+ "currency": "GBP"
+ }
+ }
+ ]
+ }
+ ]
+}
+```
+
+## Entradas de lista de códigos
+
+Los siguientes tipos de documentos son introducidos por la extensión de tarifa
+
+- tariffs - Para proporcionar tarifas y horarios de precios.
+- tariffMethod - Para resumir el método por el cual se fijan las tarifas, y enlazar a la documentación detallada de los métodos para fijar tarifas. Esto puede incluir documentación escrita y hojas de cálculo con los modelos utilizados para calcular las tarifas.
+- tariffReview - Para resumir las disposiciones para la revisión y regulación de las tarifas, y enlazar con la documentación detallada que explique cómo se regulan las tarifas. Esto es importante para poder explicarles a los usuarios por qué están pagando lo que están pagando, y el alcance de los cambios en las estructuras de pago.
+- tariffIllustration - Para vincular a gráficos e informes sobre el cambio en el tiempo en los precios de las tarifas. Utilice el tipo de material de imagen relevante al vincular a gráficos PNG, JPEG o GIF para permitir que las aplicaciones muestren directamente este contenido.
+
+## Issues
+
+Reporte issues para esta extensión en el [repositorio de extensiones ocds](https://github.com/open-contracting/ocds-extensions/issues), poniendo el nombre de la extensión en el título del issue.
+
+## Registro de cambios
+
+### 2021-04-19
+
+- Agregar la columna Sección a la lista de códigos `+documentType.csv`.
+
+### 2020-06-04
+
+- Revisar las palabras normativas y no-normativas.
+
+### 2020-04-24
+
+- Agregar las propiedades `minProperties`, `minItems` y/o `minLength`.
+
+### 2019-03-20
+
+- Establecer `"uniqueItems ": true` en los campos matriz y agregar `"minLength": 1` en los campos de cadena obligatorios.
+- Hacer `Tariff.unit` no nulo, como `Item.unit`.
+- Hacer `Tariff.dimensions` no nulo (deshacer el cambio anterior).
+
+### 2018-05-08
+
+- Hacer que `Tariff.id` sea obligatorio para soportar el seguimiento de revisiones y [fusión de listas](https://standard.open-contracting.org/latest/es/schema/merging/#lists)
+
+### 2018-05-01
+
+- Hacer que `Tariff.dimensions` pueda ser nulo.
diff --git a/es/extensions/tariffs/1.1/codelists/+documentType.csv b/es/extensions/tariffs/1.1/codelists/+documentType.csv
new file mode 100644
index 000000000..cea0dd9c2
--- /dev/null
+++ b/es/extensions/tariffs/1.1/codelists/+documentType.csv
@@ -0,0 +1,5 @@
+Código,Título,Descripción,Sección
+tariffs,Tariffs,For providing tariff and pricing schedules.,contract
+tariffMethod,Tariff method,For summarizing the method by which tariffs are set and linking to detailed documentation of the methods for setting tariffs. This might include written documentation and spreadsheets providing the models used to calculate tariffs.,contract
+tariffReview,Tariff review,For summarizing the arrangements for the review and regulation of tariffs and linking to detailed documentation that covers how tariffs are regulated. This is important to explain to users why they are paying what they are paying and the scope for changes to payment structures.,contract
+tariffIllustration,Tariff illustration,For linking to graphs and reports on the change over time in tariff prices. Use the relevant image media type when linking to PNG or JPEG or GIF graphs to allow applications to directly display this content.,contract
diff --git a/es/extensions/tariffs/1.1/codelists/chargePaidBy.csv b/es/extensions/tariffs/1.1/codelists/chargePaidBy.csv
new file mode 100644
index 000000000..c2b269e9d
--- /dev/null
+++ b/es/extensions/tariffs/1.1/codelists/chargePaidBy.csv
@@ -0,0 +1,3 @@
+Código,Título,Descripción
+government,Government,The charge is paid by the government
+user,User,The charge is paid by businesses or citizens using the facilities provided by the contract
diff --git a/es/extensions/tariffs/1.1/codelists/index.html b/es/extensions/tariffs/1.1/codelists/index.html
new file mode 100644
index 000000000..1befb4b01
--- /dev/null
+++ b/es/extensions/tariffs/1.1/codelists/index.html
@@ -0,0 +1,363 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Sustainability +
+ ++ Adds fields to the tender and lot objects, to provide information related to Sustainable Public Procurement. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Sustainability +
+ +
+ The extension defines a new Sustainability object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ description
+
+ |
+ + Description + | +
+ A description of how the contracting process or lot incorporates Sustainable Public Procurement. + + |
+ + string + | +
+
+ goal
+
+ |
+ + Goal + | +
+ The sustainability goal pursued, from the sustainabilityGoal codelist. New sub-codes may be used outside those in the codelist, following the format [existing-code].[sub-code]. + + |
+ + string from open sustainabilityGoal codelist + | +
+
+ strategies
+
+ |
+ + Strategies + | +
+ The strategies used to pursue the sustainability goal(s), from the sustainabilityStrategy codelist. + + |
+ + array of strings from open sustainabilityStrategy codelist + | +
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasSustainability
+
+ |
+ + Has sustainability + | +
+ Whether the contracting process incorporates Sustainable Public Procurement. + + |
+ + boolean + | +
+
+ sustainability
+
+ |
+ + Sustainability + | +
+ Information about how the contracting process incorporates Sustainable Public Procurement. + + |
+ + array of Sustainability objects + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasSustainability
+
+ |
+ + Has sustainability + | +
+ Whether the lot incorporates Sustainable Public Procurement. + + |
+ + boolean + | +
+
+ sustainability
+
+ |
+ + Sustainability + | +
+ Information about how the lot incorporates Sustainable Public Procurement. + + |
+ + array of Sustainability objects + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/tariffs/1.1/extension.json b/es/extensions/tariffs/1.1/extension.json
new file mode 100644
index 000000000..ef23eff3e
--- /dev/null
+++ b/es/extensions/tariffs/1.1/extension.json
@@ -0,0 +1,27 @@
+{
+ "name": {
+ "en": "Tariffs",
+ "es": "Tarifas"
+ },
+ "description": {
+ "en": "Adds fields to the contract and implementation objects to capture details of the tariffs, tolls and user fees set out in the contract and in use throughout the life of the project.",
+ "es": "Agrega campos al contrato y objetos de implementaci\u00f3n para capturar los detalles de las tarifas, los peajes y las tarifas de los usuarios establecidos en el contrato y en uso durante la vida del proyecto."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/tariffs/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "codelists": [
+ "+documentType.csv",
+ "chargePaidBy.csv"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/tariffs/1.1/index.html b/es/extensions/tariffs/1.1/index.html
new file mode 100644
index 000000000..41b41bdf4
--- /dev/null
+++ b/es/extensions/tariffs/1.1/index.html
@@ -0,0 +1,429 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tarifas +
+ ++ Agrega campos al contrato y objetos de implementación para capturar los detalles de las tarifas, los peajes y las tarifas de los usuarios establecidos en el contrato y en uso durante la vida del proyecto. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +documentType.csv +
+ +
+ You can download the +documentType.csv file in English.
+
+ The extension adds these codes to the documentType.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ tariffs
+
+ |
+ + Tariffs + | +
+ For providing tariff and pricing schedules. + +
|
+
+
+ tariffMethod
+
+ |
+ + Tariff method + | +
+ For summarizing the method by which tariffs are set and linking to detailed documentation of the methods for setting tariffs. This might include written documentation and spreadsheets providing the models used to calculate tariffs. + +
|
+
+
+ tariffReview
+
+ |
+ + Tariff review + | +
+ For summarizing the arrangements for the review and regulation of tariffs and linking to detailed documentation that covers how tariffs are regulated. This is important to explain to users why they are paying what they are paying and the scope for changes to payment structures. + +
|
+
+
+ tariffIllustration
+
+ |
+ + Tariff illustration + | +
+ For linking to graphs and reports on the change over time in tariff prices. Use the relevant image media type when linking to PNG or JPEG or GIF graphs to allow applications to directly display this content. + +
|
+
+ chargePaidBy.csv +
+ +
+ You can download the chargePaidBy.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ government
+
+ |
+ + Government + | +
+ The charge is paid by the government + + |
+
+
+ user
+
+ |
+ + User + | +
+ The charge is paid by businesses or citizens using the facilities provided by the contract + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/tariffs/1.1/release-schema.json b/es/extensions/tariffs/1.1/release-schema.json
new file mode 100644
index 000000000..db1fc6ae5
--- /dev/null
+++ b/es/extensions/tariffs/1.1/release-schema.json
@@ -0,0 +1,153 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "tariffs": {
+ "title": "Tarifas",
+ "description": "Las tarifas que se aplican durante la vida del proyecto. Tambi\u00e9n se conoce como peajes o cargos de usuario. \u00c9stos pueden ser copiados inicialmente de la secci\u00f3n del contrato y luego actualizados con cualquier revisi\u00f3n durante la vida de la fase de implementaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Tariff"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "tariffs": {
+ "title": "Tarifas",
+ "description": "Las tarifas establecidas en los cronogramas del contrato. Tambi\u00e9n se conoce como impuestos o cargos de usuario. Las actualizaciones de las tarifas sobre la operaci\u00f3n del contrato pueden ser proporcionadas en la secci\u00f3n de implementaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Tariff"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Tariff": {
+ "title": "Tarifa",
+ "description": "Un art\u00edculo en una tabla de tarifas que establece un desglose del usuario o tasas gubernamentales que se pagan con relaci\u00f3n a cada unidad de un bien o servicios en particular.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador de tarifa",
+ "description": "Un identificador local para esta tarifa espec\u00edfica. Este campo se utiliza para realizar un seguimiento de las revisiones de una tarifa a trav\u00e9s de m\u00faltiples entregas de OCDS.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo de la tarifa",
+ "description": "El t\u00edtulo de esta tarifa.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "paidBy": {
+ "title": "Pagado por",
+ "description": "\u00bfSe trata de un cargo de usuario (pagado por empresas o ciudadanos que utilizan las facilidades proporcionadas por el contrato), o un cargo pagado por el gobierno?",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "chargePaidBy.csv",
+ "openCodelist": false,
+ "enum": [
+ "government",
+ "user",
+ null
+ ]
+ },
+ "period": {
+ "title": "Periodo de la tarifa",
+ "description": "El per\u00edodo al que se aplica esta tarifa.",
+ "$ref": "#/definitions/Period"
+ },
+ "value": {
+ "title": "Valor de la tarifa",
+ "description": "El precio por unidad de esta tarifa.",
+ "$ref": "#/definitions/Value"
+ },
+ "unit": {
+ "title": "Unidad de las tarifas",
+ "description": "La unidad contra la cual se cobra esta tarifa.",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Nombre de la unidad",
+ "description": "El nombre de la unidad a la que se cobra la tarifa. P.ej. Toneladas",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "scheme": {
+ "title": "Esquema",
+ "description": "La lista de la que se toman los identificadores de las unidades de medida. Se recomienda el uso del esquema 'UNCEFACT' para la lista de la Recomendaci\u00f3n 20 de las UN/CEFACT de \"C\u00f3digos de unidades de medida utilizados en el comercio internacional\".",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "El identificador de la lista de c\u00f3digos se hace referencia en la propiedad de esquema. Por ejemplo, con UNCEFACT, este es el valor de la columna \"Common Code\". A partir de este identificador, las aplicaciones pueden buscar el nombre o s\u00edmbolo legible para humanos para esta unidad de medida.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "uri": {
+ "title": "URI",
+ "description": "Si el esquema utilizado provee una URI legible por computadora para esta unidad de medici\u00f3n, \u00e9sta puede proporcionarse.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ },
+ "minProperties": 1
+ },
+ "dimensions": {
+ "title": "Dimensiones de la tarifa",
+ "description": "Utilizado para capturar los diferentes desgloses en los cargos de la tarifa. Cualquier n\u00famero de dimensiones se puede registrar dentro de este objeto. Los nombres de dimensiones deben seguir las convenciones de OCDS de camelCase.",
+ "type": "object",
+ "patternProperties": {
+ "^.*": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "notes": {
+ "title": "Notas sobre las tarifas",
+ "description": "Cualquier nota sobre esta partida de tarifas. Esto puede incluir informaci\u00f3n para aclaraci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/tariffs/1.1/schema/index.html b/es/extensions/tariffs/1.1/schema/index.html
new file mode 100644
index 000000000..f33eeeb23
--- /dev/null
+++ b/es/extensions/tariffs/1.1/schema/index.html
@@ -0,0 +1,541 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tarifas +
+ ++ Agrega campos al contrato y objetos de implementación para capturar los detalles de las tarifas, los peajes y las tarifas de los usuarios establecidos en el contrato y en uso durante la vida del proyecto. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Introducción
+Algunos contratos, en particular los contratos de Asociación Público Privada, incluyen acuerdos sobre las tarifas de usuario que se cobrarán por el uso de la infraestructura o los servicios a los que se refiere el contrato.
+Por ejemplo, un proyecto de Asociación Pública Privada para construir un puente puede establecer los peajes para coches y otros vehículos para cruzar el mismo.
+La extensión de tarifas permite establecer una lista estructurada de estos cargos.
+También incluye entradas de lista de códigos adicionales para la lista de códigos documentType para:
+-
+
- tariffs +
- tariffMethod +
- tariffReview +
- tariffIllustration +
Modelado de tarifas
+El modelo de tarifas se basa en la extensión de métricas, permitiendo una lista de elementos tarrif, cada uno con un identificador, título, período, valor, unidades y un conjunto arbitrario de dimensiones.
+Por ejemplo, si el peaje para un puente de carretera varía según (a) el tipo de vehículo y (b) la hora del día; una implementación de la extensión de tarifas puede crear nuevos campos para dimensions.vehicleType y dimensions.timeOfDay, rellenando estos de acuerdo con las listas de códigos locales. En los casos de APP, estas dimensiones adicionales pueden reflejar las utilizadas en las secciones de demanda estimada y otras métricas.
Ejemplo
+El ejemplo siguiente muestra una tabla de tarifas muy sencilla, sin períodos ni unidades, pero con dos dimensiones. Las tarifas que se refieren a un determinado conjunto de fechas podrían tener un bloque period. Los que se refieren a una unidad particular (por ejemplo, toneladas) podrían tener esto indicado usando un bloque unit.
{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "tariffs": [
+ {
+ "id": "1",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 1",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 0.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "2",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 2",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 2.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "3",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 3",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 6.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "4",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 4",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 8.0,
+ "currency": "GBP"
+ }
+ }
+ ]
+ }
+ ]
+}
+Entradas de lista de códigos
+Los siguientes tipos de documentos son introducidos por la extensión de tarifa
+-
+
- tariffs - Para proporcionar tarifas y horarios de precios. +
- tariffMethod - Para resumir el método por el cual se fijan las tarifas, y enlazar a la documentación detallada de los métodos para fijar tarifas. Esto puede incluir documentación escrita y hojas de cálculo con los modelos utilizados para calcular las tarifas. +
- tariffReview - Para resumir las disposiciones para la revisión y regulación de las tarifas, y enlazar con la documentación detallada que explique cómo se regulan las tarifas. Esto es importante para poder explicarles a los usuarios por qué están pagando lo que están pagando, y el alcance de los cambios en las estructuras de pago. +
- tariffIllustration - Para vincular a gráficos e informes sobre el cambio en el tiempo en los precios de las tarifas. Utilice el tipo de material de imagen relevante al vincular a gráficos PNG, JPEG o GIF para permitir que las aplicaciones muestren directamente este contenido. +
Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2021-04-19
+-
+
- Agregar la columna Sección a la lista de códigos
+documentType.csv.
+
2020-06-04
+-
+
- Revisar las palabras normativas y no-normativas. +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-03-20
+-
+
- Establecer
"uniqueItems ": trueen los campos matriz y agregar"minLength": 1en los campos de cadena obligatorios.
+ - Hacer
Tariff.unitno nulo, comoItem.unit.
+ - Hacer
Tariff.dimensionsno nulo (deshacer el cambio anterior).
+
2018-05-08
+-
+
- Hacer que
Tariff.idsea obligatorio para soportar el seguimiento de revisiones y fusión de listas
+
2018-05-01
+-
+
- Hacer que
Tariff.dimensionspueda ser nulo.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/tariffs/index.html b/es/extensions/tariffs/index.html
new file mode 100644
index 000000000..073cc82d4
--- /dev/null
+++ b/es/extensions/tariffs/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tarifas +
+ ++ Agrega campos al contrato y objetos de implementación para capturar los detalles de las tarifas, los peajes y las tarifas de los usuarios establecidos en el contrato y en uso durante la vida del proyecto. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ tariffs
+
+ |
+ + Tarifas + | +
+ Las tarifas que se aplican durante la vida del proyecto. También se conoce como peajes o cargos de usuario. Éstos pueden ser copiados inicialmente de la sección del contrato y luego actualizados con cualquier revisión durante la vida de la fase de implementación. + + |
+ + array of Tariff objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ tariffs
+
+ |
+ + Tarifas + | +
+ Las tarifas establecidas en los cronogramas del contrato. También se conoce como impuestos o cargos de usuario. Las actualizaciones de las tarifas sobre la operación del contrato pueden ser proporcionadas en la sección de implementación. + + |
+ + array of Tariff objects + | +
+ Tariff +
+ +
+ The extension defines a new Tariff object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador de tarifa + | +
+ Un identificador local para esta tarifa específica. Este campo se utiliza para realizar un seguimiento de las revisiones de una tarifa a través de múltiples entregas de OCDS. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título de la tarifa + | +
+ El título de esta tarifa. + + |
+ + string + | +
+
+ paidBy
+
+ |
+ + Pagado por + | +
+ ¿Se trata de un cargo de usuario (pagado por empresas o ciudadanos que utilizan las facilidades proporcionadas por el contrato), o un cargo pagado por el gobierno? + + |
+ + string from closed chargePaidBy codelist + | +
+
+ period
+
+ |
+ + Periodo de la tarifa + | +
+ El período al que se aplica esta tarifa. + + |
+ + Period object + | +
+
+ value
+
+ |
+ + Valor de la tarifa + | +
+ El precio por unidad de esta tarifa. + + |
+ + Value object + | +
+
+ unit
+
+ |
+ + Unidad de las tarifas + | +
+ La unidad contra la cual se cobra esta tarifa. + + |
+ + object + | +
+
+ unit.
+ |
+ + Nombre de la unidad + | +
+ El nombre de la unidad a la que se cobra la tarifa. P.ej. Toneladas + + |
+ + string + | +
+
+ unit.
+ |
+ + Esquema + | +
+ La lista de la que se toman los identificadores de las unidades de medida. Se recomienda el uso del esquema 'UNCEFACT' para la lista de la Recomendación 20 de las UN/CEFACT de "Códigos de unidades de medida utilizados en el comercio internacional". + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ unit.
+ |
+ + ID + | +
+ El identificador de la lista de códigos se hace referencia en la propiedad de esquema. Por ejemplo, con UNCEFACT, este es el valor de la columna "Common Code". A partir de este identificador, las aplicaciones pueden buscar el nombre o símbolo legible para humanos para esta unidad de medida. + + |
+ + string + | +
+
+ unit.
+ |
+ + URI + | +
+ Si el esquema utilizado provee una URI legible por computadora para esta unidad de medición, ésta puede proporcionarse. + + |
+ + string + | +
+
+ dimensions
+
+ |
+ + Dimensiones de la tarifa + | +
+ Utilizado para capturar los diferentes desgloses en los cargos de la tarifa. Cualquier número de dimensiones se puede registrar dentro de este objeto. Los nombres de dimensiones deben seguir las convenciones de OCDS de camelCase. + + |
+ + object + | +
+
+ dimensions.
+ |
+ + + | ++ + | ++ string + | +
+
+ notes
+
+ |
+ + Notas sobre las tarifas + | +
+ Cualquier nota sobre esta partida de tarifas. Esto puede incluir información para aclaración. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/tariffs/1.1/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/tariffs/master/index.html b/es/extensions/tariffs/master/index.html
new file mode 100644
index 000000000..c5153271b
--- /dev/null
+++ b/es/extensions/tariffs/master/index.html
@@ -0,0 +1,430 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tarifas +
+ ++ Agrega campos al contrato y objetos de implementación para capturar los detalles de las tarifas, los peajes y las tarifas de los usuarios establecidos en el contrato y en uso durante la vida del proyecto. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +documentType.csv +
+ +
+ You can download the +documentType.csv file in English.
+
+ The extension adds these codes to the documentType.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ tariffs
+
+ |
+ + Tariffs + | +
+ For providing tariff and pricing schedules. + +
|
+
+
+ tariffMethod
+
+ |
+ + Tariff method + | +
+ For summarizing the method by which tariffs are set and linking to detailed documentation of the methods for setting tariffs. This might include written documentation and spreadsheets providing the models used to calculate tariffs. + +
|
+
+
+ tariffReview
+
+ |
+ + Tariff review + | +
+ For summarizing the arrangements for the review and regulation of tariffs and linking to detailed documentation that covers how tariffs are regulated. This is important to explain to users why they are paying what they are paying and the scope for changes to payment structures. + +
|
+
+
+ tariffIllustration
+
+ |
+ + Tariff illustration + | +
+ For linking to graphs and reports on the change over time in tariff prices. Use the relevant image media type when linking to PNG or JPEG or GIF graphs to allow applications to directly display this content. + +
|
+
+ chargePaidBy.csv +
+ +
+ You can download the chargePaidBy.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ government
+
+ |
+ + Government + | +
+ The charge is paid by the government + + |
+
+
+ user
+
+ |
+ + User + | +
+ The charge is paid by businesses or citizens using the facilities provided by the contract + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/tariffs/master/release-schema.json b/es/extensions/tariffs/master/release-schema.json
new file mode 100644
index 000000000..db1fc6ae5
--- /dev/null
+++ b/es/extensions/tariffs/master/release-schema.json
@@ -0,0 +1,153 @@
+{
+ "definitions": {
+ "Implementation": {
+ "properties": {
+ "tariffs": {
+ "title": "Tarifas",
+ "description": "Las tarifas que se aplican durante la vida del proyecto. Tambi\u00e9n se conoce como peajes o cargos de usuario. \u00c9stos pueden ser copiados inicialmente de la secci\u00f3n del contrato y luego actualizados con cualquier revisi\u00f3n durante la vida de la fase de implementaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Tariff"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Contract": {
+ "properties": {
+ "tariffs": {
+ "title": "Tarifas",
+ "description": "Las tarifas establecidas en los cronogramas del contrato. Tambi\u00e9n se conoce como impuestos o cargos de usuario. Las actualizaciones de las tarifas sobre la operaci\u00f3n del contrato pueden ser proporcionadas en la secci\u00f3n de implementaci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Tariff"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "Tariff": {
+ "title": "Tarifa",
+ "description": "Un art\u00edculo en una tabla de tarifas que establece un desglose del usuario o tasas gubernamentales que se pagan con relaci\u00f3n a cada unidad de un bien o servicios en particular.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "Identificador de tarifa",
+ "description": "Un identificador local para esta tarifa espec\u00edfica. Este campo se utiliza para realizar un seguimiento de las revisiones de una tarifa a trav\u00e9s de m\u00faltiples entregas de OCDS.",
+ "type": "string",
+ "minLength": 1
+ },
+ "title": {
+ "title": "T\u00edtulo de la tarifa",
+ "description": "El t\u00edtulo de esta tarifa.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "paidBy": {
+ "title": "Pagado por",
+ "description": "\u00bfSe trata de un cargo de usuario (pagado por empresas o ciudadanos que utilizan las facilidades proporcionadas por el contrato), o un cargo pagado por el gobierno?",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "chargePaidBy.csv",
+ "openCodelist": false,
+ "enum": [
+ "government",
+ "user",
+ null
+ ]
+ },
+ "period": {
+ "title": "Periodo de la tarifa",
+ "description": "El per\u00edodo al que se aplica esta tarifa.",
+ "$ref": "#/definitions/Period"
+ },
+ "value": {
+ "title": "Valor de la tarifa",
+ "description": "El precio por unidad de esta tarifa.",
+ "$ref": "#/definitions/Value"
+ },
+ "unit": {
+ "title": "Unidad de las tarifas",
+ "description": "La unidad contra la cual se cobra esta tarifa.",
+ "type": "object",
+ "properties": {
+ "name": {
+ "title": "Nombre de la unidad",
+ "description": "El nombre de la unidad a la que se cobra la tarifa. P.ej. Toneladas",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "scheme": {
+ "title": "Esquema",
+ "description": "La lista de la que se toman los identificadores de las unidades de medida. Se recomienda el uso del esquema 'UNCEFACT' para la lista de la Recomendaci\u00f3n 20 de las UN/CEFACT de \"C\u00f3digos de unidades de medida utilizados en el comercio internacional\".",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "unitClassificationScheme.csv",
+ "openCodelist": true,
+ "minLength": 1
+ },
+ "id": {
+ "title": "ID",
+ "description": "El identificador de la lista de c\u00f3digos se hace referencia en la propiedad de esquema. Por ejemplo, con UNCEFACT, este es el valor de la columna \"Common Code\". A partir de este identificador, las aplicaciones pueden buscar el nombre o s\u00edmbolo legible para humanos para esta unidad de medida.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "uri": {
+ "title": "URI",
+ "description": "Si el esquema utilizado provee una URI legible por computadora para esta unidad de medici\u00f3n, \u00e9sta puede proporcionarse.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "uri"
+ }
+ },
+ "minProperties": 1
+ },
+ "dimensions": {
+ "title": "Dimensiones de la tarifa",
+ "description": "Utilizado para capturar los diferentes desgloses en los cargos de la tarifa. Cualquier n\u00famero de dimensiones se puede registrar dentro de este objeto. Los nombres de dimensiones deben seguir las convenciones de OCDS de camelCase.",
+ "type": "object",
+ "patternProperties": {
+ "^.*": {
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "notes": {
+ "title": "Notas sobre las tarifas",
+ "description": "Cualquier nota sobre esta partida de tarifas. Esto puede incluir informaci\u00f3n para aclaraci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/tariffs/master/schema/index.html b/es/extensions/tariffs/master/schema/index.html
new file mode 100644
index 000000000..8ae498be1
--- /dev/null
+++ b/es/extensions/tariffs/master/schema/index.html
@@ -0,0 +1,542 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tarifas +
+ ++ Agrega campos al contrato y objetos de implementación para capturar los detalles de las tarifas, los peajes y las tarifas de los usuarios establecidos en el contrato y en uso durante la vida del proyecto. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Introducción
+Algunos contratos, en particular los contratos de Asociación Público Privada, incluyen acuerdos sobre las tarifas de usuario que se cobrarán por el uso de la infraestructura o los servicios a los que se refiere el contrato.
+Por ejemplo, un proyecto de Asociación Pública Privada para construir un puente puede establecer los peajes para coches y otros vehículos para cruzar el mismo.
+La extensión de tarifas permite establecer una lista estructurada de estos cargos.
+También incluye entradas de lista de códigos adicionales para la lista de códigos documentType para:
+-
+
- tariffs +
- tariffMethod +
- tariffReview +
- tariffIllustration +
Modelado de tarifas
+El modelo de tarifas se basa en la extensión de métricas, permitiendo una lista de elementos tarrif, cada uno con un identificador, título, período, valor, unidades y un conjunto arbitrario de dimensiones.
+Por ejemplo, si el peaje para un puente de carretera varía según (a) el tipo de vehículo y (b) la hora del día; una implementación de la extensión de tarifas puede crear nuevos campos para dimensions.vehicleType y dimensions.timeOfDay, rellenando estos de acuerdo con las listas de códigos locales. En los casos de APP, estas dimensiones adicionales pueden reflejar las utilizadas en las secciones de demanda estimada y otras métricas.
Ejemplo
+El ejemplo siguiente muestra una tabla de tarifas muy sencilla, sin períodos ni unidades, pero con dos dimensiones. Las tarifas que se refieren a un determinado conjunto de fechas podrían tener un bloque period. Los que se refieren a una unidad particular (por ejemplo, toneladas) podrían tener esto indicado usando un bloque unit.
{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "tariffs": [
+ {
+ "id": "1",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 1",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 0.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "2",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 2",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 2.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "3",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 3",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 6.0,
+ "currency": "GBP"
+ }
+ },
+ {
+ "id": "4",
+ "title": "Standard Toll",
+ "dimensions": {
+ "vehicleType": "Class 4",
+ "registration": "No registration"
+ },
+ "value": {
+ "amount": 8.0,
+ "currency": "GBP"
+ }
+ }
+ ]
+ }
+ ]
+}
+Entradas de lista de códigos
+Los siguientes tipos de documentos son introducidos por la extensión de tarifa
+-
+
- tariffs - Para proporcionar tarifas y horarios de precios. +
- tariffMethod - Para resumir el método por el cual se fijan las tarifas, y enlazar a la documentación detallada de los métodos para fijar tarifas. Esto puede incluir documentación escrita y hojas de cálculo con los modelos utilizados para calcular las tarifas. +
- tariffReview - Para resumir las disposiciones para la revisión y regulación de las tarifas, y enlazar con la documentación detallada que explique cómo se regulan las tarifas. Esto es importante para poder explicarles a los usuarios por qué están pagando lo que están pagando, y el alcance de los cambios en las estructuras de pago. +
- tariffIllustration - Para vincular a gráficos e informes sobre el cambio en el tiempo en los precios de las tarifas. Utilice el tipo de material de imagen relevante al vincular a gráficos PNG, JPEG o GIF para permitir que las aplicaciones muestren directamente este contenido. +
Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2021-04-19
+-
+
- Agregar la columna Sección a la lista de códigos
+documentType.csv.
+
2020-06-04
+-
+
- Revisar las palabras normativas y no-normativas. +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
2019-03-20
+-
+
- Establecer
"uniqueItems ": trueen los campos matriz y agregar"minLength": 1en los campos de cadena obligatorios.
+ - Hacer
Tariff.unitno nulo, comoItem.unit.
+ - Hacer
Tariff.dimensionsno nulo (deshacer el cambio anterior).
+
2018-05-08
+-
+
- Hacer que
Tariff.idsea obligatorio para soportar el seguimiento de revisiones y fusión de listas
+
2018-05-01
+-
+
- Hacer que
Tariff.dimensionspueda ser nulo.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/techniques/index.html b/es/extensions/techniques/index.html
new file mode 100644
index 000000000..8950c9e9e
--- /dev/null
+++ b/es/extensions/techniques/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Tarifas +
+ ++ Agrega campos al contrato y objetos de implementación para capturar los detalles de las tarifas, los peajes y las tarifas de los usuarios establecidos en el contrato y en uso durante la vida del proyecto. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Implementation +
+ +
+ The extension defines these fields in the Implementation object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ tariffs
+
+ |
+ + Tarifas + | +
+ Las tarifas que se aplican durante la vida del proyecto. También se conoce como peajes o cargos de usuario. Éstos pueden ser copiados inicialmente de la sección del contrato y luego actualizados con cualquier revisión durante la vida de la fase de implementación. + + |
+ + array of Tariff objects + | +
+ Contract +
+ +
+ The extension defines these fields in the Contract object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ tariffs
+
+ |
+ + Tarifas + | +
+ Las tarifas establecidas en los cronogramas del contrato. También se conoce como impuestos o cargos de usuario. Las actualizaciones de las tarifas sobre la operación del contrato pueden ser proporcionadas en la sección de implementación. + + |
+ + array of Tariff objects + | +
+ Tariff +
+ +
+ The extension defines a new Tariff object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + Identificador de tarifa + | +
+ Un identificador local para esta tarifa específica. Este campo se utiliza para realizar un seguimiento de las revisiones de una tarifa a través de múltiples entregas de OCDS. + + |
+ + string + | +
+
+ title
+
+ |
+ + Título de la tarifa + | +
+ El título de esta tarifa. + + |
+ + string + | +
+
+ paidBy
+
+ |
+ + Pagado por + | +
+ ¿Se trata de un cargo de usuario (pagado por empresas o ciudadanos que utilizan las facilidades proporcionadas por el contrato), o un cargo pagado por el gobierno? + + |
+ + string from closed chargePaidBy codelist + | +
+
+ period
+
+ |
+ + Periodo de la tarifa + | +
+ El período al que se aplica esta tarifa. + + |
+ + Period object + | +
+
+ value
+
+ |
+ + Valor de la tarifa + | +
+ El precio por unidad de esta tarifa. + + |
+ + Value object + | +
+
+ unit
+
+ |
+ + Unidad de las tarifas + | +
+ La unidad contra la cual se cobra esta tarifa. + + |
+ + object + | +
+
+ unit.
+ |
+ + Nombre de la unidad + | +
+ El nombre de la unidad a la que se cobra la tarifa. P.ej. Toneladas + + |
+ + string + | +
+
+ unit.
+ |
+ + Esquema + | +
+ La lista de la que se toman los identificadores de las unidades de medida. Se recomienda el uso del esquema 'UNCEFACT' para la lista de la Recomendación 20 de las UN/CEFACT de "Códigos de unidades de medida utilizados en el comercio internacional". + + |
+ + string from open unitClassificationScheme codelist + | +
+
+ unit.
+ |
+ + ID + | +
+ El identificador de la lista de códigos se hace referencia en la propiedad de esquema. Por ejemplo, con UNCEFACT, este es el valor de la columna "Common Code". A partir de este identificador, las aplicaciones pueden buscar el nombre o símbolo legible para humanos para esta unidad de medida. + + |
+ + string + | +
+
+ unit.
+ |
+ + URI + | +
+ Si el esquema utilizado provee una URI legible por computadora para esta unidad de medición, ésta puede proporcionarse. + + |
+ + string + | +
+
+ dimensions
+
+ |
+ + Dimensiones de la tarifa + | +
+ Utilizado para capturar los diferentes desgloses en los cargos de la tarifa. Cualquier número de dimensiones se puede registrar dentro de este objeto. Los nombres de dimensiones deben seguir las convenciones de OCDS de camelCase. + + |
+ + object + | +
+
+ dimensions.
+ |
+ + + | ++ + | ++ string + | +
+
+ notes
+
+ |
+ + Notas sobre las tarifas + | +
+ Cualquier nota sobre esta partida de tarifas. Esto puede incluir información para aclaración. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/techniques/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/techniques/master/extension.json b/es/extensions/techniques/master/extension.json
new file mode 100644
index 000000000..902a884d0
--- /dev/null
+++ b/es/extensions/techniques/master/extension.json
@@ -0,0 +1,31 @@
+{
+ "name": {
+ "en": "Techniques",
+ "es": "T\u00e9cnicas"
+ },
+ "description": {
+ "en": "Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions.",
+ "es": "Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/techniques/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "dynamicPurchasingSystemType.csv",
+ "dynamicPurchasingSystemStatus.csv",
+ "frameworkAgreementMethod.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ },
+ "testDependencies": [
+ "https://raw.githubusercontent.com/open-contracting-extensions/ocds_lots_extension/master/extension.json"
+ ]
+}
diff --git a/es/extensions/techniques/master/index.html b/es/extensions/techniques/master/index.html
new file mode 100644
index 000000000..10cc732c9
--- /dev/null
+++ b/es/extensions/techniques/master/index.html
@@ -0,0 +1,489 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Técnicas +
+ ++ Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ dynamicPurchasingSystemStatus.csv +
+ +
+ You can download the dynamicPurchasingSystemStatus.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ pending
+
+ |
+ + Pending + | +
+ The DPS has not yet started. + + |
+
+
+ active
+
+ |
+ + Active + | +
+ The DPS has started. + + |
+
+
+ cancelled
+
+ |
+ + Cancelled + | +
+ The DPS has been cancelled prior to starting. + + |
+
+
+ terminated
+
+ |
+ + Terminated + | +
+ The DPS had started, and has now come to a close. This might be due to its successful completion, or might be early termination due to some non-completion. + + |
+
+ dynamicPurchasingSystemType.csv +
+ +
+ You can download the dynamicPurchasingSystemType.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ open
+
+ |
+ + Open + | +
+ The dynamic purchasing system can also be used by buyers not listed in the contracting process. + + |
+
+
+ closed
+
+ |
+ + Closed + | +
+ The dynamic purchasing system can only be used by buyers listed in the contracting process. + + |
+
+ frameworkAgreementMethod.csv +
+ +
+ You can download the frameworkAgreementMethod.csv file in English.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ withReopeningCompetition
+
+ |
+ + With reopening of competition + | +
+ Contracts are awarded by reopening the competition (e.g. mini-competition or mini-tender). + + |
+
+
+ withoutReopeningCompetition
+
+ |
+ + Without reopening of competition + | +
+ Contracts are awarded without the reopening of competition (e.g. direct call-off or direct award). + + |
+
+
+ withAndWithoutReopeningCompetition
+
+ |
+ + With and without reopening of competition + | +
+ Contracts are awarded both with and without the reopening of competition. + + |
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/techniques/master/release-schema.json b/es/extensions/techniques/master/release-schema.json
new file mode 100644
index 000000000..11547b822
--- /dev/null
+++ b/es/extensions/techniques/master/release-schema.json
@@ -0,0 +1,229 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "techniques": {
+ "title": "T\u00e9cnicas",
+ "description": "Informaci\u00f3n sobre el uso de t\u00e9cnicas, como acuerdos marco, sistemas de compra din\u00e1mica y subastas electr\u00f3nicas.",
+ "$ref": "#/definitions/Techniques"
+ },
+ "competitive": {
+ "title": "Is the framework agreement call-off competitive?",
+ "description": "Whether this call-off is competitive or not.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ }
+ }
+ },
+ "Lot": {
+ "properties": {
+ "techniques": {
+ "title": "T\u00e9cnicas",
+ "description": "Informaci\u00f3n sobre el uso de t\u00e9cnicas, como acuerdos marco, sistemas de compra din\u00e1mica y subastas electr\u00f3nicas.",
+ "$ref": "#/definitions/Techniques"
+ }
+ }
+ },
+ "LotGroup": {
+ "properties": {
+ "techniques": {
+ "title": "T\u00e9cnicas",
+ "description": "Informaci\u00f3n sobre el uso de t\u00e9cnicas, como acuerdos marco, sistemas de compra din\u00e1mica y subastas electr\u00f3nicas.",
+ "$ref": "#/definitions/Techniques"
+ }
+ }
+ },
+ "Techniques": {
+ "title": "T\u00e9cnicas",
+ "description": "Informaci\u00f3n sobre el uso de t\u00e9cnicas, como acuerdos marco, sistemas de compra din\u00e1mica y subastas electr\u00f3nicas.",
+ "type": "object",
+ "properties": {
+ "hasFrameworkAgreement": {
+ "title": "Acuerdo marco involucrado",
+ "description": "Si se trata de un acuerdo marco.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "frameworkAgreement": {
+ "title": "Acuerdo marco",
+ "description": "Informaci\u00f3n sobre el acuerdo marco.",
+ "$ref": "#/definitions/FrameworkAgreement"
+ },
+ "hasDynamicPurchasingSystem": {
+ "title": "Sistema de compra din\u00e1mica involucrado",
+ "description": "Si se trata de un sistema de compra din\u00e1mica.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "dynamicPurchasingSystem": {
+ "title": "Sistema de compra din\u00e1mica",
+ "description": "Informaci\u00f3n sobre el sistema de compra din\u00e1mica.",
+ "$ref": "#/definitions/DynamicPurchasingSystem"
+ },
+ "hasElectronicAuction": {
+ "title": "Subasta electr\u00f3nica utilizada",
+ "description": "Si se utiliza una subasta electr\u00f3nica.",
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "electronicAuction": {
+ "title": "Subasta electr\u00f3nica",
+ "description": "Informaci\u00f3n sobre la subasta electr\u00f3nica.",
+ "$ref": "#/definitions/ElectronicAuction"
+ }
+ },
+ "minProperties": 1
+ },
+ "FrameworkAgreement": {
+ "title": "Acuerdo marco",
+ "description": "Informaci\u00f3n sobre el acuerdo marco.",
+ "type": "object",
+ "properties": {
+ "minimumParticipants": {
+ "title": "N\u00famero m\u00ednimo de participantes",
+ "description": "El n\u00famero m\u00ednimo de participantes en el acuerdo marco",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "maximumParticipants": {
+ "title": "N\u00famero m\u00e1ximo de participantes",
+ "description": "El n\u00famero m\u00e1ximo de participantes en el acuerdo marco. Si no hay un m\u00e1ximo, establecerlo en 1e9999 (que analiza hasta infinito).",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "method": {
+ "title": "M\u00e9todo",
+ "description": "Si los contratos se adjudican con, sin o ambos con y sin re-apertura del concurso.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "frameworkAgreementMethod.csv",
+ "openCodelist": false,
+ "enum": [
+ "withReopeningCompetition",
+ "withoutReopeningCompetition",
+ "withAndWithoutReopeningCompetition",
+ null
+ ]
+ },
+ "periodRationale": {
+ "title": "Duraci\u00f3n razonable",
+ "description": "La justificaci\u00f3n de casos excepcionales cuando la duraci\u00f3n de un acuerdo marco excede los l\u00edmites legales.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "buyerCategories": {
+ "title": "Categor\u00edas de compradores",
+ "description": "Cualquier categor\u00eda adicional de compradores que participe en el acuerdo marco y que no se mencione por su nombre (por ejemplo, \"todos los hospitales de la regi\u00f3n de la Toscana\"). ",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "value": {
+ "title": "Valor",
+ "description": "El valor total estimado superior del acuerdo marco.",
+ "$ref": "#/definitions/Value"
+ },
+ "period": {
+ "title": "Periodo",
+ "description": "El per\u00edodo durante el cual se estima que el acuerdo marco estar\u00e1 activo.",
+ "$ref": "#/definitions/Period"
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Una descripci\u00f3n resumida del acuerdo marco. Esto complementa cualquier informaci\u00f3n estructurada proporcionada utilizando los otros campos.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "DynamicPurchasingSystem": {
+ "title": "Sistema de compra din\u00e1mica",
+ "description": "Informaci\u00f3n sobre el sistema de compra din\u00e1mica.",
+ "type": "object",
+ "properties": {
+ "type": {
+ "title": "Tipo",
+ "description": "En el caso de las centrales de compras, si el sistema de compra din\u00e1mica puede ser utilizado por compradores que no figuran en el proceso de contrataci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "dynamicPurchasingSystemType.csv",
+ "openCodelist": false,
+ "enum": [
+ "open",
+ "closed",
+ null
+ ]
+ },
+ "status": {
+ "title": "Estado",
+ "description": "El estado del sistema de compra din\u00e1mica.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "codelist": "dynamicPurchasingSystemStatus.csv",
+ "openCodelist": false,
+ "enum": [
+ "pending",
+ "active",
+ "cancelled",
+ "terminated",
+ null
+ ]
+ }
+ },
+ "minProperties": 1
+ },
+ "ElectronicAuction": {
+ "title": "Subasta electr\u00f3nica",
+ "description": "Informaci\u00f3n sobre la subasta electr\u00f3nica.",
+ "type": "object",
+ "properties": {
+ "url": {
+ "title": "URL",
+ "description": "La direcci\u00f3n de Internet de la subasta electr\u00f3nica.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "description": {
+ "title": "Descripci\u00f3n",
+ "description": "Cualquier informaci\u00f3n adicional sobre la subasta electr\u00f3nica.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/techniques/master/schema/index.html b/es/extensions/techniques/master/schema/index.html
new file mode 100644
index 000000000..c67ea0d6b
--- /dev/null
+++ b/es/extensions/techniques/master/schema/index.html
@@ -0,0 +1,797 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Técnicas +
+ ++ Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. Also, adds a field to the tender object in a framework agreement call-off to indicate if it is competitive or direct.
+Guía
+value y period del acuerdo marco
+Los campos value y period de los objetos FrameworkAgreement solo deben usarse si una fuente de datos proporciona valores y períodos tanto para el contrato / lote como para el acuerdo marco, como TED XML Schema R2.08. De lo contrario:
-
+
- Si una adquisición no está dividida en lotes, utilice los campos
tender.valueytender.contractPeriod.
+ - Si una adquisición se divide en lotes, utilice los campos
valueycontractPeriodde los objetosLot.
+
method del acuerdo marco
+Estos son los posibles valores del campo method de un acuerdo marco y sus sinónimos más comunes:
-
+
- withoutReopeningCompetition: cancelaciones +
- withReopeningCompetition: mini-competencias +
- withAndWithoutReopeningCompetition: cancelaciones y mini-competencias +
Contexto legal
+In the European Union, this extension's fields correspond to eForms BG-706 (Techniques), BG-157 (Group Framework Maximum Value and BT-271 (Framework Maximum Value). For correspondences to eForms fields, see OCDS for eForms. For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplos
+Acuerdo marco
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "techniques": {
+ "hasFrameworkAgreement": true,
+ "frameworkAgreement": {
+ "minimumParticipants": 2,
+ "maximumParticipants": 100,
+ "method": "withoutReopeningCompetition",
+ "periodRationale": "<A good justification>",
+ "buyerCategories": "all hospitals in the Tuscany region",
+ "value": {
+ "amount": 240000,
+ "currency": "EUR"
+ },
+ "period": {
+ "durationInDays": 730
+ },
+ "description": "Call offs are estimated to be organized every 3 months, with an average value of 60,000 euros per contract."
+ }
+ }
+ }
+ ]
+ }
+}
+Sistema de compra dinámica
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "techniques": {
+ "hasDynamicPurchasingSystem": true,
+ "dynamicPurchasingSystem": {
+ "type": "closed",
+ "status": "active"
+ }
+ }
+ }
+ ]
+ }
+}
+Subasta electrónica
+{
+ "tender": {
+ "lots": [
+ {
+ "id": "1",
+ "techniques": {
+ "hasElectronicAuction": true,
+ "electronicAuction": {
+ "url": "https://example.com/auction/1",
+ "description": "<Any relevant details>"
+ }
+ }
+ }
+ ]
+ }
+}
+Direct call-off
+{
+ "tender": {
+ "id": "2421-1016-CM20",
+ "procuringEntity": {
+ "name": "I.MUNICIPALIDAD DE CONCEPCION | DIRECCION DE SALUD MUNICIPAL DE CONCEPCION",
+ "id": "CL-MP-3413"
+ },
+ "competitive": false
+ },
+ "awards": [
+ {
+ "id": "42133251",
+ "title": "JERINGAS DAS CONCEPCION",
+ "description": "2239-16-LR15 Órtesis, Prótesis, Endoprótesis e Insumos de Salud. FINANCIAMIENTO: 215.22.04.005.001 SP 28 SE SOLICITA LA ACEPTACIÓN DE ESTA ORCOM A TRAVÉS DE LA PLATAFORMA MERCADO PUBLICO ANTES DE REALIZAR LA ENTREGA DEL BIEN O SERVICIO",
+ "status": "active",
+ "date": "2020-06-23T15:40:44Z",
+ "value": {
+ "amount": 7526475.0,
+ "currency": "CLP"
+ },
+ "suppliers": [
+ {
+ "name": "Tecnika S.A. | Tecnika S.A.",
+ "id": "CL-MP-27291"
+ }
+ ],
+ "items": [
+ {
+ "id": "111570611",
+ "description": "Aparatos de inyección hipodérmica o accesorios(1391678 )JERINGA HIPODERMICA CONTROLADA VENOTEK 10ML LUER LOCK CON AGUJA 21GX1 1/2 100 UNIDADES 1418179",
+ "quantity": 500.0,
+ "unit": {
+ "value": {
+ "amount": 4228.0,
+ "currency": "CLP"
+ }
+ }
+ }
+ ]
+ }
+ ],
+ "relatedProcesses": [
+ {
+ "id": "1",
+ "relationship": [
+ "framework"
+ ],
+ "title": "Órtesis, Prótesis, Endoprótesis e Insumos de Salud",
+ "scheme": "ocid",
+ "identifier": "ocds-70d2nz-2239-16-LR15"
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2023-06-07
+-
+
- Merge the Competitive extension. +
- Add
LotGroup.techniquesfield.
+
2020-10-05
+-
+
- Add fields:
+
-
+
FrameworkAgreement.minimumParticipants
+FrameworkAgreement.value
+FrameworkAgreement.period
+FrameworkAgreement.description
+
+
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues), en [pull requests] (https://github.com/open-contracting-extensions/ocds_techniques_extension/pulls?q=is%3Apr+is%3Aclosed) y en https://github.com/open-contracting/standard/issues/695.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/tenderClassification/index.html b/es/extensions/tenderClassification/index.html
new file mode 100644
index 000000000..60b7c4c11
--- /dev/null
+++ b/es/extensions/tenderClassification/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Técnicas +
+ ++ Adds fields to the tender, lot and lot group objects to describe the use of techniques, such as framework agreements, dynamic purchasing systems and electronic auctions. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ techniques
+
+ |
+ + Técnicas + | +
+ Información sobre el uso de técnicas, como acuerdos marco, sistemas de compra dinámica y subastas electrónicas. + + |
+ + Techniques object + | +
+
+ competitive
+
+ |
+ + Is the framework agreement call-off competitive? + | +
+ Whether this call-off is competitive or not. + + |
+ + boolean + | +
+ Lot +
+ +
+ The extension defines these fields in the Lot object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ techniques
+
+ |
+ + Técnicas + | +
+ Información sobre el uso de técnicas, como acuerdos marco, sistemas de compra dinámica y subastas electrónicas. + + |
+ + Techniques object + | +
+ LotGroup +
+ +
+ The extension defines these fields in the LotGroup object from the Lotes extension:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ techniques
+
+ |
+ + Técnicas + | +
+ Información sobre el uso de técnicas, como acuerdos marco, sistemas de compra dinámica y subastas electrónicas. + + |
+ + Techniques object + | +
+ Techniques +
+ +
+ The extension defines a new Techniques object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ hasFrameworkAgreement
+
+ |
+ + Acuerdo marco involucrado + | +
+ Si se trata de un acuerdo marco. + + |
+ + boolean + | +
+
+ frameworkAgreement
+
+ |
+ + Acuerdo marco + | +
+ Información sobre el acuerdo marco. + + |
+ + FrameworkAgreement object + | +
+
+ hasDynamicPurchasingSystem
+
+ |
+ + Sistema de compra dinámica involucrado + | +
+ Si se trata de un sistema de compra dinámica. + + |
+ + boolean + | +
+
+ dynamicPurchasingSystem
+
+ |
+ + Sistema de compra dinámica + | +
+ Información sobre el sistema de compra dinámica. + + |
+ + DynamicPurchasingSystem object + | +
+
+ hasElectronicAuction
+
+ |
+ + Subasta electrónica utilizada + | +
+ Si se utiliza una subasta electrónica. + + |
+ + boolean + | +
+
+ electronicAuction
+
+ |
+ + Subasta electrónica + | +
+ Información sobre la subasta electrónica. + + |
+ + ElectronicAuction object + | +
+ FrameworkAgreement +
+ +
+ The extension defines a new FrameworkAgreement object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ minimumParticipants
+
+ |
+ + Número mínimo de participantes + | +
+ El número mínimo de participantes en el acuerdo marco + + |
+ + number + | +
+
+ maximumParticipants
+
+ |
+ + Número máximo de participantes + | +
+ El número máximo de participantes en el acuerdo marco. Si no hay un máximo, establecerlo en 1e9999 (que analiza hasta infinito). + + |
+ + number + | +
+
+ method
+
+ |
+ + Método + | +
+ Si los contratos se adjudican con, sin o ambos con y sin re-apertura del concurso. + + |
+ + string from closed frameworkAgreementMethod codelist + | +
+
+ periodRationale
+
+ |
+ + Duración razonable + | +
+ La justificación de casos excepcionales cuando la duración de un acuerdo marco excede los límites legales. + + |
+ + string + | +
+
+ buyerCategories
+
+ |
+ + Categorías de compradores + | +
+ Cualquier categoría adicional de compradores que participe en el acuerdo marco y que no se mencione por su nombre (por ejemplo, "todos los hospitales de la región de la Toscana"). + + |
+ + string + | +
+
+ value
+
+ |
+ + Valor + | +
+ El valor total estimado superior del acuerdo marco. + + |
+ + Value object + | +
+
+ period
+
+ |
+ + Periodo + | +
+ El período durante el cual se estima que el acuerdo marco estará activo. + + |
+ + Period object + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Una descripción resumida del acuerdo marco. Esto complementa cualquier información estructurada proporcionada utilizando los otros campos. + + |
+ + string + | +
+ DynamicPurchasingSystem +
+ +
+ The extension defines a new DynamicPurchasingSystem object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ type
+
+ |
+ + Tipo + | +
+ En el caso de las centrales de compras, si el sistema de compra dinámica puede ser utilizado por compradores que no figuran en el proceso de contratación. + + |
+ + string from closed dynamicPurchasingSystemType codelist + | +
+
+ status
+
+ |
+ + Estado + | +
+ El estado del sistema de compra dinámica. + + |
+ + string from closed dynamicPurchasingSystemStatus codelist + | +
+ ElectronicAuction +
+ +
+ The extension defines a new ElectronicAuction object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ url
+
+ |
+ + URL + | +
+ La dirección de Internet de la subasta electrónica. + + |
+ + string + | +
+
+ description
+
+ |
+ + Descripción + | +
+ Cualquier información adicional sobre la subasta electrónica. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/tenderClassification/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/tenderClassification/master/extension.json b/es/extensions/tenderClassification/master/extension.json
new file mode 100644
index 000000000..2b2806257
--- /dev/null
+++ b/es/extensions/tenderClassification/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Tender classification",
+ "es": "Clasificaci\u00f3n de la licitaci\u00f3n"
+ },
+ "description": {
+ "en": "Adds an array of classification objects to the tender object, in order to categorize the procedure or call-off as a whole.",
+ "es": "Agregar una serie de objetos de clasificaci\u00f3n al objeto de licitaci\u00f3n para categorizar el procedimiento o la solicitud de orden de compra como un todo."
+ },
+ "documentationUrl": {
+ "en": "https://extensions.open-contracting.org/en/extensions/tenderClassification/"
+ },
+ "compatibility": [
+ "1.1"
+ ],
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+itemClassificationScheme.csv"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/tenderClassification/master/index.html b/es/extensions/tenderClassification/master/index.html
new file mode 100644
index 000000000..5c8b4dde6
--- /dev/null
+++ b/es/extensions/tenderClassification/master/index.html
@@ -0,0 +1,326 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificación de la licitación +
+ ++ Agregar una serie de objetos de clasificación al objeto de licitación para categorizar el procedimiento o la solicitud de orden de compra como un todo. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Código + | ++ Título + | ++ Descripción + | +
|---|---|---|
+
+ TED_CATEGORY
+
+ |
+ + EC Public passenger transport services covered + | +
+ A classification of the services covered by the award of contracts for public passenger transport services according to Regulation 1370/2007 of the European Parliament. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/tenderClassification/master/release-schema.json b/es/extensions/tenderClassification/master/release-schema.json
new file mode 100644
index 000000000..fd9a48d5c
--- /dev/null
+++ b/es/extensions/tenderClassification/master/release-schema.json
@@ -0,0 +1,24 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "classification": {
+ "title": "Clasificaci\u00f3n de la licitaci\u00f3n",
+ "description": "La clasificaci\u00f3n primaria del proceso de contrataci\u00f3n.",
+ "$ref": "#/definitions/Classification"
+ },
+ "additionalClassifications": {
+ "title": "Clasificaciones adicionales de licitaciones",
+ "description": "Clasificaciones adicionales del proceso de contrataci\u00f3n.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/tenderClassification/master/schema/index.html b/es/extensions/tenderClassification/master/schema/index.html
new file mode 100644
index 000000000..be5a40f05
--- /dev/null
+++ b/es/extensions/tenderClassification/master/schema/index.html
@@ -0,0 +1,253 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificación de la licitación +
+ ++ Agregar una serie de objetos de clasificación al objeto de licitación para categorizar el procedimiento o la solicitud de orden de compra como un todo. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agregar una lista de objetos de clasificación al objeto de licitación para categorizar el procedimiento o la solicitud de orden de compra como un todo.
+Se espera que los ítems a ser adquiridos tengan clasificaciones más específicas que el procedimiento en su conjunto.
+Contexto legal
+In the European Union, this extension's fields correspond to eForms BG-261 (Classification). For correspondences to Tenders Electronic Daily (TED), see OCDS for the European Union.
+Ejemplo
+{
+ "tender": {
+ "classification": {
+ "description": "Advertising management services",
+ "id": "79341200-8",
+ "scheme": "CPV"
+ },
+ "additionalClassifications": [
+ {
+ "description": "Advertising campaign services",
+ "id": "79341400-0",
+ "scheme": "CPV"
+ },
+ {
+ "description": "Customer services",
+ "id": "79342300-6",
+ "scheme": "CPV"
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2021-01-19
+-
+
- Agregar "o solicitud de orden de compra" en la descripción de la extensión. +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues) y en pull requests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/tender_datePublished/index.html b/es/extensions/tender_datePublished/index.html
new file mode 100644
index 000000000..396de23f8
--- /dev/null
+++ b/es/extensions/tender_datePublished/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Clasificación de la licitación +
+ ++ Agregar una serie de objetos de clasificación al objeto de licitación para categorizar el procedimiento o la solicitud de orden de compra como un todo. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ classification
+
+ |
+ + Clasificación de la licitación + | +
+ La clasificación primaria del proceso de contratación. + + |
+ + Classification object + | +
+
+ additionalClassifications
+
+ |
+ + Clasificaciones adicionales de licitaciones + | +
+ Clasificaciones adicionales del proceso de contratación. + + |
+ + array of Classification objects + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/tender_datePublished/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/tender_datePublished/master/release-schema.json b/es/extensions/tender_datePublished/master/release-schema.json
new file mode 100644
index 000000000..1620742f2
--- /dev/null
+++ b/es/extensions/tender_datePublished/master/release-schema.json
@@ -0,0 +1,17 @@
+{
+ "definitions": {
+ "Tender": {
+ "properties": {
+ "datePublished": {
+ "title": "Fecha de publicaci\u00f3n ",
+ "description": "La fecha en que se public\u00f3 la licitaci\u00f3n.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/tender_datePublished/master/schema/index.html b/es/extensions/tender_datePublished/master/schema/index.html
new file mode 100644
index 000000000..aa902a15d
--- /dev/null
+++ b/es/extensions/tender_datePublished/master/schema/index.html
@@ -0,0 +1,231 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Fecha de publicación de la licitación +
+ ++ Agregar un campo de fecha para indicar cuándo se publicó la licitación. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Esta extensión agrega un campo para indicar explícitamente la fecha y hora en que se publicó la licitación. Este campo puede ser diferente de los campos tender/tenderPeriod/startDate y date.
Uso
+Tener esta información de manera fácil de acceder puede tener muchos beneficios, por ejemplo, poder computar algunos indicadores que dirán cuántos días tiene un potencial oferente para preparar una oferta.
+Para satisfacer tales casos de uso, se debe utilizar el campo tender/datePublished.
Ejemplo
+{
+ "tender": {
+ "datePublished": "2019-07-23T1:27:10.673000-06:00"
+ }
+}
+Registro de cambios
+Esta extensión se discutió originalmente en https://github.com/open-contracting/standard/issues/892.
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/transaction_milestones/index.html b/es/extensions/transaction_milestones/index.html
new file mode 100644
index 000000000..5b03be69a
--- /dev/null
+++ b/es/extensions/transaction_milestones/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Fecha de publicación de la licitación +
+ ++ Agregar un campo de fecha para indicar cuándo se publicó la licitación. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Tender +
+ +
+ The extension defines these fields in the Tender object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ datePublished
+
+ |
+ + Fecha de publicación + | +
+ La fecha en que se publicó la licitación. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/transaction_milestones/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/transaction_milestones/master/release-schema.json b/es/extensions/transaction_milestones/master/release-schema.json
new file mode 100644
index 000000000..be9fcda13
--- /dev/null
+++ b/es/extensions/transaction_milestones/master/release-schema.json
@@ -0,0 +1,13 @@
+{
+ "definitions": {
+ "Transaction": {
+ "properties": {
+ "relatedImplementationMilestone": {
+ "title": "Hito de implementaci\u00f3n relacionado",
+ "description": "Un enlace al hito en la secci\u00f3n de implementaci\u00f3n de OCDS a la que se refiere esta transacci\u00f3n.",
+ "$ref": "#/definitions/MilestoneReference"
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/transaction_milestones/master/schema/index.html b/es/extensions/transaction_milestones/master/schema/index.html
new file mode 100644
index 000000000..1c01d76ec
--- /dev/null
+++ b/es/extensions/transaction_milestones/master/schema/index.html
@@ -0,0 +1,235 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Hitos relacionados con transacción +
+ ++ Agregar un campo a relatedImplementationMilestone a los objetos de transacción, para que los pagos de un contrato puedan vincularse a un hito de implementación. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Esta extensión agrega un campo relatedImplementationMilestone a los objetos de la transacción, para que los pagos de un contrato puedan vincularse con un hito de implementación.
This extension must be used with the Metrics extension.
+Ejemplo
+{
+ "contracts": [
+ {
+ "id": "1",
+ "awardID": "1",
+ "implementation": {
+ "milestones": [
+ {
+ "id": "1234",
+ "title": "Example milestone",
+ "dueDate": "2017-01-01T17:00:00Z",
+ "dateMet": "2016-12-28T17:00:00Z",
+ "status": "met",
+ "dateModified": "2016-12-28T17:00:00Z"
+ }
+ ],
+ "transactions": [
+ {
+ "id": "ABC-123",
+ "source": "http://www.example.com/budget/FY17",
+ "date": "2017-01-05T13:00:00Z",
+ "value": {
+ "amount": 150000,
+ "currency": "GBP"
+ },
+ "payer": {
+ "id": "GB-GOV-00000000",
+ "name": "Example ministry"
+ },
+ "payee": {
+ "id": "GB-COH-99999999",
+ "name": "Example consortium"
+ },
+ "relatedImplementationMilestone": {
+ "id": "1234",
+ "title": "Example milestone"
+ }
+ }
+ ]
+ }
+ }
+ ]
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/transaction_milestones/v1.1/README.md b/es/extensions/transaction_milestones/v1.1/README.md
new file mode 100644
index 000000000..510d9b6f8
--- /dev/null
+++ b/es/extensions/transaction_milestones/v1.1/README.md
@@ -0,0 +1,55 @@
+# Transacciones - Extensión relatedMilestone
+
+## Antecedentes
+
+En OCDS las `transactions` son propiedad del objeto ` implementation`.
+
+Algunos contratos vinculan los pagos con un contrato a hitos específicos para la entrega del contrato.
+
+## Campos de extensión
+
+Esta extensión agrega una propiedad `relatedImplementationMilestone` al objeto `transaction`.
+
+La propiedad `relatedImplementationMilestone` es un objeto de ` milestoneReference`.
+
+El objeto `milestoneReference` es introducido por la [extensión de métricas](https://github.com/open-contracting/ocds_metrics_extension).
+
+## Ejemplo
+
+```json
+"implementation": {
+ "milestones": [
+ {
+ "id": "1234",
+ "title": "Example milestone",
+ "dueDate": "2017-01-01T17:00:00Z",
+ "dateMet": "2016-12-28T17:00:00Z",
+ "status": "met",
+ "dateModified": "2016-12-28T17:00:00Z"
+ }
+ ],
+ "transactions": [
+ {
+ "id": "ABC-123",
+ "source": "http://www.example.com/budget/FY17",
+ "date": "2017-01-05T13:00:00Z",
+ "value": {
+ "amount": 150000,
+ "currency": "GBP"
+ },
+ "payer": {
+ "id": "GB-GOV-00000000",
+ "name": "Example ministry"
+ },
+ "payee": {
+ "id": "GB-COH-99999999",
+ "name": "Example consortium"
+ },
+ "relatedImplementationMilestone": {
+ "id": "1234",
+ "title": "Example milestone"
+ }
+ }
+ ]
+}
+```
diff --git a/es/extensions/transaction_milestones/v1.1/extension.json b/es/extensions/transaction_milestones/v1.1/extension.json
new file mode 100644
index 000000000..236bb4ae9
--- /dev/null
+++ b/es/extensions/transaction_milestones/v1.1/extension.json
@@ -0,0 +1,14 @@
+{
+ "name": {
+ "en": "ocds_transactions_relatedMilestone_extension",
+ "es": "ocds_transactions_relatedMilestone_extension"
+ },
+ "description": {
+ "en": "Adds a relatedImplementationMilestone property to the transactions object so that disbursements can be linked with their associated milestone.",
+ "es": "Agrega una propiedad relatedImplementationMilestone al objeto de transacciones para que los desembolsos se puedan vincular con su hito asociado."
+ },
+ "documentationUrl": {},
+ "compatibility": [
+ "1.1"
+ ]
+}
diff --git a/es/extensions/transaction_milestones/v1.1/index.html b/es/extensions/transaction_milestones/v1.1/index.html
new file mode 100644
index 000000000..60e0a621b
--- /dev/null
+++ b/es/extensions/transaction_milestones/v1.1/index.html
@@ -0,0 +1,315 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Hitos relacionados con transacción +
+ ++ Agregar un campo a relatedImplementationMilestone a los objetos de transacción, para que los pagos de un contrato puedan vincularse a un hito de implementación. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Transaction +
+ +
+ The extension defines these fields in the Transaction object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedImplementationMilestone
+
+ |
+ + Hito de implementación relacionado + | +
+ Un enlace al hito en la sección de implementación de OCDS a la que se refiere esta transacción. + + |
+ + MilestoneReference object + | +
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/transaction_milestones/v1.1/release-schema.json b/es/extensions/transaction_milestones/v1.1/release-schema.json
new file mode 100644
index 000000000..be9fcda13
--- /dev/null
+++ b/es/extensions/transaction_milestones/v1.1/release-schema.json
@@ -0,0 +1,13 @@
+{
+ "definitions": {
+ "Transaction": {
+ "properties": {
+ "relatedImplementationMilestone": {
+ "title": "Hito de implementaci\u00f3n relacionado",
+ "description": "Un enlace al hito en la secci\u00f3n de implementaci\u00f3n de OCDS a la que se refiere esta transacci\u00f3n.",
+ "$ref": "#/definitions/MilestoneReference"
+ }
+ }
+ }
+ }
+}
diff --git a/es/extensions/transaction_milestones/v1.1/schema/index.html b/es/extensions/transaction_milestones/v1.1/schema/index.html
new file mode 100644
index 000000000..789767548
--- /dev/null
+++ b/es/extensions/transaction_milestones/v1.1/schema/index.html
@@ -0,0 +1,235 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Hitos relacionados con transacción +
+ ++ Agregar un campo a relatedImplementationMilestone a los objetos de transacción, para que los pagos de un contrato puedan vincularse a un hito de implementación. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Antecedentes
+En OCDS las transactions son propiedad del objeto implementation.
Algunos contratos vinculan los pagos con un contrato a hitos específicos para la entrega del contrato.
+Campos de extensión
+Esta extensión agrega una propiedad relatedImplementationMilestone al objeto transaction.
La propiedad relatedImplementationMilestone es un objeto de milestoneReference.
El objeto milestoneReference es introducido por la extensión de métricas.
Ejemplo
+"implementation": {
+ "milestones": [
+ {
+ "id": "1234",
+ "title": "Example milestone",
+ "dueDate": "2017-01-01T17:00:00Z",
+ "dateMet": "2016-12-28T17:00:00Z",
+ "status": "met",
+ "dateModified": "2016-12-28T17:00:00Z"
+ }
+ ],
+ "transactions": [
+ {
+ "id": "ABC-123",
+ "source": "http://www.example.com/budget/FY17",
+ "date": "2017-01-05T13:00:00Z",
+ "value": {
+ "amount": 150000,
+ "currency": "GBP"
+ },
+ "payer": {
+ "id": "GB-GOV-00000000",
+ "name": "Example ministry"
+ },
+ "payee": {
+ "id": "GB-COH-99999999",
+ "name": "Example consortium"
+ },
+ "relatedImplementationMilestone": {
+ "id": "1234",
+ "title": "Example milestone"
+ }
+ }
+ ]
+}
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/unstructuredChanges/index.html b/es/extensions/unstructuredChanges/index.html
new file mode 100644
index 000000000..05ab3089c
--- /dev/null
+++ b/es/extensions/unstructuredChanges/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Hitos relacionados con transacción +
+ ++ Agregar un campo a relatedImplementationMilestone a los objetos de transacción, para que los pagos de un contrato puedan vincularse a un hito de implementación. +
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Transaction +
+ +
+ The extension defines these fields in the Transaction object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedImplementationMilestone
+
+ |
+ + Hito de implementación relacionado + | +
+ Un enlace al hito en la sección de implementación de OCDS a la que se refiere esta transacción. + + |
+ + MilestoneReference object + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/unstructuredChanges/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/unstructuredChanges/master/release-schema.json b/es/extensions/unstructuredChanges/master/release-schema.json
new file mode 100644
index 000000000..6602b2b15
--- /dev/null
+++ b/es/extensions/unstructuredChanges/master/release-schema.json
@@ -0,0 +1,109 @@
+{
+ "definitions": {
+ "Amendment": {
+ "properties": {
+ "unstructuredChanges": {
+ "title": "Cambios no estructurados",
+ "description": "Cambios no estructurados o semi-estructurados de una notificaci\u00f3n anterior.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/UnstructuredChange"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ }
+ },
+ "UnstructuredChange": {
+ "title": "Cambio no estructurado",
+ "description": "Cambio no estructurado o semi-estructurado de una notificaci\u00f3n anterior.",
+ "type": "object",
+ "properties": {
+ "relatedLot": {
+ "title": "Lote relacionado",
+ "description": "El identificador del lote al que se refiere este cambio, si lo hubiera.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "oldValue": {
+ "title": "Valor viejo",
+ "description": "El valor del elemento de datos al que hace referencia el campo `where`, antes del cambio.",
+ "$ref": "#/definitions/UnstructuredChangeValue"
+ },
+ "newValue": {
+ "title": "Nuevo valor",
+ "description": "El valor del elemento de datos al que hace referencia el campo `where`, despu\u00e9s del cambio.",
+ "$ref": "#/definitions/UnstructuredChangeValue"
+ },
+ "where": {
+ "title": "Donde",
+ "description": "Una referencia a un elemento de datos de una notificaci\u00f3n anterior que se est\u00e1 modificando.",
+ "type": "object",
+ "properties": {
+ "section": {
+ "title": "Secci\u00f3n",
+ "description": "El identificador de la secci\u00f3n que contiene el elemento de datos, si el aviso anterior est\u00e1 organizado en secciones.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "label": {
+ "title": "Etiqueta",
+ "description": "La etiqueta del elemento de datos.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ }
+ },
+ "minProperties": 1
+ }
+ },
+ "minProperties": 1
+ },
+ "UnstructuredChangeValue": {
+ "title": "Valor del cambio no estructurado",
+ "description": "Un valor de un elemento de datos. El valor debe describirse utilizando exactamente uno de los campos `text`, `classifications` o `date`.",
+ "type": "object",
+ "properties": {
+ "text": {
+ "title": "Valor del texto",
+ "description": "Un texto. Si el cambio elimin\u00f3 o borr\u00f3 el elemento de datos, utilice la cadena vac\u00eda (\"\").",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "classifications": {
+ "title": "Clasificaciones",
+ "description": "Una lista de clasificaciones",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ },
+ "date": {
+ "title": "Fecha",
+ "description": "Una fecha.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "pattern": "^\\d{4}-[01]\\d-[0-3]\\d(T[0-2]\\d:[0-5]\\d:[0-5]\\d([+-][0-2]\\d:?[0-5]\\d|Z))?$"
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/unstructuredChanges/master/schema/index.html b/es/extensions/unstructuredChanges/master/schema/index.html
new file mode 100644
index 000000000..5450252db
--- /dev/null
+++ b/es/extensions/unstructuredChanges/master/schema/index.html
@@ -0,0 +1,452 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cambios no estructurados +
+ ++ Agrega una matriz unstructuredChanges al objeto Amendment. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Agrega una matriz unstructuredChanges al objeto Amendment.
+Guía
+En muchos regímenes de contratación, es habitual modificar un anuncio de licitación describiendo los cambios en palabras, en lugar de volver a publicar el anuncio completo. Esto se debe a que el proceso está diseñado para los humanos: es más fácil para un humano leer una descripción de los cambios, que calcular la diferencia entre dos anuncios completos.
+En cambio, para una máquina es fácil calcular la diferencia entre dos notificaciones completas, pero es difícil o imposible interpretar una descripción de cambios. Hay muchas formas en las que una descripción de cambios puede salir mal, de las que un humano puede recuperarse, pero que una máquina no puede. Por ejemplo:
+-
+
- La etiqueta del campo que está sujeto a modificación puede hacer referencia a:
+
-
+
- una etiqueta que no aparece en el aviso anterior +
- una etiqueta incorrecta o imprecisa en el aviso anterior +
+ - El tipo de datos del nuevo valor puede ser inconsistente con el tipo de datos del campo. +
El OCDS está diseñado para ser leído por máquinas. Lo ideal es que el sistema fuente desde el que se exportan los datos de OCDS contenga los valores de cada campo antes y después de un cambio. En ese caso, debería seguir simplemente el modelo de entregas y registros.
+Esta extensión está pensada para ser utilizada sólo en los casos en que un sistema de origen no rastrea los valores de los campos, sino que rastrea una descripción de los cambios, como en la UE (véase Contexto legal más abajo). Nota: La falta de estructura impide muchos análisis de datos.
+Contexto legal
+Esta extensión se desarrolló principalmente para permitir la asignación de los formularios estándar de la Unión Europea para la contratación pública a OCDS (específicamente el Formulario 14 Corrigendum), pero podría ser útil en contextos no comunitarios.
+See OCDS for the European Union for guidance on how to use it with TED F14 data.
+Ejemplo
+{
+ "tender": {
+ "amendments": [
+ {
+ "id": "1",
+ "unstructuredChanges": [
+ {
+ "oldValue": {
+ "text": "https://city.example.org/procurement"
+ },
+ "newValue": {
+ "text": "https://procurement.example.org"
+ },
+ "where": {
+ "section": "I.1",
+ "label": "Main address"
+ }
+ },
+ {
+ "oldValue": {
+ "date": "2020-12-15"
+ },
+ "newValue": {
+ "date": "2019-12-15T14:00:00+03:00"
+ },
+ "where": {
+ "section": "I.4",
+ "label": "Notice date"
+ }
+ },
+ {
+ "oldValue": {
+ "classifications": [
+ {
+ "scheme": "CPV",
+ "id": "79000000"
+ }
+ ]
+ },
+ "newValue": {
+ "classifications": [
+ {
+ "scheme": "CPV",
+ "id": "79822500"
+ }
+ ]
+ },
+ "where": {
+ "section": "II.2.2",
+ "label": "Main CPV code"
+ },
+ "relatedLot": "lot-2"
+ }
+ ]
+ }
+ ]
+ }
+}
+Issues
+Reporte issues para esta extensión en el repositorio de extensiones ocds, poniendo el nombre de la extensión en el título del issue.
+Registro de cambios
+2020-09-16
+-
+
- Agregar sección Guía +
2020-07-13
+-
+
- Relajar el formato de fecha para permitir fecha o fecha y hora +
2020-06-04
+-
+
- Revisar las palabras normativas y no normativas. +
2020-04-24
+-
+
- Agregar las propiedades
minProperties,minItemsy/ominLength.
+
Esta extensión se discutió originalmente como parte del [OCDS para el perfil de la UE] (https://github.com/open-contracting-extensions/european-union/issues/63), en pull resquests.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/withheldInformation/index.html b/es/extensions/withheldInformation/index.html
new file mode 100644
index 000000000..e600e2d63
--- /dev/null
+++ b/es/extensions/withheldInformation/index.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Cambios no estructurados +
+ ++ Agrega una matriz unstructuredChanges al objeto Amendment. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Amendment +
+ +
+ The extension defines these fields in the Amendment object from OCDS:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ unstructuredChanges
+
+ |
+ + Cambios no estructurados + | +
+ Cambios no estructurados o semi-estructurados de una notificación anterior. + + |
+ + array of UnstructuredChange objects + | +
+ UnstructuredChange +
+ +
+ The extension defines a new UnstructuredChange object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ relatedLot
+
+ |
+ + Lote relacionado + | +
+ El identificador del lote al que se refiere este cambio, si lo hubiera. + + |
+ + string + | +
+
+ oldValue
+
+ |
+ + Valor viejo + | +
+ El valor del elemento de datos al que hace referencia el campo |
+ + UnstructuredChangeValue object + | +
+
+ newValue
+
+ |
+ + Nuevo valor + | +
+ El valor del elemento de datos al que hace referencia el campo |
+ + UnstructuredChangeValue object + | +
+
+ where
+
+ |
+ + Donde + | +
+ Una referencia a un elemento de datos de una notificación anterior que se está modificando. + + |
+ + object + | +
+
+ where.
+ |
+ + Sección + | +
+ El identificador de la sección que contiene el elemento de datos, si el aviso anterior está organizado en secciones. + + |
+ + string + | +
+
+ where.
+ |
+ + Etiqueta + | +
+ La etiqueta del elemento de datos. + + |
+ + string + | +
+ UnstructuredChangeValue +
+ +
+ The extension defines a new UnstructuredChangeValue object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ text
+
+ |
+ + Valor del texto + | +
+ Un texto. Si el cambio eliminó o borró el elemento de datos, utilice la cadena vacía (""). + + |
+ + string + | +
+
+ classifications
+
+ |
+ + Clasificaciones + | +
+ Una lista de clasificaciones + + |
+ + array of Classification objects + | +
+
+ date
+
+ |
+ + Fecha + | +
+ Una fecha. + + |
+ + string + | +
+
+
+
+
+
+ + + This page has moved to a /es/extensions/withheldInformation/master/ +
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/withheldInformation/master/extension.json b/es/extensions/withheldInformation/master/extension.json
new file mode 100644
index 000000000..08685aa88
--- /dev/null
+++ b/es/extensions/withheldInformation/master/extension.json
@@ -0,0 +1,26 @@
+{
+ "name": {
+ "en": "Withheld information",
+ "es": "Withheld information"
+ },
+ "description": {
+ "en": "Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld.",
+ "es": "Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld."
+ },
+ "documentationUrl": {
+ "en": "https://github.com/open-contracting-extensions/ocds_withheldInformation_extension"
+ },
+ "schemas": [
+ "release-schema.json"
+ ],
+ "codelists": [
+ "+itemClassificationScheme.csv"
+ ],
+ "compatibility": [
+ "1.1"
+ ],
+ "contactPoint": {
+ "name": "Open Contracting Partnership",
+ "email": "data@open-contracting.org"
+ }
+}
diff --git a/es/extensions/withheldInformation/master/index.html b/es/extensions/withheldInformation/master/index.html
new file mode 100644
index 000000000..eec2293ac
--- /dev/null
+++ b/es/extensions/withheldInformation/master/index.html
@@ -0,0 +1,298 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Withheld information +
+ ++ Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld. +
+
+
+
+
+
+
+
+
+
+
+
+ + Codelists +
+ ++ +itemClassificationScheme.csv +
+ +
+ You can download the +itemClassificationScheme.csv file in English.
+
+ The extension adds these codes to the itemClassificationScheme.csv codelist.
+
| + Code + | ++ Title + | ++ Description + | +
|---|---|---|
+
+ eu-non-publication-justification
+
+ |
+ + European Union non-publication justification + | +
+ The main reasons for not immediately publishing information required by eForms within the context of public procurement according to the legislation of the European Parliament. + +
|
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/extensions/withheldInformation/master/release-schema.json b/es/extensions/withheldInformation/master/release-schema.json
new file mode 100644
index 000000000..5130b0229
--- /dev/null
+++ b/es/extensions/withheldInformation/master/release-schema.json
@@ -0,0 +1,80 @@
+{
+ "properties": {
+ "withheldInformation": {
+ "title": "Withheld information",
+ "description": "Details of items of information whose publication is temporarily or permanently withheld.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/WithheldInformationItem"
+ },
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "definitions": {
+ "WithheldInformationItem": {
+ "title": "Withheld information item",
+ "description": "An item of information whose publication is temporarily or permanently withheld.",
+ "type": "object",
+ "required": [
+ "id"
+ ],
+ "properties": {
+ "id": {
+ "title": "ID",
+ "description": "The locally unique identifier for the withheld information item.",
+ "type": "string",
+ "minLength": 1
+ },
+ "field": {
+ "title": "Field",
+ "description": "The identifier of the field with which the withheld information would otherwise be published.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "name": {
+ "title": "Name",
+ "description": "The name or title of the field with which the withheld information would otherwise be published.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "availabilityDate": {
+ "title": "Availability date",
+ "description": "The date on which the withheld information will be published.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "format": "date-time"
+ },
+ "rationale": {
+ "title": "Rationale",
+ "description": "The rationale for withholding the information.",
+ "type": [
+ "string",
+ "null"
+ ],
+ "minLength": 1
+ },
+ "rationaleClassifications": {
+ "title": "Rationale classifications",
+ "description": "Classifications of the rationale for withholding the information.",
+ "type": "array",
+ "items": {
+ "$ref": "#/definitions/Classification"
+ },
+ "wholeListMerge": true,
+ "uniqueItems": true,
+ "minItems": 1
+ }
+ },
+ "minProperties": 1
+ }
+ }
+}
diff --git a/es/extensions/withheldInformation/master/schema/index.html b/es/extensions/withheldInformation/master/schema/index.html
new file mode 100644
index 000000000..30a24e28d
--- /dev/null
+++ b/es/extensions/withheldInformation/master/schema/index.html
@@ -0,0 +1,372 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Withheld information +
+ ++ Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld. +
+
+
+
+
+
+
+
+
+
+
+ + Documentation +
+Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld.
+Legal context
+In the European Union, this extension's fields correspond to eForms BG-8 (Not Immediately Published). For correspondences to eForms fields, see OCDS for eForms.
+Example
+{
+ "withheldInformation": [
+ {
+ "id": "cro-bor-law-18d27a53-0109-4f93-9231-6659d931bce0",
+ "field": "cro-bor-law",
+ "name": "Cross Border Law",
+ "rationale": "Publication of this information is delayed because...",
+ "rationaleClassifications": [
+ {
+ "scheme": "eu-non-publication-justification",
+ "id": "oth-int",
+ "description": "Other public interest",
+ "uri": "http://publications.europa.eu/resource/authority/non-publication-justification/oth-int"
+ }
+ ],
+ "availabilityDate": "2024-12-31T09:00:00+01:00"
+ }
+ ]
+}
+Issues
+Report issues for this extension in the ocds-extensions repository, putting the extension's name in the issue's title.
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/es/index.html b/es/index.html
new file mode 100644
index 000000000..0e8dba942
--- /dev/null
+++ b/es/index.html
@@ -0,0 +1,117 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Withheld information +
+ ++ Adds a top-level withheld information array to describe items of information whose publication is temporarily or permanently withheld. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ + Schema +
+ +
+ You can download the release-schema.json file in English.
+
+ Release +
+ ++ The extension defines these fields in the release schema: +
+ +| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ withheldInformation
+
+ |
+ + Withheld information + | +
+ Details of items of information whose publication is temporarily or permanently withheld. + + |
+ + array of WithheldInformationItem objects + | +
+ WithheldInformationItem +
+ +
+ The extension defines a new WithheldInformationItem object with these fields:
+
| + Field + | ++ Title + | ++ Description + | ++ Type(s) + | +
|---|---|---|---|
+
+ id
+
+ |
+ + ID + | +
+ The locally unique identifier for the withheld information item. + + |
+ + string + | +
+
+ field
+
+ |
+ + Field + | +
+ The identifier of the field with which the withheld information would otherwise be published. + + |
+ + string + | +
+
+ name
+
+ |
+ + Name + | +
+ The name or title of the field with which the withheld information would otherwise be published. + + |
+ + string + | +
+
+ availabilityDate
+
+ |
+ + Availability date + | +
+ The date on which the withheld information will be published. + + |
+ + string + | +
+
+ rationale
+
+ |
+ + Rationale + | +
+ The rationale for withholding the information. + + |
+ + string + | +
+
+ rationaleClassifications
+
+ |
+ + Rationale classifications + | +
+ Classifications of the rationale for withholding the information. + + |
+ + array of Classification objects + | +
+
+
+
+
+
+ + OCDS Extension Explorer +
+ ++ Disclose more data about your contracting processes, using extensions to the Open Contracting Data Standard. +
+ +
+
+
+
+
+
+
+
+
+
+
+ For data publishers
+OCDS defines a core set of fields and codes for describing contracting processes. You can use extensions to describe additional fields outside the core set.
+ Read the publisher guidance +
+
+
+
+
+
+ For data users
+OCDS data can include fields and codes from the OCDS schema and from extensions. To understand extended data, you need to identify which extensions are used and read the extensions' documentation.
+ Read the user guidance +
+
+
+
+
+
+ + Publisher Guidance +
+ ++ To implement OCDS, you must identify the fields and codes in OCDS that match the data elements that you want to publish. Some data elements might not match any field or code in OCDS. To cover such cases, you can add additional fields or codes to your OCDS data. Extensions provide a way to document these additional fields and codes. +
+ ++ Why use extensions? +
+ ++ We recommend using extensions to describe your additional fields and codes so that: +
+ +-
+
- + Analysts can access definitions for fields and codes to help them interpret your data. + +
- + Developers can access information about the structure of your data to help write software to process it. + +
- + Your data is consistent with that of other publishers and compatible with reusable tools and methodologies. + +
+ Use an extension +
+ ++ To publish additional fields or codes using an extension: +
+ +-
+
- + Use the Extension Explorer to find an extension that describes the data element(s) you want to publish. If you can’t find a suitable extension, you might need to create an extension. + +
- + Structure your data according to the extension’s schema and documentation. + +
-
+ Declare the extension in your package’s `extensions` array using the URL from the extension’s documentation. For example, to declare the Bid statistics and details extension:
+ ++
+ {"extensions": ["https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"]} ++
+ - + Check your data using the OCDS Data Review Tool. + +
+ Create an extension +
++ If you can’t find a suitable extension to describe the data elements you want to publish, you can create an extension. +
+ ++ Extensions can introduce new fields, add codes to open codelists and introduce additional validation rules to existing OCDS fields. However, extensions cannot remove fields, change the title or description of fields or add codes to closed codelists. To suggest such changes, open an issue on the standard issue tracker. +
+ ++ You should also consider whether the data you want to publish belongs to the contracting process or whether it exists independently. Data that exists independently of the contracting process is typically better published in a separate dataset. For example, data on changes to the beneficial ownership of suppliers, which is usually tracked outside of procurement systems. +
+ ++ To create an extension you need to understand JSON Schema and the structure of the OCDS schema. Extensions are fragments of JSON Schema that can be merged into the OCDS schema to create an extended schema. +
+ ++ The standard extension template describes the structure and components of an extension and the technical steps to document an extension. +
+ ++ There are five steps to creating an extension: +
+ ++ Discuss +
+ ++ Before creating an extension, search for related discussions on the standard issue tracker. +
+ ++ If you can’t find any related discussions, open an issue to describe the extension you plan to create. The issue’s description should include: +
+ +-
+
- + The extension’s use case(s). Describe your reason for adding additional fields and/or codes and what users will do with the data. + +
- + The concepts or process that you want to represent. Explain the underlying concepts described by the extension and the workflow for collecting the data. Include references to legislation and other documentation, and consider providing a + diagram. + +
- + Examples of existing data. Provide examples of how the data covered by the extension is represented in your data sources. + +
- + To encourage collaboration, keep this issue up to date throughout the development of your extension. + +
+ Develop +
+ ++ You first need to decide on the name, structure and format of the fields in your extension. +
+ ++ You can start by mocking up an example of the data you are creating an extension for in JSON format. Consider: +
+ +-
+
- + How would different data fit into this structure? + +
- + Are the field names intuitive for users? + +
- + Is the structure easy for applications to consume? + +
- + You can also check other standards for potential models. The more different examples of source data, and different use cases for the data you can consider, the better. + +
+ Before continuing, you should invite feedback on your mockup using the Github issue you created in the previous step. +
+ ++ Once you have settled on a model, you should then document the schema for your extension. The following tools are available to help you: +
+ +-
+
- + You can use the OCDS Extension Creator to edit the OCDS schema and generate a patch. For more information on using the extension creator, refer to its documentation. + +
- + You can copy the standard extension template and use a text editor to edit the schema files. + +
- + You can use JSONschema.net to generate a schema from your JSON mockup. + +
+ Your schema should follow the schema style guide. +
+ ++ Document +
+ ++ You will need to find somewhere to host your extension online at a stable URL. Creating a GitHub repository for your extension is a good option because it offers version control and issue tracking. +
+ ++ You also need to write a README file and/or other documentation for your extension. +
+ ++ Your documentation should include a description of the extension and its use cases, and examples of data structured according to the extension. +
+ ++ Test +
++ Test your extension by following steps 2-4 in Use an extension. +
+ ++ Register +
++ We encourage you to register your extension so that others can discover it using the Extension Explorer. +
+ ++ Extensions that are useful to only a single publisher do not need to be registered. +
+ ++ To register an extension, it must meet the following criteria: +
+ +-
+
- + The documentation is in English. According to the translation and localization policy, “the authoritative language for the standard is English.” As such, all extensions in the Extension Explorer – as part of the standard’s documentation + – must be in English. + +
- + The documentation, excluding examples, is more than 200 characters long. Documentation of less than 200 characters cannot adequately describe an extension, its purpose and technical details. + +
- + The extension.json and README.md files are not publisher-specific. If the extension’s name or description suggests it is relevant to only one publisher, then it is unlikely to be used by other publishers, even if the schema patch is + relevant. + +
- + No other extension expresses the same concepts. Having multiple ways to express the same concept would be counter-productive to standardization. + +
- + The extension follows the schema style guide. + +
+ Versioning +
++ OCDS extensions should use semantic versioning. +
+ +
+
+
+
+
+
+ + User Guidance +
+ ++ To use data, you first need to understand its structure and meaning. OCDS data can contain fields from: +
+ +
-
+
- + OCDS, whose fields are described in its schema and in its Schema Reference. + +
- + Extensions, whose fields are described in their schema and in their documentation. + +
+ To identify which extensions are used in OCDS data, you can either: +
+ +-
+
-
+ Check for an
extensionsfield at the package level. For data with extensions, this field contains an array of URLs toextension.jsonfiles. Each file contains adocumentationUrlobject with a URL to the extension's documentation. Open the URL to read its documentation (in many cases, the URL leads to this website). For example, the following data declares the Bid statistics and details extension: ++++ {"extensions": ["https://raw.githubusercontent.com/open-contracting-extensions/ocds_bid_extension/master/extension.json"]} ++
+ - + Upload the data to the OCDS Data Review Tool, which lists the extensions used and links to their documentation. + +
+
+
+
+
+
+ + + This page has moved to a /en/ +
+- `s. The `::before` pseudo-element generates an element
+ // *within* the .breadcrumb-item and thereby inherits the `text-decoration`.
+ //
+ // To trick IE into suppressing the underline, we give the pseudo-element an
+ // underline and then immediately remove it.
+ + .breadcrumb-item:hover::before {
+ text-decoration: underline;
+ }
+ // stylelint-disable-next-line no-duplicate-selectors
+ + .breadcrumb-item:hover::before {
+ text-decoration: none;
+ }
+
+ &.active {
+ color: $breadcrumb-active-color;
+ }
+}
diff --git a/static/lib/bootstrap/_button-group.scss b/static/lib/bootstrap/_button-group.scss
new file mode 100644
index 000000000..d7220029a
--- /dev/null
+++ b/static/lib/bootstrap/_button-group.scss
@@ -0,0 +1,163 @@
+// stylelint-disable selector-no-qualifying-type
+
+// Make the div behave like a button
+.btn-group,
+.btn-group-vertical {
+ position: relative;
+ display: inline-flex;
+ vertical-align: middle; // match .btn alignment given font-size hack above
+
+ > .btn {
+ position: relative;
+ flex: 1 1 auto;
+
+ // Bring the hover, focused, and "active" buttons to the front to overlay
+ // the borders properly
+ @include hover {
+ z-index: 1;
+ }
+ &:focus,
+ &:active,
+ &.active {
+ z-index: 1;
+ }
+ }
+}
+
+// Optional: Group multiple button groups together for a toolbar
+.btn-toolbar {
+ display: flex;
+ flex-wrap: wrap;
+ justify-content: flex-start;
+
+ .input-group {
+ width: auto;
+ }
+}
+
+.btn-group {
+ // Prevent double borders when buttons are next to each other
+ > .btn:not(:first-child),
+ > .btn-group:not(:first-child) {
+ margin-left: -$btn-border-width;
+ }
+
+ // Reset rounded corners
+ > .btn:not(:last-child):not(.dropdown-toggle),
+ > .btn-group:not(:last-child) > .btn {
+ @include border-right-radius(0);
+ }
+
+ > .btn:not(:first-child),
+ > .btn-group:not(:first-child) > .btn {
+ @include border-left-radius(0);
+ }
+}
+
+// Sizing
+//
+// Remix the default button sizing classes into new ones for easier manipulation.
+
+.btn-group-sm > .btn { @extend .btn-sm; }
+.btn-group-lg > .btn { @extend .btn-lg; }
+
+
+//
+// Split button dropdowns
+//
+
+.dropdown-toggle-split {
+ padding-right: $btn-padding-x * .75;
+ padding-left: $btn-padding-x * .75;
+
+ &::after,
+ .dropup &::after,
+ .dropright &::after {
+ margin-left: 0;
+ }
+
+ .dropleft &::before {
+ margin-right: 0;
+ }
+}
+
+.btn-sm + .dropdown-toggle-split {
+ padding-right: $btn-padding-x-sm * .75;
+ padding-left: $btn-padding-x-sm * .75;
+}
+
+.btn-lg + .dropdown-toggle-split {
+ padding-right: $btn-padding-x-lg * .75;
+ padding-left: $btn-padding-x-lg * .75;
+}
+
+
+// The clickable button for toggling the menu
+// Set the same inset shadow as the :active state
+.btn-group.show .dropdown-toggle {
+ @include box-shadow($btn-active-box-shadow);
+
+ // Show no shadow for `.btn-link` since it has no other button styles.
+ &.btn-link {
+ @include box-shadow(none);
+ }
+}
+
+
+//
+// Vertical button groups
+//
+
+.btn-group-vertical {
+ flex-direction: column;
+ align-items: flex-start;
+ justify-content: center;
+
+ > .btn,
+ > .btn-group {
+ width: 100%;
+ }
+
+ > .btn:not(:first-child),
+ > .btn-group:not(:first-child) {
+ margin-top: -$btn-border-width;
+ }
+
+ // Reset rounded corners
+ > .btn:not(:last-child):not(.dropdown-toggle),
+ > .btn-group:not(:last-child) > .btn {
+ @include border-bottom-radius(0);
+ }
+
+ > .btn:not(:first-child),
+ > .btn-group:not(:first-child) > .btn {
+ @include border-top-radius(0);
+ }
+}
+
+
+// Checkbox and radio options
+//
+// In order to support the browser's form validation feedback, powered by the
+// `required` attribute, we have to "hide" the inputs via `clip`. We cannot use
+// `display: none;` or `visibility: hidden;` as that also hides the popover.
+// Simply visually hiding the inputs via `opacity` would leave them clickable in
+// certain cases which is prevented by using `clip` and `pointer-events`.
+// This way, we ensure a DOM element is visible to position the popover from.
+//
+// See https://github.com/twbs/bootstrap/pull/12794 and
+// https://github.com/twbs/bootstrap/pull/14559 for more information.
+
+.btn-group-toggle {
+ > .btn,
+ > .btn-group > .btn {
+ margin-bottom: 0; // Override default `