Wikidata January 2018

wikidata@lists.wikimedia.org

37 participants
27 discussions

BREAKING CHANGE: wbcheckconstraints status parameter
by Lucas Werkmeister 29 Jan '18

29 Jan '18

Hi all! This is an announcement for a breaking change to the default value of a parameter of the WikibaseQualityConstraints constraint checking API, to go live on 26 February 2018. It potentially affects clients that use the *wbcheckconstraints* API action. (We are not aware of any such clients apart from the *checkConstraints* gadget, which is not affected.) Recently, we added a status parameter to the *wbcheckconstraints* API action, with the intention that API users can declare ahead of time which results they’re actually interested in, so that other results don’t need to be sent to them: specifically, for most items the vast majority of results indicate compliance with a constraint, which we expect most users aren’t interested in. *On 26 February 2018, we will change the default value of the status parameter to violation|warning|bad-parameters.* We assume that most users of the API will only be interested in results that actually indicate problems, and this should significantly reduce the size of API responses. Users who wish to receive all results, regardless of status, should specify status=* in their API requests. Our motivation for this change is that we want to enable caching of constraint check results, but don’t want to bloat the cache with tons of compliance and not-in-scope results that we don’t even show in the gadget. With the status parameter, we can store only problematic results in the cache, while still guaranteeing that the response we send is complete, since the request indicated that it only needs these results anyways. This also means that when we enable caching (see phabricator:T184812 <https://phabricator.wikimedia.org/T184812>), only requests with status=violation|warning|bad-parameters will benefit from it. Please let us know if you have any questions. -- Lucas Relevant tickets: - phabricator:T183927 <https://phabricator.wikimedia.org/T183927> - phabricator:T184812 <https://phabricator.wikimedia.org/T184812> - phabricator:T184937 <https://phabricator.wikimedia.org/T184937> -- Lucas Werkmeister Software Developer (Intern) Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 https://wikimedia.de Imagine a world, in which every single human being can freely share in the sum of all knowledge. That‘s our commitment. 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

weekly summary #296
by Lydia Pintscher 23 Jan '18

23 Jan '18

Hey folks :) Here is your summary of what's been happening around Wikidata over the past week. Discussions - Closed request for adminship: Mahir256 <https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Administrat…> (as successful) Events <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Events>/ Press/Blogs <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Press_coverage> - Getting data from Wikidata into WordPress custom taxonomy <https://blogs.pjjk.net/phil/getting-data-wikidata-wordpress-custom-taxonomy/> - PIDapalooza <https://pidapalooza.org/> - Girona, 23-24 January,with a session on PIDs in Wikidata <http://sched.co/Cwmd> by Andy Mabbett - The EuropeanaTech Call for Proposals is open till February 7 <https://easychair.org/cfp/europeanatech2018>. Themes are Data, Discovery, Delivery. The conference will take place in Rotterdam, NL, May 15-16, 2018. - Call for papers for Celtic Knot conference is open <https://wikimedia.org.uk/wiki/Cynhadledd_Celtic_Knot_2018> Other Noteworthy Stuff - Nominations for the Steward elections are open <https://meta.wikimedia.org/wiki/Stewards/Elections_2018> - Grant proposal for GlobalFactSync <https://meta.wikimedia.org/wiki/Grants:Project/DBpedia/GlobalFactSync> - repology <https://repology.org> is a nice new project about software packages with the help of Wikidata. They have a list of potentially outdated packages on Wikidata <https://repology.org/metapackages/?inrepo=wikidata&outdated=1> that might need updating or fixing. - Painters <https://tools.wmflabs.org/mix-n-match/painters.php> gives you a list of paintings that don't have a creator statement but "painting by" in the description - Big City Lights: where are the cities whose items are most used across the Wikimedia projects? <https://www.wikidata.org/wiki/Wikidata:Wikidata_Concepts_Monitor/WDCM_Journ…> Did you know? - Newest properties <https://www.wikidata.org/wiki/Special:ListProperties>: - General datatypes: Commons compatible image available at URL <https://www.wikidata.org/wiki/Property:P4765>, is a hydrated form of <https://www.wikidata.org/wiki/Property:P4770>, biological phase <https://www.wikidata.org/wiki/Property:P4774>, lot number <https://www.wikidata.org/wiki/Property:P4775>, MAC Address Block Large ID <https://www.wikidata.org/wiki/Property:P4776>, has boundary <https://www.wikidata.org/wiki/Property:P4777> - External identifiers: SRCBB coach ID <https://www.wikidata.org/wiki/Property:P4751>, Manus Online ID <https://www.wikidata.org/wiki/Property:P4752>, Ecocrop ID <https://www.wikidata.org/wiki/Property:P4753>, Harvard botanical journal ID <https://www.wikidata.org/wiki/Property:P4754>, UK railway station code <https://www.wikidata.org/wiki/Property:P4755>, V Live channel ID <https://www.wikidata.org/wiki/Property:P4756>, Songwriters Hall of Fame ID <https://www.wikidata.org/wiki/Property:P4757>, MONA ID <https://www.wikidata.org/wiki/Property:P4758>, Luminous-Lint ID <https://www.wikidata.org/wiki/Property:P4759>, LTI Korea Library ID <https://www.wikidata.org/wiki/Property:P4760>, Images d'Art artwork ID <https://www.wikidata.org/wiki/Property:P4761>, Common Database on Designated Areas ID <https://www.wikidata.org/wiki/Property:P4762>, crates.io ID <https://www.wikidata.org/wiki/Property:P4763>, Arcade artwork ID <https://www.wikidata.org/wiki/Property:P4764>, Australian honours ID <https://www.wikidata.org/wiki/Property:P4766>, cinematografo company ID <https://www.wikidata.org/wiki/Property:P4767>, cinematografo name ID <https://www.wikidata.org/wiki/Property:P4768>, GameRankings game ID <https://www.wikidata.org/wiki/Property:P4769>, compArt institution ID <https://www.wikidata.org/wiki/Property:P4771>, compArt person ID <https://www.wikidata.org/wiki/Property:P4772>, MobyGames company ID <https://www.wikidata.org/wiki/Property:P4773>, USA Rugby player ID <https://www.wikidata.org/wiki/Property:P4778>, MYmovies actor ID <https://www.wikidata.org/wiki/Property:P4779>, MYmovies movie ID <https://www.wikidata.org/wiki/Property:P4780>, MYmovies director ID <https://www.wikidata.org/wiki/Property:P4781>, Movieplayer characters ID <https://www.wikidata.org/wiki/Property:P4782>, Movieplayer film ID <https://www.wikidata.org/wiki/Property:P4783>, Movieplayer TV-series ID <https://www.wikidata.org/wiki/Property:P4784>, MYmovies name ID <https://www.wikidata.org/wiki/Property:P4785> - Query examples: - Map of nuclear tests <https://query.wikidata.org/#%23defaultView%3AMap%0Aselect%20%3Fbooks%20%3Fb…> (source <https://twitter.com/SciHiBlog/status/953009741680214018>) - Languages with more than one writing system <https://query.wikidata.org/#%23%20languages%20with%20more%20than%20one%20wr…> (source <https://twitter.com/WikidataFacts/status/953959895535161344>) - Subclasses of malware <https://query.wikidata.org/#%23defaultView%3AGraph%0APREFIX%20gas%3A%20%3Ch…> (source <https://twitter.com/WikiDigi/status/954058770862215169>) - Male actors who starred in a trilogy of movies when they were in their 20s and then no fewer than 40 years later played the same character again <https://query.wikidata.org/#%23%20male%20actors%20who%20starred%20in%20a%20…> (source <https://twitter.com/WikidataFacts/status/954134597096427520> - see whole thread for more) - Bands from the UK whose member's average age is at least 70 <https://query.wikidata.org/#SELECT%20%3Fband%20%3FbandLabel%20%28AVG%28%3Fa…> (source <https://twitter.com/korenchkin/status/955410384323792898>) - Disney movie narrative locations <https://query.wikidata.org/#%23Disney%20animated%20movies%20and%20their%20n…> (source <https://twitter.com/csl_/status/955506614085316608>) Development - Worked on persistent editing of grammatical features of a lexeme’s form (phab:T173742 <https://phabricator.wikimedia.org/T173742>) - Made diffs for statements, grammatical features and representations of a form work (phab:T182424 <https://phabricator.wikimedia.org/T182424>) - Turned off access to lexicographical data from the clients for now ( phab:T178904 <https://phabricator.wikimedia.org/T178904>) - Started logging warning on pages that use too many items (phab:T184319 <https://phabricator.wikimedia.org/T184319>) - Added support for relation <https://www.wikidata.org/wiki/Property:P2309> instance or subclass of <https://www.wikidata.org/wiki/Q30208840> in the constraint checks ( phab:T169858 <https://phabricator.wikimedia.org/T169858>) - Now also checking single value <https://www.wikidata.org/wiki/Q19474404> and multi value <https://www.wikidata.org/wiki/Q21510857> constraints on qualifiers and references (phab:T175566 <https://phabricator.wikimedia.org/T175566>) - Now also checking difference within range <https://www.wikidata.org/wiki/Q21510854> constraints on qualifiers and references (phab:T175565 <https://phabricator.wikimedia.org/T175565>) - Fixed a bug with duplicate items in “distinct values” violation message in the constraint checks gadget (phab:T184705 <https://phabricator.wikimedia.org/T184705>) You can see all open tickets related to Wikidata here <https://phabricator.wikimedia.org/maniphest/query/4RotIcw5oINo/#R>. 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> - Suggested and open tasks <https://www.wikidata.org/wiki/Wikidata:Contribute/Suggested_and_open_tasks> ! - 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> Anything to add? Please share! :) Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

Call for papers is OPEN
by Jason Evans 22 Jan '18

22 Jan '18

Hello everyone! I am happy to announce that the call for papers for Celtic Knot 2018 <https://wikimedia.org.uk/wiki/Cynhadledd_Celtic_Knot_2018> is now open. The deadline for proposals <https://wikimedia.org.uk/wiki/Celtic_Knot_Conference_2018/Call_for_papers> will be March 31st. Celtic Knot 2018 aims to continue where last years conference left off. Speakers are encouraged to share their success stories and the challenges they have faced whilst helping to develop a small or minority language Wicipedia. So please submit your papers, and share this message in your own circles. Information on registration for the conference will be available soon, but if you have any questions in the meantime please get in touch. Mae'r wefan Celtic Knot hefyd ar gael yn y Gymraeg <https://wikimedia.org.uk/wiki/Cynhadledd_Celtic_Knot_2018> (The Celtic Knot website is also available in Welsh <https://wikimedia.org.uk/wiki/Cynhadledd_Celtic_Knot_2018>) Many thanks Jason -- Logo LlGC - NLW Logo Jason Evans WIKIMEDIWR CENEDLAETHOL| NATIONAL WIKIMEDIAN MYNEDIAD DIGIDOL| DIGITAL ACCESS Llyfrgell Genedlaethol Cymru | The National Library of Wales Aberystwyth, Ceredigion SY23 3BU 01970 632405| jje(a)llgc.org.uk <mailto:jje@llgc.org.uk> | www.llgc.org.uk <http://www.llgc.org.uk/> Twitter <https://twitter.com/Wici_LLGC> Twitter <https://twitter.com/Wiki_NLW> Hapus i siarad Cymraeg

1 0

Fwd: Call for Papers: EuropeanaTech 2018 Conference
by Sandra Fauconnier 19 Jan '18

19 Jan '18

Hi all! Here's a call for proposals for the EuropeanaTech conference, which will take place in Rotterdam, May 15-16, 2018. https://pro.europeana.eu/event/europeanatech-conference-2018 Some of the suggested topics are very Wikidata- and Wikimedia-related. Best! Sandra (User:Spinster) ---------- Forwarded message ---------- From: Gregory Markus <gmarkus(a)beeldengeluid.nl> Date: Thu, Jan 18, 2018 at 9:17 AM Subject: Call for Papers: EuropeanaTech 2018 Conference To: EUROPEANA-TECH(a)list.ecompass.nl Dear EuropeanaTech community EuropeanaTech is about the practical application of research concepts and the latest technologies to digital libraries. For this edition of EuropeanaTech, we concentrate on t*he three D’s: Data, Discovery and Delivery*. Intertwined are the concepts of participation, linked and big data; language and tools. Across all the subjects we are looking for the inclusion of rigorous evaluations of the outcomes. The conference will be a mix of invited speakers and successful presentations from this call. We are not expecting an academic paper but a lively presentation of work that you have been doing under the subjects below. We are as interested in the glorious failures as we are in the gorgeous successes. Submission Guidelines Please submit your proposal* by February 7*. It should contain a title, an abstract of 250 words, some key words and a two sentence evaluation of its practical benefits or learning. The Programme Committee will evaluate all the submitted proposals and will notify you before the end of February if your proposal has been selected for presentation. *We have room for up to 15 presentations* to be given in the conference as a result of this call. The conference fee and your travelling costs will be covered if your presentation is chosen. Submissions are to be made via EasyChair: https://easychair.org/ conferences/?conf=eurtech18 List of Topics *DATA* 1. *User generated content and metadata:* from crowdsourcing of descriptive data and transcription projects to Wikidata and structured data on the Commons to how to combine institutional and user generated metadata. We are looking for what has worked, or what hasn’t and can be done better. 2. *Enhancing the results of digitisation: *various applications connect the act of digitisation with required data processes for the use of the data. What are the latest techniques, have they been applied at scale, do they work in the in the more challenging audio-visual areas? We are interested in everything from 3D capture, OCR, sound/video labelling, named entity recognition and feature detection, to machine or deep learning to help classify and categorise the digitised data. 3. *Decentralisation vs Centralisation:* We know that aggregation works as a process to bring together disparate data, standardised, normalise it and make it available to other parties, but we also know that this is labour intensive, very hierarchical, and does not distribute knowledge and expertise. On the other hand more decentralised ways of working have yet to be really proven in practice. Presentations that give the latest thinking on how we can best enable access to cultural heritage data and reduce friction costs are welcome, particularly with evaluation on the relative strengths and weaknesses. 4. *Multilingualism*: Google has more or less cracked full text translation of mainstream languages, but we are still struggling with niche languages and metadata. Presentations that evaluate the current thinking or give insights into the latest work in the area would fit well in this section of the creation and use of multilingual data in Cultural Heritage. *DISCOVERY* 1. *User Interaction: *Search is still the dominant means of gaining access to the wealth of cultural heritage data now online, but does it represent that wealth? Search is ungenerous: it withholds information, and demands a query, what are the alternatives? Papers on generous interfaces and frictionless design are sought to shed new light on how Cultural Heritage can show itself more deeply. Evaluating the benefits and weaknesses to the user in the process. 2. *Artificial Intelligence: *For this subject topics ranging from machine learning to neural network-based approaches to Cultural Heritage are welcome. This includes applications of AI from image feature recognition to natural language processing, and from building search interfaces on features/colour similarity between images and discovery to the use of human metadata and computer vision. We would also be interested in the audio and moving image equivalents. Anything dealing with the combination of metadata tags, image similarity and machine learning based on user input would be very relevant as would Artificial Intelligence technology for content curation. *DELIVERY* 1. *Digital Innovation: *The corporate culture of our memory institutions, set up to preserve and conserve our heritage and the organisation of digital innovation are not a marriage made in heaven. The Labs/Skunkworks model is increasingly seen at best as an interim stage and at worst as a dead end for organising innovation. So how should GLAMs go about organising for digital innovation? How can governments and/or funders best support digital transformation of the GLAM-sector? 2. *Evaluation techniques:* Evaluation should be part of everything we do in the publicly funded space of most of cultural heritage, but the how is struggling to gain a common language, one that we can apply so funders get a picture of the project within its broader context. Evaluation has been requested to be part of all papers submitted but the latest in techniques and agreement on a framework for the sector would constitute useful insights. 3. *Open source community:* What is the health and standing of the open source community within the cultural heritage sector? Does it thrive or is it a nice idea that is not a reality? How can projects with a limited lifespan create and sustain products for the sector at large while developing and engaging a thriving community around them? From digitisation to search engine development should there be more emphasis on the need for vibrant open source communities and more resources to realizing them? Papers on barriers and successes are requested. -- *Gregory Markus* Project Leader *Netherlands Institute for Sound and Vision* *Media Parkboulevard 1 <https://maps.google.com/?q=Media+Parkboulevard+1&entry=gmail&source=g>, 1217 WE Hilversum | Postbus 1060, 1200 BB Hilversum | * *beeldengeluid.nl* <http://www.beeldengeluid.nl/> *T* 0612350556 *Aanwezig:* - ma, di, wo, do, vr ===== This is the mailing list of the EuropeanaTech community - http://pro.europeana.eu/europeana-tech You can unsubscribe at http://list.ecompass.nl/listserv/cgi-bin/wa?SUBED1=EUROPEANA-TECH&A=1

1 0

Fwd: [Input requested] Knowledge as a Service at the Wikimedia Developer Summit 2018
by Adam Baso 18 Jan '18

18 Jan '18

Cross-post. ---------- Forwarded message ---------- From: Adam Baso <abaso(a)wikimedia.org> Date: Thu, Jan 18, 2018 at 6:38 AM Subject: [Input requested] Knowledge as a Service at the Wikimedia Developer Summit 2018 To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> Howdy Wikitechnorati, (And thank you for patience with me cross-posting if you're on other lists.) I'm writing to invite your input on the following Phabricator task ahead of next week's Wikimedia Developer Summit 2018 [1] session. Knowledge as a Service https://phabricator.wikimedia.org/T183315 The purpose [2] of the Wikimedia Developer Summit 2018 sessions is to provide guidance for Phase 2 of the Movement Strategic Direction [3] on buildout of technology capabilities. We'd really love your thoughts to help set context for our session next week, as Knowledge as a Service is a primary consideration in the Movement Strategic Direction. What is Knowledge as a Service? Its essence is about information architecture approaches and the necessary software that will ultimately allow content consumption and creation to radiate to new and different types of interfaces and devices in addition to browser-based approaches. As you review position papers from attendees [4] you'll notice that the way they (myself included) think about best solving this is through a heavy emphasis on technology that makes it easier to better structure information and its metadata for re-use, remixing, and querying. What might this mean? Does it mean we should build Wikimedia software in an API- and metadata-first manner following industry standards compatible with content structuration? Does it mean weaving our existing structured and semi-structured data technologies together? How do we build technology that can ensure successful collaboration between communities on increasingly structured and interdependent information sources? And how can we ensure the tech will bolster growth of multilingual and multimedia content creation and consumption? I've copied some of the essential material from the Movement Strategic Direction concerning Knowledge as a Service so you have it here. We would appreciate your input and hope you will subscribe to the Phabricator task to contribute and follow along as we explore this topic. https://phabricator.wikimedia.org/T183315 The following content is copied from https://meta.wikimedia.org/ wiki/Strategy/Wikimedia_movement/2017/Direction : Knowledge as a service: To serve our users, we will become a platform that serves open knowledge to the world across interfaces and communities. We will build tools for allies and partners to organize and exchange free knowledge beyond Wikimedia. Our infrastructure will enable us and others to collect and use different forms of free, trusted knowledge. ... As technology spreads through every aspect of our lives, Wikimedia's infrastructure needs to be able to communicate easily with other connected systems. ... As a platform, we need to transform our structures to support new formats, new interfaces, and new types of knowledge. We have a strategic opportunity to go further and offer this platform as a service to other institutions, beyond Wikimedia. In a world that is becoming more and more connected, building the infrastructure for knowledge gives others a vested interest in our success. It is how we ensure our place in the larger network of knowledge, and become an essential part of it. As a service to users, we need to build the platform for knowledge or, in jargon, provide knowledge as a service. ... Knowledge as a service: A platform that serves open knowledge to the world across interfaces and communities Our openness will ensure that our decisions are fair, that we are accountable to one another, and that we act in the public interest. Our systems will follow the evolution of technology. We will transform our platform to work across digital formats, devices, and interfaces. The distributed structure of our network will help us adapt to local contexts. ... We will build tools for allies and partners to organize and exchange free knowledge beyond Wikimedia. We will continue to build the infrastructure for free knowledge for our communities. We will go further by offering it as a service to others in the network of knowledge. We will continue to build the partnerships that enable us to develop knowledge we can't create ourselves. ... Our infrastructure will enable us and others to collect and use different forms of free, trusted knowledge. We will build the technical infrastructures that enable us to collect free knowledge in all forms and languages. We will use our position as a leader in the ecosystem of knowledge to advance our ideals of freedom and fairness. We will build the technical structures and the social agreements that enable us to trust the new knowledge we compile. We will focus on highly structured information to facilitate its exchange and reuse in multiple contexts. Thank you. -Adam [1] https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018 [2] https://www.mediawiki.org/wiki/Wikimedia_Developer_ Summit/2018/Purpose_and_Results [3] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_ movement/2017/Direction [4] https://wikifarm.wmflabs.org/devsummit/index.php/Session:10

1 0

[CfP] ISWC 2018 - Workshop and Tutorial Proposals
by Maribel Acosta 17 Jan '18

17 Jan '18

17th International Semantic Web Conference (ISWC 2018) Monterey, California (USA), October 8-12, 2018 This is an announcement of the ISWC 2018 call for Workshop and Tutorial proposals. The deadline for submissions is on Sunday* **January 21**, 2018* We are very much looking forward to innovative ideas from the subscribers of this list. Website: http://iswc2018.semanticweb.org Facebook: https://www.facebook.com/groups/InternationalSemanticWebConference Twitter: @iswc2018 (https://twitter.com/iswc2018) Important dates: http://iswc2018.semanticweb.org/important-dates/ In this announcement: Workshop and Tutorial proposals: ***second call*** Call for Workshop and Tutorial Proposals =============================== In addition to the regular research program, ISWC 2018 will feature a workshop and tutorial program addressing the diverse interests of its audience. We hereby invite you to submit a tutorial proposal on a topic relevant to the ISWC 2018 audience. Detailed info: http://iswc2018.semanticweb.org/call-for-tutorial-proposals/ Besides tutorials, ISWC will host a number of workshops on topics related to the general theme of the conference. The role of the workshops is to provide a context for a focused and intensive scientific exchange among researchers interested in a particular topic. As such, workshops are the primary venues for the exploration of emerging ideas as well as for the discussion of novel aspects of established research topics. We invite you to submit a proposal for workshops on a topic of interest to ISWC attendees. Detailed info: http://iswc2018.semanticweb.org/call-for-workshop-proposals/ Workshops & Tutorials Chairs * Amrapali Zaveri, Maastricht University, Maastricht, Netherlands * Elena Demidova, L3S Research Center, Leibniz Universität Hannover, Hannover, Germany Important Dates for Workshops and Tutorials ================================== Workshop & Tutorial proposals: January 21, 2018 Workshop & Tutorial proposals notifications: February 15, 2018 Workshop paper submissions due: June 1, 2018 Workshop paper notifications sent: July 13, 2018 Workshops & Tutorials: October 8-9, 2018 Conference: October 10-12, 2018 The ISWC Organising Committee (http://iswc2018.semanticweb.org/organization/)

1 0

Code level documentation / reporting for Wikidata Query Service
by Guillaume Lederrey 16 Jan '18

16 Jan '18

Hello all! We are now publishing a bunch of documentation / reports on the code behind Wikidata Query Service [1]. All this is very developer oriented, so skip the rest of this email if you just want to use the service. All the reports are generated via Maven, and reflect the current state of the master branch of the project [2]. Reports are organized by modules. Feel free to browse through them and see if you find anything interesting. A few pointers to get started (links provided to the "tools" module, the same reports are available for other modules as well): * JaCoCo code coverage [3]: line and branch unit test coverage * JDepend [4]: a few slightly obscure code metrics. Package cycles and "distance" are interesting ones. * Dependency updates [5]: which of our dependencies could be upgraded (yes, we have some work to do on that side) If you know about other interesting reports that could be added to that collection, feel free to reach out to me. And if you want to start addressing some of those issues, patches are always welcomed! Thanks for your time... Guillaume [1] https://doc.wikimedia.org/wikidata-query-rdf/parent/ [2] https://github.com/wikimedia/wikidata-query-rdf/ [3] https://doc.wikimedia.org/wikidata-query-rdf/parent/tools/jacoco/index.html [4] https://doc.wikimedia.org/wikidata-query-rdf/parent/tools/jdepend-report.ht… [5] https://doc.wikimedia.org/wikidata-query-rdf/parent/dependency-updates-repo… -- Guillaume Lederrey Operations Engineer, Discovery Wikimedia Foundation UTC+2 / CEST

2 2

weekly summary #295
by Lydia Pintscher 16 Jan '18

16 Jan '18

Hey folks :) Here is your summary of what's been happening around Wikidata over the past week. Discussions - Open request for adminship: Mahir256 <https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Administrat…> - Closed request for adminship: Jarekt <https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Administrat…> (as successful) Events <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Events>/ Press/Blogs <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Press_coverage> - Upcoming: Wikidata workshop in Vienna <https://www.wikidata.org/wiki/Wikidata:Events/Vienna/2017-02-03> - WikiJabber podcast with Andy Mabbett <https://wikijabber.org/wikijabber-0005-with-pigsonthewing> Other Noteworthy Stuff - GraFa, a new faceted browser for Wikidata is looking for feedback. <https://lists.wikimedia.org/pipermail/wikidata/2018-January/011721.html> - Analysis: How much are items about scientific articles, genes and chemical entities used on the Wikimedia projects? <https://www.wikidata.org/wiki/Wikidata:Wikidata_Concepts_Monitor/WDCM_Journ…> - New catalogs in Mix'n'match - for example Nobel Prize People Nomination <https://tools.wmflabs.org/mix-n-match/#/catalog/864> (More than 600 properties now have a corresponding catalog in Mix'n'match. <https://query.wikidata.org/#SELECT%20DISTINCT%20%3Fq%20%3FqLabel%20%7B%20%3…> ) - Next round of Projects Grants <https://meta.wikimedia.org/wiki/Grants:Project> is open for applications until the end of January (see also this blog post <https://blog.wikimedia.org/2018/01/08/inspire-new-readers-campaign/>) Did you know? - Newest properties <https://www.wikidata.org/wiki/Special:ListProperties>: National Historic Ships certificate no. <https://www.wikidata.org/wiki/Property:P4750>, Dictionnaire des auteurs luxembourgeois ID <https://www.wikidata.org/wiki/Property:P4749>, Line Music album ID <https://www.wikidata.org/wiki/Property:P4748>, Line Music artist ID <https://www.wikidata.org/wiki/Property:P4747>, Elhuyar ZTH ID <https://www.wikidata.org/wiki/Property:P4746>, is proceedings from <https://www.wikidata.org/wiki/Property:P4745>, Basketball-Reference.com NBDL player ID <https://www.wikidata.org/wiki/Property:P4744>, animal breed <https://www.wikidata.org/wiki/Property:P4743>, Uniform Resource Identifier Scheme <https://www.wikidata.org/wiki/Property:P4742>, OpenEdition journal ID <https://www.wikidata.org/wiki/Property:P4741>, Brooklyn Museum artwork ID <https://www.wikidata.org/wiki/Property:P4740>, Musée des Augustins artwork ID <https://www.wikidata.org/wiki/Property:P4739>, Yale Center for British Art artwork ID <https://www.wikidata.org/wiki/Property:P4738>, Solomon R. Guggenheim Museum artwork ID <https://www.wikidata.org/wiki/Property:P4737>, IBM graphic character global identifier <https://www.wikidata.org/wiki/Property:P4736>, IBM coded character set ID <https://www.wikidata.org/wiki/Property:P4735>, IBM code page identifier <https://www.wikidata.org/wiki/Property:P4734>, produced sound <https://www.wikidata.org/wiki/Property:P4733>, IUPAC GoldBook ID <https://www.wikidata.org/wiki/Property:P4732>, The Baseball Cube player ID <https://www.wikidata.org/wiki/Property:P4731>, Mir@bel journal ID <https://www.wikidata.org/wiki/Property:P4730>, INRAN Italian Food ID <https://www.wikidata.org/wiki/Property:P4729>, uBio ID <https://www.wikidata.org/wiki/Property:P4728>, Deutsche Synchronkartei dubbing voice actor ID <https://www.wikidata.org/wiki/Property:P4727>, Sign@l journal ID <https://www.wikidata.org/wiki/Property:P4726>, C-SPAN organization ID <https://www.wikidata.org/wiki/Property:P4725>, Le Maitron person ID <https://www.wikidata.org/wiki/Property:P4724>, GSMArena phone ID <https://www.wikidata.org/wiki/Property:P4723>, Érudit journal ID <https://www.wikidata.org/wiki/Property:P4722> - Query examples: - Gallery of photography techniques <https://query.wikidata.org/#%23defaultView%3AImageGrid%0ASELECT%20%3Fitem%2…> - Street names that exist several times in Berlin <https://query.wikidata.org/#SELECT%20%3Flabel%20%28COUNT%28%3Fstreet%29%20A…> (source <https://twitter.com/WikidataFacts/status/952260901008232448>) - Average length of movie by genre and year <https://query.wikidata.org/#%23%20average%20duration%20of%20movies%20by%20g…> (source <https://twitter.com/WikidataFacts/status/950503579881701376>) - Inventions by Republicans <https://query.wikidata.org/#%23%20things%20Republicans%20have%20%E2%80%9Cdi…> (source <https://twitter.com/csl_/status/950510713541361665>) - Celebrities born in January of a leap year <https://query.wikidata.org/#SELECT%0A%20%20%28COUNT%28%3Fpage%29%20AS%20%3F…> (source <https://twitter.com/fnielsen/status/950705578376036353>) - Countries with no rivers <https://query.wikidata.org/#%23%20countries%20with%20no%20rivers%0ASELECT%2…> (source <https://twitter.com/WikidataFacts/status/951568753816457217>) - Female aviation pioneers born before 1900 <https://query.wikidata.org/#%23defaultView%3ATimeline%0Aselect%20%3Fbooks%2…> (source <https://twitter.com/SciHiBlog/status/951582861399871488>) - People who died on K2 <https://query.wikidata.org/#%23%20Zgin%C4%99li%20na%20K2%0ASELECT%20%3Fhima…> (source <https://twitter.com/dziennikarz/status/952629249944547329>) - Showcase items <https://www.wikidata.org/wiki/Wikidata:Showcase_items>: 15 January 2018 <https://www.wikidata.org/wiki/Q45919591> Development - Wikidata moved to a new and bigger server. - Added support for a constraint scope in the constraint check gadget ( phabricator:T183542 <https://phabricator.wikimedia.org/T183542>) - Now ignoring deprecated constraints in the constraint check gadget ( phabricator:T180874 <https://phabricator.wikimedia.org/T180874>) - Added new Lua function getAllStatements (phabricator:T166056 <https://phabricator.wikimedia.org/T166056> - thanks Eran!) - Worked on diff support and edit summaries for edits on Forms ( phabricator:T182424 <https://phabricator.wikimedia.org/T182424>) - Worked on persistent editing of the grammatical features of a Form ( phabricator:T173742 <https://phabricator.wikimedia.org/T173742>) - Google Code-In 2017 work on the Wikidata Query Service UI: - add highlight and selection for query result table, by Anpans ( phabricator:T183807 <https://phabricator.wikimedia.org/T183807>) - keyboard accessibility, by eflyjason (phabricator:T173213 <https://phabricator.wikimedia.org/T173213> and subtasks) - make more areas translatable, by Albert221 (phabricator:T171636 <https://phabricator.wikimedia.org/T171636>) - mobile / responsive menus, by eflyjason (phabricator:T154890 <https://phabricator.wikimedia.org/T154890>) - lazy loading in ImageGrid, by Sydney (phabricator:T166216 <https://phabricator.wikimedia.org/T166216>) You can see all open tickets related to Wikidata here <https://phabricator.wikimedia.org/maniphest/query/4RotIcw5oINo/#R>. 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> - Suggested and open tasks <https://www.wikidata.org/wiki/Wikidata:Contribute/Suggested_and_open_tasks> ! - 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> Anything to add? Please share! :) Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

