Re: [Bigdata-developers] json and ask: trac 704

[Peter A. <ans...@gm...>]

I am not sure what the exact relationship is either, but I did not think
that bigdata supported sesame-2.7 yet, based on recent release
announcements referencing 2.6.10.

It may turn out that the conneg failures are due to missing Sesame
parser/writer implementations and nanosparqlserver may be dropping back to
SPARQL Results XML as a failsafe backup. If that is the case, you could
either backport the modules (not sure how much effort that would take but
it shouldn't be too difficult if necessary), or wait until bigdata has a
dependency on sesame-2.7 to start relying on SPARQL Results JSON for
boolean results.

Cheers,

Peter

On 30 July 2013 13:09, Jeremy J Carroll <jj...@sy...> wrote:

> the result exhibits with the nanosparqlserver. I do not understand the
> architecture enough to know how much sesame code that uses.
>
> Jeremy J Carroll
> Principal Architect
> Syapse, Inc.
>
>
>
> On Jul 29, 2013, at 8:06 PM, Peter Ansell <ans...@gm...> wrote:
>
> Hi Bryan, Jeremy,
>
> Sesame-2.6 did not support SPARQL Results JSON Boolean results, if that is
> related to this issue. That feature was added in Sesame-2.7.0 [1]
>
> Cheers,
>
> Peter
>
> [1] https://openrdf.atlassian.net/browse/SES-535
>
> On 30 July 2013 10:16, Bryan Thompson <br...@sy...> wrote:
>
>>  Sure. Problem is likely in conneg code of webapp package. Post ticket.
>>
>>  Would be GREAT to get curl examples for rest api.
>>
>>  Am back in us and will have more bandwidth soon for things.
>>
>>   B
>>
>>
>>
>> -------- Original message --------
>> From: Jeremy J Carroll <jj...@sy...>
>> Date: 07/29/2013 8:13 PM (GMT-05:00)
>> To: Big...@li...
>> Subject: [Bigdata-developers] json and ask: trac 704
>>
>>
>>
>>  json response does not seem to work with SPARQL ask, see
>>
>>  https://sourceforge.net/apps/trac/bigdata/ticket/704
>>
>>  i.e.  curl -H "Accept: application/sparql-results+json"
>> --data-urlencode query='ask {}' http://localhost:2333/sparql
>>
>>  incorrectly returns XML
>>
>>  I am going to go for a work around right now, but hope to assign time
>> at the end of the week to work on this issue, which is a problem for me,
>> and my uninformed guess is that the fix is trivial.
>>
>>  My understanding of a call I had with Mike is that an approach we could
>> take is:
>> 1) I fix the issue to my satisfaction on a syapse copy of the bigdata
>> code base
>> 2) I can deploy that internally as my hot fix
>> 3) I create a patch, add it to the trac ticket and reassign the ticket to
>> Mike or Bryan
>>
>>  Jeremy J Carroll
>> Principal Architect
>> Syapse, Inc.
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Get your SQL database under version control now!
>> Version control is standard for application code, but databases havent
>> caught up. So what steps can you take to put your SQL databases under
>> version control? Why should you start doing it? Read more to find out.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Bigdata-developers mailing list
>> Big...@li...
>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>
>>
>
>