diff --git a/docs/governance/normative.md b/docs/governance/normative.md index a1114304d..78d3c3a18 100644 --- a/docs/governance/normative.md +++ b/docs/governance/normative.md @@ -40,7 +40,7 @@ Specifically: These files are presently: * Accessible at [https://standard.open-contracting.org/schema/](https://standard.open-contracting.org/schema/) -* Accessible under [https://standard.open-contracting.org/latest/en/](../index) ([example](../release-schema.json)) +* Accessible under [https://standard.open-contracting.org/latest/en/](../index) ([example](../../build/current_lang/release-schema.json)) * Rendered as tables and using Docson under [Reference](../schema/index) ([example](../schema/release)) * Located in the [`schema` directory](https://github.com/open-contracting/standard/tree/HEAD/schema) diff --git a/docs/locale/es/LC_MESSAGES/codelists.po b/docs/locale/es/LC_MESSAGES/codelists.po index 1e04d1eab..8bdaf0fd7 100644 --- a/docs/locale/es/LC_MESSAGES/codelists.po +++ b/docs/locale/es/LC_MESSAGES/codelists.po @@ -2075,8 +2075,8 @@ msgstr "Ontologías de Cantidades, Unidades, Dimensiones y Tipos de Datos" #. Description #: schema/codelists/unitClassificationScheme.csv:2 msgid "" -"Use the [QUDT Code](https://www.qudt.org/qudt/owl/1.0.0/unit/Instances.html)" +"Use the [QUDT Code](https://www.qudt.org)" " value." msgstr "" "Usa el valor del [QUDT " -"Code](https://www.qudt.org/qudt/owl/1.0.0/unit/Instances.html)." +"Code](https://www.qudt.org)." diff --git a/docs/locale/es/LC_MESSAGES/schema/reference.po b/docs/locale/es/LC_MESSAGES/schema/reference.po index bc366a87c..04a3ff19b 100644 --- a/docs/locale/es/LC_MESSAGES/schema/reference.po +++ b/docs/locale/es/LC_MESSAGES/schema/reference.po @@ -1151,13 +1151,13 @@ msgstr "" #: ../../docs/schema/reference.md:383 msgid "" "If the [Quantities, Units, Dimensions and Data Types " -"Ontologies](https://www.qudt.org/qudt/owl/1.0.0/unit/Instances.html) unit classification " +"Ontologies](https://www.qudt.org) unit classification " "scheme is used, then publishers can use its CamelCase unit names, such as " "\"SquareMile\", in the `unit.name` field." msgstr "" "Si se usa el esquema de clasificación de unidades [Quantities, Units, " "Dimensions and Data Types " -"Ontologies](https://www.qudt.org/qudt/owl/1.0.0/unit/Instances.html), los publicadores " +"Ontologies](https://www.qudt.org), los publicadores " "pueden usar sus nombres de unidad CamelCase, como \"SquareMile\", en el " "campo `unit.name`." diff --git a/docs/locale/fr/LC_MESSAGES/codelists.po b/docs/locale/fr/LC_MESSAGES/codelists.po index 27fab311a..1ffb51260 100644 --- a/docs/locale/fr/LC_MESSAGES/codelists.po +++ b/docs/locale/fr/LC_MESSAGES/codelists.po @@ -2110,6 +2110,6 @@ msgstr "Quantités, unités, dimensions et ontologies de types de données" #. Description #: schema/codelists/unitClassificationScheme.csv:2 msgid "" -"Use the [QUDT Code](https://www.qudt.org/qudt/owl/1.0.0/unit/Instances.html)" +"Use the [QUDT Code](https://www.qudt.org)" " value." msgstr "" diff --git a/docs/locale/fr/LC_MESSAGES/schema/reference.po b/docs/locale/fr/LC_MESSAGES/schema/reference.po index dbc4376a9..a6f17149f 100644 --- a/docs/locale/fr/LC_MESSAGES/schema/reference.po +++ b/docs/locale/fr/LC_MESSAGES/schema/reference.po @@ -1142,7 +1142,7 @@ msgstr "" #: ../../docs/schema/reference.md:383 msgid "" "If the [Quantities, Units, Dimensions and Data Types " -"Ontologies](https://www.qudt.org/qudt/owl/1.0.0/unit/Instances.html) unit classification " +"Ontologies](https://www.qudt.org) unit classification " "scheme is used, then publishers can use its CamelCase unit names, such as " "\"SquareMile\", in the `unit.name` field." msgstr "" diff --git a/docs/schema/reference.md b/docs/schema/reference.md index 565ebe7f1..01df9e565 100644 --- a/docs/schema/reference.md +++ b/docs/schema/reference.md @@ -584,7 +584,7 @@ The items block is used to list the line-items associated with a tender, award o The `unit` block allows detailed specification of the parameters and price of units that make up a line-item. -If the [Quantities, Units, Dimensions and Data Types Ontologies](https://www.qudt.org/qudt/owl/1.0.0/unit/Instances.html) unit classification scheme is used, then publishers can use its CamelCase unit names, such as "SquareMile", in the `unit.name` field. +If the [Quantities, Units, Dimensions and Data Types Ontologies](https://www.qudt.org) unit classification scheme is used, then publishers can use its CamelCase unit names, such as "SquareMile", in the `unit.name` field. Other unit classification schemes can be used, including those in the [unitClassificationScheme codelist](codelists.md#unit-classification-scheme). diff --git a/schema/codelists/documentType.csv b/schema/codelists/documentType.csv index 2ec2a4d7b..72dd463d4 100644 --- a/schema/codelists/documentType.csv +++ b/schema/codelists/documentType.csv @@ -38,7 +38,7 @@ planning,needsAssessment,Needs assessment,Documentation of the needs assessments planning,feasibilityStudy,Feasibility study,"Documentation of feasibility studies carried out for a future contracting process, providing information on net benefits or costs of the proposed goods, works or services.",, planning,projectPlan,Project plan,"Documentation of project planning for a future contracting process, and, where applicable, a copy of the project plan document.",, tender,billOfQuantity,Bill of quantity,"Documentation that provides itemized information on materials, parts and labour, and the terms and conditions for their provision, providing information that would enable bidders to price work effectively. Structured versions of item and quantity information at each of tender, award and contract stage can be provided using units within the items building block.",, -"tender",bidders,Information on bidders,"Documentation on bidders or participants, their validation documents and any procedural exemptions for which they qualify.",, +tender,bidders,Information on bidders,"Documentation on bidders or participants, their validation documents and any procedural exemptions for which they qualify.",, "tender, award, contract, implementation",conflictOfInterest,Conflict of interest,Documentation of conflicts of interest declared or uncovered.,, implementation,debarments,Debarments,Documentation of any debarments issued.,, "tender, contract, implementation",illustration,Illustrations,"Images intended to provide supporting information. The URL for images should be directly to an image file that applications can display as part of a gallery of images. At the tender stage, images can be illustrations of goods, works or services needed or for sale. At the implementation stage, images can be illustrations or visual evidence of physical progress.",, diff --git a/schema/codelists/unitClassificationScheme.csv b/schema/codelists/unitClassificationScheme.csv index 4b2116b91..73229582b 100644 --- a/schema/codelists/unitClassificationScheme.csv +++ b/schema/codelists/unitClassificationScheme.csv @@ -1,3 +1,3 @@ Code,Title,Description UNCEFACT,UN/CEFACT Recommendation 20,Use the common code from the latest version of the UN/CEFACT Recommendation 20 list of 'Codes for Units of Measure Used in International Trade'. -QUDT,"Quantities, Units, Dimensions and Data Types Ontologies",Use the [QUDT Code](http://qudt.org) value. +QUDT,"Quantities, Units, Dimensions and Data Types Ontologies",Use the [QUDT Code](https://www.qudt.org) value. diff --git a/schema/dereferenced-release-schema.json b/schema/dereferenced-release-schema.json index 415dc2187..ae77bd7d8 100644 --- a/schema/dereferenced-release-schema.json +++ b/schema/dereferenced-release-schema.json @@ -628,7 +628,7 @@ "object", "null" ], - "description": "Additional classification information about organizations can be provided using organization details extensions that define particular fields and classification schemes.", + "description": "Additional information about the organization.", "title": "Details", "properties": { "scale": { @@ -1236,7 +1236,7 @@ }, "amount": { "title": "Amount", - "description": "The value reserved for the future contract(s), within the budget. A negative value indicates income to the budget as a result of the future contract(s), rather than expenditure. If the budget is drawn from multiple sources or extends over multiple years, the budget breakdown extension can be used. This field should not be used to report the total value of the budget line that will fund the future contract(s).", + "description": "The value reserved for the future contract(s), within the budget. A negative value indicates income to the budget as a result of the future contract(s), rather than expenditure. This field should not be used to report the total value of the budget line that will fund the future contract(s).", "type": "object", "properties": { "amount": { @@ -1768,7 +1768,7 @@ }, "milestones": { "title": "Planning milestones", - "description": "A list of milestones associated with the planning process.", + "description": "Milestones associated with the planning process.", "type": "array", "items": { "title": "Milestone", @@ -2435,7 +2435,7 @@ }, "description": { "title": "Tender description", - "description": "A summary description of the tender. This complements any structured information provided using the items array. Descriptions should be short and easy to read. Avoid using ALL CAPS.", + "description": "A summary description of the tender. Descriptions should be short and easy to read. Avoid using ALL CAPS.", "type": [ "string", "null" @@ -3078,7 +3078,7 @@ }, "additionalClassifications": { "title": "Additional classifications", - "description": "An array of additional classifications for the item.", + "description": "Additional classifications for the item.", "type": "array", "items": { "title": "Classification", @@ -4623,7 +4623,7 @@ }, "submissionMethodDetails": { "title": "Submission method details", - "description": "Information about the methods by which bids are submitted. 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.", + "description": "Information about how to submit bids. 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.", "type": [ "string", "null" @@ -4682,7 +4682,7 @@ }, "enquiryPeriod": { "title": "Enquiry period", - "description": "The period during which potential bidders may submit questions and requests for clarification to the buyer or the procuring entity. Details of how to submit enquiries should be provided in attached notices, or in submissionMethodDetails. Structured dates for when responses to questions will be made can be provided using tender milestones.", + "description": "The period during which potential bidders may submit questions and requests for clarification to the buyer or the procuring entity.", "type": "object", "properties": { "startDate": { @@ -4724,7 +4724,7 @@ }, "hasEnquiries": { "title": "Has enquiries?", - "description": "A true/false field to indicate whether any enquiries were received during the tender stage. Structured information on enquiries that were received, and responses to them, can be provided using the enquiries extension.", + "description": "Whether any enquiries were received.", "type": [ "boolean", "null" @@ -4752,7 +4752,7 @@ }, "selectionCriteria": { "title": "Selection criteria", - "description": "The minimum requirements for potential suppliers to participate in the contracting process. Selection criteria ensure that a potential supplier has the legal and financial capacities and the technical and professional abilities to perform the contract. More structured information can be provided using the selection criteria extension.", + "description": "The minimum requirements for potential suppliers to participate in the contracting process. Selection criteria ensure that a potential supplier has the legal and financial capacities and the technical and professional abilities to perform the contract.", "type": [ "string", "null" @@ -4894,7 +4894,7 @@ }, "tenderers": { "title": "Tenderers", - "description": "All organizations that submit a bid. More detailed information on bids and the bidding organization can be provided using the bid extension.", + "description": "All organizations that submit a bid.", "type": "array", "items": { "properties": { @@ -5568,7 +5568,7 @@ }, "milestones": { "title": "Milestones", - "description": "A list of milestones associated with the tender.", + "description": "Milestones associated with the tender: for example, the date on which responses to enquiries are published.", "type": "array", "items": { "title": "Milestone", @@ -8098,7 +8098,7 @@ }, "additionalClassifications": { "title": "Additional classifications", - "description": "An array of additional classifications for the item.", + "description": "Additional classifications for the item.", "type": "array", "items": { "title": "Classification", @@ -10142,7 +10142,7 @@ }, "additionalClassifications": { "title": "Additional classifications", - "description": "An array of additional classifications for the item.", + "description": "Additional classifications for the item.", "type": "array", "items": { "title": "Classification", @@ -10789,7 +10789,7 @@ "properties": { "transactions": { "title": "Transactions", - "description": "A list of the spending transactions made against this contract", + "description": "The spending transactions made against this contract.", "type": "array", "items": { "type": "object", @@ -13477,7 +13477,7 @@ }, "milestones": { "title": "Contract milestones", - "description": "A list of milestones associated with the finalization of this contract.", + "description": "Milestones associated with the finalization of this contract.", "type": "array", "items": { "title": "Milestone", @@ -14450,7 +14450,7 @@ }, "amount": { "title": "Amount", - "description": "The value reserved for the future contract(s), within the budget. A negative value indicates income to the budget as a result of the future contract(s), rather than expenditure. If the budget is drawn from multiple sources or extends over multiple years, the budget breakdown extension can be used. This field should not be used to report the total value of the budget line that will fund the future contract(s).", + "description": "The value reserved for the future contract(s), within the budget. A negative value indicates income to the budget as a result of the future contract(s), rather than expenditure. This field should not be used to report the total value of the budget line that will fund the future contract(s).", "type": "object", "properties": { "amount": { @@ -14982,7 +14982,7 @@ }, "milestones": { "title": "Planning milestones", - "description": "A list of milestones associated with the planning process.", + "description": "Milestones associated with the planning process.", "type": "array", "items": { "title": "Milestone", @@ -15649,7 +15649,7 @@ }, "description": { "title": "Tender description", - "description": "A summary description of the tender. This complements any structured information provided using the items array. Descriptions should be short and easy to read. Avoid using ALL CAPS.", + "description": "A summary description of the tender. Descriptions should be short and easy to read. Avoid using ALL CAPS.", "type": [ "string", "null" @@ -16292,7 +16292,7 @@ }, "additionalClassifications": { "title": "Additional classifications", - "description": "An array of additional classifications for the item.", + "description": "Additional classifications for the item.", "type": "array", "items": { "title": "Classification", @@ -17837,7 +17837,7 @@ }, "submissionMethodDetails": { "title": "Submission method details", - "description": "Information about the methods by which bids are submitted. 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.", + "description": "Information about how to submit bids. 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.", "type": [ "string", "null" @@ -17896,7 +17896,7 @@ }, "enquiryPeriod": { "title": "Enquiry period", - "description": "The period during which potential bidders may submit questions and requests for clarification to the buyer or the procuring entity. Details of how to submit enquiries should be provided in attached notices, or in submissionMethodDetails. Structured dates for when responses to questions will be made can be provided using tender milestones.", + "description": "The period during which potential bidders may submit questions and requests for clarification to the buyer or the procuring entity.", "type": "object", "properties": { "startDate": { @@ -17938,7 +17938,7 @@ }, "hasEnquiries": { "title": "Has enquiries?", - "description": "A true/false field to indicate whether any enquiries were received during the tender stage. Structured information on enquiries that were received, and responses to them, can be provided using the enquiries extension.", + "description": "Whether any enquiries were received.", "type": [ "boolean", "null" @@ -17966,7 +17966,7 @@ }, "selectionCriteria": { "title": "Selection criteria", - "description": "The minimum requirements for potential suppliers to participate in the contracting process. Selection criteria ensure that a potential supplier has the legal and financial capacities and the technical and professional abilities to perform the contract. More structured information can be provided using the selection criteria extension.", + "description": "The minimum requirements for potential suppliers to participate in the contracting process. Selection criteria ensure that a potential supplier has the legal and financial capacities and the technical and professional abilities to perform the contract.", "type": [ "string", "null" @@ -18108,7 +18108,7 @@ }, "tenderers": { "title": "Tenderers", - "description": "All organizations that submit a bid. More detailed information on bids and the bidding organization can be provided using the bid extension.", + "description": "All organizations that submit a bid.", "type": "array", "items": { "properties": { @@ -18782,7 +18782,7 @@ }, "milestones": { "title": "Milestones", - "description": "A list of milestones associated with the tender.", + "description": "Milestones associated with the tender: for example, the date on which responses to enquiries are published.", "type": "array", "items": { "title": "Milestone", @@ -21308,7 +21308,7 @@ }, "additionalClassifications": { "title": "Additional classifications", - "description": "An array of additional classifications for the item.", + "description": "Additional classifications for the item.", "type": "array", "items": { "title": "Classification", @@ -23346,7 +23346,7 @@ }, "additionalClassifications": { "title": "Additional classifications", - "description": "An array of additional classifications for the item.", + "description": "Additional classifications for the item.", "type": "array", "items": { "title": "Classification", @@ -23993,7 +23993,7 @@ "properties": { "transactions": { "title": "Transactions", - "description": "A list of the spending transactions made against this contract", + "description": "The spending transactions made against this contract.", "type": "array", "items": { "type": "object", @@ -26681,7 +26681,7 @@ }, "milestones": { "title": "Contract milestones", - "description": "A list of milestones associated with the finalization of this contract.", + "description": "Milestones associated with the finalization of this contract.", "type": "array", "items": { "title": "Milestone", @@ -27502,7 +27502,7 @@ "properties": { "transactions": { "title": "Transactions", - "description": "A list of the spending transactions made against this contract", + "description": "The spending transactions made against this contract.", "type": "array", "items": { "type": "object", @@ -30878,7 +30878,7 @@ }, "amount": { "title": "Amount", - "description": "The value reserved for the future contract(s), within the budget. A negative value indicates income to the budget as a result of the future contract(s), rather than expenditure. If the budget is drawn from multiple sources or extends over multiple years, the budget breakdown extension can be used. This field should not be used to report the total value of the budget line that will fund the future contract(s).", + "description": "The value reserved for the future contract(s), within the budget. A negative value indicates income to the budget as a result of the future contract(s), rather than expenditure. This field should not be used to report the total value of the budget line that will fund the future contract(s).", "type": "object", "properties": { "amount": { @@ -34187,7 +34187,7 @@ "object", "null" ], - "description": "Additional classification information about organizations can be provided using organization details extensions that define particular fields and classification schemes.", + "description": "Additional information about the organization.", "title": "Details", "properties": { "scale": { @@ -34299,7 +34299,7 @@ }, "additionalClassifications": { "title": "Additional classifications", - "description": "An array of additional classifications for the item.", + "description": "Additional classifications for the item.", "type": "array", "items": { "title": "Classification",