|
From: Jason K. <jb...@en...> - 2017-07-01 00:32:42
|
Hi there, Thanks for the great project. I am trying to use this for backend of my project. Though Blazegraph looks not that active for now, it is the fastest SPARQL endpoint in my experiences. I am trying to parse my SPARQL query result with Turtle, but Blazegraph does not return Turtle format but OWL/XML format, that my library cannot parse. I specifically did following command: curl -X POST http://localhost:9999/blazegraph/sparql --data-urlencode 'query=<queryStr>' -H 'Accept: text/turtle' I checked that this is correct: https://jira.blazegraph.com/browse/BLZG-1689 but it only returns in OWL format. Thanks in advance! With regards, Jason Koh cseweb.ucsd.edu/~jbkoh |
|
From: Jason K. <jb...@en...> - 2017-07-01 00:52:58
|
I tried application/x-turtle also, which does work. With regards, Jason Koh cseweb.ucsd.edu/~jbkoh On Fri, Jun 30, 2017 at 5:26 PM, Jason Koh <jb...@en...> wrote: > Btw, Build Version=2.1.4 > > > With regards, > Jason Koh > cseweb.ucsd.edu/~jbkoh > > On Fri, Jun 30, 2017 at 5:09 PM, Jason Koh <jb...@en...> wrote: > >> Hi there, >> >> Thanks for the great project. I am trying to use this for backend of my >> project. Though Blazegraph looks not that active for now, it is the fastest >> SPARQL endpoint in my experiences. >> >> I am trying to parse my SPARQL query result with Turtle, but Blazegraph >> does not return Turtle format but OWL/XML format, that my library cannot >> parse. I specifically did following command: >> curl -X POST http://localhost:9999/blazegraph/sparql --data-urlencode >> 'query=<queryStr>' -H 'Accept: text/turtle' >> I checked that this is correct: https://jira.blazegra >> ph.com/browse/BLZG-1689 >> but it only returns in OWL format. >> >> Thanks in advance! >> >> >> With regards, >> Jason Koh >> cseweb.ucsd.edu/~jbkoh >> > > |
|
From: Bryan T. <br...@bl...> - 2017-07-01 03:06:18
|
Glad you figured it out. The supported formats are defined here: https://wiki.blazegraph.com/wiki/index.php/REST_API#MIME_Types Thanks, Bryan On Fri, Jun 30, 2017 at 5:52 PM, Jason Koh <jb...@en...> wrote: > I tried application/x-turtle also, which does work. > > > With regards, > Jason Koh > cseweb.ucsd.edu/~jbkoh > > On Fri, Jun 30, 2017 at 5:26 PM, Jason Koh <jb...@en...> wrote: >> >> Btw, Build Version=2.1.4 >> >> >> With regards, >> Jason Koh >> cseweb.ucsd.edu/~jbkoh >> >> On Fri, Jun 30, 2017 at 5:09 PM, Jason Koh <jb...@en...> wrote: >>> >>> Hi there, >>> >>> Thanks for the great project. I am trying to use this for backend of my >>> project. Though Blazegraph looks not that active for now, it is the fastest >>> SPARQL endpoint in my experiences. >>> >>> I am trying to parse my SPARQL query result with Turtle, but Blazegraph >>> does not return Turtle format but OWL/XML format, that my library cannot >>> parse. I specifically did following command: >>> curl -X POST http://localhost:9999/blazegraph/sparql --data-urlencode >>> 'query=<queryStr>' -H 'Accept: text/turtle' >>> I checked that this is correct: >>> https://jira.blazegraph.com/browse/BLZG-1689 >>> but it only returns in OWL format. >>> >>> Thanks in advance! >>> >>> >>> With regards, >>> Jason Koh >>> cseweb.ucsd.edu/~jbkoh >> >> > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > |
|
From: Jason K. <jb...@en...> - 2017-07-01 02:39:59
|
Oh sorry, it was a typo. I tried application/x-turtle also, which does NOT work. With regards, Jason Koh cseweb.ucsd.edu/~jbkoh On Fri, Jun 30, 2017 at 7:38 PM, Bryan Thompson <br...@bl...> wrote: > Glad you figured it out. The supported formats are defined here: > https://wiki.blazegraph.com/wiki/index.php/REST_API#MIME_Types > > Thanks, > Bryan > > On Fri, Jun 30, 2017 at 5:52 PM, Jason Koh <jb...@en...> wrote: > > I tried application/x-turtle also, which does work. > > > > > > With regards, > > Jason Koh > > cseweb.ucsd.edu/~jbkoh > > > > On Fri, Jun 30, 2017 at 5:26 PM, Jason Koh <jb...@en...> wrote: > >> > >> Btw, Build Version=2.1.4 > >> > >> > >> With regards, > >> Jason Koh > >> cseweb.ucsd.edu/~jbkoh > >> > >> On Fri, Jun 30, 2017 at 5:09 PM, Jason Koh <jb...@en...> wrote: > >>> > >>> Hi there, > >>> > >>> Thanks for the great project. I am trying to use this for backend of my > >>> project. Though Blazegraph looks not that active for now, it is the > fastest > >>> SPARQL endpoint in my experiences. > >>> > >>> I am trying to parse my SPARQL query result with Turtle, but Blazegraph > >>> does not return Turtle format but OWL/XML format, that my library > cannot > >>> parse. I specifically did following command: > >>> curl -X POST http://localhost:9999/blazegraph/sparql --data-urlencode > >>> 'query=<queryStr>' -H 'Accept: text/turtle' > >>> I checked that this is correct: > >>> https://jira.blazegraph.com/browse/BLZG-1689 > >>> but it only returns in OWL format. > >>> > >>> Thanks in advance! > >>> > >>> > >>> With regards, > >>> Jason Koh > >>> cseweb.ucsd.edu/~jbkoh > >> > >> > > > > > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Bigdata-developers mailing list > > Big...@li... > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > |
|
From: Bryan T. <br...@bl...> - 2017-07-01 03:19:17
|
Just looking at the wiki page. Maybe it is the whitespace between the
":" and text/turtle? The examples there do not have that whitespace.
Pretty sure it is not part of the http header convention.
E.g., curl -X POST http://localhost:8080/bigdata/sparql
--data-urlencode 'query=SELECT * { ?s ?p ?o } LIMIT 1' -H
'Accept:application/rdf+xml'
>From the same wiki page.
Bryan
On Fri, Jun 30, 2017 at 5:52 PM, Jason Koh <jb...@en...> wrote:
> I tried application/x-turtle also, which does work.
>
>
> With regards,
> Jason Koh
> cseweb.ucsd.edu/~jbkoh
>
> On Fri, Jun 30, 2017 at 5:26 PM, Jason Koh <jb...@en...> wrote:
>>
>> Btw, Build Version=2.1.4
>>
>>
>> With regards,
>> Jason Koh
>> cseweb.ucsd.edu/~jbkoh
>>
>> On Fri, Jun 30, 2017 at 5:09 PM, Jason Koh <jb...@en...> wrote:
>>>
>>> Hi there,
>>>
>>> Thanks for the great project. I am trying to use this for backend of my
>>> project. Though Blazegraph looks not that active for now, it is the fastest
>>> SPARQL endpoint in my experiences.
>>>
>>> I am trying to parse my SPARQL query result with Turtle, but Blazegraph
>>> does not return Turtle format but OWL/XML format, that my library cannot
>>> parse. I specifically did following command:
>>> curl -X POST http://localhost:9999/blazegraph/sparql --data-urlencode
>>> 'query=<queryStr>' -H 'Accept: text/turtle'
>>> I checked that this is correct:
>>> https://jira.blazegraph.com/browse/BLZG-1689
>>> but it only returns in OWL format.
>>>
>>> Thanks in advance!
>>>
>>>
>>> With regards,
>>> Jason Koh
>>> cseweb.ucsd.edu/~jbkoh
>>
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li...
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>
|
|
From: Jason K. <jb...@en...> - 2017-07-01 00:56:48
|
Btw, Build Version=2.1.4 With regards, Jason Koh cseweb.ucsd.edu/~jbkoh On Fri, Jun 30, 2017 at 5:09 PM, Jason Koh <jb...@en...> wrote: > Hi there, > > Thanks for the great project. I am trying to use this for backend of my > project. Though Blazegraph looks not that active for now, it is the fastest > SPARQL endpoint in my experiences. > > I am trying to parse my SPARQL query result with Turtle, but Blazegraph > does not return Turtle format but OWL/XML format, that my library cannot > parse. I specifically did following command: > curl -X POST http://localhost:9999/blazegraph/sparql --data-urlencode > 'query=<queryStr>' -H 'Accept: text/turtle' > I checked that this is correct: https://jira.blazegraph.com/browse/BLZG- > 1689 > but it only returns in OWL format. > > Thanks in advance! > > > With regards, > Jason Koh > cseweb.ucsd.edu/~jbkoh > |
|
From: Jason K. <jb...@en...> - 2017-07-01 02:52:26
|
Thanks for the suggestion. I tried both with/without a space after the colon, but both don't work. (Space after the colon is a common practice: https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html) With regards, Jason Koh cseweb.ucsd.edu/~jbkoh On Fri, Jun 30, 2017 at 7:48 PM, Bryan Thompson <br...@bl...> wrote: > Just looking at the wiki page. Maybe it is the whitespace between the > ":" and text/turtle? The examples there do not have that whitespace. > Pretty sure it is not part of the http header convention. > > E.g., curl -X POST http://localhost:8080/bigdata/sparql > --data-urlencode 'query=SELECT * { ?s ?p ?o } LIMIT 1' -H > 'Accept:application/rdf+xml' > > From the same wiki page. > > Bryan > > On Fri, Jun 30, 2017 at 5:52 PM, Jason Koh <jb...@en...> wrote: > > I tried application/x-turtle also, which does work. > > > > > > With regards, > > Jason Koh > > cseweb.ucsd.edu/~jbkoh > > > > On Fri, Jun 30, 2017 at 5:26 PM, Jason Koh <jb...@en...> wrote: > >> > >> Btw, Build Version=2.1.4 > >> > >> > >> With regards, > >> Jason Koh > >> cseweb.ucsd.edu/~jbkoh > >> > >> On Fri, Jun 30, 2017 at 5:09 PM, Jason Koh <jb...@en...> wrote: > >>> > >>> Hi there, > >>> > >>> Thanks for the great project. I am trying to use this for backend of my > >>> project. Though Blazegraph looks not that active for now, it is the > fastest > >>> SPARQL endpoint in my experiences. > >>> > >>> I am trying to parse my SPARQL query result with Turtle, but Blazegraph > >>> does not return Turtle format but OWL/XML format, that my library > cannot > >>> parse. I specifically did following command: > >>> curl -X POST http://localhost:9999/blazegraph/sparql --data-urlencode > >>> 'query=<queryStr>' -H 'Accept: text/turtle' > >>> I checked that this is correct: > >>> https://jira.blazegraph.com/browse/BLZG-1689 > >>> but it only returns in OWL format. > >>> > >>> Thanks in advance! > >>> > >>> > >>> With regards, > >>> Jason Koh > >>> cseweb.ucsd.edu/~jbkoh > >> > >> > > > > > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Bigdata-developers mailing list > > Big...@li... > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > |
|
From: Bryan T. <br...@bl...> - 2017-07-01 03:01:36
|
Conneg is handled here: https://github.com/blazegraph/database/blob/64bb8ca92eb063d45d68ec920a34b5321b80e2fe/bigdata-core/bigdata-sails/src/java/com/bigdata/rdf/sail/webapp/BigdataRDFContext.java at around line 2470. Not sure what is going on offhand. Can you set a debugger on this and see what is happening? } else { // Use whatever was specified by the client. final List<String> acceptHeaders = Collections.list(req.getHeaders("Accept")); acceptStr = ConnegUtil.getMimeTypeForQueryParameterQueryRequest( req.getParameter(BigdataRDFServlet.OUTPUT_FORMAT_QUERY_PARAMETER), acceptHeaders.toArray(new String[acceptHeaders.size()])); } // Do conneg. final ConnegUtil util = new ConnegUtil(acceptStr); On Fri, Jun 30, 2017 at 7:52 PM, Jason Koh <jb...@en...> wrote: > Thanks for the suggestion. I tried both with/without a space after the > colon, but both don't work. > (Space after the colon is a common practice: > https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html) > > > With regards, > Jason Koh > cseweb.ucsd.edu/~jbkoh > > On Fri, Jun 30, 2017 at 7:48 PM, Bryan Thompson <br...@bl...> > wrote: >> >> Just looking at the wiki page. Maybe it is the whitespace between the >> ":" and text/turtle? The examples there do not have that whitespace. >> Pretty sure it is not part of the http header convention. >> >> E.g., curl -X POST http://localhost:8080/bigdata/sparql >> --data-urlencode 'query=SELECT * { ?s ?p ?o } LIMIT 1' -H >> 'Accept:application/rdf+xml' >> >> From the same wiki page. >> >> Bryan >> >> On Fri, Jun 30, 2017 at 5:52 PM, Jason Koh <jb...@en...> wrote: >> > I tried application/x-turtle also, which does work. >> > >> > >> > With regards, >> > Jason Koh >> > cseweb.ucsd.edu/~jbkoh >> > >> > On Fri, Jun 30, 2017 at 5:26 PM, Jason Koh <jb...@en...> wrote: >> >> >> >> Btw, Build Version=2.1.4 >> >> >> >> >> >> With regards, >> >> Jason Koh >> >> cseweb.ucsd.edu/~jbkoh >> >> >> >> On Fri, Jun 30, 2017 at 5:09 PM, Jason Koh <jb...@en...> wrote: >> >>> >> >>> Hi there, >> >>> >> >>> Thanks for the great project. I am trying to use this for backend of >> >>> my >> >>> project. Though Blazegraph looks not that active for now, it is the >> >>> fastest >> >>> SPARQL endpoint in my experiences. >> >>> >> >>> I am trying to parse my SPARQL query result with Turtle, but >> >>> Blazegraph >> >>> does not return Turtle format but OWL/XML format, that my library >> >>> cannot >> >>> parse. I specifically did following command: >> >>> curl -X POST http://localhost:9999/blazegraph/sparql --data-urlencode >> >>> 'query=<queryStr>' -H 'Accept: text/turtle' >> >>> I checked that this is correct: >> >>> https://jira.blazegraph.com/browse/BLZG-1689 >> >>> but it only returns in OWL format. >> >>> >> >>> Thanks in advance! >> >>> >> >>> >> >>> With regards, >> >>> Jason Koh >> >>> cseweb.ucsd.edu/~jbkoh >> >> >> >> >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > Check out the vibrant tech community on one of the world's most >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> > _______________________________________________ >> > Bigdata-developers mailing list >> > Big...@li... >> > https://lists.sourceforge.net/lists/listinfo/bigdata-developers >> > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > |
|
From: Jason K. <jb...@en...> - 2017-07-01 03:43:30
|
Building it from the source file is a long shot to me for now, but I will try it later. With regards, Jason Koh cseweb.ucsd.edu/~jbkoh On Fri, Jun 30, 2017 at 8:01 PM, Bryan Thompson <br...@bl...> wrote: > Conneg is handled here: > https://github.com/blazegraph/database/blob/64bb8ca92eb063d45d68ec920a34b5 > 321b80e2fe/bigdata-core/bigdata-sails/src/java/com/ > bigdata/rdf/sail/webapp/BigdataRDFContext.java > at around line 2470. Not sure what is going on offhand. Can you set > a debugger on this and see what is happening? > > } else { > // Use whatever was specified by the client. > final List<String> acceptHeaders = Collections.list(req. > getHeaders("Accept")); > acceptStr = ConnegUtil.getMimeTypeForQueryParameterQueryRequest( > req.getParameter(BigdataRDFServlet.OUTPUT_FORMAT_QUERY_PARAMETER), > acceptHeaders.toArray(new String[acceptHeaders.size()])); > } > > // Do conneg. > final ConnegUtil util = new ConnegUtil(acceptStr); > > > On Fri, Jun 30, 2017 at 7:52 PM, Jason Koh <jb...@en...> wrote: > > Thanks for the suggestion. I tried both with/without a space after the > > colon, but both don't work. > > (Space after the colon is a common practice: > > https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html) > > > > > > With regards, > > Jason Koh > > cseweb.ucsd.edu/~jbkoh > > > > On Fri, Jun 30, 2017 at 7:48 PM, Bryan Thompson <br...@bl...> > > wrote: > >> > >> Just looking at the wiki page. Maybe it is the whitespace between the > >> ":" and text/turtle? The examples there do not have that whitespace. > >> Pretty sure it is not part of the http header convention. > >> > >> E.g., curl -X POST http://localhost:8080/bigdata/sparql > >> --data-urlencode 'query=SELECT * { ?s ?p ?o } LIMIT 1' -H > >> 'Accept:application/rdf+xml' > >> > >> From the same wiki page. > >> > >> Bryan > >> > >> On Fri, Jun 30, 2017 at 5:52 PM, Jason Koh <jb...@en...> wrote: > >> > I tried application/x-turtle also, which does work. > >> > > >> > > >> > With regards, > >> > Jason Koh > >> > cseweb.ucsd.edu/~jbkoh > >> > > >> > On Fri, Jun 30, 2017 at 5:26 PM, Jason Koh <jb...@en...> > wrote: > >> >> > >> >> Btw, Build Version=2.1.4 > >> >> > >> >> > >> >> With regards, > >> >> Jason Koh > >> >> cseweb.ucsd.edu/~jbkoh > >> >> > >> >> On Fri, Jun 30, 2017 at 5:09 PM, Jason Koh <jb...@en...> > wrote: > >> >>> > >> >>> Hi there, > >> >>> > >> >>> Thanks for the great project. I am trying to use this for backend of > >> >>> my > >> >>> project. Though Blazegraph looks not that active for now, it is the > >> >>> fastest > >> >>> SPARQL endpoint in my experiences. > >> >>> > >> >>> I am trying to parse my SPARQL query result with Turtle, but > >> >>> Blazegraph > >> >>> does not return Turtle format but OWL/XML format, that my library > >> >>> cannot > >> >>> parse. I specifically did following command: > >> >>> curl -X POST http://localhost:9999/blazegraph/sparql > --data-urlencode > >> >>> 'query=<queryStr>' -H 'Accept: text/turtle' > >> >>> I checked that this is correct: > >> >>> https://jira.blazegraph.com/browse/BLZG-1689 > >> >>> but it only returns in OWL format. > >> >>> > >> >>> Thanks in advance! > >> >>> > >> >>> > >> >>> With regards, > >> >>> Jason Koh > >> >>> cseweb.ucsd.edu/~jbkoh > >> >> > >> >> > >> > > >> > > >> > > >> > ------------------------------------------------------------ > ------------------ > >> > Check out the vibrant tech community on one of the world's most > >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> > _______________________________________________ > >> > Bigdata-developers mailing list > >> > Big...@li... > >> > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > >> > > > > > > > > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Bigdata-developers mailing list > > Big...@li... > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > |
|
From: Jerven B. <jer...@si...> - 2017-07-02 20:50:10
|
The issue is that it is a SELECT query, which does not have an RDF output, which is why it can't give a turtle output. Only for CONSTRUCT and DESCRIBE queries can one normally get RDF output. Regards, Jerven On Saturday, July 1, 2017 5:01:08 AM CEST Bryan Thompson wrote: > Conneg is handled here: > https://github.com/blazegraph/database/blob/64bb8ca92eb063d45d68ec920a34b532 > 1b80e2fe/bigdata-core/bigdata-sails/src/java/com/bigdata/rdf/sail/webapp/Big > dataRDFContext.java at around line 2470. Not sure what is going on offhand. > Can you set a debugger on this and see what is happening? > > } else { > // Use whatever was specified by the client. > final List<String> acceptHeaders = > Collections.list(req.getHeaders("Accept")); acceptStr = > ConnegUtil.getMimeTypeForQueryParameterQueryRequest( > req.getParameter(BigdataRDFServlet.OUTPUT_FORMAT_QUERY_PARAMETER), > acceptHeaders.toArray(new String[acceptHeaders.size()])); > } > > // Do conneg. > final ConnegUtil util = new ConnegUtil(acceptStr); > > On Fri, Jun 30, 2017 at 7:52 PM, Jason Koh <jb...@en...> wrote: > > Thanks for the suggestion. I tried both with/without a space after the > > colon, but both don't work. > > (Space after the colon is a common practice: > > https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html) > > > > > > With regards, > > Jason Koh > > cseweb.ucsd.edu/~jbkoh > > > > On Fri, Jun 30, 2017 at 7:48 PM, Bryan Thompson <br...@bl...> > > > > wrote: > >> Just looking at the wiki page. Maybe it is the whitespace between the > >> ":" and text/turtle? The examples there do not have that whitespace. > >> Pretty sure it is not part of the http header convention. > >> > >> E.g., curl -X POST http://localhost:8080/bigdata/sparql > >> --data-urlencode 'query=SELECT * { ?s ?p ?o } LIMIT 1' -H > >> 'Accept:application/rdf+xml' > >> > >> From the same wiki page. > >> > >> Bryan > >> > >> On Fri, Jun 30, 2017 at 5:52 PM, Jason Koh <jb...@en...> wrote: > >> > I tried application/x-turtle also, which does work. > >> > > >> > > >> > With regards, > >> > Jason Koh > >> > cseweb.ucsd.edu/~jbkoh > >> > > >> > On Fri, Jun 30, 2017 at 5:26 PM, Jason Koh <jb...@en...> wrote: > >> >> Btw, Build Version=2.1.4 > >> >> > >> >> > >> >> With regards, > >> >> Jason Koh > >> >> cseweb.ucsd.edu/~jbkoh > >> >> > >> >> On Fri, Jun 30, 2017 at 5:09 PM, Jason Koh <jb...@en...> wrote: > >> >>> Hi there, > >> >>> > >> >>> Thanks for the great project. I am trying to use this for backend of > >> >>> my > >> >>> project. Though Blazegraph looks not that active for now, it is the > >> >>> fastest > >> >>> SPARQL endpoint in my experiences. > >> >>> > >> >>> I am trying to parse my SPARQL query result with Turtle, but > >> >>> Blazegraph > >> >>> does not return Turtle format but OWL/XML format, that my library > >> >>> cannot > >> >>> parse. I specifically did following command: > >> >>> curl -X POST http://localhost:9999/blazegraph/sparql --data-urlencode > >> >>> 'query=<queryStr>' -H 'Accept: text/turtle' > >> >>> I checked that this is correct: > >> >>> https://jira.blazegraph.com/browse/BLZG-1689 > >> >>> but it only returns in OWL format. > >> >>> > >> >>> Thanks in advance! > >> >>> > >> >>> > >> >>> With regards, > >> >>> Jason Koh > >> >>> cseweb.ucsd.edu/~jbkoh > >> > > >> > ----------------------------------------------------------------------- > >> > ------- Check out the vibrant tech community on one of the world's most > >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> > _______________________________________________ > >> > Bigdata-developers mailing list > >> > Big...@li... > >> > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > > -------------------------------------------------------------------------- > > ---- Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Bigdata-developers mailing list > > Big...@li... > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > ---------------------------------------------------------------------------- > -- Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers |
|
From: Jason K. <jb...@en...> - 2017-07-02 20:55:09
|
Ah, got it! I must have been out of mind. Thanks for the clarification! With regards, Jason Koh cseweb.ucsd.edu/~jbkoh On Sun, Jul 2, 2017 at 1:36 PM, Jerven Bolleman <jer...@si...> wrote: > The issue is that it is a SELECT query, which does not have an RDF output, > which is why it can't give a turtle output. Only for CONSTRUCT and DESCRIBE > queries can one normally get RDF output. > > Regards, > Jerven > > On Saturday, July 1, 2017 5:01:08 AM CEST Bryan Thompson wrote: > > Conneg is handled here: > > https://github.com/blazegraph/database/blob/ > 64bb8ca92eb063d45d68ec920a34b532 > > 1b80e2fe/bigdata-core/bigdata-sails/src/java/com/bigdata/ > rdf/sail/webapp/Big > > dataRDFContext.java at around line 2470. Not sure what is going on > offhand. > > Can you set a debugger on this and see what is happening? > > > > } else { > > // Use whatever was specified by the client. > > final List<String> acceptHeaders = > > Collections.list(req.getHeaders("Accept")); acceptStr = > > ConnegUtil.getMimeTypeForQueryParameterQueryRequest( > > req.getParameter(BigdataRDFServlet.OUTPUT_FORMAT_QUERY_PARAMETER), > > acceptHeaders.toArray(new String[acceptHeaders.size()])); > > } > > > > // Do conneg. > > final ConnegUtil util = new ConnegUtil(acceptStr); > > > > On Fri, Jun 30, 2017 at 7:52 PM, Jason Koh <jb...@en...> wrote: > > > Thanks for the suggestion. I tried both with/without a space after the > > > colon, but both don't work. > > > (Space after the colon is a common practice: > > > https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html) > > > > > > > > > With regards, > > > Jason Koh > > > cseweb.ucsd.edu/~jbkoh > > > > > > On Fri, Jun 30, 2017 at 7:48 PM, Bryan Thompson <br...@bl...> > > > > > > wrote: > > >> Just looking at the wiki page. Maybe it is the whitespace between the > > >> ":" and text/turtle? The examples there do not have that whitespace. > > >> Pretty sure it is not part of the http header convention. > > >> > > >> E.g., curl -X POST http://localhost:8080/bigdata/sparql > > >> --data-urlencode 'query=SELECT * { ?s ?p ?o } LIMIT 1' -H > > >> 'Accept:application/rdf+xml' > > >> > > >> From the same wiki page. > > >> > > >> Bryan > > >> > > >> On Fri, Jun 30, 2017 at 5:52 PM, Jason Koh <jb...@en...> > wrote: > > >> > I tried application/x-turtle also, which does work. > > >> > > > >> > > > >> > With regards, > > >> > Jason Koh > > >> > cseweb.ucsd.edu/~jbkoh > > >> > > > >> > On Fri, Jun 30, 2017 at 5:26 PM, Jason Koh <jb...@en...> > wrote: > > >> >> Btw, Build Version=2.1.4 > > >> >> > > >> >> > > >> >> With regards, > > >> >> Jason Koh > > >> >> cseweb.ucsd.edu/~jbkoh > > >> >> > > >> >> On Fri, Jun 30, 2017 at 5:09 PM, Jason Koh <jb...@en...> > wrote: > > >> >>> Hi there, > > >> >>> > > >> >>> Thanks for the great project. I am trying to use this for backend > of > > >> >>> my > > >> >>> project. Though Blazegraph looks not that active for now, it is > the > > >> >>> fastest > > >> >>> SPARQL endpoint in my experiences. > > >> >>> > > >> >>> I am trying to parse my SPARQL query result with Turtle, but > > >> >>> Blazegraph > > >> >>> does not return Turtle format but OWL/XML format, that my library > > >> >>> cannot > > >> >>> parse. I specifically did following command: > > >> >>> curl -X POST http://localhost:9999/blazegraph/sparql > --data-urlencode > > >> >>> 'query=<queryStr>' -H 'Accept: text/turtle' > > >> >>> I checked that this is correct: > > >> >>> https://jira.blazegraph.com/browse/BLZG-1689 > > >> >>> but it only returns in OWL format. > > >> >>> > > >> >>> Thanks in advance! > > >> >>> > > >> >>> > > >> >>> With regards, > > >> >>> Jason Koh > > >> >>> cseweb.ucsd.edu/~jbkoh > > >> > > > >> > ------------------------------------------------------------ > ----------- > > >> > ------- Check out the vibrant tech community on one of the world's > most > > >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > >> > _______________________________________________ > > >> > Bigdata-developers mailing list > > >> > Big...@li... > > >> > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > > > > ------------------------------------------------------------ > -------------- > > > ---- Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > > > Bigdata-developers mailing list > > > Big...@li... > > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > > ------------------------------------------------------------ > ---------------- > > -- Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Bigdata-developers mailing list > > Big...@li... > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > |