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

[csnyulas]

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?) applies. The possible values are provided in this table: https://docs.ted.europa.eu/eforms/latest/schema/all-in-one.html#_referring_to_sections_of_a_notice

ePO 4.0.0 provides the following model:

While many of the possible values could be dereferenced, and appropriate IRIs for the referenced element(s) can be created, as part of the XML to RDF mapping process, some of them, especially those that are not referring to a particular technical id, are not so straightforward.

Although the current ePO model, which provides the epo:hasElementReference attribute to link directly to a notice element through its IRI, is nice it is likely not fully appropriate for all cases, and it would be more safe to provide a model where the the epo:ReviewObject would have a epo:relatesToEFormSectionIdentifier relationship to a adms:Identifier, similar to how it is done in the modeling of epo:ChangeInformation and epo-con:ContractModificationInformation. That would make the mapping of field BT-786-Review similar to that of BT-13716-notice, BT-1501(p)-Contract and BT-1501(p)-Contract:

Class Path: epo:ReviewRequest / epo:ReviewObject / adms:Identifier / rdf:PlainLiteral Property Path: ?this epo:refersToPreviousReview / epo:relatesToEFormSectionIdentifier / skos:notation ?value .

Does this field apply to ReviewDecision as well?

[AchillesDougalis]

Hello, there has already been an update on the Review concepts mentioned here: https://github.com/OP-TED/ted-rdf-mapping-eforms/issues/84. According to your suggestions and that update, a predicate epo:relatesToEFormSectionIdentifier [0..*] from epo:Document to adms:Identifier would solve the problem, and we could also delete the attribute epo:hasElementReference from epo:Document that was originally created for epo:ReviewObject.

[andreea-pasare]

As of ePO 5.0.0, the following model is implemented:

Note that the epo:ReviewInformation class was added, having the following properties:

• the epo:hasElementReference was moved from the Document level to the epo:ReviewInformation level
• the epo:relatesToEFormSectionIdentifier property was added
• a epo:ReviewInformation may concern a epo:ReviewRequest or a epo:ReviewDecision