Hi!
> For SELECT queries, the response format is
> application/sparql-results+xml by default (even without specifying the
> format parameter), and the only other format I could persuade it to
> offer was JSON (with format=json).
Yes, the query supports only xml and json formats now.
> For CONSTR
Hi all!
We have some breaking API changes that will soon be deployed to wikidata.org.
The deployment date should be: 9th September 2015 (just under 2 weeks)
The change making the breaks an be found at:
https://gerrit.wikimedia.org/r/#/c/227686/
The breaking changes are:
- XML output alia
On Thu, Aug 27, 2015 at 12:49 PM, Richard Light
wrote:
> Hi Daniel,
>
> Thanks for updating the page. I think, however, you have been a bit
> over-zealous in changing the URLs. The sentence:
>
> For example, the concept URI of Douglas Adams is
> http://www.wikidata.org/wiki/Special:EntityData/Q4
Hi Daniel,
Thanks for updating the page. I think, however, you have been a bit
over-zealous in changing the URLs. The sentence:
For example, the /concept URI/ of Douglas Adams is
http://www.wikidata.org/wiki/Special:EntityData/Q42.
should I think use the concept namespace http://www.wikid
Hi Richard!
You are right, the Data access documentation did not properly distinguish
between concept URI and data URL. I have fixed this now. URLs of the form
https://www.wikidata.org/entity/Q3807415.rdf are not canonical at all - we
support them for convenience, but they should not be used as id
On 26.08.2015 23:49, Daniel Kinzler wrote:
Am 26.08.2015 um 17:08 schrieb Markus Krötzsch:
Ok, but when a user edits a wiki thourgh the browser, this is not related to the
API anyway, is it?
It is. The UI uses the same API calls a bot would use.
Right, of course, but since my code is unlike
On 27.08.2015 00:51, Hong, Yongmin wrote:
Sometimes when community want to approve tasks for already flagged bot,
they want bot doesn't mark their task as bot edit so it appears on RC
and Watchlist as non-bot edit. I think this can be a reason?
Thanks. This is a relevant use case indeed! I will
Bene,
Thanks for this. Yes, that works.
For SELECT queries, the response format is
application/sparql-results+xml by default (even without specifying the
format parameter), and the only other format I could persuade it to
offer was JSON (with format=json).
For CONSTRUCT queries (the useful
Hi Richard,
I can only answer the last part of your question but you can access the
SPARQL endpoint directly under
wdqs-beta.wmflabs.org/bigdata/namespace/wdq/sparql?query= and I think
you can also add a format parameter to specify in which format the
result should be returned.
Best regards
Hi,
I am doing some 'kicking the tyres' tests on Wikidata as Linked Data. I
like the SPARQL end-point, which is more helpful than most, and
successfully managed a query for "people with the surname Light" last
night. (Only five of them in the world, apparently, but that's another
matter. :
10 matches
Mail list logo