Re: Fuseki support text/plain

https://www.w3.org/TR/sparql11-protocol/#query-via-post-direct On 24/04/17 19:25, Laura Morales wrote: What is the reason you would like to send queries with that particular mimetype? Is it a question of configuring an HTTP client in your code? It's not really about the mime type, it's about

Re: Fuseki support text/plain

> What is the reason you would like to send queries with that particular > mimetype? Is it a question of configuring an HTTP client in your code? It's not really about the mime type, it's about sending a plain text request where the whole content is interpreted as the query, without the need of

Re: Fuseki support text/plain

What is the reason you would like to send queries with that particular mimetype? Is it a question of configuring an HTTP client in your code? --- A. Soroka Laura Morales wrote on 4/24/17 2:46 AM: text/plain is not supported by SPARQL Protocol, but you can try application/sparql-query.

Re: How to make complex SPARQL queries reusable?

Another option is to express the query logic in standard rule notation, such as RIF, and translate to sparql. This approach is especially indicated if the sparql queries represent actual business rules. Regards, --Paul > On Apr 24, 2017, at 06:22, Andy Seaborne wrote: > >

Re: Jena native store indexes

"Should have been, could have been". It is how it is, your opinion is just one of many and you will achieve nothing by complaining on this list. Go create a W3C Community Group and initiate some real work to achieve the standardisation that you think is required. On Mon, 24 Apr 2017 at 13.30,

Re: Jena native store indexes

Hello, You seem to fundamentally misunderstand how the standardisation process works. The point is not whether i understand standardisation or not, the point is your argument At the time that SPARQL 1.1 was standardised indexing was not a widely used extension so there was no

Re: How to make complex SPARQL queries reusable?

Simon, 1/ SpinRDF provides ways of defining custom functions and property functions in SPARQL. http://spinrdf.org/ There'll probably be something in the SHACL-sphere (not in the standard, but in the same general area/style/framework) soon. 2/ There are methods in ExprUtils to parse

Re: Jena native store indexes

On 24/04/17 10:57, Rob Vesse wrote: You seem to fundamentally misunderstand how the standardisation process works. The intent of a standard is never to specify every feature that exists or that could exist but rather to specify a set of standard functionality that will be useful to end users

Re: Jena native store indexes

You seem to fundamentally misunderstand how the standardisation process works. The intent of a standard is never to specify every feature that exists or that could exist but rather to specify a set of standard functionality that will be useful to end users while also being amenable to multiple

Re: Fuseki support text/plain

On 24/04/17 09:34, Martynas Jusevičius wrote: text/plain is not supported by SPARQL Protocol, but you can try application/sparql-query. https://www.w3.org/TR/sparql11-protocol/#query-operation On Mon, 24 Apr 2017 at 08.21, Laura Morales wrote: Right now when I send POST

Re: How to make complex SPARQL queries reusable?

You could use federated queries to return the sub query -- this is probably not efficient but might provide a starting point for futher investigation. If you are doing this in code you could use the QueryBuilder ( https://jena.apache.org/documentation/extras/querybuilder/) and pass the sub query

Re: Fuseki support text/plain

text/plain is not supported by SPARQL Protocol, but you can try application/sparql-query. https://www.w3.org/TR/sparql11-protocol/#query-operation On Mon, 24 Apr 2017 at 08.21, Laura Morales wrote: > Right now when I send POST requests to Fuseki, it seems to accept >

How to make complex SPARQL queries reusable?

Hello, I have complex SPARQL queries, which I would like to divide into several parts (like function definitions), in order to reuse these parts among different SPARQL queries and in order to make a single SPARQL query easier to understand. What are my options to achieve this? I had a

Re: How to make complex SPARQL queries reusable?

I don't think that this is possible with the current implementation since a Function is supposed to return a single value and you'd need something that returns a set of values resp. bindings. Have you checked SPARQL SPIN [1]? Maybe this is something you could use. [1] http://spinrdf.org/ >

How to make complex SPARQL queries reusable?

Hello, I have complex SPARQL queries, which I would like to divide into several parts (like function definitions), in order to reuse these parts among different SPARQL queries and in order to make a single SPARQL query easier to understand. What are my options to achieve this? I had a look at