Making RELAX NG schemas normative rather than non-normative
eb2m-mrt at asahi-net.or.jp
Wed Mar 16 22:07:48 CET 2011
> That aside, more importantly, I'd like to know just what real-world problem
> does the making RELAX NG schemas normative actually solve?
The answer is shown in the log of DR-10:0030, which I referenced.
>The RELAX NG schemas specify root elements of each OPC part, while
>the XSD schemas do not. For example, DrawingML_Chart.rnc specifies
>that the root element of the OPC part DrawingML Chart is a chartSpace
>The RELAX NG schemas use the & operator for allowing different
>elements without specifying constraints on their sequences, but it is
>not always possible to use the xsd:all construct in W3C XML
>Schema. For example, wml.rnc uses the & operator in w_EG_RPrBase, but
>wml.xsd does not use xsd:all in EG_RPrBase.
>The RELAX NG schemas represent co-occurrence constraints between
>elements and attributes. For example, pml.rnc specifies that the pic
>element and the attribute spid in p_CT_OleObject are mutually
>exclusive. Meanwhile, pml.xsd simply allows both in CT_OleObject.
>VML drawing parts (Part 4, §8.1) can be validated against RELAX NG
>schemas, but cannot be validated against XSD schemas. This is because
>there are no XSD schemas for the unqualified xml element, which is the
>root element of VML drawing parts.
Makoto <EB2M-MRT at asahi-net.or.jp>
More information about the sc34wg4