Re: [Wikidata-l] Suggestions for improvements of Wikidata

2015-04-16 Thread Tom Morris
Any chance you could put this list up on the wiki? Perhaps in your user
space. It'd be interesting to see these issues end up being tracked in
Phabricator and hopefully fixed. :)

Yours,

--
Tom Morris
http://tommorris.org/

___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions for improvements of Wikidata

2015-04-13 Thread Cristian Consonni
2015-04-13 14:54 GMT+02:00 Cristian Consonni kikkocrist...@gmail.com:
 With this premise, I think that Romaine's proposal for a game is
 absolutely doable and a good idea.

I want to clarify, I mean that I agree with Gerard that the best
indication for country for Battle of Stalingrad is URSS, I simply
say that a game should keep it simple (so in this case, either the
system is able to infer URSS as a possibility to present to the user
or otherwise the user should (be instructed to) say not sure).

I am much less convinced about the citizenship violations. Even if I
believe that citizenship is a concept introduced with the modern
nation-state, for a variety of reasons this is anyway applied to
people that have lived before that state(at least in is modern form)
was established.

For example, Galileo Galilei is reported as an error but all the
biggest Wikipedias (and some others that I am able to read) state that
Galileo Galilei was Italian (catalan Wikipedia says that he was Tuscan
in the artcle, but caegorizes him in the category Físics italians
(Italian pysicists) and Astrònoms italians (Italian astronomers). On
the other hand, the use of the name Italia to indicate at least a
portion of present-day Italy goes back in history and there are
mentions in documents from at least 42 b.C. (and possibly this will be
the same for most Europe).

C

___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions for improvements of Wikidata

2015-04-13 Thread Gerard Meijssen
Hoi,
The point is very much that the battle WAS in the USSR. It is not not
applicable it is one of the most important battles in the second world
war. My point is that we should not forget this. The battle of Uhud was not
in Saudi Arabia either...
Thanks,
  GerardM

On 13 April 2015 at 12:10, Cristian Consonni kikkocrist...@gmail.com
wrote:

 2015-04-09 8:29 GMT+02:00 Gerard Meijssen gerard.meijs...@gmail.com:
  Because the battle of Stalingrad as a battle was not fought by modern day
  Russia, it was fought by the USSR and Nazi Germany. Associating the
 battle
  of Stalingrad with modern day Russia is wrong on so many levels. At the
 time
  it was Stalingrad, hence the name. It will never be the battle of
 Wolgograd.

 I believe that you should have a Not applicable button to click for
 these cases.

 C

 ___
 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] Suggestions for improvements of Wikidata

2015-04-13 Thread Magnus Manske
Well, getting a list of violations per country would not be hard, given
the dates. There are, for example, 2,300 UK citizens who died 1706 or
earlier:
https://tools.wmflabs.org/autolist/?language=enproject=wikipediacategory=depth=12wdq=claim%5B27%3A145%5D%20and%20between%5B570%2C0%2C1706%5Dstatementlist=run=Runmode_manual=ormode_cat=ormode_wdq=notmode_find=orchunk_size=1

It would be possible to generate a daily constraint violation report for
more such conditions, given a list of valid data ranges (e,g, Q145 / 1701
/ now for UK). I'd volunteer, if someone makes a machine-readable list
(table?) on a wiki page :-)

A more fine-tuned bot could actually auto-replace some, if the new
country is the same or larger as the old one. But given the numbers, it
is probably not necessary to toy with such forces (we can fix a few
thousand by hand once; new entries should be low in numbers).


On Mon, Apr 13, 2015 at 2:22 PM Andrew Gray andrew.g...@dunelm.org.uk
wrote:

 This is an example of a more general problem, I think - country is
 treated as an indefinite concept, which breaks down for historic
 people as well. To take Magnus's example, Wikidata records that Henry
 VIII was a citizen of the UK, which would no doubt have surprised him
 (https://www.wikidata.org/wiki/Q38370).

 Perhaps what we want is to figure out some way that country (P17)
 and citizenship (P27) can have robust constraints based on date of
 birth/death or on date of an event, so that - for example - anyone who
 is reported as having citizenship of the UK has to have been born
 before or died after 1707. For something like the battle, the
 constraint would be that the event has to have happened while the P17
 country was in existence.

 I don't know if we can do anything this sophisticated with the current
 constraints system - perhaps it would have to be organised on a
 country-by-country basis, one report for the UK, then the USSR, and so
 on as we define the cases. Perhaps something to look at doing a year
 down the line, when we've imported a lot of data we can fix ;-)

 Andrew.


 On 13 April 2015 at 13:00, Gerard Meijssen gerard.meijs...@gmail.com
 wrote:
  Hoi,
  The point is very much that the battle WAS in the USSR. It is not not
  applicable it is one of the most important battles in the second world
 war.
  My point is that we should not forget this. The battle of Uhud was not in
  Saudi Arabia either...
  Thanks,
GerardM
 
  On 13 April 2015 at 12:10, Cristian Consonni kikkocrist...@gmail.com
  wrote:
 
  2015-04-09 8:29 GMT+02:00 Gerard Meijssen gerard.meijs...@gmail.com:
   Because the battle of Stalingrad as a battle was not fought by modern
   day
   Russia, it was fought by the USSR and Nazi Germany. Associating the
   battle
   of Stalingrad with modern day Russia is wrong on so many levels. At
 the
   time
   it was Stalingrad, hence the name. It will never be the battle of
   Wolgograd.
 
  I believe that you should have a Not applicable button to click for
  these cases.
 
  C
 
  ___
  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
 



 --
 - Andrew Gray
   andrew.g...@dunelm.org.uk

 ___
 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] Suggestions for improvements of Wikidata

2015-04-13 Thread Cristian Consonni
2015-04-13 14:00 GMT+02:00 Gerard Meijssen gerard.meijs...@gmail.com:
 The point is very much that the battle WAS in the USSR. It is not not
 applicable it is one of the most important battles in the second world war.
 My point is that we should not forget this. The battle of Uhud was not in
 Saudi Arabia either...

Ok, but I think that having a system that, for examples, cross checks
dates and presents URSS as a possibility would be much more
complicated to build.

I think that the Wikidata game (or a similar game-like system) can not
address all possible complicated scenarios,  and thus there will
always be some cases that should be handled directly editing Wikidata.

I was following Magnus here, in the post where he introduces the
Wikidata Game[1]:
«So what’s the approach here? I feel the crucial issue for
gamification is breaking complicated processes down into simple
actions, which themselves are just manifest decisions – “A”, “B”, or
“I don’t want to decide this now!”.

[...]

Of course, this simplification misses a lot of “fine-tuning” – what if
you are asked to decide the gender of an item that has been
accidentally tagged as “person”? What if the gender of this person is
something other than “male” or “female”? Handling all these special
cases would, of course, be possible – but it would destroy the
simplicity of the three-button interface. The games always leave you a
“way out” – when in doubt, skip the decision. Someone else will take
care of it, eventually, probably on Wikidata proper.»

With this premise, I think that Romaine's proposal for a game is
absolutely doable and a good idea.

C


[1] http://magnusmanske.de/wordpress/?p=203

___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions for improvements of Wikidata

2015-04-13 Thread Thomas Douillard
Of course there will always be some things too complicated to be reasonably
expressed in Wikidata, or hard to process by software.

But in the case of historical datas, we better have to think of a common
and practical representation and ways for tools to process datas, because
this is totally a WIkipedia common usecase :) There is already tools to
draw wars in a map and chronological datas.

