Hello all,
This is a follow-up on previous announcements related to the migration of
wb_terms table (March 23rd
<https://www.wikidata.org/wiki/Wikidata:Project_chat/Archive/2020/03#Importa…>,
April 6th
<https://www.wikidata.org/wiki/Wikidata:Project_chat/Archive/2020/04#wb_term…>)
that concerns tool developers querying the database replicas on Labs.
As the last step of the migration, and as mentioned in the previous
discussions, the table wb_terms_no_longer_updated will be dropped. We are
doing this because the last steps of database migration have been achieved
and announced a month ago, and we don’t want to keep a table containing
outdated information accessible for too long. The table has already been
deleted in production (without any impact on tools or users) and the
replicas on Labs will be deleted on April 29th. (Ticket
<https://phabricator.wikimedia.org/T248086>)
If you’re maintaining tools querying the database with the replicas, you
can adapt your code to the new table structure
<https://doc.wikimedia.org/Wikibase/master/php/md_docs_storage_terms.html>
(the former shared link doesn't work anymore). You can also have a
look at suggestions
to optimize your queries
<https://www.wikidata.org/wiki/User:Amir_Sarabadani_(WMDE)/Database_normaliz…>.
If you have any questions or issues, feel free to reach out to me. Thanks
for your understanding,
--
Léa Lacroix
Project Manager Community Communication 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.
Hi everyone,
I hope you’re all having a great day!
I’m super excited to announce that I’ll be joining the software department at
Wikimedia Germany to help advance engagement between the software
development team and the communities using and contributing to
Wikidata/Wikibase.
Together with Léa, Sam and Lydia, I will be liaising with the different
user groups within the Wikibase community to provide information about
software changes and promote a smooth and productive collaboration between
stakeholders. You can share bug reports with us at <
https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team>
Please leave a note on my talkpage <
https://www.wikidata.org/wiki/User_talk:Mohammed_Sadat_(WMDE)> or write to
me directly anytime you encounter issues with the Wikibase software so that
I can bring them to the development team:
* mohammed.sadat_ext(a)wikimedia.de
* Telegram (@masssly) and IRC (mabdulai)
Best Regards,
--
Mohammed Sadat Abdulai
*Community Communications Manager for Wikidata/Wikibase*
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Hi everyone,
The first weekend of May the Wikimedia Hackathon 2020 in Tirana was
supposed to happen. As an alternative, we're organizing a remote
hackathon. Please have a look at
https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2020/Remote_Hackathon
and sign up if you're interested in participating.
All of the sessions, projects, and initiatives are run by the
participants themselves and not overseen by a core organizing team. All
ideas including technical projects and sessions, non-technical projects
and sessions, and social events/socal time are very welcome.
Please spread the word!
Maarten
Hi,
This message is relevant for people writing SPARQL queries and using the
Wikidata Query Service:
As part of the work of redesigning the WDQS updater[0] we identified that
blank nodes[1] are problematic[2] and we plan to deprecate their usage in
the wikibase RDF model[3]. To ease the deprecation process we are
introducing the new function wikibase:isSomeValue() that can be used in
place of isBlank() when it was used to filter SomeValue[4].
What does this mean for you: nothing will change for now, we are only
interested to know if you encounter any issues with the
wikibase:isSomeValue() function when used as a replacement of the isBlank()
function. More importantly, if you used the isBlank() function for other
purposes than identifying SomeValue (unknown values in the UI), please let
us know as soon as possible.
The current plan is as follow:
1. Introduce a new wikibase:isSomeValue() function
We are at this step. You can already use wikibase:isSomeValue() in the
Query Service. Here’s an example query (Humans whose gender we know we
don't know):
SELECT ?human WHERE {
?human wdt:P21 ?gender
FILTER wikibase:isSomeValue(?gender) .
}
You can also search the wikis[8] to find all the pages where the function
isBlank is referenced in a SPARQL query.
2. Generate stable labels for blank nodes in the wikibase RDF output
Instead of "autogenerated" blank node labels wikidata will now provide a
stable label for blank nodes. In other words the wikibase triples using
blank nodes such as:
s:Q2-6657d0b5-4aa4-b465-12ed-d1b8a04ef658 ps:P576 _:genid2 ;
will become
s:Q2-6657d0b5-4aa4-b465-12ed-d1b8a04ef658 ps:P576
_:1668ace9a6860f7b32569c45fe5a5c0d ;
This is not a breaking change.
3. [BREAKING CHANGE] Convert blank nodes to IRIs in the WDQS updater
At this point some WDQS servers will start returning IRIs such as
http://www.wikidata.org/somevalue/1668ace9a6860f7b32569c45fe5a5c0d (the
exact form of the IRI is still under discussion) instead of blank node
literals like t1514691780 auto-generated by blazegraph. Queries still using
isBlank() will stop functioning. Tools explicitly relying on the presence
of blank nodes (t1514691780) in the query results will also be affected.
We don’t have a defined date for this change yet, but we will follow the
Wikidata breaking change process (announcing the change 4 weeks in advance).
4. [BREAKING CHANGE] Change the RDF model and remove blank nodes completely
from the RDF dumps
Instead of doing the conversion and blank node removal in the WDQS updater
we will do it at RDF generation.
This is a breaking change of the somevalue section of the RDF model[5] and
the no value owl constraint for properties[6].
We don’t have a defined date for this change yet, but we will follow the
Wikidata breaking change process (announcing the change 4 weeks in advance).
If you encounter issues using wikibase:isSomeValue() or if you have
questions about the process, feel free to write a comment on the
Phabricator ticket[3] or the Contact the development team (query service
and search) wiki page[7].
Thanks!
--
David Causse
0: https://phabricator.wikimedia.org/T244590
1: https://en.wikipedia.org/wiki/Blank_node
2: https://phabricator.wikimedia.org/T244341#5889997
3: https://phabricator.wikimedia.org/T244341
4: https://www.mediawiki.org/wiki/Wikibase/DataModel#PropertySomeValueSnak
5:
https://www.mediawiki.org/wiki/Wikibase/Indexing/RDF_Dump_Format#Somevalue
6: https://www.mediawiki.org/wiki/Wikibase/Indexing/RDF_Dump_Format#Novalue
7:
https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team/Query_S…
8:
https://www.wikidata.org/w/index.php?search=all%3Ainsource%3A%2FisBlank+%2A…
I recently asked <https://twitter.com/thadguidry/status/1247635376094707712>
a Freebase colleague @narphorium to graciously spend some time to write up
what was once a very cool Freebase app that many of us used in Freebase to
see overlap of Freebase Properties (like WD statements) between 1-5
Freebase Topics (like WD Items) that then ran a query to find other Topics
that matched that overlapping set.
I thought that sharing this knowledge would allow others to get inspired
and learn and possibly build a similar shape tool for Wikidata; if not
already existing.
Freebase Sets
https://github.com/narphorium/freebase-sets
Best of luck WD engineers!
Thad
https://www.linkedin.com/in/thadguidry/
Hello,
Is there any documentation to "wbeditentity", except from the few
examples on the API-document-page?
Any documentation about the format/grammar of the data?
And is there any API-documentation for lexicographical data at al?
The few bits on the source-code generated page aren't sufficient.
Cheers,
M
--
Michael F. Schönitzer
Prochintalstr. 2
80993 München
Mail: michael(a)schoenitzer.de
Jabber: schoenitzer(a)jabber.ccc.de
Tel: 089/37918949 - Mobil: 017657895702