Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebProtege can't display certain classes (e.g. from the DPV ontology) #812

Open
csnyulas opened this issue Oct 10, 2024 · 0 comments
Open
Labels
Status: Needs Triage Should be the default status for issues that have been acknowledged, but not yet processed. Type: Bug Indicates that WebProtege is not working as expected

Comments

@csnyulas
Copy link
Member

Describe the bug
Many classes in the OWL ontologies published as part of the W3C Data Privacy Vocabulary (DPV) cannot be displayed in WebProtege.

To Reproduce
Steps to reproduce the behavior:

  1. Download an OWL ontology module from the DPV GitHub Repository, for example the core DPV module (of DPV version 2.0) https://github.com/w3c/dpv/blob/master/2.0/dpv/dpv-owl.rdf
  2. Create a new Project in WebProtege by using the file downloaded in step 1, to initialize the project content
  3. Navigate through the classes, some will throw an error. For example in the DPV ontology, click on the "Processing" class
  4. See error
    image

Expected behavior
To see the content of all the classes rendered properly

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Windows
  • Browser Chrome
  • Version 129

Additional context
The problem may be related to the presence of some blank nodes, that are meant to encode source information. However, after removing all the blank nodes from the RDF file in a text editor, and updated the WebProtege project with the new file (through the Project --> Apply External Edits menu option), I still got some further errors (could be related to the existence of some erroneous information that was not deleted during the update, but this is just a wild guess),

@csnyulas csnyulas added Type: Bug Indicates that WebProtege is not working as expected Status: Needs Triage Should be the default status for issues that have been acknowledged, but not yet processed. labels Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Should be the default status for issues that have been acknowledged, but not yet processed. Type: Bug Indicates that WebProtege is not working as expected
Projects
None yet
Development

No branches or pull requests

1 participant