Wikidata May 2018

wikidata@lists.wikimedia.org

48 participants
28 discussions

Wiki PageID
by Gintautas Sulskus 05 Oct '18

05 Oct '18

Hi, I have a couple of questions regarding the Wiki Page ID. Does it always stay unique for the page, where the page itself is just a placeholder for any kind of information that might change over time? Consider the following cases: 1. The first time someone creates page "Moon" it is assigned ID=1. If at some point the page is renamed to "The_Moon", the ID=1 remains intact. Is this correct? 2. What if we have page "Moon" with ID=1. Someone creates a second-page "The_Moon" with ID=2. Is it possible that page "Moon" is transformed into a redirect? Then, "Moon" would be redirecting to page "The_Moon"? 3. Is it possible for page "Moon" to become a category "Category:Moon" with the same ID=1? Thanks, Gintas

7 11

Wikidata HDT dump
by Laura Morales 02 Oct '18

02 Oct '18

Hello everyone, I'd like to ask if Wikidata could please offer a HDT [1] dump along with the already available Turtle dump [2]. HDT is a binary format to store RDF data, which is pretty useful because it can be queried from command line, it can be used as a Jena/Fuseki source, and it also uses orders-of-magnitude less space to store the same data. The problem is that it's very impractical to generate a HDT, because the current implementation requires a lot of RAM processing to convert a file. For Wikidata it will probably require a machine with 100-200GB of RAM. This is unfeasible for me because I don't have such a machine, but if you guys have one to share, I can help setup the rdf2hdt software required to convert Wikidata Turtle to HDT. Thank you. [1] http://www.rdfhdt.org/ [2] https://dumps.wikimedia.org/wikidatawiki/entities/

15 81

Re: [Wikidata] [Wikimedia-l] Solve legal uncertainty of Wikidata
by Denny Vrandečić 08 Jul '18

08 Jul '18

