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-dev] [Webprotege] Class renaming issue

Tania Tudorache tudorache at
Thu Dec 18 10:30:28 PST 2014

A correction to my previous email. Thank you, Matthew, for it!

My description was correct only for the UUID naming setting (the default 
in WebProtege, or Project menu -> New Entity Setting -> IRI setting = 
Auto-generated Universally Unique Id (UUID) ).

If the IRI setting is changed to "Supplied Name" (which is probably what 
Pierre had), the IRI is supposed to be changed if the display label is 
changed. I could reproduce the bug from the initial report.

There seems to be a few issues with the display label textbox, and we 
hope to fix them soon.

Thank you for the report!


On 12/15/2014 04:46 PM, Tania Tudorache wrote:
> Hi Pierre,
> Thank you for filing the bug.
> Just to clarify:
> - when changing the display label, it is not expected that the IRI of 
> the class changes (your bug report says the opposite). The idea is 
> that the IRIs stay unchanged, but the display label can change without 
> any serious consequence. That is also the behavior in WebProtege.
> I reproduced the bug that if you change the text in the "Display name" 
> textfield, then the display label does not actually change. WebProtege 
> uses as default the rdfs:label as the display property, so if you 
> change the rdfs:label, it actually changes the display name, as expected.
> To fix the bug, there are two options: (1) make the "Display name" 
> textfield not editable (seems the most reasonable solution), or (2) if 
> the "Display name" textfield is editable, then update the value of the 
> display property (in this case, rdfs:label), and so, the display name 
> will be updated.. However solution (2) is much more complicated, 
> because it means reverse-engineering the text in the "Display name" 
> textfield, and write the right value in an ontology property. There 
> might be the case that the display property is an entity (not text), 
> or maybe there is a display pattern made up of several properties, not 
> a single property as it is now. In some cases, it might not even 
> possible to guess the right value from a text, so I am not in favor of 
> (2).
> Tania
> On 12/11/2014 08:08 AM, pierre wrote:
>> Hi,
>> We are trying to integrate webprotege with the DBpedia mappings wiki
>> but stumbled over an issue while trying to rename ontology classes.
>> We also filed a bug report on github:
>> It would be nice if we could get some feedback on that issue,
>> since its the only thing stopping us from beta testing webprotege
>> as a replacement for the DBpedia mappings wiki.
>> Kind regards,
>> Pierre Ahrendt
>> Freie Universität Berlin
>> _______________________________________________
>> protege-dev mailing list
>> protege-dev at
> _______________________________________________
> protege-dev mailing list
> protege-dev at

More information about the protege-dev mailing list