Hi,
I am studing the viability of use wikidata for store manufactured products information, this is my project proposal https://meta.wikimedia.org/wiki/WikiObject.
One of the challenges would be to protect product data like manufacturer property value or like width, lenght or any tech specs that are defined by manufacturer at the origin.
After reading Wikipedia:Protection_policy https://en.wikipedia.org/wiki/Wikipedia:Protection_policy, I'm answering myself if it could be possible to protect only these property values, for example defining a standart template for them, and make it only editable by authorized users (manufacturers?)
greetings and thanks in advance
Hi Quico,
I am not sure this is the way to go, - at least at the moment. I would like to have Wikidata open.
For instance, I don't think a publisher selling a book or a scientific article should be the only one able to edit specific property values. The strength of Wikimedia wikis is that anyone (more of less) is able to edit.
best Finn
On 05/08/2017 08:52 PM, Quico Prol wrote:
Hi,
I am studing the viability of use wikidata for store manufactured products information, this is my project proposal https://meta.wikimedia.org/wiki/WikiObject.
One of the challenges would be to protect product data like manufacturer property value or like width, lenght or any tech specs that are defined by manufacturer at the origin.
After reading Wikipedia:Protection_policy https://en.wikipedia.org/wiki/Wikipedia:Protection_policy, I'm answering myself if it could be possible to protect only these property values, for example defining a standart template for them, and make it only editable by authorized users (manufacturers?)
greetings and thanks in advance
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
Hi fn
I'm agree, at the moment is not the way to go , I'm just checking viability of this for a future.
Pretty sure that data integrity will be an important topic for product owners and general users if this project gets more attention.
greetings
2017-05-09 14:34 GMT+02:00 fn@imm.dtu.dk:
Hi Quico,
I am not sure this is the way to go, - at least at the moment. I would like to have Wikidata open.
For instance, I don't think a publisher selling a book or a scientific article should be the only one able to edit specific property values. The strength of Wikimedia wikis is that anyone (more of less) is able to edit.
best Finn
On 05/08/2017 08:52 PM, Quico Prol wrote:
Hi,
I am studing the viability of use wikidata for store manufactured products information, this is my project proposal https://meta.wikimedia.org/wiki/WikiObject.
One of the challenges would be to protect product data like manufacturer property value or like width, lenght or any tech specs that are defined by manufacturer at the origin.
After reading Wikipedia:Protection_policy https://en.wikipedia.org/wiki/Wikipedia:Protection_policy, I'm answering myself if it could be possible to protect only these property values, for example defining a standart template for them, and make it only editable by authorized users (manufacturers?)
greetings and thanks in advance
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
2017-05-10 15:25 GMT+02:00 Quico Prol franprol@gmail.com:
Hi fn
I'm agree, at the moment is not the way to go , I'm just checking viability of this for a future.
Pretty sure that data integrity will be an important topic for product owners and general users if this project gets more attention.
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.
L.
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
Hi, thanks for your replies,
Luca, not offended at all, I'm not interest in preserve company interests nor abandon open aproach, quite the oppositte, maybe I didnt explain well before:
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 https://lib.reviews/ that retrieve product info from wikidata searching by EAN number (using wikidata query service https://query.wikidata.org/ 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.
Lydia, agree with not black/white,
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 https://meta.wikimedia.org/wiki/WikiObject#SWOT_Analysis:_strengths.2C.C2.A0weaknesses.2C.C2.A0opportunities.2C_and.C2.A0threats
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.
greetings
2017-05-10 16:18 GMT+02:00 Lydia Pintscher lydia.pintscher@wikimedia.de:
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
On Thu, May 11, 2017 at 12:32 PM, Quico Prol franprol@gmail.com wrote:
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
;-) We're getting there!
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.
Basically it should be possible to add an additional reference without breaking the existing signature. Someone adding an additional reference to a statement shouldn't force the original signer to resign the statement. We want more references and this would be a disincentive. IIRC the thinking for qualifiers was similar but it has been a while... Will discuss this more again as the students make progress on their exploration work.
Cheers Lydia