Rob Speer wrote: > The result of this, by the way, is that commercial entities sell modified > versions of Wikidata with impunity. It undermines the terms of other > resources such as DBPedia, which also contains facts extracted from > Wikipedia and respects its Share-Alike terms. Why would anyone use DBPedia > and have to agree to share alike, when they can get similar data from > Wikidata which promises them it's CC-0? The comparison to DBpedia is interesting: the terms for DBpedia state "Attribution in this case means keep DBpedia URIs visible and active through at least one (preferably all) of @href, <link />, or "Link:". If live links are impossible (e.g., when printed on paper), a textual blurb-based attribution is acceptable." http://wiki.dbpedia.org/terms-imprint So according to these terms, when someone displays data from DBpedia, it is entirely sufficient to attribute DBpedia. What that means is that DBpedia follows exactly the same theory as Wikidata: it is OK to extract data from Wikipedia and republish it as your own dataset under your own copyright without requiring attribution to the original source of the extraction. (A bit more problematic might be the fact that DBpedia also republishes whole paragraphs of Text under these terms, but that's another story) My understanding is that all that Wikidata has extracted from Wikipedia is non-copyrightable in the first place and thus republishing it under a different license (or, as in the case of DBpedia for simple triples, with a different attribution) is legally sound. If there is disagreement with that, I would be interested which content exactly is considered to be under copyright and where license has not been followed on Wikidata. For completion: the discussion is going on in parallel on the Wikidata project chat and in Phabricator: https://phabricator.wikimedia.org/T193728#4212728 https://www.wikidata.org/wiki/Wikidata:Project_chat#Wikipedia_and_other_Wik… I would appreciate if we could keep the discussion in a single place. Gnom1 on Phabricator has offered to actually answer legal questions, but we need to come up with the questions that we want to ask. If it should be, for example, as Rob Speer states on the bug, "has the copyright of interwiki links been breached by having them be moved to Wikidata?", I'd be quite happy with that question - if that's the disagreement, let us ask Legal help and see if my understanding or yours is correct. Does this sound like a reasonable question? Or which other question would you like to ask instead? On Thu, May 17, 2018 at 4:15 PM Rob Speer <rob(a)luminoso.com> wrote: > > As always, copyright is predatory. As we can prove that copyright is the > enemy of science and knowledge > > Well, this kind of gets to the heart of the issue, doesn't it. > > I support the Creative Commons license, including the share-alike term, > which requires copyright in order to work, and I've contributed to multiple > Wikimedia projects with the understanding that my work would be protected > by CC-By-SA. > > Wikidata is engaged in a project-wide act of disobedience against CC-By-SA. > I would say that GerardM has provided an excellent summary of the attitude > toward Creative Commons that I've encountered on Wikidata: "it's holding us > back", "it's the enemy", "you can't copyright knowledge", "you can't make > us follow it", etc. > > The result of this, by the way, is that commercial entities sell modified > versions of Wikidata with impunity. It undermines the terms of other > resources such as DBPedia, which also contains facts extracted from > Wikipedia and respects its Share-Alike terms. Why would anyone use DBPedia > and have to agree to share alike, when they can get similar data from > Wikidata which promises them it's CC-0? > > On Wed, 16 May 2018 at 21:43 Gerard Meijssen <gerard.meijssen(a)gmail.com> > wrote: > > > Hoi, > > Thank you for the overly broad misrepresentation. As always, copyright is > > predatory. As we can prove that copyright is the enemy of science and > > knowledge we should not be upset that *copyright *is abused we should > > welcome it as it proves the point. Also when we use texts from everywhere > > and rephrase it in Wikipedia articles "we" are not lily white either. > > > > In "them old days" generally we felt that when people would use > Wikipedia, > > it would only serve our purpose; share the sum of all knowledge. I still > > feel really good about that. And, it has been shown that what we do; > > maintain / curate / update that data that it is not easily given to do as > > well as "we" do it. > > > > When we are to be more precise with our copyright, there are a few things > > we could do to make copyright more transparent. When data is to be > uploaded > > (Commons / Wikipedia or Wikidata) we should use a user that is OWNED and > > operated by the copyright holder. The operation may be by proxy and as a > > consequence there is no longer a question about copyright as the > copyright > > holder can do as we wants. This makes any future noises just that, > > annoying. > > > > As to copyright on Wikidata, when you consider copyright using data from > > Wikipedia. The question is: "What Wikipedia" I have copied a lot of data > > from several Wikipedias and believe me, from a quality point of view > there > > is much to be gained by using Wikidata as an instrument for good because > it > > is really strong in identifying friends and false friends. It is superior > > as a tool for disambiguation. > > > > About the copyright on data, the overriding question with data is: do you > > copy data wholesale in Wikidata. That is what a database copyright is > > about. As I wrote on my blog [1], the best data to include is data that > is > > corroborated by the fact that it is present in multiple sources. This > > negates the notion of a single source, it also underscores that much of > the > > data everywhere is replicated a lot. It also underscores, again, the > notion > > that data that is only present in single sources is what needs attention. > > It needs tender loving care, it needs other sources to establish > > credentials. That is in its own right what makes any claim of copyright > > moot. It is in this process that it becomes a "creative" process negating > > the copyright held on databases. > > > > I welcome the attention that is given to copyright in Wikidata. However > our > > attention to copyright is predatory in two ways. It is how can we get > > around existing copyright and how can we protect our own. As argued, > > Wikidata shines when it is used for what it is intended to be; the place > > that brings data, of Wikipedias first and elsewhere second, together to > be > > used as a repository of quality, open and linked data. > > Thanks, > > GerardM > > > > [1] > > > > > https://ultimategerardm.blogspot.nl/2018/05/wikidata-copyright-and-linked-d… > > > > On 11 May 2018 at 23:10, Rob Speer <rob(a)luminoso.com> wrote: > > > > > Wow, thanks for the heads up. When I was getting upset about projects > > that > > > change the license on Wikimedia content and commercialize it, I had no > > idea > > > that Wikidata was providing them the cover to do so. The Creative > Commons > > > violation is coming from inside the house! > > > > > > On Tue, 8 May 2018 at 03:48 mathieu stumpf guntz < > > > psychoslave(a)culture-libre.org> wrote: > > > > > > > Hello everybody, > > > > > > > > There is a phabricator ticket on Solve legal uncertainty of Wikidata > > > > <https://phabricator.wikimedia.org/T193728> that you might be > > interested > > > > to look at and participate in. > > > > > > > > As Denny suggested in the ticket to give it more visibility through > the > > > > discussion on the Wikidata chat > > > > < > > > > https://www.wikidata.org/wiki/Wikidata:Project_chat# > > > Importing_datasets_under_incompatible_licenses>, > > > > > > > > I thought it was interesting to highlight it a bit more. > > > > > > > > Cheers > > > > > > > > _______________________________________________ > > > > Wikimedia-l mailing list, guidelines at: > > > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > > > > https://meta.wikimedia.org/wiki/Wikimedia-l > > > > New messages to: Wikimedia-l(a)lists.wikimedia.org > > > > Unsubscribe: > https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > > > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> > > > _______________________________________________ > > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ > > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/ > > > wiki/Wikimedia-l > > > New messages to: Wikimedia-l(a)lists.wikimedia.org > > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> > > _______________________________________________ > > Wikimedia-l mailing list, guidelines at: > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > > https://meta.wikimedia.org/wiki/Wikimedia-l > > New messages to: Wikimedia-l(a)lists.wikimedia.org > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> > _______________________________________________ > Wikimedia-l mailing list, guidelines at: > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > https://meta.wikimedia.org/wiki/Wikimedia-l > New messages to: Wikimedia-l(a)lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>

