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.wikidata.org/entity/.
No problems about any confusion: I see it as a useful learning exercise. For example, I was also going to comment on your double-redirect strategy, but having checked it in Vapour I then re-read the Cool URIs document and realised that it is an impeccable implementation of one of the strategies described there. So now I know more than I did yesterday. :-)
Best wishes,
Richard
On 27/08/2015 11:37, Daniel Kinzler wrote:
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 identifiers, and should not show up in our output anywhere.
You can see the changes I made to the documentation here: https://www.wikidata.org/w/index.php?title=Wikidata%3AData_access&type=r...
Sorry about the confusion.
-- daniel
Am 27.08.2015 um 09:20 schrieb Richard Light:
This described a postfix pattern which delivers RDF XML (e.g. [2]). However, this pattern is itself subject to content negotiation, and an initial 303 response converts the URL to e.g. [3]. I am interested in knowing what pattern of URL will deliver RDF/XML /without /requiring content negotiation, and the answer to that question is not [2] but [3]. This matters, for example, in scenarios where one wants to use XSLT's document() function to retrieve an RDF XML response directly. The URL pattern [2] will fail. So the documentation is currently unhelpful.
[...]
[1] https://www.wikidata.org/wiki/Wikidata:Data_access [2] https://www.wikidata.org/entity/Q3807415.rdf [3] https://www.wikidata.org/wiki/Special:EntityData/Q3807415.rdf