Working Group meeting 11/04/2023

Date: 11/04/2023
Participants: Natalie Muric, Sellitto Giovanni Paolo
Model editor: Andreea Pasăre
Note editor: Jana Ahmad

Agenda

Continue discussing 1st draft of eContract Model with respect to the initial contract information requirements.

  • To continue from Award of the contract

Discussion

The WG continued to discuss and model the Award of the Contract in the eContract module, specifically in relation to the requirements for initial contract information. Our methodology involves assessing whether the following requirements are already covered by ePO. If they are, the working group will map them to ePO. If they are not covered, they will be implemented as follows. The bullet points represent the initial contract information requirements, while the sub-bullets indicate their mapping to ePO.

Award of the contract

  • Award identifier:

    • adms:identifier of the epo:AwardDecision

  • Award date

    • epo:hasAwardDecisionDate (type is changed to xsd:dateTime)

  • Award time

    • epo:hasAwardDecisionDate (type is changed to xsd:dateTime)

314dlAAAgAAM7N9axKeLcAfLMIMEgGCQABAMEgCCQQJAMEgACAYJAMEgASAYJAAEgwSAYJAAEAwSAIJBAkAwSAAIBgkA4Q1SkiRdawBf+WWwbSf+DwAAAABJRU5ErkJggg==
  • Winner economic operator

    • epo:Winner

  • Economic operator name

    • dct:title on the foaf:Agent

  • Economic operator identifier

    • epo:hasRegistrationCountry from org:Organization to at-voc:country

JXAAAAAElFTkSuQmCC
  • Documents

    • epo:Contract epo:associatedWith epo:Document

  • Attachment identifier

    • adms:identifier on epo:Document

  • Attachment description code

    • At-voc-new:document-type

  • Attached document

    • we do not provide the binary object, only URL (epo:hasAccessURL on the epo:Document)

YAAAAASUVORK5CYII=
  • Deliverable offered

    • epo:specifiesDeliverable epo:Item

  • Deliverable name

    • dct:title on the epo:Item

  • Deliverable description

    • dct:description on the epo:Item

  • Delivered quantity

    • epo-cat:hasQuantity from epo:Deliverable to epo:Quantity

v9UEkII6T0AAAAAAADw64CII4SQ31gAAAAAAADg12FkRRwAAAAAAAAAAMAogYgDAAAAAAAAAAAYAog4AAAAAAAAAACAIYCIAwAAAAAAAAAAGAKIOAAAAAAAAAAAgCGAiAMAAAAAAAAAABgCiDgAAAAAAAAAAIAhgIgDAAAAAAAAAAAYAog4AAAAAAAAAACAIYCIAwAAAAAAAAAAGAKIOAAAAAAAAAAAgCGAiAMAAAAAAAAAABgCiDgAAAAAAAAAAIAhgIgDAAAAAAAAAAAYAog4AAAAAAAAAACAIYCIAwAAAAAAAAAAGAKIOAAAAAAAAAAAgCGAiAMAAAAAAAAAABgCiDgAAAAAAAAAAIAhgIgDAAAAAAAAAAAYAog4AAAAAAAAAACAIYCIAwAAAAAAAAAAGAKIOAAAAAAAAAAAgCEQiDhCCCGEEEIIIYQQQsjg8v8Bm7AYG5PqRrMAAAAASUVORK5CYII=
  • Deliverable total amount:

    • epo:hasContractValue relation is created between epo:Contract and epo:MonetaryValue

y1xItra7zVrAAAAAElFTkSuQmCC
  • epo-con:ContractAmendment object is created with:

    • epo:emendsContract relation with epo:Contract.

    • epo:hasContractAmendmentDate property.

    • epo:providesUpdatedContractValue relation with epo:MonetaryValue

    • epo:hasContractAmendment relation with epo:Contract

mEwuQAAAABJRU5ErkJggg==
  • Contract Roles class is created to specify all roles that participant in Contact

x9QunatetNeMgAAAABJRU5ErkJggg==

Action:

  • Change xsd:date to xsd:dateTime.

  • proposal to adopt epo-cat:Deliverable into all modules

  • What’s the difference between a epo:Contractor and a epo-ord:Seller for all modules?