headers
Andras Kovi | 1 Feb 2011 11:13
Picon
Favicon

Protege leaves files open if parsing fails

Hi all!

I am relatively new to Protege, so please don't mind if I ask a dumb question.

I am using 4.1.0 Build 213 on Win7 and try to load a manchester syntax OWL file. Since this file sometimes contains errors, the parsing fails.

The  real problem is that the file is not closed after the failure, thus correction is impossible until I restart Protege.

Is there a fix for this issue? It is pretty annoying and severky reduces my effectiveness.

Thank you,
Andras

Andras Kovi
Budapest University of Technology and Economics
Eml: kovi <at> mit.bme.hu

J 
_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Permalink | Reply | 7 comments |
headers
Timothy Redmond | 1 Feb 2011 16:27
Picon
Favicon

Re: Protege leaves files open if parsing fails


There was a bug report about something very like this on the owlapi mailing list [1].  If this is the right issue then this should be fixed in the latest svn release of Protege 4.1.  I am thinking that we will make a beta or candidate release of Protege 4.1 soon so it would be nice to confirm that this is fixed.

-Timothy


[1] http://sourceforge.net/tracker/index.php?func=detail&aid=2163709&group_id=90989&atid=595534
On 02/01/2011 02:13 AM, Andras Kovi wrote:
Hi all!

I am relatively new to Protege, so please don't mind if I ask a dumb question.

I am using 4.1.0 Build 213 on Win7 and try to load a manchester syntax OWL file. Since this file sometimes contains errors, the parsing fails.

The  real problem is that the file is not closed after the failure, thus correction is impossible until I restart Protege.

Is there a fix for this issue? It is pretty annoying and severky reduces my effectiveness.

Thank you,
Andras

Andras Kovi
Budapest University of Technology and Economics
Eml: kovi <at> mit.bme.hu

J _______________________________________________ protege-discussion mailing list protege-discussion <at> lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/protege-discussion Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Permalink | Reply | 6 comments |
headers
Andras Kovi | 1 Feb 2011 18:16
Picon
Favicon

Re: Protege leaves files open if parsing fails

I guess the build instructions on the Wiki are obsolete as the checkout on 
protege--core trunk resulted in Protege 3.5.x.  I saw the protege4 repo as 
well but currently I do not have time to play with maven.

So I am eagerly waiting for the beta release bundle.

Thanks,
Andras

From:
Timothy Redmond <tredmond <at> stanford.edu>
To:
protege-discussion <at> mailman.stanford.edu
Date:
2011.02.01 16:27
Subject:
Re: [protege-discussion] Protege leaves files open if parsing fails

There was a bug report about something very like this on the owlapi 
mailing list [1].  If this is the right issue then this should be fixed in 
the latest svn release of Protege 4.1.  I am thinking that we will make a 
beta or candidate release of Protege 4.1 soon so it would be nice to 
confirm that this is fixed.

-Timothy

[1] 
http://sourceforge.net/tracker/index.php?func=detail&aid=2163709&group_id=90989&atid=595534

On 02/01/2011 02:13 AM, Andras Kovi wrote: 
Hi all! 

I am relatively new to Protege, so please don't mind if I ask a dumb 
question. 

I am using 4.1.0 Build 213 on Win7 and try to load a manchester syntax OWL 
file. Since this file sometimes contains errors, the parsing fails. 

The  real problem is that the file is not closed after the failure, thus 
correction is impossible until I restart Protege. 

Is there a fix for this issue? It is pretty annoying and severky reduces 
my effectiveness. 

Thank you, 
Andras 

Andras Kovi
Budapest University of Technology and Economics
Eml: kovi <at> mit.bme.hu

J 

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: 
http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: 
http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Permalink | Reply | 5 comments |
headers
Timothy Redmond | 1 Feb 2011 18:54
Picon
Favicon

Re: Protege leaves files open if parsing fails

On 02/01/2011 09:16 AM, Andras Kovi wrote:
> I guess the build instructions on the Wiki are obsolete as the checkout on
> protege--core trunk resulted in Protege 3.5.x.

Not obsolete - we are maintaining two versions of Protege.  The build 
instructions for Protege 4.1 are at [1].  In particular, if you have ant 
and java, the 40 second build of Protege is very easy and will give you 
a basic but working Protege (plugins like hermit can be downloaded with 
"check for plugins").

I was thinking it would be nice to get you and early build and if you 
can build it yourself that would be cool.

> I saw the protege4 repo as
> well but currently I do not have time to play with maven.

We actually are still mostly ant based.  The maven builds also work to 
some degree and are being supported to make hudson operate smoothly 
[2].  In our day to day work we don't use maven that much.  I am  very 
happy about the hudson/nexus/sonar work which is due to Dr. Christian 
Johner who was recently visiting.

-Timothy

[1] http://protegewiki.stanford.edu/wiki/Protege4DevDocs#Building_Protege4.1_from_scratch_using_ant
[2] http://bmir-hudson1.stanford.edu/view/1-Protege4/

> So I am eagerly waiting for the beta release bundle.
>
> Thanks,
> Andras
>
>
>
> From:
> Timothy Redmond<tredmond <at> stanford.edu>
> To:
> protege-discussion <at> mailman.stanford.edu
> Date:
> 2011.02.01 16:27
> Subject:
> Re: [protege-discussion] Protege leaves files open if parsing fails
>
>
>
>
> There was a bug report about something very like this on the owlapi
> mailing list [1].  If this is the right issue then this should be fixed in
> the latest svn release of Protege 4.1.  I am thinking that we will make a
> beta or candidate release of Protege 4.1 soon so it would be nice to
> confirm that this is fixed.
>
> -Timothy
>
>
> [1]
> http://sourceforge.net/tracker/index.php?func=detail&aid=2163709&group_id=90989&atid=595534
>
> On 02/01/2011 02:13 AM, Andras Kovi wrote:
> Hi all!
>
> I am relatively new to Protege, so please don't mind if I ask a dumb
> question.
>
> I am using 4.1.0 Build 213 on Win7 and try to load a manchester syntax OWL
> file. Since this file sometimes contains errors, the parsing fails.
>
> The  real problem is that the file is not closed after the failure, thus
> correction is impossible until I restart Protege.
>
> Is there a fix for this issue? It is pretty annoying and severky reduces
> my effectiveness.
>
> Thank you,
> Andras
>
> Andras Kovi
> Budapest University of Technology and Economics
> Eml: kovi <at> mit.bme.hu
>
> J
>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Permalink | Reply | 4 comments |
headers
Andras Kovi | 1 Feb 2011 19:30
Picon
Favicon

Re: Protege leaves files open if parsing fails

Hi Timothy,

I went through the 40 sec build and Protege started perfectly. 
Unfortunately, the bug is not gone. I loaded a malformed owl file, the 
loading failed, but I was unable to modify the file until I exited the 
application.

Thanks,
Andras

From:
Timothy Redmond <tredmond <at> stanford.edu>
To:
protege-discussion <at> mailman.stanford.edu
Date:
2011.02.01 18:55
Subject:
Re: [protege-discussion] Protege leaves files open if parsing fails

On 02/01/2011 09:16 AM, Andras Kovi wrote:
> I guess the build instructions on the Wiki are obsolete as the checkout 
on
> protege--core trunk resulted in Protege 3.5.x.

Not obsolete - we are maintaining two versions of Protege.  The build 
instructions for Protege 4.1 are at [1].  In particular, if you have ant 
and java, the 40 second build of Protege is very easy and will give you 
a basic but working Protege (plugins like hermit can be downloaded with 
"check for plugins").

I was thinking it would be nice to get you and early build and if you 
can build it yourself that would be cool.

> I saw the protege4 repo as
> well but currently I do not have time to play with maven.

We actually are still mostly ant based.  The maven builds also work to 
some degree and are being supported to make hudson operate smoothly 
[2].  In our day to day work we don't use maven that much.  I am  very 
happy about the hudson/nexus/sonar work which is due to Dr. Christian 
Johner who was recently visiting.

-Timothy

[1] 
http://protegewiki.stanford.edu/wiki/Protege4DevDocs#Building_Protege4.1_from_scratch_using_ant

[2] http://bmir-hudson1.stanford.edu/view/1-Protege4/

> So I am eagerly waiting for the beta release bundle.
>
> Thanks,
> Andras
>
>
>
> From:
> Timothy Redmond<tredmond <at> stanford.edu>
> To:
> protege-discussion <at> mailman.stanford.edu
> Date:
> 2011.02.01 16:27
> Subject:
> Re: [protege-discussion] Protege leaves files open if parsing fails
>
>
>
>
> There was a bug report about something very like this on the owlapi
> mailing list [1].  If this is the right issue then this should be fixed 
in
> the latest svn release of Protege 4.1.  I am thinking that we will make 
a
> beta or candidate release of Protege 4.1 soon so it would be nice to
> confirm that this is fixed.
>
> -Timothy
>
>
> [1]
> 
http://sourceforge.net/tracker/index.php?func=detail&aid=2163709&group_id=90989&atid=595534

>
> On 02/01/2011 02:13 AM, Andras Kovi wrote:
> Hi all!
>
> I am relatively new to Protege, so please don't mind if I ask a dumb
> question.
>
> I am using 4.1.0 Build 213 on Win7 and try to load a manchester syntax 
OWL
> file. Since this file sometimes contains errors, the parsing fails.
>
> The  real problem is that the file is not closed after the failure, thus
> correction is impossible until I restart Protege.
>
> Is there a fix for this issue? It is pretty annoying and severky reduces
> my effectiveness.
>
> Thank you,
> Andras
>
> Andras Kovi
> Budapest University of Technology and Economics
> Eml: kovi <at> mit.bme.hu
>
> J
>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: 
http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: 
http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Permalink | Reply | 3 comments |
headers
Timothy Redmond | 1 Feb 2011 20:39
Picon
Favicon

Re: Protege leaves files open if parsing fails

On 02/01/2011 10:30 AM, Andras Kovi wrote:
> Hi Timothy,
>
> I went through the 40 sec build and Protege started perfectly.
> Unfortunately, the bug is not gone.

Ah the good news and the bad news :).  I am adding a bug report for this 
item and I will take a look at it.  The tricky part of testing this is 
the windows 7 part but we have some machines that we can probably access.

-Timothy

[1] https://bmir-gforge.stanford.edu/gf/project/owleditor/tracker/?action=TrackerItemEdit&tracker_item_id=2970&start=0

>   I loaded a malformed owl file, the
> loading failed, but I was unable to modify the file until I exited the
> application.
>
> Thanks,
> Andras
>
>
>
>
> From:
> Timothy Redmond<tredmond <at> stanford.edu>
> To:
> protege-discussion <at> mailman.stanford.edu
> Date:
> 2011.02.01 18:55
> Subject:
> Re: [protege-discussion] Protege leaves files open if parsing fails
>
>
>
> On 02/01/2011 09:16 AM, Andras Kovi wrote:
>> I guess the build instructions on the Wiki are obsolete as the checkout
> on
>> protege--core trunk resulted in Protege 3.5.x.
> Not obsolete - we are maintaining two versions of Protege.  The build
> instructions for Protege 4.1 are at [1].  In particular, if you have ant
> and java, the 40 second build of Protege is very easy and will give you
> a basic but working Protege (plugins like hermit can be downloaded with
> "check for plugins").
>
> I was thinking it would be nice to get you and early build and if you
> can build it yourself that would be cool.
>
>> I saw the protege4 repo as
>> well but currently I do not have time to play with maven.
> We actually are still mostly ant based.  The maven builds also work to
> some degree and are being supported to make hudson operate smoothly
> [2].  In our day to day work we don't use maven that much.  I am  very
> happy about the hudson/nexus/sonar work which is due to Dr. Christian
> Johner who was recently visiting.
>
> -Timothy
>
> [1]
> http://protegewiki.stanford.edu/wiki/Protege4DevDocs#Building_Protege4.1_from_scratch_using_ant
>
> [2] http://bmir-hudson1.stanford.edu/view/1-Protege4/
>
>
>
>
>> So I am eagerly waiting for the beta release bundle.
>>
>> Thanks,
>> Andras
>>
>>
>>
>> From:
>> Timothy Redmond<tredmond <at> stanford.edu>
>> To:
>> protege-discussion <at> mailman.stanford.edu
>> Date:
>> 2011.02.01 16:27
>> Subject:
>> Re: [protege-discussion] Protege leaves files open if parsing fails
>>
>>
>>
>>
>> There was a bug report about something very like this on the owlapi
>> mailing list [1].  If this is the right issue then this should be fixed
> in
>> the latest svn release of Protege 4.1.  I am thinking that we will make
> a
>> beta or candidate release of Protege 4.1 soon so it would be nice to
>> confirm that this is fixed.
>>
>> -Timothy
>>
>>
>> [1]
>>
> http://sourceforge.net/tracker/index.php?func=detail&aid=2163709&group_id=90989&atid=595534
>
>> On 02/01/2011 02:13 AM, Andras Kovi wrote:
>> Hi all!
>>
>> I am relatively new to Protege, so please don't mind if I ask a dumb
>> question.
>>
>> I am using 4.1.0 Build 213 on Win7 and try to load a manchester syntax
> OWL
>> file. Since this file sometimes contains errors, the parsing fails.
>>
>> The  real problem is that the file is not closed after the failure, thus
>> correction is impossible until I restart Protege.
>>
>> Is there a fix for this issue? It is pretty annoying and severky reduces
>> my effectiveness.
>>
>> Thank you,
>> Andras
>>
>> Andras Kovi
>> Budapest University of Technology and Economics
>> Eml: kovi <at> mit.bme.hu
>>
>> J
>>
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion <at> lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion <at> lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>>
>>
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion <at> lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Permalink | Reply | 2 comments |
headers
Andras Kovi | 1 Feb 2011 21:27
Picon
Favicon

Re: Protege leaves files open if parsing fails

I cannot promise anything, but if I have time tomorrow I'll try to run the 
stuff in Eclipse to catch where the file handle gets lost.
Will it work if I follow the instructions on [1a]?

Thanks,
Andras

[1a] http://protegewiki.stanford.edu/wiki/CompileProtege4InEclipseFromSvn

From:
Timothy Redmond <tredmond <at> stanford.edu>
To:
protege-discussion <at> mailman.stanford.edu
Date:
2011.02.01 20:39
Subject:
Re: [protege-discussion] Protege leaves files open if parsing fails

On 02/01/2011 10:30 AM, Andras Kovi wrote:
> Hi Timothy,
>
> I went through the 40 sec build and Protege started perfectly.
> Unfortunately, the bug is not gone.

Ah the good news and the bad news :).  I am adding a bug report for this 
item and I will take a look at it.  The tricky part of testing this is 
the windows 7 part but we have some machines that we can probably access.

-Timothy

[1] 
https://bmir-gforge.stanford.edu/gf/project/owleditor/tracker/?action=TrackerItemEdit&tracker_item_id=2970&start=0

>   I loaded a malformed owl file, the
> loading failed, but I was unable to modify the file until I exited the
> application.
>
> Thanks,
> Andras
>
>
>
>
> From:
> Timothy Redmond<tredmond <at> stanford.edu>
> To:
> protege-discussion <at> mailman.stanford.edu
> Date:
> 2011.02.01 18:55
> Subject:
> Re: [protege-discussion] Protege leaves files open if parsing fails
>
>
>
> On 02/01/2011 09:16 AM, Andras Kovi wrote:
>> I guess the build instructions on the Wiki are obsolete as the checkout
> on
>> protege--core trunk resulted in Protege 3.5.x.
> Not obsolete - we are maintaining two versions of Protege.  The build
> instructions for Protege 4.1 are at [1].  In particular, if you have ant
> and java, the 40 second build of Protege is very easy and will give you
> a basic but working Protege (plugins like hermit can be downloaded with
> "check for plugins").
>
> I was thinking it would be nice to get you and early build and if you
> can build it yourself that would be cool.
>
>> I saw the protege4 repo as
>> well but currently I do not have time to play with maven.
> We actually are still mostly ant based.  The maven builds also work to
> some degree and are being supported to make hudson operate smoothly
> [2].  In our day to day work we don't use maven that much.  I am  very
> happy about the hudson/nexus/sonar work which is due to Dr. Christian
> Johner who was recently visiting.
>
> -Timothy
>
> [1]
> 
http://protegewiki.stanford.edu/wiki/Protege4DevDocs#Building_Protege4.1_from_scratch_using_ant

>
> [2] http://bmir-hudson1.stanford.edu/view/1-Protege4/
>
>
>
>
>> So I am eagerly waiting for the beta release bundle.
>>
>> Thanks,
>> Andras
>>
>>
>>
>> From:
>> Timothy Redmond<tredmond <at> stanford.edu>
>> To:
>> protege-discussion <at> mailman.stanford.edu
>> Date:
>> 2011.02.01 16:27
>> Subject:
>> Re: [protege-discussion] Protege leaves files open if parsing fails
>>
>>
>>
>>
>> There was a bug report about something very like this on the owlapi
>> mailing list [1].  If this is the right issue then this should be fixed
> in
>> the latest svn release of Protege 4.1.  I am thinking that we will make
> a
>> beta or candidate release of Protege 4.1 soon so it would be nice to
>> confirm that this is fixed.
>>
>> -Timothy
>>
>>
>> [1]
>>
> 
http://sourceforge.net/tracker/index.php?func=detail&aid=2163709&group_id=90989&atid=595534

>
>> On 02/01/2011 02:13 AM, Andras Kovi wrote:
>> Hi all!
>>
>> I am relatively new to Protege, so please don't mind if I ask a dumb
>> question.
>>
>> I am using 4.1.0 Build 213 on Win7 and try to load a manchester syntax
> OWL
>> file. Since this file sometimes contains errors, the parsing fails.
>>
>> The  real problem is that the file is not closed after the failure, 
thus
>> correction is impossible until I restart Protege.
>>
>> Is there a fix for this issue? It is pretty annoying and severky 
reduces
>> my effectiveness.
>>
>> Thank you,
>> Andras
>>
>> Andras Kovi
>> Budapest University of Technology and Economics
>> Eml: kovi <at> mit.bme.hu
>>
>> J
>>
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion <at> lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion <at> lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>>
>>
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion <at> lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: 
http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: 
http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Permalink | Reply | 1 comment |
headers
Timothy Redmond | 1 Feb 2011 21:36
Picon
Favicon

Re: Protege leaves files open if parsing fails

On 02/01/2011 12:27 PM, Andras Kovi wrote:
> I cannot promise anything, but if I have time tomorrow I'll try to run the
> stuff in Eclipse to catch where the file handle gets lost.
> Will it work if I follow the instructions on [1a]?

That would be most appreciated but it is clearly also well above and 
beyond the call of duty.  These directions should work but I will give 
them a test later today.

-Timothy

> Thanks,
> Andras
>
> [1a] http://protegewiki.stanford.edu/wiki/CompileProtege4InEclipseFromSvn
>
>
>
> From:
> Timothy Redmond<tredmond <at> stanford.edu>
> To:
> protege-discussion <at> mailman.stanford.edu
> Date:
> 2011.02.01 20:39
> Subject:
> Re: [protege-discussion] Protege leaves files open if parsing fails
>
>
>
> On 02/01/2011 10:30 AM, Andras Kovi wrote:
>> Hi Timothy,
>>
>> I went through the 40 sec build and Protege started perfectly.
>> Unfortunately, the bug is not gone.
> Ah the good news and the bad news :).  I am adding a bug report for this
> item and I will take a look at it.  The tricky part of testing this is
> the windows 7 part but we have some machines that we can probably access.
>
> -Timothy
>
> [1]
> https://bmir-gforge.stanford.edu/gf/project/owleditor/tracker/?action=TrackerItemEdit&tracker_item_id=2970&start=0
>
>
>
>
>>    I loaded a malformed owl file, the
>> loading failed, but I was unable to modify the file until I exited the
>> application.
>>
>> Thanks,
>> Andras
>>
>>
>>
>>
>> From:
>> Timothy Redmond<tredmond <at> stanford.edu>
>> To:
>> protege-discussion <at> mailman.stanford.edu
>> Date:
>> 2011.02.01 18:55
>> Subject:
>> Re: [protege-discussion] Protege leaves files open if parsing fails
>>
>>
>>
>> On 02/01/2011 09:16 AM, Andras Kovi wrote:
>>> I guess the build instructions on the Wiki are obsolete as the checkout
>> on
>>> protege--core trunk resulted in Protege 3.5.x.
>> Not obsolete - we are maintaining two versions of Protege.  The build
>> instructions for Protege 4.1 are at [1].  In particular, if you have ant
>> and java, the 40 second build of Protege is very easy and will give you
>> a basic but working Protege (plugins like hermit can be downloaded with
>> "check for plugins").
>>
>> I was thinking it would be nice to get you and early build and if you
>> can build it yourself that would be cool.
>>
>>> I saw the protege4 repo as
>>> well but currently I do not have time to play with maven.
>> We actually are still mostly ant based.  The maven builds also work to
>> some degree and are being supported to make hudson operate smoothly
>> [2].  In our day to day work we don't use maven that much.  I am  very
>> happy about the hudson/nexus/sonar work which is due to Dr. Christian
>> Johner who was recently visiting.
>>
>> -Timothy
>>
>> [1]
>>
> http://protegewiki.stanford.edu/wiki/Protege4DevDocs#Building_Protege4.1_from_scratch_using_ant
>
>> [2] http://bmir-hudson1.stanford.edu/view/1-Protege4/
>>
>>
>>
>>
>>> So I am eagerly waiting for the beta release bundle.
>>>
>>> Thanks,
>>> Andras
>>>
>>>
>>>
>>> From:
>>> Timothy Redmond<tredmond <at> stanford.edu>
>>> To:
>>> protege-discussion <at> mailman.stanford.edu
>>> Date:
>>> 2011.02.01 16:27
>>> Subject:
>>> Re: [protege-discussion] Protege leaves files open if parsing fails
>>>
>>>
>>>
>>>
>>> There was a bug report about something very like this on the owlapi
>>> mailing list [1].  If this is the right issue then this should be fixed
>> in
>>> the latest svn release of Protege 4.1.  I am thinking that we will make
>> a
>>> beta or candidate release of Protege 4.1 soon so it would be nice to
>>> confirm that this is fixed.
>>>
>>> -Timothy
>>>
>>>
>>> [1]
>>>
> http://sourceforge.net/tracker/index.php?func=detail&aid=2163709&group_id=90989&atid=595534
>
>>> On 02/01/2011 02:13 AM, Andras Kovi wrote:
>>> Hi all!
>>>
>>> I am relatively new to Protege, so please don't mind if I ask a dumb
>>> question.
>>>
>>> I am using 4.1.0 Build 213 on Win7 and try to load a manchester syntax
>> OWL
>>> file. Since this file sometimes contains errors, the parsing fails.
>>>
>>> The  real problem is that the file is not closed after the failure,
> thus
>>> correction is impossible until I restart Protege.
>>>
>>> Is there a fix for this issue? It is pretty annoying and severky
> reduces
>>> my effectiveness.
>>>
>>> Thank you,
>>> Andras
>>>
>>> Andras Kovi
>>> Budapest University of Technology and Economics
>>> Eml: kovi <at> mit.bme.hu
>>>
>>> J
>>>
>>>
>>> _______________________________________________
>>> protege-discussion mailing list
>>> protege-discussion <at> lists.stanford.edu
>>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>>
>>> Instructions for unsubscribing:
>>> http://protege.stanford.edu/doc/faq.html#01a.03
>>>
>>> _______________________________________________
>>> protege-discussion mailing list
>>> protege-discussion <at> lists.stanford.edu
>>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>>
>>> Instructions for unsubscribing:
>>> http://protege.stanford.edu/doc/faq.html#01a.03
>>>
>>>
>>>
>>> _______________________________________________
>>> protege-discussion mailing list
>>> protege-discussion <at> lists.stanford.edu
>>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>>
>>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion <at> lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>>
>>
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion <at> lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing:
> http://protege.stanford.edu/doc/faq.html#01a.03
>
>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion <at> lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Permalink | Reply | 0 comments |
headers
Guillaume.Duclaux | 2 Feb 2011 06:09
Picon
Picon
Favicon

