csnyulas

Mapping of eForms field `OPT-050-Part` (Document Status)

3

EPO does not seem to provide a direct representation of the eForms SDK filed `OPT-050-Part` (Document Status), which according to the eForms team represents: _References to tender documents. Determines if...

New eForms subtype required

2

Starting with **eForms SDK v1.12** there is a new eForms subtype `E6`: https://docs.ted.europa.eu/eforms/1.12/reference/code-lists/notice-subtype.html (which was [not present in SDK 1.11](https://docs.ted.europa.eu/eforms/1.11/reference/code-lists/notice-subtype.html)) So, to allow a complete mapping of the values of...

Is the property `epo:hasReceivedSubmissionType` still needed? (Re: mapping of eForms field `BT-760-LotResult` "Received Submissions Type")

1

While mapping the eForms field `BT-760-LotResult` (Received Submissions Type), we observed that although in ePO the `epo:SubmissionStatisticalInformation` class provides a property `epo:hasReceivedSubmissionType` that points to `at-voc:received-submission-type`, as it can be...

Alignment between eForms and ePO representation of contract modifications

1

While exploring the possible mappings of the Contract Modification information encoded in **eForms** to **ePO 4.0.0**, we realized that there is quite significant discrepancy between the two representations, which is...

`epo:ContractLotCompletionInformation` should have relation to `epo:LotGroup` also

2

While mapping the eForms fields under the node `ND-TenderAggregatedAmounts` (i.e. Tender Payment Value `BT-779-Tender`, Tender Payment Value Additional Information `BT-780-Tender` and Tender Penalties `BT-782-Tender`), we discovered a discrepancy between the...

Is there a field that links a ReviewDecision to a ReviewRequest

3

As described in https://github.com/OP-TED/ePO/issues/777 the ePO ontology defines a mandatory property that links every `epo:ReviewDecision` instance to one `epo:ReviewRequest` instance, with the meaning that the given decision "resolves" or "answers"...