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.
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.
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
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?
Romaine
On Wed, Dec 5, 2012 at 4:48 PM, Romaine Wiki romaine_wiki@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.
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
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.
On Thu, Dec 6, 2012 at 1:53 PM, Klein,Max kleinm@oclc.org wrote:
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
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. --
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
On 08/12/2012 17:32, "Jeroen De Dauw" jeroendedauw@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.
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.Humfrey@bbc.co.uk wrote:
On 08/12/2012 17:32, "Jeroen De Dauw" jeroendedauw@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
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 svenmanguard@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.Humfrey@bbc.co.uk wrote:
On 08/12/2012 17:32, "Jeroen De Dauw" jeroendedauw@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
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