Open msinclair2 opened 7 years ago
I have not tried JFact 4.x with Protege 5.2, so there might be some bug to fix; in the meantime, the latest 4.x release is 4.0.4, available on Maven Central - you can try deploying that manually and reporting any exceptions you see (the fact it did not get started successfully is not much in terms of debug info...)
Hi Ignazio,
I downloaded 4.0.4, and it worked! However, the version name still shows up as 4.0.3 in the menus, so the display name was not updated.
I also noticed there is 5.0.0 and 5.0.1, what are the major differences between 4 and 5?
Thanks, Michael
On Mon, Sep 11, 2017 at 4:10 PM, Ignazio Palmisano <notifications@github.com
wrote:
I have not tried JFact 4.x with Protege 5.2, so there might be some bug to fix; in the meantime, the latest 4.x release is 4.0.4, available on Maven Central - you can try deploying that manually and reporting any exceptions you see (the fact it did not get started successfully is not much in terms of debug info...)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/owlcs/jfact/issues/18#issuecomment-328673428, or mute the thread https://github.com/notifications/unsubscribe-auth/ATWldh50Td6M5Y1rZUJcKcFyBYrmTdC3ks5sha_PgaJpZM4PT0U7 .
Version 5 is for owlapi 5, however there are currently reported bugs against it, I wouldn't recommend using it for the moment.
Ignazio,
I am running through the traditional pizza ontology with JFact 4.0.4 on Protege 5.2.0 and there are classification errors which aren't happening with FaCT++. I'm attaching the example ontology. JFact thinks that HighCaloriePizza == Pizza == LowCaloriePizza, while FaCT++ gets it right. Do you know why this could be happening? Also, ProbeInconsistentTopping shows up twice (redundantly) under owl:Nothing. Sometimes I need to stop and start the reasoner with the inferred hierarchy open in order to get the inferred hierarchy to show otherwise it only shows the incosistent owl:Nothing results and nothing else.
Thanks, Michael
On Mon, Sep 11, 2017 at 11:32 PM, Ignazio Palmisano < notifications@github.com> wrote:
Version 5 is for owlapi 5, however there are currently reported bugs against it, I wouldn't recommend using it for the moment.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/owlcs/jfact/issues/18#issuecomment-328741295, or mute the thread https://github.com/notifications/unsubscribe-auth/ATWldrNSug1lL7PpUlwBcPigSA5XwT1Pks5shhdlgaJpZM4PT0U7 .
Likely a bug, thanks for reporting it.
Returning the owl:Nothing result only is harder to analyse, I'll try replicating but that will take time.
The attachment didn't make it through from email to comment, can you attach it to the issue or paste the definition of the classes?
Sorry, I guess attachments don't work if you attach them directly to your email reply from within gmail.
I'm trying to attach it to my response on github now, but it won't accept a ".owl" filetype, only a limited range of file types. So, I'm changing it from "pizza.owl" to "pizza.txt", and when you download it, you can manually change the extension back if necessary.
Perhaps it has to do with the syntax of datatype property expressions, as this seems to have changed between versions, e.g. specifying "xsd:integer" instead of just "integer".
Would you be able to update jfact for the latest version of Protege (5.2.0)?
I inquired about this on the protege user list, and got the following response from Csongor: