Hi!
Thank you for your comments!
Joe, I translated for you list of lectures / questions from Russian to
English, see https://bit.ly/3yyIYyH
I hope this helps you.
The most complex part for students is writing the chapter for this book.
One student selects one Wikidata object and we together with a student
think - which interesting properties we can calculate and visualize using
SPARQL.
I prepared the algorithm for students which contain 14 formal steps, see
https://w.wiki/3MSW (in Russian).
But of course, each student requires a lot of personal work (with teacher),
see attached the file which contains an example of my comments to the
Russian student's work (3 pages of the book).
It requires several iterations before I give up and say to a student that
it is enough, it is OK.
At this moment, I'm sure, there are a lot of errors in this book. But from
version to version, I hope, this book will be more clear and solid :)
After one semester of work with 6 students (September 2020 - January 2021)
we prepared 6 chapters in our draft of the book "Wikidata programming" in
Russian and in English.
Now I finished work with my students. I hope to continue work with new
students in September-December 2021. Then I will add new extended chapters
from my Wikiversity course (
https://en.wikiversity.org/wiki/Research_in_programming_Wikidata) to this
LaTeX book.
What kind of help I want from you.
If you want to describe some topics related to Wikidata, which will be
useful for beginners, it will be great.
At this moment the book contains chapters with research about different
objects of Wikidata.
Now this book looks like a book with specific programming recipes.
But there is no introduction describing the basic elements of SPARQL and
basic elements of Wikidata, the Wikidata interface, an overview of
scientific articles on Wikidata.
I think these are very important parts that the book is missing right now.
So, I hope to find co-authors for this book.
Best regards,
Andrew Krizhanovsky.
On Wed, 19 May 2021 at 21:52, Joe Corneli <holtzermann17(a)gmail.com> wrote:
> Could you share the syllabus of the course you are teaching please? I am
> getting involved in teaching and something like this could inspire the
> faculty here.
>
> On Wed, 19 May 2021 at 19:29, Andrew Krizhanovsky <
> andrew.krizhanovsky(a)gmail.com> wrote:
>
> > Hello all.
> >
> > We wrote the very first version of the book "Programming Wikidata for
> youth
> > and students":
> >
> https://www.dropbox.com/sh/0ujam53seriygmg/AAA83UtcAA5dCL2LpQ4ueOQGa?dl=0
> >
> > LaTeX source code is available on GitHub:
> > https://github.com/componavt/wd_book
> >
> > If you are interested in participating in the writing of this book,
> > please write
> > to me (andrew.krizhanovsky at gmail.com).
> >
> > I am teaching a course at Petrozavodsk State University, the results of
> > this course are presented in the Wikiversity project "Research in
> > programming Wikidata" (https://w.wiki/3MKp). Therefore, I hope that this
> > book will be updated and replenished with new materials every year.
> >
> > Best regards,
> > Andrew Krizhanovsky.
> > _______________________________________________
> > Wiki-research-l mailing list -- wiki-research-l(a)lists.wikimedia.org
> > To unsubscribe send an email to
> wiki-research-l-leave(a)lists.wikimedia.org
> >
> _______________________________________________
> Wiki-research-l mailing list -- wiki-research-l(a)lists.wikimedia.org
> To unsubscribe send an email to wiki-research-l-leave(a)lists.wikimedia.org
>
Hello all.
We wrote the very first version of the book "Programming Wikidata for youth
and students":
https://www.dropbox.com/sh/0ujam53seriygmg/AAA83UtcAA5dCL2LpQ4ueOQGa?dl=0
LaTeX source code is available on GitHub:
https://github.com/componavt/wd_book
If you are interested in participating in the writing of this book,
please write
to me (andrew.krizhanovsky at gmail.com).
I am teaching a course at Petrozavodsk State University, the results of
this course are presented in the Wikiversity project "Research in
programming Wikidata" (https://w.wiki/3MKp). Therefore, I hope that this
book will be updated and replenished with new materials every year.
Best regards,
Andrew Krizhanovsky.
We are thrilled to announce that the International Workshop on Archives and
Linked Data (https://linkedarchives.inesctec.pt/) will be run in
conjunction with the 25th International Conference on Theory and Practice
of Digital Libraries (TPDL 2021) (http://www.tpdl.eu/tpdl2021/).
The workshop aims to gather researchers and specialists who are engaged in
initiatives that cross Archives and the Semantic Web and those planning
similar initiatives in cultural heritage organizations.
We'd love to have your contributions, so please take a look at the call:
https://linkedarchives.inesctec.pt/#submission.
Please note that *20 June 2021* is the submission deadline.
The workshop will include invited talks, presentations of papers and demos,
as well as an opportunity for participants to meet and discuss latest
developments and opportunities in the field.
TPDL 2021 is an online event and registration will be free of cost.
Workshop papers are published and extended versions of best papers are
candidates for publication in the ACM Journal on Computing and Cultural
Heritage <https://dl.acm.org/journal/jocch> (JOCCH).
We look forward to receiving your submissions and seeing you in September!
Best,
Carla Teixeira Lopes
(on behalf of the Organizing Committee)
Hello all,
I am a relatively new Wikidata user, and have run across some inconsistency with regard to given names, sex/gender, and the intersections of the two concepts. I'm not sure what conversations have already happened, or what the best solutions are.
Given names:
Given names can be classed as given name<https://www.wikidata.org/wiki/Q202444>, or any of 42 subclasses of given name<https://w.wiki/3Kwj>, which include "female given name<Q11879590>", "male given name<Q12308941>", and "unisex given name<Q3409032>" (among others). The real-world application of these gender-specific classes to items for given names is problematic for a number of reasons.
Names associated with one gender in one culture and/or time period are frequently associated with another or all genders in other cultures and/or time periods. This is not well adjusted for in practice in Wikidata. Some names include "instance of<https://www.wikidata.org/wiki/Property:P31>" statements for multiple classes on the same name item, and others proliferate items for the same name string for usage by various genders. It seems like a burdensome, if not impossible, endeavor for little return to try to straighten it out.
Assigning gendered given names can lead to incorrect assumptions about a living person's sex or gender. Bots use labels to assign values for given names, regardless of whether the person's gender identity is known and asserted on Wikidata. This can lead to unreferenced statements being made about the sex or gender of a living person, based solely on the label, as discussed here<https://www.wikidata.org/wiki/Wikidata:Project_chat#Bots_using_Labels_to_Po…>. This is understandable-the concept of gender differs widely across cultures, as does the usage of many given names. Someone in Russia, where given names are more closely tied to gender, may see an item for a person with a "male given name" and assume that the person identifies as male. Which is by no means always the case in every culture.
Since there is a very widely used property for sex or gender, it would be easy to determine which gender groups are represented in a group of people/items sharing the same given name with a simple query<https://w.wiki/3Kwm>, without a need for all the different gender-dependent subclasses of names.
Sex or gender:
A related problem is the assignment of sex or gender values to living persons based on weak assumptions. I'm sure my example above is not an isolated incident. There are many constraints in Wikidata that prod users to assign sex or gender values to items for humans. For example, values of the property "student of<https://www.wikidata.org/wiki/Property:P1066>" have an item-requires-statement constraint of property "sex or gender<https://www.wikidata.org/wiki/Property:P21>". Flagging the absence of this statement and suggesting it be added, when the sex or gender of many people represented in Wikidata is not known, creates a situation ripe for unintentional misgendering<https://en.wikipedia.org/wiki/Transphobia#Misgendering>.
Many living people may not want their gender identities made public, for many valid reasons ranging from a simple desire for personal privacy to a fear for personal safety. This seems to fall under the Wikidata policy for living people section on statements that may violate privacy<https://www.wikidata.org/wiki/Wikidata:Living_people#Statements_that_may_vi…>. A number of properties for attributes of living persons include both a "living person protection class<https://www.wikidata.org/wiki/Property:P8274>" of "property that may violate privacy<https://www.wikidata.org/wiki/Q44601380>" and a "property constraint<https://www.wikidata.org/wiki/Property:P2302>" of "citation needed constraint<https://www.wikidata.org/wiki/Q54554025>" with a constraint status of either mandatory<https://www.wikidata.org/wiki/Q21502408> constraint or suggested<https://www.wikidata.org/wiki/Q62026391> constraint.
Given the fact that people with many gender identities face persecution and may not want to make their gender identity public, and given the fact that harm can be done by wrongly assuming someone's gender identity on Wikidata, I think both a protection class and citation needed constraint are overdue for P21.
I also see that the Wikidata protection policy<https://www.wikidata.org/wiki/Wikidata:Protection_policy> includes Create-protection, which can prevent a page from being created except by certain users. I see that it cannot be applied to deleted items or properties. It seems possible, and perhaps very useful, to add specific properties used with specific items to the Create-protection policy in order to protect the privacy of living persons. For instance, if a person didn't want their sex or gender, their political party, their sexual orientation, or some other piece of personal information disclosed on Wikidata, it would be useful to protect that item from having those corresponding properties created at all.
What do members of this list think of:
-Separating the concepts of sex/gender and given name in Wikidata?
-Separating given names from other attributes of persons, such as nationality or ethnic group?
-Removing property constraints that require sex or gender to be identified in items for persons?
-Adding the living person protection class of "property that may violate privacy" to "sex or gender" (P21)?
-Adding a property constraint of "citation needed constraint" with a constraint status of either mandatory constraint or suggested constraint?
-Adding protections against the creation of specific property statements being added to specific items for living persons?
Where could such changes be discussed, voted on, or proposed to the community? I also don't know where to look for past conversations surrounding these issues, which almost certainly exist and would be useful to review.
Thanks,
Crystal Clements, MLIS
Science Cataloger
Cataloging and Metadata Services
University of Washington Libraries
Box 352900
Seattle, Washington 98195
cec23(a)uw.edu
Is it expected that everyday Wikidata editors will know they should bypass that warning, and how to do it? That warning stopped me in my tracks.
-----Original Message-----
From: Smit <me(a)smitop.com>
Sent: Friday, May 14, 2021 4:07 PM
To: Crystal E. Clements <cec23(a)uw.edu>; wikidata(a)lists.wikimedia.org
Subject: Re: [Wikidata] Re: Given Names and Sex/Gender for Humans in Wikidata
On 2021-05-14 6:53 p.m., Crystal E. Clements wrote:
> Thanks, Smit. I've read about that on the property chat for P21. I
> haven't been able to get it to work. Here's an example (I know this
> person's gender and fixed the statement after taking this screen shot
> of my feeble attempt at "unknown value"). Am I doing it wrong?
You can bypass that warning by hitting "publish" again (warnings generated from edit filters can always be bypassed by attempting to do the edit again). That error message is coming from
https://www.wikidata.org/wiki/Special:AbuseFilter/13
which doesn't seem to handle unknown value properly.
Note that all edits where that warning was ignored can be seen at https://www.wikidata.org/wiki/Special:RecentChanges?tagfilter=Unexpected+va…
Thanks, Smit. I've read about that on the property chat for P21. I haven't been able to get it to work. Here's an example (I know this person's gender and fixed the statement after taking this screen shot of my feeble attempt at "unknown value"). Am I doing it wrong?
[cid:image001.png@01D748D8.ED6935B0]
-----Original Message-----
From: Smit <me(a)smitop.com>
Sent: Friday, May 14, 2021 3:30 PM
To: Crystal E. Clements <cec23(a)uw.edu>; wikidata(a)lists.wikimedia.org
Subject: Re: [Wikidata] Given Names and Sex/Gender for Humans in Wikidata
On 2021-05-14 6:22 p.m., Crystal E. Clements wrote:
> Given the fact that people with many gender identities face
> persecution and may not want to make their gender identity public, and
> given the fact that harm can be done by wrongly assuming someone's
> gender identity on Wikidata, I think both a protection class and
> citation needed constraint are overdue for P21.
Note that this is currently handled by setting that property to "unknown value" and adding an explanation in a reference.