Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

submissionTerms: define catalog #159

Closed
JachymHercher opened this issue Feb 7, 2021 · 3 comments
Closed

submissionTerms: define catalog #159

JachymHercher opened this issue Feb 7, 2021 · 3 comments
Labels
Community Relates to a regular extension Documentation Involves editing the readme or metadata Schema Involves editing the schema
Milestone

Comments

@JachymHercher
Copy link

JachymHercher commented Feb 7, 2021

Based on open-contracting/standard#396 (comment), we should define electronic catalogs in https://extensions.open-contracting.org/en/extensions/submissionTerms/master/. I suggest using a definition based on open-contracting/standard@d54ca05, e.g.

An electronic format (typically prescribed by the buyer) that participants in the contracting process must follow when exchanging information about technical specifications, evaluation criteria, bids, lots, etc.


Note: the extension uses "catalogue" while the guidance "catalog". Catalog is more popular in US English, so should be the default option, but I'm not sure whether we don't want to stick to catalogue instead because it is already a field (changing a field has bigger impact than changing documentation) and because it is an EU extension and the EU uses "catalogue".

@ColinMaudry
Copy link
Member

ColinMaudry commented Feb 20, 2021

Beside UK and Scotland, I don't think that the submissionTerms extension has been broadly adopted. I suggest:

  • we fix the spelling of "catalog" in the schema
  • we inform the adopters we know of

@jpmckinney jpmckinney added Community Relates to a regular extension Documentation Involves editing the readme or metadata Schema Involves editing the schema labels Feb 22, 2021
@jpmckinney
Copy link
Member

jpmckinney commented Jun 7, 2023

This extension is planned to be merged into OCDS 1.2: open-contracting/standard#1183

We can make/discuss the rename when doing that merge. This is less disruptive to the two publishers, as they can continue using this extension with the original naming. They will only need to rename fields when upgrading to OCDS 1.2.

@jpmckinney
Copy link
Member

I've added a definiton to the field description, which closes this issue.

open-contracting-extensions/ocds_submissionTerms_extension@db48678

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community Relates to a regular extension Documentation Involves editing the readme or metadata Schema Involves editing the schema
Projects
None yet
Development

No branches or pull requests

3 participants