Re: [Wikidata-l] WikiData change propagation for third parties

On 04.05.2013 19:13, Jona Christopher Sahnwaldt wrote: > We will produce a DBpedia release pretty soon, I don't think we can > wait for the "real" dumps. The inter-language links are an important > part of DBpedia, so we have to extract data from almost all Wikidata > items. I don't think it's sens

Re: [Wikidata-l] WikiData change propagation for third parties

On 4 May 2013 17:12, Daniel Kinzler wrote: > On 04.05.2013 12:05, Jona Christopher Sahnwaldt wrote: >> On 26 April 2013 17:15, Daniel Kinzler wrote: >>> *internal* JSON representation, which is different from what the API >>> returns, >>> and may change at any time without notice. >> >> Somewhat

Re: [Wikidata-l] WikiData change propagation for third parties

On 04.05.2013 12:05, Jona Christopher Sahnwaldt wrote: > On 26 April 2013 17:15, Daniel Kinzler wrote: >> *internal* JSON representation, which is different from what the API returns, >> and may change at any time without notice. > > Somewhat off-topic: I didn't know you have different JSON > rep

Re: [Wikidata-l] WikiData change propagation for third parties

On 26.04.2013 21:13, Sebastian Hellmann wrote: > Hi Daniel, > > Am 26.04.2013 18:01, schrieb Daniel Kinzler: >> You guys are the only reason the interface still exists :) DBpedia is the >> only >> (regular) external user (LuceneSearch is the only internal user). Note that >> there's nobody really

Re: [Wikidata-l] WikiData change propagation for third parties

On 26 April 2013 17:15, Daniel Kinzler wrote: > On 26.04.2013 16:56, Denny Vrandečić wrote: >> The third party propagation is not very high on our priority list. Not >> because >> it is not important, but because there are things that are even more >> important - >> like getting it to work for W

Re: [Wikidata-l] WikiData change propagation for third parties

Hi Daniel, Am 26.04.2013 18:01, schrieb Daniel Kinzler: You guys are the only reason the interface still exists :) DBpedia is the only (regular) external user (LuceneSearch is the only internal user). Note that there's nobody really maintaining this interface, so finding an alternative would b

Re: [Wikidata-l] WikiData change propagation for third parties

On 26.04.2013 17:09, Dimitris Kontokostas wrote: > * We do have the OAIRepository extension installed on Wikidata. Did anyone > try that? > > > Great! Didn't know that. I see it installed > (http://www.wikidata.org/wiki/Special:OAIRepository) but it is password > protected, can we (DBpedi

Re: [Wikidata-l] WikiData change propagation for third parties

On 26.04.2013 17:31, Dimitris Kontokostas wrote: > What we do right now in DBpedia Live is that we have a local clone of > Wikipedia > that get's in sync using the OAIRepository extension. This is done to abuse > our > local copy as we please. It would be owesome if this Just Worked (tm) for Wik

Re: [Wikidata-l] WikiData change propagation for third parties

Hi Daniel, On Fri, Apr 26, 2013 at 6:15 PM, Daniel Kinzler wrote: > On 26.04.2013 16:56, Denny Vrandečić wrote: > > The third party propagation is not very high on our priority list. Not > because > > it is not important, but because there are things that are even more > important - > > like get

Re: [Wikidata-l] WikiData change propagation for third parties

On 26.04.2013 16:56, Denny Vrandečić wrote: > The third party propagation is not very high on our priority list. Not because > it is not important, but because there are things that are even more > important - > like getting it to work for Wikipedia :) And this seems to be stabilizing. > > What w

Re: [Wikidata-l] WikiData change propagation for third parties

Hi Denny On Fri, Apr 26, 2013 at 5:56 PM, Denny Vrandečić < denny.vrande...@wikimedia.de> wrote: > The third party propagation is not very high on our priority list. Not > because it is not important, but because there are things that are even > more important - like getting it to work for Wikipe

Re: [Wikidata-l] WikiData change propagation for third parties

The third party propagation is not very high on our priority list. Not because it is not important, but because there are things that are even more important - like getting it to work for Wikipedia :) And this seems to be stabilizing. What we have, for now: * We have the broadcast of all edits th

Re: [Wikidata-l] WikiData change propagation for third parties

Recently I spoke with Wikia, and being able to subscribe to the recent changes feed is a very important feature to them. Apparently polling API's recent changes creates a much higher stress on the system than subscribing. Now, we don't need (from the start) to implement publishing of all the data

Re: [Wikidata-l] WikiData change propagation for third parties

Dear Jeremy, all, In addition to what Sebastian said, in DBpedia Live we use the OAI-PMH protocol to get update feeds for English, German & Dutch WIkipedia. This OAI-PMH implementation [1] is very convenient for what we need (and I guess for most people) because it uses the latest modification dat

Re: [Wikidata-l] WikiData change propagation for third parties

Dear Jeremy, please read email from Daniel Kinzler on this list from 26.03.2013 18:26 : * A dispatcher needs about 3 seconds to dispatch 1000 changes to a client wiki. * Considering we have ~300 client wikis, this means one dispatcher can handle about 4000 changes per hour. * We currently have t

Re: [Wikidata-l] WikiData change propagation for third parties

Hi, On Fri, Apr 26, 2013 at 5:29 AM, Sebastian Hellmann wrote: > Well, PubSubHubbub is a nice idea. However it clearly depends on two factors: > 1. whether Wikidata sets up such an infrastructure (I need to check whether > we have capacities, I am not sure atm) Capacity for what? the infrastru

Re: [Wikidata-l] WikiData change propagation for third parties

Well, PubSubHubbub is a nice idea. However it clearly depends on two factors: 1. whether Wikidata sets up such an infrastructure (I need to check whether we have capacities, I am not sure atm) 2. whether performance is good enough to handle high-volume publishers Basically, polling to recent ch

Re: [Wikidata-l] WikiData change propagation for third parties

Hello Dimirtis what do you thing of that ? shall i write this part as an abstract part in the proposal and wait for more details , or could we have a smiliar plan like the one already implemented in dbpedia http://wiki.dbpedia.org/DBpediaLive#h156-3 thanks regards On Fri, Apr 26, 2013 at 12:50

Re: [Wikidata-l] WikiData change propagation for third parties

On Thu, Apr 25, 2013 at 10:42 PM, Hady elsahar wrote: > 2- is there any design pattern or a brief outline for the change propagation > design , how it would be ? in order that i could make a rough plan and > estimation about how it could be consumed from the DBpedia side ? I don't know anythin

[Wikidata-l] WikiData change propagation for third parties

Hello All , i'm planning to write a proposal for WikiData to DBpedia project in GSoC2013 i've found in the change propagation page : Support for 3rd party clients, that is, client wikis and other consumers > outside of Wikimedia, i