[Auscope-geosciml] RE : RE : wfs filter

[Simon Cox]

It’s a mixture of (a) the Xpath subset and (b) query nesting logic
In the WFS 1.x specs. 
Both have been fixed in WFS 2.0.  


--------------------------------------------------------
Simon Cox

European Commission, Joint Research Centre, 
Institute for Environment and Sustainability, 
Spatial Data Infrastructures Unit, TP 262 
Via E. Fermi, 2749, I-21027 Ispra (VA), Italy 
Tel: +39 0332 78 3652
Fax: +39 0332 78 6325
mailto:simon.cox at jrc.ec.europa.eu 
http://ies.jrc.ec.europa.eu/simon-cox 

SDI Unit: http://sdi.jrc.ec.europa.eu/ 
IES Institute: http://ies.jrc.ec.europa.eu/
JRC: http://www.jrc.ec.europa.eu/
--------------------------------------------------------

-----Original Message-----
From: auscope-geosciml-bounces at lists.arcs.org.au
[mailto:auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of Stephen M
Richard
Sent: Thursday, 3 September 2009 20:19
To: Boisvert, Eric
Cc: auscope-geosciml at lists.arcs.org.au; Robin,Alexandre
Subject: Re: [Auscope-geosciml] RE : RE : wfs filter

Is the xpath processor not recognizing codespace criteria a WFS
implementation issue, or does the spec actually say codespace criteria on
xpath are not processed in wfs filter?
steve

Boisvert, Eric wrote:
> Actually, you can't, or at least not to the point that codeSpace is of any
use.  Filter sees the world in denormalised form.
>  
> consider this instance
>  
> <Feature>
>   <gml:name codeSpace="urn:1">concept_a</gml:name>
>   <gml:name codeSpace="urn:2">concept_b</gml:name>
> </Feature>
>  
> We want to select concept_a of codeSpace urn:2 (this instance should 
> not match)
>  
> <ogc:And>
>    <ogc:PropertyIsEqualTo>
>      <ogc:PropertyName>gml:name</ogc:PropertyName>
>      <ogc:Literal>concept_a</ogc:Literal>
>    </ogc:PropertyIsEqualTo>
>    <ogc:PropertyIsEqualTo>
>      <ogc:PropertyName>gml:name/@codeSpace</ogc:PropertyName>
>      <ogc:Literal>urn:2</ogc:Literal>
>    </ogc:PropertyIsEqualTo>
> </ogc:And>
>  
> will match the instance
>  
> This problem has been reported some times ago.
>  
> This means that we can't really target specific codeSpace when we query a
term, codeSpace are useless in filter.
> I know it is unlikely that many codeSpace for the same property are to be
present in the same feature (gml:name is the only one I can think of), but
just to point out that codeSpace can't be use to tell term apart in
WFS/Filter.  You might as well ignore codeSpace filtering altogether. and
hope that the term is unique.
>  
> I don't think it's a show stopper, it will return false positive in the
worst case scenario. 
>  
> Eric
>  
>  
>  
>
>  
> ________________________________
>
> De: auscope-geosciml-bounces at lists.arcs.org.au de la part de Simon Cox
> Date: jeu. 2009-09-03 05:31
> À: auscope-geosciml at lists.arcs.org.au; steve.richard at azgs.az.gov
> Cc: 'Robin, Alexandre'
> Objet : Re: [Auscope-geosciml]RE : CGI Value abomination 
> [SEC=UNCLASSIFIED]
>
>
>
> Yes - I still strongly urge y'all to attempt a 'cull' of the 
> soft-typed values, and replace them with ScopedName (this _is_ 
> ControlledConcept Steve!) or Measure wherever possible.
> As Eric points out, you can actually write filters against those.
>
>
>
>   

--
Stephen M. Richard
Section Chief, Geoinformatics
Arizona Geological Survey
416 W. Congress St., #100
Tucson, Arizona, 85701 USA

Phone: 
Office: (520) 209-4127
Reception: (520) 770-3500
FAX: (520) 770-3505

email: steve.richard at azgs.az.gov

_______________________________________________
Auscope-geosciml mailing list
Auscope-geosciml at lists.arcs.org.au
http://lists.arcs.org.au/cgi-bin/mailman/listinfo/auscope-geosciml