[Playlist] Schema files and element order

Lucas Gonze lucas.gonze at gmail.com
Wed Feb 14 15:06:00 UTC 2007


On 2/14/07, Sebastian Pipping <webmaster at hartwork.org> wrote:
>         <track>
>                 <location>http://example.com/first/</location>
>                 <annotation>location below will burn us</annotation>
>                 <location>http://example.com/second/</location>
>         </track>
...
> I suppose this is be valid - we are in deep trouble if not.

It is indeed valid.

> >From what I read XSD/WXS does not support unordered elements
> in other ways than <sequence>, <choice> or <all> which all do
> not fit here. Relax NG in contrast does support this: We just
> wrap the body of <track> and <playlist> by <interleave> and
> weare done.
>
> I am curious what you think and suggest about this.

The XSD problem is totally stupid and annoying, since it pushes the
validator's maldesign into the underlying spec.  That said, there
isn't a lot to be done about it, except I suppose to deemphasize XML
Schema validation relative to Relax NG.  That was the reason why
Matthias created the improved 2nd generation RNG code.  Or should we
be more draconian and declare XML Schema to be unable to do the job at
all?

Is that what you have in mind?

-Lucas



More information about the Playlist mailing list