Cumulated content of Working Group Meeting from 2021

Working group meeting

Date: 14/12/2021
Participants: Hilde Kjølset, Natalie Muric
Model editor: Eugen Costezki
*Note editor: *Andreea Pasăre

Agenda:

  • Continue discussing a new approach on structuring ePO:

    • Present Situations, Roles, Notice taxonomy, Notice Content model.

    • Present an example of instantiation of the Submission/Awarding situation. === (Future agenda)

  • Continue discussing the attributes in the eCatalogue from GH Issue #284

    • Process control: Information about the specification that applies to the transaction.

    • Business process type identifier: Identifies the business process context in which the transaction appears. It enables the buyer to process the invoice in an appropriate way.

    • Specification identification: An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms. This identifies the European invoice norm, as well as any extensions applied. The identification may include the version of the specification.

    • Catalogue validity period: A time interval or a duration of a catalogue’s validity.

    • Contract reference: A reference to a contract the catalogue is based on.

    • Contract identifier: The identifier of the referenced contract.

    • Contract type: The type of a contract that is being referred to (such as framework agreement) expressed as a code.

    • Contract issue date: The date on which the contract comes into effect.

    • Contract subdivision: A relevant subdivision of the contract a catalogue refers to.

Discussion:

Giving the same presentation as the one from the last meeting, since some of the domain experts could not participate then.

Going through the set of roles features that were analyzed by the Working Group. Only some of them are relevant to the ePO.

The new approach: a Role is a class that is played by an Agent. We can not instantiate a Role without stating the Agent that is playing that Role.

Roles overview diagram:

hPDWoFSvegeY8fAQAcYOwZUTbcRwIAALBXKF0AyMUGaNlwHwkAAMBeoXQBIBcboGXDfSQAAAB7hdIFAAAAgPqE0gUAAACA+oTSBQAAAID6hNIFAAAAgPqE0gUAAACA+oTSBQAAAID6hNIFAAAAgPr0nmi1AAAAAADUH5QuAAAAANQnlC4AAAAA1CeULgAAAADUJ5QuAAAAANQnlC4AAAAA1CeULlC23N9aLHZL+pUy+ZVp3H8LAAAAUJ1QukBbVsiJXZK5Dkv6lduvt8v5i9IFAACA2oHSBZQuAAAA1CeULqB0AQAAoD79f+fpL831pKCuAAAAAElFTkSuQmCC

Award Decision Situation diagram:

70S7UQ4nu9+AAAAAElFTkSuQmCC

A situation is a relational context as shown in the below diagram:

wqnb77+NjHMgHu3j0Mfnb+PzZ2XiRexTL7AAAAAElFTkSuQmCC

All the terms that we already have in the ePO model are actually a description of a StipulatedSituationTerm.

wPycnnvoOKsF5AAAAAElFTkSuQmCC

Presenting an Awarding example at the instance level.

zFkAAAAASUVORK5CYII=
oMi0vnw6ePQAAAABJRU5ErkJggg==

Notices:

Started systematizing notices. It will be like a module, separate from the core ePO model.