Wikidata-tech

wikidata-tech@lists.wikimedia.org

621 discussions

dashes - in JSON keys - suck
by Thad Guidry 20 Jun '24

20 Jun '24

"mainsnak": { "snaktype": "value", "property": "P31", "hash": "d679b35e7a9523b92903b52661a9e4c15d8d76d3", "datavalue": { "value": { "entity-type": "item", "numeric-id": 112826905, "id": "Q112826905" }, "type": "wikibase-entityid" }, "datatype": "wikibase-item" }, One of the constant pain points that I have heard and run across is this: Any chance Wikidata's JSON format might be a little more developer friendly > for tooling in general? Like why do they sometimes have "entity-type" and > "numeric-id" as keys with dashes, when a lot of the world and our parsing > libraries have sorta standardized around at least only camelCase or > snake_case in JSON. I mean, look at what they did with "snaktype" and > "entity-type" ! Can you find out, Thad ? So I said to them, sure. 😉 (granted I know all characters are allowed for object property names in JSON and someone likely in the team at the time said, "eh, doesn't matter, it's JSON, it eats anything".) Thad https://www.linkedin.com/in/thadguidry/ https://calendly.com/thadguidry/

1 0

[BREAKING Change Announcement] Upcoming Changes to Wikibase: new EntitySchema data type
by Lydia Pintscher 18 Jun '24

18 Jun '24

