Working Group Meeting

Discuss new Github Issues related to eForms.

After checking eForms fields BT-808 and BT-807, predicate epo:specifiesReviewRequester was added on the level of epo:ReviewDecision.

Maybe in the future we can replace predicates epo:specifiesReviewer and epo:specifiesReviewRequester with just an epo:specifiesRole predicate.

Class epo:ReviewInformation was created.

Predicate epo:relatestoEFormsSectionIdentifier was added with domain epo:ReviewInformation and range adms:Identifier.

Attribute epo:hasElementReference was removed from epo:Document and added to epo:ReviewInformation.

Predicate epo:resolvesReviewRequest was renamed to epo:answersReviewRequest.

Indeed code list at-voc:received-submission-type seems to be redundant.

All the values of the code list were analysed and it was made sure that for each value of the code list there is an attribute on class epo:SubmissionStatisticalInformation that represents it.

The codelist at-voc:received-submission-type was removed.

epo:ProcedureSpecificTerm, epo:ContractSpecificTerm and epo:LotSpecificTerm classes were deleted and all terms that were specialisations of these classes are now specializations of epo:Term.

However, there are diagrams that show different points of view of specific terms. Eg, all the terms that were under epo:ProcedureSpecificTerm appear on a specific diagram as seen below. To discuss the business value for these diagrams in the future.

To create a diagram with all the relationships of epo:LotGroup