On 2016-08-11 22:29, Markus Kroetzsch wrote:
> On 11.08.2016 18:45, Andra Waagmeester wrote:
>> On Thu, Aug 11, 2016 at 4:15 PM, Markus Kroetzsch
>> <markus.kroetzsch(a)tu-dresden.de <mailto:firstname.lastname@example.org>>
>> has a statement "population: 20,086 (point in time: 2011)" that is
>> confirmed by a reference. Nevertheless, the statement is marked as
>> "deprecated". This would mean that the statement "the popluation was
>> 20,086 in 2011" is wrong. As far as I can tell, this is not the case.
>> I wouldn't say that with a deprecated rank, that statement is "wrong". I
>> consider de term deprecated to indicate that a given statement is no
>> longer valid in the context of a given resource (reference). I agree, in
>> this specific case the use of the deprecated rank is wrong, since no
>> references are given to that specific statement.
>> Nevertheless, I think it is possible to have disagreeing resources on an
>> identical statement, where two identical statements exists, one with
>> rank "deprecated" and one with rank "normal". It is up to the user to
>> decide which source s/he trusts.
> The status "deprecated" is part of the claim of the statement. The
> reference is supposed to support this claim, which in this case is
> also the claim that it is deprecated. The status is not meant to
> deprecate a reference (not saying that this is never useful,
> potentially, but you can only use it in one way, and it seems much
> more practical if deprecated statements get references that explain
> why they are deprecated).
Yes. I think a complete deprecated statement should look like this :
Value: <some value>
Qualifier: P2241:reason for deprecation + <some reason>
* P248:Stated in (or any other property for a reference) --> a reference
where the value is true (explaining why we added it)
Value: <name of the reference>
+ any additional qualifiers
* P1310:statement disputed by --> a reference
explaining why the claim is deprecated
Value: <name of the reference>
+ any additional qualifiers
JL aka Melderick
I’m Léa, I’m working at Wikimedia Deutschland since today as community
communication manager for Wikidata :)
We may already met on the Wikimedia projects with my personal account,
Auregann <https://fr.wikipedia.org/wiki/Utilisatrice:Auregann>. I
contribute on French Wikipedia, where I used to participate in the
newcomers welcoming project, add a few pictures on Commons, and I’m an
active member of the local user group laNCO
in which I organized a lots of community events, training sessions and GLAM
partnerships since 2011.
I used to work in IT, web development, on a local open data program, then
I’ve been an IT trainer in libraries for three years.
I started my position at WMDE to support Lydia on the community
communication on Wikidata, and some projects of improving the Wikimedia
projects with Wikidata data : I will also support all the structured data
efforts for Wikipedia, Commons, Wiktionnary… I’m here to discuss with
volunteers who edit the projects, welcome your ideas and suggestions, help
to find solutions to your problems and make sure that we can work together
to improve our projects and keep editing our favorite knowledge base in a
nice atmosphere :)
I will begin by discovering the working processes on Wikidata, chatting
with you and helping Lydia to answer to the technical questions
also work on upcoming topics such as reviewing our communication tools,
getting the improved showcase items selection process going, and organizing
something cool for Wikidata’s 4th anniversary :)
If you have any question, suggestion or idea, my talk page
<https://www.wikidata.org/wiki/User:Lea_Lacroix_(WMDE)> is wide open and I
will answer you as soon as I can. If you think that my advice could be
useful or if you want to inform me about a discussion happening somewhere,
feel free to ping me. You can also send me an e-mail or reach me on IRC
I’m very happy to join the team and look forward to working with you on all
As you may know, statements in Wikidata can be marked as "preferred" or
"deprecated" to distinguish them from the "normal" ones.
I found that many items have perfectly valid historical statements
marked as "deprecated". For example, our showcase item "Kleinmachnow"
has a statement "population: 20,086 (point in time: 2011)" that is
confirmed by a reference. Nevertheless, the statement is marked as
"deprecated". This would mean that the statement "the popluation was
20,086 in 2011" is wrong. As far as I can tell, this is not the case.
It seems that somebody wanted to indicate that this old population is no
longer current. This is achieved not by deprecating the old value, but
by setting another (newer) value as "preferred".
Similar problems occur for the mayor of this town.
I hope there is no deeper confusion in the community regarding this
intended use of "preferred" and "deprecated". Most other items are using
it correctly, it seems. The fact that it occurs in a showcase item is
still making me a bit concerned.
Prof. Dr. Markus Kroetzsch
Knowledge-Based Systems Group
Faculty of Computer Science
+49 351 463 38486
Hey folks :)
Just a quick note that we have now rolled out the ArticlePlaceholder
on Welsh and Kannada Wikipedia as well. Both project had requested it.
Here are 2 example pages:
We are continuing to work on improving it based on the feedback we've
gotten so far from the projects that already have it. This includes
layout fixes, making it possible to translate an article from another
language using the ContentTranslation tool and getting them to show up
in search engine results.
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
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.
Many items were created for Wikimania talks. They were created because
Wikimania talks represent the best practices of the Wikimedia projects. All
these talks were selected in a process to bring out the best our movement
has to offer in the many years Wikimania was held. All the persons who gave
these presentation are known by either their nick or their name as they
themselves identified them at the time of offering the presentation for
For whatever reasons a Wikidata admin removed these items without any
discussion. In the discussion that followed other people presented the
arguments why there are no valid arguments for this deletion. A request was
made repeatedly to undelete the items involved.
Given the current state of affair there is little option but to recreate
these items. It must be noted that the current situation is problematic on
many levels. Among them it became clear that admins do as they wish and are
not held accountable for their actions. The only thing asked is for the
undeletion of items and some sober thought on what may be expected of a
At long last, we’re delighted to announce you can now render sparql queries
using the Histropedia timeline engine \o/
Histropedia WikidataQuery Viewer
Unlike the main Histropedia site this tool renders timelines with data
directly from live Wikidata queries. It lets you map query variables to
values used to render the timeline. A few notable extra features compared
with the built in timeline view on the Wikidata query service:
*Precision* - You can render each event according to the precision of the
date (as long as you add date precision to your query). It will default to
day precision if you leave this out.
*Rank *– The events on the timeline have a rank defined by the order of
your sparql query results. You can also choose a query variable to use for
rank, but it’s not really needed if you use ORDER BY in your query to
control the order of results. Higher ranked events are placed more
prominently on the timeline.
*URL* – You can choose whichever URL you like from your query results,
which will be opened in a new tab when you double click on an event on the
*Automatic colour code / filter* – You can choose any variable in your
sparql query to use for colour coding and filtering. From what I could tell
from the preview, this seems to be the same as the new map layers feature
that is close to launch on the Wikidata Query service (which looks awesome
by the way!)
Also similar to the ‘group by property’ feature on Magnus’ Listeria tool,
but using an arbitrary variable from the sparql results instead of a
*Some cool examples:*
Note: click on the droplet icon (top right) to see the colour code key and
- Discoveries about planetary systems, colour coded by type of object
<http://tinyurl.com/zlqupz9> (only items with an image and discoverer)
- Who's birthday is today? colour coded by country of citizenship
- Oil paintings at the Louvre, colour coded by creator
- Descendants of Alfred the Great, colour coded by religion, in Japanese
<http://tinyurl.com/h75utbg> – Note: select ‘no value’ in the filter
panel for a fun edit list of people missing religion statement :)
More examples on a dropdown list from the query input page
<http://www.histropedia.com/showcase/wikidata-viewer.html> in the tool.
The tool has been created by myself and fellow Histropedia co-founder Sean
code, and it’s a very early stage app so please let me know if anything
You can find more info on the JS library (called HistropediaJS) on this
announcement from the Histropedia mailing list
we have a vacancy in our group on text mining in Open Access publications. The results of the text mining process will be stored using Wikidata infrastructure. The position is for three years with a possibility of extension.
The Job is part of a new project "NOA - The replication of open access images: development of a method for automatic harvesting, indexing and provision of open access images from technical subjects using the infrastructure of Wikimedia Commons and Wikidata".
You will part of a dynamic international team at the Hochschule Hannover. Hannover is a large and central city in Germany with a number of universities and research institutes. Basic knowledge of German is an advantage but not strictly necessary. For full details, please, refer to: http://www.hs-hannover.de/dezernat-i-personal-und-organisation/personalange…
Please note that applications should be send before 19th August 2016!
For any questions about the project and the job, please contact me.
I'm looking forward to all questions and applications!
Prof. Dr. Christian Wartena
Fakultät III - Medien, Information und Design
Abt. Information und Kommunikation
Lehrgebiet Sprach- und Wissensverarbeitung
Studiengangskoordinator Bachelor Informationsmanagement (BIM)
Expo Plaza 12
Tel: +49 (0)511 9296 2594
Cheers Dan! :-)
I actually still need to sort out a bug reporting system, but I've got that
one noted down for now.
Will add a link to the app soon for a better way to report things.
On 10 Aug 2016 21:36, "Dan Garry" <dgarry(a)wikimedia.org> wrote:
Neat! It's always exciting to see awesome things like this built on top of
the Wikidata Query Service.
One small piece of feedback: the timelines look quite blurry
<https://i.imgur.com/k56aeFD.png> on my computer. Should I file this as a
bug report somewhere? :-)
Thanks, and keep up the great work!
On 10 August 2016 at 12:49, Navino Evans <navino(a)histropedia.com> wrote:
> Hi all,
> At long last, we’re delighted to announce you can now render sparql
> queries using the Histropedia timeline engine \o/
> Histropedia WikidataQuery Viewer
> Unlike the main Histropedia site this tool renders timelines with data
> directly from live Wikidata queries. It lets you map query variables to
> values used to render the timeline. A few notable extra features compared
> with the built in timeline view on the Wikidata query service:
> *Precision* - You can render each event according to the precision of the
> date (as long as you add date precision to your query). It will default to
> day precision if you leave this out.
> *Rank *– The events on the timeline have a rank defined by the order of
> your sparql query results. You can also choose a query variable to use for
> rank, but it’s not really needed if you use ORDER BY in your query to
> control the order of results. Higher ranked events are placed more
> prominently on the timeline.
> *URL* – You can choose whichever URL you like from your query results,
> which will be opened in a new tab when you double click on an event on the
> *Automatic colour code / filter* – You can choose any variable in your
> sparql query to use for colour coding and filtering. From what I could tell
> from the preview, this seems to be the same as the new map layers feature
> that is close to launch on the Wikidata Query service (which looks awesome
> by the way!)
> Also similar to the ‘group by property’ feature on Magnus’ Listeria tool,
> but using an arbitrary variable from the sparql results instead of a
> Wikidata property.
> *Some cool examples:*
> Note: click on the droplet icon (top right) to see the colour code key and
> filter options
> - Discoveries about planetary systems, colour coded by type of object
> <http://tinyurl.com/zlqupz9> (only items with an image and discoverer)
> - Who's birthday is today? colour coded by country of citizenship
> - Oil paintings at the Louvre, colour coded by creator
> - Descendants of Alfred the Great, colour coded by religion, in
> Japanese <http://tinyurl.com/h75utbg> – Note: select ‘no value’ in the
> filter panel for a fun edit list of people missing religion statement
> More examples on a dropdown list from the query input page
> <http://www.histropedia.com/showcase/wikidata-viewer.html> in the tool.
> The tool has been created by myself and fellow Histropedia co-founder Sean
> code, and it’s a very early stage app so please let me know if anything
> You can find more info on the JS library (called HistropediaJS) on this
> announcement from the Histropedia mailing list
> Wikidata mailing list
Lead Product Manager, Discovery
Wikidata mailing list
Dear users, developers and all people interested in semantic wikis,
We are very happy to announce that early bird registration to the 13th
Semantic MediaWiki Conference is now open!
Important facts reminder:
* Dates: September 28th to September 30th 2016 (Wednesday to Friday)
* Location: German Institute for International Educational Research
(DIPF), Schloßstraße 29, Frankfurt am Main, Germany.
* Conference page: https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2016
* Participants: Everybody interested in semantic wikis, especially in
Semantic MediaWiki, e.g. users, developers, consultants, business
representatives and researchers.
We welcome new contributions from you:
* We encourage contributions about applications and development of
semantic wikis; for a list of topics, see .
* Please propose regular talks, posters or workshops on the conference
website. We will do our best to consider your proposal in the conference
program. An interesting variety of contributions has already been
proposed, see .
* Presentations will generally be video and audio recorded and made
available for others after the conference.
News on participation and tutorials:
* You can now officially register for the conference  and benefit
from early bird fees until September 11, 2016.
* German Institute for International Educational Research (DIPF)  and
Open Semantic Data Association e. V.  have become the official
organisers of SMWCon Fall 2016
* Thanks go to Wikimedia Germany  for supporting SMWCon Fall 2016
If you have questions you can contact Sabine Melnicki, Kendra Sticht and
Christoph Schindler (Program Chairs), Karsten Hoffmeyer (General Chair)
or Lia Veja (Local Chair) per e-mail (Cc).
We will be happy to see you in Frankfurt!
Sabine Melnicki, Kendra Sticht and Christoph Schindler