You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by Andy Seaborne <an...@apache.org> on 2017/09/01 11:42:28 UTC
Re: SPARQL LOAD Error on Fuseki 3.4.0
On 31/08/17 15:35, Yasunori Yamamoto wrote:
> Thank you for your quick response.
> On the 3.5.0-SNAPSHOT, SPARQL LOAD queries work fine.
>
> In addition, as this issue also happens on the 2.6.0, some UTF-8 characters make something wrong.
> For example, the following errors occur.
> 1. Caused by: org.apache.jena.riot.RiotException: [line: 522, col: 15] Failed to find a prefix name or keyword: ―(8213;0x2015)
> 2. Caused by: org.apache.jena.riot.RiotException: [line: 496, col: 14] Failed to find a prefix name or keyword: ☆(9734;0x2606)
>
> The former was caused by “LOAD <http://ja.dbpedia.org/resource/富士山>", and the latter was caused by "LOAD <http://ja.dbpedia.org/resource/東京都>".
>
> I hope these will be fixed soon.
I'm afraid that's not enough information to start to investigate.
> [line: 522, col: 15]
That's in the data. Looks like a misused ―(8213;0x2015; name "Horizontal
Bar") instead of "-" (0x002D; "Hyphen-Minus") in a prefix name.
Make sure the far end is sending correct data with the correct HTTP
headers. (I found it sending back "text/rdf+n3" (N3 is not the same as
Turles in prefix names), the NT version isn't N-triples and the RDF/XML
version is broken in yet more ways as well).
Then please check the tickets and raise a new one if there is nothing
present with a standalone, small example.
Even better, submit a fix!
Andy
>
> Regards,
> Yasunori
> 差出人: Andy Seaborne
> 送信日時: 平成 29年8月31日 17:36
> 宛先: users@jena.apache.org
> 件名: Re: SPARQL LOAD Error on Fuseki 3.4.0
>
>
>
> On 31/08/17 07:51, Yasunori Yamamoto wrote:
>> Hello, I have switched Fuseki from 2.6.0 to 3.4.0 and found that the SPARQL LOAD query failed, which didn’t on 2.6.0.
>> When starting up with the option --update and issuing the update query to the SPARQL update endpoint (i.e., “LOAD <http://dbpedia.org/resource/Joseph_Hocking>” to http://localhost:3030/myDB/update ), I encountered the HTTP 500 error.
>> The server said the following.
>>
>> Caused by: org.apache.jena.riot.RiotException: Failed to determine the content type: (URI=http://dbpedia.org/resource/Joseph_Hocking : stream=text/html)
>>
>> This issue also happened to another dataset server’s URI.
>>
>> Caused by: org.apache.jena.riot.RiotException: Failed to determine the content type: (URI=http://www.wikidata.org/entity/Q2 : stream=application/json)
>>
>> The both didn’t happen if I use Fuseki 2.6.0.
>>
>> Regards,
>> Yasunori
>>
>
> Hello there,
>
> This looks like https://issues.apache.org/jira/browse/JENA-1378 which is
> about content negotiation when redirection is happening.
>
> It is fixed in the development snapshot builds.
>
> If you want the data itself, you can get it directly from DBpedia as:
>
> http://dbpedia.org/data/Joseph_Hocking.xml
>
> or
>
> https://www.wikidata.org/wiki/Special:EntityData/Q2.rdf
>
> though of course, if this is part of a process, fixing up URLs
> temporarily isn't satisfactory.
>
> Would you be able to try out a development build please? The more
> verification we get in as varied conditions the better.
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/jena/
>
>
> Andy
>
>
Re: SPARQL LOAD Error on Fuseki 3.4.0
Posted by "Lorenz B." <bu...@informatik.uni-leipzig.de>.
That is exactly the issue with the Virtuoso serializer - Github tickets
are still open. Now it means waiting or trying between the other
serializers provided by Virtuoso.
> Use the full URI. They aren't in the escapable set.
>
> Or the data needs to agree on %-encoding - which is not an escape
> mechanism, The %-X-X really is in the URI.
>
> I've forgotten why these characters are excluded (Eric Prud'hommeaux
> may remember - he sorted that part of the spec out - it comes from
> SPARQL 1.0 and that goes back to W3c policy at the time and XML 1.0
> NameStartChar (rule [4] in XML 1.0). There are(were?) concerns about
> codepoints that look the same with dereferencable entities.
>
> In the case of HORIZONTAL BAR, is that a mistake for Hyphen-Minus anyway?
>
> Andy
>
> On 01/09/17 16:34, Yasunori Yamamoto wrote:
>> Thank you for telling me the issue.
>> I confirmed that uploading an RDF/XML file of the one of the above URI
>> made no error (<http://ja.dbpedia.org/resource/富士山>).
>> The problem is that some illegal characters such as WHITE STAR or
>> HORIZONTAL BAR are in the prefixed URI or PN_LOCAL, which should be
>> escaped?
>>
>> https://www.w3.org/TR/turtle/#grammar-production-PN_LOCAL
>>
>> Yasunori
>>
>> 2017-09-01 21:10 GMT+09:00 Lorenz Buehmann
>> <bu...@informatik.uni-leipzig.de>:
>>>
>>>
>>>>
>>>>
>>>> On 31/08/17 15:35, Yasunori Yamamoto wrote:
>>>>> Thank you for your quick response.
>>>>> On the 3.5.0-SNAPSHOT, SPARQL LOAD queries work fine.
>>>>>
>>>>> In addition, as this issue also happens on the 2.6.0, some UTF-8
>>>>> characters make something wrong.
>>>>> For example, the following errors occur.
>>>>> 1. Caused by: org.apache.jena.riot.RiotException: [line: 522, col:
>>>>> 15] Failed to find a prefix name or keyword: ―(8213;0x2015)
>>>>> 2. Caused by: org.apache.jena.riot.RiotException: [line: 496, col:
>>>>> 14] Failed to find a prefix name or keyword: ☆(9734;0x2606)
>>>>
>>>>>
>>>>> The former was caused by “LOAD
>>>>> <http://ja.dbpedia.org/resource/富士山>",
>>>>> and the latter was caused by "LOAD
>>>>> <http://ja.dbpedia.org/resource/東京都>".
>>>>>
>>>>> I hope these will be fixed soon.
>>>>
>>>> I'm afraid that's not enough information to start to investigate.
>>>>
>>>>> [line: 522, col: 15]
>>>>
>>>> That's in the data. Looks like a misused ―(8213;0x2015; name
>>>> "Horizontal Bar") instead of "-" (0x002D; "Hyphen-Minus") in a prefix
>>>> name.
>>>>
>>>> Make sure the far end is sending correct data with the correct HTTP
>>>> headers. (I found it sending back "text/rdf+n3" (N3 is not the same as
>>>> Turles in prefix names), the NT version isn't N-triples and the
>>>> RDF/XML version is broken in yet more ways as well).
>>>
>>> Andy is right. That's probably another issue with the Virtuoso triple
>>> store serializers.
>>>
>>> I raised two issues some time ago [1], [2] - doesn't look that they
>>> have
>>> been fixed so far (or maybe only in Virtuoso 8.x once it will be
>>> released).
>>>
>>> Your issue might be different or related - you should ask the
>>> developers.
>>>
>>>
>>> [1] https://github.com/openlink/virtuoso-opensource/issues/569
>>>
>>> [2] https://github.com/openlink/virtuoso-opensource/issues/567
>>>
>>>>
>>>> Then please check the tickets and raise a new one if there is nothing
>>>> present with a standalone, small example.
>>>>
>>>> Even better, submit a fix!
>>>>
>>>> Andy
>>>>
>>>>>
>>>>> Regards,
>>>>> Yasunori
>>>>> 差出人: Andy Seaborne
>>>>> 送信日時: 平成 29年8月31日 17:36
>>>>> 宛先: users@jena.apache.org
>>>>> 件名: Re: SPARQL LOAD Error on Fuseki 3.4.0
>>>>>
>>>>>
>>>>>
>>>>> On 31/08/17 07:51, Yasunori Yamamoto wrote:
>>>>>> Hello, I have switched Fuseki from 2.6.0 to 3.4.0 and found that the
>>>>>> SPARQL LOAD query failed, which didn’t on 2.6.0.
>>>>>> When starting up with the option --update and issuing the update
>>>>>> query to the SPARQL update endpoint (i.e., “LOAD
>>>>>> <http://dbpedia.org/resource/Joseph_Hocking>” to
>>>>>> http://localhost:3030/myDB/update ), I encountered the HTTP 500
>>>>>> error.
>>>>>> The server said the following.
>>>>>>
>>>>>> Caused by: org.apache.jena.riot.RiotException: Failed to determine
>>>>>> the content type: (URI=http://dbpedia.org/resource/Joseph_Hocking :
>>>>>> stream=text/html)
>>>>>>
>>>>>> This issue also happened to another dataset server’s URI.
>>>>>>
>>>>>> Caused by: org.apache.jena.riot.RiotException: Failed to determine
>>>>>> the content type: (URI=http://www.wikidata.org/entity/Q2 :
>>>>>> stream=application/json)
>>>>>>
>>>>>> The both didn’t happen if I use Fuseki 2.6.0.
>>>>>>
>>>>>> Regards,
>>>>>> Yasunori
>>>>>>
>>>>>
>>>>> Hello there,
>>>>>
>>>>> This looks like https://issues.apache.org/jira/browse/JENA-1378
>>>>> which is
>>>>> about content negotiation when redirection is happening.
>>>>>
>>>>> It is fixed in the development snapshot builds.
>>>>>
>>>>> If you want the data itself, you can get it directly from DBpedia as:
>>>>>
>>>>> http://dbpedia.org/data/Joseph_Hocking.xml
>>>>>
>>>>> or
>>>>>
>>>>> https://www.wikidata.org/wiki/Special:EntityData/Q2.rdf
>>>>>
>>>>> though of course, if this is part of a process, fixing up URLs
>>>>> temporarily isn't satisfactory.
>>>>>
>>>>> Would you be able to try out a development build please? The more
>>>>> verification we get in as varied conditions the better.
>>>>>
>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/jena/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Andy
>>>>>
>>>>>
>>>
>
--
Lorenz Bühmann
AKSW group, University of Leipzig
Group: http://aksw.org - semantic web research center
Re: SPARQL LOAD Error on Fuseki 3.4.0
Posted by Andy Seaborne <an...@apache.org>.
Use the full URI. They aren't in the escapable set.
Or the data needs to agree on %-encoding - which is not an escape
mechanism, The %-X-X really is in the URI.
I've forgotten why these characters are excluded (Eric Prud'hommeaux may
remember - he sorted that part of the spec out - it comes from SPARQL
1.0 and that goes back to W3c policy at the time and XML 1.0
NameStartChar (rule [4] in XML 1.0). There are(were?) concerns about
codepoints that look the same with dereferencable entities.
In the case of HORIZONTAL BAR, is that a mistake for Hyphen-Minus anyway?
Andy
On 01/09/17 16:34, Yasunori Yamamoto wrote:
> Thank you for telling me the issue.
> I confirmed that uploading an RDF/XML file of the one of the above URI
> made no error (<http://ja.dbpedia.org/resource/富士山>).
> The problem is that some illegal characters such as WHITE STAR or
> HORIZONTAL BAR are in the prefixed URI or PN_LOCAL, which should be
> escaped?
>
> https://www.w3.org/TR/turtle/#grammar-production-PN_LOCAL
>
> Yasunori
>
> 2017-09-01 21:10 GMT+09:00 Lorenz Buehmann <bu...@informatik.uni-leipzig.de>:
>>
>>
>>>
>>>
>>> On 31/08/17 15:35, Yasunori Yamamoto wrote:
>>>> Thank you for your quick response.
>>>> On the 3.5.0-SNAPSHOT, SPARQL LOAD queries work fine.
>>>>
>>>> In addition, as this issue also happens on the 2.6.0, some UTF-8
>>>> characters make something wrong.
>>>> For example, the following errors occur.
>>>> 1. Caused by: org.apache.jena.riot.RiotException: [line: 522, col:
>>>> 15] Failed to find a prefix name or keyword: ―(8213;0x2015)
>>>> 2. Caused by: org.apache.jena.riot.RiotException: [line: 496, col:
>>>> 14] Failed to find a prefix name or keyword: ☆(9734;0x2606)
>>>
>>>>
>>>> The former was caused by “LOAD <http://ja.dbpedia.org/resource/富士山>",
>>>> and the latter was caused by "LOAD
>>>> <http://ja.dbpedia.org/resource/東京都>".
>>>>
>>>> I hope these will be fixed soon.
>>>
>>> I'm afraid that's not enough information to start to investigate.
>>>
>>>> [line: 522, col: 15]
>>>
>>> That's in the data. Looks like a misused ―(8213;0x2015; name
>>> "Horizontal Bar") instead of "-" (0x002D; "Hyphen-Minus") in a prefix
>>> name.
>>>
>>> Make sure the far end is sending correct data with the correct HTTP
>>> headers. (I found it sending back "text/rdf+n3" (N3 is not the same as
>>> Turles in prefix names), the NT version isn't N-triples and the
>>> RDF/XML version is broken in yet more ways as well).
>>
>> Andy is right. That's probably another issue with the Virtuoso triple
>> store serializers.
>>
>> I raised two issues some time ago [1], [2] - doesn't look that they have
>> been fixed so far (or maybe only in Virtuoso 8.x once it will be released).
>>
>> Your issue might be different or related - you should ask the developers.
>>
>>
>> [1] https://github.com/openlink/virtuoso-opensource/issues/569
>>
>> [2] https://github.com/openlink/virtuoso-opensource/issues/567
>>
>>>
>>> Then please check the tickets and raise a new one if there is nothing
>>> present with a standalone, small example.
>>>
>>> Even better, submit a fix!
>>>
>>> Andy
>>>
>>>>
>>>> Regards,
>>>> Yasunori
>>>> 差出人: Andy Seaborne
>>>> 送信日時: 平成 29年8月31日 17:36
>>>> 宛先: users@jena.apache.org
>>>> 件名: Re: SPARQL LOAD Error on Fuseki 3.4.0
>>>>
>>>>
>>>>
>>>> On 31/08/17 07:51, Yasunori Yamamoto wrote:
>>>>> Hello, I have switched Fuseki from 2.6.0 to 3.4.0 and found that the
>>>>> SPARQL LOAD query failed, which didn’t on 2.6.0.
>>>>> When starting up with the option --update and issuing the update
>>>>> query to the SPARQL update endpoint (i.e., “LOAD
>>>>> <http://dbpedia.org/resource/Joseph_Hocking>” to
>>>>> http://localhost:3030/myDB/update ), I encountered the HTTP 500 error.
>>>>> The server said the following.
>>>>>
>>>>> Caused by: org.apache.jena.riot.RiotException: Failed to determine
>>>>> the content type: (URI=http://dbpedia.org/resource/Joseph_Hocking :
>>>>> stream=text/html)
>>>>>
>>>>> This issue also happened to another dataset server’s URI.
>>>>>
>>>>> Caused by: org.apache.jena.riot.RiotException: Failed to determine
>>>>> the content type: (URI=http://www.wikidata.org/entity/Q2 :
>>>>> stream=application/json)
>>>>>
>>>>> The both didn’t happen if I use Fuseki 2.6.0.
>>>>>
>>>>> Regards,
>>>>> Yasunori
>>>>>
>>>>
>>>> Hello there,
>>>>
>>>> This looks like https://issues.apache.org/jira/browse/JENA-1378 which is
>>>> about content negotiation when redirection is happening.
>>>>
>>>> It is fixed in the development snapshot builds.
>>>>
>>>> If you want the data itself, you can get it directly from DBpedia as:
>>>>
>>>> http://dbpedia.org/data/Joseph_Hocking.xml
>>>>
>>>> or
>>>>
>>>> https://www.wikidata.org/wiki/Special:EntityData/Q2.rdf
>>>>
>>>> though of course, if this is part of a process, fixing up URLs
>>>> temporarily isn't satisfactory.
>>>>
>>>> Would you be able to try out a development build please? The more
>>>> verification we get in as varied conditions the better.
>>>>
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/jena/
>>>>
>>>>
>>>>
>>>> Andy
>>>>
>>>>
>>
Re: SPARQL LOAD Error on Fuseki 3.4.0
Posted by Yasunori Yamamoto <yy...@dbcls.rois.ac.jp>.
Thank you for telling me the issue.
I confirmed that uploading an RDF/XML file of the one of the above URI
made no error (<http://ja.dbpedia.org/resource/富士山>).
The problem is that some illegal characters such as WHITE STAR or
HORIZONTAL BAR are in the prefixed URI or PN_LOCAL, which should be
escaped?
https://www.w3.org/TR/turtle/#grammar-production-PN_LOCAL
Yasunori
2017-09-01 21:10 GMT+09:00 Lorenz Buehmann <bu...@informatik.uni-leipzig.de>:
>
>
>>
>>
>> On 31/08/17 15:35, Yasunori Yamamoto wrote:
>>> Thank you for your quick response.
>>> On the 3.5.0-SNAPSHOT, SPARQL LOAD queries work fine.
>>>
>>> In addition, as this issue also happens on the 2.6.0, some UTF-8
>>> characters make something wrong.
>>> For example, the following errors occur.
>>> 1. Caused by: org.apache.jena.riot.RiotException: [line: 522, col:
>>> 15] Failed to find a prefix name or keyword: ―(8213;0x2015)
>>> 2. Caused by: org.apache.jena.riot.RiotException: [line: 496, col:
>>> 14] Failed to find a prefix name or keyword: ☆(9734;0x2606)
>>
>>>
>>> The former was caused by “LOAD <http://ja.dbpedia.org/resource/富士山>",
>>> and the latter was caused by "LOAD
>>> <http://ja.dbpedia.org/resource/東京都>".
>>>
>>> I hope these will be fixed soon.
>>
>> I'm afraid that's not enough information to start to investigate.
>>
>> > [line: 522, col: 15]
>>
>> That's in the data. Looks like a misused ―(8213;0x2015; name
>> "Horizontal Bar") instead of "-" (0x002D; "Hyphen-Minus") in a prefix
>> name.
>>
>> Make sure the far end is sending correct data with the correct HTTP
>> headers. (I found it sending back "text/rdf+n3" (N3 is not the same as
>> Turles in prefix names), the NT version isn't N-triples and the
>> RDF/XML version is broken in yet more ways as well).
>
> Andy is right. That's probably another issue with the Virtuoso triple
> store serializers.
>
> I raised two issues some time ago [1], [2] - doesn't look that they have
> been fixed so far (or maybe only in Virtuoso 8.x once it will be released).
>
> Your issue might be different or related - you should ask the developers.
>
>
> [1] https://github.com/openlink/virtuoso-opensource/issues/569
>
> [2] https://github.com/openlink/virtuoso-opensource/issues/567
>
>>
>> Then please check the tickets and raise a new one if there is nothing
>> present with a standalone, small example.
>>
>> Even better, submit a fix!
>>
>> Andy
>>
>>>
>>> Regards,
>>> Yasunori
>>> 差出人: Andy Seaborne
>>> 送信日時: 平成 29年8月31日 17:36
>>> 宛先: users@jena.apache.org
>>> 件名: Re: SPARQL LOAD Error on Fuseki 3.4.0
>>>
>>>
>>>
>>> On 31/08/17 07:51, Yasunori Yamamoto wrote:
>>>> Hello, I have switched Fuseki from 2.6.0 to 3.4.0 and found that the
>>>> SPARQL LOAD query failed, which didn’t on 2.6.0.
>>>> When starting up with the option --update and issuing the update
>>>> query to the SPARQL update endpoint (i.e., “LOAD
>>>> <http://dbpedia.org/resource/Joseph_Hocking>” to
>>>> http://localhost:3030/myDB/update ), I encountered the HTTP 500 error.
>>>> The server said the following.
>>>>
>>>> Caused by: org.apache.jena.riot.RiotException: Failed to determine
>>>> the content type: (URI=http://dbpedia.org/resource/Joseph_Hocking :
>>>> stream=text/html)
>>>>
>>>> This issue also happened to another dataset server’s URI.
>>>>
>>>> Caused by: org.apache.jena.riot.RiotException: Failed to determine
>>>> the content type: (URI=http://www.wikidata.org/entity/Q2 :
>>>> stream=application/json)
>>>>
>>>> The both didn’t happen if I use Fuseki 2.6.0.
>>>>
>>>> Regards,
>>>> Yasunori
>>>>
>>>
>>> Hello there,
>>>
>>> This looks like https://issues.apache.org/jira/browse/JENA-1378 which is
>>> about content negotiation when redirection is happening.
>>>
>>> It is fixed in the development snapshot builds.
>>>
>>> If you want the data itself, you can get it directly from DBpedia as:
>>>
>>> http://dbpedia.org/data/Joseph_Hocking.xml
>>>
>>> or
>>>
>>> https://www.wikidata.org/wiki/Special:EntityData/Q2.rdf
>>>
>>> though of course, if this is part of a process, fixing up URLs
>>> temporarily isn't satisfactory.
>>>
>>> Would you be able to try out a development build please? The more
>>> verification we get in as varied conditions the better.
>>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/jena/
>>>
>>>
>>>
>>> Andy
>>>
>>>
>
Re: SPARQL LOAD Error on Fuseki 3.4.0
Posted by Lorenz Buehmann <bu...@informatik.uni-leipzig.de>.
>
>
> On 31/08/17 15:35, Yasunori Yamamoto wrote:
>> Thank you for your quick response.
>> On the 3.5.0-SNAPSHOT, SPARQL LOAD queries work fine.
>>
>> In addition, as this issue also happens on the 2.6.0, some UTF-8
>> characters make something wrong.
>> For example, the following errors occur.
>> 1. Caused by: org.apache.jena.riot.RiotException: [line: 522, col:
>> 15] Failed to find a prefix name or keyword: ―(8213;0x2015)
>> 2. Caused by: org.apache.jena.riot.RiotException: [line: 496, col:
>> 14] Failed to find a prefix name or keyword: ☆(9734;0x2606)
>
>>
>> The former was caused by “LOAD <http://ja.dbpedia.org/resource/富士山>",
>> and the latter was caused by "LOAD
>> <http://ja.dbpedia.org/resource/東京都>".
>>
>> I hope these will be fixed soon.
>
> I'm afraid that's not enough information to start to investigate.
>
> > [line: 522, col: 15]
>
> That's in the data. Looks like a misused ―(8213;0x2015; name
> "Horizontal Bar") instead of "-" (0x002D; "Hyphen-Minus") in a prefix
> name.
>
> Make sure the far end is sending correct data with the correct HTTP
> headers. (I found it sending back "text/rdf+n3" (N3 is not the same as
> Turles in prefix names), the NT version isn't N-triples and the
> RDF/XML version is broken in yet more ways as well).
Andy is right. That's probably another issue with the Virtuoso triple
store serializers.
I raised two issues some time ago [1], [2] - doesn't look that they have
been fixed so far (or maybe only in Virtuoso 8.x once it will be released).
Your issue might be different or related - you should ask the developers.
[1] https://github.com/openlink/virtuoso-opensource/issues/569
[2] https://github.com/openlink/virtuoso-opensource/issues/567
>
> Then please check the tickets and raise a new one if there is nothing
> present with a standalone, small example.
>
> Even better, submit a fix!
>
> Andy
>
>>
>> Regards,
>> Yasunori
>> 差出人: Andy Seaborne
>> 送信日時: 平成 29年8月31日 17:36
>> 宛先: users@jena.apache.org
>> 件名: Re: SPARQL LOAD Error on Fuseki 3.4.0
>>
>>
>>
>> On 31/08/17 07:51, Yasunori Yamamoto wrote:
>>> Hello, I have switched Fuseki from 2.6.0 to 3.4.0 and found that the
>>> SPARQL LOAD query failed, which didn’t on 2.6.0.
>>> When starting up with the option --update and issuing the update
>>> query to the SPARQL update endpoint (i.e., “LOAD
>>> <http://dbpedia.org/resource/Joseph_Hocking>” to
>>> http://localhost:3030/myDB/update ), I encountered the HTTP 500 error.
>>> The server said the following.
>>>
>>> Caused by: org.apache.jena.riot.RiotException: Failed to determine
>>> the content type: (URI=http://dbpedia.org/resource/Joseph_Hocking :
>>> stream=text/html)
>>>
>>> This issue also happened to another dataset server’s URI.
>>>
>>> Caused by: org.apache.jena.riot.RiotException: Failed to determine
>>> the content type: (URI=http://www.wikidata.org/entity/Q2 :
>>> stream=application/json)
>>>
>>> The both didn’t happen if I use Fuseki 2.6.0.
>>>
>>> Regards,
>>> Yasunori
>>>
>>
>> Hello there,
>>
>> This looks like https://issues.apache.org/jira/browse/JENA-1378 which is
>> about content negotiation when redirection is happening.
>>
>> It is fixed in the development snapshot builds.
>>
>> If you want the data itself, you can get it directly from DBpedia as:
>>
>> http://dbpedia.org/data/Joseph_Hocking.xml
>>
>> or
>>
>> https://www.wikidata.org/wiki/Special:EntityData/Q2.rdf
>>
>> though of course, if this is part of a process, fixing up URLs
>> temporarily isn't satisfactory.
>>
>> Would you be able to try out a development build please? The more
>> verification we get in as varied conditions the better.
>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/jena/
>>
>>
>>
>> Andy
>>
>>