Working Group meeting

Date: 24/01/2023
Participants: Jana Ahmad, Laszlo Ketszeri,, Natalie Muric, Csongor Nyulas, Giampaolo Sellito
Model editor: Andreea Pas─âre
Note editor: Eugeniu Costetchi

Agenda

Discuss github following issues:

  • Standard form mappings - TED-SWS github issues:

  • Standard form mappings - ePO github issues:

Discussion

GH 119

  • When we have missing mapping in the technical mapping but the data exists in the standard forms, then we should add the remark in the RDF output as a rdfs:comment. ==== GH 418

  • The generalisation statement between a role and its type (AcquiringParty, SellerParty or AuxiliaryParty) should not be present in the technical mapping.

  • This ticket and https://github.com/OP-TED/ted-rdf-mapping/issues/289 were closed, with the same resolution.

3mAMQLGv5mEAAAAASUVORK5CYII=

GH 419

The property epo:hasLotAwardLimit has been deleted.

ecfgQcWzhmwAAAABJRU5ErkJggg==

epo:hasMaximumNumberOfLotsToBeAwarded is kept.

GH 420

  • In the standard form, we have just generalised information (generalisation criterion) at the procedure level.

  • And the procurement criteria is specified for the lot level .

  • In the standard form, procedure specifies criteria summary (so we can have summary criterion at the procedure level .).

  • We should differentiate between criteria and criteria summary

  • Create participation criterion class in a lot level (so we have 4 criteria now).

  • Participation is at the submission level.

  • Participation conditions should be even before submission

  • Two approaches for Criteria modelling (concept and instance diagrams) have been presented and are depicted below.

Example 1

yIR40IZYXGeAAAAAElFTkSuQmCC
w7EgibL+4XIAQAAABSCyAEAAAAUgsgBAAAAFILIAQAAABSCyAEAAAAUgsgBAAAAFILIAQAAABSCyAEAAAAUgsgBAAAAFILIAQAAABSCyAEAAAAUgsgBAAAAFILIAQAAABSCyAEAAAAUwifLC09Co9Wnh4tXBgAAAMgLkQMAAAAoBJEDAAAAKASRAwAAACgEkQMAAAAohI4iRzwWAAAAIC9EDgAAAKAQRA4AAACgEEQOAAAAoBBEDgAAAKAQRA4AAACgEEQOAAAAoBBEDgAAAKAQRA4AAACgEEQOAAAAoBBEDgAAAKAQRA4AAACgEEQOAAAAoBBEDgAAAKAQRA4AAACgEEQOAAAAoBD+H4fyFIxTZr5jAAAAAElFTkSuQmCC

Example 2

8BBMyJXFrigRQAAAAASUVORK5CYII=
P+SOUqRgPVgAAAABJRU5ErkJggg==
  • Submission terms:

    • Submission terms: rules for submission

    • Submission terms has participation condition

    • Participation conditions had reserved procurement.

hHAAAAEgIwjkAAACQEIRzAAAAICEI5wAAAECCEM4BAACAhCCcAwAAAAlBOAcAAAAS4n9cFkMmx2ncXgAAAABJRU5ErkJggg==