-
Notifications
You must be signed in to change notification settings - Fork 3
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
BT-747, BT-752: Check whether to use requirements or selectionCriteria extension #97
Comments
This is also relevant to the following business terms:
Currently, the guidance uses the selectionCriteria extension. |
For now, just focus on which to use in eForms. Once decided, the issue linked in the description can be addressed. |
BT-747 could be expressed using the requirements extension by adding Due to the limited documentation and examples in the eForms SDK, I'm struggling to assess whether BT-752 could be expressed using the requirements extension. For example, I can find no documentation nor examples of how some of the codes in the number weight codelist (e.g. The selection criteria extension seems like a safer option since it basically reproduces the eForms model so there shouldn't be any issues using it to express data from eForms. Another benefit of using the selection criteria extension is consistency with the modelling of similar concepts in the award criteria extension. @jpmckinney are you happy to use the selection criteria on that basis or should I move on to assessing the other business terms listed in #97 (comment) and leave BT-752 as a question mark for now? |
Hmm, let's go with the selection criteria extension, as it does seem like the safer option. I have a vague memory now that we created the extension because those number weight, etc. fields weren't expressible using the requirements extension – not sure if CCCEV can express them (or the new version of CCCEV). |
Sounds good. All the business terms mentioned in this issue are already mapped to the selection criteria extension so I think the issue can be closed. |
See open-contracting/ocds-extensions#170
The text was updated successfully, but these errors were encountered: