From: Jocelyn <li...@dj...> - 2007-02-22 13:30:44
|
For now, I made the GEANT_GROUP_TASK and GEANT_GROUP_COMMAND. So this is a basic geant task, which can be used as any task. It doesn't have any extra semantic appart from being a tasks containing a sequential group of tasks. The schema should looks like <define name="group"> <element name="group"> <ref name="dir_if_unless"/> <optional> <attribute name="name"/> </optional> <ref name="tasks"/> </element> </define> so a group can include another group and so on, as the example in my previous post. Does it answer the question ? Jocelyn On 2/21/2007 20:08 PM, Eric Bezault wrote: > > How does it look in the schema? Is there a way to express > > that when <group> appears where a task is expected, then > > it should contain tasks. And when it appears in places > > where a foo is expected then it should contain foos, and > > not tasks. > > > |