Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Date: Thu, 26 Apr 2012 21:52:50 +0000 (UTC)
From: "Damian Steer (JIRA)" <jira@apache.org>
To: jena-dev@incubator.apache.org
Message-ID: <624036558.490.1335477170467.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <244820656.374.1335474891311.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (JENA-238) construct query where clause does not
 seem to work as advertised
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JENA-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263171#comment-13263171 ] 

Damian Steer commented on JENA-238:
-----------------------------------

>From http://www.w3.org/TR/sparql11-query/#constructWhere

"A short form for the CONSTRUCT query form is provided for the case where the template and the pattern are the same and the pattern is *just a basic graph pattern* (no FILTERs and no complex graph patterns are allowed in the short form)."

Unless this has changed that would mean no OPTIONAL or UNION in the where clause.
                
> construct query where clause does not seem to work as advertised
> ----------------------------------------------------------------
>
>                 Key: JENA-238
>                 URL: https://issues.apache.org/jira/browse/JENA-238
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: ARQ, LARQ
>    Affects Versions: ARQ 2.9.0, LARQ 1.0.0
>         Environment: Windows Vista 32-bit
>            Reporter: Andrew Crapo
>
> Here are two queries:
> select ?o ?o1 ?o2 where {<http://sadl.org/AssetManagement/ALoco#LocoA> 
> 	<http://com.ge.research.sadl/locomotive#poweredBy> ?o  . 
> 	OPTIONAL {?o <http://com.ge.research.sadl/locomotive#operatingTemperature> ?o1} .
> 	OPTIONAL {?o <http://com.ge.research.sadl/locomotive#desiredOperatingTemperature> ?o2}}
> 	
> construct where {<http://sadl.org/AssetManagement/ALoco#LocoA> 
> 	<http://com.ge.research.sadl/locomotive#poweredBy> ?o  . 
> 	OPTIONAL {?o <http://com.ge.research.sadl/locomotive#operatingTemperature> ?o1} .
> 	OPTIONAL {?o <http://com.ge.research.sadl/locomotive#desiredOperatingTemperature> ?o2}}
> My understanding is that the where clause for construct should handle OPTIONAL. The first query works fine, the second query has a parse error. The same is true if I try to use a construct query with a UNION in it--it will not parse.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira