good afternoon;
> On 2017-10-09, at 12:03, George News <george.n...@gmx.net> wrote:
>
> On 2017-10-09 11:53, Lorenz Buehmann wrote:
>>
>>
>> On 09.10.2017 10:22, George News wrote:
>>> Hi all,
>>>
>>> Here it goes. The MWE is below.
>>>
>>> As you can see when I execute Q_without.rq I get an empty array in
>>> bindings. However with Qmax_without.rq I get {} (empty object) in
>>> bindings.
>>>
>>> What I'm saying is that if I'm getting nothing when listing the
>>> matching entities, I don't know why I get an empty object when
>>> listing the matching entities with an aggregate operation like MAX.
>>>
>> Well, I guess Andy already gave you the answer in the beginning of
>> the thread: A query with an aggregate always returns a row by
>> convention. But compared to the aggregate function COUNT which simply
>> can return 0 then, MAX can't return any concrete value because the
>> MAX of nothing is not specified.
>
> I understood it, but I don't agree with this behaviour. Is this in the
> standard or is it just Jena behaviour?
the recommendation describes the intended behaviour here :
https://www.w3.org/TR/sparql11-query/#aggregateAlgebra
> …
best regards, from berlin,
---
james anderson | ja...@dydra.com | http://dydra.com
