Re: Foreach description discrepancies

Petr Kuba <kuba@optimsys.cz> writes:

> Proposed change:
> Remove the elements that cannot appear in executable content from the
> XML Schema.

Here are the changes I suggest to the schema, I haven't checked instances
yet, but I welcome checks from anyone:

- the type "foreach-full.type" is renamed and redefined so that
are no longer allowed: break, emphasis, mark, phoneme, prosody,
say-as, sub, voice and structure. Only "executable.content" remains.

    <xsd:complexType name="foreach-not-in-prompt.type" mixed="true">
      <xsd:annotation>
        <xsd:documentation>This type is for foreach elements that appear outside of prompts, in executable content</xsd:documentation>
      </xsd:annotation>
      <xsd:group ref="executable.content" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:attribute name="item" type="RestrictedVariableName.datatype" use="required"/>
      <xsd:attribute name="array" type="Script.datatype" use="required"/>
    </xsd:complexType>

- the type "foreach-restricted.type" is renamed "foreach-in-prompt.type".
Its definition is unchanged.

Max.