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

[csnyulas]

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 the language is official or not, because only those that are official can be used in court of law.

[AchillesDougalis]

Although it is called document status, OPT-050-Part seems to be the equivalent of the OPT-050-Lot (both fields were valid from eForms SDK versions 1.3-1.8).

OP feedback for OPT-050-Lot reads that this is not to be mapped explicitly. Rather, it is used as part of the XPath expression in fields BT-708-Lot and BT-737-Lot, to specify whether the language of a procurement document is an official or unofficial language.

In the same way, perhaps this could be mapped by using fields BT-708-Part and BT-737-Part.

[andreea-pasare]

It relates to https://github.com/OP-TED/ePO/issues/732

[andreea-pasare]

The mapping of OPT-050-Part is done via OPT-050-Lot, since a epo:PlannedProcurementPart foresees a epo:Lot as depicted in the diagram below:

Using the relationship epo:isSubjectToLotSpecificTerm we can get to epo:AccessTerm where the language (official or unofficial) of the available procurement documents is provided as depicted in the diagram below:

Given the fact that the Documents Official Language and Documents Unofficial Language fields (BT-708-Part, BT-737-Part, BT-708-Lot, BT-737-Lot) in eForms are mutually exclusive, the Document status is inferred using the following logic:

• if the epo:providesProcurementDocumentsInOfficialLanguage is used, then the language of the provided procurement documents is official
• if the epo:providesProcurementDocumentsInUnofficialLanguage is used, then the language of the provided procurement documents is unofficial