The eProcurement Ontology provides the formal, semantic foundation for the creation and reuse of linked open data in the domain of public procurement in the EU.
As a follow up to #284: It is needed to include information on the buyer and the seller explicitly, as both might not be the catalogue provider and/or catalogue receiver.
Use Cases
Simple: A company and a municipality agreed on a contract for items that can be bought by the municipality from the seller. To this end, the selling company sends a catalogue of the items to the municipality. Here, the epo-cat:CatalogueProvider and the epo-cat:CatalogueReceiver are also the epo:OfferingParty and the epo:Seller.
Complex: A central purchasing body agreed with a company on a contract allowing contracting authorities associated to the central purchasing body to buy items from this company. To this end, the company sends a epo:Catalogue with the items that can be bought to the central purchasing body. The central purchasing body validates the epo:Catalogue, and if valid forwards it to the contracting authorities. Thus, there are two transactions were organisations act in different roles:
The Company (epo:OfferingParty & epo-cat:CatalogueProvider) sends the epo:Catalogue to the central purchasing body (epo:CatalogueReceiver)
The central purchasing body (epo:CatalogueProvider) sends the catalogue of the comany (epo:OfferingParty) to the various contracting authorites (epo-cat:CatalogueReceiver & epo:Buyer).
As a follow up to #284: It is needed to include information on the buyer and the seller explicitly, as both might not be the catalogue provider and/or catalogue receiver.
Use Cases
Proposal
Add the following associations: