Summary: Wiki Workshop 2022  will take place virtually as part of
The Web Conference 2022 . Call for papers is now open:
https://wikiworkshop.org/2022/#call . Deadline to submit for paper to
appear in the proceedings of the conference is Feb 3, for all other
submissions March 10. The workshop will take place on April 25, 2022.
We are delighted to announce that Wiki Workshop 2022  will be held
virtually April 25, 2022 and as part of the Web Conference 2022 .
In the past years, Wiki Workshop has traveled to Oxford, Montreal,
Cologne, Perth, Lyon, and San Francisco, and (virtually) to Taipei and
Last year, we had more than 150 participants in the workshop along
with 22 accepted paper presentations, keynote, panel, music and more.
The workshop is now a vibrant event for Wikimedia researchers and
those interested in this space to get together on an annual basis.
We encourage contributions by all researchers who study the Wikimedia
projects. We specifically encourage 1-2 page submissions of
preliminary research. You will have the option to publish your work as
part of the proceedings of The Web Conference 2022.
You can read more about the call for papers and the workshop at
http://wikiworkshop.org/2022/#call. Please note that the deadline for
the submissions to be considered for proceedings is February 3. All
other submissions should be received by March 10.
If you have questions about the workshop, please let us know on this
list or at wikiworkshop(a)googlegroups.com.
Looking forward to seeing many of you in this year's edition.
Srijan Kumar, Georgia Tech
Emily Lesack, Wikimedia Foundation
Miriam Redi, Wikimedia Foundation
Bob West, EPFL
Leila Zia, Wikimedia Foundation
We are currently in discussions about possibly introducing a new property
that might simply be called* "activity" or "activities"* to hold the value
of a popular *"things to do"* that you typically see in search results when
looking around tourist attractions, parks, etc.
The risk is that of large lands, administrative territories, or country
being abused, but this could be mitigated by disallowing that new property
on those broader kinds of instances where it doesn't make sense. I.E. a
proposed property would likely be much more specific to things that
typically do have activities as advertised or managed by governments
through various amenities or resources, such as "boating" because the
government maintains a "boat ramp" for public use, etc. And would *not
allow* something like Switzerland https://www.wikidata.org/wiki/Q39 =
"activity": "snow skiing" as an example.
"activity" has a corollary with "amenity" which is different. "swimming"
an activity *is not* "swimming pool" an amenity.
The discussion over this new property is likely to directly overlap with
OpenStreetMap and their properties and tags (some of which are enumerated),
where they have Tag:amenity=swimming pool (new tag is leisure:swimming pool)
<https://wiki.openstreetmap.org/wiki/Tag:leisure%3Dswimming_pool> as an
example. Some activities are *a sport*, and others are *not a sport*.
In Schema.org, we already have https://schema.org/TouristAttraction but
there's no property already made to hold "hasActivities" for example. (but
we could in the future if deemed useful) @Dan Brickley <danbri(a)google.com>
Also, a new property like "activity" or "has activities" would align quite
well to many search services such as Google, Bing, Yandex having similar
lookup services such as https://www.google.com/search?q=activities+near+me
as well as Government services such as https://www.recreation.gov like
https://www.recreation.gov/search?q=boating and several other European and
international lookup services.
The initial discussion is here if you want to see some of the provenance
and work I've been doing:
Whew, too long, ok... Thoughts?
Hello Wikidata users,
I am worried about a growing trend I have been noticing in new property
proposals over the last 3 years or so. This is around SEO tactics, but
slighted against our lovely GLAM institutions who I have the utmost
respect for as I've worked for some over my career.
I've written a quick summary comment in one of the pending property
proposals to bring some attention to my worries, but I thought it was
probably important enough to copy here for a wider audience.
[image: Pictogram voting comment.svg] *Comment* Finally, I'm worried that I
am seeing more "at" kind of properties being proposed in the last 3 years,
that are basically providing little metadata to users, and instead are
simply being minted as more or less "GLAM SEO tactics". We should be trying
to provide deeper information for users, and not simply "more info about
subject at this institution" style properties (in whatever subform they are
taking). We are better than that. We can do better than that. Let's think
more about what users are likely missing from finding information on a
given subject, and their needs for *disambiguating that information*. It
might mean we need less properties and instead provide richer metadata in
the form of qualifiers or better qualifiers than we have now to help users.
--Thadguidry <https://www.wikidata.org/wiki/User:Thadguidry> (talk
<https://www.wikidata.org/wiki/User_talk:Thadguidry>) 05:08, 28 December
Replies in kind are best done in the property proposal discussion link
above for the best context, if you can.
Otherwise, you can reply in this thread.
Greetings from Afrocine Project,
It is already the end of the Months of African Cinema global contest and a
lot has been achieved! We have been able to get over 4,000 articles created
in 16 languages!
We are about to constitute the International Jury team, which will consist
of members from all the languages that participated in the global
contest/edit-a-thon. If you would like to join us in the Jury team, please
let us know by 31 December 2021 by filling this form.
Thanks for all your contributions this year and congratulations to you!
Together we are bridging the content gap and improving on the systemic
bias, in-respect of the African continent.
Community Liaison – Afrocine project
I am currently working on the wiki data knowledge graph to compute the article's embeddings.
My question is the following: are some entities of the graph redirected? And if yes: how can I redirect these nodes, are there some redirection tables?