Re: Fuseki support other query languages

> > On 04/03/17 13:49, Laura Morales wrote: > > > >> well I don't have a specific use case in mind, > >> I just find SPARQL very counter-intuitive and difficult to reason with > > > > Could you be more specific about these intuitions and difficulties? > > > > Chris > > Forget SPARQL, i mean

Re: Fuseki support other query languages

On Sun, 05 Mar 2017 16:24:03 +0100, Chris Dollin wrote: On 04/03/17 13:49, Laura Morales wrote: well I don't have a specific use case in mind, I just find SPARQL very counter-intuitive and difficult to reason with Could you be more specific about these

Re: Fuseki support other query languages

Using SERVICE to inject pragma into the query is not exact standard ... nor exactly spec-compliant :-) I think that is trying to do something like a traversal of 1 to 4 in depth and get a picture: {0,4} includes the start. Standard SPARQL has arbitrary length traversal and can't limit the

Re: Fuseki support other query languages

> I don't know where in particular you got it https://query.wikidata.org

Re: Fuseki support other query languages

That is in no way a normal SPARQL query. I don't know where in particular you got it, but it is an example of Blazegraph/BigData's "GAS" API. It's not an example of idiomatic SPARQL at all. https://wiki.blazegraph.com/wiki/index.php/RDF_GAS_API That is a specialist extension API for one

Re: Fuseki support other query languages

> Could you be more specific about these intuitions and difficulties? with other query languages such as gremlin you start from a vertex (or set of vertices), and follow links (predicates). This is very intuitive, because it resemble the picture of a graph that I have in mind. For example, I

Re: Fuseki support other query languages

On 04/03/17 13:49, Laura Morales wrote: well I don't have a specific use case in mind, I just find SPARQL very counter-intuitive and difficult to reason with Could you be more specific about these intuitions and difficulties? Chris

Re: Fuseki support other query languages

On Sat, 04 Mar 2017 16:10:56 +0100, Laura Morales wrote: OK if I get this right, TDB is the actual database storing all triples/n-quads, and Fuseki is a layer on top of it whose purpose is to parse SPARQL queries and retrieve triples from TDB. Right? YES, and if

RE: Fuseki support other query languages

@jena.apache.org Subject: Re: Fuseki support other query languages Fuseki is not a database. It is a SPARQL server. Jena TDB is the usual database used with Fuseki. Using Fuseki without Jena is nonsensical. Fuseki is totally based on Jena. https://jena.apache.org/documentation/index.html --- A. Soroka

Re: Fuseki support other query languages

HI All, Here's a little case study in going from a spec to a SPARQL query, and separately to SQL. HTH, -- Adrian Adrian Walker Reengineering LLC San Jose, CA, USA 860 830 2085 www.executable-english.com -SPECIFICATION- I have a graph where resources

Re: Fuseki support other query languages

> My goal is simply to learn more about graph databases, so I want to install > and use one. I've installed Fuseki, but I found SPARQL to be overly complex > compared to other query languages. It's a little like wanting to use RDBMS but finding SQL overly complex. Sure, there is probably some

Re: Fuseki support other query languages

"Fuseki" as in the distribution "apache-jena-fuseki" is the bundling of database (in memory and on disk), query engine and HTTP server as well as text indexing. "Fuseki" as in the Jena module, is the server part. We tend to use the same word in different views - external and internal.

Re: Fuseki support other query languages

On 04/03/17 14:51, Laura Morales wrote: In the RDF space: ... For Property Graphs: Apache TinkerPop (you have to find a persistence layer IIRC), and for analytics, Apache Spark/GraphX, Apache Giraph, and others. Andy what's the difference between these two areas? Does it mean

Re: Fuseki support other query languages

In between TDB and Fuseki is ARQ, which is Jena's SPARQL implementation. https://jena.apache.org/documentation/query/index.html ARQ can be used with a variety of backends, including in-memory systems and on-disk databases like TDB. Fuseki is mostly responsible for HTTP management and handing

Re: Fuseki support other query languages

OK if I get this right, TDB is the actual database storing all triples/n-quads, and Fuseki is a layer on top of it whose purpose is to parse SPARQL queries and retrieve triples from TDB. Right? > Fuseki is not a database. It is a SPARQL server. Jena TDB is the usual > database used with

Re: Fuseki support other query languages

> In the RDF space: > ... > For Property Graphs: > > Apache TinkerPop (you have to find a persistence layer IIRC), and for > analytics, Apache Spark/GraphX, Apache Giraph, and others. > > Andy > what's the difference between these two areas? Does it mean that GraphX/Giraph are only

Re: Fuseki support other query languages

Fuseki is not a database. It is a SPARQL server. Jena TDB is the usual database used with Fuseki. Using Fuseki without Jena is nonsensical. Fuseki is totally based on Jena. https://jena.apache.org/documentation/index.html --- A. Soroka The University of Virginia Library > On Mar 4, 2017, at

Re: Fuseki support other query languages

> RDF4J (formerly known as Sesame, Eclipse license) "RDF4J (formerly known as Sesame) is an open source Java framework for processing RDF data." I'm not looking at a framework, I'm only interested in the database component. Like, say, MySQL, PostgreSQL, etc... That's why I'm interested in

Re: Fuseki support other query languages

> Titan (Apache license) has become JanusGraph at the Linux Foundation (Apache 2 license). Andy

Re: Fuseki support other query languages

On 04/03/17 14:00, Laura Morales wrote: There are plenty of graph databases that provide the other languages you mentioned. Is there some reason why you want to use Jena? Perhaps, as John Fereira asked, you will describe your use case. Because as far as I can tell, Jena/Fuseki is the *only*

Re: Fuseki support other query languages

> There are plenty of graph databases that provide the other languages you > mentioned. Is there some reason why you want to use Jena? Perhaps, as John > Fereira asked, you will describe your use case. Because as far as I can tell, Jena/Fuseki is the *only* free/libre graph database. All other

Re: Fuseki support other query languages

> well I don't have a specific use case in mind, I just find SPARQL very > counter-intuitive and difficult to reason with ... > nope, never before. Now I'm even more confused about the purposes of > Fuseki/Elda/LDP Then you will probably want to settle on a particular use case through which to

Re: Fuseki support other query languages

ry language to Fuseki, or not? >>> >>> >>>> Sent: Saturday, March 04, 2017 at 1:32 PM >>>> From: baran...@gmail.com >>>> To: users@jena.apache.org >>>> Subject: Re: Fuseki support other query languages >>>> >>>

Re: RE: Fuseki support other query languages

> Presumably there is some sort of use case for which extending fuseki to > support other query languages might solve. Perhaps describing that use case > would lead to an answer which describes how using jena or something that uses > jena can solve that use case. well I don't have a specific

Re: Fuseki support other query languages

<laure...@mail.com> wrote: This message is very confusing. I was asking whether it would be possible to add another (more friendly) query language to Fuseki, or not? Sent: Saturday, March 04, 2017 at 1:32 PM From: baran...@gmail.com To: users@jena.apache.org Subject: Re: Fuseki support

Re: Fuseki support other query languages

There are plenty of graph databases that provide the other languages you mentioned. Is there some reason why you want to use Jena? Perhaps, as John Fereira asked, you will describe your use case. --- A. Soroka The University of Virginia Library > On Mar 4, 2017, at 8:44 AM, Laura Morales

Re: Fuseki support other query languages

> Certainly it would be _possible_ to write an extension for Fuseki that would > do such a thing. It is not in any obvious way part of the current remit for > the Jena project. Are you interested in undertaking that work? I would if I knew how to do it, but I wouldn't even know how to approach

Re: Fuseki support other query languages

---Original Message- From: A. Soroka [mailto:aj...@virginia.edu] Sent: Saturday, March 4, 2017 7:45 AM To: users@jena.apache.org Subject: Re: Fuseki support other query languages Certainly it would be _possible_ to write an extension for Fuseki that would do such a thing. It is not in any obvious way

RE: Fuseki support other query languages

@virginia.edu] Sent: Saturday, March 4, 2017 7:45 AM To: users@jena.apache.org Subject: Re: Fuseki support other query languages Certainly it would be _possible_ to write an extension for Fuseki that would do such a thing. It is not in any obvious way part of the current remit for the Jena project

Re: Fuseki support other query languages

@gmail.com >> To: users@jena.apache.org >> Subject: Re: Fuseki support other query languages >> >> >> I think it was a false estimation to allure SQL folks for Semantic Web >> with SPARQL. >> >>> SPARQL is rather cumbersome and counter-intuitive

Re: Fuseki support other query languages

This message is very confusing. I was asking whether it would be possible to add another (more friendly) query language to Fuseki, or not? > Sent: Saturday, March 04, 2017 at 1:32 PM > From: baran...@gmail.com > To: users@jena.apache.org > Subject: Re: Fuseki support other que

Re: Fuseki support other query languages

I think it was a false estimation to allure SQL folks for Semantic Web with SPARQL. SPARQL is rather cumbersome and counter-intuitive to work with... and that was one of the important reasons, why they ignored SPARQL. There are also other reasons. But the most important one is: No

Fuseki support other query languages

SPARQL is rather cumbersome and counter-intuitive to work with... I was wondering whether it would be possible to support in Fuseki some other more friendly query language, such as graphql or gremlin.