About the support of Arabic dialects by Wikidata
by abdelwaheb turki 15 Jan '18

15 Jan '18

Dear Mr. or Ms., I thank you for your efforts. I ask if Wikidata can be adjusted to support all Arabic dialects. The Arabic dialects are: North Levantine Arabic (apc), South Levantine Arabic (ajp), Gulf Arabic (afb), Hejazi Arabic (acw), Najdi Arabic (ars), Hadhrami Arabic (ayh), Sanaani Arabic (ayn), Ta'izzi-Adeni Arabic (acq), Mesopotamian Arabic (acm), Cypriot Arabic (acy), Egyptian Arabic (arz), Northwest Arabian Arabic (avl), Sudanese Arabic (apd), Bahrani Arabic (abv), Libyan Arabic (ayl), Tunisian Arabic (aeb-arab), Algerian Arabic (arq), Moroccan Arabic (ary), Hassaniya Arabic (mea), Saharan Arabic (aao), and Chadian Arabic (shu). Yours Sincerely, Houcemeddine Turki

4 5

Wikidata + Wikipedia outreach
by Brill Lyle 10 Jan '18

10 Jan '18

So User:Multichill has taken it upon himself to delete all of the catalog entries for the Black Lunch Table. One of the first if not only successful implementations of Wikidata as a task list for Wikipedia. There are other initiatives also using catalog, which I assume will also be deleted. Beyond the fact that this destroys hundreds of hours of work, it also negatively impacts outreach. If there was an alternative to catalog that could be used that would be one thing. If there was discussion about this action, that would also be one thing. But this wholesale destruction of outreach is unacceptable. https://www.wikidata.org/w/index.php?title=Special:Contributions/Multichill… https://www.wikidata.org/wiki/User_talk:Multichill#Black_Lunch_Table https://www.wikidata.org/wiki/Property_talk:P972#Abuse_of_this_property_for… https://www.wikidata.org/wiki/Wikidata:Requests_for_deletions#Artist_of_Bla… I am beside myself. I have been heavily evangelizing Wikidata in its integration with Wikipedia, especially multiple language Wikipedias. This was such a hostile unconstructive act, I am beside myself. This catalog tag was meant to be used to support various En Wiki outreach initiatives which address gender gap and diversity on the projects. What has happened here has very seriously negatively impacted that work. I am asking for support here. If the property was not okay, which after much discussion there seemed to be a consensus it was fine, then the opportunity to find other solutions should have been made, versus deleting all that work. - Erika *Erika Herzog* Wikipedia *User:BrillLyle <https://en.wikipedia.org/wiki/User:BrillLyle>*

17 54

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Wikidata January 2018