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

Warnings in Protégé #57

Closed
carueda opened this issue Oct 25, 2017 · 6 comments
Closed

Warnings in Protégé #57

carueda opened this issue Oct 25, 2017 · 6 comments
Assignees
Milestone

Comments

@carueda
Copy link
Member

carueda commented Oct 25, 2017

@lewismc @dr-shorthair

I just loaded http://sweetontology.net/sweetAll in Protégé 5.2.0.

This was initially as an extra verification of the COR-enabled resolution (#51), which seems to be properly in place.

However, upon looking at the log (protege.log -- I have manually removed some of the most irrelevant lines) I note several WARNs associated with SWEET. Most of them seem to be Annotation property warnings, for example:

Annotation property range axiom turned to object property range after parsing. 
  This could introduce errors if the original range was an anonymous expression: 
  http://sweetontology.net/propTime/Period is the new domain.

Annotation property range axiom turned to object property range after parsing. 
  This could introduce errors if the original range was an anonymous expression: 
  http://sweetontology.net/propTimeFrequency/Frequency is the new domain.

Annotation property range axiom turned to object property range after parsing. 
  This could introduce errors if the original range was an anonymous expression: 
  http://sweetontology.net/propTime/Time is the new domain.

You are probably already aware of this. Feel free to proceed as you deem appropriate.

@carueda
Copy link
Member Author

carueda commented Nov 24, 2017

Update with just released version 3.1.0: similar warnings as previously noted, plus the following errors:

Level:       ERROR
Message:     Illegal redeclarations of entities: reuse of entity
http://sweetontology.net/relaMath/hasDimension in punning not allowed 
[Declaration(ObjectProperty(<http://sweetontology.net/relaMath/hasDimension>)), 
Declaration(DataProperty(<http://sweetontology.net/relaMath/hasDimension>))]
Level:       ERROR
Message:     Illegal redeclarations of entities: reuse of entity 
http://sweetontology.net/relaMath/hasDimension in punning not allowed 
[Declaration(ObjectProperty(<http://sweetontology.net/relaMath/hasDimension>)), 
Declaration(DataProperty(<http://sweetontology.net/relaMath/hasDimension>))]

@carueda
Copy link
Member Author

carueda commented Dec 7, 2017

Copying note just added to the referenced bioportal issue:

Here's the discussion on Protege's user support mailing list: http://protege-project.136.n4.nabble.com/Debugging-owlapi-errors-on-SWEET-ontology-td4664108.html.

@lewismc
Copy link
Member

lewismc commented Jan 1, 2018

I just loaded SWEET master into Protege 5.0.0 and there are many more issues. I've attached my log file such that we can work our way through it.
As you can see @carueda there are possibly hundreds of instances where unparsed triple is present.
protege.log

@dr-shorthair
Copy link
Collaborator

Error at line 111 - could this cascade to later problems?
18:57:55.110 [Installing plugins thread] ERROR PluginInstaller An error occurred whilst downloading and installing the OWLAPI RDF Library plugin: https://github.com/protegeproject/rdf-library/releases/download/rdf-library-2.0.2/rdf-library-2.0.2.jar

@lewismc
Copy link
Member

lewismc commented Jan 2, 2018

Very possibly @dr-shorthair I'll scope this out closer to ESIP. Hopefully we can get a few fixes in place and possibly even make a 3.2.0 release.

@lewismc lewismc modified the milestones: 3.2.0, 3.3.0 Mar 7, 2018
@lewismc
Copy link
Member

lewismc commented Jul 16, 2019

Superseded by #124

@lewismc lewismc closed this as completed Jul 16, 2019
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

No branches or pull requests

3 participants