Menu
▾
▴
Re: [Bigdata-developers] export data using curl by named graph
|
From: Alex M. <ale...@gm...> - 2015-11-09 18:11:22
|
Hi Bryan,
I've tried that and a number of methods. On export though I get data that I
guess is a description for the service.
Can blazegraph create some specific examples to show how to accomplish this
using curl? The task is to load an rdf xml file and then export the same
file using a named graph.
I'm evaluating the system for a large client and have completed this task
for other systems but I'm not clear on how to do this with the given
documentation.
[exec] <rdf:RDF
[exec] xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
[exec]
[exec] <rdf:Description rdf:nodeID="service">
[exec] <rdf:type
rdf:resource="http://www.w3.org/ns/sparql-service-description#Service"/>
[exec] <endpoint
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://52.89.40.122:9999/bigdata/sparql"/>
[exec] <endpoint
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://52.89.40.122:9999/bigdata/LBS/sparql"/>
[exec] <supportedLanguage
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/sparql-service-description#SPARQL10Query"/>
[exec] <supportedLanguage
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/sparql-service-description#SPARQL11Query"/>
[exec] <supportedLanguage
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/sparql-service-description#SPARQL11Update"/>
[exec] <feature
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/sparql-service-description#BasicFederatedQuery"/>
[exec] <feature
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/sparql-service-description#UnionDefaultGraph"/>
[exec] <feature
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.bigdata.com/rdf#/features/KB/Mode/Quads"/>
[exec] <inputFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/RDF_XML"/>
[exec] <inputFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/N-Triples"/>
[exec] <inputFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/Turtle"/>
[exec] <inputFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/N3"/>
[exec] <inputFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.wiwiss.fu-berlin.de/suhl/bizer/TriG/Spec/"/>
[exec] <inputFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://sw.deri.org/2008/07/n-quads/#n-quads"/>
[exec] <inputFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/SPARQL_Results_XML"/>
[exec] <inputFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/SPARQL_Results_JSON"/>
[exec] <inputFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/SPARQL_Results_CSV"/>
[exec] <inputFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/SPARQL_Results_TSV"/>
[exec] <resultFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/RDF_XML"/>
[exec] <resultFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/N-Triples"/>
[exec] <resultFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/Turtle"/>
[exec] <resultFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/N3"/>
[exec] <resultFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.wiwiss.fu-berlin.de/suhl/bizer/TriG/Spec/"/>
[exec] <resultFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/SPARQL_Results_XML"/>
[exec] <resultFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/SPARQL_Results_JSON"/>
[exec] <resultFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/SPARQL_Results_CSV"/>
[exec] <resultFormat
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/formats/SPARQL_Results_TSV"/>
[exec] <entailmentRegime
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:resource="http://www.w3.org/ns/entailment/Simple"/>
[exec] <defaultDataset
xmlns="http://www.w3.org/ns/sparql-service-description#"
rdf:nodeID="defaultDataset"/>
[exec] </rdf:Description>
Regards
Alex
www.tilogeo.com
On Mon, Nov 9, 2015 at 1:46 PM, Bryan Thompson <br...@sy...> wrote:
> Alex,
>
> I believe that you should be using the parameters defined at [1] for
> SPARQL UPDATE. Notably, replace ?c=... with
> using-named-graph-uriSpecify zero or more named graphs for this the
> update request (protocol option with the same semantics as USING NAMED).
>
> This is per the SPARQL UPDATE specification.
>
> Thanks,
> Bryan
>
> [1]
> https://wiki.blazegraph.com/wiki/index.php/REST_API#UPDATE_.28SPARQL_1.1_UPDATE.29
>
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://blazegraph.com
> http://blog.blazegraph.com
>
> Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance
> graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
> APIs. Blazegraph is now available with GPU acceleration using our disruptive
> technology to accelerate data-parallel graph analytics and graph query.
>
> CONFIDENTIALITY NOTICE: This email and its contents and attachments are
> for the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email
> and its contents and attachments.
>
> On Sun, Nov 8, 2015 at 1:49 PM, Alex Muir <ale...@gm...> wrote:
>
>> Hi,
>>
>> Using the REST API how do I export the same data file that I uploaded?
>>
>> I'm unclear with the BLAZEGRAPH REST API on the method to associate a named graph on upload and export that same named graph.
>>
>> With the following
>>
>> curl -X POST -H 'Content-Type:application/xml' --data-binary @data.rdf
>> http://62.59.40.122:9999/bigdata/sparql?c=http://abc.com/id/graph/xyz
>>
>> curl -X POST http://62.59.40.122:9999/bigdata/sparql
>> --data-urlencode 'query=named-graph-uri http://abc.com/id/graph/xyz' -H 'Accept: application/rdf+xml" | gzip > data.rdf.gz
>>
>> I get data exported but not the same large file that I inserted.
>>
>> Regards
>> Alex
>> www.tilogeo.com
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Bigdata-developers mailing list
>> Big...@li...
>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>
>>
>
|
