me category that large absolute values
are less precise. So same effect as for xsd:float.
Best regards
Chavdar
-Original Message-
From: Andy Seaborne
Sent: Tuesday, 18 August, 2020 19:07
To: users@jena.apache.org
Subject: Re: Float comparison
On 18/08/2020 10:31, Richard Cyganiak
-Original Message-
From: Marco Neumann
Sent: Wednesday, 19 August, 2020 11:45
To: users@jena.apache.org
Subject: Re: Float comparison
Andy, yes I would agree xsd:float can lead to some funky behavior here due to
precision. While you are at it this could also explain why ?y is bound to ?x
the decimal. Start with a decimal.
>
> xsd:decimal("0.1001244561")
> or "0.1001244561"^^xsd:decimal
> or 0.1001244561 (in Turtle and SPARQL).
>
> > but I guess this falls in the same category that large absolute values
> are less precise. So same e
561"^^xsd:decimal
or 0.1001244561 (in Turtle and SPARQL).
but I guess this falls in the same category that large absolute values are less
precise. So same effect as for xsd:float.
Best regards
Chavdar
-Original Message-
From: Andy Seaborne
Sent: Tuesday, 18 August, 202
decimal does not seem to help, but I guess this falls in the
> same category that large absolute values are less precise. So same
> effect as for xsd:float.
>
> Best regards
> Chavdar
>
>
>
> -Original Message-
> From: Andy Seaborne
> Sent: Tuesday, 18 August,
decimal does not seem to help, but I guess this falls in the same
> category that large absolute values are less precise. So same effect as for
> xsd:float.
>
> Best regards
> Chavdar
>
>
>
> -Original Message-
> From: Andy Seaborne
> Sent: Tuesday, 18 August, 2020
, 18 August, 2020 19:07
To: users@jena.apache.org
Subject: Re: Float comparison
On 18/08/2020 10:31, Richard Cyganiak wrote:
> The xsd:float datatype represents IEEE 754 single-precision floating point
> numbers.
>
> As with any floating-point datatype, the precision depends
perator for RDF termequality, and SPARQL "=" for value
comparison (by op:numeric-equal):
Andy
But on SPARQL float comparison I got an advise to check in this mailing list
for other opinions.
I understand that SPARQL comparison is mathematically based so 1.0 should be
this
> for the interest of others in the list
>
>
>
> But on SPARQL float comparison I got an advise to check in this mailing list
> for other opinions.
>
> I understand that SPARQL comparison is mathematically based so 1.0 should be
> equal to 1. However below in item 2 you will
Hello
I posted the message below to the TopBraid users mailing list and already
clarified that as sh:equals is based on RDF node equality, values such as
"1.0"^^xsd:float and "1"^^xsd:float count as distinct. So I am keeping this for
the interest of others in the list
10 matches
Mail list logo
