Working Group Meeting

Date: 23/01/2025  
Participants: Peter Borresen, Paul Donohoe, Yves Jordan
Model editor: Andreea Passare
Note editor: Achilles Dougalis

Agenda

  • eFulfilment meeting regarding Receipt Advice.

  • Unmappable eForms fields in PIN, CEI and T02 notice subtypeshttps://github.com/OP-TED/ePO/issues/726[#726]

  • Phttps://github.com/OP-TED/ePO/issues/529[otential problem with modelling of epo:Period ]ePO #529

  • Mapping of at-voc:timeperiod to the OWL Time Ontology ePO #681

Discussions

During the first part of the WGM, eFulfilment and specifically Receipt Advice was discussed: Definitions and clarifications were given for specific Business Groups, and Business Terms in the Receipt Advice data model.

Regarding the “Unmappable eForms fields in PIN, CEI and T02 notice subtypeshttps://github.com/OP-TED/ePO/issues/726[#726]” github issue:

  • Examples of T01 , and T02 eForms were given to the WGM.

  • Regarding the following fields: Τhey are just for T02 and are about a Tender, so they should be put in a class on the level of epo:TenderAwardOutcome. This class should be named epo:TenderAwardOutcomeInformation. Another class: epo:ContractCondition was added.

    • OPP-080-Tender: Kilometers Public Transport: Represented as a predicate to the epo:Quantity class.

    • OPP-035-Tender: Revenues Allocation of tickets sales code uses the following codelist With only one value.

    • OPP-032-Tender: Revenues Allocation: Add epo:hasTicketsSalesRevenueAllocation xsd:decimal, [0..1] attribute on epo:TenderAwardOutcomeInformation.

    • OPP-030-Tender: Contract conditions Code: uses the following codelist.

    • OPP-031-Tender: Contract Conditions Description (other than revenue allocation): epo:hasContractConditionsDescription rdf:plainLiteral. [0..1] attribute on epo:ContractConditio.n

    • OPP-033-Tender: Penalties and Rewards Code: has only one value (found here). Not going to implement.

    • OPP-034-Tender: Penalties and Rewards Description: epo:hasPenaltiesAndRewardsDescription rdf:plainLiteral [0..1] attribute to to epo:TenderAwardOutcomeInformation.

KCzrishwAAAPy6IAAAACDbpXdNkIUgAAAAvygIAAAAyHbbCZCNPj9SAADwS4AAAAAAAAAA4AGBAAAAAAAAAOABgQAAAAAAAADgAYEAAAAAAAAA4AGBAAAAAAAAAOABgQAAAAAAAADgAYEAAAAAAAAA4AGBAAAAAAAAAOABgQAAAAAAAADgAfltO7kJAAAAAAAAeCAgAAAAAAAAAHhAIAAAAAAAAAB4QCAAAAAAAAAAeED+H2itRRxdk7YeAAAAAElFTkSuQmCC
  • BT-127-Notice:No modification will happen for now.

cXfckNAKrHAJr3udMi82hMAPAfCbarVEStLmMAAAAASUVORK5CYII=

Action Points

  • Create a Github issue: For the Receipt Advice ePO diagram: To represent the action-code and reject-reasons codelists also at the level of the epo-ful:ReceiptAdvice.

mqVvqbbcXMAAAAAElFTkSuQmCC