10 12

Re: [Wikidata] [Wikimedia-l] Solve legal uncertainty of Wikidata
by Info WorldUniversity 04 Jul '18

04 Jul '18

Hi Mathieu, Rob, Denny, and Wikidatans, I'm writing to inquire about further Wikidata CC licensing clarifications. Wikidata may be heading to https://creativecommons.org/licenses/by-sa/4.0/ which allows for a) sharing b) adapting and even c) commercially MIT OCW uses, by way of comparison, https://creativecommons.org/licenses/by-nc-sa/4.0/ which allows for a) sharing b) adapting but c) non-commercially At a Wikimedia conference in early 2017, with Lydia and Dario present, I think I learned that all books / WikiCitations in all 301 of Wikipedia languages could be licensed, or heading to be licensed, with CC-0 licensing - https://creativecommons.org/share-your-work/public-domain/cc0/ - and per - https://phabricator.wikimedia.org/T193728 - which would allow them to be data sources for online bookstores even. Is this the case. Could some of Wikidata's data be licensed with CC-SA-4 ( https://creativecommons.org/licenses/by-sa/4.0/) and other data be licensed with CC-0? Thanks. Cheers, Scott On Thu, May 17, 2018 at 8:39 AM, Rob Speer <rob(a)luminoso.com> wrote: > > As always, copyright is predatory. As we can prove that copyright is the > enemy of science and knowledge > > Well, this kind of gets to the heart of the issue, doesn't it. > > I support the Creative Commons license, including the share-alike term, > which requires copyright in order to work, and I've contributed to multiple > Wikimedia projects with the understanding that my work would be protected > by CC-By-SA. > > Wikidata is engaged in a project-wide act of disobedience against CC-By-SA. > I would say that GerardM has provided an excellent summary of the attitude > toward Creative Commons that I've encountered on Wikidata: "it's holding us > back", "it's the enemy", "you can't copyright knowledge", "you can't make > us follow it", etc. > > The result of this, by the way, is that commercial entities sell modified > versions of Wikidata with impunity. It undermines the terms of other > resources such as DBPedia, which also contains facts extracted from > Wikipedia and respects its Share-Alike terms. Why would anyone use DBPedia > and have to agree to share alike, when they can get similar data from > Wikidata which promises them it's CC-0? > > On Wed, 16 May 2018 at 21:43 Gerard Meijssen <gerard.meijssen(a)gmail.com> > wrote: > > > Hoi, > > Thank you for the overly broad misrepresentation. As always, copyright is > > predatory. As we can prove that copyright is the enemy of science and > > knowledge we should not be upset that *copyright *is abused we should > > welcome it as it proves the point. Also when we use texts from everywhere > > and rephrase it in Wikipedia articles "we" are not lily white either. > > > > In "them old days" generally we felt that when people would use > Wikipedia, > > it would only serve our purpose; share the sum of all knowledge. I still > > feel really good about that. And, it has been shown that what we do; > > maintain / curate / update that data that it is not easily given to do as > > well as "we" do it. > > > > When we are to be more precise with our copyright, there are a few things > > we could do to make copyright more transparent. When data is to be > uploaded > > (Commons / Wikipedia or Wikidata) we should use a user that is OWNED and > > operated by the copyright holder. The operation may be by proxy and as a > > consequence there is no longer a question about copyright as the > copyright > > holder can do as we wants. This makes any future noises just that, > > annoying. > > > > As to copyright on Wikidata, when you consider copyright using data from > > Wikipedia. The question is: "What Wikipedia" I have copied a lot of data > > from several Wikipedias and believe me, from a quality point of view > there > > is much to be gained by using Wikidata as an instrument for good because > it > > is really strong in identifying friends and false friends. It is superior > > as a tool for disambiguation. > > > > About the copyright on data, the overriding question with data is: do you > > copy data wholesale in Wikidata. That is what a database copyright is > > about. As I wrote on my blog [1], the best data to include is data that > is > > corroborated by the fact that it is present in multiple sources. This > > negates the notion of a single source, it also underscores that much of > the > > data everywhere is replicated a lot. It also underscores, again, the > notion > > that data that is only present in single sources is what needs attention. > > It needs tender loving care, it needs other sources to establish > > credentials. That is in its own right what makes any claim of copyright > > moot. It is in this process that it becomes a "creative" process negating > > the copyright held on databases. > > > > I welcome the attention that is given to copyright in Wikidata. However > our > > attention to copyright is predatory in two ways. It is how can we get > > around existing copyright and how can we protect our own. As argued, > > Wikidata shines when it is used for what it is intended to be; the place > > that brings data, of Wikipedias first and elsewhere second, together to > be > > used as a repository of quality, open and linked data. > > Thanks, > > GerardM > > > > [1] > > > > https://ultimategerardm.blogspot.nl/2018/05/wikidata- > copyright-and-linked-data.html > > > > On 11 May 2018 at 23:10, Rob Speer <rob(a)luminoso.com> wrote: > > > > > Wow, thanks for the heads up. When I was getting upset about projects > > that > > > change the license on Wikimedia content and commercialize it, I had no > > idea > > > that Wikidata was providing them the cover to do so. The Creative > Commons > > > violation is coming from inside the house! > > > > > > On Tue, 8 May 2018 at 03:48 mathieu stumpf guntz < > > > psychoslave(a)culture-libre.org> wrote: > > > > > > > Hello everybody, > > > > > > > > There is a phabricator ticket on Solve legal uncertainty of Wikidata > > > > <https://phabricator.wikimedia.org/T193728> that you might be > > interested > > > > to look at and participate in. > > > > > > > > As Denny suggested in the ticket to give it more visibility through > the > > > > discussion on the Wikidata chat > > > > < > > > > https://www.wikidata.org/wiki/Wikidata:Project_chat# > > > Importing_datasets_under_incompatible_licenses>, > > > > > > > > I thought it was interesting to highlight it a bit more. > > > > > > > > Cheers > > > > > > > > _______________________________________________ > > > > Wikimedia-l mailing list, guidelines at: > > > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > > > > https://meta.wikimedia.org/wiki/Wikimedia-l > > > > New messages to: Wikimedia-l(a)lists.wikimedia.org > > > > Unsubscribe: https://lists.wikimedia.org/ > mailman/listinfo/wikimedia-l, > > > > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> > > > _______________________________________________ > > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ > > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/ > > > wiki/Wikimedia-l > > > New messages to: Wikimedia-l(a)lists.wikimedia.org > > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> > > _______________________________________________ > > Wikimedia-l mailing list, guidelines at: > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > > https://meta.wikimedia.org/wiki/Wikimedia-l > > New messages to: Wikimedia-l(a)lists.wikimedia.org > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> > _______________________________________________ > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/ > wiki/Wikimedia-l > New messages to: Wikimedia-l(a)lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> > -- -- - Scott MacLeod - Founder & President - https://twitter.com/WorldUnivAndSch - World University and School - http://worlduniversityandschool.org - http://scottmacleod.com - CC World University and School - like CC Wikipedia with best STEM-centric CC OpenCourseWare - incorporated as a nonprofit university and school in California, and is a U.S. 501 (c) (3) tax-exempt educational organization.

4 3

IRC office hour today
by Léa Lacroix 29 May '18

29 May '18

Hello all, As a reminder, we will have an office hour today, from 18:00 to 19:00 (UTC+2, Berlin time <https://www.timeanddate.com/worldclock/converter.html?iso=20180529T160000&p…>). It will take place on the channel #wikimedia-office. First, we will present what the Wikidata development team has been working on during the last months, and collect your questions and feedback. The second part will be dedicated to lexicographical data on Wikidata, and the first release that happened last week. We will give some news but again, keep time for your questions and suggestions. See you there! -- 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.

1 1

Weekly Summary #314
by Léa Lacroix 28 May '18

28 May '18

*Here's your quick overview of what has been happening around Wikidata over the last week.* Discussions - Closed request for adminship: Pintoch <https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Administrat…>, Addshore <https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Administrat…> (both successful) - New request for comments: Why do we have an item for dogs and another one for *Canis lupus familiaris*? <https://www.wikidata.org/wiki/Wikidata:Requests_for_comment/Why_do_we_have_…> Events <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Events> - IRC office hour, on May 29th at 18:00 (UTC+2, Berlin time), on the IRC channel #wikimedia-office. Special topic: Lexemes on Wikidata Press, articles, blog posts <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Press_coverage> - Paper on Cellosaurus <https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5945021/>, with mappings to Wikidata, by Amos Bairoch - Blog post from Galder Gonzalez announcing the Lexemes <http://wikimedia.eus/2018/05/jcioqetik-171081era-informazio-lexikografikoa-…> (in Basque) Other Noteworthy Stuff - Ongoing: On 24 May, there was a significant outage affecting Wikidata and sister projects that use Wikidata. As a result, some features of are temporarily disabled: Wikidata's property suggester, Lua modules and parser functions calling by label instead of ID, search for the ArticlePlaceholder. We apologize for the inconvenience, we're working to get them back as soon as possible. For technical details, see: phab:T195520 <https://phabricator.wikimedia.org/T195520> & Incident documentation/20180524-wikidata <https://wikitech.wikimedia.org/wiki/Incident_documentation/20180524-wikidata> . - As announced last week <https://www.wikidata.org/wiki/Wikidata:Project_chat#New_constraint_types>, the “integer <https://www.wikidata.org/wiki/Help:Property_constraints_portal/Integer>” constraint type and the “separators <https://www.wikidata.org/wiki/Property:P4155>” parameter for the “single value <https://www.wikidata.org/wiki/Help:Property_constraints_portal/Single_value>” and “single best value <https://www.wikidata.org/wiki/Help:Property_constraints_portal/Single_best_…>” constraint types are now supported in WikibaseQualityConstraints. - Lexicographical data is now available on Wikidata! Check the announcement <https://www.wikidata.org/wiki/Wikidata_talk:Lexicographical_data#First_expe…> for more details. Feel free to try adding words and give feedback - Structured Data on Commons has designs for displaying and using multilingual captions on the file page <https://commons.wikimedia.org/wiki/Commons:Structured_data/Get_involved/Fee…>. Feedback is welcome on the talk page. - You can try the new Drag&Drop gadget developed by Yarl <https://www.wikidata.org/wiki/Wikidata:Project_chat#Drag'n'drop_gadget_rewrite_–_feedback_welcomed> and give feedback - The European Commission announces a review <https://www.communia-association.org/2018/05/10/database-directive-study-op…> of the Database Directive <https://en.wikipedia.org/wiki/en:Database_Directive>. - OpenRefine 3.0 beta <https://github.com/OpenRefine/OpenRefine/releases> was released. You can get an overview of the new Wikidata-related features <https://www.wikidata.org/wiki/Wikidata:Tools/OpenRefine/Editing> with tutorials and videos. - TextRazor <https://www.textrazor.com/> (Q54365914 <https://www.wikidata.org/wiki/Q54365914>) is a web service which analyses text and identifies the entities and concepts discussed, giving the corresponding Wikidata QIDs. Did you know? - Newest properties <https://www.wikidata.org/wiki/Special:ListProperties>: - General datatypes: grammatical gender <https://www.wikidata.org/wiki/Property:P5185>, conjugation class <https://www.wikidata.org/wiki/Property:P5186>, word stem <https://www.wikidata.org/wiki/Property:P5187>, Sandbox-Lexeme <https://www.wikidata.org/wiki/Property:P5188>, Sandbox-Form <https://www.wikidata.org/wiki/Property:P5189>, synonym <https://www.wikidata.org/wiki/Property:P5190>, derived from <https://www.wikidata.org/wiki/Property:P5191>, Wikidata property example for lexemes <https://www.wikidata.org/wiki/Property:P5192>, Wikidata property example for forms <https://www.wikidata.org/wiki/Property:P5193>, officialized by <https://www.wikidata.org/wiki/Property:P5194>, Wikidata dataset import page <https://www.wikidata.org/wiki/Property:P5195>, output method <https://www.wikidata.org/wiki/Property:P5196>, IMDA rating <https://www.wikidata.org/wiki/Property:P5201>, adapted by <https://www.wikidata.org/wiki/Property:P5202>, topographic map <https://www.wikidata.org/wiki/Property:P5203>, date of commercialization <https://www.wikidata.org/wiki/Property:P5204>, stroke count <https://www.wikidata.org/wiki/Property:P5205>, has conjugation class <https://www.wikidata.org/wiki/Property:P5206> - External identifiers: CIVICUS Monitor country entry <https://www.wikidata.org/wiki/Property:P5180>, Relationship Science organization ID <https://www.wikidata.org/wiki/Property:P5181>, JMA Seismic Intensity Database ID <https://www.wikidata.org/wiki/Property:P5182>, Eurohockey.com club ID <https://www.wikidata.org/wiki/Property:P5183>, Daum Encyclopedia ID <https://www.wikidata.org/wiki/Property:P5184>, Melon song ID <https://www.wikidata.org/wiki/Property:P5197>, ASC Leiden Thesaurus ID <https://www.wikidata.org/wiki/Property:P5198>, British Library system number <https://www.wikidata.org/wiki/Property:P5199>, eBird hotspot ID <https://www.wikidata.org/wiki/Property:P5200>, BAG public space ID <https://www.wikidata.org/wiki/Property:P5207>, BAG building ID <https://www.wikidata.org/wiki/Property:P5208> - New property proposals <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Property_proposal> to review: - General datatypes: Vocalized form <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Vocalized_form>, display technology <https://www.wikidata.org/wiki/Wikidata:Property_proposal/display_technology>, compound of <https://www.wikidata.org/wiki/Wikidata:Property_proposal/compound_of>, Chromosome number <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Chromosome_number>, Vietnamese character reading pattern <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Vietnamese_charact…>, fanqie <https://www.wikidata.org/wiki/Wikidata:Property_proposal/fanqie>, evokes <https://www.wikidata.org/wiki/Wikidata:Property_proposal/evokes>, homograph lexeme <https://www.wikidata.org/wiki/Wikidata:Property_proposal/homograph_lexeme>, homograph form <https://www.wikidata.org/wiki/Wikidata:Property_proposal/homograph_form>, prime factor <https://www.wikidata.org/wiki/Wikidata:Property_proposal/prime_factor>, classifier <https://www.wikidata.org/wiki/Wikidata:Property_proposal/classifier>, Accomplice <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Accomplice>, Slavic Alphabet <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Slavic_Alphabet>, signum <https://www.wikidata.org/wiki/Wikidata:Property_proposal/signum> - External identifiers: BMRB ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/BMRB_ID>, ICSC ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/ICSC_ID>, Baidu Baike ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Baidu_Baike_ID>, Tree of Life Web Project ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Tree_of_Life_Web_P…>, Argentine biography deputy ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Argentine_biograph…>, B.R.A.H.M.S. ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/B.R.A.H.M.S._ID>, Chromosome numbers of the flora of Germany database ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Chromosome_numbers…>, Filmow ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Filmow_ID>, Cité de la musique ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Cit%C3%A9_de_la_mu…>, Giant Bomb ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Giant_Bomb_ID>, OpenCorporates corporate grouping <https://www.wikidata.org/wiki/Wikidata:Property_proposal/OpenCorporates_cor…>, Artists in Canada record number <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Artists_in_Canada_…>, RollDaBeats ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/RollDaBeats_ID>, Songfacts ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Songfacts_ID>, ARWU ID <https://www.wikidata.org/wiki/Wikidata:Property_proposal/ARWU_ID> - Properties not really used <https://www.wikidata.org/wiki/User:Edgars2007/Dormant_properties>, created >3 months: - Inventories of American Painting and Sculpture control number (P4814) <https://www.wikidata.org/wiki/Property:P4814>, Amtrak station code (P4803) <https://www.wikidata.org/wiki/Property:P4803>, make-up artist (P4805) <https://www.wikidata.org/wiki/Property:P4805>, sets environment variable (P4809) <https://www.wikidata.org/wiki/Property:P4809>, Technical Element Score (P4815) <https://www.wikidata.org/wiki/Property:P4815>, Rugby Australia ID (P4799) <https://www.wikidata.org/wiki/Property:P4799>, TORA ID (P4820) <https://www.wikidata.org/wiki/Property:P4820>, Panoptikum identifier (P4818) <https://www.wikidata.org/wiki/Property:P4818>, Cour des comptes magistrate ID (P4821) <https://www.wikidata.org/wiki/Property:P4821>, La Poste personality ID (P4822) <https://www.wikidata.org/wiki/Property:P4822> - Query examples: - Map of places of birth of Liverpool's football players <https://query.wikidata.org/#%0A%23defaultView%3AMap%0ASELECT%20%3Fitem%20%3…> (source <https://twitter.com/dziennikarz/status/1000433044161998850>) - Areas of Malaysia states <https://query.wikidata.org/#SELECT%20%3Fstate_of_Malaysia%20%3Fstate_of_Mal…> (source <https://twitter.com/sweemeng/status/999843265120628736>) - People and the distance between their place of birth and place of death <https://query.wikidata.org/#SELECT%20DISTINCT%20%3Fitem%20%3FitemLabel%20%3…> (source <https://twitter.com/PoulpyWP/status/999724326327857155>) - Grammatical cases of languages <https://query.wikidata.org/#SELECT%20%3Flanguage%20%3FlanguageLabel%20%28GR…> (source <https://twitter.com/WikidataFacts/status/999412738123292672>) Development - Deployed and activate WikibaseLexeme on wikidata.org so you can now store the first lexicographical data on Wikidata (phab:T191457 <https://phabricator.wikimedia.org/T191457>) - Fixing the encoding issues on labels of items linked on Lexemes ( phab:T195470 <https://phabricator.wikimedia.org/T195470>, phab:T195359 <https://phabricator.wikimedia.org/T195359>) - Fixed an issue that was preventing adding Forms and Lexemes in statements (phab:T195402 <https://phabricator.wikimedia.org/T195402>) - Suppressed the browser's autocomplete that covers WikibaseLexeme's suggestion on Special:NewLexeme (phab:T195383 <https://phabricator.wikimedia.org/T195383>, phab:T191526 <https://phabricator.wikimedia.org/T191526>) - Worked on a bug about representation overwriting other representation with the same language code (phab:T193636 <https://phabricator.wikimedia.org/T193636>) - Changed title of the field of a lemma language to make it less likely for people to add a translation as a second Lemma (phab:T193603 <https://phabricator.wikimedia.org/T193603>) - Working on the RDF mapping of WikibaseLexeme (phab:T160260 <https://phabricator.wikimedia.org/T160260>) - Working on implementing fulltext search for Lexemes (phab:T189739 <https://phabricator.wikimedia.org/T189739>) - Working on showing Lemmas for linked Lexemes instead of just their ID on special pages like Special:AllPages (phab:T195382 <https://phabricator.wikimedia.org/T195382>) - Fixing issues that happened after dropping an index from the wb_terms table (phab:T194270 <https://phabricator.wikimedia.org/T194270>, phab:T195642 <https://phabricator.wikimedia.org/T195642>, phab:T195611 <https://phabricator.wikimedia.org/T195611>) - Made constraint check result appear directly after adding a new statement (phab:T194247 <https://phabricator.wikimedia.org/T194247>) - Working on looking up entities by external identifiers on Special:Search (phab:T99899 <https://phabricator.wikimedia.org/T99899>) - Added Docker image to Wikibase website (phab:T189936 <https://phabricator.wikimedia.org/T189936>) - Added WikibaseImport script to Docker images to make it easier for people to start their own Wikibase install with some data imported from Wikidata (phab:T192080 <https://phabricator.wikimedia.org/T192080>) You can see all open tickets related to Wikidata here <https://phabricator.wikimedia.org/maniphest/query/4RotIcw5oINo/#R>. If you want to help, you can also have a look at the tasks needing a volunteer <https://phabricator.wikimedia.org/project/board/71/query/zfiRgTnZF7zu/?filt…> . Monthly Tasks - Add labels, in your own language(s), for the new properties listed above. - Comment on property proposals: all open proposals <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Overview> - Suggested and open tasks <https://www.wikidata.org/wiki/Wikidata:Contribute/Suggested_and_open_tasks> ! - Contribute to a Showcase item <https://www.wikidata.org/wiki/Special:MyLanguage/Wikidata:Showcase_items> . - Help translate <https://www.wikidata.org/wiki/Special:LanguageStats> or proofread the interface and documentation pages, in your own language! - Help merge identical items <https://www.wikidata.org/wiki/User:Pasleim/projectmerge> across Wikimedia projects. - Help write the next summary! <https://www.wikidata.org/wiki/Wikidata:Status_updates/Next> -- 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.

1 0

digital personal bibliography
by Andreas Dittrich 25 May '18

25 May '18

Dear List, currently I am working on a digital bibliography of all published texts by the Austrian writer Ilse Aichinger. My intention is to make this list publicly available as a digitally structured database. I found that wikidata could be the right place for this. (Am I right?) At first I wanted to use the FRBR vocabulary to describe the relations between the texts, but librarians recommended to use BIBFRAME, as this seems to get to be the standard vocabulary – and wikidata also uses this vocabulary, as I learned from the wikidata-project group Wikidata:WikiProject_Books <https://www.wikidata.org/wiki/Wikidata:WikiProject_Books>. --- Currently I am recording the bibliographic units locally in BIBTEX format (because I started in this format). Later on I will transform the dataset to BIBFRAME and the wikidata-bibframe-vocabulary so that I can load it to wikidata. Now I would like to ask you: Are there comparable, perhaps even exemplary projects for bibliographies on wikidata? Which ones? Should I suggest or announce the project somewhere? Do you have recommendations regarding the workflow (e.g. is quickstatements <https://tools.wmflabs.org/quickstatements>-tool the best way to push my data to wikidata)? Is someone here with experience regarding building a bibliography in wikidata? With best regards, Andrew

3 4

First experiment of lexicographical data is out
by Léa Lacroix 24 May '18

24 May '18

Hello all, After several years discussing about it, and one year of development and discussion with the communities, the development team has now released the first version of lexicographical data support on Wikidata <https://www.wikidata.org/wiki/Wikidata:Lexicographical_data>. Since the start of Wikidata in 2012, the multilingual knowledge base was mainly focused on concepts: Q-items are related to a thing or an idea, not to the word describing it. Starting now, Wikidata stores a new type of data: words, phrases and sentences, in many languages, described in many languages. This information will be stored in new types of entities, called Lexemes, Forms and Senses. It will allow editors to describe precisely all words in all languages, and will be reusable, just like the whole content of Wikidata, by multiple tools and queries, everything that the community creates to play with words. Lexicographical data can be reused inside and outside the Wikimedia projects, and can provide support for Wiktionary. The first release A new namespace and several new entity types have been created in order to model words and phrases. If you’re new to this project, you can learn more by looking at the documentation <https://www.wikidata.org/wiki/Wikidata:Lexicographical_data/Documentation>, briefly describing the data model and the interface. The technical structure is set, but the editors remain free to model and organize data as they prefer, with the usual open discussions and community processes that we apply on Wikidata. Some discussions about new properties <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Lexemes> to create have already started: if you want to be involved in the early stage of the project to shape it, please participate! Please note that the version that is now deployed is a first experiment, that will be continuously improved in the future. Some features are missing, some bugs may certainly occur. Here are the features that are included in the first release: - Add, edit and delete Lexemes, Forms, statements, qualifiers, references - Link between the different entity types (Item to Lexeme, Form to Item, etc.) - Entity suggestion when adding a property or a value And the following features will not be included in the first version, but are planned for the future: - Find Lexemes and Forms via Special:Search - RDF support (which also means: the ability to query it with query.wikidata.org) - Support for Senses - Merging of Lexemes - Including the data on other Wikimedia projects, such as Wiktionary How to try it? The features described above are now deployed on Wikidata.org. Here are some suggestions of what you can do to explore this new territory: - If you’re not familiar with the structure of Lexemes, have a look at the documentation <https://www.wikidata.org/wiki/Wikidata:Lexicographical_data/Documentation> - Look at what is already existing <https://www.wikidata.org/wiki/Special:AllPages?from=&to=&namespace=146>. Please note that Special:Search and the search bar on the top right corner of pages is not supporting Lexemes yet. We’re working on this. - Create a new Lexeme with Special:NewLexeme <https://www.wikidata.org/wiki/Special:NewLexeme> - If a property that you need is missing, you can suggest it here <https://www.wikidata.org/wiki/Wikidata:Property_proposal/Lexemes> - Discuss about how to model words and ask questions on Wikidata talk:Lexicographical data - Report bugs or issues that you may encounter: either on the talk page or on Phabricator, if you’re comfortable using it (create a task, add the tag Lexicographical data, and add Lea_Lacroix_(WMDE) as a subscriber) About mass imports and tools We kindly ask you to *not plan any mass import from any source for the moment*. There are several reasons behind that: first of all, like mentioned above, the release is a first version and we need to observe how our system reacts to the manual edits before starting considering automatic ones. The system may not be ready for big massive imports at the beginning. Second reason is legal. Lexicographical data in Wikidata is released under CC0, and the responsibility of each editor is to make sure that the data they will add is compatible with CC0. For more information, you can have a look at the advice of WMF Legal team <https://meta.wikimedia.org/wiki/Wikilegal/Lexicographical_Data>. Finally, we strongly encourage you to discuss with the communities before considering any import from the Wiktionaries. Wiktionary editors have been putting a lot of efforts during years to build definitions, and we should be respectful of this work, and discuss with them to find common solutions to work on lexicographical data and enjoy the use of it together. We also suggest you to wait a bit before building tools or scripts on the top of lexicographical data. The interface and its API are probably going to evolve during the next months, and the system may not be stable enough to support such tools. We will inform you as soon as it will be possible. Next steps After this first release, some improvements will be made on a very regular basis (new deployments every week). Once you tried playing with the new data, feel free to give us feedback. We’re looking especially to know what are the most important features for you to be worked on next. - What did you experiment while editing lexicographical data? What went wrong or was unexpected? - What bugs or troubles during the process did you encounter? - What are the features that are, in your opinion, the most important? Which one should we work on next? If you’re interested in following the discussions and further announcements about lexicographical data, I encourage you to follow Wikidata:Lexicographical data <https://www.wikidata.org/wiki/Wikidata:Lexicographical_data> and its talk page, where we will discuss about how to organize and structure data, new features to be added, ideas of tools and queries, and a lot of other things. Additional note: with this new kind of data enabled on Wikidata, we expect some new editors to get interest in it, edit Lexemes, suggest properties or ask questions. They may not be familiar with all of our community processes and our ways to organize content. They will need help and support as well as links to useful resources to understand how the Wikidata community works. I hope that we will all be kind and patient, both with other editors and with the software that may not work exactly as we want it to at the beginning :) Thanks to the people who tested the model and the interface before the release, who showed support and curiosity about lexicographical data on Wikidata! If you have any question or idea, feel free to write on Wikidata talk:Lexicographical data or contact me. -- 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.

8 7

Multilingual captions designs for the file page
by Keegan Peterzell 23 May '18

23 May '18

Greetings, The draft designs for how multilingual file captions may work on the file page is up on Commons. [1] Feedback is welcome on the talk page, as well as any relevant questions. [2] Multilingual captions were first introduced back in January as a proposed change to the UploadWizard, [3] and will be one of the first features of structured data on Commons later this year. Thanks, and as always I invite you to follow along with Structured Data [4]. 1. https://commons.wikimedia.org/wiki/Commons:Structured_data/Get_involved/Fee… 2. https://commons.wikimedia.org/wiki/Commons_talk:Structured_data/Get_involve… 3. https://commons.wikimedia.org/wiki/Commons:Structured_data/Get_involved/Fee… 4. https://commons.wikimedia.org/wiki/Commons:Structured_data/Get_involved -- Keegan Peterzell Technical Collaboration Specialist Wikimedia Foundation

1 0

Weekly Summary #313
by Léa Lacroix 22 May '18

22 May '18

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Wikidata May 2018