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

Question about modelling section V.0.4: Contract/lot/concession/prize NOT awarded #424

Open
csnyulas opened this issue Jun 9, 2023 · 0 comments
Assignees
Labels
type: feature request something requested to be implemented in a future release type: implementation question something needs clarified, refined or decided before the implementation can continue

Comments

@csnyulas
Copy link
Contributor

csnyulas commented Jun 9, 2023

In most forms one of the first questions in Section V is about the whether a "procurement element" has been awarded or not.

In forms that are based on directive 24 or 25 (such as F03, F06, F21, F22) the question is "A contract/lot is awarded", while for forms that are based on directive 23 (such as F23, F25) the question is "A concession/lot is awarded".

In all these cases a negative answer will be encoded as
AWARD_CONTRACT/NO_AWARDED_CONTRACT, which will be converted into a
" epo:LotAwardOutcome instance epo:hasAwardStatus <http://publications.europa.eu/resource/authority/winner-selection-status/clos-nw>" RDF triple.

image

In case of form F13 the question is "The contest was terminated without an award or attribution of prizes" , where a positive answer (i.e. the constest was terminated") is encoded as
RESULTS/NO_AWARDED_PRIZE, which will be also converted into a
" epo:LotAwardOutcome instance epo:hasAwardStatus <http://publications.europa.eu/resource/authority/winner-selection-status/clos-nw>" RDF triple.

image

Questions:

  1. As part of issue Feedback F13 (issue 6, TM): Section V.0.4: It is not clear why there are three empty rows. #355, it was suggested that for the RESULTS/NO_AWARDED_PRIZE XPath in F13 we assert also the
    " tedm:ProcurementProcessInformation instance epo:isCompetitionTerminated true" statement
    (see this comment)
    Would it be advisable/correct/necessary to do the same for the other forms as well, in case there is a match for the AWARD_CONTRACT/NO_AWARDED_CONTRACT XPath?
  2. Both the NO_AWARDED_CONTRACT and NO_AWARDED_PRIZE XML elements can have either a PROCUREMENT_DISCONTINUED or PROCUREMENT_UNSUCCESSFUL child element, depending on what is selected in the V.1.1.1 and V.1.1.2 fields. Does this choice has any effect on the validity of the previous statement(s), i.e. "epo:hasAwardStatus at-voc:winner-selection-status/clos-nw" and "epo:isCompetitionTerminated true"? (i.e. is it possible that the presence of one of those sub-elements, e.g. PROCUREMENT_UNSUCCESSFUL would mean that the competition is not necessarily closed?)
@csnyulas csnyulas added type: feature request something requested to be implemented in a future release type: implementation question something needs clarified, refined or decided before the implementation can continue labels Jun 9, 2023
@csnyulas csnyulas added this to the 2023-planning milestone Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request something requested to be implemented in a future release type: implementation question something needs clarified, refined or decided before the implementation can continue
Projects
None yet
Development

No branches or pull requests

4 participants