RE: [XQueryX] Inconsistency in schema definition

A very easy error to make. I found the same error in another schema I was
using: I was writing a schema-aware stylesheet to work with that schema, and
was completely baffled that an element didn't match (let's say)
"schema-element(whereClause)". The schema had been in use for some time and
of course instances were validating against it quite happily.

Well spotted.

Michael Kay 

> -----Original Message-----
> From: public-qt-comments-request@w3.org 
> [mailto:public-qt-comments-request@w3.org] On Behalf Of Franz 
> Haeuslschmid
> Sent: 06 October 2004 16:17
> To: public-qt-comments@w3.org
> Subject: [XQueryX] Inconsistency in schema definition
> 
> Hello,
> 
> I investigated the XML schema definition for XQueryX and came across a
> passage that stroke me:
> 
> <!-- This is the flwor expression -->
> <xsd:complexType name="flworExpr">
>   <xsd:complexContent>
>     <xsd:extension base="expr">
>       <xsd:sequence>
>         <xsd:choice maxOccurs="unbounded">
>           <xsd:element ref="forClause"/>
>           <xsd:element ref="letClause"/>
>         </xsd:choice>
>         <xsd:element name="whereClause" minOccurs="0"/>
>         <xsd:element name="orderByClause" minOccurs="0"/>
>         <xsd:element name="returnClause"/>
>       </xsd:sequence>
>     </xsd:extension>
>   </xsd:complexContent>
> </xsd:complexType>
> 
> Is it intended, that the elements with name "whereClause", 
> "orderByClause"
> and "returnClause" have no type information? I rather think, 
> it should be
> 
>         <xsd:element ref="whereClause" minOccurs="0"/>
>         <xsd:element ref="orderByClause" minOccurs="0"/>
>         <xsd:element ref="returnClause"/>
> 
> to reference globally defined elements.
> 
> By the way: how will those little changes be incorporated 
> into the working
> draft?
> 
> Regards,
> Franz Häuslschmid.
> 
>

Received on Wednesday, 6 October 2004 15:28:07 UTC