> - The options schema uses a different modeling approach than all the others.
> It's not that all the others are consistent but this one seems to be
> introducing yet another way to model options, i.e. all as attributes of one
> element. Maybe we should make it consistent with at least one of the other
> option schemas.
I took this one because it's very compact. So, how should it be done. With
Jsoniq :-)? Or XML module style:
<opt:enable component="function" />
<opt:enable component="index" />
> - The issue I raised about backwards compatibility was my fault. The way it's
> done, is perfectly fine.
> - Wasn't the sources element required for Alexander?
The sources are still there. But not in the sources element anymore.
Your team Zorba Coders is subscribed to branch lp:zorba.
Mailing list: https://launchpad.net/~zorba-coders
Post to : email@example.com
Unsubscribe : https://launchpad.net/~zorba-coders
More help : https://help.launchpad.net/ListHelp