Re: linked data and URLs

good morning, if you are willing to admit to an anti-pattern, this is one: it conflates location with identity. that is cheap, convenient and easy, but, as your question illustrates, it leads to externalisations which misrepresent the actual model. > On 2018-05-22, at 13:00, Claude Warren wro

Re: linked data and URLs

True, my use case is development. It is easier if links that are results of SPARQL point back to the development system. On May 22, 2018 9:55 AM, "Martynas Jusevičius" wrote: Why generate URIs at all in the beginning, can't you use blank nodes? Rewriting URIs is generally a bad idea in a Link

Re: Update Query Parsing error

On 22/05/18 18:24, Bart van Leeuwen wrote: Yes, simply imported through POM The suggested modification doesn't have any effect. Initialization can be tracked with DEBUG_INIT: public static void main(String[] args) throws Exception { JenaSystem.DEBUG_INIT = true; JenaSystem

Re: Nodes without dereferenceable URIs

Don't use blank nodes. You will regret it in the long run. On Tue, May 22, 2018 at 4:43 PM, Laura Morales wrote: > How can I deal with a RDF graph where I don't have dereferenceable URIs, > but still need the URIs to link with other graphs? For example if I have a > personal graph of documents t

Re: Update Query Parsing error

Yes, simply imported through POM The suggested modification doesn't have any effect. Met Vriendelijke Groet / With Kind Regards Bart van Leeuwen twitter: @semanticfire tel. +31(0)6-53182997 Netage B.V. http://netage.nl Esdoornstraat 3 3461ER Linschoten The Netherlands From: Andy Seaborne

Re: Update Query Parsing error

Is this untouched Jena jars downloaded from maven central? Try putting this in: public static void main(String[] args) throws Exception { ***   JenaSystem.init();*     ... Andy On 22/05/18 16:27, Bart van Leeuwen wrote: Sample Code: # package com.e

Re: Update Query Parsing error

Sample Code: # package com.example.netage; import com.complexible.stardog.api.Connection; import com.complexible.stardog.api.ConnectionConfiguration; import com.complexible.stardog.jena.SDJenaFactory; import org.apache.jena.update.UpdateExecutionFactory; import org.ap

Re: Update Query Parsing error

Would be interested to learn form the Jena folks if they can explain this, then I'll happily open a ticket Met Vriendelijke Groet / With Kind Regards Bart van Leeuwen twitter: @semanticfire tel. +31(0)6-53182997 Netage B.V. http://netage.nl Esdoornstraat 3 3461ER Linschoten The Netherlands

Re: Update Query Parsing error

Bart - it does not like an issue with the update but somehow system initialization has not happened. Was there a log message as well? How are you running the update? What's the application code look like?     Andy On 22/05/18 14:24, Bart van Leeuwen wrote: Hi, On Jena 3.7.0 The following

Re: Update Query Parsing error

I think you should open a JIRA ticket. On Tue, May 22, 2018 at 4:53 PM, Bart van Leeuwen < bart_van_leeu...@netage.nl> wrote: > Hi, > > Although you are correct this should be ?g in both cases, it does not fix > the issue. > > Met Vriendelijke Groet / With Kind Regards > Bart van Leeuwen > > > tw

Re: Update Query Parsing error

Hi, Although you are correct this should be ?g in both cases, it does not fix the issue. Met Vriendelijke Groet / With Kind Regards Bart van Leeuwen twitter: @semanticfire tel. +31(0)6-53182997 Netage B.V. http://netage.nl Esdoornstraat 3 3461ER Linschoten The Netherlands From: Paul Herm

Nodes without dereferenceable URIs

How can I deal with a RDF graph where I don't have dereferenceable URIs, but still need the URIs to link with other graphs? For example if I have a personal graph of documents that I only need to use for myself, what URIs should I use? Blank nodes? _:document1 _:document2 _:document3 or do I m

Re: linked data and URLs

I am thinking that perhaps the easiest solution will be to create a Node rewriter and filter all the Fuseki results through it to rewrite the nodes. I will also have to rewrite all the queries going in but it might be doable. On Tue, May 22, 2018 at 3:15 PM, Claude Warren wrote: > Can not use

Re: linked data and URLs

Can not use blank nodes at the start as they cause significant problems later when trying to do deletes and such via update protocols in Fuseki. Small models are built locally and sent as update requests to the Fuseki server so methods that require access to do renames will not be efficient as the

Re: linked data and URLs

Why generate URIs at all in the beginning, can't you use blank nodes? Rewriting URIs is generally a bad idea in a Linked Data setting. Make one datasource canonical and let the other one deal with that. Or maybe you can configure your proxy in a way that hides the port number and you don't need th

Re: linked data and URLs

On my system, I structure the system as APIs that return linked data and HTML/JavaScript that rewrites the URLs. No question - it's work anyway you do it. On Tue, May 22, 2018, 7:00 AM Claude Warren wrote: > I have what I think may be a common problem and am looking for suggested > patterns an

Re: Update Query Parsing error

Bart, Graph ?x <-> graph ?g ? Paul On 22 May 2018 at 15:24:33, Bart van Leeuwen (bart_van_leeu...@netage.nl) wrote: Hi, On Jena 3.7.0 The following the query ( which is accepted by Stardog on the console ) DELETE { Graph ?g { ?resultset

Update Query Parsing error

Hi, On Jena 3.7.0 The following the query ( which is accepted by Stardog on the console ) DELETE { Graph ?g { ?resultset < http://vocab.resc.info/insight#organization> < http://data.resc.info/data/stations/BrandweerAmsterdamAmstelland>}} WHERE { Graph ?x { ?resultset a

linked data and URLs

I have what I think may be a common problem and am looking for suggested patterns and anti-patterns for a solution. For the sake of this example let's assume that the system described creates FOAF records. == PROBLEM Backend: The backend system generates FOAF records but does not have any info