Re: [protege-user] Is there a way to hide non-English annotations?

Michael DeBellis <[email protected]> Fri, 19 Dec 2025 14:16:13 -0800
Newsgroups gmane.comp.misc.ontology.protege.owl
Message-ID <CALGFikdqUSJQ+S4gU6o0S4Y6R_oLimJ3LejqNjHsB4qSeGEwzA@mail.gmail.com>
--===============2684592936064051178==
Content-Type: multipart/alternative; boundary="00000000000086a92e0646556d8d"

--00000000000086a92e0646556d8d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Igor,  The only thing that worries me about doing that is I could see
myself making changes to the one with the non-English annotations
removed... but come to think of it, there are so many extra comments that
aren't in English in DCAT it would be pretty hard not to notice, so I think
I will try that. It will make browsing and understanding DCAT easier.
Actually another thing I could do is just write a SPARQL update to add a
comment on each entity that says something like "ENGLISH ONLY VERSION, DO
NOT EDIT!" Thanks, that's a great idea.

Michael

On Fri, Dec 19, 2025 at 1:47=E2=80=AFPM Igor Toujilov via protege-user <
[email protected]> wrote:

> I did not mean permanently stripping off multilingual annotations. You ca=
n
> use the reduced ontology just for search, and then return to the original
> ontology for other tasks.
>
> *Sent:* Thursday, December 18, 2025 at 9:30 PM
> *From:* "Michael DeBellis" <[email protected]>
> *To:* "User support for WebProtege and Protege Desktop" <
> [email protected]>
> *Subject:* Re: [protege-user] Is there a way to hide non-English
> annotations?
> Thanks Igor, that's a great idea but unfortunately it won't work for this
> ontology.
>
> As I understand it, for W3C vocabularies like DCAT, multilingual
> annotations are normative. Labels and comments with language tags are par=
t
> of the standard=E2=80=99s internationalization support, and downstream to=
oling
> (catalogs, portals, UI layers, and national data platforms) rely on them =
to
> present metadata in the user=E2=80=99s preferred language. Removing them =
would
> break conformance with DCAT=E2=80=99s design goals and reduce interoperab=
ility,
> especially in European and international contexts where multilingual
> catalogs are the norm.
>
> Since I want what I'm building to be as consistent with those other tools
> as possible, I need to leave them in. I don't think there is a way to hid=
e
> them but just wanted to see if there was something I was missing.
>
> On Thu, Dec 18, 2025 at 12:09=E2=80=AFPM Igor Toujilov via protege-user <
> [email protected]> wrote:
>
>> Hi Michael,
>>
>> This is not straightforward approach, but it may help:
>>
>>
>>
>> -- Save the original ontology in a convenient format, e. g. XML/RDF.
>>
>> -- Write a script, e. g. XSLT, or a program to strip the unwanted
>> annotations.
>>
>> -- Use the reduced ontology in Protege.
>>
>>
>>
>> Cheers,
>>
>> Igor
>>
>> *Sent:* Thursday, December 18, 2025 at 4:15 AM
>> *From:* "Michael DeBellis" <[email protected]>
>> *To:* "User support for WebProtege and Protege Desktop" <
>> [email protected]>
>> *Subject:* [protege-user] Is there a way to hide non-English annotations=
?
>> I'm working with the DCAT W3C Data Catalog ontology. It has a ton of
>> comments in around 20 different languages. It makes finding the ones you
>> want to read a bit hard to find. I considered deleting the non-english o=
nes
>> but there are reasons in terms of how the ontology I'm building will be
>> used that make that not an option.
>>
>> I looked at the various preferences to see if there was a way to hide
>> non-English annotations but didn't see anything. The one thing I thought
>> might work is on the dialog that comes up on File>Preferences>Renderer w=
hen
>> you hit the Configure button you get a dialog to define the label
>> annotation properties and their order and there is a field at the bottom
>> with the values:
>>
>> "en, en-US, !"
>>
>> I thought if I deleted the ! that might just show English annotations.
>> That was a longshot anyway because that dialog is for labels not all
>> annotations but I thought maybe. But nothing changes when I remove the
>> exclamation mark. I also thought "maybe it needs to be set before the
>> ontology loads" but when I load my ontology that imports DCAT the pref g=
ets
>> set back to include the !
>>
>> If there are any tricks or hacks to just show english while keeping the
>> other languages appreciate the feedback.
>>
>> Michael
>> https://www.michaeldebellis.com/blog
>> _______________________________________________ protege-user mailing lis=
t
>> [email protected]
>> https://mailman.stanford.edu/mailman/listinfo/protege-user
>> _______________________________________________
>> protege-user mailing list
>> [email protected]
>> https://mailman.stanford.edu/mailman/listinfo/protege-user
>
> _______________________________________________ protege-user mailing list
> [email protected]
> https://mailman.stanford.edu/mailman/listinfo/protege-user
> _______________________________________________
> protege-user mailing list
> [email protected]
> https://mailman.stanford.edu/mailman/listinfo/protege-user
>

--00000000000086a92e0646556d8d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Igor,=C2=A0 The only thing that worries me about doing tha=
t is I could see myself making changes to the one with the non-English anno=
tations removed... but come to think of it, there are so many extra comment=
s that aren&#39;t in English in DCAT it would be pretty hard not to notice,=
 so I think I will try that. It will make browsing and understanding DCAT e=
asier. Actually another thing I could do is just write a SPARQL update to a=
dd a comment on each entity that says something like &quot;ENGLISH ONLY VER=
SION, DO NOT EDIT!&quot; Thanks, that&#39;s a great idea.<div><br></div><di=
v>Michael</div></div><br><div class=3D"gmail_quote gmail_quote_container"><=
div dir=3D"ltr" class=3D"gmail_attr">On Fri, Dec 19, 2025 at 1:47=E2=80=AFP=
M Igor Toujilov via protege-user &lt;<a href=3D"mailto:[email protected]=
tanford.edu">[email protected]</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div><div style=3D"font-family:=
Verdana;font-size:12px"><div>
<p align=3D"left" style=3D"line-height:100%;margin-bottom:0in">I did not me=
an permanently stripping off multilingual annotations. You can use the redu=
ced ontology just for search, and then return to the original ontology for =
other tasks.</p>

<div>=C2=A0
<div name=3D"quote" style=3D"margin:10px 5px 5px 10px;padding:10px 0px 10px=
 10px;border-left:2px solid rgb(195,217,229)">
<div style=3D"margin:0px 0px 10px"><b>Sent:</b>=C2=A0Thursday, December 18,=
 2025 at 9:30 PM<br>
<b>From:</b>=C2=A0&quot;Michael DeBellis&quot; &lt;<a href=3D"mailto:mdebel=
[email protected]" target=3D"_blank">[email protected]</a>&gt;<br>
<b>To:</b>=C2=A0&quot;User support for WebProtege and Protege Desktop&quot;=
 &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">p=
[email protected]</a>&gt;<br>
<b>Subject:</b>=C2=A0Re: [protege-user] Is there a way to hide non-English =
annotations?</div>

<div name=3D"quoted-content">
<div>Thanks Igor, that&#39;s a great idea but unfortunately it won&#39;t wo=
rk for this ontology.=C2=A0
<div><br>
As I understand it, for W3C vocabularies like DCAT, multilingual annotation=
s are normative. Labels and comments with language tags are part of the sta=
ndard=E2=80=99s internationalization support, and downstream tooling (catal=
ogs, portals, UI layers, and national data platforms) rely on them to prese=
nt metadata in the user=E2=80=99s preferred language. Removing them would b=
reak conformance with DCAT=E2=80=99s design goals and reduce interoperabili=
ty, especially in European and international contexts where multilingual ca=
talogs are the norm.=C2=A0</div>

<div>=C2=A0</div>

<div>Since I want what I&#39;m building to be as consistent with those othe=
r tools as possible, I need to leave them in. I don&#39;t think there is a =
way to hide them but just wanted to see if there was something I was missin=
g.=C2=A0</div>
</div>
=C2=A0

<div class=3D"gmail_quote">
<div class=3D"gmail_attr">On Thu, Dec 18, 2025 at 12:09=E2=80=AFPM Igor Tou=
jilov via protege-user &lt;<a href=3D"mailto:[email protected]=
u" target=3D"_blank">[email protected]</a>&gt; wrote:</div>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div style=3D"font-family:Verdana;font-size:12px">
<div>
<p align=3D"left" style=3D"line-height:100%;margin-bottom:0in">Hi Michael,<=
/p>

<p align=3D"left" style=3D"line-height:100%;margin-bottom:0in">This is not =
straightforward approach, but it may help:</p>

<p align=3D"left" style=3D"line-height:100%;margin-bottom:0in">=C2=A0</p>

<p align=3D"left" style=3D"line-height:100%;margin-bottom:0in">-- Save the =
original ontology in a convenient format, e. g. XML/RDF.</p>

