Working Group meeting 04/05/2023

Date: 04/05/2023
Participants: Natalie Muric, Peter Borresen, Thomas Pettersson
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.

  • Discuss the proposal to change epo-cat:ItemDescription to 'epo-cat:ItemProperty

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

  • What is the Difference between epo:hasManufacturerItemID and epo:hasSerialID

Discussion:

  • The participants has approved the removal of the "postAwardObject" class and instead considers "postAward" objects as documents for the eOrdering, eCatalogue, and eFulfilment modules.

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

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

  • The participants has approved changing from 'epo-cat:ItemDescription' to 'epo:ItemProperty'

  • The participants approved that "epo:Contractor" and "epo-ord:Seller" are the same for all modules. However, it still needs to be determined how to incorporate this into the model."

  • epo:hasBatchId, epo:SerialId are different, and they are in Item instances. (TBD 16)

9k=

  • The participants discussed the need for parties to have authorization.

    • The relation between person and epo:Certificate should be added

9k=

  • The participants discussed removing if removing epo-ord:DeliveryTerm​ will affect eFulfulment model.

    • epo:hasGeneralDeliveryTerm​, epo:hasDeliveryTermDescription​ ​ properties will be added to epo-ord:DeliveryInformation

    • epo:specifiesDeliveryTermLocation​ relatin will be added between epo-ord:DeliveryInformation and dct:Location

9k=

  • The participants discussed the ReceiptAdvice

  • There are three type of rejection for recipet

  • In ReceiptLine livel

  • In Consignment Delivery Shipment.

  • TransportHandlingUnit

Action points:

  • "epo:Contractor" and "epo-ord:Seller" are the same for all modules. However, it still needs to be determined how to incorporate this into the model.

  • ReceiptAdvice modeling in eFulfilment epic