2007/5/20, Fabrice Colin <<a href="mailto:fabrice.colin@gmail.com">fabrice.colin@gmail.com</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br><br>I would like to request a change to the Xesam Query Language.<br>The schema at <a href="http://grillbar.org/xesam/drafts/xesam-query.xsd">http://grillbar.org/xesam/drafts/xesam-query.xsd</a> defines<br><br>
<xs:complexType name="selectProximityType"><br> <xs:complexContent><br> <xs:extension base="selectBaseType"><br> <xs:sequence><br> <xs:group ref="simpleTypes"/>
<br> <xs:element name="distance" type="xs:integer"/><br> </xs:sequence><br> <xs:attribute name="ordered" type="xs:boolean"/><br> <!-- May be ignored. If ordered="true" the words should
<br> appear in the same order as specified by the listed simpleTypes --><br> </xs:extension><br> </xs:complexContent><br></xs:complexType><br><br>I think it would make sense to define 'distance' as an attribute, and give
<br>a maximum to the simpleTypes group, as follows :<br><br><xs:complexType name="selectProximityType"><br> <xs:complexContent><br> <xs:extension base="selectBaseType"><br> <xs:sequence>
<br> <xs:group ref="simpleTypes" maxOccurs="100"/><br> </xs:sequence><br> <xs:attribute name="distance" type="xs:integer"/><br> <xs:attribute name="ordered" type="xs:boolean"/>
<br> <!-- May be ignored. If ordered="true" the words should<br> appear in the same order as specified by the listed simpleTypes --><br> </xs:extension><br> </xs:complexContent>
<br></xs:complexType><br><br>What do you guys think ?</blockquote><div><br>+1 from me.<br><br>I think it makes it a bit easier to handle since the overall structure of the proximity selector is closer to the other standard ones then. I guess this was your motivation too?
<br><br>Cheers,<br>Mikkel <br></div><br></div><br>