Feedback F20 (issue 11, CM): VI.3 Consider adding Notice hasAdditionalInformation to EPO

[csnyulas]

VI.3 Should it be considered in the future to create Notice hasAdditionalInformation to map to.
Seeing the ContractModification Notice point to the Procedure is strange?

[csnyulas]

This seems to be a question that should be discussed in EPO meetings. Perhaps there should be an issue created on the EPO repository, and this one linked to that.

Regarding the suggestion to add the hasAdditionalInformation attribute to the epo:Notice class, we should not forget that a notice is in fact a document. What would it mean to add additional information on a notice document? Isn't this additional information in fact about something described in this document? If not the Procedure, then what?

[muricna]

A Jira Ticket has been created

[andreea-pasare]

In eForms, this section maps to BT-300 which belongs to BG-710 Additional Information that has the following description:

Additional information, which may differ per lot. In case of a prior information notice used only for information, this information may differ per part of the notice that may later become a lot or a self-standing procedure.

It looks like this should not be at the Notice level, but at the Procedure/Lot/PlannedProcurementPart level.
At the moment, we have epo:hasAdditionalInformation at epo:ProcurementObjectLevel which covers for both Procedure and Lot:

I propose to move the attribute at the epo:ProcurementElement in order to also cover for PlannedProcurementPart.

[muricna]

This maybe true but if we look at the notice as a whole should this not be an attribute of the notice. Is it not Notice hasAdditionalInformation a Contract or Procedure that hasAdditionalInformation seems strange