Re: [Bigdata-developers] Problems with RDR

[Max O. <ma...@ni...>]

Wonderful. Got it to work now.

Thanks,
-max

On Thu, Apr 16, 2015 at 12:33 AM Brad Bebee <be...@sy...> wrote:

> Max,
>
> There were two issues, which are below.  Thank you for pointing out the
> Wiki issue.  It's been updated and corrected:
> http://wiki.blazegraph.com/wiki/index.php/Reification_Done_Right#Reification_Done_Right
> .  Let us know how it works for you.
>
> Thanks, --Brad
>
> 1.  The dublin core name space needed to be declared:
>
> @prefix : <http://bigdata.com> .
> @prefix foaf: <http://xmlns.com/foaf/0.1/
>
> >
> @prefix dct:  <http://purl.org/dc/elements/1.1/> .
>
> :bob foaf:name "Bob" .
> <<:bob foaf:age 23>> dct:creator <http://example.com/crawlers#c1> ;
>                      dct:source <http://example.net/homepage-listing.html> .
>
> 2.  The RDR content-type needed to be specified in the CURL request.
>
> curl -D -H 'Content-Type: application/x-turtle-RDR' --upload-file bob.tut
> -X POST '
> http://localhost:9999/bigdata/namespace/test/sparql/test/sparql?context-uri=http://example.org/tbox
> '
>
>
>
> On Wed, Apr 15, 2015 at 10:04 AM, Bryan Thompson <br...@sy...> wrote:
>
>> The RDR specific mime types are also defined here:
>> http://wiki.blazegraph.com/wiki/index.php/Reification_Done_Right#RDF_Data_Interchange
>>
>> Thanks,
>> Bryan
>>
>> ----
>> Bryan Thompson
>> Chief Scientist & Founder
>> SYSTAP, LLC
>> 4501 Tower Road
>> Greensboro, NC 27410
>> br...@sy...
>> http://blazegraph.com
>> http://blog.bigdata.com <http://bigdata.com>
>> http://mapgraph.io
>>
>> Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance
>> graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
>> APIs.  MapGraph™ <http://www.systap.com/mapgraph> is our disruptive new
>> technology to use GPUs to accelerate data-parallel graph analytics.
>>
>> 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 Wed, Apr 15, 2015 at 10:03 AM, Bryan Thompson <br...@sy...>
>> wrote:
>>
>>> Max,
>>>
>>> I've fixed the wiki.
>>>
>>> The problem is the Content-Type header.  I have modified the servlet to
>>> report back the Content-Type header in the error message.
>>>
>>> You are probably specifying Content-Type=application/x-turtle. When I
>>> use this value I get the same error message.
>>>
>>> You need to specify *application/x-turtle-RDR* per
>>> http://wiki.blazegraph.com/wiki/index.php/NanoSparqlServer#MIME_Types
>>>
>>> Thanks,
>>> Bryan
>>> ----
>>> Bryan Thompson
>>> Chief Scientist & Founder
>>> SYSTAP, LLC
>>> 4501 Tower Road
>>> Greensboro, NC 27410
>>> br...@sy...
>>> http://blazegraph.com
>>> http://blog.bigdata.com <http://bigdata.com>
>>> http://mapgraph.io
>>>
>>> Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance
>>> graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
>>> APIs.  MapGraph™ <http://www.systap.com/mapgraph> is our disruptive new
>>> technology to use GPUs to accelerate data-parallel graph analytics.
>>>
>>> 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 Tue, Apr 14, 2015 at 10:00 PM, Max Ott <ma...@ni...> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have trying to get the RDR extension working as this is the feature
>>>> I'm most interested in. So I copied a simple statement from the web site
>>>> into a file called 'bob.tut'
>>>>
>>>> @prefix : <http://bigdata.com> .
>>>> @prefix foaf: <http://xmlns.com/foaf/0.1/> .
>>>>
>>>> :bob foaf:name "Bob" .
>>>> <<:bob foaf:age 23>> dct:creator <http://example.com/crawlers#c1> ;
>>>>                      dct:source <
>>>> http://example.net/homepage-listing.html> .
>>>>
>>>> (BTW, the trailing dot on line 2 and ‘;’ on line 5 is missing in the
>>>> wiki writeup).
>>>>
>>>> I then created a namespace “test” with RDR selected which gave me the
>>>> following service description:
>>>>
>>>> ….
>>>> <endpoint xmlns="http://www.w3.org/ns/sparql-service-description#"
>>>> rdf:resource="http://localhost:9999/bigdata/namespace/test/sparql”/>
>>>> …
>>>>         <feature xmlns="
>>>> http://www.w3.org/ns/sparql-service-description#" rdf:resource="
>>>> http://www.bigdata.com/rdf#/features/KB/Mode/Sids"/>
>>>>         <feature xmlns="
>>>> http://www.w3.org/ns/sparql-service-description#" rdf:resource="
>>>> http://www.bigdata.com/rdf#/features/KB/TruthMaintenance"/>
>>>>
>>>> If I now try to upload ‘bob’, I get the following error:
>>>>
>>>> $ curl -D- -H 'Content-Type: text/turtle' --upload-file bob.tut -X POST
>>>> '
>>>> http://localhost:9999/bigdata/namespace/test/sparql/test/sparql?context-uri=http://example.org/tbox'
>>>>
>>>> HTTP/1.1 100 Continue
>>>>
>>>> HTTP/1.1 500 Server Error
>>>> Content-Type: text/plain
>>>> Transfer-Encoding: chunked
>>>> Server: Jetty(9.2.3.v20140905)
>>>>
>>>> INSERT-WITH-BODY: baseURI=
>>>> http://192.168.59.3:9999/bigdata/namespace/test/sparql, context-uri=[
>>>> http://example.org/tbox]
>>>> java.util.concurrent.ExecutionException:
>>>> org.openrdf.rio.RDFParseException: IRI included an unencoded space: '32'
>>>> [line 5]
>>>> ….
>>>>
>>>> Looks like the RDF parser didn’t get the memo that I’m sending RDR
>>>> data, but I have no idea what I’m doing wrong, nor apparently what I'm
>>>> doing - period :)
>>>>
>>>> Any help would be greatly appreciated.
>>>>
>>>> Cheers,
>>>> -max
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>>>> Develop your own process in accordance with the BPMN 2 standard
>>>> Learn Process modeling best practices with Bonita BPM through live
>>>> exercises
>>>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
>>>> event?utm_
>>>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>>>> _______________________________________________
>>>> Bigdata-developers mailing list
>>>> Big...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>>>
>>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>> Develop your own process in accordance with the BPMN 2 standard
>> Learn Process modeling best practices with Bonita BPM through live
>> exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
>> event?utm_
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>> _______________________________________________
>> Bigdata-developers mailing list
>> Big...@li...
>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>
>>
>
>
> --
> _______________
> Brad Bebee
> Managing Partner
> SYSTAP, LLC
> e:  be...@sy...
> m: 202.642.7961
> f:  571.367.5000
> w:  www.systap.com
>
>
> Blazegraph™ <http://www.blazegraph.com> is our ultra high-performance
> graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
> APIs.  MapGraph™ <http://www.systap.com/mapgraph> is our disruptive new
> technology to use GPUs to accelerate data-parallel graph analytics.
>
> 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, LLC.  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.
>