Working Group meeting 25/04/2023

Date: 25/04/2023
Participants: Natalie Muric, Veit Jahns
Model editor: Andreea Pasăre
Note editor: Jana Ahmad

Agenda

Goal: Discuss the current status and any potential improvements/harmonisations needed for the eCatalogue, eFulfilment, and eOrdering modules.

  • Discuss removing "postAward" objects and considering them as a document.

  • Also, consider "epo-cat:announcesPostAwardObject."

  • Revise "epo-cat:hasExternalSpecification" property in the "epo-cat:item" object and consider deleting it since we have added "epo-cat:hasExternalSpecification" association between "epo-cat:Item" and "epo:Document."

  • Change eCat:Item to epo:Item

  • Discuss adopting "epo" as a uniform namespace prefix in the ePO model.

  • Revise the naming of "epo-cat:ItemDescription" to align it between modules.

  • Discuss aligning VAT and other tax categories between modules.

  • Propose using "TaxInformation" instead of "hasVATRate" and "hasVATCategory."

  • What is the difference between TaxInformationSchema and TaxInformation?

  • Discuss if "epo-ord:PriceDiscountInformation" and "epo-cat:ChargeInformation" are the same and align them across modules.

  • Propose changing "epo-cat:specifiesItem" to "epo:specifiesDeliverable."

  • Propose adopting "epo-cat:Deliverable" into all modules.

  • Discuss the difference between "epo:Contractor" and "epo-ord:Seller" for all modules.

  • Decide whether "epo:hasSerialID" should be at the Item level or the Batch level.

  • A party should have authorization. This needs to be modeled. Take into account the Certificate as well.

  • Discuss epo-ord:TaxInformation definition.

  • Discuss removing epo-ord:DeliveryTerm.

Discussion:

  • The WG Discussed removing "postAward" objects and considering them as documents, and also consider removing the 'epo-cat:announcesPostAwardObject' relation in the following modules.

    • ​ eNotice ​​

    • eOrdering ​​

    • eCatalogue ​​

    • eFulfilment

txIAcH9iivgBAABOAgIIAAAAAAAIPQIIAAAAAAAIPQIIAAAAAAAIPQIIAAAAAAAIvUcim+sCAAAAAAAQZgQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQegQQAAAAAAAQev8HU+pY4brTeroAAAAASUVORK5CYII=

  • The definition of epo-cat:Catalogue is changed to: A Document describing a set of Items offered for purchase that can be processed in an electronic way.

  • It is noted that Catalogue is part of the Contract

  • The WG approved to Remove "epo-cat:hasExternalSpecification" property in the "epo-cat:item" in Catalogue class

EFAHPJAAAAABJRU5ErkJggg==

  • The WG has agreed upon the use of 'epo' as the standardized namespace prefix in the ePO model.

8Bs01oDOcG8HcAAAAASUVORK5CYII=

  • The WG has proposed a change from 'epo-cat:ItemDescription' to 'epo-cat:ItemProperty'.

UcdpdFAINQAwAAwCDUAAAAMAg1AAAADAHlRtsrHoRAVgAAAABJRU5ErkJggg==

  • Should we retain both 'epo-cat:ChargeInformation' and 'epo-ord:PriceDiscountInformation', or are they identical in meaning?

    • The WG discussed the validity or appropriateness of using "epo-ord:PriceDiscountInformation" in the context of epo-cat:Price level.

      • The WG has agreed to keep 'epo-ord:PriceDiscountInformation' as part of the 'epo-cat:Price' level.

    • The WG deliberated on whether epo-cat:ChargeInformation aligns with the "epo-cat:Price" or "epo-cat:Line or epo-cat:Item level components.

      • The WG is considering the possibility of moving 'TaxInformation' to 'epo-cat:Item', but further investigation is required

LhQcEQRBEARBEARBEARBEEr+P56Ja0g4FqdaAAAAAElFTkSuQmCC

  • The WG has agreed to the proposal of using 'TaxInformation' as an alternative to 'hasVATRate' and 'hasVATCategory'.

CTzbI9ZDpxUAAAAASUVORK5CYII=

  • The WG has reached an agreement to eliminate 'epo-cat:specifiesItem' between 'epo-cat:Item' and 'epo:Deliverable', and to consider 'epo:Deliverable' as a type of 'epo-cat:Item'.

ViVpFgEAs2f4AgAAACBLhi8AAAAAsmT4AgAAACBLhi8AAAAAsmT4AgAAACBLhi8AAAAAsmT4AgAAACBLhi8AAAAAsmT4AgAAACBLhi8AAAAAsmT4AgAAACBLhi8AAAAAsmT4AgAAACBLhi8AAAAAsmT4AgAAACBLhi8AAAAAsmT4AgAAACBLhi8AAAAAsmT4AgAAACBLhi8AAAAAsmT4AgAAACBLhi8AAAAAsmT4AgAAACBLteFLkiRJkiRJyqWxf2Lk8ToXvWdeAAAAAElFTkSuQmCC

  • The WG discussed the optimal location of 'epo:hasSerialID' at Item or Batch Level.

    • The WG has proposed to remove epo:hasSerialID and use epo:hasManufacturerItemID.

qNkjHFuAAAAAFf5jpK1Vsw5zw0AAADgKr33ePbeUWuN1pokSZIkSdK1lVLiBSRS2Dp6OHWhAAAAAElFTkSuQmCC

  • The definition of epo-ord:TaxInformation is changed to Information about the imposition of mandatory levies required by law.

Action Points:

  • Replace 'epo-ord:concludesContract' between 'epo:Contract' and 'epo-ord:OrderResponse' with 'epo-ord:implementsContract'.

P+nGxgblJGB6gAAAABJRU5ErkJggg==

  • We need to create a model that encompasses all the documents that form part of the Contract.

  • Revise 'Deliverable' in the context of eContract