Empty graphs in Fuseki simply don't exist. They no more exist than a
predicate that has not been used. Named graphs only come into existence
when there is at least one triple added to it. If you think about datasets
as collections of quads ( ) then you can see that the dataset
can only locate
Thank you for the quick replies!
Thinking about it, this is totally obvious. It does not matter what the
property is that is followed zero times to end up at the start.
On 26.09.19 10:39, Lorenz Buehmann wrote:
ah and forgot, the formal translation and evaluation is described here:
Hi all,
I am trying to get the Apache Jena UnionModel working for my scenario, but I
keep encountering unexpected behavior. I’ve set up a minimal, free-standing
example on github in this repository (clone the git repo, configure Maven in
your IDE and execute the main() method, I.e. it probably
ah and forgot, the formal translation and evaluation is described here:
https://www.w3.org/TR/sparql11-query/#PropertyPathPatterns
On 26.09.19 10:35, Andy Seaborne wrote:
> And the "+" operation is "one or more" which would require :prop to be
> present.
>
> On 9/26/19 9:32 AM, Lorenz Buehmann
And the "+" operation is "one or more" which would require :prop to be
present.
On 9/26/19 9:32 AM, Lorenz Buehmann wrote:
* means zero or more
if you do zero steps from your start node :foo to reach a node ?x, this
?x is trivially the start node itself
On 26.09.19 10:18, Andreas Textor
* means zero or more
if you do zero steps from your start node :foo to reach a node ?x, this
?x is trivially the start node itself
On 26.09.19 10:18, Andreas Textor wrote:
> Hi all,
>
> I've found a behaviour with a SPARQL path expression that I find
> confusing.
>
> Given a graph that contains
Hi all,
I've found a behaviour with a SPARQL path expression that I find confusing.
Given a graph that contains just the one triple ":foo :prop :bar" (for
any prefix :), I execute the following select query:
select * where { :foo :prop* ?x . }
and get both :foo and :bar as results for ?x,
Elio,
I worked on the Granatum project where I built the query engine. We did
much the same thing that you are trying to do. Our solution was to create
a vocabulary that the application would use and map that vocabulary to the
vocabularies of the SPARQL endpoints we were querying. The solution
still unclear what you're asking for...
what are "mapping rules" in your context?
You should start again by describing your setup and planned task -
ideally from scratch as detailed as possible. And to make sure, Apache
Jena - which this mailing list as about - is not a "mapping tool".
On
hello,
I am trying to federate multiple ontologies by adding mapping rules on each
one of them.
by doing so, I keep them independent but at the same time I can query them
both.
Best regards,
Elio HBEICH
On Wed, Sep 25, 2019 at 5:27 PM Claude Warren wrote:
> I am not certain exactly what you
10 matches
Mail list logo
