owldiff-support — Share Your issues/suggestions on this list.

Re: [Owldiff-support] NoClassDefFoundError from OWLDiff Protege plugin

[Petr K. <pet...@fe...>]

Dear Richard,
> I am using Protégé 4.1 on a Windows box. I installed the OWLDiff 
> plugin, but when I try to use it I get the following error:
>
> NoClassDefFoundError: 
> org/semanticweb/owlapi/model/MissingImportHandlingStrategy
>
> cz.cvut.kbss.owldiff.protege.OWLDiffPlugin$1.run(OWLDiffPlugin.java:75)
>
sorry for so long delay. This should be fixed now.

Cheers,
Petr

[Owldiff-support] NoClassDefFoundError from OWLDiff Protege plugin

[Markeloff, R. <rma...@mi...>]

Hello,

I am using Protégé 4.1 on a Windows box. I installed the OWLDiff plugin, but when I try to use it I get the following error:

NoClassDefFoundError: org/semanticweb/owlapi/model/MissingImportHandlingStrategy
    cz.cvut.kbss.owldiff.protege.OWLDiffPlugin$1.run(OWLDiffPlugin.java:75)

I downloaded owlapi-api-3.4.2.jar, which contains the missing class, and tried the following all to no avail:

·         Put owlapi-api-3.4.2.jar in the bin directory

·         Put owlapi-api-3.4.2.jar in the plugins directory

·         Put owlapi-api-3.4.2.jar in the bundles directory

·         Explicitly add owlapi-api-3.4.2.jar to the classpath in run.bat, and then use run.bat to start Protégé
I welcome any suggestions on how to fix this.

Thank you,

Richard Markeloff

[Owldiff-support] ANN: OWLDiff 0.2

[Petr K. <pet...@fe...>]

Folks,

we have just release 0.2 version of OWLDiff, see 
https://sourceforge.net/projects/owldiff 
<https://sourceforge.net/projects/owldiff/?source=directory>.

Important changes include:
- support for annotated axiom comparison
- CEX diff bug fixes
- complete Mavenization - you can find the artifacts (with sources and 
javadoc) in Maven repo: http://krizik.felk.cvut.cz/m2repo/
- support for Subversion 1.7

Cheers,

Petr Kremen and Marek Smid
The current OWLDiff team

-- 
Dr. Petr Kremen
Czech Technical University in Prague
Faculty of Electrical Engineering
Department of Cybernetics
Knowledge Based and Software Systems Group
Karlovo námestí 13
12000 Praha 2, Czech Republic
phone 00420 224 35 73 50
email pet...@fe...
web http://kbss.felk.cvut.cz

Re: [Owldiff-support] owldiff-standalone

[Petr K. <kr...@fe...>]

Hi Felix,

thanks you for this report. We will solve this by next OWLDiff 
standalone release.

Cheers,
Petr

[Owldiff-support] ANN: OWLDiff v 0.1.5

[Petr K. <kr...@fe...>]

Folks,


an OWLAPI-3.2.2-compliant version of OWLDiff has been released. Please,


1) download at 
http://sourceforge.net/projects/owldiff/files/owldiff/0.1.5/cz.cvut.kbss.owldiff.protege.jar

2) comment at owl...@li...


Cheers,


Petr Kremen

Czech Technical University in Prague

[Owldiff-support] owldiff-standalone

[Felix K. <kil...@gm...>]

Hi!
I have a problem running owldiff-standalone:

06.03.2011 14:43:59 cz.cvut.kbss.owldiff.standalone.SwingDiffFrame <init>
WARNUNG: Reasoner factory not found. Reason :
java.lang.NullPointerException
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:186)
    at
cz.cvut.kbss.owldiff.standalone.SwingDiffFrame.<init>(SwingDiffFrame.java:87)
    at
cz.cvut.kbss.owldiff.standalone.SwingDiffFrame.main(SwingDiffFrame.java:379)
06.03.2011 14:44:00 cz.cvut.kbss.owldiff.standalone.SwingDiffFrame <init>
WARNUNG: OWLDiff icon not found.


The problem is obvious:

SwingDiffFrame:
String reasonerFactory = System.getProperty("reasonerFactory");

There is no system property called reasonerFactory. Noone provides it.

I wrote a small script for testing:

#!/bin/bash
classpath=.:lib/owldiff-standalone-0.1.4.jar:lib/owldiff-core-0.1.4.jar:lib/pellet-owlapi.jar:lib/pellet-core.jar
#classpath=.:lib/owldiff-standalone-0.1.4.jar:lib/owldiff-core-0.1.4.jar:lib/owlapi/owlapi-bin.jar
#java  -classpath $classpath -jar
-DreasonerFactory=cz.cvut.kbss.owldiff.diff.OWLReasonerFactoryProvider
lib/owldiff-standalone-0.1.4.jar
java  -classpath $classpath -jar  lib/owldiff-standalone-0.1.4.jar
#java  -classpath $classpath -jar
-DreasonerFactory=org.semanticweb.owlapi.reasoner.OWLReasonerFactory
lib/owldiff-standalone-0.1.4.jar

But I get a reasoner instanciation exception.

Unfortunatelly, I could not find a reasoner in the package.
I suggest someone puts a reasoner in the jar and puts it in the Manifest.

Thanks for reading this
Felix

Re: [Owldiff-support] Problems with OWldiff plugin

[Petr K. <kr...@fe...>]

Hi Christian,

> However, whereas the standalone version works fine, the Protege plugin
> doesn't. Here is the stacktrace:
>
> ---------------------------------------------------------------------------------------------------
> Error 21 Logged at Thu Feb 10 12:32:59 CET 2011
> NoClassDefFoundError:
> org/protege/editor/owl/model/inference/ProtegeOWLReasonerFactory
>      java.lang.Class.getDeclaredMethods0(Native Method)
>      java.lang.Class.privateGetDeclaredMethods(Class.java:2444)
>      java.lang.Class.getDeclaredMethod(Class.java:1952)
>      java.awt.Component.isCoalesceEventsOverriden(Component.java:5860)
>      java.awt.Component.access$300(Component.java:171)
>      java.awt.Component$3.run(Component.java:5814)
>      java.awt.Component$3.run(Component.java:5812)
>      java.security.AccessController.doPrivileged(Native Method)
>      java.awt.Component.checkCoalescing(Component.java:5811)
>      java.awt.Component.<init>(Component.java:5780)
>      java.awt.Container.<init>(Container.java:270)
>      javax.swing.JComponent.<init>(JComponent.java:573)
>
> org.protege.editor.core.ui.view.ViewComponent.<init>(ViewComponent.java:25)
>
> org.protege.editor.owl.ui.view.AbstractOWLViewComponent.<init>(AbstractOWLViewComponent.java:32)
>
> org.protege.editor.owl.ui.view.AbstractActiveOntologyViewComponent.<init>(AbstractActiveOntologyViewComponent.java:21)
>      cz.cvut.kbss.owldiff.protege.OWLDiffPlugin.<init>(OWLDiffPlugin.java:65)
>      sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>      java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>      java.lang.Class.newInstance0(Class.java:372)
>      java.lang.Class.newInstance(Class.java:325)
>
> org.protege.editor.core.plugin.PluginUtilities.getExtensionObject(PluginUtilities.java:131)
>
> org.protege.editor.core.plugin.ExtensionInstantiator.instantiate(ExtensionInstantiator.java:74)
>
> org.protege.editor.core.ui.view.ViewComponentPluginJPFImpl.newInstance(ViewComponentPluginJPFImpl.java:131)
>
> org.protege.editor.core.ui.view.ViewComponentPluginJPFImpl.newInstance(ViewComponentPluginJPFImpl.java:46)
>
> org.protege.editor.core.ui.workspace.Workspace.showResultsView(Workspace.java:360)
>
> org.protege.editor.core.ui.workspace.Workspace.showResultsView(Workspace.java:336)
>
> cz.cvut.kbss.owldiff.protege.actions.AbstractOWLDiffCompareToAction.actionPerformed(AbstractOWLDiffCompareToAction.java:29)
>      javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2012)
>
> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2335)
>
> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:404)
>      javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
>      javax.swing.AbstractButton.doClick(AbstractButton.java:374)
>      javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:829)
>
> javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:873)
>      java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:289)
>      java.awt.Component.processMouseEvent(Component.java:6175)
>      javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
>      java.awt.Component.processEvent(Component.java:5940)
>      java.awt.Container.processEvent(Container.java:2105)
>      java.awt.Component.dispatchEventImpl(Component.java:4536)
>      java.awt.Container.dispatchEventImpl(Container.java:2163)
>      java.awt.Component.dispatchEvent(Component.java:4362)
>      java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4461)
>      java.awt.LightweightDispatcher.processMouseEvent(Container.java:4125)
>      java.awt.LightweightDispatcher.dispatchEvent(Container.java:4055)
>      java.awt.Container.dispatchEventImpl(Container.java:2149)
>      java.awt.Window.dispatchEventImpl(Window.java:2478)
>      java.awt.Component.dispatchEvent(Component.java:4362)
>      java.awt.EventQueue.dispatchEvent(EventQueue.java:604)
>
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
>
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
>
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
>      java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
>      java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
>      java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
> --------------------------------------------------------------------------------------------------
>    
This seems that You are using the OWLDiff plugin for Protege 4.0 in 
Protege 4.1, am I right ? Unfortunately, there is no P4.1 version of 
OWLDiff,
but our plans are to make one, although the schedule is not settled.

Cheers,

Petr

Re: [Owldiff-support] OWLDiff: not working properly

[Cristian C. <cr...@ie...>]

Dear Petr, thank you for looking into this. I'll let you know how "switching
to plain view" worked--that is, assuming that I can figure out how to
"switch" to plain view.

 

I am afraid, that it might be an issue of *annotation axioms* not be working
properly.

Anyway, switching to the plain axiom list view should help.

I have created a ticket
<https://sourceforge.net/tracker/?func=detail&aid=3027329&group_id=231165&at
id=1082518>  for the issue. Based on our time-constraints we will try to fix
it ASAP. Please let me know, whether switching to plain view helped.

Re: [Owldiff-support] OWLDiff: not working properly

[Petr K. <kr...@la...>]

Dear Christian,

I am afraid, that it might be an issue of *annotation axioms* not be 
working properly.

Anyway, switching to the plain axiom list view should help.

I have created a ticket 
<https://sourceforge.net/tracker/?func=detail&aid=3027329&group_id=231165&atid=1082518> 
for the issue. Based on our time-constraints we will try to fix it ASAP. 
Please let me know, whether switching to plain view helped.

Cheers,
Petr

[Owldiff-support] OWLDiff: not working properly

[Cristian C. <cr...@ie...>]

I've been trying to use OWLDiff, but so far I have not been able to make it
work properly with my ontologies, neither as a standalone, nor as a Protégé
plugin. I am attaching two screenshots that show what happens while
attempting to use it as a Protégé Plugin: while the command prompt window
seems to be showing the proper results of the comparison, the Protégé window
shows nothing. What am I doing wrong? I need to see the differences in
Protégé please, not just the command prompt window. (Note that I have no
trouble running OWLDiff on the toy ontologies that come with the standalone
OWLDiff distribution.)

Many thanks,

Christian Cocos
Post Doctoral Fellow
Centre for Logic and Information, StFX University 54B St. Mary's Street,
Antigonish NS, Canada B2G 2W5
Tel: + 1 (902) 867-4931, Fax: +1 (902) 867-1397

Current research: "Building Decision-Support Through Dynamic Workflow
Systems for Health Care"

Re: [Owldiff-support] Using OWLDiff in a Java application

[Petr K. <kr...@la...>]

Hi Oylum,

> I need to use OWLDiff for finding out if there are differences between 
> an ontology downloaded long before and the same ontology just 
> downloaded from the Internet. However, since I do not know the source 
> code, I do not know how to do or where to begin. Could you please give 
> me some clues?
You can take a look at the source codes of the OWLDiff available at 
sourceforge.net SVN, namely at the SwingFrame class. If You have any 
particular question, problem, let us know.

Cheers,
Petr

Re: [Owldiff-support] compiling/java 1.5

[Alan R. <ala...@gm...>]

On Thu, Apr 1, 2010 at 1:53 AM, Petr Kremen <kr...@la...> wrote:
> Hi Alan,
>>
>> It appears that the protege owldiff tool was compiled for java 1.6.
>> I try to run in 1.5 because I there are some issues I have with 1.6. I
>> checked out the source to recompile but instructions don't work -
>> maven can't find various dependencies.
>>
>> Would it be possible to either
>> a) release a java 1.5 version
>>
>
> We chose for this option, as the configuration management for the project is
> not in currently a very good shape.

Thanks. Works for me now.
Best,
Alan

>
> You can try now, although you might need to remove the original plugin
> manually from the Protege installation before, as we didn't change the
> plugin release version.
>
> Cheers,
> Petr
>

Re: [Owldiff-support] compiling/java 1.5

[Petr K. <kr...@la...>]

Hi Alan,
> It appears that the protege owldiff tool was compiled for java 1.6.
> I try to run in 1.5 because I there are some issues I have with 1.6. I
> checked out the source to recompile but instructions don't work -
> maven can't find various dependencies.
>
> Would it be possible to either
> a) release a java 1.5 version
>   
We chose for this option, as the configuration management for the 
project is not in currently a very good shape.

You can try now, although you might need to remove the original plugin 
manually from the Protege installation before, as we didn't change the 
plugin release version.

Cheers,
Petr

[Owldiff-support] compiling/java 1.5

[Alan R. <ala...@gm...>]

Hi,

It appears that the protege owldiff tool was compiled for java 1.6.
I try to run in 1.5 because I there are some issues I have with 1.6. I
checked out the source to recompile but instructions don't work -
maven can't find various dependencies.

Would it be possible to either
a) release a java 1.5 version
b) update and test the build instructions on a fresh machine?

Thanks,
Alan

Re: [Owldiff-support] [Pellet-users] ANN: OWLDiff plugin for Protege 4.1

[Alan R. <ala...@gm...>]

Hi,

I just tried this, and it should be an excellent addition to protege!
I tried it comparing two subsequent versions of an ontology I work on: OBI.
It correctly lists the changed object properties (I was interested in
the syntactic view)
Noticed a few things.

1) Doesn't show up in the list when you check for plugins. I expect
this requires some coordination with Tim Redmond (cced) to add it to
the list.
2) There wasn't a link on the page you pointed to, or in your email,
saying where the plugin could be downloaded from or how to install it.
I know how to do that, but others might not.
3) It wasn't clear how to invoke the tool. First I looked for a tab,
then views, then menus and found it under tools.
4) I've attached a screenshot. Notice that it shows the path to the
temp directory where the ontology was downloaded from. Since I chose
to compare to a rev in the repository (THANKS FOR THAT!!!), it would
be clearer to show the name of the ontology and the two version
numbers.
5) The green color for the diff is very hard to read.
6) If you pop the view (click on the square little icon in the right
upper corner) to get a new window with the view (so as to have more
space to work) the contents of the diff are not shown.

So generally very positive for me. Needs some cosmetic tweaks and more
documentation.

Regards,
Alan


On Wed, Mar 31, 2010 at 2:11 AM, Petr Kremen <kr...@la...> wrote:
> Hi to all,
>
> let me announce the release of the OWLDiff plugin for Protege 4.1. Main
> features include:
>
> * syntactic and semantic comparison of OWL 2 ontologies including entailment
> explanations and CEX diff
> * embedded SVN client to easily compare ontologies under SVN version
> control.
> * various visualization options
>
> More detailed info can be found at
> http://protegewiki.stanford.edu/index.php/OWLDiff
>
> If You have a technical issue (including a bug report) regarding OWLDiff
> installation/operation, please use the mailing list
> owl...@li...
>
> Any other kind of comment/suggestion/statement send, please, to
> kb...@la.... Especially, we would highly appreciate statements of
> interest/use cases to drive further plugin development.
>
> Petr Kremen
> On behalf of the Knowledge-based and software systems group, Czech Technical
> University
>
>
> _______________________________________________
> Pellet-users mailing list
> Pel...@li...
> http://lists.owldl.com/mailman/listinfo/pellet-users
> _______________________________________________
>
> Sponsored by Clark & Parsia, LLC http://clarkparsia.com/
>

[Owldiff-support] ANN: OWLDiff plugin for Protege 4.1

[Petr K. <kr...@la...>]

Hi to all,

let me announce the release of the OWLDiff plugin for Protege 4.1. Main 
features include:

* syntactic and semantic comparison of OWL 2 ontologies including 
entailment explanations and CEX diff
* embedded SVN client to easily compare ontologies under SVN version 
control.
* various visualization options

More detailed info can be found at 
http://protegewiki.stanford.edu/index.php/OWLDiff

If You have a technical issue (including a bug report) regarding OWLDiff 
installation/operation, please use the mailing list 
owl...@li... 
<mailto:owl...@li...>

Any other kind of comment/suggestion/statement send, please, to 
kb...@la... <mailto:pet...@fe...>. Especially, we 
would highly appreciate statements of interest/use cases to drive 
further plugin development.

Petr Kremen
On behalf of the Knowledge-based and software systems group, Czech 
Technical University

Re: [Owldiff-support] OWLDiff export výsledků

[Ondrej Z. <ond...@vs...>]

Ahoj Petře,
zajímal jsem se o to proto, že provádíme nějaké změny v ontologiích a 
OWLDiff se mi hodil na kontrolu, co se všechno změnilo. V textové podobě 
by se mi to kontrolovalo rychleji a také bych od toho měl přímo záznam.

Zdravím,
Ondra

Petr Kremen wrote:
> Ahoj Ondro,
>
> omlouvám se za zpoždění.
>
> OWLDiff samostné změny ukládat neumí. Na co by se ti to hodilo ? Asi 
> by nemuselo být náročné tam přidělat.
>
> Petr
>

[Owldiff-support] OWLDiff export výsledků

[Petr K. <kr...@la...>]

Ahoj Ondro,

omlouvám se za zpoždění.

OWLDiff samostné změny ukládat neumí. Na co by se ti to hodilo ? Asi by 
nemuselo být náročné tam přidělat.

Petr

Re: [Owldiff-support] Owldiff-support Digest, Vol 1, Issue 1

[Melanie H. <Mel...@un...>]

Dear Petr,


I've just downloaded and tested OWLDIFF 0.1.3 on different versions of
our ontology. It works perfectly on Protege 4 output now, and also does
it very quickly. We'll be relying constantly on OWLDIFF to track changes
to an ontology we're developing collaboratively.

Thanks again for producing this new version much sooner than we expected.

Best regards,
Melanie



owl...@li... wrote:
> Send Owldiff-support mailing list submissions to
> 	owl...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.sourceforge.net/lists/listinfo/owldiff-support
> or, via email, send a message with subject or body 'help' to
> 	owl...@li...
>
> You can reach the person managing the list at
> 	owl...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Owldiff-support digest..."
>
>
> Today's Topics:
>
>    1. Introduction (Petr Kremen)
>    2. [Fwd: Re: OwlDiff CEX Result understanding	Problem] (Petr Kremen)
>    3. owldiff problems parsing owl files (Melanie Hilario)
>    4. Re: owldiff problems parsing owl files (Petr Kremen)
>    5. Re: owldiff problems parsing owl files (Melanie Hilario)
>    6. ANN: OWLDiff 0.1.3 (Petr Kremen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 17 Sep 2008 09:30:39 +0200
> From: Petr Kremen <kr...@la...>
> Subject: [Owldiff-support] Introduction
> To: owl...@li...
> Message-ID: <48D...@la...>
> Content-Type: text/plain; charset=ISO-8859-2
>
> Here is the place to put all Your questions/suggestions/proposals
> regarding OWLDiff.
>
>
> CVUT OWLDiff team
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 13 May 2009 18:38:40 +0200
> From: Petr Kremen <kr...@la...>
> Subject: [Owldiff-support] [Fwd: Re: OwlDiff CEX Result understanding
> 	Problem]
> To: owl...@li...
> Message-ID: <4A0...@la...>
> Content-Type: text/plain; charset="utf-8"
>
>
> -------------- next part --------------
> An embedded message was scrubbed...
> From: Mario Rothe <m....@fu...>
> Subject: Re: OwlDiff CEX Result understanding Problem
> Date: Wed, 13 May 2009 18:09:26 +0200
> Size: 6225
> -------------- next part --------------
> An embedded message was scrubbed...
> From: Marek Smid <sm...@fe...>
> Subject: Re: OwlDiff CEX Result understanding Problem
> Date: Tue, 12 May 2009 18:11:41 +0200
> Size: 5278
>
> ------------------------------
>
> Message: 3
> Date: Tue, 01 Dec 2009 11:32:58 +0100
> From: Melanie Hilario <Mel...@un...>
> Subject: [Owldiff-support] owldiff problems parsing owl files
> To: owl...@li...
> Message-ID: <200...@we...>
> Content-Type: text/plain; CHARSET=US-ASCII; DelSp=Yes; format=flowed
>
> Hello,
>
> I'm trying owldiff but it seems it has problems reading my owl files,  
> which were
> edited in Protege 4 and output in RDF/XML syntax. I get the following  
> error message:
>
> Could not parse ontology.  Either a suitable parser could not be  
> found, or parsing failed.  See parser logs below for explanation.
> The following parsers were tried.
> 1) org.coode.owl.rdfxml.parser.RDFXMLParser
> ... (deleted irrelevant parsers)
>
> Detailed logs:
> --------------------------------------------------------------------------------
> Parser class: org.coode.owl.rdfxml.parser.RDFXMLParser
> org.coode.owl.rdfxml.parser.OWLRDFParserException: Unable to determine  
> the type of restriction!
>
> ... (deleted logs of other parsers)
>
> Is there a way of finding out which restriction (or which line) is  
> causing problems?
> I thought at first owldiff was stumbling on the SWRL rules, so I  
> deleted them, but
> the problem remains. Many thanks for any help.
>
> Melanie
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 01 Dec 2009 15:43:48 +0100
> From: Petr Kremen <kr...@la...>
> Subject: Re: [Owldiff-support] owldiff problems parsing owl files
> To: Melanie Hilario <Mel...@un...>
> Cc: owl...@li...
> Message-ID: <4B1...@la...>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Dear Melanie,
>   
>> I'm trying owldiff but it seems it has problems reading my owl files,  
>> which were
>> edited in Protege 4 and output in RDF/XML syntax. I get the following  
>> error message:
>>
>> Could not parse ontology.  Either a suitable parser could not be  
>> found, or parsing failed.  See parser logs below for explanation.
>> The following parsers were tried.
>> 1) org.coode.owl.rdfxml.parser.RDFXMLParser
>> ... (deleted irrelevant parsers)
>>
>> Detailed logs:
>> --------------------------------------------------------------------------------
>> Parser class: org.coode.owl.rdfxml.parser.RDFXMLParser
>> org.coode.owl.rdfxml.parser.OWLRDFParserException: Unable to determine  
>> the type of restriction!
>>
>> ... (deleted logs of other parsers)
>>
>> Is there a way of finding out which restriction (or which line) is  
>> causing problems?
>> I thought at first owldiff was stumbling on the SWRL rules, so I  
>> deleted them, but
>> the problem remains. Many thanks for any help.
>>   
>>     
> The OWLDiff tool uses OWLAPI v2.2.0, while Protege 4.0 uses the OWLAPI 
> v3. This might be a problem as the OWLAPI v2.2.0 parser might not handle 
> all the OWL2 syntax. I can take a look at Yr. source if You provide me 
> with it and help you with it.
>
> Anyway, we want to make a new release of OWLDiff in a short term
>
> Cheers,
> Petr
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 01 Dec 2009 17:17:48 +0100
> From: Melanie Hilario <Mel...@un...>
> Subject: Re: [Owldiff-support] owldiff problems parsing owl files
> To: Petr Kremen <kr...@la...>
> Cc: owl...@li...
> Message-ID: <4B1...@un...>
> Content-Type: text/plain; CHARSET=US-ASCII; format=flowed
>
> Dear Petr,
>
> Thank you very much for your quick reply. I would really appreciate it 
> if you could
> tell me what's causing the parsing failure in the file I'll send you 
> separately
> (unfortunately it can't be made public yet -- but will be disseminated 
> freely once it
> attains a decent state).
>
> I look forward to the new version of owldiff. It would really be a big 
> help to people
> like us who develop ontologies collaboratively without using 
> sophisticated co-authoring
> tools.
>
> Thanks again and best regards,
> Melanie
>
>
> Petr Kremen wrote:
>   
>> Dear Melanie,
>>     
>>> I'm trying owldiff but it seems it has problems reading my owl 
>>> files,  which were
>>> edited in Protege 4 and output in RDF/XML syntax. I get the 
>>> following  error message:
>>>
>>> Could not parse ontology.  Either a suitable parser could not be  
>>> found, or parsing failed.  See parser logs below for explanation.
>>> The following parsers were tried.
>>> 1) org.coode.owl.rdfxml.parser.RDFXMLParser
>>> ... (deleted irrelevant parsers)
>>>
>>> Detailed logs:
>>> -------------------------------------------------------------------------------- 
>>>
>>> Parser class: org.coode.owl.rdfxml.parser.RDFXMLParser
>>> org.coode.owl.rdfxml.parser.OWLRDFParserException: Unable to 
>>> determine  the type of restriction!
>>>
>>> ... (deleted logs of other parsers)
>>>
>>> Is there a way of finding out which restriction (or which line) is  
>>> causing problems?
>>> I thought at first owldiff was stumbling on the SWRL rules, so I  
>>> deleted them, but
>>> the problem remains. Many thanks for any help.
>>>   
>>>       
>> The OWLDiff tool uses OWLAPI v2.2.0, while Protege 4.0 uses the OWLAPI 
>> v3. This might be a problem as the OWLAPI v2.2.0 parser might not 
>> handle all the OWL2 syntax. I can take a look at Yr. source if You 
>> provide me with it and help you with it.
>>
>> Anyway, we want to make a new release of OWLDiff in a short term
>>
>> Cheers,
>> Petr
>>
>>     
>
>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 07 Dec 2009 13:32:51 +0100
> From: Petr Kremen <kr...@la...>
> Subject: [Owldiff-support] ANN: OWLDiff 0.1.3
> To: owl...@li...
> Message-ID: <4B1...@la...>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi to all,
>
> let me inform You about a new OWLDiff release, v. 0.1.3. The main change 
> to the previous version is migration to OWLAPI v3.
>
> Cheers,
> Petr
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing. 
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
>
> ------------------------------
>
> _______________________________________________
> Owldiff-support mailing list
> Owl...@li...
> https://lists.sourceforge.net/lists/listinfo/owldiff-support
>
>
> End of Owldiff-support Digest, Vol 1, Issue 1
> *********************************************
>   

[Owldiff-support] ANN: OWLDiff 0.1.3

[Petr K. <kr...@la...>]

Hi to all,

let me inform You about a new OWLDiff release, v. 0.1.3. The main change 
to the previous version is migration to OWLAPI v3.

Cheers,
Petr

Re: [Owldiff-support] owldiff problems parsing owl files

[Melanie H. <Mel...@un...>]

Dear Petr,

Thank you very much for your quick reply. I would really appreciate it 
if you could
tell me what's causing the parsing failure in the file I'll send you 
separately
(unfortunately it can't be made public yet -- but will be disseminated 
freely once it
attains a decent state).

I look forward to the new version of owldiff. It would really be a big 
help to people
like us who develop ontologies collaboratively without using 
sophisticated co-authoring
tools.

Thanks again and best regards,
Melanie


Petr Kremen wrote:
> Dear Melanie,
>> I'm trying owldiff but it seems it has problems reading my owl 
>> files,  which were
>> edited in Protege 4 and output in RDF/XML syntax. I get the 
>> following  error message:
>>
>> Could not parse ontology.  Either a suitable parser could not be  
>> found, or parsing failed.  See parser logs below for explanation.
>> The following parsers were tried.
>> 1) org.coode.owl.rdfxml.parser.RDFXMLParser
>> ... (deleted irrelevant parsers)
>>
>> Detailed logs:
>> -------------------------------------------------------------------------------- 
>>
>> Parser class: org.coode.owl.rdfxml.parser.RDFXMLParser
>> org.coode.owl.rdfxml.parser.OWLRDFParserException: Unable to 
>> determine  the type of restriction!
>>
>> ... (deleted logs of other parsers)
>>
>> Is there a way of finding out which restriction (or which line) is  
>> causing problems?
>> I thought at first owldiff was stumbling on the SWRL rules, so I  
>> deleted them, but
>> the problem remains. Many thanks for any help.
>>   
> The OWLDiff tool uses OWLAPI v2.2.0, while Protege 4.0 uses the OWLAPI 
> v3. This might be a problem as the OWLAPI v2.2.0 parser might not 
> handle all the OWL2 syntax. I can take a look at Yr. source if You 
> provide me with it and help you with it.
>
> Anyway, we want to make a new release of OWLDiff in a short term
>
> Cheers,
> Petr
>