Hi everyone, This is a breaking change announcement relevant for some Wikibase API users. What is Changing? On 2 July 2024, we will enable the EntitySchema data type on Wikidata, and we expect the community to create the first properties with that data type and start using them in statements shortly afterwards. This means that there will be values with the data value type wikibase-entityid containing an EntitySchema ID (with "entity-type": "entity-schema" in the JSON value). However, EntitySchema is not yet a full-featured Wikibase entity type; it is our intention to eventually make it work like other entity types (Item, Property, etc.), but at the moment, using EntitySchema in e.g. the wbgetentities API or Special:EntityData does not work. Who is Affected? Code which assumes that IDs found in wikibase-entityid data values can be used with other Wikibase entity APIs may need adjusting. Other Wikibases instances besides Wikidata are not affected unless they also use the EntitySchema extension and set $wgEntitySchemaEnableDatatype = true. What You Need to Do If your code works with statements of arbitrary data types, and looks up entities referenced in values with the data value type wikibase-entityid, you probably want to check that the entity-type is not entity-schema before proceeding. (Note that, if your goal is to display the value, you can instead use the wbformatvalue API for any data type.) If you use the wbformatvalue API, you should make sure that you also specify the datatype or property parameter (depending on which information you have available; note that specifying both parameters at once is an error). Without this information, not all values can be formatted correctly; in particular, trying to format an EntitySchema value without specifying the datatype or property will result in an error (“An illegal set of parameters have been used”). (Specifying the datatype or property parameter for wbformatvalue has always been advisable, and necessary for some other data value types, but this is the first time it becomes relevant for wikibase-entityid data values.) As previously announced <https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/th…>, the new data type is already enabled on Test Wikidata, so you can try out the behaviour there. (An example item on Test Wikidata with a statement linking to an EntitySchema is human <https://test.wikidata.org/wiki/Q497>.) If you have any questions or concerns about this change, please don’t hesitate to reach out to us in this ticket (T332157 <https://phabricator.wikimedia.org/T332157>). Cheers, Lydia -- Lydia Pintscher - https://lydiapintscher.de - WD:Q18016466 <https://www.wikidata.org/wiki/Q18016466> Portfolio Lead for Wikidata Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30-577 11 62-0 https://wikimedia.de 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 Charlottenburg, VR 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207. Geschäftsführende Vorstände: Franziska Heine, Dr. Christian Humborg

1 0

(DEC 2024) Huawei H13-811_V3.0 Dumps [Questions] Simple Strategy for Achievement
by xutehosaulle＠gmail.com 15 Apr '24

15 Apr '24

JustCerts offers three formats of actual and newest H13-811_V3.0 Exam Questions to help students customize their HCIA Cloud Service H13-811_V3.0 study experience. These real Huawei H13-811_V3.0 Dumps (Questions) are available with up to 90 days of free updates that remove post-purchase anxiety. Buy today and get free H13-811_V3.0 Dumps (Questions) updates.

1 0

Timestamps with calendarmodel other than Q1985727 and Q1985786
by Mitar 24 Mar '24

24 Mar '24

Hi! Recently, a timestamp with calendarmodel https://www.wikidata.org/wiki/Q12138 has been introduced into Wikidata: https://www.wikidata.org/w/index.php?title=Q105958428&oldid=2004936527 How is this possible? I thought that the only allowed values are Q1985727 and Q1985786? Mitar -- https://mitar.tnode.com/ https://twitter.com/mitar_m https://noc.social/@mitar

1 1

From JSON to RDF dumps
by daniel＠degu.cl 25 Feb '24

25 Feb '24

Hi all, I wonder if the Wikidata RDF dump (in https://dumps.wikimedia.org/wikidatawiki/entities/) is generated directly from the JSON dump. If this is the case, what tool used? Best Regards, Daniel

4 3

[Significant Change Announcement] Upcoming Changes to Wikibase API Modules: Addition of New Parameters
by Mohammed Sadat Abdulai 19 Feb '24

19 Feb '24

*(apologies for cross-posting)* Hello, This is a significant change announcement relevant for some Wikibase API users. What's Changing? Over the coming weeks, most Wikibase API modules will gain three new parameters: returnto, returntoquery, and returntoanchor. Additionally, these API modules may return tempusercreated and tempuserredirect fields in their responses. These parameters are being added to support user interaction flows related to IP Masking <https://meta.wikimedia.org/wiki/IP_Editing:_Privacy_Enhancement_and_Abuse_M…> . Who’s Affected? Only users who use the API to make anonymous edits are affected. If you don’t use the API to make edits, or if you only make authenticated edits, you can safely ignore these changes, and disregard the additional API parameters and response data. What You Need to Do If you use the API to make anonymous edits, the response may contain a tempusercreated string indicating the name of the temporary account that was created, and a tempuserredirect nullable string. If the tempuserredirect is not null, you should redirect the user to that URL to complete the setup for the temporary account. Afterwards, the user will automatically be returned to the current wiki; you can use the returnto, returntoquery, and/or returntoanchor parameters in your original API request to control the title, query, and anchor where the redirect returns to. If you have any questions or concerns about this change, please don’t hesitate to reach out to us in this ticket (T357024 <https://phabricator.wikimedia.org/T357024>). Cheers, -- Mohammed S. Abdulai *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. A lot is happening around Wikidata - Keep up to date! <https://www.wikidata.org/wiki/Wikidata:Status_updates> 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 Charlottenburg, VR 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207. Geschäftsführende Vorstände: Franziska Heine, Dr. Christian Humborg

1 0

Wikibase/Wikidata Database Technologies and Strategies
by Elton Figueiredo de Souza Soares 02 Feb '24

02 Feb '24

Dear Wikibase/Wikidata Community, We are trying to understand which database technologies and strategies Wikibase/Wikidata uses for storing, updating, and querying the data (knowledge) it manipulates. By looking at the documentation<https://wmde.github.io/wikidata-wikibase-architecture/assets/img/03-dataflo…> we understood that RDF is only used for the Wikidata Query Service, but we could not find out exactly how Wikibase/Wikidata stores the information that is translated to RDF during the data dump. More specifically, we understood that a MySQL (or is it MariaDB?) relational database is used as the key persistence component for most of Wikibase/Wikidata services and that the information that is maintained in this database is periodically exported to multiple formats, including RDF. In addition, looking at the relational database schema published in the documentation<https://www.mediawiki.org/wiki/Manual:Database_layout> we could not locate tables that are easily mappable to the Wikibase Data Model<https://www.mediawiki.org/wiki/Wikibase/DataModel>. Thus, we hypothesize that there is some software component (Wikibase Common Data Access?) that dynamically translates the data contained in those tables to Statements, Entities, etc. Is that hypothesis, correct? If yes, does this software component uses any intermediate storage mechanism for caching those Statements, Entities, ...? Or are those translations always performed at runtime on-the-fly (be it for querying, adding, or updating Statements, Entities, …)? Finally, we would like to understand more about how Wikidata REST API<https://www.wikidata.org/wiki/Wikidata:REST_API> is implemented: • In which database are the statements that added/retrieved through it stored? Is it being stored in the central MySQL database or in another database? • Does it have any support for pagination of statements? For example, if an item has many statements associated with a property, does the API assumes that both the underlying database and the network will support the retrieval of all those statements? • Are you currently considering implementing the support for more flexible querying of statements, or such requirement has been fully delegated to the Wikidata Query Service? If there is an updated documentation that could help us answer those questions, could you kindly point us to it? Otherwise, would you be able to share this information with us? Best Regards, Elton F. de S. Soares Advisory Software Engineer Rio de Janeiro, RJ, Brazil IBM Research E-mail: eltons(a)ibm.com<mailto:eltons@ibm.com>

2 2

Wikidata Database Technologies/Techniques
by Elton Figueiredo de Souza Soares 01 Feb '24

01 Feb '24

Dear Wikidata Community, We are trying to understand which database technologies and strategies Wikidata uses for storing, updating, and querying the data (knowledge) it manipulates. By looking at the documentation<https://wmde.github.io/wikidata-wikibase-architecture/assets/img/03-dataflo…> we understood that RDF is only used for the Wikidata Query Service, but we could not find out exactly how Wikidata stores the information that is translated to RDF during the data dump. More specifically, we understood that a MySQL (or is it MariaDB?) relational database is used as the key persistence component for most of Wikidata services and that the information that is maintained in this database is periodically exported to multiple formats, including RDF. In addition, looking at the relational database schema published in the documentation<https://www.mediawiki.org/wiki/Manual:Database_layout> we could not locate tables that are easily mappable to the Wikibase Data Model<https://www.mediawiki.org/wiki/Wikibase/DataModel>. Thus, we hypothesize that there is some software component (Wikibase Common Data Access?) that dynamically translates the data contained in those tables to Statements, Entities, etc. Is that hypothesis, correct? If yes, does this software component uses any intermediate storage mechanism for caching those Statements, Entities, ...? Or are those translations always performed at runtime on-the-fly (be it for querying, adding, or updating Statements, Entities, …)? Finally, we would like to understand more about how Wikidata REST API<https://www.wikidata.org/wiki/Wikidata:REST_API> is implemented: * In which database are the statements that added/retrieved through it stored? Is it being stored in the central MySQL database or in another database? * Does it have any support for pagination of statements? For example, if an item has many statements associated with a property, does the API assumes that both the underlying database and the network will support the retrieval of all those statements? * Are you currently considering implementing the support for more flexible querying of statements, or such requirement has been fully delegated to the Wikidata Query Service? If there is an updated documentation that could help us answer those questions, could you kindly point us to it? Otherwise, would you be able to share this information with us? Best Regards, Elton F. de S. Soares Advisory Software Engineer Rio de Janeiro, RJ, Brazil IBM Research E-mail: eltons(a)ibm.com<mailto:eltons@ibm.com>

1 0

[Breaking Change Announcement] Empty Senses / Forms Lists Presentation in Lexeme Dumps
by Mohammed Sadat Abdulai 24 Jan '24

24 Jan '24

(*apologies for cross-posting*) Hello, This is a breaking change announcement relevant to those working with Lexeme dumps. In Lexeme dumps, "senses" and "forms" values, when not empty, are shown as arrays. When these lists are empty, they are currently displayed as objects. For example, values with content are displayed in array format: "senses":[{"id":"L4-S1",...] but empty values are treated as objects: "senses":{} However, empty lists should be presented as arrays as well: "senses":[] In this change, empty lists of forms and senses will be switched from objects to arrays. This adjustment makes the dumps more consistent and matches the same way non-empty values are presented. We will roll this change out on February 8th. We anticipate the impact of this change to be minimal and harmless for most use cases. Therefore, we haven't generated a test dump, as it would demand substantial resources and time. If you have any questions or concerns about this change, please don’t hesitate to reach out to us in this ticket ( T305660 <https://phabricator.wikimedia.org/T305660>). Cheers, -- Mohammed S. Abdulai *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. A lot is happening around Wikidata - Keep up to date! <https://www.wikidata.org/wiki/Wikidata:Status_updates> 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 Charlottenburg, VR 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207. Geschäftsführende Vorstände: Franziska Heine, Dr. Christian Humborg

1 0

MediaWiki in the age of AI - Keynote by Markus Krötzsch
by Bernhard Krabina, KM-A 04 Dec '23

04 Dec '23

Dear Wikidata community, we are happy to announce that Markus Krötzsch will be joining us in Paderborn for the keynote talk at SMWCon 2023! In this talk, Markus will provide a personal perspective on the origins and principles of semantic wikis, and some of the key challenges that lie ahead in managing knowledge in the age of A! Don't miss it - you can still attend in person, or follow the conference via YouTube or Zoom. https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2023 I you have not already participated in our __community survey__, please do so until this Wednesday. It is important for us to learn more about your SMW usage. Results will be presented next Tuesday. We thank this year's conference sponsors: ArchiXL: http://www.archixl.nl/ Specialists in enterprise architecture, knowledge management, and semantics Hallo Welt!: https://bluespice.com/ The company behind BlueSpice, the open-source enterprise wiki software MyWikis Europe: https://mywikis.eu/ GDPR compliant (Semantic) MediaWiki hosting from the heart of Europe. Wikibase Solutions: https://wikibase-solutions.com/ Specialist in business solutions with MediaWiki As well as the conference organizers MediaWiki Stakeholders' Group: https://mwstake.org/ Advocating the needs of MediaWiki users outside the Wikimedia Foundation KM-A Knowledge Management Associates: https://km-a.net/ KM-A educates and advises Knowledge Managers and connects the KM Community in Austria and the world. Paderborn University: https://www.uni-paderborn.de/en/ While always keeping society's needs in mind, scientists at Paderborn University are working on the technologies of the future. Juggel: https://www.juggel.com/ AI supported Knowledge Management based on MediaWiki and Semantic MediaWiki Best regards, Bernhard, Ad and Tobias

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Wikidata-tech