Why are the XML Schema fragments not normative?

[Roland Illig <roland.illig@gmx.de>]

Hi,

your decision to make the XML Schema fragments non-normative has several 
consequences:

1. The normative text doesn't specify the ordering and the number of 
child elements as exactly as the Schema fragments. For example, in the 
<PolicySet> element, some child elements may occur in arbitrary order 
(xs:choice), but the normative text doesn't lose a word about it. So, 
may the child elements appear in arbitrary order? And, what's the 
meaning of the normative text at all? The XML Schema fragments have a 
defined meaning. The meaning of the ordering of the normative text isn't 
defined anywhere, is it?

2. The normative text says that the <PolicyIssuer> element shall have at 
most one <Attribute> child. The Schema fragments talks of an unbounded 
number of <Attribute>s. What's correct?

3. Some quotes in the Schema fragments are "pretty quotes" (5.4), but 
since they are not normative, it doesn't matter. :)

In section 5.8, "one to many" already implies "required", doesn't it?

Roland