[XESAM] Minutes of meeting 2007-05-15

[Mikkel Kamstrup Erlandsen]

2007/5/20, Fabrice Colin <fabrice.colin at gmail.com>:
>
> Hi all,
>
> I would like to request a change to the Xesam Query Language.
> The schema at http://grillbar.org/xesam/drafts/xesam-query.xsd defines
>
> <xs:complexType name="selectProximityType">
>   <xs:complexContent>
>     <xs:extension base="selectBaseType">
>       <xs:sequence>
>         <xs:group ref="simpleTypes"/>
>         <xs:element name="distance" type="xs:integer"/>
>       </xs:sequence>
>       <xs:attribute name="ordered" type="xs:boolean"/>
>         <!-- May be ignored. If ordered="true" the words should
>              appear in the same order as specified by the listed
> simpleTypes -->
>     </xs:extension>
>   </xs:complexContent>
> </xs:complexType>
>
> I think it would make sense to define 'distance' as an attribute, and give
> a maximum to the simpleTypes group, as follows :
>
> <xs:complexType name="selectProximityType">
>   <xs:complexContent>
>     <xs:extension base="selectBaseType">
>       <xs:sequence>
>         <xs:group ref="simpleTypes" maxOccurs="100"/>
>       </xs:sequence>
>       <xs:attribute name="distance" type="xs:integer"/>
>       <xs:attribute name="ordered" type="xs:boolean"/>
>         <!-- May be ignored. If ordered="true" the words should
>              appear in the same order as specified by the listed
> simpleTypes -->
>     </xs:extension>
>   </xs:complexContent>
> </xs:complexType>
>
> What do you guys think ?


+1 from me.

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?

Cheers,
Mikkel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freedesktop.org/archives/xdg/attachments/20070521/d90fc723/attachment-0001.htm