Navigating online resources in Protege (v 4.0 or >)

Hi List,

I'm new to the Protege Mailing list and not an expert ontologist (at all), so please forgive any misnaming or
improper use of consecrated terms in the following message.

I'm running Protégé 4.0 (build 115) with the SKOS plugin to maintain and edit a few controlled
vocabularies on my local machine. These consist in series of RDF documents (with a mix of SKOS and OWL properties).
The RDFs  are also stored in a Triple-Store and can be accessed/queried via a SPARQL end-point. Every
resource is identified by a RESTful http-URI (eg
http://resource.geosciml.org/classifier/cgi/lithology/0066) that is redirected (303 http status
code) to a SPARQL end-point query.
Every URI returns a valid RDF document where all the triples related to the selected entity are reported.

As I  open load an ontology from one of the URI, the content of the RDF response is loaded into Protege cache and
I can visualise the resource, that's great!
However, Protege doesn't allow me to navigate the online resources: ie, when selecting a related
individual to the one I've loaded, the URI is not resolved and no content is available.

* Test:
(1) In Protégé, load the following Ontology from the URI:
http://resource.geosciml.org/classifierscheme/cgi/201012/simplelithology

(2) Protege identifies 263 individuals associated with this conceptScheme

(3) Go to the "Individuals" tab, and select any individual (except the simpleLithology one that you've
just loaded).

(4) Selected individual doesn't have the rich content that is identify by its URI.

My question:
-->> Is there a way in the current version of Protege to enable navigation through online resources (ie with
resolvable URIs)?
It would be neat to select a resource and load its online content

I guess I could generate a new entry where all concepts are imported using owl:imports... but this would be
one more thing to maintain....

Cheers

Guillaume

Dr Guillaume Duclaux

Mineral Down Under Flagship & AuScope Grid
CSIRO Earth Science and Resource Engineering

Phone: +61 8 6436 8728  | Fax: +61 8 6436 8559  | Mobile:  +61 422 289 732

guillaume.duclaux <at> csiro.au<mailto:guillaume.duclaux <at> csiro.au> |
www.csiro.au<http://www.csiro.au/> |
Address: Australian Resources Research Centre, 26 Dick Perry Avenue, Kensington WA 6151

PLEASE NOTE
The information contained in this email may be confidential or privileged. Any unauthorised use or
disclosure is prohibited. If you have received this email in error, please delete it immediately and
notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent,
warrant and/or guarantee that the integrity of this communication has been maintained or that the
communication is free of errors, virus, interception or interference.

Please consider the environment before printing this email.

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Permalink | Reply | 1 comment |
headers
Thomas Russ | 2 Feb 2011 10:10
Picon
Favicon

Re: Navigating online resources in Protege (v 4.0 or >)


On Feb 1, 2011, at 9:09 PM, <Guillaume.Duclaux <at> csiro.au> <Guillaume.Duclaux <at> csiro.au> wrote:

> I guess I could generate a new entry where all concepts are imported using owl:imports... but this would be
one more thing to maintain....

I think this is really your only option.

In OWL, the URIs are just used to unambiguously name classes, individuals and properties.  They are not used
as links for paging in additional information.  That is what the imports statements for ontology
inclusion are used for.

You might be able to write an additional tool or plugin that provides the function that you want, but there
isn't anything in Protege that I know of that will do what you want.

_______________________________________________
protege-discussion mailing list
protege-discussion <at> lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
Permalink | Reply | 0 comments |

Gmane