2015-04-13 14:54 GMT+02:00 Cristian Consonni kikkocrist...@gmail.com:

 2015-04-13 14:00 GMT+02:00 Gerard Meijssen gerard.meijs...@gmail.com:
  The point is very much that the battle WAS in the USSR. It is not not
  applicable it is one of the most important battles in the second world
 war.
  My point is that we should not forget this. The battle of Uhud was not in
  Saudi Arabia either...

 Ok, but I think that having a system that, for examples, cross checks
 dates and presents URSS as a possibility would be much more
 complicated to build.

 I think that the Wikidata game (or a similar game-like system) can not
 address all possible complicated scenarios,  and thus there will
 always be some cases that should be handled directly editing Wikidata.

 I was following Magnus here, in the post where he introduces the
 Wikidata Game[1]:
 «So what’s the approach here? I feel the crucial issue for
 gamification is breaking complicated processes down into simple
 actions, which themselves are just manifest decisions – “A”, “B”, or
 “I don’t want to decide this now!”.

 [...]

 Of course, this simplification misses a lot of “fine-tuning” – what if
 you are asked to decide the gender of an item that has been
 accidentally tagged as “person”? What if the gender of this person is
 something other than “male” or “female”? Handling all these special
 cases would, of course, be possible – but it would destroy the
 simplicity of the three-button interface. The games always leave you a
 “way out” – when in doubt, skip the decision. Someone else will take
 care of it, eventually, probably on Wikidata proper.»

 With this premise, I think that Romaine's proposal for a game is
 absolutely doable and a good idea.

 C


 [1] http://magnusmanske.de/wordpress/?p=203

 ___
 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] Suggestions for improvements of Wikidata

2015-04-13 Thread Andrew Gray
This is an example of a more general problem, I think - country is
treated as an indefinite concept, which breaks down for historic
people as well. To take Magnus's example, Wikidata records that Henry
VIII was a citizen of the UK, which would no doubt have surprised him
(https://www.wikidata.org/wiki/Q38370).

Perhaps what we want is to figure out some way that country (P17)
and citizenship (P27) can have robust constraints based on date of
birth/death or on date of an event, so that - for example - anyone who
is reported as having citizenship of the UK has to have been born
before or died after 1707. For something like the battle, the
constraint would be that the event has to have happened while the P17
country was in existence.

I don't know if we can do anything this sophisticated with the current
constraints system - perhaps it would have to be organised on a
country-by-country basis, one report for the UK, then the USSR, and so
on as we define the cases. Perhaps something to look at doing a year
down the line, when we've imported a lot of data we can fix ;-)

Andrew.


On 13 April 2015 at 13:00, Gerard Meijssen gerard.meijs...@gmail.com wrote:
 Hoi,
 The point is very much that the battle WAS in the USSR. It is not not
 applicable it is one of the most important battles in the second world war.
 My point is that we should not forget this. The battle of Uhud was not in
 Saudi Arabia either...
 Thanks,
   GerardM

 On 13 April 2015 at 12:10, Cristian Consonni kikkocrist...@gmail.com
 wrote:

 2015-04-09 8:29 GMT+02:00 Gerard Meijssen gerard.meijs...@gmail.com:
  Because the battle of Stalingrad as a battle was not fought by modern
  day
  Russia, it was fought by the USSR and Nazi Germany. Associating the
  battle
  of Stalingrad with modern day Russia is wrong on so many levels. At the
  time
  it was Stalingrad, hence the name. It will never be the battle of
  Wolgograd.

 I believe that you should have a Not applicable button to click for
 these cases.

 C

 ___
 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




-- 
- Andrew Gray
  andrew.g...@dunelm.org.uk

___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions for improvements of Wikidata

2015-04-13 Thread Magnus Manske
Huh, just when I sent this mail, I realized that there is a database with
nation dates, it's called Wikidata...

So I present:
https://tools.wmflabs.org/wikidata-todo/wrong_nationality.html

Have fun!

On Mon, Apr 13, 2015 at 3:43 PM Magnus Manske magnusman...@googlemail.com
wrote:

 Well, getting a list of violations per country would not be hard, given
 the dates. There are, for example, 2,300 UK citizens who died 1706 or
 earlier:

 https://tools.wmflabs.org/autolist/?language=enproject=wikipediacategory=depth=12wdq=claim%5B27%3A145%5D%20and%20between%5B570%2C0%2C1706%5Dstatementlist=run=Runmode_manual=ormode_cat=ormode_wdq=notmode_find=orchunk_size=1

 It would be possible to generate a daily constraint violation report for
 more such conditions, given a list of valid data ranges (e,g, Q145 / 1701
 / now for UK). I'd volunteer, if someone makes a machine-readable list
 (table?) on a wiki page :-)

 A more fine-tuned bot could actually auto-replace some, if the new
 country is the same or larger as the old one. But given the numbers, it
 is probably not necessary to toy with such forces (we can fix a few
 thousand by hand once; new entries should be low in numbers).


 On Mon, Apr 13, 2015 at 2:22 PM Andrew Gray andrew.g...@dunelm.org.uk
 wrote:

 This is an example of a more general problem, I think - country is
 treated as an indefinite concept, which breaks down for historic
 people as well. To take Magnus's example, Wikidata records that Henry
 VIII was a citizen of the UK, which would no doubt have surprised him
 (https://www.wikidata.org/wiki/Q38370).

 Perhaps what we want is to figure out some way that country (P17)
 and citizenship (P27) can have robust constraints based on date of
 birth/death or on date of an event, so that - for example - anyone who
 is reported as having citizenship of the UK has to have been born
 before or died after 1707. For something like the battle, the
 constraint would be that the event has to have happened while the P17
 country was in existence.

 I don't know if we can do anything this sophisticated with the current
 constraints system - perhaps it would have to be organised on a
 country-by-country basis, one report for the UK, then the USSR, and so
 on as we define the cases. Perhaps something to look at doing a year
 down the line, when we've imported a lot of data we can fix ;-)

 Andrew.


 On 13 April 2015 at 13:00, Gerard Meijssen gerard.meijs...@gmail.com
 wrote:
  Hoi,
  The point is very much that the battle WAS in the USSR. It is not not
  applicable it is one of the most important battles in the second world
 war.
  My point is that we should not forget this. The battle of Uhud was not
 in
  Saudi Arabia either...
  Thanks,
GerardM
 
  On 13 April 2015 at 12:10, Cristian Consonni kikkocrist...@gmail.com
  wrote:
 
  2015-04-09 8:29 GMT+02:00 Gerard Meijssen gerard.meijs...@gmail.com:
   Because the battle of Stalingrad as a battle was not fought by modern
   day
   Russia, it was fought by the USSR and Nazi Germany. Associating the
   battle
   of Stalingrad with modern day Russia is wrong on so many levels. At
 the
   time
   it was Stalingrad, hence the name. It will never be the battle of
   Wolgograd.
 
  I believe that you should have a Not applicable button to click for
  these cases.
 
  C
 
  ___
  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
 



 --
 - Andrew Gray
   andrew.g...@dunelm.org.uk

 ___
 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] Suggestions for improvements of Wikidata

2015-04-13 Thread Cristian Consonni
2015-04-13 18:46 GMT+02:00 Magnus Manske magnusman...@googlemail.com:
 So I present:
 https://tools.wmflabs.org/wikidata-todo/wrong_nationality.html

All links to Wikidata are missing the /wiki/ part.

C

___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions for improvements of Wikidata

2015-04-09 Thread Gerard Meijssen
Hoi,
Because the battle of Stalingrad as a battle was not fought by modern day
Russia, it was fought by the USSR and Nazi Germany. Associating the battle
of Stalingrad with modern day Russia is wrong on so many levels. At the
time it was Stalingrad, hence the name. It will never be the battle of
Wolgograd.
Thanks,
  GerardM

On 7 April 2015 at 23:27, Roland Cornelissen metamatter...@gmail.com
wrote:

 Hi,

 On 05-04-15 16:10, Gerard Meijssen wrote:

 It does not make sense to couple coordinates with countries... The battle
 of Stalingrad for instance was firmly in the USSR and not in modern day
 Russia.

 Why not? Every Place has a history that can't be evaded.
 The beautiful part of Linked Data is these little graphs one gets when
 joining data on defined properties. For instance joining data based on
 coordinates would provide an insight into the history of a certain Place.

 The battle of Stalingrad is an event that has taken Place at Stalingrad,
 which is now Wolgograd, both have the same coordinates. There are even more
 places at these coordinates :-)

 Cheers,
 Roland


 ___
 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] Suggestions for improvements of Wikidata

2015-04-08 Thread Roland Cornelissen

Hi,

On 05-04-15 16:10, Gerard Meijssen wrote:

It does not make sense to couple coordinates with countries... The
battle of Stalingrad for instance was firmly in the USSR and not in
modern day Russia.

Why not? Every Place has a history that can't be evaded.
The beautiful part of Linked Data is these little graphs one gets when 
joining data on defined properties. For instance joining data based on 
coordinates would provide an insight into the history of a certain Place.


The battle of Stalingrad is an event that has taken Place at Stalingrad, 
which is now Wolgograd, both have the same coordinates. There are even 
more places at these coordinates :-)


Cheers,
Roland

___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions for improvements of Wikidata

2015-04-08 Thread Roland Cornelissen

Hi,

On 05-04-15 16:10, Gerard Meijssen wrote:
It does not make sense to couple coordinates with countries... The 
battle of Stalingrad for instance was firmly in the USSR and not in 
modern day Russia.

Why not? Every Place has a history that can't be evaded.
The beautiful part of Linked Data is these little graphs one gets when 
joining data on defined properties. For instance joining data based on 
coordinates would provide an insight into the history of a certain Place.


The battle of Stalingrad is an event that has taken Place at Stalingrad, 
which is now Wolgograd, both have the same coordinates. There are even 
more places at these coordinates :-)


Cheers,
Roland

___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions for improvements of Wikidata

2015-04-02 Thread James Heald
As an example of a step towards E1 (outside Wikidata), the list might 
remember the code-snippet that the DJ wrote for Commons,


https://commons.wikimedia.org/wiki/User:TheDJ/wdcat.js

If you add
importScript('User:TheDJ/wdcat.js');
to your  common.js  file on Commons, then whenever you go to a Commons 
category that is the target of a P373 on Wikidata, it adds a link to the 
page that goes to Reasonator for the corresponding article-like Wikidata 
item.


It's something I've found very useful, eg working through the BBC 
YourPaintings list of painters on Mix'n'Match, and the corresponding 
tracking pages linked from

https://en.wikipedia.org/wiki/Wikipedia:GLAM/Your_paintings/header
to see what article-like Wikidata item (if any) a Commons category may 
relate to.


  -- James.


On 02/04/2015 14:41, Romaine Wiki wrote:

[snip]



*E. Outside Wikidata*

E1. Commons: show on Commons somewhere when a category, gallery page,
institution page, template, file etc is used in a statement on Wikidata. If
a page is renamed or deleted, this must be changed on Wikidata as well, but
noticing where a page is used is not easy.
If an image is linked in a statement on Wikidata, on the image page this is
shown. Somehow this should also be implemented for categories, gallery
pages, institution pages, templates, and others.
This should be added to pages like Special:WhatLinksHere, Special:MovePage,
Special:GlobalUsage

E2. Wikipedia/other wikis: develop an extension, that communities can
enable, that shows on the bottom of articles, in the style of the category
box, an automatic box with all the identifiers used for authority control
https://www.wikidata.org/wiki/Q18614948 to replace templates like
https://www.wikidata.org/wiki/Q5153934.



___
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] Suggestions

2012-12-10 Thread Nicholas Humfrey

On 08/12/2012 17:32, Jeroen De Dauw jeroended...@gmail.com wrote:

 Hey,
 
 It woud be great to have keys into other databases from Wikidata. I'd be
 happy to contribute Freebase IDs to matching Wikidata concepts. However, I'm
 wondering if it really makes sense to have a separate property for every type
 of ID. Shouldn't it be modeled more like interwiki links so that each concept
 has many foreign keys each with an associated data source. That's how we've
 modeled it in Freebase and it scales quite well.
 
 If I'm not mistaken this is what we plan to do. The current system we're using
 for the language links can certainly handle it, as it's not WP specific.

I would love to see equivalency links to other sites with stable
identifiers, such as IMDb and MusicBrainz.


