Wikidata June 2021

wikidata@lists.wikimedia.org

26 participants
32 discussions

On the subject of Linked Data Availability and Retention
by Thad Guidry 01 Jul '21

01 Jul '21

Hi Community! We often act like and think that things are, well ... forever (even our own lives!). But Time waits for no one. So... I had posted this over in the LD4 Slack channel but thought that this would be good for folks here to at least always be aware of and think about in our growing Linked Data world. ---- All Linked Data efforts need stable identifiers (on both ends of a "link"). I.E. linking is only good if the other side will be retrievable and available (online or offline through web/archives/files) throughout the expected lifetime of an effort and beyond. Think closely about "knowledge retention" (libraries/books hold knowledge for hundreds of years!) and what the Linked Data lifecycle itself that ideally will do that for your projects. Then look towards not the tools, but instead the communities that are well established and have the likelihood to continue to provide stable identifiers that are retrievable well into the future + another 100+ years. This might include government efforts, or communities that have foundations behind them that are well grounded through philanthropic means with perpetuity ... to avoid link rot or non-retrievability through complete void of the knowledge or stable identifiers in the future. I'm hopeful that communities will think about data retention policies and generally "Linked Data Availability" much more deeply and seriously. This could be likened to something like GitHub's Arctic Vault, Internet Archive, or decentralized storage solutions like Filecoin, to be able to backup and retain the knowledge for thousands of years, if need be. --- Thad https://www.linkedin.com/in/thadguidry/ https://calendly.com/thadguidry/

4 3

Weekly Summary #474
by Mohammed Sadat Abdulai 28 Jun '21

28 Jun '21

