TizianaPasciuto / CTP_Ontology

Creative Commons Attribution 4.0 International
0 stars 0 forks source link

Checking out to deal with ontology documentation via LODE #5

Closed riccardoAlbertoni closed 7 months ago

riccardoAlbertoni commented 8 months ago

I have experimented a little with Widoco [1]. Widoco produces LODO-compliant documentation. Besides a tool to generate ontology documentation, it also means to deploy a web base application to deploy the documentation as HTTP reachable pages.

We focus on the generation of the ontology documentation as a first step and then we will check if the web-based publication is needed for our purposes or if we can simply publish the ontology documentation attached in the git repository.

Installing Widoco

A complete list of the widoco option are available at https://github.com/dgarijo/Widoco/?tab=readme-ov-file#options

Suggestions

[1] https://github.com/dgarijo/Widoco

riccardoAlbertoni commented 8 months ago

Issues:

TizianaPasciuto commented 7 months ago

The previously listed points have been addressed; however, some of them require additional notes:

  • [x] I opted for cc-by license, but this is a decision we need to consider together

Added to the repository an .md file with the specific license document.

  • [x] Abstract and diagrams might need to be included

The ontology model image has been inserted, but since the repository is not public, the image is not displayed on the HTML page. I tested it with images published on the web, and they are displayed without any issues. I think that the problem will be solved once the ontology is made public.

It was necessary to change the namespace from https:///w3id.org/ctp to https:///w3id.org/ctp#, because without the presence of the # the ctp prefix was always displayed.

  • [x] doublecheck the OOPS validations created when adding -oops to widoco command

Resolution of the 69 missing annotations reported by OOPS! (P08. Missing annotation), since for classes and properties of the ontology it was always missing rdfs:label. As a result, the problem found on the html page related to the classes displayed with the lowercase letter instead of the uppercase letter was also solved. Partial resolution of the 16 cases detected by OOPS! (P11. Missing domain or range in properties). Only one case concerned the CTP ontology, due to an oversight that has been corrected. The other missed domain or range in properties concern ontologies that have been referred to as equivalent to some properties of CTP ontology.

  • [x] In documentation insert CQs

I added in the repository an .md file that contains the 25 CQs in both Italian and English and I have attempted to write them for querying in SPARQL. They need to be checked as I may have made mistakes. Furthermore, while writing them, I realized that in some cases, inverse relationships might be necessary, which I had not considered in the ontology model.

In addition to that, the README file of the ontology has been compiled. It now includes a brief introduction and information about the methodology followed for development, as well as some key phases of the development process. It also indicates any tools used and provides links to resources that contributed to the creation of the ontology (such as CQs, tabular information, model diagram, etc.). A references section will also be added.

The work has brought to light new issues, including:

TizianaPasciuto commented 7 months ago

New steps (emerged during the today's meeting - 21.03.2024):

TizianaPasciuto commented 7 months ago

The previously listed points have been addressed; however, some of them require additional notes:

  • [ ] Testing of the SPARQL Query tab in Protege for the CTP core ontology;

As already verified during the meeting on March 21st, the SPARQL query tab doesn't work. The plugins suggested by various websites were not found in the update list because they were already present in my version of Protege.

  • [x] Resolution of OOPS! issues;

There are still two points left to resolve. I also read the related publication (now uploaded in Zotero - DOI:10.4018/ijswis.2014040102), but it doesn't provide much additional information on resolving my issues. These points are: