search

OP-TED / ePO

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.
European Union Public License 1.2
58 stars 18 forks source link

The subclasses of epo:Notice are missing in 4.x, while the change is not the the release notes #645

Closed kvistgaard closed 3 months ago

kvistgaard commented 3 months ago

In the latest ePO release epo:Notice has no subclasses. At the same time, such a significant change is not mentioned in the Release notes. And the documentation still shows subclasses. Both are on ... EPO/latest

AchillesDougalis commented 3 months ago

Hello,

In the latest ePO release epo:Notice has no subclasses.

As seen on the first image, on the Master Branch (version 4.0.2) of the eNotice module, epo:Notice does have subclasses that are consistent with the documentation of the Notice module (image 2). Could the problem be that these subclasses do not appear in the epo:core module? 2024-06-25_19-05 2024-06-25_19-16

kvistgaard commented 3 months ago

Could the problem be that these subclasses do not appear in the epo:core module

Indeed, I was expecting it to be in the core.

Now I have a few questions before you close the issue:

  1. Where can I read about the reasons for splitting the ontology into modules?
  2. Why are the modules not published as TTL, as it is with the core?
  3. Which file contains all owl:imports to compose the full ePO?
AchillesDougalis commented 3 months ago

1) The original reasoning for splitting the ontology can be found in WG meeting 7/1/21 and WG meeting 14/12/21, but we are currently in the proccess of reconsidering that idea.

2) Every ePO module is available in both XML/RDF and Turtle/RDF formats.

3) There is not a single file containing all the owl:imports to compose the full ePO, because of the module structure. In this structure, the ePO core module contains all the general concepts of the Ontology, and each other specialization module imports the core module. So to answer your question, It depends on how someone plans to use the Ontology. For example, if someone wants to use the Ontology for querying information on eForms, they should use the eNotice module. If someone wants to query information about the ESPD request, they should use the eAccess module,et cetera.

We realize that there is a lack in the documentation regarding how modules work, and we are currently in the process of expanding the documentation site, so thank you for bringing this matter to light.

kvistgaard commented 3 months ago

Thanks. Well, I hope you'll decide to have one core file and the only other to be the one with restrictions.