Hi everyone,
We are working on making it easier to use Wikidata's data to build
applications. A big part of that is a better API. Over the past months
we have been developing the first version and gotten testing and
feedback for it. Last week we made it available on test.wikidata.org.
Today the first version of the new Wikibase REST API is available on
Wikidata. I'd like to thank everyone who helped along the way by
providing feedback and testing.
You can find more information on what you can already do with the new
Wikibase REST API at https://www.wikidata.org/wiki/Wikidata:REST_API.
We will continue to build out its functionality and your input on what
would be most useful for you will help prioritize the next steps.
Please leave your thoughts at
https://www.wikidata.org/wiki/Wikidata_talk:REST_API_feedback_round#The_Wik….
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher - WD:Q18016466
Product Manager for Wikidata
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
https://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.
*(apologies for cross posting)* Hello everyone,
As you may already know, we are developing a new REST API to improve
programmatic access to data from Wikidata and other Wikibase instances.
Many thanks to everyone who gave us the initial feedback on the proposed
implementation plan of the REST API and subsequently tested the
experimental phase of it on Beta Wikidata
<https://wikidata.beta.wmflabs.org>.
All the items listed in our previous communication
<https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/me…>
as still needing to be completed for the initial release have now been
completed and we are pleased to announce that the Wikibase REST API is
planned to go live on Wikidata about a week later.
What is the current state capable of doing?
-
Retrieve the data of an Item with ‘GET /entities/items/{item_id}’ and
filter what fields (i.e. type, labels, descriptions, aliases, statements,
sitelinks) are returned when reading the Item data
-
Retrieve all statements of an Item with ‘GET
/entities/items/{item_id}/statements’
-
Retrieve the data of a single statement of an Item with ‘GET
/entities/items/{item_id}/statements/{statement_id}’ or ‘GET
/statements/{statement_id}’
-
Conditionally request the data only if it has changed since the
specified revision/timestamp (using If-None-Match, If-Modified-Since
HTTP headers)
-
Create a statement on an Item with ‘POST
/entities/items/{item_id}/statements’
-
Authenticate and authorize as a Beta Wikidata user when making edits
using the API, as well as provide edit tags and edit comment, and mark an
edit as one made by a bot.
-
Replacing the statement on an Item with ‘PUT
/entities/items/{item_id}/statements/{statement_id}’ or ‘PUT
/statements/{statement_id}’
-
Removing the statement from an Item with ‘DELETE
/entities/items/{item_id}/statements/{statement_id}’ or ‘DELETE
/statements/{statement_id}’
-
Automated edit summaries
The following functionality is still awaiting a final security review of a
library <https://phabricator.wikimedia.org/T316523> and will be enabled
once that is finished:
-
Editing a statement on an Item with ‘PATCH
/entities/items/{item_id}/statements/{statement_id}’ or ‘PATCH
/statements/{statement_id}’
Please note that the following items previously listed under "The following
will likely not be available in the first version but follow later" have
not yet been finished and will not be available in this initial release:
-
Creating or deleting an Item
-
Getting a statement from an Item based on the Property ID in the
statement
-
Any operation (reading, adding, editing, removing) on sitelinks, labels,
descriptions and aliases
-
Any operation on entity types other than Items (i.e. Properties,
Lexemes, …)
-
Translated error messages
However, we will continue to work on these items in the future to provide a
more comprehensive REST API. In order to prioritize our next steps, we
would greatly appreciate feedback on which missing features you would find
most useful to add next.
If you have any questions or want to provide feedback please let us
know at Wikidata
talk:REST API feedback round
<https://www.wikidata.org/wiki/Wikidata_talk:REST_API_feedback_round#The_Wik…>.
As this new API is more tailored to the Wikibase data model than the Action
API, we have outlined the differences in the JSON data format between the
two
<https://doc.wikimedia.org/Wikibase/master/php/rest_data_format_differences.…>
for you for easy comparison.
Thank you for your patience and support as we continue to improve the
Wikibase REST API.
Cheers,
--
Mohammed Sadat
*Community Communications Manager, Wikidata*
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0) 30 577 116 2466
https://wikimedia.de
Grab a spot in my calendar for a chat: calendly.com/masssly.
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.
Hello 👋🏽
I'm Benedict Nnaemeka Udeh from Nigeria, a recently hired Community
Relations Specialist (CRS
<https://meta.wikimedia.org/wiki/Community_Relations_Specialists>) for
Wikidata and Commons.
I'm a member of the Igbo Wikimedians User Group, the Founder of IG Wikidata
Hub, and the Founder of Wiki Mentor Africa, a mentorship program that seeks
to bring more African developers and technical writers into the technical
space of Wikimedia. I'm passionate about community growth and capacity
building. Like you, I'm incredibly spirited about the free knowledge
movement.
In my new position as CRS, I will focus on collaboration and communication
with you about Wikidata and Commons product development, the user-facing
changes and roll-outs, and sometimes on projects with special needs for
collaboration with Volunteers. In other words, I am here to serve you (the
editors, contributors, and readers of Commons and Wikidata projects) and
the working groups at the Foundation that support Commons and Wikidata.
I've already started sharing some updates; you can find them on the Product
and technical support for Commons Portal
<https://commons.wikimedia.org/wiki/Commons:Product_and_technical_support_fo…>.
Please feel free to use the discussion page
<https://commons.wikimedia.org/wiki/Commons_talk:Product_and_technical_suppo…>
to discuss these updates.
I look forward to working with and for you all and can't wait to see the
fantastic things we will do together.
Benedict Udeh
Community Relations Specialist
Sehr geehrte Damen und Herren,
ich recherchiere für die Universität für Musik und darstellende Kunst
Wien diverse Namen von Musikern, Komponisten, Schauspieler usw. auf
Ihrer Seite.
Bei einer Recherche fiel mir auf, dass bei dem Komponisten Peter
Kreuder (Q76660) https://www.wikidata.org/wiki/Q76660 der Link zu der
Vienna History Wiki ID 38214
(
https://www.geschichtewiki.wien.gv.at/Special:URIResolver/?curid=38214)
falsch verlingt wurde. Es wird hier die Seite des Richard Franz Kreutel
angezeigt.
Ich denke es ist im allgemeinen Interesse, wenn Fehler bemerkt und
gemeldet werden.
Mit freundlichen Grüßen
Renate Schiebel
Universität für Musik und darstellende Kunst, Wien
Archiv
Tel: 0171155-6512
Anton-von-Webern Platz 1/I
schiebel-renate(a)mdw.ac.at
Hi.
I'm setting up a local instance of Wikidata, but have a particular
issue: ./runBlazegraph.sh produces tons of logging, most labelled as
"DEBUG", and I've found no documentation about the parameters to use to
suppress it (or, at least, to use a different logging level).
Adding
-Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog
-Dorg.eclipse.jetty.LEVEL=WARN
to the "exec java" command has reduced a bit the output, but still it
reacts to ./loadRestAPI.sh with an insane quantity of debugging
informations (which, of course, has heavy impact on performance).
Any advice on it?
Thank you.
--
Roberto Guido
http://www.madbob.org/
*(apologies for cross-posting)*
Hello,
We’re pleased to announce security and maintenance updates for Wikibase
Suite that are compatible with MediaWiki 1.35 and 1.36. These updates,
which include the release of new container images, take the form of two new
Suite versions: wmde.7 and wmde.8, respectively.
Release wmde.7 includes two security fixes for issues in the Wikibase
extension:
-
Validate term length in Special:NewProperty (phab:T308659
<https://phabricator.wikimedia.org/T308659>)
-
Escape message in hook handler (phab:T302215)
<https://phabricator.wikimedia.org/T302215>
Note that wmde.8 release is based on Mediawiki version 1.36 which is no
longer maintained. We provide this update for technical reasons, as
updating to the most recent 1.36-compatible Wikibase version will be needed
to update Wikibase to Mediawiki 1.37. WMDE will be releasing that new
version shortly. The wmde.8 release includes a fix for the “Escape message
in hook handler” issue (phab:T302215
<https://phabricator.wikimedia.org/T302215>).
Both releases also include minor updates, such as translation updates for
MediaWiki and the Wikibase and WikibaseLocalMedia extensions, as well as
the Query Service UI and Quick Statements.
For update instructions, see Upgrading Wikibase
<https://github.com/wmde/wikibase-release-pipeline/blob/main/docs/topics/upg…>
.
If you have any questions, please feel free to ask on this mailing list, or
you can leave a comment at Talk:Wikibase/FAQ
<https://www.mediawiki.org/wiki/Talk:Wikibase/FAQ>.
Cheers,
--
Mohammed Sadat
*Community Communications Manager for Wikidata/Wikibase*
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0) 30 577 116 2466
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.
Hello everyone,
We are working on making it easier to access Wikidata’s data
programmatically so that more people can build great applications on top of
our data. As part of this we are building a new REST API for Wikibase. A
while ago we asked for feedback on the draft specification for that new API
<https://www.wikidata.org/wiki/Wikidata:REST_API_feedback_round> (see previous
communication
<https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/me…>
). It is in development now. While it is not in the state which we would
like to run on Wikidata, you can now have a look at the current development
state on Beta Wikidata <https://wikidata.beta.wmflabs.org> and follow along
as we build out the API. You can find the current state of the
specification we are working from at
https://doc.wikimedia.org/Wikibase/master/js/rest-api/. *(Small caveat: The
specification might sometimes be slightly ahead of the code development and
contain functionality that still needs to be implemented.)*
Please note that the API is still in the experimental development state.
There might be changes in the functionality available and API’s behavior
that we will not announce separately.
The current state can already do the following:
-
Retrieve the data of an Item with ‘GET /entities/items/{item_id}’ and
filter what fields (i.e. type, labels, descriptions, aliases, statements,
sitelinks) are returned when reading the Item data
-
Retrieve all statements of an Item with ‘GET
/entities/items/{item_id}/statements’
-
Retrieve the data of a single statement of an Item with ‘GET
/entities/items/{item_id}/statements/{statement_id}’ or ‘GET
/statements/{statement_id}’
-
Conditionally request the data only if it has changed since the
specified revision/timestamp (using If-None-Match, If-Modified-Since
HTTP headers)
-
Create a statement on an Item with ‘POST
/entities/items/{item_id}/statements’
-
Authenticate and authorize as a Beta Wikidata user when making edits
using the API, as well as provide edit tags and edit comment, and mark an
edit as one made by a bot.
If you want to give it a try, here are some REST API calls for an example
Item (“house cat”) on Beta Wikidata:
-
Get the complete data of the Item: GET
https://wikidata.beta.wmflabs.org/w/rest.php/wikibase/v0/entities/items/Q59…
-
Get all labels: GET
https://wikidata.beta.wmflabs.org/w/rest.php/wikibase/v0/entities/items/Q59…
-
Get a specific statement by its ID: GET
https://wikidata.beta.wmflabs.org/w/rest.php/wikibase/v0/entities/items/Q59…
-
Get all statements: GET
https://wikidata.beta.wmflabs.org/w/rest.php/wikibase/v0/entities/items/Q59…
The following things are still missing before it can go live on Wikidata in
a first version:
-
Replacing the statement on an Item with ‘PUT
/entities/items/{item_id}/statements/{statement_id}’ or ‘PUT
/statements/{statement_id}’
-
Editing a statement on an Item with ‘PATCH
/entities/items/{item_id}/statements/{statement_id}’ or ‘PATCH
/statements/{statement_id}’
-
Removing the statement from an Item with ‘DELETE
/entities/items/{item_id}/statements/{statement_id}’ or ‘DELETE
/statements/{statement_id}’
-
Automated edit summaries
The following will likely not be available in the first version but follow
later:
-
Creating or deleting an Item
-
Getting a statement from an Item based on the Property ID in the
statement
-
Any operation (reading, adding, editing, removing) on sitelinks, labels,
descriptions and aliases
-
Any operation on entity types other than Items (i.e. Properties,
Lexemes, …)
-
Translated error messages
If you have any feedback on what’s there so far please let us know at Wikidata
talk:REST API feedback round
<https://www.wikidata.org/wiki/Wikidata_talk:REST_API_feedback_round>.
Cheers,
--
Mohammed Sadat
*Community Communications Manager for Wikidata/Wikibase*
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0) 30 577 116 2466
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.
*(apologies for cross-posting)*
*This announcement is significant for Wikidata API users.*
As a follow-up to the recent improvements we made to the Special:NewLexeme
<https://www.wikidata.org/wiki/Special:NewLexeme> page (see the previous
announcement
<https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/th…>)
we introduced a new search profile that will prioritize Items representing
languages in the Lexeme language input. This will allow editors to more
easily find the correct Item for the language of a Lexeme they are creating.
Users of the wbsearchentities Action API module can use a new parameter,
"profile", to select the search profile to use. The default value,
"default", is equivalent to the previous behavior of the API, and should be
suitable for most purposes. The "language" profile can be used to search
for Items representing languages, as it will prioritize these Items as
results. The wbsearch submodule of the query Action API module also gains
this parameter (called "wbsprofile", or "gwbsprofile" when wbsearch is
being used as a generator), with the same allowed values and meaning. The
new parameter is optional, so most API users should not need to update
their code; users who use the API to search for language Items can add
"profile=language" to their request parameters.
New profiles may be added in future without additional significant change
announcements, though we will likely mention them in the weekly summary and
other channels as appropriate. As with any Action API module, the valid
values of the "profile" parameter may be discovered via the "help" or
"paraminfo" modules, and the values will have documentation messages
explaining what the profile can be used for.
The new parameter is already available on Test Wikidata, though the two
profiles will produce the same search results there. It will become
available on Wikidata on Thursday, 28 July 2022.
If you have feedback or questions please let us know on this phabricator
ticket <https://phabricator.wikimedia.org/T307869>.
Cheers
--
Mohammed Sadat
*Community Communications Manager for Wikidata/Wikibase*
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0) 30 577 116 2466
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.
Hello all,
The next *Wikidata Bug Triage Hour session* will take place on Thursday, *May
5th, at 16:00 UTC* (18:00 CEST) on Jitsi.
This meeting is open to everyone involved in Wikidata and interested in
following the progress of the software development, or having specific
issues or requests related to software. During this session, we look at
tickets of our tracking system Phabricator, we improve their description,
tags and keywords together, in order to make them more understandable and
easier to discover and to pick by a development team or a volunteer in the
future.
The upcoming session doesn't have a specific topic, it's an open
discussion, so you are welcome to join and *bring a Phabricator task that
you particularly care about or that deserves some love*.
The meeting is taking place on Jitsi, it is not recorded in video but we
are taking collaborative notes. You can find all the links and information
here: https://www.wikidata.org/wiki/Wikidata:Events#Wikidata_bug_triage_hour
And finally: there is no prerequisite or need to have participated in
previous sessions to join - you can also join only to listen and *discover
more about how we track and describe bugs and feature requests for Wikidata
:)*
Looking forward to meet you there!
--
Léa Lacroix
Community Engagement Coordinator
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.
(This change is relevant for all Wikidata users working with labels,
descriptions, and aliases.)
Based on a long-standing community request we have enabled a new language
code for labels, descriptions, and aliases on Test Wikidata: “mul”, a
special language code meaning “multiple languages”. It is intended to
replace the current duplication of certain labels and aliases in many
languages: instead of the given name Douglas (Q463035)
<https://www.wikidata.org/wiki/Q463035> having the label “Douglas” in
hundreds of Latin-script languages, it should be enough to add it once as
the “mul” label and have all other languages falling back to that (before,
as usual, falling back to “en” as a last resort). This should reduce the
amount of redundant data in Wikidata, and relieve some pressure from the
query service. A big thank you goes to all people involved in the
discussions!
The purpose of the Test Wikidata version of this feature is to determine
whether the current functionality is already sufficient, or whether the
feature needs more work before it can be enabled on Wikidata proper.
Current implementation:
-
You can interact with the new language code using the API.
-
The new language code appears in the table of labels at the top of an
item page for users whose Babel information includes “mul” (or who use ?
uselang=mul in the URL). If there is already a “mul” label, it will be
available for everyone under the usual “all entered languages” option.
-
The page heading will fall back to the “mul” label if necessary.
Fallbacks to “mul” have the usual “indicator” that shows a fallback took
place (CSS class wb-language-fallback-mul).
For more details, see T285156 <https://phabricator.wikimedia.org/T285156>
(or T297393 <https://phabricator.wikimedia.org/T297393> for the Test
Wikidata implementation). You are welcome to leave any feedback about the
technical implementation of the new language code on these tickets.
The new language code will very likely need adjustment of Wikidata policies
and guidelines. In case you would like to contribute to drafting
preliminary new guidelines, a good starting point is: Help
talk:Label#Drafting of guidelines for new language code mul
<https://www.wikidata.org/wiki/Help_talk:Label#Drafting_of_guidelines_for_ne…>
.
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.