Working Group meeting 09/02/2023

Date: 09/02/2023
Participants: Fred van Blommestein, Alba Colomer, Wim Kok, Laszlo Ketszeri, Natalie Muric, Pietro Palermo, Sellitto Giovanni Paolo
Model editor: Eugeniu Costetchi
Note editor: Jana Ahmad

Agenda

  • Define epo:Project and epo:ProcurementProject

  • Continue on eOrdering open discussion

    • Goal is to ensure completeness of the current model

    • The current method of checking and depicting if the ePO model is complete regarding PEPPOL requirements is by having diagrams which clearly depict the necessary elements.

    • To be continued from ac:BuyerCustomerParty

Discussion

The WG discussed the definition of procurement project that links together the call for tender with an element that is not present in the Call for Tender but that is overarching multiple calls for tenders. It links together that are very different but are developed in the context and contribute to the same value. Note, Order refers to a project

rGxwAAAABJRU5ErkJggg==

The WG continued to discuss the Order diagram with respect to Peppol Order transaction 3.2 (T01) to be sure that they are compatible.

The current approach to assessing the completeness of the ePO model with respect to PEPPOL requirements involves determining whether the following requirements are already covered by ePO. If they are, the WG will map them to ePO. If they are not covered, they will be implemented as follows. The bullet points represent the PEPPOL requirements, while the sub-bullets indicate their mapping to ePO.

  • ac:BuyerCustomerParty

    • Order specifies a Buyer

    • We have Buyer party electronic address (cbc:EndpointID)

+AnGqd8LXYYQdAAAAAElFTkSuQmCC
  • Note: Order has always one buyer

  • Buyer has contactPoint and contactPoint hasInternetAddress

F+vJlnOFOa7GgAAAABJRU5ErkJggg==
  • A role has a channel

    • epo:Channel is added class Order

    • epo:exposesChannel relation is created between epp:AgentInRole and epo:channel{}y

      • epo:Channel has two properties

        • po:exposesChannelhasAddress property

        • epo:hasEndpointIdentifier

    • Consider creating a subclass AdHocChannel.

    • epo:hasEndpointIdentifier relation between epo:channel and adms:Identifier

AUzmr1VW3V+HAAAAAElFTkSuQmCC
  • cac:Party:

    • Is a party or agent in Order model (e.g., buyer, seller)

    • Organization which is a type of agent can have identifiers.

    • epo:hasLegalIdentifier relation is created between The eop:Organization and epo:Identifier

    • epo:hasTaxIdentifier relation is created between The eop:Organization and epo:Identifier

  • We have: Party name, Postal address, Party identification (adms:identifier)

  • cac:PartyTaxScheme:

    • TaxScheme class is created

    • epo-ord:TaxInformation Object is created

    • In epo:Identifier we have hasScheme

Actions

  • We need to discuss urgently access term and channel [OP and Meaningfy]

  • In order to align with Core Voc, it means we need to add cv:LegalEntity and org:FormalOrganization between org:Organization and epo:Business.