Working group meeting

Date: 07/12/2021
Participants: Giorgia Lodi, Natalie Muric, Giovanni Paolo Sellitto
Model editor: Eugen Costezki
*Note editor: *Andreea Pasăre


  • Proposes a new approach on WGM.

  • Redundancy links to enumerations were merged into master branch.

  • The eCatalogue module was merged into the master branch.

  • Announce a proposal to structure the EPO model.

    • 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 on Locations/Geometry/Address

  • We need to provide coordinates, address or a named reference.

  • Location class

    • Geographical name

    • May have a geometry

  • Place of performance requires a location (in the notices NUTS code is required, and a text field for more info).

  • Use the core location namespace.

  • Use the naming conventions from the core.

  • Use “fullAddress” field in the address class

  • Some properties are differently called

    • adminLevel1 == country code

    • adminLevel2 == region/state/county

    • …​ === Decision on redundant code attributes

  • Decision: update the conversion & conventions checking script and the documentation so that

    • There is no more handling of code attributes (i.e. attributes with type Code/skos:Concept)

    • The dependency relations between the class and enumerations

      • In the core-model file the dependency relation shall have the range skos:Concept (regardless of the enumeration URI)

      • In the shack-shape file the dependency relation shall be checked for the precise controlled list. Those are warnings not errors.

  • Update the documentation accordingly === Discussion on eCatalogue

  • Module-specific should be used

    • In other modules other namespace should be used

  • An investigation must be done on deciding what is the “core” of epo and what is in the notification module or other ones.

Discussion on Situations, Roles, Notice taxonomy, Notice Content model.

Presenting Role modeled with subclasses: ProcurementRole ProcurementSubrole and RelatedRoles:


Situation in DOLCE acts as a relational context just as the Term classes in the below diagram:


Discussing the Awarding example at an instance level provided.

Checking the definition of Buyer from EPO model:
“A role of an agent that awards a contract and/or purchases items.”

Presenting the SubmissionActualSituation example diagram:


Submission phase per lot - instance level diagram:

Award decision phase for a lot the was not awarded diagram:



  • Are the Awarder and the Acquirer the same Organisation?

  • Do we need to have an AcquiringCPB and an AwardingCPB?

  • Should we have the example models published as HTML reports?