*Here's your quick overview of what has been happening around Wikidata over the last week.* Discussions - New request for comments: Automatic analysis and breakdown of links (for social accounts reference) <https://www.wikidata.org/wiki/Wikidata:Requests_for_comment/Automatic_analy…> Events <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Events> - Past: - log of Wikibase Live session 2021-06-24 <https://meta.wikimedia.org/wiki/Wikibase_Community_User_Group/Meetings/2021…> - Upcoming: - SPARQL queries live on Twitch <https://www.twitch.tv/belett> and in French by Vigneron, June 28 at 18:00 CEST - Next Linked Data for Libraries LD4 Wikidata Affinity Group <https://www.wikidata.org/wiki/Wikidata:WikiProject_LD4_Wikidata_Affinity_Gr…> call: Robert Chavez (Northeastern University) will provide an introduction to SPARQL and using the Wikidata Query Service.; [1] <https://docs.google.com/document/d/14wazqg7XJM3Asqq4kFcNHCVgBOGODRp0U8yFc-2…>, June 29th. - Online Wikidata meetup in Swedish #69 <https://www.wikidata.org/wiki/Wikidata:Events/Swedish_online_editathon#Träf…>, July 4 Press, articles, blog posts, videos <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Press_coverage> - Blogs - A Journey Into Wikidata with Five Indigenous Artists <https://linkeddigitalfuture.ca/2021/06/22/wikidata-with-five-indigenous-art…> - Adding Data to Wikidata is Efficient with QuickStatements <https://blogs.bl.uk/digital-scholarship/2021/06/adding-data-to-wikidata-is-…> - Papers - Which methods are the most effective in enabling novice users to participate in ontology creation? A usability study <https://www.wikidata.org/wiki/Q107338764> (compares Wikidata to other knowledge modelling tools) - Videos - LIVE Wikidata editing #47 - YouTube <https://www.youtube.com/watch?v=QywDX83OZrw>, Facebook <https://www.facebook.com/groups/WikidataCommunity/permalink/298581516170364…>, for the #ArcticKnot. - SPARQL queries live on Twitch about lexicography and lexemes <https://www.youtube.com/watch?v=9Dvzb4Svzck> by Vigneron, for the #ArcticKnot. - Wikidata Lab XXX: Roundtripping process for Tainacan - YouTube <https://www.youtube.com/watch?v=x6m0rRgadu4> - Creating a new faculty item in Wikidata - [ https://www.youtube.com/watch?v=fu68LM5NicM YouTube - Writing data to Wikidata <https://www.youtube.com/watch?v=9fC3oXvQfqI>, Wikidata Sandbox items <https://www.youtube.com/watch?v=nvWkaCcEEHA> Tool of the week - Template:Item documentation <https://www.wikidata.org/wiki/Template:Item_documentation> now includes Template:Generic queries for positions <https://www.wikidata.org/wiki/Template:Generic_queries_for_positions>. It can be used for every position item in the talk page. See example with head of the United Nations Secretariat <https://www.wikidata.org/wiki/Talk:Q81066>. Other Noteworthy Stuff - Wikidata Community/Diversity 2021 Survey has been published <https://commons.wikimedia.org/wiki/File:Wikidata_Community_Survey_2021.pdf>. The results are meant to serve as a baseline to see how the community might (not) change in the future. Feel free to give us your feedback on this discussion page <https://www.wikidata.org/wiki/Wikidata_talk:Usability_and_usefulness/2021-2…> . - Call for candidates for the 2021 election to the position of primary contact <https://meta.wikimedia.org/wiki/Wikibase_Community_User_Group/2021_contact_…> for the Wikibase Community User Group <https://meta.wikimedia.org/wiki/Wikibase_Community_User_Group>. Applicants should present themselves on this page <https://meta.wikimedia.org/wiki/Wikibase_Community_User_Group/2021_contact_…> before *2021-07-08 17:00 (UTC)*, after which voting will commence. - Bodh <https://www.wikidata.org/wiki/Wikidata:Bodh> is a new tool to edit Lexemes by hand on a larger scale. - Wikidata Vertical Analysis <https://wikitech.wikimedia.org/wiki/User:AKhatun/Wikidata_Vertical_Analysis> by AKhatun (WMF) - Wikidata Lexeme Forms now supports Igbo nouns <https://lexeme-forms.toolforge.org/template/igbo-noun/> - Wikidata Lexeme Forms now supports Malayalam proper nouns <https://twitter.com/LucasWerkmeistr/status/1406334472891551745> - A new version of the Open Art Browser allows discovering works of art in the new section "Types", which presents you more than 1500 expressions of art. Explore it! <http://openartbrowser.org/en/classes> Did you know? - Newest properties <https://www.wikidata.org/wiki/Special:ListProperties>: - General datatypes: date of resignation <https://www.wikidata.org/wiki/Property:P9667>, curid <https://www.wikidata.org/wiki/Property:P9675>, consequence of text <https://www.wikidata.org/wiki/Property:P9680> - External identifiers: RBF event ID <https://www.wikidata.org/wiki/Property:P9666>, cirkev.cz Catholic services ID <https://www.wikidata.org/wiki/Property:P9668>, Olympic Committee of Israel athlete ID <https://www.wikidata.org/wiki/Property:P9669>, ZKM person ID <https://www.wikidata.org/wiki/Property:P9670>, Bundesstiftung Aufarbeitung person ID <https://www.wikidata.org/wiki/Property:P9671>, Fotodok ID <https://www.wikidata.org/wiki/Property:P9672>, museumPASSmusées ID <https://www.wikidata.org/wiki/Property:P9673>, Burke Herbarium Image Collection contributor ID <https://www.wikidata.org/wiki/Property:P9674>, Vindskyddskartan.se ID <https://www.wikidata.org/wiki/Property:P9676>, Hokej.cz player ID <https://www.wikidata.org/wiki/Property:P9677>, Franciscan Center of Christian Oriental Studies ID <https://www.wikidata.org/wiki/Property:P9678>, Companies Registration Office (Ireland) Registration Number <https://www.wikidata.org/wiki/Property:P9679> - New property proposals <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Property_proposal> to review: - General datatypes: delta of <https://www.wikidata.org/wiki/Wikidata:Property_proposal/delta_of>, Astrological sign <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Astrological_sign>, announced at <https://www.wikidata.org/wiki/Wikidata:Property_proposal/announced_at>, contact point (2) <https://www.wikidata.org/wiki/Wikidata:Property_proposal/contact_point_(2)> - External identifiers: WTA-Trainer-ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/WTA-Trainer-ID>, Villo! station ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Villo!_station_ID>, LexM ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/LexM_ID>, Classical Archives composer ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Classical_Archives…>, UFC ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/UFC_ID>, Tapology ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Tapology_ID>, Bellator ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Bellator_ID>, Bauforschung Baden-Württemberg Objekt-ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Bauforschung_Baden…>, FightMatrix ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/FightMatrix_ID>, World Curling Federation Championship ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/World_Curling_Fede…>, Ethereum token address <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Ethereum_token_add…>, Legie 100 legionary ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Legie_100_legionar…>, PsycNET ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/PsycNET_ID>, Index Theologicus ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Index_Theologicus_…>, MK ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/MK_ID>, CCC in Idaho Collection ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/CCC_in_Idaho_Colle…>, Gameblog.fr game ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Gameblog.fr_game_ID>, African Film Database ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/African_Film_Datab…>, Games und Erinnerungskultur Datenbank ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Games_und_Erinneru…>, Great Ukrainian Encyclopedia Online ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Great_Ukrainian_En…>, Native-Land.ca Territory ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Native-Land.ca_Ter…>, Native-Land.ca Language ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Native-Land.ca_Lan…>, Great Encyclopedia of Cyril and Methodius ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Great_Encyclopedia…>, HockeyLive player ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/HockeyLive_player_…>, eishockey.info player ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/eishockey.info_pla…> - Query examples: - Street names in Alsatian <https://w.wiki/3Yev> (source <https://phabricator.wikimedia.org/T262922#7178793>) - What kind of places in Wales host public toilets? <https://w.wiki/3Z8o> (Source <https://twitter.com/WICI_LLGC/status/1409488011197300742>) - UK Health Ministers and their occupations on Wikidata <https://w.wiki/3Yoe> (Source <https://twitter.com/piecesofuk/status/1409081946865610756>) - Count of statements by property for theatrical plays <https://w.wiki/3YJM> (Source <https://twitter.com/Tagishsimon/status/1408382965898436610>) - Things dedicated to St. John the Baptist <https://w.wiki/3XdN> ( Source <https://twitter.com/euwikipedia/status/1407790562917367816>) Development - Mismatch Finder: We started building the foundation of the place that will store the mismatches between Wikidata and other databases/catalogs/... - Continued work on migrating the checks of regular expressions for constraints from SPARQL to a better solution to take that load off of the SPARQL endpoint (phab:T176312 <https://phabricator.wikimedia.org/T176312> ) - Made it possible to show language links from multilingual Wikisource to the other language versions of Wikisource (phab:T275958 <https://phabricator.wikimedia.org/T275958>) - Added a new constraint type to indicate that a certain Property should only be used on Lexemes with a specific language (phab:T200689 <https://phabricator.wikimedia.org/T200689>) - Fixed a weird issue with suggesters popping back up when they shouldn't (phab:T284219 <https://phabricator.wikimedia.org/T284219>) - Invalid data will not be handled better in RDF outputs (phab:T285131 <https://phabricator.wikimedia.org/T285131>) - Working on lowering the rate limit at which a misbehaving bot can waste new Item IDs to further reduce the percentage of skipped Item IDs ( phab:T284538 <https://phabricator.wikimedia.org/T284538>) - Working on not suggesting real Item IDs in the API sandbox to avoid accidental edits by people who think it is not making real edits ( phab:T219215 <https://phabricator.wikimedia.org/T219215>) - Working on reducing the time it takes between entering a value in a new statement and being able to save the statement (phab:T281669 <https://phabricator.wikimedia.org/T281669>) - Improved documentation of the usage tracking aspects in API help pages. Usage tracking is an internal mechanism to track which article on Wikipedia etc uses which data from an Item on Wikidata. (phab:T283040 <https://phabricator.wikimedia.org/T283040>) - Language codes for monolingual strings "gsw-fr", "ykg", "wya", "osa-latn" were made available: Alsatian, Tundra Yukaghir, Wendat, Osage ( phab:T262922 <https://phabricator.wikimedia.org/T262922>, phab:T252198 <https://phabricator.wikimedia.org/T252198>, phab:T283364 <https://phabricator.wikimedia.org/T283364>, phab:T265297 <https://phabricator.wikimedia.org/T265297>) - The English name for language code "crh" and the Swedish name for "fa" were corrected (phab:T240350 <https://phabricator.wikimedia.org/T240350>, phab:T281702 <https://phabricator.wikimedia.org/T281702>) - Lexeme language codes ha-arab, sux-latn, sux-xsux, gsg, tlh-piqd, tlh-latn, bfi, pwn, enm were added. That is Hausa in Arabic script, Sumerian in cuneiform and Latin-script, German Sign Language, Klingon in pIqaD and Latin script, British Sign Language, Paiwan and Middle English. ( phab:T282512 <https://phabricator.wikimedia.org/T282512>, phab:T279557 <https://phabricator.wikimedia.org/T279557>) - It was determined that language codes can be activated for Wikidata while being blocked for use on Incubator (phab:T273705 <https://phabricator.wikimedia.org/T273705>), this to avoid projects such as a "British English Wikipedia" - Language code "es-419" for Latin American Spanish has been available for labels and descriptions for quite some time (phab:T230786 <https://phabricator.wikimedia.org/T230786>) - A possibly confusing Russian mis-translation of the name of the language code for "multiple languages" (mul) is being reviewed ( phab:T245927 <https://phabricator.wikimedia.org/T245927>) - "en-simple: <https://simple.wikipedia.org/wiki/>" can be used instead of "simple: <https://simple.wikipedia.org/wiki/>" to link to Simple Wikipedia. Query Services outputs "en-simple", not "simple" for sitelinks to Simple Wikipedia (phab:T283149 <https://phabricator.wikimedia.org/T283149>). - There was some discussion about the creation of a language code "en-in" for monolingual strings, but "en-in" as interface language seems to be preferred (phab:T212313 <https://phabricator.wikimedia.org/T212313>) You can see all open tickets related to Wikidata here <https://phabricator.wikimedia.org/maniphest/query/4RotIcw5oINo/#R>. If you want to help, you can also have a look at the tasks needing a volunteer <https://phabricator.wikimedia.org/project/board/71/query/zfiRgTnZF7zu/?filt…>. Monthly Tasks - Add labels, in your own language(s), for the new properties listed above. - Comment on property proposals: all open proposals <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Overview> - Contribute to a Showcase item <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Showcase_items> . - Help translate <https://www.wikidata.org/wiki/Special:LanguageStats> or proofread the interface and documentation pages, in your own language! - Help merge identical items <https://www.wikidata.org/wiki/User:Pasleim/projectmerge> across Wikimedia projects. - Help write the next summary! <https://www.wikidata.org/wiki/Wikidata:Status_updates/Next> -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 https://wikimedia.de Keep up to date! Current news and exciting stories about Wikimedia, Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now <https://www.wikimedia.de/newsletter/>. Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us to achieve our vision! https://spenden.wikimedia.de Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

[CfP] Wikidata Workshop 2021: Second Call for Papers
by Lucie Kaffee 28 Jun '21

28 Jun '21

Please find the second call for papers for the Wikidata workshop below. I am looking forward to reading your work related to Wikidata and seeing some of you there! The Second Wikidata Workshop Co-located with the 20th International Conference on Semantic Web (ISWC 2021). Date: October 24 or 25, 2021 The workshop will be held online, afternoon European time. Website: https://wikidataworkshop.github.io/2021/ == Important dates == Papers due: Friday, July 30, 2021 Notification of accepted papers: Friday, September 24, 2021 Camera-ready papers due: Monday, October 4, 2021 Workshop date: October 24/25, 2021 == Overview == Wikidata is an openly available knowledge base, hosted by the Wikimedia Foundation. It can be accessed and edited by both humans and machines and acts as a common structured-data repository for several Wikimedia projects, including Wikipedia, Wiktionary, and Wikisource. It is used in a variety of applications by researchers and practitioners alike. In recent years, we have seen an increase in the number of publications around Wikidata. While there are several dedicated venues for the broader Wikidata community to meet, none of them focuses on publishing original, peer-reviewed research. This workshop fills this gap - we hope to provide a forum to build this fledgling scientific community and promote novel work and resources that support it. The workshop seeks original contributions that address the opportunities and challenges of creating, contributing to, and using a global, collaborative, open-domain, multilingual knowledge graph such as Wikidata. We encourage a range of submissions, including novel research, opinion pieces, and descriptions of systems and resources, which are naturally linked to Wikidata and its ecosystem or enabled by it. What we’re less interested in are works that use Wikidata alongside or in lieu of other resources to carry out some computational task - unless the work feeds back into the Wikidata ecosystem, for instance by improving or commenting on some Wikidata aspect, or suggesting new design features, tools, and practices. We also encourage submissions on the topic of Abstract Wikipedia, particularly around collaborative code management, natural language generation by a community, the abstract representation of knowledge, and the interaction between Abstract Wikipedia and Wikidata on the one, and Abstract Wikipedia and the language Wikipedias on the other side. We welcome interdisciplinary work, as well as interesting applications that shed light on the benefits of Wikidata and discuss areas of improvement. The workshop is planned as an interactive half-day event, in which most of the time will be dedicated to discussions and exchange rather than oral presentations. For this reason, all accepted papers will be presented in short talks and accompanied by a poster. All works will be presented online. == Topics == Topics of submissions include, but are not limited to: - Data quality and vandalism detection in Wikidata - Referencing in Wikidata - Anomaly, bias, or novelty detection in Wikidata - Algorithms for aligning Wikidata with other knowledge graphs - The Semantic Web and Wikidata - Community interaction in Wikidata - Multilingual aspects in Wikidata - Machine learning approaches to improve data quality in Wikidata - Tools, bots, and datasets for improving or evaluating Wikidata - Participation, diversity, and inclusivity aspects in the Wikidata ecosystem - Human-bot interaction - Managing knowledge evolution in Wikidata - Abstract Wikipedia == Submission guidelines == We welcome the following types of contributions. - Full research paper: Novel research contributions (7-12 pages) - Short research paper: Novel research contributions of smaller scope than full papers (3-6 pages) - Position paper: Well-argued ideas and opinion pieces, not yet in the scope of a research contribution (6-8 pages) - Resource paper: New dataset or other resources directly relevant to Wikidata, including the publication of that resource (8-12 pages) - Demo paper: New system critically enabled by Wikidata (6-8 pages) Submissions must be as PDF or HTML, formatted in the style of the Springer Publications format for Lecture Notes in Computer Science (LNCS). For details on the LNCS style, see Springer’s Author Instructions. The papers will be peer-reviewed by at least three researchers. Accepted papers will be published as open access papers on CEUR (we will only publish to CEUR if the authors agree to have their papers published). Papers have to be submitted through easychair: https://easychair.org/conferences/?conf=wikidata21 == Proceedings == The complete set of papers will be published with the CEUR Workshop Proceedings (CEUR-WS.org). == Organizing committee == Lucie-Aimée Kaffee, University of Southampton, lucie.kaffee[[(a)]]gmail.com Simon Razniewski, Max Planck Institute for Informatics, srazniew[[@]] mpi-inf.mpg.de Aidan Hogan, University of Chile, ahogan[[(a)]]dcc.uchile.cl == Programme committee == Miriam Redi, Wikimedia Foundation John Samuel, CPE Lyon Dennis Diefenbach, University Jean Monet Lydia Pintscher, Wikimedia Deutschland Edgar Meij, Bloomberg L.P. Thomas Pellissier Tanon, Lexistems Hiba Arnaout, MPI for Informatics Fabian Suchanek, Télécom ParisTech Filip Ilievski, ISI Marco Ponza, Bloomberg L.P. Heiko Paulheim, University of Mannheim Cristina Sarasua, University of Zurich Pavlos Vougiouklis, Huawei Technologies, Edinburgh Finn Årup Nielsen, Technical University of Denmark Andrew D. Gordon, Microsoft Research & University of Edinburgh -- Lucie-Aimée Kaffee

1 0

CfP ISWC 2021 - Call for Posters, Demos and Lightning Talks *one week left*
by International Semantic Web Conference 28 Jun '21

28 Jun '21

20th International Semantic Web Conference (ISWC 2021) Virtual, October 24-28, 2021 https://iswc2021.semanticweb.org Call for Posters, Demos, and Lightning Talks ******************************************* The ISWC 2021 Posters and Demos Track complements the paper tracks of the conference by offering an opportunity to present late-breaking research results, on-going research or resource projects, and speculative or innovative work in progress. The Lightning Talks track will open a few weeks before ISWC 2021 takes place. We invite submissions relevant to the area of the Semantic Web and which address, but are not limited to, the topics of the Research Track, the Resources Track, the In-Use Track, and the Industry Track. We also invite Visionary ideas, Position statements, Negative results, Outrageous ideas, Novel but thoughtful speculation, and Humorous thoughts (or similar). Track details: https://iswc2021.semanticweb.org/posters-demos Track chairs: - Catia Pesquita (Universidade de Lisboa, Portugal) - Oshani Seneviratne (Rensselaer Polytechnic Institute, NY, USA) Contact: iswc2021-poster-demo(a)easychair.org ***** Important Dates ***** - Papers due: 5 July 2021 - Notifications: 28 July 2021 - Camera-ready paper due: 1 September 2021 *** All deadlines are AoE (Anywhere on Earth) *** Submission link for all papers: https://easychair.org/conferences/?conf=iswc2021 Follow ISWC on social media: - Twitter: @iswc_conf #iswc_conf (https://twitter.com/iswc_conf) - LinkedIn: https://www.linkedin.com/groups/13612370 - Facebook: https://www.facebook.com/ISWConf The ISWC 2021 Organising Team https://iswc2021.semanticweb.org/organizing-committee

1 0

Bodh: a new tool for for lexicographical data
by Bodhisattwa Mandal 27 Jun '21

27 Jun '21

Hello all, We are happy to announce that a new tool <https://bodh.toolforge.org/>, named Bodh, has been developed by Jayprakash, <User:Jay (CIS-A2K)> as a CIS-A2K assignment, to add or modify statements for lexemes, senses and forms. This tool presents lexicographical data in tabular format generated from SPARQL queries or from manual lists. Users can switch whether to work on lexeme proper, sense or form and add or modify statements there. The idea of this tool was inspired by the one and only Magnus Manske's <https://www.wikidata.org/wiki/Q13520818> Tabernacle <https://tabernacle.toolforge.org/#/> which helps editors to add or modify statements, labels, descriptions and aliases for Wikidata's entity data. The tool is going to be documented here <https://www.wikidata.org/wiki/Wikidata:Bodh>. Users of this tool can request for more features or report for bugs using this phabricator project profile <https://phabricator.wikimedia.org/project/profile/5166/>. Happy editing! Regards, Bodhisattwa Wikidata Co-ordinator, CIS-A2K

2 2

Re: [Wikibase] Re: SPARQL and January 1 dates
by Olaf Simons 24 Jun '21

24 Jun '21

Dear all, thank you, Dragan for the answer, yet this is nothing I can explain to "normal users". They use the Query Service with the recommended input help and they do get inexplicable January 1st dates (which, if the are not suspicious, they will accept as the new knowledge). What would speak against a a Query helper that gives data pretty much as we have entered them? Best, Olaf > Dragan Espenschied <dragan.espenschied(a)rhizome.org> hat am 23.06.2021 19:53 geschrieben: > > > Hello Olaf, > > The trick is to query for the property value node instead of the > proterty direct value. > > Example in ArtBase: > > https://tinyurl.com/yft9u5kg > On Wikidata, you can replace > "rt:" --> "wdt:" > "rp:" --> "p:" > "rpsv:" --> "psv:" > > With the "property direct" ("rt") you query for just the value of the > property. > > With "property" ("rp") you query for the node that holds the value, and > more meta-information about the value. > > The node contains the "node value" ("rpsv"), and that value has a > precision value ("wikibase:timePrecision"). 9 is year level, 10 is > month level, 11 is day level. > > Hope that helps! :) > > > > select ?artwork ?inception ?date_precision WHERE { > ?artwork rt:P3 r:Q5 . > ?artwork rt:P26 ?inception . > > ?artwork rp:P26 ?inception_node . > ?inception_node rpsv:P26 ?inception_value . > ?inception_value wikibase:timePrecision ?date_precision . > } > LIMIT 100 > > > > > > > -- > Dragan Espenschied > Preservation Director > Rhizome at the New Museum > > On Mi, Jun 23 2021 at 11:50:12 +0200, Olaf Simons > <olaf.simons(a)pierre-marteau.com> wrote: > > Dear All, > > > > I wonder whether there is a simple way to retrieve dates with the > > precision in they have been put into a wikibase. > > > > Using SPARQL I get all years such as "1749" as "1 January 1749" > > statements, no matter whether the person is born that day or not. > > Should I run different searches? > > > > Best, > > Olaf > > > > > > > > > > > > Dr. Olaf Simons > > Forschungszentrum Gotha der Universität Erfurt > > Am Schlossberg 2 > > 99867 Gotha > > Büro: +49-361-737-1722 > > Mobil: +49-179-5196880 > > Privat: Hauptmarkt 17b/ 99867 Gotha > > _______________________________________________ > > Wikibaseug mailing list -- wikibaseug(a)lists.wikimedia.org > > To unsubscribe send an email to wikibaseug-leave(a)lists.wikimedia.org > > _______________________________________________ > Wikibaseug mailing list -- wikibaseug(a)lists.wikimedia.org > To unsubscribe send an email to wikibaseug-leave(a)lists.wikimedia.org Dr. Olaf Simons Forschungszentrum Gotha der Universität Erfurt Am Schlossberg 2 99867 Gotha Büro: +49-361-737-1722 Mobil: +49-179-5196880 Privat: Hauptmarkt 17b/ 99867 Gotha

2 2

[Virtual OM-2021] 2nd CFP: 16th workshop on Ontology Matching collocated with ISWC
by Pavel Shvaiko 23 Jun '21

23 Jun '21

------------------------------------------------------------------------------ SECOND CALL FOR CONTRIBUTIONS THE SUBMISSION DEADLINE IS ON AUGUST 9TH, 2021 ------------------------------------------------------------------------------ The Sixteenth International Workshop on ONTOLOGY MATCHING (OM-2021) http://om2021.ontologymatching.org/ October 25th, 2021, International Semantic Web Conference (ISWC) Workshop Program, VIRTUAL CONFERENCE BRIEF DESCRIPTION AND OBJECTIVES Ontology matching is a key interoperability enabler for the Semantic Web, as well as a useful technique in some classical data integration tasks dealing with the semantic heterogeneity problem. It takes ontologies as input and determines as output an alignment, that is, a set of correspondences between the semantically related entities of those ontologies. These correspondences can be used for various tasks, such as ontology merging, data interlinking, query answering or navigation over knowledge graphs. Thus, matching ontologies enables the knowledge and data expressed with the matched ontologies to interoperate. The workshop has three goals: 1. To bring together leaders from academia, industry and user institutions to assess how academic advances are addressing real-world requirements. The workshop will strive to improve academic awareness of industrial and final user needs, and therefore, direct research towards those needs. Simultaneously, the workshop will serve to inform industry and user representatives about existing research efforts that may meet their requirements. The workshop will also investigate how the ontology matching technology is going to evolve, especially with respect to data interlinking, knowledge graph and web table matching tasks. 2. To conduct an extensive and rigorous evaluation of ontology matching and instance matching (link discovery) approaches through the OAEI (Ontology Alignment Evaluation Initiative) 2021 campaign: http://oaei.ontologymatching.org/2021/ 3. To examine similarities and differences from other, old, new and emerging, techniques and usages, such as web table matching or knowledge embeddings. This year, in sync with the main conference, we encourage submissions specifically devoted to: (i) datasets, benchmarks and replication studies, services, software, methodologies, protocols and measures (not necessarily related to OAEI), and (ii) application of the matching technology in real-life scenarios and assessment of its usefulness to the final users. TOPICS of interest include but are not limited to: Business and use cases for matching (e.g., big, open, closed data); Requirements to matching from specific application scenarios (e.g., public sector, homeland security); Application of matching techniques in real-world scenarios (e.g., in cloud, with mobile apps); Formal foundations and frameworks for matching; Novel matching methods, including link prediction, ontology-based access; Matching and knowledge graphs; Matching and deep learning; Matching and embeddings; Matching and big data; Matching and linked data; Instance matching, data interlinking and relations between them; Privacy-aware matching; Process model matching; Large-scale and efficient matching techniques; Matcher selection, combination and tuning; User involvement (including both technical and organizational aspects); Explanations in matching; Social and collaborative matching; Uncertainty in matching; Expressive alignments; Reasoning with alignments; Alignment coherence and debugging; Alignment management; Matching for traditional applications (e.g., data science); Matching for emerging applications (e.g., web tables, knowledge graphs). SUBMISSIONS Contributions to the workshop can be made in terms of technical papers and posters/statements of interest addressing different issues of ontology matching as well as participating in the OAEI 2021 campaign. Long technical papers should be of max. 12 pages. Short technical papers should be of max. 5 pages. Posters/statements of interest should not exceed 2 pages. All contributions have to be prepared using the LNCS Style: http://www.springer.com/computer/lncs?SGWID=0-164-6-793341-0 and should be submitted in PDF format (no later than August 9th, 2021) through the workshop submission site at: https://www.easychair.org/conferences/?conf=om2021 Contributors to the OAEI 2021 campaign have to follow the campaign conditions and schedule at http://oaei.ontologymatching.org/2021/. DATES FOR TECHNICAL PAPERS AND POSTERS: August 9th, 2021: Deadline for the submission of papers. September 6th, 2021: Deadline for the notification of acceptance/rejection. September 20th, 2021: Workshop camera ready copy submission. October 25th, 2021: OM-2021, Virtual Conference. Contributions will be refereed by the Program Committee. Accepted papers will be published in the workshop proceedings as a volume of CEUR-WS as well as indexed on DBLP. ORGANIZING COMMITTEE 1. Pavel Shvaiko (main contact) Trentino Digitale, Italy 2. Jérôme Euzenat INRIA & Univ. Grenoble Alpes, France 3. Ernesto Jiménez-Ruiz City, University of London, UK & SIRIUS, University of Oslo, Norway 4. Oktie Hassanzadeh IBM Research, USA 5. Cássia Trojahn IRIT, France PROGRAM COMMITTEE (to be completed): Alsayed Algergawy, Jena University, Germany Manuel Atencia, INRIA & Univ. Grenoble Alpes, France Zohra Bellahsene, LIRMM, France Jiaoyan Chen, University of Oxford, UK Valerie Cross, Miami University, USA Jérôme David, University Grenoble Alpes & INRIA, France Gayo Diallo, University of Bordeaux, France Daniel Faria, Instituto Gulbenkian de Ciéncia, Portugal Alfio Ferrara, University of Milan, Italy Marko Gulic, University of Rijeka, Croatia Wei Hu, Nanjing University, China Ryutaro Ichise, National Institute of Informatics, Japan Antoine Isaac, Vrije Universiteit Amsterdam & Europeana, Netherlands Naouel Karam, Fraunhofer, Germany Prodromos Kolyvakis, EPFL, Switzerland Patrick Lambrix, Linköpings Universitet, Sweden Oliver Lehmberg, University of Mannheim, Germany Fiona McNeill, Heriot Watt University, UK Peter Mork, MITRE, USA Axel Ngonga, University of Paderborn, Germany George Papadakis, University of Athens, Greece Catia Pesquita, University of Lisbon, Portugal Henry Rosales-Méndez, University of Chile, Chile Kavitha Srinivas, IBM, USA Pedro Szekely, University of Southern California, USA Valentina Tamma, University of Liverpool, UK Ludger van Elst, DFKI, Germany Xingsi Xue, Fujian University of Technology, China Ondrej Zamazal, Prague University of Economics, Czech Republic ------------------------------------------------------- More about ontology matching: http://www.ontologymatching.org/ http://book.ontologymatching.org/ ------------------------------------------------------- Best Regards, Pavel ------------------------------------------------------- Pavel Shvaiko, PhD Trentino Digitale, Italy http://www.ontologymatching.org/ https://www.trentinodigitale.it/ http://www.dit.unitn.it/~pavel -- Cap. Soc. Euro 6.433.680,00 - REG. IMP. / C.F. / P.IVA 00990320228 E-mail: tndigit(a)tndigit.it <mailto:tndigit@tndigit.it> - www.trentinodigitale.it <http://www.trentinodigitale.it> Società soggetta ad attività di direzione e coordinamento da parte della Provincia Autonoma di Trento - C.Fisc. 00337460224. Questo messaggio è indirizzato esclusivamente ai destinatari in intestazione, può contenere informazioni protette e riservate ai sensi della normativa vigente e ne è vietato qualsiasi impiego diverso da quello per cui è stato inviato. Se lo avete ricevuto per errore siete pregati di eliminarlo in ogni sua parte e di avvisare il mittente

1 0

SPARQL and January 1 dates
by Olaf Simons 23 Jun '21

23 Jun '21

Dear All, I wonder whether there is a simple way to retrieve dates with the precision in they have been put into a wikibase. Using SPARQL I get all years such as "1749" as "1 January 1749" statements, no matter whether the person is born that day or not. Should I run different searches? Best, Olaf Dr. Olaf Simons Forschungszentrum Gotha der Universität Erfurt Am Schlossberg 2 99867 Gotha Büro: +49-361-737-1722 Mobil: +49-179-5196880 Privat: Hauptmarkt 17b/ 99867 Gotha

1 0

WDQS Data Reloads Complete
by Ryan Kemper 23 Jun '21

23 Jun '21

Hi all, We recently reloaded our Wikidata journal files (the database, basically) across our whole wdqs fleet, which should resolve a number of inconsistency issues. The ticket for the data reload itself is https://phabricator.wikimedia.org/T267927. The reload resolves the following tickets: https://phabricator.wikimedia.org/T274982 https://phabricator.wikimedia.org/T266211 https://phabricator.wikimedia.org/T255657 https://phabricator.wikimedia.org/T268408 https://phabricator.wikimedia.org/T272120 https://phabricator.wikimedia.org/T273937

1 0

We are working on a tool to perform checks on mismatching data between Wikidata and external databases
by Mohammed Sadat Abdulai 22 Jun '21

22 Jun '21

Hello everyone, This is to announce that we have finalized the concepts and started development for a tool to help editors work on mismatches between Wikidata's data and other databases/websites. Why are we doing this? Wikidata is becoming too big for the editors to monitor individual data points. Additionally, keeping Wikidata’s data in sync with the external database (meant in the broadest way possible) requires a lot of effort and existing workflows are haphazard and one-off. Who are we doing this for? The target audience of this tool are tech-savvy editors whose primary goal is finding mismatches and data quality improvement. They are: - Dedicated data quality workers who specifically seeks out lists of issues in an area of their interest to fix a number of mistakes - Heavily affected by the data quality - Experienced using bots and mass editing gadgets What is the solution? We will build a system that will have a store for mismatches. Different people and organizations can load mismatches they found into this system. Various tools can then get mismatches from the system to help editors resolve them. Sources for the mismatches can be many. We will start with mismatches that we found as part of previous work to find references for statements lacking references (aka Reference Treasure Hunt <https://www.wikidata.org/wiki/Wikidata:Automated_finding_references_input>). In the future, categories on Wikipedia that indicate a mismatch between the local value on that Wikipedia and the corresponding value on Wikidata could also be possible. Various research organizations as well as large data re-users could also contribute mismatches they found in their internal processes when doing quality assurance on Wikidata’s data. We hope that this tool will help to make it easier for editors to find and fix the mismatches between Wikidata’s data and other databases. Feel free to ask questions or give us feedback at the discussion page: Wikidata_talk:Mismatch_Finder <https://www.wikidata.org/wiki/Wikidata_talk:Mismatch_Finder> Cheers, -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 https://wikimedia.de Keep up to date! Current news and exciting stories about Wikimedia, Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now <https://www.wikimedia.de/newsletter/>. Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us to achieve our vision! https://spenden.wikimedia.de Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Wikidata June 2021