<p align=3D"left" style=3D"line-height:100%;margin-bottom:0in">-- Write a s=
cript, e. g. XSLT, or a program to strip the unwanted annotations.</p>

<p align=3D"left" style=3D"line-height:100%;margin-bottom:0in">-- Use the r=
educed ontology in Protege.</p>

<p align=3D"left" style=3D"line-height:100%;margin-bottom:0in">=C2=A0</p>

<p align=3D"left" style=3D"line-height:100%;margin-bottom:0in">Cheers,</p>

<p align=3D"left" style=3D"line-height:100%;margin-bottom:0in">Igor</p>
</div>

<div>
<div>=C2=A0
<div style=3D"margin:10px 5px 5px 10px;padding:10px 0px 10px 10px;border-le=
ft:2px solid rgb(195,217,229)">
<div style=3D"margin:0px 0px 10px"><b>Sent:</b>=C2=A0Thursday, December 18,=
 2025 at 4:15 AM<br>
<b>From:</b>=C2=A0&quot;Michael DeBellis&quot; &lt;<a href=3D"mailto:mdebel=
[email protected]" target=3D"_blank">[email protected]</a>&gt;<br>
<b>To:</b>=C2=A0&quot;User support for WebProtege and Protege Desktop&quot;=
 &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">p=
[email protected]</a>&gt;<br>
<b>Subject:</b>=C2=A0[protege-user] Is there a way to hide non-English anno=
tations?</div>

<div>
<div>I&#39;m working with the DCAT W3C Data Catalog ontology. It has a ton =
of comments in around 20 different languages. It makes finding the ones you=
 want to read a bit hard to find. I considered deleting the non-english one=
s but there are reasons in terms of how the ontology I&#39;m building will =
be used that make that not an option.
<div>=C2=A0
<div>I looked at the various preferences to see if there was a way to hide =
non-English annotations but didn&#39;t see anything. The one thing I though=
t might work is on the dialog that comes up on File&gt;Preferences&gt;Rende=
rer when you hit the Configure button you get a dialog to define the label =
annotation properties and their order and there is a field at the bottom wi=
th the values:</div>

<div>=C2=A0</div>

<div>&quot;en, en-US, !&quot;</div>

<div>=C2=A0</div>

<div>I thought if I deleted the ! that might just show English annotations.=
 That was a longshot anyway because that dialog is for labels not all annot=
ations but I thought maybe. But nothing changes=C2=A0when I remove the excl=
amation mark. I also thought &quot;maybe it needs to be set before the onto=
logy loads&quot; but when I load my ontology that imports DCAT the pref get=
s set back to include the !</div>

<div>=C2=A0</div>

<div>If there are any tricks or hacks to just show english while keeping th=
e other languages appreciate the feedback.</div>

<div>=C2=A0</div>

<div>Michael</div>

<div><a href=3D"https://www.michaeldebellis.com/blog" target=3D"_blank">htt=
ps://www.michaeldebellis.com/blog</a></div>
</div>
</div>
_______________________________________________ protege-user mailing list <=
a href=3D"mailto:[email protected]" target=3D"_blank">protege=
[email protected]</a> <a href=3D"https://mailman.stanford.edu/mailma=
n/listinfo/protege-user" target=3D"_blank">https://mailman.stanford.edu/mai=
lman/listinfo/protege-user</a></div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
protege-user mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">proteg=
[email protected]</a><br>
<a href=3D"https://mailman.stanford.edu/mailman/listinfo/protege-user" targ=
et=3D"_blank">https://mailman.stanford.edu/mailman/listinfo/protege-user</a=
></blockquote>
</div>
_______________________________________________ protege-user mailing list <=
a href=3D"mailto:[email protected]" target=3D"_blank">protege=
[email protected]</a> <a href=3D"https://mailman.stanford.edu/mailma=
n/listinfo/protege-user" target=3D"_blank">https://mailman.stanford.edu/mai=
lman/listinfo/protege-user</a></div>
</div>
</div>
</div></div></div>
_______________________________________________<br>
protege-user mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">proteg=
[email protected]</a><br>
<a href=3D"https://mailman.stanford.edu/mailman/listinfo/protege-user" rel=
=3D"noreferrer" target=3D"_blank">https://mailman.stanford.edu/mailman/list=
info/protege-user</a><br>
</blockquote></div>

--00000000000086a92e0646556d8d--

--===============2684592936064051178==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
protege-user mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/protege-user

--===============2684592936064051178==--