Lydia, agree with not black/white,When I say protect some data I refer something like protect "Berlin is the capital of Germany" in a wikidata statement.The equivalent in this case whoul be for example "the EAN (European Article Number) for Raspberry Pi Model B 512MB is 2100000010196". Protect this kind of information whould be neccesary for people to use it in a realiable way.
Lets say somebody has a Online Store , or Inventory Management Software or a product review website that retrieve product info from wikidata searching by EAN number (using wikidata query service API) number, they need to know that product EAN number will be always the correct number for this product.
Regarding company interests, using wikidata for storing product info (I called this wikiobjects but the name doesn't matter) people would be able to find "fridges with A++ Energy Label" or "Lowest carbon footprint laptops with less that 2 kg weight", again you need that weight and carbon/energy certificates trustworthy values.
For companies will be interesting that their products are in wikidata, because if wikiobjects gets popular, it could be like other online platforms, "if it is not in , it doesn't exists" and this is important for companies although they expose their products to inevitable good and bad criticism.
Signed statements and inline validation, wow!, I didnt know about them, quite cool features, I have added them to wikiobjects project proposal page in a new section
I have seen that changes in references and qualifiers don't break signature nor trigged a warning like label and description changes, just curious why not.
On Wed, May 10, 2017 at 3:35 PM, Luca Martinelli
<martinelliluca@gmail.com> wrote:
> No offence, but I really don't see why Wikidata should abandon its
> open approach and create small sacks of "premium items" to preserve
> the interests of private companies, instead of the common interest in
> free knowledge, given also that there is no extensive proof of any
> need for such a radical measure.
>
> Wikidata's rules work because they are the same for
> everything/everyone and apply in the same way to everything/everybody.
> If they think their data are so valuable that we cannot be trusted
> with their maintenance, they can very well keep it.
Agreed. However I don't think we need to see it black and white. There
are many things we can do and meet in the middle. Right now for
example Lucas and Olga are working hard on showing constraint
violations right next to statements and making them available via the
API. Additionally a team of students started working on exploratory
work for signed statements
(https://phabricator.wikimedia.org/T138708 ). Those are all pieces of
the puzzle that will get us to better data quality while still staying
an open project. I am sure we can do more in this direction. I should
take the time to write down more of my current thinking...
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager 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.
_______________________________________________
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata