Working Group Meeting

Date: 25/03/2025  
Participants: Victorio Bentivogli,Veit Jahns, Natalie Muric
Model editor: Andreea Pasăre
Note editor: Achilles Dougalis

Agenda

Discussions

  • Issue #744 was discussed: Attribute epo:hasCalculationMethod was added to the class epo-cat:EnvironmentalEmissionInformation.

iRYaYTYAAAAAElFTkSuQmCC

  • Issue #730 was discussed:

    • We use the same Attribute for eOrdering and eCatalogue, both at the level of the OrderResponse, Catalogue Response, CatalogueResponseLine thus a more general definition is required.

    • Definition of epo-ord:hasResponseDescription was modified to: "Explanation of the response".

  • Issue #722 was discussed: The expert for the Catalogue concepts was pointed to the issue for review.

  • Issue #549 was discussed: epo:hasProcurementScopeDividedIntoLot Definition was updated to: “Defines Lot”.

  • Issue #605 was discussed: it was agreed to remove attribute epo:hasOJSType and change the datatype for epo:hasOJSIssueNumber from xsd:integer to rdf:PlainLiteral

  • Issue #662 was discussed: Since in eForms, the Subcontractors are referenced at the level of the Organization, as of ePO 5.0.0 the following implementation is adopted:

    • Removing epo:foreseesSubcontractor and epo:specifiesSubcontractors predicates between epo:Tender and epo:Subcontractor and use org:Organization epo:foreseesSubcontractor epo:Subcontractor.

    • Keeping epo:Contractor epo:foreseesSubcontractor epo:Subcontractor and epo:Contractor epo:hasSubcontractor epo:Subcontractor since they might be used in a future use-case.

AZFxB7F3tJEMAAAAAElFTkSuQmCC

  • Issue #610 was discussed: The name of the concept epo:VehicleInformation was changed to epo:CleanVehicleDirectiveInformation as depicted below:

wNa0YAQsC4bRQAAAABJRU5ErkJggg==

  • Issues #743 and #443 were discussed: epo-ord:hasAcceptanceStatus was renamed to epo-ord:hasResponseStatus.

wO0FnrBtq2jjQAAAABJRU5ErkJggg==

  • Issue #623 was discussed:

    • The ePO team prefers not to have the at-voc-new:document-type code list on the level of epo:Document, but a new Class for each of the concepts mentioned in the code-lists.

    • It was argued that currently there is no need to change this as this code list is used to reference a number of additional documents.

    • Maybe that code list could be trimmed so we can only have relevant values.

    • There should be examples of that codelist.

    • Predicate epo:documentUsedInPublicProcurement was renamed to epo:hasDocumentType.

y0MS4AAAAASUVORK5CYII=

Action Points

  • Create a ticket to get all the values that are relevant to procurement that the at-voc-new:document-type code list contains.

  • Fix Issue #623 and create another issue about Document status if needed.

TED Developer Docs

This website is managed by: Publications Office of the European Union

Need Help?

Follow us

Legal

About us

Other services

Discover more on europa.eu

Contact the EU

Social Media

EU institutions and bodies