csnyulas

Unmappable eForms fields in PIN, CEI and T02 notice subtypes

2

While trying to map the fields that can be found only in PIN, CEI and T01/T02 eForms notice subtypes, we encountered the following fields that do not seem to be...

As part of the [eForms to RDF mappings](https://github.com/OP-TED/ted-rdf-mapping-eforms) both eForms SDK fields `BT-157-LotsGroup` and `BT-271-LotsGroup` are mapped to the property `epo:hasLaunchFrameworkAgreementMaximumValue`. This was accepted as part of the competition and...

Mapping of eForms fields `BT-808-Review` (Review Applicant Identifier) and `BT-807-Review` (Review Body Identifier)

3

In ePO 4.0.0 there is no relation between the `epo:ReviewRequest` and the `epo:ReviewRequester`, nor between `epo:ReviewDecision` and the `epo:Reviewer`. This makes the mapping of the eForms fields `BT-808-Review` (Review Applicant...

Moving properties `epo:isWithdrawn`, `epo:hasWithdrawalDate`, `epo:hasWithdrawalReason` and `epo:hasReviewRequestFee` from `epo:ReviewRequest` to`epo:ReviewDecision`

2

According to the eForms team's response to this issue https://github.com/OP-TED/eForms-SDK/issues/1187, the properties `epo:isWithdrawn`, `epo:hasWithdrawalDate`, `epo:hasWithdrawalReason` and `epo:hasReviewRequestFee` should be on the class `epo:ReviewDecision` , NOT on the `epo:ReviewRequest` class. If...

How is the relationship between `epo:ReviewDecision` and `epo:ReviewRequest` represented in eForms?

2

The property `epo:resolvesReviewRequest` in ePO 4.0.0 (which will be replaced with the property `epo:resolvesReviewRequest` in ePO 5.0.0, according to #756) is supposed to link a `epo:ReviewDecision` to a `epo:ReviewRequest`, as...

Cardinality restriction of `epo:hasMainActivity` causes SHACL shape violation

1

As described in issue https://github.com/OP-TED/eForms-SDK/issues/1186, we have encountered many notices where both the "Activity Authority" (field `BT-10-Procedure-Buyer`) and the "Activity Entity" (field `BT-610-Procedure-Buyer`) is specified. I assume that this is...

Mapping of eForms field `BT-786-Review` (Review Notice Section Identifier)

2

The eForms field `BT-786-Review` (Review Notice Section Identifier), which was introduced in SDK v1.13, provides a references to a "section" of the current notice to which a ReviewRequest (or ReviewDecision?)...

`epo:SubmissionTerm` inheritance is wrong

1

According to the [submission term ](https://docs.ted.europa.eu/EPO/4/_attachments/html_reports/ePO/index.html?goto=1:1:7:5:150) diagram in ePO 4.0.0 `epo:SubmissionTerm` is a subclass of both `epo:ProcedureSpecificTerm` and `epo:LotSpecificTerm`. This is conceptually wrong, since according to the OWL semantics (which...

Mapping of eForms fields `BT-509-Organization-Company`, `BT-500-Organization-TouchPoint` and `BT-509-Organization-TouchPoint`

1

The following eForms fields do not have direct correspondence in ePO (and therefore cannot be mapped to ePO 4.0.0): - `BT-509-Organization-Company` (Organisation eDelivery Gateway) - `BT-500-Organization-TouchPoint` (Name) - `BT-509-Organization-TouchPoint` (eDelivery...

Linking roles to PlannedProcurementParts (Mapping of fields `OPT-301-Part-FiscalLegis`, `OPT-301-Part-EnvironLegis`, `OPT-301-Part-EmployLegis`, `OPT-301-Part-TenderReceipt`, `OPT-301-Part-TenderEval`, `OPT-301-Part-AddInfo` and `OPT-301-Part-DocProvider`)

1

This issue is about the mapping of various roles that are related to the "PlannedProcurementParts" in eForms: - `OPT-301-Part-FiscalLegis` (or `ND-PartFiscalLegislation`) --> **epo:TaxInformationProvider** - `OPT-301-Part-EnvironLegis` (or `ND-PartEnvironmentalLegislation`) --> **epo:EnvironmentalProtectionInformationProvider** -...