This list is closed, nobody may subscribe to it.
2010 |
Jan
|
Feb
(19) |
Mar
(8) |
Apr
(25) |
May
(16) |
Jun
(77) |
Jul
(131) |
Aug
(76) |
Sep
(30) |
Oct
(7) |
Nov
(3) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(2) |
Jul
(16) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
(7) |
Dec
(7) |
2012 |
Jan
(10) |
Feb
(1) |
Mar
(8) |
Apr
(6) |
May
(1) |
Jun
(3) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(8) |
Dec
(2) |
2013 |
Jan
(5) |
Feb
(12) |
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(22) |
Aug
(50) |
Sep
(31) |
Oct
(64) |
Nov
(83) |
Dec
(28) |
2014 |
Jan
(31) |
Feb
(18) |
Mar
(27) |
Apr
(39) |
May
(45) |
Jun
(15) |
Jul
(6) |
Aug
(27) |
Sep
(6) |
Oct
(67) |
Nov
(70) |
Dec
(1) |
2015 |
Jan
(3) |
Feb
(18) |
Mar
(22) |
Apr
(121) |
May
(42) |
Jun
(17) |
Jul
(8) |
Aug
(11) |
Sep
(26) |
Oct
(15) |
Nov
(66) |
Dec
(38) |
2016 |
Jan
(14) |
Feb
(59) |
Mar
(28) |
Apr
(44) |
May
(21) |
Jun
(12) |
Jul
(9) |
Aug
(11) |
Sep
(4) |
Oct
(2) |
Nov
(1) |
Dec
|
2017 |
Jan
(20) |
Feb
(7) |
Mar
(4) |
Apr
(18) |
May
(7) |
Jun
(3) |
Jul
(13) |
Aug
(2) |
Sep
(4) |
Oct
(9) |
Nov
(2) |
Dec
(5) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Daniel H. <da...@de...> - 2017-07-29 17:46:37
|
Hi, In the Blazegraph web page (https://www.blazegraph.com/product/) I used to see a comparison between the open source version (GPLv2) and the version extended for using the GPU. Currently, I see only the opensource version. The second column of the table is filled with Xs and has no product label. Why? Cheers, Daniel |
From: Daniel H. <da...@de...> - 2017-07-29 17:46:36
|
Hi, In the Blazegraph web page (https://www.blazegraph.com/product/) I used to see a comparison between the open source version (GPLv2) and the version extended for using the GPU. Currently, I see only the opensource version. The second column of the table is filled with Xs and has no product label. Why? Cheers, Daniel |
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 <jerven.bolleman@sib.swiss> 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 > |
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-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: 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: 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: 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 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: 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: 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 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: 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: Steve B. <ste...@va...> - 2017-06-29 19:24:47
|
Followup: I performed this query: PREFIX wdt: <http://www.wikidata.org/prop/direct/> SELECT DISTINCT ?country WHERE { ?country wdt:P1448 "中华人民共和国"@zh-hans. } on the Wikidata Blazegraph endpoint using this URI: https://query.wikidata.org/sparql?query=PREFIX%20wdt%3A%20%3Chttp%3A%2F%2Fwww.wikidata.org%2Fprop%2Fdirect%2F%3E%0ASELECT%20DISTINCT%20%3Fcountry%20WHERE%20%7B%0A%20%20%20%20%3Fcountry%20wdt%3AP1448%20%22%E4%B8%AD%E5%8D%8E%E4%BA%BA%E6%B0%91%E5%85%B1%E5%92%8C%E5%9B%BD%22%40zh-hans.%0A%7D and I got a result. So I guess my problem is not a Blazegraph one, per se. Steve On 6/29/17 12:33 PM, Steve Baskauf wrote: > We have set up a Blazegraph instance at https://sparql.vanderbilt.edu > and have loaded it with data. Those data include multilingual > translations of a controlled vocabulary. The problem I'm having > occurs when I send via HTTP to the endpoint a query that contains URL > encoded literals that represent non-ASCII UTF-8 characters from other > languages. Here is a query that contains a literal with the character > "ú" (URL encoded as %C3%BA): > > SELECT DISTINCT ?term where { > ?term <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> > <http://rs.tdwg.org/cv/status/>. > ?term <http://www.w3.org/2004/02/skos/core#hiddenLabel> 'Común'. > } > > If I paste the query into the Blazegraph SPARQL endpoint GUI box at > https://sparql.vanderbilt.edu, I get a single result: the URI > <http://rs.tdwg.org/cv/status/extant> as I should. However, if I URL > encode the query and sent it to the same Blazegraph endpoint via HTTP > GET as: > > https://sparql.vanderbilt.edu/sparql?query=SELECT%20DISTINCT%20%3Fterm%20where%20%7B%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23isDefinedBy%3E%20%3Chttp%3A%2F%2Frs.tdwg.org%2Fcv%2Fstatus%2F%3E.%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2004%2F02%2Fskos%2Fcore%23hiddenLabel%3E%20%27Com%C3%BAn%27.%0A%7D > > > there are no results. I'm confident that the URL encoding is correct > because if the same query is sent via HTTP GET to our old > Callimachus-based endpoint, it returns the correct URI: > > http://rdf.library.vanderbilt.edu/sparql?query=SELECT%20DISTINCT%20%3Fterm%20where%20%7B%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23isDefinedBy%3E%20%3Chttp%3A%2F%2Frs.tdwg.org%2Fcv%2Fstatus%2F%3E.%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2004%2F02%2Fskos%2Fcore%23hiddenLabel%3E%20%27Com%C3%BAn%27.%0A%7D > > > The problem appears to be with the endpoint's handling of the encoded > literal characters. If I change the literal to one that does not > contain non-ASCII characters, such as "common" (a hidden label synonym > of "Común"), so that the query is: > > SELECT DISTINCT ?term where { > ?term <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> > <http://rs.tdwg.org/cv/status/>. > ?term <http://www.w3.org/2004/02/skos/core#hiddenLabel> 'common'. > } > > the URL encoded HTTP GET: > > https://sparql.vanderbilt.edu/sparql?query=SELECT%20DISTINCT%20%3Fterm%20where%20%7B%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23isDefinedBy%3E%20%3Chttp%3A%2F%2Frs.tdwg.org%2Fcv%2Fstatus%2F%3E.%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2004%2F02%2Fskos%2Fcore%23hiddenLabel%3E%20%27common%27.%0A%7D > > > produces the correct result. > > I am at a loss as to where to go with this as far as trouble-shooting > is concerned. It's possible that there is some incorrect server > configuration setting that I don't know about. I suppose it's also > possible that it's a bug. This is a rather serious problem for us > because we have significant multilingual data in the triplestore and > users need to be able to search against it. > > Steve Baskauf > -- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences postal mail address: PMB 351634 Nashville, TN 37235-1634, U.S.A. delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235 office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 322-4942 If you fax, please phone or email so that I will know to look for it. http://bioimages.vanderbilt.edu http://vanderbilt.edu/trees |
From: Steve B. <ste...@va...> - 2017-06-29 17:34:23
|
We have set up a Blazegraph instance at https://sparql.vanderbilt.edu and have loaded it with data. Those data include multilingual translations of a controlled vocabulary. The problem I'm having occurs when I send via HTTP to the endpoint a query that contains URL encoded literals that represent non-ASCII UTF-8 characters from other languages. Here is a query that contains a literal with the character "ú" (URL encoded as %C3%BA): SELECT DISTINCT ?term where { ?term <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <http://rs.tdwg.org/cv/status/>. ?term <http://www.w3.org/2004/02/skos/core#hiddenLabel> 'Común'. } If I paste the query into the Blazegraph SPARQL endpoint GUI box at https://sparql.vanderbilt.edu, I get a single result: the URI <http://rs.tdwg.org/cv/status/extant> as I should. However, if I URL encode the query and sent it to the same Blazegraph endpoint via HTTP GET as: https://sparql.vanderbilt.edu/sparql?query=SELECT%20DISTINCT%20%3Fterm%20where%20%7B%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23isDefinedBy%3E%20%3Chttp%3A%2F%2Frs.tdwg.org%2Fcv%2Fstatus%2F%3E.%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2004%2F02%2Fskos%2Fcore%23hiddenLabel%3E%20%27Com%C3%BAn%27.%0A%7D there are no results. I'm confident that the URL encoding is correct because if the same query is sent via HTTP GET to our old Callimachus-based endpoint, it returns the correct URI: http://rdf.library.vanderbilt.edu/sparql?query=SELECT%20DISTINCT%20%3Fterm%20where%20%7B%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23isDefinedBy%3E%20%3Chttp%3A%2F%2Frs.tdwg.org%2Fcv%2Fstatus%2F%3E.%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2004%2F02%2Fskos%2Fcore%23hiddenLabel%3E%20%27Com%C3%BAn%27.%0A%7D The problem appears to be with the endpoint's handling of the encoded literal characters. If I change the literal to one that does not contain non-ASCII characters, such as "common" (a hidden label synonym of "Común"), so that the query is: SELECT DISTINCT ?term where { ?term <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <http://rs.tdwg.org/cv/status/>. ?term <http://www.w3.org/2004/02/skos/core#hiddenLabel> 'common'. } the URL encoded HTTP GET: https://sparql.vanderbilt.edu/sparql?query=SELECT%20DISTINCT%20%3Fterm%20where%20%7B%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23isDefinedBy%3E%20%3Chttp%3A%2F%2Frs.tdwg.org%2Fcv%2Fstatus%2F%3E.%0A%3Fterm%20%3Chttp%3A%2F%2Fwww.w3.org%2F2004%2F02%2Fskos%2Fcore%23hiddenLabel%3E%20%27common%27.%0A%7D produces the correct result. I am at a loss as to where to go with this as far as trouble-shooting is concerned. It's possible that there is some incorrect server configuration setting that I don't know about. I suppose it's also possible that it's a bug. This is a rather serious problem for us because we have significant multilingual data in the triplestore and users need to be able to search against it. Steve Baskauf -- Steven J. Baskauf, Ph.D., Senior Lecturer Vanderbilt University Dept. of Biological Sciences postal mail address: PMB 351634 Nashville, TN 37235-1634, U.S.A. delivery address: 2125 Stevenson Center 1161 21st Ave., S. Nashville, TN 37235 office: 2128 Stevenson Center phone: (615) 343-4582, fax: (615) 322-4942 If you fax, please phone or email so that I will know to look for it. http://bioimages.vanderbilt.edu http://vanderbilt.edu/trees |
From: Stas M. <sma...@wi...> - 2017-06-15 22:35:35
|
Hi! Blazegraph implements virtual graphs via special syntax: https://wiki.blazegraph.com/wiki/index.php/VirtualGraphs Also, it is possible to set default graphs for queries via default-graph-uri and named graphs via named-graph-uri. However, these match "FROM" and "FROM NAMED" - are there parameters that match "FROM VIRTUAL GRAPH" and "FROM NAMED VIRTUAL GRAPH"? Using virtual graphs could be really helpful if one needs to use aliasing for graphs, however if it's not supported for REST API it may be less useful. Thanks, -- Stas Malyshev sma...@wi... |
From: Brad B. <be...@sy...> - 2017-05-17 00:09:43
|
Mariano, Thank you. I'll send you a note off-list and we can setup a time to discuss the options. Thanks, --Brad On Tue, May 16, 2017 at 8:27 AM, Mariano Rodriguez muro <mr...@us...> wrote: > Hi guys, > > I think the layout confused me a bit. A lot of things changed in the > website, I cannot find information regarding the cluster mode > in Blazegraph, nor the GPU versions, in the "products" page, there is only > the single-server and embedded versions listed. Also, in licenses, there > used to be the option to buy commercial licenses directly. Now there is > only a pointer to the GPL license. > > Has the business model of Blazegraph change? what is the current > situation? could you point me to the right information to read about > commercial licenses? > > > Mariano Rodriguez Muro > Research Staff, IBM Research > IBM T.J. Watson research center > Yorktown heights, NY. USA > +1-914-945-2607 <(914)%20945-2607> > mr...@us... > > > > ----- Original message ----- > From: Brad Bebee <be...@sy...> > To: Mariano Rodriguez muro <mr...@us...> > Cc: bigdata-developers <big...@li...> > Subject: Re: [Bigdata-developers] Website down? > Date: Mon, May 15, 2017 5:49 PM > > Mariano, > > Just checked and it seems to be functioning normally. Let us know if > you're still seeing issues. > > Thanks, --Brad > > On Mon, May 15, 2017 at 2:34 PM, Mariano Rodriguez muro < > mr...@us...> wrote: > > Hi, is the blazegraph website having technical difficulties? It is not > rendering properly in chrome or safari. I see some error message about CSS. > It is making it hard to read information about licenses, features etc. > > Mariano Rodriguez Muro > Research Staff, IBM Research > IBM T.J. Watson research center > Yorktown heights, NY. USA > +1-914-945-2607 <(914)%20945-2607> > mr...@us... > > > ------------------------------------------------------------ > ------------------ > 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 > > > > > -- > _______________ > Brad Bebee > CEO, Managing Partner > SYSTAP, LLC > e: be...@sy... > m: 202.642.7961 <(202)%20642-7961> > f: 571.367.5000 <(571)%20367-5000> > > CONFIDENTIALITY NOTICE: This email and its contents and attachments are > for the sole use of the intended recipient(s) and are confidential or > proprietary to SYSTAP, LLC. Any unauthorized review, use, disclosure, > dissemination or copying of this email or its contents or attachments is > prohibited. If you have received this communication in error, please notify > the sender by reply email and permanently delete all copies of the email > and its contents and attachments. > > > > > ------------------------------------------------------------ > ------------------ > 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 > > -- _______________ Brad Bebee CEO, Managing Partner SYSTAP, LLC e: be...@sy... m: 202.642.7961 f: 571.367.5000 CONFIDENTIALITY NOTICE: This email and its contents and attachments are for the sole use of the intended recipient(s) and are confidential or proprietary to SYSTAP, LLC. Any unauthorized review, use, disclosure, dissemination or copying of this email or its contents or attachments is prohibited. If you have received this communication in error, please notify the sender by reply email and permanently delete all copies of the email and its contents and attachments. |
From: Mariano R. m. <mr...@us...> - 2017-05-16 15:27:19
|
<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt" ><div dir="ltr" >Hi guys, </div> <div dir="ltr" > </div> <div dir="ltr" >I think the layout confused me a bit. A lot of things changed in the website, I cannot find information regarding the cluster mode in Blazegraph, nor the GPU versions, in the "products" page, there is only the single-server and embedded versions listed. Also, in licenses, there used to be the option to buy commercial licenses directly. Now there is only a pointer to the GPL license. </div> <div dir="ltr" > </div> <div dir="ltr" >Has the business model of Blazegraph change? what is the current situation? could you point me to the right information to read about commercial licenses?</div> <div dir="ltr" > </div> <div dir="ltr" > </div> <div dir="ltr" >Mariano Rodriguez Muro<br>Research Staff, IBM Research<br>IBM T.J. Watson research center<br>Yorktown heights, NY. USA<br>+1-914-945-2607<br>mr...@us...</div> <div dir="ltr" > </div> <div dir="ltr" > </div> <blockquote data-history-content-modified="1" dir="ltr" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" >----- Original message -----<br>From: Brad Bebee <be...@sy...><br>To: Mariano Rodriguez muro <mr...@us...><br>Cc: bigdata-developers <big...@li...><br>Subject: Re: [Bigdata-developers] Website down?<br>Date: Mon, May 15, 2017 5:49 PM<br> <div dir="ltr" >Mariano, <div> </div> <div>Just checked and it seems to be functioning normally. Let us know if you're still seeing issues.</div> <div> </div> <div>Thanks, --Brad</div></div> <div> <div>On Mon, May 15, 2017 at 2:34 PM, Mariano Rodriguez muro <span dir="ltr" ><<a href="mailto:mr...@us..." target="_blank" >mr...@us...</a>></span> wrote: <blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" ><div dir="ltr" style="font-family:Arial,Helvetica,sans-serif;font-size:10.5pt" ><div dir="ltr" >Hi, is the blazegraph website having technical difficulties? It is not rendering properly in chrome or safari. I see some error message about CSS. It is making it hard to read information about licenses, features etc.</div> <div dir="ltr" ><span><font color="#888888" > </font></span></div> <div dir="ltr" ><span><font color="#888888" >Mariano Rodriguez Muro<br>Research Staff, IBM Research<br>IBM T.J. Watson research center<br>Yorktown heights, NY. USA<br><a href="tel:(914)%20945-2607" target="_blank" value="+19149452607" >+1-914-945-2607</a><br><a href="mailto:mr...@us..." target="_blank" >mr...@us...</a></font></span></div></div><br><br>------------------------------<wbr>------------------------------<wbr>------------------<br>Check out the vibrant tech community on one of the world's most<br>engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot" target="_blank" >http://sdm.link/slashdot</a><br>______________________________<wbr>_________________<br>Bigdata-developers mailing list<br><a href="mailto:Big...@li..." target="_blank" >Bigdata-developers@lists.<wbr>sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/bigdata-developers" rel="noreferrer" target="_blank" >https://lists.sourceforge.net/<wbr>lists/listinfo/bigdata-<wbr>developers</a><br> </blockquote></div> <div> </div>-- <div data-smartmail="gmail_signature" ><div dir="ltr" ><div><div dir="ltr" ><div dir="ltr" ><div dir="ltr" ><div dir="ltr" ><div dir="ltr" ><div dir="ltr" ><div dir="ltr" ><div dir="ltr" ><div><div dir="ltr" ><div><div>_______________<br>Brad Bebee</div> <div>CEO, Managing Partner</div> <div><span style="font-size:12.8px" >SYSTAP, LLC</span></div> <div><span style="font-size:12.8px" >e: <a href="mailto:be...@sy..." target="_blank" >be...@sy...</a></span></div>m: 202.642.7961</div> <div>f: 571.367.5000</div> <div> </div></div> <div dir="ltr" ><div><span style="font-size:9pt;font-family:Helvetica" >CONFIDENTIALITY NOTICE: </span><span style="font-family:Helvetica;font-size:12px" >This email and its contents and attachments are for the sole use of the intended recipient(s) and are confidential or proprietary to SYSTAP, LLC. Any unauthorized review, use, disclosure, dissemination or copying of this email or its contents or attachments is prohibited. If you have received this communication in error, please notify the sender by reply email and permanently delete all copies of the email and its contents and attachments.</span></div></div></div> <div><div><img src="https://mail.google.com/mail/u/0/images/cleardot.gif" ></div></div></div></div></div></div></div></div></div></div></div></div></div></div></blockquote> <div dir="ltr" > </div></div><BR> |
From: Edgar Rodriguez-D. <ed...@sy...> - 2017-05-15 21:49:16
|
Hi Mariano, It looks like the site is up to me. You can check with http://www.downforeveryoneorjustme.com/blazegraph.com - it may be a DNS issue on your side, not sure. Cheers, - Edgar > On May 15, 2017, at 2:34 PM, Mariano Rodriguez muro <mr...@us...> wrote: > > Hi, is the blazegraph website having technical difficulties? It is not rendering properly in chrome or safari. I see some error message about CSS. It is making it hard to read information about licenses, features etc. > > Mariano Rodriguez Muro > Research Staff, IBM Research > IBM T.J. Watson research center > Yorktown heights, NY. USA > +1-914-945-2607 > mr...@us... > > ------------------------------------------------------------------------------ > 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: Brad B. <be...@sy...> - 2017-05-15 21:49:14
|
Mariano, Just checked and it seems to be functioning normally. Let us know if you're still seeing issues. Thanks, --Brad On Mon, May 15, 2017 at 2:34 PM, Mariano Rodriguez muro <mr...@us...> wrote: > Hi, is the blazegraph website having technical difficulties? It is not > rendering properly in chrome or safari. I see some error message about CSS. > It is making it hard to read information about licenses, features etc. > > Mariano Rodriguez Muro > Research Staff, IBM Research > IBM T.J. Watson research center > Yorktown heights, NY. USA > +1-914-945-2607 <(914)%20945-2607> > mr...@us... > > > ------------------------------------------------------------ > ------------------ > 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 > > -- _______________ Brad Bebee CEO, Managing Partner SYSTAP, LLC e: be...@sy... m: 202.642.7961 f: 571.367.5000 CONFIDENTIALITY NOTICE: This email and its contents and attachments are for the sole use of the intended recipient(s) and are confidential or proprietary to SYSTAP, LLC. Any unauthorized review, use, disclosure, dissemination or copying of this email or its contents or attachments is prohibited. If you have received this communication in error, please notify the sender by reply email and permanently delete all copies of the email and its contents and attachments. |
From: Mariano R. m. <mr...@us...> - 2017-05-15 21:43:28
|
<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt" ><div dir="ltr" >Hi, is the blazegraph website having technical difficulties? It is not rendering properly in chrome or safari. I see some error message about CSS. It is making it hard to read information about licenses, features etc.</div> <div dir="ltr" > </div> <div dir="ltr" >Mariano Rodriguez Muro<br>Research Staff, IBM Research<br>IBM T.J. Watson research center<br>Yorktown heights, NY. USA<br>+1-914-945-2607<br>mr...@us...</div></div><BR> |
From: Bryan T. <br...@bl...> - 2017-05-10 14:38:09
|
Depending on your use case, there are a few ways that this can be approached. If your entailments are computable solely against the set of statements being inserted, then an external reasoner can be used on the payload. If your entailments can be computed separately for each named graph, but you need to compute against both the named graph and the payload, then some people have used a workflow solution. This approach has been described a few times on the list and Igor (Cc) can elaborate. Basically, you have one Journal per named graph. Some system delivers the delta to that Journal. The journal operates in the truth maintenance mode for that named graph. The total delta (changes in ground statements plus change in entailed statements) is then replicated to another journal (or a family of replicas) which operate in quads mode. This approach also means that you can scale the inference workload independently of the query workload. Thanks, Bryan On Wed, May 10, 2017 at 6:59 AM, Mikel Egaña Aranguren < mik...@gm...> wrote: > Hi; > > The system we are building uses named graphs for provenance, and some of > the resources on those named graphs are related by owl:sameAs, so we would > like to also use inference when querying for resources that are related > with owl:sameAs. > > However, when creating a namespace, it is not possible to have both quads > and inference. Is there any workaround for this? > > Thanks > > Regards > > -- > Mikel Egaña Aranguren, Ph.D. > > https://mikel-egana-aranguren.github.io > > > > ------------------------------------------------------------ > ------------------ > 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: Mikel E. A. <mik...@gm...> - 2017-05-10 13:59:22
|
Hi; The system we are building uses named graphs for provenance, and some of the resources on those named graphs are related by owl:sameAs, so we would like to also use inference when querying for resources that are related with owl:sameAs. However, when creating a namespace, it is not possible to have both quads and inference. Is there any workaround for this? Thanks Regards -- Mikel Egaña Aranguren, Ph.D. https://mikel-egana-aranguren.github.io |
From: Mikel E. A. <mik...@gm...> - 2017-04-24 08:11:54
|
Ok, thanks. We have configured the whole endpoint as read-only 2017-04-22 3:43 GMT+02:00 Brad Bebee <be...@sy...>: > I would estimate about four weeks or so for the 2.1.5 release. We recently > had a jetty security update ticket, which we will likely roll into the > release. > > On Apr 21, 2017 3:08 AM, "Mikel Egaña Aranguren" < > mik...@gm...> wrote: > >> Thanks, I think we will go for the proxy solution explained bellow. >> >> Is there any estimated date for the 2.1.5 release? >> >> Regards >> >> 2017-04-20 15:10 GMT+02:00 Bryan Thompson <br...@bl...>: >> >>> There is no simple single switch. You can either make the entire >>> endpoint read-only (edit web.xml) or you can control the forward of the >>> request to require authentication for POST w/o query=. >>> >>> Thanks, >>> Bryan >>> >>> On Thu, Apr 20, 2017 at 5:52 AM, Mikel Egaña Aranguren < >>> mik...@gm...> wrote: >>> >>>> hi: >>>> >>>> is there an easy way to configure blazegraph so that INSERT and DELETE >>>> queries cannot be executed from an "outside" connection? we are deploying >>>> Blazegraph as a war in an internal Tomcat server >>>> >>>> thanks >>>> >>>> regards >>>> >>>> -- >>>> Mikel Egaña Aranguren, Ph.D. >>>> >>>> https://mikel-egana-aranguren.github.io >>>> >>>> >>>> >>>> ------------------------------------------------------------ >>>> ------------------ >>>> 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 >>>> >>>> >>> >> >> >> -- >> Mikel Egaña Aranguren, Ph.D. >> >> https://mikel-egana-aranguren.github.io >> >> >> >> ------------------------------------------------------------ >> ------------------ >> 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 >> >> -- Mikel Egaña Aranguren, Ph.D. https://mikel-egana-aranguren.github.io |
From: Brad B. <be...@sy...> - 2017-04-22 02:15:42
|
I would estimate about four weeks or so for the 2.1.5 release. We recently had a jetty security update ticket, which we will likely roll into the release. On Apr 21, 2017 3:08 AM, "Mikel Egaña Aranguren" < mik...@gm...> wrote: > Thanks, I think we will go for the proxy solution explained bellow. > > Is there any estimated date for the 2.1.5 release? > > Regards > > 2017-04-20 15:10 GMT+02:00 Bryan Thompson <br...@bl...>: > >> There is no simple single switch. You can either make the entire >> endpoint read-only (edit web.xml) or you can control the forward of the >> request to require authentication for POST w/o query=. >> >> Thanks, >> Bryan >> >> On Thu, Apr 20, 2017 at 5:52 AM, Mikel Egaña Aranguren < >> mik...@gm...> wrote: >> >>> hi: >>> >>> is there an easy way to configure blazegraph so that INSERT and DELETE >>> queries cannot be executed from an "outside" connection? we are deploying >>> Blazegraph as a war in an internal Tomcat server >>> >>> thanks >>> >>> regards >>> >>> -- >>> Mikel Egaña Aranguren, Ph.D. >>> >>> https://mikel-egana-aranguren.github.io >>> >>> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> 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 >>> >>> >> > > > -- > Mikel Egaña Aranguren, Ph.D. > > https://mikel-egana-aranguren.github.io > > > > ------------------------------------------------------------ > ------------------ > 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 > > |