Re: [Wikidata-l] Conflict of Interest policy for Wikidata
Also, when adding information to Wikipedia/Wikidata, it is best practice (but not mandatory) to provide external references backing up your claims. Nicolas. On Wednesday, January 7, 2015 10:26 AM, Peter F. Patel-Schneider pfpschnei...@gmail.com wrote: Wikipedia has already addressed this question. See http://en.wikipedia.org/wiki/Wikipedia:Autobiography. In summary, one should not add or change information about oneself, unless the change could not be considered to be non-controversial or there is some reason that a change should be made and the reasons for the change are laid out in a talk page. This is pretty much just the general conflict of interest guidelines applied to information about oneself, I think. There was an instance of someone writing their own Wikipedia entry. (I'm not linking to information about the issue to somewhat hide the identity of the guilty.) The end of the discussion was that the page would not be taken down. The decision hinged, in part, on how easy it would be to anonymously enter or change information about oneself, so forbidding this kind of activity is impossible to police. The best that can be done is to point out that this kind of activity is strongly discouraged. I think that the Wikipedia policy should be carried over directly to Wikidata. It lets responsible individuals fix or point out errors concerning information about them, but has strong admonitions against making any other kind of changes to this information. Peter F. Patel-Schneider On 01/07/2015 06:25 AM, Markus Krötzsch wrote: Back to Denny's original question: Does anybody see a specific danger of abuse if living people get to edit their own data right now? Entering wrong claims deliberately would maybe not be the biggest issue here (since it is already in conflict with other general policies -- we do not want wrong data, whoever is entering it -- and the fact that we want to rely on external sources for all non-obvious data would still apply). Could it be problematic if somebody enters too much/too detailed data on their own person? Could somebody use this to place links to external web content (spam) hidden in personal properties? But this, again, would probably conflict with other policies too, and it does not seem to be a problem specific to the particular POVs that a living person may have. Any other ideas of possible abuse? My main question is: where could POV be an issue when entering (externally referenced) data of the granularity that we have? Some proposals of what we could allow/forbid that are specific to our special form of content: * Allow living people to edit certain properties on their own page (whitelist)? I currently don't see any way of really abusing things like birthdate, given name, etc. that are just personal properties, unless maybe in rare cases where there is a real dispute (maybe a living person who insists on being younger than he really is?). * Alternatively, maybe it could even be enough to have a blacklist of certain properties that one could be using in illegitimate ways (no specific idea now what this might be). * I would also allow people to set their labels and reasonable aliases, but not have them enter any descriptions (could be POVed). If living people are asked to not edit all or certain parts of their entity, then there needs be a process for them to report errors. I would not like wrong information to be broadcasted about me on Wikidata without having any way to get it fixed. In addition, there should be a template that one can use on one's user page to disclose that one is the person described in a certain item. Conversely, we should also use our website account on property (P553) to connect living people to their Wikidata user account, so the COI is recorded in the data. One could further disclose other COIs on one's user page in some standard format, but maybe with Wikidata we could actually derive such COIs automatically (your family members, the companies you founded, the university you graduated from, etc. can all be specified in data). Cheers, Markus On 04.01.2015 19:57, Andy Mabbett wrote: Yes. they can. That's stated explicitly: A Wikimedia Project community may adopt an alternative paid contribution disclosure policy. If a Project adopts an alternative disclosure policy, you may comply with that policy instead of the requirements in this section when contributing to that Project. And Commons, for one, has already done so: https://commons.wikimedia.org/wiki/Commons:Paid_contribution_disclosure_policy which says in full: The Wikimedia Commons community does not require any disclosure of paid contributions from its contributors. On 4 January 2015 at 07:40, Jasper Deng jas...@jasperswebsite.com wrote: @Andy: no, the terms of use are the minimum because since a user must legally accept them when editing a project,
Re: [Wikidata-l] Wikidata RDF export available
With respect to the RDF export I'd advocate for: 1) an RDF format with one fact per line. 2) the use of a mature/proven RDF generation framework. Optimizing too early based on a limited and/or biased view of the potential use cases may not be a good idea in the long run. I'd rather keep it simple and standard at the data publishing level, and let consumers access data easily and optimize processing to their need. Also, I should not have to run a preprocessing step for filtering out the pieces of data that do not follow the standardŠ Note that I also understand the need for a format that groups every facts about an subject into one record, and serialize them one record per line. It sometime makes life easier for bulk processing of large datasets. But that's a different discussion. -- Nicolas Torzec. On 8/12/13 1:49 AM, Markus Krötzsch mar...@semantic-mediawiki.org wrote: On 11/08/13 22:29, Tom Morris wrote: On Sat, Aug 10, 2013 at 2:30 PM, Markus Krötzsch mar...@semantic-mediawiki.org mailto:mar...@semantic-mediawiki.org wrote: Anyway, if you restrict yourself to tools that are installed by default on your system, then it will be difficult to do many interesting things with a 4.5G RDF file ;-) Seriously, the RDF dump is really meant specifically for tools that take RDF inputs. It is not very straightforward to encode all of Wikidata in triples, and it leads to some inconvenient constructions (especially a lot of reification). If you don't actually want to use an RDF tool and you are just interested in the data, then there would be easier ways of getting it. A single fact per line seems like a pretty convenient format to me. What format do you recommend that's easier to process? I'd suggest some custom format that at least keeps single data values in one line. For example, in RDF, you have to do two joins to find all items that have a property with a date in the year 2010. Even with a line-by-line format, you will not be able to grep this. So I think a less normalised representation would be nicer for direct text-based processing. For text-based processing, I would probably prefer a format where one statement is encoded on one line. But it really depends on what you want to do. Maybe you could also remove some data to obtain something that is easier to process. Markus ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Linking WikiData to Freebase
Yes that was one of the issues raised in this paper: There is no money in Linked Data Prateek Jain, Pascal Hitzler, Krzysztof Janowicz, Chitra Venkatramani = http://knoesis.wright.edu/pascal/pub/nomoneylod.pdf -Nicolas. On 6/17/13 3:08 PM, Barry Norton barry.nor...@ontotext.com wrote: One can't license something for which one does/can not have the copyright. Barry On 17/06/13 23:03, Federico Leva (Nemo) wrote: Tom Morris, 15/06/2013 14:11: On Sat, Jun 15, 2013 at 3:52 AM, Federico Leva (Nemo) wrote: For a closer integration with MusicBrainz, they'd probably have to change their (non)licenses. https://en.wikipedia.org/__wiki/MusicBrainz#Licensing https://en.wikipedia.org/wiki/MusicBrainz#Licensing (They seem to claim they're free content, but they aren't.) The core MusicBrainz facts (artists, albums, tracks) are in the public domain. It's the extra stuff like user generated comments, ratings, etc that they license. Yes, but their licensing scheme is not very clear and PD is not a license. Nemo ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] Wikidata FAQ translated, and proposing my help.
Hi, Agreed, June is still far away in the future ;) - What are the specific tasks you are working on right now, and for which you would need feedback/help? - Or the ones you would like to tackle next and for which you are looking for some ahead? - Any backlog I can look up? -Nicolas. On Tue, Apr 10, 2012 at 3:03 AM, Lydia Pintscher lydia.pintsc...@wikimedia.de wrote: Hey Nicolas, On Tue, Apr 10, 2012 at 4:01 AM, Nicolas Torzec nicolas.tor...@gmail.com wrote: Dear Wikidata, I just wanted to let you know that I have spent a couple of hours translating the Wikidata FAQ into French. = See http://meta.wikimedia.org/wiki/Wikidata/FAQ/fr As I already said on Twitter: Thanks! I also went after the first Wikidata documentation and published an introduction to the project, as a proof that I did my due diligence :) = http://zecdata.com/2012/04/09/wikidata-one-common-source-of-structured-data-for-all-wikipedias Awesome. I linked it on http://meta.wikimedia.org/wiki/Wikidata/Press I would be happy to help and collaborate if needed. (I have worked on various related topics at Yahoo! Labs and other places over the past 10+ years. So I may be of some help. Feel free to look me up on LinkedIn) Sounds great. Is there anything you are particularly interested in? I just heard you'll be meeting Denny in June. That'd be a good start but it's still quite far away. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Community Communications for Wikidata Wikimedia Deutschland e.V. Eisenacher Straße 2 10777 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/681/51985. ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
[Wikidata-l] Wikidata FAQ translated, and proposing my help.
Dear Wikidata, I just wanted to let you know that I have spent a couple of hours translating the Wikidata FAQ into French. = See http://meta.wikimedia.org/wiki/Wikidata/FAQ/fr I also went after the first Wikidata documentation and published an introduction to the project, as a proof that I did my due diligence :) = http://zecdata.com/2012/04/09/wikidata-one-common-source-of-structured-data-for-all-wikipedias I would be happy to help and collaborate if needed. (I have worked on various related topics at Yahoo! Labs and other places over the past 10+ years. So I may be of some help. Feel free to look me up on LinkedIn) Best, Nicolas. [@nicolastorzec on Twitter] ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
