We all get moments like that! One's former self often seems to have a
rather different view of the world.
Andy
On 18/12/15 09:50, Claude Warren wrote:
no worries Andy, I started looking at that code this AM an thought --
why? What was I thinking when I wrote this? I am going to revisit it this
evening if I get a chance and at least add some comments to explain why.
On Fri, Dec 18, 2015 at 9:08 AM, Andy Seaborne <[email protected]> wrote:
Claude,
Sorry about that. Guess I only did -Pdev builds.
Andy
On 18/12/15 08:10, ASF subversion and git services (JIRA) wrote:
[
https://issues.apache.org/jira/browse/JENA-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063674#comment-15063674
]
ASF subversion and git services commented on JENA-1102:
-------------------------------------------------------
Commit 6a3d329e32f8807754518fa6ed5e7e703503c8ec in jena's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=6a3d329 ]
Fix to QueryBuilder for JENA-1102
SPARQL: EBV of "a"@en should be true but is false
-------------------------------------------------
Key: JENA-1102
URL: https://issues.apache.org/jira/browse/JENA-1102
Project: Apache Jena
Issue Type: Bug
Components: ARQ
Reporter: Richard Cyganiak
Assignee: Andy Seaborne
Priority: Minor
Fix For: Jena 3.1.0
{code}
SELECT ("pass" AS ?result) WHERE { FILTER("Hello") }
{code}
{code}
SELECT ("pass" AS ?result) WHERE { FILTER("Hello"@en) }
{code}
The first has a result, the second doesn’t. Tested on sparql.org.
According to what I think is [the relevant bit of the spec|
http://www.w3.org/TR/sparql11-query/#ebv], both should be true because
they are plain literals and have non-zero length:
bq. If the argument is a plain literal or a typed literal with a
datatype of xsd:string, the EBV is false if the operand value has zero
length; otherwise the EBV is true.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
