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

BUG: > v.1.12 contradicts ESC guide on the use of BT-750 #1054

Open
rkottmann opened this issue Oct 25, 2024 · 2 comments
Open

BUG: > v.1.12 contradicts ESC guide on the use of BT-750 #1054

rkottmann opened this issue Oct 25, 2024 · 2 comments

Comments

@rkottmann
Copy link

rkottmann commented Oct 25, 2024

After some investigation we figured that your way of implementing the guide on Exclusion and Selction Criteria makes it impossible for us to implement a rquired German national tailoring.

In short: Please allow BT-750 also in case of using the code for procurement document in BT-821.

For details see please see: https://code.europa.eu/eproc/eforms/crs/-/issues/72 (there are also issues on the specification level..)

@rkottmann rkottmann changed the title > v.1.12 contradicts ESC guide on the use of BT-750 BUG: > v.1.12 contradicts ESC guide on the use of BT-750 Oct 25, 2024
@bertrand-lorentz
Copy link
Contributor

While having a quick look at this issue, I got a bit confused because I couldn't find a rule involving BT-750-Lot and BT-821-Lot directly.
So here's my understanding, to try to help clarify the issue.
The SDK currently has 2 sets of rules that apply on various notice types:

  1. If BT-821-Lot != 'epo-notice' then BT-809-Lot is forbidden
  2. If BT-809-Lot is not present, then BT-750-Lot is forbidden

As a logical consequence of those 2 rules, if BT-821-Lot != 'epo-notice' then BT-750-Lot is forbidden.

@ferrakaop
Copy link

We provided some options in https://code.europa.eu/eproc/eforms/crs/-/issues/72 for the technical/implementation point of view. We should get some more policy input before we adjust the SDK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants