Hey Denny! Awesome tool!
It's so awesome, we are already wondering about how to handle the load this may
generate.
As far as I can see, qlabel uses the wbgetentities API module. This has the
advantage of allowing the labels for all relevant entities to be fetched with a
single query, but it has
On 1 April 2014 20:01, Denny Vrandečić vrande...@google.com wrote:
a bug on the github project
I've raised another, about the use of adjectives and adverbs:
https://github.com/googleknowledge/qlabel/issues/2
--
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk
Am 02.04.2014 11:04, schrieb Magnus Manske:
The ../entity/Q12345.json won't work, because of cross-domain browser
limitations? Unless wikidata allows these server-side (forgot what the
mechanism
was called).
It's called JsonP. We could support it, but it would render the URL
uncacheable...
It's called JsonP. We could support it, but it would render the URL
uncacheable... bah, annoying.
CORS to the rescue? Or did I miss something? Sorry in that case.
--
Thomas Steiner, Employee, Google Inc.
http://blog.tomayac.com, http://twitter.com/tomayac
-BEGIN PGP SIGNATURE-
CORS is indeed pretty well supported now
http://caniuse.com/cors
Mohamed
On Wed, Apr 2, 2014 at 12:29 PM, Thomas Steiner to...@google.com wrote:
It's called JsonP. We could support it, but it would render the URL
uncacheable... bah, annoying.
CORS to the rescue? Or did I miss something?
Hoi Max,
Is it possible to compare your index with the items in Wikidata. There are
several things that I would like to do
* add all coordinates to Wikidata items
* report on all coordinates where what you know differs from Wikidata
A next obvious question is how can we keep the two data sets in
That's the one!
On Wed, Apr 2, 2014 at 11:33 AM, Innovimax SARL innovi...@gmail.com wrote:
CORS is indeed pretty well supported now
http://caniuse.com/cors
Mohamed
On Wed, Apr 2, 2014 at 12:29 PM, Thomas Steiner to...@google.com wrote:
It's called JsonP. We could support it, but it
Yes, if it's enabled on Wikidata.
On Wed, Apr 2, 2014 at 1:26 PM, Daniel Kinzler
daniel.kinz...@wikimedia.dewrote:
Am 02.04.2014 14:12, schrieb Magnus Manske:
That's the one!
CORS should work fine with the cacheable URLs.
-- daniel
--
Daniel Kinzler
Senior Software Developer
Indeed, and this is the good part about it. It's solvable server side and
Wikidata is a server, so I just a matter of opening a bug, isn'it ?
It seems there is already bunch of them open
https://bugzilla.wikimedia.org/buglist.cgi?quicksearch=CORS
Mohamed
On Wed, Apr 2, 2014 at 2:59 PM, Magnus
I've been thinking about this kind of problem in my own systems. Name
and link generation from entities is a cross-cutting concern that's
best separated from other queries in your application. With SPARQL
and multiple languages each with multiple rdf:label it is awkward to
write queries that
Could one of the front-ends (squid?) perform a simple batch service, by
just concatenating the /entity/ JSON for requested items? That could
effectively run on the cache and still deliver batches.
On Wed, Apr 2, 2014 at 4:44 PM, Paul Houle ontolo...@gmail.com wrote:
I've been thinking about
Of course. You can cache the individual entities somewhere inside the
server-system where they can be stuck together very quickly, or you
can cache them on the client.
On Wed, Apr 2, 2014 at 12:04 PM, Magnus Manske
magnusman...@googlemail.com wrote:
Could one of the front-ends (squid?) perform
That's a toughie. Looking forward to see that one resolved :)
On Wed, Apr 2, 2014 at 2:14 AM, Andy Mabbett a...@pigsonthewing.org.ukwrote:
On 1 April 2014 20:01, Denny Vrandečić vrande...@google.com wrote:
a bug on the github project
I've raised another, about the use of adjectives and
Yes.
That is why qLabel has a mechanism to implement your own loaders. The
Wikidata and Freebase loaders are much more efficient than the generic RDF
loader. Using SPARQL, RDF loading can be made more effective, but the LOD
protocols break down with regards to that.
Such a basic thing like
On Wed, Apr 2, 2014 at 8:57 PM, Denny Vrandečić vrande...@google.com wrote:
What I am much more worried about is that we -- if my understanding is
current and correct -- do not even count accesses to the Wikidata web API,
in particular not which modules are called. So, in short, we actually
Hello all,
I think we should create a property for the items of Wikimapia, they are of
additional value to Wikipedia articles as they mark the area of a certain
subject instead of only a coordinate.
http://wikimapia.org
Romaine
___
Wikidata-l
You should visit [[WD:PP]]([1]) and its subpages for proposing property.
[1]: https://www.wikidata.org/wiki/WD:PP
-Yena Hong (Revi)
Wikimedian
-- Sent from Android --
2014. 4. 3. 오전 8:29에 Romaine Wiki romaine_w...@yahoo.com님이 작성:
Hello all,
I think we should create a property for the items
17 matches
Mail list logo