What would the linking policy be for the wider web? We are interested in:
- Official Twitter
- Official Facebook
- Official Homepage(s) and blogs
- Fan sites


MusicBrainz have done quite a lot of work on this, for example:
http://musicbrainz.org/doc/Category:External_Website_Relationship_Class

They also have some nice JavaScript in their editor to make sure that URLs
are consistently formatted for well-known sites.


nick.


http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal 
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on 
it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.


___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions

2012-12-10 Thread Sven
I assume we're still talking abiut things to link into a Wikidata entry? I 
could see a place for official social media accounts, and even for the related 
Wikia site, but definitely not for fan sites. 

On Dec 10, 2012, at 6:34 AM, Nicholas Humfrey nicholas.humf...@bbc.co.uk 
wrote:

 
 On 08/12/2012 17:32, Jeroen De Dauw jeroended...@gmail.com wrote:
 
 Hey,
 
 It woud be great to have keys into other databases from Wikidata. I'd be
 happy to contribute Freebase IDs to matching Wikidata concepts. However, I'm
 wondering if it really makes sense to have a separate property for every 
 type
 of ID. Shouldn't it be modeled more like interwiki links so that each 
 concept
 has many foreign keys each with an associated data source. That's how we've
 modeled it in Freebase and it scales quite well.
 
 If I'm not mistaken this is what we plan to do. The current system we're 
 using
 for the language links can certainly handle it, as it's not WP specific.
 
 I would love to see equivalency links to other sites with stable
 identifiers, such as IMDb and MusicBrainz.
 
 
 What would the linking policy be for the wider web? We are interested in:
 - Official Twitter
 - Official Facebook
 - Official Homepage(s) and blogs
 - Fan sites
 
 
 MusicBrainz have done quite a lot of work on this, for example:
 http://musicbrainz.org/doc/Category:External_Website_Relationship_Class
 
 They also have some nice JavaScript in their editor to make sure that URLs
 are consistently formatted for well-known sites.
 
 
 nick.
 
 
 http://www.bbc.co.uk/
 This e-mail (and any attachments) is confidential and may contain personal 
 views which are not the views of the BBC unless specifically stated.
 If you have received it in error, please delete it from your system.
 Do not use, copy or disclose the information in any way nor act in reliance 
 on it and notify the sender immediately.
 Please note that the BBC monitors e-mails sent or received.
 Further communication will signify your consent to this.

 
 ___
 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] Suggestions

2012-12-10 Thread swuensch
This discussion should be on a prominent place at wikidata because the
community has to decide about this.

On Mon, Dec 10, 2012 at 3:28 PM, Sven svenmangu...@gmail.com wrote:

 I assume we're still talking abiut things to link into a Wikidata entry? I
 could see a place for official social media accounts, and even for the
 related Wikia site, but definitely not for fan sites.

 On Dec 10, 2012, at 6:34 AM, Nicholas Humfrey nicholas.humf...@bbc.co.uk
 wrote:

 
  On 08/12/2012 17:32, Jeroen De Dauw jeroended...@gmail.com wrote:
 
  Hey,
 
  It woud be great to have keys into other databases from Wikidata. I'd
 be
  happy to contribute Freebase IDs to matching Wikidata concepts.
 However, I'm
  wondering if it really makes sense to have a separate property for
 every type
  of ID. Shouldn't it be modeled more like interwiki links so that each
 concept
  has many foreign keys each with an associated data source. That's how
 we've
  modeled it in Freebase and it scales quite well.
 
  If I'm not mistaken this is what we plan to do. The current system
 we're using
  for the language links can certainly handle it, as it's not WP specific.
 
  I would love to see equivalency links to other sites with stable
  identifiers, such as IMDb and MusicBrainz.
 
 
  What would the linking policy be for the wider web? We are interested in:
  - Official Twitter
  - Official Facebook
  - Official Homepage(s) and blogs
  - Fan sites
 
 
  MusicBrainz have done quite a lot of work on this, for example:
  http://musicbrainz.org/doc/Category:External_Website_Relationship_Class
 
  They also have some nice JavaScript in their editor to make sure that
 URLs
  are consistently formatted for well-known sites.
 
 
  nick.
 
 
  http://www.bbc.co.uk/
  This e-mail (and any attachments) is confidential and may contain
 personal views which are not the views of the BBC unless specifically
 stated.
  If you have received it in error, please delete it from your system.
  Do not use, copy or disclose the information in any way nor act in
 reliance on it and notify the sender immediately.
  Please note that the BBC monitors e-mails sent or received.
  Further communication will signify your consent to this.
 
 
  ___
  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] Suggestions

2012-12-09 Thread Gregor Hagedorn
 If I'm not mistaken this is what we plan to do. The current system we're
 using for the language links can certainly handle it, as it's not WP
 specific.

that would be great!

On top of my wish list are the Wiktionaries, since most of the
entities needed to use Wikidata for descriptive knowledge are provided
only on summary pages (dozens of terms in one page) on Wikipedias,
whereas the Wiktionaries define them as pages.

And I believe it will strengthen Wikidata if it can be open to open
data initiatives outside of the Wikimedia Foundation. Clearly there
needs to be control which initiatives are accepted as valid
authoritative sources of identifiers, but I wonder whether the
interwiki list is not already a good mechanism for this? If the
interwiki list could be supplemented with a generic definition how to
make an ajax-identifier lookup call, to present the user a picklist,
this could be a huge long-term benefit (i.e. it could be used by
Wikidata, but also in any Wikipedia when using a more powerful visual
editor).

Gregor

___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions

2012-12-08 Thread Jeroen De Dauw
Hey,

It woud be great to have keys into other databases from Wikidata. I'd be
 happy to contribute Freebase IDs to matching Wikidata concepts. However,
 I'm wondering if it really makes sense to have a separate property for
 every type of ID. Shouldn't it be modeled more like interwiki links so that
 each concept has many foreign keys each with an associated data source.
 That's how we've modeled it in Freebase and it scales quite well.


If I'm not mistaken this is what we plan to do. The current system we're
using for the language links can certainly handle it, as it's not WP
specific.

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions

2012-12-06 Thread Klein,Max
  I think it would be good to make clear which specific content
  additions will be possible in future. I think we should have a list
  which states what content will be in next deployment and what content
  will be later on. I read somewhere about Link_FA, Link_GA, but also
  IMDb, IBDB, VIAF, but also of course Commons. A lot others are too on
  https://en.wikipedia.org/wiki/Template:Authority_control
 
 Neither of those will be in the next deployment. It is pretty certain
 that all of them will be possible at some point.
 
  Currently VIAF is in discussion and willing to be added on some
 wiki's, but with Wikidata it can be done much easier. Any plans for it?
 
 Linking to a VIAF id? That will be possible. I can't tell you when.

