Code development platform for open source projects from the European Union institutions 🔵 EU Login authentication by SMS has been phased out. To see alternatives please check here

Skip to content

Estimated value between ranges

Rule Definition

When the estimated value is informed through a range, the estimated value used for analysis is the lower limit of the range.


Additional Information

Rule elaboration

There are several SHACL Rules to achieve this simplification, as there are different cases for obtaining the Estimated Value.

  • Result Notices:

The estimated value information comes from the relationship with NoticeAwardInformation. We will follow this path: epo:ResultNotice -> epo:announcesNoticeAwardInformation (epo:NoticeAwardInformation) -> epo:hasTotalAwardedValue (epo:MonetaryValue) -> epo:hasAmountValue.

A filter will be added to ensure that (epo:MonetaryValue) -> epo:hasCurrency is http://publications.europa.eu/resource/authority/currency/EUR.

  • Competition Notices:

A SPARQL query will be used to obtain the Estimated Value related to the procedure using the path: epo:CompetitionNotice -> epo:refersToProcedure (epo:Procedure) -> epo:hasEstimatedValue (epo:MonetaryValue) -> epo:hasAmountValue.

A filter will be added to ensure that (epo:MonetaryValue) -> epo:hasCurrency is http://publications.europa.eu/resource/authority/currency/EUR.

  • Estimated Value based on Lots:

A SPARQL query will be used to retrieve the epo:Lot elements related to the notice and sum the estimated values associated with each Lot, using the path: epo:Notice -> epo:announcesLotAwardOutcome (epo:LotAwardOutcome) -> epo:hasAwardedValue (epo:MonetaryValue) -> epo:hasAmountValue.

A filter will be added to ensure that (epo:MonetaryValue) -> epo:hasCurrency is http://publications.europa.eu/resource/authority/currency/EUR.

  • A construct query is used to add the triple that links the epo:Notice with the calculated Estimated Values.

Rule source

(Provide URL to legal source, if applicable)

Rule implementation

(Provide only URIs of formal encodings of the rules for execution. These are typically URIs of SHACL rules or RML maps. Each URI should be provided on a new line with no additional information)

Implementation note

(Provide additional implementation information if needed)

Related rules

#25

#82

#83

Related generic rule

(If the rule is a specialisation of a generic rule registered in this Rulebook, include here URL of that generic rule)

History note

(If applicable, add here a note about a previous state of the rule, before the Rulebook)

Edited by Enrique Jose Barcala Soto