Complex types in DR 11-0021

[MURATA Makoto]

Chris,

Some element names in the proposed addition have never been
used in dml*.xsd.  They certainly need new subclauses.

bash-3.2$ grep "\"cNvCnPr\"" dml*.xsd | wc -l
0
bash-3.2$ grep "\"cNvFrPr\"" dml*.xsd | wc -l
0
bash-3.2$ grep "\"linkedTxbx\"" dml*.xsd | wc -l
0
bash-3.2$ grep "\"txbx\"" dml*.xsd | wc -l
0
bash-3.2$ grep "\"txbxContent\"" dml*.xsd | wc -l
0
bash-3.2$ grep "\"wgp\"" dml*.xsd | wc -l
0
bash-3.2$ grep "\"wpc\"" dml*.xsd | wc -l
0
bash-3.2$ grep "\"wsp\"" dml*.xsd | wc -l
0

I also think that the other elements also need new subclauses,
although they appear
in existing schemas.  Historically, if the same element name appear in
more than one
context, OOXML has always introduced more than one subclause.

Regards,
Makoto

2011/5/28 Chris Rae <Chris.Rae at microsoft.com>:
> Hi all - Murata-san mentioned during the call that DR 11-0021 (Ecma's DR regarding the inadequate specification of DrawingML in WordprocessingML) introduced a number of new complex types without defining them.
>
> I've just had a look into this now - I think actually we don't typically introduce definitions of complex types; we instead define only simple types and elements. Complex types always have an extant instance in an element definition, so they are introduced that way. So I don't think we need to explicitly introduce definitions of the complex types.
>
> Murata-san, am I understanding this correctly?
>
> Enjoy the weekend all,
>
> Chris
>
>



-- 

Praying for the victims of the Japan Tohoku earthquake

Makoto