[Playlist] Schema files and element order

[Sebastian Pipping]

Tim Mccune wrote:
> Yes, but you can still achieve the behavior that you describe.
> 
> <xsd:choice>
>     <xsd:sequence>
>         <xsd:sequence>
>             <xsd:element name="def" maxOccurs="unbounded"/>
>             <xsd:element name="abc" minOccurs="0"/>
>         </xsd:sequence>
>         <xsd:element name="def"/>
>     </xsd:sequence>
>     <xsd:sequence>
>         <xsd:element name="def" maxOccurs="unbounded"/>
>     </xsd:sequence>
> </xsd:choice>

---------------------------------------------------------------
I suppose there we can find a solution like this
but do we really want to do this for XSPF?

I planned to make such a list anyway so here is
a hopefully correct regex-style summary direct
children of <playlist> and <track>.


== Track ==
album          ?
annotation     ?
creator        ?
duration       ?
extension        *
identifier       *
image          ?
info           ?
link             *
location         *
meta             *
title          ?
trackNum       ?


== Playlist ==
annotation     ?
attributions   ?
creator        ?
date           ?
extension        *
identifier     ?
image          ?
info           ?
license        ?
link             *
location       ?
meta             *
title          ?
tracklist          1


I tried to do some math on the number of combinations
but it was harder then I thought so no numbers for now.

For handmade XSD we really need another solution.



Sebastian