<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear Jocelyn,</p>
<div class="moz-cite-prefix">On 06.09.2026 13:39, Jocelyn Aznar via
Lingtyp wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3218aaf0-0ebc-47bc-bd03-b3bf92aa7b9d@jocelynaznar.eu">Dear
Yuri,
<br>
<br>
Le 06/09/2026 à 07:25, Yuri Koryakov via Lingtyp a écrit :
<br>
<blockquote type="cite">On the one hand, all information not added
by people themselves is taken from public online sources; people
add further information voluntarily. On the other hand, this
table does not contain any sensitive personal information – no
emails, place of residence, place of work, position, etc.
<br>
</blockquote>
<br>
Note that you suggest to people to provide email address in the
comment section.
<br>
</blockquote>
<p class="MsoNormal"><span lang="EN-US"
style="mso-ansi-language:EN-US">Yes, you're
right. Although this only applies to quite rare cases where
there are complete
namesakes and they need to be distinguished somehow, and only as
one of the
methods. I've added ORCID, by the way, thanks for the idea!</span></p>
<blockquote type="cite"
cite="mid:3218aaf0-0ebc-47bc-bd03-b3bf92aa7b9d@jocelynaznar.eu">In
some countries (like the US), the pronoun to use is actually a
sensitive personal information, as it reveal gender info. Native
language can be a proxy for ethnic identity which also can be
problematic in many countries. Google Doc, especially with a free
account, is not safe for personal info, not to mention that
someone/AI could vandalize the spreadsheet and insert/modify the
data, and when collecting personal info, the database creator is
responsible of providing a database which is secured enough
according to the sensitivity of the info collected.
<br>
</blockquote>
<!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" LatentStyleCount="156">
</w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Обычная таблица";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
</style>
<![endif]-->
<p class="MsoNormal"><span lang="EN-US"
style="mso-ansi-language:EN-US">Yes, it's very important. For a
while, I'll keep
an eye out for vandalism by checking the edit history. After
the active phase of adding names, I will make a static webpage
and change the way new names are added.</span></p>
<blockquote type="cite"
cite="mid:3218aaf0-0ebc-47bc-bd03-b3bf92aa7b9d@jocelynaznar.eu">More
practical issue, I can imagine in the US that inviting a
researcher that asked for the pronoun they could be problematic,
either for the researcher or the lab inviting them. As it is
information available on Google Doc, this will be automatically
scanned by the IA that the border police uses.
<br>
</blockquote>
<p class="MsoNormal"><span lang="EN-US"
style="mso-ansi-language:EN-US">Horrible, I
didn't know about such problems in the US (I would understand if
it were Russia...).</span></p>
<blockquote type="cite"
cite="mid:3218aaf0-0ebc-47bc-bd03-b3bf92aa7b9d@jocelynaznar.eu">Birthday
can also be problematic actually, as the other disambiguators, as
they allow to identify the person, which is normal for the purpose
of this database, two people having the same name might want
different ways of being addressed. Better in this case ORCID or
professional URL which are publicly available data.
<br>
<br>
Somehow, GDPR might seem annoying, but, in this day and age of IA,
any info available on internet is being scrapped and compiled, and
automatically analyzed by more and more fascist governments and
organizations for whatever reasons they have, or will have.
Somehow, I wonder more and more about the relevance of open access
data in this new context.
<br>
</blockquote>
<p class="MsoNormal"><span lang="EN-US"
style="mso-ansi-language:EN-US">To
sum up, I can say that all sensitive information is added by
people
themselves. Just in case, I've added the following warning: <b>Warning</b>:
All information you provide will be publicly available. If you
feel any information is too sensitive and/or could be used
against you, do not provide it.</span></p>
<blockquote type="cite"
cite="mid:3218aaf0-0ebc-47bc-bd03-b3bf92aa7b9d@jocelynaznar.eu">
<blockquote type="cite">
<blockquote type="cite">- There isn't only one valid
pronunciation of my name.
<br>
</blockquote>
<br>
The IPA column allows you to specify multiple pronunciation
variants, both equivalent and language-specific.
<br>
</blockquote>
<br>
Right.
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">
<br>
- I'm ok with people having difficulties pronouncing my name
(at the end of the day, no one can master the pronunciation of
the many phonologies we work with in our profession).
<br>
- Pushing people to pronounce your name following your
expectations can cause situations in which they feel really
ill at ease because they cannot pronounce your name.
<br>
</blockquote>
Well, we don't force people to pronounce the names exactly this
way, but we do give them a reference point. For example, when I
just see the name Jocelyn, I don't even know what the first
sound might be – [ʤ / ʒ / x / j] or something else.
<br>
</blockquote>
<br>
Of course I understand this issue.
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">- I'm also ok with people adapting my
name if it is too hard to pronounce, that's usually what
happens in practice.
<br>
- From a more technical angle,it would make more sense if the
IPA transcription follows the same order of the first name +
other name.
<br>
</blockquote>
Okay, maybe. But this way one can show the order in which a
person prefers to pronounce their name. (By the way, the most
common order in this column is: first name + other name.)
<br>
</blockquote>
<br>
This is not so clear from the instruction neither, and this is not
what's systematically done from the data that was already
populated.
<br>
</blockquote>
The Guide says "Please provide a transcription of your full name (<b>in
your preferred order</b>)."
<blockquote type="cite"
cite="mid:3218aaf0-0ebc-47bc-bd03-b3bf92aa7b9d@jocelynaznar.eu"><br>
For the purpose of this database, I would have a dedicated column
for the preferred name for a seminar/event, not just "Other names"
which can lead to confusion as it might contain many info in
different order. 1 info : 1 column.</blockquote>
If I created a separate column for each type of information, the
database would grow too large. And in general, a person can provide
the preferred name for a seminar/event when registering for that
seminar/event.
<blockquote type="cite"
cite="mid:3218aaf0-0ebc-47bc-bd03-b3bf92aa7b9d@jocelynaznar.eu">I
think this project would be better handled through the server of
an institution (well, more of our institutions rely on
Microsoft/Google and co., but if they pay for the services, the
data might be actually properly handled), with a better interface,
like a form in which people can enter these info and a page that
displays those info.
<br>
</blockquote>
Yes, perhaps that would be the ideal solution. But I don't have such
possibility (and I'm not sure all linguists would be willing to
provide such information on a Russian institution's server). I
proceed from a simple maxim: The best is the enemy of the good.
<blockquote type="cite"
cite="mid:3218aaf0-0ebc-47bc-bd03-b3bf92aa7b9d@jocelynaznar.eu"><br>
Best,
<br>
Jocelyn
<br>
</blockquote>
Yours,<br>
Yuri
<blockquote type="cite"
cite="mid:3218aaf0-0ebc-47bc-bd03-b3bf92aa7b9d@jocelynaznar.eu">_______________________________________________
<br>
Lingtyp mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Lingtyp@listserv.linguistlist.org">Lingtyp@listserv.linguistlist.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://listserv.linguistlist.org/cgi-bin/mailman/listinfo/lingtyp">https://listserv.linguistlist.org/cgi-bin/mailman/listinfo/lingtyp</a>
<br>
</blockquote>
</body>
</html>