Re: [Owldiff-support] owldiff problems parsing owl files

[Petr K. <kr...@la...>]

Dear Melanie,
> I'm trying owldiff but it seems it has problems reading my owl files,  
> which were
> edited in Protege 4 and output in RDF/XML syntax. I get the following  
> error message:
>
> Could not parse ontology.  Either a suitable parser could not be  
> found, or parsing failed.  See parser logs below for explanation.
> The following parsers were tried.
> 1) org.coode.owl.rdfxml.parser.RDFXMLParser
> ... (deleted irrelevant parsers)
>
> Detailed logs:
> --------------------------------------------------------------------------------
> Parser class: org.coode.owl.rdfxml.parser.RDFXMLParser
> org.coode.owl.rdfxml.parser.OWLRDFParserException: Unable to determine  
> the type of restriction!
>
> ... (deleted logs of other parsers)
>
> Is there a way of finding out which restriction (or which line) is  
> causing problems?
> I thought at first owldiff was stumbling on the SWRL rules, so I  
> deleted them, but
> the problem remains. Many thanks for any help.
>   
The OWLDiff tool uses OWLAPI v2.2.0, while Protege 4.0 uses the OWLAPI 
v3. This might be a problem as the OWLAPI v2.2.0 parser might not handle 
all the OWL2 syntax. I can take a look at Yr. source if You provide me 
with it and help you with it.

Anyway, we want to make a new release of OWLDiff in a short term

Cheers,
Petr

[Owldiff-support] owldiff problems parsing owl files

[Melanie H. <Mel...@un...>]

Hello,

I'm trying owldiff but it seems it has problems reading my owl files,  
which were
edited in Protege 4 and output in RDF/XML syntax. I get the following  
error message:

Could not parse ontology.  Either a suitable parser could not be  
found, or parsing failed.  See parser logs below for explanation.
The following parsers were tried.
1) org.coode.owl.rdfxml.parser.RDFXMLParser
... (deleted irrelevant parsers)

Detailed logs:
--------------------------------------------------------------------------------
Parser class: org.coode.owl.rdfxml.parser.RDFXMLParser
org.coode.owl.rdfxml.parser.OWLRDFParserException: Unable to determine  
the type of restriction!

... (deleted logs of other parsers)

Is there a way of finding out which restriction (or which line) is  
causing problems?
I thought at first owldiff was stumbling on the SWRL rules, so I  
deleted them, but
the problem remains. Many thanks for any help.

Melanie

[Owldiff-support] [Fwd: Re: OwlDiff CEX Result understanding Problem]

[Petr K. <kr...@la...>]

[Owldiff-support] Introduction

[Petr K. <kr...@la...>]

Here is the place to put all Your questions/suggestions/proposals
regarding OWLDiff.


CVUT OWLDiff team