Editorpane widget

View: New views
7 Messages — Rating Filter:   Alert me  

Editorpane widget

by Barry Jackson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I am using Protege 3.4 Beta with build 504 on MacOS X.

I am able to create an http link as described in the  
EditorPaneWideget instructions ( and when I click on the link it  
opens the site chosen.  However, if I save the project and come back  
to it later the text field is often changed from an editor page  
widget to a SingleLiteralWidget - which displays the html code.  
Sometimes I can reallocate the widget to EditorPanewideget but this  
is not always the case.

Perhaps you could advise.

Barry

_______________________________________________
protege-owl mailing list
protege-owl@...
https://mailman.stanford.edu/mailman/listinfo/protege-owl

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

Re: Editorpane widget

by Tania Tudorache :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Barry,

The forms information is saved in the pprj file. You need to open the
pprj file, not the owl file, if you want to see the saved form
configurations.
If you open the owl file, then you will see the default form
configuration (which does not include the EditorPaneWidget).

Tania


Barry Jackson wrote:

> I am using Protege 3.4 Beta with build 504 on MacOS X.
>
> I am able to create an http link as described in the  
> EditorPaneWideget instructions ( and when I click on the link it  
> opens the site chosen.  However, if I save the project and come back  
> to it later the text field is often changed from an editor page  
> widget to a SingleLiteralWidget - which displays the html code.  
> Sometimes I can reallocate the widget to EditorPanewideget but this  
> is not always the case.
>
> Perhaps you could advise.
>
> Barry
>
> _______________________________________________
> protege-owl mailing list
> protege-owl@...
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
>
>  

_______________________________________________
protege-owl mailing list
protege-owl@...
https://mailman.stanford.edu/mailman/listinfo/protege-owl

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

Re: Editorpane widget

by Barry Jackson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Tania

Really sorry to bother you again but I am opening the pprj file.  But  
still lose the EditorPaneWidget.  I notice that this problem also  
occurs with the URL widget.

When I go back to Version 3.2 opening the pprj file when using the  
URL widget the format is retained.  This is not the case with 3.3 or  
3.4.

I will go over my work at the weekend.

Thank you.

Barry

On Jul 4, 2008, at 12:25 PM, Tania Tudorache wrote:

> Barry,
>
> The forms information is saved in the pprj file. You need to open the
> pprj file, not the owl file, if you want to see the saved form
> configurations.
> If you open the owl file, then you will see the default form
> configuration (which does not include the EditorPaneWidget).
>
> Tania
>
>
> Barry Jackson wrote:
>> I am using Protege 3.4 Beta with build 504 on MacOS X.
>>
>> I am able to create an http link as described in the
>> EditorPaneWideget instructions ( and when I click on the link it
>> opens the site chosen.  However, if I save the project and come back
>> to it later the text field is often changed from an editor page
>> widget to a SingleLiteralWidget - which displays the html code.
>> Sometimes I can reallocate the widget to EditorPanewideget but this
>> is not always the case.
>>
>> Perhaps you could advise.
>>
>> Barry
>>
>> _______________________________________________
>> protege-owl mailing list
>> protege-owl@...
>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>
>> Instructions for unsubscribing: http://protege.stanford.edu/doc/ 
>> faq.html#01a.03
>>
>>
>
> _______________________________________________
> protege-owl mailing list
> protege-owl@...
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/ 
> faq.html#01a.03
>

_______________________________________________
protege-owl mailing list
protege-owl@...
https://mailman.stanford.edu/mailman/listinfo/protege-owl

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

Re: Editorpane widget

by Tania Tudorache :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Barry,

The EditorPaneWidget has been available only since Protege 3.4 beta. If
you open the project with an earlier version of Protege (e.g. Protege
3.2), then you will not see the widget, because it was not part of that
distribution. If you save the project in an older version of Protege,
then the reference to the EditorPaneWidget will be deleted in the pprj
file. This means that the next time you open it in Protege 3.4 beta, it
will be gone.

So, my advice is to use only the Protege 3.4 beta and not switch back to
older versions. You can make this test with Protege 3.4 beta 504: open
the project, configure the form of a class to use the EditorPaneWidget,
save, close project and reopen the pprj file. You should be able to see
the EditorPaneWidget.

Tania


Barry Jackson wrote:

> Hi Tania
>
> Really sorry to bother you again but I am opening the pprj file.  But  
> still lose the EditorPaneWidget.  I notice that this problem also  
> occurs with the URL widget.
>
> When I go back to Version 3.2 opening the pprj file when using the  
> URL widget the format is retained.  This is not the case with 3.3 or  
> 3.4.
>
> I will go over my work at the weekend.
>
> Thank you.
>
> Barry
>
> On Jul 4, 2008, at 12:25 PM, Tania Tudorache wrote:
>
>  
>> Barry,
>>
>> The forms information is saved in the pprj file. You need to open the
>> pprj file, not the owl file, if you want to see the saved form
>> configurations.
>> If you open the owl file, then you will see the default form
>> configuration (which does not include the EditorPaneWidget).
>>
>> Tania
>>
>>
>> Barry Jackson wrote:
>>    
>>> I am using Protege 3.4 Beta with build 504 on MacOS X.
>>>
>>> I am able to create an http link as described in the
>>> EditorPaneWideget instructions ( and when I click on the link it
>>> opens the site chosen.  However, if I save the project and come back
>>> to it later the text field is often changed from an editor page
>>> widget to a SingleLiteralWidget - which displays the html code.
>>> Sometimes I can reallocate the widget to EditorPanewideget but this
>>> is not always the case.
>>>
>>> Perhaps you could advise.
>>>
>>> Barry
>>>
>>> _______________________________________________
>>> protege-owl mailing list
>>> protege-owl@...
>>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>>
>>> Instructions for unsubscribing: http://protege.stanford.edu/doc/ 
>>> faq.html#01a.03
>>>
>>>
>>>      
>> _______________________________________________
>> protege-owl mailing list
>> protege-owl@...
>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>
>> Instructions for unsubscribing: http://protege.stanford.edu/doc/ 
>> faq.html#01a.03
>>
>>    
>
> _______________________________________________
> protege-owl mailing list
> protege-owl@...
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
>
>  

_______________________________________________
protege-owl mailing list
protege-owl@...
https://mailman.stanford.edu/mailman/listinfo/protege-owl

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

Re: Editorpane widget

by Barry Jackson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Tania

Thank you for you advice.  I only suggested the other versions to  
illustrate that Protege 3.4 Beta operates differently to versions 3.2  
and 3.3 with regard to the URL widget.

However, I hate to say it but I am still having a problem. Not with  
creating the property associated with editpanewidget but with saving  
and opening.

Here are my steps.

> Open project using Protege 3.4 Beta
>
> Create a class, say A
>
> Create an individual say B in class A
>
> Create a datatype property say C with the Domain A and range set to  
> String and made functional.
>
> Then use the Forms menu to set the field to editpanewidget.


I think we are agreed on the above.

***********

If I save the project and then open it there is not problem. The  
editpanewideget remains. I think this is what you said in your email,  
and I agree that will happen.  But, ...

When I go to close the project or exit protege it asks me if I want  
to save. It does this even if I have made no changes.

If I don't save changes then open the project again there is not  
problem as you would expect,  however, if I save changes when I open  
the project again then the editpane widget is converted to a single  
literal widget.

This also occurs if I add another individual say B1 and then save.  I  
can avoid this if I go to the Properties tab and uncheck and check  
again the function box.

***********

I might point out that this issue also applies to the URLwidget.

***********

I mentioned the earlier versions to you as the problem I have with  
the URLwidget did not occur then. I don't as a rule use earlier  
versions of Protege.

***********

I hope I have expained in more detail my steps.

Barry




On Jul 9, 2008, at 2:21 PM, Tania Tudorache wrote:

> Hi Barry,
>
> The EditorPaneWidget has been available only since Protege 3.4  
> beta. If
> you open the project with an earlier version of Protege (e.g. Protege
> 3.2), then you will not see the widget, because it was not part of  
> that
> distribution. If you save the project in an older version of Protege,
> then the reference to the EditorPaneWidget will be deleted in the pprj
> file. This means that the next time you open it in Protege 3.4  
> beta, it
> will be gone.
>
> So, my advice is to use only the Protege 3.4 beta and not switch  
> back to
> older versions. You can make this test with Protege 3.4 beta 504: open
> the project, configure the form of a class to use the  
> EditorPaneWidget,
> save, close project and reopen the pprj file. You should be able to  
> see
> the EditorPaneWidget.
>
> Tania
>
>
> Barry Jackson wrote:
>> Hi Tania
>>
>> Really sorry to bother you again but I am opening the pprj file.  But
>> still lose the EditorPaneWidget.  I notice that this problem also
>> occurs with the URL widget.
>>
>> When I go back to Version 3.2 opening the pprj file when using the
>> URL widget the format is retained.  This is not the case with 3.3 or
>> 3.4.
>>
>> I will go over my work at the weekend.
>>
>> Thank you.
>>
>> Barry
>>
>> On Jul 4, 2008, at 12:25 PM, Tania Tudorache wrote:
>>
>>
>>> Barry,
>>>
>>> The forms information is saved in the pprj file. You need to open  
>>> the
>>> pprj file, not the owl file, if you want to see the saved form
>>> configurations.
>>> If you open the owl file, then you will see the default form
>>> configuration (which does not include the EditorPaneWidget).
>>>
>>> Tania
>>>
>>>
>>> Barry Jackson wrote:
>>>
>>>> I am using Protege 3.4 Beta with build 504 on MacOS X.
>>>>
>>>> I am able to create an http link as described in the
>>>> EditorPaneWideget instructions ( and when I click on the link it
>>>> opens the site chosen.  However, if I save the project and come  
>>>> back
>>>> to it later the text field is often changed from an editor page
>>>> widget to a SingleLiteralWidget - which displays the html code.
>>>> Sometimes I can reallocate the widget to EditorPanewideget but this
>>>> is not always the case.
>>>>
>>>> Perhaps you could advise.
>>>>
>>>> Barry
>>>>
>>>> _______________________________________________
>>>> protege-owl mailing list
>>>> protege-owl@...
>>>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>>>
>>>> Instructions for unsubscribing: http://protege.stanford.edu/doc/
>>>> faq.html#01a.03
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> protege-owl mailing list
>>> protege-owl@...
>>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>>
>>> Instructions for unsubscribing: http://protege.stanford.edu/doc/
>>> faq.html#01a.03
>>>
>>>
>>
>> _______________________________________________
>> protege-owl mailing list
>> protege-owl@...
>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>
>> Instructions for unsubscribing: http://protege.stanford.edu/doc/ 
>> faq.html#01a.03
>>
>>
>
> _______________________________________________
> protege-owl mailing list
> protege-owl@...
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/ 
> faq.html#01a.03
>

_______________________________________________
protege-owl mailing list
protege-owl@...
https://mailman.stanford.edu/mailman/listinfo/protege-owl

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

Re: Editorpane widget

by Tania Tudorache :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Barry,

Thank you for the very detailed steps. I was able to reproduce the
behavior. I will try to fix this in one of the next beta-s.

Tania


Barry Jackson wrote:

> Tania
>
> Thank you for you advice.  I only suggested the other versions to  
> illustrate that Protege 3.4 Beta operates differently to versions 3.2  
> and 3.3 with regard to the URL widget.
>
> However, I hate to say it but I am still having a problem. Not with  
> creating the property associated with editpanewidget but with saving  
> and opening.
>
> Here are my steps.
>
>  
>> Open project using Protege 3.4 Beta
>>
>> Create a class, say A
>>
>> Create an individual say B in class A
>>
>> Create a datatype property say C with the Domain A and range set to  
>> String and made functional.
>>
>> Then use the Forms menu to set the field to editpanewidget.
>>    
>
>
> I think we are agreed on the above.
>
> ***********
>
> If I save the project and then open it there is not problem. The  
> editpanewideget remains. I think this is what you said in your email,  
> and I agree that will happen.  But, ...
>
> When I go to close the project or exit protege it asks me if I want  
> to save. It does this even if I have made no changes.
>
> If I don't save changes then open the project again there is not  
> problem as you would expect,  however, if I save changes when I open  
> the project again then the editpane widget is converted to a single  
> literal widget.
>
> This also occurs if I add another individual say B1 and then save.  I  
> can avoid this if I go to the Properties tab and uncheck and check  
> again the function box.
>
> ***********
>
> I might point out that this issue also applies to the URLwidget.
>
> ***********
>
> I mentioned the earlier versions to you as the problem I have with  
> the URLwidget did not occur then. I don't as a rule use earlier  
> versions of Protege.
>
> ***********
>
> I hope I have expained in more detail my steps.
>
> Barry
>
>
>
>
> On Jul 9, 2008, at 2:21 PM, Tania Tudorache wrote:
>
>  
>> Hi Barry,
>>
>> The EditorPaneWidget has been available only since Protege 3.4  
>> beta. If
>> you open the project with an earlier version of Protege (e.g. Protege
>> 3.2), then you will not see the widget, because it was not part of  
>> that
>> distribution. If you save the project in an older version of Protege,
>> then the reference to the EditorPaneWidget will be deleted in the pprj
>> file. This means that the next time you open it in Protege 3.4  
>> beta, it
>> will be gone.
>>
>> So, my advice is to use only the Protege 3.4 beta and not switch  
>> back to
>> older versions. You can make this test with Protege 3.4 beta 504: open
>> the project, configure the form of a class to use the  
>> EditorPaneWidget,
>> save, close project and reopen the pprj file. You should be able to  
>> see
>> the EditorPaneWidget.
>>
>> Tania
>>
>>
>> Barry Jackson wrote:
>>    
>>> Hi Tania
>>>
>>> Really sorry to bother you again but I am opening the pprj file.  But
>>> still lose the EditorPaneWidget.  I notice that this problem also
>>> occurs with the URL widget.
>>>
>>> When I go back to Version 3.2 opening the pprj file when using the
>>> URL widget the format is retained.  This is not the case with 3.3 or
>>> 3.4.
>>>
>>> I will go over my work at the weekend.
>>>
>>> Thank you.
>>>
>>> Barry
>>>
>>> On Jul 4, 2008, at 12:25 PM, Tania Tudorache wrote:
>>>
>>>
>>>      
>>>> Barry,
>>>>
>>>> The forms information is saved in the pprj file. You need to open  
>>>> the
>>>> pprj file, not the owl file, if you want to see the saved form
>>>> configurations.
>>>> If you open the owl file, then you will see the default form
>>>> configuration (which does not include the EditorPaneWidget).
>>>>
>>>> Tania
>>>>
>>>>
>>>> Barry Jackson wrote:
>>>>
>>>>        
>>>>> I am using Protege 3.4 Beta with build 504 on MacOS X.
>>>>>
>>>>> I am able to create an http link as described in the
>>>>> EditorPaneWideget instructions ( and when I click on the link it
>>>>> opens the site chosen.  However, if I save the project and come  
>>>>> back
>>>>> to it later the text field is often changed from an editor page
>>>>> widget to a SingleLiteralWidget - which displays the html code.
>>>>> Sometimes I can reallocate the widget to EditorPanewideget but this
>>>>> is not always the case.
>>>>>
>>>>> Perhaps you could advise.
>>>>>
>>>>> Barry
>>>>>
>>>>> _______________________________________________
>>>>> protege-owl mailing list
>>>>> protege-owl@...
>>>>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>>>>
>>>>> Instructions for unsubscribing: http://protege.stanford.edu/doc/
>>>>> faq.html#01a.03
>>>>>
>>>>>
>>>>>
>>>>>          
>>>> _______________________________________________
>>>> protege-owl mailing list
>>>> protege-owl@...
>>>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>>>
>>>> Instructions for unsubscribing: http://protege.stanford.edu/doc/
>>>> faq.html#01a.03
>>>>
>>>>
>>>>        
>>> _______________________________________________
>>> protege-owl mailing list
>>> protege-owl@...
>>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>>
>>> Instructions for unsubscribing: http://protege.stanford.edu/doc/ 
>>> faq.html#01a.03
>>>
>>>
>>>      
>> _______________________________________________
>> protege-owl mailing list
>> protege-owl@...
>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>
>> Instructions for unsubscribing: http://protege.stanford.edu/doc/ 
>> faq.html#01a.03
>>
>>    
>
> _______________________________________________
> protege-owl mailing list
> protege-owl@...
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
>
>  

_______________________________________________
protege-owl mailing list
protege-owl@...
https://mailman.stanford.edu/mailman/listinfo/protege-owl

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

Re: Editorpane widget

by Barry Jackson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Tania
Thank you for your patience.  I really value your work and that of  
your colleagues.
Barry



On Jul 9, 2008, at 5:08 PM, Tania Tudorache wrote:

> Hi Barry,
>
> Thank you for the very detailed steps. I was able to reproduce the
> behavior. I will try to fix this in one of the next beta-s.
>
> Tania
>
>
> Barry Jackson wrote:
>> Tania
>>
>> Thank you for you advice.  I only suggested the other versions to
>> illustrate that Protege 3.4 Beta operates differently to versions 3.2
>> and 3.3 with regard to the URL widget.
>>
>> However, I hate to say it but I am still having a problem. Not with
>> creating the property associated with editpanewidget but with saving
>> and opening.
>>
>> Here are my steps.
>>
>>
>>> Open project using Protege 3.4 Beta
>>>
>>> Create a class, say A
>>>
>>> Create an individual say B in class A
>>>
>>> Create a datatype property say C with the Domain A and range set to
>>> String and made functional.
>>>
>>> Then use the Forms menu to set the field to editpanewidget.
>>>
>>
>>
>> I think we are agreed on the above.
>>
>> ***********
>>
>> If I save the project and then open it there is not problem. The
>> editpanewideget remains. I think this is what you said in your email,
>> and I agree that will happen.  But, ...
>>
>> When I go to close the project or exit protege it asks me if I want
>> to save. It does this even if I have made no changes.
>>
>> If I don't save changes then open the project again there is not
>> problem as you would expect,  however, if I save changes when I open
>> the project again then the editpane widget is converted to a single
>> literal widget.
>>
>> This also occurs if I add another individual say B1 and then save.  I
>> can avoid this if I go to the Properties tab and uncheck and check
>> again the function box.
>>
>> ***********
>>
>> I might point out that this issue also applies to the URLwidget.
>>
>> ***********
>>
>> I mentioned the earlier versions to you as the problem I have with
>> the URLwidget did not occur then. I don't as a rule use earlier
>> versions of Protege.
>>
>> ***********
>>
>> I hope I have expained in more detail my steps.
>>
>> Barry
>>
>>
>>
>>
>> On Jul 9, 2008, at 2:21 PM, Tania Tudorache wrote:
>>
>>
>>> Hi Barry,
>>>
>>> The EditorPaneWidget has been available only since Protege 3.4
>>> beta. If
>>> you open the project with an earlier version of Protege (e.g.  
>>> Protege
>>> 3.2), then you will not see the widget, because it was not part of
>>> that
>>> distribution. If you save the project in an older version of  
>>> Protege,
>>> then the reference to the EditorPaneWidget will be deleted in the  
>>> pprj
>>> file. This means that the next time you open it in Protege 3.4
>>> beta, it
>>> will be gone.
>>>
>>> So, my advice is to use only the Protege 3.4 beta and not switch
>>> back to
>>> older versions. You can make this test with Protege 3.4 beta 504:  
>>> open
>>> the project, configure the form of a class to use the
>>> EditorPaneWidget,
>>> save, close project and reopen the pprj file. You should be able to
>>> see
>>> the EditorPaneWidget.
>>>
>>> Tania
>>>
>>>
>>> Barry Jackson wrote:
>>>
>>>> Hi Tania
>>>>
>>>> Really sorry to bother you again but I am opening the pprj  
>>>> file.  But
>>>> still lose the EditorPaneWidget.  I notice that this problem also
>>>> occurs with the URL widget.
>>>>
>>>> When I go back to Version 3.2 opening the pprj file when using the
>>>> URL widget the format is retained.  This is not the case with  
>>>> 3.3 or
>>>> 3.4.
>>>>
>>>> I will go over my work at the weekend.
>>>>
>>>> Thank you.
>>>>
>>>> Barry
>>>>
>>>> On Jul 4, 2008, at 12:25 PM, Tania Tudorache wrote:
>>>>
>>>>
>>>>
>>>>> Barry,
>>>>>
>>>>> The forms information is saved in the pprj file. You need to open
>>>>> the
>>>>> pprj file, not the owl file, if you want to see the saved form
>>>>> configurations.
>>>>> If you open the owl file, then you will see the default form
>>>>> configuration (which does not include the EditorPaneWidget).
>>>>>
>>>>> Tania
>>>>>
>>>>>
>>>>> Barry Jackson wrote:
>>>>>
>>>>>
>>>>>> I am using Protege 3.4 Beta with build 504 on MacOS X.
>>>>>>
>>>>>> I am able to create an http link as described in the
>>>>>> EditorPaneWideget instructions ( and when I click on the link it
>>>>>> opens the site chosen.  However, if I save the project and come
>>>>>> back
>>>>>> to it later the text field is often changed from an editor page
>>>>>> widget to a SingleLiteralWidget - which displays the html code.
>>>>>> Sometimes I can reallocate the widget to EditorPanewideget but  
>>>>>> this
>>>>>> is not always the case.
>>>>>>
>>>>>> Perhaps you could advise.
>>>>>>
>>>>>> Barry
>>>>>>
>>>>>> _______________________________________________
>>>>>> protege-owl mailing list
>>>>>> protege-owl@...
>>>>>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>>>>>
>>>>>> Instructions for unsubscribing: http://protege.stanford.edu/doc/
>>>>>> faq.html#01a.03
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> protege-owl mailing list
>>>>> protege-owl@...
>>>>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>>>>
>>>>> Instructions for unsubscribing: http://protege.stanford.edu/doc/
>>>>> faq.html#01a.03
>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> protege-owl mailing list
>>>> protege-owl@...
>>>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>>>
>>>> Instructions for unsubscribing: http://protege.stanford.edu/doc/
>>>> faq.html#01a.03
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> protege-owl mailing list
>>> protege-owl@...
>>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>>
>>> Instructions for unsubscribing: http://protege.stanford.edu/doc/
>>> faq.html#01a.03
>>>
>>>
>>
>> _______________________________________________
>> protege-owl mailing list
>> protege-owl@...
>> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>>
>> Instructions for unsubscribing: http://protege.stanford.edu/doc/ 
>> faq.html#01a.03
>>
>>
>
> _______________________________________________
> protege-owl mailing list
> protege-owl@...
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/ 
> faq.html#01a.03
>

_______________________________________________
protege-owl mailing list
protege-owl@...
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 
LightInTheBox - Buy quality products at wholesale price