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

Fix missing imports #6

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix missing imports #6

wants to merge 1 commit into from

Conversation

vChavezB
Copy link

@vChavezB vChavezB commented Jan 3, 2024

Added missing imports for correct use with Protege and owlapi.
Fixes #5

Added missing imports for correct use with Protege and owlapi
@kenwenzel
Copy link
Collaborator

Hi @vchavez,

thank you for reporting this. Currently, these lists are rdf:Lists and therefore only compatible with OWL full. Instead of importing the vocabulary we could also just define the two types within math.ttl:

rdfs:Class a rdfs:Ressource .
rdf:List rdfs:subClassOf rdfs:Class .

This would prevent generic tools from downloading RDF files from the web.

What do you think?

@vChavezB
Copy link
Author

vChavezB commented Jan 18, 2024

I tried the suggestion in Protege but I still get the same error

grafik

Here is the changed file with the suggestion

(note: uploaded as txt as github blacklists ttl extension files)
math.txt

@kenwenzel
Copy link
Collaborator

@vChavezB Could you try to change:
rdfs:Class a rdfs:Ressource .
to
rdfs:Class a rdfs:Resource .

Sorry for the mistake.

@kenwenzel
Copy link
Collaborator

kenwenzel commented Jan 18, 2024

OK, I've looked at the log messages:

   INFO  17:34:13  Reloading OntologyID(OntologyIRI(<http://openmath.org/vocab/math>) VersionIRI(<null>)) from file:/home/ken/Downloads/math.ttl
   INFO  17:34:13  Usage of rdf vocabulary: http://www.w3.org/1999/02/22-rdf-syntax-ns#first -> http://www.w3.org/1999/02/22-rdf-syntax-ns#type -> http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
  ERROR  17:34:13  Entity not properly recognized, missing triples in input? http://org.semanticweb.owlapi/error#Error31 for type Class
  ERROR  17:34:13  Entity not properly recognized, missing triples in input? http://org.semanticweb.owlapi/error#Error32 for type Class
  ERROR  17:34:13  Entity not properly recognized, missing triples in input? http://org.semanticweb.owlapi/error#Error33 for type Class
   INFO  17:34:13  Unparsed triple: _:genid-nodeid-node1hkemojj2x39 -> http://www.w3.org/2002/07/owl#onProperty -> http://www.w3.org/1999/02/22-rdf-syntax-ns#first
   INFO  17:34:13  Unparsed triple: _:genid-nodeid-node1hkemojj2x10 -> http://www.w3.org/2002/07/owl#onProperty -> http://www.w3.org/1999/02/22-rdf-syntax-ns#first
   INFO  17:34:13  Unparsed triple: _:genid-nodeid-node1hkemojj2x54 -> http://www.w3.org/2002/07/owl#onProperty -> http://www.w3.org/1999/02/22-rdf-syntax-ns#first
   INFO  17:34:13  Applying 13 change(s) to patch ontology to reloaded ontology

So I tried to just add

rdf:first a owl:ObjectProperty .

and suprisingly this is working?!

But I'm also not completely against adding the imports. I just can't assess the possible impacts if tools try to resolve them.

@vChavezB
Copy link
Author

vChavezB commented Jan 18, 2024

Thanks for the update, that worked. Well from my short experience with ontology tools is that if you do not have internet access you need to point to the imports locally. Protege has an option for this and the owlapi also has a way to do this.

So this might hinder development if the users of this project do not implement a way to load ontologies locally. So for compatiblity reasons this might break software that depend on this ontology. I think the manual declaration of the entities would be a better solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error loading in Protege due to missing imports
2 participants