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.
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
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
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
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/)
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
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
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_Tablehttps://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>*