It is probably time for me to chime in on this, as the author of VIAFbot which 
just pushed 250,000 links on English Wikipedia. (BTW, if you want to see 
in-depth statistics I've written a blog post about it 
http://hangingtogether.org/?p=2306).

I've been receiving a lot of emails asking to replicate VIAFbot on different 
Wikis (Commons, French, Italian, Dutch, Swedish) and my reply has always been 
that the most important next step is to write Wikidata. The only thing that 
needs to be possible on the Wikidata side is to be able to write properties, 
because a VIAF ID is a property of a Wikidata cluster. 

Then my plan is to run through the lists of pages that transclude any authority 
control template {{en:Authority control}} /Union {{de:Normdaten}} /Union 
{{fr:Autorite}} /Union {{it:Bio}} / Union {{commons:Creator}} and load the 
interwikis for each link. Then find or create the Wikidata concept for that 
multilingual cluster. If all the different sources are in agreement, write a 
VIAF ID property, and if there is disagreement use the Wikidata 'source' method 
to note which language thinks what.

Since VIAFbot was written in pywikipediabot, and pywikidata exists I think the 
bot will be relatively easy. How do I apply for a bot flag on Wikidata?
 
 
 Cheers
 Lydia

Cheers,
Max

___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions

2012-12-05 Thread Lydia Pintscher
On Wed, Dec 5, 2012 at 4:48 PM, Romaine Wiki romaine_w...@yahoo.com wrote:
 Hello all,

 Wikidata has grown rapidly the past weeks, a community of users is active 
 now, and we are just in the beginning of Wikidata, but still already 
 tremendous work already has been done with all the items with interwiki's 
 added. We all have picked up Wikidata enthusiastic, and I think we all want 
 to get further with it very much. The project fits the needs of the 
 communities very much.

 My personal background is to translate and explain the technical stuff to 
 users on wiki's, and return the feedback to the developers, as most users 
 consider bugzilla and technical things far far far away.

 The weekly summary is great to have, but for more transparency it would be 
 nice to have a time line, or otherwise a clear (expected) date when the next 
 big change will be (like with the deployment of new MediaWiki versions). 
 Reading the e-mails and reading on meta, I almost only see the technical 
 changes which are coming, but for the communities on Wikidata and Wikipedia's 
 it would be great to know when the next step in content adding will be 
 possible.

There are simply no fixed dates for that. That's the reason no dates
are published ;-) It's basically done when it is done. I am sorry we
can't be more specific about that. There are things influencing
schedules that are out of our hand.

 Also it would be nice to have a list of those things that will be possible in 
 the future, but have no date yet to be implemented. The reason for this is 
 double:
 * On local communities I notice a lot of stories, fables and myths of how 
 Wikidata will be in future, but often with no ground.

Please name them and I am happy to give a definitive answer.

 * Also there are a lot of things that would have potential on Wikidata. Yes 
 sure, I can add it to Wikidata:Contact_the_development_team but already my 
 last comment is archived somewhere and out of sight.

Everything there is looked at and handled by me. Things we will
implement are moved to bugzilla. Nothing is lost.

 I think it would be good to make clear which specific content additions will 
 be possible in future. I think we should have a list which states what 
 content will be in next deployment and what content will be later on. I read 
 somewhere about Link_FA, Link_GA, but also IMDb, IBDB, VIAF, but also of 
 course Commons. A lot others are too on 
 https://en.wikipedia.org/wiki/Template:Authority_control

Neither of those will be in the next deployment. It is pretty certain
that all of them will be possible at some point.

 Currently VIAF is in discussion and willing to be added on some wiki's, but 
 with Wikidata it can be done much easier. Any plans for it?

Linking to a VIAF id? That will be possible. I can't tell you when.


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.

___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l


Re: [Wikidata-l] Suggestions

2012-12-05 Thread Marco Fleckinger

Hello Romaine,

On 05/12/12 16:48, Romaine Wiki wrote:

The weekly summary is great to have, but for more transparency it
would be nice to have a time line, or otherwise a clear (expected)
date when the next big change will be (like with the deployment of
new MediaWiki versions). Reading the e-mails and reading on meta, I
almost only see the technical changes which are coming, but for the
communities on Wikidata and Wikipedia's it would be great to know
when the next step in content adding will be possible.

Also it would be nice to have a list of those things that will be
possible in the future, but have no date yet to be implemented. The
reason for this is double: * On local communities I notice a lot of
stories, fables and myths of how Wikidata will be in future, but
often with no ground. * Also there are a lot of things that would
have potential on Wikidata. Yes sure, I can add it to
Wikidata:Contact_the_development_team but already my last comment is
archived somewhere and out of sight.


So what you want is a diffent view on things like

http://meta.wikimedia.org/wiki/Wikidata/Development/Current_sprint

or

http://meta.wikimedia.org/wiki/Wikidata/Status_updates

?

More a table where all features of the single status updates are listed 
in a table with red, yellow or green background? They should also be 
divided into Categories, that it's a little easier to follow the 
development by watching one single view.


Something similar to

http://en.wikipedia.org/wiki/Firefox#Release_history

?

Sorry, this will maybe be possible with phase III, and we still do not 
have it ;-)


But in the meantime we could create such a table on our own, maybe on 
[[meta:Wikidata/Development]]


Marco

___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l