It also works equally as well with Jena SDB (with a SQL database (e.g. MySQL)
on the back end). We've been using Fuseki with SDB in production for five
years or so.
-Original Message-
From: A. Soroka [mailto:aj...@virginia.edu]
Sent: Saturday, March 4, 2017 9:46 AM
To:
Minor clarification:
Fuseki's default behaviour is the calculate the blank node closure based
on the "subject ( ?p ?o)".
There's a registry DescribeHandlerRegistry and a context key for setting
it (ARQConstants.registryDescribeHandlers).
The registry keeps a list of DescribeHandlerFactory
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
> 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
"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.
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
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
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
> 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
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
> 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
> Titan (Apache license)
has become JanusGraph at the Linux Foundation (Apache 2 license).
Andy
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*
> 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
> 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
Will BNodes in two DatasetGraph's ever collide?
No.
In Jena, the internal blank node identifier is globally unique.
In the parsers, blanks node internal label are based on UUIDs so they
are universally unique to very high probability.
Internally generated blank nodes (createResource()) are
Yes, and I'm increasingly convinced (pretty totally convinced at this point)
that an LDP piece for Fuseki would be a bad idea. I'm not going to pursue it.
---
A. Soroka
The University of Virginia Library
> On Mar 4, 2017, at 8:49 AM, Andy Seaborne wrote:
>
> On 04/03/17
> 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
On 04/03/17 12:45, A. Soroka wrote:
> It is not in any obvious way part of the current remit for the Jena
> project.
Why not?!
Isn't LDP for RDF just another service over the data?
Andy
---
A. Soroka
The University of Virginia Library
On Mar 4, 2017, at 7:40 AM, Laura Morales
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
> 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
Well, GraphQL isn't a query language for graphs :-) You'll notice that
the website does not say "graph". Really, it's a "data access language"
and good at doing that.
You could say the Turtle+variables part of SPARQL is the same theme as
GraphQL. (e.g. no filters). There are languages in the
> The big thing that LDP adds is its container model.
>
>Andy
Yes. This is hugely useful, if it meets your use cases. It allows for a lot of
automatic management for an important class of relationships.
https://www.w3.org/TR/ldp/#ldpc
---
A. Soroka
The University of Virginia Library
> On
On 04/03/17 11:27, Jean-Marc Vanel wrote:
2017-03-04 12:08 GMT+01:00 Laura Morales :
What problem is a "Linked Data Platform" trying to solve that can't
already be accomplished with a RDF server like Fuseki?
Consider this use case:
- manage a team's public FOAF
As a software developer I am frequent asked if I can do something like this.
My answer is usually something like "yes" but with a followup question that
"Should we do this?" Presumably there is some sort of use case for which
extending fuseki to support other query languages might solve.
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?
---
A. Soroka
The University of Virginia Library
> On Mar 4, 2017, at 7:40 AM,
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 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
2017-03-04 12:08 GMT+01:00 Laura Morales :
> What problem is a "Linked Data Platform" trying to solve that can't
> already be accomplished with a RDF server like Fuseki?
Consider this use case:
- manage a team's public FOAF profiles with URL prefix http://xx.com/
- a
What problem is a "Linked Data Platform" trying to solve that can't already be
accomplished with a RDF server like Fuseki? If I'm correct also Fuseki has a
REST front end available.
> Sent: Saturday, March 04, 2017 at 11:48 AM
> From: "Jean-Marc Vanel"
> To: "Jena
Apache Fuseki is a pure SPARQL server, with a native triple database.
Apache Marmotta is a complex beast, primarily an LDP server [1] , but it
mixes a lot of ingredients:
http://marmotta.apache.org/platform/index.html
Its persistence layer is only SQL databases.
It does offer a SPARQL service,
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.
What's the difference between Apache Fuseki and Apache Marmotta?
On 03/03/17 19:57, Dick Murray wrote:
Hi.
Question regarding the design thoughts behind Context and the callbacks.
Also merging BNodes...
I have implemented a Thrift based RPC DatasetGraph consisting of a Client
(implements DatasetGraph) which forwards calls to an IFace (generated from
a
34 matches
Mail list logo