Working Group meeting

Clarify unpublished fields ticket (#712) and discuss the potential solutions.

It was explained that the problem is that currently unpublished fields cannot be mapped. To resolve that, the unpublished information needs to be properly modelled in the ontology.

It was clarified that the unpublished information is described using the following four business terms described here:

It is required to provide a way to describe different procurement concepts (like LotAwardCriteria) with these dedicated fields.

SDK explorer was used to identify fields that the unpublished information applies to. Relevant term identifiers contain the hidden field identifier in the parenthesis (for example "BT-195(BT-5422)-Lot").

The eForms expert explained that in XML representation the relevant fields can have special value to indicate that the information it’s not published (for example "-1" for monetary value).

It was concluded that it is required to map concepts as well as values.

The approach was further discussed. It was clarified that suitable object properties are required to link an ontology concept to unpublished information (epo:NonPublishedInformation class).

It was clarified that concepts that are in the scope of interest need to be treated independently (not associated with the Notice). NonPublishedInformation can be described for various concepts and it is not specific to the Notice. However, for the purpose of mapping it is required to make unpublished information reachable via notice.

The eForms expert estimated that there are about 120 unpublished fields as for now.

When discussing the possible approach, it was confirmed that it is sufficient to use a relative path to a value starting from the considered class (mappings).