Hello Gregor, Thank you for your clear and convincing summary of 3rd party data licensing.
Could you or someone else on- or off-list tell me if Wikimedia is planning some sort of comprehensive technical separation of 3rd party data to ensure attribution, clearance of rights for downstream reuse etc.? My current project, www.linkedheritage.eu, is looking at this type of question right now so I'm happy to discuss. Best wishes, Michael Hopwood Linked Heritage Project Lead EDItEUR United House, North Road London N7 9DP UK Tel: +44 20 7503 6418 Mob: +44 7811 591036 Skype: michael.hopwood.editeur http://www.linkedheritage.org/ http://editeur.org/ The information contained in this e-mail is confidential and may be privileged. It is intended for the addressee only. If you are not the intended recipient, please inform the sender and delete this e-mail immediately. The contents of this e-mail must not be disclosed or copied without the sender's consent. We cannot accept any responsibility for viruses, so please scan all attachments. The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the company. EDItEUR Limited is a company limited by guarantee, registered in England no 2994705. Registered Office: United House, North Road, London N7 9DP, United Kingdom -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: 17 November 2012 12:00 To: [email protected] Subject: Wikidata-l Digest, Vol 12, Issue 10 Send Wikidata-l mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.wikimedia.org/mailman/listinfo/wikidata-l or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Wikidata-l digest..." Today's Topics: 1. Re: Wikidata license (was "Introduction and some questions on Wikidata") (Gregor Hagedorn) 2. Re: Wikidata demo repo is being spammed. (Vito) 3. weekly summary #32 (Lydia Pintscher) 4. A framework for policies & similar stuffs (Vito) 5. Property specification on-wiki (Jeroen De Dauw) 6. Re: Property specification on-wiki (Daniel Kinzler) 7. Re: Property specification on-wiki (Gregor Hagedorn) ---------------------------------------------------------------------- Message: 1 Date: Fri, 16 Nov 2012 14:06:00 +0100 From: Gregor Hagedorn <[email protected]> To: "Discussion list for the Wikidata project." <[email protected]> Subject: Re: [Wikidata-l] Wikidata license (was "Introduction and some questions on Wikidata") Message-ID: <cadcrvwzeozqwv7mduyaw_z9-dwpzejbsr5tsby-ubjzgbac...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 > Just to clarify, my concern is about externally made databases, > regardless of whether these are imported directly into Wikidata, or > have been incorporated into Wikipedia first and imported into Wikidata > from there. For example, the population data in Wikipedia's list of > ceremonial English counties > (http://en.wikipedia.org/wiki/List_of_ceremonial_counties_of_England), > which also features in the infoboxes of the articles on each county, > would I think be covered by database right under U.K law. Like other > ONS material, it has been made available under the OGL, which does > impose some obligations on re-users (somewhat similar to CC-BY). This is in interesting case. However, while the database right gives you certain rights, it does not give you a copyright (i.e. the conent may be legally problematic, but it cannot be covered by CC BY-SA). Thus, the use on Wikipedia is either exclusively licensed with an obligation to prevent re-use by third parties (which is not the case, WMF does not do this), or it is illegal, or acceptance of open re-use is an implicit waiver of database rights. I believe you can not allow it on Wikipedia but then NOT allow further reuse. However, to clarify: 1. It is much preferable to add such data to Wikidata and include their source in a structured way. Whether OGL or other licenses need to be explicitly supported by Wikidata in the future will have to be a separate discussion, on Wikidata.org. 2. My goal in participating in this discussion is to avoid the impression that re-use of Wikipedia content is not possible at all without looking at each invidivual data element and record. 3. Wikidata plans to support a hierarchy of multiple data for the same statement (multiple values from different sources for a single property in a single item). This makes it possible (although not required) to mix Wikipedia-harvested information with poor sourcing with clean, well sourced data. 4. Not harvesting from Wikipedia implies to verify that almost all information from Wikipedia is in WIkidata, but cleanly sourced, before it si possible to migrate a class of infoboxes to Wikidata. I believe this is an impossible task, making some import of Wikipedia-harvested data necessary. Where better, sourced information exist, these would take precedence. Gregor ------------------------------ Message: 2 Date: Fri, 16 Nov 2012 15:12:45 +0100 From: Vito <[email protected]> To: [email protected] Subject: Re: [Wikidata-l] Wikidata demo repo is being spammed. Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Il 16/11/2012 07:24, Katie Filbert ha scritto: > On Fri, Nov 16, 2012 at 2:40 AM, Snaevar <[email protected] > <mailto:[email protected]>> wrote: > > Hello, > > I wanted to let you guys know that there is spam being added to > items (descriptions and labels) on the demo repo. > > > Thanks for reporting this. > > I've deleted the spam. > > Cheers, > Katie > Unfortunately I already saw spambots doing sul on wikidata, so a spam attacks are at the hand. Please report any spam to stewards in order to let them check&lock everything. Vito -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.wikimedia.org/pipermail/wikidata-l/attachments/20121116/762e7ddf/attachment-0001.html> ------------------------------ Message: 3 Date: Fri, 16 Nov 2012 16:27:02 +0100 From: Lydia Pintscher <[email protected]> To: "Discussion list for the Wikidata project." <[email protected]> Subject: [Wikidata-l] weekly summary #32 Message-ID: <CABfqUgJEF=HQOZrEYK=0od2k_vhanrv8ug4er1zqltarkfg...@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Heya folks :) Here's the summary of what's been happening over the last week around Wikidata. = Development = * Implemented patching and automatic resolution of edit conflicts so you wont get as many edit conflicts anymore https://bugzilla.wikimedia.org/show_bug.cgi?id=39836 * Worked on $.valueview system for DataValues editing in the user interface * Started implementing DataType constructor in JavaScript * Added ValueValidator and ValueFormatter factory * Improvements to Diff extension * Construct PropertyValueSnak objects in the create claim API when needed * Improved Entity serialization (is now more concise and better encapsulated) * Added newFromArray to all DataValue objects and created DataValue factory using this * Worked on development environment distribution with Vagrant * Improved code that handles changes from the repository and reporting them in the client?s RecentChanges * Fought with broken selenium tests & refactored/fixed them * Reviewed tons of JS code * Set up QUnit test coverage report (will be online soon) * Updated demo system http://wikidata-test.wikimedia.de See http://meta.wikimedia.org/wiki/Wikidata/Development/Current_sprint for what we?re working on next. You can follow our commits at https://gerrit.wikimedia.org/r/#/q/(status:open+project:mediawiki/extensions/Wikibase)+OR+(status:merged+project:mediawiki/extensions/Wikibase),n,z and view the subset awaiting review at https://gerrit.wikimedia.org/r/#/q/status:open+project:mediawiki/extensions/Wikibase,n,z You can see all open bugs related to Wikidata at https://bugzilla.wikimedia.org/buglist.cgi?emailcc1=1&list_id=151540&resolution=---&emailtype1=exact&emailassigned_to1=1&query_format=advanced&email1=wikidata-bugs%40lists.wikimedia.org = Discussions/Press = * Translate Wikidata?s user interface and open it to the world http://blog.wikimedia.org/2012/11/10/translate-wikidata-user-interface/ * Licenses and importing data http://lists.wikimedia.org/pipermail/wikidata-l/2012-November/thread.html#1224 = Events = see http://meta.wikimedia.org/wiki/Wikidata/Events * Wikimedia Conferentie and hackathon * ISWC * Wikidata intro and Q&A in Cambridge, MA * Wikidata intro and Q&A in Vienna = Other Noteworthy Stuff = * We had to turn off language switching for anonymous users because of caching issues for now http://www.wikidata.org/wiki/Wikidata:Project_chat#language_switching_turned_off_for_anonymous_users * Vagrant setup for Wikidata so you can start testing and hacking easily https://github.com/SilkeMeyer/wikidata-vagrant = Open Tasks for You = * Hack on one of https://bugzilla.wikimedia.org/buglist.cgi?keywords=need-volunteer%2C%20&keywords_type=allwords&emailcc1=1&list_id=151541&resolution=---&emailtype1=exact&emailassigned_to1=1&query_format=advanced&email1=wikidata-bugs%40lists.wikimedia.org Anything to add? Please share! :) Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Community Communications for Wikidata Wikimedia Deutschland e.V. Obentrautstr. 72 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/681/51985. ------------------------------ Message: 4 Date: Fri, 16 Nov 2012 19:10:59 +0100 From: Vito <[email protected]> To: [email protected] Subject: [Wikidata-l] A framework for policies & similar stuffs Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Hi all wikidatians! I don't know if the matter has been already took in consideration but I think we should state a framework for policies, help and community pages. There's not so much to do, we already have a working model which is Commons. For example I've just seen https://www.wikidata.org/wiki/Help:Descrizione which is quite fine with me but it should be a translation of a common policy https://www.wikidata.org/wiki/Help:Description placed under https://www.wikidata.org/wiki/Help:Descrizione/it currently our {{autotranslate}} is transcluded only into another template, I hope the list will increase asap ;) Vito ------------------------------ Message: 5 Date: Fri, 16 Nov 2012 20:13:46 +0100 From: Jeroen De Dauw <[email protected]> To: "Discussion list for the Wikidata project." <[email protected]> Subject: [Wikidata-l] Property specification on-wiki Message-ID: <CAMhmagAXtcOJLf_k8hYZ416EcQfiKXDBZy=uoodkq-omhka...@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Hey, (Mail mainly directed at Denny) I am wondering to what extend we want to be able to specify the "data type" of a property on wiki. Right now one can only provide which DataType to use (where DataTypes are system defined) and nothing else. Do we also want to be able to specify things such as a list of allowed values, which ValueValidators to use, ect? I'm asking since Tpt poked me asking about doing exactly such a thing, which is written down here: https://www.wikidata.org/wiki/User_talk:Tpt/Support_of_external_ids I have been working under the assumption we do not want this (at least initially) so there currently is no place to track such per-property info internally. If we do want to support this any time soon, I'd like to know now so we can already facilitate it. (By facilitate it I mean holding it into account when writing new code or modifying existing stuff, not actually implementing it.) Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. -- -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.wikimedia.org/pipermail/wikidata-l/attachments/20121116/91847cef/attachment-0001.html> ------------------------------ Message: 6 Date: Fri, 16 Nov 2012 20:42:25 +0100 From: Daniel Kinzler <[email protected]> To: "Discussion list for the Wikidata project." <[email protected]> Subject: Re: [Wikidata-l] Property specification on-wiki Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 On 16.11.2012 20:13, Jeroen De Dauw wrote: > I have been working under the assumption we do not want this (at least > initially) so there currently is no place to track such per-property info > internally. If we do want to support this any time soon, I'd like to know now > so > we can already facilitate it. (By facilitate it I mean holding it into account > when writing new code or modifying existing stuff, not actually implementing > it.) As far as I remember the discussion, we 1) do not want to allow custom data types, composite data types or list types. Data types are defined by php code. 2) We do want to be able to impose additional restrictions on data values - like a range for numbers or a regex for strings. Could be modeled by a Claim for a special, internal property "value-restriction" or some such. -- daniel -- Daniel Kinzler, Softwarearchitekt Wikimedia Deutschland - Gesellschaft zur F?rderung Freien Wissens e. V. ------------------------------ Message: 7 Date: Sat, 17 Nov 2012 00:38:27 +0100 From: Gregor Hagedorn <[email protected]> To: "Discussion list for the Wikidata project." <[email protected]> Subject: Re: [Wikidata-l] Property specification on-wiki Message-ID: <cadcrvwyuahp7mlw_5fdy_kre9bwndycnrc0oikxwb79eq3r...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 > As far as I remember the discussion, we > 1) do not want to allow custom data types, composite data types or list types. > Data types are defined by php code. > 2) We do want to be able to impose additional restrictions on data values - > like > a range for numbers or a regex for strings. Could be modeled by a Claim for a > special, internal property "value-restriction" or some such. >From my background of biological descriptive data, where categorical data with value/state lists are the norm, I agree with Daniel that we don't need restrictions. Strict restriction in the sense of "allowed value lists/enumerations" are difficult to manage in the face of massive collaboration and diversity of content. The classical 1980 solution is to enhance the definition state enumerations (= categorical values) while entering data. This works well in very small collaborations, but does not scale well to large collaborations. While not requiring restriction constraints in a classical sense, for descriptive data we would need some "constraint management". The management allows saving constraint violating values, while supporting review and revision of these. In my case, lists of _recommended_ categorical values even more that ranges or regexpressions. Below I describe one possible version of functionality specs. I know that this can not be realized now, but in the light of Jeroen's question is might be valuable to already now have such a future functionality in mind when setting up the data management. 1. For each property of type URL or string literal, a list of recommend values (a "recommended-rdfs:range") can be defined. These values must be supported in the sense that in addition to a code word a brief description/definition can be given. It may be best to only allow only items as values (which have a label and description). 2. Optionally, at a later stage, a second list of "accepted values" can be defined for each property 3. Items violating range or enumeration constraints for a given property can be imported and saved. 4. It is easy, by a standard mechanism, to analyze for a given property which items and which values are from the list of recommended values or the list of accepted values, and which not. 5. In the user interface of the editor, the user is supported by a display of recommended values. ---- Gregor ------------------------------ _______________________________________________ Wikidata-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-l End of Wikidata-l Digest, Vol 12, Issue 10 ****************************************** _______________________________________________ Wikidata-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-l
