Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] WebProtege

Alex Shkotin alex.shkotin at gmail.com
Fri Nov 6 20:58:22 PST 2009


Hi Tania,

but "problem" is with webProtege as was shown in the picture I have sent
you:
we have infinite hierarchy of classes in class tree if they are equivalent.

Alex

2009/11/7 Tania Tudorache <tudorache at stanford.edu>

> Thanks for the link!
>
> I just loaded the dic.owl in Protege 3.4.1 without any problem. Are you
> using the latest Protege 3.4.1?
>
> If you get some exceptions, or have a stack trace showing the problem,
> please post them. So far, I am not able to reproduce the infinite cycle.
>
> Tania
>
> Alex Shkotin wrote:
>
>   Hi Tania,
>
> the picture is now attached.
> see ontology at  http://earth.jscc.ru/ontologies/dic.owl
>
> Alex
>
>
>
> 2009/11/6 Tania Tudorache <tudorache at stanford.edu>
>
>> Hi Alex,
>>
>> Seems like the website is down and I cannot download the picture. Do you
>> have an owl file that causes this behavior?
>>
>> Normally, equivalent classes should not cause problems to Protege OWL 3.
>>
>> Thanks,
>> Tania
>>
>> Alex Shkotin wrote:
>>
>>  Hi Tania,
>>
>> may be this is an example of infinite cycle:
>> http://clip2net.com/clip/m3050/1257447788-clip-3kb.png
>>
>> these two classes are just declared equivalent.
>>
>> Alex
>>
>>
>>
>> 2009/11/5 Tania Tudorache <tudorache at stanford.edu>
>>
>>> Hi Anna,
>>>
>>> We have a collaborator that implemented a big part of the WebProtege
>>> backend with the OWL-API, but it is not yet released. We do plan to have it
>>> soon. As much as possible we would like to use more of the OWL-API. There
>>> are some complex functionalities that we do not have yet working with the
>>> OWL-API (e.g. collaboration, extensions to SWRL, etc.), and this is an
>>> impediment.
>>>
>>> On the other hand, you should be able to use most Protege 4 ontologies in
>>> Protege 3 and WebProtege. There shouldn't be an infinite cycle in P3. Can
>>> you send us an example OWL file with this problem? You can send the file
>>> also off-line.
>>>
>>> The Login problem is fixed in the next WebProtege release. The Login
>>> button is now in the top right corner of WebProtege (similar to the iGoogle
>>> page), and it is single sign-on for all ontologies, which makes sense.
>>>
>>> The list of ontologies that are shown in MyWebProtege tab are also
>>> controlled by the access policies: you will only see the ontologies for
>>> which you have read access.
>>>
>>> We plan to have the new WebProtege release sometimes this month.
>>>
>>> Tania
>>>
>>> ----- Original Message -----
>>> From: "Anna Burla" <ANNABU at il.ibm.com>
>>> To: protege-discussion at lists.stanford.edu
>>> Sent: Thursday, November 5, 2009 7:53:01 AM GMT -08:00 US/Canada Pacific
>>> Subject: [protege-discussion] WebProtege
>>>
>>>
>>> Hello,
>>> I am using Protege 4 for creating and viewing our ontology.
>>> I want to use WebProtege and found few problematic issues:.
>>> 1) WebProtege works only with Protege 3.4 that doesn't support well owl
>>> files that were created in protege 4. It creates infinite loops in
>>> classes
>>> tree. Is it known issue?
>>> 2) On "My web protege" page there is no "login" icon. And only when I
>>> enter
>>> some project, I see "login" option.
>>> Now if I logg in I still don't see projects that have "read/write" access
>>> for specific user and not "world" group. How can I by-pass this problem?
>>> All that I want is to define project that not all "world" group can see,
>>> but only few users.
>>> Thanx a lot in advance,
>>> Anna.
>>>
>>> _______________________________________________
>>> 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 listprotege-discussion at lists.stanford.eduhttps://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 listprotege-discussion at lists.stanford.eduhttps://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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20091107/e8ccef54/attachment.html>


More information about the protege-discussion mailing list